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
My huawei p9 Eva l19 keeps restarting and fail software. Please help.
Phone unlocked.
The video https://streamable.com/71z5e
Thanks.
danro28 said:
My huawei p9 Eva l19 keeps restarting and fail software. Please help.
Phone unlocked.
The video https://streamable.com/71z5e
Thanks.
Click to expand...
Click to collapse
Bootloop doesn't happen by itself - to get help you must describe which stock/custom firmware you had, were you flashing another firmware and which or trying to root, or you were changing something under root before it started to happen
Solution to unbrick highly depends on the firmware, etc - for firmware is needed full model, cust and number
Btw, does it boot to Fastboot, EMUI Recovery (or you flashed custom Recovery TWRP) or eRecovery?
The Phone model is Eva l19.
The software is shown în The video
The bootloader is unlocked and s-o is The frp.
I tried various versions of The software but The result was The same. Using The method update.app it was working to 5%, The says 6% and then back 5 % and then erron instalation.
danro28 said:
The Phone model is Eva l19.
The software is shown în The video
The bootloader is unlocked and s-o is The frp.
I tried various versions of The software but The result was The same. Using The method update.app it was working to 5%, The says 6% and then back 5 % and then erron instalation.
Click to expand...
Click to collapse
Too small and not sharp - can you write what is your firmware version on your phone
Eva-l19c432b388
You say you were installing various firmwares - if you did, specially if you maybe combined various custs, then it was a road to mess
I would suggest you to carefully study posts OP #1 and #2 from HWOTA7 thread
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Forget (at the moment - later you could do if you wish but once you solve your Nougat) about changing cust and upgtading to Chinese Nougat.
Use the HWOTA7 method instead to change the cust/location to c432 (to clean up) and to install one of the latest FullOTA-MF stock firmwares, eg L19c432b505 or so
Be careful, use L19 only if your P9 is dual SIM, otherwise must be L09
Follow every detail (but adapted to your case), including Factory Reset and Wiping Cache at the end
I tried this method but i can't recover bootloader Code because hcu client doesn't work on my pc.
Win 10 64 bit.
Could you conect to my pc and help ME fix my Phone?