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 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
Hello everyone, I'm new here and I'm looking for help for my P8 lite 2017 Pra-Lx1 L31.
I flashed wrong costomrom, now starts for 2 rectangles blue and green then passes
for eRecovery in Chinese
I have already tried to update for wi-fi and it gives error in the search of the server.
I can access the fastboot mode and I have the unlocked bootloader and the frp locked.
I can not install TWRP through fastboot.
I have already tried UPDATE.APP by dload mode and it gives error or stops at 5%.
I already used several tutos here of the forum but nothing solved.
Has this ever happened to anyone? How can I solve ?
I thanked a charitable soul. :crying::crying::crying:
Edit : Solved
It was days of exaltation and headaches but at last I managed to find the thing.
With a lot of searching I found on the net 1 firm compatible, I did the dload method
* then wipe / data reset, installed TWRP and backed up. Again data reset and
replaces the backup of another PRA-LX1 from a friend.
Voila, I updated and now I have the impeccable PRA-LX1 8.0.0.385 (C432).
The version that had before the brick was PRA-LX1 8.0.0.046 (OC71).
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?
Hi.
I have Huawei P9 with bootloader unlocked and firmware version: 8.0.0.046 (0OHZ).
First i update to
EVA-AL10b399Sp17a /Android 7 (this Firmware is required for the Update to Oreo)
then i update to
EVA-AL10C00B540 (8.0.0.540) /Android 8 Oreo
I believe I have not correctly rebranding from EVA-L09 to EVA-AL10 then firmware version is 8.0.0.046 (0OHZ) and not 8.0.0.540
Then i installed TWRP for Oreo (This TWRP is made by @Pretoriano80 for Honor 9 Lite)
Now the phone no longer enters recovery and does not start .. It restarts in loop remaining on the "your device has been unlocked and can't be trusted" screen.
Help me please
Help Please
amo74 said:
Hi.
I have Huawei P9 with bootloader unlocked and firmware version: 8.0.0.046 (0OHZ).
First i update to
EVA-AL10b399Sp17a /Android 7 (this Firmware is required for the Update to Oreo)
then i update to
EVA-AL10C00B540 (8.0.0.540) /Android 8 Oreo
I believe I have not correctly rebranding from EVA-L09 to EVA-AL10 then firmware version is 8.0.0.046 (0OHZ) and not 8.0.0.540
Then i installed TWRP for Oreo (This TWRP is made by @Pretoriano80 for Honor 9 Lite)
Now the phone no longer enters recovery and does not start .. It restarts in loop remaining on the "your device has been unlocked and can't be trusted" screen.
Help me please
Click to expand...
Click to collapse