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.
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
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
Hello guys, my nokia 8 ta-1004 stuck at download mode due to me bricking it, I wanted to solve an issue with the Sim Card and wifi that makes my nokia's wifi switcher won't turn on, so I decided to downgrade the system via OST v6.0.4 to android 7 but unfortunately it won't work as I run in some problem with downloading and when I tried to just flash my nokia 8 to the same Oreo rom with OST v6.1.2, it failed and it got stuck at download mode, I tried all online methods I have found but with no success, I may need to flash the phone with the latest rom, I hope someone can help thank you all.
You can try to reboot it by pressing and holding power+volume up or thru "fastboot reboot"
Since this Huawei P10 never received a single OTA update (from Carphone Warehouse, SIM free) and was stuck on Nougat I decided to go custom ROM route. This was a HUGE mistake but I did learn a lot which may be helpful to others.
The situation goes like this:
Tried to flash TWRP, failed, tried to flash system (openkirin pie) also failed. Nothing would work at all.
Tried to re-lock bootloader thinking it would make everything stock again automagically (not sure why I thought it does on some devices).
Then got into bootloop with no access to fastboot as bootloader HAD to force factory reset but couldn't (broken recovery). After some time you'd get some white EMUI screen in Chinese where all the options are broken.
Flashed the latest version I could find using DC-Phoenix with flashpoint, this is where I really ****ed up as this firmware had XLOADER2.
Phone is alive!!!! but no IMEI and NCK lock. HCU tool, DC unlocker, etc, nothing works with XLOADER2 for fixing the IMEI or NCK lock.
Tried to downgrade to Nougat. Complete brick, back into testpoint mode.....
Testpoint mode cannot even flash XLOADER1 anymore!! I did still manage to get the phone working again, but now it is a tablet .
So in short:
YOU STILL CANNOT GO BACK TO XLOADER1 FROM XLOADER2 - EVEN if you disassemble and use testpoint mode! I have NO idea what Huawei have done to prevent this but its something evil. So if you are at this point with no IMEI then you will never have a working phone ever again. Tablet yes if you are lucky but NOT phone.
So the process (not detailed, requires Google) to make your bricked XLOADER2 Huawei P10 a tablet rather than a brick:
You'll need DC-phoenix and maybe a 3-day 15 credit license but don't by the license until it tells you to otherwise it might be a waste of money if you have problems with disassembly for example
Download HiSuite to make sure you have all the required drivers
Disassemble your phone, plug USB into the computer, ground the testpoint pin and hold the power button
You should see a HUAWEI USB COM device in device manager
Using DC phoenix you need to select a booloader mode, try all Kirin 960 bootloaders until one works. You can also select an OEMINFO update at this point too if you want
Your phone is now in some half working fastboot mode. Leave it plugged in!
Using firmware finder, find the "379" firmware (the latest one they have for VTR-Lx9) where x is 0 or 2.
Using firmware extrator, extract: xloader, fastboot, teeos, ptable (hisi_gpt or something like that), vbmeta, kernel (ramdisk)
Using fastboot manually flash all of these images, kernel may fail but its OK if it does
Now fastboot reboot, your phone will brick again. Put it back into testpoint mode
Using DC-phoenix to select a bootloader (again) use the same Kirin 960 one as what worked for you before
Use DC phoenix to flash the "379" firmware and customisation and run the update.
If ANY steps fail, repeat again to fastboot reboot, testpoint mode, bootloader from DC phoenix, then run the update.
If all partitions flash OK and it asks you to go into update mode, with the USB connected, hold vol-, vol+ and power until 3 seconds AFTER you feel the phone vibrate
Eventually you should see some more COM ports appear in device manager (PCUI and some other random one). If you can see your screen (doubtful as it will be face down) you will see update mode 5%
Again, update with DC-phoenix (same 379 firmware and customisation you did before)
Your brick should now be a tablet. Bootloader should be unlocked if it was unlocked at the start of the process.
So typing that out and given I don't have time or the load of files I had downloaded to do this there is not much detail so if you do this you need to be someone who knows what they are doing really. I don't expect anyone to actually be stupid enough to follow this.
I just don't understand what XLOADER2 did (must be at a very low hardware/bios level) so completely lock the device down even in testpoint mode. I'd imagine even their repair centres would not be possible to repair IMEI now and just throw motherboard into the bin.
https://forum.xda-developers.com/p10/how-to/unbrick-p10-vtr-l09-vtr-l29-unbrick-t3916694
Anyone in this boat and has lost IMEI this thread is a must read!