Database Develop

[How-To] Root G870AUCU1ANG3 (GS5 Active)

**Make certain that your reactivation lock in security settings is off before beginning this process**
1. Take the NG3 OTA update.
2. Download and install Towelroot-v3.apk(this version does not require internet access).
3. Place your phone into "Download Mode" (press and hold the Home, Volume Down, and Power keys until the phone powers on and displays warning screen, then press Volume Up key) and flash the G870A_NE4_Stock_Kernel using Odin's PDA slot(AP in Odin v3.09+).
4. Open the Towelroot app from your app drawer and press "Make it Rain" to root your device.
5. Power off then boot into "Download Mode" again and flash the G870A_NG3_Stock_Kernel also in Odin's PDA slot(AP in Odin v3.09+).
6. Download SuperSu to manage root access. Done!
Troubleshooting:
1. If the NG3 OTA update fails consider flashing the G870AUCU1ANE4_Full_Odin.tar to return to stock then take the NG3 OTA update, (or place the G870A_NE4toNG3_OTA.zip onto your ext-sdcard and sideload from stock recovery). Once updated to NG3 continue to Step 2 above.
2. The most common cause of an Odin flash failure is a bad usb port or cable. Please check before reporting a failure.
Notes:
1. After flashing the NE4 kernel your phone may run a little wonky and towelroot may not root on the first try. If that happens reboot and try towelroot once again. Once rooted and after flashing the NG3 kernel your phone will once again run like a champ!
2. The above process will not affect your User Data or Knox Warranty Flag.
Credits:
@lordmorphous - Tester

Gonna try this... Thanks! :beer:
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

Yes this worked. Thank you very much.......

Are we going to trip Knox using the method above ???
Just wanna be sure about this. ...g

gregsarg said:
Are we going to trip Knox using the method above ???
Just wanna be sure about this. ...g
Click to expand...
Click to collapse
Nope.

Does anyone have a list of the benefits of updating to NG3?
I just rooted my new phone on NE4 and I want to know whether it's worth taking the time.

Thanks for the How-to! Worked great for me!

Any benefits on ng3 over stock?

Root possible for 'straight out-of-the-box' G870AUCU1ANG3???
I've looked and looked around the forums here and have come to the conclusion that the AT&T S 5 I recently picked up is, sadly, unable to be rooted. Does anyone here know if this is true? As the title suggests, my phone seems to have come loaded with G870AUCU1ANG3. Is it possible that it came with the previous iteration (NE4, I think??) and I didn't avoid an update, thus meaning I can flash the earlier version? Can I even tell whether it's possible to 'revert' to NE4 (or whatever it would be)? Is any of this even possible without having been previously rooted, or am I wasting my time searching this out? Naive but earnest questions... sorry if I'm in the wrong place here. I promise, I poked around the site for a few days in search of clarity before posting.

papayajelly said:
I've looked and looked around the forums here and have come to the conclusion that the AT&T S 5 I recently picked up is, sadly, unable to be rooted. Does anyone here know if this is true? As the title suggests, my phone seems to have come loaded with G870AUCU1ANG3. Is it possible that it came with the previous iteration (NE4, I think??) and I didn't avoid an update, thus meaning I can flash the earlier version? Can I even tell whether it's possible to 'revert' to NE4 (or whatever it would be)? Is any of this even possible without having been previously rooted, or am I wasting my time searching this out? Naive but earnest questions... sorry if I'm in the wrong place here. I promise, I poked around the site for a few days in search of clarity before posting.
Click to expand...
Click to collapse
There shouldn't be any reason why you can't follow the instructions in the 1st post of this thread starting with step 2.

I've been searching for a while and can't find anything about using this root method and then being able to install safestrap. Has anyone been successful in doing this? Do I need to downgrade before and does anybody have the downgrade file? FYI Just bought my phone last night and was successful in rooting.

rescuedad said:
I've been searching for a while and can't find anything about using this root method and then being able to install safestrap. Has anyone been successful in doing this? Do I need to downgrade before and does anybody have the downgrade file? FYI Just bought my phone last night and was successful in rooting.
Click to expand...
Click to collapse
Never mind, I figured it out. If you have the active you need to downgrade the kernel to NE4 like you do if you need root. Then you install Safestrap 3.75. I'm doing a Nandroid backup as I type. I'm going to re-flash the NG3 stock kernel when I'm done and hopefully that will be fine.
If it bricks, I can always take it back since I blocked the knox counter... BTW I'm on At&T

I downgraded to the NE4 to root. Along with others here I have to ask, what are, if any, benefits to upgrading the kernel?

panthersdzynes said:
I downgraded to the NE4 to root. Along with others here I have to ask, what are, if any, benefits to upgrading the kernel?
Click to expand...
Click to collapse
Not sure I understand the question but I will take a shot......typically the kernel, modules, and non-hlos.bin have to match or else you may experience issues such as no wifi, lag, etc. The NE4 and NG3 kernel and modules may be similar enough that you will not experience issues immediately but they may develop later unless you reflash the NG3 kernel to match your modules and non-hlos.

muniz_ri said:
Not sure I understand the question but I will take a shot......typically the kernel, modules, and non-hlos.bin have to match or else you may experience issues such as no wifi, lag, etc. The NE4 and NG3 kernel and modules may be similar enough that you will not experience issues immediately but they may develop later unless you reflash the NG3 kernel to match your modules and non-hlos.
Click to expand...
Click to collapse
I see. Thank you, that answers my question.

THanks XDA
Been away along time. Had iphones for the last 6 years. Use to go here all the time in the Kaiser days (Att Tilt) if any of you remember. I see XDA has still been kicking ass while I've been gone! Glad to be back and Thank You everyone especially first poster for the guide to root my Att GS5 Active.
THANK YOU

Working perfectly. ..thank you. ..g

There was a small update released today. Can someone that is rooted grab it from their fota/cache folder and send to me so that I can update this guide? Thanks.

WORKED! AWESOME!
Now... I have installed SuperSU. Was that left out of the first post?
Also, if I do not flash the NG3 Stock Kernel back afterwards, will I experience funkiness?
Thanks again!

Stock recovery and upgrading Lollipop with future OTAs after rooting

Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!

LordGrahf said:
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
Click to expand...
Click to collapse
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.

Thank you sir!

obsanity said:
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Click to expand...
Click to collapse
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.

I'm kinda curious myself. I had no idea root killed OTA's. Maybe I wouldn't have done that if I knew that. I'm very new to the Nexus device. It's my 1st. I unlocked the bootloader and rooted already.
Sent from Mark's Nexus 6

crowbarman said:
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?

I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!

LordGrahf said:
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
Click to expand...
Click to collapse
not sure what you mean by GI, but according to some others, after uninstalling root via SuperSU an OTA will still not install. This should not be the case unless the boot or recovery images are modified. Easily fixed by following the procedures above to fastboot the stock images on your phone.
kjnangre said:
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
Click to expand...
Click to collapse
Yes, it behaves exactly the same.

crowbarman said:
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.

obsanity said:
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
Click to expand...
Click to collapse
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.

crowbarman said:
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
Click to expand...
Click to collapse
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1

obsanity said:
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
Click to expand...
Click to collapse
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?

crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.

obsanity said:
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
Click to expand...
Click to collapse
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?

LordGrahf said:
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
Click to expand...
Click to collapse
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.

obsanity said:
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
Click to expand...
Click to collapse
There is an argument that publishing the method would allow Google to close it that much quicker, I suppose.

crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.

I assume that the encryption doesn't get in the way of being able to flash the images?
When I went from 5.0 to 5.0.1 on my old Nexus 5 all I did was flash the two new 5.0.1 images I extracted from the full factory image, then re-rooted. This is far cleaner than reverting back to the previous image then doing an OTA. I've not had to update my N6 yet so I don't know if my method will work still, but I hope it does.

Chainfire said:
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
Click to expand...
Click to collapse
Thanks for the additional information.
I did spend a fair amount of time reading your documentation but failed to utilize a hex editor. I am not 'whining' about the lack of open source, rather, simply mildly surprised, but your website aptly describes the challenges with 5.0. Many are used to various root methods being available.
Your solution is fine with me.. I love your work.
Edit: I thought I'd add that the discussion has devolved from the OP, which was whether an OTA can be applied after uninstalling root. The answer was no, due to the unknowns about what still might be modified following the uninstall via SuperSU.

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

[How-To] Update to G870A(Active Model)_OJ3 - 5.1.1 (Unrooted Stock ROM)

**You can begin the following process from any Build/ROM but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
**Note** Rooting all Samsung 5.1.x builds currently requires a modified kernel therefore, due to the locked bootloader, achieving root on this build/device is not currently possible.
Downloads:
- G870A_OJ3_Stock_ROM.zip
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. Press "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 G870A_OC5_Bootloader using Odin's PDA/AP slot.
*If you are already on the OC5 bootloader, set "Reboot" setting to "Normal" and skip Step 7.
**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 about 1 - 2 minutes before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Recommended: Package Disabler Pro to disable unwanted bloatware (root access not required).
Known Issues:
- None!
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. The bootloader will not be flashed in order to allow for downgrading to previous firmware versions.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you do not already have root access (or to unbrick) you must flash the G870AUCU1ANE4_Full_Odin.tar using Odin's PDA/AP slot (Caution! Do not flash if you have taken the OF2, OF3 or OJ3 ota update) and root with TowelRoot, before continuing with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2

Sweet! I have been anxiously waiting for this for my active. Thank you!
Sent from my SAMSUNG-SM-G900A using Tapatalk

I want to try it so bad, but I need my root!
Could everybody tell us what you think performance/battery wise though?
Thanks a lot!

Awesome gna do some flashn!

Thanks @muniz_ri.
Sent from my SAMSUNG-SM-G870A using Tapatalk

Followed the directions and it worked fine.
Used the suggested package disable pro with the defaults and then updated everything. Phone seems to be working fine so far.
I did read in one of the other threads that the battery life and such might not be as good as expected because we are still on the old bootloader, is this true or does the bootloader have nothing to do with the operating system?

Oh man....now do I...or don't I....

Install went well. Now to test.
Sent from my SAMSUNG-SM-G870A using Tapatalk

AnarchoXen said:
Oh man....now do I...or don't I....
Click to expand...
Click to collapse
Do it!
Sent from my SAMSUNG-SM-G870A using Tapatalk

If it requires root to flash... I would hope that I could then keep root after the flash.
I'm holding off on 5.1.1 until root is available. Just can't do without it I don't think.

Well i went ahead and did it, no problems at all. Now to see if I really can live without root!

Gonna try my hands at rooting this >_> i will update status.
Did some testing bricked my device 5 times. doesnt get past the bootloader part, so :/
For those of you that are testing this yourselves. You will ave to use the stock firmware for 4.x to unbrick. and then upgrade from 5.0 -> 5.1 in that order. So i guess im going to ave to wait for a root method too >_>
Within further testing, the files do update via flashfire, i just ave no clue how to get the system files to mount/unmount without bricking because it's unpacked.

Very good. Running smooth and fast. I do miss some root features.
SM-G870A Peace

Teranode said:
Gonna try my hands at rooting this >_> i will update status.
Did some testing bricked my device 5 times. doesnt get past the bootloader part, so :/
For those of you that are testing this yourselves. You will ave to use the stock firmware for 4.x to unbrick. and then upgrade from 5.0 -> 5.1 in that order. So i guess im going to ave to wait for a root method too >_>
Within further testing, the files do update via flashfire, i just ave no clue how to get the system files to mount/unmount without bricking because it's unpacked.
Click to expand...
Click to collapse
You can save yourself some time, or not, but all that has already been tried. No current way to root 5.1.1 on locked bootloader devices.

Meh I have a bunch of nexus and 2 one plus phones I just wanted to see of I can get this working on a s5 model. Att still committed to their locked bootloaders

berniesteven said:
Do it!
Sent from my SAMSUNG-SM-G870A using Tapatalk
Click to expand...
Click to collapse
I am! Now...at the ATT logo screen currently.
Well that was quick.

So use to this tutorials that I didn't read (or see) the UNROOTED part.....darn it
Can this be undone ?
If so, how
Thanks!

orion2323 said:
So use to this tutorials that I didn't read (or see) the UNROOTED part.....darn it
Can this be undone ?
If so, how
Thanks!
Click to expand...
Click to collapse
Odin back to ne4. See the op.
SM-G870A Peace

berniesteven said:
Odin back to ne4. See the op.
SM-G870A Peace
Click to expand...
Click to collapse
Thank you...did it; up and running with the previous build
"4. If you do not already have root access (or to unbrick) you must flash the G870AUCU1ANE4_Full_Odin.tar using Odin's PDA/AP slot (Caution! Do not flash if you have taken the OF2, OF3 or OJ3 ota update) and root with TowelRoot, before continuing with the above process"
I was afraid to try it but needed my root
I'm hoping to get a 128GB card next week and wanted to erase my phone anyway...

orion2323 said:
Thank you...did it; up and running with the previous build
"4. If you do not already have root access (or to unbrick) you must flash the G870AUCU1ANE4_Full_Odin.tar using Odin's PDA/AP slot (Caution! Do not flash if you have taken the OF2, OF3 or OJ3 ota update) and root with TowelRoot, before continuing with the above process"
I was afraid to try it buy needed my root
I'm hoping to get a 128GB card next week and wanted to erase my phone anyway...
Click to expand...
Click to collapse
Glad it worked out well for you. If I helped, don't forget to hit thanks.
SM-G870A Peace

root

hi,
I would love to root my sm-g800f.
Which guide should I follow?
Thanks

What ROM? You can try flashing the correct CF Auto Root for your phone model and Android version using Odin if it using the latest Lollipop.

lfom said:
What ROM? You can try flashing the correct CF Auto Root for your phone model and Android version using Odin if it using the latest Lollipop.
Click to expand...
Click to collapse
I have to look, so, for 'CF Auto Root' for G800FXXU1BPC3 Lollipop MR1 and
Odin.
Odin goes on PC and
CF Auto Root goes on device.
Am I right?

Both files go on PC, you used Odin to flash CF Auto Root into mobile. Seek for the files in the official page:
https://autoroot.chainfire.eu/
There are many videos on YouTube about it as most Samsung phones are rooted this way. Just make sure you use the correct file for your phone (G800F).
Backup everything you can first in case something goes wrong you may need to wipe mobile data and reflash stock ROM.
The other option is to use Odin to flash TWRP and then flash SuperSU zip from Chainfire. First, TWRP goes on PC then SuperSU Zip on phone, that you flash using TWRP. I am sure there are tutorials here about it, just pick TWRP for G800F, SuperSU is universal but some version may be needed according to your Android version. Can't help more because I have G800H and not rooted as Marshmallow was released for it and it has all I need. Good luck.

lfom said:
Both files go on PC, you used Odin to flash CF Auto Root into mobile. Seek for the files in the official page:
https://autoroot.chainfire.eu/
There are many videos on YouTube about it as most Samsung phones are rooted this way. Just make sure you use the correct file for your phone (G800F).
Backup everything you can first in case something goes wrong you may need to wipe mobile data and reflash stock ROM.
The other option is to use Odin to flash TWRP and then flash SuperSU zip from Chainfire. First, TWRP goes on PC then SuperSU Zip on phone, that you flash using TWRP. I am sure there are tutorials here about it, just pick TWRP for G800F, SuperSU is universal but some version may be needed according to your Android version. Can't help more because I have G800H and not rooted as Marshmallow was released for it and it has all I need. Good luck.
Click to expand...
Click to collapse
first way, I think, should be more simple.
How silly, I would root to change fonts on device.
And of course to free space, delete junkie and have control of my device.
Marshmallow is going to make me regret rooting?

You can change fonts using atock, no root needed. Also use Debloater to disable junk, no root needed either.
You can't use OTA to upgrade to MM when it arrives as it usually won't install or bootloops, so you will need to flash MM to go back to stock and upgrade then root again. Flashfire from Chainfire would be able to install OTAKU and keep root, but support to S5 mini is unkonwm, and no reports of success as far as I know.
Last but not least, flashing anything other than stock ROM through Odin will trip a Knox security counter and you'll lose warranty.

lfom said:
You can change fonts using atock, no root needed. Also use Debloater to disable junk, no root needed either.
You can't use OTA to upgrade to MM when it arrives as it usually won't install or bootloops, so you will need to flash MM to go back to stock and upgrade then root again. Flashfire from Chainfire would be able to install OTAKU and keep root, but support to S5 mini is unkonwm, and no reports of success as far as I know.
Click to expand...
Click to collapse
I don' t uderstand.
I'm stock. If I'll root I'll not be anymore stock.
If I don't root, will MM arrive OTA?
lfom said:
Last but not least, flashing anything other than stock ROM through Odin will trip a Knox security counter and you'll lose warranty.
Click to expand...
Click to collapse
I know

dezuha said:
I don' t uderstand.
I'm stock. If I'll root I'll not be anymore stock.
If I don't root, will MM arrive OTA?
Click to expand...
Click to collapse
Yes, when it's available for your phone model, as long as you're stock. Sorry, wasn't clear before.

lfom said:
Yes, when it's available for your phone model, as long as you're stock. Sorry, wasn't clear before.
Click to expand...
Click to collapse
you are joking!
You are very nice in answering to my questions.
''fonts using atock'', I think I can't.
I can only use payment monotype fonts

dezuha said:
you are joking!
You are very nice in answering to my questions.
''fonts using atock'', I think I can't.
I can only use payment monotype fonts
Click to expand...
Click to collapse
This is using stock MM on my G800H, I don't remember on Lollipop but I'm almost sure there was a similar option:

http://forum.xda-developers.com/galaxy-s5-mini/general/guide-easiest-method-root-g800h-t3340949
http://forum.xda-developers.com/galaxy-s5-mini/general/sm-g800f-rooting-guide-t3164859
I have found these two guides.
Which one do I have to follow?
lfom said:
This is using stock MM on my G800H, I don't remember on Lollipop but I'm almost sure there was a similar option:
Click to expand...
Click to collapse
I have those 5 ones.
But I would like other fonts.