My phone is Mate 20 X EVR-L29 C636. Like many of us, I received an OTA EMUI10 update 10.0.0.180. It resulted in Soft brick. I have access to erecovery and fastboot.
Thanks to efforts of lot of people on this forum, many people successfully unbricked their phone using dload method with recently released 10.0.0.180 build. I have family pictures on phone, which I do not want to lose using dload method.
I checked my build number using fastboot and it says EVR-L29 9.1.0.347(C636E3R1P11). Thanks to @thunderbolt128. He thinks that my phone's CUST and vendor partitions are still 9.1. May be the other partitions upgraded to EMUI 10. My question is it possible to flash CUST and vendor partitions using any method (may be fastboot flash?) without erasing user data? I can perhaps using "EMUI extractor" to extract images and try flashing them. My problem is that I always had Samsung Notes and I do not know the partition layout of Huawei Mate 20 x. Any help and suggestions are welcome.
PS C:\platform-tools> .\fastboot.exe oem get-build-number
(bootloader) :EVR-L29 9.1.0.347(C636E3R1P11)
OKAY [ 0.016s]
Finished. Total time: 0.033s
PS C:\platform-tools> .\fastboot.exe getvar vendorcountry
vendorcountry: hw/spcseas
Finished. Total time: 0.020s
PS C:\platform-tools> .\fastboot.exe oem get-bootinfo
(bootloader) locked
OKAY [ 0.004s]
Finished. Total time: 0.018s
PS C:\platform-tools> .\fastboot.exe getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: 'FAIL:need all image flashed!')
Finished. Total time: 0.033s
PS C:\platform-tools>
hsarao said:
My phone is Mate 20 X EVR-L29 C636. Like many of us, I received an OTA EMUI10 update 10.0.0.180. It resulted in Soft brick. I have access to erecovery and fastboot.
Thanks to efforts of lot of people on this forum, many people successfully unbricked their phone using dload method with recently released 10.0.0.180 build. I have family pictures on phone, which I do not want to lose using dload method.
I checked my build number using fastboot and it says EVR-L29 9.1.0.347(C636E3R1P11). Thanks to @thunderbolt128. He thinks that my phone's CUST and vendor partitions are still 9.1. May be the other partitions upgraded to EMUI 10. My question is it possible to flash CUST and vendor partitions using any method (may be fastboot flash?) without erasing user data? I can perhaps using "EMUI extractor" to extract images and try flashing them. My problem is that I always had Samsung Notes and I do not know the partition layout of Huawei Mate 20 x. Any help and suggestions are welcome.
PS C:\platform-tools> .\fastboot.exe oem get-build-number
(bootloader) :EVR-L29 9.1.0.347(C636E3R1P11)
OKAY [ 0.016s]
Finished. Total time: 0.033s
PS C:\platform-tools> .\fastboot.exe getvar vendorcountry
vendorcountry: hw/spcseas
Finished. Total time: 0.020s
PS C:\platform-tools> .\fastboot.exe oem get-bootinfo
(bootloader) locked
OKAY [ 0.004s]
Finished. Total time: 0.018s
PS C:\platform-tools> .\fastboot.exe getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: 'FAIL:need all image flashed!')
Finished. Total time: 0.033s
PS C:\platform-tools>
Click to expand...
Click to collapse
wait, if you have fastboot and adb access, why dont u just use the command line in order to manually copy over all the data from your phone to your pc/laptop?
Sent from my Huawei Mate 20 X EVR-AL00 using Tapatalk
I only have erecovery and fastboot access. The emergency backup option in erecovery does not work neither does the safe mode boot.
Is there a way to copy data using fastboot ?
hsarao said:
I only have erecovery and fastboot access. The emergency backup option in erecovery does not work neither does the safe mode boot.
Is there a way to copy data using fastboot ?
Click to expand...
Click to collapse
hmmmm ok, it seems like fastboot is write to device only, unfortunately. can u check if you have ADB access when ure in erecovery?
Sent from my Huawei Mate 20 X EVR-AL00 using Tapatalk
jbmc83 said:
hmmmm ok, it seems like fastboot is write to device only, unfortunately. can u check if you have ADB access when ure in erecovery?
Sent from my Huawei Mate 20 X EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
No, ereceovery does not provide access to ADB. Has anyone checked if the EMUI 10 is available using erecovery? Some one was saying, EMUI 10 will only be available in erecovery after the stable release.
Thanks
hsarao said:
No, ereceovery does not provide access to ADB. Has anyone checked if the EMUI 10 is available using erecovery? Some one was saying, EMUI 10 will only be available in erecovery after the stable release.
Thanks
Click to expand...
Click to collapse
yes thats true. depending on region/cust, stable release will pop up starting in december, but can potentially take until february/march....
Sent from my Huawei Mate 20 X EVR-AL00 using Tapatalk
Related
After i got my unlock Code from Huawei and enabled Usb Debugging mode and Oem unlock in developer options,I've Unlocked my bootloader Successfully.
my phone Started to Do a factory reset and it failed so i did it by myself manually.
after that i enabled Usb Debugging mode ,but i couldnt enable oem unlock option and i boot my phone to fastboot and Started flashing the TWRP...but it said:
Writing...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
can Someone help me to Flash recovery and root my phone?
phone info's:
Model:MHA-L29
Build num. : MHA-L29C185B138
Bootloader Unlocked
Maybe lock it and unlock again.
gm007 said:
Maybe lock it and unlock again.
Click to expand...
Click to collapse
the problem is that i cant do any operation on Bootloader including locking bootloader...
ezraiil1 said:
the problem is that i cant do any operation on Bootloader including locking bootloader...
Click to expand...
Click to collapse
C:\Users\Abolfazl\Desktop\>fastboot flash recovery 1.img
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
C:\Users\Abolfazl\Desktop\>fastboot flash recovery 1.img
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
C:\Users\Abolfazl\Desktop\>fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Abolfazl\Desktop\>fastboot oem unlock *********
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Abolfazl\Desktop\>fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Abolfazl\Desktop\>fastboot devices
AHK7N16B18003212 fastboot
What version of fastboot do you have?
5[Strogino] said:
What version of fastboot do you have?
Click to expand...
Click to collapse
Minimal ADB and Fastboot
ezraiil1 said:
After i got my unlock Code from Huawei and enabled Usb Debugging mode and Oem unlock in developer options,I've Unlocked my bootloader Successfully.
my phone Started to Do a factory reset and it failed so i did it by myself manually.
after that i enabled Usb Debugging mode ,but i couldnt enable oem unlock option and i boot my phone to fastboot and Started flashing the TWRP...but it said:
Writing...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
can Someone help me to Flash recovery and root my phone?
phone info's:
Model:MHA-L29
Build num. : MHA-L29C185B138
Bootloader Unlocked
Click to expand...
Click to collapse
try to revoke usb debugging then enable again
eddmecha said:
try to revoke usb debugging then enable again
Click to expand...
Click to collapse
it doesnt work...
ezraiil1 said:
it doesnt work...
Click to expand...
Click to collapse
have you tried with a different cable & pc?how about your drivers?is it the lastest?
I had the exact same problem. Disable everything related to "Find my phone" and restart. TWRP will flash after this.
ezraiil1 said:
After i got my unlock Code from Huawei and enabled Usb Debugging mode and Oem unlock in developer options,I've Unlocked my bootloader Successfully.
my phone Started to Do a factory reset and it failed so i did it by myself manually.
after that i enabled Usb Debugging mode ,but i couldnt enable oem unlock option and i boot my phone to fastboot and Started flashing the TWRP...but it said:
Writing...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
can Someone help me to Flash recovery and root my phone?
phone info's:
Model:MHA-L29
Build num. : MHA-L29C185B138
Bootloader Unlocked
Click to expand...
Click to collapse
eddmecha said:
have you tried with a different cable & pc?how about your drivers?is it the lastest?
Click to expand...
Click to collapse
Problem Solved.
Had to pay 30$ to Funkyhuawei to Flash a firmware and Unlock it again.
Problem Solved.
Had to pay 30$ to Funkyhuawei to Flash a firmware and Unlock it again.
Thank you everybody,all of you were Useless xD
love u all.
Cya!
Hello
after i succesfully used DC Phoenix to recover Huawei Mate 8 (NXT-L29C432) i cannot flash TWRP or anything on my phone , as im still getting the "FAILED (remote: image verification error)" from fastboot. So i also cannot root and use the device as before
Im sure im not alone with this issue, but i cannot find any clear solution for this. Can you please help or advice me further??
I spent 15€, recovered the phone, but with this, its still partial success.
I basicaly followed https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
Here some outputs:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.0-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22140 KB)...
OKAY [ 0.530s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.562s
Before the use of DC Phoenix, i always get this number.
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
QHC0216327001941 fastboot
Now:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
0123456789ABCDEF fastboot
In Fastboot mode, on phone screen i see:
PHONE Unlocked
FRP Lock
DC - Unlocker 2 Client 1.00.1308 reports:
FB LockState: UNLOCKED
USER LockState: LOCKED
unlocked
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ -0.000s]
finished. total time: -0.000s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
In Developer menu i have the
"Allow OEM unlock" grayed & disabled, im unable to swich it on..
Can you please explain what happend and how to fix this?
Thank you for further help.
Solved with mighty HCU client, i was able to import the just the SN back without problems. Then as usual.. unlock the bootloader, TWRP, SU... and now the phone is back in shape
I hope I can recover my Mate 9 Pro.
Maybe 15€ is have to spend but FunkyHuawei is more expensive.
Hi. I have same problem., I unlocked Huawei WAS-AL00 bootloader via Miracle Huawei Tool, it unlocked successfully. But, I can't flash TWRP, it says-FAILED (remote: image verification error)
Whent type fastboot oem lock-state info in CMD, it shows:
FB LockState: UNLOCKED
USER LockState: LOCKED
There is not FRP or OEM lock option in settings, becuse this is China version model and doesn't support Google Play.
What is USER LOCK STATE? Please help me. Thanks.
Remote:image verification error.
When i try to flash Mate 8 nxt l29 twrp recovery its says remote:image verification error..the phone fastboot is unlocked .i tried many twrp images but still the same problem
Hello,
I need help to unbrick my phone please,
After trying to back to stock i got stuck while dload method with BLL-L22C636B150 (android 6.0) Firmware after flashing RollbackPackage from same firmware (android 7.0 to 6.0)
My phone's screen is now only black, no boot logo anymore or recovery.
It's only show connected fastboot while plug in, i can only reboot to fastboot.
PS C:\adb> fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.006s
PS C:\adb> fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NRD90M test-keys
finished. total time: 0.005s
PS C:\adb> fastboot oem get-product-model
...
(bootloader) HUAWEI BLL-L22
OKAY [ 0.007s]
finished. total time: 0.008s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/spcseas
finished. total time: 0.005s
PS C:\adb> fastboot oem get-psid
...
(bootloader) SN:YCP7XXXX
(bootloader) IMEI:8646XXXX
(bootloader) IMEI1:8646XXXX
What can i do please ?
Try team mt tool for unbrick provide file from marshmallow update.app
siddhrsh said:
Try team mt tool for unbrick provide file from marshmallow update.app
Click to expand...
Click to collapse
13:00:27: All images are found, everything is ready for the unbricking process.
13:00:29: Unbricking started. Your computer may freezes during the process.
13:00:29: flash boot "C:\adb\348\boot.img"
13:00:31: The Boot image is flashing successfully
13:00:31: flash system "C:\adb\348\system.img"
13:03:26: The System image is flashing successfully
13:03:26: flash cust "C:\adb\348\cust.img"
13:03:49: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 13.115s]
writing 'cust' 1/2...
OKAY [ 3.142s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.109s]
writing 'cust' 2/2...
OKAY [ 0.035s]
finished. total time: 16.401s
13:03:49: Error#1
13:03:49: flash recovery "C:\adb\348\recovery.img"
13:03:51: The Recovery image is flashing successfully
13:03:51: Completed
13:03:51: Something went wrong (((
Still black screen rebooting only on fastboot mode
Demodark said:
13:00:27: All images are found, everything is ready for the unbricking process.
13:00:29: Unbricking started. Your computer may freezes during the process.
13:00:29: flash boot "C:\adb\348\boot.img"
13:00:31: The Boot image is flashing successfully
13:00:31: flash system "C:\adb\348\system.img"
13:03:26: The System image is flashing successfully
13:03:26: flash cust "C:\adb\348\cust.img"
13:03:49: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 13.115s]
writing 'cust' 1/2...
OKAY [ 3.142s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.109s]
writing 'cust' 2/2...
OKAY [ 0.035s]
finished. total time: 16.401s
13:03:49: Error#1
13:03:49: flash recovery "C:\adb\348\recovery.img"
13:03:51: The Recovery image is flashing successfully
13:03:51: Completed
13:03:51: Something went wrong (((
Still black screen rebooting only on fastboot mode
Click to expand...
Click to collapse
Did you flash marshmallow files
Images
Yes i tried to unbrick with : Huawei_GR5_2017_BLL-22_C636B150_South_East_Asia_6.0.zip
17:49:30: All images are found, everything is ready for the unbricking process.
17:49:32: Unbricking started. Your computer may freezes during the process.
17:49:32: flash boot "C:\adb\B150\boot.img"
17:49:34: The Boot image is flashing successfully
17:49:34: flash system "C:\adb\B150\system.img"
17:52:03: The System image is flashing successfully
17:52:03: flash cust "C:\adb\B150\cust.img"
17:52:26: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 12.833s]
writing 'cust' 1/2...
OKAY [ 3.181s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.114s]
writing 'cust' 2/2...
OKAY [ 0.045s]
finished. total time: 16.173s
17:52:26: Error#1
17:52:26: flash recovery "C:\adb\B150\recovery.img"
17:52:29: The Recovery image is flashing successfully
17:52:29: flash userdata "C:\adb\B150\userdata.img"
17:52:36: target reported max download size of 471859200 bytes
sending 'userdata' (143361 KB)...
OKAY [ 3.784s]
writing 'userdata'...
OKAY [ 1.013s]
finished. total time: 4.797s
17:52:36: Error#1
17:52:36: Completed
17:52:36: Something went wrong (((
Huawei Multi-Tool by Team MT v. 8.0.3.1 beta
I dont know wich one i can try now ?
http://pro-teammt.ru/firmware-database/?firmware_model=bll-l22&firmware_page=0
Black Screen
I tried to unbrick with update.zip (full OTA B150 version) script said all done without bug, but still black screen (no light) stuck in fastboot mode.
Demodark said:
I tried to unbrick with update.zip (full OTA B150 version) script said all done without bug, but still black screen (no light) stuck in fastboot mode.
Click to expand...
Click to collapse
Just flash the small data file via dload method.it should be 700-800 MB i guess. Once flashed, reboot to stock recovery and factory reset and boot
shashank1320 said:
Just flash the small data file via dload method.it should be 700-800 MB i guess. Once flashed, reboot to stock recovery and factory reset and boot
Click to expand...
Click to collapse
What is "the small data file" please ?
PS C:\adb> fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.007s
PS C:\adb> fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NRD90M test-keys
finished. total time: 0.005s
PS C:\adb> fastboot oem get-product-model
...
(bootloader) HUAWEI BLL-L22
OKAY [ 0.006s]
finished. total time: 0.006s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/spcseas
finished. total time: 0.006s
PS C:\adb> fastboot oem get-psid
...
(bootloader) SN:YCP7N17609000963
(bootloader) IMEI:864646034450028
(bootloader) IMEI1:864646034717855
OKAY [ 0.005s]
finished. total time: 0.005s
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.009s
PS C:\adb>
Demodark said:
What is "the small data file" please ?
Click to expand...
Click to collapse
Let me check the firmware and get the link for you
shashank1320 said:
Let me check the firmware and get the link for you
Click to expand...
Click to collapse
News ?
Demodark said:
News ?
Click to expand...
Click to collapse
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v74004/f1/full/hw/spcseas/
Unzip and see if there is update.app file in it, if so, dload it and it should be fine
shashank1320 said:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v74004/f1/full/hw/spcseas/
Unzip and see if there is update.app file in it, if so, dload it and it should be fine
Click to expand...
Click to collapse
Link is dead.
Demodark said:
Link is dead.
Click to expand...
Click to collapse
Let me recheck
What can i do ?
Always black screen, but phone detected as fastboot mode, reboot only leads to fastboot mode.
have you tried unlocking again your bootloader? updating or rollbacking of EMUI makes your bootloader locked by default.
try to unlock it first and flash your OS
if you want to use the dload way. try flashing the stock recovery after unlocking your bootloader.
Demodark said:
Link is dead.
Click to expand...
Click to collapse
K.. But after that how reset the DNS to its original state
So...
Just ran the following commands:
Code:
C:\beta-flashy_0.2>fastboot oem get-product-model
...
(bootloader) MHA-L29
OKAY [ 0.009s]
finished. total time: 0.011s
C:\beta-flashy_0.2>fastboot oem get-build-number
...
(bootloader) :MHA-L29 9.0.1.191(C432E7)
OKAY [ 0.010s]
finished. total time: 0.011s
C:\beta-flashy_0.2>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :MHA-L29 8.0.0.376(C567)
OKAY [ 0.010s]
finished. total time: 0.011s
C:\beta-flashy_0.2>fastboot getvar vendorcountry
vendorcountry: hw/usa
finished. total time: 0.008s
My device seems to be halfway stuck between PIE and OREO. I can only enter fastboot, and as you can see, my device responds to fastboot commands. As far as I can tell, I can even flash whatever I want. Bootloader seems to be unlocked (Red text, "PHONE Unlocked," and "FRP Unlock."
What happened...
I upgraded from Oreo (.376 build) to Pie (9.0.1.191 build) using the method outlined here. Success! Got greedy, decided to install Resurrection Remix OpenKirin Pie build. No problem. Didn't like the camera, tried to flash back to stock. Bootloop. Whoops. Flash RR again? Nope, that didn't work either. I *was* able, however, to successfully flash and boot OpenKirin's Omnirom Pie. I really should have left well enough alone at that point. But no, I thought, maybe I can get back to stock from here. Tried to flash SYSTEM.img from stock firmware, aaaand... bootloop. Re-flashing Omnirom doesn't work, either. Have been stuck like this since Friday morning.
Again, I have Fastboot, and it's unlocked.
I've tried the DLOAD method twice over the weekend, and once more this morning. It almost immediately says "Software install failed" every time.
I am out of ideas. Based on the fastboot responses above, does anybody have any ideas?
daina said:
So...
Just ran the following commands:
Code:
C:\beta-flashy_0.2>fastboot oem get-product-model
...
(bootloader) MHA-L29
OKAY [ 0.009s]
finished. total time: 0.011s
C:\beta-flashy_0.2>fastboot oem get-build-number
...
(bootloader) :MHA-L29 9.0.1.191(C432E7)
OKAY [ 0.010s]
finished. total time: 0.011s
C:\beta-flashy_0.2>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :MHA-L29 8.0.0.376(C567)
OKAY [ 0.010s]
finished. total time: 0.011s
C:\beta-flashy_0.2>fastboot getvar vendorcountry
vendorcountry: hw/usa
finished. total time: 0.008s
My device seems to be halfway stuck between PIE and OREO. I can only enter fastboot, and as you can see, my device responds to fastboot commands. As far as I can tell, I can even flash whatever I want. Bootloader seems to be unlocked (Red text, "PHONE Unlocked," and "FRP Unlock."
What happened...
I upgraded from Oreo (.376 build) to Pie (9.0.1.191 build) using the method outlined here. Success! Got greedy, decided to install Resurrection Remix OpenKirin Pie build. No problem. Didn't like the camera, tried to flash back to stock. Bootloop. Whoops. Flash RR again? Nope, that didn't work either. I *was* able, however, to successfully flash and boot OpenKirin's Omnirom Pie. I really should have left well enough alone at that point. But no, I thought, maybe I can get back to stock from here. Tried to flash SYSTEM.img from stock firmware, aaaand... bootloop. Re-flashing Omnirom doesn't work, either. Have been stuck like this since Friday morning.
Again, I have Fastboot, and it's unlocked.
I've tried the DLOAD method twice over the weekend, and once more this morning. It almost immediately says "Software install failed" every time.
I am out of ideas. Based on the fastboot responses above, does anybody have any ideas?
Click to expand...
Click to collapse
Have been able to flash TWRP (Pie). Am trying to see if I can flash a custom ROM from here. Have my doubts.
daina said:
Have been able to flash TWRP (Pie). Am trying to see if I can flash a custom ROM from here. Have my doubts.
Click to expand...
Click to collapse
Results from DC-Unlocker:
Code:
DC Phoenix 0.0.0.118
user:daina
Looking for a device in upgrade mode
No devices detected in upgrade mode
Device found: 5RE0217927000170
Detecting recovery partition
File size: 5,476,648,324 bytes
Current version(CURVER): MHA_Global-CUST 9.0.1(C999)
ERECOVERY_KERNEL partition found
ERECOVERY_RAMDISK partition found
ERECOVERY_VENDOR partition found
11/18/2019 4:26:30 PM Starting to try Rescue Recovery...
Looking for a device in fastboot mode
Device found: 5RE0217927000170
Getting IMEI...
Getting build number...
Getting model ...
Getting battery state...
Getting backdoor info...
Getting lock state info...
Getting lock boot info...
Build number: :MHA-L29 9.0.1.191(C432E7)
Model: MHA-L29
Vendor/Country: Vendor/Country: hw/usa
Battery state: 6812mv
OEM lock state info:
FB LockState: UNLOCKED
USER LockState: LOCKED
OEM get bootinfo:
unlocked
Process identifier:20538296
Getting build number...
Getting base version...
Getting cust version...
Getting preload version...
Erasing ver .. .
File size: 5,476,648,324 bytes
Current version(CURVER): MHA_Global-CUST 9.0.1(C999)
Writing rescue_recovery_kernel partition
RESCUE_RECOVERY_KERNEL partition update :FAIL image verification error
Cannot enter in Recovey mode
My mate 9 mha-l29 after a failed update from hisuite (the cell reboot during the update) remains stuck in the screen as show in the image below. no access to recovery emui.
Inviato dal mio SNE-LX1 utilizzando
velocity86 said:
My mate 9 mha-l29 after a failed update from hisuite (the cell reboot during the update) remains stuck in the screen as show in the image below. no access to recovery emui.
Inviato dal mio SNE-LX1 utilizzando Tapatalk
View attachment 4942543
Click to expand...
Click to collapse
Cannot open the attachment. Anyway, did you resolve - if not, do you remember what was your firmware version and to which version you were trying to upgrade?
Do you have ADB/Fastboot tools installed to PC - if not, you can find on XDA Minimal ADB and Fastboot
Boot the phone to Fastboot (switch the phone off, connect by USB to PC, press and keep pressing Vol- and boot by Pow).
In Fastboot screen, does it show at the bottom that Phone (Bootloader) is locked (in green) or unlocked (red), also does it show that FRP (OEM) is locked or unlocked (you can also attach a photo)
Execute the following Fastboot commands and provide the results back (not from the first command - it's just to check if PC is connected to the phone)
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
Thanks for the help. I hope to resolve the problem
C:\ADB>fastboot devices
AHK7N16B02001730 fastboot
C:\ADB>fastboot oem get-bootinfo
(bootloader) locked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADB>fastboot oem get-product-model
(bootloader) MHA-L29
OKAY [ 0.017s]
finished. total time: 0.017s
C:\ADB>fastboot oem get-build-number
(bootloader) :MHA-L29 8.0.0.379(C432)
OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADB>fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :MHA-L29 8.0.0.379(C432)
OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADB>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s