Related
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.
I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk
dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
Click to expand...
Click to collapse
Thanks! I'll give that a shot. But a question before I do something really dumb. Where does this recovery tar file go in odin? PDA?
Yep always PDA
Sent from my SM-P900 using Tapatalk
Worked! I now have rooted KOT49H.T900UEUAND4.
Good stuff
Sent from my SM-P900 using Tapatalk
OK. Here comes the "but". It turns out that I cannot connect over SSL. Wifi works, I have an IP, I can brows non-secure websites. But I cannlt connect to anything https, nor will apps like Google Play connect.
Do we think this is related, or should i start a new thread?
UPDATE: I wiped data and now all is fine. The really interesting thing that I've noticed is that the Device Status is showing as "Official".
JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?
gbr357 said:
JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?
Click to expand...
Click to collapse
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.
Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?
gbr357 said:
Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?
Click to expand...
Click to collapse
I think I would have done that if I had known there was a B5 recovery image available. The guidance that I was given was to flash the B3 image from the P900. And that *did* work fine. Before there was a root flash for the T900, people were using the P900 root with success. Don't know that there is much difference. In the end, either way, you will end up with a B5 recovery image, as that is what Chainfire included in the T900 root file.
Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.
gbr357 said:
Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.
Click to expand...
Click to collapse
Which file from Chainfire did you flash? Was it CF-Auto-Root-v2wifi-v2wifixx-smt900.zip? For me, flashing that after OTAing to ND4 left me unable to boot. Maybe that got fixed in the past couple of day?
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Well. technically I wasn't rooted either. I completely removed root with SuperSU.Is your recovery NB5?
JJMT said:
I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?
Click to expand...
Click to collapse
That's the problem I've been writing about for a week. The new OTA update (t900ueuand4) doesn't work with auto-root and crashes exactly where yours did.
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Can you give me the link for the new chainfire file that must have been re-written in the last 2 days
---------- Post added at 11:32 PM ---------- Previous post was at 11:28 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Just re-downloaded the chainfire file and it's identical to the file I got 10 days ago dated May 10th. If you had success flashing it with the firmware t900ueuand4 installed at the time of rooting, then I'll give it a shot too.
JJMT said:
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.
Click to expand...
Click to collapse
All I had to do, was stop after 3. Didn't require a factory reset. Everything is great
The same here. Used the Note 12 recovery mod to unbrick the tablet.
Flashed the CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5 and it works. :good:
Now oor Samsung tablet pro 12.2 is rooted.
dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I ran into a similar issue except my device came up to an error regarding firmware upgrade failed, use kies to recover. I could not get this to work with kies 3. Searching the threads, I found your post. Worked beautifully. The failed attempt did trip Knox. Not sure I care.
Thanks!
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
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 NK2 / Fix boot loop after NE2 to NK2 update
I've gotten a lot of question about rooting the Sprint Samsung Galaxy Note II from people on NK2. As we know, the NK2 update has some anti-root measures in place that have caused confusion. Some people are just rooting for the first time after receiving the NK2 update and some were already rooted on NE2 and lost root or soft bricked after taking the NK2 update. First, I'll show how to root NK2 if you're already running stock NK2. The instructions for those who soft bricked after taking the NK2 update from rooted NE2 will be listed second.
Warning #1: Rooting your device will void your warranty and your insurance.
Warning #2: I'm not responsible for your device. If you want to root it, you understand that there are risks involved. If you have questions then you should ask before proceeding or don't do it.
Instructions for rooting stock NK2.
01. Review the warnings above.
02. Charge your device to at least 60%
03. Have your device, a good micro USB cable, and your Windows PC ready.
04. Create a folder on your desktop and and name it "L900 ROOT". Download the following files into it:
file Sprint Samsung Galaxy Note II drivers for Windows.
file Odin 1.85. You will need to unzip this file using 7zip or UnRAR.
file TWRP recovery
file SuperSU (donation is recommended)
05. Install the Note II drivers on your PC.
06. Move the SuperSU file onto the root of your external SD card.
07. Power off your device.
08. Put your device into download mode by pressing and holding volume down+home+power. When the warning screen appears, press volume up. A screen saying, "Downloading...Do not turn off target" will appear. This is download mode.
09. Right click on Odin and run as administrator.
10. Connect your device to your PC. The ID:COM box will highlight. If the ID:COM box doesn't highlight, then see the troubleshooting below.
11. Uncheck Auto Reboot and F Reset Time. Repartition should also be unchecked.
12. Click the PDA button. This will prompt you to select a file.
13. Select the openrecovery-twrp-x.x.x.x-toltesrp file from your L900 ROOT folder.
14. Click Start.
15. When Odin completes flashing TWRP it will say, "PASS". This may take several minutes. If it takes more than ten minutes see troubleshooting below.
16. Disconnect your device from your PC. Your device will still be on the screen saying, "Downloading...Do not turn off target". You will ignore this warning and go to step 17.
17. Remove and then replace the battery in your device.
18. Boot into TWRP recovery by pressing and holding volume up+home+power until "Teamwin" appears.
19. Tap "Install".
20. Select the UPDATE-SuperSU-vX.XX.zip file.
21. Swipe to confirm flash. This will flash SuperSU to your device.
22. Reboot System. Your device will reboot.
23. You're now rooted running NK2. Sign into Google and your Samsung account. You can install Root Checker and run it to confirm root. Enjoy.
Instructions for soft bricked after taking NK2 from rooted NE2.
WARNING: If you're stuck in a boot loop or stuck at the Samsung logo then remove and replace your battery. Make sure your device is at least 60% charged before following these instructions.
01. Create a folder on your desktop and and name it "L900 ROOT". Download the following files into it:
file Sprint Samsung Galaxy Note II drivers for Windows.
file Odin 1.85. You will need to unzip this file using 7zip or UnRAR.
file TWRP recovery
file SuperSU (donation is recommended)
file Stock NE2 firmware. You will need to unzip this file using 7zip or UnRAR.
02. Install the Note II drivers on your PC.
03. Put your device into download mode by pressing and holding volume down+home+power. When the warning screen appears, press volume up. A screen saying, "Downloading...Do not turn off target" will appear. This is download mode.
04. Right click on Odin and run as administrator.
05. Connect your device to your PC. The ID:COM box will highlight. If the ID:COM box doesn't highlight, then see the troubleshooting below.
06. Uncheck Repartition. Auto Reboot and F Reset Time should be checked.
07. Click the PDA button. This will prompt you to select a file.
08. Select the L900VPUCNE2_L900SPTCNE2_SPR file.
09. Click Start. Odin will flash NE2. When it's complete it will say, "PASS" and reboot automatically. This will take a long time. If it takes more than 30 minutes see the troubleshooting below.
10. Your device is now stock NE2. Now you can either root it as you did before (in which case you're done here) or you can take the NK2 update (in which case go to step 11)
11. You will get an update notification for NK2 shortly. Take the update when you get the notice.
12. You will now go to the steps for rooting stock NK2 above, starting with step 06.
If you rooted NE2 and want to stop the Sprint update notification from nagging you to take the NK2 update [TAP HERE].
Troubleshooting
These are common troubleshooting steps for issues with rooting, installing firmware, and custom recovery.
1. Proceedure. This is the #1 cause of failure. Make sure you follow the instructions precisely. If you aren't sure about something then ask a question.
2. Cable. A poor quality cable can prevent Odin from recognizing your device. Use a different cable.
3. Drivers. Try reinstalling drivers.
4. Bad download. Try redownloading files, drivers.
5. USB port. Some computers, especially older ones, function better on certain USB ports. Try another USB port.
6. Insufficient charge. Charge your device, it's in the instructions.
7. Restart your PC. Sometimes all it takes to get things running smoothly is a fresh start.
I know how frustrating it can be trying to find the information you need to get your device running the way you want. I really hope this helps someone. If you need help please post a question or message me directly. We are a community and we're here to help eachother. If this has helped you, then please remember to post that it worked for you. Donations are appreciated. If it didn't work for you then ask for help. Please don't just post that it doesn't work. This process works, so it's more likely that you just a little assistance.
Cheers and happy rooting!
Thank you. rooting worked perfectly.
romagnus said:
Thank you. rooting worked perfectly.
Click to expand...
Click to collapse
Thanks for reporting your success. I'm happy my guide helped you!
Thanks chzeckmate. This didn't completely work for me because I ended up doing something stupid and throwing myself into a bootloop. I had to reflash NE2 and then took the NK2 OTA. Once that was done I used Chainfire's Auto Root through Odin. Now rooted on NK2 with stock recovery. I may go with a custom recovery later but prefer to leave things as is for now.
Your post got me off the fence about trying to get the NK2 update (just to get rid of the nags) and getting it rooted.
-andone- said:
Thanks chzeckmate. This didn't completely work for me because I ended up doing something stupid and throwing myself into a bootloop. I had to reflash NE2 and then took the NK2 OTA. Once that was done I used Chainfire's Auto Root through Odin. Now rooted on NK2 with stock recovery. I may go with a custom recovery later but prefer to leave things as is for now.
Your post got me off the fence about trying to get the NK2 update (just to get rid of the nags) and getting it rooted.
Click to expand...
Click to collapse
The second set of instructions deals with fixing the boot loop. You'll notice it instructs you to flash NE2 and then take NK2 OTA and then follow the first set of instructions to root and flash custom recovery. That said, I'm glad you got yourself sorted out. If you want custom recovery now, you can follow the first set of instructions. The fact that you're already rooted doesn't matter, it's totally fine to go ahead. I would highly recommend getting custom recovery so that you can make a nandroid backup to restore from in the event you have any issues in the future. Custom recovery is also necessary for flashing ROMs and ZIPs. I'm of the opinion that custom recovery is essential. Anyway, thanks for reporting. If you have any questions or need any help with anything let me know.
By the way, if you just wanted to get rid of the update nag there's a link at the bottom of this guide for how to do that. See it →HERE←
Thanks again and happy flashing!
chzeckmate said:
The second set of instructions deals with fixing the boot loop. You'll notice it instructs you to flash NE2 and then take NK2 OTA and then follow the first set of instructions to root and flash custom recovery. That said, I'm glad you got yourself sorted out. If you want custom recovery now, you can follow the first set of instructions. The fact that you're already rooted doesn't matter, it's totally fine to go ahead. I would highly recommend getting custom recovery so that you can make a nandroid backup to restore from in the event you have any issues in the future. Custom recovery is also necessary for flashing ROMs and ZIPs. I'm of the opinion that custom recovery is essential. Anyway, thanks for reporting. If you have any questions or need any help with anything let me know.
By the way, if you just wanted to get rid of the update nag there's a link at the bottom of this guide for how to do that. See it →HERE←
Thanks again and happy flashing!
Click to expand...
Click to collapse
Thanks for the follow up. I started out on rooted NE2 and CWM recovery. I was hoping against hope to try to be all sly and avoid needing to reflash NE2. So I flashed the stock recovery back on my device and then used the "unroot" option in SuperSU. This is where I was hoping I could just take the NK2 OTA and then follow your instructions to install TWRP and root. I rebooted the device and there was no more option to install NK2 in the Update Samsung Software menu option. At this point I'm thinking no problem, I'll just go into stock recovery and flash the NK2 OTA I had moved out of the cache folder to prevent an accidental install. When I flashed that, that's when I got stuck in my bootloop. I'm sure there was a no-no in there somewhere. Again, I think no problem, I'll just go flash CWM back on there and grab my latest nandroid. That didn't exactly work since I realized my software and baseband were now different versions. I reflashed NE2 and tried restoring said nandroid to give up for the night. All I got was a neverending parade of force closes from gapps. I finally conceded and just flashed NE2, took NK2 OTA and then CF Auto Rooted. Super long route to what ended up being a very simple solution.
Also, what I did to get rid of the NK2 nag was to open the notification drawer and long press on the notification. It brought up the "App Info" menu option. Clicked that and went into the app info and unchecked the "Show notifications" box. I know it turned off any notifications handled by that system app, but it worked for me so I just went with it.
I wish I had a better grasp on the Android platform than I do. A lot of what I've learned has come from weeding through many, many posts here on XDA and a lot of trial and error on my part. Honestly, I'm both glad and surprised that I haven't bricked my phone yet.
thanks.
thanks. it worked. next i'll see how to get a good backup then maybe a new ROM
Downgrade to NE2
I am sorry for out of topic, do we can downgrade from NK2 to NE2 directly from Odin?
komputertua said:
I am sorry for out of topic, do we can downgrade from NK2 to NE2 directly from Odin?
Click to expand...
Click to collapse
Odin will not let you downgrade.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Is there any other options to downgrade?
I am on stock NK2 and have some trouble with it.
Need to go to fresh MK4 or maybe Ne2.
I've been looking for NK2 tarballs but can't find it.
Just flash a custom recovery then custom mk4 rom.
Sent from my GT-N7105 using XDA Premium 4 mobile app
So there is no way to go to stock NE2?
Sorry for being fussy, could you tell me please what differences between NE2 & NK2? Is NK2 a major update including new radio and bootloader?
Sent from my HM NOTE 1W using Tapatalk
komputertua said:
So there is no way to go to stock NE2?
Sorry for being fussy, could you tell me please what differences between NE2 & NK2? Is NK2 a major update including new radio and bootloader?
Sent from my HM NOTE 1W using Tapatalk
Click to expand...
Click to collapse
NK2 is only a minor security update. Bootloader, modem, and kernel did not change. So you might be able to odin ne2 over nk2 but trying to odin any other version (unless we get something newer aka lollipop) will fail.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Thankyou jlmancuso, it works.
I've downgraded from NK2 to NE2, directly from Odin.
Thankyou very much
Sent from my HM NOTE 1W using Tapatalk
lost root, can't get it back
I had root while on ne2. took nk2. lost root. 27 May decided to re-root. worked great. backed up with titanium. downloaded twrp manager. it said I needed root. retried titanium. it didn't have root either. re-did these instructions again and again. all "seems" right with the world. I got "passed" in green. I got "team win" ! installed super su 1.94. looked ok. but no root. what is there that I don't know? any ideas! I did have some trouble with my sd card. Sandisk 64 GIG did not want to read. replaced it.
note II Sprint L900
Seaogre said:
I had root while on ne2. took nk2. lost root. 27 May decided to re-root. worked great. backed up with titanium. downloaded twrp manager. it said I needed root. retried titanium. it didn't have root either. re-did these instructions again and again. all "seems" right with the world. I got "passed" in green. I got "team win" ! installed super su 1.94. looked ok. but no root. what is there that I don't know? any ideas! I did have some trouble with my sd card. Sandisk 64 GIG did not want to read. replaced it.
note II Sprint L900
Click to expand...
Click to collapse
Would help if you stated exactly which rom you were using. Stock or name of the custom rom.
Sent from my GT-N7105 using XDA Premium 4 mobile app
lost root, can't get it back
jlmancuso said:
Would help if you stated exactly which rom you were using. Stock or name of the custom rom.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
First I want to thank you for the quick reply!!
it was still stock rom! sorry about that. I am still headed the custom rom way. Do you know about the bluetooth stack prob? I need a rom that has that fixed.
I found out what happened. the 64 gig Sandisk sd card was wonky and it lost the super user app that managed. (I had forgotten about it) I had tried several apps (to see if any could get root) I reloaded samsung drivers. I swapped cables. Finally all is well.
all of this and I haven't even soft bricked my phone! It is great to know that you guys are ready to assist. That is what makes me brave!
Thanks again!
Had to figure all this out the hard way.... Glad to see somebody posted for others. I wasn't aware that it was a general issue, I thought it was my config! ?
Sent from my SPH-L900 using Tapatalk
Is it safe to update the SuperSU Binaries? I've run into issues losing root previously doing so...
Hey y'all, sorry if this is a dumb question. I'm looking at rooting my son's Sprint Note 2. Currently it's on stock. If I follow this will it give me root so that I can install roms? I found one here on XDA that basically makes it a WiFi only tablet which is exactly what I need. Sorry again if I should have asked thus elsewhere but this just seems really straight forward and others have told me that rooting this phone was a huge pain. Currently it's on 4.4.2
Sent from my Nexus 6 using Tapatalk