I have successfully rooted 5.1.1 but with a snag, since we cannot unlock the bootloader and flash an unsigned kernel I am unable to completely and fully have a painless root process available. However... the process that I did work on does work it just requires that each reboot you have to manually set selinux to permissive via adb in order to get your phone to boot. So I am opening this thread to ask considering the method.
Make sure you read this post fully!
Builds currently confirmed working:
Code:
OJ7
OJ9
Important: Once you flash OJ7 or any part of it, you will no longer be able to flash back to a previous build, this includes the files needed to root.
As mentioned above, this method is simple but has a caveat, once you root your phone you'll need a script or run a command each time you reboot or turn on your phone. This can be a pain if your phone battery dies while on the Go or if your phone randomly reboots and you do not have a laptop or desktop on hand or nearby. So know what you are getting into before you perform this root method. With that said, onto the goods...
This is a Combined root method from SamFirm and myself. I also need to give credit to those who provided me with some of the files that got this whole thing started and those who continue on this effort:
@shichemt
@Apexseal
@elesbb
@designgears
Thanks!
Prerequisites:
Samsung Drivers
Developer mode turned on
First, reboot your phone into Download Mode:
Power off your phone or reboot, hold Vol+Down, Power and Home
Once you are in download mode, load up Odin (Odin3 v3.10.7.exe) and do the following:
In the 'images' directory, you will have 1 file->
G{920,925}A_Kernel_Root_5.1.1_SamFirm.NET.tar.md5 (Place in the AP slot)
Once you have the file added into Odin, press start and wait until the phone boots up completely. (Again, make sure Developer Mode is on!)
Next pretty simple, run the root-Install.sh (linux) or root-Install.cmd (windows).
Follow the prompts and enjoy root on your SM-G{920,925}A!
Secondly, you will always from here on out need to use the root-Boot.sh (linux) or root-boot.cmd (windows) to boot your phone up. Without it... you'll be stuck in a boot loop with Selinux Enforced. This script will make your phone boot as Selinux Permissive.
Here are the steps for OJ9:
Using the same steps as above to Flash the downgraded system partition and once the phone is fully booted up, make sure Developer mode is on and then run the root-Install.{cmd,sh} script. I have provided a separate download link for this as well, so again if you are on OJ9, you need to flash the separate package specific to your build.
Process Order::
AP_G920AUCU3BOJ7+G{920,925}A_Kernel_Root_5.1.1.tar (Place in the AP slot)
Run root-Install.{cmd,sh} from g{920,925}a-5.1.1-root~metalcated-v{4,1}.zip
BE AWARE, I cannot guarantee the safety of your data, BACKUP! BACKUP! BACKUP! - but this should work without wiping your data.
Another Important Note: The Samsung drivers for Windows have issues with this process or maybe its just Windows being Windows! - I have found out that if you get stuck and adb is not responding after the root process is complete and you are either stuck at the AT&T screen or have a black screen waiting for adb to come back up, remove the driver (shown in the screenshot and then scan for hardware changes. This will refresh the driver and force adb to respond again.
Downloads
G920A
Root Files:
g920a-5.1.1-root~metalcated-v4.zip
OJ9 - AP_G920AUCU3BOJ7+G920A_Kernel_Root_5.1.1.tar
Pre-Rooted FlashFire System Images:
g920a-5.1.1-rooted-debloated~metalcated.zip
OJ7 User Binary - Restore:
G920AUCU3BOJ7_User_Binary.rar
G925A
Root Files:
g925a-5.1.1-root~metalcated-v1.zip
OJ9 - AP_G925AUCU3BOJ7+G925A_Kernel_Root_5.1.1.tar.zip
Pre-Rooted FlashFire System Images:
I don't yet have a debloated image for the g925a
OJ7 User Binary - Restore:
G925AUCU3BOJ7_User_Binary.zip
To use the Pre-Rooted FlashFire image, extract the zip to your sdcard into the Flashfire directory and then perform a restore with FlashFire.
Beware, you are flashing these files at your own risk. Don't come yelling at me if it messes anything up! Make backups of you data before flashing anything, you have been warned!
This process can be painful to get working, but if all you want is a debloated ROM, root your phone then install Flashfire and flash the system image posted above and you will have your deboated ROM. You can then remove root using the SuperSU app and your phone will boot cleanly from here on out with no bloat. Of course its up to you what you want to do. - I know one of the testers said this is what he was going to do.
Anyone can use these files to make a better process if its one so desires, all I ask is that you provide credit for the source like I have done above in this post as to where I obtained these files to assist me in getting this process working. If you want to help, please PM me and we can chat about making this process better.
I am still working towards a hack to try and force selinux to be permissive at kernel load without having an unlocked BL, not sure if it will work, but I am trying to make it so. Will keep you all posted on progress.
Install Xposed? Confirmed working! http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Enjoy!
~metalcated
Pic of supersu working?
Does it trip Knox or any of that mumbo jumbo? If we test it how do we go back if we don't want to reroot every time?
Sent from my SAMSUNG-SM-G920A using Tapatalk
PMDColeslaw said:
Does it trip Knox or any of that mumbo jumbo? If we test it how do we go back if we don't want to reroot every time?
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
See attached image.
Nice! So if we flash this and want to revert back to stock I assume Odin would be the only way. If so does that mean loss of all your data?
Sent from my SAMSUNG-SM-G920A using Tapatalk
Can you show us how to do this ? Thank you!
PMDColeslaw said:
Nice! So if we flash this and want to revert back to stock I assume Odin would be the only way. If so does that mean loss of all your data?
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
Honestly I would say a clean removal of SuperSU through the SuperSU App should work. Although I have not tried this yet, but I don't see why it wouldn't work. However if it does not, yes flash back to using Odin would be needed and a total loss of data would be in order, so as always... backup, backup!
Interesting. I wonder if you could use this to develop some sort of script like the safestrap recovery on the S4? Maybe one that runs the root commands on boot from a file on the phone instead of adb.
Sent from my SAMSUNG-SM-G920A using Tapatalk
PMDColeslaw said:
Interesting. I wonder if you could use this to develop some sort of script like the safestrap recovery on the S4? Maybe one that runs the root commands on boot from a file on the phone instead of adb.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
I welcome it to anyone willing to do it.
It's out of my wheelhouse unfortunately, but it seems like a possibility. Hopefully someone else can give it a shot. Are you able to debloat with the root you have so far?
Sent from my SAMSUNG-SM-G920A using Tapatalk
PMDColeslaw said:
It's out of my wheelhouse unfortunately, but it seems like a possibility. Hopefully someone else can give it a shot. Are you able to debloat with the root you have so far?
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
I created a system img that is flashable via FlashFire, I will zip it up and upload to AFH.
I tried to run root-Install.cmd, after that I stuck in booting (with at&t logo), seems that root-Boot.cmd doesn't help. BTW,my firmware version is G920AUCU3BOI2, would that make a difference?
dreamyy5 said:
I tried to run root-Install.cmd, after that I stuck in booting (with at&t logo), seems that root-Boot.cmd doesn't help. BTW,my firmware version is G920AUCU3BOI2, would that make a difference?
Click to expand...
Click to collapse
I haven't tried this on OI2, you may need to upgrade to OJ7. I put the link in the thread. If you pull apart the tar and extract the system.img and boot.img from the kernel and make your own tar (use 7zip), you SHOULD not loose your personal data and all it would do it update your system. BUT, you'll also need to update the recovery, etc. It can be done but you'd need to be careful how you do it so you don't loose your data. I would just back up your phone and expect to loose your data. Let me know if you need help.
With different builds in mind, I updated the scripts. PM me if you want the updated link to tested on other builds.
metalcated said:
I haven't tried this on OI2, you may need to upgrade to OJ7. I put the link in the thread. If you pull apart the tar and extract the system.img and boot.img from the kernel and make your own tar (use 7zip), you SHOULD not loose your personal data and all it would do it update your system. BUT, you'll also need to update the recovery, etc. It can be done but you'd need to be careful how you do it so you don't loose your data. I would just back up your phone and expect to loose your data. Let me know if you need help.
With different builds in mind, I updated the scripts. PM me if you want the updated link to tested on other builds.
Click to expand...
Click to collapse
I'm on BOJ9. Can I still flash the debloated file or is it based on another build?
UPDATE: After flashing the two files in images folder the phone rebooted and I got this Knox message.
When I try to run the root.cmd file nothing happens. Any suggestions?
Try to use debloater and disable Knox and reboot then try again if root is not active. I may need to dig some more and add some cmds to the script to disable Knox software. I was able to boot up and then disable it.
metalcated said:
Try to use debloater and disable Knox and reboot then try again if root is not active. I may need to dig some more and add some cmds to the script to disable Knox software. I was able to boot up and then disable it.
Click to expand...
Click to collapse
I cant get root because the intall-root.cmd file won't run. It just flashes a cmd prompt and then closes. I'm on windows 10
Oh you know something. I didn't include adb.exe, do you have adb installed? Install it here if not - http://forum.xda-developers.com/showthread.php?t=2588979
Plus make sure that you have the correct drivers installed and can see your device.
# adb devices
metalcated said:
Plus make sure that you have the correct drivers installed and can see your device.
# adb devices
Click to expand...
Click to collapse
I do have adb and can see it under devices. Do I need to move the .cmd file to the adb folder?
PMDColeslaw said:
I do have adb and can see it under devices. Do I need to move the .cmd file to the adb folder?
Click to expand...
Click to collapse
Only if you don't have the directory for adb in your path. So if you don't then yes.
Related
im wanting to flash the Eclipse 1.0 ROM that is out but im currently still on the initial version that was on the phone at release. i have heard that taking the OTA when rooted can cause boot loops and that i need to OTA fist before flashing Eclipse. what are the steps i need to take in order to safky take the OTA?
also, are titanium backups working so i can load all my apps and data once i get onto eclipse? i thought i saw something about them not working a while back and have not been keeping up with if this has been sorted out?
yamaha83 said:
im wanting to flash the Eclipse 1.0 ROM that is out but im currently still on the initial version that was on the phone at release. i have heard that taking the OTA when rooted can cause boot loops and that i need to OTA fist before flashing Eclipse. what are the steps i need to take in order to safky take the OTA?
also, are titanium backups working so i can load all my apps and data once i get onto eclipse? i thought i saw something about them not working a while back and have not been keeping up with if this has been sorted out?
Click to expand...
Click to collapse
download and install the newest SS that was just released. then go to your stock slot. uninstall SS from the SS app. Then flash stock recovery and system (assuming you didn't flash your baseband as well, if you did then flash the old baseband back on there). then either install pwnmymoto without running, take ota, then check to confirm you have root. OR take ota then root with rockmymoto. then follow instructions to instlal SS on rootzwiki. then follow instructions for the rom.
TIBU works. (not sure for the eclipse rom, just post over there on that thread that question, i haven't run it yet so idk but i would presume that it will since it is based off of the original FW for the phone and not source.) I typically install the apps i had myself from the play store then just reinstall data with TiBu. This is ebcause I have ran into problems installing apps from tibu personally but it was most likely my own error. I never have a problem otherwise, so i just install my own apps. Sometimes google or something does it for me as well so i only instlal a few root apps taht i already saved the apks for so i just move the folder to my phone and install them. Once done with all of that i go and put my data back in with tibu.
jayboyyyy said:
download and install the newest SS that was just released. then go to your stock slot. uninstall SS from the SS app. Then flash stock recovery and system (assuming you didn't flash your baseband as well, if you did then flash the old baseband back on there). then either install pwnmymoto without running, take ota, then check to confirm you have root. OR take ota then root with rockmymoto. then follow instructions to instlal SS on rootzwiki. then follow instructions for the rom.
TIBU works. (not sure for the eclipse rom, just post over there on that thread that question, i haven't run it yet so idk but i would presume that it will since it is based off of the original FW for the phone and not source.) I typically install the apps i had myself from the play store then just reinstall data with TiBu. This is ebcause I have ran into problems installing apps from tibu personally but it was most likely my own error. I never have a problem otherwise, so i just install my own apps. Sometimes google or something does it for me as well so i only instlal a few root apps taht i already saved the apks for so i just move the folder to my phone and install them. Once done with all of that i go and put my data back in with tibu.
Click to expand...
Click to collapse
ok so within the safestrap app i click uninstall recovery, i assume thats what you mean by uninstall safestrap from within the app? after that how do i install the stock recovery and system?
yamaha83 said:
ok so within the safestrap app i click uninstall recovery, i assume thats what you mean by uninstall safestrap from within the app? after that how do i install the stock recovery and system?
Click to expand...
Click to collapse
hmmmm. you go and learn how to use fastboot is how you do it lol. you can also just rsd lite if you don't care about keeping your data. i just posted some general instructions that will help you with fastboot.
http://forum.xda-developers.com/showthread.php?t=2525495&page=6
also , if you don't want to install the sdk tools you can just go download the motofastboot file from here, and run that
http://forum.xda-developers.com/showthread.php?t=2489249
jayboyyyy said:
hmmmm. you go and learn how to use fastboot is how you do it lol. you can also just rsd lite if you don't care about keeping your data. i just posted some general instructions that will help you with fastboot.
http://forum.xda-developers.com/showthread.php?t=2525495&page=6
also , if you don't want to install the sdk tools you can just go download the motofastboot file from here, and run that
http://forum.xda-developers.com/showthread.php?t=2489249
Click to expand...
Click to collapse
i may just use RSDLITE... its been a long time since I had to use fastboot dont really have the time to mess around with it. hmmmmmm
yamaha83 said:
i may just use RSDLITE... its been a long time since I had to use fastboot dont really have the time to mess around with it. hmmmmmm
Click to expand...
Click to collapse
its extremely simple in reality. download that fastboot file from that link. put it in a a folder on your c drive (for instance "fastboot") download the FW for your hone. unzip. put the system and recovery img in the fastboot file you created. then open cmd. type "cd c:/fastboot" THEn plug phone into computer, the reboot phone into fastboot mode with power button and volume down button held for like 3 secs. then run commands in fastboot, fastboot flash recovery recovery.img
fastboot flasht system system.img
fastboot reboot
and your done.
or go use rsd light and remove all of the code from the fastboot commands except for the flash system and flash recovery (the code in the xml file).
jayboyyyy said:
its extremely simple in reality. download that fastboot file from that link. put it in a a folder on your c drive (for instance "fastboot") download the FW for your hone. unzip. put the system and recovery img in the fastboot file you created. then open cmd. type "cd c:/fastboot" THEn plug phone into computer, the reboot phone into fastboot mode with power button and volume down button held for like 3 secs. then run commands in fastboot, fastboot flash recovery recovery.img
fastboot flasht system system.img
fastboot reboot
and your done.
or go use rsd light and remove all of the code from the fastboot commands except for the flash system and flash recovery (the code in the xml file).
Click to expand...
Click to collapse
ah thank you!! that was enough of a refresher to get me going! thanks a lot!
yamaha83 said:
ah thank you!! that was enough of a refresher to get me going! thanks a lot!
Click to expand...
Click to collapse
np. i had to go refresh on my fastboot stuff when i first got the phone because i hadn't touched phone stuff for over a year.
Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help
saman0suke1 said:
Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help
Click to expand...
Click to collapse
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.
My Nexus 6 took 5.0.1 just fine, but my Nexus 7 does this same thing, running stock ROM/Bootloader/Recovery/etc. The ONLY thing done to it is the Fastboot OEM unlock, but I doubt that alone would stop it. I'm curious to know what resolves this ( other than downloading the factory image and flashing it without wiping the userdata )
Just got same error. I didnt even root phone, bought it today, it installed apps from backup of my previous Nexus 4 and OTA is failing.
cupfulloflol said:
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.
Click to expand...
Click to collapse
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!
saman0suke1 said:
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!
Click to expand...
Click to collapse
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.
cupfulloflol said:
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.
Click to expand...
Click to collapse
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!
saman0suke1 said:
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!
Click to expand...
Click to collapse
I'm interested as well. Mine is rooted and I have encryption disabled, and I have TWRP on my phone. I tried to sideload the OTA update, but I can't get my phone to start sideload. I even flashed the stock recovery to get it to go, and no dice. What do I do next?
Anyone? I would appreciate the feedback, thanks!
sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.
cmh714 said:
sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.
Click to expand...
Click to collapse
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!
saman0suke1 said:
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!
Click to expand...
Click to collapse
If your doing from the PC you need to extract the zip file from within the image and then fastboot them. As for root, when you do it from fastboot I dont believe it matters as you will lose root anyway and need to re-root via flashing SuperSU.zip
Worked great! Thanks! Android 5.0.1 and root, no data deleted
Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!
Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.
naulsballs said:
Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using XDA Free mobile app
saman0suke1 said:
Worked great! Thanks! Android 5.0.1 and root, no data deleted
Click to expand...
Click to collapse
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
TOCS88 said:
Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!
Click to expand...
Click to collapse
Try pulling your Sim card out and rebooting.
scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you're planning to stay rooted (meaning no OTA in future) system.img, boot.img and radio.img in any order.
scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you use fastboot, just run these commands in terminal (I used windows, so in order to flash using fastboot, put the image that you downloaded for the update in the same folder where you have fastboot and open a terminal there) you can rename the .img files to whatever you like and replace those name in the commands below:
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
Then reboot it:
fastboot reboot-bootloader
Then flash these:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
And that's it. These commands are run while the phone is connected to the PC, you have to turn it on by pressing volume up + volume down + power.
Good luck.
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
yosmokinman said:
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
Click to expand...
Click to collapse
That is true, kind of just wondering/gathering information. It just seemed like with the new root method, OTA would be possible and less risky than before.
Sent from my MotoG3 using Tapatalk
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Srandista said:
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Click to expand...
Click to collapse
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
quakeaz said:
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Sounds good!
Sent from my MotoG3 using Tapatalk
quakeaz said:
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Click to expand...
Click to collapse
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Thanks for the info. So I take it while using systemless root, installing ota without unrooting is a big nono? The January ota just downloaded and is asking me to install, should I do it manually?
Chainfire said:
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Click to expand...
Click to collapse
Thank you for this thread and the procedure. I tried myself to avoid as much as possible to use a computer for super easy OTA update. But there is always one obligatory step: to root the phone.
Phone systemless rooted (2.66) - TWRP installed - OTA arrives.
In SuperSu app : Fully unroot
Install OTA - success
Fastboot boot (or install) TWRP
Flash superSu 2.66.zip
And that's it!
My question is the following: Does it exist a possibility to load on step 3. something that could flash superSu.zip from within the phone, no computer required?
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Judim said:
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Click to expand...
Click to collapse
Yes, this is one of the use-cases of FlashFire. I just haven't finished updating it to 6.0 yet.
Oh nice!
I didn't know it cause I never had the chance to try out FlashFire.
Thanks so much for everything you do for the Android community!
Cheers!
Srandista said:
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Click to expand...
Click to collapse
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
ShanxRoux said:
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
Click to expand...
Click to collapse
Did you modify system?
Try flashing system, boot, and recovery.
Then try again.
Hi, I have a Oneplus One and today has been released an OTA, so I tried the method. I have COS13 JK (latest full rom) firmware, with systemless 2.84beta supersu and twrp.
The only apps that have root access are AdAway and Greenify (without mods to system apps). No Busybox installed.
I reverted via fastboot to original JK boot.img and recovery.img, and restored, via Adaway, the original hosts file, then I applied the OTA via stock Cyano Recovery, but update failed ("system partition has unexpected contents" error).
Why?
Thanks.
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
caldent said:
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
I tried: no way to install OTA, I had to wait for the full rom, and dirty flashed it via TWRP without a problem.
Then I rerooted.
Bye!
ok i seem to be getting the run around on where i need to be to ask my question(s)
i am very interested in systemless root....
that being said i am clueless and all info i am findingis just super confusing me.
if someone could humor a noob to systemless rooting that would be greatly appreciated!!
i recently bought 2 new phone for my household, both are the lg tribute hd (also called lg x style)
one click root and pc method of kingoroot etc dont work... i cant locate a twrp or a cwm for this model easily by searching so i am assuming there isnt one (maybe someone could located or help to build one?)- or maybe im not tech smart enough and i can use any?(i dont think so)
model is lg ls675,android 6.0.1, kernel version 3.10.49, build # MXB48T, software is ls676zv3
main reason at the moment for trying to get root is to remove bloatware and to be able to wifi tether without limitations buy the provider, on ther phone that i have obtained root on i used an app called WIFI Tether Router which works beautifully but requires root...
please help as this is how we use our computer with internet and its beneficial all the way around especially to get rid of bloatware and keep device running smoothly...
thanks again for any help. greatly appreciated.
if im not in the right thread please kindly direct me to the correct one. thanks
TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this
Wow and so it begins, great work thanks!
Thanks
Sent from my Pixel using XDA-Developers mobile app
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.
zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root
Since no guide has been updated with information on official TWRP for root and backup reasons, I thought I'd create one.
DISCLAIMER:
To do this method requires you to unlock your bootloader. Your warranty is now void. This method assumes you have basic knowledge of ADB and Fastboot commands and know how to recover your device if you accidentally type a wrong command and now boot to TWRP and can't boot to system. If you cannot recover from this, Read up on guides to "return to stock" and familiarize yourself on how to recover your device should something go wrong.
There are two methods for root. You can flash TWRP to your boot image to be able to reboot to TWRP without a PC, or just a temp boot so you can just have root and not TWRP. I'll put in brackets the minor differences.
1: Get ready
Download latest build of TWRP img file from their website.(Previous link is to their instructions and device specific patches, download page is HERE.) {download the latest zip if you want to flash TWRP}
Download what you want on your phone (SU, Magisk, etc)
2:
Hook phone up to your PC, be sure you have latest adb/fastboot drivers. (I do not support windows related questions. If you have latest drivers, you'll have no issue with the below commands, Linux just works for this kind of thing)
3:
Navigate to your directory that has that img downloaded. (windows, shift right click and say "open command prompt here")
Type the below commands, and terminal output should be similar: (I.E. this is a copy/paste of terminal)
Main thing to remember is "Fastboot boot {filename}.img"
Code:
[email protected]:~$ adb reboot bootloader
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ fastboot boot twrp-3.2.1-1-nash.img
downloading 'boot.img'...
OKAY [ 0.841s]
booting...
OKAY [ 5.135s]
finished. total time: 5.976s
[email protected]:~/Downloads$
BE SURE TO DO BOOT AND NOT FLASH!!! (If you ask why you can no longer boot to system, I'll let you know you missed this line.)
5:
You're now in TWRP!
It will ask you for your password. This is your PIN or password to unlock your phone. Enter it.
TWRP has now decrypted your storage to read the zip file(s) you put on your phone!
Go to install and navigate to your directory where you put that file
Install Magisk/SU/TWRP/whatever you please.
(Note: some root zips require a factory reset)
6:
Reboot!
You're Done congratulations!
Attached are images if they help you see you're doing the right thing.
Special thanks @erfanoabdi @invisiblek @npjohnson @joemossjr @jbats
Without the above people a lot of what's above woudn't have been possible for this device specifically. Also, thanks to everyone who pitched in to get a device over to invisiblek. Leaps and bounds have been done since that donation. And thanks to the other devs who have invested in this phone and their time to help out.
(Quoted from Nathan Chance)
Quite a few people have asked to donate to me in the past and I have turned them down. I am not in this for the money, this is my hobby, something I truly enjoy. If you truly want to donate to something (it is not expected in the slightest), I recommend an entity like the Open Source Initiative, the Free Software Foundation, XDA, or any one of the people I have thanked in the OP. Additionally, you are free to copy any and all of my work; the only thing I request is that you not ask for donations as well (though I can't really enforce this lol). Thank you.
Random issues post:
SU does some wonky edits to the ramdisk. It is highly suggested to flash Magisk for root.
Some have reported needing to wipe data after flashing Magisk. If you can't boot after flashing Magisk, just go back into recovery (can be twrp or stock) and wipe data/factory reset to boot again.
Note: we do not have a recovery partition. Never flash the img file! Download the flashable zip if you want twrp on your phone and flash per OP instructions.
Awesome thanks
I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo
droidgreg said:
I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo
Click to expand...
Click to collapse
Be sure to mount system under the "mount" button
I need the OCX27.1 oreo. I did a return to stock flashall to OCX27 and now reflashed TWRP and Magisk and boots fine but I lost baseband and IMEI
Added warning to OP that some root zips require a data wipe.
I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.
will4958 said:
I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.
Click to expand...
Click to collapse
This guide assumes you can unlock your bootloader. Since Verizon and AT&T feel they have a right to lock down their devices, this guide won't work. That is why I voted with my wallet and left Vz after my M7 due to them putting phone OEM's privates in a vice and forced them to lock out those carrier variants.
Has this method been tested with OCX27.1 Oreo on TMO?
droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
It probably hasn't been tested, but it should work in theory.
Uzephi said:
It probably hasn't been tested, but it should work in theory.
Click to expand...
Click to collapse
I was on 27.1 when I attempted to root and got into a bootloop and lost my baseband when I flashall back to stock OCX27. I have a feeling 27.1 update isn't compatible with this method and cannot be downgraded to even OCX 27 Oreo
so no go on 27.1 twrp? I have root on 27.1 TMO obtained post update. Obtained by fastbooting the nash twrp and running magisk 16.zip. No needing to format data or anything
I was just wondering about the installable twrp zip. I am coming from samsung development so all this A/B partitioning and some of the other partitions are new to me.
As soon as I can get twrp on the phone and feel comfortable recovering. The kernels and roms will start coming.
Feels strange not having odin to save my ass
droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
tested and working
mattlowry said:
tested and working
Click to expand...
Click to collapse
Have you actually flashed installer.zip to install TWRP or just booted TWRP and only flash magisk or SU for root without installing TWRP?
I fastboot booted the twrp. I didn't try the installer. What is it?
Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.
luponcooper said:
Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.
Click to expand...
Click to collapse
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).
Uzephi said:
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).
Click to expand...
Click to collapse
Thanks a lot uzephi for answering.
I have the 6gb ram and 64gb model, XT1789-05. I try whit no succes to install Magisk (Error1) so i made a factory reset but still doesn't boot, stays in M logo.
Im super noob, can you guide me? i dont know how to recover the boot.img.
excuse my english.