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
Related
I got the update for the January Security Update today. I grabbed the .zip's location and the link on Google's servers is:
https://android.googleapis.com/pack...51c56752.signed-angler-MMB29P-from-MMB29M.zip
Hope it helps others!
PSA: this is not flashable over custom ROMs, and cannot be used to install the factory OS from nothing. That's what the factory images are for . This .zip is solely to incrementally update from the December security update to the January one.
Is there an easy way to flash this update.zip without the need of a computer?
tinker_tf said:
Is there an easy way to flash this update.zip without the need of a computer?
Click to expand...
Click to collapse
Unless you have a custom recovery, no. Sorry about that
Updated. Thanks for the link!
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Also, I don't have the December update, where do I find that?
And lastly, I'm on MDB08L Build, will that work?
For those wanting to use this update and have completely stock system based on MMB29M. Boot into recovery and do an ADB sideload update.zip (rename zip first). Mine updated with no issues.
CipherSec said:
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Click to expand...
Click to collapse
If you've got all that set up, why not just update using the full factory image (without the wipe)
LeoRex said:
If you've got all that set up, why not just update using the full factory image (without the wipe)
Click to expand...
Click to collapse
I assumed I'll lose all my system modifications (i.e. Xposed Modules and their settings) as well as losing root and TWRP and having to reroot again.
pmedwards25 said:
Unless you have a custom recovery, no. Sorry about that
Click to expand...
Click to collapse
This is exactly the file you need if you don't have custom recovery, don't have root, and have not unlocked bootloader. It is the same file that would eventually come to you OTA. You do however need access to adb and a computer. I don't think this is flashable with a custom recovery.
Thanks..
Thanks for this file bro. dont need to wait.
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Casyis said:
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Click to expand...
Click to collapse
Try flash stock system image
Does this update fix the LTE issue?
HRodMusic said:
Does this update fix the LTE issue?
Click to expand...
Click to collapse
No it does not
I got it:
For systemless root, fastboot flash: 1) boot.img; 2) recovery.img; 3) vendor.img; 4) system.img
Boot to recovery and enter sideloade mode. adb sideload [update].zip
Reboot to bootloader. Re-flash TWRP, then in TWRP re-flash kernel (if custom) & superSU.
I used a toolkit to root my 6P. I'm using rooted stock rom. I got an OTA update but it seems I can't update it that way as per all others. So how do I go about installing this on my mobile? Do I need to unroot, flash stock recovery & then flash the new image? Then again I have to root?
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
asj0422 said:
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
Click to expand...
Click to collapse
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
kmp14 said:
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
Click to expand...
Click to collapse
i just tried this again with the same results. it says that the installer is expecting a different build (the one that my settings app shows i'm on) but that i have a build called huawei/mmasomething/ dee_stroyer somethingsomething. (i would post exactly what it says but i've already rebooted into system). I do remember something with "dee_stroyer" when i was rooting but it's not the system...
anyone else have any ideas? i'd like to just update normally and keep my data... and the stock android with root.
EDIT: also, the update won't update my recovery will it? i don't want to have to reflash that. i should be able to update even when i'm away from a computer haha.
Rooted with TWRP. I just tried an ADB sideload and get the same error.
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.
Desperate help needed to go back to stock (Mate 10 Pro EMUI 8 TWRP & MAGISK) BLA-L09
Hello there. I'm used to Samsung devices and the more I read about Huawei devices the more lost I feel about them.
So, my Mate 10 pro BLA-L09 is currently running Build Number 8.0.0.131(C782). It is rooted with Pretoriano's TWRP and Magisk (Using the All-In-One tool). Of course, I can't get any pending update installed. I would like to receive that EMUI 9 update. I've read people have been successful using HuRupdater and some others ended up with a hard bricked device. Some other people suggest the safest option is to uninstall Magisk, flash stock recovery and let the phone update itself.
So far, I've downloaded the same full 8.0.0.131(C782) firmware I'm on from Firmware Finder and downloaded Huawei Update extractor to extract the recovery from UPDATE.APP. However, instead of having one recovery file to extract, there are 3 Recoveries (named: RECOVERY_RAMDIS, RECOVERY_VBMETA, RECOVERY_VENDOR) and another 4 E-Recoveries.
Can anyone please give me some step by step guidance on what to do? I'll Paypal you a beer if I'm successful with the help.
Cheers!
May be you can simply dload the firmware and then it should be full stock if dload works. Dload guide is given in my signature
shashank1320 said:
May be you can simply dload the firmware and then it should be full stock if dload works. Dload guide is given in my signature
Click to expand...
Click to collapse
Thanks! But I think dload won't work with custom recovery, right? I'm on TWRP. And getting stock recovery is just what I'm trying to achieve.
93starletgt said:
Thanks! But I think dload won't work with custom recovery, right? I'm on TWRP. And getting stock recovery is just what I'm trying to achieve.
Click to expand...
Click to collapse
Dload replaces your twrp and custom boot both. It will bring back your phone to full stock. Else you could extract the images from your firmware and then flash. Let me give you the commands.
Thanks! I just fixed my issue by flashing this through TWRP: it Installs the Oreo stock recovery.
The procedure was:
-Booted into TWRP
-Uninstalled Magisk (by flashing Magisk Uninstall Zip)
-Flashed the stock recovery (from the link below) through TWRP
-Reboot
-Check for system updates, phone will install them with no problems
Phone will be unrooted and will have stock recovery. Don't know if this will work for every stock build, it worked with mine 8.0.0.131(C782).
Link:
https://mega.nz/#!8Swx3QaC!3JQ9imU70E9O1BxgO53Z754lGCZxCbKGgSHqvTEcXsQ
I was getting the command ready for you. Glad you fixed it yourself
[*]Run the command to boot to fastboot
Code:
adb reboot bootloader
[*]On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
[*]Flash the stock Recovery Ramdisk as
Code:
fastboot flash recovery_ramdisk <Recovery_File_Name>.img
[*]If you have installed magisk, flash the stock boot ramdisk.img as
Code:
fastboot flash ramdisk <ramdisk_File_Name>
Hello,
i'm trying to root a Sharp B10 (SH-A01) with Magisk.
It would be nice if i could do this without unlocking because i want to keep the stock rom anyway.
First problem is that i can't find a custom recovery (TWRP, CWM) for this device from where i could install Magisk.
Then i found out that Magisk gives the possibility to root a device through the Magisk Manager App by patching the boot.img.
But the second problem is that i can't find the boot.img either. I spotted the boot partition on the device and tried to pull with adb but i would need an already rooted device to give the needed permissions.
Is there anything else I could do to get this thing rooted besides compiling my own TWRP for the device?
thanks a lot,
paul
Hello, i search the same.
paulquappe said:
Hello,
i'm trying to root a Sharp B10 (SH-A01) with Magisk.
It would be nice if i could do this without unlocking because i want to keep the stock rom anyway.
First problem is that i can't find a custom recovery (TWRP, CWM) for this device from where i could install Magisk.
Then i found out that Magisk gives the possibility to root a device through the Magisk Manager App by patching the boot.img.
But the second problem is that i can't find the boot.img either. I spotted the boot partition on the device and tried to pull with adb but i would need an already rooted device to give the needed permissions.
Is there anything else I could do to get this thing rooted besides compiling my own TWRP for the device?
thanks a lot,
paul
Click to expand...
Click to collapse
Neither Magisk nor TWRP is needed to root Android: Chainfire's SuperSu does the job. You flash its ZIP via stock recovery "adb sideload"
jwoegerbauer said:
Neither Magisk nor TWRP is needed to root Android: Chainfire's SuperSu does the job. You flash its ZIP via stock recovery "adb sideload"
Click to expand...
Click to collapse
Hi,
thanks for your answer.
I already managed to root this device. I got the boot.img with Wwr_MTK & SP flash tool (windows tools...), patched it with the magisk app and than flashed the patched boot.img
1. Unlock your bootloader enter in download mode Vol+ + Vol- + USB conected to pc (Keep in mind that by doing this you will lose your files, it is advisable to make a backup of your photos, music, etc.)
2. Once you start your cell phone install magisk manager, Choosing the boot.img file of your rom into the app (Tip: Only!!! If your model is SM-A015M Android 11 I leave you my own modified boot.img to flash:
File on MEGA
mega.nz
Otherwise, you can download the firmware (3.79 gb) and extract the boot.img from the firmware of your model SM-A015 M / F ... Android 10, Android 11... etc. And No need for pc
https://samfrew.com/model/SM-A015M/
3. The image will begin to flash
4. When it restarts you will have Root on the cell phone!
------------------------------------------------------------------------------------------------------------------------------------------------
Extra: If you need the custom recovery I give you the link with my TWRP which is installed through the Odin program on a PC (this step does not delete your files)
File on MEGA
mega.nz
Keep in mind that to install TWRP you must deactivate the DM-VERITY & FORCEENCRYPT DISABLER I leave it in a link:
Zackptg5 - Android
zackptg5.com
This is a module that can be installed via magisk, which is necessary to decrypt the system ... so once TWRP is installed, it is advisable to uninstall it via Magisk to avoid R / W errors
Hi, I'm having trouble with Magisk re-installation.
First I installed Magisk using the flashing boot.img method, it was working correctly but I tried to remove the youtube vanced module, when it asked for a reboot it went straight to the bootloader, I just re-flashed the original boot.img to the phone and got it working again. the issue came when I tried to reinstall Magisk from scratch again. Whenever I tried to install it the process would go without any issue but when I tried to start the system it is going to the bootloader again.
I tried installing twrp using this guide and got the custom recovery working on both slots, then I tried to flash magisk using the zip file, the installer ran without throwing any issues but when I tried to reboot again to the system it still goes to fastboot, this time not only corrupting the system start but also the twrp recovery. I haded to reflash the stock boot.img image on slot A and the twrp image on slot B to re install twrp on both slots.
Also using the TWRP tried running the uninstall magisk zip but whenever I try to run it it just fails because it cannot find the magisk.img file and exits by telling that I have not installed magisk.
Tried erasing the folders inside of /data/adb but its the same issue all over again.
Does anyone has any idea or suggestion on what could I try to fix the issue?
Thanks
Try flashing patched boot image (the same version as your system) and boot into the system, go into magisk manager and do complete uninstall. Or download the latest Magisk uninstaller and try from TWRP again. Recent versions of Magisk ditched magisk.img, so you might be using old version of the uninstaller.
_mysiak_ said:
Try flashing patched boot image (the same version as your system) and boot into the system, go into magisk manager and do complete uninstall. Or download the latest Magisk uninstaller and try from TWRP again. Recent versions of Magisk ditched magisk.img, so you might be using old version of the uninstaller.
Click to expand...
Click to collapse
Tried using the lastest uninstaller found on the topjohnwu/Magisk repository, which did not show any error but after installing magisk the phone still goes to bootloader, then tried to run the uninstaller again but it only works on the b slot and to run it on the a slot I have to reflash boot.img and then install twrp on both slots.
But thanks for the sugestion.
jtcp2703 said:
Tried using the lastest uninstaller found on the topjohnwu/Magisk repository, which did not show any error but after installing magisk the phone still goes to bootloader, then tried to run the uninstaller again but it only works on the b slot and to run it on the a slot I have to reflash boot.img and then install twrp on both slots.
But thanks for the sugestion.
Click to expand...
Click to collapse
I would restore stock ROM, skip TWRP installation and flash just correct patched boot image.
_mysiak_ said:
I would restore stock ROM, skip TWRP installation and flash just correct patched boot image.
Click to expand...
Click to collapse
Do you know where can I find the lastest stock rom? Right now I'm on 10.3.9.0 PFQEUXM, or if the lastest is not possible, could I flash a older version of the rom without any trouble?
jtcp2703 said:
Do you know where can I find the lastest stock rom? Right now I'm on 10.3.9.0 PFQEUXM, or if the lastest is not possible, could I flash a older version of the rom without any trouble?
Click to expand...
Click to collapse
Try to find the full OTA zip for the latest version (or at least the same you have) and extract it with this tool https://github.com/cyxx/extract_android_ota_payload
Xiaomi hasn't released the fastboot rom for the recent updates yet.
So far I was able to find only global links here (they should work too, but rather backup your data first). http://4pda.ru/forum/index.php?showtopic=962154
You might have luck installing older fastboot EU ROM, but again, backup your data first.
If you did not enable "allow system modifications" in TWRP, it should be enough to flash only stock boot image (there are links to them somewhere on this forum).
Also I would avoid installing TWRP.
Sapper Morton said:
The complete firmware images, can only be found in .tgz archives, payload.bin OTAs only contains incremental firmware updates; thus you won't be able to successfully restore, system, vendor, boot, critical partitions and etc; the recommended method is to restore to either 10.3.4.0 PFQMIXM or 10.3.7.0 PFQEUXM, both .tgz archives, complete firmware inside. @_mysiak_
Click to expand...
Click to collapse
There are usually two types of OTA zip files, small incremental ones (which you described) - for monthly updates and full OTA (1-2gb in size) - for direct update across several versions. You can create all needed fastboot images from the full OTA payload.bin with before mentioned python extractor script.
Sapper Morton said:
You can try for yourself, I wasn't able to restore using this images (assuming of course you have a corrupt, system, vendor, boot, ... partition): https://bigota.d.miui.com/V10.3.6.0...UTGlobal_V10.3.6.0.PFQMIXM_00713c5a1d_9.0.zip
I was only able to return to global channel, by using 10.3.4.0 PFQMIXM firmware, .tgz archive.
Click to expand...
Click to collapse
By wasn't able to restore you mean that you couldn't convert payload.bin to fastboot images, or that converted fastboot images were not working?
I've just extracted these files from payload.bin from the link you provided (with this app). I don't have a phone to test them though (I did the same thing a few times on Mi A1 and flashing, phone and OTA worked afterwards).
Code:
abl.img
bluetooth.img
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
dtbo.img
hyp.img
imagefv.img
keymaster.img
modem.img
product.img
qupfw.img
rpm.img
storsec.img
system.img
tz.img
uefisecapp.img
vbmeta.img
vendor.img
xbl.img
xbl_config.img