soft bricked EVA-L09? - Huawei P9 Questions & Answers

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

Related

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.

[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.

Softbrick P9 Plus

Hello folks,
so a friend of mine is a complete noob and have this problem with his p9 plus.
The phone keeps rebooting itself in an endless loop, i can't access recovery and only when plugged in to the PC i can access fast-boot.
Phone is locked, FRP Lock.
With getvar command i managed to get this info:
rescue_phoneinfo: VIE-L09C113B170
seems that there is no full zip of this rom anywhere just partial ota (found those with firmware finder) but even with that when i try to flash recovery i get command not allowed.
On the fastboot screen of the phone i have this reboot reason AP_S_PANIC
anyone knows a how to get the phone out of this? (i was thinking that maybe unlocking the bootloader could be of any use, but in the request page it's needed the Product_ID and i don't have it. (can't *#*#1357946#*#*)
I don't know if it does work in a locked bootloader.
I have my P9+ for a week and maybe if you download a firmware compatible with your version and try to 'hard' update the phone, using a SD card with a update file on a dload folder and restarting the phone pressing VolUp + VolDown +Pwr, you can restore your friend's phone.
I'm sorry if I didn't help, I am myself stucked trying to rollback my version to MM and have the NFC and the Bluetooth working again...
myself also got this problem..please anyone..

Bricked phone! Stuck in fastboot only, bootloader is locked! Need help, please!

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

P9 completely dead, no usb, fastboot, system

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

Categories

Resources