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
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.
I'll keep this short, as I don't want to waste anyone's time. 2 days ago I installed an OTA update on my Honor 8 while I had TWRP installed. I didn't know it was a red no-no when I did that and I now regret it.
I've looked for help on reddit but that got me nowhere as there are not that many Android support subreddits and the existing ones are not that active. I know that I have to flash my phone with the right firmware, but I can't seem to find the right one, as there are many different versions, such as OTA updates, FullOTA, as well as the region code. Then there's the issue of flashing. Every kind of unbricking video I've watched, flashes the firmware of their device using an SD card. I don't have a microSD card reader, so I don't even know how I'll get the firmware on it. I'd prefer to use something like adb platform tools to flash the firmware, but if it isn't possible that way, I guess I'll buy an SD card and use someone else's setup to move the firmware.
My phone's model number is FRD-L09, it was running Android 7.0 and EMUI 5.0. I don't know the region code, but I bought the device from an UK supplier, but on the back of the phone's box, it says Huawei Technologies (Netherlands).
Any kind of help would be greatly greatly appreciated!!
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
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.)
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.