Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty could be void if you tamper with any part of your device / software.
* Same statement for XDA.
Here's an alternative method to install Magisk that support OTA updates (copied from the Mi A1 forum and expanded )
You need a PC with Android platform tools (they exist also for MacOS and Linux). When using Windows, you should also install MiFlash tool to get the required drivers to recognize the device.
BOOTLOADER UNLOCK
First thing to do: unlock the bootloader (if you didn't already do this, obviously). Smartphones with Android One are much easier to unlock compared to other Xiaomi phones with MIUI (where you have to ask for authorization and wait for weeks).
CAUTION: when you unlock the bootloader, the phone will reset, erasing all your saved data. Backup your data before unlocking.
1. Go to Settings > System > About phone > and tap many times on "Build number" until you unlock "Developer options" (on Andoird 9 "About phone" is right at the top of the Settings app).2. Go back to the previous page (i.e. Settings > System), where you can find now "Developer options". Go there and enable the "OEM unlocking" option (and it's better to never disable this).3. Now you can shutdown your phone, then turn it on while holding the "Volume down" button pressed. Release it when you see the Fastboot screen You can also use the command "adb reboot-bootloader" if you already connected the phone to the PC.4. Now connect the phone with your PC via USB cable, open an administrative command prompt, move to the directory where the Android platform tools are placed and unlock the bootloader with the following command:
Code:
fastboot oem unlock
The phone will reboot, erasing all the data.
Now you unlocked your phone's bootloader and can continue to the next section.
MAGISK INSTALLATION
5. Download and install on the smartphone the latest version of Magisk Manager's apk available.
You need the smartphone to be connected to the internet, because Magisk won't install and won't work properly without a connection.
6. Now you can easily download an already patched boot.img from the following list and jump straight to point 10 of this guide, or you can continue to the next point and learn to patch yourself an original boot.img
If you choose the short way, be sure that you select the patched_boot.img with the same "Build number" currently installed on your phone (see point 1 of this guide), and don't flash the file directly on the phone memory, because Magisk will not work properly (do exactly what this guide says, and you will not find problems, hopefully).
For our convenience, extract the patched_boot.img file in the same directory where Android platform tools are located.
patched_boot 9.6.4.0 (2018 July update) - patched with Magisk 17.1
patched_boot 9.6.6.0 (2018 August update) - patched with Magisk 17.1
patched_boot 9.6.8.0 (2018 September update) - patched with Magisk 17.1
patched_boot 9.6.9.0 (2018 October update) - patched with Magisk 17.1
patched_boot 9.6.10.0 (2018 November 1st update) - patched with Magisk 17.1
patched_boot 9.6.11.0 (2018 November 2nd update) - patched with Magisk 17.1
patched_boot 10.0.2.0 (2018 December upgrade to Android 9.0 Pie) - patched with Magisk 18.0
patched_boot 10.0.3.0 (2019 January update) - patched with Magisk 18.0
In case you erroneously flash those patched files directly on the phone, flash back the original boot.img via fastboot and follow the guide:
original boot.img 9.6.4.0 (2018 July update) - taken from fastboot ROM
original boot.img 9.6.6.0 (2018 August update) - taken from OTA update
original boot.img 9.6.8.0 (2018 September update) - taken from OTA update
original boot.img 9.6.9.0 (2018 October update) - taken from OTA update
original boot.img 9.6.10.0 (2018 November 1st update) - taken from OTA update
original boot.img 9.6.11.0 (2018 November 2nd update) - taken from OTA update
original boot.img 10.0.2.0 (2018 December upgrade to Android 9.0 Pie) - taken from fastboot ROM
original boot.img 10.0.3.0 (2019 January update) - taken from fastboot ROM
7. You need the original boot.img to patch. You can find it inside the official fastboot ROM zip for daisy. Check that the downloaded ROM version is the same as the "Build number" currently installed on your phone (see point 1 of this guide). If the versions are different, update (or downgrade if possible) your phone to that version. You can also download original boot.img elsewhere (for example at the point 6 of this guide), but always pick the same "Build number" of your phone.
After you get the boot.img, copy it to the phone memory (via USB or microSD, or download directly from the phone browser, as you prefer).
8. Open the Magisk Manager app installed previously, it will ask if you want to install Magisk. Accept by tapping on "Install" > "Patch Boot Image File" and select the boot.img file that you get on the point 7 of this guide.
9. Wait until the process completes (about 1 minute), then tap on "Close". Now in the phone memory, inside the Download directory, you should have a patched_boot.img file. Copy that file to the PC, inside the same folder where the Android platform tools are located, for our convenience.
10. Reboot the phone in fastboot mode (as already explained in point 3 of this guide), open an administrative command prompt, move to the Android platform tools directory and then write the following command:
Code:
fastboot boot patched_boot.img
If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button. Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
11. Last step to stay safe when a new OTA update arrives: go to "Settings" > "System" > "Developer options" > and disable "Automatic system updates". From now on, you should check manually if a new OTA update is available.
Now the installation is finished, you can use Magisk Manager to install modules and manage root permissions.
HOW TO APPLY OTA UPDATES
UPDATE 9 February 2019 It seems that with the latest Magisk (v18.1) and Magisk Manager (v7.0.0) the following procedure is working fine again. I didn't test it personally, but some users gave positive feedback.
WARNING! January 2019 Since the arrival of Android 9 Pie, the OTA update with Magisk as described in the following section, doesn't seem to work anymore. It could work, but you could also get a bootloop with the risk of losing your data.
Before upgrading from Android 8 to 9, or doing an OTA update after Android 9 you should:
- backup your data;
- remove any lockscreen password or fingerprint;
- uninstall totally Magisk and reboot.
If after doing this you get a bootloop, you could try to manually flash the vanilla boot.img via fastboot on the current slot (the same version as the last installed OTA). If you managed to fix the bootloop you can then install Magisk anew, from step 5 of this guide.
If the phone wants your PIN or password to proceed after the OTA update or after fixing the bootloop, and your PINs or passwords doesn't work, then you could have to reset the phone (or erasing the data partition, that should be the same thing), losing all your data.
Last chance if everything fails, you can flash the latest fastboot ROM from the official Xiaomi site and the phone will be working again.
IMPORTANT: OTA updates will work only if all the partitions on the smartphone are untouched. Magisk Manager can restore the original boot.img following this section of the guide, but if you tampered directly with the system partition (e.g. manually editing build.prop) or other partitions, OTA will refuse to install.
You can try to fix OTA updates without the need to flash the whole original fastboot ROM, by flashing only the tampered partitions (usually only "system") with the corresponding img file found inside the fastboot ROM zip. Check the "Troubleshooting" section of this guide for details.
12. When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!
Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk. If the boot.img was already non-vanilla (for example you flashed the boot.img with TWRP before installing Magisk), Magisk Manager will backup that modified version of boot.img, and when restored the OTA will not work, as that's not a vanilla boot.img.
13. Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.
14. When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".
After the reboot you will have the updated Android version with Magisk already working.
Thanks to user @jashancheema for the Mi A1 guide and a bigger thanks to @topjohnwu for the OTA part and above all for developing Magisk.
TROUBLESHOOTING
WARNING: before attempting any of the following operations, you must disable any screen lock, PIN or password, because you risk to not get back your data (encryption issues). It is recommended to take a backup, too (as every time a custom modding is involved).
You can get errors when installing OTA updates if you didn't follow meticulously the guide.
Check this list to try to find where the problem lies:
- when a new version is found, the updater will check if all the partitions on the device are untouched. If there is a partition that has been modified, the OTA updater will not proceed with the installation;- typically, the two partitions commonly modified by user modding are the boot partition (that's where Magisk and TWRP are installed) and the system partition (when you change a config file, add or remove a system app, etc.);- a system partition modified only by using Magisk modules is effectively untouched, because Magisk register all changes to /system in a file in the /data partition and then trick Android to believe those changes are really applied to /system;- boot partition instead is really modified, but if you install Magisk following this guide, Magisk will save a copy of the untouched boot partition, and restoring it before applying OTA update will make the update work.
Now, if you didn't follow this guide to install Magisk and you installed it in other ways, Magisk could alert you that he cannot restore the original boot.img (the boot partition) when you try to apply the OTA update.
To fix this, you can flash directly the vanilla (original, unmodified, untouched) boot.img taken from the point 6 of this guide, using those commands:
Code:
fastboot getvar current-slot
fastboot flash boot_? boot.img
the first command will tell you what is the current slot in use (a or b), the second command will flash the original boot into the phone, but you have to change the "?" in the command with a or b (i.e. the current slot that the first command provided).
Remember that the boot.img file version must correspond to the Android build version currently running in your phone.
If the OTA update will still refuse to apply, probably you changed something directly in the /system partition (for example you changed something in the build.prop without using a Magisk module to do this).
In this case you have to flash the original system.img in the phone with those commands:
Code:
fastboot getvar current-slot
fastboot flash system_? system.img
and as before, the first command will tell you the right slot to use instead of the "?" in the second command.
Here you can find the system.img extracted from the OTA updates zip (along with every other .img file inside that):
9.6.6.0 (August 2018) OTA update dump as .img files
9.6.8.0 (September 2018) OTA update dump as .img files
9.6.9.0 (October 2018) OTA update dump as .img files
9.6.10.0 (November 2018) full fastboot ROM
9.6.11.0 (November 2018) OTA update dump as .img files
If you want to obtain the system.img by yourself, you can find it inside the fastboot images but usually they are not updated monthly like OTA updates. But you can extract the system.img directly from the OTA update zips found in this thread (as I did above with my dumps), using the Python scripts found here.
To make the Python scripts work in Debian/Ubuntu and derivatives, you have to download both "extract_android_ota_payload.py" and "update_metadata_pb2.py", give them execution property and then install the package "python-protobuf". After this you can give this command to unpack the payload.bin file (that you must extract from the OTA update zip):
Code:
./extract_android_ota_payload.py /path/to/payload.bin
This will extract in the current directory all the .img files inside payload.bin, including the system.img
I don't know how to proceed in Windows, probably you only need to install the latest Python2 release and the script will work.
As the last resort, you can flash directly with MiFlash the latest fastboot image available (even if older than your current version). Use the "flash_all.bat" script but before take a backup of your data, because the phone will be fully reset.
If you don't want to take the risk of not doing a backup, use the script "flash_all_except_storage.bat" when flashing, so you will keep all your data, but be warned that sometimes you will not be able to access the data anymore, because of encryption problems.
Right after the flash, you can start following the guide from point 5 or 6.
It should not be a problem downgrading the build version via fastboot, as long as the Android main version remain the same (Oreo 8.1 at the moment).
Thx, nice work :good:
Thanks to the OP. Great post! Totally noob friendly guide. Nice work.
It should also work on mi a2, thanks!
Lione2 said:
It should also work on mi a2, thanks!
Click to expand...
Click to collapse
Sure, but you can't use the posted patched_boot.img, because they're designed for Mi A2 Lite (daisy) and not for Mi A2 (jasmine).
EDIT: I posted the patched and original boot files for Mi A2 jasmine in the second post. I don't know if I can make a thread in the Mi A2 forum section with an adapted copy of my guide, there are already two guides there (even if not polished like this) and I don't want to create more confusion with a third guide about the same argument...
i've installed magisk from previous guide - what steps should I take to apply OTA update? - 12 to 14?
Now magisk informs me that there is 17.1 version - how to update it?
krzygaj said:
i've installed magisk from previous guide - what steps should I take to apply OTA update? - 12 to 14?
Now magisk informs me that there is 17.1 version - how to update it?
Click to expand...
Click to collapse
If you flashed directly the patched_boot.img via fastboot in both slots A and B as the other guide said previously, you must flash the original boot.img to both slots, then start the guide from point 10.
BubuXP said:
If you flashed directly the patched_boot.img via fastboot in both slots A and B as the other guide said previously, you must flash the original boot.img to both slots, then start the guide from point 10.
Click to expand...
Click to collapse
I did as you wrote but still can't install August update - is there any log?
- extracted boot.img from rom: http://en.miui.com/download-354.html
- did fastboot flash boot_a boot.img and fastboot flash boot_b boot.img and rebooted
- next rebooted and did fastboot boot patched_boot.img with patched_boot 9.6.4.0 (July update) - patched with Magisk 17.1
later did steps in guide - but when i do system update it stops on first stage
Any ideas?
krzygaj said:
I did as you wrote but still can't install August update - is there any log?
- extracted boot.img from rom: http://en.miui.com/download-354.html
- did fastboot flash boot_a boot.img and fastboot flash boot_b boot.img and rebooted
- next rebooted and did fastboot boot patched_boot.img with patched_boot 9.6.4.0 (July update) - patched with Magisk 17.1
later did steps in guide - but when i do system update it stops on first stage
Any ideas?
Click to expand...
Click to collapse
You tampered the system partition? Try flashing also the system.img in that case.
Another case could be that you made an OTA update from the June build to July: in this case the partitions on the other slot (probably only the boot partition) where lost when overwrited with fastboot (and cannot be restored, as we don't have any June build ROM or OTA).
If everything fails, do a full fastboot flash with MiFlash tool, but using the flash_all_except_storage.bat script, that should keep your data intact, restore all partitions (A and B) to stock versions and you can then apply OTA (before or after installing Magisk, but I suggest after installing Magisk so you can test if the guide works fine).
BubuXP said:
If everything fails, do a full fastboot flash with MiFlash tool, but using the flash_all_except_storage.bat script, that should keep your data intact, restore all partitions (A and B) to stock versions and you can then apply OTA (before or after installing Magisk).
Click to expand...
Click to collapse
Thanks above worked :good:
Hope the next update will go smoothly
September?
When booting comes a warning message because of the unlocked boot loader. How can I disable this message?
PC295 said:
When booting comes a warning message because of the unlocked boot loader. How can I disable this message?
Click to expand...
Click to collapse
you can't turn that off with open bootloader
Guys, after i have unlocked bootloader i cannot charge my phone when is off because he go on when I insert the plug, it's normal?
proton242 said:
Guys, after i have unlocked bootloader i cannot charge my phone when is off because he go on when I insert the plug, it's normal?
Click to expand...
Click to collapse
No
ConradB said:
No
Click to expand...
Click to collapse
ConradB you have some suggestion? Thank you
proton242 said:
ConradB you have some suggestion? Thank you
Click to expand...
Click to collapse
Same problem on mine, I don't know if it's a ROM bug or it's caused by unlocked bootloader or Magisk.
The only solution at the moment is charging while the phone is switched on.
BubuXP said:
Same problem on mine, I don't know if it's a ROM bug or it's caused by unlocked bootloader or Magisk.
The only solution at the moment is charging while the phone is switched on.
Click to expand...
Click to collapse
Ciao BubuXP, provando a rimuovere Magisk (lasciando il bootloader sbloccato) tutto torna alla normalità, cosa dici, crea casino quando patcha il boot.img?
Rooting Huawei Mediapad M5 Lite ( All Editions ).
Requirements:
1. Unlocked Huawei Mediapad M5 lite ( All Editions ).
2. Minimal ADB Tools.
3. Magisk Manager latest from magisk manager website.
4. Huawei Firmware Finder ( Download from Playstore ).
4. Original Firmware Update.zip of current device you are running (Check in your device from Huawei Firmware Finder app).
5. Zarchiver ( Download from Playstore ).
6. Ramdisk.img file ( Extracted from Update.zip ).
Procedure:
1. Download Zarchiver app in playstore and download the current stock rom update.zip ( check your version in update settings) and open the update.zip file in Zarchiver app in your tab and extract the RAMDISK.img to any folder in your tablet.
2. Open Magisk Manager app in you tab and click on 1st "install" option then "select and patch a file" then browse your RAMDISK.img you copied to your internal memory. It will patch the RAMDISK.img and store it in downloads folder in your tab.
3. Download the minimal ADB tools from any website and install them your pc.
4. Copy the patched-ramdisk.img file to adb folder in PC and open the command prompt from the adb folder .
2. Enable USB debugging setting in the tablet and connect the tablet to the pc. After connecting open command prompt in the adb folder you have installed and type
Code:
adb devices
. You must see a device in the output. ( If not properly enable your usb debugging settings).
3. After that type
Code:
adb reboot bootloader
. Your device will boot into the fastboot mode and you will see BOOTLOADER UNLOCKED on the tab screen.
4. Now type
Code:
fastboot flash ramdisk patched-ramdisk.img
( patched-ramdisk file name may differ).
5. Your device is Successfully Rooted.
You need unlocked bootloader for this
Yes
lapora said:
You need unlocked bootloader for this
Click to expand...
Click to collapse
I have provided complete guide to unlock bootloader
i sold it and bought a samsung galaxy tab s5e no more huawei **** i spend hours to make the twrp and magisk to work with out errors but at least i didn't pay a third party unlock service because huawei decided to lock everything.
lapora said:
i sold it and bought a samsung galaxy tab s5e no more huawei **** i spend hours to make the twrp and magisk to work with out errors but at least i didn't pay a third party unlock service because huawei decided to lock everything.
Click to expand...
Click to collapse
You tried to make twrp? Magisk works man.
hi , i can't find IMG file into update.zip ? why
ouawai said:
hi , i can't find IMG file into update.zip ? why
Click to expand...
Click to collapse
It´s inside the file "update.app". You need a special tool to extract.
Please take a look to this thread:
https://forum.xda-developers.com/mediapad-m5/how-to/root-root-guide-huawei-mediapad-m5-t3786157
From the M5 guide:
"Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device"
I might be dumb AF but these guides are incomplete :/
Can anybody please share the Profiles.xml containing the images for the M5 Lite?
So far I used the Firmware Finder for downloading the latest rom which contains the UPDATE.APP and also downloaded the HuaweiUpdateExtractor but without the right profile it won't open file.
EDIT: currently following the main guide about extracting the ramdisk image: https://www.theandroidsoul.com/extract-huawei-firmware-update-app/
EDIT-2: guide (the one of my link above, not the guide of this thread) followed and finally rooted! Man, what a journey.
https://topjohnwu.github.io/Magisk/install.html
Rooting Huawei Mediapad M5 Lite ( All Editions )
Requirements on drumiec edition:
1. Unlocked Huawei Mediapad M5 lite.
2. Minimal ADB Tools [also added to post]
3. WinRar or other extraction tool
4. Magisk Manager apk file from original XDA topic.
5. Huawei Update Extractor [UPDATED: v0.9.9.5] [also added to post]
6. Original Firmware update.zip of current device you are running from https://pro-teammt.ru/en/online-firmware-database/
I used website that actually belong to Huawei Firmware Finder aplication TeamMT, so will give you same result with searching database (look at screen1.jpg - attached to post)
When you will find your firmware version click on filelist and pick the first link, usually is the largest file from all 3 links (like 1.8GB for example).
7. Download update.zip and extract UPDATE.APP from inside using WinRAR or so.
8. Open Huawei Update Extractor and open with it UPDATE.APP file by clicking [...] button.
Important: If program will not let you open the file because of some CRC errors, go on settings tab and uncheck Verify Header Checksum.
For me was not possible to open UPDATE.APP without previous step.
9. Find RAMDISK.img file on the list and extract it.
10. Copy RAMDISK.img file to tablet at any place.
11. Install Magisk Manager apk on tablet.
12. Follow the original guide.
Notice: Magisk will show you output location of your patched ramdisk file right after it finish processing it.
Latest update.zip for Huawei Mediapad M5 Lite 10.1 linked here:
FW version: BAH2-W19 8.0.0.230 C431 update.zip download
drumiec said:
10. Copy RAMDISK.img file to tablet at any place.
Click to expand...
Click to collapse
use
Code:
adb pull
and
Code:
adb push
to achieve the transfers as people noticed that using MTP can corrupt the file:
Code:
1. adb push /path/to/RAMDISK.IMG /sdcard
2. Patch the file using Magisk.
3. adb pull /sdcard/Download/magisk_patched.img ./
And then flash it through fastboot.
Hey Bossman, im stuck at the very end. I copied the patched magisk img to my pc folder where the adb is and when i type the fastboot flash ramdisk ****** it says
"error: cannot load 'patched-ramdisk.img': No such file or directory"
I dont know what im doing wrong?
the adb debugging on and im at the bootloader screen and my stuff is unlocked.
please help me, im not sure where im going wrong, the directions are so simple.
edit* nvm i fixed it
i had to do that adb pull and it worked from there. thank you again so much. i dont know what im going to do with this huawei device but online it said it was a good tablet to have so maybe more will come with this. if not, i can always use it as a security monitor? lol thanks again, have a great night!
sadiqkarur said:
Rooting Huawei Mediapad M5 Lite ( All Editions ).
Requirements:
1. Unlocked Huawei Mediapad M5 lite ( All Editions ).
2. Minimal ADB Tools.
3. Magisk Manager latest from magisk manager website.
4. Huawei Firmware Finder ( Download from Playstore ).
4. Original Firmware Update.zip of current device you are running (Check in your device from Huawei Firmware Finder app).
5. Zarchiver ( Download from Playstore ).
6. Ramdisk.img file ( Extracted from Update.zip ).
Procedure:
1. Download Zarchiver app in playstore and download the current stock rom update.zip ( check your version in update settings) and open the update.zip file in Zarchiver app in your tab and extract the RAMDISK.img to any folder in your tablet.
2. Open Magisk Manager app in you tab and click on 1st "install" option then "select and patch a file" then browse your RAMDISK.img you copied to your internal memory. It will patch the RAMDISK.img and store it in downloads folder in your tab.
3. Download the minimal ADB tools from any website and install them your pc.
4. Copy the patched-ramdisk.img file to adb folder in PC and open the command prompt from the adb folder .
2. Enable USB debugging setting in the tablet and connect the tablet to the pc. After connecting open command prompt in the adb folder you have installed and type
Code:
adb devices
. You must see a device in the output. ( If not properly enable your usb debugging settings).
3. After that type
Code:
adb reboot bootloader
. Your device will boot into the fastboot mode and you will see BOOTLOADER UNLOCKED on the tab screen.
4. Now type
Code:
fastboot flash ramdisk patched-ramdisk.img
( patched-ramdisk file name may differ).
5. Your device is Successfully Rooted.
Click to expand...
Click to collapse
Same issue here.
The solution is written on the Magisk Homepage:
Don't extract the file with Zarchive.
Download the file update. Zip from the Tablet to the PC (with the Huawei Tool) and unzip the file one time with 7zip.
Use the tool Huawei Firmware extracter. Disable in the settings the checksumme check and extract the Ramdisk.img. Copy the file back to the Tablet and let it patch from Magisk. Copy the patched file back to the PC, boot the Tablet into Fastboot (via adb reboot bootloader) and flash the Ram disk.img.
Remember to active at every reboot the USB Debugging in the Dev settings. It's disabled automatically.
Thanks for the guide. Should I unroot device if I get a new official update?
With the updates I lost my root access which I was using for multi user on my M5 lite Wifi
So I had to do the whole process again.
Here is the patched file for the version : BAH2-W19 8.0.0.278 (OCEC431)
so if you have the same version you can skip some steps and flash it.
firmware : BAH2-W19OCEC431B278
https://www.mediafire.com/file/mizbqmyztiuyj13/magisk_patched.img/file
You 'll have to re-edit the file to enable the multiuser (if you already did it previously the users will still have their config)
check there https://forum.xda-developers.com/p8...-root-add-multi-user-support-disable-t3602872
drumiec said:
Rooting Huawei Mediapad M5 Lite ( All Editions )
Requirements on drumiec edition:
1. Unlocked Huawei Mediapad M5 lite.
2. Minimal ADB Tools [also added to post]
3. WinRar or other extraction tool
4. Magisk Manager apk file from original XDA topic.
5. Huawei Update Extractor [UPDATED: v0.9.9.5] [also added to post]
6. Original Firmware update.zip of current device you are running from https://pro-teammt.ru/en/online-firmware-database/
I used website that actually belong to Huawei Firmware Finder aplication TeamMT, so will give you same result with searching database (look at screen1.jpg - attached to post)
When you will find your firmware version click on filelist and pick the first link, usually is the largest file from all 3 links (like 1.8GB for example).
7. Download update.zip and extract UPDATE.APP from inside using WinRAR or so.
8. Open Huawei Update Extractor and open with it UPDATE.APP file by clicking [...] button.
Important: If program will not let you open the file because of some CRC errors, go on settings tab and uncheck Verify Header Checksum.
For me was not possible to open UPDATE.APP without previous step.
9. Find RAMDISK.img file on the list and extract it.
10. Copy RAMDISK.img file to tablet at any place.
11. Install Magisk Manager apk on tablet.
12. Follow the original guide.
Notice: Magisk will show you output location of your patched ramdisk file right after it finish processing it.
Latest update.zip for Huawei Mediapad M5 Lite 10.1 linked here:
FW version: BAH2-W19 8.0.0.230 C431 update.zip download
Click to expand...
Click to collapse
tbozo said:
With the updates I lost my root access which I was using for multi user on my M5 lite Wifi
So I had to do the whole process again.
Here is the patched file for the version : BAH2-W19 8.0.0.278 (OCEC431)
so if you have the same version you can skip some steps and flash it.
firmware : BAH2-W19OCEC431B278
https://www.mediafire.com/file/mizbqmyztiuyj13/magisk_patched.img/file
You 'll have to re-edit the file to enable the multiuser (if you already did it previously the users will still have their config)
check there https://forum.xda-developers.com/p8...-root-add-multi-user-support-disable-t3602872
Click to expand...
Click to collapse
So with this file, the process from the OP is shortened to:
1. Type
Code:
adb reboot bootloader
. Your device will boot into the fastboot mode and you will see BOOTLOADER UNLOCKED on the tab screen.
2. Now type
Code:
fastboot flash ramdisk magisk_patched.img
(above file for BAH2-W19 8.0.0.278 (OCEC431)).
3. Your device is Successfully Rooted.
Is this right?
edit: to answer my own question: yes
Also, do we need to do this after every OTA update? (not that I expect so many in the future...)
Keine ramdisk Partition mehr
Hi,
since the last update BAH2-L09OCEC432B278 a ramsisk partition is no longer available.
I followed the modified guide with 7-zip and downloading the update.app on my PC and then pushing it onto the tablet with
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push c:/RECOVERY_RAMDIS.img /storage/emulated/0/Download
I created the magisk_patched.img and used the pull adb command to get it back onto my PC.
I followed the steps in the guide with fastboot, but the very last command fails.
The tablet says both are unlocked, on the Magisk Website there is a short section on "Magisk in Recovery", but pushing the Power on and Volume up does not give my a Magisk option.
Update: I followed the Patching guide, but this fails with the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery magisk_patched.img
target reported max download size of 471859200 bytes
sending 'recovery' (26386 KB)...
OKAY [ 0.826s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.842s
Hi,
I have the Huawei MediaPad M5 lite 10 but the Build Number for me is 'BAH2-W19 8.0.0.278 (OCEC432)'
and I can't seem to find the update file for it to follow the steps above?
Any help would be appreciated on what steps I need to do.
Thanks, :good:
Your Build number translates to the same firmware as mine: BAH2-L09OCEC432B278
This is a great explanation: https://www.theandroidsoul.com/extract-huawei-firmware-update-app/
Download the file from MT Team and extract is with 7Zip: https://pro-teammt.ru/en/
Hope this helps.
PS: Could you let me know if you are able to flash your phone since it is the same build?
THX!
Balamku said:
Your Build number translates to the same firmware as mine: BAH2-L09OCEC432B278
This is a great explanation:
Download the file from MT Team and extract is with 7Zip:
Hope this helps.
PS: Could you let me know if you are able to flash your phone since it is the same build?
THX!
Click to expand...
Click to collapse
Thanks for the link. reading the explanation then, mines would be BAH2-W19OCEC432B278. Thanks for that
---------- Post added at 03:51 PM ---------- Previous post was at 03:10 PM ----------
Balamku said:
Your Build number translates to the same firmware as mine: BAH2-L09OCEC432B278
This is a great explanation:
Download the file from MT Team and extract is with 7Zip
Hope this helps.
PS: Could you let me know if you are able to flash your phone since it is the same build?
THX!
Click to expand...
Click to collapse
Huawei Update Extractor: it mentions this in there but I have a MacBook and there doesn't seem to be a version for this.
Am I missing something?
Hmm, I have Linux and had to dual boot into Windows, because of several tools - this one included - wanting Windows. There is an emulator / VM available for Windows on Mac, but might be a bit over the top...
( this tutorial is only for iodé os 3.4-20221215-pioneer on a Sony Xperia h3113 pioneer )
In this exploitation system, the boot.img is stocked in the payload of your zip install.
0. Before all,
I am not responsible if you make a mistake and brick your phone ( bad usb connexion, wrong or corrupted img ect.. ), I won't help you if it's the case after this tutorial.
You'll need to know how to use* " Minimal ADB and Fastboot" , and get the correct USB windows drivers for your phone ( *like unlock the bootloader with the sony code given with your IMEI activate the developper mode, usb debug & unlock the bootloader )
After typing adb reboot bootloader on the CMD of Minimal ADB Fastboot wait until the blue light appear on your Xperia XA2 pioneer.
Download Latest Minimal ADB and Fastboot Tool v1.4.3 (Dec 2018)
Minimal ADB and Fastboot Tool v1.4.3 is now available for download and install.If you are looking for the latest version of the Minimal ADB and Fastboot tool
rootmygalaxy.net
1. Root won't install with magisk in Lineage Os 19.1 or idoé os 3.4.20221215 if you don't change the original recovery file to TWRP recovery.
Download : https://eu.dl.twrp.me/pioneer/twrp-3.7.0_9-0-pioneer.img.html rename the *.img to twrp.img copy the *.zip in your phone
boot on TWRP with the administrator CMD ( you have copied in ) Minimal ADB Fastboot by typing : fastboot boot twrp.img
install TWRP with "Minimal ADB and Fastboot" by following the Advanced > Flash Current TWRP option, with the *.zip of TWRP on your phone.
Sony Xperia XA2
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
( the “Fix Recovery Bootloop” option is not needed anymore , pay attention to use "advanced" and not "install" in TWRP )
2. Download the *.zip of your system installation ( Lineage Os 19.1, iodé Os 3.4-2 - Android 12 ) and extract it on windows.
3. Use "payload dumper go" to get the boot.img, there's a tutorial on XDA here :
https://forum.xda-developers.com/t/...-payload-bin-using-payload-dumper-go.4468781/ )
NB : If you don't want to extract the boot.img with payload dumper go
just take this one only for Sony XA2 H3113 Pioneer ( 1 sim only )
Download boot.img on mega nz
4. Copy the boot.img in a folder of your XA2 H3113 pioneer phone.
5. Install Magisk, then patch the boot.img
( I've followed this video tutorial )
6. Copy the " magisk *** patched *.img" files of your H3113 download folder in the windows folder install of minimal ADB fastboot, and rename it to magisk.img
7.
In the administrator CMD of minimal ADB Fastboot on windows type :
. "adb reboot bootloader" enter
. "fastboot flash boot magisk.img" enter
It's alldone !
for h3123
hi not works more for me i am trying flashing twrp goes to bootloop
CyanRose said:
hi not works more for me i am trying flashing twrp goes to bootloop
Click to expand...
Click to collapse
This tutorial is for h3113, i don't know for h3213, I don't have one.
Also take care of the version of iodé os, I won't do update anymore ( I'll stay on 3.4-20221215). But Android 11 was faster on xperia H3113.
Iodé os didn't inform me before the update that it would change the core of the system and change the recovery ( unroot the phone ).
This update bring me only ****s like a slower system, unroot the phone and de-configurate all aps in the iodé ap ( an integrated firewall ).