Hi guys I have a problem. I tried to upgrade my p9 plus manually with an ota update.
I had VIE-L09ITAC555B130 and I tried to install VIE-L09ITAC555B360 to get emui 5.0. The updater wasn't able to complete the download so I tried manually. B360 is split in two files (I don't know why, this is my first Huawei), I tried the first but at 30/40% I got an error, then I tried the second update.app and now my phone boot in eRecovery mode.
I can also boot in fastboot mode but my bootloader is locked and I can't get the product ID.
I also tried to install B130 again but it didn't complete the process. I don't know what to do anymore, some suggestion?
Sorry if my english is pretty bad...
Did anyone find a solution in this particular case? I read all forums but I didn't find the steps to fix it yet...
Situation: Huawei P9 keeps turning on and freeze at Huawei Logo. I have an option to go to fastboot mode, but unfortunately, I can't do
anything else (FRP locked). I received the unlock OEM code from official Huawei site, but I can't unlock OEM.
When I launch the fastboot OEM unlock ... command (with unlock code), I always get:
...
FAILED (remote: Command not allowed)
When I am trying to flash is the same situation: FAILED (remote: Command not allowed)
SD micro card is not booting...
The phone is not rooted.
Are any masters who could provide how to unlock bootloader or any flashing method without an unlocked bootloader in this particular situation?
15€ for dc phoenix
any other options?
I have probably the same issue, but maybe you are luckier than me.
Can you still get into the manual updater via "vol+ & vol- & power"?
If you can, you can flash it here with the stock rom app in dload folder of the sd-card.
For me however, I cannot get into the manual updater, erecovery.
I am still trying to figure out if I can get "fastboot update rom.zip" to work. It tells me the android-info.txt is missing and I have no idea where to get it, or how to make one.
noalt said:
I have probably the same issue, but maybe you are luckier than me.
Can you still get into the manual updater via "vol+ & vol- & power"?
If you can, you can flash it here with the stock rom app in dload folder of the sd-card.
For me however, I cannot get into the manual updater, erecovery.
I am still trying to figure out if I can get "fastboot update rom.zip" to work. It tells me the android-info.txt is missing and I have no idea where to get it, or how to make one.
Click to expand...
Click to collapse
I can't get into the manual updater via "vol+ & vol- & power". I'm still looking how to remove FRP lock.
Don't bother with the DC-unlocker. It did not work. :-/
noalt said:
Don't bother with the DC-unlocker. It did not work. :-/
Click to expand...
Click to collapse
So strange that nobody knows how to fix it. I spend many hours how to find a solution but still couldn't find it..
Did you try by yourself to erase FRP with DC-Unlocker?
Yes, I did. Afterwards I saw in the faq that it doesnt work for bricked phones.
Thankfully I never bricked the phone, but frankly I didn't know there were cases that even DC Phonex cannot resolve (at least to unlock bootloader for the first step)
The following guide helped many people to unbrick phones, but it relies on flashing through fastbook - requiring to have the bootloader unlocked (hence you are again with the chicken and egg problem):
http://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
There is also another commercial 'repeair' tool that was spoken on XDA Huawei topics about, but now looking carefully, seems it's not for unlcking bootloader and neither for unbricking (?!) - you can double-check if you find anything useful:
https://hcu-client.com/
Sorry it doesn't help you...!
The fastboot flash commands are locked due to the frp-lock.
I talked to the tech-guy from dc-unlocker and he said the frp-unlock from the tool only removes the associated google account in the OS, but does not change the frp-lock.
This however might work: https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
But I'm thinking of returning the phone for repair because it is only a week old and still in waranty.
If somebody tries it, I will be glad to hear how it turned out.
Have you tried wiping everything (data/cache) by using the stock recovery? Volume up and the power button should do it. Then check if it will boot after doing those steps.
thedarkinvader said:
Have you tried wiping everything (data/cache) by using the stock recovery? Volume up and the power button should do it. Then check if it will boot after doing those steps.
Click to expand...
Click to collapse
Stock recovery is not available. I think it's partially overwritten.
noalt said:
Stock recovery is not available. I think it's partially overwritten.
Click to expand...
Click to collapse
I think we need to know what OP did before all of this happened to get a more clear idea of why it happened and how to solve it
thedarkinvader said:
I think we need to know what OP did before all of this happened to get a more clear idea of why it happened and how to solve it
Click to expand...
Click to collapse
For me:
-Bought the phone with android 6.0, Bluetooth was working.
-Upgraded to android nougat with the normal updater (in running OS).
-Upgrade was succesfull but bluetooth was not working.
-Set factory defaults, bluetooth still not working.
-Downloaded stock rom android 7.0 and installed it using dload method (using manual updater (vol+ & vol- & power).
-Was succesfull but still no bluetooth.
-Reverted to android 6.0 using the rollback package and a stock rom I downloaded (using manual updater)
-Revert was succesfull, adroid 6.0 was running and bluetooth was working.
-Wanted to try updating to android 7.0 once again using the normal updater.
-Normal updater said it was already at latest version, but it was android 6.0 (???)
-Tried updating to android 7.0 (same package as before) using dload method (manual updater)
-Updater stopped at 5% and said wrong package (weird, it worked before)
-Tried using the same rollback package as before to get it to region c900 (worldwide)
-Went to 100%, rebooted and stuck at boot-logo.
-After a while, rebooted my phone, but always stuck at boot-logo.
-No longer can shut down my phone. Holding power reboots.
-Tried getting to erecovery using vol+ & power. Reboots to boot-logo (vibrates twice during reboot)
-Tried getting to manual updater using vol+ & vol- & power. Reboots to boot-logo (vibrates twice during reboot)
-Can get into fastboot mode, but bootloader andr frp are locked. (Limited fastboot commands).
-Letting power drain shows red power circle indicating the battery is practically empty and will only boot to fastboot mode (plugged in)
-After charging still stuck at boot-logo.
I think that is about it...
Thanks for the help
noalt said:
For me:
-Bought the phone with android 6.0, Bluetooth was working.
-Upgraded to android nougat with the normal updater (in running OS).
-Upgrade was succesfull but bluetooth was not working.
-Set factory defaults, bluetooth still not working.
-Downloaded stock rom android 7.0 and installed it using dload method (using manual updater (vol+ & vol- & power).
-Was succesfull but still no bluetooth.
-Reverted to android 6.0 using the rollback package and a stock rom I downloaded (using manual updater)
-Revert was succesfull, adroid 6.0 was running and bluetooth was working.
-Wanted to try updating to android 7.0 once again using the normal updater.
-Normal updater said it was already at latest version, but it was android 6.0 (???)
-Tried updating to android 7.0 (same package as before) using dload method (manual updater)
-Updater stopped at 5% and said wrong package (weird, it worked before)
-Tried using the same rollback package as before to get it to region c900 (worldwide)
-Went to 100%, rebooted and stuck at boot-logo.
-After a while, rebooted my phone, but always stuck at boot-logo.
-No longer can shut down my phone. Holding power reboots.
-Tried getting to erecovery using vol+ & power. Reboots to boot-logo (vibrates twice during reboot)
-Tried getting to manual updater using vol+ & vol- & power. Reboots to boot-logo (vibrates twice during reboot)
-Can get into fastboot mode, but bootloader andr frp are locked. (Limited fastboot commands).
-Letting power drain shows red power circle indicating the battery is practically empty and will only boot to fastboot mode (plugged in)
-After charging still stuck at boot-logo.
I think that is about it...
Thanks for the help
Click to expand...
Click to collapse
Any luck in doing a rollback again? I mean, wouldn't hurt to try doing it again. I also wonder why doing steps the second time gives us different results. Weird.
Well, I sort of tried it but it only works from the manual updater, which is not accessible.
So, I bit the bullet and tried dc-phoenix flasher. (https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial)
-Loaded nougat in dc-phoenix. Started flashing using the "backdoor".
-In the end there was something that failed, but it did managed to write back the erecovery and manual updater. (I pressume it would not have failed if I had chosen the marshmallow image)
-So at this point, I still had no OS.
-I tried using the manual updater to go to nougat but that did not work.
-I tried the marshmallow package with the manual updater and this did worked.
-So I had a working marshmallow. (with bluetooth working)
-and NOW the first thing I did was OEM UNLOCK!!!!!!
-Flashed TWRP and installed nougat with TWRP.
-The flashing procedure was a partial succes. Nougat was running but without a keyboard installed for some reason.
-Installed a play store keyboard so I can actually type the password of my wifi
-But still no bluetooth in Nougat.
-This evening I am going to try a package via the firmware finder. (The nougat I was trying is b384)
noalt said:
So, I bit the bullet and tried dc-phoenix flasher. (https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial)
-Loaded nougat in dc-phoenix. Started flashing using the "backdoor".
-In the end there was something that failed, but it did managed to write back the erecovery and manual updater. (I pressume it would not have failed if I had chosen the marshmallow image)
-So at this point, I still had no OS.
-I tried using the manual updater to go to nougat but that did not work.
-I tried the marshmallow package with the manual updater and this did worked.
-So I had a working marshmallow. (with bluetooth working)
-and NOW the first thing I did was OEM UNLOCK!!!!!!
-Flashed TWRP and installed nougat with TWRP.
-The flashing procedure was a partial succes. Nougat was running but without a keyboard installed for some reason.
-Installed a play store keyboard so I can actually type the password of my wifi
-But still no bluetooth in Nougat.
-This evening I am going to try a package via the firmware finder. (The nougat I was trying is b384)
Click to expand...
Click to collapse
That happened to me one, not having a keyboard to use. I think you have to flash the public zip that comes with the full package.
Since you're unlocked and have the whole package, I suggest that you do the HWOTA steps then. The post title should be about the nocheck recovery thingy.
I got it sorted yesterday.
Got 3 zips with the firmware finder and installed those through twrp.
Bluetooth working and everything
I'm still on b386 though. I tried 397 and 393 which the firmware finder said where compatible (imei check), but they both failed to install through twrp.
And then I got tired of it, so I stuck with b386.
Thank you all for the assistance!
noalt said:
I got it sorted yesterday.
Got 3 zips with the firmware finder and installed those through twrp.
Bluetooth working and everything
I'm still on b386 though. I tried 397 and 393 which the firmware finder said where compatible (imei check), but they both failed to install through twrp.
And then I got tired of it, so I stuck with b386.
Thank you all for the assistance!
Click to expand...
Click to collapse
I'm not sure if it's the same for the other versions (L-XX) but for my P9 (L19C363), installing the B394 gave me "dynamic photos" in the Camera app (live photos in iOS) and searching for photos by date, album, etc. in the Gallery app. If what they say is true, that the bootloader being unlocked doesn't affect being able to install updates, I suggest that you flash the stock recovery and update through it if want to get those features
Hi
I've problem with P9 Dual Sim EVA-L19. I buy this phone with strange sympthom (no camera app, bluetooth not working). Looks like bad update Android. I try update firmware via dload and SDCard but update still stoping on 5% and after few second message Software update failed. I try 3 diffrend source software and situation no change. Where is problem?
Probably bootloader is locked. Actual software: L19C432B399 (Orange Poland distribution)
kaziutek144 said:
Hi
I've problem with P9 Dual Sim EVA-L19. I buy this phone with strange sympthom (no camera app, bluetooth not working). Looks like bad update Android. I try update firmware via dload and SDCard but update still stoping on 5% and after few second message Software update failed. I try 3 diffrend source software and situation no change. Where is problem?
Probably bootloader is locked. Actual software: L19C432B399 (Orange Poland distribution)
Click to expand...
Click to collapse
Locked Bootloader should not be a problem for DLOAD, but I doubt if your b399 is applicable for DLOAD - for DLOAD it should be FullOTA-MFPV, not just FullOTA-MF.
And the problem is that newer packages are no more PV distributions
Have you tried Factory Reset and Clear Cache from Recovery or eRecovery?
Connect the switched off phone to the charger and switch it on by pressing and keeping pressed Vol+, and by pressing Pow.
Phone will boot to eRecovery.
Choose Install Latest version and Recovery to reinstall the whole firmware - you must have WLAN connection that eRecovery can download from.
Follow by Factory Reset from eRecovery and Clear Cache.
There should be also an option in HiSuite on the PC to force reinstallation of the firmware (sorry, I didn't try, not using HiSuite)
Firmware can be also (re)installed from Firmware Finder, but it requires changing the DNS server on your home WLAN.
Btw, c432 means the pan-European cust, hence you may even go with the newer b504/b505 but eRecovery method will not offer them to you.
There are other methods, HWOTA/HWOTA7 to (re)install FullOTA-MF firmware which is not PV (only PV is applicable for DLOAD), but they require the unlocked Bootloader
PS: If eRecovery reinstallation fails, then you can install the following EVA-L19c432b399 package by DLOAD:
https://androidhost.ru/6se
When you download, you have to unzip, there are might be further zipped or archived folders.
Eventually you will find a Documentation folder with the guides for installation (this is internal Huawei package for service repair) and Software folder that must contain the usual three ZIP installation files.
Those three ZIP files (do not unzip them) are applicable for DLOAD - indeed, in the Installation guide in the Software folder, DLOAD installation must be described.
(I didn't try this particular L19c432b399 package but I tried for DLOAD and it worked two other service restore packages from the same source, and they had the Documentation/Software structure as described)
You made my day
I don't know about eRecovery and this method solve my problem. Bluetooth work great, camera and much more app come back
Thanks for you help
Hi, i managed to downgrade my p20 pro from Emui 10 to 9.1 and i tried to downgrade it even further to 8.1 using Hisuite software, i used hisuite proxy and firmware finder to get the firmware needed, after installing it a message popped up in my phone showing an error in the installation and that i should boot in Erecovery (seems a bad firmware) when i clicked the phone went black, i can't boot in any of the fastboot nor recovery.. i attached a screenshot it seems that the phone is identified on the pc. is there any kind of solution to enter the recovery so that it can be recognized on Hisuite please ?
ps : the device seems in fastboot but doesn't turn on
Try this guide https://forum.xda-developers.com/t/...2-here-is-the-situation-and-solution.3878714/
Hey everyone,
after spending about 5 hours trying everything I could think of and what I found in all kinds of forums, I'll try here before the phone is gonna be burried.
Got a "dead" P10 from a friend - booted straight to an error page with the headline "Your device has failed verification and may not work properly." My guess is that it was supposed to be updated, didn't have enough memory and then crashed.
Here's what I tried:
Factory reset - aborts at about 25%.
Download of a new firmware version via WLAN - aborts
Upload via SD-Card (dload) - firmware update failed
The phone is not recognized on the PC - so wouldn't know how to flash it from there.
I can still access it via fastboot, but I actually don't now how that could help me
Can anyone think of anything else that could be done?
LG
Maxi
Somebody got any idea?