Develop Bugs

[HOW-TO]OTA Update your Stock Rooted GSIII without wiping phone (ODIN TWRP 2.2.2.0)

I am putting together a quick guide on how to update your Stock ROM, Rooted, custom recovery T-Mo GSIII without having to wipe your phone.
You will need:
- Kies (If your phone has not prompted you to install the OTA yet, Kies will download and attempt to install it for you) (http://org.downloadcenter.samsung.c.../20120809103126135/Kies_2.3.2.12074_13_13.exe)
- ODIN 3.7 (http://forum.xda-developers.com/attachment.php?attachmentid=1270006&stc=1&d=1345396888)
- STOCK T-Mo GSIII recovery.img (I extracted this from the stock ODIN image for T-Mo) (http://forum.xda-developers.com/attachment.php?attachmentid=1269983&stc=1&d=1345396186)
- TWRP or CWM ODIN Flash-able recovery (CWM - http://forum.xda-developers.com/attachment.php?attachmentid=1269979&stc=1&d=1345396186 , TWRP - http://forum.xda-developers.com/attachment.php?attachmentid=1269980&stc=1&d=1345396186)
- Recovery flashable SuperSU root package (http://forum.xda-developers.com/attachment.php?attachmentid=1269984&stc=1&d=1345396186)
SO, place your phone in download mode (Vol Down + Home + Power), and via ODIN, flash the "Stock-Recovery-Image(Working T-Mobile T999).tar" image. ( This is putting the stock recovery back on your phone so the update can install).
When it reboots, either select yes to allow the OTA update to install (if your phone is already aware there is an update) on your phone, OR plug you phone into your PC and allow Kies to prompt you to update your firmware. Select yes and allow the OTA to install.
Once completed, your phone is updated without having to wipe, but you have lost root and customer recovery, so.....
Again, in Download mode, Flash either of the provided ODIN flash-able custom recoveries (TWRP, or CWM) I prefer TWRP
Once that is complete, you can reboot your phone into the new recovery (Vol UP + Home + Power)
Once in recovery, flash the SuperSU.zip package and Voila, all done, Triangle away and you in cool runnings.
Let me know if I need to clarify anything here. It makes sense to me, but then again, I fumbled through it to figure it out and extract the right recoveries and set permissions etc.....
Please hit the thanks button if this helped you in any way
Hans

Nice instructions, but I'm going to wait a few days. I'm want to see if the dev that did the flash and root without tripping the flash counter will do the same for the new firmware. I'm still not too keen on custom recoveries yet even though I backed up my IMEI, so I just want to be rooted. If not, I'll use your guide.:good:

Wildchld already released it.
http://forum.xda-developers.com/showthread.php?t=1838101
Sent from my SGH-T999 using xda app-developers app

DocHoliday77 said:
Wildchld already released it.
http://forum.xda-developers.com/showthread.php?t=1838101
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
But with Wildchild's it's a complete ROM (650-700MB), correct? Are you not wiping when you flash his?

Actually I'm not 100% that you need to do a full wipe, but I'm guessing you probably should. Depends on what's different. You can always nabdroid and give it a shot. I will later if I have time.
Anyway, I was more responding to the post above mine about stock with root than to the op. Sorry if shoulda been a little more clear on that.
Sent from my SGH-T999 using xda app-developers app

i might wait. finally got google now and google wallet working and i dont want to mess it up lol

RotaryXperiment7 said:
i might wait. finally got google now and google wallet working and i dont want to mess it up lol
Click to expand...
Click to collapse
What did you have to modify to get them working? Like I said before, I made this little method so you did not have to wipe your phone to get the OTA installed.
The only thing I could see that would cause the OTA to break wallet, or Google now would be that if you have to modify pieces in the /system/ directory that would be overwritten. The only thing I had to do after updating was re-flash my little installer for international boot image, re-remove Carrier IQ as it was added back, and revert the googlesearch.apk to the earlier backed up version (functioning unified search) with titanium. Outside of that I run a pretty tight ship as far as system modifications go outside of root and root privileged programs.

had to edit build pro for wallet

Thanks op, this worked great for me! Updated and rooted again...
Sent from my rooted T-Mo SGS3

I tried several times but couldent unroot my phone. I even tried through the root kit by mskip. I think the problem may be that I got my phone unlocked, not using an unlock code but some other method (all I know about this method is that my phone says"restricted access" for a few seconds upon restarting.)
Any suggestions on how to unroot? Also, if I unroot, will I loose the unlock?

pappuhathi said:
I tried several times but couldent unroot my phone. I even tried through the root kit by mskip. I think the problem may be that I got my phone unlocked, not using an unlock code but some other method (all I know about this method is that my phone says"restricted access" for a few seconds upon restarting.)
Any suggestions on how to unroot? Also, if I unroot, will I loose the unlock?
Click to expand...
Click to collapse
I think the best method to unroot your phone will be to ODIN it back to the stock T-Mobile image. (Overwrites EVERYTHING, probably your unlock as well).
http://forum.xda-developers.com/showthread.php?t=1737855
Above is the link to the stock image.
Apologies, in general, but I feel you may have the wrong thread if your looking to unroot your phone. That is off topic on what is being discussed here.

has anyone tried this and kept google wallet and google now working? Any troubles?
I'm wanting to update but I'm rooted withthose two apps finally up and running.

arts711 said:
has anyone tried this and kept google wallet and google now working? Any troubles?
I'm wanting to update but I'm rooted withthose two apps finally up and running.
Click to expand...
Click to collapse
I would assume the build.prop file will be overwritten. So its possible you would need to modify after updating. May not be any way around it.
If you want to test for others, make nandroid backup , upgrade and test. If it works, update us. If not, update us

cybrnook said:
I would assume the build.prop file will be overwritten. So its possible you would need to modify after updating. May not be any way around it.
If you want to test for others, make nandroid backup , upgrade and test. If it works, update us. If not, update us
Click to expand...
Click to collapse
So (in case this all doesn't work out) to restore via nandroid, just root and apply right?

cybrnook said:
I would assume the build.prop file will be overwritten. So its possible you would need to modify after updating. May not be any way around it.
If you want to test for others, make nandroid backup , upgrade and test. If it works, update us. If not, update us
Click to expand...
Click to collapse
You are correct about build.prop being overwritten.
Sent from my rooted T-Mo SGS3.
If I've helped you, be sure to use the thanks button!

arts711 said:
So (in case this all doesn't work out) to restore via nandroid, just root and apply right?
Click to expand...
Click to collapse
Well if it doesn't work (Which I think it won't), you don't need to worry about restoring root. You just need to flash a custom recovery to revert your nandroid backup. Your root and customization will come back with that.
But with some of the added features that come with the update, I would say don't look back. Upgrade to the latest, then reapply your customization to get wallet and all working again.
IF you have to revert your nandroid back, make sure to do a factory wipe before you revert to your backup.

thanks! i'll give it a shot this weekend once i get more time.

I've used two different versions of Odin and two different T-Mobile stock recoveries (other one is here), and I can't get stock recovery to replace CWM on my GS3. Odin reports that the flash is successful, but when it reboots, ROM Manager still shows me as having latest CWM Touch, and the T-Mo update fails. I'm attempting the update via Kies right now, but I anticipate failure due to CWM still being installed as recovery.
-- I have Cerberus anti-theft installed, but I don't see anything about protecting recovery.
-- I have Busybox installed, but that shouldn't affect recovery.
Any ideas?
EDIT: Interestingly enough, where the OTA update failed, the Kies update went smooth as silk. Now to re-root and remove bloatware!

RaymondPJR said:
Nice instructions, but I'm going to wait a few days. I'm want to see if the dev that did the flash and root without tripping the flash counter will do the same for the new firmware. I'm still not too keen on custom recoveries yet even though I backed up my IMEI, so I just want to be rooted. If not, I'll use your guide.:good:
Click to expand...
Click to collapse
Are you referring to MrRobinson's rooting method? I'm waiting for it too.
Sent from my SGH-T999 using XDA Premium App

Im unable to update. I used Odin to flash the stock recovery, then downloaded the update via settings-> about device-> software update. Installing reboots the phone but then fails and reverts to current state. I can't update through kies also bc it just says "connecting", no errors. I tried uninstalling/reinstalling drivers but kies never completes connecting. Any help?
Sent from my SGH-T999 using xda app-developers app
EDIT: I uninstalled all my samsung drivers and Kies from "Programs and Features" in win7, deleted Samsung folders from HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER. Reinstalled Kies and connected my phone to install the drivers. Kies was stuck in the connecting loop still, so I unmounted my sd card, turned on USB debugging and Kies finally connected and asked to upgrade. Upgrading at this moment.

[GUIDE] how to root Sph-L710/L710T S3 4.4.2 (updated as of 8/19/2015)

I'm sorry i had the wrong links and because of this i had miss information. So i formally apologize by updating with the proper links.
this first method doesn't work with the Sph-L710T or the Sph-L710 on NJ2/NJ3
First method: You can root the stock 4.4.2 ND8/NDC:laugh:
1st. Make sure your on 4.4.2 ND8 or NDC
2nd. Download Towel Root
3rd. Place Towel Root in sdcard or internal storage
4th. With any file manager find and install Towel Root
5th. Open Towel Root and well root
6th. Go to play store and download https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en and also https://play.google.com/store/apps/details?id=stericson.busybox&hl=en let super user update the binary
7th. Flash any recovery you want {personally i went with PhilZ Touch (this was before PhilZ had a root Option)}
8th. Enjoy your rooted stock 4.4.2 ND8/NDC
Down below is one more way too root Stock ND8/NDC/NJ2/NJ3 or NF4/OA3 (L710T) and basically any other update
(link to the almighty ODIN)
Second Method: mostly recommended
1st. Odin flash TWRP
2nd. In Odin choose PDA, PA or AP then select the TWRP Tar you just downloaded
3rd. Make sure Auto reboot is unchecked (also at this time your s3 should be in download mode)
4th. Hit start and let Odin let it finish!!
5th. 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
6th. now your in TWRP
7th. so to root your stock rom with TWRP flash the following file SuperSU.zip by Chain fire (pro tip. Install any other custom recovery the same way I did for TWRP above if it is in .tar format)
and here is Philz recovery for the D2Lte 6.48.4 ( which you must flash in TWRP)
and here is TWRP that was made specifically for the D2Rephersher/triband/L710T TWRP (which you must flash in a recovery)
Third method Most recent.
Hidyman said:
This is in reference to Samsung Galaxy S3 for Boost Mobile SPH-L710.
Just want to let anyone out there that updated their Boost S3 to L710VPUC0J1 know that you can still root and/or ROM your phone.
Use the instructions to (use Odin to) update the recovery to TWRP first (in the second set of instructions). I had trouble trying to go right to PhilZ Recovery (which I believe is based off of ClockWorkMod). I Had to do the TWRP (twrp-2.8.7.0-d2spr.img.tar) first.
It was the only way to get it to actually accept the recovery, not sure why, maybe because the latest Samsung firmware fixed an exploit or two.
This is an older phone, but it is still a viable one.
I hope this helps someone out there.
It took me a while to figure this quandary out.
As always this WILL flag KNOX, but I'm sure this won't be an issue at this date and time (8/2016).
Click to expand...
Click to collapse

work on ND8 rom? sprint phone?

Tekone said:
work on ND8 rom? sprint phone?
Click to expand...
Click to collapse
i want to say yes but towel root does come with a warning that it might brick your device.....but i want to say yes since most things that can be done to the ND8 can be done to the NDC and also in reverse order.....so try it and report back it will be good to know if it works on both bootloaders

Sprint S3 Android 4.4.2 ND8-It works!
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!

oops
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.

henhun said:
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.
Click to expand...
Click to collapse
ND8 or NDC? have you tried updating your profile/PRL?

6th_Hokage said:
ND8 or NDC? have you tried updating your profile/PRL?
Click to expand...
Click to collapse
Ya know. People keep talking about ND8 and ND___. I have no idea what that means. I know I should be embarrassed.
UPDATE: FIGURED IT OUT, BASEBAND VERSION. GOTCHA. IT IS NDC.
I was JUST coming back to update my post. I DID update the PRL and restarted my phone. That seems to have done the trick. Thank GOD I got my data connection back!! It worked. Even though I found the info somewhere else, thank you so much for the quick reply. PRL update fixes the problem. You're awesome.

I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app

jbnorton0524 said:
I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
many users of basically the same phone report different things with every root method out there. If it worked for you that's great tell other users what you did for it to work and if it didn't work, then ask for help and you will get help; some people don't have success with any method while others do with all of the methods.....my phone falls under every method.....

Successful Towelroot on VM Galaxy S3 4.4.2.NDC
6th_Hokage said:
you can root the stock 4.4.2
first step make sure your on 4.4.2
second step download Towel Root
third step place Towel Root in sdcard or internal storage
fourth step with any file manager find and install Towel Root
fifth step root
sixth step go to play store and download Superuser (Chainfire) and also Busy Box (Stericson) let super user update the binary
seventh step flash any recovery you want personally i went with Philliz Touch
eighth step if you want flash a custom rom now if not enjoy your rooted stock 4.4.2
Click to expand...
Click to collapse
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is usafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave

dave260 said:
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is unsafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave
Click to expand...
Click to collapse
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the binary (<---completely forgot to fix that) you must hit the option normal not TWRP/CWM

churninern said:
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!
Click to expand...
Click to collapse
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.

Darkangels6sic6 said:
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.
Click to expand...
Click to collapse
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all

Knox Counter and "Device Status"
6th_Hokage said:
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the recovery you must hit the option normal not TWRP/CWM
Click to expand...
Click to collapse
Thanks for your response. I may be over thinking these indicators. All I did was Towelroot, successfully. On the phone, the "About Device, Status" now says CUSTOM (was "Official"). The Knox counter according to app "Phone Info" shows Knox Counter at 0x0. As you said, since the counter is not tripped, should be no problem on warranty. So then Device Status CUSTOM is not a problem? I'm not really worried about warranty at this point, but I think I'll hold off further mods for another 6 moths.
Thanks again for your help!

6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
Thanks. I tried the md8 and mk3 "mk3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all.
I'm guessing maybe I should install twrp. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most md8 Roms want you to odin or flash an md8 base.

Darkangels6sic6 said:
Thanks. I tried the ND8 and MK3 "MK3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all
I'm guessing maybe I should install TWRP. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most ND8 Roms want you to Odin or flash an md8 base.
Click to expand...
Click to collapse
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be

6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
6th_Hokage said:
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be
Click to expand...
Click to collapse
I was afraid you would say that.

Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!

strangelady said:
Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!
Click to expand...
Click to collapse
your welcome strangelady and if you want check out the links in my signature area for other cool stuff

added two more t=root methods

Trying to root, have no idea what I'm doing.

Alright so I was rooted, but now there's been at least one new version of Android, so I need to do it again and update. I am confused as to how this whole thing works. I used to have an iPod touch which I jailbroke, and you could update the firmware simply by jailbreaking with a jailbroken version of the newer OS. Does Android work in a similar fashion with rooting, in which when you flash the ROM (am I saying this right?), it is a different Android version? So can I just find a ROM that's 4.3 to update, or should I update to 4.3 over the air and then root again? I actually already did the OTA update because it was really bothering me and currently I don't even use root features frequently. Anyway, the no-flash trip link in the how to root section says 4.1.1, which I assume means Android 4.1.1, and I don't want this. What can I do?
If I get a current version of a custom ROM, LiquidSmooth or something, will that update my Android version?
I'm sorry if I'm making zero sense right now, or if this is in entirely the wrong section. I'm trying my best here.

You're on stock ? If so what version,4.3?

FYI this isn't the right place to post this. But check out THIS thread about Preparing to flash an ND8 (kitkat) rom. It is short, very informative and has important links to other things you may need. Good luck!
~CTP

Nexus11 said:
You're on stock ? If so what version,4.3?
Click to expand...
Click to collapse
Indeed.

Azhai said:
Indeed.
Click to expand...
Click to collapse
I will help U but you take full responsibility for anything that may happen to your device in the process.
It seems like U are still rooted, but but just on MK3 still. This will upgrade U to ND8
Here goes:
#1 Install Odin on your PC, run the program. (Link to Odin 3.07. LINK for ODINClick link and it will automatically download to system) Extract from ZIP
#2 Load the ND8 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (leave check in the Auto-Reboot and F-Reset)
#3 Then after that is successful run CF Auto Root LINK CF-AUTO ROOT This down load must be extracted and U will see Odin application in there too along with CF-Auto tar
#3b (I didn't do this because I don't really care, but if U want) get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
#4 Load your phone into Download Mode one last time and then put whatever recovery you have (I use Philz, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. U will then be rooted and custom recovery.. U can stay there and set up phone or flash a custom ROM. I would do a nandroid back-up in philz first before U flash a new ROM though.
Link to PhilZ 6.416 Tar DIRECT LINK I use this one because it WORKS with no issues
or U can go here and get other versions of Philz. LINK
This guide was originally posted by Bilgerryan (below) and I augmented a few things and added links so U wouldn't have to search and search.
Quote:
Originally Posted by bilgerryan
Install Odin on your PC, run the program. Load the ND8 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol. Load your phone into Download Mode one last time and then put whatever recovery you have (I use Philz, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2738533&page=51

Needs to be moved
Glad that answers are coming in, but this thread needs to be moved; @KennyG123, can you assist?

What in the blue hell????!! A question in Development?!!!
Please read forum rules before posting. Rule 15 will help you decide where your post needs to go.
Thank you for your cooperation
Thread moved

Thanks for the move. Reading is hard.
So can someone just clear up the whole version thing for me? I attempted to do the 4.4 OTA update that showed up, and it seems to have worked in the sense that the notification went away, but my version is the same (4.3) and I seem to still be rooted. I guess I really don't understand any of the rooting process. I know I've used Odin and stuff but I really don't know what any of it does. Is there already a thread somewhere that explains what all of this stuff actually does? I mean, updating and staying rooted can't be that hard to do.

Azhai said:
Thanks for the move. Reading is hard.
So can someone just clear up the whole version thing for me? I attempted to do the 4.4 OTA update that showed up, and it seems to have worked in the sense that the notification went away, but my version is the same (4.3) and I seem to still be rooted. I guess I really don't understand any of the rooting process. I know I've used Odin and stuff but I really don't know what any of it does. Is there already a thread somewhere that explains what all of this stuff actually does? I mean, updating and staying rooted can't be that hard to do.
Click to expand...
Click to collapse
Attempts to take an OTA on a rooted phone should fail. There is already a thread, chad the pathfinder gave u the link...
Sent from my SPH-L710, using Tapatalk 2 Cyan. ND8. Rooted and rom'd with WICKED-X (HELLS YA!)

How to root after you take the OG5 OTA update

Some tips for those who already took the OG5 OTA update and want root (will be obvious to most of you, and most of this has already been covered in other posts, but some might benefit from this guide with download links included):
1. Copy the BeastMode kernel zip to your phone or SD card.
2. Start Odin3 v3.10.6
3. Place the TWRP tar in the AP slot
4. Uncheck Auto Reboot in the options tab
5. Flash TWRP -- when it's finished flashing, disconnect USB and pull the battery for 10 seconds (on my phone, if I put the battery in too soon, it boots without pressing the power key)
6. Put the battery back in and boot to TWRP
7. Install the modified kernel zip you copied in step 1, and reboot.
8. Since you're in TWRP, might as well clear the cache.
At this point, there are a number of ways to get SuperSU on your phone. My TWRP asked me if I wanted it to install SuperSU, I said yes, but I already had SuperSU installed on my phone, anyway.
You can also use TWRP to install the SuperSU zip.
My phone complained about "KNOX has unfortunately stopped", so I just used Titanium to freeze all the KNOX apps, which cured that.
Be very patient the first time you run apps that request root. It will pop up the "grant" dialog eventually, but sometimes it's slow to do that after a boot.
NOTES: Some users are reporting that TWRP won't load. It may have to do with tripping that reactivation lock with Odin. Once done, it's possible TWRP can't deal with it. So you may be able to get around that by using Odin to install CWM recovery instead of TWRP.
Also, try rebooting recovery again after the flash to make sure the root prompt is clear. If it is booting the system, go into security and disable the reactivation lock.
Still getting the business about slow to wake or launcher not responding? Try adding the line below to end of your build.prop but have one empty line at bottom with no added spaces to the end this line:
ro.HOME_APP_ADJ=1
(thanks to samep for the added info in NOTES)

Will this process work on the Galaxy s5 with og5 5.11
Will this process work on the Galaxy s5 with og5 5.11, I no this is the note section but it appears to be the same build number in the same manufacturer is it possible for someone to report this kernel to the galaxy s5 and root it that way? What exactly is happening here on the note for those of you that wouldn't work on the s5?

Dmary said:
Will this process work on the Galaxy s5 with og5 5.11, I no this is the note section but it appears to be the same build number in the same manufacturer is it possible for someone to report this kernel to the galaxy s5 and root it that way? What exactly is happening here on the note for those of you that wouldn't work on the s5?
Click to expand...
Click to collapse
PM sent.
Sent from my SM-N910P using Tapatalk

So, its been about a year since I rooted a phone, but I feel like I'm missing something at the beginning of the instructions. In the video
https://www.youtube.com/watch?t=32&v=k2oOvf5tOCY
it goes over the auto root process, but that hasn't been updated. Is that something I need to run first anyway? Wouldn't it not work due to the mismatch of android version?
Oh, never mind. It froze at the TWRP screen, but a restart fixed that.

I would like to know if it's possible on the S5 as well...G900V...Everywhere i've read says it's not.
samep said:
PM sent.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse

When I try to flash twrp, odin says failed. Any suggestions?

Thanks so much for this guide! Just got a new Note 4 and I'm about to root as well. Is TWRP still giving issues installing? Should I just go with CMW recovery? any other tips would be greatly appreciated. Just want to make sure I cover all bases before I begin...

Newbie_from_NJ said:
Thanks so much for this guide! Just got a new Note 4 and I'm about to root as well. Is TWRP still giving issues installing? Should I just go with CMW recovery? any other tips would be greatly appreciated. Just want to make sure I cover all bases before I begin...
Click to expand...
Click to collapse
TWRP is fine for most. Steps 4, 5 and 6 are important to assure TWRP recovery sticks.
If you decide to flash a custom ROM and get a binary failure, reboot recovery and try again.
Sent from my SM-N910P using Tapatalk

samep said:
Steps 4, 5 and 6 are important to assure TWRP recovery sticks.
Click to expand...
Click to collapse
Step 6, in order to do this, i will need to press button combinations on the phone, correct?
Do you happen to know them? If not, I'm sure Google to the rescue.
Sent from my SM-N910P using Tapatalk

Newbie_from_NJ said:
Step 6, in order to do this, i will need to press button combinations on the phone, correct?
Do you happen to know them? If not, I'm sure Google to the rescue.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
From power off, Vol+, Home + Power.
Sent from my SM-N910P using Tapatalk

I am also curious about whether this would work on a G900V.

Anyone try this on their 920v????

samep said:
PM sent.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Could you please reply about G900V? I would greatly appreciate it.

AcidBurn22 said:
Could you please reply about G900V? I would greatly appreciate it.
Click to expand...
Click to collapse
I sent the PM to not clutter this thread with off-topic discussion.
Sorry, I don't have this phone, nor have I rooted one.
If you need help or don't know where to start, I'd suggest reading thread below before asking in thread:
http://forum.xda-developers.com/showpost.php?p=61688768&postcount=1
Reading through the OP's threads, the same thing started at OE1 update that started here, you can no longer downgrade in Odin once taking this one and later updates; it progressively worsens. Regarding your carrier, it appears that root prior to OG5 update is a prerequisite as well as steps to keep root in the update process (those do not apply here). But I don't claim to know any more about it than you so read, search and ask in the appropriate thread. Best wishes for success; perhaps it's not as grim as I describe it. I only researched a few minutes, following closed threads to links to next thread, starting here:
http://forum.xda-developers.com/showpost.php?p=61682294&postcount=242
If you have a choice, don't take the OE1 update until you're rooted and clear on how to keep root through updates. But again, I'm not claiming to know any more than yourself, possibly less with the effort I gave.
Anyone else finding this through search, please keep this thread on topic. Refer to your specific thread regarding phone model and carrier. Thanks.
Sent from my SM-N910P using Tapatalk

DaggettBeaver said:
Some tips for those who already took the OG5 OTA update and want root (will be obvious to most of you, and most of this has already been covered in other posts, but some might benefit from this guide with download links included):
1. Copy the BeastMode kernel zip to your phone or SD card.
2. Start Odin3 v3.10.6
3. Place the TWRP tar in the AP slot
4. Uncheck Auto Reboot in the options tab
5. Flash TWRP -- when it's finished flashing, disconnect USB and pull the battery for 10 seconds (on my phone, if I put the battery in too soon, it boots without pressing the power key)
6. Put the battery back in and boot to TWRP
7. Install the modified kernel zip you copied in step 1, and reboot.
8. Since you're in TWRP, might as well clear the cache.
At this point, there are a number of ways to get SuperSU on your phone. My TWRP asked me if I wanted it to install SuperSU, I said yes, but I already had SuperSU installed on my phone, anyway.
You can also use TWRP to install the SuperSU zip.
My phone complained about "KNOX has unfortunately stopped", so I just used Titanium to freeze all the KNOX apps, which cured that.
Be very patient the first time you run apps that request root. It will pop up the "grant" dialog eventually, but sometimes it's slow to do that after a boot.
NOTES: Some users are reporting that TWRP won't load. It may have to do with tripping that reactivation lock with Odin. Once done, it's possible TWRP can't deal with it. So you may be able to get around that by using Odin to install CWM recovery instead of TWRP.
Also, try rebooting recovery again after the flash to make sure the root prompt is clear. If it is booting the system, go into security and disable the reactivation lock.
Still getting the business about slow to wake or launcher not responding? Try adding the line below to end of your build.prop but have one empty line at bottom with no added spaces to the end this line:
ro.HOME_APP_ADJ=1
(thanks to samep for the added info in NOTES)
Click to expand...
Click to collapse
Thanks for this. I have Sprint SM-N910P 5.1.1 and want to root to debloat it.
I have rooted my previous phones. Where do I get the OG5 so I can proceed in rooting my Note 4?
Thanks in advance.:good:

Reivaj1803 said:
Thanks for this. I have Sprint SM-N910P 5.1.1 and want to root to debloat it.
I have rooted my previous phones. Where do I get the OG5 so I can proceed in rooting my Note 4?
Thanks in advance.:good:
Click to expand...
Click to collapse
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk

samep said:
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I wasn't aware of the latest update, thanks for the heads up.
I have never tried Chainfire auto root. I found Chainfire post http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
I'll try this route.
Thank you sir, greatly appreciate it. ???

samep said:
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have an issue I'm hoping you could help me with.
I posted this in the Chainfire thread, but have not received any response.
I rooted my Sprint Note 4 SM-N910P via Chainfire Auto Root. With the exception of 1 issue of being stuck in the bootloader where I had to remove the battery and then boot into recovery manually, all went well.
Once it was done and rebooted I got a message during boot, 'Set Warranty Bit: Kernel'
I have SM-N910P 5.1.1 and SU with Titaniun Backup Pro. Reason was to get rid of the bloatware.
I have un-installed the bloatware via TB and the confirmations show they have been deleted with strikethrough but no sooner that I go to check top confirm, they are active with the strikethrough removed.
I also get, out of the blue, prompt to download massive amounts of bloatware I never had to begin with "Sprint Default Configuration: Select to Install New Sprint Default Apps". At first thought it was an update so i downloaded it and along came uber, nba, stock care racing, sprint fun app and sprint international app and a few others.
I tried the same with those, to un-install via TB, and while some have been un-installed, the remaining have not and I get the message prompt to install again.
Anyone idea how I got this and how I can get rid of it?

Reivaj1803 said:
I have an issue I'm hoping you could help me with.
I posted this in the Chainfire thread, but have not received any response.
I rooted my Sprint Note 4 SM-N910P via Chainfire Auto Root. With the exception of 1 issue of being stuck in the bootloader where I had to remove the battery and then boot into recovery manually, all went well.
Once it was done and rebooted I got a message during boot, 'Set Warranty Bit: Kernel'
I have SM-N910P 5.1.1 and SU with Titaniun Backup Pro. Reason was to get rid of the bloatware.
I have un-installed the bloatware via TB and the confirmations show they have been deleted with strikethrough but no sooner that I go to check top confirm, they are active with the strikethrough removed.
I also get, out of the blue, prompt to download massive amounts of bloatware I never had to begin with "Sprint Default Configuration: Select to Install New Sprint Default Apps". At first thought it was an update so i downloaded it and along came uber, nba, stock care racing, sprint fun app and sprint international app and a few others.
I tried the same with those, to un-install via TB, and while some have been un-installed, the remaining have not and I get the message prompt to install again.
Anyone idea how I got this and how I can get rid of it?
Click to expand...
Click to collapse
I believe it was determined that titanium wasn't working correctly due to lack of busybox. OsmOsis wrote a nice script to install busybox that works for systemless root as well as the traditional system root method.
Goto the link below and look for his link to busybox installer and install that in recovery.http://forum.xda-developers.com/showpost.php?p=40409356&postcount=1
If you don't want the custom recovery, use Stericson Busybox in Google Play, instead.
The Sprint apps are likely getting pushed by a root folder /preload You can't freeze this with titanium and how you deal with that may leave indicators to detect that you modified system. Mounting to delete may trigger that and make it not possible to full un-root to take OTA for update. But you could just freeze the preloaded applications after they update. If you use the application manager in Settings, you get the option to remove updates and disable some apps but not all apps. I'm not sure how this applies to preload.
If OTA capability is not of importance, you can consider taking further steps to get a better kernel, make root more stable and modify system and read only partitions for more customization like deleting the preload directory.
So the solution would depend on your preferences. Retain OTA capability with strict SELinux Enforcing mode or go for more customization, not caring for OTA updates but waiting for update stock tar and electing a more stable root with custom kernel? Which would you prefer?
Sent from my SM-N910P using Tapatalk

samep said:
I believe it was determined that titanium wasn't working correctly due to lack of busybox. OsmOsis wrote a nice script to install busybox that works for systemless root as well as the traditional system root method.
Goto the link below and look for his link to busybox installer and install that in recovery.http://forum.xda-developers.com/showpost.php?p=40409356&postcount=1
If you don't want the custom recovery, use Stericson Busybox in Google Play, instead.
The Sprint apps are likely getting pushed by a root folder /preload You can't freeze this with titanium and how you deal with that may leave indicators to detect that you modified system. Mounting to delete may trigger that and make it not possible to full un-root to take OTA for update. But you could just freeze the preloaded applications after they update. If you use the application manager in Settings, you get the option to remove updates and disable some apps but not all apps. I'm not sure how this applies to preload.
If OTA capability is not of importance, you can consider taking further steps to get a better kernel, make root more stable and modify system and read only partitions for more customization like deleting the preload directory.
So the solution would depend on your preferences. Retain OTA capability with strict SELinux Enforcing mode or go for more customization, not caring for OTA updates but waiting for update stock tar and electing a more stable root with custom kernel? Which would you prefer?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I actually did remove and disabled most the apps that I was able to. The rest there were not options, other than root.
My preference was to root, maintain OTA capabilities and remove the bloatware.
What option/s would best suit that preference?

Phone going off and on after trying to root

Hello
Today i tried to root my Note 4 but something went wrong i think and now it only goes on, shows samsung logo, sprint logo, make a sound and goes off and repeat.
During rooting this also came so went to internet for help there they said: untick auto reboot on odin, remove cabel, remove battery, go to home+power+volume up. I did alls of this but phone still not working.
Any one here that can help me?

Teted said:
Hello
Today i tried to root my Note 4 but something went wrong i think and now it only goes on, shows samsung logo, sprint logo, make a sound and goes off and repeat.
During rooting this also came so went to internet for help there they said: untick auto reboot on odin, remove cabel, remove battery, go to home+power+volume up. I did alls of this but phone still not working.
Any one here that can help me?
Click to expand...
Click to collapse
Flash one of the prerooted roms in this thread:
http://forum.xda-developers.com/showthread.php?t=2956667
Read the OP carefully and choose one of the three versions there.
Most use the Hybrid X 3.0 version.
As far as the odin procedure you mentioned, that's for odining twrp custom recovery and it works.

^_yep_^
And if you're wondering what's up with the stock root you attempted, if you took the OG5 update, you need to flash SuperSU zip and a Touchwiz-Android 5.1.1 custom kernel for Sprint Note 4 in recovery prior to boot for the root exploit. The older root tutorials no longer apply; also, they may likely fail to warn you that you cannot flash older stock tars if you updated past OB7.
Sent from my SM-N910P using Tapatalk

jhill110 said:
Flash one of the prerooted roms in this thread:
http://forum.xda-developers.com/showthread.php?t=2956667
Read the OP carefully and choose one of the three versions there.
Most use the Hybrid X 3.0 version.
As far as the odin procedure you mentioned, that's for odining twrp custom recovery and it works.
Click to expand...
Click to collapse
I will try this and report if any problems occur.
Edit:
I tryed what jhill110 said me to do and now i'm using my rooted phone with no problems.