Database Develop

[Guide]Extracting Stock firmware files using Huawei Update Extractor/splitupdate

There seems to be a little confusion on how to do this and I've written down how to in many posts now so I figure I'd just write it down in a little guide.
What you need:
Firmware update.zip from http://pro-teammt.ru/firmware-database/
Windows only: Huawei Update Extractor
Linux/Mac(?)/(Windows too): splitupdate perl script (requires perl)
Direct link: https://mega.nz/#!4PBknJrK!iZQDI4ti6ERmQJC6afgUGTSvHHKcm9KFz9okmwwez3I
Source: https://github.com/marcominetti/split_updata.pl/tree/f5f415262be3487de28321b49dcb69d947897bf1
(Or my 'special' version https://mega.nz/#!NS4VnL7Q!5GMn-soCf_WMW6fZANd-TDzxjQkZW2LynEQtJ_TlUdU which extracts
to the same folder as 'splitupdate' instead of 'output/', and includes a mount script (Linux only, maybe Mac?) for extraction of files of the different images)
Archive extractor of your choice (7zip, winrar, winzip and so on.)
Firmware build
First you need to determine what your current firmware is, this can be done by going to 'Settings -> System -> About Phone' on your phone. Check 'Build Number'.
Mine says:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BLA-L29 8.0.0.132(C636) (Replace 8.0.0. with C636 and add a B infront of 132 )
This can be translated into BLA-L29C636B132.
Now we have our current firmware!
Info on Nougat -> Oreo
As of Oreo the partitions changed a little.
'Boot' partition was split into 'ramdisk' and 'kernel'.
'Recovery' partition was split into 'recovery_ramdisk', 'recovery_vendor' and 'recovery_vbmeta', and shares the 'kernel' partition with 'ramdisk'.
The one's you probably want to flash are 'ramdisk' and 'recovery_ramdisk'. (Ramdisk is where Magisk/SuperSU goes, recovery_ramdisk is where TWRP goes)
Firmware update.zip
In this example I will be using my firmware, BLA-L29C636B132.
First start by going to http://pro-teammt.ru/firmware-database/ and enter your full firmware in the 'Enter model', click on Find Model.
This is what it will look like after you have searched. Locate the row that says FullOTA-MF and click on the 'update' link in that row.
When it's downloaded, open update.zip in your choice of archive manager and extract UPDATE.app to your desktop or somewhere easy to find.
Huawei Update Extractor:
Download Huawei Update Extractor from the link above, it's attached to first post in that thread I linked to (v0.9.9.5).
Extract the zip to your desktop (Or Downloads folder).
Enter the newly created folder that should be named 'HuaweiUpdateExtractor_0.9.9.5', and run HuaweiUpdateExtractor.exe.
Start by going to the 'Settings' tab and uncheck 'Verify header checksum'.
(Something is wrong with the header of erecovery_ramdisk, also it's mispelled to erecovery_ramdis, or maybe character limit? The partition on phone is named correctly. This does not need to be unchecked on Nougat firmware)
Then go back to the 'Extract' tab and click on the button that says '...' and open your UPDATE.APP
Rightclick on the file you want to extract and click on 'Extract Selected', this will bring up a dialog where you choose where to extract to.
After this you can flash the file using fastboot. Take 'ramdisk' for example.
Make sure you have adb & fastboot installed (https://forum.xda-developers.com/showthread.php?t=2317790)
Open up a command prompt and connect phone, reboot to fastboot mode using: usb plugged in, power + vol down, release power when phone vibrates.
Or you can use the command 'adb reboot bootloader'.
Make sure phone is recognized in fastboot mode with the command: 'fastboot devices', it should show up as a fastboot device.
Next we can flash RAMDISK.img using: 'fastboot flash ramdisk RAMDISK.img'.
On Nougat you would extract 'BOOT' from UPDATE.APP and flash using:
'fastboot flash boot BOOT.img'
Linux/Mac(?)(and Windows with perl installed, I use Strawberry Perl)
First download the splitupdate zip from above.
Extract it and enter the extracted 'split' folder, open a terminal and:
'chmod +x splitupdate'
'chmod +x crc'
Now put your UPDATE.APP in the 'split' folder and open a terminal and use the following command:
'./splitupdate UPDATE.APP file_to_extract'. If you write 'file_to_extract' or anything that is or is not in the UPDATE.APP it will list all images in it.
Typing './splitupdate UPDATE.APP' will extract all files in UPDATE.APP
It will output files to the newly created 'output' folder. The filtering is not perfect. If you use './splitupdate UPDATE.APP RAMDISK', it will extract all images with RAMDISK in its name, so you will get RAMDISK.img and RECOVERY_RAMDISK.img. This is fine for me as the original script extracted everything, which takes long for the larger images.
And if you use the 'special' version:
'chmod +x simg2img'
'chmod +x mount.sh'
I edited the splitupdate script for the 'special' version just to make it easier for me as I like to check SYSTEM, VENDOR, PROCDUCT and those images for changes.
So it made it easier if it extracted directly to the root of 'split' folder instead of 'output', then I could run the mount.sh script directly.
To use mount.sh, first edit the script and replace YOUR_SUDO_PASSWORD_HERE with your password or remove 'echo YOUR_SUDO_PASSWORD_HERE | ' and input password manually when it asks.
Then simply extract SYSTEM.img (or Product, vendor, odm whichever you like) and './mount.sh SYSTEM' (yes, no extension).
This will convert SYSTEM.img to SYSTEM.raw and mount it to 'split_folder/SYSTEM/' as a loop device, it will also chmod 777 everything in SYSTEM/.
Linux ADB and Fastboot
Use google for this one. ADB usually works fine right away, Fastboot might get 'no permissions' and need to be run as sudo if it's missing udev permissions/entries.
You can make fastboot work without sudo but it's easier to google it as it might get lengthy and there are a lot of different distros of linux (I use Ubuntu)

Hi ante0, i have downloaded the bla a09 8.0.0.109 c567 which is the recent update for my US mate 10 pro version, i was using hisuite to update my phone which is failing but i was able to grab the update which it down loaded and it has the following files in it, bla-a09_hw_usa( which contains update_full_BLA-A09_hw_usa, public( which contains update_data_full_public), update.zip which contains update.app and other xml files, i have already bl unlocked and rooted with supersu but i wanted to install magisk and i installed twrp and tried sideloading magisk but it fails stating boot image already modified and advised flask stock boot, so which files do i need to flash and what are the fastboot commands to do so and i was also thinking about complete bl lock just to make it look like new phone and how do i do that, please direct me, thank you.

I think to update you'll need to:
A) Unroot your supersu.
B) Restore stock boot and restore your stock recovery with guide in OP and with the firmware files actually installed on your phone.
Then you could root oreo with magisk.

oslo83 said:
I think to update you'll need to:
A) Unroot your supersu.
B) Restore stock boot and restore your stock recovery with guide in OP and with the firmware files actually installed on your phone.
Then you could root oreo with magisk.
Click to expand...
Click to collapse
there lies my problem, i am trying to flash an updated stock firmware than the one that came with my phone, i have unrooted supersu and deleted supersu app and dont have root anymore confirmed by rootcheck apps, since my boot is already patched once magisk wont flash and advising me to flash stock boot image but i dont know which to flash as with oreo there seems to be different partitions and i dont know commands other than basic fastbbot commands to flash stuff.

ok so i was able to flash ramdisk, recovery and system and boot back to OS ( i have earlier erased system by mistake) and i have flashed system.img from updated firmware but version still shows old one, and i am trying to use funkyhuawei erecovery method to flash the updated firmware and when i boot to erecovery to update but the update button is missing and i just have rebbot, wipe date/fr and wipe cache, so what do i need to flash and commands for it in order to make erecovery work and i have update button enabled, thank you.

lingarajug said:
ok so i was able to flash ramdisk, recovery and system and boot back to OS ( i have earlier erased system by mistake) and i have flashed system.img from updated firmware but version still shows old one, and i am trying to use funkyhuawei erecovery method to flash the updated firmware and when i boot to erecovery to update but the update button is missing and i just have rebbot, wipe date/fr and wipe cache, so what do i need to flash and commands for it in order to make erecovery work and i have update button enabled, thank you.
Click to expand...
Click to collapse
If you can, use the HWOTA method instead. It's free and found: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
If you can't use HWOTA and have to use Funky:
You seem to be in normal Recovery. You should see a button that says 'Download latest firmware', the one you're describing is showing buttons that are in normal Recovery.
Are you booting using Usb plugged in + vol up + power?

For some reason my phone would only boot to revovery and not erecocery, anyway i used hisuite method and was able to flash new firmware. Thank you.

I've just unbricked my Mate 10 pro via this method. Thank you Sir.

Not sure if this is the right place but where can I find the original Huawei OS it was shipped with? I installed Lineage and want to go back to Factory.
I just want to .img file. I have only unlocked the bootloader not rooted the phone.
Lack of camera and other features means I need to get back.
Any ideas?

elviss0812345 said:
I've just unbricked my Mate 10 pro via this method. Thank you Sir.
Click to expand...
Click to collapse
You bricked your device because you don't know what you are doing,not because of this guide.Oh,and i thought KangRom was responsible for bricking you device....anyone else to blame ?

My phone was bricked because of Lineage OS, and i unbricked with this guide. Read my post first.
Pretoriano80 said:
You bricked your device because you don't know what you are doing,not because of this guide.Oh,and i thought KangRom was responsible for bricking you device....anyone else to blame ?
Click to expand...
Click to collapse

elviss0812345 said:
My phone was bricked because of Lineage OS, and i unbricked with this guide. Read my post first.
Click to expand...
Click to collapse
lol,i've read "bricked"... .I apologize for that!:good:

There is no way at least for the US version to find firmwares shipped with phone until now, i figured it out by connecting phone to hisuite on PC and it showed update available and i clicked update and waited until download part of update process completed and then i went to documents folder and hisuite and the app stores the download there and it will have 3 zip files, u can copy them to a different place because once the update completes those files are deleted. Might be the same for other models if supported by hisuite.

Here https://playstoreappinstall.com/play-store-for-huawei/ more info

@lingaraguj not already listed there :
http://pro-teammt.ru/firmware-database/?firmware_model=ALP
?

oslo83 said:
@lingaraguj not already listed there :
http://pro-teammt.ru/firmware-database/?firmware_model=ALP
?
Click to expand...
Click to collapse
US version firmware not listed, lots of international versions though.

can i flash everything in UPDATE.APP to go back to fully stock.
if i can what is the fastboot command for every one of them files like "fastboot flash ramdisk RAMDISK.img'?
ive mate 10 pro.

lex71 said:
Not sure if this is the right place but where can I find the original Huawei OS it was shipped with? I installed Lineage and want to go back to Factory.
I just want to .img file. I have only unlocked the bootloader not rooted the phone.
Lack of camera and other features means I need to get back.
Any ideas?
Click to expand...
Click to collapse
It should say your current firmware (besides Lineage) in Settings -> (System?) -> About.
dark3bod said:
can i flash everything in UPDATE.APP to go back to fully stock.
if i can what is the fastboot command for every one of them files like "fastboot flash ramdisk RAMDISK.img'?
ive mate 10 pro.
Click to expand...
Click to collapse
It's better to use:
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I'm not sure if symlinks will be set up correctly if you flash images directly. And some partitions can't be flashed from fastboot (like the erecovery ones)

ante0 said:
It should say your current firmware (besides Lineage) in Settings -> (System?) -> About.
It's better to use:
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I'm not sure if symlinks will be set up correctly if you flash images directly. And some partitions can't be flashed from fastboot (like the erecovery ones)
Click to expand...
Click to collapse
@ante0
This man is a legend.........
I would like to express my gratitude in you answering my pms and assisting to get the device up and running.
If ever am in Sweden:silly: ill definitely buy you beeeeeeeeeeeeeeeeeeeeeeers
Thanks for the patience and the help you bring to us noobs bricking these bloody Mate 9's

Im now on lineage os. I didnt flash twrp and magisk. Can i only flash stock system.img to get fully stock. Or i have to flash ramdisk and boot first before system.img

[GUIDE][ZS620KL][Update 29.08.2019] 5Z How to unlock root up/downgrade and unbrick

Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
[Update 29.08.2019] Added new download locations for raw images
[Update 07.01.2019] Added more current raw image for ZS620KL WW 80.30.96.111
[Update 25.10.2018] Added raw image for ZS621KL.
[Update 09.08.2018] Updated for 80.11.37.95 and future versions.
[Update 20.07.2018] I was able to root FW 80.11.37.86 with Magisk Manager 5.8.3 so you are no longer locked to FW 80.11.37.69 and do not have to downgrade.
This guide is split into two sections: rooting and downgrade/unbrick.
Each section is split into a quick how to for experienced users and a more detailed guide.
General info:
The most current firmware as of 20.07.18 is 80.11.37.86. Newer versions will work too!
This guide is written for firmware 80.11.37.86. If you do not want to upgrade/downgrade to 80.11.37.86 you will need to use the firmware (zip file from ASUS) you are on in all the steps.
If you upgrade your firmware to a newer version AFTER rooting it you will lose root! You will need to patch the boot.img of the new firmware again > follow the rooting guide.
I have only tested this on my ZS620KL Z01RD WW version. It should work on other variants JP/RU.
Magisk hide is working and Safetynet check passes.
Bugs/problems:
Unlocking the bootloader will void your warranty! Currently there is no method known to relock it!
You will get a warning message about your unlocked bootloader at every boot.
You will no longer receive OTA updates but you can download the new firmwares directly from Asus.
You will get a warning message about an internal problem every boot. Which you can disable if you do not need write access to the vendor partition.
> see rooting guide 10.
[Downloads]
for rooting
The latest and official platform tools (adb/fastboot) directly from google.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Payload_dumper to extract the boot.img from the firmware:
https://androidfilehost.com/?fid=818070582850510260
Magisk Manager:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The bootloader unlock app and the 80.11.37.86 firmware for your device (WW/RU/JP) from ASUS:
https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_Download/
for downgrade/unbrick
raw firmware (ZS620KL WW):
WW 80.10.8.54
https://www.androidfilehost.com/?fid=1899786940962570681
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
WW 80.30.96.111
https://www.androidfilehost.com/?fid=1899786940962570682
https://drive.google.com/file/d/16OgxiPFSDJwhitnqJaITuO-XPOrg_7q9/view
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
Confirmed working by amscova.
raw firmware (ZS621KL):
https://addrom.com/raw-rom-unbrick-for-asus-zenfone-5z-zs621kl/
https://www.androidfilehost.com/?fid=1899786940962570680
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
Confirmed working by B Nath.
[Rooting how to]
Upgrade to firmware 80.11.37.86 and enable usb debugging.
Unlock your bootloader with the app.
Extract boot.img from firmware using payload_dumper.
Patch boot.img with magisk manager.
fastboot flash boot patched_boot.img.
Enjoy root.
[Rooting guide]
You can root any firmware from 80.11.37.86 up with this guide. To upgrade to a newer firmware version copy the zip file (e.g. UL-Z01R-WW-80.11.37.86-user.zip) you downloaded from Asus
to the root of your phones internal memory and reboot or unplug your usb cable.
You will get an update found notification. Start the update. To downgrade check the downgrade guide below.
Enable usb debugging in System > Developer options. If you can not see System > Developer options go to System > About phone > Software information > Build number and tap it multiple times.
This will make the Developer options visible.
WARNING! Upgrading to some firmwares disables usb debugging and you need to enable it again.
Make a backup of all the data you do not want to lose.
Download the platform tools and extract them into a folder (i will use c:\5z\ in this guide) this will create a subfolder platform-tools.
You need a current fastboot version for this to work (due to a/b slots/partitions), so please use the current platformtools!
Download the bootloader unlock app, extract the UnlockTool_9.1.0.3_180621_fulldpi_Draco_GDPR.apk and copy it to your phone.
Use a filemanager on your phone to install it and follow the on screen instructions to unlock the bootloader.
WARNING! You will lose your warranty and all data on the phone so backup beforehand. You will see the first warning message at boot after this. There is currently no method know to relock the bootloader.
Download payload_dumper and extract it to c:\5z\. A payload_dumper-win64 folder will be created.
Download the firmware zip of the version you have on your phone and extract payload.bin from the zip to c:\5z\payload_dumper-win64\payload_input\ folder.
Start c:\5z\payload_dumper-win64\payload_dumper.exe and let it finish. Now copy the c:\5z\payload_dumper-win64\payload_output\boot.img to your phone (i will use the download folder).
Download Magisk Manager, copy the apk to your phone and use a filemanager on your phone to install it. Start the app and update it if you are asked.
When you are asked if you want to install Magisk > install. Select Method > Patch Boot Image File. Now select the boot.img in the download folder and let it finish patching.
Copy the patched_boot.img from the MagiskManager folder on your phone to c:\5z\platform-tools\
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\platform-tools\
To check if your phone has been found:
Code:
fastboot devices
You should see the serial number of your phone.
Now flashing the patched boot image:
Code:
fastboot flash boot patched_boot.img
The output should look something like this:
target reported max download size of 268435456 bytes
sending 'boot' (18724 KB)...
OKAY [ 0.620s]
writing 'boot_a'...
OKAY [ 0.133s]
finished. total time: 0.756s
And the reboot:
Code:
fastboot reboot
Your phone should be booting now and you will see the second warning message "There is an internal problem with your device...".
If you want to get rid of that warning and do not need write access to your vendor partition (you most likely do not):
Open Magisk Manager and in the main screen press Uninstall > Restore Images to restore the images, check Preserve AVB 2.0/dm-verity checkbox in "Advanced Settings" on the main screen, then reinstall Magisk by pressing Install > direct install in the main screen.
Should you be stuck in the Zenfone boot animation or something went wrong, you will need to follow the steps in the unbrick section.
Otherwise your phone is rooted now. Enjoy.
[Downgrade/unbrick how to]
Download and extract the raw firmware.
With the phone in fastboot mode execute flashall_aft.cmd in the extraction folder.
You are now downgraded/unbricked with firmware 80.10.8.54.
Copy firmware version of your choice to internal sd card root and reboot/unplug usb cable to get "update notification".
Start the update to selected firmware from the "update found" notification.
[Downgrade/unbrick guide]
If you need to downgrade the firmware or if you have somehow bricked your device you can try to flash a raw (full) image of the phone.
Download and extract the raw firmware to c:\5z\raw.
If the download link is no longer working google for WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip and download it.
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\raw
To flash the raw image:
Code:
flashall_aft.cmd
This will take a few minutes and the phone will reboot automatically. The first boot will take a little longer but your phone should now be unbricked and downgraded to 80.10.8.54.
You can now go to the root section of the guide and upgrade to a more current firmware.
Thanks to Renaf2 for his ZE620KL guide, GSPD and amscova for providing the ZS620KL raw image links and B Nath for finding the ZS621KL raw image.

Nice Theard
Thank You for your work

Upgrade after rooting
Hello,after downgrade and rooting the phone with your method,it is posible to put in internal memory the last version of firmware(80.11.37.86) and upgrade the phone,or the phone remains blocked in the version of firmware(80.11.37.69) which we make downgrade and root?Thank you for your hard work.

isthisadagger said:
Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
Click to expand...
Click to collapse
Process is too long. I am working on unofficial Unlock Tool so that we can retain the warranty.
For downgrading, there is a tool for that. For me, fastboot codes may mess up the system/cache partitions.
If anyone wanna test my unlocking tool, feel free to PM me via Telegram
MOD EDIT: LINK REMOVED
The distribution of social media links is no longer allowed on XDA. Please refer to the thread linked below:
Telegram and Whatsapp Channels - Going Forward

mihaitaiosub said:
Hello,after downgrade and rooting the phone with your method,it is posible to put in internal memory the last version of firmware(80.11.37.86) and upgrade the phone,or the phone remains blocked in the version of firmware(80.11.37.69) which we make downgrade and root?Thank you for your hard work.
Click to expand...
Click to collapse
Yes it is possible but you will lose root.
Patching the boot.img for 80.11.37.79 and 80.11.37.86 does not seem to work with this method.

isthisadagger said:
Yes it is possible but you will lose root.
Patching the boot.img for 80.11.37.79 and 80.11.37.86 does not seem to work with this method.
Click to expand...
Click to collapse
And is not possible to root again whith method described on this thread?

mihaitaiosub said:
And is not possible to root again whith method described on this thread?
Click to expand...
Click to collapse
This is why we need TWRP.

mihaitaiosub said:
And is not possible to root again whith method described on this thread?
Click to expand...
Click to collapse
It is possible with Magisk Manager 5.8.3.

isthisadagger said:
Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
[Update 20.07.2018] I was able to root FW 80.11.37.86 with Magisk Manager 5.8.3 so you are no longer locked to FW 80.11.37.69 and do not have to downgrade.
This guide is split into two sections: rooting and downgrade/unbrick.
Each section is split into a quick how to for experienced users and a more detailed guide.
General info:
The most current firmware as iof 20.07.18 is 80.11.37.86.
I have only tested this on my ZS620KL Z01RD WW version. It should work on other variants JP/RU.
This guide is written for firmware 80.11.37.86. If you do not want to upgrade to 80.11.37.86 you will need to use the firmware you are on in all the steps.
Magisk hide is working and Safetynet check passes.
Bugs/problems:
Unlocking the bootloader will void your warranty!
You will get a warning message about your unlocked bootloader at every boot.
You will get a warning message about an internal problem every boot. Which you can disable if you do not need write access to the vendor partition.
> see rooting guide 10.
[Downloads]
for rooting
The latest and official platform tools (adb/fastboot) directly from google.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Payload_dumper to extract the boot.img from the firmware:
https://androidfilehost.com/?fid=818070582850510260
Magisk Manager:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The bootloader unlock app and the 80.11.37.86 firmware for your device (WW/RU/JP) from ASUS:
https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_Download/
for downgrade/unbrick
raw firmware:
https://drive.google.com/file/d/1ogbQeeNDRPFCb9jl3kpRDK_DmsneQ0xL/view?usp=drivesdk
[Rooting how to]
Upgrade to firmware 80.11.37.86 and enable usb debugging.
Unlock your bootloader with the app.
Extract boot.img from firmware using payload_dumper.
Patch boot.img with magisk manager.
fastboot flash boot patched_boot.img.
Enjoy root.
[Rooting guide]
You can root any firmware up to 80.11.37.86 with this guide. To upgrade to a newer firmware version copy the zip file (e.g. UL-Z01R-WW-80.11.37.86-user.zip) you downloaded from Asus
to the root of your phones internal memory and reboot or unplug your usb cable.
You will get an update found notification. Start the update. To downgrade check the downgrade guide below.
Enable usb debugging in System > Developer options. If you can not see System > Developer options go to System > About phone > Software information > Build number and tap it multiple times.
This will make the Developer options visible.
WARNING! Upgrading to some firmwares disables usb debugging and you need to enable it again.
Make a backup of all the data you do not want to lose.
Download the platform tools and extract them into a folder (i will use c:\5z\ in this guide) this will create a subfolder platform-tools.
You need a current fastboot version for this to work (due to a/b slots/partitions), so please use the current platformtools!
Download the bootloader unlock app, extract the UnlockTool_9.1.0.3_180621_fulldpi_Draco_GDPR.apk and copy it to your phone.
Use a filemanager on your phone to install it and follow the on screen instructions to unlock the bootloader.
WARNING! You will lose your warranty and all data on the phone so backup beforehand. You will see the first warning message at boot after this.
Download payload_dumper and extract it to c:\5z\. A payload_dumper-win64 folder will be created.
Download the firmware zip of the version you have on your phone and extract payload.bin from the zip to c:\5z\payload_dumper-win64\payload_input\ folder.
Start c:\5z\payload_dumper-win64\payload_dumper.exe and let it finish. Now copy the c:\5z\payload_dumper-win64\payload_output\boot.img to your phone (i will use the download folder).
Download Magisk Manager, copy the apk to your phone and use a filemanager on your phone to install it. Start the app and update it if you are asked.
When you are asked if you want to install Magisk > install. Select Method > Patch Boot Image File. Now select the boot.img in the download folder and let it finish patching.
Copy the patched_boot.img from the MagiskManager folder on your phone to c:\5z\platform-tools\
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\platform-tools\
To check if your phone has been found:
Code:
fastboot devices
You should see the serial number of your phone.
Now flashing the patched boot image:
Code:
fastboot flash boot patched_boot.img
The output should look something like this:
target reported max download size of 268435456 bytes
sending 'boot' (18724 KB)...
OKAY [ 0.620s]
writing 'boot_a'...
OKAY [ 0.133s]
finished. total time: 0.756s
And the reboot:
Code:
fastboot reboot
Your phone should be booting now and you will see the second warning message "There is an internal problem with your device...".
If you want to get rid of that warning and do not need write access to your vendor partition (you most likely do not):
Open Magisk Manager and in the main screen press Uninstall > Restore Images to restore the images, check Preserve AVB 2.0/dm-verity checkbox in "Advanced Settings" on the main screen, then reinstall Magisk by pressing Install > direct install in the main screen.
Should you be stuck in the Zenfone boot animation or something went wrong, you will need to follow the steps in the unbrick section.
Otherwise your phone is rooted now. Enjoy.
[Downgrade/unbrick how to]
Download and extract the raw firmware.
With the phone in fastboot mode execute flashall_aft.cmd in the extraction folder.
You are now downgraded/unbricked with firmware 80.10.8.54.
Copy firmware version of your choice to internal sd card root and reboot/unplug usb cable to get "update notification".
Start the update to selected firmware from the "update found" notification.
[Downgrade/unbrick guide]
If you need to downgrade the firmware or if you have somehow bricked your device you can try to flash a raw (full) image of the phone.
Download and extract the raw firmware to c:\5z\raw.
If the download link is no longer working google for WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip and download it.
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\raw
To flash the raw image:
Code:
patchall_aft.cmd
This will take a few minutes and the phone will reboot automatically. The first boot will take a little longer but your phone should now be unbricked and downgraded to 80.10.8.54.
You can now go to the root section of the guide and upgrade to a more current firmware.
Thanks to Renaf2 for his ZE620KL guide and GSPD for providing the raw image name.
Click to expand...
Click to collapse
Does unbricking lock the bootloader back since we will be flashing a raw a file.

With Magisk Manager 5.8.3 the whole guide works like a charm
THX

My Zenfone 5z isn't being detected in fastboot mode, kindly help with correct driver softwares, my PC is running on Windows 10
Update : I got my phone to detect in fastboot

How to wipe cache partition
Hi,
I am able to boot into recovery on Z5z but not able to see "wipe cache partition" option. I only see a wipe data/factory reset option.
I want to wipe cache to see if battery life improves. Can anyone let me know how to do this?
Thanks

chandru.biradar2 said:
Does unbricking lock the bootloader back since we will be flashing a raw a file.
Click to expand...
Click to collapse
No.

kelly66 said:
Hi,
I am able to boot into recovery on Z5z but not able to see "wipe cache partition" option. I only see a wipe data/factory reset option.
I want to wipe cache to see if battery life improves. Can anyone let me know how to do this?
Thanks
Click to expand...
Click to collapse
Honestly killing the cache rarely helps things.

hi guys how to do this on Macbook pro? Any clues?

shantanudl said:
hi guys how to do this on Macbook pro? Any clues?
Click to expand...
Click to collapse
I do not have any experience with mac os but if you want to root:
Adb/fastboot is available for mac os. All you need to do is find a tool to extract the boot.img from the payload.bin.
If you want to downgrade/unbrick: You would need to convert the bat/cmd files in the full firmware to some shell scripts and exchange the fastboot.exe.

How do I un-root, re-lock bootloader?

ferez said:
How do I un-root, re-lock bootloader?
Click to expand...
Click to collapse
unroot: You press "uninstall" in magisk manager or install an updated firmware without patching boot.img or downgrade.
I have not tried re-locking the bootloader.

So if I'm getting this right, after unlocking the bootloader I will not get OTA updates.
But I will be able to download the latest version (SKU) from Asus and put it in /sdcard/ folder, and rebooting will start the update of the new firmware.
Is this correct?
Kind regards
/Jens

jens13 said:
So if I'm getting this right, after unlocking the bootloader I will not get OTA updates.
But I will be able to download the latest version (SKU) from Asus and put it in /sdcard/ folder, and rebooting will start the update of the new firmware.
Is this correct?
Kind regards
/Jens
Click to expand...
Click to collapse
You won't get OTAs + your warranty is voided (due to unlocking Officially)
Yes, you can update your phone by sideloading the zip from ASUS Support Website

HELP!! (Soft-) bricked my P20Pro CLT-L29

He guys,
as you've read I bricked my phone and I don't know how or where I did the mistake?
Status before brick:
-) FW: EMUI 8.xxx (not exactly sure which one it was)
-) TWRP: 3.2.3.0
-) Rooted
-) BL: unlocked
-) PHONE Unlock
-) FRP Unlock
What I wanted to do:
-) FW Update to: EMUI 9.0 via FirmwareFinder
What I've done:
-) Did a Titanium Backup
-) Installed Firmware Finder
-) Downloaded the Firmware CLT-L29C432E5R1P9B195 (9.0.0.195) (BUT there were ONLY 2 files)
-) 1. file was "update.zip"
-) 2. file was "update_full_CLT-L29_hw_eu.zip"
-) Renamed the files to
-) 1. kept file name "update.zip"
-) 2. file renamed "update_full_CLT-L29_hw_eu.zip" --> update_all_hw.zip
-) Put the 2 files + hurupdater_04.zip + recovery.img (TWRP 3.2.1.0.img) to a folder in Root on my device
-) Reboot to recovery -> TWRP
-) TWRP -> Install -> hurupdater_04.zip
ERRORS:
-) first I saw a message --> "CLT-L09 "Firmware installing --> how can that happened, if I downloaded the CLT-L29 version?
-) Then it aborted the installing process
Current situation:
-) TWRP is installed again --> TWRP 3.2.1.-0 by Pretorian
-) PHONE Unlock
-) FRP Unlock
-) no OS
!! Cannot access my files either via TWRP or Windows explorer --> all files are encrypted and have totally weird names
So please, please help me installing an OS again!
!! And is there a chance to get access to my pictures back???
I appreciate every helpfull advise.
Thanks in advance!!!

He guys,
nobody has an idea to solve/help me with my issues/situation?
I searched the forum and also other forums and pages to find a solution to "my" problem, but without any helpful results.
I am afraid of doing an eRecovery restore because of losing all my data.
I have currently: TWRP installed -> Files/folders with weird names (shown in TWRP & Phone connected to PC "Explorer")
What can I do to save, restore, copy my pictures and files from phone to PC?
Please give me some hints.

This way brought me back
Try downloading the firmware here: FIRMWARE
Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.

Vedrick said:
Try downloading the firmware here: FIRMWARE
Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.
Click to expand...
Click to collapse
Thanks for the help and the links.
BUT before I'll start doing this, there is just one issue left: the encrypted "storage / files" (pics etc.) in TWRP.
BEFORE I want to say, that I've removed all the security barriers like fingerprint, pattern and faceID !!!!
I tried using this https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
with different kinds of TWRP versions:
TWRP 3.2.1-0.img
twrp_clt_0.1.img frome here
https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
twrp-3.2.1-0-charlotte-mod.img frome here
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
twrp-3.2.3-4-charlotte.img
But nothing works, my files shown in TWRP -> storage are still encrypted and still shown with weird gibberish names?
Do you know how to solve this, or where I can get the right TWRP version?
I'm totally at the end of ideas and not finding the right way to get access to my pictures and stuff again.

Da_Hausa said:
Thanks for the help and the links.
BUT before I'll start doing this, there is just one issue left: the encrypted "storage / files" (pics etc.) in TWRP.
BEFORE I want to say, that I've removed all the security barriers like fingerprint, pattern and faceID !!!!
I tried using this https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
with different kinds of TWRP versions:
TWRP 3.2.1-0.img
twrp_clt_0.1.img frome here
https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
twrp-3.2.1-0-charlotte-mod.img frome here
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
twrp-3.2.3-4-charlotte.img
But nothing works, my files shown in TWRP -> storage are still encrypted and still shown with weird gibberish names?
Do you know how to solve this, or where I can get the right TWRP version?
I'm totally at the end of ideas and not finding the right way to get access to my pictures and stuff again.
Click to expand...
Click to collapse
I honestly don't think any twrp will work, another reason i'll never buy a huawei again. You could try extracting the image files from the update.app that you get from the update.zip file. then manually flash:
You can extract the image files using EMUI Extractor Application.
fastboot flash cust cust.img
fastboot flash system system.img
I believe the pictures are located on the userdata partition. be sure to flash the right android version as it may depend on what framework you have and how far you got when it was updating. You may want to verify the location of those pictures first.

SO I replicated your soft brick, after I backup up my photos. I ccouldn't save them. I'm up and running though. Turns out I had to first manually flash those image files located in update.app. Then I had to do this

Modified\Updated (Bricked device fix)
1) Try downloading the firmware here: FIRMWARE
2) Extract the update.app file from the update.zip, then use EMUI extractor to extract all the image files. You'll then need to manually flash a few of them: (You can move all these images into the main folder of the Reflash tools located in step 3, then run CMD-HERE)
Commands: (Some might error, i forget which but its alright)
fastboot flash cust cust.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk recovery_ramdis.img (Very Important)
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash vector vector.img
fastboot flash system system.img
fastboot reboot, unplug the USB-C cable and hold the volume up button. this will put you into recovery mode.
Then you'll need to format data using with the EMUI recovery and if given the option format cache.
Reboot back into bootloader\Download mode.
3) Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.

Unfortunately I seem to have the same issue. I followed @Vedrick's tutorial.
However after fastboot reboot I'm stuck on 'Your device is booting now...'
Any ideas?
I worry that perhaps the 'boot image' on my p20 is messed up. However in the .APP file I can't find the boot image to restore. I do however see 2 SYSTEM images.
nvm! Got it! Had to fastboot erase userdata.

Question How to flash twrp recovery and root redmi note 10s?

I can't install a twrp recovery if I tried
A message appears (remote : this partition doesn't exist)

You wont be able to find rosemary's twrps yet... But you can root this model unlocking bootloader and flashing a modified boot.img from magisk APK, you can follow this instructions to do that; (you'll need the redmi note 10 s original rom firmware to extract the boot img and you can get it from here: https://c.mi.com/es/miuidownload/detail?device=1900397)
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR.​
Now install the Magisk Manager app on your phone.​
Open the Magisk Manager app and click on the Install.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the next step choose ‘Select and Patch a File’ from the option.
Browse and select the boot.img file, and it will start patching the boot image.​
The output file will be stored in the download folder with the name magisk_patched.img.​
Copy the patched boot image file to your computer in folder C:\adb. Also, rename the patched file to boot.img.​
Reboot your Redmi Note 10 to Fastboot mode and connect it to your computer.​
In the C:\adb folder (or platform-tools folder) press Shift + Right click on an empty area and select ‘Open Command window here’ or ‘Open PowerShell window here.’
You can check if the device is connected or not by entering the below command that should return some device id.​
fastboot devices​
Now enter the below command to flash Magisk and root Redmi Note 10.​
fastboot flash boot boot.img​
After flashing the patched boot image. reboot your device to the system.​
Install Magisk Manager if it’s not already installed.​
Complete the in-app instructions, and the device will automatically reboot into the system.​
That’s all, now your phone is rooted. You can check for root access using any root checker app. And once you have root access on your Redmi Note 10, you can enjoy all the apps and features that require root access. As you know Xiaomi phones show ads on some system apps that you can disable with root access. You can use different Xposed Modules to customize your phone. Also, you can install Xposed Framework on your phone to use modules.
Or if your system has an a/b partition you'll have to type this on your command window:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img

Or follow this page... https://mytechgyangadgets.com/how-to-root-redmi-note-10s-via-magisk-and-supersu/

Ali mohamed 96 said:
I can't install a twrp recovery if I tried
A message appears (remote : this partition doesn't exist)
Click to expand...
Click to collapse
Theres 2 ways to do It explained up but i prefer first one

This is a questionable part I think:
1. If your phone doesn’t have A/B partition system:
fastboot flash boot boot.img
2. If your phone has A/B partition system:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Based on the Treble Check app, at least my phone, supported Seamless System Updates and is detected to have an A/B system partition => should be used 2?
This might be a reason of : "this partition doesn't exist" with 1.
Source: https://www.naldotech.com/root-xiaomi-redmi-note-10s-magisk/

#bosr you have to follow the second step pf your post yo success, It seems that note's 10 has an a/b system partition...

!! Success !!
The process I´ve rooted my Redmi Note 10s with V12.5.8.0.RKLEUXM ROM:
(besides all needed drivers, adbs, proper fasboot ROM version, unlocked bootloader, little bit of a fear that the phone could be hard bricked and a few more) :
- patched boot.img via magisk manager v23
- flashed empty vbmeta.img as decribed here https://forum.xda-developers.com/t/root-gained.4290689/
- flashed patched_boot.img (the latest platform-tools flashed it directly to boot_a)
- reboot
Voila, Redmi Note 10s is rooted and Magisk v23 installed

Ricardo 182 said:
You wont be able to find rosemary's twrps yet... But you can root this model unlocking bootloader and flashing a modified boot.img from magisk APK, you can follow this instructions to do that; (you'll need the redmi note 10 s original rom firmware to extract the boot img and you can get it from here: https://c.mi.com/es/miuidownload/detail?device=1900397)
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR.​
Now install the Magisk Manager app on your phone.​
Open the Magisk Manager app and click on the Install.
In the next step choose ‘Select and Patch a File’ from the option.
Browse and select the boot.img file, and it will start patching the boot image.​
The output file will be stored in the download folder with the name magisk_patched.img.​
Copy the patched boot image file to your computer in folder C:\adb. Also, rename the patched file to boot.img.​
Reboot your Redmi Note 10 to Fastboot mode and connect it to your computer.​
In the C:\adb folder (or platform-tools folder) press Shift + Right click on an empty area and select ‘Open Command window here’ or ‘Open PowerShell window here.’
You can check if the device is connected or not by entering the below command that should return some device id.​
fastboot devices​
Now enter the below command to flash Magisk and root Redmi Note 10.​
fastboot flash boot boot.img​
After flashing the patched boot image. reboot your device to the system.​
Install Magisk Manager if it’s not already installed.​
Complete the in-app instructions, and the device will automatically reboot into the system.​
That’s all, now your phone is rooted. You can check for root access using any root checker app. And once you have root access on your Redmi Note 10, you can enjoy all the apps and features that require root access. As you know Xiaomi phones show ads on some system apps that you can disable with root access. You can use different Xposed Modules to customize your phone. Also, you can install Xposed Framework on your phone to use modules.
Or if your system has an a/b partition you'll have to type this on your command window:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Click to expand...
Click to collapse
"
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR."
I am not able to see boot.img file in the extracted rom. I used the same link that you had shared to download the rom. This is the file name - miui_ROSEMARYINGlobal_V12.5.5.0.RKLINXM_ab4be8a721_11.0.zip.
What is the mistake I am making?

GildroY said:
"
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR."
I am not able to see boot.img file in the extracted rom. I used the same link that you had shared to download the rom. This is the file name - miui_ROSEMARYINGlobal_V12.5.5.0.RKLINXM_ab4be8a721_11.0.zip.
What is the mistake I am making?
Click to expand...
Click to collapse
Also checked the global rom from here https://xiaomifirmwareupdater.com/miui/rosemary/stable beta/V12.5.12.0.RKLMIXM/
Same thing - cant find the boot.img

GildroY said:
Also checked the global rom from here https://xiaomifirmwareupdater.com/miui/rosemary/stable beta/V12.5.12.0.RKLMIXM/
Same thing - cant find the boot.img
Click to expand...
Click to collapse
You are searching in the wrong type of ROM. It must be the fastboot type.
for example: rosemary_global_images_V12.5.11.0.RKLMIXM_20210618.0000.00_11.0_global_06239807c1.tgz
Unpack (winrar, winzip, 7-zip ...) it, there is a folder images and boot.img in it
Do not forget to flash empty vbmeta.img first, see here

bosr said:
You are searching in the wrong type of ROM. It must be the fastboot type.
Unzip it, there is a folder images and boot.img in it
Click to expand...
Click to collapse
Yeah. Apologies. Just realized it.

I was able to successfully get root access using the additional step mentioned by @bosr (Thanks a lot for that). However post that I literally bricked my device trying to debloat the device by using debloater. Post removing few of the mi bloatware apps, when I rebooted and the device kept on going into default mi recovery (even with power + vol-). I was not able to access the fastboot mode at all, no matter what I do.
Then I did the ultimate blunder ... reset the device from mi recovery. Post that I lost adb privileges as well. Besides the phone would still not boot - MIUI logo flashed with sound, then a white setup screen for a sec and again reboot.
Searching online could not fetch anything. Then I tried moving the phone to mi assistance mode from mi recovery (which is nothing but sideload mode), connect to PC and used 'adb sideload'.
Voila, the phone was detected, from sideload mode, I was able to reboot to fastboot mode, and then flash the stock rom using miflashtool. Whole 4 hours of tussle.
Sharing here, just in case someone else, gets into the same situation.
!! BADLY WAITING FOR A CLEAN ROM FOR THIS DEVICE .... <Prayers>!!

It is strange.
I did it on two "10s" devices with EAA roms w/o problems.
Did you flash flash empty vbmeta.img first and boot.img than?
Did you use the latest platform-tools as previous ones are not able to flash directly to boot_a) automatically and you must use fastboot flash boot_a command instead.

bosr said:
It is strange.
I did it on two "10s" devices with EAA roms w/o problems.
Did you flash flash empty vbmeta.img first and boot.img than?
Did you use the latest platform-tools as previous ones are not able to flash directly to boot_a) automatically and you must use fastboot flash boot_a command instead.
Click to expand...
Click to collapse
Apologies for incorrect use of language. What I meant was that your instructions were 100% correct and accurate. However, post getting root access successfully and magisk installed, I tried to debloat the device using 'debloater' module under Magisk and ended up deleting some rogue apps which Mi wants us to keep. All the issues happened after that.
I have updated my original comment as well.

OK. Apology accepted

Hi Y'all,
I just got a new Note 10s and I'm willing to root device.
I'm still in the phase of waiting for the unlocked bootloader, but already trying to get all the necessary data for root.
While searching for the fastbbot Rom to extract the boot.img I discovered the follwing problem:
I can only find the fastboot Rom for the following SW: V12.5.8.0.RKLEUXM
But my Note 10s is already on V12.5.10.0.RKLEUXM. For this SW only the recovery ROM is available.
How long will it take for Xiaomi to upload the latest fastboot ROM? Or am I doing something wrong,
Any help really appreciated
Andreas

I also got a new Note 10s. I updated it to the latest available version (12.5.8.0 RKLEUXM, EEA).
Downloaded these ROMs (recovery and fastboot):
miui_ROSEMARYEEAGlobal_V12.5.8.0.RKLEUXM_b29e7c6a8a_11.0.zip
rosemary_eea_global_images_V12.5.8.0.RKLEUXM_20210617.0000.00_11.0_eea_6ec37534bb.tgz
But I didn't found any boot.img in the last fastboot one.
Finally I extracted boot.img from the first one (recovery) using payload_dumper - but what's wrong with the easier and usual way to extract it from the fastboot ROM? Isn't it available anymore inside this ROM?
@Agzyx
You could try the payload_dumper method to extract boot.img from recovery ROM.

@Mac23
payload_dumper may be a solution. I need to wait another 5 days for bootloader unlock anyway, so I have some more time before trying to gain root access.
@All
Is there a way to "downgrade" to V12.5.8.0.RKLEUXM?
Loss of data is no problem, as the phone will be rooted anyway in the future.
Andreas

Agzyx said:
@Mac23
payload_dumper may be a solution. I need to wait another 5 days for bootloader unlock anyway, so I have some more time before trying to gain root access.
@All
Is there a way to "downgrade" to V12.5.8.0.RKLEUXM?
Loss of data is no problem, as the phone will be rooted anyway in the future.
Andreas
Click to expand...
Click to collapse
It should be possible with XiaoMiTool

Mac23 said:
I also got a new Note 10s. I updated it to the latest available version (12.5.8.0 RKLEUXM, EEA).
Downloaded these ROMs (recovery and fastboot):
miui_ROSEMARYEEAGlobal_V12.5.8.0.RKLEUXM_b29e7c6a8a_11.0.zip
rosemary_eea_global_images_V12.5.8.0.RKLEUXM_20210617.0000.00_11.0_eea_6ec37534bb.tgz
But I didn't found any boot.img in the last fastboot one.
Finally I extracted boot.img from the first one (recovery) using payload_dumper - but what's wrong with the easier and usual way to extract it from the fastboot ROM? Isn't it available anymore inside this ROM?
@Agzyx
You could try the payload_dumper method to extract boot.img from recovery ROM.
Click to expand...
Click to collapse
Not sure, what you are looking for, but boot.img is in the fastboot rom:

How To Guide [UPDATED] [REALME 8i/NARZO 50] How to get fastboot access and root your device easily.

Hello everyone! In this guide, I Sidharth will tell you how to flash recovery, root and access bootloader on the Realme 8i and Narzo 50, you probably have seen another guide by Pritish, it's not wrong but it became kind of outdated .
So lets begin,
Requirements:
PC (with windows or linux installed)
Platform tools installed
First unlock the bootloader by following this guide: http://telegra.ph/HOW-TO-UNLOCK-BOOTLOADER-REALME-8INARZO-50-05-08
Or this guide: https://forum.xda-developers.com/t/...-flash-twrp-and-root-rmx3151-rmx3286.4369399/ (dont worry about the boot imgs, just unlock the bootloader normally and boot the phone, don't go on the second step)
So after doing that, you should have platform tools and adb drivers installed, I am not going to tell you how to do that exactly but you should find tons of tutorials on the internet for both linux and windows. (I am going to be using Linux in this case but everything is the same for both windows and linux in this case)
Download this file: https://drive.google.com/file/d/13J2zlrUz84ZDSPERdosgNO6xdhwah4hl/view?usp=sharing
and paste it in your mtkclient folder (you should have that by now if you already unlocked the bootloader.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open the terminal and then type: python mtk w lk lk.bin
Now, power off your phone, hold both volume buttons and until it is done
Check if the phone boots into fastboot by holding volume down and power.
If it shows something like this then congrats, you have fastboot access now.
Flashing recovery is very easy now.
Download TWRP image from the TWRP website: https://twrp.me/realme/realme8i.html
Just keep it in the platform tools folder for now.
Boot into your phone, and download the magisk apk from here: https://github.com/topjohnwu/Magisk/releases
After downloading it, download ZArchiver from the Play Store and replace .apk with .zip and save it.
Now power off the phone and boot into fastboot/bootloader.
Open the terminal inside platform tools and:
fastboot flash recovery recovery.img
fastboot reboot recovery
You will be in your custom recovery now .
Now goto install, and select your magisk zip, and flash it normally.
After that is done, reboot to system and rename the magisk zip to apk again and install the apk.
Boom you have also rooted your device .
Thanks to Pritish for bootloader unlock guide and patched lk

also guys please let me know if you have any problems

here is how you can setup mtkclient on linux:
git clone https://github.com/bkerler/mtkclient
cd mtkclient
pip3 install -r requirements.txt
then you should have a mtkclient folder where u can execute the commands

bootloop on logo no way to fix hard to find how i can unbrick
the only thimg im able to do is on adb reflash the recovery and acces the Recovery TWRP but no way to acces the system

suauvia said:
bootloop on logo no way to fix hard to find how i can unbrick
the only thimg im able to do is on adb reflash the recovery and acces the Recovery TWRP but no way to acces the system
Click to expand...
Click to collapse
Just like bootloader unlock method, in MTK Tools, give this command:
#
python mtk e metadata,userdata,md_udc
#
(Without #)
Then connect your phone in BROM mode, then restart. it will be fine

suauvia said:
bootloop on logo no way to fix hard to find how i can unbrick
the only thimg im able to do is on adb reflash the recovery and acces the Recovery TWRP but no way to acces the system
Click to expand...
Click to collapse
be specific, did the lk file cause this or are you tryintg to unbrick through fastboot
if the lk caused this then tell me if you are on realme ui 3.0 or you are a narzo 50 user.

Sidharth09 said:
be specific, did the lk file cause this or are you tryintg to unbrick through fastboot
if the lk caused this then tell me if you are on realme ui 3.0 or you are a narzo 50 user.
Click to expand...
Click to collapse
thanks for your help but after doing so
python mtk e metadata,userdata,md_udc
nothing ha changed stil on realme logo and orange state and 5 seconds message and reloop reboot again
i was on UI 2,0 and updated firmware RMX3151 11.A_46
no idea if Lk make this
i have reflashed the stock recovery and format data also with TWRP recovery format data and cache but always on any move its a reloop reboot on Realme logo
-------
if i relock the bootloader ist possible to recover this phone and then how i can do this
im 67 old and not very used to this kind of operations

heroksiddiqi said:
Just like bootloader unlock method, in MTK Tools, give this command:
#
python mtk e metadata,userdata,md_udc
#
(Without #)
Then connect your phone in BROM mode, then restart. it will be fine
Click to expand...
Click to collapse
python mtk e metadata,userdata,md_udc
doneand nothing has changed

Is there a way to do this on a Mac? I have Realme 8i RMX3151 but do not have access to a Windows computer. Thank you.
I tried the Deep Testing App and it gives the following error "Failed to submit application. This phone model does not support deep testing."

suauvia said:
thanks for your help but after doing so
python mtk e metadata,userdata,md_udc
nothing ha changed stil on realme logo and orange state and 5 seconds message and reloop reboot again
i was on UI 2,0 and updated firmware RMX3151 11.A_46
no idea if Lk make this
i have reflashed the stock recovery and format data also with TWRP recovery format data and cache but always on any move its a reloop reboot on Realme logo
-------
if i relock the bootloader ist possible to recover this phone and then how i can do this
im 67 old and not very used to this kind of operations
Click to expand...
Click to collapse
u can always flash your stock LK again if it somehow made a problem so here
paste it in mtkclient and then
python mtk w lk lk.img
check if it fixes it!

jack1192 said:
Is there a way to do this on a Mac? I have Realme 8i RMX3151 but do not have access to a Windows computer. Thank you.
I tried the Deep Testing App and it gives the following error "Failed to submit application. This phone model does not support deep testing."
Click to expand...
Click to collapse
with mac it is not possible since mtkclient does not work on a mac

Sidharth09 said:
u can always flash your stock LK again if it somehow made a problem so here
paste it in mtkclient and then
python mtk w lk lk.img
check if it fixes it!
Click to expand...
Click to collapse
not working even worst even on fastboot it blocks about nserie decrypt or something like not remember well now i remake the process and get back to locked reboot on logo --- i would ask if i am on TWRP recovery and i want to flash a 7z firmware on .ofp files or a decrypted zip file do you think it will work ??
anyway trying to copy the 6 giigas firmware zip to an SD card the pc say that is too big to copy so maybe thru fastboot i can copt to the phone but i dont know about the command if you know about please let me know about the procedure if is positive way
or ist it any other way to recover the phone ??
finally i would like to install a Lineage customrom

suauvia said:
not working even worst even on fastboot it blocks about nserie decrypt or something like not remember well now i remake the process and get back to locked reboot on logo --- i would ask if i am on TWRP recovery and i want to flash a 7z firmware on .ofp files or a decrypted zip file do you think it will work ??
anyway trying to copy the 6 giigas firmware zip to an SD card the pc say that is too big to copy so maybe thru fastboot i can copt to the phone but i dont know about the command if you know about please let me know about the procedure if is positive way
or ist it any other way to recover the phone ??
finally i would like to install a Lineage customrom
Click to expand...
Click to collapse
finally i follow instructions on this link
[GUIDE][UNBRICK] Realme 8i/Narzo 50 Unbrick Free without Auth [RMX3151][RMX3286]
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX3151 (Realme 8i) and RMX3286...
forum.xda-developers.com
[GUIDE][UNBRICK] Realme 8i/Narzo 50 Unbrick Free without Auth [RMX3151][RMX3286]​all well now
thanks your guide to unlock the bootloader works a charm no success with other ones

Sidharth09 said:
Hello everyone! In this guide, I Sidharth will tell you how to flash recovery, root and access bootloader on the Realme 8i and Narzo 50, you probably have seen another guide by Pritish, it's not wrong but it became kind of outdated .
So lets begin,
Requirements:
PC (with windows or linux installed)
Platform tools installed
First unlock the bootloader by following this guide: http://telegra.ph/HOW-TO-UNLOCK-BOOTLOADER-REALME-8INARZO-50-05-08
Or this guide: https://forum.xda-developers.com/t/...-flash-twrp-and-root-rmx3151-rmx3286.4369399/ (dont worry about the boot imgs, just unlock the bootloader normally and boot the phone, don't go on the second step)
So after doing that, you should have platform tools and adb drivers installed, I am not going to tell you how to do that exactly but you should find tons of tutorials on the internet for both linux and windows. (I am going to be using Linux in this case but everything is the same for both windows and linux in this case)
Download this file: https://drive.google.com/file/d/13J2zlrUz84ZDSPERdosgNO6xdhwah4hl/view?usp=sharing
and paste it in your mtkclient folder (you should have that by now if you already unlocked the bootloader.)View attachment 5682939
Open the terminal and then type: python mtk w lk lk.bin
View attachment 5682941
Now, power off your phone, hold both volume buttons and until it is done
View attachment 5682943
Check if the phone boots into fastboot by holding volume down and power.
If it shows something like this then congrats, you have fastboot access now.View attachment 5682945
Flashing recovery is very easy now.
Download TWRP image from the TWRP website: https://twrp.me/realme/realme8i.html
Just keep it in the platform tools folder for now.
Boot into your phone, and download the magisk apk from here: https://github.com/topjohnwu/Magisk/releases
After downloading it, download ZArchiver from the Play Store and replace .apk with .zip and save it.
Now power off the phone and boot into fastboot/bootloader.
Open the terminal inside platform tools and:
fastboot flash recovery recovery.img
fastboot reboot recovery
You will be in your custom recovery now .
Now goto install, and select your magisk zip, and flash it normally.
After that is done, reboot to system and rename the magisk zip to apk again and install the apk.
Boom you have also rooted your device .
Thanks to Pritish for bootloader unlock guide and patched lk
Click to expand...
Click to collapse
now I cannot turn on my phone after try to access recovery :/

hoangnguyen320 said:
now I cannot turn on my phone after try to access recovery :/
Click to expand...
Click to collapse
i holded power button for 5 minutes...

hoangnguyen320 said:
i holded power button for 5 minutes..
Click to expand...
Click to collapse
volume up and power?

Sidharth09 said:
Hello everyone! In this guide, I Sidharth will tell you how to flash recovery, root and access bootloader on the Realme 8i and Narzo 50, you probably have seen another guide by Pritish, it's not wrong but it became kind of outdated .
So lets begin,
Requirements:
PC (with windows or linux installed)
Platform tools installed
First unlock the bootloader by following this guide: http://telegra.ph/HOW-TO-UNLOCK-BOOTLOADER-REALME-8INARZO-50-05-08
Or this guide: https://forum.xda-developers.com/t/...-flash-twrp-and-root-rmx3151-rmx3286.4369399/ (dont worry about the boot imgs, just unlock the bootloader normally and boot the phone, don't go on the second step)
So after doing that, you should have platform tools and adb drivers installed, I am not going to tell you how to do that exactly but you should find tons of tutorials on the internet for both linux and windows. (I am going to be using Linux in this case but everything is the same for both windows and linux in this case)
Download this file: https://drive.google.com/file/d/13J2zlrUz84ZDSPERdosgNO6xdhwah4hl/view?usp=sharing
and paste it in your mtkclient folder (you should have that by now if you already unlocked the bootloader.)View attachment 5682939
Open the terminal and then type: python mtk w lk lk.bin
View attachment 5682941
Now, power off your phone, hold both volume buttons and until it is done
View attachment 5682943
Check if the phone boots into fastboot by holding volume down and power.
If it shows something like this then congrats, you have fastboot access now.View attachment 5682945
Flashing recovery is very easy now.
Download TWRP image from the TWRP website: https://twrp.me/realme/realme8i.html
Just keep it in the platform tools folder for now.
Boot into your phone, and download the magisk apk from here: https://github.com/topjohnwu/Magisk/releases
After downloading it, download ZArchiver from the Play Store and replace .apk with .zip and save it.
Now power off the phone and boot into fastboot/bootloader.
Open the terminal inside platform tools and:
fastboot flash recovery recovery.img
fastboot reboot recovery
You will be in your custom recovery now .
Now goto install, and select your magisk zip, and flash it normally.
After that is done, reboot to system and rename the magisk zip to apk again and install the apk.
Boom you have also rooted your device .
Thanks to Pritish for bootloader unlock guide and patched lk
Click to expand...
Click to collapse
you can already do this using fastbootd

How to install usbdk in linux? I am using archlinux.

Sidharth09 said:
volume up and power?
Click to expand...
Click to collapse
just power , i tried all vl and pwer
and the battery was 90%

kawsarahmed369 said:
How to install usbdk in linux? I am using archlinux.
Click to expand...
Click to collapse
u dont need those for linux