Related
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!
Hey everyone,
So, a couple months back I rebranded my EVA-L09 to a VIE-AL10 through the rebrand tool.
A couple weeks back I wanted to revert back to EVA-L09 to go back to Magic Rainbow v4 or v3.
I failed in trying to rebrand it back and ended up where I am now, I have TWRP installed, I can do the dload methods to install whatever, but I can't for the life of me get any ROM or firmware to boot. It either doesn't go past the "Your device is not trusted" screen or it hangs at the boot animation.
Extra notes: Yes I was on Oreo when I tried to revert, I am currently not on Oreo as I tried to flash a Nougat VIE-AL10 firmware to attempt to get the phone to at least boot to a usable state for the time being, however now it's stuck on a boot animation.
Would appreciate any help,
Cheers.
Update:
I tried to follow this: https://forum.xda-developers.com/showpost.php?p=77161313&postcount=2
But as mentioned above the phone hangs on "Your device is booting now..." after HWOTA copies the Nougat firmware files.
gamr13 said:
Hey everyone,
So, a couple months back I rebranded my EVA-L09 to a VIE-AL10 through the rebrand tool.
A couple weeks back I wanted to revert back to EVA-L09 to go back to Magic Rainbow v4 or v3.
I failed in trying to rebrand it back and ended up where I am now, I have TWRP installed, I can do the dload methods to install whatever, but I can't for the life of me get any ROM or firmware to boot. It either doesn't go past the "Your device is not trusted" screen or it hangs at the boot animation.
Extra notes: Yes I was on Oreo when I tried to revert, I am currently not on Oreo as I tried to flash a Nougat VIE-AL10 firmware to attempt to get the phone to at least boot to a usable state for the time being, however now it's stuck on a boot animation.
Would appreciate any help,
Cheers.
Click to expand...
Click to collapse
EVA is P9, VIE is P9 Plus
Don't mix firmwares, you wll (no wonder if you really mixed), brick the phone
One procedure is for P9 = EVA (and this is P9 portal here):
rebranding from EVA L09/L19 to EVA AL00c00b535 and back
https://forum.xda-developers.com/p9-plus/development/rebrand-update-tool-hwota7-p9-plus-vie-t3843930
The other is for P9 Plus = VIE (different phone, eg bigger display)
rebranding from VIE L09/L29 to VIE AL00c00b535 and back
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
zgfg said:
EVA is P9, VIE is P9 Plus
Don't mix firmwares, you wll (no wonder if you really mixed), brick the phone
One procedure is for P9 = EVA (and this is P9 portal here):
rebranding from EVA L09/L19 to EVA AL00c00b535 and back
https://forum.xda-developers.com/p9-plus/development/rebrand-update-tool-hwota7-p9-plus-vie-t3843930
The other is for P9 Plus = VIE (different phone, eg bigger display)
rebranding from VIE L09/L29 to VIE AL00c00b535 and back
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Click to expand...
Click to collapse
I was reading through the first link there, as mentioned in the second post I made in here. After following the steps one-by-one the device is stuck at "Your device is booting now..."
gamr13 said:
I was reading through the first link there, as mentioned in the second post I made in here. After following the steps one-by-one the device is stuck at "Your device is booting now..."
Click to expand...
Click to collapse
Be more specific, confirm
- Your phone is P9 or P9 Plus?
If P9, was it L09 (single SIM) or L19 (dual SIM)
- On exactly which Chinese Oreo have you been (cannot be VIE, you must well know what you exactly had and what you were flashing), was it EVA -AL00c00 or what and which build number bXX it was
- Did you go to some Open Kirin/AOSP custom ROM or stayed on that stock Chinese ROM?
You first had to come back to Chinese stock Oreo, not downgrading to Nougat directly from Open Kirin / AOSP
- Downgrading consists of several steps, HiSuite to go to Chinese Nougat and then HWOTA7 to rebrand to eg c432 Nougat.
Up to each step did you exactly do when you got stuck in Booting?
-More precisely, if you downgraded by HiSuite to AL10c00 Nougat, did it boot successfully (or were you here stuck at booting)?
If that step was successful, which (full build name and number) you were flashing by HWOTA7 to rebrand to from the Chinese Nougat?
-Have you tried to switch off and boot again?
Have you tried booting to Recovery and do Factory reset and Wipe Cache and Internal mem and then tried to teboot?
zgfg said:
Be more specific, confirm
- Your phone is P9 or P9 Plus?
If P9, was it L09 (single SIM) or L19 (dual SIM)
- On exactly which Chinese Oreo have you been (cannot be VIE, you must well know what you exactly had and what you were flashing), was it EVA -AL00c00 or what and which build number bXX it was
- Did you go to some Open Kirin/AOSP custom ROM or stayed on that stock Chinese ROM?
You first had to come back to Chinese stock Oreo, not downgrading to Nougat directly from Open Kirin / AOSP
- Downgrading consists of several steps, HiSuite to go to Chinese Nougat and then HWOTA7 to rebrand to eg c432 Nougat.
Up to each step did you exactly do when you got stuck in Booting?
-More precisely, if you downgraded by HiSuite to AL10c00 Nougat, did it boot successfully (or were you here stuck at booting)?
If that step was successful, which (full build name and number) you were flashing by HWOTA7 to rebrand to from the Chinese Nougat?
-Have you tried to switch off and boot again?
Have you tried booting to Recovery and do Factory reset and Wipe Cache and Internal mem and then tried to teboot?
Click to expand...
Click to collapse
Sure,
EVA-L09 is a regular P9. Not a P9 Plus.
I never honestly checked which Oreo firmware I was on. I downloaded the VIE-AL10C00B535 (8.0.0.535) firmware and used that.
Yes, at one point I did go to the OpenKirin AOSP ROMs. However, I was able to do the volume + & - + Power to return to Nougat and then re-flash Oreo. After this I stayed on the EMUI 8.0 firmware.
I did not use HiSuite as it never worked for me. It would always just tell me to go to a service center.
I did not use HiSuite. When I returned to EMUI 5.0.1 from eRecovery (?) Restoring over WiFi on the actual phone it booted fine and I then upgraded again to the Oreo firmware.
Yes, I have tried rebooting.
Yes, I have tried a factory reset.
When I tried to revert from a VIE-AL10 rebrand, my phone ended up getting stuck between an AL10 and an EVA-L09. Meaning that I can use the EVA-L09 TWRP but not an EVA-L09 compatible firmware or ROM. I can only boot AL10 firmwares or ROMs however they hang at the boot animation.
gamr13 said:
Sure,
EVA-L09 is a regular P9. Not a P9 Plus.
I never honestly checked which Oreo firmware I was on. I downloaded the VIE-AL10C00B535 (8.0.0.535) firmware and used that.
Yes, at one point I did go to the OpenKirin AOSP ROMs. However, I was able to do the volume + & - + Power to return to Nougat and then re-flash Oreo. After this I stayed on the EMUI 8.0 firmware.
I did not use HiSuite as it never worked for me. It would always just tell me to go to a service center.
I did not use HiSuite. When I returned to EMUI 5.0.1 from eRecovery (?) Restoring over WiFi on the actual phone it booted fine and I then upgraded again to the Oreo firmware.
Yes, I have tried rebooting.
Yes, I have tried a factory reset.
When I tried to revert from a VIE-AL10 rebrand, my phone ended up getting stuck between an AL10 and an EVA-L09. Meaning that I can use the EVA-L09 TWRP but not an EVA-L09 compatible firmware or ROM. I can only boot AL10 firmwares or ROMs however they hang at the boot animation.
Click to expand...
Click to collapse
>> I downloaded the VIE-AL10C00B535 (8.0.0.535) firmware and used that.
In yout previous post:
>> I tried to follow this: https://forum.xda-developers.com/sho...13&postcount=2
Guide you cited is for rebranding European P9 EVA to Chinese P9 EVA-AL10c00b535 - see attached screenshots from the guide, observe it is everywhere EVA-AL10, not VIE-AL10
Once again, it must be EVA before rebranding and EVA after rebranding.
VIE is different phone (different hardware - bigger display), P9 Plus.
If you didn't care about difference between EVA and VIE, maybe you really downloaded and flashed AL10c00b535 for VIE (P9 Plus) to your EVA (P9)
----
>> Yes, at one point I did go to the OpenKirin AOSP ROMs. However, I was able to do the volume + & - + Power to return to Nougat
This is procedure to boot to Recovery (eRecovery if charging by USB), not to Nougat
----
Details are important, not just when writing posts but really when reading guides and flashing, otherwise bad things can happen ;(
So please, consider again, did you really flash VIE AL10 to your P9 (5,2 inch display)?
(Maybe it worked somehow for AL10b535 because packages for Chinese P9 = EVA and P9 Plus = VIE are similar, but now when returning to Nougat it stays on VIE and doesn't boot)
zgfg said:
>> I downloaded the VIE-AL10C00B535 (8.0.0.535) firmware and used that.
In yout previous post:
>> I tried to follow this: https://forum.xda-developers.com/sho...13&postcount=2
Guide you cited is for rebranding European P9 EVA to Chinese P9 EVA-AL10c00b535 - see attached screenshots from the guide, observe it is everywhere EVA-AL10, not VIE-AL10
Once again, it must be EVA before rebranding and EVA after rebranding.
VIE is different phone (different hardware - bigger display), P9 Plus.
If you didn't care about difference between EVA and VIE, maybe you really downloaded and flashed AL10c00b535 for VIE (P9 Plus) to your EVA (P9)
----
>> Yes, at one point I did go to the OpenKirin AOSP ROMs. However, I was able to do the volume + & - + Power to return to Nougat
This is procedure to boot to Recovery (eRecovery if charging by USB), not to Nougat
----
Details are important, not just when writing posts but really when reading guides and flashing, otherwise bad things can happen ;(
So please, consider again, did you really flash VIE AL10 to your P9 (5,2 inch display)?
(Maybe it worked somehow for AL10b535 because packages for Chinese P9 = EVA and P9 Plus = VIE are similar, but now when returning to Nougat it stays on VIE and doesn't boot)
Click to expand...
Click to collapse
I honestly can't remember how I did it now, it's been a while, but it did go through successfully, and it was working fine after applying the patch.
But yeah, as of now all I can use is fastboot and TWRP. That's all. I've tried flashing EVA-L09 firmware, it doesn't boot. I've flashed AL10 firmware and it gets to a boot animation, but no further than that.
gamr13 said:
I honestly can't remember how I did it now, it's been a while, but it did go through successfully, and it was working fine after applying the patch.
But yeah, as of now all I can use is fastboot and TWRP. That's all. I've tried flashing EVA-L09 firmware, it doesn't boot. I've flashed AL10 firmware and it gets to a boot animation, but no further than that.
Click to expand...
Click to collapse
Boot to Fastboot:
- connect by USB to PC and boot by: press and keep pressing Vol-, then Pow
Ececute from the PC side and copy/paste back your results (is Bootloader still unlocked, what the phone thinks it is current model, cust, build number)
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
@gamr13 Please enter the shown commands by @zgfg in Fastboot mode and tell us the result.
There is not much hope to restore your device after all that you have done wrong → but if you try, what we recommend, we may can recover it.
I can confirm: EVA-L09 is not the same device as VIE-L09 → you can not rebrand EVA-L09 to VIE-AL10, and it is not possible to rebrand VIE-L09 to EVA-AL10 - That causes a lot of problems and you should not be surprised if your device does not boot again.
If your original device was an EVA-L09 you can rebrand to all EVA models, but not to VIE models - That's why there are two threads - one for P9 and the other for P9 Plus.
If you flash oeminfos and related Firmware → it must match with your device!
But if you think, you can flash whatever you like, then your device get "bricked". And here we are now.
BTW: Rebranding back to your originally model can not be done with HWOTA7 - as long the device is on Android 8 ! First a downgrade from Chinese Brand Oreo to Chinese Brand Nougat is required → after this step it is possible to use hwota7 again to rebrand. I have written all the steps in separate Posts after the main Thread.
First we need this Fastboot mode information, then we can see in which status, on which firmware and which oeminfo your device is currently.
Then it's time to flash exactly this firmware with the correct method → for this step, wait for instructions from us.
Only when the device works again, it is possible to downgrade with the correct method and return to the original model, or whatever.
As long as the device is in a "brick", nothing works, since the "brick" must first be resolved.
If it is a "semi brick", a "hard brick" can happen as well, after that the device will be dead and without any function → It teaches you to be careful with flashing and get all the information before you flash anything.
We've also had other issues caused by users doing wrong actions - not knowing what they're actually doing. But both cases were solved successfully - which was not easy:https://forum.xda-developers.com/p9/help/huawei-p9-potentally-bricked-t3841197/
Hey guys,
I've attached a screenshot below which contains all the commands and what I got from them below.
Note about the get-build-number, that was the most recent firmware I tried to flash out of literally 10 other firmwares I tried.
I appreciate everything you guys are trying to do to help me fix this problem. I'm currently trying to survive with a Galaxy S3 Mini, and it's not going well in the slightest.
Cheers.
EDIT: Just as a note, which may be obvious from the screenshots to you or not, the partitions are like Nougat, meaning I do not flash the recovery to ramdisk.
gamr13 said:
Hey guys,
I've attached a screenshot below which contains all the commands and what I got from them below.
Note about the get-build-number, that was the most recent firmware I tried to flash out of literally 10 other firmwares I tried.
I appreciate everything you guys are trying to do to help me fix this problem. I'm currently trying to survive with a Galaxy S3 Mini, and it's not going well in the slightest.
Cheers.
EDIT: Just as a note, which may be obvious from the screenshots to you or not, the partitions are like Nougat, meaning I do not flash the recovery to ramdisk.
Click to expand...
Click to collapse
Looks promissing
It says EVA, not VIE - ok
Somehow you are on c900b182 which means MM (not Nougat) - did you rollback to MM?
In Fastboot screen, does it show in red, at the bottom, both Phone (=Bootloader) and FRP Unlocked?
zgfg said:
Looks promissing
It says EVA, not VIE - ok
Somehow you are on c900b182 which means MM (not Nougat) - did you rollback to MM?
In Fastboot screen, does it show in red, at the bottom, both Phone (=Bootloader) and FRP Unlocked?
Click to expand...
Click to collapse
Yes, I tried to flash MM as well.
In fastboot mode it only shows PHONE Unlocked.
gamr13 said:
Yes, I tried to flash MM as well.
In fastboot mode it only shows PHONE Unlocked.
Click to expand...
Click to collapse
Why didn't you wait, you attempted to rollback?
Now Bootloader is unlocked but FRP is locked (and you cannot boot to System to unlock OEM=FRP)
It can block you fir further flashing ;-(
Do you want to go to c432, is it L09 (Single SIM) or L19 (Dual SIM)?
zgfg said:
Why didn't you wait, you attempted to rollback?
Now Bootloader is unlocked but FRP is locked (and you cannot boot to System to unlock OEM=FRP)
It can block you fir further flashing ;-(
Do you want to go to c432, is it L09 (Single SIM) or L19 (Dual SIM)?
Click to expand...
Click to collapse
This was around a week ago, and the FRP lock thing went away when I did the rebrand - as it's supposed to
But yeah, I can't boot the system.
It's the single SIM EVA-L09.
gamr13 said:
This was around a week ago, and the FRP lock thing went away when I did the rebrand - as it's supposed to
But yeah, I can't boot the system.
It's the single SIM EVA-L09.
Click to expand...
Click to collapse
Procedure for rebranding from c900b182 to c432 is here:
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
Once on c432b182 you should receive OTAs to get back to Nougat.
However, procedure requires flashing OEMIFO, which most likely will be forbidden to you because your FRP is locked and you cannot boot to Systen to unlock OEM.
Which means serious brick
In that case you can try with DC Unlock (sorry, I don't know a better method), it will cost you 15 EUR (probably) and you must ask them for on-line help if needed
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
zgfg said:
Procedure for rebranding from c900b182 to c432 is here:
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
Once on c432b182 you should receive OTAs to get back to Nougat.
However, procedure requires flashing OEMIFO, which most likely will be forbidden to you because your FRP is locked and you cannot boot to Systen to unlock OEM.
Which means serious brick
In that case you can try with DC Unlock (sorry, I don't know a better method), it will cost you 15 EUR (probably) and you must ask them for on-line help if needed
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Click to expand...
Click to collapse
I'll follow the first link carefully and report back, thanks!
gamr13 said:
I'll follow the first link carefully and report back, thanks!
Click to expand...
Click to collapse
Try but you most likely you will need second link
Here was another user who also had to use DC Unlocker, take a look into the thread (posts #6-#11), in the last post he described how it was resolved for him by DC Unlocker
https://forum.xda-developers.com/p9/help/bought-phone-ebay-registration-wizard-t3840803
zgfg said:
Try but you most likely you will need second link
Here was another user who also had to use DC Unlocker, take a look into the thread (posts #6-#11), in the last post he described how it was resolved for him by DC Unlocker
https://forum.xda-developers.com/p9/help/bought-phone-ebay-registration-wizard-t3840803
Click to expand...
Click to collapse
I used DC Unlocker before to get my bootloader unlock key.
gamr13 said:
I used DC Unlocker before to get my bootloader unlock key.
Click to expand...
Click to collapse
I was not writing you about getting the code but to use DC Unlocker to unlock FRP ( carefully read the story, posts #6 till #11, I gave you in the previous post)
Because their tool can unlock both FRP and Bootloader, but it costs more than just getting the Bootloader code
Personally I didn't use their tool (never bricked the phone or so to need it), and cannot help you about the tool further
I have a Huawei P9 that doesn't seem to receive updates.
EMUI 4.1.1
Build: EVA-L09C900B182
Andriod: 6.0
I have tried using firmware finder but I always get checksum failed before it passes 1%.
I had a look through the Forums and it seems that people recommend rebranding though that was in 2017.
I was wondering if there is any easy way to update?
I am a noob so i want to try avoid rooting and rebranding if possible.
Has anyone managed to update this?
2 years later and I'm still trying...
focussss said:
Has anyone managed to update this?
2 years later and I'm still trying...
Click to expand...
Click to collapse
For c900 there is no newer firmware.
Flashing anything else than c900 means rebranding - but rebranding requires unlocking Bootloader (not 'rooting')
So wandering, what are you really trying to do for two years?!
- Unlock Bootloader (4 Euros):
https://www.dc-unlocker.com/
- Rebrand properly to be able to update to Nougat eg EVA-L09c432b504:
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
I followed that guide but now my phone is stuck on "Type the password to decrypt storage" when I enter my Google password it says it's correct but data on my phone is corrupted. Any ideas?
focussss said:
I followed that guide but now my phone is stuck on "Type the password to decrypt storage" when I enter my Google password it says it's correct but data on my phone is corrupted. Any ideas?
Click to expand...
Click to collapse
Are you talking about TWRP asking for pass or Android?
If Android, on which firmware are you, what was the last step you performed?
Also, make sure you used TWRP for MM, not for Nougat - since you were on c900 MM when you started with rebranding to c432 (?)
Btw, you unlocked the Bootloader?
Thanks for the quick response and all your assistance. I managed to finally boot into EVA-L09C432B182 and will write what I did in the rebranding post for others who run into this issue. I still have no updates on L09C432B182 though.
focussss said:
Thanks for the quick response and all your assistance. I managed to finally boot into EVA-L09C432B182 and will write what I did in the rebranding post for others who run into this issue. I still have no updates on L09C432B182 though.
Click to expand...
Click to collapse
For OTA you must have a valid SIM card and WiFi - check manually to the System Update to trigger checking for an update
You can also try with HiSuite (PC) - latest versions of HiSuite have an option at the bottom to update the firmware
See:
https://huaweiflash.com/how-to-flash-huawei-stock-firmware-all-methods/
You can also update by DLOAD (read the guide above), you must download FullOTA-MF-PV (must be PV), like b360, from Firmware Finder
There is also HWOTA method, see:
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Hello I'm the proud owner of a VTR-L09 P10 with the oreo based VTR-L09 8.0.0.364(c530) firmware and an unlocked bootloader. I have tried many tutos across the internet but I still can't downgrade it to nougat in order for rebranding to VTR-29.
Can someone with matching conf or a close one who has succeeded in rebranding can help me with a working tuto.
Thanks in advance and....
HAPPY NEW YEAR !!!!
First, you twist nougat and Oreo. Your phone is on Oreo and you wanted to downgrade to Nougat.
I don't know, why the downgrade didn't work for you, but maybe now it does with the correct understanding of versions (nougat is the older one).
If you're a bit experiment friendly, you can try something for me - but I really can't guarantee you that this will work without brick!
You need an SD card for this, don't try it without!
- Download your desired firmware from Firmware Finder. I recommend 8.0.0.382 for L29-C432, which I installed on my rebranded P10 yesterday.
Here are the links:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2323/g1699/v202186/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...l/VTR-L29_hw_eu/update_full_VTR-L29_hw_eu.zip
http://update.hicloud.com:8180/TDS/...86/f1/full/public/update_data_full_public.zip
- Download my oeminfo file and put it on SD.
- Download and flash this TWRP. It will ask you for a password at boot, type your phone PIN.
- Backup your oeminfo with TWRP on SD AND internal memory, just to be sure.
- Now flash my oeminfo file with TWRP via Install/Use Image.
- Go to my guide and follow now Tutorial #2, Oreo to Oreo, exactly. You can use the TWRP version you already installed, but everything has to be like in the tutorial.
It should work, but, as I mentioned above, I can't guarantee it.
The worst thing which can happen is that you brick your firmware. For this, you should be able to reinstall an L09 firmware after restoring your oeminfo file via eRecovery.
But I think the recovery will stop installing L29 if it didn't work with the oemfile - if so, you just need to restore the oeminfo backup.
Don't boot into your L09 firmware with L29 oeminfo!
Jannomag said:
First, you twist nougat and Oreo. Your phone is on Oreo and you wanted to downgrade to Nougat.
I don't know, why the downgrade didn't work for you, but maybe now it does with the correct understanding of versions (nougat is the older one).
If you're a bit experiment friendly, you can try something for me - but I really can't guarantee you that this will work without brick!
You need an SD card for this, don't try it without!
- Download your desired firmware from Firmware Finder. I recommend 8.0.0.382 for L29-C432, which I installed on my rebranded P10 yesterday.
Here are the links:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2323/g1699/v202186/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...l/VTR-L29_hw_eu/update_full_VTR-L29_hw_eu.zip
http://update.hicloud.com:8180/TDS/...86/f1/full/public/update_data_full_public.zip
- Download my oeminfo file and put it on SD.
- Download and flash this TWRP. It will ask you for a password at boot, type your phone PIN.
- Backup your oeminfo with TWRP on SD AND internal memory, just to be sure.
- Now flash my oeminfo file with TWRP via Install/Use Image.
- Go to my guide and follow now Tutorial #2, Oreo to Oreo, exactly. You can use the TWRP version you already installed, but everything has to be like in the tutorial.
It should work, but, as I mentioned above, I can't guarantee it.
The worst thing which can happen is that you brick your firmware. For this, you should be able to reinstall an L09 firmware after restoring your oeminfo file via eRecovery.
But I think the recovery will stop installing L29 if it didn't work with the oemfile - if so, you just need to restore the oeminfo backup.
Don't boot into your L09 firmware with L29 oeminfo!
Click to expand...
Click to collapse
Hello
I tried it and now I'm stuck in and endless reboot loop with only Huawei logo
Can you help me please ?
Did you do the factory reset via eRecovery?
The update with my script worked without any errors?
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...