Database Develop

[q] help restoring to stock

Ok so I rooted my galaxy note3(about a month ago), but today when I turned it on the phone instantly installs a new update without my permission and takes away my root. This would be fine, but now my phone says "custom" when booting up and it is not rooted anymore. How would I be able to take away the "custom" boot image? I am seriously considering selling att GN3 at this point(tired with ATT bs and lack of any info on updates) and opting for a nexus 5. My only problem is that people will be turned off by my previous evidence of rooting my device because it says "custom". I essentially would like to return my phone to all stock settings.

nigerson said:
Ok so I rooted my galaxy note3(about a month ago), but today when I turned it on the phone instantly installs a new update without my permission and takes away my root. This would be fine, but now my phone says "custom" when booting up and it is not rooted anymore. How would I be able to take away the "custom" boot image? I am seriously considering selling att GN3 at this point(tired with ATT bs and lack of any info on updates) and opting for a nexus 5. My only problem is that people will be turned off by my previous evidence of rooting my device because it says "custom". I essentially would like to return my phone to all stock settings.
Click to expand...
Click to collapse
Try simply rebooting. That worked for me after unrooting via odin one click on mi9. The first boot showed custom wich confused me but after just a reboot it went away. I think it softbooted after odin and didnt run through the whole process.
If not then the only option currently to remove custom is to re root using kingo then use xposed to fake custom system status. The latter would be shady however if you plan to sell the device.

powdered_donuts said:
Try simply rebooting. That worked for me after unrooting via odin one click on mi9. The first boot showed custom wich confused me but after just a reboot it went away. I think it softbooted after odin and didnt run through the whole process.
If not then the only option currently to remove custom is to re root using kingo then use xposed to fake custom system status. The latter would be shady however if you plan to sell the device.
Click to expand...
Click to collapse
Sorry to bother you, but I am not too familiar with how to do this. Would you be able to show me some sort of step-by-step guide which I would be able to use? Also how do I check if I'm on mi9 and not something else(because I currently have the most updated firmware on my phone)

http://forum.xda-developers.com/showthread.php?t=1574401QUOTE=nigerson;47504941]Sorry to bother you, but I am not too familiar with how to do this. Would you be able to show me some sort of step-by-step guide which I would be able to use? Also how do I check if I'm on mi9 and not something else(because I currently have the most updated firmware on my phone)[/QUOTE]
The most updated is mj5 if you took the ota update that hit recently. You can check by going to settings then about phone then look at the last 3 digits of the baseband.
To install xposed go to the link at the top it pasted there on my tablet for some reason. Instructions are there for installation.
download the xposed installer apk. You must be rooted. Use kingoapp for that if necessary. Open xposed installer and go to framework. Install the most recent framework. Then go to download. Download cosmetic device status normal modification. Use that to remove the custom padlock. Reboot. Hit thanx

powdered_donuts said:
http://forum.xda-developers.com/showthread.php?t=1574401QUOTE=nigerson;47504941]Sorry to bother you, but I am not too familiar with how to do this. Would you be able to show me some sort of step-by-step guide which I would be able to use? Also how do I check if I'm on mi9 and not something else(because I currently have the most updated firmware on my phone)
Click to expand...
Click to collapse
The most updated is mj5 if you took the ota update that hit recently. You can check by going to settings then about phone then look at the last 3 digits of the baseband.
To install xposed go to the link at the top it pasted there on my tablet for some reason. Instructions are there for installation.
download the xposed installer apk. You must be rooted. Use kingoapp for that if necessary. Open xposed installer and go to framework. Install the most recent framework. Then go to download. Download cosmetic device status normal modification. Use that to remove the custom padlock. Reboot. Hit thanx [/QUOTE]
So, I am on mj5 right now since I got the OTA update and I am no longer rooted because of this. How can I flash to stock or reroot and install xposed? Or am I ****ed?
*EDIT USED KINGO INSTALLED FRAMEWORK ALL IS GOOD IN THE HOOD *

[Q] Can I unroot without wiping / back to stock?

Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.

GADGTGUY said:
Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.
Click to expand...
Click to collapse
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.

You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6

the_rooter said:
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.
Click to expand...
Click to collapse
They push a BES client that checks. They already told me they know the phone is rooted. (big brother)
jj14 said:
You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6
Click to expand...
Click to collapse
Thanks for this info....
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.

GADGTGUY said:
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
It may - but it still won't get you direct OTA (since OTA now checks for any change to system files)

GADGTGUY said:
[snip]I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
Just to echo what jj14 said. The "Full unroot" option in SuperSU will remove root, but it won't (at least it hadn't on the last version of it that I tried) revert one file that root modifies, so, while you won't have root, and the BES client should work, the update checks the entire file system, so it will fail. A quick flash of only the system.img file using fastboot will remove root and leave everything else untouched.

Thanks for all the advice guys!
I appreciate the assistance... this is why this community rocks!
D.

I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.

GADGTGUY said:
I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.
Click to expand...
Click to collapse
Many of us would recommend you learn fastboot commands manually rather than relying on toolkits. This helps you get out of trouble when things go wrong. That said, its too late now

root/install custom rom without PC/Odin.

For those who do not have access to a computer I achieved root on Kit Kat without a PC by following these steps :
All needed items will be linked below.
Root device using kingroot (will not trip Knox) if you are only wanting root for basic root apps (greenify etc.) then this is all you need to do. Have fun! (Just remember anything that changes the /system partition significantly such as xposed will trip Knox.)
To install superSU instead of kingroot/kinguser (will trip Knox)
Install flashify from the play store
Use flashify to install twrp (this step trips Knox)
Download SuperSU zip
Remove kingroot and the included kinguser app (follow instructions from kingroot thread)
Reboot into recovery and install SuperSU zip
OR :
After installing twrp just download a ROM (and if needed gapps) of your choice and flash.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461 for kingroot English.
https://play.google.com/store/apps/details?id=com.cgollner.flashify flashify play store link
For SuperSU zip google is your friend

hotrodwinston said:
For those who do not have access to a computer I achieved root today without a PC by following these steps :
Root device using kingroot (will not trip Knox)
(Tablet is now technically rooted but most people prefer SuperSU and to not have incompletely translated apps controlling root access)
Install flashify from the play store
Use flashify to install twrp (will trip Knox)
Download SuperSU zip
Remove kingroot and the included kinguser app
Reboot into recovery and install SuperSU zip
OR :
After installing twrp just download a ROM (and if needed gapps) of your choice and flash.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461 for kingroot English.
For SuperSU zip google is your friend
Click to expand...
Click to collapse
You've just negated the whole point of using kingroot, not tripping Knox.
You could have simply rooted using twrp or cfauto root without kingroot at all. I know it saves connecting to a PC, but that is trivial.
Kinguser supersu app is fully English and has no problems as a supersu replacement. I used it for months.

ashyx said:
You've just negated the whole point of using kingroot, not tripping Knox.
You could have simply rooted using twrp or cfauto root without kingroot at all. I know it saves connecting to a PC, but that is trivial.
Kinguser supersu app is fully English and has no problems as a supersu replacement. I used it for months.
Click to expand...
Click to collapse
Some people don't have a PC - this method would let them install custom roms or install xposed without needing a PC.

hotrodwinston said:
Some people don't have a PC - this method would let them install custom roms or install xposed without needing a PC.
Click to expand...
Click to collapse
I agree but then you stated about flashing supersu and twrp which would trip Knox and sort of made the first part of your informative post pointless, that's all.
Also flashing roms will also trip Knox, so again negates the point of rooting with kingroot.

ashyx said:
I agree but then you stated about flashing supersu and twrp which would trip Knox and sort of made the first part of your informative post pointless, that's all.
Also flashing roms will also trip Knox, so again negates the point of rooting with kingroot.
Click to expand...
Click to collapse
I see your point - will modify the op to reflect different goals of rooting - my use of kingroot was to obtain root knowing I was going to trip Knox to install a custom rom as I do not have a PC to run Odin.

Kingroot does not work on lollipop. Don't want to trip Knox. Is there any other way to root? Not flashing any rom BTW.

If you have a computer and can downgrade to 4.4 kingroot should work then

djide said:
Kingroot does not work on lollipop. Don't want to trip Knox. Is there any other way to root? Not flashing any rom BTW.
Click to expand...
Click to collapse
I had never heard of that tool. Did it work well on KK ? Looks like there are newer versions that could work with Lollipop. My only concern is that it is all in Chinese and I don't know how reliable it is

I saw in another thread that someone had success using KIng Root on the AT&T variant. I have tried several times and on several different days, but as of yet King Root will not work for me on the SM-T807V. This is the Verizon variant. Some folks have speculated that King Root might work on Lollipop if you have the Exynos chip and not the Snapdragon. Unfortunately, or fortunately, for me, I have the Verizon with the different chip. I believe I also read that Sprint variants also have Snapdragons.

Elbrin said:
I saw in another thread that someone had success using KIng Root on the AT&T variant. I have tried several times and on several different days, but as of yet King Root will not work for me on the SM-T807V. This is the Verizon variant. Some folks have speculated that King Root might work on Lollipop if you have the Exynos chip and not the Snapdragon. Unfortunately, or fortunately, for me, I have the Verizon with the different chip. I believe I also read that Sprint variants also have Snapdragons.
Click to expand...
Click to collapse
Sprint does have snapdragon, but their bootloaders are unlocked in which they can flash anything they want. Sucks that kingroot doesn't work onm Verizon
Sent from my SM-T800 using Tapatalk

DUHAsianSKILLZ said:
Sprint does have snapdragon, but their bootloaders are unlocked in which they can flash anything they want. Sucks that kingroot doesn't work onm Verizon
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
I'm not sure whether the failure for it to work is the exploit itself or user error.
It has worked both on my exynos tab s t805 and my snapdragon m8.
Both running kitkat.
Earlier versions have worked on other devices I own.
I can't see what would be different exploit wise with the Verizon device.
It took me a few goes for the exploit to work and most importantly the device will reboot at least once and then continue the exploit, so must not be touched after the reboot.
My advice here is to set the screen timeout to at least 10 mins, so it can be monitored after it reboots.
Also it needs to be kingroot v4. Another point is that if the app root fails then it's worth trying the desktop version as, from past experience, this has worked when the app hasn't.

Yes but in my opinion the app is interesting because it makes it possible to keep the Knox counter at 0×0. Using the desktop version installs another recovery and triggers Knox. But it looks like the team is working hard to make it functional for devices on lollipop. I hope we will see progress for the tab s

I have tried both the desktop and the mobile version and both met with the same results -no root. The common thought now seems to be, from my readings, is that Verizon has a locked bootloader which might be more of the issue versus the difference in the chip. Oh well, I will just have to be patient with Tab S and just enjoy my rooted S6 Edge.
Sent from my SM-T807V using XDA Free mobile app

Elbrin said:
I have tried both the desktop and the mobile version and both met with the same results -no root. The common thought now seems to be, from my readings, is that Verizon has a locked bootloader which might be more of the issue versus the difference in the chip. Oh well, I will just have to be patient with Tab S and just enjoy my rooted S6 Edge.
Sent from my SM-T807V using XDA Free mobile app
Click to expand...
Click to collapse
The bootloader is irrelevant as the exploit doesn't involve the bootloader. Not only that it works on the bootloader locked att model.

Keep root after update ??
hello just wondering if after king root gains root would I be able to update from Samsung update in settings ? And if It does let us update from setting will it remove or patch over the root exploit..! Thanks...
-Ahmed- smt700 (wifi 0nly)

As far as Knox is not tripped, I believe you should but you will lose root in the process.
Sent from my SM-T700 using Tapatalk

djide said:
Kingroot does not work on lollipop. Don't want to trip Knox. Is there any other way to root? Not flashing any rom BTW.
Click to expand...
Click to collapse
Downgrade to kitkat, root with king root then flash lollipop stock official fw with flashfire, with injects supersu option
Really kingroot works?

Joker87 said:
Downgrade to kitkat, root with king root then flash lollipop stock official fw with flashfire, with injects supersu option
Really kingroot works?
Click to expand...
Click to collapse
I have not read any posts from anyone that has been able to root a VERIZON (caps used for emphasis ) Tab S (SM-T807V) with King Root or Kingo.
Sent from my SM-T807V using XDA Free mobile app

Op updated with more info regarding different steps if you just want root or want to go further and install xposed or custom Roms.
Sorry for taking so long to update - real life got in the way.

Has anyone found a method to replace kingroot with supersu without tripping Knox? I have tried the same steps that worked on my s6 on here and that didn't work. Worked only right after completing the process but when I reboot I lost root.

[GUIDE] How to root without tripping knox - Kitkat and Lollipop, Locked bootloader

I take no responsibility for what happens to your device if you follow this guide. Rooting or modifying carries risks, however I have tested this procedure many times with 100% success on my SM-t805. It should work for any device, but I can't confirm, so feedback please if it works for your device.
1. Firstly you need to downgrade your device to a XXU1ANF8 or earlier firmware suitable for your particular model. This is available at http://samsung-updates.com/ or you can use this one XSG-T805XXU1ANF8-20140625 which is for the T805 model only.
https://www.androidfilehost.com/?fid=23501681358555496 T800 only
Download and then install the firmware on your device with ODIN.
If you are still on Kitkat then there is no need to wipe the data partition. However if you are running Lollipop after successful installation you will need to boot into recovery POWER + HOME + VOL UP then select WIPE DATA/RESET -
YOU WILL LOSE ALL YOUR USER DATA SO BACK UP ANYTHING YOU NEED TO THE SD CARD FIRST!
NOTE: IF THE INSTALL FAILS AT HIDDEN.IMG OR CACHE.IMG SIMPLY BOOT INTO RECOVERY AFTERWARDS AND WIPE CACHE THEN CARRY ON WITH THE REST OF THE PROCEDURE.
2. Once booted into Android, set up your wifi and google account and skip everything else (this wont be needed if you didn't wipe the data partition)
3. Next we need to install a Few apps, so go ahead and install these apps from Play Store:
System app remover(root)
Root Validator
Terminal Emulator For Android
KINGROOT 4.1
Kingroot updates and earlier versions if posted version doesn't work:
http://androidxda.com/download-kingroot-application
Kingroot 4.5 (latest version)
We also need to download the package from this LINK
4. Using the built in File Manager extract the zip package to your internal SD card. Once extracted, inside the extracted folder is another folder called MRW.
THIS FOLDER NEEDS TO BE MOVED TO THE ROOT OF YOUR INTERNAL SD CARD OR THIS WON'T WORK.
5. Next go to Settings set your display timeout to 10 mins.
Now Run KINGROOT then wait for it to do it's thing. If it reboots part way through the process then after rebooting unlock your device, but don't touch anything for a couple of mins. The app should restart and continue. If you are successful you can move to the next step. If not, exit the app and run it again, it may take several attempts before you eventually achieve root.
6. After success uninstall the KINGROOT app (NOT KINGUSER) (not required with v4.5) and the other blue app with Chinese writing.
Now reboot - DO NOT RUN THE KINGUSER APP
7. Let your device fully boot then run the Terminal Emulator and wait for the command prompt
NOTE: IF AT ANY POINT YOU SEE A POP UP BOX WITH CHINESE WRITING ASKING YOU TO UPDATE THE KINGUSER APP SELECT CANCEL.
Now type or copy and paste the following command into the Terminal window:
su
It will ask for root permission, so select ALLOW.
Without closing the terminal emulator window, hit the HOME button and run the SYSTEM APP REMOVER app. (The app is red and simply called UNINSTALL)
The app will ask for root permission, hit ALLOW.
Look for the KINGUSER app then select it and uninstall it. Exit from the app.
Re-open the terminal emulator window and type the following:
sh /sdcard/mrw/root.sh
This will run a script, you will see a bunch of warnings, just ignore them .At then end of the script the SUPERSU app will run.
8. Hit CONTINUE then NORMAL.
Next you may see another message that 'Samsung knox has been detected'. When you see this message select CANCEL.
Once completed you should see a message saying that installation has been successful. Hit OK.
If you see the message again 'Samsung knox has been detected' select CANCEL then exit the SUPERSU app.
9 . Now check with ROOT VALIDATOR that you have root and everything looks ok.
DO NOT REBOOT.
The root is only temporary, if you reboot you will lose root.
10. The next step is to install our ROM of choice with Flashfire.
For more info on FLASHFIRE see here: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
11. Run FLASHFIRE and grant it root.
12. Agree to the disclaimer and then hit the Red circle with a white +.
Next select 'Flash firmware package' and then navigate to the firmware you want to install (in this case the stock tar package) and select it.
Wait until it finishes scanning the archive.
Next you will see the list of partitions to be flashed, all that is really required is BOOT, RECOVERY and SYSTEM. You can flash the others if you wish.
When you're happy hit the TICK and then you will see a list of what will be flashed. If you tap any one of them you will be able to change the options. Tap the REBOOT option then select DOWNLOAD from the list. This is so we can boot into download mode after the flashing process to flash the Lollipop BOOTLOADER. If not upgrading to lollipop just select REBOOT
I'd advise to leave the rest as is and then hit FLASH
NOW WATCH CHAINFIRES MAGIC!
13. After reboot it should boot directly into DOWNLOAD mode or REBOOT if not updating to Lollipop.
If updating to Lollipop we need to flash a Lollipop BOOTLOADER. I have provided a link below for the T800 and T805. If you have a T700/705/T807/T707 or if the ones provided don't work then you will have to extract it from the Lollipop stock ROM and then TAR it up.
T800XXU1BOCC_BOOTLOADER.tar
T805XXU1BOCC_BOOTLOADER.tar
Latest T800 boot loader thanks DUHasian skillz.
T800XXU1BOE3 bootloader
Flash the BOOTLOADER with ODIN.
If successful then after reboot you should have a rooted version of Lollipop or whatever rom you decided to install and an untripped Knox counter(hopefully)
Good luck and please give feed back.
If you wish you can give feedback to Chainfire at the link posted at the beginning of this post.
NOTE: If you wish to change roms or update and wish to keep root you will have to use the same procedure with Flashfire.
Also note that if you flash a custom KERNEL or BOOTLOADER then it may trip KNOX. Custom ROMs with stock KERNEL and BOOTLOADER should be OK(but don't hold me to that)
CREDITS TO CHAINFIRE FOR FLASHFIRE AND SUPERSU, KINGTEAM FOR ROOT AND WOLFDROID FOR THE KINGROOT REMOVAL SCRIPT.

My god I've been waiting for a thread like this one for a long time.
I don't have time to try it today but I'll give you feedback in a day or two.
Feedback here http://forum.xda-developers.com/showpost.php?p=61296003&postcount=12
Moderators, this thread should be sticked

Just so that I understand the limits of this method I need to ask. Is this method specific to achieve rooted (SuperSU) Lollipop 5.0.2 without tripping Knox or can further changes be made? For example:
1) Remove system apps (removing bloat).
2) Adding system apps such as Viper4Android, busybox, which must be installed in /system/priv-app
3) The Lollipop/Samsung compatible XPosed framework and modules
4) Installing a Tab S model compatible recovery (e.g. TWRP) as I would really like nandroid backups.
I only ask as in the Tab S Kingroot thread there was a post which mentioning that despite Kingroot having successfully achieved root without tripping Knox if you messed with the /system partition files there was the possibility of tripping Knox.
The comment in step 12 "... then navigate to the firmware you want to install ..." suggests that you could install one of the model compatible custom ROMs (e.g. CM). Is that a correct assumption or right now are you restricted to Lollipop stock? Some of those ROMs are from Lollipop 5.1.1 AOSP source (e.g. CM 12.1) which may be going too far with this method and still not trip Knox.
One last question, if I did implemented this could I go back to a pure unrooted stock kitkat/lollipop using Odin or Flashfire without tripping Knox? Odin would be fine.
I greatly appreciate the effort and quality of your post. I had hoped that a "Knox off" SuperSU lollipop root would be found for my month old Tab S 10.5 as I'm used to the low risk flashing on the Nexus devices and have had a mean itch to root without obvious risk to my warranty.
Thanks again

This method can be used to root any Rom.
Once you have root you can practically do what you please.
As for tripping Knox if you mess with the system partition, that's the whole point of root it already messes with the system partition. It shouldn't trip Knox, but never say never.
Just ensure once you have root you remove everything Knox related.
I can't confirm if a custom Rom will trip Knox, but as already stated as long as the bootloader and kernel are stock I believe it won't trip Knox.
Custom recovery may trip Knox.
You can go back to stock any time you wish.

ashyx, as I'm a Linux user its taken me a while to set up a Windows machine but I finally have KIES working and Odin recognizing my Tab S. Now I'm doing my "read your how-to OP twice and root once" prework, but I'm left with a bit of confusion. In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
I apologize if this is a noob question but I just want to get things right and avoid a bricked device especially when the bootloader is involved. At this point I'm only looking to remove bloat and add specific apps that require root so rooted stock is good enough but I'll be in position to try a custom ROM if I feel the need.
Thanks again

3DSammy said:
ashyx, as I'm a Linux user its taken me a while to set up a Windows machine but I finally have KIES working and Odin recognizing my Tab S. Now I'm doing my "read your how-to OP twice and root once" prework, but I'm left with a bit of confusion. In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
I apologize if this is a noob question but I just want to get things right and avoid a bricked device especially when the bootloader is involved. At this point I'm only looking to remove bloat and add specific apps that require root so rooted stock is good enough but I'll be in position to try a custom ROM if I feel the need.
Thanks again
Click to expand...
Click to collapse
Good question. DO NOT flash bootloader in step 12 (newer bootloader) as Knox is likely to be tripped when you flash the 4.4.2 bootloader via odin in step 13. That was the instruction in Mobile odin (which could not flash bootloader). Flashing bootloader in step 12 is redundant.
shayind4

shayind4 said:
Good question. DO NOT flash bootloader in step 12 (newer bootloader) as Knox is likely to be tripped when you flash the 4.4.2 bootloader via odin in step 13. That was the instruction in Mobile odin (which could not flash bootloader). Flashing bootloader in step 12 is redundant.
shayind4
Click to expand...
Click to collapse
Firstly, nowhere does it state to flash the kitkat bootloader on a lollipop Rom in step 12 or 13.
By step 13 you should be running a lollipop Rom.
Secondly Knox should not trip when flashing a stock bootloader. The bootloader can be flashed independently in Odin.
Lastly Flashfire does NOT flash bootloaders.
If you don't flash the bootloader your Rom won't boot.
I suggest you digest the guide again.

3DSammy said:
In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
Click to expand...
Click to collapse
It doesn't state to flash the boot loader in step 12? :what:
Your boot loader will be replaced when you downgrade to kitkat via Odin.
You need to reflash the lollipop boot loader after using Flashfire to install your Lollipop Rom or it won't boot.

Do i need to use a prerooted rom with flashfire, to maintain root, or can i just flash any original samsung room even if its not prerooted?

Paddiii said:
Do i need to use a prerooted rom with flashfire, to maintain root, or can i just flash any original samsung room even if its not prerooted?
Click to expand...
Click to collapse
No, this is the whole point of the post. Flashfire will root for you.

ashyx said:
It doesn't state to flash the boot loader in step 12? :what: ...
Click to expand...
Click to collapse
My bad, I saw the word "Boot" in step 12 and incorrectly assumed that was referring to a bootloader image.
Thanks for correcting me and your patience.

Sorry for being so long to give the feedback I promised.
I have one thing to say: thank you ! Your method works perfectly ! I am now running stock samsung lollipop on my T800 with knox untripped (0x0).
Little thing: your 4.4 file for the T800 isn't working (something wrong when flashing for the Hidden img). I took the same file but in XEF (I'm in France).
I just have a few questions now that could help other users:
-You say you are not sure about flashing another rom as long as it is with stock kernel and bootloader. But on a scale from 0 to 10 how sure are you about it working ? (I know you don't have any responsability in what happens, I just want a piece of advice).
- If for any reason I want to go back to stock, I just need to reflash the firmware with Odin ?
-Can I uninstall apps like the knox related ones without any risk about tripping knox ? (I think it is okay) (Edit: Ok I did it and knox not tripped. I used this tool http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 that is very convenient for that purpose )
Again thank you for this tutorial !

bibihub said:
Sorry for being so long to give the feedback I promised.
I have one thing to say: thank you ! Your method works perfectly ! I am now running stock samsung lollipop on my T800 with knox untripped (0x0).
Little thing: your 4.4 file for the T800 isn't working (something wrong when flashing for the Hidden img). I took the same file but in XEF (I'm in France).
I just have a few questions now that could help other users:
-You say you are not sure about flashing another rom as long as it is with stock kernel and bootloader. But on a scale from 0 to 10 how sure are you about it working ? (I know you don't have any responsability in what happens, I just want a piece of advice).
- If for any reason I want to go back to stock, I just need to reflash the firmware with Odin ?
-Can I uninstall apps like the knox related ones without any risk about tripping knox ? (I think it is okay) (Edit: Ok I did it and knox not tripped. I used this tool http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 that is very convenient for that purpose )
Again thank you for this tutorial !
Click to expand...
Click to collapse
The hidden.img failure is because its carrier/region related.For some it will flash ok, for others it will fail. It isn't actually required at all. Even if it fails to flash the rest of the Rom will.
All that needs to be done after that failure is to wipe cache in recovery.
As regards flashing custom roms. Remember your Rom is already custom as you have modified it.
I would say a good chance custom stock roms won't trip Knox as long as it's build properties reflect its a stock Rom.
However something like Cyanogen probably would trip Knox as its not based on stock.
I won't say this is for sure, but I think it's the general consensus.

Over one thousand views and literally only one person has bothered posting feed back.

ashyx said:
Over one thousand views and literally only one person has bothered posting feed back.
Click to expand...
Click to collapse
OK now two. I successfully applied your instructions yesterday. I really appreciate your guide.
What I did, differently is flashed with Odin using a Virtualbox Windows guest VM from my Ubuntu 14.04 host PC. It took a few days of false starts to get that working. Here is a "[How-To] Linux, Virtualbox and ODIN for your Samsung device", that I just posted to help others who do not have access to Windows machines.
Of the whole procedure the scariest moment was after flashing 4.4.2 stock with Odin over my devices 5.0.2 install. The reboot was too fast for me to get into recovery to wipe user data. I could not power off the SM-T800 and holding POWER + VOL DOWN just rebooted where it would hang displaying "SAMSUNG".
Booting into recovery ( POWER + VOL UP + HOME) had no effect what so ever. Finally I found that if I was fast enough I could reboot (POWER + VOL DOWN) and as soon as the screen went blank hold down the "POWER + VOL UP + HOME" buttons, then the tablet booted into recovery where wiping user data worked as described in your guide.
After completing your guide I am on stock Android 5.0.2 with Knox 0x0000.
My root apps so far:
Busybox
Titanium backup
GMD Gestures.
ES File Explorer with RW access to all partitions
System Uninstall Pro
Universal init.d
See Update below: "Unfortunately so far Viper4Android is not working as I cannot get SELinux permissive enabled either by the SELinux app or an init.d shell script using the "setenforce 0" command. From what I've read that is due to the Samsung stock bootloader."
V4A now works, see: "[HOW-TO] Installing Viper4Android (V4A) Audio on a Lollipop Tab S"
I took the high road and only froze the following KNOX related apps using titanium backup:
com.sec.enterprise.knox.attestation
KLMS Agent
KNOX
KNOX
KNOX II
KNOX SetUpWizardClient
So far I debloated 117Mgs of other apps using System Uninstall Pro. I bought the pro version of Flashfire just to show respect for Chainfire's development efforts. I have not tried to see if Flashfire's backups can be successfully restored yet.
Thanks again for your guide.:good:

Thanks for the feedback, it's constructive and encouraging for others to know It's successful.
For future reference you can disable auto reboot in Odin then manually reboot with POWER + VOL DOWN + HOME then as soon as it restarts switch to VOL UP while continuing to hold the other buttons.
The above procedure can be used at any point and will restart the device and get you into recovery every time.

just registered to suport OP, it works
I thought I did not need to run the su script as I could use kinguser w/o problems. But the flashfire is not compatible with other kinguser. Hope chainfire could remove this restriction. Maybe there is another way to flash rom or other mobile odin alternatives.
The OP could add a link about how to use odin for newbies like me. The odin 3.10 have different wording than previous version.
One more thing to mention is that the kingroot will work if you downgrade. I was in kitkat XXU1ANFB which is only one version up. The kingroot failed 20 times. XXU1ANF8 only takes 3 times to work.
After debloating in lolipop, the system is not smoother than before. The display has less contrast and dimer than kitkat. I did not wipe data/cache so my setting stays the same.
I rooted only for better battery performance as charging will take 10+ hours and could not hold charge at use with power cord plugged. It seems that the performance is not improved for this device after debloating.

vancities said:
I thought I did not need to run the su script as I could use kinguser w/o problems. But the fireflash is not compatible with other root authorization app. Hope chainfire could remove this restriction. Maybe there is another way to flash rom or other mobile odin alternatives.
The OP could add a link about how to use odin for newbies like me. The odin 3.10 have different wording than previous version.
One more thing to mention is that the kingroot will work if you downgrade. I was in kitkat XXU1ANFB which is only one version up. The kingroot failed 20 times. XXU1ANF8 only takes 3 times to work.
After debloating in lolipop, the system is not smoother than before. The display has less contrast and dimer than kitkat. I did not wipe data/cache so my setting stays the same.
I rooted only for better battery performance as charging will take 10+ hours and could not hold charge at use with power cord plugged. It seems that the performance is not improved for this device after debloating.
Click to expand...
Click to collapse
I'm not quite sure what you're saying, but I think youre saying you had success?
Regarding Odin, it is not the intention of this post to spoon feed every single step, some knowledge is expected prior to following this guide. Anything relating to the actual process in this guide is explained in detail. Any other information you would ever require is already posted on XDA.

ashyx said:
I'm not quite sure what you're saying, but I think youre saying you had success?
Regarding Odin, it is not the intention of this post to spoon feed every single step, some knowledge is expected prior to following this guide. Anything relating to the actual process in this guide is explained in detail. Any other information you would ever require is already posted on XDA.
Click to expand...
Click to collapse
I had success. What I mean is the step 6 7 8 9 are not necessary if flashfire could work with kinguser.
Also kingroot only works on XXU1ANF8 and maybe lower. I mentioned this because in other thread about kingroot, someone got success but most did not.

So my feedback . everything was great , was a little confused about Odin at first but like you said everything can be found on xda. Need to be on the most recent Odin which I believe is 3.10. Kingroot took forever to root but I believe it has something to do with connectivity to the servers. So my tab s is rooted no Knox counter. I'm hoping the custom tw rom doesn't revert all the hard work ? thanks again op.

Root for people on G920TUVU5EQC2

Okay, so thanks to this thread here: https://forum.xda-developers.com/tmo...t3382856/page6 and the person who did it (to my knowledge) @AZWildcat
Copy & pasted @ktrinh4213
1) Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet -- CF-Auto Root works on all versions of Android thus far. "CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip"
2) Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
3) Download And Install the Samsung USB Driver in your PC.
4) Extract the CF-Auto-Root files in your PC.
5) Go to Settings->About Device->Tap Build Number until Developer Options is unlocked.
6) Go back to Settings-> Developer Options-> Toggle OEM Unlock. This will prevent your device from being soft-bricked (and save you time downloading and reinstalling the OEM ROM).
7) Switch off your Mobile. Enter into Download mode->Volume Down+Home+Power Buttons.
8) After entering into Download Mode it will say Warning Press Volume Up button to continue.
9) Connect Your Mobile With PC via USB Cable.
10) Launch Odin Application.It Will Show the message "ADDED!!!". If you did not get this message Repeat the above steps.
11) After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file. If using Odin 10.x, look for the AP button, and search for the CF-Auto Root file. Select it. Where the messages populate, go to the Options tab. Tick the Auto reboot. THIS WILL TRIP KNOX.
12) Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
13) Reboot again.
You can See the Superuser after the Reboot in your Applications list.
Sorry if I did tagging wrong I usually lurk

Flash TWRP and then the SuperSU ZIP.

Also auto root still work. At least it did on mine phone

britchel said:
Also auto root still work. At least it did on mine phone
Click to expand...
Click to collapse
The baseband isn't listed on Autoroot which is why I've not used it.

Obievil said:
The baseband isn't listed on Autoroot which is why I've not used it.
Click to expand...
Click to collapse
That is the same reason I havent either ;-;

EncryptedCurse said:
Flash TWRP and then the SuperSU ZIP.
Click to expand...
Click to collapse
sorry it has been a long time since i rooted my phone i know how to install twrp and supersu but how does just installing supersu root my phone i thought you had to have a rooted phone to install supersu

britchel said:
Also auto root still work. At least it did on mine phone
Click to expand...
Click to collapse
what was your base?

timspotatochips said:
sorry it has been a long time since i rooted my phone i know how to install twrp and supersu but how does just installing supersu root my phone i thought you had to have a rooted phone to install supersu
Click to expand...
Click to collapse
Super SU does require root. I was confused by his answer as well. I wondered if I could use the latest Base for my phone from Autoroot but I'm not willing to risk it without knowing for sure.

Obievil said:
Super SU does require root. I was confused by his answer as well. I wondered if I could use the latest Base for my phone from Autoroot but I'm not willing to risk it without knowing for sure.
Click to expand...
Click to collapse
Yeah haha well i dont mind testing it in a few weeks and I can let you know unbricking usually isnt hard just flashing stock usually will fix it I was also curious if I could downgrade by flashing stock roms cause i dont care about knox

timspotatochips said:
what was your base?
Click to expand...
Click to collapse
EQC1, I think... the one before this one... there's actually a tread on how to root s6 with mm

britchel said:
EQC1, I think... the one before this one... there's actually a tread on how to root s6 with mm
Click to expand...
Click to collapse
oh okay do you have the link please and thank you ))?

timspotatochips said:
Yeah haha well i dont mind testing it in a few weeks and I can let you know unbricking usually isnt hard just flashing stock usually will fix it I was also curious if I could downgrade by flashing stock roms cause i dont care about knox
Click to expand...
Click to collapse
My phone is out of contract so I don't care about knox anymore, It's been so long I am still a little afraid of bricking it. the last phone I rooted was the Galaxy S3, believe it or not lol!

Obievil said:
My phone is out of contract so I don't care about knox anymore, It's been so long I am still a little afraid of bricking it. the last phone I rooted was the Galaxy S3, believe it or not lol!
Click to expand...
Click to collapse
oh dang last phone I rooted was my nexus 6 and knox is useless im sure you can still encrypt your phone without it and well samsung pay is ass and you can get a new kernal for fingerprint scanner if it no longer works but ill let you know if I am able to root my phone I assume youre on the same firmware as me?

timspotatochips said:
oh dang last phone I rooted was my nexus 6 and knox is useless im sure you can still encrypt your phone without it and well samsung pay is ass and you can get a new kernal for fingerprint scanner if it no longer works but ill let you know if I am able to root my phone I assume youre on the same firmware as me?
Click to expand...
Click to collapse
Yes I am, it's how I landed on this thread.

Obievil said:
Yes I am, it's how I landed on this thread.
Click to expand...
Click to collapse
haha i assumed so just wanted to clarify

Just out of stupidity, and morbid curiosity I tried to Autoroot the last known good rom from that site. And it failed with a FRP lock error message. I'm surprised it didn't brick.

Hey why don't you make your own rom. Pretty easy... you customize it to your like, I made mine and it's pretty stable. And it roots it from pc

britchel said:
Also auto root still work. At least it did on mine phone
Click to expand...
Click to collapse
britchel said:
Hey why don't you make your own rom. Pretty easy... you customize it to your like, I made mine and it's pretty stable. And it roots it from pc
Click to expand...
Click to collapse
I don't think you understand. The rom isn't the issue here, It's getting root access that's the problem.

Okay, so thanks to this thread here: https://forum.xda-developers.com/tm...oot-samsung-galaxy-s6-sm-g920t-t3382856/page6 and the person who did it (to my knowledge) @AZWildcat
Copy & pasted @ktrinh4213
1) Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet -- CF-Auto Root works on all versions of Android thus far. "CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip"
2) Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
3) Download And Install the Samsung USB Driver in your PC.
4) Extract the CF-Auto-Root files in your PC.
5) Go to Settings->About Device->Tap Build Number until Developer Options is unlocked.
6) Go back to Settings-> Developer Options-> Toggle OEM Unlock. This will prevent your device from being soft-bricked (and save you time downloading and reinstalling the OEM ROM).
7) Switch off your Mobile. Enter into Download mode->Volume Down+Home+Power Buttons.
8) After entering into Download Mode it will say Warning Press Volume Up button to continue.
9) Connect Your Mobile With PC via USB Cable.
10) Launch Odin Application.It Will Show the message "ADDED!!!". If you did not get this message Repeat the above steps.
11) After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file. If using Odin 10.x, look for the AP button, and search for the CF-Auto Root file. Select it. Where the messages populate, go to the Options tab. Tick the Auto reboot. THIS WILL TRIP KNOX.
12) Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
13) Reboot again.
You can See the Superuser after the Reboot in your Applications list.
Sorry if I did tagging wrong I usually lurk

This worked, I just rooted my device! Thank you for linking this!