Related
I recently upgraded my captivate with the official att/samsung froyo release. So far it seems to have made my phone worse. It's slower, and freezes periodically. I was wondering if it's possible to root after the official upgrade or is this blocked. Hoping I can root and flash new kernel and get better performance. This droid world is new to me, so any assistance would be appreciated, especially if it's written for a novice.
Btw, I've done 2 master resets hoping it would help, and it didn't.
Here is how to install AT&T's official 2.2 Froyo ROM with all of the suckiness removed and a bunch of awsomeness added.
1. Download this. Rename it update.zip and copy it to sd_card, the the phone's internal memory,not the removable micro sd card.
http://www.mediafire.com/?ve234hbg64ctcu0
2. Download this, and copy it to sd_card.
http://www.designgears.com/roms/cognition/Cognitionv4.3.1.zip
3. Use this tool to flash back to 2.1 (don't master clear)
http://forum.xda-developers.com/showthread.php?t=731989
4. Remove battery, hold vol up + vol down + power and reinsert battery. Phone will boot into recovery mode.
5. In recovery select "reinstal packages". Then reboot
6. If phone reboots back into a the same recovery, repeat 5
7. Phone should boot into a custom recovery.
8. Select install zip -> choose zip -> Cognitionv4.3.1.zip -> install
9. Reboot
cypho said:
Here is how to install AT&T's official 2.2 Froyo ROM with all of the suckiness removed and a bunch of awsomeness added.
1. Download this. Rename it update.zip and copy it to sd_card, the the phone's internal memory,not the removable micro sd card.
http://www.mediafire.com/?ve234hbg64ctcu0
2. Download this, and copy it to sd_card.
http://www.designgears.com/roms/cognition/Cognitionv4.3.1.zip
3. Use this tool to flash back to 2.1 (don't master clear)
http://forum.xda-developers.com/showthread.php?t=731989
4. Remove battery, hold vol up + vol down + power and reinsert battery. Phone will boot into recovery mode.
5. In recovery select "reinstal packages". Then reboot
6. If phone reboots back into a the same recovery, repeat 5
7. Phone should boot into a custom recovery.
8. Select install zip -> choose zip -> Cognitionv4.3.1.zip -> install
9. Reboot
Click to expand...
Click to collapse
Dont you think you should have told the op that those are directions for flashing Cognition 4.3.1?? What if he doesn't want to flash a rom, just a kernel?
OP: Download Superclick v1.7. It will root your phone. From there, search Development threads for a kernel.
cypho said:
Here is how to install AT&T's official 2.2 Froyo ROM with all of the suckiness removed and a bunch of awsomeness added.
1. Download this. Rename it update.zip and copy it to sd_card, the the phone's internal memory,not the removable micro sd card.
http://www.mediafire.com/?ve234hbg64ctcu0
2. Download this, and copy it to sd_card.
http://www.designgears.com/roms/cognition/Cognitionv4.3.1.zip
3. Use this tool to flash back to 2.1 (don't master clear)
http://forum.xda-developers.com/showthread.php?t=731989
4. Remove battery, hold vol up + vol down + power and reinsert battery. Phone will boot into recovery mode.
5. In recovery select "reinstal packages". Then reboot
6. If phone reboots back into a the same recovery, repeat 5
7. Phone should boot into a custom recovery.
8. Select install zip -> choose zip -> Cognitionv4.3.1.zip -> install
9. Reboot
Click to expand...
Click to collapse
this is horrible advice for someone running 2.2. 2.2 brought 3e recovery which does not allow flashing 'update.zip' any more.
all the OP was looking for was how to root.
SuperOneClick 1.7 will take care of that in the RAGE method....
Pirateghost said:
this is horrible advice for someone running 2.2. 2.2 brought 3e recovery which does not allow flashing 'update.zip' any more.
all the OP was looking for was how to root.
SuperOneClick 1.7 will take care of that in the RAGE method....
Click to expand...
Click to collapse
Thanks for the Rage part. Keep forgetting that, even when I use it on my phone.
So I tried superclick 1.7 and had no luck. It would say waiting for device, I'd plug in. my phone and then would say it was running, but nothing happened. Tried with debugging on and off. Any advice? Also can you direct me where to get superclick. I'm worried that the site I got it from may be malicious. Also I'm running windows 7, just in case that makes a difference.
http://forum.xda-developers.com/showthread.php?t=803682
make sure you have the drivers installed for you phone, and you have USB debugging ON....it has to be on in order for it to work
Thank you Pirateghost. Got it rooted.
Considering I know very little about all this, is there somewhere you can to direct me to get easy, step by step, directions on how to load a new rom on my phone? I got it rooted using superoneclick v1.7, loaded titanium back up and rom manager. I'm using one click lag fix, although it seems many feel that it's not good. I was thinking of going with cog4. Any suggestions? Your awesome, thanks.
Cdub3 said:
Thank you Pirateghost. Got it rooted.
Considering I know very little about all this, is there somewhere you can to direct me to get easy, step by step, directions on how to load a new rom on my phone? I got it rooted using superoneclick v1.7, loaded titanium back up and rom manager. I'm using one click lag fix, although it seems many feel that it's not good. I was thinking of going with cog4. Any suggestions? Your awesome, thanks.
Click to expand...
Click to collapse
Flashing a rom is quite simple. Obviously I'm going to be biased and suggest Andromeda3 as the recommended ROM, since I put so much time into that rom. Check out the guides and tutorials found in Q&A and development
Sent from my HTC Vision
Most all of the roms here have flashing instructions on page 1 of that thread.
And back up before you start. You can never back up too much.
Sorry about my stupidity, but people keep mentioning 3e recovery being an issue for me since I have froyo. Will odin take care of this? Also does this whole process take me back to eclair or will it still be froyo. It seems the more questions and information, the more this process its intimidating me. Just don't want to ruin my phone
Cdub3 said:
Sorry about my stupidity, but people keep mentioning 3e recovery being an issue for me since I have froyo. Will odin take care of this? Also does this whole process take me back to eclair or will it still be froyo. It seems the more questions and information, the more this process its intimidating me. Just don't want to ruin my phone
Click to expand...
Click to collapse
yes odin will fix this in about 5 seconds or less!
before you start disable lagfix! this is important! but speed mod may just work be cause it has similar lagfix options available in the kernel. still wouldn't try it though.
recovery is part of the kernel. grab a kernel in .tar format. speedmod is great for this
open odin (not one click but full version) put .tar of kernel in pda slot
put phone in download mode (if 3 button is broke you may want to flash back to 2.1 with 3 button fix or another rom with 3-button fix via odin) you can access download mode via use of adb in the mean time.
plug in phone, make sure auto reboot is selected and reformat is not selected.
the left most box in odin should turn yellow. hit start. it takes about 3 seconds. phone will reboot with new kernel all data will be intact.
at that point you can enter recovery mode which will be cwm. you can root from cwm or install a rooted rom that will include another kernel.
kernel flashing doesn't effect data or settings or version number but kernel need to be same android version, eclair rom needs eclair kernel, froyo needs froyo ect. but a 2.2 rom can run 2.2.1 kernel and vice versa. same goes with 2.3 and 2.3.3 ect. also samsung tw roms need tw kernels, sense roms need sense kernels and aosp roms need aosp kernels. and of cource the kernel should be for you phone.
Speedmod is an i9000 kernel, if you want to just root and use stock froyo you will have to flash am I9000 modem.bin or there will be sound issues...
Use the 3e recovery push. Had to use on Vibrant.
Sent from my SAMSUNG-SGH-I897 using XDA App
studacris said:
Speedmod is an i9000 kernel, if you want to just root and use stock froyo you will have to flash am I9000 modem.bin or there will be sound issues...
Click to expand...
Click to collapse
true but you can flash a different kernel afterwards.
if the op want to read all about fixing 3e recovery with adb or other method fine. but a kernel swap is quick and easy.
Dani897 said:
true but you can flash a different kernel afterwards.
if the op want to read all about fixing 3e recovery with adb or other method fine. but a kernel swap is quick and easy.
Click to expand...
Click to collapse
I agree, just informing in case he stuck with a captivate modem with that kernel and couldn't understand the issues he was having.
so i did this, and on odin it says it passed and that it was successful, but when i check my kernel, it doesn't say speedmod. it's just the same stock kernel. I don't have kies, I have kies mini. Don't know if that's the prob. I'm in the US and I didn't think you could get the full kies. My drivers said there was an error, saying the I9000 drivers didn't work. I downloaded the kernel version specific for the ATT captivate sgh-1897. I downloaded the odin version, not the cwm version because that is what the instructions on the tourist in paradise site said to do. what now? I honestly think all I need is the kernel. I'm just looking to make my phone run faster and try to get the most out of my battery.. speedmod kernel seems right up my ally. I don't think I even need to mess with a ROM. So will this not work with kies mini? any help is appreciated
Cdub3 said:
so i did this, and on odin it says it passed and that it was successful, but when i check my kernel, it doesn't say speedmod. it's just the same stock kernel. I don't have kies, I have kies mini. Don't know if that's the prob. I'm in the US and I didn't think you could get the full kies. My drivers said there was an error, saying the I9000 drivers didn't work. I downloaded the kernel version specific for the ATT captivate sgh-1897. I downloaded the odin version, not the cwm version because that is what the instructions on the tourist in paradise site said to do. what now? I honestly think all I need is the kernel. I'm just looking to make my phone run faster and try to get the most out of my battery.. speedmod kernel seems right up my ally. I don't think I even need to mess with a ROM. So will this not work with kies mini? any help is appreciated
Click to expand...
Click to collapse
speedmod might not change the kernel version in about phone, some devs do not change that.
use the 3 button combo to get into recovery mode, does it boot into cwm with green text? if it did you are running speedmod.
also when phone boots it will say sgh-i897 on a black splash screen after the att param.ifs splash screen
if you still have blue samsung 3e recovery and no black galaxy s splash screen there was a problem.
So I do get a different screen when phone fires up. It does say sgh-1897 which is different than before, I can't seen to get the 3 button recovery thing to happen though. Hope it's right, just thought my phone would be faster. Seemed faster with oneclick lag fix. Guess I'm crazy. The phone does seem louder when it fires up, which I read this kernel helps make happen. Is there another way to get to recovery to see if the 3e issue is fixed. If so is there another kernel that would be faster for me or do I need to do the ROM thing next. Also, since I didn't think this worked I tried to install oneclick lag fix again, but couldn't because there wasn't enough space.does this mean speed mod went through. I also did the speed mod flash like 3 times thinking that it wasn't working. is that as problem? Sorry for all the questions. I'm just new to all this and I don't have much computer savy either. Thanks for putting up with me.
ok so you do have speedmod.
for recovery, with phone off, press volume+volume for 2 seconds
continue to hold volume and press power, holding all three till the first splash screen pops up then release.
first decide if you want to keep speedmod, you can root in recovery and flash to a different kernel after, can also flash a new rom now.
speedmod is an i9000 port. it may not work perfect with the kb1 modem. if you flash kc1 modem it will not work with bluetooth calling. i use it as a tool to flash other roms, to root, and to flash other kernels and not deal with 3e, that is the point of me suggesting it. but giving up bluetooth calling isn't a big sacrifice to some people and many do use it like you are.
now if you want speedmod and lagfix you can do that in recovery, speedmod has a universal lagfix. disable this before flashing a voodoo kernel (or stock) if you change it later.
the lagfix has the options to set data, dbdata, or cache to ext2,ext3,ext4,ext4 non journalling, or jfs
it can also set /system to ext4
voodoo settings are /system=ext4
/cache=ext4nj
/data=ext4
/dbdata=ext4
these are the most common settings and are very successfull.
feel free to pm me with questions, rom recomendation, ect...
edit, just noticed you already have root via rageagaintthecage method via superoneclick, i always forget about that on the sgs though i have done it on an evo the hard way a while back, now we have superoneclick so it's not hard anymore. you can install a market app called sgs kernel flash and experiment with kernels that way. prolly what i'd have told you if i read the whole thread.
OK, so I should have done it before I flashed the wrong firmware.
That's beside the point. After doing some research, I found someone with a similar situation that was able to flash their SGS with Heinz 57 and recover their mess up.
I am currently operational with USCC's 2.2.1 Froyo, but with no internal phone storage available.
I plan to flash with Heinz 57.
I did the CWM already. Will likely do it again for verification when I start this.
I will flash my Kernel with:
Touchwiz Froyo
imnuts
PeanutButta Jelly Time (Release 0531 with voodoo, no undervolt)
I will then flash with:
ROM Heinz 57 v1.2 with PBJT
I will likely flash a custom theme after that.
...but that is later and not as important.
Both the Kernel and Custom ROM are .zip files that Odin3 doesn't see, do I change their file extension to a .tar or extract them and re-compress them as a .tar?
Just extract them and use them that way?
Should the Odin3 re-partition box be checked?
Will I need a .pit file as well?
Where should I place the specific files prior to flashing? PDA/Phone/CSC?
I will likely do the flashing later this week when I have more time. My first attempt, I ran out of time and caused myself extra stress.
Thanks for the verification and info! Appreciate the time everyone puts into helping others!
You flash the rom and kernel in custom recovery or cwm. Odin is really only for going all the way back to stock. I haven't seen to many roms made available to be flashed in odin. As for the repartition. When flashing back to stock.I alwayd use that trick. Now the main thing to remember is to uncheck it when flashing the cwm package. Hope this helps.
Tap-a-Talked from my Mesmerize
Running CM7 @1.2ghz w/ Tk-Glitch ML Kernel.
Much love to all the Dev's working to advance the Mesmerize and Fascinate. You guys Rock!
I would suggest reading the second sticky in this forum (newbies guide...) and really spend some time with it before you do anything more. Flashing roms and kernels is not same as recovery.
Sent from my SCH-I500 using XDA Premium App
never, never, never ever use anything in odin besides pit and pda section! I would suggest you read the stickies as started above, it will help you. then read them again, then read a few more threads in the fascinate section and their stickies, then you'll
have misty oh the answers you seek. before flashing you should be sure of what youre doing,.and if you aren't sure, do not do it. you need to read more because if it breaks nobody can fix it BUT YOU.
not trying to sound preachy but I've been in this boat and thank god people told me I needed more information, it saved me cuz I knew how to fix my error.. good luck
Sent from my SCH-I500 using XDA Premium App
First off, Thanks to everyone for the posts and for future patience.
I know there has been a lot of discussion on this subject, but I seem to have elevated it to a new level of loopy. Bear with me, please; I'll make whatever changes needed. I have researched/read a lot tried many of the recommended procedures and frankly, I think it has all become mud stew in my head. My wife is none too happy, and if you guys could help me save my genitals/marriage, I'd be much appreciative.
The facts: 1 T-Mobile SGS4G t959v, 1 Mac os X 10.6.8, 1 Heimdall 1.3.1 and 1 ticked-off wife.
So, following the xda forum, I successfully rooted the device. Then I downloaded ROM manager and installed CwM (now I realize the error of my ways), downloaded and flashed Bionix. Phone looped "3e" recovery.
After much research, found heimdall on XDA, and was able to get the recovery image changed to CwM Voodoo Lagfix Recovery v3.0.2.8x. Now, I'm looping that recovery. Tried the bali 3.3 kernel, flashed just fine. found sgs4g official gb2.3.6....Rom, flashed just fine. Still, I remain at the red voodoo screen.
Obviously, I can access the sd card through my mac, and have tried various update.zip procedures, and various ROMs.
So, I've been reading for several days now, poring over these and other forums, and if I understand it correctly, bali3.3_heimdall.tar.gz (thank you very much!) is supposed to undo the ROM manager screw up from earlier (and I can only think that I am missing some critical info here), but no, still looking at the voodoo recovery.
I AM kind of new to this, however I have rooted and modded 4- MyTough 3g's and a defy, All running CMx.
Thanks again,
SN
Try disabling voodoo lag fix and see if that helps
Sent from my HTC_Amaze_4G using xda premium
Thanks again,
it's done, with no change.
You are aware that Bali3.3 is a Froyo kernel? If the last rom you flashed was GB 2.3.6 then try flashing a GB kernel and make sure your mounts are correct.
missed the bali/froyo. does this imply that I might flash a froyo rom over bali? or do I need to flash a gb kernel for the 2.3.6 rom? Also, I'm using heimdall and I don't know how to use non-.tar files with it; or if you can.
supernugget said:
missed the bali/froyo. does this imply that I might flash a froyo rom over bali? or do I need to flash a gb kernel for the 2.3.6 rom? Also, I'm using heimdall and I don't know how to use non-.tar files with it; or if you can.
Click to expand...
Click to collapse
:facepalm:
There are line-by-line instructions all over this forum to install kernels and custom roms.
The search button is your best friend here. Use it! Google can also search the xda forum... try starting your search with: site:forum.xda-developers.com
For example:
Code:
site:forum.xda-developers.com Galaxy S 4G Heimdall
or
Code:
site:forum.xda-developers.com galaxy s 4g download mode
Learning to use XDA will help you find what you need. Following the rules will help you get answers.
I say all this, because every problem you are having is already answered in this forum!
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hi. I am having trouble finding the clockwork mod for this device on this forum. I found some instrucions on the cyanogen mod forum with an oficial rom from them. Which one anyone suggest me? roms from the forum or cyanogens 7. im searching for an ics rom..
Sent from my SAMSUNG-SGH-I897 using Tapatalk 2 Beta-5
The hard way is usually what new owners of the Captivate learn, and fast, like I did over the past week or so. I ended up:
- getting the i897uckk4 Odin One Click - Stock ROM and flashing that so it was fully updated (at least as far as the AT&T stock stuff is concerned)
- located the Odin3 v1.85 flasher
- flashed the captivate-recovery-cwm5-kernel.tar onto the Captivate (it's the stock KK4 kernel with CWM 5 ready to go)
- then used CWM to update/upgrade from a bunch of ROMs, currently using Doc's Master beta v9, but I've tried about 10 ROMs in the past few days, this one is working fine at the moment aside from some ROM Control FC issues, but it's beta obviously
That should get you going. Found all the files here by searching, use the names I just mentioned above to locate them as I didn't save individual links, sorry.
Hope this helps...
Thank U Very Much
br0adband said:
The hard way is usually what new owners of the Captivate learn, and fast, like I did over the past week or so. I ended up:
- getting the i897uckk4 Odin One Click - Stock ROM and flashing that so it was fully updated (at least as far as the AT&T stock stuff is concerned)
- located the Odin3 v1.85 flasher
- flashed the captivate-recovery-cwm5-kernel.tar onto the Captivate (it's the stock KK4 kernel with CWM 5 ready to go)
- then used CWM to update/upgrade from a bunch of ROMs, currently using Doc's Master beta v9, but I've tried about 10 ROMs in the past few days, this one is working fine at the moment aside from some ROM Control FC issues, but it's beta obviously
That should get you going. Found all the files here by searching, use the names I just mentioned above to locate them as I didn't save individual links, sorry.
Hope this helps...
Click to expand...
Click to collapse
Thank U Very Much, Your guild is awesome worked the 1st time, I been trying for 3 days NOW, THANK U SO Much.
Clockwork mod is a recovery kernel replacement which allows flashing of unsigned zip files. You flash or "reinstall packages" as an update.zip from the original recovery. This roots the phone and installs Clockwork recovery.
Flashing roms without knowing the three button method to get into recovery or the button combo to get into download mode could spell trouble for people who are just learning about rom flashing.
It takes a few months of reading threads until a level of understanding is reached where you can flash roms and get out of trouble on your own.
br0adband said:
The hard way is usually what new owners of the Captivate learn, and fast, like I did over the past week or so. I ended up:
- getting the i897uckk4 Odin One Click - Stock ROM and flashing that so it was fully updated (at least as far as the AT&T stock stuff is concerned)
- located the Odin3 v1.85 flasher
- flashed the captivate-recovery-cwm5-kernel.tar onto the Captivate (it's the stock KK4 kernel with CWM 5 ready to go)
- then used CWM to update/upgrade from a bunch of ROMs, currently using Doc's Master beta v9, but I've tried about 10 ROMs in the past few days, this one is working fine at the moment aside from some ROM Control FC issues, but it's beta obviously
That should get you going. Found all the files here by searching, use the names I just mentioned above to locate them as I didn't save individual links, sorry.
Hope this helps...
Click to expand...
Click to collapse
Thanks alot..im going to try that now and se how it goes
Sent from my SAMSUNG-SGH-I897 using Tapatalk 2 Beta-5
askpcguy said:
Clockwork mod is a recovery kernel replacement which allows flashing of unsigned zip files. You flash or "reinstall packages" as an update.zip from the original recovery. This roots the phone and installs Clockwork recovery.
Flashing roms without knowing the three button method to get into recovery or the button combo to get into download mode could spell trouble for people who are just learning about rom flashing.
It takes a few months of reading threads until a level of understanding is reached where you can flash roms and get out of trouble on your own.
Click to expand...
Click to collapse
Ive been flashing for a while now. I have a galaxy fit rooted and with clockwork..i was just asking because i want to now if i do this will it take away my currently settings..since i network unlocked it and am currently using it with claro.. Im on stock rooted 2.3.5 uckk4 unlocked network
Sent from my SAMSUNG-SGH-I897 using Tapatalk 2 Beta-5
br0adband said:
The hard way is usually what new owners of the Captivate learn, and fast, like I did over the past week or so. I ended up:
- getting the i897uckk4 Odin One Click - Stock ROM and flashing that so it was fully updated (at least as far as the AT&T stock stuff is concerned)
- located the Odin3 v1.85 flasher
- flashed the captivate-recovery-cwm5-kernel.tar onto the Captivate (it's the stock KK4 kernel with CWM 5 ready to go)
- then used CWM to update/upgrade from a bunch of ROMs, currently using Doc's Master beta v9, but I've tried about 10 ROMs in the past few days, this one is working fine at the moment aside from some ROM Control FC issues, but it's beta obviously
That should get you going. Found all the files here by searching, use the names I just mentioned above to locate them as I didn't save individual links, sorry.
Hope this helps...
Click to expand...
Click to collapse
Soooo sorry to bother, but I'm at my wits end trying to root and remod my new captivate. The last one crapped out on me, so I was able to get a replacement, but I don't remember flashing it being this hard 6 months ago...lol! Anyway, here's my current stats and what I'm looking for:
Firmware: 2.3.5
Baseband: I897UCKK4
Kernel: 2.6.35.7-I897UCKK4-CL614489
Build: Gingerbread.UCKK4
I can if need be flash it back to 2.1 with Odin, but I followed your instructions, and now I'm stuck. I can't for the life of me find the captivate-recovery-cwm5-kernel file anywhere, on here or elsewhere. I don't even think the phone is rooted now, which is very strange because I was able to flash it, but anyway...any help would be greatly appreciated! Thanks in advance!!
I can't upload the Odin One Click ROM, it's too much for my current situation, but here's the captivate-recovery-cwm5-kernel.tar file:
http://dl.dropbox.com/u/19019338/captivate-recovery-cwm5-kernel.tar
MD5: 8464e7cee89c7364d62b760c28a4ca73
File size: 6,359,040 bytes
and here's Odin v1.85 if you don't have it:
http://dl.dropbox.com/u/19019338/Odin3_v1.85.zip
MD5: 9a81990a61454402e8714f494bb4eb68
File size: 204,173 bytes
Now, the basics are thus so pay attention:
Since Samsung is never going to release a proper ICS build for us, from what I understand - let me repeat that: from what I understand everything is working with Gingerbread bootloaders, so that's the important aspect. Before you go flashing anything, you'll need to get the Captivate OFF Froyo of any version if you're still using it. So, update that thing using Samsung Kies to the latest version which is that KK4 ROM - that's all that's required.
Once you're done that, and you're "stock" then you would flash the captivate-recovery-cwm5-kernel.tar kernel using Odin (run Odin with Admin privilege, put the Captivate in download mode, connect it, when detected, click the PDA button in Odin to load that captivate-recovery-cwm5-kernel.tar file, then Start to flash it). Once that's done you have the same kernel for KK4 but with CWM ready to go when you are with a proper GB bootloader and you're set.
The only reason I mentioned the Odin One Click above was because I did a few things that "pooched" my Captivate and soft-bricked it at one point but recovered it with Odin and the One Click when Kies couldn't do anything at all. There's a thread around here with all the Odin One Click ROMs, that's where I got mine from.
tl;dr version:
- if you're running any Froyo anything, use Kies to do the upgrade to Gingerbread, NOT the Odin One Click. Kies will update the bootloader from Froyo to GB as required (the Odin One Click was part of what caused my soft-brick, so I learned from the experience)
- if you're already running any Gingerbread ROM, you already have the GB bootloader, so you can use the Odin One Click to go to a pure stock AT&T basic clean ROM as mentioned above
- once you're "stock" use Odin v1.85 to flash the captivate-recovery-cwm5-kernel.tar so you get the same stock kernel but CWM as well
- use CWM to install whatever ROM you want from that point on making sure the ROM archive(s) and any updates or whatever are copied to the internal storage
Personal suggestion: remove the microSD card from the Captivate before doing any flashing at all. Yes it's possible to read from that device (called the external SD in CWM), I simply don't recommend it, ever.
That's about it. The Odin One Click KK4 is not rooted, iirc, I can't say for certain at this moment either way. I only used it a few times to "save" me from the soft-brick. Now that CWM is in there, I've jumped from ROM to ROM over the past week or so but Doc's Master v8 is my fall back stable one so far. Obviously when you load a ROM, look at the Apps and if you don't see SU or SuperUser, it's not rooted.
br0adband said:
I can't upload the Odin One Click ROM, it's too much for my current situation, but here's the captivate-recovery-cwm5-kernel.tar file:
http://dl.dropbox.com/u/19019338/captivate-recovery-cwm5-kernel.tar
MD5: 8464e7cee89c7364d62b760c28a4ca73
File size: 6,359,040 bytes
and here's Odin v1.85 if you don't have it:
http://dl.dropbox.com/u/19019338/Odin3_v1.85.zip
MD5: 9a81990a61454402e8714f494bb4eb68
File size: 204,173 bytes
Now, the basics are thus so pay attention:
Since Samsung is never going to release a proper ICS build for us, from what I understand - let me repeat that: from what I understand everything is working with Gingerbread bootloaders, so that's the important aspect. Before you go flashing anything, you'll need to get the Captivate OFF Froyo of any version if you're still using it. So, update that thing using Samsung Kies to the latest version which is that KK4 ROM - that's all that's required.
Once you're done that, and you're "stock" then you would flash the captivate-recovery-cwm5-kernel.tar kernel using Odin (run Odin with Admin privilege, put the Captivate in download mode, connect it, when detected, click the PDA button in Odin to load that captivate-recovery-cwm5-kernel.tar file, then Start to flash it). Once that's done you have the same kernel for KK4 but with CWM ready to go when you are with a proper GB bootloader and you're set.
The only reason I mentioned the Odin One Click above was because I did a few things that "pooched" my Captivate and soft-bricked it at one point but recovered it with Odin and the One Click when Kies couldn't do anything at all. There's a thread around here with all the Odin One Click ROMs, that's where I got mine from.
tl;dr version:
- if you're running any Froyo anything, use Kies to do the upgrade to Gingerbread, NOT the Odin One Click. Kies will update the bootloader from Froyo to GB as required (the Odin One Click was part of what caused my soft-brick, so I learned from the experience)
- if you're already running any Gingerbread ROM, you already have the GB bootloader, so you can use the Odin One Click to go to a pure stock AT&T basic clean ROM as mentioned above
- once you're "stock" use Odin v1.85 to flash the captivate-recovery-cwm5-kernel.tar so you get the same stock kernel but CWM as well
- use CWM to install whatever ROM you want from that point on making sure the ROM archive(s) and any updates or whatever are copied to the internal storage
Personal suggestion: remove the microSD card from the Captivate before doing any flashing at all. Yes it's possible to read from that device (called the external SD in CWM), I simply don't recommend it, ever.
That's about it. The Odin One Click KK4 is not rooted, iirc, I can't say for certain at this moment either way. I only used it a few times to "save" me from the soft-brick. Now that CWM is in there, I've jumped from ROM to ROM over the past week or so but Doc's Master v8 is my fall back stable one so far. Obviously when you load a ROM, look at the Apps and if you don't see SU or SuperUser, it's not rooted.
Click to expand...
Click to collapse
Thanks dude... I only have one question in all this. I network unlock my phone when it was on eclair, i updated to ginger via kies and it stayed unlock will i loose the unlock if i installed cmw and any rom?
Sent from my SAMSUNG-SGH-I897 using Tapatalk 2 Beta-5
Jose0726 said:
Thanks dude... I only have one question in all this. I network unlock my phone when it was on eclair, i updated to ginger via kies and it stayed unlock will i loose the unlock if i installed cmw and any rom?
Sent from my SAMSUNG-SGH-I897 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Can't say on that respect, mine is not even being used as a phone, actually - it's basically a DAP/PMP/PocketPC for me.
Still can't find a service provider with a decent plan that I'd be willing to fork over some money for so, until I find one (if I ever do), this Captivate of mine won't even have a SIM in it.
You won't loose network unlock ever unless your EFS gets modified in anyway...
Sent from my SGH-I897 using xda premium
br0adband said:
I can't upload the Odin One Click ROM, it's too much for my current situation, but here's the captivate-recovery-cwm5-kernel.tar file:
http://dl.dropbox.com/u/19019338/captivate-recovery-cwm5-kernel.tar
MD5: 8464e7cee89c7364d62b760c28a4ca73
File size: 6,359,040 bytes
and here's Odin v1.85 if you don't have it:
http://dl.dropbox.com/u/19019338/Odin3_v1.85.zip
MD5: 9a81990a61454402e8714f494bb4eb68
File size: 204,173 bytes
Now, the basics are thus so pay attention:
Since Samsung is never going to release a proper ICS build for us, from what I understand - let me repeat that: from what I understand everything is working with Gingerbread bootloaders, so that's the important aspect. Before you go flashing anything, you'll need to get the Captivate OFF Froyo of any version if you're still using it. So, update that thing using Samsung Kies to the latest version which is that KK4 ROM - that's all that's required.
Once you're done that, and you're "stock" then you would flash the captivate-recovery-cwm5-kernel.tar kernel using Odin (run Odin with Admin privilege, put the Captivate in download mode, connect it, when detected, click the PDA button in Odin to load that captivate-recovery-cwm5-kernel.tar file, then Start to flash it). Once that's done you have the same kernel for KK4 but with CWM ready to go when you are with a proper GB bootloader and you're set.
The only reason I mentioned the Odin One Click above was because I did a few things that "pooched" my Captivate and soft-bricked it at one point but recovered it with Odin and the One Click when Kies couldn't do anything at all. There's a thread around here with all the Odin One Click ROMs, that's where I got mine from.
tl;dr version:
- if you're running any Froyo anything, use Kies to do the upgrade to Gingerbread, NOT the Odin One Click. Kies will update the bootloader from Froyo to GB as required (the Odin One Click was part of what caused my soft-brick, so I learned from the experience)
- if you're already running any Gingerbread ROM, you already have the GB bootloader, so you can use the Odin One Click to go to a pure stock AT&T basic clean ROM as mentioned above
- once you're "stock" use Odin v1.85 to flash the captivate-recovery-cwm5-kernel.tar so you get the same stock kernel but CWM as well
- use CWM to install whatever ROM you want from that point on making sure the ROM archive(s) and any updates or whatever are copied to the internal storage
Personal suggestion: remove the microSD card from the Captivate before doing any flashing at all. Yes it's possible to read from that device (called the external SD in CWM), I simply don't recommend it, ever.
That's about it. The Odin One Click KK4 is not rooted, iirc, I can't say for certain at this moment either way. I only used it a few times to "save" me from the soft-brick. Now that CWM is in there, I've jumped from ROM to ROM over the past week or so but Doc's Master v8 is my fall back stable one so far. Obviously when you load a ROM, look at the Apps and if you don't see SU or SuperUser, it's not rooted.
Click to expand...
Click to collapse
Thank you SO much for the links and all the time you put in to the explanation. I followed your suggestions, and now I'm running ICS Cyanogenmod 9 in dazzling full color!! You've made what could potentially be a very complicated process extremely easy...I wish I could thank your post 10-fold!! How is your ROM on battery life, btw? I was running CM 7 on my other Captivate, and it wasn't all that great on the battery...waiting to see how 9 works, but my girlfriend still insists it was because I had "too much junk" on the phone...lol! Thanks again!!
Battery life using Doc's Master v8 is as expected, didn't do any extended testing with the CM9 nightly, but then again I'm on the original Samsung stock battery too so, it doesn't hold a full charge anymore like a brand new one would.
I'm hoping to get some cash together soon to get that Anker 2-pack w/charger on Amazon (the 1800 mAh batteries that everyone raves about). I thought about getting the 3500 mAh monster extended on off eBay but, as I'm still trying to locate that Trident Cyclops case (which you just sent me 2 PMs about, thanks), I figure having 2 batteries instead of one would still be a more efficient solution while still being able to keep the Captivate in a nice protective case.
Maybe I need to do some guides for people and put up a donate button to get me some batteries and that case, who knows.
Glad the instructions proved useful.
br0adband said:
Battery life using Doc's Master v8 is as expected, didn't do any extended testing with the CM9 nightly, but then again I'm on the original Samsung stock battery too so, it doesn't hold a full charge anymore like a brand new one would.
I'm hoping to get some cash together soon to get that Anker 2-pack w/charger on Amazon (the 1800 mAh batteries that everyone raves about). I thought about getting the 3500 mAh monster extended on off eBay but, as I'm still trying to locate that Trident Cyclops case (which you just sent me 2 PMs about, thanks), I figure having 2 batteries instead of one would still be a more efficient solution while still being able to keep the Captivate in a nice protective case.
Maybe I need to do some guides for people and put up a donate button to get me some batteries and that case, who knows.
Glad the instructions proved useful.
Click to expand...
Click to collapse
Could any one give me a link to the cm9 ics. I recently flashed aokp and dark night but couldnt use my phone as i got a no network message and when try to ad apns settings were not saving :/
Sent from my SAMSUNG-SGH-I897 using Tapatalk 2 Beta-5
http://goo.im/cm/captivatemtd/nightly
Bottom of the list, and apparently a new nightly was just posted a short time ago (20120412) so... time for a backup and a flash to see what's changed.
And also remember to get the latest Gapps from that site as well when flashing CM (which is 20120317)
http://goo.im/gapps
Hello Canadian users with SGH-T959W!
I spent some time the last few days comparing the kernel source for SGH-T959W and SGH-T959V, and found they are exactly the same (plus a few fixes for us on SGH-T959V from the SGH-T959W source!)!
This is good for you, because we have unofficial cm7, cm9, aokp, et alii... ports for the SGH-T959V.
Maybe a forum admin could update the Samsung Galaxy S 4G forum to also say: SGH-T959V & SGH-T959W
Technically, the only real difference is that the stock roms for the SGH-T959W will have different pre-installed software. The hardware of the SGH-T959W is the same as the SGH-T959V.
Enjoy!
Read this stuff to continue:
http://forum.xda-developers.com/showthread.php?p=28566711#post28566711
BTW, if anyone has an odin or kies tarball, please PM me!
This way I can verify if the bootloaders are different or not, and if they are different, I can make you guys custom Heimdall OneClick and Odin packages.
bhundven said:
I spent some time the last few days comparing the kernel source for SGH-T959W and SGH-T959V, and found they are exactly the same (plus a few fixes for us on SGH-T959V from the SGH-T959W source!)!
Click to expand...
Click to collapse
Sorry to bump this thread, but out of curiosity, what were the fixes you were able to implement after seeing the kernel source for the 959W?
If it's something you'd rather not explain and will just be rolling out in future kernels, no big deal; just curious.
Thanks.
fingolfin14 said:
Sorry to bump this thread, but out of curiosity, what were the fixes you were able to implement after seeing the kernel source for the 959W?
If it's something you'd rather not explain and will just be rolling out in future kernels, no big deal; just curious.
Thanks.
Click to expand...
Click to collapse
The hardware is exactly the same. There is still a problem with the OTA Assert, meaning, how the rom knows if it is able to install on the phone or not during install from cwm. Also how it identifies itself to the play store.
I'm fixing this in the next cm9 unofficial release (coming soon, eta... a few hours, maybe).
The only real difference between SGH-T959V and SGH-T959W is the pre-installed/bundled software on the phone.
Everything else is one-to-one.
I'm still paranoid about bootloaders. So I'm still waiting for someone to post Kies or leaked tar.md5 for the SGH-T959W so that I can diff the bootloaders. If they are different, I will create new Heimdall OneClicks for SGH-T959W so that it is simple for you to go back to stock. See my current Heimdall OneClick thread to get an idea of what I mean.
On the other hand, we have some issues with our SGH-T959V bootloaders, and I have Unbrickable Mod on my phone. So, if the bootloaders are different, I would like to try flashing the SGH-T959W bootloaders to see if they work any better.
Also, there are a few fixes in the SGH-T959W kernel source that I will be incorporating into the current unofficial CM7 and CM9 ports I work on. Not having these fixes shouldn't have any negative impact on SGH-T959W.
I hope this info is informative. If not, ask more!
I have a SGH-T959W which seemed to have a bad flash already (from before.. and I am trying to revive it) on it (seems stuck on the cwm screen, and the system partition doesn't seem to have all the data that it needs to). Is there any way of getting the original ROM for this phone? Even if I install a cm build for the T959V, I don't get errors but its stuck in a cwm loop (keeps coming back to cwm).
When I try any of the one-clicks for the T959V, it succeeds on the kernel upload but always fails on the modem upload.
Where would you look for the Kies tar for this phone? Any possible way of getting the original ROM from a brand new phone? (any instructions for these would be great)
bhundven said:
The hardware is exactly the same. There is still a problem with the OTA Assert, meaning, how the rom knows if it is able to install on the phone or not during install from cwm. Also how it identifies itself to the play store.
I'm fixing this in the next cm9 unofficial release (coming soon, eta... a few hours, maybe).
The only real difference between SGH-T959V and SGH-T959W is the pre-installed/bundled software on the phone.
Everything else is one-to-one.
I'm still paranoid about bootloaders. So I'm still waiting for someone to post Kies or leaked tar.md5 for the SGH-T959W so that I can diff the bootloaders. If they are different, I will create new Heimdall OneClicks for SGH-T959W so that it is simple for you to go back to stock. See my current Heimdall OneClick thread to get an idea of what I mean.
On the other hand, we have some issues with our SGH-T959V bootloaders, and I have Unbrickable Mod on my phone. So, if the bootloaders are different, I would like to try flashing the SGH-T959W bootloaders to see if they work any better.
Also, there are a few fixes in the SGH-T959W kernel source that I will be incorporating into the current unofficial CM7 and CM9 ports I work on. Not having these fixes shouldn't have any negative impact on SGH-T959W.
I hope this info is informative. If not, ask more!
Click to expand...
Click to collapse
phaedrus81 said:
I have a SGH-T959W which seemed to have a bad flash already (from before.. and I am trying to revive it) on it (seems stuck on the cwm screen, and the system partition doesn't seem to have all the data that it needs to). Is there any way of getting the original ROM for this phone? Even if I install a cm build for the T959V, I don't get errors but its stuck in a cwm loop (keeps coming back to cwm).
When I try any of the one-clicks for the T959V, it succeeds on the kernel upload but always fails on the modem upload.
Click to expand...
Click to collapse
This is annoying, sorry you are going through this. It sounds like something dorked your param.lfs.
I've had this happen to me, and it always appends 'bootmode=2' to the kernel command line. Only way to fix it is to flash a new param.lfs from the stock image...
phaedrus81 said:
Where would you look for the Kies tar for this phone? Any possible way of getting the original ROM from a brand new phone? (any instructions for these would be great)
Click to expand...
Click to collapse
...which brings me to this part. Someone told me that they have this image, but when I asked them to post it somewhere, I got no response.
Bug Wind and Samsung for a kies mini or a stock image that you can flash to the phone. Samsung is probably not going to be as helpful as Wind, so I'd try bugging the crap out of Wind.
Hopefully someone will get me the tar.md5 soon, and we can get you guys a one-click with bootloaders (which includes the param.lfs).
If you feel bold/brave, you can try flashing the bootloaders from my Stock oneclick in my signature.
Since it should be the same hardware it should work the same. Granted after flashing your phone will now be a SGH-T959V and not an SGH-T959W.
I hold no guarantee that it will work, and/or that it won't try to shoot you at your favorite new 3d film. <.< ... >.>
Thanks for the info about what might be causing the cwm loop issue
I think I will the one-click with bootloaders a try (will update this thread with the results). At this point I think I have exhausted all other options to revive the device.
bhundven said:
This is annoying, sorry you are going through this. It sounds like something dorked your param.lfs.
I've had this happen to me, and it always appends 'bootmode=2' to the kernel command line. Only way to fix it is to flash a new param.lfs from the stock image...
...which brings me to this part. Someone told me that they have this image, but when I asked them to post it somewhere, I got no response.
Bug Wind and Samsung for a kies mini or a stock image that you can flash to the phone. Samsung is probably not going to be as helpful as Wind, so I'd try bugging the crap out of Wind.
Hopefully someone will get me the tar.md5 soon, and we can get you guys a one-click with bootloaders (which includes the param.lfs).
If you feel bold/brave, you can try flashing the bootloaders from my Stock oneclick in my signature.
Since it should be the same hardware it should work the same. Granted after flashing your phone will now be a SGH-T959V and not an SGH-T959W.
I hold no guarantee that it will work, and/or that it won't try to shoot you at your favorite new 3d film. <.< ... >.>
Click to expand...
Click to collapse
phaedrus81 said:
Thanks for the info about what might be causing the cwm loop issue
I think I will the one-click with bootloaders a try (will update this thread with the results). At this point I think I have exhausted all other options to revive the device.
Click to expand...
Click to collapse
Also, just to make sure you have tried different cables and computers.
Not being able to flash the modem sounds like a cable/computer issue.
If you have that issue while flashing bootloaders, you could hard-brick your phone.
The first time you flash with the oneclick, it will not flash bootloaders. The second time, the option to flash bootloaders opens up, but you still have to enable it.
Don't forget to read all the documentation in my thread before doing anything.
If you have any questions, ask before you do.
The Root Doesn't work. I follow the step and it damaged my phone! T959W
bhundven said:
Hello Canadian users with SGH-T959W!
I spent some time the last few days comparing the kernel source for SGH-T959W and SGH-T959V, and found they are exactly the same (plus a few fixes for us on SGH-T959V from the SGH-T959W source!)!
This is good for you, because we have unofficial cm7, cm9, aokp, et alii... ports for the SGH-T959V.
Maybe a forum admin could update the Samsung Galaxy S 4G forum to also say: SGH-T959V & SGH-T959W
Technically, the only real difference is that the stock roms for the SGH-T959W will have different pre-installed software. The hardware of the SGH-T959W is the same as the SGH-T959V.
Enjoy!
Read this stuff to continue:
http://forum.xda-developers.com/showthread.php?p=28566711#post28566711
Click to expand...
Click to collapse
I try your root process for my T959W now My phone Can't turn on . It turn on and off with the glaxy S 4G logo and T-Mobile . HELP PLS i tried to unroot It does work and It . PLS HELPPPP!!!!!
GMK63 said:
I try your root process for my T959W now My phone Can't turn on . It turn on and off with the glaxy S 4G logo and T-Mobile . HELP PLS i tried to unroot It does work and It . PLS HELPPPP!!!!!
Click to expand...
Click to collapse
Please be more specific as to which 'process' you followed and what you did.
Sorry I've been delayed in responding!
Again, if you can be more specific as to exactly what you did, I will be better prepared to help you.
It does look like it could be a cable/computer issue. I tried different cables and some of them didn't get as far as the modem (failed the kernel upload as well). Haven't got a cable which succeeds in the modem flash yet.
All of the driver stuff on windows makes me nervous though. Is there any way to flash this on linux. Does the one-click package work with fastboot or can fastboot be used to flash the individual pieces?
bhundven said:
Also, just to make sure you have tried different cables and computers.
Not being able to flash the modem sounds like a cable/computer issue.
If you have that issue while flashing bootloaders, you could hard-brick your phone.
The first time you flash with the oneclick, it will not flash bootloaders. The second time, the option to flash bootloaders opens up, but you still have to enable it.
Don't forget to read all the documentation in my thread before doing anything.
If you have any questions, ask before you do.
Click to expand...
Click to collapse
phaedrus81 said:
It does look like it could be a cable/computer issue. I tried different cables and some of them didn't get as far as the modem (failed the kernel upload as well). Haven't got a cable which succeeds in the modem flash yet.
All of the driver stuff on windows makes me nervous though. Is there any way to flash this on linux. Does the one-click package work with fastboot or can fastboot be used to flash the individual pieces?
Click to expand...
Click to collapse
These phones do not have fastboot, but they have download mode.
Yes, you can do this from: Windows, Linux, or Mac OS X
If you still have problems with multiple cables, I highly recommend trying a different computer. I've had this problem myself before. It drove me nuts until I got a friends laptop and everything worked perfectly. My laptop's usb ports had gone bad for some unexplainable reason.
Check out the wiki pages we have written:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
Steps I followed
managed to get my Wind SGH-T959W rooted and up and running with a unofficial CM9 build, but it took a bit of work.
Firstly, I tried just about every one-click solution out there, to no avail. It's possible SOC 1.7 with rattlethecage works, but I didn't have the patience to find out whether I simply had to wait a bit longer.
I followed this guide(whilst clenching every clenchable muscle I could consciously control):
http://www.galaxyforums.net/forum/of...ngerbread.html
The gist is, Odin 1.7, stock+voodoo for T959V, plus some update that I'm not qualified to describe. That should get you rooted and if that's all you're looking for, you'll have to suffer through a little T-Mobile branding on startup.
Once you got it all rooted, you'd think it'd be a good idea to toss sgs-ics on there, right? Well, no. After installing the 4G variant, it promptly set off into a boot loop which I'm again, unqualified to diagnose. The obvious solution was to try another team's version of ICS, which I indeed found here:
http://forum.xda-developers.com/show....php?t=1730954
Barring some missing features, it sounds like a good alternative to sgs-ics. Though I had to go through one additional step, which I really, honestly assure you I was under-qualified to execute. When I tried to load Team Acid's CM9 r3 it gave me an assert on the updater-script, since the hardware didn't match up. Easy. Unzip the package, open up META-INF/com/google/android/updater-script, remove the first check. You know it's the same hardware, you don't need some stinkin' script to tell you it won't work.
So all said and done, I now have a Wind Mobile SGH-T959W running ICS 4.0.4 courtesy of bhundven, the Odin folks, Team Acid, and likely a slew of other contributors.
Thanks folks, and enjoy!
PS, if you want that tarball bhundven, send me a PM with some brief instructions, and hopefully you can help my fellow Winders.
.......(---------THAT WHAT I FOLLOWED .
But I did the first part and They said i should get the stuff I store on my SD Card to pull out a file (``12) In CWM, use your volume up/down positions to navigate, scroll down to "Install Zip From SDcard". Select with a click of the power button. Navigate to where you put sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip (in the root of your SDcard) and select with the power button. Confirm you want to install.
``)
but it doesn't give me the option to go get it on my SDcard and Now my Phone just turns on and off with the samsung galaxy S logo plus T-mobile exclusive logo . The only possitive thing about all the damage is that I can still put my phone on dowload mode and I just think if someone knows how to get my phone back to it state they will need me to put it on download mode. :crying:
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you in advance for your Help, for replying and offering to help.:highfive:
I appriciate it. My phone is Mobillicity carrier just like wind .
GMK63 said:
.......(---------THAT WHAT I FOLLOWED .
But I did the first part and They said i should get the stuff I store on my SD Card to pull out a file (``12) In CWM, use your volume up/down positions to navigate, scroll down to "Install Zip From SDcard". Select with a click of the power button. Navigate to where you put sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip (in the root of your SDcard) and select with the power button. Confirm you want to install.
``)
but it doesn't give me the option to go get it on my SDcard and Now my Phone just turns on and off with the samsung galaxy S logo plus T-mobile exclusive logo . The only possitive thing about all the damage is that I can still put my phone on dowload mode and I just think if someone knows how to get my phone back to it state they will need me to put it on download mode. :crying:
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you in advance for your Help, for replying and offering to help.:highfive:
I appriciate it. My phone is Mobillicity carrier just like wind .
Click to expand...
Click to collapse
Ok, this is really simple. I've explained it in quite a few threads in the Galaxy S 4G forums in General, Q&A, and the Dev forum. I'm going to explain this, but in a way to be more general. So I'm being verbose in case anyone else with a T959W happens to run across this and has not tried anything yet.
Again, I'm not good with windows at all, and I prefer it that way.
If you're on windows, check out our wiki:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
There is tons of help there for setting up heimdall on windows with all the right drivers and such.
Once you have heimdall setup get AntonX's latest cwm zip for his kernel.
This kernel is a BML kernel, and this guide I am giving you right now will help you get cm9 installed which is an MTD kernel. You can find out more about BML vs. MTD here.
Once you have downloaded AntonX's kernel, extract the zImage from it and open up the terminal/cmd prompt and navigate to the directory you extracted the zImage to.
Put your phone into Download Mode and type the following in the command prompt:
Code:
heimdall flash --kernel zImage
The heimdall program will flash this kernel+initramfs to the kernel partition and reboot the phone. Do not unplug the usb cable until you see the "Galaxy S" screen. When you see that screen, unplug the usb cable and remove the battery from the back.
Assuming you downloaded CM9 and put it on your sdcard already, you can get into recovery by holding the vol+ and vol-, then pressing the power button to turn the phone on. When you see the "Galaxy S" screen, let go of the buttons, and you should be in the recovery now.
This is where things get a little tricky. If you have not tried to do anything to your phone yet. This would be a great time to use the "Backup and Recovery" menu on CWM. Do a full backup.
The "assert 7" error that the previous person got was because the cwm install script (the updater-script) checks the already installed /system/build.prop's data against the "to be installed" build.prop to verify this rom can be installed. If it doesn't exist, then it moves forward.
So the first order of business is to wipe the /system partition. Go to "Mounts and Storage" and format the system partition.
Now go back to the main screen and do "Factory Reset/Wipe Data".
Now go "Install zip from sdcard" -> "choose zip from sdcard" -> and use the volume keys to select the zip file.
After the rom is installed, navigate back to the main screen and "Reboot the system now" if it doesn't reboot by itself.
When the phone reboots, because it is going from BML to MTD, it obviously can't just install the files to what would be an MTD partition if the kernel knows nothing about MTD. So it boots into the newly installed MTD kernel and continues the installation, which in the end will also reboot again.
The first boot is very slow. It is building a cache of all the pre-installed system applications. Let it sit for a while. I know it's tempting to go play with your phone right away, but resist if you can.
The next CM9 release will be on a different kernel, and albeit a much better rom.
I will also be adding OTA Asserts for SGH-T959W so that you will not have to wipe /system before installing the rom, but I do that still just for good measure. But this also means that your phone will work properly with the google play store.
If this still does not work, please let me know what went wrong and I will be happy to assist!
-Bryan
Confused
bhundven said:
Ok, this is really simple. I've explained it in quite a few threads in the Galaxy S 4G forums in General, Q&A, and the Dev forum. I'm going to explain this, but in a way to be more general. So I'm being verbose in case anyone else with a T959W happens to run across this and has not tried anything yet.
Again, I'm not good with windows at all, and I prefer it that way.
If you're on windows, check out our wiki:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
There is tons of help there for setting up heimdall on windows with all the right drivers and such.
Once you have heimdall setup get AntonX's latest cwm zip for his kernel.
This kernel is a BML kernel, and this guide I am giving you right now will help you get cm9 installed which is an MTD kernel. You can find out more about BML vs. MTD here.
Once you have downloaded AntonX's kernel, extract the zImage from it and open up the terminal/cmd prompt and navigate to the directory you extracted the zImage to.
Put your phone into Download Mode and type the following in the command prompt:
Code:
heimdall flash --kernel zImage
The heimdall program will flash this kernel+initramfs to the kernel partition and reboot the phone. Do not unplug the usb cable until you see the "Galaxy S" screen. When you see that screen, unplug the usb cable and remove the battery from the back.
Assuming you downloaded CM9 and put it on your sdcard already, you can get into recovery by holding the vol+ and vol-, then pressing the power button to turn the phone on. When you see the "Galaxy S" screen, let go of the buttons, and you should be in the recovery now.
This is where things get a little tricky. If you have not tried to do anything to your phone yet. This would be a great time to use the "Backup and Recovery" menu on CWM. Do a full backup.
The "assert 7" error that the previous person got was because the cwm install script (the updater-script) checks the already installed /system/build.prop's data against the "to be installed" build.prop to verify this rom can be installed. If it doesn't exist, then it moves forward.
So the first order of business is to wipe the /system partition. Go to "Mounts and Storage" and format the system partition.
Now go back to the main screen and do "Factory Reset/Wipe Data".
Now go "Install zip from sdcard" -> "choose zip from sdcard" -> and use the volume keys to select the zip file.
After the rom is installed, navigate back to the main screen and "Reboot the system now" if it doesn't reboot by itself.
When the phone reboots, because it is going from BML to MTD, it obviously can't just install the files to what would be an MTD partition if the kernel knows nothing about MTD. So it boots into the newly installed MTD kernel and continues the installation, which in the end will also reboot again.
The first boot is very slow. It is building a cache of all the pre-installed system applications. Let it sit for a while. I know it's tempting to go play with your phone right away, but resist if you can.
The next CM9 release will be on a different kernel, and albeit a much better rom.
I will also be adding OTA Asserts for SGH-T959W so that you will not have to wipe /system before installing the rom, but I do that still just for good measure. But this also means that your phone will work properly with the google play store.
If this still does not work, please let me know what went wrong and I will be happy to assist!
-Bryan
Click to expand...
Click to collapse
I have Window 7 and I went on wiki. I don't know what rom or what I am suppose to download to get heimdall . Plus the steps is not for T959W.
GMK63 said:
I have Window 7 and I went on wiki. I don't know what rom or what I am suppose to download to get heimdall . Plus the steps is not for T959W.
Click to expand...
Click to collapse
:facepalm:
Then send your phone back to Mobillicity. Tell them that you don't know what a smart phone is and did something stupid to it. Go get yourself a nice clamshell phone.
I gave you explicit instructions that work for SGH-T959V and SGH-T959W. As a matter of fact, these instructions work on any "Galaxy S" phone, but you shouldn't flash just any other phone's rom to any other phone.
It just so happens that the SGH-T959V and SGH-T959W are the same exact hardware, just pre-packaged with different software and sold in different regions.
THEY ARE THE SAME PHONE!
With that, I am done with this thread. It was not meant for support! It was merely an announcement.
If you need any more help, please check out the Galaxy S 4G forums.
You can find plenty of directions that will work on either SGH-T959V or SGH-T959W on the wiki.
If you are looking for general information, look at the General forum.
If you need help or are asking a question, look at the Q&A (Questions and Answers) forum.
If you are looking to provide constructive feedback and/or logs to help development of ROMs and Kernels, check out the Developer forum. (Note, do not ask questions in the developer forum).
Don't forget the XDA Forum Rules