P20 stuck in Fastboot after Update - Huawei P20 Questions & Answers

Hello, I am new here!
I have a problem with my P20. Yesterday I tried downgrading with HiSuite Proxy from Emui 9.1 to 8.1. The update went well, the emui loading circle with percentage appeared on the phone, then at 80 percent there appeared an error on the screen that the update has failed and I should either enter recovery or reboot. I clicked on reboot (I am dumb, I know) and since then the phone is showing a black screen and I cannot do anything. The phone is in Fastboot and it responds to fastboot commands from adb tools.
I think the problem is, that in Hisuite proxy I selected "normal update" instead of "rollback". That made Hisuite perform an update over a newer version of emui.
In the beginning, the phone was recognised by windows as "Andoid device" with a subname "HI3650". After switching drivers in device-manager, I got "ADB device" there.
What I tried so far:
- switching ADB drivers in device manager in windows
- system recovery in Hisuite. It fails, tried with several HiSuite versions so far.
- "fastboot flashing unlock" (most fastboot commands return errors like "FAILED (remote: check password failed!)" or "FAILED (remote: Command not allowed)"
I am not a pro with these things but understood that I could flash a recovery image with fastboot. Someone on this forum said something about .pac images which could be flashed even with a locked bootloader, mine is locked. Could somebody with good knowledge help me out? I did plenty of google searching before and also browsed through this forum, i did not find a solution, at least not with locked bootloader.
I would appreciate any help to save the phone before having to trash it!

Servus2403 said:
Hello, I am new here!
I have a problem with my P20. Yesterday I tried downgrading with HiSuite Proxy from Emui 9.1 to 8.1. The update went well, the emui loading circle with percentage appeared on the phone, then at 80 percent there appeared an error on the screen that the update has failed and I should either enter recovery or reboot. I clicked on reboot (I am dumb, I know) and since then the phone is showing a black screen and I cannot do anything. The phone is in Fastboot and it responds to fastboot commands from adb tools.
I think the problem is, that in Hisuite proxy I selected "normal update" instead of "rollback". That made Hisuite perform an update over a newer version of emui.
In the beginning, the phone was recognised by windows as "Andoid device" with a subname "HI3650". After switching drivers in device-manager, I got "ADB device" there.
What I tried so far:
- switching ADB drivers in device manager in windows
- system recovery in Hisuite. It fails, tried with several HiSuite versions so far.
- "fastboot flashing unlock" (most fastboot commands return errors like "FAILED (remote: check password failed!)" or "FAILED (remote: Command not allowed)"
I am not a pro with these things but understood that I could flash a recovery image with fastboot. Someone on this forum said something about .pac images which could be flashed even with a locked bootloader, mine is locked. Could somebody with good knowledge help me out? I did plenty of google searching before and also browsed through this forum, i did not find a solution, at least not with locked bootloader.
I would appreciate any help to save the phone before having to trash it!
Click to expand...
Click to collapse
Hello there! I can help you with this since I got exact same problem. Do you have any messaging app? add me on telegram t.me/dexxik or discord Dexxo#0295 if you want quicker response.
First of all, you f*cked up. I can help you recover your phone but you won't be able to use that phone for calling/messaging again.

Related

[Q] One Mini Update Utility fail at 95% (log attached)

Hello to all.
My first post was about One mini with unlocked bootloader and failed system. Situation changed so I describe all "story" wondering that sb clever would tell me what to do now...
At the beginning, I visited some "specialist", who applied me a fantasy about bootloader rebuilding and took cash for nothing. Because thay said that tried to flash European ROM on device bought in USA with ATT brand and S ON (look attach) I had to learn a little to do anything by myself.
First of all I flashed TWRP Recovery using AllinOne. First CMD window replied "device not found" but second one responded that Recovery was flashed succesfully. In fact TWRP run. And it was all.
Than I tried to do anything by ADB. Drivers were installed correctly but any command form adb responded "device not found"
Device manager showed QHSUSB DLOAD when connected not powered one mini. (Yes I know what it means)
Sideload in TWRP was not working too.
Flashing wih USB OTG mounted under TWRP was not working too.
Newest RUU_M4_UL_K44_SENSE60_MR_Cingular_US_4.13.502.3_ from htc site (.htc.com / us / support / htc-one-mini-att / news / ) was showing connection error at the beginngin but was detecting system version and suggested update. Always failed after reboot.
Today I tried to flash RUU.zip (ver same as installed on my bricked one mini). AllinOne asked about Bootloader lock so I relocked bootloader. Flashing failed so I started mentioned newest original RUU from HTC. Bootloader was rebooted and procedure started. (with unlocked bootloader it failed at this moment) Unfortunaelly it stopped at 95% with comunicate "signature error".
Cell restarted, htc logo appeared ("by android" sign was added) and device manager detected HTC device and mass memory. Unfortunetelly system havent boot up and now manager shows only "not recognized device" but QHSUSB DLOAD not appeared again
What would you advice to do now? Try to update again? When you check Fastboot reply at CMD screenshot than it seems to be ALMOST updated. But still sth is wrong
I read RUU log and edited fonts colour to make it more readable.
I can see that all time ADB has a problem with "adb devices" command and it asks fastboot (i coloured it on pink).
Later it flash two almost 400MB each zip files but after second one gives signature fail. If Update comes from HTC and almost all update was correct what may it mean now?
I attach
1 image with bootloader details when bought broken
2 image of ADB fastboot report after 95% Update to 4.13.502
3 log from Updater

LG G2 D800 Brick - Have Fastboot, but No ADP, No Recovery, Download Mode broken,

Been searching on these forums for the last 6 hours, trying a number of different solutions, and I haven't found an answer yet. I am going to go back through step-by-step through the night in my next post unless someone else appears with a solution, first, starting with using fastboot to flash the firmware images again.
I had attempted to install CWM 12 on my LG G2 D80020u today. It didn't work, but when I attempted to recover, I hit a wall.
I found a few solutions for my problem, but they assume Windows PC, and I'm running Ubuntu Linux.
Currently:
If I reboot normally with the device unplugged, I get the LG logo with "security error"
I CAN access fastboot and erase/flash various images, but none have solved my issue yet
I CAN get to Download Mode, but my linux computer cannot see the device to transfer files.
I CANNOT use ADP. I could earlier, but now when I type "adp devices", my terminal displays no devices.
If I run ./ioroot.sh, I get "Waiting on ADB detection" and then a stand-still.
Any ideas? Thanks for all of the help.

Failed to restore fastboot following petrov.0's GUIDE

Hi everyone,
I have received my new Idol 3 4.7 (6039Y, european version) yesterday. I was stupid enough to apply all proposed updates before reading the forums thoroughly, so I got stuck with a 01005 build, with fastboot disabled.
I followed petrov.0’s guide to restore fastboot: http://forum.xda-developers.com/idol-3/development/6039-guide-how-to-return-fastboot-t3201077 or at least I tried.
I chose the files for "6039Y (repartitioned by following the repartitioning guide)" in the hope that it would save me some further work. QFIL seemed happy, but on restart, there was a message complaining about something like "unencryption failed", then saying that it was necessary to wipe the memory and perform factory reset. Then the phone spent some time wiping the data, and reboot took me to the stock recovery with a big nasty red error message.
So I used Alcatel Mobile Upgrade to restore the stock system, which went fine, but I was still stuck with a 01005 build. Then I tried again to follow petrov.0’s instructions, now using the files for "6039Y (8GB stock partition sizes)". According to QFIL's log, all went fine (except it waited forever in the final step, after the phone rebooted).
Once rebooted, the phone works ok, "adb devices" lists the phone, but "fastboot devices" still doesn’t.
Does anyone have the same problem? Any idea on how to solve it?
P.S.: this is my first post so I can't reply to petrov.0’s thread, and I couldn't find a Q&A thread on this subject, so here it is.
Fastboot -i 0x1bbb devices should be the right syntax. You have to directly adresy the devices by add “-i 0x1bbb“. Next zimě try to use search and read a little before posting stupid questions.
?
DallasCZ said:
Fastboot -i 0x1bbb devices should be the right syntax. You have to directly adresy the devices by add “-i 0x1bbb“. Next zimě try to use search and read a little before posting stupid questions.
Click to expand...
Click to collapse
No need to be rude : of course, I also tested the "fastboot -i 0x1bbb devices" with no more success.
(AFAIK, the -i option is just a filter: am I wrong?)
Turns out I was even more stupid than DallasCZ thought: my problem was that I used the fastboot commands in recovery mode rather than fastboot mode!
In case anyone as dumb as I passes by: use "adb reboot-bootloader" before trying any fastboot command.
And I confirm that the phone is NOT listed if I omit the -i option. The man page is really not clear about that: maybe the XDA-University guide about fastboot http://forum.xda-developers.com/showthread.php?t=2277112 could mention this kind of quirk?
Sorry for the noise.
I really have failed to restore fastboot commands using @petrov.0 's guide.
The problem I had having failed at flashing a modified OTA update file...well to cut a long story short I resorted to using Alcatels Mobile Upgrade Q 4.9.2 to fix my phone. I have no windows so was running the program on Linux host using VirtualBox. After loads of trouble with the drivers with 64 bit windows XP finally got everything to work using Windows 7.
I thought it would now be simple to restore fastboot commands using QFIL and to get my awesome 16GB internal memory back but despite phone definitely being in download mode and the phone showing up as Android HS-USB QDLoader 9008 on COM6 and QFIL automatically choosing COM6 etc and following everything in the guide as it should be I got an error when I hit the download button. Something about the phone not being in Firehose mode. I tried again and this time the error was about Sahara.
Anyone have any ideas?! Is it perhaps just not possible through Virtualbox?
Please help me! I want my 16GB internal memory back!
(phone is 6039Y-2AALWE7 and Upgrade Q updated it from 1AB2AZ22 to 1AJEAZE0)
fastboot - no permisions
deleted - found a simple solution.... for fastboot command in linux you need "sudo"!
Thank you
deleted
please a moderator wipe this post
gridmuncher said:
I really have failed to restore fastboot commands using @petrov.0 's guide.
The problem I had having failed at flashing a modified OTA update file...well to cut a long story short I resorted to using Alcatels Mobile Upgrade Q 4.9.2 to fix my phone. I have no windows so was running the program on Linux host using VirtualBox. After loads of trouble with the drivers with 64 bit windows XP finally got everything to work using Windows 7.
I thought it would now be simple to restore fastboot commands using QFIL and to get my awesome 16GB internal memory back but despite phone definitely being in download mode and the phone showing up as Android HS-USB QDLoader 9008 on COM6 and QFIL automatically choosing COM6 etc and following everything in the guide as it should be I got an error when I hit the download button. Something about the phone not being in Firehose mode. I tried again and this time the error was about Sahara.
Anyone have any ideas?! Is it perhaps just not possible through Virtualbox?
Please help me! I want my 16GB internal memory back!
(phone is 6039Y-2AALWE7 and Upgrade Q updated it from 1AB2AZ22 to 1AJEAZE0)
Click to expand...
Click to collapse
Any progress with this ?!? I'm a Linux user too, but I must admit that for this process I had to start my dusty Windows installation. As for the second attempt ... if the first one fails you must restart the phone in download mode again.
petrov.0 said:
Any progress with this ?
Click to expand...
Click to collapse
Sadly no. I don't understand why Upgrade Q would work in Virtualbox but QFIL doesn't. Still get the firehose error:
NOP: Fail Code: 10
Unable to send FireHose NOP, Device is not in Firehose mode!
Download Fail: System.Exception: Failed to send Firehose NOP to the phone
As I said before the phone is definitely in download mode and shows up in device manager correctly. I tried altering the USB filter in Virtualbox to be less device specific and a few other things, plugging unplugging, different usb cable, different usb port on laptop etc but no luck.
I might try a different Windows version but I think I'll probably resort to using a friends computer at some point.
Don't want to dual-boot windows as my laptop HDD is toooooooooo full and it would involve altering a few of my partitions etc.

Need some help on Huawei Maimang 5 (Chinese Version)

Hi there!, i just bought a Huawei Maimang 5(MLA-AL10, Chinese Version) two weeks ago, then i noticed it had android 6.0 so i decided to upgrade it to 7.0..., since the Huawei Updater didn't find any update for my cellphone i downloaded FirmwareFinder App and use it instead, it worked but during the process the phone just rebooted and got bricked.
I tried to "save it" installing a new firmware via MicroSD, using Huawei eRecovery and Adb Tools, and nothing worked. Here my doubts:
1. Via MicroSD: i' m not sure the firmware i put on the card was the correct, i have found a lot of MLA-AL10 Roms and tried them all without any good results, the phone just start installation and at 5% reboot itself. Is there anyone out there who can help me finding the right one?
2. Via Huawei eRecovery: after i connect to a wifi network, my cellphone shows the next message: "There's no info for the package installed" and the only options i have left are: "Shutdown or Reboot", so i discarded this solution.
3. Via Adb Tools: using command "ADB DEVICES" shows empty list, i have no idea what i am doing wrong, my laptop recognize the phone and HiSuite too, but not Adb.
Hope someone can help me out.
Note: the phone has USB debugging disable.
Try recovery http://www.hardreset.info/devices/huawei/huawei-maimang-5/recovery-mode/
I forgot to mention i tried that too, and i cannot wipe data..., after 5% or 6% the EMUI logo dissapear and shows an exclamation mark.
Maybe this post will be help you https://forum.xda-developers.com/mate-8/help/boot-to-fastboot-mode-flashing-restore-t3550116
The solution is DC-Phoenix + 15 credits

Stuck at bootloop after update, can't access ADB.

Hi, I need your help here. I'm trying to fix my friends phone for her. What she told me is that it got stuck at the second boot screen after an update. She also said that it happened before and her father got it working. So my first thought was to clean flash stock firmware but I can't get ADB working. I've installed usb drivers and minimal ADB and fastboot but it doesn't recognize the phone in "adb devices" (I have no idea if USB debugging was on in dev options but I'm assuming it wasn't). I have no idea what to do now as I'm not that familiar with Xiaomi firmware.
Thanks in advance.
Edit: Xiaomiflash sees the device but not as COM.. but 72e728fb (?) and trying to flash it in this state ends with error:Flash xbl error

Categories

Resources