Develop Bugs

Rooting and flashing ROMS with T-Mobile Note 3 with KitKat

Ok. I have seen several people asking about rooting their T-Mobile Note 3. I am sure there have been posts on how to accomplish this feat. I am going to put out the steps that I took and mention a few other options and my thoughts on those. I hope to make this an all inclusive post for newbies. This method works whether you are on 4.3 or 4.4 BUT you will need to make sure the recovery and ROM you download is for the correct version of android you are using. To make this easier I am going to assume you are already on 4.4 Not everything will be clear but should be able to be easily understood. If there is something you don't understand ask and I am sure people will try to help. That or you can do a google search and probably find the answer a whole lot faster. If you did have a problem and found the solution please post it so others can use your information. I don't have the time at the moment to provide all the links but I will try to update this thread as much as I can.
I am NOT responsible for bricked devices, voided warranties or downloaded virus to your computer.
That being said rooting should be a relatively simple and easy process.
1. Download Odin 3.07 or 3.09 .zip file and install on your computer. (I have found no real difference in between the two when attempting root.) (No link provided just google it.)
2. Download the custom recovery of you choice. (I use and prefer twrp, but some people have had problems flashing ROMs and have had better luck with philz recovery) Below is the link for TWRP. If using 4.4 make sure to download the img.tar file for 2.7. There are other files but you want the one ending in img.tar! http://teamw.in/project/twrp2
3. Open Odin and connect your phone. You need to put your phone into download mode before connecting. Shut your phone off and then turn back on while holding volume down, power and home key. You will see a special screen pop up and a warning. Acknowledge the warning and the connect to the computer. If you don't get a blue bar on the left side of Odin after connecting your phone then you need to update your driver's (google search).
4. Place the .tar file that you downloaded into the PDA(3.07) or AP(3.09) section. Make sure the ONLY boxes on the left are Auto Reboot and F. Reset Time are checked (that should be the default settings)!!
5. Hit the start button. Be advised that Flashing a custom recovery WILL trip Knox.
6. You should the blue bar turn green and say "pass." You know have a custom recovery on your phone and you can disconnect your phone.
At this point you do not have root access, you just have a custom recovery. You now have a choice to make. Do you want your phone rooted or do you want to flash a custom ROM. If you want to flash a custom ROM jump to #8. If you just want root and plan on staying on stock go to #7.
7. Download the latest version of SuperSU file from http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip and flash from your custom recovery. when you restart your phone make sure you can open the SuperSU app. If you cannot go to the play store and reinstall it from there. Congrats!!
8. If you want a custom ROM you need to download the .zip file of that ROM. I would recommend placing it on your EXTERNAL sd card.
9. Go to your custom recovery. There are some things you are going to need to back up prior to Flashing the ROM.
a. Backup your stock ROM, This could save you from some major problems. Back up-system, data and boot-to your EXTERNAL sd card.
b. Backup you EFS files (this can be done via twrp, other wise you will need to do it another way-Google search)
10. Wipe the phone. You want to wipe Data, Cache and Dalvik
11. Flash you custom ROM. Almost every custom ROM comes rooted. You just need to read the info on that ROM
12. Your phone should reboot and you are done!!
Below is some Q&A and helpful tips.
If I upgrade to 4.4 from 4.3 to get a diffent ROM can I switch back? NO
What is "Bricked"? It is a phone that will not boot and only stays on a black screen. Soft Brick is where your phone constantly reboots without opening your ROM.
What is Knox? Google it
Will tripping Knox void my warranty? Probably
How do I get into the recovery? Shut your phone off and then restart while holding the volume up, power and home key. You have to let go as soon as you see the blue letters "Recovery Booting"
There are not that many ROMS for T-mobile can I use an international ROM? Yes! I currently run an international ROM but on most of them you do loose your wifi calling feature. You also need to download a custom T-Mobile Kernel and the Wifi/BT fix.
Should I use CF Auto root or Klingo? I personally don't like the idea of Klingo. Some of the things I have seen they appear to be a little fishy and with them rooting your phone they initially have access to EVERYTHING. CF auto root does not place a custom recovery. You CANNOT flash a custom ROM without a custom recovery. I did it my way because I wanted a custom ROM and just not root.
What about the De La Vega Method? I have no idea and it seemed more work that it was worth. I did not care about tripping Knox
Tips:
Some ROMS will delete your internal memory when flashing as will wiping your phone. That is why I strongly suggest placing the backups and ROMS on your external sd card.
Some ROMS come with an Auroma set up. You will automatically be directed into it when you flash from recovery.
If you are flashing an international ROM make sure that you flash the ROM, T-mobile Kernel and Wifi Fix before choosing the reboot option. If you don't have the t-mobile kernel prior to reboot you will go into a bootloop.
I hope this helps and I will add more and clarify this post in the next few days. I just hope this can help some of you new guys out a little bit and if you found it useful especially if you obtained root please hit the thanks meter.

OK, I deleted all the information here about all the errors I made so that this won't confuse anyone. To summarize my error, I thought I had purchased Android 4.4.2 and flashed the wrong versions. After flashing the correct version, 4.3, everything worked.
The SD-card is not visible in stock recovery and the ADB method won't work without first having root, so that leaves the Odin method.
The Odin method flashes TWRP recovery successfully and when I exited it asked me if I wanted to root the device. I chose 'yes' and it worked for a while then booted into the Android OS. In Android it booted normally, then after I did something which I did not think about and don't recall, a dialog advised me that the GUI portion of the root process still needed to be applied. I allowed it to proceed and now I am rooted with TWRP. I verified the root through ADB by creating a file in the root directory.
Frank

I will try to break this down for you.
1. You need to reflash twrp via Odin to make sure it works correctly since doing auto root.
2. That screen you saw is exactly what you wanted to see. As stated in the OP when you see that screen let go of the buttons and wait, twrp will open shortly. I get the same screen so don't worry. Once you get into twrp and if you need a tutorial on twrp I would suggest looking it up on YouTube.
3. If you reflash the stock ROM via Odin it should fix everything. I am not sure about the partition problem. I will get back if I get some more info.
I would not worry about trying to reflash stock. I would just reflash twrp, boot into recovery and then proceed as listed in the OP.

Frank Westlake said:
**************************************************************************
I found my problem. I think the box, or something, was mislabeled because "About" tells me I have Android 4.3, not 4.4.2. So I flashed the 4.3 version of TWRP and booted right into it. After another reboot to make sure it's stable I'll try rooting again.
Frank
Click to expand...
Click to collapse
Great. Yes, it did not work because 2.7 is written for the new bootloader in 4.4. Are you planning on staying stock jb or planning on flashing a ROM?
sm-n900t: Powered by X-Note V13

FFTony said:
Are you planning on staying stock jb or planning on flashing a ROM?
Click to expand...
Click to collapse
Stock. With root I'm able to customize everything right on the device about as much as the ROM builders. But there are things I cannot do on the device so I'll be keeping an eye on the ROMs to see if anything is attractive.
After I finished this update I refreshed this page and saw that you had been commenting. The screen you saw should be there was also there when I flashed the correct TWRP, and it did move on to TWRP as you said. I'm adding the following paragraph separately so that it's easier for people to find if they need it:
After I had flashed the wrong version of TWRP (4.4 instead of 4.3) it boot-looped to the "SEANDROID NOT ENFORCING" display. To get out of that boot-loop I held the Download Mode keys (HOME-POWER-VOLDOWN) until it rebooted into the first download mode screen, the warning which says you can press VOL-DOWN to boot normally. At that point press VOL-DOWN and it will boot normally. If you press VOL-UP and continue into Download Mode then you will still be in the boot-loop when you reset the device and you will need to reboot again into the Download Mode warning screen and press VOL-DOWN to boot normally.
Thank you very much for your help with this.
Frank

FFTony said:
What about the De La Vega Method? I have no idea and it seemed more work that it was worth.
Click to expand...
Click to collapse
Samsung explains about Root De La Vega here: Samsungknox.com/en/blog/about-root-de-la-vega

Bootloop on grey battery icon, doesnt power off and unable to flash custom roms

So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.

Tan9890 said:
So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.
Click to expand...
Click to collapse
Knox trigger can't be reversed.
Of course, it is a bootloader issue. Follow the procedure and it should work out well for you.
1. Use stock recovery to wipe cache and factory reset.
2. Don't use cf-auto root.
3. Download Philz recovery latest version and supersu zip file. (For Note 2 )
4. Flash Philz. Uncheck auto reboot option in ODIN. Once you get pass message, unplug. Don't start your phone yet. Boot directly into recovery.
5. Install supersu zip file
6. Reboot to check if you are rooted.
7. DN3 5.5 has given me a headache. But it must be something ---- looking at the number of people using it.
8. I prefer Dr. Ketan's V12 Touchwiz ROM.
With Aroma installer, it is almost impossible to go wrong. Support is amazing. Doc himself answers all queries as fast as he can. But choice is yours.
Press thumps up if you found this suggestion helpful.
Link to all the files: http://www.ibtimes.co.uk/root-galax...d-4-4-2-kitkat-install-philz-recovery-1447891
Sent from my GT-N7100 using Tapatalk

Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'

Tan9890 said:
Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'
Click to expand...
Click to collapse
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk

ceomaverick said:
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?

Tan9890 said:
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?
Click to expand...
Click to collapse
Very weird. Never heard of such a thing. Btw, which recovery you are using? TWRP or CWM. Also, chk if the version is latest. The latest versions are fixed for these very issues.
Probably, flashing N7100XXUFNI1 out of the box should solve your problem.
Beyond that I don't have answers.
Sent from my GT-N7100 using Tapatalk

Snippet taken from: http://mark.candleshoreblog.com/2013/06/13/tip-steps-to-prevent-clockwork-or-any-custom-recovery-from-being-overwritten-by-factory-stock-roms-at-android-system-reboot/:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run. All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again. Do the following:
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.
That’s all there is to it.

Can't boot to recovery download mode...

So I rooted my sgh-m919 (m919uvuemk2) running android 4.3. Root went fine, but I couldn't get TWRP (2.8.7.0) installed. Anytime I tried to boot into it, it would just boot normally. Thinking it was knox messing with the firmware boot, I uninstalled it. It seemed to uninstall fine but when I tried to get into recovery/download mode while holding the buttons it flashed the android screen then rebooted normally.
Then I installed andromizer and was finally able to get to TWRP. So I installed cyanogenmod 12.1 fine, but gapps failed (error code 70). So i've lost root. And my phone still can't get into download mode. Flashes and boots normally. Doesn't seem like a hard or soft brick situation, but I don't really know. I wasn't able to find any forums that fit this description.
Any ideas or recommendations on what I should do?
Any help greatly appreciated... thank you!

slungshot said:
So I rooted my sgh-m919 (m919uvuemk2) running android 4.3. Root went fine, but I couldn't get TWRP (2.8.7.0) installed. Anytime I tried to boot into it, it would just boot normally. Thinking it was knox messing with the firmware boot, I uninstalled it. It seemed to uninstall fine but when I tried to get into recovery/download mode while holding the buttons it flashed the android screen then rebooted normally.
Then I installed andromizer and was finally able to get to TWRP. So I installed cyanogenmod 12.1 fine, but gapps failed (error code 70). So i've lost root. And my phone still can't get into download mode. Flashes and boots normally. Doesn't seem like a hard or soft brick situation, but I don't really know. I wasn't able to find any forums that fit this description.
Any ideas or recommendations on what I should do?
Any help greatly appreciated... thank you!
Click to expand...
Click to collapse
I think you may have some terms confused.
To get into Download Mode: Turn off your phone, then turn it on and hold down the Volume Down button. You will get a screen that starts with "Warning!!", and where you can press Volume Up to Continue, or Volume Down to Cance.
To get into Recovery Mode: Turn off your phone, then turn it on and hold down the Volume Up button. You will get some small text at the top left of the screen, and then whichever Recovery you have installed in the Recovery partition will run.
You use Download mode to flash using ODIN.
To get something into the Recovery partition, you can flash using ODIN, or if you are rooted, you can use an app like the TWRP Manager app, and some others.
Also, there isn't an official 2.8.7.0 TWRP. The latest is 2.8.4.0 which may be most/part of your issue.
Getting root is very easy on the SGH-M919, just use the CF-AutoRoot app. But, you don't need root to flash TWRP with ODIN. Also, almost every non-stock ROM will come pre-rooted. So, if you have flashed a CM rom, you are rooted. But, you may need to download SuperSU from the app store.
Rob

Hi Rob, Thanks for the reply. My problem is I hold down the buttons but they no longer boot me into recovery, the android recovery screen flashes for a sec, then boots normally.
I may have found a workaround though, it seems I can now do a recovery option from the power down menu, and that boots me into TWRP. Not sure why the buttons no longer get me into the recovery console, but this may work.
Funny thing is I lost root after installing cm 12.1 while rooted. I think I may downgrade to kit kat because it seems like lollipop drains the battery much faster.
rlichtefeld said:
I think you may have some terms confused.
To get into Download Mode: Turn off your phone, then turn it on and hold down the Volume Down button. You will get a screen that starts with "Warning!!", and where you can press Volume Up to Continue, or Volume Down to Cance.
To get into Recovery Mode: Turn off your phone, then turn it on and hold down the Volume Up button. You will get some small text at the top left of the screen, and then whichever Recovery you have installed in the Recovery partition will run.
You use Download mode to flash using ODIN.
To get something into the Recovery partition, you can flash using ODIN, or if you are rooted, you can use an app like the TWRP Manager app, and some others.
Also, there isn't an official 2.8.7.0 TWRP. The latest is 2.8.4.0 which may be most/part of your issue.
Getting root is very easy on the SGH-M919, just use the CF-AutoRoot app. But, you don't need root to flash TWRP with ODIN. Also, almost every non-stock ROM will come pre-rooted. So, if you have flashed a CM rom, you are rooted. But, you may need to download SuperSU from the app store.
Rob
Click to expand...
Click to collapse

slungshot said:
Hi Rob, Thanks for the reply. My problem is I hold down the buttons but they no longer boot me into recovery, the android recovery screen flashes for a sec, then boots normally.
I may have found a workaround though, it seems I can now do a recovery option from the power down menu, and that boots me into TWRP. Not sure why the buttons no longer get me into the recovery console, but this may work.
Funny thing is I lost root after installing cm 12.1 while rooted. I think I may downgrade to kit kat because it seems like lollipop drains the battery much faster.
Click to expand...
Click to collapse
If TWRP 2.8.70 is not functioning correctly, then please try the last stable version: 2.8.4.0.
See the thread here: http://forum.xda-developers.com/showthread.php?t=2263001&page=61
I run 2.8.4.0, and the buttons work and TWRP Manager works, etc.
CM12 comes pre-rooted - all non-stock ROMs do. You may have lost the SuperSU app when you flashed, but that can be downloaded from the app store.
Rob

Thanks Rob. I figured out that I was still able to reboot into recovery without buttons so I just went that route. Where did you get the 4.4.4 rom? I can't find anything on the cyanogen site other than snapshot 4.4.2, which I installed last night trying to solve my problem of when someone calls they hear a wicked echo.
rlichtefeld said:
If TWRP 2.8.70 is not functioning correctly, then please try the last stable version: 2.8.4.0.
See the thread here: http://forum.xda-developers.com/showthread.php?t=2263001&page=61
I run 2.8.4.0, and the buttons work and TWRP Manager works, etc.
CM12 comes pre-rooted - all non-stock ROMs do. You may have lost the SuperSU app when you flashed, but that can be downloaded from the app store.
Rob
Click to expand...
Click to collapse

slungshot said:
Thanks Rob. I figured out that I was still able to reboot into recovery without buttons so I just went that route. Where did you get the 4.4.4 rom? I can't find anything on the cyanogen site other than snapshot 4.4.2, which I installed last night trying to solve my problem of when someone calls they hear a wicked echo.
Click to expand...
Click to collapse
SamMobile has all the Stock firmwares for all the Samsung phones. However, their downloads can be a little slow.
Luckily, ShinySide on this forum in the General Section has this thread with fast downloads:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Flashing 4.4.4 will get you the most recent firmware - boot, recovery, modem and ROM. So, you'll need to flash a recovery and CM Rom after that if you want to go back to CM. However, with CM you lose WiFi Calling. You could root the Stock and remove any apps you don't want, or freeze them with TitaniumBackup. That way you get the best of both worlds - stock, but only running the apps you want.
YMMV.
Rob

Custom ROM for OH1 bootloader SIII

Is the OH1 bootloader compatible with custom roms that require nd8?
I want to put Wicked S5 Xperience on my SIII but it says must have nd8 bootloader and I did the ota to OH1 and rerooted w/ twrp and supersu.

OH1 compatible with custom roms
aschubart said:
Is the OH1 bootloader compatible with custom roms that require nd8?
I want to put Wicked S5 Xperience on my SIII but it says must have nd8 bootloader and I did the ota to OH1 and rerooted w/ twrp and supersu.
Click to expand...
Click to collapse
Hey all,
Answered my own question. Successfully installed wicked s5 xperience 2.2 (wih requires nd8) without a hitch. basically I followed the step by step with exception to. I used twrp... wich they dont support. I did a dirty flash... worked fine but all my old settings were still there, So I did a Proper clean flash and all is good. Way better modem.... than OH1. I have signal and data in places I used to not get.
Hope this helps anyone else.

I have a question, how did you go about installing a custom ROM with OH1.
I can't seem to use Odin to install TWRP. It says success but when I try to 'adb reboot recovery', it just goes to the stock recovery. Any idea on how to install a custom recovery?

TheFatDemon said:
I have a question, how did you go about installing a custom ROM with OH1.
I can't seem to use Odin to install TWRP. It says success but when I try to 'adb reboot recovery', it just goes to the stock recovery. Any idea on how to install a custom recovery?
Click to expand...
Click to collapse
Did you
Hold power button to turn off your S3, after it turns off about 10 seconds later it will turn back on to the battery charging screen so before that quickly hold Volume+ and Home, to boot into recovery.
I got from http://forum.xda-developers.com/showthread.php?t=2787771
If odin says success it should boot to twrp.
Once I was in twrp I just installed my downloaded ROM. You probably will want to do a wipe first to have a clean flash.

aschubart said:
Did you
Hold power button to turn off your S3, after it turns off about 10 seconds later it will turn back on to the battery charging screen so before that quickly hold Volume+ and Home, to boot into recovery.
I got from http://forum.xda-developers.com/showthread.php?t=2787771
If odin says success it should boot to twrp.
Once I was in twrp I just installed my downloaded ROM. You probably will want to do a wipe first to have a clean flash.
Click to expand...
Click to collapse
I ended up having to do that. For some reason Odin wasn't kicking me into recovery so I had to boot into recovery myself. Another issue that I noticed was that TWRP couldn't root stock firmware. It would install SuperSU but wouldn't install the su binary. I ended up just installing AICP.
Thanks for the help.

TheFatDemon said:
I ended up having to do that. For some reason Odin wasn't kicking me into recovery so I had to boot into recovery myself. Another issue that I noticed was that TWRP couldn't root stock firmware. It would install SuperSU but wouldn't install the su binary. I ended up just installing AICP.
Thanks for the help.
Click to expand...
Click to collapse
Glad you got it going.. I haven't tried Ice Cold looks like a solid ROM though.

Roms
Is there any rom for the l710vpudoh1?

Hi...Please can you get an OH1 modem for me? My phone has no service and im running android 6.0.1

GS3 ATT Overwrites CWM, can I use this version of cfautoroot to root?

Hey guys,
Im not new to rooting and custom roms and all, but I never had something like this happen before. I'm on 4.4.2 on my i747 and I got the cwm from Clockworkmod.com and every time I flash the custom recovery with odin 3 my stock recovery overwrites cwm. Can I use the 4.0.4 version of cf autoroot to root my phone or will it brick?
Any help is appreciated, thanks again

Easiest way to root this phone is just flash supersu in custom recovery.
1) Download a recovery flashable supersu.zip to the phone storage.
2) Use Odin to flash custom recovery (consider using TWRP, CWM hasn't been developed in quite some time). Be sure to uncheck auto-reboot in Odin. Upon success do not reboot into system, unplug the USB cable and pull the battery.
3) Replace battery and boot straight into recovery. Hold vol up + home + power together and don't let go until you see "recovery booting" in little blue text in the upper left.
4) Make a backup in recovery, just in case things go wrong.
5) Flash the supersu.zip in custom recovery.
6) Reboot into system.
You might have to update the supersu binary and reboot a few times until it gets Knox properly disabled and everything settles. Once you're rooted the stock rom will stop overwriting your custom recovery every time you boot into it.
This phone is very brickable, but generally not when messing with recovery, rooting, or custom roms. The things that tend to result in hard bricks are messing with the bootloader and modem (keep them matched and don't ever downgrade), accidentally flashing a rom intended for i9300 (the other S3), or attempting to unlock the already not locked bootloader. Use caution in those areas and this is actually a pretty modder friendly phone (especially for a Samsung).

jason2678 said:
Easiest way to root this phone is just flash supersu in custom recovery.
1) Download a recovery flashable supersu.zip to the phone storage.
2) Use Odin to flash custom recovery (consider using TWRP, CWM hasn't been developed in quite some time). Be sure to uncheck auto-reboot in Odin. Upon success do not reboot into system, unplug the USB cable and pull the battery.
3) Replace battery and boot straight into recovery. Hold vol up + home + power together and don't let go until you see "recovery booting" in little blue text in the upper left.
4) Make a backup in recovery, just in case things go wrong.
5) Flash the supersu.zip in custom recovery.
6) Reboot into system.
You might have to update the supersu binary and reboot a few times until it gets Knox properly disabled and everything settles. Once you're rooted the stock rom will stop overwriting your custom recovery every time you boot into it.
This phone is very brickable, but generally not when messing with recovery, rooting, or custom roms. The things that tend to result in hard bricks are messing with the bootloader and modem (keep them matched and don't ever downgrade), accidentally flashing a rom intended for i9300 (the other S3), or attempting to unlock the already not locked bootloader. Use caution in those areas and this is actually a pretty modder friendly phone (especially for a Samsung).
Click to expand...
Click to collapse
Thanks. 2 more questions,
1) Do I use the .img.tar file [twrp-3.0.2-0-d2att.img.tar] or the .img file [twrp-3.0.2-0-d2att.img] here > https://dl.twrp.me/d2att/
2) I have the kot94h....NJ2 build number on my phone as I attempted root before, does this matter?

Ulti2x said:
Thanks. 2 more questions,
1) Do I use the .img.tar file [twrp-3.0.2-0-d2att.img.tar] or the .img file [twrp-3.0.2-0-d2att.img] here > https://dl.twrp.me/d2att/
2) I have the kot94h....NJ2 build number on my phone as I attempted root before, does this matter?
Click to expand...
Click to collapse
The twrp files that end in .tar are packaged to be flashed with Odin.
I never updated my i747 past NJ1, but I've not seen any discussion that NJ2 changed anything with respect to rooting on this phone. Just try the stable TWRP flashable supersu.zip.
My experience has been that even if rooting this way fails the worst thing that happens is your rom won't boot, so you pull the battery, boot back into recovery, restore a backup, and you're back up and running. I've never had rooting this way fail on the good old i747, only on newer phones with stock marshmallow.

jason2678 said:
The twrp files that end in .tar are packaged to be flashed with Odin.
I never updated my i747 past NJ1, but I've not seen any discussion that NJ2 changed anything with respect to rooting on this phone. Just try the stable TWRP flashable supersu.zip.
My experience has been that even if rooting this way fails the worst thing that happens is your rom won't boot, so you pull the battery, boot back into recovery, restore a backup, and you're back up and running. I've never had rooting this way fail on the good old i747, only on newer phones with stock marshmallow.
Click to expand...
Click to collapse
Thanks so much. I will do what you told me and report back. By the way, do all att s3's have unlocked bootloaders?, and how do you update the supersu binary?

Ulti2x said:
Thanks so much. I will do what you told me and report back. By the way, do all att s3's have unlocked bootloaders?, and how do you update the supersu binary?
Click to expand...
Click to collapse
The i747 and i747m were all unlocked by default. I'm pretty sure t999's are too.
Verizon's were locked. There was an unlock exploit for Verizon. Occasionally I read about someone trying it on an AT&T S3 and bricking it here.
I think supersu will pop up something on it's own if it is out of date, and retrieves what it needs from the Play store. It has been ages since I actually rooted stock on this phone. I vaguely remember Knox blocking root, supersu updating, rebooting a time or two then supersu eventually offering to disable Knox.

jason2678 said:
The i747 and i747m were all unlocked by default. I'm pretty sure t999's are too.
Verizon's were locked. There was an unlock exploit for Verizon. Occasionally I read about someone trying it on an AT&T S3 and bricking it here.
I think supersu will pop up something on it's own if it is out of date, and retrieves what it needs from the Play store. It has been ages since I actually rooted stock on this phone. I vaguely remember Knox blocking root, supersu updating, rebooting a time or two then supersu eventually offering to disable Knox.
Click to expand...
Click to collapse
I got backed up and successfully rooted. Thanks so much for the help. By the way, in logs and apps in supersu free it shows the loading circle forever, does that matter? I still have full root access to all apps.
EDIT: Turned out I needed a reboot to disable KNOX, you were right. Thanks for all your help jason!