Database Develop

[Q][HELP] Any experienced XDA'er in Edmonton, Alberta Canada?

Hi All,
As the title reads... I am looking for an experienced XDA'er here in Edmonton, Alberta, Canada to help me out. Allow me to explain...
I purchased my Galaxy S (I9000M) at the end of August 2010 coming from a Samsung Omnia i910 WM6.1. I wanted to move to Android due to its vast opensource abilities and so I could learn to mod, flash, etc and really enjoy what a "smartphone" has to offer but since getting the phone, all I have read is how terrible it is, how it breaks, bad gps, faulty internal sd card, etc, etc, etc and so most of my reading here on XDA since getting my SGS has been about this type of thing and not about the GOOD stuff.
Now with this being said, I have been one of the lucky ones so it seems. My GPS is not the greatest but it is not bad for what I ever need it for. I have never had my sd card fail ("KNOCK ON WOOD") and at the same time, I have never flashed anything through Odin, CWM etc. I have only ever flashed through Kies and I am now on the newest FroYo for Bell Mobility which is JL2.
Seeing as how I seem to have been lucky with my phone, I have started reading more on how to flash kernels, custom ROMs, etc and I am now more interested than ever especially since Samsung has supposedly said that this JL2 firmware has fixed the bugs that were killing i9000M's by the boat load but... I am scared to get past the reading and just take the damn plunge so...
I am looking for an experienced XDA'er here in Edmonton who may be able to offer me the assistance of "showing me" exactly how and what needs to be done to "properly" flash a custom kernel, ROM, theme(s), etc and perhaps even give me a lesson or two in the Android system itself as I really do like this type of thing. I am not dumb or anything but coming from a WM phone and being someone who has grown up only on Windows there are definitely things that I dont get about Linux and Android and some of the terminology is quite confusing.
I would be willing to "donate" for the help and/or lesson(s) and I really hope there is someone out here that would be willing the help me out.
Please PM me or even post a reply here if you are interested in being of assistance and I ask everyone else to please be kind with your replies as I am looking to learn here and do not wish to be discouraged by rude comments.
Thank You in advane...
yiannisthegreek

Anyone in the Edmonton area?

It'd probably be easier to get someone to help you online, or simply to teach yourself. It really isn't too difficult to follow a guide in order to flash a kernel, ROM, etc.
Also, people aren't going to respond instantly, so you should probably wait longer than an hour and a half before bumping this topic.

seeARMS said:
It'd probably be easier to get someone to help you online, or simply to teach yourself. It really isn't too difficult to follow a guide in order to flash a kernel, ROM, etc.
Also, people aren't going to respond instantly, so you should probably wait longer than an hour and a half before bumping this topic.
Click to expand...
Click to collapse
Thanks for the reply seeARMS. Ya I know... Im a bit impatient which I guess is another one of my issues with flashing. Like I said... I have read a bunch and for example, today I was going to try flashing Hardcores K12j kernel and I downloaded it and I downloaded Odin and I got confused at the instructions as follows...
"Download Odin from from here. Extract the Odin.exe file into a temporary folder, for example C:\Temp\Odin\." (I extracted it to my Downloads folder)
Download the SpeedMod kernel.
If you are using the Galaxy S, download the kernel from here.
If you are using the AT&T Captivate, download the kernel from here.
Make sure to download the Odin flashable version (not the -CWM version).
Extract the speedmod-kernel-x-y.tar file from the zip file into the same directory as Odin. (Again... I extracted it to my Downloads folder. I dont think I understand what it means by saying te "extract it to the same directory")
Now here is where I get stuck and give up. I know its silly but I was hoping that someone could physically show me how to do this, get it done and from there I could learn from that person so I could then do it on my own.
Ya... I know it sounds stupid. Perhaps you could explain the Odin thing for me above where I am getting stuck? That would be a great help to start...

yiannisthegreek said:
Thanks for the reply seeARMS. Ya I know... Im a bit impatient which I guess is another one of my issues with flashing. Like I said... I have read a bunch and for example, today I was going to try flashing Hardcores K12j kernel and I downloaded it and I downloaded Odin and I got confused at the instructions as follows...
"Download Odin from from here. Extract the Odin.exe file into a temporary folder, for example C:\Temp\Odin\." (I extracted it to my Downloads folder)
Download the SpeedMod kernel.
If you are using the Galaxy S, download the kernel from here.
If you are using the AT&T Captivate, download the kernel from here.
Make sure to download the Odin flashable version (not the -CWM version).
Extract the speedmod-kernel-x-y.tar file from the zip file into the same directory as Odin. (Again... I extracted it to my Downloads folder. I dont think I understand what it means by saying te "extract it to the same directory")
Now here is where I get stuck and give up. I know its silly but I was hoping that someone could physically show me how to do this, get it done and from there I could learn from that person so I could then do it on my own.
Ya... I know it sounds stupid. Perhaps you could explain the Odin thing for me above where I am getting stuck? That would be a great help to start...
Click to expand...
Click to collapse
Sure. So, you have your Downloads folder, with the Odin.exe file in it. Open it up. Now, open up the Speedmod ZIP file you downloaded. (Should be called something like: "speedmod-kernel-k12k-500hz.zip") Inside this file, you should find a similarly named .TAR file. This is the file we're going to be flashing.
Extract this .TAR file anywhere (for simplicity, just extract it into the Downloads folder where your odin.exe file is). With Odin open, click the "PDA" button on the right side, and navigate to where the .TAR file is. Select the TAR file.
Make sure Odin looks exactly like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(MAKE SURE NOTHING ELSE IS CHECKED)
After doing this, put your phone into Download mode up holding the volume down + home button + power button until you see the "SAMSUNG" text. You should now see the following on your screen:
After you see this, connect your phone to your computer, and click "Start". You're done!
To verify it flashed correctly, after your phone boots, go to Settings -> About, and make sure Kernel said "Speedmod".
If you need any more help, just ask.

@seeARMS,
When I try to "open" or extract anything from the .zip file all I see inside it is something called "zimage". I use winrar to unzip files.
When I double click the kernal file and winrar opens, it says that the .zip IS the .tar so what do I do? Do I extract the zimage file and drop that into odin or do I just drop the .zip file in?
Please explain... and THANKS for your help...
EDIT: Can you tell me what kernel you are using and why?

yiannisthegreek said:
@seeARMS,
When I try to "open" or extract anything from the .zip file all I see inside it is something called "zimage". I use winrar to unzip files.
When I double click the kernal file and winrar opens, it says that the .zip IS the .tar so what do I do? Do I extract the zimage file and drop that into odin or do I just drop the .zip file in?
Please explain... and THANKS for your help...
EDIT: Can you tell me what kernel you are using and why?
Click to expand...
Click to collapse
You want to import the .TAR file into Odin, not the zImage file.
If you're interested in flashing my custom ROM visit this thread and read the second post (installation instructions).
P.S. That ROM uses the latest SpeedMod kernel, K12K. There are basically two kernels I'd choose from: this, and the Voodoo kernel (or the variation of the voodoo kernel, the Advanced Voodoo kernel). I've tried both, and although they're similar, I prefer the SpeedMod kernel. Personally I believe it's generally faster, but a ton of ROM devs have different opinions.
If you need any extra help, feel free to ask.

seeARMS said:
You want to import the .TAR file into Odin, not the zImage file.
If you're interested in flashing my custom ROM visit this thread and read the second post (installation instructions).
P.S. That ROM uses the latest SpeedMod kernel, K12K. There are basically two kernels I'd choose from: this, and the Voodoo kernel (or the variation of the voodoo kernel, the Advanced Voodoo kernel). I've tried both, and although they're similar, I prefer the SpeedMod kernel. Personally I believe it's generally faster, but a ton of ROM devs have different opinions.
If you need any extra help, feel free to ask.
Click to expand...
Click to collapse
So then the.zip IS the .tar? And if I want to flasy your rom then I need this kernal first for 2e recovery correct?

I've only had my Galaxy i9000 for about a month, but I can tell you not to worry about all the negatives you've been hearing. There are many, many positives that really go "untold" in comparison to people complaining
Trust me, you'll enjoy the phone

Kops said:
I've only had my Galaxy i9000 for about a month, but I can tell you not to worry about all the negatives you've been hearing. There are many, many positives that really go "untold" in comparison to people complaining
Trust me, you'll enjoy the phone
Click to expand...
Click to collapse
I REALLY hope so. Im gunna try my very first kernel flash here right away thanks to seeARMS help and then Im gunna try out his new JL2 ROM as a Thank You for my very first custom ROM!!! Wish me luck...

Much THANKS to seeARMS!!!
Thanks so much seeARMS for taking the time and effort to help guide me into my FIRST kernel flash which will lead me to flashing your new JL2 ROM as a true show of my appreciation!!!
I dont have a PayPal acct (yet) but Im going to get one and I will be sending you a donation for your help and support!!!
Thanks again and also, thanks for creating for our Canadian SGS i9000M's!!!

Yes and if you really do get stuck I do live in edmonton, alberta. I've gone through my fair share of ups and downs with this phone and have a working knowledge, and now on my way learning on creating custom themes. There are a few tricks for the most part your learn as you go, but mostly when you start tweaking and adding in lagfix's. But from my experience try to flash custom kernel. I recommend Hardcore's speedmod also. He is constantly tweaking and always updating. Which is a curse in one hand and a blessing in another. After flashing his kernel all you have to do is download custom firmwares to the internal sd card and update through ROM Manager / Recovery Mode. Be aware that BELL I9000M are a very finicky phone when it comes to the SDcard failing. You won't be warned most of the time of failures until apps just start force closing on you after a flash to days later. It a chance you take and sometimes feels like its the direct cause of a flash, but its not. I believe the equipment is faulty to begin with. Stressing of the SD card whether flashing or recording video's or other heavy operation will have the same effect on the internal SD card in terms of it failing.

Woolios said:
Yes and if you really do get stuck I do live in edmonton, alberta. I've gone through my fair share of ups and downs with this phone and have a working knowledge, and now on my way learning on creating custom themes. There are a few tricks for the most part your learn as you go, but mostly when you start tweaking and adding in lagfix's. But from my experience try to flash custom kernel. I recommend Hardcore's speedmod also. He is constantly tweaking and always updating. Which is a curse in one hand and a blessing in another. After flashing his kernel all you have to do is download custom firmwares to the internal sd card and update through ROM Manager / Recovery Mode. Be aware that BELL I9000M are a very finicky phone when it comes to the SDcard failing. You won't be warned most of the time of failures until apps just start force closing on you after a flash to days later. It a chance you take and sometimes feels like its the direct cause of a flash, but its not. I believe the equipment is faulty to begin with. Stressing of the SD card whether flashing or recording video's or other heavy operation will have the same effect on the internal SD card in terms of it failing.
Click to expand...
Click to collapse
Hi Woolis,
Thanks for the info and the reply. I will definitely keep you in mind should I have a need to have a "pro" look at my phone if it is messed up some how and the fact that you are here in Edmonton is a REAL blessing!!!

[Q] Help With Old Partially Rooted G1

So I have a G1. I rooted it and then tried flashing CM5 (Or 6, I don't remember) but something went wrong so I just dropped this project. I picked it up again because my girlfriend has a dumbphone, so I want to give her this smartphone until I can buy her a better one. When I boot up the G1 normally, it just stays at the boot screen. I am able to get into recovery. However, when I trying to flash CM6 I had to go through a few steps. I flashed CWM Recovery, created a backup, updated radios and such, then flashed Danger SPL. After that (I think that's all I did, it was about a year ago so I don't exactly remember) it reverted to JesusFreke's Recovery(the default recovery installed using the rooting method that I used). The phone is in S-OFF and I believe the H-BOOT Version indicates that Danger SPL was flashed successfully as well, but I'm kind of stuck now. Any help would be appreciated.
Boot Screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recovery:
H-BOOT:

looks like you just about there, i would recommend getting the latest amon_ra recovery for it has more options and will make other tasks easier.
http://forum.xda-developers.com/showthread.php?t=566669
also you should definitely get the latest radio/spl found here
http://forum.xda-developers.com/showthread.php?t=831139
to make things easy start by flashing the rom found here
http://forum.xda-developers.com/showthread.php?t=613809
you have everything almost done, so try to get amon_ra, the 2708 + radio/spl, and flash an awesome new rom --- maybe ezgingerbread or froyobylazslo?
keep at it, it worth it in the end

demkantor said:
looks like you just about there, i would recommend getting the latest amon_ra recovery for it has more options and will make other tasks easier.
http://forum.xda-developers.com/showthread.php?t=566669
also you should definitely get the latest radio/spl found here
http://forum.xda-developers.com/showthread.php?t=831139
to make things easy start by flashing the rom found here
http://forum.xda-developers.com/showthread.php?t=613809
you have everything almost done, so try to get amon_ra, the 2708 + radio/spl, and flash an awesome new rom --- maybe ezgingerbread or froyobylazslo?
keep at it, it worth it in the end
Click to expand...
Click to collapse
Thanks for the response
I'm having a problem. I tried flashing the custom recovery multiple ways but it didn't work. The farthest I got was through fastboot. I installed fastboot on my computer and I have the recovery file in the root of the SD. I put the G1 into fastboot and checked to see if it was detected:
Code:
fastboot devices
HT841GZ06125 fastboot
I assume that means it's detected. Then I ran this:
Code:
fastboot flash recovery recovery-RA-dream-v1.7.0.img
error: cannot load 'recovery-RA-dream-v1.7.0.img'
What's wrong?

The recovery.img you want to flash needs to be in your current working directory our you need to give the full path as a parameter, i.e.
Code:
fastboot flash recovery recovery.img
if the recovery image is in your working directory or
Code:
fastboot flash recocery /home/xyz/work/recovery.img
if the recovery image is located in the directory /home/xyz/work

Wow, I feel so dumb. For some reason I thought fastboot worked through the sdcard, although now I realize that is impossible because the SD wasn't mounted. Happily running CM6.1 now =]

Vulf said:
Wow, I feel so dumb. For some reason I thought fastboot worked through the sdcard, although now I realize that is impossible because the SD wasn't mounted. Happily running CM6.1 now =]
Click to expand...
Click to collapse
Meh I find CM6 gets really slow after a while
You should try Froyobylaszlo
Froyobylaszlo for speed and stability and usability...oh and it looks good
EzGingerbread...if you for some reason really like Gingerbread

I'm a bit at the same stage as Vulf,and just grabbed my G1 out of the dust again, whilst my Sensation XE is being repaired.
I have been struggling for three days now to get a ROM flashed, but I obviously must be doing something wrong. I know there's a whole lot of information available. I been through a lot of topics, and tried different things. I am now kinda frustrated and wondering what I'm doing wrong, and hope someone can help me out.
Take for instance FrankDrey's ROM, I'd love to try it, and just followed your steps perhaps 10 times. But, just like many other ROM's I try to install (i.e CM7.2, ezGingerBread), I end up in the 'hanging G1' screen. I tried using different kernels (perhaps the wrong one?), tried the swipes using 'fastboot', the superswipe and all kinds of things, but I never got anything to work. But... for some reason, there's 1 ROM that did work for me, just not 100%. I tried Froyo DreamTeam ROM, which installed (like most other roms did, except some gave Status 7 boot write error), but this one actually booted up. I could not work with it, because I did not get the 'install wizard', did not see the 'Market', my phone has no lock screen anymore (pressing any button activates the phone), and I could not use my 'Phone' and 'Home' key anymore. (these still work in recovery mode though) I tried different 'gapps' apart from the one being suggested, and been looking at some 'custom ATMD' or so which might be a cause for the 'home' and 'phone' key, but I did not recognize anything in there that I have been doing.
I really hope someone can please help me out, so I can finally get this phone to work again properly (and give it to my sister in a few weeks )
Here's the information fastboot gives me, which seems to be what it should be, I think:
DREAM PVT 32B SHIP S-ON
HBOOT 1.33.0013D (DREA11000)
CPLD-4
RADIO-2.22.28.25
Oct 21 2009:22:33:27
I believe that the Kernel I used was one of EzTerry (excuse me if I misspelled that), the 1.5.1 Froyo based.
Thanks in advance to anyone who's taking time to read and help me out.

With that radio/SPL you should be able to run ezGingerbread without problems. To be sure, do a
fastboot erase system -w
then boot into recovery and flash latest version of Terry's ROM http://sandbox.devnull.name/android/gingerbread/GINGERBREAD-DS-Stable-v1.0-20111204.zip and gapps http://www.multiupload.com/7B0LCBTREB, then boot the ROM. The first boot might take some time ... (>= 5 min)

anddisa should also mention to look at his signature. he has a version of ezgingerbread that is almost the same as ezterrys but has a few nice tweaks to it. if you tap his sig it will link you to a page explaining his version and a dropbox for the files.
oh and anddisa i love your work and all the help you give on xda so in case i never thanked you ill do it in the post above!

Hello AndSisa and demkantor. First I'd just like to say thank you for the help! .
Is the erase system -w better, or is it the same as the 'wipe' from the recovery menu? I tried both just to make sure . Also, I had the feeling that installing another kernel was sort of required for the ROM to work.
Anyway, I followed your steps, but instead, I flashed the ROM from your signature. As demkantor mentioned, for some reason my preference goes to the ADS_Magpie ROM. I also tried that ROM earlier, without any luck I have to add, and I'm afraid I'm facing the same again as I speak . I downloaded the Signed-v1.0 by the way.
I think I'll wait another 10 minutes and try the ezGingerbread rom soon which you posted in your reply (which I tried as well a few times), trying it the way you suggest me. I'll keep my fingers crossed, and will post my result in a reply if no one else has replied after my post, and otherwise I'll edit this post .
Thanks in advance, and when I got my ROM running, I'll make sure to properly thank you using the 'Thank you' button.

Yes with that radio and spl you should be able to flash Frayo, froyobylaszlo, EzGingerbread, and a few other ROMs.
Are you sure you're waiting long enough?
It may take a few minutes...
If you are waiting that long, then hmm...sounds odd...
When you flashed frayo was it the ONLY thing you flashed? Make sure it is.
You don't need to flash any kernels or anything.
Just frayo-signed.zip and that's all...
Btw, my theory is confirmed
Google apps controls the Home/Phone keys, Lockscreen and other stuff!

My 2nd attempt in flashing ezGingerBread turns out to fail as well I'm afraid. I've waited for nearly 10 minutes now (and counting), yet no sign of life.
For some reason, I got a feeling that it just skips to install something or so. For instance, when I install this DreamTeam Froyo, and install the Google Apps they provide (or any other cause none worked for me), it does say "Google Apps installed", or something like that after I flashed the .zip file. However, in the menu, I don't see any Google app at all. Should I try another SD card, or can't it be the SD card? As for the SD card, I partitioned it as some topic advises, I guess yours. (512MB Ext4, 96swap, other GB's FAT32).
As for your ROM, Frankdrey, I tried 4 different methods to be honest. I tried the straight-forward, flash it + gapps. I tried flashing + kernel + gapps, I tried flashing kernel, your rom, and then gapps, and even once without gapps, but without any result .
Also, can it be possible that the kernel I installed is not compatible with the ROM? I flashed the 1.5.2f_S one from Terry, been switching between the Froyo / GIngerbread one depending on the android version.

Nonono...for my ROM you don't need to flash Gapps
Just flash the ROM and thats it!
No kernel, no Gapps
Everything is included!
Both EzGingerBread and Frayo/Froyobylaszlo include the kernel in them!
So you don't need to flash any kernels, just make sure you have the correct SPL/Radio and you're all set!

I feel there is something missing from the equation here. What was the last working rom you had on your g1? Have you ever had a custom mtd? According to what your telling us your radio/spl are ideal, you seem to have the latest recovery and understand fastboot.
Try this mount your sd sd card to make sure it works, take everything off except superwipe and frayo (ease of use) thats all you should need. From recovery flash superwipe.zip then teboot to recovery. Flash frayo.zip the reboot. Wait. Wait. Even as long as 20 min. After that i would sugest just starting over with dreaming.nbh
Sent from my NXM726HN using XDA App

frankdrey said:
Yes with that radio and spl you should be able to flash Frayo, froyobylaszlo, EzGingerbread, and a few other ROMs.
Are you sure you're waiting long enough?
It may take a few minutes...
If you are waiting that long, then hmm...sounds odd...
When you flashed frayo was it the ONLY thing you flashed? Make sure it is.
You don't need to flash any kernels or anything.
Just frayo-signed.zip and that's all...
Btw, my theory is confirmed
Google apps controls the Home/Phone keys, Lockscreen and other stuff!
Click to expand...
Click to collapse
Hey frankdrey, how did you confirm the gapps could be causing the home keys etc problems. What google app(s) is the source?
Sent from my NXM726HN using XDA App

There is another possibillity at least to see what is happening: While booting your phone keep it connected to usb and type
adb logcat
on the console of your PC. At least after one/two minutes you should see something there. On a Linux system you could also do a
adb logcat | tee boot.log
so the output is written into the boot.log file, too.
If you provide later that log, probably we can see what's happening.
Sent from my Gingerbread on Dream using XDA App

I unfortunately can't put a catlog here anymore, but I can say that it's working now! Good start of a working day/week .
What the exact problem is a mystery, and I think it will stay that way.
What I've done is putting the old dreamimg.nbh back on the phone, and started the whole rooting thing all over. The only difference, in actions that I've been doing, is that I did not pick the *cyan* coloured RA Recovery this time.
As for the question if I ran any custom ROM before on this phone, I only used the 'default' rooted ROM so far. On my other G1, things worked like a charm.
Anyway, I just got the 'setup wizard' from Frayo on my screen, so I think I'll start working with it and enjoying it!
I feel a bit silly that I never thought of doing the whole thing over earlier
Thanks for the help and input, and I hope that anyone else facing this issue will get things worked out too.
demkantor said:
Hey frankdrey, how did you confirm the gapps could be causing the home keys etc problems. What google app(s) is the source?
Click to expand...
Click to collapse
I think it's probably based on his previous experience, and the fact that I said something in my previous post like "I did get one ROM to work, but just not 100%. The market wasn't in the apps list, I had no lockscreen (every button activates the phone instantly), my dial (phone) key is not working, nor was my home-button." must have given him the last bit of confirmation he needed .

I think it was that you were flashing a kernel after the ROMs...
You're not supposed to do that for most ROM
And yes about google apps
I think it is the entire google services framework
Ill try look into the code (if there is code for gapps)
And ill see what's up

[Q] - Simple route to GB bootloaders from ICS w/Froyo BL

The title pretty much says it all. I've been reading for days and my eyes are burning yet I still haven't found anything exactly like what I'm asking...and I don't want to keep asking stupid questions in the dev section.....
I was on a custom Froyo ROM for a long time and finally got around to trying out SlimICS 4.2 a couple of weeks ago. The instructions called for a CM9 flash first, then SlimICS. It all worked perfectly and I love the ROM.
I've never tried GB and am still on Froyo bootloaders. I would like to switch to GB bootloaders, maybe for no good reason at all. I figure in the long run it will be a good idea. (different rom, kernel, JB, whatever)
I was told that trying to use Odin to simply flash GB bootloaders over an ICS rom and kernel might be a bad idea. I'm hoping someone has successfully done this but most of my reading has got me feeling a bit cautious about bootloaders...
I'm looking for a simple, logical sequence to get me back exactly where I am (ICS) but with GB bootloaders. Perhaps back to a custom Froyo rom/kernel then flash GB bootloaders then back to ICS? I'm guessing that cwm will be able to restore the state of my current rom after all that. I'm so sick of setting up everything from scratch and Titanium can only do so much....
Thanks

Here ya go...
U cannot flash the GB Bootloaders while you are running a Rom that has the mtd/yaffs or yaffs2 partition, that is, a CM, MIUI, ICS, JellyBean and such like. U will need to be on a bml/rfs partition, that is, a Stock Rom or at least a Dev Rom based from a stock firmware.
Do an Nandroid Backup on what you are running currently.
Backup everything you do want to save...apps, contacts, messages, emails, pics, efs folder, etc.
Then you will need to flash back to Stock GB Firmware with Bootloaders included. The i897ucKK4 is the latest official. Here is Stock I897UCKK4 Android 2.3.5 One Clicks. Use the Odin or Heimdall version that includes the GB Bootloaders. If you have a newer Captivate that does not like using the One Clicks, then see this thread for the .tar package of the i897ucKK4... [ROM] I897UCKK4 [17.11.2011][Android 2.3.5]. With this you will probably have to wipedata/factory reset first. Then use regular Odinv3 1.83 or similar to flash it. **Note: Flashing Bootloaders is risky. So be sure you have a trust worthy micro usb/usb cable, constant power source, etc. You don't want to loose power or connection during the few seconds that the bootloaders are being flashed. Bad bootloader flash = hard brick.
Once you are successfully back on Stock KK4, then go to this thread... [KERNEL][KK4][1/28/11] Corn Kernel and use the regular Odin to flash the .tar 7.0A version of this kernel. This will give you the CWM Recovery that you need.
Then reboot into CWM and reinstall the ICS Rom you were on before per that Rom's install instructions.
Once you are booted up on that ICS Rom, reboot into the Recovery of that Rom and then you can Restore your backup that you did at the beginning of this process.
You should be good now.
For issues along the way with connections to the pc, download mode, etc. please see this thread... Captivate Connection Issues and Download Mode Help

The most direct route would be to flash a Gingerbread-based Stock rom with bootloaders from your current setup. This will put you back at stock (including your partitioning), so you'll have to flash as if you're going to CM-based roms for the first time when you go back to ICS/JB.
Obviously, there's all the normal cautions of backing up, bootloader dangers, etc.

@ jmtheiss... I Ninja'd ya by a few minutes. Lol
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

They both said it better than I could have but what it comes down to is there is no "simple" way to go about what you are wanting to do...
Sent from my SGH-I897 using xda app-developers app

I don't think a lousy "thanks" even begins to cover it. I really appreciate when someone puts that much effort into helping somebody out. Cheers!
And that definitely qualifies as "simple" enough...better than something requiring rooting again and getting a functional recovery, etc. A couple of Odin sessions and a couple of cwm flashes are fine.
Thanks again guys.

bcflyfisher said:
I was told that trying to use Odin to simply flash GB bootloaders over an ICS rom and kernel might be a bad idea. I'm hoping someone has successfully done this but most of my reading has got me feeling a bit cautious about bootloaders...
Thanks
Click to expand...
Click to collapse
I have done it successfully a couple of times without any issues. I have only done it when absolutely necessary since they do say there's some risk there.
What I don't understand is how you *could* run ICS without GB bootloaders? I didn't think that was possible.

I'm living proof. I was hesitant but their instructions said if coming from Froyo flash CM9 first then SlimICS. I flipped a coin and it worked fine. The developer of Slim (krarvind) knows I'm on Froyo bootloaders and didn't seem too phased by it. Whether or not I'd be able to jump to JB with whatever kernel is unknown so I'm going to backtrack a little and do what I probably should have in the first place.

Here's an update of what I did just in case it's helpful to someone else down the road.......
I did my best to follow the suggestions given by 4-2ndtwin in the 2nd post. I generally have pretty good backups of everything done but I did new ones just for kicks. Nandroid, Titanium Backup, efs, SMS, call log, APN, and a few other things. I downloaded all the necessary files, and laid them all out sequentially on my screen so I wouldn't get distracted and screw up. In the end I'm pretty much exactly where I wanted to be but of course there were a few unexpected issues.
- The Heimdall One-Click of stock GB with bootloaders was very easy. I had Samsung drivers on the computer already but Heimdall insisted on installing new ones. After that it did its thing and I was on official KK4 with GB bootloaders.
- Next up was regular Odin flash of the Corn Kernel. When I connected the phone in download mode Odin didn't give me a yellow light. If I connected the phone while it was NOT in download mode Odin recognized it. I wasted at least an hour to discover that it was just a driver issue. The drivers that Heimdall wanted weren't "good enough" for Odin. Interestingly, neither was the original package I had on the computer. The one that worked was called "Samsung_USB_Driver_for_Mobile_Phones.zip" from the Samsung website. After installing that Odin saw my phone in download mode and I was able to install the Corn Kernel. Rebooting into recovery gave an option to root the phone.
- At this point everyone in the world decided they needed something from me so between work and phone calls/texts I ended up using the phone on GB for a while.
- My boot screens had been a total mess since my first custom rom so I decided to do the boot screen fix next - http://forum.xda-developers.com/showthread.php?t=1065743 - TRusselo added a bunch of good info to the thread and there's a good post on page 10 from irishvandal that explains the whole sequence of boot screens and what you can and cannot change.
- So the next step should have been to flash CM9 on my way back to SlimICS just like I did a month ago. I figured since I had been using the phone for a couple of hours I should wipe everything ... so I did the cache, data, format system, dalvik cache, and then I went to flash CM9 and noticed that for some reason I didn't have the zip file on the phone any more. I must have deleted it myself because nothing else spontaneously disappeared. When I rebooted normally to plug the phone in and transfer files I discovered that in wiping/formatting I messed something up and I kept getting stuck on the Corn Kernel boot screen. I could get into recovery or download mode just fine, just no normal boot. I was able to mount storage in recovery but when I tried to copy over the CM9 zip it kept hanging. After numerous attempts I decided to just go right back to the beginning.....
- Heimdall once again wanted its own drivers. No problem, I did that, then uninstalled them and reinstalled the drivers Odin likes, then got Corn again, did the boot screen fix again just to try a different image, then downloaded a new CM9 Nightly and copied it to the SD, flashed it with no issues, then flashed SlimICS (which actually has 2 zips plus addon packages) and I was back to ICS with GB bootloaders. It's amazing how fast things can be done when there are no more surprises!
- When the phone was rebooting into Slim ICS I got a message I don't remember seeing before - "Android is upgrading" or something similar. Weird. The next time I booted to recovery to try to restore the nandroid backup I ended up in CWMR Touch v5.5.0.4, which is weird looking and makes me feel strange. When I tried to do a full restore it encountered a few issues such as not being able to restore data normally. I don't recall the details but when I reinstalled Titanium Backup it would just FC so I couldn't restore any of my other apps. The "solution" was to reflash the Slim zips and do a restore of the system only. This set up all the tedious stuff for me. I got TiBu again and restored apps+data and that worked. Chose my launcher and it was back almost the way I wanted it. Interestingly, I had to replace the widgets but the shortcuts were all there in the right places.
- Voice search force closed. Slim doesn't include it in the base rom but it's available as an add-on and I had the zip on the sd from last time but flashing it didn't fix the problem (it had worked the first time I installed Slim). Some random sequence of freezing the Voice Search app, wiping its data, reflashing the Voice zip, unfreezing the app and it worked. In the process I noticed that in TiBu it was originally listed as Voice Search 2.x.x but then it was suddenly 3.x.x with a different icon. Then an hour later after all kinds of restoring (SMS, call log, etc) voice was force closing again. It was also listed as 2.x.x. This time it took me twice as long to randomly do things until it started working again (and at the same time it turned back into 3.x.x. It's been fine since...
So again a huge thanks for the advice! I got to spend the better part of a day fighting my way through minor issues but I learned a lot about my phone and got over my aversion to Odin for the last time. Hopefully someone else can benefit from something I've gone through. If nothing else, I feel a renewed sense of accomplishment.

^
If all ur ics and jb roms have run well...then i see no need to flash the bootloaders.
Sent from my SAMSUNG-SGH-I897 using xda premium

[Q] Upgrading SPH-P100 from 2.2 to 2.3 or higher

Hi all:
This is my first post here and I am new to the world of Android so please bare with me. I was given an Sprint (unactivated) Galaxy Tab SPH-P100 from work. It was brand new in the box. I am to use it for development purposes, but it stuck on firmware 2.2 (DJ14 baseband) and need at least 2.3 for the apps I have to work on. I also wouldn't mind going higher to maybe ICS. I have been looking all over for information about this specific model, but what I am finding is either outdated with broken links or the comments state it bricked the device. I was able to successfully root the device though. Can someone point me in the right direction of how I upgrade? I know that this tablet is ancient in the realm to technology, but it looks like this forum is active enough. Please keep in mind that I am new to all of this so I might ask a lot of questions. Thanks all!

g.curtisjr said:
Hi all:
This is my first post here and I am new to the world of Android so please bare with me. I was given an Sprint (unactivated) Galaxy Tab SPH-P100 from work. It was brand new in the box. I am to use it for development purposes, but it stuck on firmware 2.2 (DJ14 baseband) and need at least 2.3 for the apps I have to work on. I also wouldn't mind going higher to maybe ICS. I have been looking all over for information about this specific model, but what I am finding is either outdated with broken links or the comments state it bricked the device. I was able to successfully root the device though. Can someone point me in the right direction of how I upgrade? I know that this tablet is ancient in the realm to technology, but it looks like this forum is active enough. Please keep in mind that I am new to all of this so I might ask a lot of questions. Thanks all!
Click to expand...
Click to collapse
I have the same basic problem only I have the AT&T Galaxy Tab with 2.2. It lags a lot when swiping and hangs up for seconds at a time. I really just want to try some other ROMs and maybe upgrade to 2.3 or higher so I can speed it up and let my kids use it. I was able to root it and install ROM Manager from the Market. I tried flashing a couple of ROMs, but they get the same error....
E:failed to verify whole-file signature
E:signature verification failed
-- Appling Muti-CSC...
Installing Muti-CSC
Insallation aborted.
I'm willing to get my hands dirty, but I just can't seem to find the right threads. As he stated above, all the older threads seems to have dead links that lead to iLivid install or Doedexed.com. PLEASE point me in the right direction! I've already put in hours of research, but I'm getting frustrated! THANKS!

Your problem isn't the same.
You are trying to use Samsung stock recovery to flash custom Rom.
You need cwm recovery.
Sent from my GT-N7100 using xda app-developers app

priyana said:
Your problem isn't the same.
You are trying to use Samsung stock recovery to flash custom Rom.
You need cwm recovery.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thanks Priyana. I believe I already have cmw installed although I don't seem to be able to boot into it. I installed ROM Manager and it supposedly installed ClockworkMod 2.5.1.8. It lists ClockworkMod 2.5.1.8 as my current Recovery. It is weird though because when I try to "Reboot into Recovery" it goes into the the Android system recovery <3e>. How do I tell if cwm is actually installed? Or how do I boot into it?

by booting into it, that is how you verify.
No, for Tab 7 you can't use ROM Manager to install CWM.
You need Odin/Heimdall to flash a new kernel that has the CWM in it.

g.curtisjr said:
Hi all:
This is my first post here and I am new to the world of Android so please bare with me. I was given an Sprint (unactivated) Galaxy Tab SPH-P100 from work. It was brand new in the box. I am to use it for development purposes, but it stuck on firmware 2.2 (DJ14 baseband) and need at least 2.3 for the apps I have to work on. I also wouldn't mind going higher to maybe ICS. I have been looking all over for information about this specific model, but what I am finding is either outdated with broken links or the comments state it bricked the device. I was able to successfully root the device though. Can someone point me in the right direction of how I upgrade? I know that this tablet is ancient in the realm to technology, but it looks like this forum is active enough. Please keep in mind that I am new to all of this so I might ask a lot of questions. Thanks all!
Click to expand...
Click to collapse
This might seem a bit obvious, but why not install the Samsung Kies Software on your Workstation and then sync your SPH-P100 to that, it should (Assuming it was running a Stock ROM.), then give you the option of updating the Device up to the last version of Gingerbread which was, or is 2.3.6.
If you want to try installing something newer like ICS or JB. And I would personally skip ICS. 'Cause the Navigation Bar can not be easily disabled or hidden. (e.g. The Back, Menu and Home Buttons are mirrored on the Display as well as on the Device!), I'd just go with a CM10(.1) JB release instead!
If you want some cheap advice on how to play with this I'd recommend you head to the Google Play Store and download an App called "GooManager" This calls up all the ~compatible~ ROMs as listed there for your Device, You can also download and install these ROMs from that App. The only real catch is that you have to be rooted to use it. But, that's simple enough to do to. With the Super-One-Click Root kit.
erechm said:
I have the same basic problem only I have the AT&T Galaxy Tab with 2.2. It lags a lot when swiping and hangs up for seconds at a time. I really just want to try some other ROMs and maybe upgrade to 2.3 or higher so I can speed it up and let my kids use it. I was able to root it and install ROM Manager from the Market. I tried flashing a couple of ROMs, but they get the same error....
E:failed to verify whole-file signature
E:signature verification failed
-- Appling Muti-CSC...
Installing Muti-CSC
Insallation aborted.
I'm willing to get my hands dirty, but I just can't seem to find the right threads. As he stated above, all the older threads seems to have dead links that lead to iLivid install or Doedexed.com. PLEASE point me in the right direction! I've already put in hours of research, but I'm getting frustrated! THANKS!
Click to expand...
Click to collapse
Sounds to me like you haven't properly rooted your Device yet. Try giving the Super-One-Click Root kit a shot, then try again

Ichijoe said:
This might seem a bit obvious, but why not install the Samsung Kies Software on your Workstation and then sync your SPH-P100 to that, it should (Assuming it was running a Stock ROM.), then give you the option of updating the Device up to the last version of Gingerbread which was, or is 2.3.6.
If you want to try installing something newer like ICS or JB. And I would personally skip ICS. 'Cause the Navigation Bar can not be easily disabled or hidden. (e.g. The Back, Menu and Home Buttons are mirrored on the Display as well as on the Device!), I'd just go with a CM10(.1) JB release instead!
If you want some cheap advice on how to play with this I'd recommend you head to the Google Play Store and download an App called "GooManager" This calls up all the ~compatible~ ROMs as listed there for your Device, You can also download and install these ROMs from that App. The only real catch is that you have to be rooted to use it. But, that's simple enough to do to. With the Super-One-Click Root kit.
Sounds to me like you haven't properly rooted your Device yet. Try giving the Super-One-Click Root kit a shot, then try again
Click to expand...
Click to collapse
Actually, Kies will not update my device because this is an original AT&T Tab that was locked down by AT&T and Samsung has not control over it. I think I need to use this Odin to somehow replace the Kernel first. Once I free this thing from AT&T's claws, I should be able to use GooManager or any other ROM manager. Hopefully anyway.
Also, I have rooted the device with Super-One-Click Root kit already so that's not the issue.
Thanks!

erechm said:
Actually, Kies will not update my device because this is an original AT&T Tab that was locked down by AT&T and Samsung has not control over it. I think I need to use this Odin to somehow replace the Kernel first. Once I free this thing from AT&T's claws, I should be able to use GooManager or any other ROM manager. Hopefully anyway.
Also, I have rooted the device with Super-One-Click Root kit already so that's not the issue.
Thanks!
Click to expand...
Click to collapse
As to updating to the ~last supported ROM~ was kinda the idea. What that "ROM" might be for you is in entirely different question. For most GSM (P-1000) Users this would almost certainly be Gingerbread 2.3.6 though. If you had rooted the device you should see see a "SuperUser" Icon. If you still don't "see it" it might be that it failed to install, during the rooting process. In which case you should just download it again from the Play Store. Then you should hopefully be able to elevate your privileges when running Apps such as the GooManager, then.

priyana said:
by booting into it, that is how you verify.
No, for Tab 7 you can't use ROM Manager to install CWM.
You need Odin/Heimdall to flash a new kernel that has the CWM in it.
Click to expand...
Click to collapse
Priyana,
I was able to get cwm loaded and booted into it. I then followed your link to the instructions for Overcome restock. I loaded via Odin and got the green success. But it won't boot up past recovery now. Please see screen shot below. I'm kind of stuck. Can you tell me my next step...
NEVERMIND! I got it working! I decided to try the restock process again and it worked! Thanks Priyana!!! The Overcome Experience is GREAT so far.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Great.
Just thought that it is not quite appropriate for us to discuss P1000 and overcome on a SPH-P100 thread.
For those who read, overcome method is not suitable for CDMA tabs.
Sent from my GT-N7100 using xda app-developers app

[Q&A] [ROM]SGT7 CM11.0 UNOFFICIAL [4.4.4][P1/L/N][Kernel 3.0.x][2015-01-15]

Q&A for [ROM]SGT7 CM11.0 UNOFFICIAL [4.4.4][P1/L/N][Kernel 3.0.x][2015-01-15]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM]SGT7 CM11.0 UNOFFICIAL [4.4.4][P1/L/N][Kernel 3.0.x][2015-01-15]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

I wanted to install this room but now im stuck at CWM. I already flash CWM 3.0.0.5 with odin3 1.7, all went well. I put the zipped rom file in sd card, after I went into cwm menu, i cannot seem to install it from sd card. it seems that I cant mount the sdcard. anyone can help me please?

I was on twrp when i flashed my sgt to cwm. Can i install this rom with twrp in the bootloader? I am concerned i will be bricking my device.

Not boot
I install 15.01.2015 rom but my phone not reboot. Only Galaxy Tab Samsung screen stay.

atoygarh said:
I install 15.01.2015 rom but my phone not reboot. Only Galaxy Tab Samsung screen stay.
Click to expand...
Click to collapse
Which bootloader do you use?

I'm also stuck.
I started out with Overcome 4.1 which has been on this thing for a couple years now at least. So it had recovery and root already, has for a long time. All I did was copy the latest CM11 nightly which was 1-19-2015, and the Banks Gapps Standard 4.4.2 signed.
Since Overcome required recovery, I just hit the power button and told it to reboot into recovery. I had both the above zips installed on my microSD. Told recovery to wipe data/factory reset.
Then told recovery to install the CM zip. Install completed. Rebooted to what looks like a NEW recovery with the hat logo. Told me I didn't have root installed (which is weird, this was rooted, used Root Explorer so I'm not crazy) so I said sure and selected "Yes."
Told recovery to install the Gapps zip. Install shows the new look with the animated android guy's guts open while it installs zip.
Told recovery to reboot. Saw the Cyanogen boot screen after the Samsung one. Scroll bar on Cyanogen finishes, but................. Then it bounces me straight into recovery. Rebooted. Same thing two more times.
I just reinstalled both zips again and tried it. And still keeps bouncing me into recovery.
So I guess the good news is I'm still in recovery. The bad news is my amateur knowledge isn't sure where to go next after a couple hours straight of reading threads.
Help very much appreciated. Gonna charge up the battery while I wait for assistance here.
---------- Post added at 05:27 PM ---------- Previous post was at 05:22 PM ----------
Quick update:
Moments later I rebooted it for yet a third time. Got past the CM progress bar boot screen, and now in some sort of animated screen with the cyanogen logo and an arrow rotating around it (says "cyanogenmod" at the bottom). I am assuming it's doing something so I will leave it and keep and eye on it....
Is that normal? Is this some sort of automated setup point?

So I got it loaded up, but Gapps won't let me sign in with my gmail account. Says "There was a problem communicating with the Google servers. Try again later."
???

Suleeto said:
So I got it loaded up, but Gapps won't let me sign in with my gmail account. Says "There was a problem communicating with the Google servers. Try again later."
???
Click to expand...
Click to collapse
So you said you already have recovery. What recovery do you use?
If yours works, i might as well try it. I was on twrp before this, then i read somewhere it should be on cwm with this rom. So i installed cwm then this is where the problem starts.

I tried a different Gapps and now all is well with that. Now, no FC's that I can see, camera snaps pics. Probably eventually find something but it feels like everything is working presently except for something dock related...
Now, one issue, one concern, one question.
ISSUE: On Overcome, official Samsung dock with HDMI and aux audio worked. I used it on a big stereo. I just set the Tab in the cradle and the sound switched to the cradle audio port (and out to the big stereo). This does not work with the latest CM. Is there something I need to add to restore functionality to the cradle? I hate plugging in my heavy duty audio connector to the top of the Tab while it's in the cradle. Looks terrible and just something to easily get snapped off in a moment of clumsiness. How do I get my cradle to work again?
CONCERN: This thing is.... slower! Yep. I haven't installed a lot... ADW and Pandora and Smart Keyboard. And... Chrome. Which is stupid slow. And as soon as I install Facebook and Facebook Messenger, it's even slower. It was never like this on Overcome. Which is of course Gingerbread, but I figured the main reason to upgrade to Kit Kat was a performance advantage. Did I misunderstand this?
QUESTION: The resolution is a tad bit small. I haven't decided what I think. What is this CM dpi set at to begin with, and what are the safe dpi's and safe way to change them on THIS particular ROM?
---------- Post added at 12:45 PM ---------- Previous post was at 12:08 PM ----------
To be specific, I'm talking about the Samsung Multimedia Dock:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And this is the audio port that isn't working. As far as I can tell the HDMI isn't, either:
If there is some sort of additional APK package I need to flash to restore the use of this, please let me know how and where to get it.

vaah said:
So you said you already have recovery. What recovery do you use?
If yours works, i might as well try it. I was on twrp before this, then i read somewhere it should be on cwm with this rom. So i installed cwm then this is where the problem starts.
Click to expand...
Click to collapse
You shouldn't have problems with twrp so far.. Which rom you have current on your tab?
Suleeto said:
I tried a different Gapps and now all is well with that. Now, no FC's that I can see, camera snaps pics. Probably eventually find something but it feels like everything is working presently except for something dock related...
Now, one issue, one concern, one question.
ISSUE: On Overcome, official Samsung dock with HDMI and aux audio worked. I used it on a big stereo. I just set the Tab in the cradle and the sound switched to the cradle audio port (and out to the big stereo). This does not work with the latest CM. Is there something I need to add to restore functionality to the cradle? I hate plugging in my heavy duty audio connector to the top of the Tab while it's in the cradle. Looks terrible and just something to easily get snapped off in a moment of clumsiness. How do I get my cradle to work again?
CONCERN: This thing is.... slower! Yep. I haven't installed a lot... ADW and Pandora and Smart Keyboard. And... Chrome. Which is stupid slow. And as soon as I install Facebook and Facebook Messenger, it's even slower. It was never like this on Overcome. Which is of course Gingerbread, but I figured the main reason to upgrade to Kit Kat was a performance advantage. Did I misunderstand this?
QUESTION: The resolution is a tad bit small. I haven't decided what I think. What is this CM dpi set at to begin with, and what are the safe dpi's and safe way to change them on THIS particular ROM?
---------- Post added at 12:45 PM ---------- Previous post was at 12:08 PM ----------
To be specific, I'm talking about the Samsung Multimedia Dock:
And this is the audio port that isn't working. As far as I can tell the HDMI isn't, either:
If there is some sort of additional APK package I need to flash to restore the use of this, please let me know how and where to get it.
Click to expand...
Click to collapse
The resolution on all CM versions for our Tab is 160dpi, problems with hdmi and aux audio weren't solved for cm 11.0 and aries kernel. For performance problems: have you tried same apps with Gingerbread? What's the expirience with Gingerbread?

storm31 said:
The resolution on all CM versions for our Tab is 160dpi, problems with hdmi and aux audio weren't solved for cm 11.0 and aries kernel. For performance problems: have you tried same apps with Gingerbread? What's the expirience with Gingerbread?
Click to expand...
Click to collapse
Gingerbread on Overcome 7 4.1.0 was fast for apps and I had a lot more running in the background than CM11 does now, so.... make of that what you will. If you read around on Gingerbread ROMs you will quickly find out Overcome is the most complete, stable ROM out there in GB for our p1000 Tabs. Everything works, and works well.
Is there a good app to benchmark device performance? I could use that and then maybe compare to GB on Overcome. Also would be nice if there was a way to see what processes were taxing the processor like you can do in Windoze.
Also, if CM is 160dpi, what was the original dpi for p1000? 120? Overcome GB used whatever was on the original Froyo OEM ROM. What are the safe resolutions and a good app to change them with on CM11?
Ok, so..... if CM11 doesn't work with multimedia dock stuffs.... what about CM Jelly Bean or ICS? Hell, I just wanted Chrome and you can't run Chrome until ICS or higher if I understand right. If this can't be resolved... considering how piss-poor the performance seems to be... I may be reflashing Overcome again. I bought the dock for the outputs (especially audio). Not to look pretty with a tab in it.

storm31 said:
You shouldn't have problems with twrp so far.. Which rom you have current on your tab?
Click to expand...
Click to collapse
I changed my recovery from twrp humberos(if i'm not mistaken) to cwm, then I did full data wipe, that's where the problem start. I had the rom file in the sd card but my cwm doesn't want to mount the sd card. So now i am stuck at boot.
Previously I have CM rom...but i can't remember what version. It had been far too long.
Can you tell me which twrp i should get? I had the files sometime ago but now its nowhere to be found.

vaah said:
I changed my recovery from twrp humberos(if i'm not mistaken) to cwm, then I did full data wipe, that's where the problem start. I had the rom file in the sd card but my cwm doesn't want to mount the sd card. So now i am stuck at boot.
Previously I have CM rom...but i can't remember what version. It had been far too long.
Can you tell me which twrp i should get? I had the files sometime ago but now its nowhere to be found.
Click to expand...
Click to collapse
Have you now a running Tab or it can't boot now?
I have made restock (and cm reflash) for some time ago with these steps:
1. flash stock rom with odin from here: http://www.androidfilehost.com/?fid=9390225151984927194 (thread: http://forum.xda-developers.com/showthread.php?t=1881981 and thanks to sos_sifou)
2. reboot, copy cm-11.0 rom to internal sd then again download mode
3. flash CF root kernel from here: http://forum.xda-developers.com/showthread.php?t=885734 or overcome kernel (http://forum.xda-developers.com/showthread.php?t=1881981)
4. reboot to cwm, flash cm rom, your tab does reboot to cwm again (kernel and cwm will updated), then again rom and gapps
5. mission completed

I can not.boot. All I did was change recovery to cwm. I can get into cwm but somehow it doesnt want to mount my sdcard. Hence I cannot proceed to install rom.
I'll try your method later when I got home.
Sent from my GT-I9300 using Tapatalk

storm31 said:
Have you now a running Tab or it can't boot now?
I have made restock (and cm reflash) for some time ago with these steps:
1. flash stock rom with odin from here: http://www.androidfilehost.com/?fid=9390225151984927194 (thread: http://forum.xda-developers.com/showthread.php?t=1881981 and thanks to sos_sifou)
2. reboot, copy cm-11.0 rom to internal sd then again download mode
3. flash CF root kernel from here: http://forum.xda-developers.com/showthread.php?t=885734 or overcome kernel (http://forum.xda-developers.com/showthread.php?t=1881981)
4. reboot to cwm, flash cm rom, your tab does reboot to cwm again (kernel and cwm will updated), then again rom and gapps
5. mission completed
Click to expand...
Click to collapse
Where do i get the cwm files?

vaah said:
Where do i get the cwm files?
Click to expand...
Click to collapse
Sorry forget about it, i follow hpyour instruction sxactly and it was great now im running cm 11 smoothly so far, just need to get gapps.
Thanks again for the help

vaah said:
Sorry forget about it, i follow hpyour instruction sxactly and it was great now im running cm 11 smoothly so far, just need to get gapps.
Thanks again for the help
Click to expand...
Click to collapse
I am curious what you consider to be "smoothly". I have everything working (well except Multimedia dock), but it's reeeeeally laggy when you try to do anything.

Yes smoothly meaning can open preloaded app by cm11 no problem. But as mentioned before i havent got the gapps. So i haven't downloaded anything from google play.
Oh also the camera does not work. But i wont take picture with this so i am okay. I wanted to revive my sgt so i was happy when it did.
So what makes your tab laggy? Opening anything is laggy?
Sent from my GT-I9300 using Tapatalk

About laggy opening. Have you moved your apps to the sd card? What type of sd card you have? A slow card? Have you set the type of acces protocol for the sd card in the performance settings or tested one of the settings?
Next thing is the internal one. There are 8, 16 and 32 giga byte tab types from samsung. Also the used type which are used from samsung and the speed of them is very different. Samsung plays so as everyone the cheap joker to get the max price of the product.
Next point is how much you have flashed a new rom. Not every ram chip can handle that with the same precice procedure and lifetime. From one point on the chip is damaged around 15%. I have written my doctor based on all that.
So please provide us with some infos.

I've got a small problem, I installed everything like it should, wiped all data e etc, installed the update twice (I was on 2.36, installed, CWM updated sort of, and I had to install again), installed gapps. But there's one small problem...MY touch screen doesn't work.
Model: GT P1000L