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.
Related
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
Hello together,
today i wanted to rebrand my honor 9 from STF-L00 to STF-L09 and everything worked fine for me at the beginning. I unlock my bootloader and then i used the update.bat and follow the instructions. It installed TWRP. After a while nothing happened and i was still in the fastboot mode. In the fastboot mode i saw that my bootloader is locked again.
Now i have no OS and cannot used adb via fastboot, it does not recognize any device detected.
I downloaded MultiTool and it says i have installed STF-L09 now on my phone.
Info:
According to MultiTool is STF-L09 installed
Bootloader and FRP are locked
I just have Huawei eRecovery, but this is not working (Pacakge info fails)
I have no rom, because my phone is booting only in eRecovery
adb fastboot does not get recognized my phone.
Have all drivers needed on pc for adb to work.
HiSuite doesn't support recovery on this device.
Please help me, i don't know what i should do and i really start to despair. :crying::crying::crying:
Thank you very much
I have pretty much the exact same problem. The only difference is I was trying to rebrand from AL10 to L09. Got the same error in the same stage of rebranding, can access the exact same things as you, same goddamn FRP lock etc. Same all the way through except for starting from AL10 in stead of L00.
I have not found any free solution, the best I could find is DC Phoenix whose program claims that it "Can write firmware by fastboot with locked bootloader and locked FRP!" The thing is, it will cost 15 Euros to use this function in their program, and after paying etc. it is only available for 72 hours. At this moment I don't have access to a computer for the next 72 hours, so I have decided to wait a short while until I have a computer available for a 72-hour period. While I guess it would only take a short time, I realise now that nothing is ever as easy as it seems with Huawei and their absolute **** software... hence I want to wait for being able to use all 72 hours before paying.
This link has their guide to what needs to be done:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
If you want to give it a try, it's the one possible solution I've found after MUCH googling. Though I remain hopeful that someone else on this forum might have a better (free) solution!
Hello Sanktgoran,
at first thank you very much for your help.
I have a question about the DC Unlocker. When i use this and write a new firmware by DC Unlocker, then i don't have to rebrand again?
Which rom do i should use to write on my phone?
Should i use the STF-AL00 rom or STF-L09 rom or it doens't matter?
Multitool says that i have STF-L09 on my phone, but my phone have no OS, because it doesn't boot.
Thanks
I'm not sure actually which one to use. I think you should go with the L09, since that is what the phone "thinks" it is at the moment. If it works to instll the L09 Firmware via DC unlocker, I think that would be the rebranding done as well. The way I understand this situation we are both in, our phones are rebranded to L09, just the actual L09 OS isn't really installed properly, and the FRP lock prevents us from unlocking bootloader, which in turn prevents us from completing the installation of L09. So by using the DC Unlocker to bypass the locks and installing the firmware, the process should then be complete.
I'm not sure about this though, it's just how i think it is. It might be that using DC will install the firmware stably and all is well, and it might be that it will install some of it and then the phone can at least boot into an incomplete OS where we could disable the FRP and bootloader locks, and thus be able to use the Update function in the HWOTA script to get things finished. Either way, I'm 99% sure that using the DC Unlocker will get us further along the path to a european Honor 9 than we are at this stage. I'm going to attempt it later today or perhaps tomorrow I think. After all, 15 euros is a small amount to spend compared to the cost of the actual phone...
Did you also copy an OEMinfo file for L09 into your adb/fastboot folder and run this command before using the HWOTA script?
ADB push oeminfo /tmp/oeminfo
ADB shell "dd if=/tmp/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
I did, I'm not 100% sure what it does/is supposed to do, but I think it has made it so that the phone thinks it's done and rebranded, and tries to boot into L09, but since the L09 installation wasn't completed in the HWOTA script, it can't boot because firmware stuff is missing. That has me thinking that it's the L09 and not AL00 which you should use with DC Unlocker.
Did you check https://forum.xda-developers.com/honor-9/help/soft-bricked-honor-9-trying-to-root-t3737967 ?
Finally, it worked for me everything fine.
Here is one tip from me:
I downloaded at first the rom from a website and started to flash, but it failed.
After a long time of searching and asking, i got help.
You have to download directly from the DC Phoenix the rom (with the custominization file) and flash.
When you don't know how, just post here and i will write a short guide.
Thanks for helping. :good:
That's great, glad things worked out for you! Was it the full firmware file you downloaded from DC Phoenix, the ~4 gigabyte update.app file? Or the three .zip files, update.zip, update_data_full_public.zip and update_full_stf-L09_hw_eu? Do you download it from their website or through the DC Unlocker program? How big was the entire download? I'm on a limited monthly data kind of thing, just curious how big the download is.
Sanktgoran said:
That's great, glad things worked out for you! Was it the full firmware file you downloaded from DC Phoenix, the ~4 gigabyte update.app file? Or the three .zip files, update.zip, update_data_full_public.zip and update_full_stf-L09_hw_eu? Do you download it from their website or through the DC Unlocker program? How big was the entire download? I'm on a limited monthly data kind of thing, just curious how big the download is.
Click to expand...
Click to collapse
I use the download function from DC Phoenix.
When you open DC Phoenix, just click "Download Files" and a website will open, where you can search for the rom.
Search for "STF-L09" and you will get all roms for the STF-L09. I prefer to use this rom:
Stanford-L09_C432B130_Firmware_Belgium_Germany_France_Netherlands_Portugal_Switzerland_Spain_Italy_Aus
And for every rom you should download the customization file. They are directly together:
Stanford-L09_C432B130_update_data_customization_hw_eu.APP
You have to download both .APP files and the both files are in total almost 3,2 GB.
You open DC Phoenix and open the files there.
The Firmware you open in "Update File"
The customization file you open in "Customization File (optional)"
You connect your phone via fastboot and then you can start to update.
I don't know from which country you are, so i don't know which version of rom do you need.
When you download the rom which i downloaded before, you have just the B130 Version. But theres is already B182 existing. You can download the new rom via your phone in the settings.
Here is also the same guide from DC Unlocker (except of the part how you can download the rom).
https://www.dc-unlocker.com/huawei-phone-flashing-in-fastboot
Somehow its possible to flash firmware in dc Phoenix and having a locked Bootloader.
Shouldnt it be possible to use config.txt and flash twrp as recovery and then flash ur full stock?
Im asking cause i m not able to unlock the bootloader. The V+ Button is broke ( Mainboard related) and i cant agree to unlock after entering my code.
A week ago I bought a Huawei mate 10 with box, was second hand but the aesthetically was new, even with their stickers. The seller did not indicate that the phone had gone through a process of rebranding. Just when I get to my house look for a way to update it and I realized that I did not get the updates by OTA watching the version of the cell I realized that in compilation only appears System 8.0.0.38 (O2YJ) and not as usual. ALP-L29C185 for example. Searching the Internet I found out about everything that is the process of rebranding and what happens to my phone is that the person who did the rebranding did not complete the process, because in the end you have to flash the firmware twice and only once did , is there any way I'm going to do this flash without paying funkyhuawei? Since buying a package of 6 credits to only use one seems ridiculous. No matter if it is an advanced tutorial, I have years experience with Android and Xda Thank you wholeheartedly really need ota updates i have One of they first builds. My original phone model are alp-l29 So I think he rebrand did it to give him IMEI As it was probably a live demo model u.u
ed.ge_2d said:
A week ago I bought a Huawei mate 10 with box, was second hand but the aesthetically was new, even with their stickers. The seller did not indicate that the phone had gone through a process of rebranding. Just when I get to my house look for a way to update it and I realized that I did not get the updates by OTA watching the version of the cell I realized that in compilation only appears System 8.0.0.38 (O2YJ) and not as usual. ALP-L29C185 for example. Searching the Internet I found out about everything that is the process of rebranding and what happens to my phone is that the person who did the rebranding did not complete the process, because in the end you have to flash the firmware twice and only once did , is there any way I'm going to do this flash without paying funkyhuawei? Since buying a package of 6 credits to only use one seems ridiculous. No matter if it is an advanced tutorial, I have years experience with Android and Xda Thank you wholeheartedly really need ota updates i have One of they first builds. My original phone model are alp-l29 So I think he rebrand did it to give him IMEI As it was probably a live demo model u.u
Click to expand...
Click to collapse
Is bootloader still unlocked?
If it is this is a lot easier.
If not you'd have to use DC-unlocker/HCU to get unlock code, then you can rebrand manually to your desired cust.
I think you need 4 credits for that, which is $4 and is a lot cheaper than FH.
ante0 said:
Is bootloader still unlocked?
If it is this is a lot easier.
If not you'd have to use DC-unlocker/HCU to get unlock code, then you can rebrand manually to your desired cust.
I think you need 4 credits for that, which is $4 and is a lot cheaper than FH.
Click to expand...
Click to collapse
How do I know if it's unlocked
ed.ge_2d said:
How do I know if it's unlocked
Click to expand...
Click to collapse
Power off phone, hold volume down and plug in usb c cable from computer to phone.
It will enter fastboot mode and should say "Phone unlock" and hopefully "FRP Unlock".
ante0 said:
Power off phone, hold volume down and plug in usb c cable from computer to phone.
It will enter fastboot mode and should say "Phone unlock" and hopefully "FRP Unlock".
Click to expand...
Click to collapse
Phone Locked, frp unlock.
ed.ge_2d said:
Phone Locked, frp unlock.
Click to expand...
Click to collapse
You can get unlock code then through HCU-client (dc-unlocker). It's the only way to get unlock code, but price is only $4 (4 credits) compared to FH which is $40ish.
After you have unlocked phone (from fastboot, 'fastboot oem unlock ##unlock_code##') you could use TWRP by Pretoriano80 (https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904) and HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to finish rebrand (If you know the intended cust), or use HWOTA to rebrand again to your desired cust (HWOTA: https://mega.nz/#!oeATEQQb!qiP3mYlQQgZYlaS3dbY_QCwNJ-urTKyLQ2zKOA9KP8g).
I have lost instructions to HWOTA though, but it should be doable with the command prompt instructions.
If you're unsure about what cust the seller was planning to rebrand to you can dump OEMINFO from TWRP (Advanced -> Terminal -> dd if=/dev/block/platform/ff3c0000.ufs/by-name/oeminfo of=/sdcard/oeminfo.bin )
then transfer to computer and open it in a hex editor. Then search for the string: 'BLA-', and Search for next until you find one which has Cust in it (For example: BLA-L29 8.0.0.127 (C432) says mine at second result.)
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.
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.