Huawei Wtf! - Huawei P9 Questions & Answers

My friend have Problem his device after trying to install custom ROM just a reboot but not go into system so he go to Huawei shop and I wait 3 days after that told him should go to another shop We can't fix it!, but before that his phone his phone open bootloader and can use ADB ،When the device is returned from him it's locked and can't open bootloader or do anything ،They told him not responsible for this and can't the installation the system in his device wtf Huawei Oh really !

So he needs his phone, I take phone but does not can't do anything like open bootloader or any thing with ADB or format and His system was returned to Android 6 !

albelushi7 said:
My friend have Problem his device after trying to install custom ROM just a reboot but not go into system so he go to Huawei shop and I wait 3 days after that told him should go to another shop We can't fix it!, but before that his phone his phone open bootloader and can use ADB ،When the device is returned from him it's locked and can't open bootloader or do anything ،They told him not responsible for this and can't the installation the system in his device wtf Huawei Oh really !
Click to expand...
Click to collapse
If your friend was able to flash custom ROM, he had to have Bootloader unlocked.
It means that he did have Bootloader code - he had to keep it because same Bootloader code is good for the same phone for the whole life. Unfortunately, people didn't dare to care about that, similarly like not caring to learn first (before they bricked the phones) about what and how to flash - this is unfortunately one of the reasons (bad posts on Internet) that Huawei changed the policy about BL codes (and now everyone, also those who do care what and how) suffer.
Anyway, for P9 you can still buy the BL code for 4-5 USD.
Also, if they returned the phone unbricked, with MM, you should be able to upgrade to Nougat by DLOAD, not needing to unlock BL (ir they didn't put c300 MM)

zgfg said:
If your friend was able to flash custom ROM, he had to have Bootloader unlocked.
It means that he did have Bootloader code - he had to keep it because same Bootloader code is good for the same phone for the whole life. Unfortunately, people didn't dare to care about that, similarly like not caring to learn first (before they bricked the phones) about what and how to flash - this is unfortunately one of the reasons (bad posts on Internet) that Huawei changed the policy about BL codes (and now everyone, also those who do care what and how) suffer.
Anyway, for P9 you can still buy the BL code for 4-5 USD.
Also, if they returned the phone unbricked, with MM, you should be able to upgrade to Nougat by DLOAD, not needing to unlock BL (ir they didn't put c300 MM)
Click to expand...
Click to collapse
Thanks for your reply, now cant flash anything < . I try to fix what can be fixed, he has the code but now when doesn't work or something is wrong, when try with ADB to unlock bootloader (.. "FAILED > emote: Command not allowed) also FRP LOCK .
i try many version with DLOAD but does not work! < Maybe can give me to try it ! another thing when try to format It seems not working only 2 % .fact now I do not know what to do with his phone but I will try!

To unlock FRP, you must unlock OEM from Settings, Development menu.
As you described, phone was bootable (to MM) when returned from service - but now, after the failed DLOADing, etc, is it bootable any more
You cannot DLOAD any P9 firmware to any P9 phone. Firmware must be:
- of the same model and cust (otherwise you first needed to rebrand)
- it must be shown eg in FirmwareFinder as FullOTA-MF-PV (not just FullOTA-MF)
If not cared about (specially about model and cust) - no wonder if it bricked the phone
If you cannot boot anymore to read full model, cust and build number from Settings, About, you can read from Fastboot (switch off, connect to PC, press and keep pressing Vol-, boot by Pow). You will need ADB & Fastboot installed on your PC - if not, search for Minimal ADB and Fastboot on XDA and install.
You can copy to bat file and execute:
Code:
fastboot devices
PAUSE
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

zgfg said:
To unlock FRP, you must unlock OEM from Settings, Development menu.
As you described, phone was bootable (to MM) when returned from service - but now, after the failed DLOADing, etc, is it bootable any more
You cannot DLOAD any P9 firmware to any P9 phone. Firmware must be:
- of the same model and cust (otherwise you first needed to rebrand)
- it must be shown eg in FirmwareFinder as FullOTA-MF-PV (not just FullOTA-MF)
If not cared about (specially about model and cust) - no wonder if it bricked the phone
If you cannot boot anymore to read full model, cust and build number from Settings, About, you can read from Fastboot (switch off, connect to PC, press and keep pressing Vol-, boot by Pow). You will need ADB & Fastboot installed on your PC - if not, search for Minimal ADB and Fastboot on XDA and install.
You can copy to bat file and execute:
Code:
fastboot devices
PAUSE
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
Click to expand...
Click to collapse
fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.013s]
finished. total time: 0.014s
-----
fastboot oem get-product-model
...
(bootloader) EVA-L19
OKAY [ 0.011s]
finished. total time: 0.012s
----
fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.010s
------
fastboot oem get-build-number
...
(bootloader) :System 8.0.0.046(0OHZ)
OKAY [ 0.011s]
finished. total time: 0.012s
-----
fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Command not allowed)

albelushi7 said:
fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.013s]
finished. total time: 0.014s
-----
fastboot oem get-product-model
...
(bootloader) EVA-L19
OKAY [ 0.011s]
finished. total time: 0.012s
----
fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.010s
------
fastboot oem get-build-number
...
(bootloader) :System 8.0.0.046(0OHZ)
OKAY [ 0.011s]
finished. total time: 0.012s
-----
fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
According to:
Code:
(bootloader) locked
your Bootloader is locked.
Does the Fastboot show also FRP locked?
And you cannot login to Android (to unlock OEM=FRP)?
According to:
Code:
(bootloader) EVA-L19
vendorcountry: hw/meafnaf
Your P9 should be L19 (dual SIM), and you had c185 Middle East cust.
From your previous posts, phone was on MM (EMUI 4), maybe you successfully upgraded to Nougat (EMUI 5)
But according to:
Code:
(bootloader) :System 8.0.0.046(0OHZ)
you attempted to flash some Oreo (EMUI 8) - and that bricked the phone?!

zgfg said:
According to:
Code:
(bootloader) locked
your Bootloader is locked.
Does the Fastboot show also FRP locked?
And you cannot login to Android (to unlock OEM=FRP)?
According to:
Code:
(bootloader) EVA-L19
vendorcountry: hw/meafnaf
Your P9 should be L19 (dual SIM), and you had c185 Middle East cust.
From your previous posts, phone was on MM (EMUI 4), maybe you successfully upgraded to Nougat (EMUI 5)
But according to:
Code:
(bootloader) :System 8.0.0.046(0OHZ)
you attempted to flash some Oreo (EMUI 8) - and that bricked the phone?!
Click to expand...
Click to collapse
the FPR loked its showed in fastboot and the system not boot anymore
actually its 8 oreo When I checked it through adb , but i said m.m Because recovery and erecovery like on emui4 !
also when i try use Erecovery Touch Not working to Connect to Wi-Fi !
Yes is P9 L19 c185 and when try use DLOAD FullOTA-MF-PV in stuck huawei logo

albelushi7 said:
the FPR loked its showed in fastboot and the system not boot anymore
actually its 8 oreo When I checked it through adb , but i said m.m Because recovery and erecovery like on emui4 !
also when i try use Erecovery Touch Not working to Connect to Wi-Fi !
Yes is P9 L19 c185 and when try use DLOAD FullOTA-MF-PV in stuck huawei logo
Click to expand...
Click to collapse
It's bricked since you flashed Oreo Bootloader over the MM or N firmware, and hence it also does not accept DLOAD
To fix, you would need to flash by Fastboot, but Bootloader is locked and you are not allowed to.
To unlock BL you would need to unlock FRP, but due to the brick you cannot enter to System to unlock OEM/FRP
Hence you are stuck…
-You can try one more DLOAD by downloading this package:
https://androidhost.ru/bN4
You will have to unzip/untar (whatever applies), you should find a folder Docs inside with the Installation guide.
This is official package for DLOAD repair (P9 L19 c185 b403) for Huawei service shops, but I'm not sure would it work over your bricked Bootlloader from Oreo
-Certainly you could recover by TestPoints (but you can also definitely brick the phone by one wrong move there),
but it requires openening back-cover, short-connecting two pins and flashing the appropriate bord firmware (you would also need TestPoints drivers).
It's risky, TG I never need it, if you want to learn about you will need to search on the Net and XDA
-Otherwise, due to the facts as above, I can only recommend you to seek for the paid help from DC Phoenix:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Ask them in advance, it might cost you cca 20 EU credits (tools and instructions for unlocking FRP and Bootloader, unbricking and flashing official Nouga firmware).
You can probably arrange also for debranding to L19 c432 Nougat if you wish
If you would then want to rebrand and upgrade to AL10 c00 b540 Oreo, you will have to start with:
- unbricked phone with latest Nougat firmware
- having Bootloader code ready
and to carefully follow OP instructions from this thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849

zgfg said:
It's bricked since you flashed Oreo Bootloader over the MM or N firmware, and hence it also does not accept DLOAD
To fix, you would need to flash by Fastboot, but Bootloader is locked and you are not allowed to.
To unlock BL you would need to unlock FRP, but due to the brick you cannot enter to System to unlock OEM/FRP
Hence you are stuck…
-You can try one more DLOAD by downloading this package:
https://androidhost.ru/bN4
You will have to unzip/untar (whatever applies), you should find a folder Docs inside with the Installation guide.
This is official package for DLOAD repair (P9 L19 c185 b403) for Huawei service shops, but I'm not sure would it work over your bricked Bootlloader from Oreo
-Certainly you could recover by TestPoints (but you can also definitely brick the phone by one wrong move there),
but it requires openening back-cover, short-connecting two pins and flashing the appropriate bord firmware (you would also need TestPoints drivers).
It's risky, TG I never need it, if you want to learn about you will need to search on the Net and XDA
-Otherwise, due to the facts as above, I can only recommend you to seek for the paid help from DC Phoenix:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Ask them in advance, it might cost you cca 20 EU credits (tools and instructions for unlocking FRP and Bootloader, unbricking and flashing official Nouga firmware).
You can probably arrange also for debranding to L19 c432 Nougat if you wish
If you would then want to rebrand and upgrade to AL10 c00 b540 Oreo, you will have to start with:
- unbricked phone with latest Nougat firmware
- having Bootloader code ready
and to carefully follow OP instructions from this thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Click to expand...
Click to collapse
I can't believe the phone back to work again!

How to bring the phone back to life and to work? The phone was restarting at the Huawei logo, adb not working and I have bootloader code but not working FPR looked and bootloader looked
Dload not working , so what I do , try use DC phoneix and go forward the bootloader unlocked and FPR but unfortunately must phone go to update mode but unfortunately now stuck again with no fastboot and no recovery !
finally I try with testpoint with IDM and Huawei bored and working!
and upgrade or install system with dload
After that install Android 7 and update to Oreo 8 with TWRP ?.

Related

Question about

Hi everybody, I have a little question regarding my P10.
The model of my phone is VTR-L09C521B101
Is there a way to flash this phone with VTR-L09C432 version?
or i need to flash with same model version (VTR-L09C521)?
Thnks
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
M1chiel said:
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
Click to expand...
Click to collapse
thanks for the answer!!
regarding bootloader, the phone shows this:
PHONE RELOCKED
FRP LOCK
ADB shows me that the phone is unlocked, the problem is when I try to send something to phone it shows:
Error Remote command not allowed.
any ideas?
thanks!
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Quintman said:
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Click to expand...
Click to collapse
Quintman, no the phone is not listed with adb devices command. I can only enter with fastboot.
Let me paste the commands that I have tried:
C:\adb>fastboot devices
WPG7N17320000978 fastboot
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\adb>fastbot oem lock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem unlock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem relock <my_unlock_code>
...
FAILED (remote: stat not match)
finished. total time: 0.016s
The Strange thing is that in the phone shows PHONE RELOCKED, not unlocked as ADB shows.
Since I uploaded boot img of another version (C432) full OTA, could this be the problem? in this case what can I do?
thanks for your help!!
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
fmm1977 said:
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
Click to expand...
Click to collapse
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Quintman said:
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Click to expand...
Click to collapse
Ok, this is what I've done step by step:
1.- With the unlock code provided by huawei, I have unlocked my phone (my version is VTR-L09C521B101 stock)
2.- Once unlocked, I have downloaded another ROM version (VTR-L29C605B151) in the web page says this rom is for latin america), so with the Huawei Update Extractor, I have extracted all files.
3.- Via ADB/FASTBOOT, I sent the files to my phone, boot.img first and then the others. (big big mistake!)
4.- Rebooted the phone, and then keeps restarting at huawei logo.
5.- Seeing that it did´t worked, what I did was to lock the phone again thinking to send it to Huawei (at this point the phone shows as "unlocked" via fastboot commands, however when I start the phone in fastboot mode, in the screen shows "PHONE RELOCKED, FRP LOCK"
6.- Sent to huawei's service, they said that they cannot fix my phone because it was tampered/rooted.
7.- Right now all I need to fix my phone is to LOCK/UNLOCK again in order to rebrand it to L29 version, since the original stock rom dont exist (not as FULL OTA).
And that´s what I did so far my friend.
Questions:
1.- Is there a way to connect to my phone and change the oem info file? or something?
2.- Do I need to wait the stock rom to be released in order to reflash via Dload method?
3.- What if the stock ROM version of my phone is never released?
thank you for your answer my friend!!
Hmm ok. I am just not sure on your step 3, I've never heard of a method that involves a boot.img... what I would suggest, is to try and download the stock firmware files (need the larger full ota files), extract the update.app file and put on sd card in \dload.
Then hold down both volume up and down and power (3 button method)
It will try and flash the stock image back to the phone.
I just tried the Dload method and nothing happened (always stuck in 5%), now im going to try to use a smaller memory card (mine is 64 Gb). lood
U have disconnected the USB cable when u try 3 button update
berka38 said:
U have disconnected the USB cable when u try 3 button update
Click to expand...
Click to collapse
Yes sr!!

P9 rescue - only fastboot (Help please)

Hi,
I have a P9 here I'm was asked to repair. I think it is kind of bricked and I hope some one can help me to unbrick it.
According to the auto dc-unlocker identification:
Found Phone : EVA-L09
Firmware : EVA-L09C432B386
FB LockState: LOCKED
USER LockState: LOCKED
So, bootloader locked and FRP locked. I don't know if the Firmware version above is right. All I know is that some Update.app files were flashed to the state of the phone now and before there where bootloops while the start animation and stuck boot with black screen.
At the moment I can do:
- turn on to see only the first huawei log with "powered by android", then nothing happens
- I can not enter eRecovery or update for Update.app
- I can only enter fastboot
I have the unlock code for the bootloader. I can not commit any fastboot commands (oem unlock, flash, etc) all is blocked with:
FAILED (remote: Command not allowed)
The locked FRP should be the reason for this.
I think OEM-unlock and usb debug from developer section was not enabled as the phone was usable. adb commands like "adb reboot bootloader" fail with
error: device '(null)' not found
fastboot devices shows the device
I have tried to uncharge the battery and then try to enter other modes than fastboot. No luck with that.
Do I have any chance to unbrick it without paying for the dc-unlocker/phoenix?
Can I do something with SRKTool?
If I have to use unlocker,
- do I have to unlock the bootloader?
- should I flash the same firmware that is now on the phone (B386) and where can I find it? (found only 1000 other versions until now)
Hope for answers
I've gone through that before, but ended up using DC-Phoenix to unbrick it when it's FRP and bootloader locked. Cost me about $15. There is a post on how to do this but I'll have to search for it again.
Here is the post I used:
https://forum.xda-developers.com/showpost.php?p=71767614&postcount=7
I guess you enter fastboot by Vol- and Power?
Not sure if the following method could help you with, but you can analyze before you go for dc-phoenix:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
scammander said:
Hi,
I have a P9 here I'm was asked to repair. I think it is kind of bricked and I hope some one can help me to unbrick it.
According to the auto dc-unlocker identification:
Found Phone : EVA-L09
Firmware : EVA-L09C432B386
FB LockState: LOCKED
USER LockState: LOCKED
So, bootloader locked and FRP locked. I don't know if the Firmware version above is right. All I know is that some Update.app files were flashed to the state of the phone now and before there where bootloops while the start animation and stuck boot with black screen.
At the moment I can do:
- turn on to see only the first huawei log with "powered by android", then nothing happens
- I can not enter eRecovery or update for Update.app
- I can only enter fastboot
I have the unlock code for the bootloader. I can not commit any fastboot commands (oem unlock, flash, etc) all is blocked with:
FAILED (remote: Command not allowed)
The locked FRP should be the reason for this.
I think OEM-unlock and usb debug from developer section was not enabled as the phone was usable. adb commands like "adb reboot bootloader" fail with
error: device '(null)' not found
fastboot devices shows the device
I have tried to uncharge the battery and then try to enter other modes than fastboot. No luck with that.
Do I have any chance to unbrick it without paying for the dc-unlocker/phoenix?
Can I do something with SRKTool?
If I have to use unlocker,
- do I have to unlock the bootloader?
- should I flash the same firmware that is now on the phone (B386) and where can I find it? (found only 1000 other versions until now)
Hope for answers
Click to expand...
Click to collapse
So you can not update via dload method? Did you try booting into recovery (not Recovery)? And you can't update with Update.app, you need to flash update.zip and full_update.zip via TWRP or Recovery. What wanted the owner of this phone to do, that he bricked it ?
Thank you all for your answers. Like I tried to describe: I was not able to access any other mode than fastboot.
"was able": I used DC-Phoenix now and it worked just fine.
Little confusing is that in all tutorials, even the on on the DC site, the UI of the tool is different.
But that's now Problem. The current Version is lot easier. Just "Standard Mode", select Update.app (full), Click Update.
The Phone gets flashed with fastboot, DC will restart it to update mode and will flash again. All automatic.
Really easy.
so you paid 15 USD ?
DallasCZ said:
so you paid 15 USD ?
Click to expand...
Click to collapse
Yes I did, and it worked.

fastboot status: PHONE Relocked, FRP Lock

hello,
have a problem with P10 stuck in Fastboot:
PHONE Relocked (green)
FRP Lock (green).
cmd command doesnt work (Before i used same comp and device many times and worked fine) to relock or unlock oem. (FAILED (remote: Command not allowed))
after debrand from VTR L09 to VTR L29 i have a new IMEI . So seems i must to get new code for unlock Bootloader ? is this a problem ? tested with new bootloader code but nothing. (FAILED (remote: Command not allowed).
?
maybe i can rollback to older emui (ex emui4) because UPDATE .app is less than 4gb ? (dload at sdcard ?)
thank yours for help
wrong section.
skiswim said:
hello,
have a problem with P10 stuck in Fastboot:
PHONE Relocked (green)
FRP Lock (green).
cmd command doesnt work (Before i used same comp and device many times and worked fine) to relock or unlock oem. (FAILED (remote: Command not allowed))
after debrand from VTR L09 to VTR L29 i have a new IMEI . So seems i must to get new code for unlock Bootloader ? is this a problem ? tested with new bootloader code but nothing. (FAILED (remote: Command not allowed).
?
maybe i can rollback to older emui (ex emui4) because UPDATE .app is less than 4gb ? (dload at sdcard ?)
thank yours for help
Click to expand...
Click to collapse
i solve this problem with this method : https://forum.xda-developers.com/p1...-stock-erecovery-dns-ff-t3730077#post75085397

soft briked my Huawei P9

if anyone help me on below much appriciated.
It seems my Huawei P9 (EVA-L19)is soft bricked as i was trying
to upgrade it to Nuget.
Now the phone cant charge even.Restatring itself & showing only
Huawei Logo.
Unable to hard reset evan. But will be able to activate fast boot mode.
( See below image)& says "Phone Locked / FRP Locked".
Also DC-Unlocker detecting the device as well.( See the 2nd image)
HiSuite does not recagnize the phone.
Is there any way to unlock through ADB or any other way.
Please help....
aselaj said:
if anyone help me on below much appriciated.
It seems my Huawei P9 (EVA-L19)is soft bricked as i was trying
to upgrade it to Nuget.
Now the phone cant charge even.Restatring itself & showing only
Huawei Logo.
Unable to hard reset evan. But will be able to activate fast boot mode.
( See below image)& says "Phone Locked / FRP Locked".
Also DC-Unlocker detecting the device as well.( See the 2nd image)
HiSuite does not recagnize the phone.
Is there any way to unlock through ADB or any other way.
Please help....
Click to expand...
Click to collapse
No pictures uploaded.
Since FRP is locked (and phone is bricked hence you cannot unlock OEM), you could not unlock Bootloader and flash.
On HCU Client they have an option to Unlock FRP (on the bricked phones) -
there were other users (particularly with P9) who similarly successfully unlocked FRP on the bricked phones by HCU Client.
Without unlocking FRP you could not flash, but you can try DLOAD.
You need to use a proper FullOTA-MF-PV package from Firmware finder (for Marshmallow and early Nougat,
there were PV firmwares on FF, they can be DLOADed with no need for TWRP, flashing, etc).
For such DLOAD you must use L19 PV firmware, same cust (like c432 or c636, etc.) that was your previous cust.
Cust cannot be changed by DLOAD or any other way, but by proper rebranding (incl. to change OEMInfo).
For the firmware version number (like b182), use the same that you had before brick, so e.g. EVA-L19c432b182 or so.
Supposidely, phone did not upgrade yet to Nougat (you said it bricked -
how were you doing upgrade to Nougat?).
If it upgraded, you will have to try Nougat FullOTA-MF-PV version for DLOAD again, of the same cust).
You can inspect what the phone rememers about its (last) firmware from Fastboot:
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry

Huawei P9 soft-bricked and unable to access any partitions

Heya! I've got the Huawei P9 rebranded on the Chinese EVA-AL10 Oreo firmware.
My phone has recently stopped working and is unable to boot into the system and recovery.
The bootloader is unlocked and it freezes on the Your device has been unlocked and can't be trusted screen that shows 3 boot options in the middle of the screen (Press power key to continue, Vol up 3 seconds for erecovery, Device will boot automatically after 5 if nothing is done on that screen). It also freezes on a similar screen without the three options if I do the Vol up + Power shortcut to enter the erecovery.
If I do the Volume up, Volume down and power boot shortcut, it boots into a screen with a green background along with a red rectangle in the upper half of the screen and a blue rectangle in the lower half. It stays on this screen for about a minute before freezing on the Your device has been unlocked... screen when it attempts to enter the erecovery.
The same screen shows when I do the Volume down and power boot shortcut when it isn't connected to my computer. The difference this time being that every time it reboots after a short period of time, it reboots into the same screen.
It is only able to successfully able to boot in the Fastboot & Rescue Mode.
Joshywooful1 said:
Heya! I've got the Huawei P9 rebranded on the Chinese EVA-AL10 Oreo firmware.
My phone has recently stopped working and is unable to boot into the system and recovery.
The bootloader is unlocked and it freezes on the Your device has been unlocked and can't be trusted screen that shows 3 boot options in the middle of the screen (Press power key to continue, Vol up 3 seconds for erecovery, Device will boot automatically after 5 if nothing is done on that screen). It also freezes on a similar screen without the three options if I do the Vol up + Power shortcut to enter the erecovery.
If I do the Volume up, Volume down and power boot shortcut, it boots into a screen with a green background along with a red rectangle in the upper half of the screen and a blue rectangle in the lower half. It stays on this screen for about a minute before freezing on the Your device has been unlocked... screen when it attempts to enter the erecovery.
The same screen shows when I do the Volume down and power boot shortcut when it isn't connected to my computer. The difference this time being that every time it reboots after a short period of time, it reboots into the same screen.
It is only able to successfully able to boot in the Fastboot & Rescue Mode.
Click to expand...
Click to collapse
For the beginning, let's see which firmware your phone thinks it is on. Execute in Fastboot and copy back results (omit output of the first line - serial number):
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
zgfg said:
For the beginning, let's see which firmware your phone thinks it is on. Execute in Fastboot and copy back results (omit output of the first line - serial number):
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
Click to expand...
Click to collapse
Code:
fastboot devices
fastboot
fastboot oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.002s]
Finished. Total time: 0.006s
fastboot oem get-product-model
(bootloader) EVA-AL10
OKAY [ 0.003s]
Finished. Total time: 0.006s
fastboot oem get-build-number
(bootloader) :EVA-AL10 8.0.0.535(C00)
OKAY [ 0.003s]
Finished. Total time: 0.007s
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :EVA-AL10C00B398
OKAY [ 0.005s]
Finished. Total time: 0.008s
fastboot getvar vendorcountry
vendorcountry: all/cn
Finished. Total time: 0.003s
The phone itself is a European model Huawei P9 EVA-L09, rebranded to EVA-AL10 using HWOTA7.
Joshywooful1 said:
The phone itself is a European model Huawei P9 EVA-L09, rebranded to EVA-AL10 using HWOTA7.
Click to expand...
Click to collapse
Do you want to go back to EVA-AL10c00 (b540 Oreo) or you want to downgrade to EVA-L09c432 (b504 Nougat)
zgfg said:
Do you want to go back to EVA-AL10c00 (b540 Oreo) or you want to downgrade to EVA-L09c432 (b504 Nougat)
Click to expand...
Click to collapse
I'm wanting to go back to EVA-AL10c00.
Joshywooful1 said:
I'm wanting to go back to EVA-AL10c00.
Click to expand...
Click to collapse
Download the official service repair for EVA-AL10c00b528:
https://androidhost.ru/6sl
Unpack until you find two folders, software with DLOAD installation and documentation with the installation guide - read and follow the guide very carefully, it describes how to perform DLOAD installation
Upon DLOAD, boot to b528 - do not setup Google account, do not restore apps or so, just connect to WiFi and check if you receive OTA updates up to b540 Patch02 (go to Settings/System/Software Update to check if OTA updates are available)
If you don't receive OTA, boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+ and boot then) and take Install latest firmware and recovery
EDIT:
Upon you update to b540 Patch02, install TWRP for Oreo, and flash Network patch (optionally also Face Unlock patch) as described in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
zgfg said:
Download the official service repair for EVA-AL10c00b528:
https://androidhost.ru/6sl
Unpack until you find two folders, software with DLOAD installation and documentation with the installation guide - read and follow the guide very carefully, it describes how to perform DLOAD installation
Upon DLOAD, boot to b528 - do not setup Google account, do not restore apps or so, just connect to WiFi and check if you receive OTA updates up to b540 Patch02 (go to Settings/System/Software Update to check if OTA updates are available)
If you don't receive OTA, boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+ and boot then) and take Install latest firmware and recovery
EDIT:
Upon you update to b540 Patch02, install TWRP for Oreo, and flash Network patch (optionally also Face Unlock patch) as described in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Click to expand...
Click to collapse
There's no installation guide in the ReleaseDocs folder. It only has several documents in Chinese (including one that tells me to use HiSuite to update my system which I'll not be able to follow as I'm unable to boot into the system). There are no documents that have DLOAD specific instructions.
zgfg said:
Download the official service repair for EVA-AL10c00b528:
https://androidhost.ru/6sl
Unpack until you find two folders, software with DLOAD installation and documentation with the installation guide - read and follow the guide very carefully, it describes how to perform DLOAD installation
Upon DLOAD, boot to b528 - do not setup Google account, do not restore apps or so, just connect to WiFi and check if you receive OTA updates up to b540 Patch02 (go to Settings/System/Software Update to check if OTA updates are available)
If you don't receive OTA, boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+ and boot then) and take Install latest firmware and recovery
EDIT:
Upon you update to b540 Patch02, install TWRP for Oreo, and flash Network patch (optionally also Face Unlock patch) as described in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Click to expand...
Click to collapse
Never mind what I said before. I've found the installation guide. It's all in Chinese so I had to put it through Google Translate so I could read it.
Joshywooful1 said:
Never mind what I said before. I've found the installation guide. It's all in Chinese so I had to put it through Google Translate so I could read it.
Click to expand...
Click to collapse
Strange, a year ago I downloaded such EVA-AL10c00b528 package from the same site and successfully unbricked.
It did have Installation guide in English
You should create DLOAD folder on your SD card, copy into the file and folder as found in the Software folder (see my screenshot), then make sure battery is 50% or more full, disconnect from USB, switch off, press and keep pressing both Vol+ and Vol-, boot
For your reference, see a similar guide from another service repair package:
https://mega.nz/#!F8UGyYQR!hOeQJyRyb13sKViCPL0XNK-cY5obHetUcvfNqHMJjTg
zgfg said:
Strange, a year ago I downloaded such EVA-AL10c00b528 package from the same site and successfully unbricked.
It did have Installation guide in English
You should create DLOAD folder on your SD card, copy into the file and folder as found in the Software folder (see my screenshot), then make sure battery is 50% or more full, disconnect from USB, switch off, press and keep pressing both Vol+ and Vol-, boot
For your reference, see a similar guide from another service repair package:
https://mega.nz/#!F8UGyYQR!hOeQJyRyb13sKViCPL0XNK-cY5obHetUcvfNqHMJjTg
Click to expand...
Click to collapse
I've just tried to enter the DLOAD mode and it just boots into the screen with a green background and 2 rectangles, a red one near in the upper portion of the screen and a blue one in the lower portion of the screen, as shown in this photo. It stays on this screen for a short amount of time before rebooting into the same screen.
Joshywooful1 said:
I've just tried to enter the DLOAD mode and it just boots into the screen with a green background and 2 rectangles, a red one near in the upper portion of the screen and a blue one in the lower portion of the screen, as shown in this photo. It stays on this screen for a short amount of time before rebooting into the same screen.
Click to expand...
Click to collapse
I never had such a brick but I remember that I saw some people reporting a screen with rectangles
You could try flashing Oreo no-check recovery:
https://mega.nz/#!UlklhYLD!rzn-ifOYF_HChWuWjYoqvcJQEXsUDE25LcQyfedKM2k
Code:
fastboot flash recovery_ramdisk eva_vie_recovery_nocheck.img
Then try to repeat DLOAD with AL10c00b528
Otherwise, there are on-line services providing paid unbrick support:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services
Even better, you can ask @Tecalote (author of HWOTA7 method for rebranding and upgrading to Chinese Oreo), look at his profile and find his gmail address (he doesn't look to XDA anymore and probably he will not answer on PM) - he is from Germany and he unbricks Huawei phones on the per-donation model
You can also open the phone and use yourself the low-level Testpoint method:
https://forum.xda-developers.com/p9/how-to/solution-dead-p9-bootloader-locked-fpr-t3997631
zgfg said:
I never had such a brick but I remember that I saw some people reporting a screen with rectangles
You could try flashing Oreo no-check recovery:
https://mega.nz/#!UlklhYLD!rzn-ifOYF_HChWuWjYoqvcJQEXsUDE25LcQyfedKM2k
Code:
fastboot flash recovery_ramdisk eva_vie_recovery_nocheck.img
Then try to repeat DLOAD with AL10c00b528
Otherwise, there are on-line services providing paid unbrick support:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services
Even better, you can ask @Tecalote (author of HWOTA7 method for rebranding and upgrading to Chinese Oreo), look at his profile and find his gmail address (he doesn't look to XDA anymore and probably he will not answer on PM) - he is from Germany and he unbricks Huawei phones on the per-donation model
You can also open the phone and use yourself the low-level Testpoint method:
https://forum.xda-developers.com/p9/how-to/solution-dead-p9-bootloader-locked-fpr-t3997631
Click to expand...
Click to collapse
I've just tried to flash that recovery and just got this output:
Code:
Sending 'recovery_ramdisk' (25668 KB) OKAY [ 0.697s]
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
zgfg said:
I never had such a brick but I remember that I saw some people reporting a screen with rectangles
You could try flashing Oreo no-check recovery:
https://mega.nz/#!UlklhYLD!rzn-ifOYF_HChWuWjYoqvcJQEXsUDE25LcQyfedKM2k
Code:
fastboot flash recovery_ramdisk eva_vie_recovery_nocheck.img
Then try to repeat DLOAD with AL10c00b528
Otherwise, there are on-line services providing paid unbrick support:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services
Even better, you can ask @Tecalote (author of HWOTA7 method for rebranding and upgrading to Chinese Oreo), look at his profile and find his gmail address (he doesn't look to XDA anymore and probably he will not answer on PM) - he is from Germany and he unbricks Huawei phones on the per-donation model
You can also open the phone and use yourself the low-level Testpoint method:
https://forum.xda-developers.com/p9/how-to/solution-dead-p9-bootloader-locked-fpr-t3997631
Click to expand...
Click to collapse
I've attempted to use DC-Phoenix to unbrick my phone and it always fails, saying
Code:
Cannot enter in Recovey mode
. I don't have the right screwdriver to remove the screws from my phone, so I can't do the testpoint method either. Is there anything else I could do?
Joshywooful1 said:
I've just tried to flash that recovery and just got this output:
Code:
Sending 'recovery_ramdisk' (25668 KB) OKAY [ 0.697s]
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Click to expand...
Click to collapse
Per your previous Fastboot results, Bootloader is unlocked.
On the Chinese firmware FRP is unlocked by default, there was even no OEM Unlock option in Developers menu
So what is blocking your Fastboot to flash - on the Fastboot screen, bottom part, what does it say, Phone locked (green) or Phone unlocked (red), and similarly, FRP locked or unlocked?!
zgfg said:
Per your previous fastboot results, Bootloader is unlocked.
On the Chinese firmware FRP is unlocked per default, there was even no OEM Unlock setting in Developers menu.
So what is blocking Fastboot to flash - on Fastboot screen, bottom part, what does it say, Phone locked (green) or Phone unlocked (red), and similarly FRP locked or unlocked?!
Click to expand...
Click to collapse
It says
Code:
PHONE Unlocked
and doesn't say anything about FRP lock/unlock.
Joshywooful1 said:
It says Phone unlocked and doesn't say anything about FRP lock/unlock.
Click to expand...
Click to collapse
Yeah, Phone=Bootloader and I just checked, Chinese AL10 does not even display FRP status on the Fastboot screen
Joshywooful1 said:
... I don't have the right screwdriver to remove the screws from my phone, so I can't do the testpoint method either. Is there anything else I could do?
Click to expand...
Click to collapse
Yes, a shame, it's a pentalobe screwdriver but the same is used for iPhones, hence not really so hard to find
And two other options were given in one of my previous answers:
zgfg said:
...
Otherwise, there are on-line services providing paid unbrick support:
...
https://ministryofsolutions.com/paid-services
Even better, you can ask @Tecalote (author of HWOTA7 method for rebranding and upgrading to Chinese Oreo), look at his profile and find his gmail address (he doesn't look to XDA anymore and probably he will not answer on PM) - he is from Germany and he unbricks Huawei phones on the per-donation model
...
Click to expand...
Click to collapse
Btw, it might be valuable for the others to prevent a similar brick, if you describe what you were doing to get such a serious brick where phone can not boot to Recovery or eRecovery, and that flashing (although Bootloader and supposedly FRP are unlocked) and even DLOAD fail
Joshywooful1 said:
I've just tried to flash that recovery and just got this output:
Code:
Sending 'recovery_ramdisk' (25668 KB) OKAY [ 0.697s]
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Click to expand...
Click to collapse
What were you doing before the brick? Did it suddenly reboot into the "RGB" screen like the other reported case over here, or were you installing some ROM or kernel? Those "RGBricks" seem to be pretty rare but fatal. How old is your phone?
Let's hope you still have enough write cycles in your eMMC judging from that log...because if that happens it means your phone finally kicked the bucket and needs a eMMC or board change. But let's be optimistic. Try wiping /system with fastboot and check if it fails. Try the testpoint method too
Joshywooful1 said:
Heya! I've got the Huawei P9 rebranded on the Chinese EVA-AL10 Oreo firmware.
My phone has recently stopped working and is unable to boot into the system and recovery.
The bootloader is unlocked and it freezes on the Your device has been unlocked and can't be trusted screen that shows 3 boot options in the middle of the screen (Press power key to continue, Vol up 3 seconds for erecovery, Device will boot automatically after 5 if nothing is done on that screen). It also freezes on a similar screen without the three options if I do the Vol up + Power shortcut to enter the erecovery.
If I do the Volume up, Volume down and power boot shortcut, it boots into a screen with a green background along with a red rectangle in the upper half of the screen and a blue rectangle in the lower half. It stays on this screen for about a minute before freezing on the Your device has been unlocked... screen when it attempts to enter the erecovery.
The same screen shows when I do the Volume down and power boot shortcut when it isn't connected to my computer. The difference this time being that every time it reboots after a short period of time, it reboots into the same screen.
It is only able to successfully able to boot in the Fastboot & Rescue Mode.
Click to expand...
Click to collapse
If chinese oreo b540 ROM is installed in your phone and you can boot into bootloader then try extracting recovery_ramdis, kernel, system and Ramdisk from Update.app and flashing it through Fastboot.
I would suggest you to follow this article https://openkirin.net/user_guide/how-to-flash-extracted-partition-images/
and this
https://openkirin.net/user_guide/how-to-extract-partition-images-from-stock-emui-firmware/

Categories

Resources