Running stock image with root, is it usually safe to take ota's?
You will receive error when installing the OTA. Unroot and then update, or... since you already have the bootloader unlocked (for rooting) you can flash from a PC the latest factory image (with the -w removed form the flash-all.bat script).
If you use magisk, you can go into it and select uninstall and restore images. Do not reboot your phone. Install the OTA and once you're at step to, go into magisk and select install and select the OTA option. Wait for the update to finish and reboot. Afterwards you're rooted and updated.
severedsnake said:
Running stock image with root, is it usually safe to take ota's?
Click to expand...
Click to collapse
Magisk Uninstall never worked for me for some reason.
Download OTA to PC
Boot into TWRP
ADB Sideload OTA
reboot
powerdown
Boot into TWRP again
flash Magisk.zip
Done
You can even flash the OTA.zip in twrp as well. When done, just fastboot into twrp, flash the twrp installer zip, then kernel, then magisk, reboot, done :good:
Related
Is there a smooth way to take an OTA update and re-root without a computer? So far my method has been:
see that there's an update
wait a week to see if the bugs are worked out
take the update at work
curse myself for forgetting I can't root until I get home
go home and flash twrp twice to get it to stick
flash magisk
get root back for Tasker and titanium
Is there a less tethered method I'm missing?
Immediately after installing new OTA, don't restart ur device, first reboot to recovery, after that reboot again to system, in this way ur TWRP will not be replaced by stock recovery. And after rebooted, again reboot to TWRP and flash the SuperSU zip to get root again.
Sounds good, except for the supersu bit. Is magisk interchangeable there?
Yes, Magisk is interchangeable with SuperSU.
You don't even have to reboot to recovery after flashing an update. Since you're rooted, the OnePlus OTA app will automatically download the 1 GB+ full OTA update zip. Once you have the update, make sure you have a copy of Magisk.zip somewhere on your internal storage. Then reboot to TWRP, flash OOS OTA, then immediately flash Magisk.zip. (Occasionally, you will run into an error where TWRP unmounts /system after flashing the OTA, simply go to main menu > mount and toggle /system off and then on again before flashing Magisk). Then simply reboot and your OS will be updated and rooted without OOS replacing TWRP.
Generally: Flash OTA -> wipe cache/Dalvik -> Flash Magisk (may need to remount /system) -> Reboot
Is it safe to take the ota with magisk or do I have to unroot and flash stock recovery?
I am on stock room and custom kernel atm
EnIXmA said:
Is it safe to take the ota with magisk or do I have to unroot and flash stock recovery?
I am on stock room and custom kernel atm
Click to expand...
Click to collapse
Hello, as Magisk changes boot image it will fail... The safetest method I think will be to download factory image, unzip, remove -w from flash-all.bat and then execute it... Then root again...
What did you do for the previous months updates?
You need to download the system image for the April update. You will need to extract the zip. Once you so that. Open up the flash. Bat file and erase the -w from the text then re-save it. Make sure you have twrp and your kernel stored locally on your phone. Reboot bootloader and run the .bat file. This process will not wipe your phone. After it's installed it will reboot your phone. Reboot bootloader and flash twrp.img through ADB. From there flash twrp.zip and your choice of kernel. Let your device reboot, then reboot into twrp and flash Magisk.
This should work as long as this update doesn't break twrp like February did. As always, you do this at your own risk.
MacTheRipperr said:
What did you do for the previous months updates?
You need to download the system image for the April update. You will need to extract the zip. Once you so that. Open up the flash. Bat file and erase the -w from the text then re-save it. Make sure you have twrp and your kernel stored locally on your phone. Reboot bootloader and run the .bat file. This process will not wipe your phone. After it's installed it will reboot your phone. Reboot bootloader and flash twrp.img through ADB. From there flash twrp.zip and your choice of kernel. Let your device reboot, then reboot into twrp and flash Magisk.
This should work as long as this update doesn't break twrp like February did. As always, you do this at your own risk.
Click to expand...
Click to collapse
Thanks. I bought the phone 2 weeks ago with the March security patch
Hi there. I wanted to go back to stock ROM, but with TWRP, caesium kernel and root/magisk. Right now I am on a custom ROM. So I wanted to backup with swift backup pro, TWRP. Then flash stock image to both slots / full wipe. Then boot to TWRP with fastboot, flash TWRP zip and kernel plus magisk, reboot TWRP and flash my debloater script. Then next month flash the factory image without the -w flag in the batch, and repeat the process above to have kernel and root. Am I missing something? Is the planned process proper? Or did I plan wrong steps?
I think you're fine, except an OTA will be more efficient the second time around.
Backup.
Connect P2XL to PC and Flash stock image to both slots.
Boot into TWRP using fastboot.
Install TWRP to the recovery ramdisk (as of TWRP 3.3.0-0).
Flash Magisk.
Flash your (unnecessary IMHO) debloater script.
Boot.
Enjoy the device until the next update, then...
Download a full OTA to the device.
Boot into TWRP.
Install the OTA.
Install TWRP to the recovery ramdisk (as of TWRP 3.3.0-0).
Flash Magisk.
Boot.
As of the release of TWRP 3.3.0-0 zip files are no longer available for installing TWRP to boot.img. TWRP will install itself into the boot.img by selecting "Install Image", then selecting "Install to recovery ramdisk".
Thanks, Sir.
OTA does not overwrite TWRP then?
Or flash OTA, boot to TWRP, flash TWRP as image, kernel & magisk? I guess I'll decrypt before flashing OTA?
An OTA will overwrite both TWRP and Magisk since it flashes a stock boot image. However, you are installing the OTA using TWRP and thus have TWRP resident in memory, so as long as you do not reboot you can flash TWRP to the ramdisk and then flash Magisk.
Strephon Alkhalikoi said:
An OTA will overwrite both TWRP and Magisk since it flashes a stock boot image. However, you are installing the OTA using TWRP and thus have TWRP resident in memory, so as long as you do not reboot you can flash TWRP to the ramdisk and then flash Magisk.
Click to expand...
Click to collapse
Thanks again, Sir.
If so what version of Magisk, TRWP, etc did you use and was it successful or any snags along the way?
I plan on manually flashing the OTA when I get home tonight, just curious if any others have had success or failures.
I just flashed the full image (not OTA) without issues. Initially flashed Magisk v20.3 and then used MM to update to v20.4. Finally, used EX Kernel Manger to download / flash latest kernel.
I flashed the OTA, and installed Magisk 20.3, everything went smoothly
My updating procedure is flashing update image without -w then sideloading twrp & sideload flash kernel & magisk, but i have changed my laptop, idk if its something to be done on the laptop or in the phone, as i flashed april update but now when sideload flashing in twrp the pc wont send file to phone it just keeps blank & wont flash zip
Nightf0x_007 said:
My updating procedure is flashing update image without -w then sideloading twrp & sideload flash kernel & magisk, but i have changed my laptop, idk if its something to be done on the laptop or in the phone, as i flashed april update but now when sideload flashing in twrp the pc wont send file to phone it just keeps blank & wont flash zip
Click to expand...
Click to collapse
I find that the USB setting gets reset on reboot. I always have to tap to change the option again.
Hi there!! Is it possible to root the Poco F3, keeping stock MIUI and still get OTA updates, without any problem (no data loss, no app auth removal, etc)
With rooted stock rom, you still get OTA updates. The smaller incremental OTA update will refuse to install, and the phone will download the full rom instead. Once the full update installed, you will have to apply root again (eg. flash the patched boot.img from the new update).
kurtschmeichel said:
With rooted stock rom, you still get OTA updates. The smaller incremental OTA update will refuse to install, and the phone will download the full rom instead. Once the full update installed, you will have to apply root again (eg. flash the patched boot.img from the new update).
Click to expand...
Click to collapse
In case you're using Magisk, would you flash the OTA update and magisk in TWRP?
What about internal data, and 2FA or banking apps? Do I need to re-authorize everything after OTA update?
I found this video
which shows that you could OTA update by "disabling magisk" for a moment. Is this procedure good?
As said, I let the phone update itself automatically. Since the smaller incremental update will not work, the phone will ask to download the bigger (±3 GB) updater. Once downloaded, it will overwrite the previously patched (rooted) boot.img.
So, when the update has finished and the phone has rebooted, you won't have root access anymore. In order to restore root access, you will have to flash a new patched boot.img.
There are different ways. I always use fastboot on my Mac. On a mac or pc, download the fastboot or recovery file of the new update that was just installed. Extract boot.img from that file. Send the file to the phone and patch it with Magisk. Send the patched boot.img back to the mac or pc and flash it to the phone (both a and b partitions) with fastboot.
Yeah, the only problem really is that, the boot-partition gets replaced with an update. So with every update you have to re-flash the patched boot.img
Magisk can patch TWRP Backups too, you can then restore the patched Boot-partition in TWRP!
So this is what I do to get Root again after an Update:
1. Boot into Fastboot Mode
2. Boot into TWRP SKKK
3. Backup Boot-partition
4. Boot Android
5. Open Magisk & patch /sdcard/TWRP/Backups/boot.emmc.win
6. Rename /Downloads/magisk_patched_xxx.img to "boot.emmc.win"
7. Move (and replace, when asked) to /sdcard/TWRP/Backups/boot.emmc.win
8. Boot TWRP SKKK and restore patched Boot
cyanGalaxy said:
Yeah, the only problem really is that, the boot-partition gets replaced with an update. So with every update you have to re-flash the patched boot.img
Magisk can patch TWRP Backups too, you can then restore the patched Boot-partition in TWRP!
So this is what I do to get Root again after an Update:
1. Boot into Fastboot Mode
2. Boot into TWRP SKKK
3. Backup Boot-partition
4. Boot Android
5. Open Magisk & patch /sdcard/TWRP/Backups/boot.emmc.win
6. Rename /Downloads/magisk_patched_xxx.img to "boot.emmc.win"
7. Move (and replace, when asked) to /sdcard/TWRP/Backups/boot.emmc.win
8. Boot TWRP SKKK and restore patched Boot
Click to expand...
Click to collapse
Thanks so much!
What about for the OTA procedure instead?
lillo9546 said:
Thanks so much!
What about for the OTA procedure instead?
Click to expand...
Click to collapse
Yup my instructions are for updates!
Unfortunately there is no "automatic way" to regain Root after an Update, at least AFAIK.
If you mean you want the small incremental updates to work, I'm not sure due to the altered Boot-partition. Might be best to use the Full Updates. ^^
You could also just flash Magisk.apk in TWRP or OrangeFox because it's also a Flashable ZIP-file, instead of manually having to patch Boot-partition.
I personally haven't done that in a long while, and the official FAQ-page of Magisk says, that that method is outdated and unsupported now, but apparently still works!
I forgot to mention OrangeFox in my previous post, but seems like a newer, better Custom Recovery than TWRP. You can also use that instead of TWRP. But make sure to use the latest Beta instead of Stable from the official Website because only the Beta can view /data (Android 12 Encryption Support). Stable TWRP also doesn't yet support A12 Encryption, only TWRP SKKK (Beta-version).
cyanGalaxy said:
Yeah, the only problem really is that, the boot-partition gets replaced with an update. So with every update you have to re-flash the patched boot.img
Magisk can patch TWRP Backups too, you can then restore the patched Boot-partition in TWRP!
So this is what I do to get Root again after an Update:
1. Boot into Fastboot Mode
2. Boot into TWRP SKKK
3. Backup Boot-partition
4. Boot Android
5. Open Magisk & patch /sdcard/TWRP/Backups/boot.emmc.win
6. Rename /Downloads/magisk_patched_xxx.img to "boot.emmc.win"
7. Move (and replace, when asked) to /sdcard/TWRP/Backups/boot.emmc.win
8. Boot TWRP SKKK and restore patched Boot
Click to expand...
Click to collapse
Can i do this procedure to dirty flash miui updates?
1. Boot twrp using Power button + Volume Up
2. Flash the ota update zip.
3. Reboot.
Can i do this?
gigavolthavoc07 said:
Can i do this procedure to dirty flash miui updates?
1. Boot twrp using Power button + Volume Up
2. Flash the ota update zip.
3. Reboot.
Can i do this?
Click to expand...
Click to collapse
Yes but make sure to use a Full OTA zip, not an incremental update zip. (the ZIP files in range of ~1-3 GB, not the ~300 MB incremental update-files)
cyanGalaxy said:
Yes but make sure to use a Full OTA zip, not an incremental update zip. (the ZIP files in range of ~1-3 GB, not the ~300 MB incremental update-files)
Click to expand...
Click to collapse
thanks man
Which custom recovery is MIUI OTA enabled?
I can't find it in Orangefox, show me!
Dirt.
orangefox version: [email protected] . 1_1_A12
user2332 said:
Which custom recovery is MIUI OTA enabled?....
Click to expand...
Click to collapse
Probably none. There is no point in trying to do that.
If you say so, I'll believe it. Thank you very much! I don't even bother with it anymore.
my way is to backup stock boot vendor_boot dtbo from twrp before flashing twrp and whenever i want to ota update i restore the backup and reboot
magisk will be gone
twrp will be gone
i start the ota update, it'll flash the small incremental update instead of using the entire 3gb rom