Develop Bugs

[HOWTO] [ROOT] No Tripping Flash Counter - Root Injected L900VPALJC +[TWRP] + more

This is a root injected FACTORY Stock L900VPALJ1 Odin Flashable Image. You flash this in Odin just as you would the completely stock ROM from samsung. I've simply injected the su binary and SuperSu app so you now have rooted stock image.
So if you want to keep your device stock yet have the functionality of root without tripping the counter or messing up OTA updates then this would be your best bet.
You can get ODIN here
and the drivers for the SPH-L900 so ODIN can detect your phone can be found at Samsung's site. Click on the Manuals & Downloads tab at the bottom and then on Software for the latest driver.
Instructions:
First, Download Image:
New Full Rom VPALJC
Mirror 1: root66_SPR_L900VPALJC.7z
Orig Release JB 4.1.1
Mirror 1: root66_SPR_L900VPALJ1.7z
Mirror 2: root66_SPR_L900VPALJ1.7z
Second, Extract and Flash:
Extract the root66_SPR_L900VPALJ1.tar.md5 from the .7z file you downloaded.
Use Odin, put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66_SPR_L900VPALJ1.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE.
OTA Updates:
Stock Recovery: Once rooted with above method, if you receive a notification for an OTA update, it has been verified you can use OTA RootKeeper to retain root through the update process.
Non-Stock Recovery: If you have loaded a non-stock recovery (per below) you can simply use it to flash the OTA update flashable zip I've created.
Mirror 1: OTA Update LJ1 to LJC
Mirror 2: OTA Update LJ1 to LJC
Optional, Recovery (will trip counter):
It seems loading any custom recovery will trip the download mode flash counter. Loading a non stock recovery will also prevent you from successfully applying any OTA updates however here is a procedure for any who want a non-stock recovery:
Currently I see TWRP has support for this device so the instructions here will install that recovery.
Option 1: Download GooManager from the Play store. Once installed click the menu and select "Install OpenRecovery Script".
Option 2: Download the TWRP recovery image here. Copy it to the /sdcard of your phone.
Connect your phone to your computer and use adb
type adb shell
once in the shell run su
then
dd if=/sdcard/openrecovery-twrp-2.3.1.1-t0ltespr.img of=/dev/block/mmcblk0p9
Alternate if unfamiliar with adb commands
Grab android terminal emulator from the play store and run the same commands starting with su and then the dd command.
De-Bloater
If you've made it this far with a stock, rooted phone with CWM or TWRP and you don't want to flash a custom rom (which will do its own de-bloating) you can check out my mrRobinson Note II De-Bloater to easily get rid of bloat system apps you no longer want to see. Simply flash in CWM or TWRP like anything else and you will be presented with a menu system to choose what to remove. If you are unsure it is safe to pick Minimal and still get a decent de-bloat.​
Bonus Files
ODIN Flashable LJC Stock Recovery: SPR_recovery_L900VPALJC.tar.md5
CWM Flashable LJC Modem: modem_CWM_L900VPALJC.zip
History:
I've injected root into other stock images and those threads have a lot of valuable information which could answer some questions that may arise here. If you have time to do some reading here are a few of the informative ones:
Samsung Galaxy S3 [ATT / Bell / Telus / Rogers / Sasktel ]
Samsung Galaxy S3 [TMO / Wind / Mobilicity]
Also did sprint and vzw but there isn't much there that won't be covered above.
FAQ
Does this remove the Sprint bloatware?
A: No. It is same as stock, nothing is removed.
Does this use an unsecured boot.img
A: No. This flashes the stock boot.img in the VPALJ1 image.
If my flash counter has been tripped, and I flash this and reset the counter, will it stay at 0.
A: Yes, as long as you don't then flash a non-stock recovery.
Can I still get OTA updates?
A: Yes if you do not load a custom recovery or remove any system apps OTA updates will still come and be able to be successfully applied. If you want to retain root through the OTA process I'd recommend trying the SuperSU survival mode.

okay will this reset my phone completely? or just install root

Question can this be implemented in to custom roms the "not tripping the counter"
Sent from >> here <<

steviee7 said:
okay will this reset my phone completely? or just install root
Click to expand...
Click to collapse
Just root.

moose1313 said:
Question can this be implemented in to custom roms the "not tripping the counter"
Sent from >> here <<
Click to expand...
Click to collapse
No. Custom roms would trip.

Nice work!

mrRobinson said:
No. Custom roms would trip.
Click to expand...
Click to collapse
Thanks I only asked because I figured if it could be injected as in tricking the phone this is coming from the manufacturer you could also tweak other things and still get away with it. ..Also without an OTA released yet can you say 100% an OTA will go through with no problems if we used this Thanks again
Sent from >> here <<

mrRobinson said:
No. Custom roms would trip.
Click to expand...
Click to collapse
maybe im just a lil special at the moment, i haven't tripped the flash counter yet i learn something when i had the s3 i think that after you flash the tar for the recovery wait till its done (uncheck reboot before u flash) and then pull the battery and it doesnt trip the counter. if im wrong someone please correct me.

Just wanted to let everyone know I did this method then accepted the OTA update and I'm still rooted. Thanks for this!

Very nice! Thank you very much! This will make it easy to go back to stock AND have custom recovery!

wraptor said:
Just wanted to let everyone know I did this method then accepted the OTA update and I'm still rooted. Thanks for this!
Click to expand...
Click to collapse
Anyway u could get this in the hands of devs particularly joshbeach so he can start getting this in the jellybomb rom?
Sent from my SPH-L900 using xda app-developers app

If I odin this, does it reset everything? Seems large for just a reocvery

JBizzleFoSho said:
If I odin this, does it reset everything? Seems large for just a reocvery
Click to expand...
Click to collapse
Its not just a recovery. that's a root method that trips the counter. Maybe you responded in wrong thread.
This will reset nothing, just fyi.

yay gonna run this and flash the new update .... ive been doing dirty jellybomb flashes for quite awhile time a start with a fresh base :good:
---------- Post added at 11:14 AM ---------- Previous post was at 10:28 AM ----------
wraptor said:
Just wanted to let everyone know I did this method then accepted the OTA update and I'm still rooted. Thanks for this!
Click to expand...
Click to collapse
I did it and lost root

fatboypup said:
yay gonna run this and flash the new update .... ive been doing dirty jellybomb flashes for quite awhile time a start with a fresh base :good:
---------- Post added at 11:14 AM ---------- Previous post was at 10:28 AM ----------
I did it and lost root
Click to expand...
Click to collapse
yes you should as it overwrites all /system. use an ota rootkeeper or supersu survival mode to retain root through the ota process.

mrRobinson said:
yes you should as it overwrites all /system. use an ota rootkeeper or supersu survival mode to retain root through the ota process.
Click to expand...
Click to collapse
thanks

Yes sorry must of been delirious last night. Some of my programs that need root (like mybackuppro) still work after the OTA so I just assumed all was good. Titanium backup doesn't however confirming no root =/. Best method to get it back?

wraptor said:
Yes sorry must of been delirious last night. Some of my programs that need root (like mybackuppro) still work after the OTA so I just assumed all was good. Titanium backup doesn't however confirming no root =/. Best method to get it back?
Click to expand...
Click to collapse
i ran CF auto root then installed rootkeeper than flashed the update again ..... still tying to get custom recovery going at the moment TWRP from goo manager says it installed but its not sticking i goto recovery and its still stock

actually i looked at the patch.... I don't see where it would be removing root.... I must be missing something.

fatboypup said:
i ran CF auto root then installed rootkeeper than flashed the update again ..... still tying to get custom recovery going at the moment TWRP from goo manager says it installed but its not sticking i goto recovery and its still stock
Click to expand...
Click to collapse
if you have a root explorer go to /system/etc and delete the install-recovery.sh file you see there. Or just rename it something else like install-recovery.bak

SGH-T999L 4.3 Root

Hello, I am looking for some tutorial, How to root SGH-T999L 4.3 android. Thanks for any info.

What is your have SELINUX Status in Settings > about ? Also is Knox enabled ?

I can't put a screen shot. Baseband version T999LUVUBMK4
Kernel version 3.0.31-2106417
[email protected] #1
Bulid number JSS15J.T999LUVUBMK4
Se for android status
Enforcing
SEPF_SGH-T999L_4.3_0010

Can you try through Download mode if you can flash a custom Recovery ? If it fails to write, you may have to flash Stock 4.3 Root66.
Please follow this thread.

Can Odin a recovery, just make sure auto reboot is not checked. After it's done boot into recovery and flash superuser, or a ROM of your choice.
Sent from my SGH-T999L

I flashed cf auto root for t999 thru odin and installed supersu from the play store but my warranty bit in download mode now shows 1. Supersu gave permission to triangle away 3.10 to reset the flash counter. System still shows modified and warranty bit 1.

red rocket said:
I flashed cf auto root for t999 thru odin and installed supersu from the play store but my warranty bit in download mode now shows 1. Supersu gave permission to triangle away 3.10 to reset the flash counter. System still shows modified and warranty bit 1.
Click to expand...
Click to collapse
The new bootloader introduced the Warranty Bit. It can not be reset with Triangle Away.

I am in recovery mode, I am choosing applly update from external storage, I am trying install Knox Remover, after few seconds phone is rebooting. During installation i rhink I have seen some failed. But I am not sure, what I am doing wrong?
Soryy I have got the solution. In Odin make sure that auto reboot is NOT checked.

Now I am trying to find the answer do I need to do more modifications to prepare my phone to install any custom rom or I can just choose straight a one and start the installation. Cheers

czarniakrps said:
Now I am trying to find the answer do I need to do more modifications to prepare my phone to install any custom rom or I can just choose straight a one and start the installation. Cheers
Click to expand...
Click to collapse
Doesnt look like you need any thing else just flash the rom and i guess the new modem and u should be ok. i havent yet flashed a rom yet. i will try in a lil bit. I have root and i have twrp installed and everything looks like its ready so i shall try.

Knox Question
Perseus71 said:
What is your have SELINUX Status in Settings > about ? Also is Knox enabled ?
Click to expand...
Click to collapse
As for selinux, I'll take a screenshot, but as to Knox you referred to it being enabled (¿Huh?).I never touched Knox, as it was meant for business users. How would I turn it off?

[GUIDE] Root T999 (variants) on android 4.3 AND remove knox

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?

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

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

work on ND8 rom? sprint phone?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

added two more t=root methods

AT&T Note 5 (N920A) Teather Root

​My knox was not tripped.
​Highly recommend to have a odin firmware!
Tested on 5.1.1
Recommend to update to PB2, BACK UP BACK UP BACK UP may delete everything.
http://www.mediafire.com/download/kuvw79x83zrdpc9/N920AUCU2APB2_User_Binary.zip
A not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated*posted a script that does push SuperSU into system/. This was originally posted in the AT&T GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1. Yes this needs to be flashed before the process begins, the script wont run with the stock kernel.*
Here's a link to the eng kernel. Download and extract. Yes flash via ODIN, add the kernel file to the AP slot.*
http://www.mediafire.com/?2i5aeu6pr0ms7io
2. The only file I downloaded and used was this one:
http://www.mediafire.com/?m0b639pfnavjmha
(G920a5.1.1.root.metalcated-v4.zip)
3.Save it and extract it on your PC
4. Verify Samsung drivers and adb are installed
5.***ENABLE USB DEBUGGING*** this is an important step.*
6. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.
7. After it reboots you have root access.
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
Let's work on bootloader unlock so we can flash custom rom, kernel and recoverys.
Thanks to Michael3214 for finding the method.
Thanks to Metalcateds for scripts.

Has anyone tried to push a script to make SELinux permissive on boot? We might be able to unteather the root.
http://forum.xda-developers.com/ver...ipt-permissive-selinux-stock-kernels-t2854364

KillKount said:
Has anyone tried to push a script to make SELinux permissive on boot? We might be able to unteather the root.
http://forum.xda-developers.com/ver...ipt-permissive-selinux-stock-kernels-t2854364
Click to expand...
Click to collapse
I have tried this with no luck. It seams to be something in the kernel that's preventing untethered reboots so far. We can use this root to unlock bootloader with someone who is good enough.

TechNyne66 said:
I have tried this with no luck. It seams to be something in the kernel that's preventing untethered reboots so far. We can use this root to unlock bootloader with someone who is good enough.
Click to expand...
Click to collapse
There are some people looking into this but haven't had much luck as of yet. It also requires a lot of time which I haven't had much of lately. Hope someone else can jump in here as well. [emoji6]

metalcated said:
There are some people looking into this but haven't had much luck as of yet. It also requires a lot of time which I haven't had much of lately. Hope someone else can jump in here as well. [emoji6]
Click to expand...
Click to collapse
Im not sure where to start. If you want to point me in the right direction i could posably help. Flashify does write recovery and kernel just gets blocked by bootloader.

do we have a xposed we can use?

TechNyne66 said:
Im not sure where to start. If you want to point me in the right direction i could posably help. Flashify does write recovery and kernel just gets blocked by bootloader.
Click to expand...
Click to collapse
There is an eng BL out there which allows flashing a recovery img but the signature checks fail so that doesn't work anyhow. Your welcome to try it. I can send you a link for it.

does anyone know whee to get the stock kernel?

This is confirmed working. I rooted, debloated, and unrooted and can now reboot with no worries and no bloat.

bmatney said:
This is confirmed working. I rooted, debloated, and unrooted and can now reboot with no worries and no bloat.
Click to expand...
Click to collapse
how did you unoot?

blane3298 said:
how did you unoot?
Click to expand...
Click to collapse
One of the last options in the settings of supersu is to fully unroot.

do you know if we can unroot and flash the stock kernel and be good to go? My phone was laggy with the eng kernel

metalcated said:
There is an eng BL out there which allows flashing a recovery img but the signature checks fail so that doesn't work anyhow. Your welcome to try it. I can send you a link for it.
Click to expand...
Click to collapse
I would be willing to try bootloader if it will work on OGG firmware.

Has anyone tried this on PB2 ?
Sent from my SGH-M919 using XDA Free mobile app

dpwguenther said:
Has anyone tried this on PB2 ?
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
Yes the kernel required to root other builds is the PB2 ENG

Can I use this on my s6 active? Thanks in advance.

blane3298 said:
do you know if we can unroot and flash the stock kernel and be good to go? My phone was laggy with the eng kernel
Click to expand...
Click to collapse
I performed the root. At the beginning yes it was laggy but i went ahead download (NO-frills CPU) base level has been 1.2GHZ max 1.5GHZ. Power-save mode ON and ZENUI launcher. AND my friends have been happy every since. NO lag at all.

TechNyne66 said:
​My knox was not tripped.
​Highly recommend to have a odin firmware!
Tested on 5.1.1
A not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated*posted a script that does push SuperSU into system/. This was originally posted in the atat GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1. Yes this needs to be flashed before the process begins, the script wont run with the stock kernel.*
Here's a link to the eng kernel. Download and extract. Yes flash via ODIN, add the kernel file to the AP slot.*
Link 1 https://mega.nz/#!lZhwxB4Q!pdBsM51Do...d4l8ANPqTKVc9E
Link 2 http://www.mediafire.com/?2i5aeu6pr0ms7io
2.Metalcateds thread is here:
http://forum.xda-developers.com/att-...-snag-t3334546
3. The only file I downloaded and used was this one:
https://www.androidfilehost.com/?fid=24438995911977129
(G920a5.1.1.root.metalcated-v4.zip)
4.Save it and extract it on your PC
5. Verify Samsung drivers and adb are installed
6.***ENABLE USB DEBUGGING*** this is an important step.*
7. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.*
8. After it reboots you have root access.*
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
Let's work on bootloader unlock so we can flash custom rom, kernel and recoverys.
Thanks to Michael3214 for finding the method.
Thanks to Metalcateds for scripts.
Click to expand...
Click to collapse
Fix your links.
First, link 1. goes to an encrypted file on Mega.
Second this link https://www.androidfilehost.com/?fid=24438995911977129 doesn't link to the Root script but links out to metalcated's debloated system image for the S6.
Edit: Well that was quick to brick my phone haha. Script finished, phone rebooted to AT&T logo, script failed and now its soft bricked XD haha.
Guess it's time to ODIN.

TechNyne66 said:
​My knox was not tripped.
​Highly recommend to have a odin firmware!
Tested on 5.1.1
A not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated*posted a script that does push SuperSU into system/. This was originally posted in the atat GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1. Yes this needs to be flashed before the process begins, the script wont run with the stock kernel.*
Here's a link to the eng kernel. Download and extract. Yes flash via ODIN, add the kernel file to the AP slot.*
Link 1 https://mega.nz/#!lZhwxB4Q!pdBsM51Do...d4l8ANPqTKVc9E
Link 2 http://www.mediafire.com/?2i5aeu6pr0ms7io
2.Metalcateds thread is here:
http://forum.xda-developers.com/att-...-snag-t3334546
3. The only file I downloaded and used was this one:
https://www.androidfilehost.com/?fid=24438995911977129
(G920a5.1.1.root.metalcated-v4.zip)
4.Save it and extract it on your PC
5. Verify Samsung drivers and adb are installed
6.***ENABLE USB DEBUGGING*** this is an important step.*
7. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.*
8. After it reboots you have root access.*
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
Let's work on bootloader unlock so we can flash custom rom, kernel and recoverys.
Thanks to Michael3214 for finding the method.
Thanks to Metalcateds for scripts.
Click to expand...
Click to collapse
i believe THIS >>> https://mega.nz/#!lZhwxB4Q!pdBsM51DoMOvgaQ4j4saZKRCezTWFd4l8ANPqTKVc9E <<< was the link you where looking for for the ENG. Kernel..... N920A.7z i have the root script also downloaded
i will post all in an index file with a site to follow

JeSTeRH4CK3D said:
i believe THIS >>> https://mega.nz/#!lZhwxB4Q!pdBsM51DoMOvgaQ4j4saZKRCezTWFd4l8ANPqTKVc9E <<< was the link you where looking for for the ENG. Kernel..... N920A.7z i have the root script also downloaded
i will post all in an index file with a site to follow
Click to expand...
Click to collapse
Will fix in a bit just making my family dinner.