Database Users

Nexus 4 Problem: Wont boot into system or recovery, but fastboot and able to flash?!!

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

stuck in boot loop no recovery locked bootloader no adb access just fastboot

hi
someone gave me this broken phone so i don't know what happened to get it to this point
here's the breakdown of what it's doing and what i've tried
it's a sprint variant
bootloader ver mata-8a1a76e
baseband ver 2.0.c4-m2.0.2
secure boot yes
device state locked
no power and won't turn on unless connected with a usb cable to laptop or charger but when connected stays on until unplugged
i've tried multiple cables
stuck in boot loop on powered by android screen
with vol up and power just boot loops back to the powered by android screen like there is no recovery
with vol down and power boots into fastboot mode and is visible in simple adb under the fastboot tab i'm able to see the serial number but not under the adb tab there's no devices listed
when i try to use erase or flash commands it says cannot be done in a locked state which tells me the bootloader is locked and the oem and usb debug is not turned on
it says the active slot is b but won't let me change slots because of locked statues
is there anyway to turn on oem unlock and usb debug with it not booting i've tried all of the flashing unlock bootloader commands in simple adb's fastboot tab but nothing is working i can see and talk to the phone with fastboot but because of locked bootloader i can't do anything.
any help would be great it's not important it's just a phone to play around with abd and roms to see what i can do and try to teach myself somethings but it was stock the guy that gave it to me dosen't know anything about phones he dropped it and broke the touch screen and just got another one
so if anyone could point me in the right direction or tell me if it's possible to get oem unlock and usb debug turned on in a non booting no adb connection but fastboot connectable phone with no bootable recovery
if you need anymore info just let me know
thanks in advance
hippiehemp

hippiehemp said:
hi
someone gave me this broken phone so i don't know what happened to get it to this point
here's the breakdown of what it's doing and what i've tried
it's a sprint variant
bootloader ver mata-8a1a76e
baseband ver 2.0.c4-m2.0.2
secure boot yes
device state locked
no power and won't turn on unless connected with a usb cable to laptop or charger but when connected stays on until unplugged
i've tried multiple cables
stuck in boot loop on powered by android screen
with vol up and power just boot loops back to the powered by android screen like there is no recovery
with vol down and power boots into fastboot mode and is visible in simple adb under the fastboot tab i'm able to see the serial number but not under the adb tab there's no devices listed
when i try to use erase or flash commands it says cannot be done in a locked state which tells me the bootloader is locked and the oem and usb debug is not turned on
it says the active slot is b but won't let me change slots because of locked statues
is there anyway to turn on oem unlock and usb debug with it not booting i've tried all of the flashing unlock bootloader commands in simple adb's fastboot tab but nothing is working i can see and talk to the phone with fastboot but because of locked bootloader i can't do anything.
any help would be great it's not important it's just a phone to play around with abd and roms to see what i can do and try to teach myself somethings but it was stock the guy that gave it to me dosen't know anything about phones he dropped it and broke the touch screen and just got another one
so if anyone could point me in the right direction or tell me if it's possible to get oem unlock and usb debug turned on in a non booting no adb connection but fastboot connectable phone with no bootable recovery
if you need anymore info just let me know
thanks in advance
hippiehemp
Click to expand...
Click to collapse
Hi, were you able to fix this issue?
I have the same exact problem here, its been few months actually, but still trying to figure this out.

download the offical firmware images and flash with fastboot
bootloader lock has not effect on flashing stock firmware or whatever slot its on

Legitsu said:
download the offical firmware images and flash with fastboot
bootloader lock has not effect on flashing stock firmware or whatever slot its on
Click to expand...
Click to collapse
Are you sure of that? Because Essential specifically instructs to enable "OEM Unlocking" and unlock the BL before flashing the factory image via fastboot...

Legitsu said:
download the offical firmware images and flash with fastboot
bootloader lock has not effect on flashing stock firmware or whatever slot its on
Click to expand...
Click to collapse
Oh God...
Please stop...
You are full of bad information...
You cannot use fastboot with a locked bootloader .. it is the Essential way...

hippiehemp said:
hi
someone gave me this broken phone so i don't know what happened to get it to this point
here's the breakdown of what it's doing and what i've tried
it's a sprint variant
bootloader ver mata-8a1a76e
baseband ver 2.0.c4-m2.0.2
secure boot yes
device state locked
no power and won't turn on unless connected with a usb cable to laptop or charger but when connected stays on until unplugged
i've tried multiple cables
stuck in boot loop on powered by android screen
with vol up and power just boot loops back to the powered by android screen like there is no recovery
with vol down and power boots into fastboot mode and is visible in simple adb under the fastboot tab i'm able to see the serial number but not under the adb tab there's no devices listed
when i try to use erase or flash commands it says cannot be done in a locked state which tells me the bootloader is locked and the oem and usb debug is not turned on
it says the active slot is b but won't let me change slots because of locked statues
is there anyway to turn on oem unlock and usb debug with it not booting i've tried all of the flashing unlock bootloader commands in simple adb's fastboot tab but nothing is working i can see and talk to the phone with fastboot but because of locked bootloader i can't do anything.
any help would be great it's not important it's just a phone to play around with abd and roms to see what i can do and try to teach myself somethings but it was stock the guy that gave it to me dosen't know anything about phones he dropped it and broke the touch screen and just got another one
so if anyone could point me in the right direction or tell me if it's possible to get oem unlock and usb debug turned on in a non booting no adb connection but fastboot connectable phone with no bootable recovery
if you need anymore info just let me know
thanks in advance
hippiehemp
Click to expand...
Click to collapse
Same problem here. After a official upgrade i can only access to fastboot mode. Select recovery, start, etc... reset the phone and returns to fastboot mode.
Secure boot - yes
only diference - Bootloader version mata-b9326aa and baseband 2.0.c4-M2.0.10

YaKuM0 said:
Same problem here. After a official upgrade i can only access to fastboot mode. Select recovery, start, etc... reset the phone and returns to fastboot mode.
Secure boot - yes
only diference - Bootloader version mata-b9326aa and baseband 2.0.c4-M2.0.10
Click to expand...
Click to collapse
If the bootloader is locked, and you can't get to recovery to sideload, you're stuck

Lost Fastboot??!!

Ok.....so after my other issues i have posted here in this thread...which still appears to be unanswered.....
https://forum.xda-developers.com/axon-7/help/modem-issue-t3917268
I have noticed that i do not have fastboot!!! i cannot get to it neither through Axon7Toolkit, not through ADB, and neither through the black warning screen if i hold Volume (-) and select "fastboot", the phone just boots on to the system. I have done EDL flashes through the djkuz's app and it doesn't seem to do anything really, as my computer recognizes just as before and with adb permissions not needed. I though the EDL flash formats data as well........
Do I have a partition missing???? If so, how can I restore it? what is a sure cut way to return as if to stock truly like purchased from ZTE themselves??
Any help guys would be much appreciated

kevace1 said:
Ok.....so after my other issues i have posted here in this thread...which still appears to be unanswered.....
https://forum.xda-developers.com/axon-7/help/modem-issue-t3917268
I have noticed that i do not have fastboot!!! i cannot get to it neither through Axon7Toolkit, not through ADB, and neither through the black warning screen if i hold Volume (-) and select "fastboot", the phone just boots on to the system. I have done EDL flashes through the djkuz's app and it doesn't seem to do anything really, as my computer recognizes just as before and with adb permissions not needed. I though the EDL flash formats data as well........
Do I have a partition missing???? If so, how can I restore it? what is a sure cut way to return as if to stock truly like purchased from ZTE themselves??
Any help guys would be much appreciated
Click to expand...
Click to collapse
Fastboot functionality is gone after stock B19.
If you want fastboot, you're going to have to EDL flash B19 Chinese firmware, that's the only one that has fastboot afaik. You're not missing a partition, the phone rebooting to system after selecting fastboot is normal.

runninghamster said:
Fastboot functionality is gone after stock B19.
If you want fastboot, you're going to have to EDL flash B19 Chinese firmware, that's the only one that has fastboot afaik. You're not missing a partition, the phone rebooting to system after selecting fastboot is normal.
Click to expand...
Click to collapse
Hey thanks for that for that answer. I was hoping that was the smoking gun.......So if you don't mind.....if you know....I pretty sure it was discussed here somewhere......what exactly is the "vendor" partition? That to me is a bit new as I do that recall that being a "common" partition as like modem, or recovery etc....there's got to be something missing that is not letting my phone get signal anymore...I can pop my SIM card in and it'll receive a message that I have "voicemail" if I have one that's still new, but it won't get service......I know for sure it has to be something software related.........
Sent from my Moto Z (2) using Tapatalk

kevace1 said:
Hey thanks for that for that answer. I was hoping that was the smoking gun.......So if you don't mind.....if you know....I pretty sure it was discussed here somewhere......what exactly is the "vendor" partition? That to me is a bit new as I do that recall that being a "common" partition as like modem, or recovery etc....there's got to be something missing that is not letting my phone get signal anymore...I can pop my SIM card in and it'll receive a message that I have "voicemail" if I have one that's still new, but it won't get service......I know for sure it has to be something software related.........
Click to expand...
Click to collapse
Are you 100% sure it's not a hardware problem? The phone not getting signal anymore can be due to many reasons.
Check the SIM card, make sure it's not defective. Try inserting it into another phone and check if it works. If it works in the other phone, then you've ruled out the SIM card.
Check the SIM card slot, make sure no pins are bent or broken. Check that the SIM card goes into the phone correctly, and if you've previously opened up the phone then check if there's any internal damage.
If you believe it's a software problem, try these:
Try resetting the APN (Settings>Network & Internet>Mobile Network>Access Point Names), or manually retype your APN (You can find this by googling for your carrier's apn eg; TMobile APN).
Check that your IMEI is still good, you can do this by inserting the SIM and heading to the Dialer, and typing *#06#
Check that your IMEI still shows up and make sure it doesn't show Null.
Go into your Dialer again and type
*#*#4636#*#*
It will bring up a menu, click on Run Ping Test and check if your phone shows Connected.

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.

(Help) EDL Test Points needed or a solution on G6+

So, basically I will make this short as possible
Due to some problems I had to sell my G6 Plus (Brazilian -8 model) but it was on a custom rom, and did the most dumb thing that I could do: Reflashing pure stock and locking it, I've used the LMSA tool then relocked in Fastboot, the thing is some files were corrupt and when locked, it doesn't boot up anymore, as i still had hope for it, I tried to LSMA again, but it doesnt recognize anymore, as the lock flag is now "Flashing_Locked", flashing manually via Fastboot gives a error related to the lock flag (also LSMA resets the device, so using my unlock key asks to enable OEM Unlock at settings, a impossible thing when OS is broken) , then searched for some solutions, first it was booting a Boot.img file from the last stock, which was the flashed one, it bootloops, then tried something on the recovery that works, but is the stock one and pretty limited, so the logical thing to do is flashing a OTA file, but only works for old versions that requires one version before the target one, so its a no go. The last thing i tried to do is booting TWRP, but it gets stuck on a red warning that indicates that system is corrupt. Then the last hope was EDL Mode, and thats the point where i want to go, i've bought a EDL Cable that's basically a green and black wire thing used on most Qualcomm based Redmi/Xiaomi devices, but it automatically boots to fastboot, so I need help to get EDL Test Points for this device, im with access to the board, i just need the right Pads to short-circuit it and blankflash it, so i can finally get it to work like normal again.
Schematics (for people who understands): https://androidfilehost.com/?fid=4349826312261726244
Any help is important, I'm sorry for some typos, english isnt my main language considering i didnt use translate
and please don't come with instructions like "have you tried LSMA?, try booting up the device and select oem unlock" because its clear that it doesnt work.