I'm trying to update to 11.2.3.3.LE15AA by OTA after rooting but having issues.
I've done the following
1. restore images with magisk
2. Perform the OTA update, I skip the restart
3. then install magisk to the inactive slot
Then after a restart, the slot does change to inactive slot however the update has not been applied
I have tried both magisk stable and canary
ahh123 said:
I'm trying to update to 11.2.3.3.LE15AA by OTA after rooting but having issues.
I've done the following
1. restore images with magisk
2. Perform the OTA update, I skip the restart
3. then install magisk to the inactive slot
Then after a restart, the slot does change to inactive slot however the update has not been applied
I have tried both magisk stable and canary
Click to expand...
Click to collapse
What do you mean by "restore images with magisk"?
Are you getting your OTA as an incr update, or are you downloading the full update? I think you have to use full update for a rooted device, but 11.2.3.3 isn't showing up for me in oxygen updater yet so I've only updated to 11.2.2.2.
Steps I followed for 11.2.2.2 update:
1) disable magisk modules
2) download full update from oxygen updater
3) perform update via local install, don't reboot
4) install magisk to inactive slot
terlynn4 said:
What do you mean by "restore images with magisk"?
Are you getting your OTA as an incr update, or are you downloading the full update? I think you have to use full update for a rooted device, but 11.2.3.3 isn't showing up for me in oxygen updater yet so I've only updated to 11.2.2.2.
Steps I followed for 11.2.2.2 update:
1) disable magisk modules
2) download full update from oxygen updater
3) perform update via local install, don't reboot
4) install magisk to inactive slot
Click to expand...
Click to collapse
Oh that makes sense. It's the incremental update.
Thanks
What I did on the OP9 to get the incremental was disable all modules and restore stock boot image in magisk. Rebooted and did the incremental update then rerooted using fastboot boot boot.img then letting magisk backup the new image and root.
A bit of a hassle but worth it when you don't want to wait for full update to become available
ahh123 said:
I'm trying to update to 11.2.3.3.LE15AA by OTA after rooting but having issues.
I've done the following
1. restore images with magisk
2. Perform the OTA update, I skip the restart
3. then install magisk to the inactive slot
Then after a restart, the slot does change to inactive slot however the update has not been applied
I have tried both magisk stable and canary
Click to expand...
Click to collapse
I was in the same situation yesterday. In fact, the incremental update has been installed, try fastboot --set-active to force boot to inactive slot
xls654 said:
I was in the same situation yesterday. In fact, the incremental update has been installed, try fastboot --set-active to force boot to inactive slot
Click to expand...
Click to collapse
For some reason I get qualcomm crashdump when I try to set to the b slot. Any ideas on what I could be doing wrong? I followed the same steps that ahh did
Related
I did some searching, but could not see a guide for moving from Magisk rooted 8.1.0 to Magisk rooted 9.0. I believe I need to uninstall Magisk, then install the update, but not sure of the exact process. Also, is it better to wipe the data when going from 8.1.0 to 9.0 or doesn't matter?
Thanks in advance!
There's two ways you can do this.
One, you can sideload the OTA using ADB (if on stock recovery), or you can flash the OTA through TWRP.
Two, you can download the factory image, and manually flash the bootloader and radio, then update /system WITHOUT the -w flag, if you don't want to wipe data.
Any time you flash a software update, whether it's the OTA or the factory image, it WILL overwrite /boot, so you will lose Magisk and any custom kernel and recovery. Simply boot TWRP using fastboot, flash Magisk (and TWRP and kernel if desired), and you'll be good to go.
No need to wipe data. My process for installing OTAs and re-rooting has always been the same and it's no different with the 9.0 update other than one exception I encountered (patching the boot image AFTER updating).
I prefer the boot image patching method:
Download the latest platform-tools from Google
Download both the OTA and full factory images
Extract boot.img from the factory image
If already rooted prior to updating, re-flash current stock boot image
Sideload OTA
Patch the extracted boot image with Magisk (make sure you're on the latest version; 16.7 beta channel)
Flash patched boot image
Normally I patch the boot image prior to sideloading the OTA but it resulted in an endless boot after the 9.0 update.
Thanks guys. I actually found a thread I bookmarked previously on this topic. Do you think this would work well still? :
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
Also I saw some people mentioning trouble with Magisk after 9.0 update. Did you encounter that or anything special to consider there?
machx1111 said:
Thanks guys. I actually found a thread I bookmarked previously on this topic. Do you think this would work well still? :
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
Also I saw some people mentioning trouble with Magisk after 9.0 update. Did you encounter that or anything special to consider there?
Click to expand...
Click to collapse
Here's a bit more specific guide for updating to 9.0
https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77269862
Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you
suloku said:
Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you
Click to expand...
Click to collapse
Try flashing the older patched boot.img on the new stock firmware.
On the 12.5.3.0 ill patched boot.img from 12.5.1.0 and all right.
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
i have the same issue of auto updated and lost my root access.
Which boot.img I should Magish'd to get the root access again?
Currently installing my twrp
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
if Flash Current TWRP fails, go to Backup > Refresh Sizes and try Flash Current TWRP again
Click to expand...
Click to collapse
Currently at the Resizing stage
Edit 1: failed, I have the error bootctrl error that prevent me from installing after resizing.
I have flashed the twrp3.5.2 directly to boot resulting in bootloop and needed to install the Boot.img from the 12.5.1 from the previous bulit
Edit: actually I can ignore that error.
Magisk installed but safety checked failed even I have the "universal safety check module installed "
Also the app thoax isn't working
I'd try removing all magisk modules, installing stock 12.5.3, then using magisk apk to create patched boot.img and flash it with fastboot (fastboot flash boot magisk_boot_patched.img)
Also, maybe try flashing bot boot_a and boot_b? I had a problem were my active boot partition changed and phone became even more broken.
suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
Might wanna also uncheck Automatic system updates in the Developer settings to be safe.
suloku said:
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
There is a setting in the Xiaomi system updater that had by default checked auto-update. That setting need to be disabled/unchecked as well.
Since you have root with Magisk, can also Force stop or debloat the updater app, so the system will not update itself.
suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
I had the same issue on Redmi Note 9 Pro (joyuse). Based on your tip I've removed some modules from `data/adb/modules` and my device is finally booting normally. Thanks!
So I had Magisk. I uninstalled it via the app, preformed a system update, then avoided the reboot, installed Magisk on the OTA partition and rebooted. This got me into fastboot mode multiple times until my phone booted. Now I booted up and I am in the Feb update partition with no Magisk. How do I root and update without losing my data?
mkhcb said:
So I had Magisk. I uninstalled it via the app, preformed a system update, then avoided the reboot, installed Magisk on the OTA partition and rebooted. This got me into fastboot mode multiple times until my phone booted. Now I booted up and I am in the Feb update partition with no Magisk. How do I root and update without losing my data?
Click to expand...
Click to collapse
Since you are having problems with updating via OTA, suggest either using flash-all method or Android Flash Tool to update to March build. Then patch boot image using either Canary 24301 or Stable 24.3. Make sure to disable mods before rooting.
No such thing as a match update
mkhcb said:
So I had Magisk. I uninstalled it via the app, preformed a system update, then avoided the reboot, installed Magisk on the OTA partition and rebooted. This got me into fastboot mode multiple times until my phone booted. Now I booted up and I am in the Feb update partition with no Magisk. How do I root and update without losing my data?
Click to expand...
Click to collapse
I would use the Android flashtool and download the factory image , patch the boot image then flash it in fastboot. No loss of data, just make sure you don't check any of the boxes like 'wipe device' or 'lock bootloader' in flashtool settings
I just flashed March. Used all old school flashed with latest adb and fastboot
Disabled all the magisk modules just in case.
Patched March update boot file in Magisk
Had the update for Magisk and did not do it at this point, as I had heard people having issues with that.
booted into bootloader Flashall.bat removing -w
booted into phone, waited for update to finish in the notifications.
booted phone back into bootloader, installed magisk boot image
Booted phone back up
enabled all magisk modules
Updated magiskapp, then updated root via direct install
Rebooted phone
And all good
Wondering what would happen if I downloaded an image, extracted the boot.img, patched it, then took the OTA, stopped at reboot to install update, flashed the patched boot image, then rebooted?
android_dan said:
Wondering what would happen if I downloaded an image, extracted the boot.img, patched it, then took the OTA, stopped at reboot to install update, flashed the patched boot image, then rebooted?
Click to expand...
Click to collapse
you need to uninstall magisk, click on uninstall magisk and click on restore images, after that you can download and intall the update, after update, flash the patched boot.img from the last update package
spinoza23 said:
you need to uninstall magisk, click on uninstall magisk and click on restore images, after that you can download and intall the update, after update, flash the patched boot.img from the last update package
Click to expand...
Click to collapse
Why would I need to uninstall magisk? I use to do something like this with my OP8 and CRdroid. I downloaded the update, extracted the boot image, patched it, reinserted the patched boot image into the update, then ran the install command in adb. In this case I'm simply inserting the patched boot image onto the phone before rebooting.
android_dan said:
Why would I need to uninstall magisk? I use to do something like this with my OP8 and CRdroind. I downloaded the update, extracted the boot image, patched it, reinserted the patched boot image into the update, then ran the install command in adb. In this case I'm simply inserting the boot image onto the phone before rebooting.
Click to expand...
Click to collapse
Because, your current patched boot.img don't allow you to install the update, you will get an error...this is a pixel, I came from oneplus 8 pro and this is some strange for me too
android_dan said:
Why would I need to uninstall magisk? I use to do something like this with my OP8 and CRdroind. I downloaded the update, extracted the boot image, patched it, reinserted the patched boot image into the update, then ran the install command in adb. In this case I'm simply inserting the boot image onto the phone before rebooting.
Click to expand...
Click to collapse
If you are rooted when taking the OTA (even before rebooting) you will fail the pre-OTA block verifications. What it sounds like you are trying to do is update via the "Install to Inactive Slot" method in Magisk, but manually. Why not just do it through Magisk (although this method has been sort of hit or miss for some people)?
Lughnasadh said:
If you are rooted when taking the OTA (even before rebooting) you will fail the pre-OTA block verifications. What it sounds like you are trying to do is update via the "Install to Inactive Slot" method in Magisk, but manually. Why not just do it through Magisk (although this method has been sort of hit or miss for some people)?
Click to expand...
Click to collapse
Because I've tried that like four times. The first it worked, Last three it took multiple attempts to get the phone to boot and lost root.
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