Related
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
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.
How to completely uninstall magisk 15.3 installed on my stock 7.1.2
When i tried the latest uninstaller and flash it thru twrp i got bootloop same as when I restore my stock boot image back up from twrp i also got bootloop i wanted to update because i already received the ota of oreo 8.0 January update
Magisk v15.3
Xiaomi mi a1
7.1.2 December Security patch
Sent from my Mi A1 using Tapatalk
Try pulling the boot image file from the December update and flash that.
But, remember that you'll also have to restore your stock recovery to be able to install an OTA. Unless you're using "fastboot boot" to just run TWRP without installing...
Didgeridoohan said:
Try pulling the boot image file from the December update and flash that.
But, remember that you'll also have to restore your stock recovery to be able to install an OTA. Unless you're using "fastboot boot" to just run TWRP without installing...
Click to expand...
Click to collapse
yes i already did that but no luck :crying: still bootloop
i only boot twrp not flash, so i have the stock recovery
paul222008 said:
yes i already did that but no luck :crying:
Click to expand...
Click to collapse
You've obviously got something else going on. Magisk only really modifies your boot image, so if you can't get your device to boot after restoring a stock image it's most likely not Magisk causing it. Your device's forum might be the best place to ask for assistance.
Thought: are you sure it's just not a long boot? If you had decrypted your device, for example, it would start encrypting as soon as you flash a stock boot image and reboot.
Didgeridoohan said:
You've obviously got something else going on. Magisk only really modifies your boot image, so if you can't get your device to boot after restoring a stock image it's most likely not Magisk causing it. Your device's forum might be the best place to ask for assistance.
Thought: are you sure it's just not a long boot? If you had decrypted your device, for example, it would start encrypting as soon as you flash a stock boot image and reboot.
Click to expand...
Click to collapse
Im encrypted also [emoji55]
Sent from my Mi A1 using Tapatalk
What could the best way to do? My concern here is to preserve my app data
Sent from my Mi A1 using Tapatalk
paul222008 said:
What could the best way to do? My concern here is to preserve my app data
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Dirty flash a full update package (not an OTA file). Don't know if that's possible for you, but it would do it.
Didgeridoohan said:
Dirty flash a full update package (not an OTA file). Don't know if that's possible for you, but it would do it.
Click to expand...
Click to collapse
How? There's only .zip of ota available for my device
Sent from my Mi A1 using Tapatalk
paul222008 said:
How? There's only .zip of ota available for my device
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Like I said earlier: Your device's forum might be the best place to ask for assistance.
I am upgrading my OP3T from 5.0.1 to 5.0.3. My device is rooted using magisk and I have TWRP installed.
The system updates says -
"Root is detected, system will begin dowloading the full package. Your device will be un-rooted once the upgrade is completed."
Now my questions are
1. How to install the upgrade (5.0.3) without unrooting it ?
2. As it says it'll un-root my device, does it also mean it'll wipe my data as well ?
EDIT - I read about Dirty flashing the version I want but I can't find 5.0.3 image on Oneplus website.
shantam2 said:
The system updates says -
"Root is detected, system will begin dowloading the full package. Your device will be un-rooted once the upgrade is completed."
Now my questions are
1. How to install the upgrade (5.0.3) without unrooting it ?
2. As it says it'll un-root my device, does it also mean it'll wipe my data as well ?.
Click to expand...
Click to collapse
1. You can't.
2. No, but you can re-root it using TWRP (which will need to be reflashed via fastboot).
przemcio510 said:
1. You can't.
2. No, but you can re-root it using TWRP (which will need to be reflashed via fastboot).
Click to expand...
Click to collapse
Re-flashing magisk via TWRP will keep my data ?
It's the same as with all previous updates.
Go to TWRP, flash the whole rom,.don't exit,.flash latest Magisk,.done.
Everything will be as before, with the new system installed
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
It's the same as with all previous updates.
Go to TWRP, flash the whole rom,.don't exit,.flash latest Magisk,.done.
Everything will be as before, with the new system installed
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
Can you elaborate more on this ?
After I upgrade (and it becomes unrooted). I immediately flash magisk via TWRP ?
I didn't get the part "flash the whole rom and don't exit" ?
Also, Will I lose any data in the process ?
shantam2 said:
Re-flashing magisk via TWRP will keep my data ?
Click to expand...
Click to collapse
Nothing will be lost even if you don't flash Magisk, so yes.
And Rastaviper meant that when you flash the update via TWRP, you don't reboot, but right after flashing the ROM you flash Magisk and then reboot, this way you will stay rooted.
przemcio510 said:
Nothing will be lost even if you don't flash Magisk, so yes.
And Rastaviper meant that when you flash the update via TWRP, you don't reboot, but right after flashing the ROM you flash Magisk and then reboot, this way you will stay rooted.
Click to expand...
Click to collapse
So no need to fastboot flash recovery?
Correct me if I'm wrong, so you dl the zip, you flash it, you then flash magisk zip? Then what? You boot up and install twrp manager in order to change recovery?
b4bass said:
So no need to fastboot flash recovery?
Correct me if I'm wrong, so you dl the zip, you flash it, you then flash magisk zip? Then what? You boot up and install twrp manager in order to change recovery?
Click to expand...
Click to collapse
If you flash the update downloaded as zip from downloads.oneplus.com via TWRP, then no, there will be no need to flash it again via fastboot and no need to install TWRP Manager.
Boot to TWRP
Flash 5.0.3 zip
Flash Magisk
Reboot & enjoy
OK thanks! I thought the recovery would go back to stock after flashing the rom
And guys, if other members help you with their posts, don't forget to thank them.
Unleashed by my rooted OP3T on 8.0
b4bass said:
OK thanks! I thought the recovery would go back to stock after flashing the rom
Click to expand...
Click to collapse
That only happens if you reboot the phone while on the stock boot image. If you use a patched boot image, or a custom kernel, or Magisk, then the stock recovery doesn't overwrite the current recovery.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
That only happens if you reboot the phone while on the stock boot image. If you use a patched boot image, or a custom kernel, or Magisk, then the stock recovery doesn't overwrite the current recovery.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
So magisk is patching bootloader? I thought it was it point not to
Though this method is saving me some serious time!
b4bass said:
So magisk is patching boot, I thought I was it point not to
Though this method is saving me some serious time!
Click to expand...
Click to collapse
Magisk makes a point of not touching the system partition but a lot of its magic is done by changing the boot image.
Sent from my OnePlus3T using XDA Labs
OK thx ! First time I replaced supersu to pet magisk. Will have to find more details on this subject
b4bass said:
So magisk is patching bootloader? I thought it was it point not to
Click to expand...
Click to collapse
Boot image is kernel and ramdisk. Boot image is not the same as bootloader!
I am trying to root my Redmi Note 9, and the instructions I am following say to install "lazyflasher-no-verity-opt-encrypt".
I downloaded it and unzipped it but can't figure out how to actually install it on the phone. There is no APK file that I can see. The other key download, Magisk, came with a APK, so that stage went okay.
When I realized that I didn't know how to install lazyflasher, I uninstalled Magisk, as I feared bricking the device on the next boot.
Is there a way to backup the whole system, before I go ahead and brick it? I want to back up not just user data and a few app settings, I want something that will allow me to restore all my installed apps and system settings, in case something goes wrong.
No, you do NOT need no-verity-opt-encrypt.
VD171 said:
No, you do NOT need no-verity-opt-encrypt.
Click to expand...
Click to collapse
Good news. Can you link me to a decent set of instructions for rooting my device? I am an android noob, with Windows and Linux skills.
And what NOT to do, if I don't want a bricked device?
Just make rooting using fastboot and flash updates using fastboot and everything will be fine.
So if I do it the fastboot way, it wipes personal data, right? Is all that data restorable by means of the standard Redmi backup tool? If not, what's recommended to backup and restore that set of data?
No, data is not formatted for rooting or updating the system.
Data is formatted only for unlocking bootloader.
Do I need to unlock the bootloader for fastboot?
You do NOT need unlocked bootloader if you want to flash signed images (from stock rom).
But, you NEED unlocked bootloader if you want to flash custom partitions, like patched boot.img and patched vbmeta.img, for rooting.
VD171 said:
You do NOT need unlocked bootloader if you want to flash signed images (from stock rom).
But, you NEED unlocked bootloader if you want to flash custom partitions, like patched boot.img and patched vbmeta.img, for rooting.
Click to expand...
Click to collapse
Thanks for all your help!
I want to do two things:
1 Install a root certificate in order to get my phone working with my local network
2 Install a backup app such as Titanium Backup.