Database Develop

Softbrick achieved, need help

P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?

I tried everything in this thread:
http://forum.xda-developers.com/p8lite/general/hand-fixing-bootloop-t3464740
to no avail. One thing I noticed is that the link given in the Fastboot menu links to a Chinese (?) website - http://zh.ui.vmall.com/emotiondownload.php?mod=restore - I'm not sure if this is indicative of me having a device for the East Asian markets and if there are any software differences?

Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).

GfIsGonnaKillMe said:
Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).
Click to expand...
Click to collapse
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?

XePeleato said:
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?
Click to expand...
Click to collapse
Just the very static image, it doesn't even go into the animation.
Edit: this is a newly bought P8 Lite, the Box says Android 5.0, don't know if relevant?
by now I've wiped stuff with TWRP more times than I can count, and tried manually flashing the boot, recovery, cust and system of b132, b170, b190, and b564 to no avail

GfIsGonnaKillMe said:
Just the very static image, it doesn't even go into the animation.
Click to expand...
Click to collapse
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.

XePeleato said:
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.
Click to expand...
Click to collapse
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery

GfIsGonnaKillMe said:
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery
Click to expand...
Click to collapse
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.

XePeleato said:
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.
Click to expand...
Click to collapse
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.

GfIsGonnaKillMe said:
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.
Click to expand...
Click to collapse
[ 8.389146s][pid:1,cpu1,init]BUG: failure at /cloud/jenkinswh/ci/workspace/Alice_Channel_ANDROID/android_code/kernel/drivers/video/hisi/hi6220/balong_compose.c:613/vpu_on_notice_ade()!
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.

XePeleato said:
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.
Click to expand...
Click to collapse
It is very nice of you to look into this! Worst case scenario, the device was broken from the start and has now lost its warranty (though I booted it up once without problems right in the beginning).
For the main problem - which is my gf - I simply factory reset my own P8 Lite and put the stickers from the new one on it. Now I don't have a phone, but at least I get to keep my relationship
ninja edit: checking my terminal history, I remember trying to fix the not-installing SuperSU by trying fastboot -w and fastboot format cache as recommended elsewhere, but both failed
Playing around with it again, it seems the only fastboot commands working are fastboot flash and fastboot reboot, everything else is giving a "FAILED (remote: Command not allowed)" error, even for things like getvar
flashing b564 allows me to get into stock recovery, will try dload update now!!
EDIT: IT WORKS!!!
Things I learned from this:
- it is important to flash right update version
- use dload if you can boot into stock recovery
- recovery will only be loaded if not connected via USB, otherwise EMUI crap will launch
- vendors do not always have correct information on device package!!

GfIsGonnaKillMe said:
P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?
Click to expand...
Click to collapse
delete

For unbrick, its easy if your bootloader is unlocked.
Just need time and flash few files by adb (downgrade)and update your device's to the android version you want.
If you want I have all the necessary files.
After your device's is like at his first boot.
Sent from my SM-N9005 powered by QS-N9005-LP

Can't get into TWRP on OEM unlocked and previously rooted device. (6.0)

Hi everybody,
I'm struggling with this P9 plus of a friend of mine.
He gave me the phone already OEM unlocked, rooted and with a working TWRP Installed.
I downloaded and updated to lastest stock-firmware (Android M 6.0) and lost (as expected) root and TWRP.
Now I'm trying to install back TWRP on the device, but without success. Flashing the recovery through fastboot works itself, but when I reboot (into recovery with power+vol up)
I always crash into the Huawei eRecoveri, with the Emui Logo.
I've repeated the process I don't know how many times, but I can't fix it. I've been googling around for answers, but without luck. Furthermore, I've read that the only "safe way" to get into TWRP is to use apps that need root, but I need TWRP to get root back.
Please help, 'cause I don't know what to do...

Same here, stuck with nougat, no erecovery (Getting package info failed).
Can't start in bootloader using v- power. Google is not my friend anymore etc....
Bootloader unlocked.
Edit: solved. Using srk tool to unlock bootloader using power +vol — at same time. The tool forced to enter bootloader. I saw that Windows 10 detect the phone even in stuck mode and srk tool could pass command lines when phone rebooted . Now i debrand and can flash another twrp to downgrade.

Issue with P9 after rooting - possible brick?

Hey guys,
This is a bit of a long one so please bear with me...
I have an EU EVA-L09 which was running EVA-L09C432B166 unrooted and with a locked bootloader. I decided to unlock it which I did successfully (Fastboot was showing both Phone & FRP as unlocked) and flashed TWRP on to it as well as BETA-SuperSU-v2.65.
After a few days with my stock email app not working and Battery Settings unaccessable since rooting (not to mention the warning message every time I booted my phone) I decided it wasn't worth it and wanted to remove it all and go back to stock. I was struggling to find a stock rom due to being impatient and just removed root via SuperSU app on my phone.
I found a stock recovery image which I tried to flash on to the phone using the BAT file (PASO 3 VOLVER A RECOVERY STOCK) which didn't seem to work. I also tried to do it via cmd line and was faced with "FAILED (remote: Command not allowed)." I also noticed that FRP was showing as locked now in fastboot. I did unlock it using DC Unlocker but it's still displaying as locked (after some research on the forum this seems normal.)
I tried to update to Nougat 7.0 by Wiping in TWRP and then installing Update.zip from another thread on this forum. This worked great but stupidly I forgot to install the EU pack zip which accompanied it before rebooting. Unfortunately this has now installed a limited version of Nougat on to the phone whilst simultaneously removing TWRP so I can't install the other zip.
I have tried to install the other zip and some old firmware using dload method but I always get stuck on 5%. I have also tried flashing TWRP again but I am facing the same , ""FAILED (remote: Command not allowed)" error. The error is also displayed when I try to re-lock the bootloader. The bootloader is definitely unlocked as I have checked with cmd line & the warning message is still being displayed on booting up. I have USB debugging enabled but am unable to enable OEM Unlock due to the option being greyed out (seems to be the case when FRP is unlocked.)
I can't do any updates using 3 button technique they all get stuck on 5%. I can't submit any flash commands in cmd.exe without getting the "command not allowed error."
There is a bit of hope because I can boot in to Nougat but it's very limited with no apps and no keyboard.
Can anybody help?

DCStreamer said:
Hey guys,
This is a bit of a long one so please bear with me...
I have an EU EVA-L09 which was running EVA-L09C432B166 unrooted and with a locked bootloader. I decided to unlock it which I did successfully (Fastboot was showing both Phone & FRP as unlocked) and flashed TWRP on to it as well as BETA-SuperSU-v2.65.
After a few days with my stock email app not working and Battery Settings unaccessable since rooting (not to mention the warning message every time I booted my phone) I decided it wasn't worth it and wanted to remove it all and go back to stock. I was struggling to find a stock rom due to being impatient and just removed root via SuperSU app on my phone.
I found a stock recovery image which I tried to flash on to the phone using the BAT file (PASO 3 VOLVER A RECOVERY STOCK) which didn't seem to work. I also tried to do it via cmd line and was faced with "FAILED (remote: Command not allowed)." I also noticed that FRP was showing as locked now in fastboot. I did unlock it using DC Unlocker but it's still displaying as locked (after some research on the forum this seems normal.)
I tried to update to Nougat 7.0 by Wiping in TWRP and then installing Update.zip from another thread on this forum. This worked great but stupidly I forgot to install the EU pack zip which accompanied it before rebooting. Unfortunately this has now installed a limited version of Nougat on to the phone whilst simultaneously removing TWRP so I can't install the other zip.
I have tried to install the other zip and some old firmware using dload method but I always get stuck on 5%. I have also tried flashing TWRP again but I am facing the same , ""FAILED (remote: Command not allowed)" error. The error is also displayed when I try to re-lock the bootloader. The bootloader is definitely unlocked as I have checked with cmd line & the warning message is still being displayed on booting up. I have USB debugging enabled but am unable to enable OEM Unlock due to the option being greyed out (seems to be the case when FRP is unlocked.)
I can't do any updates using 3 button technique they all get stuck on 5%. I can't submit any flash commands in cmd.exe without getting the "command not allowed error."
There is a bit of hope because I can boot in to Nougat but it's very limited with no apps and no keyboard.
Can anybody help?
Click to expand...
Click to collapse
Yes... Downgrade to MM with the rollback
Then flash full B136 and update
Enviado desde mi EVA-L09 mediante Tapatalk

jcalderonv74 said:
Yes... Downgrade to MM with the rollback
Then flash full B136 and update
Enviado desde mi EVA-L09 mediante Tapatalk
Click to expand...
Click to collapse
Hey @jcalderonv74 thank you for the response. I have just re-tried to do that on your suggestion and with the intermediate UPDATE.app in the dload folder on my external SD I get to the stage of the 3 button start up as per the instructions and Installing Update gets stuck on 5%.
I have noticed I do have access to stock recovery using "adb reboot recovery" command.
Any more ideas?

DCStreamer said:
Hey @jcalderonv74 thank you for the response. I have just re-tried to do that on your suggestion and with the intermediate UPDATE.app in the dload folder on my external SD I get to the stage of the 3 button start up as per the instructions and Installing Update gets stuck on 5%.
I have noticed I do have access to stock recovery using "adb reboot recovery" command.
Any more ideas?
Click to expand...
Click to collapse
Your really used the rollback package?
http://consumer.huawei.com/ch/support/products/downloads/detail/p9-chde.htm?id=92743

Have you full battery?
Wysłane z mojego EVA-L09 przy użyciu Tapatalka

xtcislove said:
Your really used the rollback package?
Click to expand...
Click to collapse
Hi, yeah I did use the rollback package @xtcislove and it would just get stuck on 5% using the dload method, and trying to flash it in command line would result in "Command not allowed".
darrr1 said:
Have you full battery?
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
@darrr1 yes the battery was full but still it wouldn't work

Ok just for completion and anybody who is having the same issues as I have had with the same or similar model of P9, this is how I solved it (after a day without sleep and a couple of migraines). Please note this is only to be used if you have exhausted all other, free options on this forum as this is slightly risky and costs money. It's a last resort.
What you'll need:
- HiSuite installed but closed on your PC
- USB cable to connect phone to PC
- DC-Phoenix with an account with 15 credits (15 Euro)
- The DC-Phoenix guide opened at "Method 2"
- Firmware .img file from their database by clicking "Enter Support Area" button in DC-Phoenix (EVA-AL10_M00A056_Factory_firmware_Global_Nonspecific_Android_6.0_EMUI_4.1.dgtks)
- Stock firmware as an .app file on an SDCard in a folder named "dload" (I used EVA-L09C432B182 (UPDATE.APP))
Method:
1. Copy the official stock firmware .app file to your SDCard inside a folder named "dload".
2. Remove SDCard & Sim Card from the phone.
3. Put your phone in to Fastboot (Turn off phone, hold volume(down), insert usb cable).
4. Load DC-Phoenix and select Fastboot mode.
5. Click "IMG Files" tab and locate the .dgtks file using the "Config or recovery file:" field.
6. DO NOT uncheck the boxes next to "Not erase NV" and "Not erase oeminfo" as this will delete your IMEI and other information completely.
7. Click UPDATE and wait for it to fully finish (you may see an error regarding FBlocks but it should still go on to complete).
8. Once you see it is completed, disconnect phone from PC and restart the phone by holding the power button.
9. This should load you in to a very basic firmware (it may take one or two reboots to achieve this).
10. Insert your SDCard with the newer, official, stock firmware that you want on the phone in to the SDCard slot WITHOUT SimCard.
11. On your phone home you should see an icon named "Upgrade" or "Upgrade/Update Phone" on the first page. (I've forgotten the exact name of the icon but it will be obvious to you).
12. Click that icon and it should go ahead and install the firmware .app on to the phone off your SDCard.
After following the on screen instructions you should now be back to stock firmware. I recommend re-locking your bootloader now using fastboot and your unlock key if you are trying to do so. If you go on to update to Nougat 7.0 before locking your bootloader back up you won't be able to do so without downgrading back to the same firmware that was on your phone when you originally unlocked it.)
Hope this helps somebody who is stuck and exhausted every other avenue with nothing left to lose.
Danny

I had a similar issue after doing this :- unlock bootloader...root MM....Upgrade to Nougat...root...Rollback to MM...root...Upgrade to Nougat.. borked!!!
I was left with a phone that only booted to bootloader and no recovery or possibility of flashing with dload worked.
Luckily DC Phoenix got it into a usable state where i could enter erecovery and flash Nougat again. Seems the backdoor method they use to load the OS, at least at a low level, is very effective!
There's probably a lesson here, but I've never had a phone so easily bricked....
Thanks :good:
Peace
---------- Post added at 07:57 AM ---------- Previous post was at 07:53 AM ----------
DCStreamer said:
Please note this is only to be used if you have exhausted all other, free options on this forum as this is slightly risky and costs money. It's a last resort.
Click to expand...
Click to collapse
:good::good:

DCStreamer said:
Ok just for completion and anybody who is having the same issues as I have had with the same or similar model of P9, this is how I solved it (after a day without sleep and a couple of migraines). Please note this is only to be used if you have exhausted all other, free options on this forum as this is slightly risky and costs money. It's a last resort.
What you'll need:
- HiSuite installed but closed on your PC
- USB cable to connect phone to PC
- DC-Phoenix with an account with 15 credits (15 Euro)
- The DC-Phoenix guide opened at "Method 2"
- Firmware .img file from their database by clicking "Enter Support Area" button in DC-Phoenix (EVA-AL10_M00A056_Factory_firmware_Global_Nonspecific_Android_6.0_EMUI_4.1.dgtks)
- Stock firmware as an .app file on an SDCard in a folder named "dload" (I used EVA-L09C432B182 (UPDATE.APP))
Method:
1. Copy the official stock firmware .app file to your SDCard inside a folder named "dload".
2. Remove SDCard & Sim Card from the phone.
3. Put your phone in to Fastboot (Turn off phone, hold volume(down), insert usb cable).
4. Load DC-Phoenix and select Fastboot mode.
5. Click "IMG Files" tab and locate the .dgtks file using the "Config or recovery file:" field.
6. DO NOT uncheck the boxes next to "Not erase NV" and "Not erase oeminfo" as this will delete your IMEI and other information completely.
7. Click UPDATE and wait for it to fully finish (you may see an error regarding FBlocks but it should still go on to complete).
8. Once you see it is completed, disconnect phone from PC and restart the phone by holding the power button.
9. This should load you in to a very basic firmware (it may take one or two reboots to achieve this).
10. Insert your SDCard with the newer, official, stock firmware that you want on the phone in to the SDCard slot WITHOUT SimCard.
11. On your phone home you should see an icon named "Upgrade" or "Upgrade/Update Phone" on the first page. (I've forgotten the exact name of the icon but it will be obvious to you).
12. Click that icon and it should go ahead and install the firmware .app on to the phone off your SDCard.
After following the on screen instructions you should now be back to stock firmware. I recommend re-locking your bootloader now using fastboot and your unlock key if you are trying to do so. If you go on to update to Nougat 7.0 before locking your bootloader back up you won't be able to do so without downgrading back to the same firmware that was on your phone when you originally unlocked it.)
Hope this helps somebody who is stuck and exhausted every other avenue with nothing left to lose.
Danny
Click to expand...
Click to collapse
Vou are the best, yeppie !! You save my live..because I have not damaged myself and tyrannized my family as it would have been possible, if you had not helped :good: Huawei P9 Plus Dual-Sim

Thank you so much!!
I can't believe how much I have scoured through the interwebs untill i came to your post.
I even went through all other DC-Unlocker options including the HCU client, which I burned another 19e on. -_-
I know you posted this over 3 years ago. But thank you for doing it! <3
Huawei p9

DCStreamer said:
Ok just for completion and anybody who is having the same issues as I have had with the same or similar model of P9, this is how I solved it (after a day without sleep and a couple of migraines). Please note this is only to be used if you have exhausted all other, free options on this forum as this is slightly risky and costs money. It's a last resort.
What you'll need:
- HiSuite installed but closed on your PC
- USB cable to connect phone to PC
- DC-Phoenix with an account with 15 credits (15 Euro)
- The DC-Phoenix guide opened at "Method 2"
- Firmware .img file from their database by clicking "Enter Support Area" button in DC-Phoenix (EVA-AL10_M00A056_Factory_firmware_Global_Nonspecific_Android_6.0_EMUI_4.1.dgtks)
- Stock firmware as an .app file on an SDCard in a folder named "dload" (I used EVA-L09C432B182 (UPDATE.APP))
Method:
1. Copy the official stock firmware .app file to your SDCard inside a folder named "dload".
2. Remove SDCard & Sim Card from the phone.
3. Put your phone in to Fastboot (Turn off phone, hold volume(down), insert usb cable).
4. Load DC-Phoenix and select Fastboot mode.
5. Click "IMG Files" tab and locate the .dgtks file using the "Config or recovery file:" field.
6. DO NOT uncheck the boxes next to "Not erase NV" and "Not erase oeminfo" as this will delete your IMEI and other information completely.
7. Click UPDATE and wait for it to fully finish (you may see an error regarding FBlocks but it should still go on to complete).
8. Once you see it is completed, disconnect phone from PC and restart the phone by holding the power button.
9. This should load you in to a very basic firmware (it may take one or two reboots to achieve this).
10. Insert your SDCard with the newer, official, stock firmware that you want on the phone in to the SDCard slot WITHOUT SimCard.
11. On your phone home you should see an icon named "Upgrade" or "Upgrade/Update Phone" on the first page. (I've forgotten the exact name of the icon but it will be obvious to you).
12. Click that icon and it should go ahead and install the firmware .app on to the phone off your SDCard.
After following the on screen instructions you should now be back to stock firmware. I recommend re-locking your bootloader now using fastboot and your unlock key if you are trying to do so. If you go on to update to Nougat 7.0 before locking your bootloader back up you won't be able to do so without downgrading back to the same firmware that was on your phone when you originally unlocked it.)
Hope this helps somebody who is stuck and exhausted every other avenue with nothing left to lose.
Danny
Click to expand...
Click to collapse
Dear DCStreamer,
I tried to follow your procedures with my Huawei tablet but don't work: where I wrong?

soft bricked EVA-L09?

Help Please.......
So I've owned sammy devices before in the past and never been afraid to flash custom kernels/roms etc on them. Since the p9 was the first Huawei device I've owned i was a little scared to flash it. But it got too much for me and i tried, and fail Now i have a P9 that doesn't work and a very upset wife because I've killed my phone.
So what i did was tried to flash via dload 3 button method a nougat fw (official)but had no camera/file manager/calendar etc. Found it was possible to downgrade via flashing a downgrade fw. I cant remember what nougat fw i tried to flash but in the about device the build number was nrd10testkeys or something like that. My official fw before was EVA-L09C706B145. After flashing the downgrade fw my phone rebooted and just hung at the Huawei boot splash screen. All i can do now is access fastboot by holding vol - while plugging in usb. I cant access recovery/cant boot past Huawei splash screen. I have tried fastboot flashing via adb but it fails due to permission error (thinking because of locked bootloader?) Have tried using Huawei updater with hisuite to recover device, download, unpacks and installs recovery to 99%then fails. Pleaee help me fix my phone so i can get back into the goodbooks with the wife.......
Tia all

Try following post #4 instructions from here: https://forum.xda-developers.com/p9/help/failed-downgrade-nougat-to-mm-bricked-t3464156

[Solved]Bricked. Can't recover stock ROM after installing TWRP 3.1.0-3. Nothing works

I have successfully unlocked the bootloader and managed to install TWRP 3.1.0-3 but that's about it. I cannot install any other TWRP version but the one I mentioned. I tried installing Magic Rainbow custom ROM but it doesn't work properly (apps are super slow, entering developer settings makes the settings app crash, can't set a password etc.). So with that I can at least access the phone interface with limited options. Developer settings crashes when I choose it; if I can get through then I can't enable USB debugging, it keeps turning itself off right as I enable it. I can't use update function so I have to use 3 button installation, which randomly fails to work very often. Due to this I haven't been able to install any updates.
I kinda gave up on rooting already, I just want to get my old firmware back at this point but I can't even do that. SRKTools stock marshmallow recovery doesn't work either. It's as if TWRP 3.1.0 has taken over everything. On the rare occasions that I managed to get EMUI update via 3 button installation it would say that the update doesn't match the current version (or something like that). I tried using recover for b378 and managed to run the 3 button update but it always gets stuck at 5%. It gives up after a while, tries booting twice and then goes into eRecovery screen. My bootloader PHONE unlocked text is in red if it matters.
I've been actively trying to fix this for the last 11 hours (yes I'm not exaggerating at all). Please, PLEASE someone help me out with this!

I've also tried using the unbrick tool of the latest SRK Tool 2.0 for b378. It goes flawless, phone restarts and does a factory wipe but then doesn't boot after the Huawei screen. It tries booting twice and then it goes into eRecovery screen. Have I ruined some hardware here?

It seems like 3 button upgrade is my salvation and it doesn't work. Many times I hold it down, I get a slightly different screen but it again hangs at booting text. I managed to flash all recovery, boot and system image files and got the installing update screen in my b378 update, but it hangs at 5%. I couldn't even manage to get the installing update screen for common b136. Also when I try to flash system.img I get an error with flashing system which is FAILED (remote:sparse flash write failure).

First at all: The Magic Rainbow custom ROM is based on B383 so it wont work on B378 firmware thats your fault here.
Just flash the rollback package (find it in my signature) and after this flash B383 or if it not work start with B136. U have to do all with the dload method.
Fast solution?
https://forum.xda-developers.com/p9/development/p9-moonlight-rom-v1-0-b378-stock-t3567223
flash the B378 version. probably your problem is solved by this.

I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.

Lauran_N said:
I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.
Click to expand...
Click to collapse
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0

xtcislove said:
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0
Click to expand...
Click to collapse
I cannot flash rollback using 3 buttons method. I see the "your device is booting now" text and then it goes to TWRP menu. Nothing happens. This is what I mean with 3 button method not working. Every single update fails probably because of this. Is there anything else I can do to flash it?
I've also tried flashing b378 and then doing the rollback. Still doesn't work: It hangs at 5% as it did with the b378 update.
Also, is there a special way of flashing those 2 files of b383? Is it just one after another? I doubt I can flash them at the same time since they have the same name.

YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.

Glad it worked for you.
Next time just read the threads in this forum.
There are several toturials how to flash the p9 the right way.

Lauran_N said:
YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.
Click to expand...
Click to collapse
Can you explain in detail how your fact? That would be nice

Genysix said:
Can you explain in detail how your fact? That would be nice
Click to expand...
Click to collapse
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen

xtcislove said:
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen
Click to expand...
Click to collapse
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.

Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You

Genysix said:
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.
Click to expand...
Click to collapse
Ok first of all, using TWRP back up everything you have there (backing up SD card isn't really needed unless you plan to wipe it too). Then, using TWRP again just wipe everything but OEM and SD card (external storage). Then, create a folder called "dload" in the main SD card directory and put ONLY the update.app in it (use the stock b136 as suggested). Now you need to flash a stock recovery using bootloader again. Just use the Huawei Update Extractor and get both recovery.img and boot.img from the rom that you're using to flash (in this case b136). Put them in the same folder as adb. Run adb cmd, write commands "fastboot flash recovery recovery.img" and then "fastboot flash boot boot.img" and finally "fastboot reboot". Quickly unplug your usb cable and use the 3 button force update (Vol Up+Vol Down+Power button all held together and don't let go until you see the update start). It should work without a problem if you had managed to wipe everything using TWRP. If it still doesn't work you could try deleting OEM info as well and flashing a new one (c432) which you can find on the forums. Back up is important in case it still doesn't work, you might need them to undo things.
If it boots, it means you've learned how to do it and you can probably unbrick it as much as you want haha. You can update to Nougat (7.0) and EMUI 5 using Huawei Updater 2.0 along with HiSuite, there is a guide here on the forums to do so by updating to b182 then to b360/b361>b378>b383 which I was unable to find for now. After that you can install a custom rom without an issue. I figured I wouldn't mess with it anymore but frankly it's likely that you are just soft bricking by skipping something very simple and failing because of that unless you went ahead and did things that you are explicitly told not to do so. If you end up having it unlocked/relocked might as well try and get a custom rom really.
If the update gets stuck at 5% or you have the icon of a usb cable end with a lightning on it your mistake is that you didn't unplug it. If the update keeps failing without these it's likely that you're using the wrong firmware and you could try using another one (FULL+PV+MV ones if you're going for a higher one). Or you could try to follow the rollback and then the update as I did. if you do the rollback then the update, your phone might get a LOCKED status again (yes not relocked).
If you are missing something or you think you have a stupid question and too shy to ask it here just PM me.

Phil_UK said:
Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You
Click to expand...
Click to collapse
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.

Lauran_N said:
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.
Click to expand...
Click to collapse
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks

Phil_UK said:
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks
Click to expand...
Click to collapse
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.

Lauran_N said:
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.
Click to expand...
Click to collapse
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.

Phil_UK said:
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.
Click to expand...
Click to collapse
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.

Lauran_N said:
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.
Click to expand...
Click to collapse
Many Thanks
I managed to flash B360_update.zip via recovery instead. I also have a B360_update_data_full_hw_eu.zip but not sure what that is for.