Related
Hi guys
Someone has succeeded with downgrade from oreo to nougat ? I need go to huawei service, to exchange the display, but problem is "relocked bootloader"
So many tutorials here, which to follow for downgrade and have "locked bootloader" ?
You can use HiSuite or install the downgrade firmware through Firmware Finder. It has the normal Nougat version, but in the description it tells that it downgrades.
HiSuite tells me that I have the latest version so.. I cant downgrade from HiSuite, or if i can tell me how to do it please
@yungshadow
As M1chiel said, try with Firmware Finder.
Remember!! Everything is on your own risk!!
Don't know which version you have, but for me this is the roll back firmware...
Let's try. But.. still 0%
If you use proxy option, you have to set proxy in WiFi settings.
localhost and 8080
Then start download and wait until 4-5%, then disable proxy and continue download.
i'm using DNS. Now 11% XD
ok i'm finally have emui 5. Now i must rebrand ?
That I don't know, I already didn't understand why you wanted to downgrade ??
yungshadow said:
ok i'm finally have emui 5. Now i must rebrand ?
Click to expand...
Click to collapse
Look here: https://forum.xda-developers.com/p10/how-to/huawei-p10-debrand-rebrand-update-guide-t3691013/page38
Can't do anything with this trash device, even TWRP fails to install. What a waste of money!
djg269 said:
That I don't know, I already didn't understand why you wanted to downgrade
Click to expand...
Click to collapse
I need to have bootloader status "locked" not "relocked" so i must rebrand to l09 and back to l29 yeah?
Ok guys
I Found a solution.
1. Downgrade from Oreo via FF using B185 (downgrade firmware) thanks
djg269 said:
2. Download some L09 firmware and install via FF
3. After installing I had bootloop (huawei logo, booting system for 10-15 sec and still restarting)
4. Enter eRecovery VOL-UP + POWER > Wipe data and cache
5. After Wipe phone said it's still L29 but now bootloader is locked not relocked
So i'm done now
Click to expand...
Click to collapse
Glad you got it fixed!!
Sent from my VTR-L09 using XDA Labs
I have a small question - in FF it says to make sure my current version is not "unlocked" - does that mean the bootloader or...? I just want to downgrade to B180 so I can install HuShed. I'm on L29C432B360 currently.
I don't remember this information. Could u send here Screenshoot with that dialog from FF ?
Same screenshot as post #4 -> https://forum.xda-developers.com/showpost.php?p=76556011&postcount=4
I used b185 from b360 with unlocked bootloader and I had no problems.
You should use b185(rollback firmware) and after this will be able toinstall whatever you want
Alright, last question - I have TWRP installed for 8.0. Will this affect the downgrade somehow? Because for example I can't install OTAs with TWRP. I'm sorry I'm kinda new to these kinds of stuff.
I didn't have installed twrp for 8.0 when i Decided to do downgrade so I think it doesn't matter but you can flash stock recovery for 8.0 if u want ofc.
Now i'm on 8.0.0.365(c432) but with official OTA update
I've gone through the process of entering my IMEI and serial number in the EMUI bootlocker website and its given me a code.
I haven't yet done any further steps including the adb commands required to remove the blootlock.
However I can now see on the MT Huawei Firmware update list that there is a new update (128) and I'm on (120b)
I've tried using the VPN option to force the update to obtain the firmware from its own servers to no avail.
The firmware checker simply states the firmware isn't compatible with device.
..has somehow simply registering caused it to be blocked for future updates?
##Secondly##.. Does continuing the process and using abd unblock commands cause it to no longer work with OTA?
Or is it only when and if you root it - that OTA can not work? (or does it work)
Quite confused and would really appreciate any advice as ideally I would like to keep OTA, but have root at sometimes with the hope that I could disable root anytime a OTA updates comes available and then re-enable after.
Any advice greatly appreciated )
dgoncalves81 said:
I've gone through the process of entering my IMEI and serial number in the EMUI bootlocker website and its given me a code.
I haven't yet done any further steps including the adb commands required to remove the blootlock.
However I can now see on the MT Huawei Firmware update list that there is a new update (128) and I'm on (120b)
I've tried using the VPN option to force the update to obtain the firmware from its own servers to no avail.
The firmware checker simply states the firmware isn't compatible with device.
..has somehow simply registering caused it to be blocked for future updates?
##Secondly##.. Does continuing the process and using abd unblock commands cause it to no longer work with OTA?
Or is it only when and if you root it - that OTA can not work? (or does it work)
Quite confused and would really appreciate any advice as ideally I would like to keep OTA, but have root at sometimes with the hope that I could disable root anytime a OTA updates comes available and then re-enable after.
Any advice greatly appreciated )
Click to expand...
Click to collapse
It is NOT related with unlocked bootloader or rooted firmware.
It's related with emui 8.1 version whitch is NOT supported by FirmwareFinder.
So basically VPN or Proxy wont work with that.
Another thing: the firmwares listed on FF aren't approved at appearance date. This means that we must wait a bit for approval, and after that can FF download the selected firmware (again, emui 8.1 is not supported).
If you are in hurry with flashing the new firmwares, you can via TWRP (methods described on forum).
BUT be aware, that even with that you can brick your phone
(trust me: after 2 days, when i brought my phone, it was hardbricked... i haven't other choice but RMA, and obviously they have changed the phone. SO be very careful.)
tamaskurti said:
It is NOT related with unlocked bootloader or rooted firmware.
It's related with emui 8.1 version whitch is NOT supported by FirmwareFinder.
So basically VPN or Proxy wont work with that.
Another thing: the firmwares listed on FF aren't approved at appearance date. This means that we must wait a bit for approval, and after that can FF download the selected firmware (again, emui 8.1 is not supported).
If you are in hurry with flashing the new firmwares, you can via TWRP (methods described on forum).
BUT be aware, that even with that you can brick your phone
(trust me: after 2 days, when i brought my phone, it was hardbricked... i haven't other choice but RMA, and obviously they have changed the phone. SO be very careful.)
Click to expand...
Click to collapse
Via twrp? What method? Depending on the device type you would have to debrand first
dladz said:
Via twrp? What method? Depending on the device type you would have to debrand first
Click to expand...
Click to collapse
The method I was referring is with HuRUpdater.
HuRupdater Thread
tamaskurti said:
The method I was referring is with HuRUpdater.
HuRupdater Thread
Click to expand...
Click to collapse
Have you used this before? On the P20 Pro?
Only reason i ask is the P20 Pro is not listed on the supported devices and as i said you would need to have the correct firmware for your device, the newer firmwares are made for the European version of the device L29 not L09, so providing you're on L29 and it's the correct firmware then it should work, but i would not like to be the person to crash test this.
I'm on the L09 which doesn't take L29 firmwares unless i debrand and then try it.
I have CLT-L29C432B128. (I have updated with hurupdater since the 128 fw is not yet approved from firmware finder)
I thinking on try flashing cn firmware.
tamaskurti said:
It is NOT related with unlocked bootloader or rooted firmware.
It's related with emui 8.1 version whitch is NOT supported by FirmwareFinder.
So basically VPN or Proxy wont work with that.
Another thing: the firmwares listed on FF aren't approved at appearance date. This means that we must wait a bit for approval, and after that can FF download the selected firmware (again, emui 8.1 is not supported).
If you are in hurry with flashing the new firmwares, you can via TWRP (methods described on forum).
BUT be aware, that even with that you can brick your phone
(trust me: after 2 days, when i brought my phone, it was hardbricked... i haven't other choice but RMA, and obviously they have changed the phone. SO be very careful.)
Click to expand...
Click to collapse
Thanks for the advice!
So the list if updates that firmware finder shows are upcoming updates - rather than being released for offical OTA distrubtion from the date listed?
If firmware finder gets it first I'm wondering if you know generally when the OTA updates start to be pushed out via the OTA update system?
I don't know.
Generally about 2-3 weeks (maybe less).
Hi
I'm unable to change the firmware on my BLA-L29 C432 B142 May security patch (rebranded from C636 about 6 months ago).
Checking OTA just says 'no updates available' and if I try to update via FunkyHuawei using eRecovery it downloads but after 'verifying' it moves on to 'recovery system running' and then errors with the message 'recovery failed' when it gets to 1%.
I've tried quite a few things to try and get something to move on, but it seems like I'm stuck on an old version of firmware and no way to change it. I need a new plan.
I've tried (with lots of factory resets and wiping cache inbetween):
- OTA updates - always says no update available.
- Via FunkyHuawei:
- Reflash same firmware (eRecovery fails during 'recovery system running')
- Reflash newer or older firmare in same region (eRecovery fails during 'recovery system running')
- Change region, reflash newer or older firmware in same region (eRecovery fails during 'recovery system running')
- Use unbrick tool to flash same or different firmware in both same and different regions (unbrick tool completes but firmware version always stays the same in about phone, the android security patch date changes though, but eRecovery won't let me reflash anything afterwards as eRecovery fails during 'recovery system running')
- The last OTA update I got was C432 .137. When everyone else was getting .145 OTA I got Firmware Finder to move me from .137 to .142.
Has anyone got any ideas on what to do next? I don't want to be stuck on the same firmware version and security patch forever.
Other than the FunkyHuawei rebrand about 6 months ago from C636 to C432, the phone is standard (no attempt to unlock bootloader, root).
I was thinking of:
- Unlock bootloader using DC unlocker (from what I've read this might still work as I'm on B142 which has a May security patch)
- Flash TWRP
- Flash a custom ROM
- Try and restore back to stock
- Possibly rebrand back to factory original C636 as there seem to be a few threads about rebranded phones not getting updates promptly, but I can't see anyone else who is getting eRecovery failing no matter what they do and no way to change firmware. I have already tried rebranding back to C636 via FH, but can't, as eRecovery fails at the same point when trying to flash the C636 firmware.
Funky should always work to update, check that DNS is correct when you enter that test site.
- Unlock bootloader using DC unlocker (from what I've read this might still work as I'm on B142 which has a May security patch)
Click to expand...
Click to collapse
This will work. I have downgraded and tested it
You could do this:
Get unlock code
Unlock bootloader
Flash TWRP (https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904)
Download firmware update.zip, public and hw zip from http://pro-teammt.ru/firmware-database/
Update to the version you want using HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279).
You will stay bootloader unlocked now though, but the rest is stock.
ante0 said:
Funky should always work to update, check that DNS is correct when you enter that test site.
Click to expand...
Click to collapse
The DNS is fine and I can load the test sites, eRecovery gets info and downloads the firmware labelled "FunkyHuawei" and the size is around 3GB. After taking a few minutes to download, the eRecovery moved on to 'verifying package', that completes, it moves on to 'recovery system running' and after it gets to 1% it says 'recovery failed'.
ante0 said:
This will work. I have downgraded and tested it
You could do this:
Get unlock code
Unlock bootloader
Flash TWRP (https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904)
Download firmware update.zip, public and hw zip from http://pro-teammt.ru/firmware-database/
Update to the version you want using HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279).
You will stay bootloader unlocked now though, but the rest is stock.
Click to expand...
Click to collapse
I will try this, anything to get me out of the hole I seem to be stuck in as all methods I've tried so far rely on eRecovery. Thankyou for all of the links.
When using HuRUpdater does it have to be in the same region, or can I rebrand at the same time?
Thasscas44 said:
The DNS is fine and I can load the test sites, eRecovery gets info and downloads the firmware labelled "FunkyHuawei" and the size is around 3GB. After taking a few minutes to download, the eRecovery moved on to 'verifying package', that completes, it moves on to 'recovery system running' and after it gets to 1% it says 'recovery failed'.
I will try this, anything to get me out of the hole I seem to be stuck in as all methods I've tried so far rely on eRecovery. Thankyou for all of the links.
When using HuRUpdater does it have to be in the same region, or can I rebrand at the same time?
Click to expand...
Click to collapse
HuRUpdater can only handle same region updates as far as I know.
You can use HWOTA to rebrand, but mankindtw (original author) has since edited the thread as he thought his tool bricked devices. But it was firmware that caused it.
And I can't remember the exact steps... You have to flash twice though, first to rebrand (example C636) and then to update to the same rebranded (C636) firmware.
https://mega.nz/#!oeATEQQb!qiP3mYlQQgZYlaS3dbY_QCwNJ-urTKyLQ2zKOA9KP8g
You could use FHRebrand tool, but it will change your bootloader unlock code so you'd have to use HCU client (DC-unlocker) twice to get it.
Also, before flashing anything, check xloader with this tool: https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
For now, stay on XLOADER 01 firmware. We don't know if Huawei will change to 02. Going from 02 to 01 will end in a hard brick.
B142 is 01 so you're safe now
Thanks to your advice, I have a plan now. And good to know about the xloader stuff, that could have ruined my day.
I'm going to:
1. Get bootloader code [update: done using dc-unlocker, confirmed working on C432 .142]
2. Flash TWRP
3. Put same region and slightly downgraded version of firmware on to a USB and flash with HuRUpdater (assuming it needs to be put on a USB OTG stick as the M10Pro doesn't have an SD card). I intend to use the downgraded version so I can see the version successfully change in "about phone"
4. Rebrand using FH tool (if there's less chance of bricking than HWOTA) and keeping an older firmware
5. Hopefully it works, and [after getting the bootloader code again from dc-unlocker in case I need it in future] I will be able to update via OTA to latest official firmware
Hopefully starting again completely will overwrite whatever it is that's getting me stuck.
Thanks to @ante0 I got out of the hole I was in.
From what I've tested, there seems to be an inability to update OTA from a rebranded BLA-L29 432 running 137 or 142.
Here's what I did.
1. Unlocked bootloader, flashed twrp, flashed downgraded 137 version of C432 with hrupdater. Success. No offer of an OTA update though so still stuck on old version.
2. Ran FH rebrand tool to change region to the factory original C636. eRecovery failed at the same stage as before. Fail.
3. Kept region as C636, unlocked bootloader and flashed twrp again. Flashed April version of C636 firmware using hrupdater, twice. Success.
4. Immediately on boot up phone offered to update OTA to the latest version of C636 firmware. Success.
It seems that the phone wouldn't offer an update OTA if on rebranded C432 and running 137 or later, but did offer OTA when it was back on C636. I live in Europe, but will keep the 636 region if it means I get OTA, else I can't pass the phone on.
Now to relock the bootloader so banking apps work. Plan to use the fastboot relock command followed by dc unlocker relock tool. Hoping not to brick at the last stage!
So I did a hard reset after relocking my bootloader in order to install my new update (EVA-L09C150B375). I successfully relocked it, then resetted it. However, after I turned it on to install the update and restore it from HiSuite, I was welcomed with the EMUI starting screen (language selection, T&C, wifi, google account) and I'm stuck there. The thing is, all my keyboards are lost and whenever I want to type in something, only the google voice button shows which I can't possibly use to enter passwords or pin. If I skip everything and 'set up as new phone', it brings me to the 'add fingerprint' scene which if I skip, I'm brought all the way back to the beginning of the WHOLE proccess (back to the EMUI logo), and I can't add a fingerprint because you have to give either a PIN or a password in order to be able to use it. I have Wi-fi connection but nothing else. I can't bring up any menus. When I do a hard reset, it bring me to this page again after rebooting. Is there a workaround? I'm completely lost.
horesz1994 said:
So I did a hard reset after relocking my bootloader in order to install my new update (EVA-L09C150B375). I successfully relocked it, then resetted it. However, after I turned it on to install the update and restore it from HiSuite, I was welcomed with the EMUI starting screen (language selection, T&C, wifi, google account) and I'm stuck there. The thing is, all my keyboards are lost and whenever I want to type in something, only the google voice button shows which I can't possibly use to enter passwords or pin. If I skip everything and 'set up as new phone', it brings me to the 'add fingerprint' scene which if I skip, I'm brought all the way back to the beginning of the WHOLE proccess (back to the EMUI logo), and I can't add a fingerprint because you have to give either a PIN or a password in order to be able to use it. I have Wi-fi connection but nothing else. I can't bring up any menus. When I do a hard reset, it bring me to this page again after rebooting. Is there a workaround? I'm completely lost.
Click to expand...
Click to collapse
First of all, unlocked bootloader does not prevent OTA - for OTA you must have stock recovery and stock boot partition (no root) but you can have bootloader unlocked.
Only thing - successful OTA may lock your bootloader back (depending if such a flag is present in stock update.zip or not) but again, you can safely start OTA with the unlocked bootloader.
Don't know why so many people go to relock bootloader before accepting OTA, which triggers hard reset and potentially troubles.
Did you at least leave OEM unlocked (OEM/FRP unlock also does not prevent OTA), that you can unlock bootloder again, install TWRP and revive your system by eg HWOTA method?
About missing keyboard - when you had your previous rooted system, have you disabled/removed Huawei default keyboards: SwiftKey and Swipe for Huawei - after hard reset it looks only for them, without them you have no keyboard...
Also, before hard resetting, have you removed fingerprint protection you have had?
Generally, if you removed fingerprint before hard reset, you should be able to skip setting the fingerprint.
I had a similar situation (no keyboard upun hard reset), and I was able to skip fingerprint, set-up a new system and then to install GBoard from apk on SD card and to continue.
zgfg said:
First of all, unlocked bootloader does not prevent OTA - for OTA you must have stock recovery and stock boot partition (no root) but you can have bootloader unlocked.
Only thing - successful OTA may lock your bootloader back (depending if such a flag is present in stock update.zip or not) but again, you can safely start OTA with the unlocked bootloader.
Don't know why so many people go to relock bootloader before accepting OTA, which triggers hard reset and potentially troubles.
Did you at least leave OEM unlocked (OEM/FRP unlock also does not prevent OTA), that you can unlock bootloder again, install TWRP and revive your system by eg HWOTA method?
About missing keyboard - when you had your previous rooted system, have you disabled/removed Huawei default keyboards: SwiftKey and Swipe for Huawei - after hard reset it looks only for them, without them you have no keyboard...
Also, before hard resetting, have you removed fingerprint protection you have had?
Generally, if you removed fingerprint before hard reset, you should be able to skip setting the fingerprint.
I had a similar situation (no keyboard upun hard reset), and I was able to skip fingerprint, set-up a new system and then to install GBoard from apk on SD card and to continue.
Click to expand...
Click to collapse
I couldn't install the new update when I was unlocked, because it went into a boot loop. That's why I decided to start over with a clean page. I haven't disabled any keyboards and I haven't removed my fingerprint.
horesz1994 said:
I couldn't install the new update when I was unlocked, because it went into a boot loop. That's why I decided to start over with a clean page. I haven't disabled any keyboards and I haven't removed my fingerprint.
Click to expand...
Click to collapse
You couldn't install OTA not because of unlocked bootloader per se, but because of TWRP or root.
You better had to remove fingerprint before forcing to relock bootloader.
Did you leave OEM (FRP) unlocked (it doesn't affect OTA anyhow) - then boot to Fastboot, unlock bootloader, install TWRP and use HWOTA to flash complete firmware
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Otherwise, if you could get over fingerprint, boot to the system and install GBoard (download the apk on the PC or another phone and put it to the SD card)
Last option, rollback to MM and then upgrade by OTAs to the latest Nougat.
zgfg said:
You couldn't install OTA not because of unlocked bootloader per se, but because of TWRP or root.
You better had to remove fingerprint before forcing to relock bootloader.
Did you leave OEM (FRP) unlocked (it doesn't affect OTA anyhow) - then boot to Fastboot, unlock bootloader, install TWRP and use HWOTA to flash complete firmware
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Otherwise, if you could get over fingerprint, boot to the system and install GBoard (download the apk on the PC or another phone and put it to the SD card)
Last option, rollback to MM and then upgrade by OTAs to the latest Nougat.
Click to expand...
Click to collapse
The problem is, I have no way of accessing the file system.
Take out SD card, put on DLOAD for rollback to MM.
zgfg said:
Take out SD card, put on DLOAD for rollback to MM.
Click to expand...
Click to collapse
I will try this, thank you! where can I find the correct rom for my phone model?
horesz1994 said:
I will try this, thank you! where can I find the correct rom for my phone model?
Click to expand...
Click to collapse
Firmware Finder
zgfg said:
Firmware Finder
Click to expand...
Click to collapse
Okay, so I've tried b136 and b167 (the two most common in these solutions in this forum), and both of them went to 5% and then came an error message:
“Incompatibility with current version. Please download the correct update package”
I'm truly lost now. Any ideas? Should I try every single package for the L09?
horesz1994 said:
Okay, so I've tried b136 and b167 (the two most common in these solutions in this forum), and both of them went to 5% and then came an error message:
“Incompatibility with current version. Please download the correct update package”
I'm truly lost now. Any ideas? Should I try every single package for the L09?
Click to expand...
Click to collapse
Here is a proven rollback guide
https://forum.xda-developers.com/showpost.php?p=73448165&postcount=371
Skip steps 7-8.
In step 9 you should get OTA updates till b504 for L09 (b399 for L19).
Steps 11-13 are about rooting by SuperSU, not part of rollback.
PS: This guide is for L09/L19 c432 - if your phone was diff cust, you should rebrand or use b182 for your cust (not b182 for c432 as in the guide - you should look for the appropriate FullOTA-MF-PV build in Firmware Finder - MUST be FullOTA-MF-PV MM for your cust)
zgfg said:
Here is a proven rollback guide
https://forum.xda-developers.com/showpost.php?p=73448165&postcount=371
Skip steps 7-8.
In step 9 you should get OTA updates till b504 for L09 (b399 for L19).
Steps 11-13 are about rooting by SuperSU, not part of rollback.
PS: This guide is for L09/L19 c432 - if your phone was diff cust, you should rebrand or use b182 for your cust (not b182 for c432 as in the guide - you should look for the appropriate FullOTA-MF-PV build in Firmware Finder - MUST be FullOTA-MF-PV MM for your cust)
Click to expand...
Click to collapse
Will do, but I have one more question; how do I find out my model number(cust)? the box only shows the IMEI and that it's EVA-L09 and nothing else. I can't access phone details in the phone itself because of the original problem.
I see for my L09c432 in this file:
/cust/hw/eu/prop/local.prop
at the end:
ro.comp.cust_version=Cust-432000 5.0.0.1(0001)
You can probably (never did myself) copy it by ADB commands to PC and read.
Maybe you need to unlock bootloader to get access.
In that case you can also install TWRP and copy the file to SD card, and then open it on the PC
PS: I usually save screenshots to the cloud with Build info (About), IMEI, etc...
zgfg said:
I see for my L09c432 in this file:
/cust/hw/eu/prop/local.prop
at the end:
ro.comp.cust_version=Cust-432000 5.0.0.1(0001)
You can probably (never did myself) copy it by ADB commands to PC and read.
Maybe you need to unlock bootloader to get access.
In that case you can also install TWRP and copy the file to SD card, and then open it on the PC
PS: I usually save screenshots to the cloud with Build info (About), IMEI, etc...
Click to expand...
Click to collapse
The guide you posted earlier worked! currently at b182, but haven't received any OTA yet (strange...). I'm now waiting for google play to update and install all the necessary apps though. Thank you, Thank you and THANK YOU!
So, is it normal that I'm now stuck on EVA-L09C900B182 ? Firmware finder is not working (not downloading, always getting error), and the stock huawei updater can't find any updates, so I'm now at emui 4.1.1. Will I receive those updates and should I wait, or should I flash from sd card the dload method?
Oh, and HiSuite also tells me that I use the newest update.
horesz1994 said:
So, is it normal that I'm now stuck on EVA-L09C900B182 ? Firmware finder is not working (not downloading, always getting error), and the stock huawei updater can't find any updates, so I'm now at emui 4.1.1. Will I receive those updates and should I wait, or should I flash from sd card the dload method?
Oh, and HiSuite also tells me that I use the newest update.
Click to expand...
Click to collapse
For OTA you must have SIM and must not be in Airplane mode.
It may take few hours or up to a day - it depends on your mobile operator.
Beginning of this year, last time I did rollback, I got b203 (if recalling correctly), then b383 or b387, then up to b398 (at that time).
Give it a try. Otherwise use DLOAD (use FF only for download), you must use FullOTA-MF-PV builds, only those work for DLOAD
zgfg said:
For OTA you must have SIM and must not be in Airplane mode.
It may take few hours or up to a day - it depends on your mobile operator.
Beginning of this year, last time I did rollback, I got b203 (if recalling correctly), then b383 or b387, then up to b398 (at that time).
Give it a try. Otherwise use DLOAD (use FF only for download), you must use FullOTA-MF-PV builds, only those work for DLOAD
Click to expand...
Click to collapse
okay, I'll wait til tomorrow. But the shady part is that even HiSuite can't find an update, what does my operator have to do with this?
I don't know how it depends on Huawei, ypur IMEI, SIM card... but once I was similarly waiting and both HiSuite and System Update told me I had the latest, and then same day later I got OTA push
Oops, sorry, I have overlooked that you say you are now on c900, not c432.
There are no OTA updates for c900
I assuned you have followed the rollback guide as above, didn't you - the guide included c432 b182 (not c900 b182), in which case you should have been getting c432 OTA updates
zgfg said:
Oops, sorry, I have overlooked that you say you are now on c900, not c432.
There are no OTA updates for c900
I assuned you have followed the rollback guide as above, didn't you - the guide included c432 b182 (not c900 b182), in which case you should have been getting c432 OTA updates
Click to expand...
Click to collapse
Yes, I followed that guide, and I don't understand why I'm on c900. Can you help getting me out of this situation? Private message convo is fine by me too.
horesz1994 said:
Yes, I followed that guide, and I don't understand why I'm on c900. Can you help getting me out of this situation? Private message convo is fine by me too.
Click to expand...
Click to collapse
Follow the guide
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
Hi guys
I have rebrand my eva-l09 by chinese oreo firmware, using HWOTA7, and after starting up, all google service are missing, abd cannot intall it correctly, i trying all GMSInSTALL apk but nothing happen.
I tried to unlock bootloader via fastboot, a message showing up on adb command (unlock frp necessary...), can't enable OEM UNLOCK, always stay on grey.
Nothing is fine for me on this chinese firmware
Model : EVA-L09
BUILD NUMBER : System 8.0.0.046(0cs6)
EMUI VERSION : 8.0.0
ANDROID VERSION : 8.0.0
ANY SOLUTION TO INSTALL C432B504?
rowland.phoen1x said:
Hi guys
I have rebrand my eva-l09 by chinese oreo firmware, using HWOTA7, and after starting up, all google service are missing, abd cannot intall it correctly, i trying all GMSInSTALL apk but nothing happen.
I tried to unlock bootloader via fastboot, a message showing up on adb command (unlock frp necessary...), can't enable OEM UNLOCK, always stay on grey.
Nothing is fine for me on this chinese firmware
Model : EVA-L09
BUILD NUMBER : System 8.0.0.046(0cs6)
EMUI VERSION : 8.0.0
ANDROID VERSION : 8.0.0
ANY SOLUTION TO INSTALL C432B504?
Click to expand...
Click to collapse
You say that you followed HWOTA7 instructions - did you really
1) Your screenshot shows model L09.
OP post #2 requores that you must rebrand (change location) from L09 (or L19, L29) to AL10.
You didn't rebrand, or it failed (how, why)?!
2) Your screenshot shows build number 8.0.0.046(OCS6).
Never seen any firmware like that.
HWOTA7, post #2, clearly describes that you must flash (after rebranding to AL10 c00), first b399sp17, and after b540.
Your build number is completely different?!
What you have is not result by following HWOTA7 instructions.
If you followed HWOTA7, you would have:
1) AL10 c00 b540 (not L09 b046 or what)
2) OEM/FRM would be permanently unlocked, with no OEM Loxk/Unlock option in Developers menu (not just grayed out)
3) You would have Playstore services preinstalled, you would just need to install Playstore apk
HWOTA7 OP post #3 describes how to rollback from (properly installed!!) AL10 c00 b540 Chinese Oreo back to Nougat (eg to L08 c432 b504)
But you don't have AL10 c00 b540, but instead something totally strange/wrong - I doubt that given eRecovery procedure will work for you.
You can try with HuRupdater (sorry, I never used and needed to use HuRupdater)
https://forum.xda-developers.com/ho...ash-official-firmware-recovery-t3769279/page1
Or, you can ask for a paid help from DC-Phoenix or Ministry of solutions:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services
zgfg said:
You say that you followed HWOTA7 instructions - did you really
1) Your screenshot shows model L09.
OP post #2 requores that you must rebrand (change location) from L09 (or L19, L29) to AL10.
You didn't rebrand, or it failed (how, why)?!
2) Your screenshot shows build number 8.0.0.046(OCS6).
Never seen any firmware like that.
HWOTA7, post #2, clearly describes that you must flash (after rebranding to AL10 c00), first b399sp17, and after b540.
Your build number is completely different?!
What you have is not result by following HWOTA7 instructions.
If you followed HWOTA7, you would have:
1) AL10 c00 b540 (not L09 b046 or what)
2) OEM/FRM would be permanently unlocked, with no OEM Loxk/Unlock option in Developers menu (not just grayed out)
3) You would have Playstore services preinstalled, you would just need to install Playstore apk
HWOTA7 OP post #3 describes how to rollback from (properly installed!!) AL10 c00 b540 Chinese Oreo back to Nougat (eg to L08 c432 b504)
But you don't have AL10 c00 b540, but instead something totally strange/wrong - I doubt that given eRecovery procedure will work for you.
You can try with HuRupdater (sorry, I never used and needed to use HuRupdater)
https://forum.xda-developers.com/ho...ash-official-firmware-recovery-t3769279/page1
Or, you can ask for a paid help from DC-Phoenix or Ministry of solutions:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services
Click to expand...
Click to collapse
Im using HWOTA7, but i change update files by anothore one i have downloaded from web, i work for give you the link of firmware used.
Any solution for my big issue please SIR
rowland.phoen1x said:
Im using HWOTA7, but i change update files by anothore one i have downloaded from web, i work for give you the link of firmware used.
Any solution for my big issue please SIR
Click to expand...
Click to collapse
Sorry, really cannot help you then.
Unfortunately, since you didn't follow the guide but flashed some other firmware instead (you thought 'better' or what), you are in a specific situation, on your own, and only you should know or find how to deal with the phone and that Oreo firmware
As suggested in the previous answer, you may try with HuRupdater, but IMO, instead of further improvising (HuRupdater is very powerful but you can brick the phone), consider paying 15-20 Euros for DC-Phoenix or Ministry of solutions to safely downgrade to Nougat
After that, if you want Oreo, please follow the HWOTA7 guide carefully and in every detail (like others who now happily use the Oreo) - you will have stable Oreo AL10 c00 b540, debloated, fully working and with less battery consumption than Nougat
Also, rooted, passing SafetyNet, with fully working GApps, and ready for Open Kirin Treble custom ROMs (maybe they will work with your Oreo, too, but cannot tell you)
And if you would ever want to go back to Nougat, you would have a proven roll-back guide as in the OP post #3
zgfg said:
Sorry, really cannot help you then.
Unfortunately, since you didn't follow the guide but flashed some other firmware instead (you thought 'better' or what), you are in a specific situation, on your own, and only you should know or find how to deal with the phone and that Oreo firmware
As suggested in the previous answer, you may try with HuRupdater, but IMO, instead of further improvising (HuRupdater is very powerful but you can brick the phone), consider paying 15-20 Euros for DC-Phoenix or Ministry of solutions to safely downgrade to Nougat
After that, if you want Oreo, please follow the HWOTA7 guide carefully and in every detail (like others who now happily use the Oreo) - you will have stable Oreo AL10 c00 b540, debloated, fully working and with less battery consumption than Nougat
Also, rooted, passing SafetyNet, with fully working GApps, and ready for Open Kirin Treble custom ROMs (maybe they will work with your Oreo, too, but cannot tell you)
And if you would ever want to go back to Nougat, you would have a proven roll-back guide as in the OP post #3
Click to expand...
Click to collapse
Foud me a solution plz sir
rowland.phoen1x
Use HCU for FRP unlock
Unlock bootloader , flash twrp to erecovery and change oeminfo (better to EVA-DL)
Tnen flash via HuRupdater B540 chinese firmware
Thats do if you know how )
rambik33 said:
rowland.phoen1x
Use HCU for FRP unlock
Unlock bootloader , flash twrp to erecovery and change oeminfo (better to EVA-DL)
Tnen flash via HuRupdater B540 chinese firmware
Thats do if you know how )
Click to expand...
Click to collapse
any method without a Box ?
I have the same issue, this is how i fix it...
rowland.phoen1x said:
Hi guys
I have rebrand my eva-l09 by chinese oreo firmware, using HWOTA7, and after starting up, all google service are missing, abd cannot intall it correctly, i trying all GMSInSTALL apk but nothing happen.
I tried to unlock bootloader via fastboot, a message showing up on adb command (unlock frp necessary...), can't enable OEM UNLOCK, always stay on grey.
Nothing is fine for me on this chinese firmware
Model : EVA-L09
BUILD NUMBER : System 8.0.0.046(0cs6)
EMUI VERSION : 8.0.0
ANDROID VERSION : 8.0.0
ANY SOLUTION TO INSTALL C432B504?
Click to expand...
Click to collapse
Maybe I can help you...
I had the same issue just like you, even I read this post before I fix my phone.
First of all, the bootloader says the FRP-Locked, OEM Lock(or whatever says, i can't remember)-Unlocked.
On the Developer Settings the Oem Unlock option was greyed out.
Just like you.
So, reading this post [GUIDE] Debranding to C432 and updating to B361 (Nougat) for EVA-L09 i had a hunch...
What did I do to have my phone back?
1. My phone had the C432 oeminfo, so, I downloaded the dload-huawei-p9-eval09-eva-b136.zip (L09C432B136) in this post. Stock ROM dload file - P9 EVA-L09 B136
2. Copy the extracted dload folder to the external microSD card.
3. Now open the dialer app and enter *#*#2846579#*#* to open the project menu
4. Go to Software Upgrade > SDCard upgrade and confirm the update installation.
5. After the update, maybe shows an error at the final, let it be.
6. The phone restarts and boots with the L09C432B136, Android 6.0, and if you check the Developer options, the OEM unlock option is enabled. You can now lock or unlock your bootloader.
7. I need to update to the latest build and if i tried to check for an update, it says there is none.
8. I downloaded this firmware Download Huawei P9 B182 Marshmallow Update [Europe] I repeat steps 2-5, lock the bootloader, and search for an update... and update after update, I'm on L09C432B504 (Nougat)
Hope to help you...
Sorry for my bad english, I have no one to practice with...