Database Develop

boot menu not coming

Hi friends,
I am using honor 5c NEM-L22 lastest Android version
I am trying to unlock the bootloader and install a twrp
The bootloader is unlocked
But the twrp is not installed
After i am trying different method but no use
After I am facing one problem
I am trying to open the boot mean but the boot mean is not opening
Please give a correct solution

Try this: reboot to fastboot mode and check that theres a green text saying: Phone Unlocked. Then on your PC in CMD navigate to platform-tools and make sure the IMG file you are flashing is there. Now type this command: fastboot flash recovery name.img then wait until it finishes. Now type fastboot reboot and bootto EMUI. Now shut down the phone and press power+volup until it vibrates, release power and keep holding volup until screen turns on. Should boot to TWRP. OR IF YOU MEANT THAT WARNING ABOUT THE BOOTLOADER BEEN UNLOCKED: I don't think its important as it doesn't let you start TWRP, just eRecovery which is a secondary recovery. Tho its still odd you don't see that warning.

Kumar.K said:
Hi friends,
I am using honor 5c NEM-L22 lastest Android version
I am trying to unlock the bootloader and install a twrp
The bootloader is unlocked
But the twrp is not installed
After i am trying different method but no use
After I am facing one problem
I am trying to open the boot mean but the boot mean is not opening
Please give a correct solution
Click to expand...
Click to collapse
Flash the correct twrp. You will get in 5c repository in my signature.

Kumar.K said:
Hi friends,
I am using honor 5c NEM-L22 lastest Android version
I am trying to unlock the bootloader and install a twrp
The bootloader is unlocked
But the twrp is not installed
After i am trying different method but no use
After I am facing one problem
I am trying to open the boot mean but the boot mean is not opening
Please give a correct solution
Click to expand...
Click to collapse
What do you mean boot menu? The power menu?

Kumar.K said:
Hi friends,
I am using honor 5c NEM-L22 lastest Android version
I am trying to unlock the bootloader and install a twrp
The bootloader is unlocked
But the twrp is not installed
After i am trying different method but no use
After I am facing one problem
I am trying to open the boot mean but the boot mean is not opening
Please give a correct solution
Click to expand...
Click to collapse
FRP status?
Are you flashing the correct file?

How many people bricked their phone while Rebranding/OTA and what solutions used ?

How many people bricked specifically hardbricked their phone after 2018-04-16 updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if they see we are bunch of people.
Edit: Just comment only if you solved the issue with this tool or any other tool that is not mentioned,here we are seeking help.

reza6d said:
How many people bricked specifically hardbricked their phone after 2018-04-16 noxloader updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if the ysee we are bunch of people.
Click to expand...
Click to collapse
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.

ante0 said:
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.
Click to expand...
Click to collapse
maybe i recall wrong but after first time seeing these noxloaders,somethings changed,anyway i edited the post.thanks.

My BLA-L29 is still on the black screen and I can not even revert to DC-Phoenix. After upgrading to 138.

Used funky

mikaole said:
Used funky
Click to expand...
Click to collapse
i think your phone was in fastboot or bootloop,we are talking about hardbrick bro,black screen not even charge led in our devices.

I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.

Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know

durc12 said:
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know
Click to expand...
Click to collapse
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions

Carnage! said:
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions
Click to expand...
Click to collapse
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.

Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
I see. I only tried flashing the recovery_ramdisk and system.img. I will try it later and I will let you know if it worked.

Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS

durc12 said:
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS
Click to expand...
Click to collapse
No, first he has to recover the current OS, and my advise was only for that.
Then he will need to use a TWRP + NoCheck combo, to get back to Oreo.
HuRUpdater can't get you back to Oreo so you guys should stop using that with Pie.

Mate 10 Pro BLA-L09
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.

diowil4 said:
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.
Click to expand...
Click to collapse
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?

Pretoriano80 said:
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?
Click to expand...
Click to collapse
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK

diowil4 said:
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
Click to expand...
Click to collapse
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.

Pretoriano80 said:
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.
Click to expand...
Click to collapse
After flashing It cannot boot to recovery.

diowil4 said:
After flashing It cannot boot to recovery.
Click to expand...
Click to collapse
So you can only boot to fastboot, no matter what?

Pretoriano80 said:
So you can only boot to fastboot, no matter what?
Click to expand...
Click to collapse
Yes.

(Help) My P8 Lite 2017 (PRA-LX1) is bricked

Hello,
I was trying to install a custom ROM from TWRP to my P8 Lite 2017 and I wiped all partitions except MicroSD.
The installation failed and I got the stock ROM and then I discovered that my bootloader is locked. I can access TWRP and when I flashed the stock ROM the phone just boots to TWRP Recovery. And I can't even unlock the bootloader because the phone doesn‘t have any OS and I can‘t enable OEM unlocking from the system settings. And because I have TWRP, I can’t access Huawei Recovery. So my phone is basically bricked.
Any help will be appreciated

luigifan3 said:
Hello,
I was trying to install a custom ROM from TWRP to my P8 Lite 2017 and I wiped all partitions except MicroSD.
The installation failed and I got the stock ROM and then I discovered that my bootloader is locked. I can access TWRP and when I flashed the stock ROM the phone just boots to TWRP Recovery. And I can't even unlock the bootloader because the phone doesn‘t have any OS and I can‘t enable OEM unlocking from the system settings. And because I have TWRP, I can’t access Huawei Recovery. So my phone is basically bricked.
Any help will be appreciated
Click to expand...
Click to collapse
Use dload with a service firmware.
You need to flash this 2 times,once for the firmware and second time for vendor,and the firmware UPDATE.APP can be found in the update_sd.zip and the vendor UPDATE.APP can be found in the PRA-L31 or PRA-L11 folders (most likely you will have PRA-L31,you can find this in the engineering menu by going into the dialer and typing this: *#*#2846579#*#*,and then going to Veneer Informations and Version Info,but since you cannot boot flash PRA-L31 vendor).
http://androidhost.ru/6uc - this is latest firmware,but takes a very very long time to download
https://mega.nz/#F!nwhAWDjC!cNovAN6dKLlO_YZ9fjMbzQ - this is the first official firmware released,but download speed is very good
If you don't know how to use dload you can look it up on forums.

If your phone is really hard bricked and can't do anything, check this out:

I know how to use dload, but how I can boot into dload mode with TWRP installed and bootloader locked?

luigifan3 said:
I know how to use dload, but how I can boot into dload mode with TWRP installed and bootloader locked?
Click to expand...
Click to collapse
Dload works no matter what,at least I was able to enter it when I bricked my phone,even when I completely screwed up my recovery partition,so you should be good. Try using it with the service firmware I left you.

dinoderda said:
Dload works no matter what,at least I was able to enter it when I bricked my phone,even when I completely screwed up my recovery partition,so you should be good. Try using it with the service firmware I left you.
Click to expand...
Click to collapse
Now I have downloaded the service firmware so how I am going to flash it now? Like do I extract the UPDATE.APP and flash it in TWRP or what? You said that flash UPDATE.APP, but am I going to do that in dload mode or TWRP?

luigifan3 said:
Now I have downloaded the service firmware so how I am going to flash it now? Like do I extract the UPDATE.APP and flash it in TWRP or what? You said that flash UPDATE.APP, but am I going to do that in dload mode or TWRP?
Click to expand...
Click to collapse
In dload,make sure you make a folder in the root of your sdcard called dload and put that in there.

dinoderda said:
In dload,make sure you make a folder in the root of your sdcard called dload and put that in there.
Click to expand...
Click to collapse
Now I have the UPDATE.APP in my dload folder, but how I boot to the dload mode now?

luigifan3 said:
Now I have the UPDATE.APP in my dload folder, but how I boot to the dload mode now?
Click to expand...
Click to collapse
Volume Up + Volume Down + Power Button.

dinoderda said:
Volume Up + Volume Down + Power Button.
Click to expand...
Click to collapse
I tried that, it just boots into TWRP
EDIT: I got to dload, but it says software installation failed

luigifan3 said:
I tried that, it just boots into TWRP
EDIT: I got to dload, but it says software installation failed
Click to expand...
Click to collapse
Hm,make sure you used the service firmware I left you,but if you are sure you did,your last resort is DC Phoenix which you will need to pay 20 euros.

luigifan3 said:
Hello,
I was trying to install a custom ROM from TWRP to my P8 Lite 2017 and I wiped all partitions except MicroSD.
The installation failed and I got the stock ROM and then I discovered that my bootloader is locked. I can access TWRP and when I flashed the stock ROM the phone just boots to TWRP Recovery. And I can't even unlock the bootloader because the phone doesn‘t have any OS and I can‘t enable OEM unlocking from the system settings. And because I have TWRP, I can’t access Huawei Recovery. So my phone is basically bricked.
Any help will be appreciated
Click to expand...
Click to collapse
if you have TWRP installed could you make a backup of your oeminfo partition so we could provide you the right firmware to recover your device

RAR1991 said:
if you have TWRP installed could you make a backup of your oeminfo partition so we could provide you the right firmware to recover your device
Click to expand...
Click to collapse
Ok, but does it provide the right info if I have flashed different oeminfo.img?

dinoderda said:
Hm,make sure you used the service firmware I left you,but if you are sure you did,your last resort is DC Phoenix which you will need to pay 20 euros.
Click to expand...
Click to collapse
I've tried a different firmware for my device and now I can't get to dload anymore so does it mean that I've chosen the wrong firmware? And by the way I read somewhere that if the dload says error it can depend on the microsd card.

I tried it again with the service firmware and I got to dload and it didn't have error anymore and now I've got everything worked and my phone is unbricked

luigifan3 said:
I tried it again with the service firmware and I got to dload and it didn't have error anymore and now I've got everything worked and my phone is unbricked
Click to expand...
Click to collapse
great

I was stuck with a similar problem. Device bricked and flashing TWRP and restoring backups, then stock recovery and stock roms, but nothing worked until I found this post. Thanks a lot dinoderda for your help.

dinoderda said:
Use dload with a service firmware.
You need to flash this 2 times,once for the firmware and second time for vendor,and the firmware UPDATE.APP can be found in the update_sd.zip and the vendor UPDATE.APP can be found in the PRA-L31 or PRA-L11 folders (most likely you will have PRA-L31,you can find this in the engineering menu by going into the dialer and typing this: *#*#2846579#*#*,and then going to Veneer Informations and Version Info,but since you cannot boot flash PRA-L31 vendor).
http://androidhost.ru/6uc - this is latest firmware,but takes a very very long time to download
https://mega.nz/#F!nwhAWDjC!cNovAN6dKLlO_YZ9fjMbzQ - this is the first official firmware released,but download speed is very good
If you don't know how to use dload you can look it up on forums.
Click to expand...
Click to collapse
Hello again, I've been using the older service firmware for few months now and now I decided to install the latest service firmware after I had no success with flashing the firmware through TWRP and I downloaded the service firmware put the necessary files to the dload folder and installed it via the software update in the dialer and typing *#*#2846579#*#* and going to dload that way. It installed to 100% and then when it restarted it goes to Error Mode and it says to update the firmware again but it just loops to error mode and I cannot do anything so I think I accidentally removed some neccessary files in the dload folder but now I would need to fix the error mode loop.

Can't boot to twrp

Device: eva-l09
Software: EMUI 5, Android 7.0
Kernel: 4.1.18-gd97adb9
Build: EVA-L09C432B386
I flashed the newest twrp and when I reboot the device to recovery it hangs on the "device is booting" screen and it freezes.
I tried flashing twrp to recovery2 too but that did not help (I can't even boot back to huawei's eRecovery).
I can't update with OTA because it gets softbricked if I do.
Please help.

Have you unlocked the bootloader?

Kr3Ep said:
Device: eva-l09
Software: EMUI 5, Android 7.0
Kernel: 4.1.18-gd97adb9
Build: EVA-L09C432B386
I flashed the newest twrp and when I reboot the device to recovery it hangs on the "device is booting" screen and it freezes.
I tried flashing twrp to recovery2 too but that did not help (I can't even boot back to huawei's eRecovery).
I can't update with OTA because it gets softbricked if I do.
Please help.
Click to expand...
Click to collapse
What does it mean 'newest TWRP' - are you flashing the proper TWRP as ported to Huawei P9 Nougat?
Find the 'newest' in this post:
https://forum.xda-developers.com/showpost.php?p=75787111&postcount=1
With the wrong TWRP (not supporting encryption etc), you may brick the phone

rupiec/ said:
Have you unlocked the bootloader?
Click to expand...
Click to collapse
I did

zgfg said:
What does it mean 'newest TWRP' - are you flashing the proper TWRP as ported to Huawei P9 Nougat?
Find the 'newest' in this post:
https://forum.xda-developers.com/showpost.php?p=75787111&postcount=1
With the wrong TWRP (not supporting encryption etc), you may brick the phone
Click to expand...
Click to collapse
I flashed this one. It's weird because I can still access Huawei's recovery. Isn't it supposed to overwrite it?

Kr3Ep said:
I flashed this one. It's weird because I can still access Huawei's recovery. Isn't it supposed to overwrite it?
Click to expand...
Click to collapse
Do you know the trick that you must, and how, to boot to TWRP immediately after flashing, otherwise you loose TWRP
https://forum.xda-developers.com/p9...rainbow-v4-t3759292/post77622126#post77622126

zgfg said:
Do you know the trick that you must, and how, to boot to TWRP immediately after flashing, otherwise you loose TWRP
https://forum.xda-developers.com/p9...rainbow-v4-t3759292/post77622126#post77622126
Click to expand...
Click to collapse
Thank you but it got solved by the correct twrp. Thought that the latest zip on twrp's official site would be the correct one, but no.

zgfg said:
What does it mean 'newest TWRP' - are you flashing the proper TWRP as ported to Huawei P9 Nougat?
Find the 'newest' in this post:
https://forum.xda-developers.com/showpost.php?p=75787111&postcount=1
With the wrong TWRP (not supporting encryption etc), you may brick the phone
Click to expand...
Click to collapse
Thanks, it worked. How can it be that the zip on the official twrp site doesn't work?

Kr3Ep said:
Thanks, it worked. How can it be that the zip on the official twrp site doesn't work?
Click to expand...
Click to collapse
There are different TWRPs for Huawei for Android 6, 7 and 8
Who knows what they have
there (maybe for M), but search on XDA to find what and how will work (eg, there is also TWRP for O but not supporting encryption/decryption, hence unable to access Data partition and Internal mem)

zgfg said:
There are different TWRPs for Huawei for Android 6, 7 and 8
Who knows what they have
there (maybe for M), but search on XDA to find what and how will work (eg, there is also TWRP for O but not supporting encryption/decryption, hence unable to access Data partition and Internal mem)
Click to expand...
Click to collapse
Ohh thanks!

Anyone successfully root Magisk with Emui 10?

Anyone successfully root Magisk with Emui 10?

Not me, so back in 9.1.

titi66200 said:
Not me, so back in 9.1.
Click to expand...
Click to collapse
So rooting 9.1 method does not work for emui 10 anymore?

How I can upgrade to 10 , also is the battery better 9؟

Johnny Eng said:
So rooting 9.1 method does not work for emui 10 anymore?
Click to expand...
Click to collapse
On EMUI 10 you can't unlock the bootloader, so no root.

Pretoriano80 said:
On EMUI 10 you can't unlock the bootloader, so no root.
Click to expand...
Click to collapse
Ahhhh that's so sad!!! What if those bootloader has been unlock and update via OTA? Will it lose bootloader unlock capabilities?
Thank you
Emui 9.1 root retainer:
1)Boot without root (make sure that Magisk patched recovery_ramdisk is installed)
2)Connect the UDB cable and boot to eRecovery (Press Volume Up when rebooting)
3)From eRecovery select Factory Reset (that won't do any wipe, but il will boot with Magisk root)
4)After boot go to /splash2 /recovery folder and delete the "command" file (this will prevent an accidental wipe if you remove the Magisk patched recovery_ramdisk)
Check if Messages and other apps are now working even if you are rooted

Is there still no root option for Android 10 on P20 Pro ?

Pretoriano80 said:
On EMUI 10 you can't unlock the bootloader, so no root.
Click to expand...
Click to collapse
What!!??
Even if you already have the unlock code from before?

mosaiques said:
What!!??
Even if you already have the unlock code from before?
Click to expand...
Click to collapse
Yes, even if you have the code you won't be able to unlock the bootloader on EMUI 10.

I don't know if version 10 relock the bootloader because with android 10 in fasboot mode my p20 pro says "Phone: Unlocked".
On the other hand fastboot flash controls do not work.

Pretoriano80 said:
Yes, even if you have the code you won't be able to unlock the bootloader on EMUI 10.
Click to expand...
Click to collapse
Ok then... So long Huawei.

Hi all,
Is there any solution to root EMUI 10 (P20 Pro CLT-29)??
I have already unlocked bootloader when I had EUI 8 or 9..
When I want to flash twrp then I got failed message.. Write failed..
Due to EMUI 10 update I lost root and I want to root again but I can not flash twrp...
USB debugging ON and OEM unlock ON.
Please advise, thank you!

@moli1984
No root on EMUI 10, if you need it return to 9.1.

Johnny Eng said:
Ahhhh that's so sad!!! What if those bootloader has been unlock and update via OTA? Will it lose bootloader unlock capabilities?
Click to expand...
Click to collapse
If the bootloader is already unlocked, you can roll back from 10 to 9.1 and it is still unlocked.

root Huawei P20 Pro to recover files
Hi Guys, I have a Huawei P20 Pro which runs on EMUI 10.0.0 model: CLT-L04. I have deleted some files (photos) from internal storage that I want to recover. Now the issue is that the phone is not rooted so file recovery softwares fail to access those deleted files. That's why I want to root the phone obviously without wiping off the data [deleted photos again]. Is there an option for me. Is there a way that I just boot it and recover my photos. It is not important whether the root process proceed or fail at the end. My goal is to recover my data not rooting. I appreciate if anyone can help me please.

arjavanb said:
Hi Guys, I have a Huawei P20 Pro which runs on EMUI 10.0.0 model: CLT-L04. I have deleted some files (photos) from internal storage that I want to recover. Now the issue is that the phone is not rooted so file recovery softwares fail to access those deleted files. That's why I want to root the phone obviously without wiping off the data [deleted photos again]. Is there an option for me. Is there a way that I just boot it and recover my photos. It is not important whether the root process proceed or fail at the end. My goal is to recover my data not rooting. I appreciate if anyone can help me please.
Click to expand...
Click to collapse
If you go into your gallery app and scroll down there should be a folder called "recently deleted". They should be there, otherwise I think you may be out of luck especially since the latest android version on the P20 pro can't be rooted.

Hi,
I have installed EMUI 10.0.0.175 OTA update.
I have been reading for a few days, and a have seen there is no way to root EMUI 10.
My priority is recover some files that i saved in /data/local.
I tried with "adb backup -all" , but it only backups "/data/app" dir.
There is someting that can i do to recover this folder, without root?
Best regards.

It's absolutely possible. Since EMUI is using a boot ramdisk for early stage boot, you need to patch the ramdisk partition using Magisk. How to get the ramdisk image? Boot into TWRP and execute command `dd if=/dev/block/by-name/ramdisk of=/ramdisk.img` in TWRP terminal and then execute command `adb pull /ramdisk.img .` in your PC terminal. Patch the ramdisk.img using Magisk and execute `fastboot flash ramdisk Magisk_patched-xxxx.img` to overwrite ramdisk partition. Make sure you keep the original copy of ramdisk.img, in case of you accidentally brick your phone. (FYI, the first boot time will take little longer than usual, and the boot flash screen will display android icon instead of "HUAWEI")