[Q] Root after official att froyo upgrade? - Captivate General

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.

Related

Help me install Froyo on AT&T Samsung Captivate

I have just unlocked AT&T Captivate with JH& update. Kindly tell me how to install froyo to it so that it doesn't get unlocked again and at the same time I could get froyo at my phone.
getting froyo
if you flash a rom you will have to re unlock it , BUT if you saved your unlcok code you can re enter it. the best way in my opion is to find a custom froyo or gingerbread rom that you want and root your phone ( if not already done just apply update zip and then turn phone off and hold down up/down buttons and power and when at&t logo comes on let go of power and continue to hold voume buttons then use buttons to go down to "re-install packets" and click power then it will root and reboot) and download cwm (i used rom manger free from market) and then transfer the "zip file" for the custom rom you want ( for froyo i used cognition 2.3b8 but just google cognition xda and is by designgears) then click reboot into recovery and "reinstall packets" and it will boot into cwm recory screen go down to "install ZIP from sd" then click it and find the rom zip you had and click it and will install zip !!!!MAKE SHORE YOU HAVE 3 BUTTON DOWNLOAD COMBINATION BEFORE MESSING WITH PHONE!!! to get to that just take sim card, sdcard, and battery out of phone, open up "odin one click" (to get it for captivate just look for odin one click by designgears) and hold down JUST up and down volume and plug in if you ever want to go back to out of box phone just use the odin and go back and if doesnt work just keep taking battery out and unplugging and re plugging if you have any questions just pm me hope you find this usefull
Look at ponack.net you should be able to find everything you need there. Everything from rooting your phone to flashing back to stock. They walk you thru it pretty well. After you have it rooted and have rom manager and titanium backup (for backing up your apps) then look for a rom here. I'm running phoenix 1.0 it's a great rom that is over clocked. Good luck with it all, after you get started it's addictive. Just a warning. Don't be affraid to ask for help when you need it this is a pretty good community of people here, just make sure you post in the right place. Happy New Year
Sent from my SAMSUNG-SGH-I897 using XDA App

Now my apps are disappearing!

So I figured out how to get my sd card to show up, but now random apps are disappearing, and my market app is totally gone!
So you decide to start a new thread and not explain anything? All without bothering to search...
Sent from my SGH-T959V using XDA Premium App
Yes, sorry. I am obviously lacking in knowledge compared to you. I am not trying to be a pain, I have been up all night trying to figure this out. But everything is so confusing to me, I read about how you feel about "noobs" and I am in no way trying to annoy ANYONE. Once my apps started to disappear, I read somewhere to reboot the phone again and when i did that it was just stuck on the Samsung screen so now I am in the process of going back to Kc1 and then to kg4 and so on. I am very confused about the 3rd step
What do I make sure is disabled?
Also, I am still downloading Kc1 and it has been stuck on DATAFS for almost 20 minutes now, which I am assuming isn't normal...
1. ODIN to KC1
2. ODIN to stock KG4 - http://forum.xda-developers.com/show....php?t=1183413
3. ODIN dr honk's kernel+cwm+root - http://forum.xda-developers.com/show....php?t=1194032
Regarding step 3, just ODIN it, do not follow the steps to get EXT4 on there. Make sure it is disabled when you reboot into recovery. Once done boot into the system. Make sure you then put KG6 on your zip
4. Get the flashable ZIP on your SD card - http://forum.xda-developers.com/show....php?t=1204776
At this point you should have made sure voodoo lagfix was disabled.
5. Reboot into recovery.
6. Flash the KG6 zip
7. Make sure voodoo lagfix is disabled again.
8. clear cache etc. etc.
9. Boot into the system.
10. Install busybox from the market, I used 1.18, 1.17 works too
11. Reboot into recovery
12. Make sure voodoo lagfix is now enabled on the next boot.
13. Now reboot.
Click to expand...
Click to collapse
So now it won't even come on just a black screen with colored specs on it! Is it bricked????? Someone pleeeease help! If I try to go into download mode odin pics it up and says added but the screen is just black with colored spots...what do i do? Was able to flash with odin but stuck in a bootloop now!
pammiecaykz said:
So now it won't even come on just a black screen with colored specs on it! Is it bricked????? Someone pleeeease help! If I try to go into download mode odin pics it up and says added but the screen is just black with colored spots...what do i do? Was able to flash with odin but stuck in a bootloop now!
Click to expand...
Click to collapse
Odin a working ROM onto it. You're soft bricked, but you can recover. Hopefully you had a backup.
ok well the problem seems to be getting worse. I would say you should start fresh from everything because I have no idea what full rom you are currently on. it sounds to me that you have a bit of a few and something went wrong. at this point because you are having disappearing apps, i think it would be beneficial to you to, once again, start fresh.
remove your sim card and your sd card. save your pics, music, or whatever else you want onto your computer and then format it to all defaults. i see you know how to use odin, so odin to raver's full KC1 and make sure you flash the modem, bootloaders, etc and that they are all in the right place in odin. once that is flashed and everything is up and running, power off the phone and then odin to bali 3.3uv. woot.
now odin to kg4 and let it boot up. once it does, go back into dl mode, flash drhonks cwm. so now you have recovery+bootloaders. i would go into recovery, disable voodoo, reboot recovery, then flash kh1 from whitehawk/posted by chadster (read the thread so you know how to get cwm back). let boot up. reenable voodoo with the voodoo app. and let me know how it goes.
pammiecaykz said:
But everything is so confusing to me, I read about how you feel about "noobs" and I am in no way trying to annoy ANYONE.
Click to expand...
Click to collapse
i am always willing to help. not sure what you mean by that, but we get a lot of "i am a noob, so explain this to me", which is fine (i know everything is confusing at first), but that does not mean you should not read the OP ot at least scan the threads/search the forum and specific thread. people really give our devs crap because they dont read. i am just trying to prevent that. nothing against you. or noobs in general. i still consider myself a noob. it just gets old saying "dont use rom manager""you install krylons cwm by moving 2 files" etc; especially when people ask a question...and the answer is posted in the post above theirs...
Well I went throught the whole process before I read your reply. I have everything on there but seem to have trouble with this "Linda" lady. I am not hearing here...which is an issue right? I don't know what to do now and my market app is gone again.
if your actual market has disappeared, go into the system/app folder on the phone and rename the com.vending or whatever to "vending.apk". then reboot and it should be there. linda should be quiet if you have already converted everything. (at least she does on froyo)
dumb question, how do i go into the folder to rename it? and how do i know if everything is converted right?
also what does the option apply update from sd card mean while i am in cwm
do you have root explorer or super manager? dl from the market. long press to move/rename or whatever. its a regular explorer with stone perks. but if it gives you a read error, look at the top right and switch to Read/Write.
you can get the voodoo app and it will tell you under lagfix
so it just keeps randomly shutting down now!
Are you sure you odined. Kc1 by raver with all of the odin files? Not just the pda, but 4 or 5 different files.
Sent from my SGH-T959V using XDA Premium App
look, pammie, this is a problem with gingerbread in its present state of development for SGS 4g. Don't blame the devs. They are doing the best they can with a newly issued model. It's samsung's fault for taking out the internal SD card in the 4g in hopes of saving $20 on the price of a phone. If samsungy had left it in, Vibrant ports would be a whole lot easier to do.
I personally have been over and over this and except for one fluke when "Linda" installed ext4 after I turned off the phone but left it plugged into the charger, I have not been successful. In the one fluke, quadrant shot up to 2500 on a tegrak stable overclock to 1.4, but then I installed something meant only for froyo (I think it was performance.zip) and the phone went into a repeating boot cycle.
My suggestion is revert back to froyo with ICBINB or some other froyo build, if you can, install the various speed improvements and wait a few weeks for the problem to be solved.
Jaeger555 you've done it again! I forgot that there were a couple more files besides the main KC1! Blessed be! I'll try that tonight. Belay that, pammie, do what jaeger555 says and if you can get back to froyo maybe stay there for a bit. btw ya like my new avatar? I found something that matches the fake indian-spanish handle I use. Wonder what he's smoking -- and where I can get some
I wasn't blaming anyone, and I apologize if it seemed like I was. I have literally been at this for over 12 hours and I just don't know what to do. I believe I flashed the correct kc1. And odined to the kg4 (is it?) and now I am stumped with this kernal thing. Do I download both files? I am so lost, I just want my phone to be decent again lol.
I can help you when I get home. Won't be a while though. Figure out what rom you want and I can help you tweak it. I got some tricks that will help you in the long run
Sent from my SGH-T959V using XDA Premium App
Pammie I found what we're looking for. It's called the KC1 Cleanup Rom.
link to raver's thread: http://forum.xda-developers.com/showthread.php?t=1129933
direct link to rom: http://sourceforge.net/projects/kc1cleanup/files/hawk.zip/download
The file is called hawk.zip. Unzip it and it contains the following files:
PITT = sgs4g.pit
PDA = T959VUVKC1-REV00-ALL-low-CL933594.tar
Phone = T959VUVKC1-Phone-CL932707.tar
CSC = SGH-T959V-CSC-TMB.tar
To install, boot up odin and put the files into the places for pit, pda, phone and csc. Hopefully that will clean off the gb bootloaders and you can start over. I assume the phone will now be unrooted but minus gb bootloaders. Then you can Odin the stock rooted KC1 rom PDA_KC1.tar.md5. I assume you have that one.
ps. Once you download hawk.zip rename it to KC1 Cleanup Rom so you know what it is!
GB was really easy for me to install, no problems whatsoever. Maybe this will help you out.
1) Odin KC1 by RaverX3X
2) Odin KH1 Leak by krylon360
3) Odin KG4 Kernel by drhonk
4) make sure lagfix is DISABLED through CWM
5) boot up
6) install BusyBox 1.17 or 1.18
7) make sure lagfix is still DISABLED through the Voodoo app
8) WIPE!
9) CWM your GB ROM
10) enable lagfix through CWM
11) restore data if you need to
12) reboot!
I've actually done this three times, and every time worked flawlessly. Best of luck!
Pammie, did you get it working? Lol. Finally home...
Sent from my SGH-T959V using XDA Premium App
Not working yet

Voodoo Lagfix, rooting, etc

I'm trying to root my g/f's Charge, and there is an immense amount of information on this forum about it, so much so, I am getting confused. I have an Incredible and I am more than comfortable rooting/kernels/roms with it, but I am having a hard time with the Charge. My g/f just wants a rooted Charge (she has EE4), running stock. (she is afraid she will have problems/glitches with her phone like I have with experimental stuff with my Incredible).
So, I can follow the directions for rooting here http://forum.xda-developers.com/showthread.php?t=1122657 but I am very confused on how/when to install(or whatever you do) the voodoo lag fix. Is voodoo lagfix just a kernel or something else? If it's a kernel, once I have CWM recovery, if I flash voodoo lagfix, will it give me root access? I know I seem rather lost, but any help would be most appreciated. I'm trying to find the simpliest/lowest maintanance/less problematic way to get her root access without her having problems with it when I am not around.
Thanks
jprakes said:
I'm trying to root my g/f's Charge, and there is an immense amount of information on this forum about it, so much so, I am getting confused. I have an Incredible and I am more than comfortable rooting/kernels/roms with it, but I am having a hard time with the Charge. My g/f just wants a rooted Charge (she has EE4), running stock. (she is afraid she will have problems/glitches with her phone like I have with experimental stuff with my Incredible).
So, I can follow the directions for rooting here http://forum.xda-developers.com/showthread.php?t=1122657 but I am very confused on how/when to install(or whatever you do) the voodoo lag fix. Is voodoo lagfix just a kernel or something else? If it's a kernel, once I have CWM recovery, if I flash voodoo lagfix, will it give me root access? I know I seem rather lost, but any help would be most appreciated. I'm trying to find the simpliest/lowest maintanance/less problematic way to get her root access without her having problems with it when I am not around.
Thanks
Click to expand...
Click to collapse
The Voodoo lagfix is just a version of kernel that you can install that changes the filesystem. If you just want stock, just flash a non voodoo kernel and u will still have root.
There are pre-made packages which should make it easier on u by cutting back steps. Grab the rooted EE4 package here.
All you have to do is extract the tar, then flash in Odin and you're good to go.
So, couple more newb questions (sorry). Installing a new kernel will not wipe her phone as long as I don't data wipe correct? Also, I keep reading that the voodoo lagfix is a lot faster, but is it really stable and pretty worry free? Like I said, it's for my g/f, and I'm not around all the time to help with it if she has problems. I mainly want to install Titanium backup and get rid of most of the bloatware and hope that the voodoo fix will make it quicker in general.
But my understanding so far is, run Odin, install CWM, then install the kernel of my choice for root access. Again, sorry for the questions. The guides that are out are really helpful, but I get confused at some of it and Odin/Samsung are a whole new animal to me.
I'm sure there will be more questions to come. Thanks ahead of time.
jprakes said:
So, couple more newb questions (sorry). Installing a new kernel will not wipe her phone as long as I don't data wipe correct?
Click to expand...
Click to collapse
Correct. It's recommended that you wipe cache & dalvik though (will not affect what you see).
jprakes said:
Also, I keep reading that the voodoo lagfix is a lot faster, but is it really stable and pretty worry free? Like I said, it's for my g/f, and I'm not around all the time to help with it if she has problems. I mainly want to install Titanium backup and get rid of most of the bloatware and hope that the voodoo fix will make it quicker in general.
Click to expand...
Click to collapse
Voodoo lagfix converts the filesystem to one that is the Linux standard which improves I/O performance. As far as being worry free, I can't guarantee she won't run into problems down the road, whether it's with an OTA update or other program she downloads that is not compatible with the changed filesystem. If you want to be safer than sorry, I'd say to just skip it altogether.
jprakes said:
But my understanding so far is, run Odin, install CWM, then install the kernel of my choice for root access. Again, sorry for the questions. The guides that are out are really helpful, but I get confused at some of it and Odin/Samsung are a whole new animal to me.
I'm sure there will be more questions to come. Thanks ahead of time.
Click to expand...
Click to collapse
All you need to do is run Odin and flash the extracted ROOTED EE4 package I linked above. This package already has a rooted kernel AND CWM baked in. But normally yes, those would be the next steps.
Just be sure to fully read the Odin instructions and follow them accordingly if it's your first time.
If you want root access without losing ANY of the stock stuff (i.e. kernel, recovery) this is another option that may work for you:
Go to this site, download the su-2.3.6.3-efgh-signed.zip file and put it on your g/fs sd card.
Assuming the drivers are installed on the computer being used and USB Debugging (under Settings > Applications > Development) is checked on the phone, start Odin 1.83 (this is the version I used at least).
With the phone OFF (some say take out the battery, some say leave it in), connect phone to computer while holding the volume-down button - should now enter "Download" mode (yellow android on screen).
After UNchecking Auto-Reboot (and replacing the battery if you took it out), under PDA flash 0817_charge_recovery.tar.md5 (found here).
If ODIN says it was successful, disconnect phone, but DO NOT RESTART PHONE YET!!
Hold down vol up + home key + power - you will see the samsung logo, but continue holding all three until it goes away then comes back (I've seen other combinations mentioned, but this is what has worked for me).
If done correctly, you should now boot into CWM recovery. To flash in CWM simply select "install zip from sdcard", then "choose zip from sdcard" and navigate to wherever you put the su-2.3.6.3-efgh-signed.zip file on the sd card and select it. Once done select reboot system now (may have to select Go Back to get to this option - I can't recall).
What is nice about this approach is that once you reboot your phone, the CWM you flashed in ODIN will be overwritten by the stock recovery, making your phone exactly as it was prior to ODIN - with the exception of being rooted and Superuser installed. Also, this is a "brief" listing of steps - I agree with d-loko that you should read up on using ODIN if you haven't used it before.
Hope this helps, and if not, or if it wasn't what you were looking for ... feel free to disregard!
d-loko said:
Correct. It's recommended that you wipe cache & dalvik though (will not affect what you see).
Voodoo lagfix converts the filesystem to one that is the Linux standard which improves I/O performance. As far as being worry free, I can't guarantee she won't run into problems down the road, whether it's with an OTA update or other program she downloads that is not compatible with the changed filesystem. If you want to be safer than sorry, I'd say to just skip it altogether.
All you need to do is run Odin and flash the extracted ROOTED EE4 package I linked above. This package already has a rooted kernel AND CWM baked in. But normally yes, those would be the next steps.
Just be sure to fully read the Odin instructions and follow them accordingly if it's your first time.
Click to expand...
Click to collapse
I'm hoping my last question, and it concerns sdcard problems. Will the rooted EE4 package give her problem free access with her sdcard while using the phone AND when connecting to her computer, or do I need to use lagfix. The SDcard problem/solutions are confusing me a bit.
dwitherell said:
If you want root access without losing ANY of the stock stuff (i.e. kernel, recovery) this is another option that may work for you:
Go to this site, download the su-2.3.6.3-efgh-signed.zip file and put it on your g/fs sd card.
Assuming the drivers are installed on the computer being used and USB Debugging (under Settings > Applications > Development) is checked on the phone, start Odin 1.83 (this is the version I used at least).
With the phone OFF (some say take out the battery, some say leave it in), connect phone to computer while holding the volume-down button - should now enter "Download" mode (yellow android on screen).
After UNchecking Auto-Reboot (and replacing the battery if you took it out), under PDA flash 0817_charge_recovery.tar.md5 (found here).
If ODIN says it was successful, disconnect phone, but DO NOT RESTART PHONE YET!!
Hold down vol up + home key + power - you will see the samsung logo, but continue holding all three until it goes away then comes back (I've seen other combinations mentioned, but this is what has worked for me).
If done correctly, you should now boot into CWM recovery. To flash in CWM simply select "install zip from sdcard", then "choose zip from sdcard" and navigate to wherever you put the su-2.3.6.3-efgh-signed.zip file on the sd card and select it. Once done select reboot system now (may have to select Go Back to get to this option - I can't recall).
What is nice about this approach is that once you reboot your phone, the CWM you flashed in ODIN will be overwritten by the stock recovery, making your phone exactly as it was prior to ODIN - with the exception of being rooted and Superuser installed. Also, this is a "brief" listing of steps - I agree with d-loko that you should read up on using ODIN if you haven't used it before.
Hope this helps, and if not, or if it wasn't what you were looking for ... feel free to disregard!
Click to expand...
Click to collapse
thanks for the alternative option, much appreciated. I don't have a problem with using CWM, I have it on my rooted Incredible, so I'm very used to it. But I do like having options, so thanks for the reply.
jprakes said:
I'm hoping my last question, and it concerns sdcard problems. Will the rooted EE4 package give her problem free access with her sdcard while using the phone AND when connecting to her computer, or do I need to use lagfix. The SDcard problem/solutions are confusing me a bit.
Click to expand...
Click to collapse
Flash the file found here in CWM after ODINing the EE4 package - that should do the trick. Just make sure it's on the sd card before ODINing the EE4 package - just in case!
jprakes said:
thanks for the alternative option, much appreciated. I don't have a problem with using CWM, I have it on my rooted Incredible, so I'm very used to it. But I do like having options, so thanks for the reply.
Click to expand...
Click to collapse
No problem, I'm a fan of options as well!

Have an SGH-T959W on Wind? Don't worry, it is exactly the same as the SGH-T959V!

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

Full on Noob, need help if possible.

Okay so, I love my Infuse but getting really tired of not being able to download anything off the play store. Just tired of it's rather less than great performance right now as well. It's is running 2.3.6 GB and want to get this thing up to ICS if possible. Just something running 4.0 so I can use my phone for what I need too. It is not rooted, no cyanogenMod, NOTHING. As the title says, I'm a full on noob here and I apologize if all this is covered in other threads, however I have just gotten to the point where I have found myself even more lost than where I started on what I needed to do/get. If someone can, I will literally need this spelled out to me (no pun intended), in order of the steps I need to take with everything. I'm getting tired of confusing myself even more from all the different stuff I have seen all over the place and I know without some serious guidance, I will just brick my phone. Thanks for any help! :laugh:
I understand this community can be a bit unorganized and confusing so I'll give you my process for rooting and installing custom firmware (there are other ways, but this works for my AT&T Infuse 4G SGH-i997).
First of all, no one uses ICS on the Infuse. There is a ROM, but it's underdeveloped because JB came out so quick. You will need to flash it to get to higher operating systems, but it is by no means a daily driver. Even JB is a little buggy compared to KitKat on the Infuse these days.
The first thing you want to do is root your phone and get a custom recovery.
There are more than a few options for rooting, but I prefer using ODIN (as I understand it, this is the tool Samsung uses to restore soft bricked phones). So this is a good thing to know how to do, in case you ever do soft brick your phone, you'll know exactly what to do.
Read the ODIN instructions in full as I will only briefly explain.
You're going to have to install Samsung drivers.
You'll be using UCLB3_Unbrick_root_1.1.zip. If you used UCLB3_Unbrick_1.1.zip it would just get you back to stock GB with no root added.
To put your phone into download mode, first turn off your phone. Plug a usb cable into your computer. Then with the phone off, hold down both volume buttons and plug the usb cable into your phone. A warning will come up and you push volume up to accept, realizing that you can easily soft brick your phone if you loose power or unplug during a download.
Once downloading is done, the phone will reboot and you'll be disappointed to see that nothing has changed. Except one small thing, you are now rooted and you should have an application called SuperUser that will allow you to do nifty and also dangerous things.
Now follow this step in the ODIN instructions to add the custom recovery (CWM = Clock Work Mod):
The version with root works exactly like the above version, but adds root. To add CWM recovery to the rooted version, download a custom Gingerbread kernel from HERE or HERE and flash the zImage using SGS Kernel Flasher (found in the Play Store) on the phone. If you go this route for root and CWM, your Custom Binary Download counter will not show any custom binary activity.
Click to expand...
Click to collapse
If you follow the link in the second "HERE," you'll get the kernel I prefer since it was most recently updated. Scroll down the downloads section and grab "2013.04.30-CWM-Synthesis-1.2Ghz.zip." (1.2Ghz is stock for our processor, anything higher will be overclocked which I don't recommend).
Extract that and grab the zImage file in the update folder. You're going to copy this to your phone in a second.
But first you need SGS Kernal Flasher, you can get it off the playstore, but I despise having to log in to an OS I'm going to write over in less than a minute so I download the APK from here. Hopefully you know how to install APKs from your SD card and that you'll have to check install from unknown sources.
Now flash the zImage using SGS Kernel Flasher. Your phone will reboot and hang on the Samsung logo and a creepy voice is going to tell you about how she's partitioning your phone and installing Voodoo lag fix. This is normal. Eventually your phone will reboot back into GB and you'll be ready to flash any ROM of your choice by rebooting into recovery.
You reboot into recovery by holding the volume up and volume down button while powering on the phone. This is different than download mode and will take you do a new screen that you control with the volume keys.
You'll be using this to put new software on your phone.
Now you can bassically follow the instructions for getting to CyanogenMod 11 (Kit Kat) from GB.
The first bullet is what I just explained in detail.
Note that I didn't include the links in these instructions, just follow the link above to get to the original post.
Obtain CWM, this can be done using Jscotts Odin back to stock (Follow instructions and use SGS kernal flasher to obtain CWM)
Run Qksters IMEI backup script here
Make certain you are on ICS, this can be done by flashing Entropy's CM9
It is recommended now that you remove your SD Card
CWM: Wipe Cache / Factory Reset
Install ROM: Scroll down for downloads sectoion
... The package will start to install..
... Phone will reboot into the install screen again...
... Continue to install [Automatically] If not manually flash again
... Phone will reboot again and be at the recovery screen...
Install Gapps: Here - Working swipe!
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
Click to expand...
Click to collapse
To be clear, when you flash a ROM, it won't be like flashing the zImage (that was just to get custom recovery). To flash the CM9 ROM or Qksters IMEI backup script for example, you leave the rom in the .zip file and simply put it on your SD card. Once in the recovery screen, you select "Install Update from ZIP" and navigate to the particular ROM you wish to install.
Also after updating to a higher version of Android, your phone will sometimes hang on the install screen for a long time. If it does for more than five minutes, it's safe to pull the battery and try flashing again (and sometimes necessary).
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Lately I've been using CyanFox and I have to say, it's the most stable ROM I've used in a while.
If you have any questions about this, feel free to ask.
Best of luck and happy flashing,
~bokonon9
Thank you muchness!
Thank you very much for helping me in this mess! I greatly appreciate it. I love my Infuse and do not want to get rid of it quite yet so hopefully this will help! Once I get a new usb cord I will get on this. My toddler decided to get a hold of it and it has to set a certain way now and can't be moved. This, is no bueno! Anyways, THANKS AGAIN!!! :laugh:
Goodluck! :laugh: :good:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Click to expand...
Click to collapse
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
wwr said:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
Click to expand...
Click to collapse
i would say go back to stock gb with odin and basically start over but with ics i always let it reboot to get a "feel" for it then i reboot to recovery and wipe basically everything then flash the next level of android which should be cm 10 then i let that boot then repeat that to get to kitkat 4.4.3 CarbonRom....sometimes you have to flash the same rom twice to get it to flash tho
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
wwr said:
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2091900&page=370
read the last post on that page by scmfxt

Categories

Resources