Database Users

[Q] I am bricked! please help!

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

[Q] Stuck in FTM Mode?

Hi folks,
My wife dropped her 2-week old Nexus 4 which caused part of the front glass to crack and portions of the touchscreen to be dead, so we had to send it into LG for repairs (at quite a price tag). Fine.
So we get it back, I turn it on, and it's in something called "FTM Mode" (file transfer mode, I think)? I can't seem to get it out of it.
Things I've tried:
Rebooting (have to hold the power button down for 5-10 sec).
Factory data reset (the settings are available through the notification menu in FTM Mode).
In recovery mode:
[*]Start (goes right back to FTM Mode)
[*]Power off (duh)
[*]Restart bootloader (gets me right back to the same screen)
[*]Recovery mode (gives me a little android with its stomach open, a red exclamation point, and says "No command.")​
I attempted LG support, but they asked me to do a few of these (after asking me to hit the "home" button...), then told me to mail it back to them because they probably have to flash it.
So, the obvious question: how the hell can I get out of FTM Mode?
Secondary question: if none of the above worked and I do have to flash the OS, can I flash it myself to default Jellybean? Any idiot-friendly step-by-step guides out there?

Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2

joshnichols189 said:
Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.

Depressio said:
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.
Click to expand...
Click to collapse
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2

joshnichols189 said:
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunately, I haven't even been able to install the bloody USB driver, so fastboot/adb can't even see the device. I've described by problem here. I think the source issue is what LG did during repairs... the device is named "Full JellyBean on Mako" instead of something like "Nexus 4", so the drivers in that post aren't being recognized by Windows as valid for the device. At least that's my guess.

OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!

Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
For future reference ADB only works in recovery and when booted into android, never in boot loader. Bit glad you got it working
Sent from my Nexus 4 using Tapatalk 2

drives
Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
how did you can install the adb drivers,have same problem

ramonrecio said:
how did you can install the adb drivers,have same problem
Click to expand...
Click to collapse
plug your phone into your computer, then restart it in bootloader mode. the drivers will automatically install

same
hi,thank you,ok i can go to fastboot mode and select restart bootloader but when i hit power ,they turn off for a second and go back to fastboot mode initial page ,the pc do the sound when disconnect and connect back to usb pc,but that's it,no drivers installation ,what can i do!! this make me crazy,please help

[Q] Fully Bricked n7?

Well to make it simple, the newest twrp is very buggy and to make a long story short i installed a new rom, and while it was restoring my data, my n7 shut off. its done this before so naturaly i held the power+volume down buttons too boot into the bootloader but it wont turn on. Any help/ suggestions?

Put it on the power supply and let it there for some time ... Then start again.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Put it on the power supply and let it there for some time ... Then start again.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you ill try that. it was at 33% battery when this happened though

Um... It probably didn't shutoff. There's a screen timeout.
Sent from my Nexus 7 using Tapatalk HD

korockinout13 said:
Um... It probably didn't shutoff. There's a screen timeout.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
i know about the screen time out, i tapped the screen for it to rewake and it didnt work, then i tried pressing the sleep button once for it to unlock and that didnt work. so it indeed shutoff

frap129 said:
Well to make it simple, the newest twrp is very buggy and to make a long story short i installed a new rom, and while it was restoring my data, my n7 shut off. its done this before so naturaly i held the power+volume down buttons too boot into the bootloader but it wont turn on. Any help/ suggestions?
Click to expand...
Click to collapse
I'm confused. It's a little off-topic, but what does "restoring my data" have to do with TWRP in the context of flashing a new ROM?
Anyway, I would proceed with a dead battery or loose battery connector hypothesis first. It's not obvious why writes to /boot, /cache, /data, or /system would affect the bootloader.
Anything is possible at a low enough probability I suppose, but you should start troubleshooting operations with the high-probability scenarios first.
For instance - with the power off, will the "charging screen" display when you plug the tab in? How about APX** mode? (Plug in to PC and start with Power+Vol-up). If you didn't see either of those, it's likely a power supply or hardware problem.
good luck
** make sure you exit APX mode by holding down the power button for at least 20 seconds. I'm not sure if it shuts itself down after an inactivity timeout - you don't want to be draining power while trying to charge the tab.

bftb0 said:
I'm confused. It's a little off-topic, but what does "restoring my data" have to do with TWRP in the context of flashing a new ROM?
Click to expand...
Click to collapse
Well, you backup your data, Wipe data and cache, flash the rom, gapps, ect. then restore data, the charging screen wont dispaly, apx mode doesnt work, but the whole story: went to flash a newer version of my rom, install faills due to error in updater binary so i go to reboot and it says "No OS Installed! Are you sure you want to reboot?" i press dont reboot, go to install the older version of the rom, go to restore data and then it shut off.

frap129 said:
Well, you backup your data, Wipe data and cache, flash the rom, gapps, ect. then restore data, the charging screen wont dispaly, apx mode doesnt work, but the whole story: went to flash a newer version of my rom, install faills due to error in updater binary so i go to reboot and it says "No OS Installed! Are you sure you want to reboot?" i press dont reboot, go to install the older version of the rom, go to restore data and then it shut off.
Click to expand...
Click to collapse
The lack of APX mode or the charger screen suggests a battery problem or a hardware failure, not a software problem. APX mode will be present even if the tablet has absolutely nothing in flash memory.
Having nothing in /system (no OS or even no filesystem) will not affect bootability of either the bootloader or the recovery.
I don't know why you would wipe data only to restore it after flashing a ROM. Usually wiping cache & dalvik-cache is sufficient for "dirty-flashing" a ROM upgrade as it is very unusual for ROM installs to diddle with the /data partition. (But making full backups is always a good idea.)
I would check (carefully) to see if the battery connector came loose before you decide to throw the tablet away.
good luck

bftb0 said:
The lack of APX mode or the charger screen suggests a battery problem or a hardware failure, not a software problem. APX mode will be present even if the tablet has absolutely nothing in flash memory.
Having nothing in /system (no OS or even no filesystem) will not affect bootability of either the bootloader or the recovery.
I don't know why you would wipe data only to restore it after flashing a ROM. Usually wiping cache & dalvik-cache is sufficient for "dirty-flashing" a ROM upgrade as it is very unusual for ROM installs to diddle with the /data partition. (But making full backups is always a good idea.)
I would check (carefully) to see if the battery connector came loose before you decide to throw the tablet away.
good luck
Click to expand...
Click to collapse
Battery connector didnt come loose, still dosent work. guess it might just be broken
EDIT: I plugged it in to my pc and the google screen came up for about 20 sec then it shut back off. havent been able to get anything since

frap129 said:
Battery connector didnt come loose, still dosent work. guess it might just be broken
EDIT: I plugged it in to my pc and the google screen came up for about 20 sec then it shut back off. havent been able to get anything since
Click to expand...
Click to collapse
Is it possible to enter Odin on the n7?
Sent from my Galaxy Nexus using xda premium

Soldier 2.0 said:
Is it possible to enter Odin on the n7?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Odin is Samsung only
Sent from my Galaxy Nexus

You can hold the power button for 10 seconds and wait till you see the Google logo. Then release and hold it 10 seconds again, when the screen turns off hold the volume down button and wait for it till it automatically boots again. You'll enter bootloader mode. Download wugfresh' nexus root toolkit and install it. When the program is loaded there is a flash stock option on the right side of the program. Select the soft brick / boot loop option under the flash button. While in boot loader mode connect your nexus and press the flash button.
This is all I know!
Sent from my Nexus 7 using xda premium

NEXUS 7 Bricked - NO OS - tried everything but...
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.

CarlKirshner1989 said:
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
Click to expand...
Click to collapse
USB debugging doesn't mean **** when you are in a custom recovery. It has adb already. Your problem is your computer. Fix your computer by following one of the bajillion threads and posts about the nexus 7 drivers issues.
Installing drivers does not need android to be booted.
Your best bet is to put it in fast boot mode and follow Google's own instructions to flash it back to stock.
Sent from my Galaxy Nexus

CarlKirshner1989 said:
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
Click to expand...
Click to collapse
I must admit I'm a little 'hazy' myself when it comes to ADB related issues... I've never had much cause to use ADB. (Think I've used 'adb pull' on a couple of occasions). And I've never been in the invidious position of not having a bootable Android OS on my Nexus 7 either - which does seems to happen a quite lot with TWRP users, less so with CWM users.
Anyway... just had a tinker... and you could try the following workaround... this seemed to work to for me.
----------------------
Locate the folder on your PC where you keep your FASTBOOT and ADB .exe files...
Copy whatever ROM .zip you want into this folder.
The following example uses SmoothROM-v5.0.zip ... There is nothing to stop you from renaming this to something shorter, for ease of typing later... so, in my case, just smooth.zip.
Boot your Nexus 7 into the BOOTLOADER (Vol down [hold] + Power button), and then into RECOVERY (TWRP) and hook it up your PC.
Open a command prompt window on the aforementioned folder... and type...
Code:
adb devices
...which should yield something like the following...
Code:
List of devices attached
012345679ABCDEF recovery
(If you don't see a serial number... then you definitely have a driver problem...)
Otherwise, it's just...
Code:
adb push smooth.zip /sdcard
Or whatever ROM you wish to 'push' to the emulated SD card.
This will likely take a fair few minutes for a 300Mb+ size file (typically the size of your average ROM)... on my Windows XP box it took 4 minutes (1328 KB/s, 32565894 bytes in 239.486s) to copy over. And there are no 'progress gauges' of any kind, either... So season your patience a liitle. You can always pull up another command prompt window and type adb devices again to ensure you still have an ongoing ADB connection.
Once copied over, and still in TWRP, you can just flash it.
Good luck.
Rgrds,
Ged.

Still nothing on mine. im just about to give up and wait to see if google releases the N7 second generation at the i/o

If You familiar with Linux, You can try to understand the logic of
changing the modes.
You need to run udevadm monitor in one terminal. Then press some
combinations of key/s and look for changes with usb-devices.
The better, if You run wireshark and sniff USB interface with your device.
Put attachment here, with a comments what was pressed.

since it seems to be a hardware problem, not software, im just going to send it to asus and see what they can do.

bricked phone, tried everything

Ok, I've put my flame suit on, but I swear I have tried everything. I am not a developer level guy by any means, but I've been installing custom roms since the OG droid. But this time I got distracted and clearly made a foolish mistake. I was installing XDABBEB's new rom and I totally flaked out and installed the bootstrap and the rom in the same flash. it obviously didn't work and even though I read the instructions, I tried to restore my rom from a backup. Now the only thing I can do is boot into fastboot.
I've tried a number of ways to get TWRP or CWM back onto my phone so I can sideload a rom onto it, but every time I try to fastboot a recovery file it says that "remote: image is not a boot image" or something. What I have gathered from my research is that I cant install a custom recovery unless I am rooted.
/
So, without a custom recovery and only fastboot at my disposal, where do I go from here?

sfl007 said:
Ok, I've put my flame suit on, but I swear I have tried everything. I am not a developer level guy by any means, but I've been installing custom roms since the OG droid. But this time I got distracted and clearly made a foolish mistake. I was installing XDABBEB's new rom and I totally flaked out and installed the bootstrap and the rom in the same flash. it obviously didn't work and even though I read the instructions, I tried to restore my rom from a backup. Now the only thing I can do is boot into fastboot.
I've tried a number of ways to get TWRP or CWM back onto my phone so I can sideload a rom onto it, but every time I try to fastboot a recovery file it says that "remote: image is not a boot image" or something. What I have gathered from my research is that I cant install a custom recovery unless I am rooted.
/
So, without a custom recovery and only fastboot at my disposal, where do I go from here?
Click to expand...
Click to collapse
Phone model?
You can try to flash through LG Flash Tools

Swakiny said:
Phone model?
You can try to flash through LG Flash Tools
Click to expand...
Click to collapse
Thanks for the reply.
I have a VS980S. I have tried the LG flash tool, but I can't get any of the numerous LG drivers to recognize my phone. I even tried dd commands in Ubuntu, but all it would do is try and mount volume after volume making it impossible to use the interface,

sfl007 said:
Thanks for the reply.
I have a VS980S. I have tried the LG flash tool, but I can't get any of the numerous LG drivers to recognize my phone. I even tried dd commands in Ubuntu, but all it would do is try and mount volume after volume making it impossible to use the interface,
Click to expand...
Click to collapse
I'm in the same boat man. I tried flashing AOKP and it hung and I rebooted and everything but TWRP was gone. I'm in the process of trying the KDZ method right now.

markrulesallnow said:
I'm in the same boat man. I tried flashing AOKP and it hung and I rebooted and everything but TWRP was gone. I'm in the process of trying the KDZ method right now.
Click to expand...
Click to collapse
I hope it works for you. I tried that and flashing TWRP with fastboot but it said that it wasn't a valid boot image. A little research said that happens when your device is not rooted. But how can I root my phone from fastboot alone?

sfl007 said:
I hope it works for you. I tried that and flashing TWRP with fastboot but it said that it wasn't a valid boot image. A little research said that happens when your device is not rooted. But how can I root my phone from fastboot alone?
Click to expand...
Click to collapse
Try IOroot ... flash it true ADB !!

Denfic said:
Try IOroot ... flash it true ADB !!
Click to expand...
Click to collapse
I'll give a try and report back. But I have a feeling it won't work. I think I have the adb driver loaded but I can't get my computer to recognize any other of the drivers.

sfl007 said:
I'll give a try and report back. But I have a feeling it won't work. I think I have the adb driver loaded but I can't get my computer to recognize any other of the drivers.
Click to expand...
Click to collapse
when opening window in map .. try to tick adb service !!! It might recognize the phone that way !

​
Denfic said:
when opening window in map .. try to tick adb service !!! It might recognize the phone that way !
Click to expand...
Click to collapse
Sorry, what do you mean by "opening window in map"?

I was also in the same boat for 36 h, stuck on trwp recovery, no rom, no gaps in memory... I'm freely sailing now! I did this:
- press together power and lower button to get usb connecting screen, unplugged usb cable.
- LG tools installed and D-802 pilots {for me] installed, plug cable and check pilots again.
- launch in LG tools option for wrong install repair
- wait until the complete rom repair is installed, quite long, and then you win automatic reboot! You just loose root. Ioroot 25 again, that's all.
Hope it works for you chaps.

I had a similar issue. Follow this step by step. It even tells you when and how to install the drivers
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Sent from my VS980 4G using xda app-developers app

Icfatpeople said:
I had a similar issue. Follow this step by step. It even tells you when and how to install the drivers
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Yeh try this ... what i meant was when opening windows in adb-map ... windows -explorer !
But try the llink provided ...it will wake up your phone ..! :good:

Believe me before doing any thing using your pc just try to change the usb port first, then let it install the driver automatically(if you're using w7/8)
if windows xp just dont plug your phone remove the old LG driver and then plug your phone to another usb port that the one you have used it before with your phone and install the driver, and then proceed....
Why i am telling you this?
because i had almost the same problem with my galaxy note 2..... it wasn't recognizing my phone until i changed my usb port in download
mode and let it istall the driver......
hope it'll help.......... :good:

Icfatpeople said:
I had a similar issue. Follow this step by step. It even tells you when and how to install the drivers
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Ok, when I try this the computer recognizes my phone as a "USB Modem Phone ADB port" in device manager. But when I follow the directions in the link above if fails at Step 24. It says the phone is not connected. It is asking for my phone to be in "Download mode" in step 17, but I can only get into Fastboot mode. Is that the issue?

Yeah it is. Have you tried getting it into download mode? I was able to when I was stuck with a fast boot
Sent from my VS980 4G using xda app-developers app
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
Try holding the power until the phone is off. Then you should be able to get to download mode
Sent from my VS980 4G using xda app-developers app

Icfatpeople said:
Yeah it is. Have you tried getting it into download mode? I was able to when I was stuck with a fast boot
Sent from my VS980 4G using xda app-developers app
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
Try holding the power until the phone is off. Then you should be able to get to download mode
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Ok, as i understand it you have to hold volume up and plug the device in while its off. The problem I am having is that the phone is always on. Regardless of what mode I have it in, I can always see the back light glowing. I've searched for ways of truly turning the phone off, but I can't find any info.
Suggestions?

sfl007 said:
Ok, as i understand it you have to hold volume up and plug the device in while its off. The problem I am having is that the phone is always on. Regardless of what mode I have it in, I can always see the back light glowing. I've searched for ways of truly turning the phone off, but I can't find any info.
Suggestions?
Click to expand...
Click to collapse
Ok, hold power button until phone turn off, still holding until LG logo appear again, then the phone will turn off completly.
Turn off = Off
(First Off will take a long time, don't worry(about 40 seconds), don't forget: still holding the power button until LG logo appear and the phone Off)

Swakiny said:
Ok, hold power button until phone turn off, still holding until LG logo appear again, then the phone will turn off completly.
Turn off = Off
(First Off will take a long time, don't worry(about 40 seconds), don't forget: still holding the power button until LG logo appear and the phone Off)
Click to expand...
Click to collapse
ok, it seems like it goes off. the backlight appears to be off, but when I hold the volume up button and then plug it in, it immediately goes to fastboot. ugh.
can i use fastboot to send the phone to download mode? I'll start searching for that now.....

Have you tried this
http://forum.xda-developers.com/showthread.php?t=2477595
Sent from my VS980 4G using xda app-developers app

Icfatpeople said:
Have you tried this
http://forum.xda-developers.com/showthread.php?t=2477595
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Holy cow. This might be the last piece of the puzzle. I will report back after trying this.

Please help! Big issue here

Hey all!
My wife's nexus 4 screen is just dead! Latest signs of life were some weird colors and black and white lines and now it's completely black.
The problem is that it's locked (pattern lock) and we cannot access the phone.
I tried many times to unlock it blindly but I don't know if it's registering touches or not.
The phone LED is blinking normally while I can hear apps notifications and calls ring normally but screen is always black.
I just want to access the internal memory to copy the important photos and some important files on PC.
As you know, a locked device cannot be accessed through MTP.
I dunno what to do, any help would be appreciated!
Fixing the screen in here will cost me around 200 to 300$ which is the device price! And I'm not planning to do so! I just want to access the internal memory to access the files and use my spare phone.
I know that also formatting the phone to original state will remove the lock but I can't find a way to do so while it's completely black!
Thanks!

Life Engineer said:
Hey all!
My wife's nexus 4 screen is just dead! Latest signs of life were some weird colors and black and white lines and now it's completely black.
The problem is that it's locked (pattern lock) and we cannot access the phone.
I tried many times to unlock it blindly but I don't know if it's registering touches or not.
The phone LED is blinking normally while I can hear apps notifications and calls ring normally but screen is always black.
I just want to access the internal memory to copy the important photos and some important files on PC.
As you know, a locked device cannot be accessed through MTP.
I dunno what to do, any help would be appreciated!
Fixing the screen in here will cost me around 200 to 300$ which is the device price! And I'm not planning to do so! I just want to access the internal memory to access the files and use my spare phone.
I know that also formatting the phone to original state will remove the lock but I can't find a way to do so while it's completely black!
Thanks!
Click to expand...
Click to collapse
Do you have a custom recovery on? Is your bootloader unlocked? If so you may have an option using adb.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Do you have a custom recovery on? Is your bootloader unlocked? If so you may have an option using adb.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes the bootloader is unlocked and I have a custom recovery!
But what options do I have if I am practically blind?
Thanks mate!
Sent from my LG-D802 using XDA Premium 4 mobile app

Life Engineer said:
Yes the bootloader is unlocked and I have a custom recovery!
But what options do I have if I am practically blind?
Thanks mate!
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unplug your device from the usb and press and hold the power button go 15 seconds. That'll make sure your device is powered off. Then press and hold vol down and power until you feel it vibrate. Then release the keys. You should now be in the bootloader. Then press power up twice and then press power. That should put you into recovery. Then use adb pull to pull your data off.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Unplug your device from the usb and press and hold the power button go 15 seconds. That'll make sure your device is powered off. Then press and hold vol down and power until you feel it vibrate. Then release the keys. You should now be in the bootloader. Then press power up twice and then press power. That should put you into recovery. Then use adb pull to pull your data off.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks man for the help!
I will try it and let you know how it goes! Hopefully it works!
Sent from my LG-D802 using XDA Premium 4 mobile app

Life Engineer said:
Thanks man for the help!
I will try it and let you know how it goes! Hopefully it works!
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No problem. If you need more help let me know.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
No problem. If you need more help let me know.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The adb method failed on me 10 times although I was sure I'm in recovery mode!
Although I followed the steps exactly and I hear the "dong" sound on PC that the device is now connected,
adb devices command gives me nothing
and adb shell gives me error: no device connected
Of course to do that I have drivers installed and androidSDK too... I even followed an online guide to make sure I'm doing everything right...
I'm desperate now
Do you think these might work from bootloader instead of recovery?
If so could you please remind me how to reach it?
Thanks anyways man!

Life Engineer said:
The adb method failed on me 10 times although I was sure I'm in recovery mode!
Although I followed the steps exactly and I hear the "dong" sound on PC that the device is now connected,
adb devices command gives me nothing
and adb shell gives me error: no device connected
Of course to do that I have drivers installed and androidSDK too... I even followed an online guide to make sure I'm doing everything right...
I'm desperate now
Do you think these might work from bootloader instead of recovery?
If so could you please remind me how to reach it?
Thanks anyways man!
Click to expand...
Click to collapse
Google 15 second adb install xda. Try those drivers. It could be just a driver issue. Do use the command adb devices first and hopefully you'll get your device recognized. Once you do then use the adb pull
You won't be able to pull any files in the bootloader, you need to be in recovery.
Sent from my Nexus 5 using XDA Free mobile app

U
jd1639 said:
Google 15 second adb install xda. Try those drivers. It could be just a driver issue. Do use the command adb devices first and hopefully you'll get your device recognized. Once you do then use the adb pull
You won't be able to pull any files in the bootloader, you need to be in recovery.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
OK, I've done this simulating a non-functioning screen:
1. Don't have the usb plugged into the phone. Make sure the device is off, press and hold power for 15 seconds
2. Press and hold vol down and power simultaneously, when you feel the vibration release both keys
3. Press vol up twice then press power. It should vibrate once as it enters recovery, give it 15 seconds to boot into recovery
4. Plug in the usb cable
5. Open a cmd window on your pc and type adb devices. It should recognize the connected device
6. If your device is recognized use adb pull /sdcard/ c:\sdcard Have the c:\sdcard folder on your pc beforehand
If your device is not recognized got to device manager and see if there is a usb port with an exclamation mark on it. If there is you don't have the drivers set up right. Right click on that usb port and go to update driver software, go to browse my computer and let me pick from a list on the computer. Chose android composite adb interface. It'll probably ask you if your sure, just say yes.

jd1639 said:
U
OK, I've done this simulating a non-functioning screen:
1. Don't have the usb plugged into the phone. Make sure the device is off, press and hold power for 15 seconds
2. Press and hold vol down and power simultaneously, when you feel the vibration release both keys
3. Press vol up twice then press power. It should vibrate once as it enters recovery, give it 15 seconds to boot into recovery
4. Plug in the usb cable
5. Open a cmd window on your pc and type adb devices. It should recognize the connected device
6. If your device is recognized use adb pull /sdcard/ c:\sdcard Have the c:\sdcard folder on your pc beforehand
If your device is not recognized got to device manager and see if there is a usb port with an exclamation mark on it. If there is you don't have the drivers set up right. Right click on that usb port and go to update driver software, go to browse my computer and let me pick from a list on the computer. Chose android composite adb interface. It'll probably ask you if your sure, just say yes.
Click to expand...
Click to collapse
Bro bro bro it works!!!! Thank you thank you! It was a driver issue!
However, I am holding the laptop right now and I tried:
adb pull /sdcard/ etc...
and
adb pull /mnt/scard/ etc...
and both say remote object "/scard/" or "/mnt/sdcard" does not exist
What could it be named?
I want the Internal memory.
:EDIT :
Its working now!
THANK YOU!
Thanks a 1000000 times!

Life Engineer said:
Bro bro bro it works!!!! Thank you thank you! It was a driver issue!
However, I am holding the laptop right now and I tried:
adb pull /sdcard/ etc...
and
adb pull /mnt/scard/ etc...
and both say remote object "/scard/" or "/mnt/sdcard" does not exist
What could it be named?
I want the Internal memory.
:EDIT :
Its working now!
THANK YOU!
Thanks a 1000000 times!
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 5 using XDA Free mobile app