Hello guys,
A few minutes ago I bricked my Nexus 4 by inserting an incorrect terminal command found in this thread from another device. http://forum.xda-developers.com/showthread.php?t=1333782
My Nexus 4 did not turn on anymore after I rebooted and whenever I try to power it on by holding on the PWR button when plugged in (via charger or computer) it shows a red LED of death for 4 seconds and goes away, while the screen stays black. I do not know what to do, can anyone please help? I have tried reading other threads but to no avail.
EDIT1: My PC displays the QHSUSB_DLOAD message when plugged
EDIT2: I got it to display Qualcomm HS-USB QDLoader 9008 (COM4). [I assume it has to do with the Qualcomm High Speed USB Driver]
you wanted to get into recovery? with a terminal emulator? su(press enter) reboot recovery(press enter) didnt work?
simms22 said:
you wanted to get into recovery? with a terminal emulator? su(press enter) reboot recovery(press enter) didnt work?
Click to expand...
Click to collapse
I was being naive and I blindly followed the command. Very foolish of me.
can you get into your recovery? can you get into the bootloader? i see you were messing with partitions, which differ on every device. if you can get into your bootloader, you can try to flash the whole system image.
simms22 said:
can you get into your recovery? can you get into the bootloader? i see you were messing with partitions, which differ on every device. if you can get into your bootloader, you can try to flash the whole system image.
Click to expand...
Click to collapse
Nope, I can't even get into recovery OR bootloader. Power button does nothing except show a red light LED for a few seconds, then goes away while screen stays black.
fakudolan said:
Nope, I can't even get into recovery OR bootloader. Power button does nothing except show a red light LED for a few seconds, then goes away while screen stays black.
Click to expand...
Click to collapse
oh, that's not good.
id look look for any tool that lg provides for flashing, if they provide something. or, id start the rma process. you can always try the fixes posted for tbe red light of death, but only the tiniest chance that it would help.
simms22 said:
oh, that's not good.
id look look for any tool that lg provides for flashing, if they provide something. or, id start the rma process. you can always try the fixes posted for tbe red light of death, but only the tiniest chance that it would help.
Click to expand...
Click to collapse
Why RMA? This isn't Google or LG's fault. Pure user error.
Sent from my iPad 4
mitchdickson said:
Why RMA? This isn't Google or LG's fault. Pure user error.
Sent from my iPad 4
Click to expand...
Click to collapse
truth.
mmcblk0p3 on the N4 is SBL2, ie one of the bootloader pieces.
Are you sure you cant get into fastboot? If you actually were able to you could reflash the bootloader and that would restore SBL2, if you cant then you're SOL.
You might still be able to fix it with QPST or something as that sounds like the mode it's booting into, though I dont actually know anything about QPST.
I agree that its a user fault, but everyone RMAs devices like this. Plus its not that hard for Google to flash stock images on them
Sent from my Nexus 4 using xda app-developers app
TheManii said:
mmcblk0p3 on the N4 is SBL2, ie one of the bootloader pieces.
Are you sure you cant get into fastboot? If you actually were able to you could reflash the bootloader and that would restore SBL2, if you cant then you're SOL.
You might still be able to fix it with QPST or something as that sounds like the mode it's booting into, though I dont actually know anything about QPST.
Click to expand...
Click to collapse
I probably could, but I have no idea what or how to use QPST.
I think I found out how to use QPST, it says COM4 Phone is in Download mode, and it asks for a Phone Image and Boot image.
Can anyone tell me what is a Phone Image?
EDIT: Nevermind, QPST is asking for .hex files...
There exists an 8960_msimage.mbn file which is what QPST is asking for under the Factory Image tab in QPST Software Download. Should I use that?
Status
Hey, can you report back whether you could fix your phone or not? I'm in the very same situation as you are right now.
Thanks
darkware said:
Hey, can you report back whether you could fix your phone or not? I'm in the very same situation as you are right now.
Thanks
Click to expand...
Click to collapse
Have you tried Gigadroid's unbrick method at http://forum.xda-developers.com/showthread.php?t=2347060?
fakudolan said:
My Nexus 4 did not turn on anymore after I rebooted and whenever I try to power it on by holding on the PWR button when plugged in (via charger or computer) it shows a red LED of death for 4 seconds and goes away, while the screen stays black. I do not know what to do, can anyone please help? I have tried reading other threads but to no avail.
EDIT1: My PC displays the QHSUSB_DLOAD message when plugged
EDIT2: I got it to display Qualcomm HS-USB QDLoader 9008 (COM4). [I assume it has to do with the Qualcomm High Speed USB Driver]
Click to expand...
Click to collapse
This happened to my first N4 without me doing anything.
Also had QHSUSB_DLOAD couldn't find any method to recover it I'm afraid.
It's under a year old so try for an RMA, I probably wouldn't suggest that you mention how it happened
aanonymoushuman said:
I agree that its a user fault, but everyone RMAs devices like this. Plus its not that hard for Google to flash stock images on them
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
People like you are the reason cell phone prices go up. A huge problem with today's society....no one takes responsibility for their own mistakes. Can't pay your mortgage? Have government refinance your house. Don't like to work? Just collect welfare and stay home. Brick your nexus for doing something stupid? Just make Google pay for it. I swear you people make me sick.
Sent from my Nexus 4 using Tapatalk 4 Beta
Related
I flash a wrong kernel (A Nexus 7 kernel), and my nexus4 become brick. No matter what I did, it still no response. I can't boot to fastboot, even i can't turn it on. Please help....
connect to PC, only show a QHSUSB_DLOAD in Device Manager. But still can't turn it on. Please help, anything i can do to fix it??
Read through the ENTIRE other thread you posted in, all the info is there.
No idea how you accidently flash wrong a kernel for the wrong device.
Get into bootloader mode. (can you? Google on how to do it manually)
Or
Plug the phone in via usb if you had adb used on it and type adb reboot bootloader (hence if use toolkit you won't have this set up.)
Sent from my Nexus 4 using xda premium
These guys are way to eager to flash any and everything on there devices
yyz71 said:
These guys are way to eager to flash any and everything on there devices
Click to expand...
Click to collapse
It just seems impossible on finding kernel for other phones on a nexus 4 forum.
Oh what's this? A link to a flash able zip? Let's flash it without thinking.
Think before you flash op.... And dont use toolkits.
Sent from my Nexus 4 using xda premium
zephiK said:
It just seems impossible on finding kernel for other phones on a nexus 4 forum.
Oh what's this? A link to a flash able zip? Let's flash it without thinking.
Think before you flash op.... And dont use toolkits.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
So true:good:
I can't connect PC with adb. I connect PC can't show the charge icon in my phone. And PC can only identify the device as QHSUSB_DLOAD.
So, what can i do..?
yatyuk said:
I can't connect PC with adb. I connect PC can't show the charge icon in my phone. And PC can only identify the device as QHSUSB_DLOAD.
So, what can i do..?
Click to expand...
Click to collapse
Send that puppy back, & get a new one...
Sent from my HTC One X using xda premium
rayford85 said:
Send that puppy back, & get a new one...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I really dislike people recommending to send the phone back (RMA) to Google for a user's own (I'll be polite here) lack of awareness and understanding of what they are doing. This person should continue to look for solutions to get it working and if not.. well, to bad. Lesson learnt. Buy another Nexus 4.
Besides that fastboot should still be accessible. If OP can eventually get into fastboot then all will be well.
Go read read FAQ thread,will show yo proper way to get back to bootloader mood don't be lazy that won't help,agree getting to bootloader mode then fastboot proper n4 kernel.try it on other pc I'd you cannot in this pc,make sure you install the driver.
Read before you ask
Sent from my HTC One X using xda app-developers app
Zackconsole said:
Go read read FAQ thread,will show yo proper way to get back to bootloader mood don't be lazy that won't help,agree getting to bootloader mode then fastboot proper n4 kernel.try it on other pc I'd you cannot in this pc,make sure you install the driver.
Read before you ask
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Bro, i already read some thread... but still not work...i try any combine key with connection to PC, and only red LED appeared few sec and then off again. I think i had driver, because i can use toolkit, unlock and root via adb before. Or can u please give me the link which i need to read? I search about the "qhsusb_dload" problem. Some tell me can easy to fix it by using power+ Vol+/- with connection to PC. But i try many times, still not work... I know i can fix it, if i can enter bootloader. But now i can't turn my phone on.... any suggestion? Thank you.
yatyuk said:
Bro, i already read some thread... but still not work...i try any combine key with connection to PC, and only red LED appeared few sec and then off again. I think i had driver, because i can use toolkit, unlock and root via adb before. Or can u please give me the link which i need to read? I search about the "qhsusb_dload" problem. Some tell me can easy to fix it by using power+ Vol+/- with connection to PC. But i try many times, still not work... I know i can fix it, if i can enter bootloader. But now i can't turn my phone on.... any suggestion? Thank you.
Click to expand...
Click to collapse
Its actually appalling the lack of support users get on here, instead being on point and helping the man out all they get is criticized.
Anyways Back to topic: yatyuk your device isn't bricked it still has life. I had the exact same issue before when connecting to the PC I was also getting the "qhsusb_dload" driver alert.
Click on the Link and Follow the steps if you can get into Fastboot Mode. Check the Post #241 of mine.
LINK
Happy Recovery!
risktaker84 said:
Its actually appalling the lack of support users get on here, instead being on point and helping the man out all they get is criticized.
Anyways Back to topic: yatyuk your device isn't bricked it still has life. I had the exact same issue before when connecting to the PC I was also getting the "qhsusb_dload" driver alert.
Click on the Link and Follow the steps if you can get into Fastboot Mode. Check the Post #241 of mine.
LINK
Happy Recovery!
Click to expand...
Click to collapse
I read your post already bro!! Thanks for your help. But, i don't understand #241. How can I get into fastboot mode?
Is the first step "1) Once in Fastboot mode, through Nexus 4 Toolkit I flashed the Clock Work Recovery. " ?
Now I connect my phone to PC, then Power + Vol- for ~10sec, my phone will had red led for few second and then off again.
risktaker84 said:
Its actually appalling the lack of support users get on here, instead being on point and helping the man out all they get is criticized.
Anyways Back to topic: yatyuk your device isn't bricked it still has life. I had the exact same issue before when connecting to the PC I was also getting the "qhsusb_dload" driver alert.
Click on the Link and Follow the steps if you can get into Fastboot Mode. Check the Post #241 of mine.
LINK
Happy Recovery!
Click to expand...
Click to collapse
Bro, can you please teach me how to enter fastboot mode? I try using all combine key with connection to PC, but only red led appear for few second then off.
I like how all the people who manage to do something so idiotic to these phones band together and stick up for each other. There is no possible way to flash the wrong nexus kernel. any who, the solution has been posted plenty of times. Enter recovery then fast food.
Sent from my Nexus 4 using xda premium
yatyuk said:
Bro, can you please teach me how to enter fastboot mode? I try using all combine key with connection to PC, but only red led appear for few second then off.
Click to expand...
Click to collapse
To get into Fastboot:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So for all the people with Bricked devices all hope is not lost. Follow this procedure to get into Fastboot.
1) Press the Power button for more then 5 seconds to do a Hard Reset. This is where you screen is completely turned off.
2) Now take your LG manufactured USB connect it to the PC. Do not connect it to the phone just yet.
3) Holding the Vol Down and Power together and NOW connect your other end of the USB connector to the phone and then your phone should give you a slight vibration and you should see the Fastboot screen (Android lying on the back)
NOTE: Make sure as soon as you see then fastboot mode Let go of the Vol and Power Button right away!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
risktaker84 said:
To get into Fastboot:
Click to expand...
Click to collapse
I try many times.....but still can't turn on...
My situation is
1) Press the Power button for more then 5 seconds to do a Hard Reset. This is where you screen is completely turned off.
--->My phone is always turned off, when i disconnect to PC....
2) Now take your LG manufactured USB connect it to the PC. Do not connect it to the phone just yet.
--->This step is ok
3) Holding the Vol Down and Power together and NOW connect your other end of the USB connector to the phone and then your phone should give you a slight vibration and you should see the Fastboot screen (Android lying on the back)
---> when i connect the usb, the phone immediately Red LED on and no vibration. LED on few second, my phone off again and remind no response
Is that mean no hope
yatyuk, use this thread for further inquiry LINK. I don't want to go back and forth in between different threads with the same issues.
Try this,
Did you ever get a Battery sign when you had it connected to the PC or AC for power?
Try this, I don't know if its gonna work or not but plug your phone in the wall receptacle for AC Charge and leave it for a while. On AC, the phone most likely, if completely dead, will stay idle but most likely jump back to Battery sign showing its charging or not.
When that happens, leave like that for a hour or two.
Let me know what happens. Good luck.
Click to expand...
Click to collapse
Thank you for your friendly help
I had read your post already, and i will keep on trying...
I had an Asylum Custom Rom installed.
I also had TWRP as the recovery installed.
I decided to try the new COLOR ROM public beta that I got from the OPPO forums.
I went into TWRP recovery, did a full wipe and then proceeded to install the new COLOR ROM.
When I rebooted, the phone never turned on again.
Now I cannot get to fastboot, recovery, or turn on the phone at all.
I browsed through many forums and tried
1. Charging phone for 5 hours (no led light when plugged in) -> nothing
2. Holding Power button for 30 secs, (5 times to try a hard reset) -> nothing
3. Holding Down button for 10 secs -> nothing
4. Power and up volume -> nothing
5. Power and down volume -> nothing
6. Plugged into computer USB and tried all button combos -> nothing
Is my phone really bricked now?
I hope for your sake it really isn't the case. It does seem like you have tried all the usual ways of getting around the symptoms you are describing. It sounds like you had a bad download and flashed it anyway. I hope someone has some advice for you to fix your device. I am currently on Asylum and was just considering trying out the new Color ROM so i think i'll hold off until i know for sure you can resurrect your device.
when you are hooked up to USB on PC can you try ADB? does it even see the device at all?
killerskincanoe said:
I hope for your sake it really isn't the case. It does seem like you have tried all the usual ways of getting around the symptoms you are describing. It sounds like you had a bad download and flashed it anyway. I hope someone has some advice for you to fix your device. I am currently on Asylum and was just considering trying out the new Color ROM so i think i'll hold off until i know for sure you can resurrect your device.
when you are hooked up to USB on PC can you try ADB? does it even see the device at all?
Click to expand...
Click to collapse
Nothing. no response whatsoever. I've worked with many different phones before starting with the Nexus One and I've always been able to get out of a potentially bad situation because I could at least always get to fastboot or recovery, but in this case, nothing. It really is like working with a brick, hence the term "brick". Now i can really understand the meaning of the term.
such a bummer. it certainly makes me think twice about trying other ROMS now jeez
update
Just an update to this thread... I sent my Find 5 to get repaired to try and figure out what the problem was. It turned out that the battery had failed and they replaced the battery for me. Glad to say that my Find 5 is up and running again.
dtwrain said:
Just an update to this thread... I sent my Find 5 to get repaired to try and figure out what the problem was. It turned out that the battery had failed and they replaced the battery for me. Glad to say that my Find 5 is up and running again.
Click to expand...
Click to collapse
good to hear !!
I couldnt really believe that flashing a rom using recovery affects fastboot let alone button combos/charging...
btw what were the costs of replacing the battery ? or was it free of charge under warranty...
dtwrain said:
Just an update to this thread... I sent my Find 5 to get repaired to try and figure out what the problem was. It turned out that the battery had failed and they replaced the battery for me. Glad to say that my Find 5 is up and running again.
Click to expand...
Click to collapse
Glad to hear it turned out that way. Really strange situation.
Oualcomm HS-USB Diagnostics 9008
1) Can you give me some advices? Smartphone OPPO find 5 x909 is in the Oualcomm HS-USB Diagnostics 9008 port. Completely brick. What we gonna do with it ? Where i may download unbrick files and will see unbrick method? Need just rowprogram0.xml, patch0.xml, 8064_msimage.mbn, MPRG8064.hex for OPPO find5 x909 strongly.
2) How i can place other (working) smartphone in Download mode? What i gonna press?
Sorry for my english, and thank you.
olezhek1975 said:
1) Can you give me some advices? Smartphone OPPO find 5 x909 is in the Oualcomm HS-USB Diagnostics 9008 port. Completely brick. What we gonna do with it ? Where i may download unbrick files and will see unbrick method? Need just rowprogram0.xml, patch0.xml, 8064_msimage.mbn, MPRG8064.hex for OPPO find5 x909 strongly.
2) How i can place other (working) smartphone in Download mode? What i gonna press?
Sorry for my english, and thank you.
Click to expand...
Click to collapse
I suggest you to ask addel in oppo forum, she can help you just pm her and tell your problem, because she has an app like odin in samsung to totally flash new rom inage from pc like odin did. But its not officially released by oppo and its hard to find, so i suggest you to contact her
Sent from my GT-I9205 using XDA Free mobile app
Hi, this is my firt post, i'm going to quote this problem that's the same problem that I have...
"Device : Nexus 7
Problem : I was trying to unroot it and flash a 4.4.2 ROM to the device and i ended up bricking it somehow. I looked around a lot on here and youtube. I found one solution i had not tried which was to get into recovery mod. But the device was stuck on the boot loaded. So i hard shut it down, and pressed the key combination to load the boot loader. And, the screen wasn't loading. I heard the little chimes my computer makes when ever a USB device is active, so i heard the thing load into the boot loader. But its not showing on the screen!
Please help i really shouldn't have done this. But i am literally about to cry.
I tried using Wugfresh's Nexus toolkit to flash the ROM, and it would stop on sending system.
I dont know if i did something wrong, if the kernel was messed up, if the kit wasnt right, please as the video said there is 4 million members here. someone has to know what to do...
-Sean"
I did exactly the same thing that this guy did... ----> http://forum.xda-developers.com/showthread.php?t=2345874
The difference is that I don't live in USA and my Nexus doesn't have warranty... What can I do T.T my pc shows the tablet as Unknown Device and makes a sound when I puggle it, there has to be something that I can do >.<
EverAngelOn said:
Hi, this is my firt post, i'm going to quote this problem that's the same problem that I have...
"Device : Nexus 7
Problem : I was trying to unroot it and flash a 4.4.2 ROM to the device and i ended up bricking it somehow. I looked around a lot on here and youtube. I found one solution i had not tried which was to get into recovery mod. But the device was stuck on the boot loaded. So i hard shut it down, and pressed the key combination to load the boot loader. And, the screen wasn't loading. I heard the little chimes my computer makes when ever a USB device is active, so i heard the thing load into the boot loader. But its not showing on the screen!
Please help i really shouldn't have done this. But i am literally about to cry.
I tried using Wugfresh's Nexus toolkit to flash the ROM, and it would stop on sending system.
I dont know if i did something wrong, if the kernel was messed up, if the kit wasnt right, please as the video said there is 4 million members here. someone has to know what to do...
-Sean"
I did exactly the same thing that this guy did... ----> http://forum.xda-developers.com/showthread.php?t=2345874
The difference is that I don't live in USA and my Nexus doesn't have warranty... What can I do T.T my pc shows the tablet as Unknown Device and makes a sound when I puggle it, there has to be something that I can do >.<
Click to expand...
Click to collapse
Can you get into the bootloader still?
I can't
b3ltazar said:
Can you get into the bootloader still?
Click to expand...
Click to collapse
No, I can't. The screen is completely black.
Have you tried any of the suggestions in the thread you linked in the OP?
EverAngelOn said:
No, I can't. The screen is completely black.
Click to expand...
Click to collapse
Do you get a charging icon when you plug in the n7? did you try a diffrent cable?What exactly does ur computer do when you plug in the dead n7 (does it thy try to install a apx driver) Does toolkit see tablet like its in the bootloader? If so try to flash a new bootloader!
try this found in another thread
To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures
Wugs tool kit
First when you plug it in hold all three power buttons
Second
I also have used the tool kit it gets stuck all the time on the flashing system. I think its a time out error because of the complexity of extracting the image and flahing the image with out a retry or check command. Here is a fix that i have figured out. When in Wugs tool kit download the Os Version you want on your device locate the folder with the downloaded image and extract it using 7 zip. once extracted flash the remaing .img files seperatly under andvance setting menu select flash system then user data it should boot right up. if you forgot what version you flashed previously flash all img files boot bootloader system user etc. if you still have problems let me know. i can give you my email.
Click thanks if i helped
b3ltazar said:
Do you get a charging icon when you plug in the n7? did you try a diffrent cable?What exactly does ur computer do when you plug in the dead n7 (does it thy try to install a apx driver) Does toolkit see tablet like its in the bootloader? If so try to flash a new bootloader!
try this found in another thread
To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures
Click to expand...
Click to collapse
My tablet doesn't show the charging icon, I've tried with different cables, when I plug it to the laptop it makes a sound and shows an APX driver... I'm stressed and that instructions didn't work for me.
EverAngelOn said:
My tablet doesn't show the charging icon, I've tried with different cables, when I plug it to the laptop it makes a sound and shows an APX driver... I'm stressed and that instructions didn't work for me.
Click to expand...
Click to collapse
Unfortunately it sounds like you erased your bootloader and nvflash can do nothing for you unless you used the unbrickable mod before u f'ed up your tablet. Try sending it to asus for Warranty tell em you installed the ota update and it wouldn't boot up afterwards. I have read many threads about this issue with nobody being able to recover there tablet. Asus does have global warranty
I need some serious help guys. Phone is stuck at boot logo and wont turn on. IT wont enter recovery mode. it wont hard reset. It wont enter download mode.
The phone was completely stock originally. So i rooted using towelroot and ran the 'AutoREC' program. That did its thing and restarted and got stuck in fastboot mode. couldnt get out of it. Eventually managed to reflash all the original stock ROM partitions and it started to boot again... only to get stuck at the LG logo. I need some serious help.
PC wont detect the phone at all and its as if there is no OS on the phone. I have the D802 variant 32gb.
which kdz variant did you flash.
v.konvict said:
which kdz variant did you flash.
Click to expand...
Click to collapse
D80220C_00
got it from "lg-firmware-rom" after entering my imei
spookyleaf said:
D80220C_00
got it from "lg-firmware-rom" after entering my imei
Click to expand...
Click to collapse
same thing happened to a d802 of a friend of mine. but he flashed the d802h variant. will keep you posted if i find a way out.
I am in the same position. Except I tried to flashify stock recovery on d800 at&t variant. I wanted to install the stock update because I was still stock. Just root with twrp before...I had the sprint variant before the ls980 and it never screwed me over like this. I'll post if I figure anything out... I got to get ahold of shellnutt... He's the g2's god.
Dam. Leme me know what happens
Sent from my Nexus 5 using XDA Free mobile app
spookyleaf said:
Dam. Leme me know what happens
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Have you tried both ways to enter recovery?
Push PWR + Vol Down till you see the LG Logo then release and press both again
Push PWR + Vol Down till you see the LG logo then release and press and hold the volume up and volume down buttons until reset screen appears.
If you can see the LG logo I think you are not Hard Bricked
I haven't tried that exactly. I'll give it a shot when I get a chance
Sent from my Nexus 5 using XDA Free mobile app
You may want to check your internal hardware to be sure it's marked as a D802. Typically the feint white stamp in the lower center/left of the phone with rear cover removed is the true model number. It's also stamped on the board and on the ribbon cables going up eithe side. Your device is showing the signs of a false d802 which has become sadly common in recent months.
If it's legit d802 then flash aboot, boot, laf and power it off.
Then hold voume up and connect to pc while still holding volume up.
Make sure you have the drivers installed, fire up lg mobile support tool or the lg flash tool 2014 (you need your kdz file now - find it using your imei and lg-firmware site)
Okay so I found this: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404 to get it to come up as a device in Windows and Linux. And this: http://forum.xda-developers.com/showthread.php?t=2582142 I'm sure you read this but you need to do it after following the first guide. I already have a Linux installed and I'm going to try today. I'll update with a guide for you only if you need it and if I succeed. I just need to remind you. You CANNOT mess up on the second guide... Well as far I can tell. But if the first guides label is actually true then maybe I'm wrong.
ok so ive ordered some tools to open up the phone and check the internals. Hopefully its a legit G2. Meanwhile every single possible combination of the power and volume keys does absolutely nothing. If all else fails ill try shorting the capacitors as ive seen on a guide from here and hopefully that will be the end of it. Thanks for all the input guys. Ill keep you posted!
darkpower_4 said:
Okay so I found this: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404 to get it to come up as a device in Windows and Linux. And this: http://forum.xda-developers.com/showthread.php?t=2582142 I'm sure you read this but you need to do it after following the first guide. I already have a Linux installed and I'm going to try today. I'll update with a guide for you only if you need it and if I succeed. I just need to remind you. You CANNOT mess up on the second guide... Well as far I can tell. But if the first guides label is actually true then maybe I'm wrong.
Click to expand...
Click to collapse
thanks i appreciate that very much. Keep me informed on how it goes. Fingers crossed!
spookyleaf said:
ok so ive ordered some tools to open up the phone and check the internals. Hopefully its a legit G2. Meanwhile every single possible combination of the power and volume keys does absolutely nothing. If all else fails ill try shorting the capacitors as ive seen on a guide from here and hopefully that will be the end of it. Thanks for all the input guys. Ill keep you posted!
Click to expand...
Click to collapse
Plug it into a windows machine, open device manager and look for Qualcomm qhsusb_bulk. If you get that, you're already in bulk and don't need to worry about shorting capacitors. If it's not being recognized in any way, you may be forced into that as a last resort.
spookyleaf said:
ok so ive ordered some tools to open up the phone and check the internals. Hopefully its a legit G2. Meanwhile every single possible combination of the power and volume keys does absolutely nothing. If all else fails ill try shorting the capacitors as ive seen on a guide from here and hopefully that will be the end of it. Thanks for all the input guys. Ill keep you posted!
Click to expand...
Click to collapse
All you really need to open it up is a guitar pick. It pries apart make sure you take the sim card out. After that it's going to take a little swipe around the edge and it'll pop open no problem.
iowabowtech said:
Plug it into a windows machine, open device manager and look for Qualcomm qhsusb_bulk. If you get that, you're already in bulk and don't need to worry about shorting capacitors. If it's not being recognized in any way, you may be forced into that as a last resort.
Click to expand...
Click to collapse
I checked that already. Not going into bulk mode. Seems like the capacitors are my last resort
so ive poped the phone open and guess what... its not a D802.. its a D800.. the at&t version... wtf.. no wonder i bricked it. gonna see if i can use the unbrickable method
did you checked the IMEI?
nope its says on the speaker grille after you remove the back cover. "D800"
how is that possible? did phone information apps showed your device as 802 aswell? did kernel info and phone info in system settings lied too?
Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?
attempted to apply for heat some to the device then re flash ?
blackcell1 said:
attempted to apply for heat to the device then re flash ?
Click to expand...
Click to collapse
Sorry, I don't quite understand what you mean?
Clarkeofcurtis said:
Sorry, I don't quite understand what you mean?
Click to expand...
Click to collapse
Use a hairdryer to warm up the back of the phone.
Are you pulling my leg? Warm it up then reflash?
nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method
blackcell1 said:
nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method
Click to expand...
Click to collapse
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice
Clarkeofcurtis said:
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice
Click to expand...
Click to collapse
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.
blackcell1 said:
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.
Click to expand...
Click to collapse
thank you so much that worked, it has said flash successful, first time I got a google logo but now nothing, what would be my next step please?
if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
---------- Post added at 04:50 PM ---------- Previous post was at 04:49 PM ----------
but from my personal experience with having to heat a phone up to restore factory images, it kinda means the phone is nearing the end of its life and id start thinking about buying your next phone before it sh*ts the bed.
blackcell1 said:
if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
Click to expand...
Click to collapse
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc
Clarkeofcurtis said:
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc
Click to expand...
Click to collapse
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.
blackcell1 said:
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.
Click to expand...
Click to collapse
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?
Clarkeofcurtis said:
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?
Click to expand...
Click to collapse
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply
blackcell1 said:
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply
Click to expand...
Click to collapse
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay
Clarkeofcurtis said:
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay
Click to expand...
Click to collapse
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:
Is it possible to send me the guide you used? Thanks.
Clarkeofcurtis said:
Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?
Click to expand...
Click to collapse
Hey there sorry for slow replies, will be back on my desktop in an hour I'll send you links for what I followed and such, I think the only reason my device was in EDL mode was due to a hardware fault? As my device is faulty indefinitely as I had to use a hairdryer to warm it up while flashing this then allowed it to enter firehose state which a lot of people seem to error with - after all my attempts and research I'm to velieve there's a fault with the phone itself the only way I could get it to even power up was applying heat to it after removing the back panel
As blackcell said deballing or something? Worked a treat!
Furthest I've managed to get now is into my boot loader however everything is locked - when I press enter recovery my handset just freezes ?
5.1 said:
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:
Click to expand...
Click to collapse
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader
Clarkeofcurtis said:
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader
Click to expand...
Click to collapse
Light usually a red LED blink while in proper EDL state as far as I know. Could be something else on the N6P. Well, it looks like you are SOL. Sorry, I don't know what else to say, since you exhausted all possibilities...
Good luck...