Related
WARNING: Following any of these instructions WILL void your warranty,
and could possibly cause irreparable harm to your device (i.e. bricked)
If you do Not understand these risks, stop here and do Not proceed.
If you do Not know how to use Odin, stop here and do Not proceed.
This guide is ONLY for SGH-T999 variants that are ALREADY RUNNING android 4.3
If you do Not have a SGH-T999 variant, stop here and do Not proceed.
If you are Not currently running android 4.3, stop here and do Not proceed.
I am not responsible for anything that happens to your device. YOU chose to follow this guide.
I have the SGH-T999V (samsung galaxy S3, canada, Videotron)
I flashed the full 4.3 firmware from samsung-updates.com as soon as it became available ... and then I tried to root it the usual ways
However knox prevented the superSu app from running, and it closed immediately, and obviously root was Not available to any app
This method will obtain ROOT and REMOVE the knox garbage
note ... altho it is optional to remove knox, I have Not tested without removing knox and do Not know if root will work using this method (guide) with knox still installed !
I did NOT create this method ... I simply found it, read thru user comments, and used it
FULL CREDIT goes to
@upndwn4par for the method ... the thread is here
@Kaito95 for the Knox Removal script ... the thread is here
@Dees_Troy for the TWRP recovery
@Chainfire for SuperSu
as you can see, this method was for the AT&T, Rogers, Bell, Telus Samsung Galaxy S3 ... I747 variants, I believe
So here is how I achieved a successful root on 4.3 using the above method, with adjustments for our T999 variant
Using Method #2
1. Download required files
a) download Odin 3.07 to your PC
b) download the latest TWRP recovery for your device, in TAR format, to your PC
click on your device here
scroll down on your device page to the section called Download - Odin Flashable Tar
below that, click on the Select the latest .tar file from here link
scroll to the bottom of the files and click on the latest TAR version
note to d2tmo users ... thanks to @Perseus71 it has been noted that 2.6 versions may have issues on your device, and it is recommended that you choose the 2.5.0.0 TAR version
example: Mine looks like this: openrecovery-twrp-2.6.3.0-d2can.tar
note to T999V users ... both d2can and d2tmo work for our device ... I personally use d2can
c) download SuperSu 1.65 zip to your DEVICE
c) download Knox Removal zip to your DEVICE
2. Reboot into Download mode ... VolumeDOWN + Power + Home
Run Odin
make sure that re-partition is NOT checked!
click the PDA button and point to the TWRP recovery TAR file that you downloaded above
connect your device to the computer ... wait briefly
the COMM port in top left box should turn blue
click Start
when it is done, PASSED, and phone has rebooted, disconnect device
3. Reboot into Recovery mode ... VolumeUP + Power + Home
Flash (install) the Knox Remover zip
Flash (install) the SuperSu zip ... it is version 1.65, current is 1.80, so it will prompt us to update later :good:
Reboot System
4. Update SuperSu from the Play Store
5. Open SuperSu
it should prompt that it needs to update the binary
accept and let it update the binary the Normal way
6. Reboot
7. Enjoy rooted 4.3, knox-free :laugh: :good:
thanks again to @Perseus71 for noting that it is possible that the default Enforcing mode of SElinux may cause issues with the ability and/or performance of some root apps despite being granted root permission
if you are experiencing similar issues, he recommends that you check out the SELINUX Status Changer app.
[I have Not personally tested this app]
reserved
in case
You may also wish to mention the SELINUX Status Changer. Here's the Thread.
With it enabled, root won't be stable.
Ahem. First ?
EDIT - TWRP 2.6.x.x has trouble remounting and formatting /Data. You may wish to reccomend version 2.5.0.0
Perseus71 said:
You may also wish to mention the SELINUX Status Changer. Here's the Thread.
With it enabled, root won't be stable.
Ahem. First ?
EDIT - TWRP 2.6.x.x has trouble remounting and formatting /Data. You may wish to reccomend version 2.5.0.0
Click to expand...
Click to collapse
hi and thanks for your input
I just looked at that SELINUX Status Changer thread and will keep an eye on it ... but for now I won't add it cuz:
the dev says it is pre-alpha version
Mine is Enforcing and root seems stable and hasn't had any problems, yet ... 4 days so far
SElinux is here to stay, and there's a big difference between proper (Google) implementation and samching implementation ... root blocked by samching, but not by standard android enforcing #BAM
congrats on being first, lol
what kind of things are you referring to when you say that root won't be stable?
what is your device d2 id?
I haven't had any problems with twrp 2.6.3 for d2can
THAT is something I WILL add, for your specific device
any particular reason you're recommending all the way back to 2.5 instead of just earlier 2.6 version?
cLogic said:
what kind of things are you referring to when you say that root won't be stable?
what is your device d2 id?
I haven't had any problems with twrp 2.6.3 for d2can
THAT is something I WILL add, for your specific device
any particular reason you're recommending all the way back to 2.5 instead of just earlier 2.6 version?
Click to expand...
Click to collapse
I have D2TMO AKA SGH-T999. Yes this is specific to my variant. I tested all the 2.6.x versions to establish that the /Data Problem exists in all these versions.
As to Root, well, Certain apps such as Nandroid Manager, and other apps have difficulty performing Root operation despite SuperSU granting it. @Aerowinder has a lot of stories. May I suggest you please visit the D2TMO Leaked 4.3 Rom thread in development for more details ?
Perseus71 said:
I have D2TMO AKA SGH-T999. Yes this is specific to my variant. I tested all the 2.6.x versions to establish that the /Data Problem exists in all these versions.
As to Root, well, Certain apps such as Nandroid Manager, and other apps have difficulty performing Root operation despite SuperSU granting it. @Aerowinder has a lot of stories. May I suggest you please visit the D2TMO Leaked 4.3 Rom thread in development for more details ?
Click to expand...
Click to collapse
fair enough ... thanks again for your input ... OP updated
Did this to the letter and soft bricked as soon as I flashed the mod zip in twrp. Stuck on pulsing samsung logo.
Had to reflash. Tried twice just to be sure.
(T999) (root, 4.3 stock)
trepoman said:
Did this to the letter and soft bricked as soon as I flashed the mod zip in twrp. Stuck on pulsing samsung logo.
Had to reflash. Tried twice just to be sure.
(T999) (root, 4.3 stock)
Click to expand...
Click to collapse
what do you mean ... bricked as soon as you flashed mod zip? you mean the knox removal script?
not sure how that's even possible
if you see the pulsing logo, then you rebooted
your T999 is rooted?
meaning it was before, or everything was fine after you did it twice?
cLogic said:
what do you mean ... bricked as soon as you flashed mod zip? you mean the knox removal script?
not sure how that's even possible
if you see the pulsing logo, then you rebooted
your T999 is rooted?
meaning it was before, or everything was fine after you did it twice?
Click to expand...
Click to collapse
The native tether mod. Knox remover worked fine.
Phone is rooted, stock 4.3.
Flashed tether mod in twrp recovery, which succeed but phone would not boot past the pulsing Samsung afterwards (10 minutes of pulsing, never booted past that) nor would it boot to recovery. I could get to boot loader luckily. I pulled the battery and tried again, same thing. Flashed stock 4.3 in Odin to get phone alive, tried flashing tether mod again, exact same result and same solution. HTH.
So close to clicking buy now on a nexus 5...
trepoman said:
The native tether mod. Knox remover worked fine.
Phone is rooted, stock 4.3.
Flashed tether mod in twrp recovery, which succeed but phone would not boot past the pulsing Samsung afterwards (10 minutes of pulsing, never booted past that) nor would it boot to recovery. I could get to boot loader luckily. I pulled the battery and tried again, same thing. Flashed stock 4.3 in Odin to get phone alive, tried flashing tether mod again, exact same result and same solution. HTH.
So close to clicking buy now on a nexus 5...
Click to expand...
Click to collapse
ummm .. not sure what this tether mod is that you are talking about, but it's not part of this guide, lol
this guide simply flashes the knox removal script (to delete knox files) and superSu (to root)
cLogic said:
ummm .. not sure what this tether mod is that you are talking about, but it's not part of this guide, lol
this guide simply flashes the knox removal script (to delete knox files) and superSu (to root)
Click to expand...
Click to collapse
Confounded facts. Always kicking my ass.
This is what happens when I stay up too late and try to do too many things. Linked from another thread and had too many tabs open.
Delete.
Thanks for the post. Sadly, no dice for me. I was directed to this post after creating my own. I've really held off asking for help, but only conclusion I can come to is I got one of those phones that just flat out won't root. Tried everything I can think of. Samsung Galaxy s3, SGH-T999v, 4.3, Wind (Canada). The Odin steps worked, when I boot into recovery, just get the stock android recover menu (original issue I've been having). Nothing seems to work in the slightest.
So I followed this to the letter and it all went well. Except, while the device seems to be rooted, SuperSU seems to be granting permissions to apps, Root Check Pro reports the device is rooted... I still can't use any apps that require root access. GameCIH doesn't work. ROM Manager doesn't work. Nothing wants to work.
Why is this happening? Because every step seemed to go flawlessly. Also, I have no idea how to put it back to stock if I wanted to try and start over lol.
[EDIT]
Oh yeah. Pertinent information. Samsung Galaxy S3 T999V through Mobilicity (Canada) running 4.3.
Used the 2.5 tar rather than the 2.6.
Also set SElinux to permissive.
ksec said:
Thanks for the post. Sadly, no dice for me. I was directed to this post after creating my own. I've really held off asking for help, but only conclusion I can come to is I got one of those phones that just flat out won't root. Tried everything I can think of. Samsung Galaxy s3, SGH-T999v, 4.3, Wind (Canada). The Odin steps worked, when I boot into recovery, just get the stock android recover menu (original issue I've been having). Nothing seems to work in the slightest.
Click to expand...
Click to collapse
are you sure you're running stock 4.3 ? baseband MK5 ?
re-do the Odin steps, except uncheck the auto reboot option .. so that it stops after successfully pushing the recovery tar
unplug the phone from the pc .. it should still be in download mode
pull the battery
then put it back in
boot into recovery immediately
if you see the TWRP recovery, great!, complete the guide and you'll be knox free and rooted
if that worked then there are two files that you seem to still have that are putting stock recovery back on normal boot .. post results here and I'll find them for you
Ergonyx said:
So I followed this to the letter and it all went well. Except, while the device seems to be rooted, SuperSU seems to be granting permissions to apps, Root Check Pro reports the device is rooted... I still can't use any apps that require root access. GameCIH doesn't work. ROM Manager doesn't work. Nothing wants to work.
Why is this happening? Because every step seemed to go flawlessly. Also, I have no idea how to put it back to stock if I wanted to try and start over lol.
[EDIT]
Oh yeah. Pertinent information. Samsung Galaxy S3 T999V through Mobilicity (Canada) running 4.3.
Used the 2.5 tar rather than the 2.6.
Also set SElinux to permissive.
Click to expand...
Click to collapse
did you go into superSu and update it's binary?
what do you mean, exactly, by apps won't work ?
do they run? you said they are being granted permission.
how were they installed?
we're they restored using Titanium?
the 2.5 TWRP was recommended for tmobile users.. we are T999V, can use d2can 2.6.3.0 or d2tmo 2.6.3.1
cLogic said:
did you go into superSu and update it's binary?
what do you mean, exactly, by apps won't work ?
do they run? you said they are being granted permission.
how were they installed?
we're they restored using Titanium?
the 2.5 TWRP was recommended for tmobile users.. we are T999V, can use d2can 2.6.3.0 or d2tmo 2.6.3.1
Click to expand...
Click to collapse
I updated the the SuperSU binary.
The apps will open but when it attempts to do anything requiring root access it is denied or fails.
SuperSU and Knox were installed through the TWRP recovery boot thing as the guide specified. Other things were either installed from the app store or downloaded APK files. I didn't have Titanium at the time I attempted rooting my phone. Wasn't mentioned in the guide so I never got it. I have the basic version now from the play store now. As I'm sure you can tell, I've never rooted my device before. Always had a friend do it for me.
Should I just restore to a stock install (not sure how to do this) and then try again? Especially now that I know the 2.5 warning was specifically for T-Mobile users? Or can I just put the 2.6X version on my phone and try again? lol
it's working
@ cLogic
Thanks a lot man, thanks to you I successfully root my sgh-t999v (stock android 4.3)
I've managed to use GooManager from the Google Play store to install latest TWRP and to flash the 4.3 mod.
Having issues when trying this. I followed all the steps and received no errors. But when the SuperSu ap tries to open on my phone it crashes, the ap only phone is stable.
I have Tomo G3 4.3 Stock rom
Flashed the TW 2.5.0.0 version
Rebooted into the touch recovery
Ran Knox removal
Ran SuperSu
Booted
Knox is not in my list off apps
SuperSu does show
Cant not open supersu, updating binarys does not work since the app crashes.
(Edit)--> Redid the whole process but did not let the phone reboot during the TW flash and the Zip installs. Seemed to of fixed the issue. (Edit)
Thanks added
I flashed Stock 4.3 via Odin before coming across this guide and now my device seems to be stuck at the boot screen. My question is, if I haven't completely booted, can I reflash using the modified version of 4.3 (root, deodexed, knox removed)? Do I have any other options right now?
So my sister has an Attt Galaxy note 2. I want to format her phone and install aokp or cyanogenmod on it cause they are smoother and faster roms. I searched on how to unlock and root the Galaxy note 2 but i've only found a bunch of guides showing how to root the phone, i haven't found one telling how to unlock the bootloader?
does anyone know how to unlock the GN2 bootloader, or is it already unlocked?
jinjin12 said:
So my sister has an Attt Galaxy note 2. I want to format her phone and install aokp or cyanogenmod on it cause they are smoother and faster roms. I searched on how to unlock and root the Galaxy note 2 but i've only found a bunch of guides showing how to root the phone, i haven't found one telling how to unlock the bootloader?
does anyone know how to unlock the GN2 bootloader, or is it already unlocked?
Click to expand...
Click to collapse
Surprise no one has answered. You can't, and you don't need to.
What firmware is the phone on now?
dicksteele said:
Surprise no one has answered. You can't, and you don't need to.
What firmware is the phone on now?
Click to expand...
Click to collapse
what do you mean you can't? Are samsung phones different somehow? I can unlock bootloader on my Nexus 4, my bro's Moto g, and my other Bro's Lg Optimus G, so why can't i unlock bootloader on Samsung Galaxy note 2?
i've never used a samsung phone before so i'm not sure if they differ somehow.
So i don't need to unlock bootloader to install aokp or cyangamod? i only need to root and install custom recovery? I think her phone is on android 4.1.2 or 4.2 i forgot which one.
jinjin12 said:
what do you mean you can't? Are samsung phones different somehow? I can unlock bootloader on my Nexus 4, my bro's Moto g, and my other Bro's Lg Optimus G, so why can't i unlock bootloader on Samsung Galaxy note 2?
i've never used a samsung phone before so i'm not sure if they differ somehow.
So i don't need to unlock bootloader to install aokp or cyangamod? i only need to root and install custom recovery? I think her phone is on android 4.1.2 or 4.2 i forgot which one.
Click to expand...
Click to collapse
Samsung does not consider your phone yours as these other manufacturers.
If she has not done the most recent Over the Air update to 4.3, it's probably on 4.1.2. The latest OTA installs Knox security. You dont want that.
There are some good choices in the http://forum.xda-developers.com/galaxy-note-2-att/development
You don't need to root either. If you do install, it will get overwritten since it's installed in the /system directory. ROMs replace the /system directory.
Just install custom recovery, follow ROMs install instructions. Verify with the thread OP if it requires the 4.3 leaked bootloader.
Located here.
http://forum.xda-developers.com/showthread.php?t=2502464
Oh and Samsung has help from AT&T
http://androidandme.com/2013/08/car...upport-unlocked-bootloaders-once-and-for-all/
dicksteele said:
Samsung does not consider your phone yours as these other manufacturers.
If she has not done the most recent Over the Air update to 4.3, it's probably on 4.1.2. The latest OTA installs Knox security. You dont want that.
There are some good choices in the http://forum.xda-developers.com/galaxy-note-2-att/development
You don't need to root either. If you do install, it will get overwritten since it's installed in the /system directory. ROMs replace the /system directory.
Just install custom recovery, follow ROMs install instructions. Verify with the thread OP if it requires the 4.3 leaked bootloader.
Located here.
http://forum.xda-developers.com/showthread.php?t=2502464
Oh and Samsung has help from AT&T
http://androidandme.com/2013/08/car...upport-unlocked-bootloaders-once-and-for-all/
Click to expand...
Click to collapse
I really appreciate the help . i posted on android central and this forum but no help until you posted so thanks. I guess samsung phones are different. I was also told that you only need to back up EFS files on samsungs phones only and NOT on Nexus 4, or Moto G right?
Also, you said you can just install custom recovery but don't you need to root phone to do that? and the most roms like aokp comes rooted by default right?
jinjin12 said:
I really appreciate the help . i posted on android central and this forum but no help until you posted so thanks. I guess samsung phones are different. I was also told that you only need to back up EFS files on samsungs phones only and NOT on Nexus 4, or Moto G right?
Click to expand...
Click to collapse
But of course.
EFS holds IMEI info, carrier info, a backup is definitely a good idea. You never know when an OH SH*T will pop up.
Here's some info. OH SH*T examples too.
http://www.droidviews.com/how-to-ba...imei-on-samsung-galaxy-devices-did-you-do-it/
Here's a couple to try.
https://play.google.com/store/apps/details?id=nl.boris.efsbackup&hl=en
http://forum.xda-developers.com/galaxy-s3/development/tool-samsung-tool-1-0-t2602325
And always back up your external sdcard to PC.
Top 5 OH SH*T's, accidentally formatted external sdcard. Helpful when upgrading to a bigger sdcard, also.
I just put in a 64MB samsung card. Fricking screams.
Good luck
dicksteele said:
But of course.
EFS holds IMEI info, carrier info, a backup is definitely a good idea. You never know when an OH SH*T will pop up.
Here's some info. OH SH*T examples too.
http://www.droidviews.com/how-to-ba...imei-on-samsung-galaxy-devices-did-you-do-it/
Here's a couple to try.
https://play.google.com/store/apps/details?id=nl.boris.efsbackup&hl=en
http://forum.xda-developers.com/galaxy-s3/development/tool-samsung-tool-1-0-t2602325
And always back up your external sdcard to PC.
Top 5 OH SH*T's, accidentally formatted external sdcard. Helpful when upgrading to a bigger sdcard, also.
I just put in a 64MB samsung card. Fricking screams.
Good luck
Click to expand...
Click to collapse
Also, you said you can just install custom recovery but don't you need to root phone to do that? and the most roms like aokp comes rooted by default right? Odin roots the phone? i saw a guide by technobuffalo and the dude used odin to root the phone before installing TWRP
jinjin12 said:
Also, you said you can just install custom recovery but don't you need to root phone to do that? and the most roms like aokp comes rooted by default right? Odin roots the phone? i saw a guide by technobuffalo and the dude used odin to root the phone before installing TWRP
Click to expand...
Click to collapse
Sorry, started replying back last night and got sidetracked.
Yes no need to root, pre-custom recovery. They are totally different. Root (superuser) is a file and app.
Custom recovery replaces the phones built-in Android recovery.Two "versions" TWRP and Clockworkmod. Both work well. Some ROM installs will suggest using a certain one.
ODIN will root the phone.
That file is here.
http://download.chainfire.eu/280/CF...t-t0lteatt-samsungsghi317.zip?retrieve_file=1
Most ROMs do have root incorporated.
dicksteele said:
Sorry, started replying back last night and got sidetracked.
Yes no need to root, pre-custom recovery. They are totally different. Root (superuser) is a file and app.
Custom recovery replaces the phones built-in Android recovery.Two "versions" TWRP and Clockworkmod. Both work well. Some ROM installs will suggest using a certain one.
ODIN will root the phone.
That file is here.
http://download.chainfire.eu/280/CF...t-t0lteatt-samsungsghi317.zip?retrieve_file=1
Most ROMs do have root incorporated.
Click to expand...
Click to collapse
odin can also flash roms and install custom recovery images right? i can just flash roms and recoveries using adb on the GN2 to flash roms also?
The technobufallo guide kind of made no sense since the guy used odin to root the phone, then used odin to flash custom recovery, then used it to flash cyanogenmod, which is pointless since like you say above, custom roms comes with root preloaded.
also my sister asked att to unlock her phone and now she's using tmobile with the phone. Would flashing any roms also lock the phone and prevent using tmobile sim?
jinjin12 said:
odin can also flash roms and install custom recovery images right? i can just flash roms and recoveries using adb on the GN2 to flash roms also?
The technobufallo guide kind of made no sense since the guy used odin to root the phone, then used odin to flash custom recovery, then used it to flash cyanogenmod, which is pointless since like you say above, custom roms comes with root preloaded.
also my sister asked att to unlock her phone and now she's using tmobile with the phone. Would flashing any roms also lock the phone and prevent using tmobile sim?
Click to expand...
Click to collapse
Yes. that does not make sense. So stop reading that guide.
You will need to flash a custom recovery. I'm detailing a TeamWin Recovery Project (TWRP) install
Here is an explanation of TWRP and how to use it.
http://www.addictivetips.com/android/what-is-twrp-how-to-install-use-it-on-android-devices-guide/
by Haroon Q Raja
Here are other ways to install a custom recovery on your Android phone
http://www.addictivetips.com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/
Also by Haroon Q Raja
INSTALLING TWRP 2.6.3.1
Download
http://goo.im/devs/OpenRecovery/t0lteatt/openrecovery-twrp-2.6.3.1-t0lteatt.img.tar
- Run Odin3 v3.07.exe
Download Link http://www.mediafire.com/download/772dlmuaxfgm0x2/Odin307.zip
- Put your Note 2 in Download Mode
Entering download mode is very simple. First you will need to turn off your device. Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device.
Plug into a RELIABLE usb port and a RELIABLE usb cable (preferably the white Samsung cable) and wait for it to show up in Odin (COM5 or something like that)
- Click the PDA slot in Odin and locate the openrecovery-twrp-2.6.3.1-t0lteatt.img.tar that you downloaded.
The filename that goes into the PDA Slot is openrecovery-twrp-2.6.3.1-t0lteatt.img.tar
MAKE SURE IN THE OPTION AREA ONLY AUTO REBOOT AND F.RESET TIME ARE CHECKED!!!
- Click START and wait. It will complete and reboot.
Just install this ROM
http://forum.xda-developers.com/showthread.php?t=2568537
It's multicarrier so TMO is supported. It's rooted already.
Right above the Vipers Audio banner, on the left is a click here to show content. It lists all the features. I don;t think she's going to need more than this ROM right now.
dicksteele said:
Yes. that does not make sense. So stop reading that guide.
You will need to flash a custom recovery. I'm detailing a TeamWin Recovery Project (TWRP) install
Here is an explanation of TWRP and how to use it.
http://www.addictivetips.com/android/what-is-twrp-how-to-install-use-it-on-android-devices-guide/
by Haroon Q Raja
Here are other ways to install a custom recovery on your Android phone
http://www.addictivetips.com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/
Also by Haroon Q Raja
INSTALLING TWRP 2.6.3.1
Download
http://goo.im/devs/OpenRecovery/t0lteatt/openrecovery-twrp-2.6.3.1-t0lteatt.img.tar
- Run Odin3 v3.07.exe
Download Link http://www.mediafire.com/download/772dlmuaxfgm0x2/Odin307.zip
- Put your Note 2 in Download Mode
Entering download mode is very simple. First you will need to turn off your device. Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device.
Plug into a RELIABLE usb port and a RELIABLE usb cable (preferably the white Samsung cable) and wait for it to show up in Odin (COM5 or something like that)
- Click the PDA slot in Odin and locate the openrecovery-twrp-2.6.3.1-t0lteatt.img.tar that you downloaded.
The filename that goes into the PDA Slot is openrecovery-twrp-2.6.3.1-t0lteatt.img.tar
MAKE SURE IN THE OPTION AREA ONLY AUTO REBOOT AND F.RESET TIME ARE CHECKED!!!
- Click START and wait. It will complete and reboot.
Just install this ROM
http://forum.xda-developers.com/showthread.php?t=2568537
It's multicarrier so TMO is supported. It's rooted already.
Right above the Vipers Audio banner, on the left is a click here to show content. It lists all the features. I don;t think she's going to need more than this ROM right now.
Click to expand...
Click to collapse
OK thanks alot man and thanks for taking the time to write all of that to help me :victory:
I was going to install aokp or cyanogenmod since she' been complaining about her phone being slow and stock touchwiz 4.1.2 is already reptty slow in itself. BUt she said she wanted to use s-pen features and especially multi window for her work, so those aokp and cyan roms were out of the the question. I still think if she wants speed, she needs aokp or cyanogenmod though, but i guess a lot of people those the touchwiz features
jinjin12 said:
OK thanks alot man and thanks for taking the time to write all of that to help me :victory:
I was going to install aokp or cyanogenmod since she' been complaining about her phone being slow and stock touchwiz 4.1.2 is already reptty slow in itself. BUt she said she wanted to use s-pen features and especially multi window for her work, so those aokp and cyan roms were out of the the question. I still think if she wants speed, she needs aokp or cyanogenmod though, but i guess a lot of people those the touchwiz features
Click to expand...
Click to collapse
No prob. That's why I pointed you to the Jedi Master X. It'll work on T Mobile, It has the speed. Check out the builder, ptmr3, stats. Fricking insane.
20000+ thanks, 8000+ posts.
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