Related
Hello guys!
I have bricked my P9 EVA-L09 today. i want to update it to android 7 with update from erecovery. i put files from update_data_full_hw_eu.zip and it went good but phone wont boot up and the second file "update.zip" ive extracted to dload but phone cant install it. I've tried many things to unbrick my phone but i cant do it. flashing system via fastboot is impossible cause it says that it cant be written. i have no root ant no bootloader unlocked. Please help me guys QQ
If you have C432, try this:
1. install via sdcard + 3buttons UPDATE.app from HUAWEI_P9_Rollback Package_EVA-L19_from Android 7.0_EMUI 5.0_to Android 6.0_EMUI 4.1_C900B300
2. install via sdcard + 3 buttons HUAWEI_P9_Firmware_EVA-L09_Android 6.0_EMUI 4.1.1_C432B182_Western Europe
marjaN_ said:
If you have C432, try this:
1. install via sdcard + 3buttons UPDATE.app from HUAWEI_P9_Rollback Package_EVA-L19_from Android 7.0_EMUI 5.0_to Android 6.0_EMUI 4.1_C900B300
2. install via sdcard + 3 buttons HUAWEI_P9_Firmware_EVA-L09_Android 6.0_EMUI 4.1.1_C432B182_Western Europe
Click to expand...
Click to collapse
that's the question, because i dont remember my previous working build but ill try this two packages anyway, thanks a lot for your reply
edit: now i cant even go to recovery after flashing rollback :/
edit2: i know why, you posted rollback for eva-L19 and i just copied it and flashed but phone have installed it correctly and i cant go to recovery :'(
Nobody can help me? :crying::crying::crying:
power off, then press the Power + voulume +, wipe data+cache
ziemiak said:
that's the question, because i dont remember my previous working build but ill try this two packages anyway, thanks a lot for your reply
edit: now i cant even go to recovery after flashing rollback :/
edit2: i know why, you posted rollback for eva-L19 and i just copied it and flashed but phone have installed it correctly and i cant go to recovery :'(
Click to expand...
Click to collapse
try installing 6.0 firmware for you model.
i cant go to eRecovery, i cant even shut down device - only full discharge can make it.But i can go to fastboot. Ive tried with fastboot commands but i have locked bootloader and every time my flashes are rejected by phone. The simpliest metod - HiSuite send me message: "no recovery packages are found for your phone model". It should be a way to unbrick it with fastboot but i dont know how.
Hi I was in your shoes yesterday I had to pay for the dn Phoenix to fix my phone it uses a backdoor to install firmware from fastboot
You could try and look for the backdoor commands I found this , I would post a link but can't yet
fastboot oem backdoor info
FB LockState: LOCKED
USER LockState: LOCKED
fastboot oem backdoor get
FBLOCK**obfuscated**
fastboot oem backdoor end
remote: fastboot stat not match
fastboot oem get-bootinfo
locked
fastboot oem check-rootinfo
old_stat: SAFE
now_stat: SAFE
change_time: 0000000000
fastboot oem check-image
secure image verify success
fastboot oem relock
remote: stat not match
fastboot oem backdoor set
remote: data parse fail
fastboot oem frp-erase
Haven't tried, but should remove the Factory Reset Protection (FRP)
fastboot oem emmc_diag
cid info:
mid 17,oid 256,pnm 064G70,prv 0.0,psn 0x18b66278,
csd dump:
D02700320F5903FFFFFFFFEF864000AB00
ext_csd dump:
...
FMW FAIL! WRITE PROTECT!
fastboot oem emmc-dump
unknown status code
fastboot oem get_key_version
huawei_key_v1
fastboot oem battery_present_check
3984mv
fastboot oem get_hwnff_ver
Ver2.3
fastboot oem get-psid
SN:**YourIMEI**
fastboot oem get-build-number
V100R001C00B000
fastboot oem get-product-model
HUAWEI M2-A01W
I will try to send my Huawei to warranty service and if they wont repair my phone ill pay for DC Phoenix too
I had the same problem!
Hi there.
Was in the same situation as you not so long ago.
Get a micro SD card, plug into PC, create a dload folder then download the rollback file from the Huawei website.
I'm a new user so can't post URL. Just Google "Huawei P9 rollback" should be the 2nd option (consumer.huawei link)
Put in the dload folder and put into your P9.
Press and hold power, vol up and down together till the Huawei logo appears and let go when you feel the vibrate.
This should force update and restart. (does not rollback to email 4.1, only unlocks the rollback from emui 5)
Next you need to download your previous firmware, in my case I'm in the UK with unlocked P9, so I downloaded EVA-L09C432B166.
Same again, put micro SD into PC, delete the rollback file and put your firmware in its place.
Put back in the P9 and repeat the above force update.
This will put you back to working stable stock.
For further reassurance, download a build previous to B166 so when it's up and running you can search for an OTA update to make sure all is in order.
Hope this helps.
Did you meant that the rollback flashes without going to eRecovery? I said some posts earlier that i cannot enter eRecovery so i cant dload anything. Im stuck on Huawei logo all the time do you think than i can flash something via dload without going to eRecovery?
erecovery is different.
I'm saying to do a force update, but in order to do so you need a microSD card.
Erecovery involves holding power up while connecting to PC in order to use HiSuite etc to recover.
Force updater tells the phone to search for dload folder on SD card or phone and install the update before trying to boot up OS.
So, if you connect microSD to your PC via a card reader etc and not via your phone, you can create a dload folder, download the rollback file from Huawei (above) the file is only around 80mb or so, plug the SD card back into your phone while powered off, hold down Power + vol up + vol down. The Huawei logo will appear, when it disappears let go of all the buttons. This should bring up the Update screen.
At this point the phone will install the rollback file. and this will bypass the rollback prevention in emui 5 and therefore allow you to install a previous emui build (4.1)
Again though your phone will still not boot at this point as there is no OS working or installed.
So you need to download the corresponding firmware for your phone/country/operator. Once downloaded, remove the memory card from the phone, connect to PC via card reader, delete the rollback file you placed in the dload folder and replace it with the downloaded OS and repeat the process used to install the rollback.
From there you should be back to stock marshmallow.
I should point out the files you download may be in zip folders. You need to extract the "update" file and that's what you place in the dload folder.
Hope this all makes sense, if not I can make a YouTube video and post it.
Good luck.
Now i know what did you mean, but sadly i cant update it too. I tried with my friend's P9 and when i hold these 3 buttons then shows special update screen and in my P9 it doesnt probably because of my bad flash rollback for P9 EVA-L19 and i have EVA-L09 model
http://www.android-hilfe.de/thema/downgrade-von-b360-zurueck-auf-b182.813366/
You must first make a step.
Only http://download-c.huawei.com/download/downloadCenter?downloadId=92743&version=363740&siteCode=de
Then
http://download-c.huawei.com/download/downloadCenter?downloadId=91783&version=358257&siteCode=de
're After You on MM and then can do what you want.
In the first link is a guide.
I did the same thing is what you doing today I've tried this and it fixed my phone
ziemiak said:
Now i know what did you mean, but sadly i cant update it too. I tried with my friend's P9 and when i hold these 3 buttons then shows special update screen and in my P9 it doesnt probably because of my bad flash rollback for P9 EVA-L19 and i have EVA-L09 model
Click to expand...
Click to collapse
The rollback package for L09 model is here: http://download-c.huawei.com/download/downloadCenter?downloadId=91892&version=363759&siteCode=es
Inform the results please.
I made a video to better understand. This wideo is showing that phone isn't searching any dload folder. https://youtu.be/oD9AI_6SqLs
edit: i have tried your advices to put rollback and try to dload it and then same with firmware but there is no reaction i didnt see there any circle with progress of flashing (like it was before i flashed rollback for L19)
Mine is now doing the exact same thing - I too tried the dload method to update from C432B182 to C432B361 and it's screwed my device up too.
Until I tried to use the 'rollback' package, it would at least allow me to power off, so I could get back into the Update screen - after doing that, and trying the B182 again, it's got into this position where I can do literally nothing with it. No combination of buttons, no matter how long I try to hold them, seems to do anything.
An update...
After letting my battery drain completely, I have been able to get into Fastboot mode, by pressing and holding the Volume Down button whilst connecting a USB cable to my PC.
From here, I have been able to run DC-Phoenix, and have been able to write some .APP files to it - which has at the very least got it booting into eRecovery, rather than the boot loop it had before, but is still not fully booting.
It looks like I might need the full, original firmware, in order to proceed?
And I've got about 68 hours left to flash using DC-Phoenix, or I'll have to spend another €15!
Yes you download the original firmware unzip it and put it in the "dload" folder of SD card then do a force update. Hold all the buttons vol + vol - and power
hi everyone...Please help!
I would like to update to( L19C636B361 EMUI 5.0). But I am stuck at a bootloop as I flashed in the wrong order. I first flashed the update.app (HUAWEI P9 Rollback Package-EVA-L19, from EMUI5.0+Android7.0 rollback to EMUI4.1+Android 6.0, C900B300) instead of updating to update.app(L19C636B361) [ wrong SD card inserted].
Then the phone rebooted and I got into the bootloop at Huawei logo. It cannot be turned off. It can only go into fastboot mode. Bootloader is locked and I cannot unlock it (though I havent unlock code). I tried adb/fastboot
There is always an error:
"FAILED: Remote: Command not allowed"
Now I tried to extract (L19c636b190) system.img , recover.img, boot img, flash it via adb/fastboot, but all failed. When I try to get into fastboot it says locked for both lines, and HiSuite tells me it has no software version for this phone version to repair the phone.
Could anyone help me solve the above situation?
Big [email protected]@
Anyone can help....please.
Coz i bring it to the service center, they charge me a unresonable price.
Try with the Marshmallow version and three buttons
Hey buddy. I had the same situation. Here is what I did: First format your sd card. After then download the right firmware where you can find at the huawei support official web page. After than try dload method. First time it will fail but your phone will open. Do a factory reset. Open your phone and flash firmware with dload method again. This time it will be successful and your phone will be stock. Just try. Sometimes methods fail bcoz of wrong files or sd card mistakes.
hiphoplife77 said:
Hey buddy. I had the same situation. Here is what I did: First format your sd card. After then download the right firmware where you can find at the huawei support official web page. After than try dload method. First time it will fail but your phone will open. Do a factory reset. Open your phone and flash firmware with dload method again. This time it will be successful and your phone will be stock. Just try. Sometimes methods fail bcoz of wrong files or sd card mistakes.
Click to expand...
Click to collapse
hi buddy, thanks for your reply
I follow your instrustions, i download the firmware on huawei web site {huawei_Asia_L19c636b190_16_01_2017(3,246,250kb)} with SD card format (fat32) or (exFat). Itried to dload method, I hold volume+- and power key and plug in to computer(windows 10). The phone will vibrate after 5 seconds. But it stuck into huawei logo,it cannot move forward to EMUI update. Besides, the notification light is red and flashing. Reboot and reboot again.
On the other hand, i tried the fastboot mode. I confirmed my device driver works with window, but i don't have any unlock code in order to flash any 3rd party rom. In my P9 , It showed "phone lock" & FRP Lock".
How did you work with dload method? Please kindly share with me ...thank for your reply again.
I had same issue with L19C432B378 92mb rollback file, first time bootloop. Try 5-6 times with 3 button restart and finally enter dload mode.
Second time 92mb flashing and my phone boot L19C900B300.
If there is red led notification, you are out of battery. Charge it about 15 minute first. So card format must be fat32 and fully formatted, not quick format. After than dload method. One more thing; dont plug your phone when trying dload method. Just hold 3 button about 10 seconds. Just try again. If you have right firmware, you will be successful.
hiphoplife77 said:
If there is red led notification, you are out of battery. Charge it about 15 minute first. So card format must be fat32 and fully formatted, not quick format. After than dload method. One more thing; dont plug your phone when trying dload method. Just hold 3 button about 10 seconds. Just try again. If you have right firmware, you will be successful.
Click to expand...
Click to collapse
Hi,
I have the same problem. After trying update in dload mode stuck in bootloop mode. I tried several times to reenter dload mode, but unsuccessful. Now I am out of battery and didn't want to charge in any mode.
Keep restarting every time I put it to charge. Any idea how to charge the battery?
Thanks
Did you got any solution?? Im having the same problem right now
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
my question is... how i can install new system with locked bootloader when i have access only to a fastboot, please help me.
werindam said:
my question is... how i can install new system with locked bootloader when i have access only to a fastboot, please help me.
Click to expand...
Click to collapse
How do you expect anybody can help you if you don't provide practically no info at all (not even were you running MM, N, O, stock or custom ROM)
- what was the last build you were running (full stock build name, inclvariant, cust, number)
- were xou running custom ROM and which one
- stock recovery or TWRP (which)
- shortly what were you doing when you bricked the phone
Also, do you have bootliader unlock code, and is FRP locked or not (you can see in fastboot).
zgfg said:
How do you expect anybody can help you if you don't provide practically no info at all (not even were you running MM, N, O, stock or custom ROM)
- what was the last build you were running (full stock build name, inclvariant, cust, number)
- were xou running custom ROM and which one
- stock recovery or TWRP (which)
- shortly what were you doing when you bricked the phone
Also, do you have bootliader unlock code, and is FRP locked or not (you can see in fastboot).
Click to expand...
Click to collapse
I dont know last build name - it was stock firmware and recovery
I just factory reset and then phone showing up that i must to enter last google account used in this phone. Thats my mom phone and she has no idea of any information about google acc and she only told me that someone who she bought from this phone maked account ahh.. Sorry for my english
And no, i dont have bootloader unlock code because i dont know how to get it.. and frp is locked
werindam said:
I dont know last build name - it was stock firmware and recovery
I just factory reset and then phone showing up that i must to enter last google account used in this phone. Thats my mom phone and she has no idea of any information about google acc and she only told me that someone who she bought from this phone maked account ahh.. Sorry for my english
And no, i dont have bootloader unlock code because i dont know how to get it.. and frp is locked
Click to expand...
Click to collapse
Do you know how many 'stock ROM and recovery' versions exist, and each may need different procedure to restore your phone
If it is P9 (single SIM, hence L09) -not Dual SIM (L19 or AL10) or Lite or Plus - it can be cust c432, c185 c900, etc, with Android 6 (builds 1xx, 2xx) or Android 7 (builds 3xx, 5xx) - all are stock firmwares
Are you familiar with Fastboot, or maybe the safest way will be to go to service (specially if still under guarantee)
zgfg said:
Do you know how many 'stock ROM and recovery' versions exist, and each may need different procedure to restore your phone
If it is P9 (single SIM, hence L09) -not Dual SIM (L19 or AL10) or Lite or Plus - it can be cust c432, c185 c900, etc, with Android 6 (builds 1xx, 2xx) or Android 7 (builds 3xx, 5xx) - all are stock firmwares
Are you familiar with Fastboot, or maybe the safest way will be to go to service (specially if still under guarantee)
Click to expand...
Click to collapse
yea i know, and if its way to restore somehow this p9 i will can do that via fastboot, just dont know how
Its p9 single sim l09. i think it was c432 rom
Since you didn't unlock Bootloader it must not be scr***ed up severely.
Try the following (independent of your prev build, no need for Fastboot, open Bootloader and other hacking tricks):
- Power off
- Connect by USB cable to the charger
- Must be in the range of reliable WiFi
- Press Vol+ & Pow (in that order) and keep pressing
It shall boot to eRecovery, giving you options to download and reinstall your whole stock firmware
Advice: When you restore, take and save screenshots from About, to know your build, IMEIs, etc
Ive got error : Getting package info failed
you need sd card. in sd card create "dload" folder, in folder copy this update.app link here oh, first link are for eva-l19 here are for eva-l09
then, insert sd card in phone, press and hold vol+ and vol - and power button (hold all buttons till see update things)
after that, download this (or download all at once) link here and delete update.app in dload folder at sd card, and copy all from this b136 download, need to be 2x folder and update.app now larger file than first. and do dload method once more (vol+, vol- and power till update starts)
ah, but you need to charge pgone atlest to 50% to be succes with dload method!
Arnys said:
you need sd card. in sd card create "dload" folder, in folder copy this update.app link here
then, insert sd card in phone, press and hold vol+ and vol - and power button (hold all buttons till see update things)
after that, download this (or download all at once) link here and delete update.app in dload folder at sd card, and copy all from this b136 download, need to be 2x folder and update.app now larger file than first. and do dload method once more (vol+, vol- and power till update starts)
ah, but you need to charge pgone atlest to 50% to be succes with dload method!
Click to expand...
Click to collapse
ok, ill try this
werindam said:
ok, ill try this
Click to expand...
Click to collapse
i edited my writes, first link are wrong, use second for eva-l09
Error: Software install failed.. ;/
battery charged? in eRecovery can see, or turn off phone and put to charger, need to be 50% (some other says need to be 70%)
Hello, i have a similar issue, but i can't boot. My phone bootloop every single time. I can't boot to recovery but i can boot in fastboot. i was in c432b382 and i tried to flash a c432b378 update to have android N
Hi
I installed openkirin RR OS B2 on my P9. I want to back to stock FW. P9 is Rebranded to AL10. Thanks for help.
Makoj said:
Hi
I installed openkirin RR OS B2 on my P9. I want to back to stock FW. P9 is Rebranded to AL10. Thanks for help.
Click to expand...
Click to collapse
Look into the corresponding threads, OpenKirin and Rebranding (Oreo)
Hello, i tried to install official rom via twrp and its end with error. I turned off my huawei (reset in twrp) and phone is dead. No reaction to charger, pc doesnt see phone, no boot. Any ideas what can i do? Please help
gabrylo97 said:
Hello, i tried to install official rom via twrp and its end with error. I turned off my huawei (reset in twrp) and phone is dead. No reaction to charger, pc doesnt see phone, no boot. Any ideas what can i do? Please help
Click to expand...
Click to collapse
It has been described and repeated elsewhere !(people don't read and try on their own, bricking the phones), stock ROMs must not be installed by TWRP (it was possible but only for the old FullOTA-MF-PV firmwares but newer Huawei firmwares are no more released as PV).
There are other methods applicable like HWOTA - that use TWRP but not just by flashing the update*** zip files through TWRP
Also, it must not be reset from TWRP, must be used Factory Reset from eRecovery or stock/EMUI Recovery
Even worse if you maybe did not use proper TWRP build - Huawei MM, N, O firmwares have different organization of partitions and apply different encryption, using the wrong TWRP will also brick the phone
You should probably try to un-brick with DC Phoenix, with 15 Euros credit
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
i tried test point and pc recognizes device as "usb ser" in device manager