EMUI Brick - Huawei Mate 10 Questions & Answers

Hey,
Five months ago, I decided to flash the EMUI 9 beta on my Huawei Mate 10 Pro (BLA-L29)
Everything was working fine until one day the device didn't want to boot.
I decided to fix the problem by using the recovery but the phone refused to boot to recovery, So I headed to fastboot and I tried flashing EMUI 8 but it gave me the error "Command not allowed"
I then noticed FRP Lock was enabled, I was so stupid to disable OEM Unlocking.
I tried using DC Phoenix with this :tutorial: but It didn't work, I got the error "Device running incompatible security patch", "Command not allowed".
I decided to try the DLOAD method but the phone never booted to the installation process.
Model: BLA-L29
Build number: :BLA-LGRP2-OVS 9.0.0.108(log)
OEM LOCK INFO:
FB LockState: Locked
USER LockState: UNLOCKED
OEM get bootinfo:
unlocked.
I don't know how to solve this problem, Could anyone help me?

Related

After hardbricked ..

My Moto Z XT1650-03 was hardbricked, finally after several days I found a blankfiles that worked with my version, however as soon as the phone started in fastboot I verified that the bootloader was blocked, hence I am not able to install recovery or any ROM, I have already tried several ROMS, I tried to install by RSD but with the bootloader blocked there is always the same error, when I try to unlock the bootloader the following error appears: (bootloader) Check 'Allow OEM Unlock' in Android Settings> Developer)
Any solution?
*My bootloader is in version 91.08, but the newest ROM I found is with version 91.07, may be why I can not update with adb?
https://imgur.com/a/Qwpz5

Huawei Y6 SCL-U31 stuck in Bootloop, tried all method but didn't work. Help needed.

My Huawei Y6 SCL U31 got stuck in bootloop. I tried to put it in recovery mode, didn't work. Tried to flash new ROM in it but the phone is OEM locked. After messing on internet for 2 days I got to know that my bootloader should be unlocked in order flash new ROM on it. I tried multiple unlocking tools but they ask for Huawei Unlock 16 Digit code and apparently Huawei has taken down the page a while ago. All I can do is to put it on fastboot mode which says FRP lock Device Lock. Please anyone tell me how to unlock the bootloader or a fix which can make my phone work again. thanks.
HELP
ahsanraza said:
My Huawei Y6 SCL U31 got stuck in bootloop. I tried to put it in recovery mode, didn't work. Tried to flash new ROM in it but the phone is OEM locked. After messing on internet for 2 days I got to know that my bootloader should be unlocked in order flash new ROM on it. I tried multiple unlocking tools but they ask for Huawei Unlock 16 Digit code and apparently Huawei has taken down the page a while ago. All I can do is to put it on fastboot mode which says FRP lock Device Lock. Please anyone tell me how to unlock the bootloader or a fix which can make my phone work again. thanks.
Click to expand...
Click to collapse
I have tried almost all the available stock roms available on my Y6 but apparently non of them work. need help!
bump

Huawei mate 10 Lite BRICK

Hello my name is Aleksander i have bricked my mate 10 lite.
Original phone is rne-l21c432 but i rebranded it few weeks back to c185 for update to OREO.
Yesterday i wannted to update to last rom b332 with HuRUpdater_0.3
It flashed ok but rhere was one error but i didnt mind of that becouse at flashing before yesderday was also error and everything worked ok.
Now i can only get in rescue mode and got this error
Error!
Func NO 15(bl31 image)
Error NO 1(security verify failed)
I tryed to flash with DC-Phoenix and it's not working. Early version of dc-phoenix works for flashing but i got this. dc-phoenix can not activate back door and fb lock state is locked.
Newer versions says that the device is not supported.
I tryed to relock bootloader and unlock again, but now i can not get in to the fastboot anymore. it is looping constantly in that rescue mode and i get that errors Func NO 15 and errror NO1.
I don't know what to do anymore.
Does anybody have any solution to try? .
The Dc-Phoenix did work like few weeks back on my Mate 10 lite.
Thank you for youre response.
rutarvip said:
Hello my name is Aleksander i have bricked my mate 10 lite.
Original phone is rne-l21c432 but i rebranded it few weeks back to c185 for update to OREO.
Yesterday i wannted to update to last rom b332 with HuRUpdater_0.3
It flashed ok but rhere was one error but i didnt mind of that becouse at flashing before yesderday was also error and everything worked ok.
Now i can only get in rescue mode and got this error
Error!
Func NO 15(bl31 image)
Error NO 1(security verify failed)
I tryed to flash with DC-Phoenix and it's not working. Early version of dc-phoenix works for flashing but i got this. dc-phoenix can not activate back door and fb lock state is locked.
Newer versions says that the device is not supported.
I tryed to relock bootloader and unlock again, but now i can not get in to the fastboot anymore. it is looping constantly in that rescue mode and i get that errors Func NO 15 and errror NO1.
I don't know what to do anymore.
Does anybody have any solution to try? .
The Dc-Phoenix did work like few weeks back on my Mate 10 lite.
Thank you for youre response.
Click to expand...
Click to collapse
Is there really no solution ?
My mate 10 lite is bricked too that's why I'm following your post too

Xiaomi Mi8 Bricked after locking bootloader

Hello. I have a problem. I have Xiaomi Mi8, which was sent back on a warranty, because it just didn't powered on one day. It was sent from PL to China, they sent it back after a month and from this time I had some issues. The phone came back with unlocked bootloader. I couldn't use Google Pay to use contactless payment, couldn't install Netflix for example, and other general problems caused by unlocked bootloader appeared.
Today I wanted to change that, so I entered fastboot mode, connected phone to PC, and entered "fastboot oem lock". It said OKAY, finished, but then phone was stuck in a bootloop.
In recovery, it says that "This MIUI version can't be installed on this device". Wiping data doesn't help.
I wanted to re-flash it with Global ROM, but Mi Flash says "Error: FAILED (remote: Erase is not allowed in Lock State)"
I wanted to unlock it using Mi-Unlock but this fails also. It ends with "Current account is not bound to this device. Add your account and device in MIUI's Settings Developer options Mi Unlock status" message.
I cannot enter settings because phone will not boot up. I read about authenticating with account_auth.exe on c mi com/thread-2173190-1-0.html (remove spaces, sorry but I cannot post links yet). I logged in, but then instead of "Unauthorized Xiaomi account" I have "Request failed" message and I cannot click "Apply Bind".
I'm running out of ideas. Phone will not boot, it can't be flashed, what else can I do other than replacing main board? Please help.
I had the same problem with Redmi Note 7 pro I have changed from china version to India version but I had some security issues with some app as the Bootloader was open since I flashed India version I did as you did from cmd I loced the Bootloader so the MIUI was blocked and phone was bricked I had to use boxes software then go back to china version again then setup new mi account with new E mail and different SIM then I was able to flash new global indian version of MIUI 12.5 but unfortunately I lost my IMEI 1 but lucklly had saved my Data on Google account ,so you should use boxes software to use your phone again!

Remote: Token verify failed, reboot device

Hello
Anyone ever seen this when trying to unlock the Note 9 Pro (Joy)?
Im in Fastboot - and the device looks like it's just going to unlock but at 99% of the counter I get the Remote: Token verify failed, reboot device error, the fastboot teddy thing flashes for a second and then back into Fastboot.
Anyone seen that before?
A
PS:- Just thought, when I started the unlock process a week ago I was running 11.0.3 and then I installed the 11.0.4 firmware....would that make a difference?
Just in case this happens to anyone else - the issue I was having was caused by using a different version of fastboot.exe other than the one that came with the unlock tool.
My bad

Categories

Resources