Database Users

[Q] Did I brick the Nexus 4?

Hey guys!
Yesterday I made a big mistake in the afternoon. I hate myself and don't know what to do now.
I was tired and without concentration so i flashed the nexus 7 franco kernel r38 on my nexus 4 :'(
Now my nexus 4 won't boot up. It's completely shutdown and without AC charging nothing happens.
With plugged in AC power supply module after pressing volume down and power on for 11 sec the red led lights up once for a short time.
If the nexus 4 is connected to the computer with usb the device manager shows me a unknown device 'QHSUSB_DLOAD'.
I have no possibility to go to fastboot mode or recovery. There is only a BlackScreen!
Is there a possibility to make my mistake undo?
If read a lot of threads for now and found solutions (UnBrickableResurrector) for the Galaxy Nexus S but there is nothing for the nexus 4.
Thank you for you help!

chris_te said:
Hey guys!
Yesterday I made a big mistake in the afternoon. I hate myself and don't know what to do now.
I was tired and without concentration so i flashed the nexus 7 franco kernel r38 on my nexus 4 :'(
Now my nexus 4 won't boot up. It's completely shutdown and without AC charging nothing happens.
With plugged in AC power supply module after pressing volume down and power on for 11 sec the red led lights up once for a short time.
If the nexus 4 is connected to the computer with usb the device manager shows me a unknown device 'QHSUSB_DLOAD'.
I have no possibility to go to fastboot mode or recovery. There is only a BlackScreen!
Is there a possibility to make my mistake undo?
If read a lot of threads for now and found solutions (UnBrickableResurrector) for the Galaxy Nexus S but there is nothing for the nexus 4.
Thank you for you help!
Click to expand...
Click to collapse
Can you boot into fastboot? recovery?
Edit: Sorry, saw that you wrote you can't...

I added the information afterwards. Sry

Basically, there are two ways to fix this:
1) I don't know how, but through QHSUSB_DLOAD you probably can flash something...
2) JTAG Repair.

1) Sounds interessting. I thought at something like this: UnBrickable Resurrector
But is there a chance to get this solution to our nexus 4?
2) Nexus 4 - JTAG Brick Repair Service is also interessting but i don't know how much time it take vom germany to usa to germany back.
I thought the nexus 4 is unbrickable

If you got it into Download mode, then you should be able to get into recovery. (Assuming you didn't do a bad flash of that)
Unplug it
Hold volume down and power
Plug it into WALL CHARGER (not a computer) while still holding the buttons

Someone also flashed a Nexus 7 kernel (also Franco) to his Nexus 4. Didn't look good because the Nexus 7 kernel overwrites a partition from the bootloader, if I remember correctly. Here is it explained better. The last post from the guy who flashed it didn't look too good also. Sorry to hear man.
Maybe you can RMA it. I don't recommend it because it's your own fault, but everyone makes a mistake sometime sooner or later.

I am another one who did the same mistake - accidently flashed the franco Nexus 7 Kernel. ::crying:
Even the Qualcomm flash tool which I tried couldn't get acces to the device. So I'm waiting for my replacement device now and hope LG can fix the problem.

chris_te said:
Hey guys!
Yesterday I made a big mistake in the afternoon. I hate myself and don't know what to do now.
I was tired and without concentration so i flashed the nexus 7 franco kernel r38 on my nexus 4 :'(
Now my nexus 4 won't boot up. It's completely shutdown and without AC charging nothing happens.
With plugged in AC power supply module after pressing volume down and power on for 11 sec the red led lights up once for a short time.
If the nexus 4 is connected to the computer with usb the device manager shows me a unknown device 'QHSUSB_DLOAD'.
I have no possibility to go to fastboot mode or recovery. There is only a BlackScreen!
Is there a possibility to make my mistake undo?
If read a lot of threads for now and found solutions (UnBrickableResurrector) for the Galaxy Nexus S but there is nothing for the nexus 4.
Thank you for you help!
Click to expand...
Click to collapse
Sorry to hear your bootloader has been obliterated. Try to RMA via Google or contact LG and find out how much they will charge to flash the device.
On a side note, I'm curious if you're able to put the phone in to download mode (not fasboot or recovery).
1. Make sure it is off
2. Hold volume up + volume down and plug in USB.
Even if you can get to download mode I don't think we have what we need to get the device working (LG drivers, KDZ image, etc) but this would indicate some promise for the future.

Until the Qualcomm USB Dowland mode is figured out, you're boned. Gonna have to send it away.

comminus said:
On a side note, I'm curious if you're able to put the phone in to download mode (not fasboot or recovery).
1. Make sure it is off
2. Hold volume up + volume down and plug in USB.
Click to expand...
Click to collapse
Hi,
I tried your suggestion and it did't work
The phone tried to boot into download mode but didn't get it. Screen was always black. After 10 second the phone vibrated and tried it once more.
Do you think the people of MobileTechVideos can help me?
I'm still waiting for a response from Josh.
Here is a link to a Nexus 4 - JTAG Brick Repair Service video: http://www.youtube.com/watch?v=gYtNWt1h66E
And if all this does not work, i have to send it to the google RMA.

If it were me, I'd pay LG to fix it. Either contact Google for RMA or contact LG and ask them what they would charge to flash the device.
Sent from my Nexus 4

chris_te said:
Hi,
I tried your suggestion and it did't work
The phone tried to boot into download mode but didn't get it. Screen was always black. After 10 second the phone vibrated and tried it once more.
Do you think the people of MobileTechVideos can help me?
I'm still waiting for a response from Josh.
Here is a link to a Nexus 4 - JTAG Brick Repair Service video: http://www.youtube.com/watch?v=gYtNWt1h66E
And if all this does not work, i have to send it to the google RMA.
Click to expand...
Click to collapse
Just press VOL - key and plug into USB connected to PC, ARE YOU IN FASTBOOT MODE ?!
IF YES, flash stock firmwares... and let the device rest for 15 min.
then plug into AC charger and let it charge for min. 1 hour...
If nothing happens, you possibly damaged your battery !
I had the same issue... I sent it for RMA.. Although by this method, many have recovered, if there is no battery issue as such !
Give it a try !
And dont use toolkit... Use FASTBOOT COMMANDS ! MANUALLY !

You have to reach fastboot mode:
1) Turn the phone off!! Not so easy (for me when never done before)!! Unplug it and try to press power, it often needs a little time/serveral tries.
When off :good:- very important:
2) Hold volume - and power simultaniosly - and plug it into WALL CHARGER (not a computer) while still holding the buttons.
3) Fastboot Mode!!!? --> :laugh:
4) Plug it to PC and flash stock rom
Good luck!

torsin said:
You have to reach fastboot mode:
1) Turn the phone off!! Not so easy (for me when never done before)!! Unplug it and try to press power, it often needs a little time/serveral tries.
When off :good:- very important:
2) Hold volume - and power simultaniosly - and plug it into WALL CHARGER (not a computer) while still holding the buttons.
3) Fastboot Mode!!!? --> :laugh:
4) Plug it to PC and flash stock rom
Good luck!
Click to expand...
Click to collapse
The people who said the bootloader was overwritten are most likely right. Its done. This phone has the same processor as the s3 and on the s3 QHSUSB_DLOAD is the kiss of death.
QHSUSB_DLOAD=Qualcomm High Speed USB Download
Its basically a piece of hardware waiting for firmware to be loaded at a factory level. You need JTAG

billard412 said:
The people who said the bootloader was overwritten are most likely right. Its done. This phone has the same processor as the s3
Click to expand...
Click to collapse
btw: s3 is arm not qualcomm, but not important here.

Was referring to the us variants that also use the qualcomm snapdragon s4 processor like the n4 does

Ah, okay - sorry I don´t know!

And for the record, Qualcomm chips are ARM cores.

Also for the record, my JTAG solution for this model will recover a device that is hardbricked via bad software flash. In this case you have flashed a Tegra kernel into the device and likely also into the incorrect partition as well. I have a complete backup of all necessary zones required for boot (sbl's, aboot, boot, rpm, tz and a few others). If you've damaged your Nexus 4's bootable zones and the device is hard bricked due to it, I can repair it for you.

Bricked A2017G B03 - help please

Hello!
As title says i bricked my Axon :crying:
I followed http://forum.xda-developers.com/showpost.php?p=68738854&postcount=100 (and the german one that linked to this one) but couldnt do the fastboot unlock.
So i couldnt finish this and my phone required a pin number to start android: bootet and started up but wanted a pin code to start/enter system.
Wasnt able to fix that with googling for answers so i went back to edl mode and rewrote my backup boot/recovery images with axon7backup.
Had no errors with that but it wont start now:
After the ZTE Logo the display goes black but it connects as "handset diagnostic interface (DFU) (ComX)" to my computer.
I fiddled around with driver installing etc and forced the HS-USB QDLoader 9008 on it but no luck, axon7backup/root can not connect.
When i did the actual flashing yesterday it never connected with the hold both vol-keys and connect usb way either, always had to reboot into edl via adb.
I cant boot anything else (no twrp/recovery) it just goes to the diagnostic interface mode.
Thanks in advance

you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....

Starvirus said:
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Click to expand...
Click to collapse
Thanks. I tried it but it wont go to FTM. Only goes to diagnostic com port.
It seems i cant even turn it off. The little red light on the front is on the whole time .

sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.

adb don't show your device?

Starvirus said:
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
Click to expand...
Click to collapse
Oh ok. I expected ftm to work from vol-down and power-button till restart.
@adb: sadly no connection possible since it goes straight to Comport Connection.
Edit:
Couldnt make that work. It was off and i connected the usb. So it showed me the loading battery picture where i cant do anything. held the vol-down the whole time. But as soon as it had some battery it went straight to comport-connection again

im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in

i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(

nsabir said:
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
Click to expand...
Click to collapse
Hi,
couldnt fix it myself so i had to send it in.
Unless some tool/rom was released in the last few months to fix it yourself i would guess your device is bricked.

Hi I have almost the same problem, I tried to unlock bootloader and now I don't have the recovery, I can boot and use my mobile but I can't restore it or update it because I don't have the recovery
I try whit axon7tool to restore the recovery but I got a error.

MaxRink said:
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
Click to expand...
Click to collapse
Hi, do you have any idea, if there will be such a flashtool to work with DFU mode? I'm thinking that there are a lot of guys have bricked their devices (including me).
((

PC doesn't recognize my LG (download mode)

Hey guys!!!
Can you please help me with this?
Yesterday i tried to install a new ROM on my LG Android phone (My LG phone is not working properly, it has a reboot loop). I tried to do a factory reset without success -> the dead Android logo appeared :/
I put my phone in Download Mode and connected to the pc but Windows does not recognize my phone.. it says: "USB device not recognized.. the last USB device you connected to this computer malfunctioned and Windows does not recognize it"
I do not know what to do now.. when i try to flash a ROM with the LG Flash Tool it fails because LG program does not recognize my device..
PS: LG Support Tool recognizes my phone (it shows the model) but i cannot flash a ROM
Thanks!!:fingers-crossed:

android_simply said:
Hey guys!!!
Can you please help me with this?
Yesterday i tried to install a new ROM on my LG Android phone (My LG phone is not working properly, it has a reboot loop). I tried to do a factory reset without success -> the dead Android logo appeared :/
I put my phone in Download Mode and connected to the pc but Windows does not recognize my phone.. it says: "USB device not recognized.. the last USB device you connected to this computer malfunctioned and Windows does not recognize it"
I do not know what to do now.. when i try to flash a ROM with the LG Flash Tool it fails because LG program does not recognize my device..
PS: LG Support Tool recognizes my phone (it shows the model) but i cannot flash a ROM
Thanks!!:fingers-crossed:
Click to expand...
Click to collapse
Were you using a custom recovery? (i.e. TWRP)? If so, are you able to boot into recovery? It was a few years ago but whenever that happened to me I would have to use the hard reset option. If I remember correctly, on my LGG2, I would hold down the power button and the volume down button at the same time until the LG logo appears, then right when it appears, release and re-press both buttons again holding them down again until the hard reset option showed. Then when it asked me if I was sure I wanted to reset my phone, select yes (it made nervous the first ten times or so). Eventually I began to trust it would, in fact, do what I was informed it would do which was boot into TWRP without actually resetting anything. From there I was always able to flash a new ROM etc. Anyway, if you knew all that sorry, just trying to help. If not, please get second opinions since I will not be held responsible for your device and since it's been years since I tinkered with mine. Having a Samsung now, I don't mess with it cause rooting a Samsung Note trips Knox and then Samsung Pay is disabled.
Anyway, happy flashing and best of luck to you. It was an awesome hobby while I was involved with it.
Cheers!
Sent from my [device_name] using XDA-Developers Legacy app

[SOLVED] A2017G Hard brick, Unauthroized ADB and DFU Only.

Hey guys,
Guess today it was my turn ****ing up.
I apparently have completely bricked my Axon 7 after trying to go from LOS 15.1 to stock oreo beta. The only thing I seem to be able to boot to is DFU mode and for some reason, if I press the Power button + Vol Down I will get stuck on the ZTE Logo and my PC will detect my phone through the ADB interface but every time I try doing something it says my device is unauthorized. Is there any way I can authorize the device whilst being completely bricked?
The only other thing I get is the unlocked bootloader warning screen. If I don't press anything the phone will be stuck there, if I select recovery the phone will simply shut down and anything else will result in a reboot. I have also tried a deep flash cable that that only results on the phone being stuck at the unlocked bootloader screen.
I cannot access the bootloader,
I cannot access EDL mode
I can access ADB, but device shows as unauthorized.
I can access DFU mode.
Any suggestions would be appreciated. I have looked at the Hard brick guide that involves taking the phone apart but that's not something I really want to do.
Thanks in advance.
Edit: My phone gets detected by MiFlash but every time I try flashing I get a cannot receive hello packet and object reference not set to an instance of an object.
ZTE axon 7 EDL tool detects it in ADB mode but says ERROR! NO ANSWER FROM PHONE!. Possibly since its not authorized with ADB.

Ouh....DFU? I think this thing is totally bricked.

I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?

Victor13f said:
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Click to expand...
Click to collapse
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !

raystef66 said:
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
Click to expand...
Click to collapse
Thank you for your help . It's a risk you take when flashing phones.

Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.

stinka318 said:
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
Click to expand...
Click to collapse
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!

Victor13f said:
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Click to expand...
Click to collapse
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....

stinka318 said:
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
Click to expand...
Click to collapse
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!

Victor13f said:
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Click to expand...
Click to collapse
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable

Choose an username... said:
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Click to expand...
Click to collapse
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!

Victor13f said:
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Click to expand...
Click to collapse
In that case you can just pretend that the phone got in that state by itself, it's not too morally correct but some people here pulled it off...

twice now i have gotten an axon 7 into this state. while mine have been a2017u models, i dont know that they are different than yours in that regard.
What worked for me the first time was letting the phone completely die. Being unable to boot into anything, it was somewhat a task to actually make it die, so i kept powering it on (which merely made the red led indicator come on). i did this over and over again over the course of a day at work whenever i noticed it had powered off.
eventually, the phone had no response at all. then, i plugged it up to my laptop, and left it, convinced i had killed it. a dialogue popped up after a minute or two on the phone screen saying to charge the phone by plugging it up. i had no access to fastboot or EDL mode prior. once i got that 'plug in to charge' screen, i switched it to the wall charger, and left it to charge a bit (50-60%) from that state, then, i unplugged it again, and somehow, i managed to get edl mode to work by unplugging it and pressing all three buttons and holding them (typical edl boot).
once there, i reflashed via MiFlash an earlier build. i rolled back using MiFlash as far back as i could. in the process, i lost my imei and serial, which i have yet to successfully recover, but i did get out of DFU pergatory. the imei thing seems to be caused by going back to MM which i did on both of my IMEI-less a2017u boards, but im only guessing. my dd axon 7 is the only one of the three boards with imei and serial, so maybe MM is a bad idea. lol.
The first time i recovered from DFU, i did it inadvertently by letting the phone die and then flashing in EDL mode as well. (i left it for a few weeks as i had given up on it.) after it died completely, and i plugged ut up to the computer and had the same experience, I flashed the beta oreo build for a2017 using miflash. the screen had stopped responding. and i ended up doing a RMA. I now know the screen response thing was bc of a faulty EDL file of B15. (happened again to another of my axon, so i retraced my steps and realized it was when i flashed b15 that it died) . the fix if your screen ever stops responding, but isnt physically damaged? re-flash via EDL a different file. it may take a few tries, but eventually a build will work. for me, it was Marshmallow. I still do not know for certain, but that possibly is what killed my IMEI. but hey, it boots and the screen works.
I genuinely hope posting my idiocy in toying with axon 7s has helped someone out there.

SM-950F Hard bricked, JTAG?

Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?

S8 Hard bricked
A_Bad_Marksman said:
Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?
Click to expand...
Click to collapse
hello!
same happened to me ......dont worry i will help u....
i think u flashed aosp rom
phone is not hard bricked its still not turned off believe me........
do the following:
donot charge phone for atlesat 24 hours .......
after 24 hours try to boot into download mode press button for like a minute it will work in multiple tries,,
immediately flash twrp and when flashed successfully suddenly press vol down + bixby + power it will boot into recovery
charge for 1 -2 hours , clear system and every thing if you have backup thats good other wise flash firmware......donot turn in till flashing the system and data in recovery mood......boot into download mood from recovery and there you go....if still a problem inbox me

Thanks, I'll give it a shot

ok let me know then

Jtag dead phone to life and rewrite IMEI
I had the same thing, sent it to Fonefunshop in England, they said they could fix it, the didn't even open it as discovered by the guys who fixed it and is necessary to use jtag.
Fonefunshop said eMMC chip was bad, which is not true, but that led me to search for someone to replace the chip. I found A2Z cellular in Ottawa, Canada. They got the phone to boot up, but IMMEI was null( I did this trying to flash back to stock after TWRP screwed up). They rewrote original IMEI , now phone works like new. These guys are amazing.
http://a2zcellular.com/

Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30

A_Bad_Marksman said:
Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30
Click to expand...
Click to collapse
I have been through that situation man.... So always ready to help, ??

Hi pros
I'm in kind of a similar situation....I think I flashed MY 950U PIE with wrong BL
This phone is dead....Doesn't boot...no download mode....No recovery mode....
When connected to pc....device manager Recognises device as QUALCOMM HS USB 9008
Any way to brig it back to life...?

Your phone is connected in edl download mod. It will accept special files which will allow it to boot to download mode and let you flash stock firmware
The tool used for this is emmcdl.exe
It has to come with phone specific files
No idea where to get it. Ask people here, those who root phones. They know.