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 *

[How-To] Update to I537_OC7 - 5.0.1 and KeepRoot

**You can begin the following process from 4.4.x Build/ROM or higher but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
**Caution!** The following process is only for the I537 AT&T S4 "Active" variant. Use on any other device may result in a hardbrick!
Download:
- I537_OC7_Stock_Rooted_ROM
- I537_OC7_Stock_Rooted_Deodexed_ROM
Pevious Builds:
- I537_OC6_Stock_Rooted_ROM
- I537_OC6_Stock_DeOdexed_ROM
Set your screen timeout setting to 10 mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" setting to "Download."
6. Press the lightning bolt then "Ok" to begin the flash.
7. Once the flash is complete and the device reboots into "Download" mode, flash the I537_OC7_Bootloader using Odin's PDA/AP slot.
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the AT&T splash screen for 1 - 2 minutes (15 - 20mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
Optional - Enable Native Tethering:
- I537_OC7_TetherAddOn
- I537_OC6_TetherAddOn (Flash using FF's "Flash zip or ota" option.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Credits:
@thisisapoorusernamechoice - for capturing the ota update and for his system dump.
@Chainfire

muniz_ri said:
**You can begin the following process from any Build/ROM but you must already have Root Access**
**Attention** The following process is only for the I537 AT&T S4 "Active" variant. Use on any other device may result in a hardbrick!
Instructions:
Click to expand...
Click to collapse
First of all, thank you thank you thank you so much for this. Yeah I grabbed you the OTA's but thanks to you (and of course Chainfire & his FlashFire) we can go from KK to LP with root. And on day one of the OTA. Awesome. :good: So down to business, and I hope I'm not getting ahead of myself or barking up the wrong tree, but hear me out on this one. @Joe-Tech was generous enough to port his regular S4 Google Play Edition (Pure Nexus) 4.4.4 Rom over to our phone. Could we repeat that for this OC6 build, using say, this rom as a base (or another if that turns out to be incompatible for whatever reason)? I doubt I have the expertise to pull that off but if it would help I'd get to work on another masterpatch and speaker phone fix

thisisapoorusernamechoice said:
First of all, thank you thank you thank you so much for this. Yeah I grabbed you the OTA's but thanks to you (and of course Chainfire & his FlashFire) we can go from KK to LP with root. And on day one of the OTA. Awesome. :good: So down to business, and I hope I'm not getting ahead of myself or barking up the wrong tree, but hear me out on this one. @Joe-Tech was generous enough to port his regular S4 Google Play Edition (Pure Nexus) 4.4.4 Rom over to our phone. Could we repeat that for this OC6 build, using say, this rom as a base (or another if that turns out to be incompatible for whatever reason)? I doubt I have the expertise to pull that off but if it would help I'd get to work on another masterpatch and speaker phone fix
Click to expand...
Click to collapse
I have an LP 5.0.1 base, ported using that ROM that you mentioned, but we all know safestrap is not compatible yet with 5.x and FlashFire can only flash TW base rom from my experience, and it still on beta phase, so let just cross fingers, i know something coming soon

Joe-Tech said:
I have an LP 5.0.1 base, ported using that ROM that you mentioned, but we all know safestrap is not compatible yet with 5.x and FlashFire can only flash TW base rom from my experience, and it still on beta phase, so let just cross fingers, i know something coming soon
Click to expand...
Click to collapse
You're the man. Thanks for this info. I'm going to make a masterpatch, hopefully it'll be needed soon. Obviously I'll be happy to test anything if and whenever something like this does happen. If I can do anything at all to help that along just let me know. I was not aware FF could only flash TW base roms, shoot
Still loving your 4.4.4, I'm torn on taking the update if it means going back to touchwiz with no current AOSP option

thisisapoorusernamechoice said:
You're the man. Thanks for this info. I'm going to make a masterpatch, hopefully it'll be needed soon. Obviously I'll be happy to test anything if and whenever something like this does happen. If I can do anything at all to help that along just let me know. I was not aware FF could only flash TW base roms, shoot
Still loving your 4.4.4, I'm torn on taking the update if it means going back to touchwiz with no current AOSP option
Click to expand...
Click to collapse
Only way im thinking to boot the new LP ROM, is to use @muniz_ri method so we can upgrade and keep root. So now we going to be on the OC6 kernel and baseband, since the gpe can boot without flashing the kernel. Then we can flash the GPE 5.x ROM, either with safestrap or FlashFire, and we can also use Odin to flash the stock kernel/partitions. But too bad none of them worked for me after the upgrade, FF will sit there for ever try to get root permission.

Joe-Tech said:
But too bad none of them worked for me after the upgrade, FF will sit there for ever try to get root permission.
Click to expand...
Click to collapse
Were other rooted apps able to get root permission?

thisisapoorusernamechoice said:
Were other rooted apps able to get root permission?
Click to expand...
Click to collapse
Nope I even tried root checker, the su app is there on the app drawer, i was able to updated from the play store, but still wasn't working though.

delete
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app

Joe-Tech said:
Nope I even tried root checker, the su app is there on the app drawer, i was able to updated from the play store, but still wasn't working though.
Click to expand...
Click to collapse
Just had a thought, probably nothing. When doing the kitkat to lollipop update to keep root with flashfire, would it help anything to convert flashfire to a system app before doing the update? Sorry if this is a stupid question

thisisapoorusernamechoice said:
Just had a thought, probably nothing. When doing the kitkat to lollipop update to keep root with flashfire, would it help anything to convert flashfire to a system app before doing the update? Sorry if this is a stupid question
Click to expand...
Click to collapse
I don't think it will make any difference.

@muniz_ri: This is great, thanks for all your work on this. As I understand it, this method will update you to OC6 with root if the original firmware was already rooted. So my question is then, if a user has already taken the OC6 update and would like to root afterwards is it currently impossible? Is the only way to root OC6 to downgrade back to NE3, root, and then follow your instructions to update to OC6 with root?
I'm guessing a root vulnerability hasn't been found for the Samsung 5.0 firmware yet, but I just wanted to check.
Also, I posted this in the other thread, but has anybody actually downgraded from OC6 to NE3 successfully? I don't want to give people wrong information.

Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?

mikelets456 said:
Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?
Click to expand...
Click to collapse
Extract the tar from the rar. Leave the zip as is. Copy the tar and the zip to your phone's internal memory or external SD card, somewhere it'll be easy for you to find

Devo7v said:
@muniz_ri: This is great, thanks for all your work on this. As I understand it, this method will update you to OC6 with root if the original firmware was already rooted. So my question is then, if a user has already taken the OC6 update and would like to root afterwards is it currently impossible? Is the only way to root OC6 to downgrade back to NE3, root, and then follow your instructions to update to OC6 with root?
I'm guessing a root vulnerability hasn't been found for the Samsung 5.0 firmware yet, but I just wanted to check.
Also, I posted this in the other thread, but has anybody actually downgraded from OC6 to NE3 successfully? I don't want to give people wrong information.
Click to expand...
Click to collapse
Correct, you will need to go back to NE3 then use towelroot before starting this process. And yes, the aboot qfuse counter determines whether or not you can downgrade. I checked it and it does allow for downgrading.

mikelets456 said:
Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?
Click to expand...
Click to collapse
If all of the above is beyond your level of understanding I strongly suggest you reconsider attempting to modify your phone.

muniz_ri said:
Correct, you will need to go back to NE3 then use towelroot before starting this process. And yes, the aboot qfuse counter determines whether or not you can downgrade. I checked it and it does allow for downgrading.
Click to expand...
Click to collapse
Great thanks, one more question: Would it be possible to use something similar to W0lfdroids method of rooting? So on stock OC6, flash the NE3 kernel (since downgrading is possible), root with Towelroot, the flash back to the OC6 kernel. Just thinking about it I'm guessing it wouldn't work because you wouldn't be able to boot 5.0 with a 4.4.2 kernel, but I figured I'd ask.

Devo7v said:
Great thanks, one more question: Would it be possible to use something similar to W0lfdroids method of rooting? So on stock OC6, flash the NE3 kernel (since downgrading is possible), root with Towelroot, the flash back to the OC6 kernel. Just thinking about it I'm guessing it wouldn't work because you wouldn't be able to boot 5.0 with a 4.4.2 kernel, but I figured I'd ask.
Click to expand...
Click to collapse
Did not bother to try since it has not worked on any 5.0 release so far.

muniz_ri said:
Did not bother to try since it has not worked on any 5.0 release so far.
Click to expand...
Click to collapse
Any chance I can implore you to try it since there will inevitably be a bunch of people already on the OC6 firmware asking how to root it and will get pissed when they find they have to wipe their phone? Or maybe you could just provide the stock OC6 kernel and I can convince @thisisapoorusernamechoice to give it a shot?

For what it's worth, just went through the process in post 1. Everything went fine, but after the Galaxy S4 boot screen, it goes black and stays. I can boot to download mode and stock recovery, so it's not a major issue, and likely something I did. I'll mess with it a bit more then Odin back to stock and start over.

bobbylx said:
For what it's worth, just went through the process in post 1. Everything went fine, but after the Galaxy S4 boot screen, it goes black and stays. I can boot to download mode and stock recovery, so it's not a major issue, and likely something I did. I'll mess with it a bit more then Odin back to stock and start over.
Click to expand...
Click to collapse
A couple questions:
What firmware were you coming from?
How long did you wait?
Did you have Xposed enabled?

[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.

[Q] First Time Rooter, Gs6 SM-G920T, need help intresting problem cant find fix.

#1-"com.tmobile.pr.adapt (10001) has been granted superuser permissions for an interactive shell" pops up on my screen every 30 seconds on the bottom of my screen in a grey box.
#2- i also noticed that i can accept and recieve calls but i can not hear, nor can the other person hear me. if i use hangouts video call, skype, etc it works fine.
#3-i also tried to get rom manager to make a recovery and it says it needs to get CWD recovery to install a new software, the first thing we need to do is install a up to date version, we will begin that process now... etc.. then it says to get started you must first sset up a custom recovery, it gives two options a samsung galaxy s3 on metro pcs or a samsung previal 2 on boost mobile, or device not listed, when i click that it says "SM-G920T does not have an officially supported CWDR yet. Have you installed a CWD based recovery manually?" so im not sure what to do from there, or if i even need that. i have been a iphone user since day one went to android after reading up a lot on it, although rooting is quite different than jailbreaking it seems, i am incredibly excited to get started if i can get past these little problems and get started and figure everything out. ANY advice, or anwsers to these problems would be Greatly appreciated! thanks!
Also i went to dev options in settings and noticed the "OEM unlocking- allow the bootloader to be unlocker" was turned off, i dont know if this is necessary to root if i did something wrong by not turning it on or what, or if it may fix any problems above if i turn it on now. thanks!
I have a samsung Galaxy S6 (SM_G920T) . i Rooted and did not trip Knox, Although i did just remember that my fingerprint sensor is not working either.
Thank you guys so much this si a incredible forum i have spent hours and hours reading and researching before making this post i appreciate it so much!

#1 Freeze that ****. Use some root tool to freeze that T-mobile apk, seems u gave it root permissions at some point. I believe there are a lot of apps that you will want to do the same.
#2 ? No idea. Stock rom/kernel?
#3 What is this I don't even. Don't do that. Go to TWRP's official web, get your zeroflte (SM-GT920T) twrp and flash it via ODIN, or else get the recovery.img and use flashify. All that assuming you want a custom recovery.
You will need to unlock the bootloader if you are on 5.1.1. I believe locked will prevent changes or wiping anything on the OS partitions, even recovery (can someone confirm?)
I believe jailbraking and rooting should be pretty much similar, if not the same, as both target to grant the user root access to do whatever he pleases on the OS.
Welcome to android btw.

How did you root? Sounds like you used the modified sboot which causes no sounds in calls and nonfunctional fingerprint scanner. If so, flash back to stock and use a different rooting method. The rest, pretty much what the above poster stated

Root
I rooted using the version that I found the only one that works it seemed like, went to Odin put my phone In download mode and then put the boot loader download in BL and the. Put a something unikernel.sbin I believe, whatever the guide said also then it was done. I thought you couldn't use the twrp or custom recovery etc on tmobile one yet but I just read a thing about xtrestolite odex pure v2 which says it's for 5.1.1 and my model of phone but in the guide it says to root using CF auto root and a link there to it but the link doesn't have my phone on the list that the guide that clearly is my phone says to use I don't know if I'm missing something but I want to use it I understand most of it but I don't know if I need to unropt first and re root then use Odin and flash twrp that's supported on my phone then use that to recover the rom. Etc. The kernel that says is used in the guide is the same one I downloaded so do I need to remove it all then let it do that or?
Sorry if this didn't make sense I'm halfway there between confused and understood I have spent the last 10 hours reading and trying to figure this out though lol. Thanks guys!

Also
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?

Just flash the 5.1.1 firmware to return to stock. To root, flash unikernel with Odin. The other method you used was to not trip knox, but as you experienced has side effects. I had to Odin back to 5.1.1 myself. Can't have those issues

thanks!
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?

CjetOKC said:
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
Click to expand...
Click to collapse
Yes, flashing to 5.1.1 works exactly like that. You need to get the version for your model (very important on this one) and then simply place that file in the AP field of ODIN while the device is in recovery mode. It is normal for ODIN to freeze for 2 minutes while verifying. Make sure to use a MD5 checker tool on the firmware before flashing.

Rooting has historically required more technical savvy and balls than jailbreaking, but PingPong made rooting the S6 brain-dead simple. CF-Auto root is still pretty painless, but you must make sure you have the right zip for your device.
Anyhoo, the quickest & easiest way to restore phone calls & fingerprint scan is to use Odin to get back to bone stock.
Next, use PingPong to root. After rooting, "com.tmobile.pr.adapt" will ask for root access. That is T-Mobile's "phone home" app and sends info about your device (probably including root status). Deny it root access and make sure you check "Remember my choice", and it won't bother you again. You will not lose any functionality by denying it root, so terminate that crap.
Don't bother with rom manager. CWM is archaic. If you want a custom recovery, use TWRP. You can install TWRP either using Odin or TWRP Manager app (it's free).
Good luck and have fun with your S6

CjetOKC said:
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Click to expand...
Click to collapse
Are you still rooted? If so, and if you are experiencing the call audio issue, go flash AOU's kernel. He has made a kernel for the tmo s6. that should eliminate your call audio issue. The finger print scanner is the only issue with flashing his kernel. Also, I rooted with the modded sboot, his TWRP and kernel, and I didn't trip knox
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002

[How To] Install TWRP on LG G2, noob friendly guide

Hi,
I made this guide after struggling to install TWRP using several guides on XDA and other forums which fail to mention few other steps needed.
I am using a verizon lg g2 on stock lollipop 5.0.2 , rooted using LG ONE CLICK ROOT. But i guess this guide goes for all g2 variants who cannot simply install twrp on their stock firmware using flashify or autorec.
ISSUE :
I have tried flashify but this app is only useful if you already have an older version of recovery installed since i failed to install any version of twrp and cwm while trying. After installing a twrp , you can flash upgrade recovery using this.
Autorec gives me unresponsive button when tapping on the FLASH TWRP icon.
Other solution requires manual installation such as THIS GUIDE which i haven't tried because i am not that advanced android user yet since i came from using iOS.
The easiest way to install TWRP is autorec but to fix the unresponsive button, follow below steps:
** Ofcourse you need root in order to install custom recovery
1. Install AUTOREC from HERE. There are different app for different g2 variant so install accordingly.
2. Go to SuperSU settings , uncheck " Enable Superuser" and then scroll bottom where you see " reinstall" under CLEANUP section. Tap on that and proceed. Wait few seconds and when done, reboot your device.
3. Go to THIS LINK and download supersu 2.46
4. After its downloaded, tap and install it. Update binary and reboot.
5. Go to autorec, give it superuser permission and tap on the "Flash TWRP" icon and you will see it working.
** note : in order to install latest twrp, you must first install the initial img version and then flash the latest version zip from within. Update link : TWRP 3.0.2-1
Feel free to post below if it worked for you or if you need further assistance.

Help with twrp & flashing rom on g2
I have a rooted G2, ATT W/stock KitKat. At one point when I bought it, it had Lollipop, and TWRP, but I bricked it trying to install Magisk as a workaround to play Pokemon. That began my unwanted journey into the world of rooting, custom recovery, flashing, and the whole bit. I've watched many videos and read many threads but I'm very much a "noob" , and something always goes wrong. I can, and do read instructions but, I have found that usually I don't understand all the slang techy terms, and/or important steps are left out of the tutorials. Most recently, I tried to install TWRP using AutoRec and a YouTube video, and got stuck in TWRP and "soft-bricked".
I started a thread on here asking for help, even offering to donate, and got like 2 short replies saying "flash a custom ROM". Like that explains anything to a newbie.... When I clearly state I'm new at this, that doesn't help. Then today I get notification my thread was moved. Anyway, for a third time, I had to (follow the only YouTube tutorial that has actually worked for me), which just unroots, and puts the device back to a damn factory reset state.
MY GOAL is that I'm bound and determined to at least get Lolliop back on the device. I prefer that over KitKat. I also would love to be able to play Pokemon again, since the a**holes at Niantic blocked rooted phones from playing. Even after I did the factory restore thing and unrooted, the game still wouldn't install, saying "device not compatible". Apparently the Magisk workaround works for some people...
I am getting so frustrated and should just leave well enough alone. Everytime I say I'm not going to mess with it anymore, I end up trying, against my better judgement, and end up bricking.
So one last try.... - If there is anyone out there in XDA land with the ability, or inclination to help, I would greatly appreciate it. I'm not a simpleton, but apparently there are so many things that have to be done precisely, or I get bricked.
If anyone can give simple, step-by-step instructions, leaving nothing out, accounting for anything that might go wrong, provide links that still exist, etc, etc. I will not only be a very happy guy, but my daughter will be happy that she can play Pokemon again, and I will be happy to have Lolliop, or even, dare I dream Marshmallow, and I would GLADLY donate a few bucks to whatever account...
If you've read this far, thanks for that, at least.

it works , thanks man ?
note : I used kingroot to rooting my device .

No dice on AutoRec... do I need a special version?
AutoRec doesn't seem to actually do anything and flashing the recovery through any of the normal programs just leads to an error message when trying to enter recovery. Any ideas?
UPDATE (8:42PM) -
Figured it out! In the SuperSU app, I disabled "mount namespace separation" and "tapjacking protection" before rebooting and trying AutoRec one more time. This enabled the hidden install button behind the lollipop icon in the app and allowed TWRP to be installed instantly. Hooray!

Bill720 said:
AutoRec doesn't seem to actually do anything and flashing the recovery through any of the normal programs just leads to an error message when trying to enter recovery. Any ideas?
UPDATE (8:42PM) -
Figured it out! In the SuperSU app, I disabled "mount namespace separation" and "tapjacking protection" before rebooting and trying AutoRec one more time. This enabled the hidden install button behind the lollipop icon in the app and allowed TWRP to be installed instantly. Hooray!
Click to expand...
Click to collapse
Can you please explain that in nubbie terms like step by step i would greatly appreciate it thank you in advance

Clarification
jboo01 said:
Can you please explain that in nubbie terms like step by step i would greatly appreciate it thank you in advance
Click to expand...
Click to collapse
To get the AutoRec app to work, you need to uncheck "tapjacking protection" inside of the SuperSu app (or its equivalent in whatever root manager you use).

not work in d805 lolipop ??????