Database Develop

Systemless root (Android 6.0) - Method for easy future OTA updates

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

Rootin and OTa

Is there anyway to root and still get OTA ?

anttaz said:
Is there anyway to root and still get OTA ?
Click to expand...
Click to collapse
You will get OTA, after Root also, but after updating your root will gone, recovery will replaced by Stock recovery, and if You are decrypted after update
it will get encrypted.

uttam.ace said:
You will get OTA, after Root also, but after updating your root will gone, recovery will replaced by Stock recovery, and if You are decrypted after update
it will get encrypted.
Click to expand...
Click to collapse
Does stock recovery not allow zip flashing?

anttaz said:
Does stock recovery not allow zip flashing?
Click to expand...
Click to collapse
It allows local upgrade, but it has not much flexibility like TWRP.

I've just updated from 4.0.2 to 4.0.3 and here's how my "OTA" was working:
1) Got notification that the update is available
2) Went to XDA to download OOS 4.0.3. full ROM zip, TWRP 3.1.4.1 image and Magisk 11.1 root
3) rebooted to TWRP, flashed new ROM, Magisk root and TWRP image.
As far as I know, that's the only sure way to update your phone while keeping root and TWRP.

Does it pass safety net?

anttaz said:
Does it pass safety net?
Click to expand...
Click to collapse
Yes, it does! With MagiskHide it works like a charm.

Will ota work for cleaning system for say arise sound mod or will have to use full? And does full wipe device clean?

anttaz said:
Will ota work for cleaning system for say arise sound mod or will have to use full? And does full wipe device clean?
Click to expand...
Click to collapse
I'm sorry, i didn't fully understand what you were trying to say here
But i'll take a wild guess and tell you that in TWRP you always need to flash full ROM, not OTA version. Otherwise your phone won't boot.

hrsa said:
I'm sorry, i didn't fully understand what you were trying to say here
But i'll take a wild guess and tell you that in TWRP you always need to flash full ROM, not OTA version. Otherwise your phone won't boot.
Click to expand...
Click to collapse
Along those lines in a way does full ROM zip wipe phone each flash?

anttaz said:
Along those lines in a way does full ROM zip wipe phone each flash?
Click to expand...
Click to collapse
Nope, it never wipes anything other than system, so all your data and apps are safe.

anttaz said:
Along those lines in a way does full ROM zip wipe phone each flash?
Click to expand...
Click to collapse
Does flashing full ROM zip wipe phone with each flash?

Thanks all
Which version twrp to use seen official and a few others in forum for our device??

Hello, sorry for my bad english (German). I installed the update too and now my root, recovery, kernel.... are away. When I try to flash the recovery or other stuff with cmd, is there an error message: FAILED (remote: Partition flashing is not allowed)
Got anyone an idea how i can flash my recovery again?

Magisk 14 News

Wow no need for custom recovery...
http://www.androidpolice.com/2017/0...hout-root-installing-without-custom-recovery/

@ultramag69 Maybe he doesn't follow Magisk closely? I know I don't. Magisk is only on used my stepmom's OP3T H2OS (which I update but don't look at the change log since it's only there in case I need it in the future), the other 2 phones I support don't use Magisk they use LOS su add-on. Not everyone who uses root cares about all the bloated/"nifty" features that come out, some just want plain old root.

I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.

I'm letting people know that with 14 they can keep stock recovery and take OTAs

ultramag69 said:
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
Click to expand...
Click to collapse
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS

lollyjay said:
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
Click to expand...
Click to collapse
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.

ultramag69 said:
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
Click to expand...
Click to collapse
No need to do that now

Honestly, who roots a phone without flashing a custom recovery the very second after? Unless they are forced to use Flashfire without BL unlock, I guess.

lollyjay said:
No need to do that now
Click to expand...
Click to collapse
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...

ultramag69 said:
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
Click to expand...
Click to collapse
No problems at all with my OP5

Magisk 14.0 breaks XPosed so had to go back to Magisk 13.3

Now where can we obtain a copy of the stock boot.img?

almostthere said:
Now where can we obtain a copy of the stock boot.img?
Click to expand...
Click to collapse
What you're supposed to do is make a backup of your boot partition any time you update your rom. So if you didn't do that then you can dirty flash your current Rom and that would give you the stock boot.img and again, go into recovery and make a backup of your boot partition. then if you want to flash a custom kernel you can.

Help the noobs
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.

s_ofer said:
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
Click to expand...
Click to collapse
I have the stock 4.5.10 boot.img for download here:
https://drive.google.com/file/d/0B3gcDbDvV4Mkbm5EMEZ4dnpSbk0/view?usp=drivesdk
Sent from my OnePlus5 using XDA Labs

Thanks.
Do any of you think it is possible to FLASH anything without unlocking the bootloader?
There is a thread somewhere for OP3T that shows somehow that is possible to load TWRP on the phone without unlocking the bootloader or wiping data.

I only use for root too but every so often I open magisk manager as it updates also both the manager app and magisk itself. But using magisk to root my Axon 7 with unlocked bootloader.

Why TWRP deleted after booting?

I flashed latest TWRP with fastboot command on CMD.
TWRP works but after I reset the TWRP was deleted and I can get STOCK recovery.
I can boot up TWRP only if I connect my device to computer and use command FASTBOOT BOOT RECOVERY.IMG
Why?

If u flashed a rom,.then before booting you must flash the root file or a custom kernel in order to keep the TWRP.
Unleashed by my rooted OP3T on 8.0

I do not flashing another rom, only new open beta versions and flash files.

saarxee said:
I do not flashing another rom, only new open beta versions and flash files.
Click to expand...
Click to collapse
New open beta is another Rom buddy.
Unleashed by my rooted OP3T on 8.0

But I dont need custom kernel and root.

saarxee said:
But I dont need custom kernel and root.
Click to expand...
Click to collapse
You have to flash at least Magisk/SuperSU or custom kernel in order to keep TWRP intact after each reboot. Not sure about modified stock kernels with dm-verity and forceencrypt disabled, they may work too.
This is the nature of stock ROM.

saarxee said:
But I dont need custom kernel and root.
Click to expand...
Click to collapse
OOS enforces encryption and restores the stock recovery when you reboot your phone.
Custom ROMs, custom kernels, and Magisk all prevent that from happening.
If you want plain OOS (stable or Open Beta) and keep TWRP, then use Xennet's patched boot image. See https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053
Sent from my OnePlus3T using XDA Labs

I flashed magisk on TWRP and TWRP deleted again after restart.
What can I do?

Reflash your current ROM via TWRP and flash Magisk right after ROM without restarting

Today I flashed open beta 24 and after that Magisk and wipe dalvik and restart recovery and I got stock recovery and dont TWRP.

saarxee said:
Today I flashed open beta 24 and after that Magisk and wipe dalvik and restart recovery and I got stock recovery and dont TWRP.
Click to expand...
Click to collapse
Like I said, use Xennet's patched boot image.
Sent from my OnePlus3T using XDA Labs

What to do about this file? flash it and install TWRP again? or only flash it and restart to recovery?
Why I need to change my boot file? If my device dont booting up after the flash?

saarxee said:
Why I need to change my boot file? If my device dont booting up after the flash?
Click to expand...
Click to collapse
Because stock will always revert to stock recovery.
If the device doesn't boot, then you're using an incompatible boot image
(it seems that Magisk/SuperSU isn't enough)

I flashed this boot patched image and choose restart to recovery and stock recovery again...

I have the same problem - twrp gets erased after booting in OS Since beta 24

I don't know guys what's wrong with your devices, I'm using Open Beta 24 with custom kernel and TWRP boots everytime.

I use stock kernel, maybe that is the clue.

Viktorrr said:
I use stock kernel, maybe that is the clue.
Click to expand...
Click to collapse
Then maybe you should flash the modified kernel that is especially modified to not restore the stock recovery.....

gizahNL said:
Then maybe you should flash the modified kernel that is especially modified to not restore the stock recovery.....
Click to expand...
Click to collapse
Correct, as I pointed out in this post https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867/post76049932
Sent from my OnePlus3T using XDA Labs

gizahNL said:
Then maybe you should flash the modified kernel that is especially modified to not restore the stock recovery.....
Click to expand...
Click to collapse
BillGoss said:
Correct, as I pointed out in this post https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867/post76049932
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
OP said that it didn't work:
I flashed this boot patched image and choose restart to recovery and stock recovery again...
Click to expand...
Click to collapse

Which version of TWRP?

So, just got the OTA update to Android Pie for my Mi 8 Global, and want to try flashing TWRP again. Every single version of TWRP I have flashed before has always either fail to boot, or always reboots into recovery and the ROM never loads. Anyone can suggest a real working TWRP file to flash? Do I need to wipe data? Etc. Since TWRP hasn't worked for me at all, I have to root with a roundabout way. Install Magisk Manager, extract and recompile boot.img into patched_boot.img and flash that in fastboot. This gives me roo but no TWRP so I can't flash any custom kernels or ROMs.

Rommco05 said:
Hi, I can't help you with twrp because I still waiting for countdown for unlocked it. From your post I understand u have a stock recovery.img, where u find stock recovery?
Click to expand...
Click to collapse
I just flash the stock boot.img and it reverts everything

Rommco05 said:
Where I can find stock .imgs?
Click to expand...
Click to collapse
Download a stock ROM and grab the boot.img from inside it.