Hi, another fool here who’s bricked their Mate 10 Pro! Will DC Phoenix will help?
I was attempting to de-brand the device and things were going well (flashed numerous Pie firmwares) but then I attempted a downgrade to Oreo and, like others have found, this bricked the phone: the update failed and rebooted to fastboot with a black screen.
So the phone's stuck in fastboot but Windows can see the device via fastboot and so does HiSuite (but HiSuite claims no recovery options are available.)
I have the device serial number, IMEI and numerous firmwares (inc BLA-09 Board Software). Bootloader is locked.
Do you think paying for DC Phoenix will help? :fingers-crossed:
Thanks
Mateus109 said:
Hi, another fool here who’s bricked their Mate 10 Pro! Will DC Phoenix will help?
I was attempting to de-brand the device and things were going well (flashed numerous Pie firmwares) but then I attempted a downgrade to Oreo and, like others have found, this bricked the phone: the update failed and rebooted to fastboot with a black screen.
So the phone's stuck in fastboot but Windows can see the device via fastboot and so does HiSuite (but HiSuite claims no recovery options are available.)
I have the device serial number, IMEI and numerous firmwares (inc BLA-09 Board Software). Bootloader is locked.
Do you think paying for DC Phoenix will help? :fingers-crossed:
Thanks
Click to expand...
Click to collapse
You will have to use test point, so this requires you to remove the back cover and short the test points.
It's not an easy task, but you can find some guides here on the forums.
Update: Took the phone to a local Huawai approved repair shop and they fixed it! They also de-branded it for me.
Related
Hi all,
Wishing you all a happy New Year in arrears and the very best for the next 12 months.
I've got a problem with my device, its a STF-AL10 model with international rom bought during the November Sales.
It came with STF-L09C432B150 installed, I got the bootloader unlocked, TWRP installed and rooted with Magisk and was working fine except the capacitive buttons.
I thought I could live without capacitive buttons but I didn't work out and I had the urge to find a solution. After some intensive reseach (48hrs on a weekend in my 'lab') it seems the B120 firmware had no issues with the capacitive buttons, so I tried to downgrade to that and thats when the problems started.
Coming from an ancient Sony Z2, I never had issues flashing ROMS, Kernels and the sort as it was almost always easily done in TWRP or CWM (I had a Multi boot thing going, so I chose which recovery I fancied!). Anyway this are my issues now:
- Obviously, my phone was rebranded at origin as I know for sure AL-10 is not for EU market
- I tried restoring the same STF-L09C432B150 (rollback package found on XDA) with DC-Unlocker (wasted 19 Euro) but did not work. Always stops at 5% near end of flashing.
- Tried B130. same error.
- Tried Chinese STF-AL10C00B110. Same error.
- Tried full board flash for STF-AL10 with all DC Phoenix files. Same error.
- Tried forced method with files on a Sandisk SDcard (64GB) formatted to exFAT. Fails, wrong files.
- I noticed that in ADB, it said my bootloader was unlocked but FRP locked.
- After board flash, ADB said Bootloader unlocked (nothing about FRP) but in Muli-tool it says LOCKED.
- Now all ADB commands the write to the phone give errors.
DC-unlocker support keep on saying I should use the correct firmware for my phone, ok but the phone was rebranded at source...do use a Chinese firmware first then update ?
in desperation I did another full board flash but this time I think I wiped oeminfo and Vendor partions. ( I think this is what caused the HARD-BRICK!). Now no Honor logo, no Recovery, No eRecovery, nothing but a blank black screen. ADB still works but no status about bootloader or FRP.
IMEI has changed to 0123456789ABCDEF
You can all laugh and shake your heads which I will take as my punishment but is there a solution to all this, I'm willing to pay another 19 EUR for DC-Phoenix if it helps to fix my phone and if possible get it rooted with all buttons and functions working. That was my intension all along (I'm not really interested in custom Roms, just root access!).
HCU tool for some reason does not install on my computer, and besides, the phone does not boot into an OS to be able to change OEM and VENDOR data.
I even tried the HOTA.zip in the ReBRAND HONOR 9 thread but the file is missing (link down).
And to top it all there is no UK service center.
Please advise...
I think DC unlock is not supported for thì this model. Did Did you try Huawei Funky???
Apparently all versions of Honor 9 are supported by DC-unlocker and DC-Pheonix....
ums1405 said:
Hi all,
Wishing you all a happy New Year in arrears and the very best for the next 12 months.
I've got a problem with my device, its a STF-AL10 model with international rom bought during the November Sales.
It came with STF-L09C432B150 installed, I got the bootloader unlocked, TWRP installed and rooted with Magisk and was working fine except the capacitive buttons.
I thought I could live without capacitive buttons but I didn't work out and I had the urge to find a solution. After some intensive reseach (48hrs on a weekend in my 'lab') it seems the B120 firmware had no issues with the capacitive buttons, so I tried to downgrade to that and thats when the problems started.
Coming from an ancient Sony Z2, I never had issues flashing ROMS, Kernels and the sort as it was almost always easily done in TWRP or CWM (I had a Multi boot thing going, so I chose which recovery I fancied!). Anyway this are my issues now:
- Obviously, my phone was rebranded at origin as I know for sure AL-10 is not for EU market
- I tried restoring the same STF-L09C432B150 (rollback package found on XDA) with DC-Unlocker (wasted 19 Euro) but did not work. Always stops at 5% near end of flashing.
- Tried B130. same error.
- Tried Chinese STF-AL10C00B110. Same error.
- Tried full board flash for STF-AL10 with all DC Phoenix files. Same error.
- Tried forced method with files on a Sandisk SDcard (64GB) formatted to exFAT. Fails, wrong files.
- I noticed that in ADB, it said my bootloader was unlocked but FRP locked.
- After board flash, ADB said Bootloader unlocked (nothing about FRP) but in Muli-tool it says LOCKED.
- Now all ADB commands the write to the phone give errors.
DC-unlocker support keep on saying I should use the correct firmware for my phone, ok but the phone was rebranded at source...do use a Chinese firmware first then update ?
in desperation I did another full board flash but this time I think I wiped oeminfo and Vendor partions. ( I think this is what caused the HARD-BRICK!). Now no Honor logo, no Recovery, No eRecovery, nothing but a blank black screen. ADB still works but no status about bootloader or FRP.
IMEI has changed to 0123456789ABCDEF
You can all laugh and shake your heads which I will take as my punishment but is there a solution to all this, I'm willing to pay another 19 EUR for DC-Phoenix if it helps to fix my phone and if possible get it rooted with all buttons and functions working. That was my intension all along (I'm not really interested in custom Roms, just root access!).
HCU tool for some reason does not install on my computer, and besides, the phone does not boot into an OS to be able to change OEM and VENDOR data.
I even tried the HOTA.zip in the ReBRAND HONOR 9 thread but the file is missing (link down).
And to top it all there is no UK service center.
Please advise...
Click to expand...
Click to collapse
Try stock service B130 firmware:
https://forum.xda-developers.com/honor-9/how-to/stf-l09c432b130-capacitive-buttons-100-t3729106
Instead of step 4 do forced upload: VOLUME UP + VOLUME DOWN + POWER
Hi,
I've managed to re flash b150. In doing so I got back recovery and erecovery but when you reach that final stage of the process the phone stops at 5%. When I reboot to recovery, factory reset stops at 35%
Any ideas
?
Sent from my [device_name] using XDA-Developers Legacy app
ADB now showing BOOTLOAD UNLOCKED but there is no FRP status.
Sent from my [device_name] using XDA-Developers Legacy app
ums1405 said:
ADB now showing BOOTLOAD UNLOCKED but there is no FRP status.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
FRP status is not only on Chinese phones
you need to sew firmware for al10
The phone was rebounded by the shop I bought it from.
It said STF-L09B150 indexical info when the phone was working.
So if I'm going to repair this brick what update files should I use?
Original Chinese or the b150 used when rebranded?
Sent from my [device_name] using XDA-Developers Legacy app
Hi all,
FYI, I've sent the phone back to the shop I bought it from.
I'll take my chances, better than paying money for something that may not work.
Thanks everyone for showing interest in my situation, I let you all know how I get along with this issue.
Ps.: As a community, lets push Huawei/Honor to release Kernel Sources for this model and others like the P10 Plus.
Ps: Huawei/Honor have to realise that a strong developer community adds value and desirability to a product. That's how a product becomes 'Cool' translating into more revenue/customers/profit - eg OnePlus.
.
Hi all, a quick update .....
Sent the phone back and from what I gather the phone actually had an issue with the main board.
Now enjoying a brand new MATE 10 (Non-pro with 6/128gb) in beautiful Obsidian black.
Wonderful.
Back in december/january some users reported a glitch while rebranding STF-AL10 to STF-L09 with the old nougat hwota (at oem bin flashing step).
After editing hwota script, then rebranded : they ended with a FRP locked status.
Their only way to unlock frp was with dcunlocker or funkyhuawei I don't remember.
After frp unlocked, their bootloader wasn't seen through fastboot.
I think this could be solved by regedit a value in registry.
To my knowledge the only public firmware files working with the dload way (3 buttons + usb connected) are the one titled "service repair", the others one won't work dload as they are. They are for hwota or forcing "official" ota.
hi!
after reading all related post in this forum and searching google for ages, i am still not able to unlock my z5c's bootloader. it is not a lack of skills or know-how - i have successfully unlocked my z1c and z3c - but this one simply does not unlock.
i have tried both windows and linux, used shell and flashtool, all drivers properly installed, phone is correctly recognized, bootloader unlock is positive, oem unlock and usb-debugging are activated, phone is in fastboot but i still end up with error "command did not succeed". flashtool additionally shows "oem unlock not activated?". it is, but doesn't seem to have any effect.
i also tried to include the .txt file with the unlockcode into flashtools filestructure: flashtool does something but can't finish the unlock proccess and my phone is not resetting.
i even tried those one-click unlocker without success.
and there is something fishy about this phone: three month ago i got it brandnew from a vendor in china via ebay and first thing i did was connecting it to the pc companion to upgrade the firmware which was 5.1 and it told me, firmware was up to date... so i tried the repair option and it told me "that due to it's prototype status it can only be upgraded from certain ips" - although the phone does not show any hints of being a prototype, neither software- nor hardwarewise and even if it was, it wouldn't prevent the bootloader from being unlocked (afaik).
so you guys are my last hope! any further ideas???
regards,
andi
Hmm... Possibly not the solution but have you tried enabling "Unknown Sources" as well?
Another thing is - you can try flashing a later version of the firmware with Flashtool - one that is common. Afaik there are some versions that have trouble unlocking. Try flashing something like Nordic Unbranded, boot it up, make the settings again.
P.S. Flashing does NOT remove the old leftover firmware - it just writes on top. So you should format the partitions (/system, /data, /cache, /dalvik-cache) before flashing in order to start clean.
when i couldn't upgrade the firmware via pc-companion i used flashtool to flash 7.1.1 (some german version) which i kept ever since. so flashing a different firmware before unlocking is something worth trying? i thought of this as well but never actually tried it because i was just too lazy going though all the setup process again if the attempt failed just like the others... but i'll give it a try then!
and thanks for the input!
Hy,
For me i had to make two steps :
- Flash a non-branded firmware from Xperifirm
- Network unlock it (actually for me it unlocked automatically at the end of the warranty ). This step it is critical (as i was informed in the Sony store)
Then the normal cmd command through adb worked fine.
Basically for me the network lock / warranty was the issue that prevented me to unlock the bootloader
thank you very much for your Input! but there is no network lock...
what i was going to do was flashing a different firmware and try again - and there is something else i didn't think of: the usb2 connector of my mainboard is blocked by an infrared device to power up my pc by voice command via alexa and a harmony hub. and to still be able to use the front usb ports of my case i connected them with an adapter cable to a free usb3 socket on the mainboard…
so it might have been the firmware, the usb2 port on a usb3 socket or prototype-status that caused the trouble - but i'll never know cause basically i'll give up on that phone since more issues occured… i contacted the vendor yesterday and it seems i'll get a full refund!
i now got my hands on a shiny new galaxy s7 and hopefully i'll experience the joys of oreo 8.1 and lineage 15.1 anywhere soon without the hazzle!
thanks again for your help and regards,
andi
So, I work somewhere in which phones need to be switched off for security reasons. Every time I leave, I switch mine back on. I noticed in the past few weeks that my Mate 10 would restart itself a few times after I turn it on after work. After a while, it sorts itself out and stops rebooting, with everything returning to normal. A few days ago, it didn't start up properly and took me to Huawei eRecovery. I'd never seen that before. I tried rebooting, but it would keep coming back to eRecovery. I also did a factory reset and cleared the cache and it looked like it was fixed because I saw a white EMUI screen asking me to set the language and all that stuff. However, the screen would soon become unresponsive and the Mate 10 reboot would itself and go back to eRecovery. I tried this a few more times until I thought I got lucky and managed to finish the whole setup process where I see the phone's home screen with the apps. However, when I tried to add my gmail account, the phone once again reset itself back into eRecovery. So I decided to choose the 'Download the latest version and recovery' option. I left that for a while and when I came back I saw that the phone was still in eRecovery. I rebooted a few times and even tried downloading the latest version again, but now it says, 'Getting package info failed'.
The phone was purchased in China. It says on the back, 'ALP-AL00'. I never attempted to rebrand, root or anything like that. All I've ever done is change the system and input language in settings, download the Google Play Store from App Gallery and updated to EMUI 9. I'm really at a loss as to what to do now. There aren't any service centres in my city or state. It's also kind of concerning that other people have posted similar issues and with no responses so far.
Bump
Bump again.
s3rialthrill3r said:
Bump again.
Click to expand...
Click to collapse
Tried to boot into recovery (not eRecovery) and do a factory reset from there?
Pretoriano80 said:
Tried to boot into recovery (not eRecovery) and do a factory reset from there?
Click to expand...
Click to collapse
How do I boot into the non-eRecovery recovery (sounds confusing already)?
s3rialthrill3r said:
How do I boot into the non-eRecovery recovery (sounds confusing already)?
Click to expand...
Click to collapse
shutdown phone remove usb cable from it power button + volume up for 5 seconds then release buttons
hamadazh said:
shutdown phone remove usb cable from it power button + volume up for 5 seconds then release buttons
Click to expand...
Click to collapse
I did that, but it still goes to eRecovery.
Try download mode..if it works, with sdcard and dload folder you can flash your last firmware...
manager77 said:
Try download mode..if it works, with sdcard and dload folder you can flash your last firmware...
Click to expand...
Click to collapse
Are you talking about the 'Download the latest version and recovery' option? I always get a ''Getting package info failed' message. Are you saying that I need to put something on an SD card and then choose that option? Where do I get the firmware and which one is the right one?
Bump
I continue searching the solution.
I have 1,5 yers with the same problem.
No I have solution yet.
Tryed Install manny Firmwares with SD card, Format under eRecovery and HiSute.
I already opened it and change the thermal paste.
Tested internal components...
Unfortunely my Huawei Mate 10 is a ALP-AL00 with a special hardware version (6Gb RAM + 128GB ROM), the International version have only 4Gb RAM.
If the Huawei return bootloader unlock i can try instal a custom rom, but without this code my best smartphone was turned into a paperweights.
I have no idea how to unlock his bootloader (The phone have Android 9.0)
I continue searching the solution.
leo.hyde said:
I have 1,5 yers with the same problem.
No I have solution yet.
Tryed Install manny Firmwares with SD card, Format under eRecovery and HiSute.
I already opened it and change the thermal paste.
Tested internal components...
Unfortunely my Huawei Mate 10 is a ALP-AL00 with a special hardware version (6Gb RAM + 128GB ROM), the International version have only 4Gb RAM.
If the Huawei return bootloader unlock i can try instal a custom rom, but without this code my best smartphone was turned into a paperweights.
I have no idea how to unlock his bootloader (The phone have Android 9.0)
I continue searching the solution.
Click to expand...
Click to collapse
Use testpoint (device back needs to be opened again), flash bootloader using DC Phoenix. Then flash board firmware. In board firmware you can use HCU to get an unlock code. You will need to repair device info using HCU after flashing board, as it will wipe it by default.
Here's a guide for fixing device when on board:
1)Flash oeminfo (own backup) from fastboot, or dump oeminfo using dd in adb shell and flash that one back using fastboot.
2)Backup modemnvm_system, modemnvm_factory and modemnvm_backup using adb pull from a command prompt (/dev/block/bootdevice/by-name/modemnvm_system and so on)
3)Flash backed up modemnvm_system, modemnvm_factory and modemnvm_backup from fastboot
3)Modify and brand with HCU (check everything but those that erase/flash empty board) (remember to fill vendor and cust)
4)Direct Unlock Network with HCU (device will find no network if not done)
5)Read Bootloader code if you ever used HCU to get code before
6)Download and flash Oreo service firmware from androidhost.ru using a OTG cable and a memory stick to flash it
After this your device should work fine and you will have an unlock code.
Please note that HCU doesn't work on firmware after May 2018, so don't replace Oeminfo after this as that will remove the unlock code generated by HCU.
leo.hyde said:
I have 1,5 yers with the same problem.
No I have solution yet.
Tryed Install manny Firmwares with SD card, Format under eRecovery and HiSute.
I already opened it and change the thermal paste.
Tested internal components...
Unfortunely my Huawei Mate 10 is a ALP-AL00 with a special hardware version (6Gb RAM + 128GB ROM), the International version have only 4Gb RAM.
If the Huawei return bootloader unlock i can try instal a custom rom, but without this code my best smartphone was turned into a paperweights.
I have no idea how to unlock his bootloader (The phone have Android 9.0)
I continue searching the solution.
Click to expand...
Click to collapse
Maybe it's because...
...
...
...
...there is no solution.
It turns out that my phone was defective. A very good friend of mine happened to be making a trip to Shenzhen anyway, so they offered to take the phone with them to sort it all out. It was taken back to the manufacturer. The motherboard was defective. Since it was within warranty, I got a free replacement.
Hello guys!
I need your help to solve a difficult problem.
In August I bought the Honor 9X STK-LX1 (431) from China.
The device came with Android 9, firmware 9.1.0.334 and security April.The device booted every time with the Honor logo screen and worked normally.
After a few days, I tried to upgrade the software manually via microsd card, using the dload method. I got a softbrick. The device was started, displayed a Huawei logo screen (not Honor logo) and stopped there. Again and again.
I tried many roms for Honor 9X STK-LX1 (C431) but none worked. Hisuite did not recognize the device, adb-fastboot did the same. I also tried eRecovery, it connected to wifi and then it showed "Get package info failed".
After many attempts, now the device is functional, without a keybord installed, but it isn’t a Honor 9X-STK-LX1.
Here are some screenshoots:
I don't know what to do, to restore my phone with the correct firmware....
So we fixed your device.
Honor9x STK has many hardware variants.
It seems yours was STK-L21A hardware variant and was branded Honor STK-L21HN C431 hw/eea.
Problems we got were:
- For your cust region and hardware variant, there is no honor STK-L21HN Emui10 dload available yet, only Huawei STK-L21.
- latest approved LGRP4 B199 online package seems corrupted (CRC). (We did not tested with previous LGRP4 builds)
- LGRP2 online packages are intended for STK-L21A OVS branded Huawei and not Honor.
So, in the end, rebranding your device from STK-L21HN to STK-L21 just did the trick to finally fix your device.
I had to use paying remote softwares to rebrand you and force flash a correct firmware.
With the help of @oslo83, we managed to make the device functional.
Now it works like a charm.
It was not easy at all and oslo83 tried
very much.
I want to thank him for his interest and help.
MOD ACTION:
Thread closed as duplicate of https://forum.xda-developers.com/honor-9x/help/honor-9x-error-preas-xxx-hwproduct-t4178769
So i had a perfectly working bla-a09 which is usa mate 10 pro, it has been collecting dust on the side with no updates, decided to play with it and rebranded to bla-l29 and it rebooted fine and model was changed, but no updates showed when i checked in phone and i decided to update manually and now its bricked. when i connect to pc it is detected and comes up as android sooner single interface and when i type fastboot devices it shows up as fastboot with correct serial number, but the screen is black, tried to flash back to original a09 firmware after extracting various needed img's from update but i get error command not allowed, as this point it looks like i need some kind of testpoint to access phone and bring it back to life, does anyone know of a way to do that, i appreciate it much.
contact with those guys and explain to them your problem..
ministryofsolutions.com