Develop Bugs

[Guide][M2 8.0] Extract and flash device partitions from official Huawei ROMs

This usually comes up once or twice in most threads, so I thought I'd write a little How-to.
First, grab the ROM you need from one of the Huawei servers. Some ROMs can be found in the dev section here.
Now extract (unzip) the ROM so that you get the UPDATE.APP file. On Windows, I would highly recommend the excellent and free 7-zip program
Now download the Huawei Update Extractor from this XDA thread
Start the Huawei Update Extractor program.
In the Huawei Update Extractor program, select the "Huawei Mediapad M2 8.0 (M2-802L)" profile in the "Profile" combobox (it is the very top dropdown in the tool's UI).
Open the UPDATE.APP you extracted earlier, in the Huawei Update Extractor tool (in the "Update File" area, press the "..." button and browse to the UPDATE.APP file).
{
"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"
}
At this point, it should show a list of the partitions from the UPDATE.APP. Select the partitions you want (you can select as many as you want at a time), then Right-click on the selection (the image below shows a single device partition image selected, "RECOVERY.img", which is the recovery partition image) and choose the "Extract Selected" option in the shortcut menu that appears. Choose a location to save it.
At this point, your selected device partition image(s) are ready for flashing to your device using fastboot.
To flash these using fastboot:
First make sure that you have the Mediapad drivers installed, and adb and fastboot installed and available.
If you're on Windows and need the ADB and fastboot binaries, you can install the "15-second ADB installer" found in this thread.
On Linux, just install the Android Command Line tools from Google.
For the phone drivers, just install HiSuite from Huawei - this will install the Mediapad device drivers. You can then uninstall HiSuite - the drivers will still continue to remain installed even if HiSuite is uninstalled, and this way you won't clutter up your computer with the useless HiSuite.
Enter fastboot mode by either using ADB ("adb reboot bootloader") or by first shutting down the phone and then powering it up while holding down the VOLDN key.
At this point, your phone should in the bootloader screen AKA "fastboot mode".
Now you can use the fastboot commands to flash the respective partitions on the system. Make sure to NOT MIX UP the partition command lines, because it will be bad if for instance you flash the BOOT.img to the recovery partition on the device. To do this, open a terminal ("cmd" on Windows - make sure to open the cmd window inside the directory where your extracted partition image files are present).
Some common fastboot flash commands are below, for the partitions which are most commonly flashed. The commands below assume that your command line terminal is open in the directory where the partition images exist, i.e they are available in the current directory. Otherwise, make sure to specify the full path to the partition image.
Code:
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img

Thank you, unfortunately I'm receiving an error:
PS C:\Users\Ei8ht\Downloads\update> fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (24208 KB)...
OKAY [ 0.507s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.538s
PS C:\Users\Ei8ht\Downloads\update>

beast.in.black said:
This usually comes up once or twice in most threads, so I thought I'd write a little How-to.
First, grab the ROM you need from one of the Huawei servers. Some ROMs can be found in the dev section here.
Now extract (unzip) the ROM so that you get the UPDATE.APP file. On Windows, I would highly recommend the excellent and free 7-zip program
Now download the Huawei Update Extractor from this XDA thread
Start the Huawei Update Extractor program.
In the Huawei Update Extractor program, select the "Huawei Mediapad M2 8.0 (M2-802L)" profile in the "Profile" combobox (it is the very top dropdown in the tool's UI).
Open the UPDATE.APP you extracted earlier, in the Huawei Update Extractor tool (in the "Update File" area, press the "..." button and browse to the UPDATE.APP file).
At this point, it should show a list of the partitions from the UPDATE.APP. Select the partitions you want (you can select as many as you want at a time), then Right-click on the selection (the image below shows a single device partition image selected, "RECOVERY.img", which is the recovery partition image) and choose the "Extract Selected" option in the shortcut menu that appears. Choose a location to save it.
At this point, your selected device partition image(s) are ready for flashing to your device using fastboot.
To flash these using fastboot:
First make sure that you have the Mediapad drivers installed, and adb and fastboot installed and available.
If you're on Windows and need the ADB and fastboot binaries, you can install the "15-second ADB installer" found in this thread.
On Linux, just install the Android Command Line tools from Google.
For the phone drivers, just install HiSuite from Huawei - this will install the Mediapad device drivers. You can then uninstall HiSuite - the drivers will still continue to remain installed even if HiSuite is uninstalled, and this way you won't clutter up your computer with the useless HiSuite.
Enter fastboot mode by either using ADB ("adb reboot bootloader") or by first shutting down the phone and then powering it up while holding down the VOLDN key.
At this point, your phone should in the bootloader screen AKA "fastboot mode".
Now you can use the fastboot commands to flash the respective partitions on the system. Make sure to NOT MIX UP the partition command lines, because it will be bad if for instance you flash the BOOT.img to the recovery partition on the device. To do this, open a terminal ("cmd" on Windows - make sure to open the cmd window inside the directory where your extracted partition image files are present).
Some common fastboot flash commands are below, for the partitions which are most commonly flashed. The commands below assume that your command line terminal is open in the directory where the partition images exist, i.e they are available in the current directory. Otherwise, make sure to specify the full path to the partition image.
Code:
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
Click to expand...
Click to collapse
I'm receveing this error
ERROR: remote (partition lenght get error)

itzmeandyos said:
I'm receveing this error
ERROR: remote (partition lenght get error)
Click to expand...
Click to collapse
Wow, it's been a while and lot of stuff has happened since I made the OP - in fact, I haven't used my M2 in years now.
Since you didn't give me much details about what you did and at what step you get the error, I will assume that you meant that you get this error at the "fastboot flash" stage for one of the partition images. This would mean that the ".img" you are trying to flash is probably not the correct one, so there must have been some error in either the choice of ROM or the image extraction process.
Please double-check and make sure that you are using an appropriate/correct source ROM for the device which you have, and that there were no errors in extracting the relevant partition images, and that you are trying to flash the correct image to the correct partition. Mixing any of this up WILL lead to a brick if the flash succeeds, so the system is protecting you from making a mistake.
If you are sure that you did all the steps correctly but are still getting this error, I do not know how to help.

beast.in.black said:
Wow, it's been a while and lot of stuff has happened since I made the OP - in fact, I haven't used my M2 in years now.
Since you didn't give me much details about what you did and at what step you get the error, I will assume that you meant that you get this error at the "fastboot flash" stage for one of the partition images. This would mean that the ".img" you are trying to flash is probably not the correct one, so there must have been some error in either the choice of ROM or the image extraction process.
Please double-check and make sure that you are using an appropriate/correct source ROM for the device which you have, and that there were no errors in extracting the relevant partition images, and that you are trying to flash the correct image to the correct partition. Mixing any of this up WILL lead to a brick if the flash succeeds, so the system is protecting you from making a mistake.
If you are sure that you did all the steps correctly but are still getting this error, I do not know how to help.
Click to expand...
Click to collapse
Sorry, the question was not so detailed, I'm tryna flash twrp to my P40 Lite E via the Android Bootloader Interface after doing tespoint procedure. Now comes the problem, I have tried the newest twrp for Kirin SoC ( downloaded from twrp official site) but it wont flash on Recovery and Ramdisk partition. There goes the Error.
Hope I was more detailed this time!

itzmeandyos said:
Sorry, the question was not so detailed, I'm tryna flash twrp to my P40 Lite E via the Android Bootloader Interface after doing tespoint procedure. Now comes the problem, I have tried the newest twrp for Kirin SoC ( downloaded from twrp official site) but it wont flash on Recovery and Ramdisk partition. There goes the Error.
Hope I was more detailed this time!
Click to expand...
Click to collapse
Ah I see. This thread was about flashing partitions extracted from Offical ROMs for the Huawei M2-802L. I think there are other tutorials for TWRP flash, which AFAIK requires an unlocked bootloader and so therefore is not possible on newer Huawei phones for the past few years.
Also, I checked the TWRP devices list for Huawei, and your P40 Lite E is NOT listed there. So the fact that you are not able to flash the image is likely the right thing to do because otherwise you would brick your device

I can semi-unlock the bootloaded, that means if I can find a twrp image for my p40 lite e I can root my phone

[GUIDE]*How to install a Generic System Image (GSI) on your HTC U12+

Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (WARNING : According to 5m4r7ph0n36uru, you can't flash vbmeta via fastboot if your device isn't S-OFF, you have to use TWRP, but I don't know how, so ask someone who knows! I will update my tutorial once I see instructions.)
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!

Romano2K said:
Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification"
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!
Click to expand...
Click to collapse
Hello, which GSI did you tried from the list? If you tried more then one, which is the one that runs better?
Thank you

Hi!
I have tried AOSP 10.0 v206 system-quack-arm64-ab-gapps.img. v208 is out now.
I still have to try others.
Let us know if you find one working better than others!

i have problem with this line fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
My fastboot say C:\adb\fastboot.exe: unknown option -- disable-verity How to fix this?
Edit: My htc is dead, power button dont work, does not respond to the charger and PC.

mientus25 said:
i have problem with this line fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
My fastboot say C:\adb\fastboot.exe: unknown option -- disable-verity How to fix this?
Edit: My htc is dead, power button dont work, does not respond to the charger and PC.
Click to expand...
Click to collapse
Hi mientus25! I'm sorry if you bricked your smartphone trying to flash it. I think the --disable-verity option not working was a matter of platform tools (adb) version.

My htc have actually hard brick. I will try to send it to the service(warranty). Will tell you what comes of it.

fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification doesn't working
it says: not allowed in production device
bootloader:unlocked

xreeman said:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification doesn't working
it says: not allowed in production device
bootloader:unlocked
Click to expand...
Click to collapse
If on 2.55.401.1 try flashing this vbmeta. It already has verity and verification disabled, pulled from an S-OFF device allowing the above flashing commands. It flashed fine on my U12+ and I've been able to boot PE 10 GSI afterwards without any problems.
@Romano2K feel free to add it to the OP.

5m4r7ph0n36uru said:
If on 2.55.401.1 try flashing this vbmeta. It already has verity and verification disabled, pulled from an S-OFF device allowing the above flashing commands. It flashed fine on my U12+ and I've been able to boot PE 10 GSI afterwards without any problems.
@Romano2K feel free to add it to the OP.
Click to expand...
Click to collapse
Hello, can I may ask you if I can send you a PM? I have an HTC u12+ and I would like to install and Android 10 GSI and I would like a step by step help to do it. Can you please also tell me which bugs are you facing with it? Thank you very much

GaetanoS.89 said:
Hello, can I may ask you if I can send you a PM? I have an HTC u12+ and I would like to install and Android 10 GSI and I would like a step by step help to do it. Can you please also tell me which bugs are you facing with it? Thank you very much
Click to expand...
Click to collapse
No help by PM. I cannot do this for professional reasons. And also for personal reasons not to give individual support.

5m4r7ph0n36uru said:
No help by PM. I cannot do this for professional reasons. And also for personal reasons not to give individual support.
Click to expand...
Click to collapse
All right, would you please write a message over with all the steps here? Thank you

GaetanoS.89 said:
All right, would you please write a message over with all the steps here? Thank you
Click to expand...
Click to collapse
Starting from a Stock ROM, Bootloader Unlocked, I took the following steps to flash and boot an Android 10 GSI to my HTC U12+:
Go to Settings > System and perform a factory reset
Reboot in the Bootloader by
Code:
adb reboot bootloader
Delete the system and data partition by
Code:
fastboot erase data
and
Code:
fastboot erase system
Flash the nonverity vbmeta image via
Code:
fastboot flash vbmeta nameofvbmeta.img
(the vbmeta image must be in the fastboot folder on your computer)
Flash the GSI via
Code:
fastboot flasch system nameofgsi.img
(the GSI must be in the fastboot folder on your computer)
Reboots the HTC U12+ into Download Mode and perform another Factory Reset
Reboot and enjoy
If /data still can't be read, do another Factory Reset from settings menu

https://www.xda-developers.com/goog...al&utm_source=twitter.com&utm_campaign=buffer
Wiil this work with the U12+???

It may work for GSIs with a fixed verity status. Thus it doesn't work for some Android 10 GSIs without flashing a noverity vbmeta as. Thus I decided long ago, to never recommend such tools, and not to help people who used one, as those using such tools most of the time didn't even care learn the basics of adb and fastboot. I can't remember anyone, who used a tool, who's ever been fully capable to identify potential problems and errors, let alone how to solve them. And the latter is the baseline to start modding a device.
Sent from my Pixel 4 XL using XDA Labs

5m4r7ph0n36uru said:
Starting from a Stock ROM, Bootloader Unlocked, I took the following steps to flash and boot an Android 10 GSI to my HTC U12+:
Go to Settings > System and perform a factory reset
Reboot in the Bootloader by
Delete the system and data partition by and
Flash the nonverity vbmeta image via (the vbmeta image must be in the fastboot folder on your computer)
Flash the GSI via (the GSI must be in the fastboot folder on your computer)
Reboots the HTC U12+ into Download Mode and perform another Factory Reset
Reboot and enjoy
If /data still can't be read, do another Factory Reset from settings menu
Click to expand...
Click to collapse
Hello,
I have unlocked the bootloader yesterday, and I was having a look to your steps, and I noticed you are not using TWRP. Are you doing everything by CMD right?

Romano2K said:
Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification"
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!
Click to expand...
Click to collapse
Hello I am trying to follow all the steps on the guode, but when I have to flash the vbmeta file from Bootloader Mode I am getting this:
C:\Users\User\Desktop\ADB2>fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Not allowed on PRODUCTION device')
fastboot: error: Command failed
If I try to install the vbmeta from Download Mode I am getting this error

GaetanoS.89 said:
Hello,
I have unlocked the bootloader yesterday, and I was having a look to your steps, and I noticed you are not using TWRP. Are you doing everything by CMD right?
Click to expand...
Click to collapse
Yes I'm doing everything from CMD indeed. Always do so, as long as it is possible.
@Romano2K vbmeta can't be flashed via fastboot on S-On/production devices. It has to be flashed as update.zip from TWRP. It should be mentioned anywhere.

5m4r7ph0n36uru said:
Yes I'm doing everything from CMD indeed. Always do so, as long as it is possible.
@Romano2K vbmeta can't be flashed via fastboot on S-On/production devices. It has to be flashed as update.zip from TWRP. It should be mentioned anywhere.
Click to expand...
Click to collapse
So how do I have to proceed??
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
And after?

GaetanoS.89 said:
So how do I have to proceed??
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
And after?
Click to expand...
Click to collapse
Which software version are you running!?
Sent from my Pixel 4 XL using XDA Labs

5m4r7ph0n36uru said:
Which software version are you running!?
Click to expand...
Click to collapse
I was running Android 9 stock. After a few trials I have been able to install and boot the Pixel Experience and the permessiver and everything seems to work without flashing the vbmeta file

Question Bricked OP9pro

Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...

danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
What did you do to try to patch it? Why are you in adb? Does fastboot work?

craznazn said:
What did you do to try to patch it? Why are you in adb? Does fastboot work?
Click to expand...
Click to collapse
Patched the boot.img using magisk and then flashed it. After patching, it totally cant boot and can only boot to bootloader.
tried alot of version of MSMtool and it will always fail with param preload error...
Then tried manually recover via extracting the payload using python then using adbtools to wipe and flash but it will also fail because some img files are unable to flash over to the phone...
Any other solutions?

U not able to flash boot the stock boot.img?

i am able to flash the stock boot.img to the phone but some critical img files will come out with
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed

You need to be in fastbootd,
Code:
fastboot reboot fastboot

craznazn said:
You need to be in fastbootd,
Code:
fastboot reboot fastbootd
Click to expand...
Click to collapse
Nope not working too...
{
"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"
}

danjcxie said:
Nope not working too...
View attachment 5281163
Click to expand...
Click to collapse
Sorry, fastboot reboot fastboot (without the d)

@danjcxie
To be honest, I would download the rom and boot with the recovery image instead, I'll upload the image collection...
Will post a link here once it's up.
Actually, just noticed there isn't a recovery image, so boot to the default boot.img using fastboot, then see if the storage shows on your computer, copy the latest default rom over to the main storage folder then then go into Settings > System > System Updates and use the cog to do a local update using the rom zip.
That should re-install everything back to default, you might get lucky and still have all your data
My collection is for the Europe build FYI:
OP9P_Image_Collection_BA_11.2.3.3.zip | by djsubterrain for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
MD5 : 00227014483b4913a2624fac6f492434
So you would reboot the phone into fastboot mode by holding vol up during boot
Once you are in fastboot mode connect the phone to your computer
Test that the computer can see it properly using fastboot devices
You should see a number returned, if so then your computer is recognising the phone, if you don't then try installing the latest drivers from here
If fastboot can see the device properly then copy the default boot.img to the same folder as your fastboot.exe and type the following :
fastboot boot boot.img
You should see a message saying it's transferring it to the phone, then it should boot the phone using it, it's slower than a normal boot but, if everything else on the phone is ok, then you should see it booted and it should accept your lock method
Once you get into the phone using that boot.img, try connecting the phone to your computer and see if it's recognised, if it is then copy over the latest stock rom to your main storage folder, then go to Settings > System > System Updates and use the cog to do a local update using the rom zip
I'm guessing it should let you because it will see a difference between your boot image and the one from the rom.

MSM tool for LE2125 - 11.2.2.2.LE15AA
User Type of Others for login MSM Tool for LE2125 - 11.2.2.2.LE15AA Drivers Mirrors: (provided by @djsubterrain) MSM Tool : https://sourceforge.net/projects/djsubterrain/files/OnePlus 9 Pro/OP9P_MSM_Tool.zip/download MD5 ...
forum.xda-developers.com

New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off

danjcxie said:
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
View attachment 5281971
Click to expand...
Click to collapse
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
#To reboot your device
fastboot reboot
#To reboot your device to fastboot mode
fastboot reboot-bootloader
Click to expand...
Click to collapse

djsubterrain said:
Turn it off and try charging it
Click to expand...
Click to collapse
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign

danjcxie said:
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
Click to expand...
Click to collapse
Yeah that symbol isn't what I get, I get a blue lightning sign with the percentage underneath. Are you running OxygenOS or ColorOS?
I think it might be time for you to contact OnePlus support

djsubterrain said:
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
Click to expand...
Click to collapse
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help

craznazn said:
OP
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
Click to expand...
Click to collapse
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?

djsubterrain said:
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
Click to expand...
Click to collapse
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on

craznazn said:
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
Click to expand...
Click to collapse
Go ahead and help the guy solve his problem.
Just remember it's fastboot, not fastbootd.
Now, how do you block people on here again?

danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
use the MSM Tool with the latest drivers
QDLoader HS-USB Driver_64bit_Setup
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
This just worked for me minutes ago
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
i downloaded Indian Variant LE2121 while my phone is LE2120 ant it worked

How To Guide [ROOT] [PSYCHE] Root Xiaomi 12x with Magisk

{
"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"
}
Sources used: link
1. First unlock your bootloader. This thread does not cover this. I suggest you do not try to tamper with the 1week~ time gate you will encounter else it may get longer should you fail.
2. Enable Developer mode and adb from Developer settings again.
3 Download the appropriate Fastboot files for your device . See the About section in your phone's settings to know what you are currently running.
4. Download latest Magisk-vXX.Y.apk and install it on your device. Magisk developer only provides files from Github, do not download it from anywhere else.
5. Extract(Install 7-zip if needed) the fastboot .tgz archive and copy the boot.img from it to your phone's sdcard through adb (or other means):
Code:
adb push psyche_eea_global_images_V13.0.3.0.SLDEUXM/images/boot.img /sdcard/
6. Open up Magisk on your phone, press Install and use the patch option to navigate to the boot.img you just copied. Select that, next next next.
7. Read the output to see where the patched boot.img got saved. Pull that.
Code:
adb pull /sdcard/Download/magisk_patched-24300_D2K9V.img
8. Reboot phone to fastboot.
Code:
adb reboot fastboot
9. Flash the modified boot image
Code:
fastboot flash boot recoveryxy.img
10. Flash dtbo (found inside rom zip)
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. Say your prayers and reboot, your device should now have functional root with Magisk
Code:
fastboot reboot

This did not work for me. Seemingly flashed okay, but phone is now bootlooping.

weggy101 said:
This did not work for me. Seemingly flashed okay, but phone is now bootlooping.
Click to expand...
Click to collapse
im sorry forgot step 10. flash vbmeta image. updated guide.

nofx161 said:
im sorry forgot step 10. flash vbmeta image. updated guide.
Click to expand...
Click to collapse
Still gets stuck in a bootloop. Just for fun I downloaded the tgz archive from another source, same situation.
If anyone else gets stuck, here's how to get out of it:
1) Reboot into RECOVERY mode. Select the option for help. It should show a picture of the phone and a USB cable.
2) Follow the onscreen URL for the MiPhoneAssistant Tool
3) I was not able to download via the tool, so I loaded the image in manually with the 2nd option. For my Chinese phone, it was a ~380 MB ZIP file called V13.0.5.0.SLDCNXM, downloaded from:
https://hugeota.d.miui.com/V13.0.5.0.SLDCNXM/miui-blockota-psyche-V13.0.4.0.SLDCNXM-V13.0.5.0.SLDCNXM-ffe7c45215-12.0.zip
4) After finishing, it just boots up to a black screen. Reboot into FASTBOOT mode.
5) From here you can reflash your ROM and be back in business.

I think it worked here, I patched the boot.img from the EEA ROM I'm running (V13.0.3.0.SLDEUXM_20220528.0000.00_12.0_eea) and the Magisk App says it's installed. The only problem is that I'm not able to edit files and/or paste new ones in the root/system folder.
I'm trying to edit build.prop but it says there's not enough space to complete the operation (using SolidExplorer), I tried to disable my nav buttons with FNG too, but that also won't work.

hey you can use my boot image which is rooted with magisk 25.0
magisk_patched-25000_WA0wW.img
drive.google.com
also the original boot if you messed up
boot.img
drive.google.com

Did anyone solved CTS profile ?

Completed successfully. The steps were really straightforward and easy to execute. The only question I had was about flashing the second slot. These instructions contain the command to flash the active slot only, but the 12x has a and b. I went ahead and flashed the second slot anyway even though it's inactive right now. Also, as was noted in the 12 thread, I was confused why Power-Vol Down boots to "fastboot" while adb reboot fastboot boots to "fastbootd". I don't know, just went with fastbootd and all was fine. Thank you @nofx161 for the instructions.
I haven't really done any testing yet but will report back if I find anything interesting.

bjs339 said:
Completed successfully. The steps were really straightforward and easy to execute. The only question I had was about flashing the second slot. These instructions contain the command to flash the active slot only, but the 12x has a and b. I went ahead and flashed the second slot anyway even though it's inactive right now. Also, as was noted in the 12 thread, I was confused why Power-Vol Down boots to "fastboot" while adb reboot fastboot boots to "fastbootd". I don't know, just went with fastbootd and all was fine. Thank you @nofx161 for the instructions.
I haven't really done any testing yet but will report back if I find anything interesting.
Click to expand...
Click to collapse
What ROM do you use? Stock or xiaomi EU or which one? Which modules have you tried? Thanks!

I'm on the stock rom and really haven't done much with it yet, so not much to report at this point.

An alternative way for installing magisk is to install twrp ( https://forum.xda-developers.com/t/shared-recovery-psyche-twrp-by-skkk.4461461/ ) and then choose "install twrp" from the advanced menu in twrp. Then restart system and tap on the magisk button. The magisk manager will be loaded from web and your good to go with root.

shortek said:
Did anyone solved CTS profile ?
Click to expand...
Click to collapse
Working on it. I've followed the instructions here: https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/ except that I'm using the Shamiko magisk module instead of the Magisk Deny List per guidance here: https://forum.xda-developers.com/t/chase-app-always-detects-root.4099627/page-9. I have two banking apps working, but not Chase and can't add a credit card to my Google Wallet yet. I tested with YASNAC and it says it passes Safety Net, so we'll see if I can get it figured out. It sounds like the Chase app is a constant struggle, and I'm not too concerned about that, but I'd really like to be able to use Google Pay.

bjs339 said:
Working on it. I've followed the instructions here: https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/ except that I'm using the Shamiko magisk module instead of the Magisk Deny List per guidance here: https://forum.xda-developers.com/t/chase-app-always-detects-root.4099627/page-9. I have two banking apps working, but not Chase and can't add a credit card to my Google Wallet yet. I tested with YASNAC and it says it passes Safety Net, so we'll see if I can get it figured out. It sounds like the Chase app is a constant struggle, and I'm not too concerned about that, but I'd really like to be able to use Google Pay.
Click to expand...
Click to collapse
Got it! This Safety Net mod fixed Google Pay: https://forum.xda-developers.com/t/...tynet-fix-2-3-1.4217823/page-91#post-87198517

bjs339 said:
Got it! This Safety Net mod fixed Google Pay: https://forum.xda-developers.com/t/...tynet-fix-2-3-1.4217823/page-91#post-87198517
Click to expand...
Click to collapse
Do you have Widevine Level 1 with this method? So we could use streaming services on high quality while being rooted. (can be checked by app DRM info).

HikL said:
Do you have Widevine Level 1 with this method? So we could use streaming services on high quality while being rooted. (can be checked by app DRM info).
Click to expand...
Click to collapse
Looks like it if I'm reading that right.

bjs339 said:
View attachment 5699583
Looks like it if I'm reading that right.
Click to expand...
Click to collapse
Great news! Thank you!

Hello. Please help me. I did everything as in instructions except one thing and it reboots in MIUI Recovery 5.0 as in this photo https://prnt.sc/Oyjs9lxGVFX8 (not my photo). The only thing that I didn't follow is instead of installing my current MIUI version official boot.img which updated tonight 13.04 Global, I used 13.02 Global because I couldn't find fastboot version of 13.04.
edit: now it started just constant bootloop without going into recovery mode, they just uploaded 13.04 fastboot version and I'm downloading it in with high hopes. I hope that if I patch the boot.img with Magisk in emulation on PC nothing bad will happen.
edit2: Sadly I was unable to do it with PC emulator, I'd appreciate if anyone patched it for me, attached file.
boot.img
drive.google.com

kiknalex said:
Hello. Please help me. I did everything as in instructions except one thing and it reboots in MIUI Recovery 5.0 as in this photo https://prnt.sc/Oyjs9lxGVFX8 (not my photo). The only thing that I didn't follow is instead of installing my current MIUI version official boot.img which updated tonight 13.04 Global, I used 13.02 Global because I couldn't find fastboot version of 13.04.
edit: now it started just constant bootloop without going into recovery mode, they just uploaded 13.04 fastboot version and I'm downloading it in with high hopes. I hope that if I patch the boot.img with Magisk in emulation on PC nothing bad will happen.
edit2: Sadly I was unable to do it with PC emulator, I'd appreciate if anyone patched it for me, attached file.
Click to expand...
Click to collapse
I patched boot.img with another phone (huawei or smth) repeated all steps and now it's just stuck in fastboot bootloop...
I tried this
Still gets stuck in a bootloop. Just for fun I downloaded the tgz archive from another source, same situation.
If anyone else gets stuck, here's how to get out of it:
1) Reboot into RECOVERY mode. Select the option for help. It should show a picture of the phone and a USB cable.
2) Follow the onscreen URL for the MiPhoneAssistant Tool
3) I was not able to download via the tool, so I loaded the image in manually with the 2nd option. For my Chinese phone, it was a ~380 MB ZIP file called V13.0.5.0.SLDCNXM, downloaded from:
https://hugeota.d.miui.com/V13.0.5....SLDCNXM-V13.0.5.0.SLDCNXM-ffe7c45215-12.0.zip
4) After finishing, it just boots up to a black screen. Reboot into FASTBOOT mode.
5) From here you can reflash your ROM and be back in business.
But my Mi PC Suite doesn't detect phone when I plug cable, although the icon on phone shows that it's plugged in. Please help me...
Edit: issue was fixed in this thread
Please Help Me. Xiaomi 12x. Bricked Phone after trying to root. Stuck in fastboot bootloop.
Hello. I've followed instructions as in this thread https://forum.xda-developers.com/t/root-psyche-root-xiaomi-12x-with-magisk.4455293/ only 1 thing I did wrong is downloading 13.02 boot.img file instead of 13.04 boot.img which wasn't available...
forum.xda-developers.com

Hmmm.... First I would reflash the 13.0.4.0 boot.img to both slots using fastboot.
Copy boot.img to fastboot folder and type
"fastboot flash boot_a boot.img" and then "fastboot flash boot_b boot.img". Now it should boot again. Then you can patch your boot.img and flash it: Copy the patched boot.img to fastboot folder "fastboot flash boot patched_boot.img". Alternatively you can flash magisk via twrp. Therefore download twrp (search our thread), rename the file to twrp.img, copy the twrp.img to fastboot folder, boot the img with "fastboot boot twrp.img" and after twrp is booted go to advanced and tip "flash current twrp" now you have twrp installed. Now you can download the magisk.apk from github, copy it to your internal storage via your pc and flash it via twrp... Violla

Voodoojonny said:
Hmmm.... First I would reflash the 13.0.4.0 boot.img to both slots using fastboot.
Copy boot.img to fastboot folder and type
"fastboot flash boot_a boot.img" and then "fastboot flash boot_b boot.img". Now it should boot again. Then you can patch your boot.img and flash it: Copy the patched boot.img to fastboot folder "fastboot flash boot patched_boot.img". Alternatively you can flash magisk via twrp. Therefore download twrp (search our thread), rename the file to twrp.img, copy the twrp.img to fastboot folder, boot the img with "fastboot boot twrp.img" and after twrp is booted go to advanced and tip "flash current twrp" now you have twrp installed. Now you can download the magisk.apk from github, copy it to your internal storage via your pc and flash it via twrp... Violla
Click to expand...
Click to collapse
Thank you for your answer. I already fixed issue in another thread, will edit my comment.

Oppo A83 [CPH1729] TWRP RECOVERY

⚠Warning: This is not official TWRP, use it at your own risk!!!
Data will be erased. Back up if neccessary
This device is kind of weird so to flash twrp you need these things:
1. Prepare materials​
Install driver so as to have access to preloader (Just install automatically and no need to do anything in device manager)
This software to access to preloader -> fastboot (fastboot is somehow not available via adb methods) Enter fastboot
This tool for flashing
2. Unlock bootloader (need testpoint, python, git (optional) - you can search on google)​
Use this tool - go to this section. Follow guides to unlock bootloader (remember to use testpoint not hardware buttons)
3. Enter fastboot mode​
Use latest MTK META Ultility tool
Select Reboot Fastboot Mode in BRom section
Hold volume down button. While holding connect it to your computer
*Now your phone is in fastboot mode​4. Flash​
Open platform-tools folder in Downloads folder
Shift + Right click then "open command window here"
Input these commands into cmd
fastboot flash boot drag twrp file to cmd
fastboot flash recovery drag twrp file to cmd.
fastboot reboot. Swipe to allow modification in twrp (to make sure that stockboot wont replace twrp). After that reboot to recovery to make it installed on your device permanently.
Now your recovery is ready to flash file you can push stock image file to your root folder using adb command: "adb push. Drag the stock image file. /" (Because Decryption right now doesnt work on my device yet)
Enjoy
*Sounds crazy but it is required to make sure twrp is installed correctly​*If successful, when you power on, you will get a red section on top of your device. If you want to recover to stock recovery, flash the recovery.img below.​*Also, if you want to make your own twrp, you can try recovery.img below.​
Also thanks SebaUbuntu and Mofadal El-Tayeb (مُفَضَّل) for awesome apps
​
​​
​

Here is the PBRB version for this device

Hey I'm stuck in the third step.can you please help me?

Sorry for late reply. What problems do you have?

Is this the stock boot image you provided?

SAMIUL ISLAM 0 said:
Is this the stock boot image you provided?
Click to expand...
Click to collapse
Yes it is. I took it from OTA update

Hey friends
I want to upgrade my oppo a 83 fone to a costum rom to upgrade my androide to android 8 or higher

mahmoud2503 said:
Hey friends
I want to upgrade my oppo a 83 fone to a costum rom to upgrade my androide to android 8 or higher
Click to expand...
Click to collapse
Unfortunately, I have no custom roms available for this phone (