Related
Warning: crawrj mentioned this wouldn't flash in TWRP. I use CWM, so not sure whether it's compatible with TWRP (or any other recoveries) at the moment. So, if you're not using CWM... I would suggest waiting a bit.
So as most people know, the new OTA update aims to kill root on the device and the motochopper root method. Once I received the update and saw that it removed root, I immediately set out to figure out what was causing the issue. I also noticed that I was getting the notice about an application performing unauthorized tasks, or something to that effect.
After doing a few file deletions and restores, I finally found the file (KNOXAgent.apk) that was causing the notice about unauthorized actions and needing to restart. I've been running the phone with the MDL update for a little over a week now, and I haven't had another notice. I did lose root during the update, but was able to easily root it again with the motochopper method once the KNOXAgent files were removed.
So, here are the steps I took to avoid losing my root.
1) adb shell
2) su
3) mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
4) rm /system/app/KNOXAgent.*
5) Reboot into recovery and flash the OTA zip provided below. It's the OTA update with the KNOXAgent patches removed from the updater-script. This will allow the update to continue installing without having an error about KNOXAgent not being found on the device.
The same process may have to be done with future OTA updates once KNOXAgent is removed, but it's better than losing your root method each time an OTA comes out. As I mentioned, I've been using this phone since May 13th with this being done. I also had to take out the My Files updates as well, since I have the CyanogenMod file browser (My Files doesn't have root support).
Unfortunately, it seems XDA has problems with filtering spam and requires that you have 10 posts before being able to post external links. Since I don't have anything else to post at the moment, and can't post on the development forums to report problems to developers in order to legitimately increase my count without having to spam threads I don't care about, you'll have to copy and paste the link to get the update package.
Update link: http://d-h.st/Dkl
RogueSly said:
So as most people know, the new OTA update aims to kill root on the device and the motochopper root method. Once I received the update and saw that it removed root, I immediately set out to figure out what was causing the issue. I also noticed that I was getting the notice about an application performing unauthorized tasks, or something to that effect.
After doing a few file deletions and restores, I finally found the file (KNOXAgent.apk) that was causing the notice about unauthorized actions and needing to restart. I've been running the phone with the MDL update for a little over a week now, and I haven't had another notice. I did lose root during the update, but was able to easily root it again with the motochopper method once the KNOXAgent files were removed.
So, here are the steps I took to avoid losing my root.
1) adb shell
2) su
3) mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
4) rm /system/app/KNOXAgent.*
5) Reboot into recovery and flash the OTA zip provided below. It's the OTA update with the KNOXAgent patches removed from the updater-script. This will allow the update to continue installing without having an error about KNOXAgent not being found on the device.
The same process may have to be done with future OTA updates once KNOXAgent is removed, but it's better than losing your root method each time an OTA comes out. As I mentioned, I've been using this phone since May 13th with this being done. I also had to take out the My Files updates as well, since I have the CyanogenMod file browser (My Files doesn't have root support).
Unfortunately, it seems XDA has problems with filtering spam and requires that you have 10 posts before being able to post external links. Since I don't have anything else to post at the moment, and can't post on the development forums to report problems to developers in order to legitimately increase my count without having to spam threads I don't care about, you'll have to copy and paste the link to get the update package.
Update link: d-h.st/Dkl
Click to expand...
Click to collapse
Nice find
travisw0204 said:
Nice find
Click to expand...
Click to collapse
Thanks. It took a bit to find, but I couldn't live without root. My battery is GAWD with the CPU limited. :3
OK I am messing around with this and providing feedback. It doesn't install on the stock recovery for obvious reasons. It doesn't install in TWRP. Gives update binary error. Have to backup my extsd so I can format to fat32 to test other recoveries.
crawrj said:
OK I am messing around with this and providing feedback. It doesn't install on the stock recovery for obvious reasons. It doesn't install in TWRP. Gives update binary error. Have to backup my extsd so I can format to fat32 to test other recoveries.
Click to expand...
Click to collapse
Weird. Flashed for me on CWM when I used it.
RogueSly said:
Weird. Flashed for me on CWM when I used it.
Click to expand...
Click to collapse
Yeah I am guessing it will work in CWM. But I have to backup and format first to test. Which recovery did you use?
crawrj said:
Yeah I am guessing it will work in CWM. But I have to backup and format first to test. Which recovery did you use?
Click to expand...
Click to collapse
I've been using http://forum.xda-developers.com/showthread.php?t=2254323. I tend to stay away from touch recoveries when there are 4 dogs in the house.
Lol, too little too late for me. :facepalm:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
Awesome! Glad to hear it's fixed. Not sure why the modem didn't install. I didn't get any errors on my device after taking out the patches for My Files and KNOXAgent, as both were missing on my system. I'll try restoring back to MDC and updating to SuperSU 1.3 to test it.
crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
I was going to ask an annoying question.... but decided it was annoying and did a search. here is what I found in the difference between SuperUser and SuperSU and SuperSU Pro ($2.49). Reference: http://android.stackexchange.com/qu...ruser-from-chainsdd-and-superuser-from-clockw
SuperSU improves everything about Superuser and adds more options. The free version offers faster notifications, there is possibility of disabling them for each app and a new interface, attractive and easy to handle. In addition, according to developer claims by using SuperSU you’ll enjoy higher speed from the apps that require root rights, especially on Android 4.0+. The paid version called SuperSU Pro provides the opportunity to keep root rights after a system update, which usually cancels these rights. Although the method is not guaranteed the option is very useful. We have password protection and advanced log configuration settings for each application.
You might also want to read SuperSU Brings Better SuperUser Root Permission Management to Android. Quoting from that article:
SuperSU is basically SuperUser on steroids. According to the developer, it “allows for advanced management of Superuser access rights for all the apps on your device that need root.”.
Edit: ::FacePalm:: What ever you do. Do not uninstall SuperUser after you install SuperSU. You will loose Root. LOL (Hey at least I can laugh at myself.) I am not worried about it yet... I know I will get it back eventually.
Edit 2: After reading the OP, all you have to do if you have TWRP Recovery installed is do the OTA, your update will install and you will automatically reboot into TWRP.
Go to Mount first and mount System.
Go to back to home and select Advanced.
Go to File Manager. NOTE: This can be very frustrating! Use BACK and Sort Options to reset Sorting if it keeps doing things you don't want it to do. Also (Up A Level) is handy. If you are on "/" directory, touch Sort Descending: Name and you will see System. Select Sysytem.
Now Sort Ascending you will see App. Select App.
Gentally and slowly Swipe down in the middle to reach Knox. I found 2 files. Select one at a time and delete them.
Reboot
Then rerun Motochopper Root method.
I am on Stock MDC still. So if you are on MDL I am not sure if this would work. Now follow the directions that I failed to see when you install SuperSU.
Install SuperSU. Open SuperSU and make sure SU binary is switched from SuperUser to SuperSU. Once you do that you can remove SuperUser.
Edit 3: Once you check to make sure SuperSU has Binary after a reboot... SuperSU will remove SuperUser for you. No need to do anything.
After all said and done... I am thinking that the TWRP stopped the OTA from installing. I have been extremely busy with work, so no time to read XDA lately has been stopping me from keeping up to date. I just need more time in the day.
crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
Well, crawrj.. I just rawly patched the modem.bin with the modem.img.p, and the baseband version and such still hasn't increased. My software version and baseband version are still showing MDC, while build number is showing MDL. The weird thing about it is the kernel also updated from its original. How does the modem not update when it's being directly flashed onto the partition? Trying to get all of my stuff over to MDL, if that's what it's supposed to be. It has the new boot sound and such, but the inconsistent version numbers make me hesitant that the update fully applied.
RogueSly said:
Well, crawrj.. I just rawly patched the modem.bin with the modem.img.p, and the baseband version and such still hasn't increased. My software version and baseband version are still showing MDC, while build number is showing MDL. The weird thing about it is the kernel also updated from its original. How does the modem not update when it's being directly flashed onto the partition? Trying to get all of my stuff over to MDL, if that's what it's supposed to be. It has the new boot sound and such, but the inconsistent version numbers make me hesitant that the update fully applied.
Click to expand...
Click to collapse
There is some kind of write protection of security that locks the modem down. I have tried 100 different ways of installing the modem and can't. It looks like the official installs are the only ones that work. So right now the ota is the only way to get the modem. But I am sure we will get it figured out in time.
Sent from my SPH-L720 using xda premium
crawrj said:
There is some kind of write protection of security that locks the modem down. I have tried 100 different ways of installing the modem and can't. It looks like the official installs are the only ones that work. So right now the ota is the only way to get the modem. But I am sure we will get it figured out in time.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Well, that sucks. I guess I will give up trying to flash it for now. Already removed KNOXAgent again and dropped faux's kernel on here. It's showing my build as MDL, so at least I don't get pestered by the update message.
aww come on lol too late for me too. I went through hell rooting my phone when i upgraded to MDL. I flashed the stock rom like 3 times before getting my phone rooted and the last piece of the puzzle were the knox files. Instead of deleting the files i froze them using the system tuner off from the playstore after i installed shabbat's custom kernel.
Do we know of a way to avoid all these run arounds to root on MDL by keeping the stock kernel and without removing knox???
tones160 said:
aww come on lol too late for me too. I went through hell rooting my phone when i upgraded to MDL. I flashed the stock rom like 3 times before getting my phone rooted and the last piece of the puzzle were the knox files. Instead of deleting the files i froze them using the system tuner off from the playstore after i installed shabbat's custom kernel.
Do we know of a way to avoid all these run arounds to root on MDL by keeping the stock kernel and without removing knox???
Click to expand...
Click to collapse
I think there are a few posts in the development sections that will help out with getting root on MDL. If it were me, I would just pull the SuperSU apk and unzip it. Grab the su binary out of there, push it to /system/xbin/, and then install SuperSU on the phone once it restarted. Now, I can't confirm that works... because I haven't had to get that dirty with rooting my phone. Motochopper worked perfectly fine when KNOXAgent was removed, so it should work if you have KNOXAgent frozen too.
Cf autoroot
wanna make sure I understand this right. I'm gonna flash this no knox update on top of forcesrom (which has knox removed), I should be ok right? but the modern still not install this way, is that correct? and I won't be able to update my modem until a new method comes out. do I got it all right? thanks! :thumbup::what:
gershee said:
wanna make sure I understand this right. I'm gonna flash this no knox update on top of forcesrom (which has knox removed), I should be ok right? but the modern still not install this way, is that correct? and I won't be able to update my modem until a new method comes out. do I got it all right? thanks! :thumbup::what:
Click to expand...
Click to collapse
That's apparently right, for now. I'm working on figuring out why the MDM partition won't flash. I tried to patch the files manually, as mentioned previously and here, but it seems that it didn't flash as the baseband didn't change?
Hopefully figure it out soon.
Getting E:Error in /external_sd/OTA 5-13-2013 (No Knox Agent), Status 7. Any advice?
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.
Hi,
I'm using Chainfire systemless root for Android 6. Can I install OTA updates without unrooting or is it better to unroot anyway? Do I habve to reinstall the boot image after an OTA Update?
You should be able to update, assuming nothing modified /system.
I am unsure whether you need to reflash SuperSU after updating. I would assume yes, but ???
You should really go read the threads in this forum. Asking questions about topics that are already answered is a forum faux pax. Don't be a noob.
Ok, I'll put myself out there as a noob then.
I've read everything that I can find about whether systemless SuperSU will allow OTA updates or not. I find no definitive answer. It's "maybe" (as above) or "You'll have to reinstall stock recovery" (which doesn't sound to me like a transparent simple OTA update) - all pretty vague and I see no answer from anyone who has actually seen it work on their own device.
So can some kind soul please point me to the apparently obvious definitive yes/no answer that they've found and I can't?
Or anyone who has systemless SuperSU installed and has seen ***with their own eyes*** the "System updated downloaded" and managed to press the button and update without any other actions?
Thank you...
I've had success with 2.63 (not out yet) using the "Full unroot" option in SuperSU, and OTA updating from 6.0 to 6.0.1 on volantis/flounder (Nexus 9 Wi-Fi). Most OTA's will not work without unrooting this way. After flashing the OTA, you will have to re-root.
The same should be possible on 2.62, assuming you are also running stock recovery.
Of course, this will only work if you have not modified /system, /vendor (if present) and /oem (if present) in any way.
Once I get FlashFire updated, it should all be much easier than that.
Thanks, Chainfire. At last a definitive explanation, and from The Master himself...
I've seen on one thread somewhere a comment about the writer using 2.63. Do you have any schedule for the release of 2.63? I'm currently unrooted, and I would want to root again only if I knew that the monthly disruption is minimal.
No great rush - I reckon it'll be another month at least before I have to do something about my current stock 6.0.1.
(Found your shirt yet? )
Not more than a few days I think. Nobody has 2.63 but me. I might skip that number though, as some are misnaming the 3rd release of 2.62 (2.62-3) as 2.63.
Note that those iterations with the same version numbers only include changes to the ZIP file scripts, not changes to the SuperSU GUI or binaries.
As for the shirt, I'm afraid it's still lost somewhere in the red light district. Long story!
Thanks again.
This is the thread that I mentioned:
http://forum.xda-developers.com/lg-g-pad-83/orig-development/v500-cyanogenmod-13-0-t3259135/page12
nytral - post #117:
"Oops, Secure booting error, boot certification verify. Supersu 2.63beta managed to generate a boot.img"
@Chainfire Does "Full unroot" restore the original boot.img ?
Because most OTA's nowadays verify the checksum of boot partition before continuing to update.
Assuming the backup hasn't gone missing, it will offer to restore the original boot image. I will also offer to attempt to restore recovery (also needed for most OTAs), though that requires a working install-recovery inside the firmware (TWRP is known for messing that up on install).
MM root could be nice, i cannot use titanium backup without the mobile rebooting when i try to do my backups, it can backup but not restore.
RichardEb said:
Hi,
I'm using Chainfire systemless root for Android 6. Can I install OTA updates
Click to expand...
Click to collapse
http://www.xda-developers.com/chainfire-systemless-root-now-supports-automated-boot-image-patching/
Just a clarification, meaning even if I have custom recovery(Since I flashed 2.65 with custom one) I can still receive OTA by using unroot option on my nexus 5? Let's say monthly security patches and I just need to reflash root?
Steps?
*Assuming I have custom recovery and rooted
1. Unroot using SuperSU
2. Install OTA using built-in
3. Reflash root
I am stock rooted 6.0 with SuperSu 2.5. At&t has finally pushed the 6.0.1 update to my phone and I need to update to get rid of that notification. I am fairly new to using Macs and am not able to use Wugfresh's toolkit anymore. Should I switch to systemless root? Do I have to do anything special in order to go from system root to systemless root? Thanks for your help.
joshpdavis80 said:
I am stock rooted 6.0 with SuperSu 2.5. At&t has finally pushed the 6.0.1 update to my phone and I need to update to get rid of that notification. I am fairly new to using Macs and am not able to use Wugfresh's toolkit anymore. Should I switch to systemless root? Do I have to do anything special in order to go from system root to systemless root? Thanks for your help.
Click to expand...
Click to collapse
Hopefully you know how to use ADB and Fastboot. If not, here's a good tutorial > http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
From where you are at, you will start by downloading the latest factory image (MMB29Q) from here > https://developers.google.com/android/nexus/images
Then fastboot flash the bootloader.img, radio.img, boot.img, and system.img. Use Method 2 (Long Method). The "flash_all" script doesn't work. Here's a tutorial for that > http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
joshpdavis80 said:
I am stock rooted 6.0 with SuperSu 2.5. At&t has finally pushed the 6.0.1 update to my phone and I need to update to get rid of that notification. I am fairly new to using Macs and am not able to use Wugfresh's toolkit anymore. Should I switch to systemless root? Do I have to do anything special in order to go from system root to systemless root? Thanks for your help.
Click to expand...
Click to collapse
Take your time and make sure you have everything set up right. Macs are known for causing issues when working with android devices. Also never use a root kit. They only cause more issues then they fix. This is the reason people wont help others that have used one of the kits. You do yourself a great injustice by using them.
hi,
i am new in these forums,
i searched over the web and also tried many root methods, but none worked.
root method for NXH19X is not working for me i tried multiple times.
the main error i am getting is "unable to mount /system; no such thing found" in TWRP
i also tried multiple Supersu files official ones and unofficial ones as well.
after some research i found out about new file system squashfs FS
then i tried this rom which supports EXT4 File System
here is link: https://forum.xda-developers.com/g-watch-r/development/rom-ext4all-g-watch-r-skin1980-t3589917
but it didnot work out as well,(get boot looped)
so flashed stock rom and now on latest update as told earlier,
so its my request, i need help. if someone please come up with any working method to root latest stock rom and security patches(build number and security patch in title)
why stock rom?
i personally like stock rom and it is working fine for me.
why root?
i have root on my phone (one plus one), i felt like i am unable to use my watch on full potential without root.
and we all like root that's why we are here right
thank you
(i actually don't know the how to write any threads so bear with me please) :fingers-crossed:
This post of mine will work. Tried on many roms and it works.
Some play store apps says i dont have root but I do as the app i use that needs root works : https://play.google.com/store/apps/details?id=com.skin1980.buttonremap
So use this procedure :
https://forum.xda-developers.com/g-watch-r/development/nxh19x-boot-img-rooted-t3651039
The problem is that u need a TWRP for squash images which you can find in the mentioned post
Grumps said:
This post of mine will work. Tried on many roms and it works.
Some play store apps says i dont have root but I do as the app i use that needs root works : https://play.google.com/store/apps/details?id=com.skin1980.buttonremap
So use this procedure :
https://forum.xda-developers.com/g-watch-r/development/nxh19x-boot-img-rooted-t3651039
The problem is that u need a TWRP for squash images which you can find in the mentioned post
Click to expand...
Click to collapse
hi
i tried your given method,
twrp seems to work fine first time,
but i lost twrp as soon as i boot into system,
some how system replace recovery with default one each time watch booted into android itself,
however i am able to boot into recovery, when tried directly from fast-boot after flashing it,
but still unable to obtain root,
the zip files seems to flash perfectly, but there is no su in app drawer,
thanks for your support, but i think new version makes it harder to gain root,
and i am fine without root i can live without it.
thanks again.
Talwinder8872 said:
hi
i tried your given method,
twrp seems to work fine first time,
but i lost twrp as soon as i boot into system,
some how system replace recovery with default one each time watch booted into android itself,
however i am able to boot into recovery, when tried directly from fast-boot after flashing it,
but still unable to obtain root,
the zip files seems to flash perfectly, but there is no su in app drawer,
thanks for your support, but i think new version makes it harder to gain root,
and i am fine without root i can live without it.
thanks again.
Click to expand...
Click to collapse
There is no SuperUser for android wear watches. It will automatically allow root access for all apps that request it...
Grumps said:
There is no SuperUser for android wear watches. It will automatically allow root access for all apps that request it...
Click to expand...
Click to collapse
ok i see, but how to confirm, it is rooted because i don't want to purchase that 'Button Re-Mapper App', before confirming,
Talwinder8872 said:
ok i see, but how to confirm, it is rooted because i don't want to purchase that 'Button Re-Mapper App', before confirming,
Click to expand...
Click to collapse
ok boom , i got it ,
i am such a noob, didn't bother to check it with root check now we are good to go, cool
thanks a million guys :good: :good:
ok i don't know how to attach screen shot,
Talwinder8872 said:
ok boom , i got it ,
i am such a noob, didn't bother to check it with root check now we are good to go, cool
thanks a million guys :good: :good:
ok i don't know how to attach screen shot,
Click to expand...
Click to collapse
Dont worry be believe you haha