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.
Hello.
Some time ago I assumed a topic about the brick of my phone, Mate 10 Lite, I managed to bring it to life through the dc_phoenix program. The only version of the system they had was EMUI 5.1.
I'd like to have 8.0.0 to install LineageOS. But I do not have the code for the bootloader, dc_unlocker and HCU shows that it does not detect the phone. HWOTA needs this code to update. Is it possible to get this code somehow differently? Thanks for the help.
bielawnyf said:
Hello.
Some time ago I assumed a topic about the brick of my phone, Mate 10 Lite, I managed to bring it to life through the dc_phoenix program. The only version of the system they had was EMUI 5.1.
I'd like to have 8.0.0 to install LineageOS. But I do not have the code for the bootloader, dc_unlocker and HCU shows that it does not detect the phone. HWOTA needs this code to update. Is it possible to get this code somehow differently? Thanks for the help.
Click to expand...
Click to collapse
Are you sure you enabled Manufacture mode?
Also, phone needs to be booted, not in fastboot
Edit; you might have to install drivers for it, they have a button in HCU/DC named Support or something, that will open a website with drivers and such. I can't remember exactly which one I used because there was 10 or so to choose from. I think it was the most recent anyway. After you have got unlock code you'll have to uninstall driver, it breaks MTP support.
Edit 2: it's named Huawei_Android_phone_drivers_2.zip and location is Other downloads / Drivers / Huawei / Phones
But you need to open Support Area link from DC/HCU, it won't let you download if you're not logged in using the program
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.
I'm trying to downgrade from 9.1 to any version that allows a bootloader unlock..
I've got a (P20 Lite) (64gb);
ANE-LX1 build 9.1.0.231 (C782E5R1P7)
EMUI 9.1.0
I believe that the C782 refers to the fact it's a UK version and ProjectMenu verifies this:
Vendor: o2
Country: uk
I tried downgrading via HiSuite, except that it gives me no options to downgrade and simply states that I'm up to date.
I also tried putting various firmwares into a dload folder and install via the ProjectMenu sdcard update
as well as a forced update (holding +&- and power whilst booting).
Both methods failed....
I've only used firmwares with 782 in them i.e
Huawei P20 Lite ANE Anne-L21 8.0.0.143(C782) Firmware Android 8.0.0 EMUI 8.0.0 05015EHQ androidhost.ru
or
Huawei P20 Lite ANE-LX1 ANE-L21 Anne-L21 8.0.0.150(C782) Firmware 8.0.0 r1 EMUI8.0 05015EHQ androidhost.ru
I noticed the firmwares were (vendor) hw and (country) eu, maybe this is why the updates are failing?...
I believe there is a way to change the vendor & country to match on the phone to match the firmware I want to install, but I couldn't manage that either...
What am I doing wrong?
Can somebody please verify that I am (at least) using the right firmware(s) or that I could try other firmwares?
Any help/guides greatly appreciated
Thanks
cant help much, but, you can try region change thing from dc unlocker region vendor cange info
here are first site i find at dc unlocker repair info
have not tried with p20 lite, but used with p9 and all worked, ofcorse, there can be driver problems if use windows 10, so, turn off driver signature before instal some drivers related!
Arnys said:
cant help much, but, you can try region change thing from dc unlocker region vendor cange info
here are first site i find at dc unlocker repair info
have not tried with p20 lite, but used with p9 and all worked, ofcorse, there can be driver problems if use windows 10, so, turn off driver signature before instal some drivers related!
Click to expand...
Click to collapse
Thanks for tho reply and the links & tips, I 'll have a look through them.
I'm pretty sure the drivers are installed correctly as I can communicate over ADB & fastboot. I'll double-check anyway
Hey there! First post.
Before Huawei stopped giving unlock codes in 2018 I got mine but I never unlocked because of warranty. Now I really want to unlock but from EMUI 9 onwards (I have 10.0.0.202(C432E9R1P3) installed) they removed the possibility of unlocking via the
Bash:
fastboot flashing unlock
command. I spoke today with Huawei technical support and they confirmed that, without rolling back to EMUI 8, I will not be able to unlock even with the code.
This leads us to the second issue: I cannot rollback via HiSuite, it does not show me the "other versions" button that could roll me back. Huawei support told me that button is the only official way and as it is now it is impossible for me to do a rollback due to security concerns of old EMUI versions. He also told me that the unofficial way is to install the system myself in someway he could not help me with.
I tried everything I could find online and everything I could think of but nothing worked: How do I rollback to EMUI 8 to get the unlock work?
Thanks in advance