So I've been stuck waiting (probably forever) for my carrier (AT&T México) to push out EMUI 9. Been asking in their forums on a release date and they said they don't have one but it's coming "soon" (never).
I'm looking into changing the firmware into stock EMUI (no carrier firmware) so I can get EMUI 9 and future updates (like EMUI 9.1) as soon as they come out.
Thing is, I'm gonna need some really detailed help since this is my first phone and I've never done any of that advanced flashing stuff and whatever on it.
Would really appreciate the help guys
Phone info:
Mate 10 ALP-L09
8.0.0.137 C212
CUSTC212D001
AT&T México (bought through the carrier. Has carrier firmware, not sure if it matters)
Phone also displays this whenever it boots up (I think it means the bootloader is unlocked? Even though I've never tinkered with the phone):
Your device has failed verification and may not work properly.
To learn more, visit:
(forum won't let me post)
----------------------------------------------------------------------------------------------------------
(1) Press Power key to continue.
(2) Press Volume Up key up to 3 seconds to enter erecovery to restore your device.
(3) Your device will stop start, if there is no operation.
----------------------------------------------------------------------------------------------------------
Related
After failing the Debrand following method [VDO-GUIDE] How to debrand Huawei Phone by SRK Tool Huawei by @somboons i'm asking some help or guidance regarding to fix this asap since this is my main phone
This was a C02B131 to C432B161 process
I'll explain (like i did in original thread [VDO-GUIDE] How to debrand Huawei Phone by SRK Tool Huawei):
Quoted:
"Hello,
My Huawei Update Extractor doesnt show P9 Plus in profile. Even if i choose "Unknown" the VERLIST.img code i get is VIE_C900B00 but i'm using C432B161 ROM, is this normal?
So here's the current situation:
Before this procedure i had already the C432B161 inside sccard dload folder.
After the OEMINFO part when phone restarted the normal orange text saying it was unlcked and might be untrustable were in RED and phone started like encripted - i coulndt to a thing but insert the encrypt code so >
> i restarted phone with vol down + power combo key thinking of TWRP but... wrong combo and phone started update the ROM i had already in DLOAD.
> All went OK (surprisly) and everything is working fine but the OTA.
> I moved sucessefull from C02B131 to C432B161 but no OTA"
Thanks!
migueli2 said:
After failing the Debrand following method [VDO-GUIDE] How to debrand Huawei Phone by SRK Tool Huawei by @somboons i'm asking some help or guidance regarding to fix this asap since this is my main phone
This was a C02B131 to C432B161 process
I'll explain (like i did in original thread [VDO-GUIDE] How to debrand Huawei Phone by SRK Tool Huawei):
Quoted:
"Hello,
My Huawei Update Extractor doesnt show P9 Plus in profile. Even if i choose "Unknown" the VERLIST.img code i get is VIE_C900B00 but i'm using C432B161 ROM, is this normal?
So here's the current situation:
Before this procedure i had already the C432B161 inside sccard dload folder.
After the OEMINFO part when phone restarted the normal orange text saying it was unlcked and might be untrustable were in RED and phone started like encripted - i coulndt to a thing but insert the encrypt code so >
> i restarted phone with vol down + power combo key thinking of TWRP but... wrong combo and phone started update the ROM i had already in DLOAD.
> All went OK (surprisly) and everything is working fine but the OTA.
> I moved sucessefull from C02B131 to C432B161 but no OTA"
Thanks!
Click to expand...
Click to collapse
Hi, have you managed to solve the problem?
I had the same situation and after hours of trying I have successfully completed the operation. I can send you the steps I did if you are still stuck.
https://forum.xda-developers.com/showpost.php?p=70812680&postcount=92
Alex91Sc said:
https://forum.xda-developers.com/showpost.php?p=70812680&postcount=92
Click to expand...
Click to collapse
Following the steps you mention in your post, voids warranty?
ehduarte said:
Following the steps you mention in your post, voids warranty?
Click to expand...
Click to collapse
The warranty is invalid just unlock bootloader
When the red text shows, just unlock bootloader again and repeat steps for installing twrp and root.
You don't actually need the update extractor, since you can just type in the version of VIE you'd like to transfer to. ( VIE-L29C185B152 example ). After that just flash the b152 ( or any other rom you've named in step 10 in SRK tool ) using sd card method. When you install stock recovery again you should be recieving OTA updates.
jakiced said:
Hi, have you managed to solve the problem?
I had the same situation and after hours of trying I have successfully completed the operation. I can send you the steps I did if you are still stuck.
Click to expand...
Click to collapse
At the time i got so mad and frustrated that i moved to iPhone 7!
But... You know... Apple have those limitations that i'm not used to, like mirror to TV just by enabling a feature without having to buy a box to do it! The share system PC-over-PHONE etc etc...
So i'm wiling to go back to Huawei and i might get another P9 Plus or Mate 9, still deciding.
But really thanks for the time you spent to reply me to try to solve some one else problem! Really appreciated.
By the way, does P9 Plus operator variants will get Nougat? Couldn't find the confirmation anywhere.
Ah, backstabbing android ?
Yes the Nougat update is coming soon! As official huawei page and chat said to me. It is ought to happen this month so i am eagerly awaiting for it every day. I would strongly suggest you go for a Mate, that is my wish also. Also, you could stick with that bitten apple for a couple of months and grab a Huawei P10 that is also coming with + suffix let's say somewhere in april, may, like the P9 did last year.
Cheers mate, all the best luck in returning to android family ?
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.
Upon a recent travesty of hard-bricking my honor 6X (post here) I searched long and hard for my salvation from brickland. I talked with Huawei support about why the either the EMUI eRecovery or HiSuite Emergency Recover didn't just native work, after all these are options built for these sort of situations right? Well the response I got was ". . .rooting changes and breaks these system." not sure if this is true but hardly believable in my opinion. This lead me to pursue the EMUI eRecovery method as all the other options quickly left me, simple put this was my situation.
Recovery: Stock
Bootloader: unlocked
FRP: locked
OS: corrupted
Admittedly I'm new to the android scene and this posed quite the challenge for me (if there was other ways to get out of this please let me know another solution I could've done). Eventually I did remedy the situation and my question is this:
Is there a method able to complete a EMUI eRecovery without adb, fastboot, a booting OS or an unlocked FRP/bootloader?
Hi!
I bought a TWO brand new Huawei Mate 10 Lite.
Both model: RNE-L21 with Emui 5.1
I updated only one of them with OTA from EMUI 5.1 (RNE-L21C432B133) to EMUI 8.0 (RNE-L21 8.0.0.341(C432))
The only reason why I updated my phone was that they wrote note "The system version can be rolled back to the official version of EMUI 5.1 in Phone Manager".
I don't know if Phone Manager is the same thing as HiSuite but i tried HiSuite and I'm not able to downgrade because it's says that my System is up to date. I've tried many different versions of HiSuite (last one 9.0.2.301) and about 2-5 times I've been lucky to see that option "See other versions" to downgrade (to RNE-L21C432B137CUSTC432D001) but anyway when downloading come up to 100% its end with error "Failed to update".
*Edit* - HiSuite and See other versions problem solved
I've seen on forum that alot of people had problem with downgrading in HiSuite and annoying message "System is up to date". They wasn't able to see option "See other versions" to downgrade. I spend many hours today to find out why sometimes I can downgrade and mostly not. To solve this problem I took out my simcard, switched off wifi and enabled airplain mode. Now HiSuite is letting me to choose firmware but when downloading is complete, phone disconnect with error "Failed to update".
As i said they are both new with warranty so I also tried to contact customer service and a guy said that I can't roll back. I told him about message before update but he ignored to comment that so I asked about HiSuite problem and his answer was "if HiSuite doesn't let me downgrade so he cannot do anything more about it"
Now I wanna ask you, what should I or can I do about it?
They shouldn't write that I can rollback if i cannot.
BL is also locked and they don't gives keys to unlock anymore. How to rollback?
Hope you help me guys.
Sorry for mistakes. English is not my mother language.
Best regards
paxsu said:
Hi!
I bought a TWO brand new Huawei Mate 10 Lite.
Both model: RNE-L21 with Emui 5.1
I updated only one of them with OTA from EMUI 5.1 (RNE-L21C432B133) to EMUI 8.0 (RNE-L21 8.0.0.341(C432))
The only reason why I updated my phone was that they wrote note "The system version can be rolled back to the official version of EMUI 5.1 in Phone Manager".
I don't know if Phone Manager is the same thing as HiSuite but i tried HiSuite and I'm not able to downgrade because it's says that my System is up to date. I've tried many different versions of HiSuite (last one 9.0.2.301) and about 2-5 times I've been lucky to see that option "See other versions" to downgrade (to RNE-L21C432B137CUSTC432D001) but anyway when downloading come up to 100% its end with error "Failed to update".
*Edit* - HiSuite and See other versions problem solved
I've seen on forum that alot of people had problem with downgrading in HiSuite and annoying message "System is up to date". They wasn't able to see option "See other versions" to downgrade. I spend many hours today to find out why sometimes I can downgrade and mostly not. To solve this problem I took out my simcard, switched off wifi and enabled airplain mode. Now HiSuite is letting me to choose firmware but when downloading is complete, phone disconnect with error "Failed to update".
As i said they are both new with warranty so I also tried to contact customer service and a guy said that I can't roll back. I told him about message before update but he ignored to comment that so I asked about HiSuite problem and his answer was "if HiSuite doesn't let me downgrade so he cannot do anything more about it"
Now I wanna ask you, what should I or can I do about it?
They shouldn't write that I can rollback if i cannot.
BL is also locked and they don't gives keys to unlock anymore. How to rollback?
Hope you help me guys.
Sorry for mistakes. English is not my mother language.
Best regards
Click to expand...
Click to collapse
Hi, try Firmware finder from Play Store, version 9.7 Select RNE-L21C432B137 firmware from 2018.06.02 N* 160963 . Use eRecovery method (recommended for Oreo). GL!
I would appreciate anyones help. I have a Huawei Mate 20 Pro Model LYA-L29. When I run the commands it tells me this about my Firmware Version:
VENDORCOUNTRY: HW/SPSEAS
BASE VERSION: LYA-LGRP2-OVS 9.1.0.357
CUSTOM VERSION: LYA-L29-CUST 9.1.0.11 (AUSC636)
OEMINFOREAD: LYA-L29-PRELOAD 9.0.0.1(C636R2)
I want to upgrade to EMUI 10 but whenever I try using HiSuite, HiCare App on Phone it says my version is up to date.
Is there any way to upgrade this phone? I have not unlocked the Bootloader because Huawei is not issuing Codes to do so.
I'd appreciate anyones help with this.
Thanks
i have the same problem
Hello, same issus here
1st thing i would try is to contact huawei support chat.
now the more extreme diy method may break safetynet and stop things such as google pay from working. if you decide to try it, you have been warned.
you can manually force an update through USB OTG.
there is a thread on this forum called "How to update Huawei Mate 20 Pro With Locked Bootloader"
it has the information you need to get it to work.
for the greatest chance of success, you want a firmware with the same cust/preload region as yours
(in the case of the OP this would be C636R2)
note, this can only be done with full firmware files, not updates.
you can use an app called "firmware finder for huawei" (play store) which you can use to find and download the full firmware file.
also, forcing the incorrect firmware will brick your phone. very easy to get confused and try to force a firmware meant for another model completely.
theoretically L29 and L09 variants should both work, however your dual sim functionality might stop working.
I did this sort of thing last year and haven't looked at it for a very long time, just giving some info which may get you on the path if you wish to try the diy method.
ANyone tried? how was it? does it work
xeroxide said:
1st thing i would try is to contact huawei support chat.
now the more extreme diy method may break safetynet and stop things such as google pay from working. if you decide to try it, you have been warned.
you can manually force an update through USB OTG.
there is a thread on this forum called "How to update Huawei Mate 20 Pro With Locked Bootloader"
it has the information you need to get it to work.
for the greatest chance of success, you want a firmware with the same cust/preload region as yours
(in the case of the OP this would be C636R2)
note, this can only be done with full firmware files, not updates.
you can use an app called "firmware finder for huawei" (play store) which you can use to find and download the full firmware file.
also, forcing the incorrect firmware will brick your phone. very easy to get confused and try to force a firmware meant for another model completely.
theoretically L29 and L09 variants should both work, however your dual sim functionality might stop working.
I did this sort of thing last year and haven't looked at it for a very long time, just giving some info which may get you on the path if you wish to try the diy method.
Click to expand...
Click to collapse