Related
RESOLVED SEE POST #6
Hey guys,
I am having trouble flashing a custom recovery (TWRP) to be specific on my brothers Note 2. I was able to easily do it with my phone but I didnt update OTA to the latest ATT software.
I have the latest samsung drivers installed too.
So in general.
1. My brother updated OTA
2. I use odin to try to flash TWRP via PDA
3. It says success but when I reboot into recovery it goes into the stock android recovery instead of the custom one
4. ??? perplexed
is your [brothers] phone rooted? (you didn't mention that in the post). if it is, the easiest way to install TWRP is to download GooManager from the Play Store and, once installed, choose Menu->Install OpenRecoveryScript.
cortez.i said:
is your [brothers] phone rooted? (you didn't mention that in the post). if it is, the easiest way to install TWRP is to download GooManager from the Play Store and, once installed, choose Menu->Install OpenRecoveryScript.
Click to expand...
Click to collapse
He is not rooted. He is stock from AT&T but he said he did an OTA update a week or two ago.
I actually tried the GooManager to install TWRP but it said it installed twrp but it goes into stock android recovery
I'm not sure if this helps or not but when I load into stock android recovery it keeps "manually loading CSC"
mc704 said:
He is not rooted. He is stock from AT&T but he said he did an OTA update a week or two ago.
I actually tried the GooManager to install TWRP but it said it installed twrp but it goes into stock android recovery
I'm not sure if this helps or not but when I load into stock android recovery it keeps "manually loading CSC"
Click to expand...
Click to collapse
so i take it [your] phone is rooted, because you have a custom recovery installed. my understanding is that the device must be rooted before you can install a custom recovery. that's why installing TWRP via GooManager didn't work.
cortez.i said:
so i take it [your] phone is rooted, because you have a custom recovery installed. my understanding is that the device must be rooted before you can install a custom recovery. that's why installing TWRP via GooManager didn't work.
Click to expand...
Click to collapse
what about ODIN doesn't it root the phone when you flash a custom recovery?
on my phone all I had to do was flash via twrp via odin and it did everything for me...
this isn't the case for my brother's phone so im a little confused
mc704 said:
what about ODIN doesn't it root the phone when you flash a custom recovery?
Click to expand...
Click to collapse
ODIN doesn't root your phone. it's the package/file that you flash with ODIN that roots your device. you didn't mention the method you used to root your phone.
mc704 said:
on my phone all I had to do was flash via twrp via odin and it did everything for me...
this isn't the case for my brother's phone so im a little confused
Click to expand...
Click to collapse
flash what via TWRP? you need to reference the methods you used to flash your device, e.g., link to post. it's difficult to help without having more info. in my case i used the CF Root method which does root your phone by using ODIN to flash a package that installs SuperSU binary and APK (app that provides root) and a Stock recovery. This took less than 30 seconds. afterwards, i added my GMail account to my device, installed GooManager from the PlayStore and then used GooManager to install TWRP. hope this is helpful.
cortez.i said:
ODIN doesn't root your phone. it's the package/file that you flash with ODIN that roots your device. you didn't mention the method you used to root your phone.
flash what via TWRP? you need to reference the methods you used to flash your device, e.g., link to post. it's difficult to help without having more info. in my case i used the CF Root method which does root your phone by using ODIN to flash a package that installs SuperSU binary and APK (app that provides root) and a Stock recovery. This took less than 30 seconds. afterwards, i added my GMail account to my device, installed GooManager from the PlayStore and then used GooManager to install TWRP. hope this is helpful.
Click to expand...
Click to collapse
I see. Sorry for not being specific
When I worked on my phone. I installed the latest samsung drivers on the main website, used Odin 3.07, flashed TWRP 2.3 by PDA, and it was rooted and the custom recovery worked awesome (I did it similar to this http://www.youtube.com/watch?v=NFHZ535L7is)
However this process does not work with my brothers note 2. Which is why im confused.... I assuming TWRP auto rooted for my phone but it didn't for my brother's phone?
I will definitely give your method a try and post back. Thanks for putting up with a newbie like me! :laugh:
mc704 said:
I see. Sorry for not being specific
When I worked on my phone. I installed the latest samsung drivers on the main website, used Odin 3.07, flashed TWRP 2.3 by PDA, and it was rooted and the custom recovery worked awesome (I did it similar to this http://www.youtube.com/watch?v=NFHZ535L7is)
However this process does not work with my brothers note 2. Which is why im confused.... I assuming TWRP auto rooted for my phone but it didn't for my brother's phone?
I will definitely give your method a try and post back. Thanks for putting up with a newbie like me! :laugh:
Click to expand...
Click to collapse
no worries... i'd hate to see you fubar your brothers phone, lol. anyway, the method used in that video appears to be created by ChainFire for the N7100, which is the international version of the Note 2. the method i referenced - also developed by ChainFire - is specific to the AT&T and Canadian versions of the Note 2. if there's one thing I've learned in my years on xda, it's to make sure that you play with stuff that's compatible with your device. several of today's devices go by the same consumer friendly name (e.g.,Galaxy S 3, Note 2) but have different internals (e.g., chips). if you flash an incompatible ROM, you could end up with a nice paperweight. hope you and your brother enjoy your phones.
cortez.i said:
no worries... i'd hate to see you fubar your brothers phone, lol. anyway, the method used in that video appears to be created by ChainFire for the N7100, which is the international version of the Note 2. the method i referenced - also developed by ChainFire - is specific to the AT&T and Canadian versions of the Note 2. if there's one thing I've learned in my years on xda, it's to make sure that you play with stuff that's compatible with your device. several of today's devices go by the same consumer friendly name (e.g.,Galaxy S 3, Note 2) but have different internals (e.g., chips). if you flash an incompatible ROM, you could end up with a nice paperweight. hope you and your brother enjoy your phones.
Click to expand...
Click to collapse
just a quick update.
I flashed CF-autoroot, TWRP, and a custom rom! Everything works great!
Thanks for the help!
I got the S4 Update, and attempted to root the device with a solid YouTube video, but the root did not work. I dried with a Mac as well as a PC, to no avail on both routes. Yet, there was this initial update [that I ACCEPTED] after the device had initially been on for approximately 30 minutes. I read in the thread of the same YouTube video for the Mac attempt that this particular update is what hindered the process. There were no replies to the individual's comment on the thread, so I posing the same question here: is this initial update the reason as to why the [simple] root access instructions no longer work? If so, what is the next step(s) I can take to root the S4? Or is it best to return the device, and see about swapping for another one, and NOT accepting the initial update?
re: rooting
mrjetpacks said:
I got the S4 Update, and attempted to root the device with a solid YouTube video, but the root did not work. I dried with a Mac as well as a PC, to no avail on both routes. Yet, there was this initial update [that I ACCEPTED] after the device had initially been on for approximately 30 minutes. I read in the thread of the same YouTube video for the Mac attempt that this particular update is what hindered the process. There were no replies to the individual's comment on the thread, so I posing the same question here: is this initial update the reason as to why the [simple] root access instructions no longer work? If so, what is the next step(s) I can take to root the S4? Or is it best to return the device, and see about swapping for another one, and NOT accepting the initial update?
Click to expand...
Click to collapse
Next time don't rely on any Youtube videos
Returning your phone will not help you at all, it still will need to be rooted whether you allow the
OTA update of the firmware or not.
Here is what you need for rooting your phone:
Download ODIN which is a windows application: http://k0nane.info/rom/odin-307.zip
Download the Odin flash TAR file TWRP custom recovery here: http://downloadandroidrom.com/file/...y/TWRP/openrecovery-twrp-2.5.0.0-jfltetmo.tar
Download the M919 MDL Rooter Odin flash TAR file here: http://batakang.com/ftp/SGH-M919/ROOT_M919UVUAMDL.zip
After you downloaded all 3 files create a new folder on your
computer's desktop and copy all three of the files into it.
Open ODIN to flash these two TAR files in the PDA slot in Odin after you put your phone into download mode.
Flash the TWRP custom recovery TAR file first and then flash the M919 MDL Rooter TAR file with Odin.
After doing that you shall be rooted.
If you want or need more specific information about using Odin and rooting here is a good link for you: http://forum.xda-developers.com/showthread.php?t=2268880
Good luck!
mrjetpacks said:
I got the S4 Update, and attempted to root the device with a solid YouTube video, but the root did not work. I dried with a Mac as well as a PC, to no avail on both routes. Yet, there was this initial update [that I ACCEPTED] after the device had initially been on for approximately 30 minutes. I read in the thread of the same YouTube video for the Mac attempt that this particular update is what hindered the process. There were no replies to the individual's comment on the thread, so I posing the same question here: is this initial update the reason as to why the [simple] root access instructions no longer work? If so, what is the next step(s) I can take to root the S4? Or is it best to return the device, and see about swapping for another one, and NOT accepting the initial update?
Click to expand...
Click to collapse
From experience trust me make sure u use oudhs cwm recovery first... yes others work but I had alot of issues flashing roms after I got mine.
This is clean and simple method if you havent got it yet.
Download Odin.3.07
Dload MDB-SETuidoff .zip NOT MDL Thats just my opinion, do as you want though.
Dload and Use superuser by koush or chainfire.
NEXT.....
Odin the oudhs cwm tar file
Then boot into recovery
Do a full reset first.
Flash MDB-SETuidoff .zip
"QUOTE" THIS SEEMS TO WORK BETTER THEN MDL ROOT ZIP.
And works on new may 7th ota and stock shipped firmware.
Continue to wipe cache
Then flash super user . zip
Then reboot Phone
Without doing it this way I had reboot freezes with the MDLroot .zip
The MDB-SETuidoff .zip gets it all squared away... its on google and in xda ...it is real important it bypasses samsungs new restricted kernel that messes with rooting.
Before I figured that out I had root with MDL zip,but couldn't reboot after a flash and kept loosing superuser after attempting to reboot.
Sent from my SGH-M919 using xda app-developers app
Misterjunky said:
Next time don't rely on any Youtube videos
Returning your phone will not help you at all, it still will need to be rooted whether you allow the
OTA update of the firmware or not.
Here is what you need for rooting your phone:
Download ODIN which is a windows application: http://k0nane.info/rom/odin-307.zip
Download the Odin flash TAR file TWRP custom recovery here: http://downloadandroidrom.com/file/...y/TWRP/openrecovery-twrp-2.5.0.0-jfltetmo.tar
Download the M919 MDL Rooter Odin flash TAR file here: http://batakang.com/ftp/SGH-M919/ROOT_M919UVUAMDL.zip
After you downloaded all 3 files create a new folder on your
computer's desktop and copy all three of the files into it.
Open ODIN to flash these two TAR files in the PDA slot in Odin after you put your phone into download mode.
Flash the TWRP custom recovery TAR file first and then flash the M919 MDL Rooter TAR file with Odin.
After doing that you shall be rooted.
If you want or need more specific information about using Odin and rooting here is a good link for you: http://forum.xda-developers.com/showthread.php?t=2268880
Good luck!
Click to expand...
Click to collapse
**
When I click on the 2nd link, the page I go to is download for "Zip Opener"... Is that correct?
mrjetpacks said:
**
When I click on the 2nd link, the page I go to is download for "Zip Opener"... Is that correct?
Click to expand...
Click to collapse
**
I was able to retrieve the file from the 2nd link. I have flashed the file [from the third link] to my device via ODIN. ODIN says everything "PASS"ed, but my device still is on the download mode screen with a full downloaded blue bar on the bottom, and I have not flashed that other file "ROOT_M919 etc etc.", yet [because I cannot find anything in the file after unzipping it that will go with ODIN].
abcdefg1234567 said:
From experience trust me make sure u use oudhs cwm recovery first... yes others work but I had alot of issues flashing roms after I got mine.
This is clean and simple method if you havent got it yet.
Download Odin.3.07
Dload MDB-SETuidoff .zip NOT MDL Thats just my opinion, do as you want though.
Dload and Use superuser by koush or chainfire.
NEXT.....
Odin the oudhs cwm tar file
Then boot into recovery
Do a full reset first.
Flash MDB-SETuidoff .zip
"QUOTE" THIS SEEMS TO WORK BETTER THEN MDL ROOT ZIP.
And works on new may 7th ota and stock shipped firmware.
Continue to wipe cache
Then flash super user . zip
Then reboot Phone
Without doing it this way I had reboot freezes with the MDLroot .zip
The MDB-SETuidoff .zip gets it all squared away... its on google and in xda ...it is real important it bypasses samsungs new restricted kernel that messes with rooting.
Before I figured that out I had root with MDL zip,but couldn't reboot after a flash and kept loosing superuser after attempting to reboot.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
This looks like a great guide. It actually makes sense. Problem is, I am on Mint and I'm trying to use Heimdall and I absolutely CANNOT get it to successfully flash the recovery tar.
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
Hey, everyone. It's been a long time since I've rooted my phone. I ended up hard bricking it and getting a new one. (I tried using ROM Manager to update my Clockwork Mod and it downloaded and installed, and when it said it needed to restart the device, I accepted, and that was the last time I was able to use the phone).
Anyway, I got it replaced and I haven't rooted it. It's been about 8 months or so and I've decided I want to root my phone again. However, after doing a little research, I saw that rooting is now different when the device is running 4.4.2. I want to be able to run CyanogenMod and flash nightlies and whatnot. Is it safe for me to root my phone and flash CyanogenMod? If so, could someone direct me step by step to doing it? It's been so long and I don't want to brick another phone.
tl;dr -> havent rooted a phone in almost a year, kinda forgot how. SPH-L710 running 4.4.2. is it safe? how do i do it? i want cyanogenmod
markopolomp said:
Hey, everyone. It's been a long time since I've rooted my phone. I ended up hard bricking it and getting a new one. (I tried using ROM Manager to update my Clockwork Mod and it downloaded and installed, and when it said it needed to restart the device, I accepted, and that was the last time I was able to use the phone).
Anyway, I got it replaced and I haven't rooted it. It's been about 8 months or so and I've decided I want to root my phone again. However, after doing a little research, I saw that rooting is now different when the device is running 4.4.2. I want to be able to run CyanogenMod and flash nightlies and whatnot. Is it safe for me to root my phone and flash CyanogenMod? If so, could someone direct me step by step to doing it? It's been so long and I don't want to brick another phone.
tl;dr -> havent rooted a phone in almost a year, kinda forgot how. SPH-L710 running 4.4.2. is it safe? how do i do it? i want cyanogenmod
Click to expand...
Click to collapse
you wont brick it by rooting but here is 3 methods
1. first and mostly recommended flash Philz recovery for the D2Lte in Odin just make sure your on the latest one then root your stock rom with the option under Philz settings called Re-root(SuperSU)
2. you can use any recovery and flash the SuperSU zip from Chain fire
3. you can just use TowelRoot for the actual rooting process then download SuperSU and BusyBox from the PlayStore
method 2 implies that you already have a recovery installed
method 3 will give you root but no recovery
6th_Hokage said:
you wont brick it by rooting but here is 3 methods
1. first and mostly recommended flash Philz recovery for the D2Lte in Odin just make sure your on the latest one then root your stock rom with the option under Philz settings called Re-root(SuperSU)
2. you can use any recovery and flash the SuperSU zip from Chain fire
3. you can just use TowelRoot for the actual rooting process then download SuperSU and BusyBox from the PlayStore
method 2 implies that you already have a recovery installed
method 3 will give you root but no recovery
Click to expand...
Click to collapse
Is there a video of how to root doing this from start to finish? I'm just too nervous to do it on my own without visuals lol
markopolomp said:
Is there a video of how to root doing this from start to finish? I'm just too nervous to do it on my own without visuals lol
Click to expand...
Click to collapse
Towelroot is super easy to use, its a one click method.
You can find a full guide for the S3 here
Pretty simple to do though,
Download the TowelRoot apps from http://towelroot.com.
Enable Unknown sources on your phones, normally this option located on Settings > Security.
Install the downloaded app (tr.apk).
Now run the app, just tap the “make it ra1n” button to start rooting.
Let the app perform the root job, wait for about 15 seconds and your phone will restart automatically.
As soon as the phone is turned on, update SuperSU to v1.99r4 or newer.
vagabond007 said:
Towelroot is super easy to use, its a one click method.
Pretty simple to do though,
Download the TowelRoot apps.
Enable Unknown sources on your phones, normally this option located on Settings > Security.
Install the downloaded app (tr.apk).
Now run the app, just tap the “make it ra1n” button to start rooting.
Let the app perform the root job, wait for about 15 seconds and your phone will restart automatically.
As soon as the phone is turned on, update SuperSU to v1.99r4 or newer.
Click to expand...
Click to collapse
In my case, TowelRoot didn't work due to Samsung Knox secure boot locks the recovery rom. You can't either go to recovery mode at all or read your phone internal storage/external SD storage from TWRP. I flashed CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 and it would get SuperSU installed to your phone. The SuperSu stopped working when disabling Knox.
Alternatively, I tried to downgrade to the 4.04 or 4.1.2 stock rom by Odin, but failed. So far, I don't have any way to root my phone and install CM11. Any suggestions will be appreciated.
wuyiL said:
In my case, TowelRoot didn't work due to Samsung Knox secure boot locks the recovery rom. You can't either go to recovery mode at all or read your phone internal storage/external SD storage from TWRP. I flashed CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 and it would get SuperSU installed to your phone. The SuperSu stopped working when disabling Knox.
Alternatively, I tried to downgrade to the 4.04 or 4.1.2 stock rom by Odin, but failed. So far, I don't have any way to root my phone and install CM11. Any suggestions will be appreciated.
Click to expand...
Click to collapse
that's why you go with the first option i gave.....
6th_Hokage said:
that's why you go with the first option i gave.....
Click to expand...
Click to collapse
Here here. And, you'll learn how to use Odin and philz. Very very valuable (imo) ?
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
markopolomp said:
Is there a video of how to root doing this from start to finish? I'm just too nervous to do it on my own without visuals lol
Click to expand...
Click to collapse
Have you figured that out?
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