This may be known to many but there are many users who were struggling with this.
Hello Folks,
Was getting few requests on XDA, Telegram and Facebook for this. As title says, there were few users reporting OTA failures while they were rooted with Magisk. Yes, that's obvious, it will fail as you have modified the boot.img (ramdisk) and stock recovery (Recovery_ramdisk.img) while rooting and installing TWRP.
Please follow below steps to update via OTA if you were rooted or using magisk.
Uninstall busybox binaries and Xposed framework (if you are using by any chance)
Uninstall Magisk (inside the app or by flashing the magisk uninstaller via TWRP)
Download update.app of your current firmware and extract stock recovery and boot file via Huawei extractor
Flash stock recovery of your actual variant as fastboot flash recovery_ramdisk recovery.img
Flash stock boot as fastboot flash ramdisk ramdisk.img
Boot to system.
Perform OTA update and reboot.
Root your phone again if you want.
Enjoy.
You could just :
1.patch the new ramdisk's update via magiskmanager then,
2.update via HuRUpdater without removing your root before,
3.then reboot straight to fastboot, and flash your new patched ramdisk
4.reboot to your rooted updated firmware with magisk module still working and root mods still applyied.
PS: I don't know about xposed frameworks
shashank1320 said:
This may be known to many but there are many users who were struggling with this.
Hello Folks,
Was getting few requests on XDA, Telegram and Facebook for this. As title says, there were few users reporting OTA failures while they were rooted with Magisk. Yes, that's obvious, it will fail as you have modified the boot.img (ramdisk) and stock recovery (Recovery_ramdisk.img) while rooting and installing TWRP.
Please follow below steps to update via OTA if you were rooted or using magisk.
Uninstall busybox binaries and Xposed framework (if you are using by any chance)
Uninstall Magisk (inside the app or by flashing the magisk uninstaller via TWRP)
Download update.app of your current firmware and extract stock recovery and boot file via Huawei extractor
Flash stock recovery of your actual variant as fastboot flash recovery_ramdisk recovery.img
Flash stock boot as fastboot flash ramdisk ramdisk.img
Boot to system.
Perform OTA update and reboot.
Root your phone again if you want.
Enjoy.
Click to expand...
Click to collapse
Do we need to keep "Enable OEM Unlock" checked or unchecked in developer settings?
mohsyn said:
Do we need to keep "Enable OEM Unlock" checked or unchecked in developer settings?
Click to expand...
Click to collapse
Doesn't matter unless you are rooting
shashank1320 said:
Doesn't matter unless you are rooting
Click to expand...
Click to collapse
Thanks
I am unable to download OTA update through system
I have the zips downloaded using firmware finder but both the dload and copying the zips to /data/update/HWoUC folder fails
dload method keeps throwing erecovery on screen and does nothing
my recovery + ramdisk + kernal are all stock
magisk completely removed
bootloader unlocked
frp unlock
am i missing something or is there some other manual update method
mohsyn said:
Thanks
I am unable to download OTA update through system
I have the zips downloaded using firmware finder but both the dload and copying the zips to /data/update/HWoUC folder fails
dload method keeps throwing erecovery on screen and does nothing
my recovery + ramdisk + kernal are all stock
magisk completely removed
bootloader unlocked
frp unlock
am i missing something or is there some other manual update method
Click to expand...
Click to collapse
It should be hwouc folder directly under root of internal memory and not data/update/hwouc
I want to root my poco f1 ....
But i have some questions regarding it
1. Will my data be format while rooting and installing twrp
2. How i will get ota update
3. Will installing ota update also format my data?
1. Your whole internal data needs to be wiped... To flash the force decryption enabler at first...
Even while installing twrp via fastboot.. Your data will be formated
2. You will get updates... But not via ota.... Yes you will get to download the updateds in some roms... But you need to dirty flash them.
3. While dirty flashing.... Formatting data is not required.
roxor101 said:
1. Your whole internal data needs to be wiped... To flash the force decryption enabler at first...
Even while installing twrp via fastboot.. Your data will be formated
2. You will get updates... But not via ota.... Yes you will get to download the updateds in some roms... But you need to dirty flash them.
3. While dirty flashing.... Formatting data is not required.
Click to expand...
Click to collapse
Does the twrp with working decryption also need to format my data?
You can root your device in two ways.
First, with twrp (OTA won't work afterwards)
Second, without twrp (OTA will work)
First method, unlock the bootloader (device will be wiped)>Grab the twrp with working decryption>Boot your device into fastboot and type fastboot flash recovery twrp.img (or whatever the recovery image name is)>Now type fastboot boot twrp.img (or whatever the recovery image name is)>Once booted into twrp, swipe to allow modification>Now download Magisk installer and copy into the device>Flash it?Reboot to system>Profit.
N.B. After flashing twrp, make sure to first boot into twrp before booting into system or else device will restore stock recovery. If you need to update in future, just grab the twrp flashable update package and flash it. That's it. No need for OTA.
Second method, this will also require an unlocked bootloader. Once the bootloader is unlocked, get the stock boot image of your current software (e.g. if you are on miui 10 with October security patch, make sure to grab the stock boot image for miui 10 october). Now install Magisk manager apk in your device. Now open magisk manager and go to install. You will find an option for patching stock boot image. Click on it and select the stock boot image. Magisk will patch the boot image and will place it in your internal memory. Now boot into fastboot mode and type fastboot boot patched_boot.img (or whatever the name is). Once device is booted into system, go to Magisk and click on Install>Direct install (recommended).Magisk will get flashed by itself and reboot. Once rebooted, go to Magisk manager and check. If you do everything correctly, you are rooted.
N.B. When you get an OTA update, open Magisk and go to Unsinatll and click on "Complete uninstall". It will uninstall magisk and revert your stock boot image back. Note that, if you play witgh system partition like modifying build.prop or change host file or bootanimantion or any such thing, you won't be able to get any further OTA update. In that case, you need to flash the complete fastboot rom through MiFlash tool.
For more information, please go to Magisk thread or search online.
Hi,
i have a problem rooting my Pixel 3.
it already worked, then i installed another rom which i did not like, so i re-installed the stock image from google (9.0.0 PQ1A.181205.006, Dec 2018).
But, here comes the problem, i can not install Magisk. When i do, my Pixel does not boot to system, but boots back to recovery or says can´t load android system.
this is how i do it:
1. flash factory image
2. boot to system
3. boot twrp
4. flash Magisk v18.0
also tried:
1. flash factory image
2. boot twrp directly
3. flash Magisk v18.0
this does not work. what i also tried is patch the stock boot.img with magisk and flash it to boot_a and boot_b. also did not work.
what am i doing wrong?
thnaks in advance for your help!
Spocki990 said:
Hi,
i have a problem rooting my Pixel 3.
it already worked, then i installed another rom which i did not like, so i re-installed the stock image from google (9.0.0 PQ1A.181205.006, Dec 2018).
But, here comes the problem, i can not install Magisk. When i do, my Pixel does not boot to system, but boots back to recovery or says can´t load android system.
this is how i do it:
1. flash factory image
2. boot to system
3. boot twrp
4. flash Magisk v18.0
also tried:
1. flash factory image
2. boot twrp directly
3. flash Magisk v18.0
this does not work. what i also tried is patch the stock boot.img with magisk and flash it to boot_a and boot_b. also did not work.
what am i doing wrong?
thnaks in advance for your help!
Click to expand...
Click to collapse
You've got the kernel and recovery messed up on your device from the failed flash of twrp and magisk. I would start over by flashing the factory image using the flash all batch file with the -w edited out of it. Then try again booting twrp, not flashing it. Once you try to flash the twrp image file you pretty much have to start over with the stock boot image. When you boot into twrp you'll want to allow modifications. You also need to setup a pin or pattern security for your system so twrp will decrypt your device.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks for the hint. It works now. But had to use the patched boot image from this link.
https://www.google.de/amp/s/forum.x...o-root-pixel-3-xl-magisk-t3856712/amp/?espv=1
Spocki990 said:
Thanks for the hint. It works now. But had to use the patched boot image from this link.
https://www.google.de/amp/s/forum.x...o-root-pixel-3-xl-magisk-t3856712/amp/?espv=1
Click to expand...
Click to collapse
you are my hero. My phone was stuck in the situation you describe after installing active edge. I was thinking about wipe my pixel 3 until I saw your post. Thank you !:good:
How Can I Flash the December security update in my magisk rooted device? If I tray the "normal" way it gives me an error.
Hi. I had the same problem. Tried with restoring stock rom without wipe, but no go. Still error.
I ended up backing up my stuff and flashed stock with wipe, and then everything went well.
After your procedure what boot.img you use to reinstall magisk?
Usually when the bootloader is unlock is impossible to install any official update.
In that case I have the same problem, and I think the solution is to lock the bootloader, try to apply the update and to see if root still works. ( I am sure not).
In other case is, unlock the bootloader again, to wait the official ROM with December patch, extract boot.img, rebuild it with magisk and install it with fastboot and wait the final result.
Is crazy but while there is not another solution is a good way to have root on this Moto One.
skia16 said:
After your procedure what boot.img you use to reinstall magisk?
Click to expand...
Click to collapse
I booted up twrp and made a backup of boot.img, then patched it and flashed with fastboot.
tys0n said:
I booted up twrp and made a backup of boot.img, then patched it and flashed with fastboot.
Click to expand...
Click to collapse
I follow this way but magisk manager tells me that magisk Is not installed
skia16 said:
I follow this way but magisk manager tells me that magisk Is not installed
Click to expand...
Click to collapse
skia16 said:
I follow this way but magisk manager tells me that magisk Is not installed
Click to expand...
Click to collapse
Make a backup of boot in twrp.
Go to backup folder and make a copy of it somewhere. Rename the copy from "boot.emmc.win" to "boot.img".
Open Magisk manager, select install, choose "patch boot image file" and select the boot.img-file to patch.
It will unpack, patch and repack the boot.img for magisk functionality.
Move the patched_boot.img to pc and flash it with fastboot. "fastboot flash boot patched_boot.img".
Reboot, open Magisk manager. It should now ask to continue with environmental setup.
Or if you have the firmware package, you could just extract boot.img from it, put it on phone and patch it instead of using boot from twrp back up.
Hi everyone, I am recently registered on this site. from some days I have the desire to do the Root on the miui global stable, it is consequently on my beloved Xiaomi Mi 8, the problem is: when the device is turned off I turn on the device pressing it under volume key + ignition key at the same time to enter in recovery mode, the latter makes me enter in "Official" mode, in the sense that it does not let me enter twrp mode where there are install, settngs, advacend options, backup ... but in the official one with only 3 buttons: wipe , connect to mi account ... So I thought of flashing the twrp via fastboot, I finally entered it, but the problem is that when I go to Install, to install the root, I can't do that, because characters (alphanumeric) appear long and randomly, so I can't identify which folder I put the Magisk on, it appears in both folders and subfolders. somewhere I read to install a zip file called LazyFlasher, to avoid possible blocking at startup, in fact I try before installing this zip file, with various combinations (first rom, then magisk, both rom and magisk, first magisk then rom , first rom that gate at the end the cache then magisk) but all fail, so I am forced to flash through fastboot with the tool I flash, because at every start it always took me back to twrp without the possibility of moving, it seems that the touch does not respond at the user's commands. So I know that this LazyFlasher file causes me to "bypass" this problem, give me confirmation ??. Thank you. PS: so far I haven't managed to install the Magisk root yet, can you give me a hand, maybe the twrp has some problems? or is my device not compatible with this version of twrp ??, I tell you that in the past with the miui global beta it didn't give me this problem. Thank you all
Have you even unlocked your bootloader? If not look for the official Xiaomi tool, it's the only way how you are able to flash twrp and root your phone.
altae said:
Have you even unlocked your bootloader? If not look for the official Xiaomi tool, it's the only way how you are able to flash twrp and root your phone.
Click to expand...
Click to collapse
Thanks for the reply, I solved everything, unlocked BL, installed twrp (no stock) and installed root. but I have a problem, when I installed the root, every time I want to restart the device for a series of reasons (slowness, delete cache, rest ...) it starts in twrp not in the system, so I have to delete everything it's starting again. I heard that the LazyFlasher file makes it possible to remedy this problem, essentially it allows you to bypass the security of android to avoid bootloap, and I hope it also corrects this problem (which when I reboot the device, I want to install a zip file, I it always starts in twrp), but during the flash of this zip (LazyFlasher) I get an error: the Updater process ended with error: 1 Error installing zip '/sdcard/lazyflasher-no-verify-opt-encrypt.zip. Thanks a lot. PS: but this file, lazyflasher should be mounted on an SD card to work ?? I don't have it on my device
Paoloqu24 said:
Thanks for the reply, I solved everything, unlocked BL, installed twrp (no stock) and installed root. but I have a problem, when I installed the root, every time I want to restart the device for a series of reasons (slowness, delete cache, rest ...) it starts in twrp not in the system, so I have to delete everything it's starting again. I heard that the LazyFlasher file makes it possible to remedy this problem, essentially it allows you to bypass the security of android to avoid bootloap, and I hope it also corrects this problem (which when I reboot the device, I want to install a zip file, I it always starts in twrp), but during the flash of this zip (LazyFlasher) I get an error: the Updater process ended with error: 1 Error installing zip '/sdcard/lazyflasher-no-verify-opt-encrypt.zip. Thanks a lot. PS: but this file, lazyflasher should be mounted on an SD card to work ?? I don't have it on my device
Click to expand...
Click to collapse
Flash a DM-Verity No-Encryption ZIP to remove encryption and disable the Verity check. OR if you want to keep encryption and root -flash a 3rd party Kernel like MiPa or Sphinx after Magisk.
Agimax said:
Flash a DM-Verity No-Encryption ZIP to remove encryption and disable the Verity check. OR if you want to keep encryption and root -flash a 3rd party Kernel like MiPa or Sphinx after Magisk.
Click to expand...
Click to collapse
thank you. in the past I flamed DM-Verity No-Encryption ZIP to remove encryption and disable Verity checking. in fact after immediately this zip I put magisk. at the access of the dispay I saw a magisk icon, so it means root installed successfully. but the problem is: when I reboot the device to clear the cache ... or install a module on the magisk, it always starts in twrp, so I have to start all over again. there is a way to keep cryptography and root, without any booting going into twrp but into the system. thank you
Paoloqu24 said:
thank you. in the past I flamed DM-Verity No-Encryption ZIP to remove encryption and disable Verity checking. in fact after immediately this zip I put magisk. at the access of the dispay I saw a magisk icon, so it means root installed successfully. but the problem is: when I reboot the device to clear the cache ... or install a module on the magisk, it always starts in twrp, so I have to start all over again. there is a way to keep cryptography and root, without any booting going into twrp but into the system. thank you
Click to expand...
Click to collapse
You shouldn't have these problems:
Flash ROM and Keep Encryption:
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'DM-Verity' file is the ONLY thing the file is named. The filename triggers what is installed during flash)
Flash MAGISK
Flash 3rd Party Kernel (I prefer MiPa or Sphinx found in other threads)
Reboot and enjoy!
Flash ROM and REMOVE Encryption: (Keeps Stock Kernel)
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'verity' AND 'forceencryp' is in the file name. The filename triggers what is installed during flash)
Reboot and enjoy!
If you have problems with any of them, you might need to format internal storage first (where you have to answer 'yes' in TWRP)
/.
As far as I understand, you are having problems while booting into TWRP. You should boot into TWRP right after flashing it, and boot into OS once again and reboot to recovery. It should work. If you see the stock recovery, keep flashing TWRP. If you want to temporarily flash it, use "fastboot boot TWRP.img" command.
The War Profiteer said:
As far as I understand, you can't boot into TWRP. You should boot into TWRP right after flashing it, and boot into OS once again and reboot to recovery. It should work. If you see the stock recovery, keep flashing TWRP. If you want to temporarily flash it, use "fastboot boot TWRP.img" command.
Click to expand...
Click to collapse
No problems booting into TWRP.
You can use "fastboot.exe flash recovery twrp.img"
Then reboot phone and hold volume-up+power. When booting until TWRP appears. If you miss it and it tries to boot it will overwrite it. But I've never had issues otherwise.
Agimax said:
You shouldn't have these problems:
Flash ROM and Keep Encryption:
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'DM-Verity' file is the ONLY thing the file is named. The filename triggers what is installed during flash)
Flash MAGISK
Flash 3rd Party Kernel (I prefer MiPa or Sphinx found in other threads)
Reboot and enjoy!
Flash ROM and REMOVE Encryption: (Keeps Stock Kernel)
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'verity' AND 'forceencryp' is in the file name. The filename triggers what is installed during flash)
Reboot and enjoy!
If you have problems with any of them, you might need to format internal storage first (where you have to answer 'yes' in TWRP)
/.
Click to expand...
Click to collapse
Thanks for the reply. I will choose the first option, I replace the stock kernel with sphinx kerne, so I get more functionality, battery life, performance, fluidity ... also the developer has mentioned us, if any desired functionality is missing in this kernel, it is possible ask the developer to add us. so I choose the first option, I have some questions before replacing the stock kernel: 1) is it possible to restore the kernel stock, in case of problem, if yes, where can I get the kernel for Mi 8? 2) if in the future there will be a new update of sphinx kerne, how do I understand if a new update has been released? will you notify me ?? 3) are you sure that after these steps, upon restarting the phone, I will find the root installed ?, if I would like to restart the device, it will not boot in twrp but in the system, because I replaced the stock kernel, the same thing is also valid for the magisk modules, zip files ... 4) the last fundamental thing, will I receive updates via OTA ?? if not, is there a way to install future updates (I would like to try the latest magisk version, 19.3) ?. 5) it is safe if I install update via ota, it does not start in twrp, but system. 6) the steps to do are, flash twrp custom via fastboot, I choose to delete the memory, restart twrp, copy the files (MIUI global stable, sphinx kernel, dm-verify), flash rom, flash dm-verify, flash magisk, flash kernel, device reboot, all right. Thanks a lot for the questions
Agimax said:
You shouldn't have these problems:
Flash ROM and Keep Encryption:
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'DM-Verity' file is the ONLY thing the file is named. The filename triggers what is installed during flash)
Flash MAGISK
Flash 3rd Party Kernel (I prefer MiPa or Sphinx found in other threads)
Reboot and enjoy!
Flash ROM and REMOVE Encryption: (Keeps Stock Kernel)
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'verity' AND 'forceencryp' is in the file name. The filename triggers what is installed during flash)
Reboot and enjoy!
If you have problems with any of them, you might need to format internal storage first (where you have to answer 'yes' in TWRP)
/.
Click to expand...
Click to collapse
I get an error during the installation of sphinx: the Updater process ended with error: 1 Error installing zip '/sdcard/sphinx.zip
Agimax said:
You shouldn't have these problems:
Flash ROM and Keep Encryption:
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'DM-Verity' file is the ONLY thing the file is named. The filename triggers what is installed during flash)
Flash MAGISK
Flash 3rd Party Kernel (I prefer MiPa or Sphinx found in other threads)
Reboot and enjoy!
Flash ROM and REMOVE Encryption: (Keeps Stock Kernel)
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'verity' AND 'forceencryp' is in the file name. The filename triggers what is installed during flash)
Reboot and enjoy!
If you have problems with any of them, you might need to format internal storage first (where you have to answer 'yes' in TWRP)
/.
Click to expand...
Click to collapse
both methods don't work, the first one gives me error when I install kernel, the second one on startup gives me a lot of error
I managed to install the root, doing the following steps: flash twrp via fastboot, copy the files to the internal memory, install rom files, install magisk files, install dm-verify, then reboot, and it works perfectly. but I have some problems: when I reboot the device, it starts in twrp not in the system, and therefore I am forced to do it again. help me !! kernel replacement gives me error, both
Paoloqu24 said:
I managed to install the root, doing the following steps: flash twrp via fastboot, copy the files to the internal memory, install rom files, install magisk files, install dm-verify, then reboot, and it works perfectly. but I have some problems: when I reboot the device, it starts in twrp not in the system, and therefore I am forced to do it again. help me !! kernel replacement gives me error, both
Click to expand...
Click to collapse
You should not have errors flashing a kernel. Maybe you should flash all partition images from fastboot. Or maybe wrong recovery? What version are you using?
Agimax said:
You should not have errors flashing a kernel. Maybe you should flash all partition images from fastboot. Or maybe wrong recovery? What version are you using?
Click to expand...
Click to collapse
the kernel is: Sphinx-v2.9
Paoloqu24 said:
the kernel is: Sphinx-v2.9
Click to expand...
Click to collapse
I mean what version of recovery. You should use this one (v3.3.1) or newer: https://www.androidfilehost.com/?fid=3556969557455275724
It's from this thread: https://forum.xda-developers.com/mi-8/development/recovery-unofficial-twrp-recovery-t3893823
Agimax said:
I mean what version of recovery. You should use this one (v3.3.1) or newer: https://www.androidfilehost.com/?fid=3556969557455275724
It's from this thread: https://forum.xda-developers.com/mi-8/development/recovery-unofficial-twrp-recovery-t3893823
Click to expand...
Click to collapse
TWRP 3.3.1.1 https://eu.dl.twrp.me/dipper/
I followed in this guide "https://clk.ink/7q4SUR" but instead of installing Disable_Dm-Verity_FEC_v1.1.zip I downloaded Disable_Dm-Verity_ForceEncrypt_09.02.2018.zip, is it the same ?, also I saw that, when I go inside the magisk, and I click on uninstall> restore image, a warning appears "there is no original boot image", I also executed this command in powershell "fastboot getvar current-slot" but I get a "GetVar Variable Not found" error. I don't know how to solve. thank you