I have one S3 that's stock and another that's rooted, so I decided to try CM9 first on rooted S3 because CM10 didn't seem quite ready for daily use. Flashed ROM and Gapps, and things were fine until wi-fi ceased functioning. Worked, then didn't ever again. Nothing I found in searching this helped. And I couldn't get to PlayStore because there was no connection. Tried many things to reset wi-fi, but despite excellent signal, the phone wasn't connected to Internet. I reflashed CM9 (same most current release) but it didn't help.
So, having not actually done anything other than adding ROM Manager, I decided to flash latest CM10 nightly with CWM recovery via ROM Manager. Everything was fine, except of course I forgot I needed to install newer Gapps. However, when I went to do so, ROM Manager was no longer there and manually trying to get recovery only resulted in download mode, which meant I couldn't install Gapps or do much of anything.
I spent time trying to figure out how to get recovery, but having run out of options, I thought it perhaps best to flash back to stock using desktop Odin. I have the MD5 for 4.1.1 LK3. So I did this, but now once past the Samsung and AT&T animations, the phone stops with a Samsung logo. And that's where I'm at.
I know I've seen threads on fixing this, but I can't find them and I would like rectify the softbrick circumstance. What to do.
eduardo_b said:
I have one S3 that's stock and another that's rooted, so I decided to try CM9 first on rooted S3 because CM10 didn't seem quite ready for daily use. Flashed ROM and Gapps, and things were fine until wi-fi ceased functioning. Worked, then didn't ever again. Nothing I found in searching this helped. And I couldn't get to PlayStore because there was no connection. Tried many things to reset wi-fi, but despite excellent signal, the phone wasn't connected to Internet. I reflashed CM9 (same most current release) but it didn't help.
So, having not actually done anything other than adding ROM Manager, I decided to flash latest CM10 nightly with CWM recovery via ROM Manager. Everything was fine, except of course I forgot I needed to install newer Gapps. However, when I went to do so, ROM Manager was no longer there and manually trying to get recovery only resulted in download mode, which meant I couldn't install Gapps or do much of anything.
I spent time trying to figure out how to get recovery, but having run out of options, I thought it perhaps best to flash back to stock using desktop Odin. I have the MD5 for 4.1.1 LK3. So I did this, but now once past the Samsung and AT&T animations, the phone stops with a Samsung logo. And that's where I'm at.
I know I've seen threads on fixing this, but I can't find them and I would like rectify the softbrick circumstance. What to do.
Click to expand...
Click to collapse
Did you remember to factory reset (wipe /data) when flashing the stock ROM? That's the most common cause of soft-bricking in this scenario.
If not, boot into recovery (Vol Up + Home + Power) and do so, then try booting the phone again.
Do I do factory reset from desktop Odin in download mode?
That's one possibility, but if you don't want to go through the Odin process again, you can just do the reset from recovery as I outlined above.
smelenchuk said:
That's one possibility, but if you don't want to go through the Odin process again, you can just do the reset from recovery as I outlined above.
Click to expand...
Click to collapse
Ah...volume UP. But wipe data/factory reset didn't help. If I select update from external storage, would that be MD5 or...?
Okay, I wiped cache partition and I'm in business. No more softbrick. Thanks!
Related
Hey guys/gals,
I recently bought a Koodo Galaxy s2x. After a few weeks I looked online and saw that there were some JB Roms for my phone. I couldn't resist and tried to flash one after rooting. I didn't have many problems with it, but there were some glitches that started to bug me, so I decided to see about going back to stock (I should have done this first I know). So then after hours(many) of searching, the best I could find was a T-Mobile stock Rom I decided to try and flash it (both times via odin). I also read somewhere that I should use darkside superwipe to clear my cache, so I tried that, but ever since that CWM stopped working on my phone. anytime I tried to do any back up or anything it just froze, and I had to hard boot. Finally I just tried flashing T-Mobile stock ICS, and Odin said "Failed". I decided to just unplug my phone, as I thought I already screwed it up, but after rebooting, the T-mobile Rom worked. I don't understand why it works fine if the Flash Failed. Now, I can no longer connect to kies (I'm hoping official JB will be shipped soon!), and I am wondering if I can somehow return to a stock Koodo Rom, and if it will connect to Kies again, as it previously had. I have looked a lot and have not found anything that I fully understand. I'm not overly experienced, which is why I should not have flashed to begin with. This is the closest thread I have found to help me, but I don't fully understand what all I need to do:
"Haven't seen anyone shared this yet.
Here's the KOODO ICS 4.0.4 stock ROM I used CWM to flash to stock after I tried the custom ROM.
h t t p s : / / sourceforge.net/projects/koo...d.zip/download
I also flashed DARKSIDE.SUPER.WIDE before I flashed this or you can used CWM Recovery 6.0.1.2 to wipe system and cache."
Is it possible for me to get back to stock phone? and still connect to Kies? and then possibly upgrade to JB through Kies if Hercules ends up receiving it?
Thanks for any help you can give me. Here is all my current phone info incase this helps:
Model:
SGH-T989
Android Version:
4.0.3
Baseband version:
T989DTLLG2
Kernel version:
3.0.8-perf-T989UVLE1 -CL508451
[email protected] #1
SMP PREEMPT Sun May 6 15:07:07 KST 2012
Build number:
IML74K.UVLE1
Thanks.
If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: https://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.
arcsine said:
If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: h t t p s ://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.
Click to expand...
Click to collapse
That link doesn't work, it says cannot find page. Also, my phone is currently not rooted, does it have to be rooted to flash from recovery? if not what do I do to flash from recovery? I know how to get into recovery, but after that do I use 'apply update from external storage'? Do I have to wipe the cache first?
Thanks.
PS: I just want to be able to get back to stock for now. At least until I learn more about flashing Roms. There is still lots for me to learn, like kernels, radios, Nightly's for official Roms, or even how to properly flash a rom without feeling lost. If I know a way to get back to stock comfortably, It will give me more reason to try some other Roms (once I learn how).
Here is a working link to the stock Koodo ROM: http://sourceforge.net/projects/koodostock/files/KOODO_SGH-T989D_Stock_Signed.zip/download
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted: http://galaxys2root.com/t-mobile-galaxy-s2/how-to-root-icsgb-on-t-mobile-galaxy-s2-sgh-t989/. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.
arcsine said:
Here is a working link to the stock Koodo ROM:
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted:. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.
Click to expand...
Click to collapse
Thanks a ton... Worked perfectly! I'm hoping it will connect to Kies once again.. I'll let you know if it works.
Unfortunately, I still can't connect to Kies.. It just sits at the Loading status (for like 10-15 mins). But At least I don't have all of the T-mobile apps and stuff anymore!
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
So building and flashing ROMs is nothing new to me. I've been doing this since the Captivate days and have done this with all of my Android devices including my new Kindle Fire 2 (which is running 4.2) but for the life of me, I cannot get a 4.2 ROM running smoothly on my GS3.
Here's the deal. When flashing any 4.2 ROM, I get the same issues. Most times, it takes several (as in at least 8) presses of the Power button or home button to wake the screen. When it finally wakes, the animation on the "unlock" button freezes. I can sometimes still swipe it to unlock but most times, the button itself doesn't move. The phone typically runs fine once unlocked.
I know there are some camera issues still but mine make it totally unusable. I can open the camera but rotating it typically screws the orientation up on screen and no other screen presses work afterward. If I tap to open settings or flash settings, the options show up on screen but then again, screen presses are no longer working. I have to exit camera and start over which typically results in a couple Gallery FCs before it finally opens again.
What I've done to no avail. I've tried multiple combinations of wiping cache, system, dalvik, internal SD card, all within TWRP as well as checking MD5 on the ROMs after they've been copied to my SDCard and am running the latest TWRP available for my phone. I have also tested this without restoring ANY data and using the packaged launchers and I get the same behavior. If I go back to a 4.1.1 ROM, everything is perfectly fine. This ONLY happens on the 4.2 ROMs available.
I'm looking for any help on getting this sorted not because it's a big deal but because it's driving me friggin' insane!
Re: [Q] ALL 4.2.2 ROMs hate my phone. Help thread.
Have you tried CWM Recovery yet? It's what I use and have literally tried every rom put there with no problems ever.
Sent from my SGH-I747 using xda premium
Jirv311 said:
I've tried multiple combinations of wiping cache, system, dalvik, internal SD card, all within TWRP
Click to expand...
Click to collapse
You don't mention it, but did you use the wipe option that is at the bottom left of the TWRP wipe menu screen? The scary looking one that says it's probably not needed?
I do that one every time.
I would restore to stock 4.1.1. Then flash TWRP's latest again and try one more time by flashing something mainstream like CyanogenMod 4.2.2.
Flashing stock ROM's has fixed a couple weird issues for me lately.
I just flashed stock 4.1.1 through Mobile Odin Pro, installed CWM Touch, and flashed AOKP 4.2.2 from Task650 and same behavior. In fact, now when I hit the power button to lock the phone, I cannot turn it back on without rebooting the phone by holding power.
I flashed stock through Mobile Odin to try and prevent tripping flash counter but I may just flash from Desktop Odin and try again.
EDIT: Is there an updated boot loader (ICS to JB) that gets flashed through desktop Odin?
Jirv311 said:
I just flashed stock 4.1.1 through Mobile Odin Pro, installed CWM Touch, and flashed AOKP 4.2.2 from Task650 and same behavior. In fact, now when I hit the power button to lock the phone, I cannot turn it back on without rebooting the phone by holding power.
I flashed stock through Mobile Odin to try and prevent tripping flash counter but I may just flash from Desktop Odin and try again.
EDIT: Is there an updated boot loader (ICS to JB) that gets flashed through desktop Odin?
Click to expand...
Click to collapse
Have you tried a different kernel? I run ktoonsez KT747 with Task's AOKP with awesome results. Nothing against Task's underwear kernel, but maybe the 4.2 version just doesn't like your phone.
Jirv311 said:
I just flashed stock 4.1.1 through Mobile Odin Pro, installed CWM Touch, and flashed AOKP 4.2.2 from Task650 and same behavior. In fact, now when I hit the power button to lock the phone, I cannot turn it back on without rebooting the phone by holding power.
I flashed stock through Mobile Odin to try and prevent tripping flash counter but I may just flash from Desktop Odin and try again.
EDIT: Is there an updated boot loader (ICS to JB) that gets flashed through desktop Odin?
Click to expand...
Click to collapse
yes if you flash the 4.1.1 stock file through the desktop odin you will upgrade the bootloader , with the new boot loader everythime you reboot the phone with a custom recovery like cwm or twrp it will raise the flash counter. Here is what I would do. reboot to twrp , wipe data/factory reset , wipe cache wipe dalvic and wipe system. then go to advanced and reboot into bootloader/download mode. once in downlaod mode flash the rooted ics 4.0.4 rom with desktop odin, I was going to link the thread by mrrobinson but it seems someone un-stickied it so your going to have to try and find it.either go back to stock from sammobile.com and root it or get a pre-rooted file. once your back on stock rooted ics download goomanager from the play store. inside the goomanager click install open recovery script. this will install twrp on your phone. after that put the rom you want back on your and follow the op for that rom. do it exactly as it states.I reccomend task650's rom. If you still have a problem try a different kernel. Not all phones are the same, some phones wont even boot up with certain kernel's. hope this helps
edit here is the link http://forum.xda-developers.com/showthread.php?t=1739426
Intub8 said:
yes if you flash the 4.1.1 stock file through the desktop odin you will upgrade the bootloader , with the new boot loader everythime you reboot the phone with a custom recovery like cwm or twrp it will raise the flash counter. Here is what I would do. reboot to twrp , wipe data/factory reset , wipe cache wipe dalvic and wipe system. then go to advanced and reboot into bootloader/download mode. once in downlaod mode flash the rooted ics 4.0.4 rom with desktop odin, I was going to link the thread by mrrobinson but it seems someone un-stickied it so your going to have to try and find it.either go back to stock from sammobile.com and root it or get a pre-rooted file. once your back on stock rooted ics download goomanager from the play store. inside the goomanager click install open recovery script. this will install twrp on your phone. after that put the rom you want back on your and follow the op for that rom. do it exactly as it states.I reccomend task650's rom. If you still have a problem try a different kernel. Not all phones are the same, some phones wont even boot up with certain kernel's. hope this helps
edit here is the link http://forum.xda-developers.com/showthread.php?t=1739426
Click to expand...
Click to collapse
I just did exactly this just now and the same exact symptoms occur. Even after flashing ktoonz kernel. This is the weirdest thing I've ever dealt with.
Jirv311 said:
I just did exactly this just now and the same exact symptoms occur. Even after flashing ktoonz kernel. This is the weirdest thing I've ever dealt with.
Click to expand...
Click to collapse
yes that is very odd. If it works fine on stock or 4.1 rom's then it definatly not a hardware issue with the button. Im sorry man , I have no idea what it could be.
Yeah I'm confused as well. I just flashed the last CM10.0 4.1.2 and it runs flawlessly. Definitely a head scratcher.
Hey guys hopefully you can help me. I was rooted for like 3 or 4 months now and have had not many problems or not anything I couldn't fix my self. My phone gets stuck on the Samsung Galaxy s4 screen anytime I reboot. I have tried different roms, different kernels, I even odin back to stock. I was using TWRP 6.0 then reverted back to TWRP 5.2 to see if that was causing the problem. Still have problems. I am going to re download the stock tar to see if it was a bad download but Odin checks the md5 and says it was good. Odin says passed every time also. Odin version is 3.07.
I get a error before and when trying to wipe dalvic cashe. I can wipe reg cash no problem. I think my phone is not mounting the internal storage when it reboots. I could be way off but need help asap. If I format super wipe with twrp then restart twrp and then factory reset I can install or restore a rom some times but still cant restart the phone. Any hope would be greatly appreciated.
EDIT
I wanted to edit my previous commet. LiquidSmooth seems to be running fine. So TW roms and GE roms **** up on my phone when I restart. so is it the internal systems when I have TW roms. I think it has something to do with partictions messing around maybe.
I like TW roms and want to continue to use them... Thank you
Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you
I got this problem a few days ago and found some topic including this one. You should check it out.
Well, what worked for me was Odin to stock firmware, root again, install recovery then custom rom. Now it's working fine. Try to downloading it again to see if it works. I downloaded mine from here, rooted and recovery it using this one.
TheAxman said:
Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you
Click to expand...
Click to collapse
+1 to what he said. I bet if you go into the stock recovery after odin flashing it will say something like cannot mount /data partition. Factory reset there, and it should fix that and make it mountable. (Its important to use the stock recovery factory reset after the odin, don't flash a custom recovery right after flashing)
This was incredibly helpful. I had the same issue. Thank you.
This is also applicable to the Verizon Wireless model.
Hi all, found my old SGH-T989 and I want to turn this phone into my play phone.
I am new to rooting and all and I don't know which versions of what to use. Everytime I mess up, I have to restore the phone back to stock 2.3.6 then upgrade to 4.1.2 via Kies, then try to root and such.
Problem is... I don't know which ROMs, gapps to use and which cwm to use!!! Seems like every guide out there is outdated because I get stuck in a bootloop every single time I try to flash a ROM or I get Error 7...
Any tips?
I just want 4.4.2 at least on my SGH-T989 What are my options? What are your suggestions?
KSmooove said:
Hi all, found my old SGH-T989 and I want to turn this phone into my play phone.
I am new to rooting and all and I don't know which versions of what to use. Everytime I mess up, I have to restore the phone back to stock 2.3.6 then upgrade to 4.1.2 via Kies, then try to root and such.
Problem is... I don't know which ROMs, gapps to use and which cwm to use!!! Seems like every guide out there is outdated because I get stuck in a bootloop every single time I try to flash a ROM or I get Error 7...
Any tips?
I just want 4.4.2 at least on my SGH-T989 What are my options? What are your suggestions?
Click to expand...
Click to collapse
You need to be on 4.1.2 for this to work. I am bit responsible for what happens. You can get 4.1.2 for Odin from samfirmware.com. Download the latest TWRP from here: http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar and flash it in Odin. Your phone should reboot. Boot into recovery by powering off your phone and then holding power and the two volume buttons until you hear two vibrations and then hold just the volume buttons until you see a black screen. Release all buttons. Flash @Chainfire's SuperSU in recovery ( http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip) Wipe cache ald Dalvik and reboot. You should be rooted and able to flash any KitKat ROM. AOSPA is a good choice. It is pretty stable.
Sent from my SGH-T989
I just flashed CarbonROM on my sister's phone this weekend. Rooting is not really required.
My process:
Flash TWRP (this was the most difficult of the entire process. It is still relatively easy though). I used Odin to flash the latest TWRP. TWRP provides odin flashable archives so it is really just a matter of knowing how to flash thing using Odin. This does not require root. The CWM wiki page says that Rooting is not required, nor is it the preferred method when flashing a new rom.
You can use Heimdall, but it is very hit and miss with this phone. Odin is much more "reliable" on the T989. I tried Heimdall, but I ended up having to reset my sister's phone because it flashed the recovery incorrectly.
Download the rom of your choice and its associated gapps package. Put them on your sd card
Boot into recovery. You will need to use TWRP's mechanisms to wipe/factory reset the phone. Then wipe cache and dalvik cache.
Install the zip of the rom and then immediately afterward install the gapps package. I usually wipe the cache and dalvik cache again for good measure at this point, but I understand it is not needed.
Reboot the phone. If all went well, it will take awhile to boot, but you will be sitting at the start screen of a brand new shiny rom.
Set it up and start using it. Most roms already come rooted.
The reason rooting isn't required using this method is because the download mode of the T989 essentially gives you root priviledges.
I've used this process on two T989 phones without any error. If you want to backup your phone, do that in step 3 _before_ you wipe/factory reset your phone.
Usually what I do is just use Odin to flash ClockworkMod then copy the ROMS to the sdcard. Boot into recovery then install zip from SD Card, select ROM. If you use CyanogenMod then just select your device and Google search the cyanogenmod gapps
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app