Nexus 4 Problem: Wont boot into system or recovery, but fastboot and able to flash?!! - Nexus 4 Q&A, Help & Troubleshooting

Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?

zroice said:
Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?
Click to expand...
Click to collapse
u flashed stock doing fastboot -w update?

C4SCA said:
u flashed stock doing fastboot -w update?
Click to expand...
Click to collapse
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?

zroice said:
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?
Click to expand...
Click to collapse
He is asking if you wiped the device after flashing. You flashed the image using the flash-all.bat, which wipes the device. And you even erased the cache. So from the flashing point of view, it seems you did everything right. Do you have the wall charger to load the battery (for some hours)? I would try this. Besides, here is another thread, which seems to be related: http://forum.xda-developers.com/nexus-4/help/qhsusbdload-problem-t2253874
cheers

Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.

now its gettin recognized only as "unknown device" not even QHSUSB_DLOAD anymore.. weird

zroice said:
Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.
Click to expand...
Click to collapse
dont do fastboot erase cache. Do fastboot format cache.
reinstall the correct google usb drivers manually (http://forum.xda-developers.com/nexus-s/general/tutorial-n00bs-install-drivers-windows-t1901617)
try to flash 4.2.2 and see if it boots up using the flash all bat.
that QHSUSB_DLOAD mode i think its teh qualcomm recovery mode or something like that, there is a thread on xda about it.

Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?

zroice said:
Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?
Click to expand...
Click to collapse
no luck with 4.2.2 either - same behaviour.. flash is alright but then it wont boot or go into recovery.. argh

I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ

halloga said:
I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ
Click to expand...
Click to collapse
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)

zroice said:
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)
Click to expand...
Click to collapse
I know this situation man, I spent many hours too and finally solution came out that simple Hope you solve it soon

well i tried that - but i only get a "red" light when holding volume down and power while on wall charger.
This resets the QHSUSB_DLOAD mode, but still wont make the phone boot for me. Tried that combo several times - only "red" light no orange or smth.
When i do that combo when the phone is plugged in to the pc and its in qhsusb_dload mode the red light will flash instead of beeing on all the time.
So I think ill give up unless someone can point me to a good QPST guide to rewrite bootloader for the nexus 4...
Must be bootloader or hardware issue im quite sure..

Related

[Q]Bricked ?

This is what happens :
1. When I normally turn my N7 on , it goes throught the google logo and gets stuck on the ROM logo .
2. I can get into the bootloader when the USB is plugged off , but i cant get into recovery it just gets stuck on the google logo .
3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected . (if i get into the bootloader when the USB is allready connected it gets in the bootloader main screen but i cant move) .
So i cant flash , get into the rom or return to stock .
ANY IDEAS ?? please help me :crying::crying:
Bump
Definitely not bricked since of powers on. Fastboot flash the stock image and you should be good as new.
Sent from my Nexus 7 using Tapatalk 2
Strange, it shouldn't make a difference whether your USB is plugged or not when trying to get to the recovery.
If you get into the fast boot menu or "boot loader main screen" and you press the volume down button a few times you get no response? Sometimes it takes a few seconds for mine to switch to recovery,etc.
Also, what caused your tablet to get stuck in that state?
brGabriel said:
Strange, it shouldn't make a difference whether your USB is plugged or not when trying to get to the recovery.
If you get into the fast boot menu or "boot loader main screen" and you press the volume down button a few times you get no response? Sometimes it takes a few seconds for mine to switch to recovery,etc.
Also, what caused your tablet to get stuck in that state?
Click to expand...
Click to collapse
If I press the volum dowm bottom while on fast boot menu I can move around the menu if the usb is plugged off , but I can only shutdown or restart the fastboot since the start and recovery options just gets stuck on the google/rom logo if it is plugged in I just gets stuck in the menu and I cant even scroll . yea I waited about half an hour on the google logo trying to get to my recovery and nothing happened .
I JUST DONT KNOW WHAT I DID ! I really dont ! I am an experienced flahser and had been so for almost 2 years now ! I just left my N7 on the table and didnt touch it at all for a week and when I tried to turn it on after that I just got that prob . but I did nothing related to flashing or so - it just happened by staying at the table !
any help ?? PLEASE
I CANT RETURN TO STOCK , if i plugg in the usb fastboot gets stuck .
have you tried charging it on the wall charger to make sure the battery has got a full charge, don't know, just throwing out options
Hmmm, well at least you're able to boot the tablet and get to fastboot menu so its not a hard brick. Sounds like a corrupted partition of sorts if you can't get into ROM or recovery. Someone with more expertise might have a possible solution. I wouldn't lose hope yet.
yes , i did charged it to full batt .
i can get into fastboot but not rom or recovery and when i plugg in usb i have no fastboot , doesnt that mean i wont ever be able to flash ?
if i will make a vid of the prob it will help ?
Get to boot loader and do
fastboot flash recovery C:\File path to recovery on computer
Once you have a recovery installed you can push a ROM to your Nexus via adb.
Sent from my Nexus 7
Or you can always use wugfreshs toolkit and click flash back to stock option and check device won't boot, the same thing happened to me awhile ago and the bootloader problem is cause you have the old bootloader the knew 4.13 bootloader fixed that
Sent from my Nexus 7 using Tapatalk HD
i've had good luck with mskip's toolkit in a similar situation
veeman said:
Get to boot loader and do
fastboot flash recovery C:\File path to recovery on computer
Once you have a recovery installed you can push a ROM to your Nexus via adb.
Sent from my Nexus 7
Click to expand...
Click to collapse
xfrancis14 said:
Or you can always use wugfreshs toolkit and click flash back to stock option and check device won't boot, the same thing happened to me awhile ago and the bootloader problem is cause you have the old bootloader the knew 4.13 bootloader fixed that
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Guys , I told you that my bootloader gets stuck when I connect the usb - so how can I possibly flash anything ? please read the whole post
rkiller51 said:
Guys , I told you that my bootloader gets stuck when I connect the usb - so how can I possibly flash anything ? please read the whole post
Click to expand...
Click to collapse
It says you can get to the boot loader with the cable unplugged. So get to the boot loader and then plug in the USB.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
veeman said:
It says you can get to the boot loader with the cable unplugged. So get to the boot loader and then plug in the USB.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
Click to expand...
Click to collapse
Are you kidding ? "3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected ."
I really appreciate any kind of help, but why even write and answer when you didnt even fully read the question ?
rkiller51 said:
Are you kidding ? "3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected ."
I really appreciate any kind of help, but why even write and answer when you didnt even fully read the question ?
Click to expand...
Click to collapse
Lol just calm down man we're all just trying to help you!
Now, you need to get your N7 into the bootloader, it does not matter if you can't navigate the bootloader on your N7. Once in the bootloader, connect the N7 to your computer with the USB cable.
Once you're connected, make sure you've downloaded the Android SDK and open a command prompt. Navigate your command prompt (make sure you ran that command prompt as administrator) to the "platform-tools" directory.
Once in the platform-tools directory run the following command without quotes:
"fastboot devices"
It should return the serial number for your device, indicating that fastboot sees your N7 and can work with it.
After that type
"fastboot flash recovery *.img"
You'll need to head to clockworkmod.com to download the N7 recovery image. Place the downloaded image in the platform-tools directory and replace "*.img" with the filename of the recovery image you downloaded.
That's it! Unplug your N7 and go into recovery, and sideload whatever ROM you want!
Let us know how it goes!
PS: If fastboot devices shows nothing, we have a bigger problem...
TMan459 said:
Lol just calm down man we're all just trying to help you!
Now, you need to get your N7 into the bootloader, it does not matter if you can't navigate the bootloader on your N7. Once in the bootloader, connect the N7 to your computer with the USB cable.
Once you're connected, make sure you've downloaded the Android SDK and open a command prompt. Navigate your command prompt (make sure you ran that command prompt as administrator) to the "platform-tools" directory.
Once in the platform-tools directory run the following command without quotes:
"fastboot devices"
It should return the serial number for your device, indicating that fastboot sees your N7 and can work with it.
After that type
"fastboot flash recovery *.img"
You'll need to head to clockworkmod.com to download the N7 recovery image. Place the downloaded image in the platform-tools directory and replace "*.img" with the filename of the recovery image you downloaded.
That's it! Unplug your N7 and go into recovery, and sideload whatever ROM you want!
Let us know how it goes!
PS: If fastboot devices shows nothing, we have a bigger problem...
Click to expand...
Click to collapse
Its hard to be calm then you new N7 is dying :/
somthing like this ? (pic attached)
If i did everything like you said it means i do have the bigger prob help me!
OK. Next thing is to ensure your N7 is properly detected in Windows.
Just head to the device manager. You should see Original Android Interface or something along those lines.
Report back with a screenshot, those are very helpful!
TMan459 said:
OK. Next thing is to ensure your N7 is properly detected in Windows.
Just head to the device manager. You should see Original Android Interface or something along those lines.
Report back with a screenshot, those are very helpful!
Click to expand...
Click to collapse
Here you go (attached) ! you have everything you need mate ?
I really appreciate the help ! :good::good:
I had similar issues and was able to get back to stock using WugFresh's Nexus Root Toolkit. Highly recommended!
From the same command Window, in the same platform - tools directory, does adb devices show your device?
I'm not the lowest of the low, but I am the slowest of the slow.

help! my g2 only boots into fastboot

I was trying to install a custom recovery (twrp) by several different methods, with absolutely no luck (but that's another secondary issue at this point) and i screwed something up. Not exactly sure but i think the last thing I did was:
using "Rashr - Flash Tool" i think i went to "flash kernel from storage" then flashed boot.img.
now the phone goes immediately, directly into fastboot even without being connected to computer.
so i tried getting into the stock recovery by holding "volume down" and "power" until lg logo, releasing the reholding until factory reset screen. after choosing yes 2 times i get a
"boot certicification verify" or something message for about a second then it goes to this screen (sorry but apparently i haven't had enough posts on the forums to include clickable links.)
h**ps://drive.google.com/file/d/0BwQdFsCQ9KZVaGM1eWdJb25WVVU/view?usp=sharing
slplsnphx said:
I was trying to install a custom recovery (twrp) by several different methods, with absolutely no luck (but that's another secondary issue at this point) and i screwed something up. Not exactly sure but i think the last thing I did was:
using "Rashr - Flash Tool" i think i went to "flash kernel from storage" then flashed boot.img.
now the phone goes immediately, directly into fastboot even without being connected to computer.
so i tried getting into the stock recovery by holding "volume down" and "power" until lg logo, releasing the reholding until factory reset screen. after choosing yes 2 times i get a
"boot certicification verify" or something message for about a second then it goes to this screen (sorry but apparently i haven't had enough posts on the forums to include clickable links.)
h**ps://drive.google.com/file/d/0BwQdFsCQ9KZVaGM1eWdJb25WVVU/view?usp=sharing
Click to expand...
Click to collapse
if u still have acces to fastboot use this or u see many disk at windows use srktool http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
amin44 said:
if u still have acces to fastboot use this or u see many disk at windows use srktool http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
Click to expand...
Click to collapse
ok, i do have access to fastboot (actually, as soon as i power it on, it immediately is in foastboot mode, even without being connected to computer). i tried using srktool's repair tools via fastboot. it seems like it's working (ie phone shows that it receives command) but that's it. does it take a loooooong time or something?
btw, i can also get into download mode by holding "vol up" while plugging into computer. so, i tried using srktool utilites via download mode and nothing.
also, i just noticed that while connected to computer in download mode, in device manager it shows G2 under "portable devices" with an exclamation point on it.
slplsnphx said:
ok, i do have access to fastboot (actually, as soon as i power it on, it immediately is in foastboot mode, even without being connected to computer). i tried using srktool's repair tools via fastboot. it seems like it's working (ie phone shows that it receives command) but that's it. does it take a loooooong time or something?
btw, i can also get into download mode by holding "vol up" while plugging into computer. so, i tried using srktool utilites via download mode and nothing.
also, i just noticed that while connected to computer in download mode, in device manager it shows G2 under "portable devices" with an exclamation point on it.
Click to expand...
Click to collapse
are u sure u do not have franken phone open battery cover and see model written inside motherbord
amin44 said:
are u sure u do not have franken phone open battery cover and see model written inside motherbord
Click to expand...
Click to collapse
I haven't taken the back off (yet) but all indications are that it's an AT&T (D800).
What part of my description makes you think that it might be a franken phone?
Did you try connecting the phone in download mode or fastboot to the LG Mobile Support Tool and performing an upgrade recovery?
audit13 said:
Did you try connecting the phone in download mode or fastboot to the LG Mobile Support Tool and performing an upgrade recovery?
Click to expand...
Click to collapse
not sure what you mean by "lg mobile support tool". i googled it and found and installed "lg pc suite". is that the same thing?
nevermind that last question. i found and installed and tried the upgrade recovery tool but for some reason the phone wont go into download mode anymore. when i power it up whith ""vol +" help down, it shows download mode for a second, but then goes right into fastboot mode.
Is it recognized by the program in fastboot mode?
Here's the program I was referring to: http://www.lg.com/ca_en/support-mobile/lg-LGD803
Even though the program says it is for the 803, I used it to recover my international d802.
slplsnphx said:
not sure what you mean by "lg mobile support tool". i googled it and found and installed "lg pc suite". is that the same thing?
nevermind that last question. i found and installed and tried the upgrade recovery tool but for some reason the phone wont go into download mode anymore. when i power it up whith ""vol +" help down, it shows download mode for a second, but then goes right into fastboot mode.
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
amin44 said:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
Thanks for the reply! But when I have phone connected to USB in fastboot, it shows up in device manager as "android device > USB modem phone port". Is that method the right fix for my situation?
ok, so likei said my phone is indeed in fastboot mode, connected to computer via usb (shows up in device manager as "android device > USB modem phone port". using srktool, i can send commands to the phone (command shows up on phone but thats it.....doesnt matter what command, it just sticks there until i unplug the phone then srktool shows the operation competed and phone shows
https://drive.google.com/file/d/0BwQdFsCQ9KZVSVg3OTZLcXV0N0E/view?usp=sharing
but none of operations actually complete on the phone.
slplsnphx said:
Thanks for the reply! But when I have phone connected to USB in fastboot, it shows up in device manager as "android device > USB modem phone port". Is that method the right fix for my situation?
Click to expand...
Click to collapse
that method fix for all situation
amin44 said:
that method fix for all situation
Click to expand...
Click to collapse
ok i shorted the capacitors, and eventually have gotten to where i can get into twrp. i assume that is serious progress, but what do i need to do next?
slplsnphx said:
ok i shorted the capacitors, and eventually have gotten to where i can get into twrp. i assume that is serious progress, but what do i need to do next?
Click to expand...
Click to collapse
flash stock ROM via download mode or flash custom ROM via twrp.
the first choice (stock ROM) is better
thanks for the responses!!
before i saw your reply, i flashed the stock .tot firmware and now i have my phone back.
but, before all this started, it was lollipop(5.0.2) and now it's Jellybean(4.2.2). i bought phone on ebay, so im assuming that it got lollipop via an ota update. so now i'm looking into flashing it back to lollipop. what's the easiest method to install stock lollipop?

Non Hacked/Rooted 6p Shut Off And Will Not Turn On

bought this phone used and I don't think it was rooted but never checked, confirmed. Last night it turned off and will not turn on anymore..
Tried the pwr button for several minutes and no change. Plugged it in with several different cables and no change.
Any other suggestions or options? USB to computer detects something but says it can't install the driver.
Any ideas?
oNe
Can you enter to the bootloader menu? Maybe you can enter recovery and wipe the cache and dalvik
martinfarrell11 said:
Can you enter to the bootloader menu? Maybe you can enter recovery and wipe the cache and dalvik
Click to expand...
Click to collapse
negative, either the phone is totally dead or the screen is dead but NOTHING happens when pwr is pressed
here is what I have tried:
1. Press and hold PWR button for over 3minutes
- Plugged in and unplugged into ac - no change
2. Press and hold volume DOWN + Pwr for over 3minutes
- Plugged in and unplugged into ac - no change
3. Plugged into different a/c power outlets with 2 different chargers - no change
NOT sure what else to try or do?
Funny thing is if ya plug into a computer it does indeed detect "something'
However it says it can't load the USB drivers something about QU_***
Open to any ideas and suggestions.. WHILE I would love to get the phone working whats more high priority for me now is the 20gb's of pics that apparently did NOT back up.
oNe
Sean Price said:
Funny thing is if ya plug into a computer it does indeed detect "something' However it says it can't load the USB drivers something about QU_***
Click to expand...
Click to collapse
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
v12xke said:
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
Click to expand...
Click to collapse
Several threads with no solution. I went through the same "something" . Can't be fixed
v12xke said:
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
Click to expand...
Click to collapse
fixed that issue, aka QHSUSB_BULK is now working properly according to Device Manager.. but Nexus 6P is not detected, and doesn't even show up in Disk Management either.
Any other ideas?
please advise..
oNe
Sean Price said:
fixed that issue, aka QHSUSB_BULK is now working properly according to Device Manager.. but Nexus 6P is not detected, and doesn't even show up in Disk Management either. Any other ideas? please advise.. oNe
Click to expand...
Click to collapse
If you found the right EDL_9008 thread, there is Qualcomm software to download for your PC. If your phone is in the right downloader mode you can use the PC software with a special recovery.img. I don't know anything about it, just read through the threads long ago. It's a mixed bag with some success stories, some not. Keep looking though, I think you are on the right track. The original poster was "Tenfar" if I recall correctly. Good luck.
Try cleaning out the charging port.
Hi there,
I think we are in the same/similar boat. My phone shut off while using it (screen froze, then went black) and seems to have bricked itself. I *am* able to get mine to turn on, but only about once per day after it has been left plugged in for a few hours (although there is no indication it is charging while plugged in - never gets warm, no lights, etc.) I can get into recovery if I am lucky (usually get to the android bot laying on its back, then PWR+VOLUP just causes the phone to shut off instead of actually getting into recovery menu.) I've been able to clear cache/factory wipe from recovery menu with no luck. I never did unlock the bootloader so I am unable to use fastboot to do anything. I tried to flash a few OTA (full and incremental) images using adb when I am able to get into recovery, but they always failed in one way or another.
I've been trying the methods described in the 'tenfar' threads - using the xiaomi flasher and QPST tools. The xiaomi tool always fails for me. I have been able to get the QFIL tool to successfully 'download' about 3 times now, with tenfar's recovery images. However, after the success message, the phone doesn't do anything (I read in other threads it should reboot itself) - and after unplugging, the behavior of the device seems to be the same - just stuck and won't turn on at all.
Right now I think I am stuck in 'EDL' mode where the only evidence that the device isn't completely dead is that it shows up in device manager as 'Qualcomm HS-USB QDLoader 9008 (COM3)', and the factory imager tools do recognize it.
It *seems* like the only way forward is to somehow get one of these factory tools to flash the right set of files onto the device - I've tried a few now with no luck. I even tried extracting the relevant *.img files out of the google factory image download and replacing tenfar's image files with them. I was able to load those onto the device with QFIL. This morning my attempt at turning on the device has me stuck on the white google logo, which is new behavior for me - usually it shows the logo for ~5-10 seconds then the device powers off. I've left it on for a while stuck on the white google image, but I'm not sure if I'm doing anything useful here.
Here are my reference threads:
tenfar's 'debrick' thread
QFIL thread
If anyone has any crazy ideas, I am open to try them. Thank you.
Maybe disable big cores?
apples1678 said:
Hi there,
I think we are in the same/similar boat. My phone shut off while using it (screen froze, then went black) and seems to have bricked itself. I *am* able to get mine to turn on, but only about once per day after it has been left plugged in for a few hours (although there is no indication it is charging while plugged in - never gets warm, no lights, etc.) I can get into recovery if I am lucky (usually get to the android bot laying on its back, then PWR+VOLUP just causes the phone to shut off instead of actually getting into recovery menu.) I've been able to clear cache/factory wipe from recovery menu with no luck. I never did unlock the bootloader so I am unable to use fastboot to do anything. I tried to flash a few OTA (full and incremental) images using adb when I am able to get into recovery, but they always failed in one way or another.
I've been trying the methods described in the 'tenfar' threads - using the xiaomi flasher and QPST tools. The xiaomi tool always fails for me. I have been able to get the QFIL tool to successfully 'download' about 3 times now, with tenfar's recovery images. However, after the success message, the phone doesn't do anything (I read in other threads it should reboot itself) - and after unplugging, the behavior of the device seems to be the same - just stuck and won't turn on at all.
Right now I think I am stuck in 'EDL' mode where the only evidence that the device isn't completely dead is that it shows up in device manager as 'Qualcomm HS-USB QDLoader 9008 (COM3)', and the factory imager tools do recognize it.
It *seems* like the only way forward is to somehow get one of these factory tools to flash the right set of files onto the device - I've tried a few now with no luck. I even tried extracting the relevant *.img files out of the google factory image download and replacing tenfar's image files with them. I was able to load those onto the device with QFIL. This morning my attempt at turning on the device has me stuck on the white google logo, which is new behavior for me - usually it shows the logo for ~5-10 seconds then the device powers off. I've left it on for a while stuck on the white google image, but I'm not sure if I'm doing anything useful here.
Here are my reference threads:
tenfar's 'debrick' thread
QFIL thread
If anyone has any crazy ideas, I am open to try them. Thank you.
Click to expand...
Click to collapse
I have the 100% same issue. Screen froze,then went black and now its stuck in EDL mode. I need my data. Recovery access or anything else would be fine/enough for me. I have had LineageOS and TWRP on the device. With TWRP i can access my data.
How have you got your device on? Mine dont start once a day or so. Its always in EDL mode ( 9008 ).
ncc8uetou5et said:
I have the 100% same issue. Screen froze,then went black and now its stuck in EDL mode. I need my data. Recovery access or anything else would be fine/enough for me. I have had LineageOS and TWRP on the device. With TWRP i can access my data.
How have you got your device on? Mine dont start once a day or so. Its always in EDL mode ( 9008 ).
Click to expand...
Click to collapse
Sorry bud - I never was able to get any further than when I posted this. I eventually gave up, got a full out of warranty refund through my CC after the manufacturer wouldn't help me at all, and upgraded to a Pixel XL. I still do have the device, I should try to boot it up again . I didn't have any data concerns on my device so I was able to give up... good luck!

Stuck in rescue mode after tried flashing stock firmware

Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.

Phone acting strange - Bricked?

Hi
My phone stopped working a couple of days ago, I had been running a custom rom for 2 mths. I tried to restart and boot to recovery TWRP as I was going to reflash the rom. It charegs with no lights, for a day I couldnt boot to TWRP if it did it stayed on the start screen with no options. Today I can get options in TWRP so I tried to start fresh install but intstallation stops at step 1 ?
I have no idea what happened to the phone or why it just died, but dont understand why I can get into TWRP but cant flash rom etc. Also sometimes it say system destroyed message? but still can get into TWRP ?
Any ideas or help will much appreciated really would like to fix this rather than write the phone off.
Thanks
i think flashing firmware is the only option
ranjodhricky said:
i think flashing firmware is the only option
Click to expand...
Click to collapse
Hi, yeah I think thats what I try, is this flashing stock rom via MI flash or a different process?
try miflash if doesn't work try QFil
update
ranjodhricky said:
try miflash if doesn't work try QFil
Click to expand...
Click to collapse
Hi, been playing with this when i have time over the last few weeks.
I have been trying to flash firmware, I dont seem to be able to get QFIL to work for me, it wont reconsise the port. However MIFlash does but I get errors, sometimes it flashes but doesnt end? other times i have had error flashing modem_a or error flashing modem_b (maybe device is locked).
In ADB it says already unlocked. Also I can only boot into fastboot, not recovery so i cant intall anything from adb sideload, it wont boot into bootloader just powers off if i try this. I guess theres no recovery on it now as I cannot boot into it.
Any ideas on where to go from here , EDL? I really didnt want to attempt to open the phone.
Thanks
Try miflash 2019 with stock rom pie latest with edl mode
if bootloader unlocked You can enter edl mode via fastboot with the command 'fastboot oem edl'
Yincen said:
Try miflash 2019 with stock rom pie latest with edl mode
if bootloader unlocked You can enter edl mode via fastboot with the command 'fastboot oem edl'
Click to expand...
Click to collapse
Thanks, tried this, says success then just carries on , so i have to disconnect. However when then trying to boot the device it shows Android one logo and if im lucky after a few attempts it goes to the screeen saying Hi There, where you choose your language to set up the phone. However it nows seem to be unresponsve and frozen on that screen.
Im beginning to think its could be hardware issue and phone is just faulty, i really dont want to bin it as its imacculate condition seems a real shame, but it is 3 years old i guess.
Any further help or ideas much appreciated.
healy2k said:
Thanks, tried this, says success then just carries on , so i have to disconnect. However when then trying to boot the device it shows Android one logo and if im lucky after a few attempts it goes to the screeen saying Hi There, where you choose your language to set up the phone. However it nows seem to be unresponsve and frozen on that screen.
Im beginning to think its could be hardware issue and phone is just faulty, i really dont want to bin it as its imacculate condition seems a real shame, but it is 3 years old i guess.
Any further help or ideas much appreciated.
Click to expand...
Click to collapse
try doing a factory reset from Recovery , good luck

Categories

Resources