Last night, whilst trying to flash all the phones in our house with their respective Nexus factory images, I inadvertently ended up running the flash-all.bat for a Nexus 5 (hammerhead) onto a Nexus 5X (bullhead) by mistake. It got as far as flashing the radio and bootloader, and rebooted the phone.
And now the phone won't turn on at all.
Can't get into fastboot mode with key combination (I'm assuming because the bootloader for the Nexus 5 was flashed mistakenly).
When plugged into a computer, it shows up in Windows Device Manager as QHSUSB_BULK.
ADB and FASTBOOT won't see the phone at all.
Can anyone help? I've tried looking online for this but the only hits I'm getting are specifically for other phones, not the Nexus 5X. A lot of the steps to resolve seem to be extremely specific to those phones (i.e. - there's a thread here about the Nexus 5 but the restore file is only for the Nexus 5).
oscillik said:
Last night, whilst trying to flash all the phones in our house with their respective Nexus factory images, I inadvertently ended up running the flash-all.bat for a Nexus 5 (hammerhead) onto a Nexus 5X (bullhead) by mistake. It got as far as flashing the radio and bootloader, and rebooted the phone.
And now the phone won't turn on at all.
Can't get into fastboot mode with key combination (I'm assuming because the bootloader for the Nexus 5 was flashed mistakenly).
When plugged into a computer, it shows up in Windows Device Manager as QHSUSB_BULK.
ADB and FASTBOOT won't see the phone at all.
Can anyone help? I've tried looking online for this but the only hits I'm getting are specifically for other phones, not the Nexus 5X. A lot of the steps to resolve seem to be extremely specific to those phones (i.e. - there's a thread here about the Nexus 5 but the restore file is only for the Nexus 5).
Click to expand...
Click to collapse
Well, that happens when you flashed the wrong bootloader image.
I remember reading about there being multiple modes with QHSUSB_BULK? Some seems to require images signed with keys from Qualcomm...
Can you take a screenshot in Windows device manager? Also try getting the USB VID and PID if possible?
alvinhochun said:
Well, that happens when you flashed the wrong bootloader image.
I remember reading about there being multiple modes with QHSUSB_BULK? Some seems to require images signed with keys from Qualcomm...
Can you take a screenshot in Windows device manager? Also try getting the USB VID and PID if possible?
Click to expand...
Click to collapse
Yeah, this is likely going to be an expensive lesson in making sure I don't have multiple factory image folders sitting on my drive, ready for flashing onto the various Nexus phones I have to 'administer' for my family and friends!
From what I've been able to gather, I had already come to the conclusion that it may be salvageable, providing I can get access to the appropriate partition image files from Qualcomm and the appropriate tool to flash it, and instructions! I've seen as much for the Nexus 5, but nothing for the Nexus 5X.
I can try and get some screenshots later tonight, and even boot up a Linux box to get some more info.
Perhaps there is an easier way...
There should be a "backup" bootloader partition (in fact, I just checked my 5X and there is one).
Perhaps try holding all buttons to get it to use the backup bootloader? But first you need to get out of the QHSUSB_BULK mode.
Reference thread for N5: http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
And then if you managed to boot the backup bootloader you should be able to just use fastboot to flash the bootloader again.
Edit: Now that I think about it, it may be bricked on even earlier boot stages since I think the bootloader image contains them as well. Probably still worth a try but I guess your chances are pretty low...
alvinhochun said:
Perhaps there is an easier way...
There should be a "backup" bootloader partition (in fact, I just checked my 5X and there is one).
Perhaps try holding all buttons to get it to use the backup bootloader? But first you need to get out of the QHSUSB_BULK mode.
Reference thread for N5: http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
And then if you managed to boot the backup bootloader you should be able to just use fastboot to flash the bootloader again.
Edit: Now that I think about it, it may be bricked on even earlier boot stages since I think the bootloader image contains them as well. Probably still worth a try but I guess your chances are pretty low...
Click to expand...
Click to collapse
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
oscillik said:
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
Click to expand...
Click to collapse
What if you hold the power button for a few seconds? Like more than 10 seconds? I think it should reboot the phone.
alvinhochun said:
What if you hold the power button for a few seconds? Like more than 10 seconds? I think it should reboot the phone.
Click to expand...
Click to collapse
If it reboots the phone, I'm not getting any feedback from the device whatsoever of that happening. Nothing appears on the screen, no vibration, no sound. Even if I do that while it's plugged into the computer, I don't get the Windows 'disconnect / reconnect' USB device sound (if you get what I mean?) to denote that a device has been unplugged/replugged back in - which is what I would expect to happen if I power cycled the phone whilst it's connected to the computer.
Hi,
I am dealing with the EXACT same situation. Did you find any solution to this? I wanted to sell my 5X in order to purchase 6P and when the buyer came I wanted to un-root the phone and write back the original recovery image. Anyway, I ended writing the bootloader also, but from my wife's Nexus 5 (hammerhead) and not from 5X
Same problem. Tried a lot of qualcomm tools and the lg flash tool with tot file. Doesnt work.
bricked
Hey brother, I am sorry to say you are screwed. I just did the same thing to my phone two weeks ago. It seems without the bootloader the phone will not react at all and yes the flash-all script flashs bootloader first then restarts but once the nexus 5 bootlader is flashed the phone cant start the bootloader.
here is my thread i started with some responses but its all bad news
http://forum.xda-developers.com/nexus-5x/help/hard-bricked-phone-t3278033
There is a plus side for you that is not for me. I have called google and was 100% honest with them as to what happend. They told me they would not warranty me out a new phone since its my fault. However they did say because it is a software issue LG should be able to fix the issue. I already started the RMA process and my phone should be arrivng at LG on monday (two days from now) so hopefully they cover it under warranty or charge me something small to just flash the proper bootloader.
I will report back to my orignal thread and this one for others as I am betting as time passes a lot of original nexus 5 owners who upgrade and are used to flashing a lot will also make the same careless mistake.
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
That's great news! I wonder if the repairing was done by changing the motherboard or they've been able to re-write the eMMC chip. Anyway, take good care of it
P.S. Did you told them that you wrongfully wrote the firmware from another phone or they didn't asked? I wonder if this could be considered that you void your warranty or not.
anjelika said:
That's great news! I wonder if the repairing was done by changing the motherboard or they've been able to re-write the eMMC chip. Anyway, take good care of it
P.S. Did you told them that you wrongfully wrote the firmware from another phone or they didn't asked? I wonder if this could be considered that you void your warranty or not.
Click to expand...
Click to collapse
They told the truth and everything worked in their favor: http://forum.xda-developers.com/showthread.php?t=3278033
Sent from my Nexus 5X using Tapatalk
the bulk mode is the qhusb 9008 mode. With the right files a unbrick is possible. Unbricked my G3 also from 9008 last week.
But the prob is to get the right files.
I get the files for the flex2. So iam try if i could rewrite those files.
I dont want to send it to lg, its funny so solve it with my own hands -
konsolen said:
the bulk mode is the qhusb 9008 mode. With the right files a unbrick is possible. Unbricked my G3 also from 9008 last week.
But the prob is to get the right files.
I get the files for the flex2. So iam try if i could rewrite those files.
I dont want to send it to lg, its funny so solve it with my own hands -
Click to expand...
Click to collapse
pardon me , did you have solve it ? my 5x have this problem for a week , i can't find the file , what i find is boardiag (N5) and blank flash (n6)
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
konsolen said:
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
Click to expand...
Click to collapse
thanks for reply , it's so hard to find OTG with C type in indonesia and LG in here must to check it not sure they can fix it .
Did some tested if this method works for N5x?
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
konsolen said:
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
Click to expand...
Click to collapse
Hi I have this issue on my H791. I do have a USB C OTG cable. Are you saying you were able to point the LG Tool to the file on the SD card through the OTG cable/PC, then flash? Can you elaborate or point me to the thread in reference? I backed up my EFS partition before all this happened, so my IMEI is still intact on a backup. Thanks.
oscillik said:
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
Click to expand...
Click to collapse
I found a way off QHSUSB_BULK that worked for me--with rubber bands. To invoke either boot loader when stuck like this I needed to drain the battery completely, and I figured that would take a very long time without the screen even turning on.
I noticed that if I held in any of the volume keys + power while connected to my PC that the phone was in reality rebooting every 30 seconds--it would come and go from Device Manager. So I grabbed three rubber bands and wrapped them around the phone at each of the 3 buttons and pressed them in.
After a few hours the phone was completely dead and I could power it back on with a brief charge. Into the bootloader it went and I'm back in business.
Related
hi
i hard bricked my lg 930
how ?
i followed this step
http://www.androidauthority.com/lg-nitro-hd-clockworkmod-cwm-recovery-48447/
(do not follow)
i tried install ClockworkMod (CWM) since i installed the koereean rom and (no wi-fi to install tru rom manager)
is anything i can do for my phone like i'm not able to go in download mode, i can't see anything on screen. black
while i connect the usb cable i can hear a sound like connecting to computer
thanks a lot
We would need some more information to know if your phone is truly bricked.
does your device show up via ADB?
does it show up with B2CAppSetup program?
have you followed the unbricking solution?
http://forum.xda-developers.com/showthread.php?t=1597488
an important part of getting the phone into download mode is unplugging the usb at the right time during a hard reboot with the volume up held.
hope any of this helps but hopefully we will hear back with more info.
Maverick.Marq said:
We would need some more information to know if your phone is truly bricked.
does your device show up via ADB?
does it show up with B2CAppSetup program?
have you followed the unbricking solution?
http://forum.xda-developers.com/showthread.php?t=1597488
an important part of getting the phone into download mode is unplugging the usb at the right time during a hard reboot with the volume up held.
hope any of this helps but hopefully we will hear back with more info.
Click to expand...
Click to collapse
first of all thanks for response
no, it doesn't show up in adb (use command adb devices)
i can hear only the sound from computer (exactly like you connect true usb cable) but nothing on screen
yes, i tried the steps but ask to connect the phone, no usb connecting
@Maverick.Marq,
No, we don't really need more info to know his phone is hosed. Basically he has flashed a supposed CWM image on top of one of the bootloader partitions instead of the recovery partition. Everyone should contact these guys and tell them their guide is horribly, horribly wrong. They never responded to my email...but maybe if more people contact them about it, they'll remove their stupid guide.
Sent from my LG-P930 using Tapatalk 2
Malnilion said:
@Maverick.Marq,
No, we don't really need more info to know his phone is hosed. Basically he has flashed a supposed CWM image on top of one of the bootloader partitions instead of the recovery partition. Everyone should contact these guys and tell them their guide is horribly, horribly wrong. They never responded to my email...but maybe if more people contact them about it, they'll remove their stupid guide.
Sent from my LG-P930 using Tapatalk 2
Click to expand...
Click to collapse
thanks
anything i can do for my phone?
some update
some update
i have 2 computers
to the first one i never installed phone drivers other then lg drivers
1- in device manager with the phone conected (without or with battery) it's show "QHSUSB_DLOAD" with exclamation , see attachment
error 2 device manager lg p930 nitro.jpg
error device manager driver lg p930.jpg
2 - in USBVIEW20.exe when i open (phone still conected) i have this error (see attachment "error in usb view.jpg" and "usb view qualcomn.jpg")
some udate 2
in second computer i had many phone drivers like sony xperia play, htc evo 3d or htc desire
it's show zeus flash device with exclamation and now QHSUSB_DLOAD like the other computer - see " error desktop device manager zeus flash device"
i made 2 posts because i can't upload more then 4 images
i think to force to take driver for QHSUSB_DLOAD but how can i do that because i tried with propietes, update driver and don't want to take " android_winusb.inf" from lg drivers
i found in adb/adroid-sdk/extras/google a file android_winusb.inf and i have 3 choises (of course, i try to force to take the drivers,)
sorry for my english
if is some developer i can give access to my computer by remote
any ideas
thanks
update
i tried to burn the recovery image with nero and i have a error size
maybe this was the problem, the recovery image was incomplete?
nickmatine said:
i tried to burn the recovery image with nero and i have a error size
maybe this was the problem, the recovery image was incomplete?
Click to expand...
Click to collapse
LOL, I have no idea why you're trying to use Nero, but yes you are correct -- recovery images should be 16MB (16777216 bytes).
That's not the issue though. The issue is that you flashed something to the mmcblk0p6 partition, which is bad.
drumist said:
LOL, I have no idea why you're trying to use Nero, but yes you are correct -- recovery images should be 16MB (16777216 bytes).
That's not the issue though. The issue is that you flashed something to the mmcblk0p6 partition, which is bad.
Click to expand...
Click to collapse
i used nero just to see if is some error
mmcblk0p6 partition it's the bootloader partition?
Hi
Hi Nickmatine,
Could you please confirm if your phone (LG P930) got unbricked?
Regards
@allians2002,
Unless he sent it in to be hardware-flashed, it's probably pretty much hosed.
I think I have the same problem
http://forum.xda-developers.com/showthread.php?t=1569514
There is nothing you can do. I will sell mine, or if someone need a new screen or something, just so damn unlucky...
allians2002 said:
Hi Nickmatine,
Could you please confirm if your phone (LG P930) got unbricked?
Regards
Click to expand...
Click to collapse
not yet, but not abandoned the project
i think know where to solder wires to hard flash but it's a very small connector. Maybe 7-8 hours just to solder the wires. If someone know where can i buy the cable for this connector i can help you and other people
nickmatine said:
not yet, but not abandoned the project
i think know where to solder wires to hard flash but it's a very small connector. Maybe 7-8 hours just to solder the wires. If someone know where can i buy the cable for this connector i can help you and other people
Click to expand...
Click to collapse
i also have exactly the same problem. after unbricking . and coming to korean firmware i tried putting at&t firmware images and in the last step. it gave me an error "less in memory " for system.img.
the battery was at 2% when i did that. since then the screen wont light up.
i am trying to see if i can charge the battery with an external charger and then put back to phone and try if it boots.. i am pretty sad about it ..
i'll buy a jtag box next week and i'll let you know
or maybe someone know without jtag like this for optimus p930
http://forum.xda-developers.com/showthread.php?p=25501047
nickmatine said:
i'll buy a jtag box next week and i'll let you know
or maybe someone know without jtag like this for optimus p930
http://forum.xda-developers.com/showthread.php?p=25501047
Click to expand...
Click to collapse
i have given my phone for repair to nearby mobile repair shop. i have a very little hope from them .. which means its bricked
hem.acharya said:
i have given my phone for repair to nearby mobile repair shop. i have a very little hope from them .. which means its bricked
Click to expand...
Click to collapse
please tell as what happened
I'll let you next week after buy medusa box
finally, i bought the medusa box but i messed up my motherboard. Why?
In the schematic diagram for Jtag they give me the wrong pins (in mirror). Beacuse i tried many times with wrong configuration my motherboard died. After that i removed the JTAG conector and i so the wrong schematic
now,i still try to fix a lg p 930 so if anybody have a hard bricked phone for sell send a messege
Sorry for my english
SOLVED
greeting
After 6 months I'm back with feedback. I was Able to fix my LG P930 with Medusa box. Meanwhile I bought a professional microscope, Octopus Box, Z3X box and Riff box, so now i fix phones by JTAG. I managed to fix my P930 so is alive again after 6 months
Hi there! First of all I don't speak english very well.
My Galaxy Nexus hard bricked yesterday.
tl;dr no boot animation, no recovery mode, no download mode, no response from computer.
I thought it had just a low battery level, I found it turned off. So I tried to recharge it but it gave no signals, no battery icon, nothing.
After an all night long recharge I tried to turn it on, to enter in download mode or in recovery mode but nothing works. I also tried to connect it with my computer with and without battery, no response, no "OMAP" device found, no sound from Windows for plugging it in, nothing.
I found this thread here in xda, many people has been redirected to it and found their solution to the brick problem.
I tried to follow all the steps but when I plug in the phone and start the .bat file nothing happens, just stuck on "Waiting for device".
The phone is unlocked and rooted. I'm running AOKP JB-MR1 Build 2 and Franco Kernel for a month, never had problems with them, never installed other ROMs after that.
What should I do now? Should I try to do something or just bring it to a support center? The phone is still in warranty, there would be any problem because it has a non-stock ROM?
I've red about a jig to force the Odin mode, should I buy it? (I found this one)
Thanks for the help.
Have you tried booting into Odin mode
ntb81 said:
Have you tried booting into Odin mode
Click to expand...
Click to collapse
Yes, it doesn't work.
have you your warranty on it?
return it and get a new one
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Beauenheim said:
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
Click to expand...
Click to collapse
Yeah, that's why I'm not sure to send it in for warranty. So have I to try with a JTAG first?
[bman123] said:
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Click to expand...
Click to collapse
I'm not understanding that too, I don't know what happened. Suddendly it stopped working. Maybe is just a battery problem, I'll try to use another one before bringing it to the shop where I bought it.
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
---------- Post added at 06:12 AM ---------- Previous post was at 06:02 AM ----------
galiganu said:
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
Click to expand...
Click to collapse
so right after I wrote that I plugged my phone into USB of my PC without battery. when I inserted the battery it started showing me the battery sign and I could started the phone. 3 minutes later it went black again, but the trick didnt work again.
any ideas? thanks
Try This !!
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Tech.Nik said:
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Click to expand...
Click to collapse
Please could you explain a bit more how to go about this? I have a Verizon Galaxy Nexus in a somewhat similar condition. This one is recognised as an OMAP 4430 device. I downloaded OMAP Flasher, installed drivers and tried to bring it back to life but after running the batch file I get this error: Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE). Can the resistor trick work on this and if yes, how can I go about it? I am not faint-hearted; I think I can handle it if given the right instructions.
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
galiganu said:
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
Click to expand...
Click to collapse
Yeah, the faulty USB port is a very common issue.
Okay, so recently installed the 4.4.2 OTA on my completely stock nexus 7 (unrooted, bootloader still locked).
Tried connecting to my PC via bluetooth (for headset) and noticed that it wasnt working (was working on 4.4), so decided that maybe a reboot would fix the problem.
And now the tablet doesn't boot. Completely unresponsive, no charging icon etc. either. Tried holding down the power button, power and +/- vol for 20+ secs to no avail. Connecting the tablet to my laptop makes windows update search for the QHSUSB_DLOAD driver. From what I've read this is supposed to be some sort of hardbrick?
I left the tablet completely stock and haven't done any tinkering except use the Wugfresh toolkit to do a backup (which only needed USB debugging on). Also the battery was definitely 60%+ before I attempted rebooting.
Help please? This is completely out of the blue seeing as I never even unlocked the bootloader or anything?
Please help!
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
mdamaged said:
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
crash91 said:
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
Click to expand...
Click to collapse
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
mdamaged said:
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
Click to expand...
Click to collapse
I'll update this tomorrow morning, thanks for your help!
crash91 said:
I'll update this tomorrow morning, thanks for your help!
Click to expand...
Click to collapse
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
mdamaged said:
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
Click to expand...
Click to collapse
Alright so still no dice. Warranty is out of the question because I bought an imported version off eBay before it was officially available on Google play here in India.
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
crash91 said:
(...)
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
Click to expand...
Click to collapse
Yeah, I don't know much about that either, sorry, I'm not going to be much help there.
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
crash91 said:
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
Click to expand...
Click to collapse
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
malikmoreni said:
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
Click to expand...
Click to collapse
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
crash91 said:
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
Click to expand...
Click to collapse
Try using the Qualcomm product support Tool google "QPST" for download links
malikmoreni said:
Try using the Qualcomm product support Tool google "QPST" for download links
Click to expand...
Click to collapse
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
crash91 said:
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
Click to expand...
Click to collapse
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
Click to expand...
Click to collapse
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
Click to expand...
Click to collapse
That's exactly the thing, it doesnt get into fastboot mode or anything, I assume you need a working bootloader to be able to boot fastboot? If it was in fastboot I would have attempted this already.
Anyway the seller says that the item is covered under a 1 year international warranty, thats my only chance now I guess....
The thing that concerns me is that I was completely stock, locked bootloader and unrooted. Only installed the official OTA updates (no sideloading either).
For those who are interested - I finally had time to drop by the service centre. They replaced the battery and motherboard (it was under warranty). I was expecting them to do some magic with QPST or something though.
The same has just happened to me, but I'm out of luck, the warranty has expired.
Did anyone have managed to fix it with the QPST drivers?
thanks.
Fyi, http://www.androidpolice.com/2015/0...rate-not-likely-a-result-of-firmware-updates/
Hi, today i installed android 6.0 on my g3 d855 then rooted it and i tried to flash recovery with AutoRec from google play, but unfortunately it was only for 5.0 so i rebooted phone and it.. just didn't wake up. Now my phone is showing lg logo sometimes. I can't get into download mode and my pc can't even see my g3. When i plug my phone with battery in it pc doesn't see phone but when i take out the baterry in devices manager i see " unknown usb device (device descriptor request failed) " . What the heck am i supposed to do? Searching for the solution for 8hrs and still nothing.
HELP ME PLEASE...
PS. sorry for my bad english
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Try entering download mode(it probably wont show anything on screen) and flash kdz or tot
TheMadScientist420 said:
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Click to expand...
Click to collapse
i did it but i am stuck on board diag thing. when i connect cable to pc and click START i get "device was not found in dload trying flash programmer"
Does it show up in device manager as qusb bulk mode qloader 9008 or any thing
TheMadScientist420 said:
Does it show up in device manager as qusb bulk mode qloader 9008 or any thing
Click to expand...
Click to collapse
ok i somehow made it, flashed all imgs in board diag but my phone still cant get into download mode, phone should reboot but it doesnt
EDIT: I made it. I've been doing so many mistakes. admin can now close the thread. thanks @TheMadScientist420 !
dombro22 said:
ok i somehow made it, flashed all imgs in board diag but my phone still cant get into download mode, phone should reboot but it doesnt
EDIT: I made it. I've been doing so many mistakes. admin can now close the thread. thanks @TheMadScientist420 !
Click to expand...
Click to collapse
Help. I have the same problem.
Gollow the guide. Or are u stuck in steps
Did same thing lal, funk me, im idiot, but, mine is not showing lg screen never, can you tell me exactly what you did?
Im not good at english, can someone explain me what ´´ short the pins ´´ means?
Di4N said:
Did same thing lal, funk me, im idiot, but, mine is not showing lg screen never, can you tell me exactly what you did?
Im not good at english, can someone explain me what ´´ short the pins ´´ means?
Click to expand...
Click to collapse
take a small metal wire, and touch with him in the 2 red dots at the same time (connect between them using something made of metal)
omer323 said:
take a small metal wire, and touch with him in the 2 red dots at the same time (connect between them using something made of metal)
Click to expand...
Click to collapse
Which dots you mean? these?
imgur.com/qwMjdtX.png (with blue)
There are any pins at GND that i need to connect with or is just an pin? ( I did not opened the phone for now, im considering to send it to warranty, since phone have 1 year and 9 months of warranty... i mean, i bought it in november, you think they will repair it? Or will send it back as it is? if i open it i lose the warranty so..
And one more thing, where can i get the tot of marshmallow? Or which one you used? In the main post it says ´´ The tot file of the rom that you were running. (not older not newer same version) ´´
Di4N said:
Which dots you mean? these?
imgur.com/qwMjdtX.png (with blue)
There are any pins at GND that i need to connect with or is just an pin? ( I did not opened the phone for now, im considering to send it to warranty, since phone have 1 year and 9 months of warranty... i mean, i bought it in november, you think they will repair it? Or will send it back as it is? if i open it i lose the warranty so..
And one more thing, where can i get the tot of marshmallow? Or which one you used? In the main post it says ´´ The tot file of the rom that you were running. (not older not newer same version) ´´
Click to expand...
Click to collapse
a. yes, this exact blue points
b. just those 2 pins! connect between them, and while they are connected, connect the USB. (you'll probably need a 2nd person help to that, unless you are very skilled with your hands)
c. i don't think any repair store will get to that level, but i don't know the level of support at your country... also, the process is pretty simple, took me about 2 hours of work to get my phone from really hard brick to fully functional rooted CM device
d. i don't know about MM tots... i would suggest using this guide: http://open-freax.fr/guide-unbrick-your-lg-g3/ it worked for me and many others for sure! it provides you all the files you need. just make sure you have efs backup or at least know your IMEI number (which suppose to be on a sticker under your battery)
Also try another cable, 2 months ago I tried it, was sure I did everything correct but nothing...changed cable and boom
Poslano sa mog LG-H815 koristeći Tapatalk
omer323 said:
a. yes, this exact blue points
b. just those 2 pins! connect between them, and while they are connected, connect the USB. (you'll probably need a 2nd person help to that, unless you are very skilled with your hands)
c. i don't think any repair store will get to that level, but i don't know the level of support at your country... also, the process is pretty simple, took me about 2 hours of work to get my phone from really hard brick to fully functional rooted CM device
d. i don't know about MM tots... i would suggest using this guide: http://open-freax.fr/guide-unbrick-your-lg-g3/ it worked for me and many others for sure! it provides you all the files you need. just make sure you have efs backup or at least know your IMEI number (which suppose to be on a sticker under your battery)
Click to expand...
Click to collapse
I have the IMEI on the phone box, i don t have any EFS backup, but i don´t think i can do it.
Wait, found something in my SDCard, i remember i did it time ago, this is the backup?
imgur.com/dgR1BBq
Di4N said:
I have the IMEI on the phone box, i don t have any EFS backup, but i don´t think i can do it.
Wait, found something in my SDCard, i remember i did it time ago, this is the backup?
imgur.com/dgR1BBq
Click to expand...
Click to collapse
yep. this suppose to be the backup i was talking about!
but if you have your IMEI number so everything is good anyway,
you can go ahead with this guide: http://open-freax.fr/guide-unbrick-your-lg-g3/
i'm sure you can do it, just read it carefully before you begin and do exactly as it sais
I actually grounded at a common ground point the main pin is the upper pin if im not mistaken but i did ground to the frame makes it a hell of a lot easier and i used anlong piece of small gauge speaker wire frayed back with about 4 or 5 strands of copper and if i. Not mistaken u must use firmware tot that u were on before brick
I´ve soldered an "connector" to fix a side at ground and the other side a needle to exactly point the pin. "Connector"
And here´s the pin which must be pinned: Here is the Pin
And if you are opening your G3, just a few screws more and you can fix your temparatures: Tutorial with Video
I also reccomend the thermal mod i record at least 10 to 15 degree cooler temps your rite there any ways
Hi there, I'm in a similar situation: I shorted that pin with GND and tried to flash through BoardDiag (I followed this guide). That's a problem. Before I had this issue, I had a fully working stock KitKat (I flashed the tot with LG Flash Tool) but I made some mistakes and tried to wipe through TWRP and to install other ROM (here's my thread). My phone died. I just think that the problem is with the TOT I am trying to flash with BoardDiag.
My D855 is currently with black screen and no led blinking (only QDLoader 9008 mode).
Any help? Thanks and happy New Year.
Try my guide here http://forum.xda-developers.com/lg-g3/general/guide-boot-recovery-download-mode-t3273824
Hi guys, this might sound really really stupid but i wanted to flash my phone back to stock and i accidentally flashed in the nexus 5 file instead of the 5x ones and now i cant enter recovery mode. Windows cant seem to detect the phone either (USB device not recognized).
Anyway around this? Thank you
fireymint said:
Hi guys, this might sound really really stupid but i wanted to flash my phone back to stock and i accidentally flashed in the nexus 5 file instead of the 5x ones and now i cant enter recovery mode. Windows cant seem to detect the phone either (USB device not recognized).
Anyway around this? Thank you
Click to expand...
Click to collapse
This should work for you. If it does, post back here and in that thread.
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Check device manager. A lot of times I would have to manually point my computer to install the driver.
PiousInquisitor said:
This should work for you. If it does, post back here and in that thread.
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Click to expand...
Click to collapse
It does not work.
I did exactly the same thing with fireymint. The N5X never boot and is always black screen since the bootloader is bad. But PC can recognize it as QHSUSB_BULK and drive it as Qualcomm HS-USB QDLoader 9008. I believe some tools can flash correct bootloader in that mode.
Till now, this post http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 provides a solution to the most similar situation of Nexus 5. But it is not for Nexus 5x. Perhaps, the only thing we can do is cross fingers and waiting for some guru who can provide rightful tools.
fireymint said:
Hi guys, this might sound really really stupid but i wanted to flash my phone back to stock and i accidentally flashed in the nexus 5 file instead of the 5x ones and now i cant enter recovery mode. Windows cant seem to detect the phone either (USB device not recognized).
Anyway around this? Thank you
Click to expand...
Click to collapse
What happens when you hold the power+vol up+vol down keys down simultaneously for a few secs? Are you able to get into fastboot mode at all?
If not, as others stated above, the bootloader is corrupt. You could try to change your USB driver and use the LGUP tool mentioned in thread links above - but those processes are proprietary and not well documented (and may still be dependent on a functional bootloader). At the end of the day, it's probably worth contacting LG or Google support and asking if they can repair/reflash the device. This might be covered under warranty, and if not, they may only charge a small fee for the service. The frustration it would save you in trying to bring a "hard" bricked device back to life is substantial.
fireymint said:
Hi guys, this might sound really really stupid but i wanted to flash my phone back to stock and i accidentally flashed in the nexus 5 file instead of the 5x ones and now i cant enter recovery mode. Windows cant seem to detect the phone either (USB device not recognized).
Anyway around this? Thank you
Click to expand...
Click to collapse
Same problem.
Now can you fix.
I believe your phone should be able to load "Download Mode" with a bad bootloader, but I have no way to try that. Download mode is when you hold Vol Up + Power. Then you should be using the tools from second post.
Also there I see, that they only have files for a 32GB model, if yours is 16GB, the guide will not work! I am waiting for my USB A -> C cable to arrive, after that I think I may be able to provide the files they need to compile the files you will need for a 16 GB Nexus 5X. Other that that, you can always send it in for warranty. If nothing works for you, nothing will work for them, so they just might replace it.