Database Users

[Q] Nexus 7 Booting Failed & No ADB Connection

Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks

greyphox said:
Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks
Click to expand...
Click to collapse
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?

Wilks3y said:
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?
Click to expand...
Click to collapse
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers

greyphox said:
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers
Click to expand...
Click to collapse
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .

nexus toolkit from dev section

ngoralph said:
nexus toolkit from dev section
Click to expand...
Click to collapse
Have you even read what hes said?
He's already tried the toolkit...

Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
The first step in the full driver guide in wugs kit is to enable usb debugging which i cannot do though as it won't power on.......
I have added the environmental variabes before yes sorry, qbkings utube vids showed me how to do that
Just tried these steps
toolkit home screen, flash stock + unroot (softbricked bootloop)
then naksaki 4.2 jzo54k, auto download and extract.
it got to dos stage and i get 'Failed bootloader is locked'
??? thanks again

Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...

greyphox said:
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...
Click to expand...
Click to collapse
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.

Wilks3y said:
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.
Click to expand...
Click to collapse
MOOOOOO!
It wrote to the system ok and now its hanging on erasing user data, googled and its happend to others.......
OK, more help please, been hanging for5 mins lol

Issue Fixed I think, he PM'd me.

Unlocked but... what do I do now?
Newbie but old or old but newbie - With the need and not just a curious want, to be able to "rename" my Nexus 7 v1 so I can see a friendly name in my old DD-WRTed Linksys GL, I finally had enough gumption to try rooting this tablet.
So, I was excited that when I used Nexus Root Toolkit v1.6.8 on my Nexus 7 v1, following the "easy and visual" steps, I actually managed to unlock this device. But when it came to the "root" part, the ADB repeatedly failed to recognize this tablet. I tried all the suggested steps and remedies, but so far, nada.
The tablet now boots past the white "Google" with an unlocked icon at the bottom, but nothing beyond thea big white "right-arrow" on the screen. I can choose a Wi-Fi signal to connect to, but that's it.
This is my first tablet and I have been playing with it for the past 3 months. I know people here are more than willing to help, so thank you in advance.
BTW, I am not that young to spend hours way past sleeping time to scour for answers and piece it together.

Wilks3y said:
Issue Fixed I think, he PM'd me.
Click to expand...
Click to collapse
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?

Kindred Mole said:
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?
Click to expand...
Click to collapse
+1

This worked for me...
Download the image file for your device which you can find at the Google Developer's site
Copy the uncompressed files from the image archive to the platform-tools folder of the Android SDK
Use the up and down volume on the device to get into bootloader mode. Connect the device to a usb port.
Open a command prompt in the platform tools folder and run the flash-all batch file to load the image to your device. After a few minutes I got the happy X logo to get me back to a blank slate.

Google Icon on bootup

Ok I just need a little help and advice so if you one of you out there in XDAland can help I’ll be truly grateful…
I’ve got the 32gb Nexus 7 which I rooted via the Wugfresh method and added I CWM for my recovery and did the OTA update to Jelly Bean 4.2.1. The last 6 months life have been peachy. Even the misses and her iDevices are jealous of my little corner of Android heaven.
So last night pick up the 7 and notice it’s running a tad sluggish and I also notice the battery is low and flashing red, so I plug in the power cable and attempted to shut it down and it just hangs… I give it 5 minutes and still not shut down so I hold power & volume down and get in to the Bootloader from here I select start and the tablet just hangs on the Google cross (red, blue, yellow, green). This now happens every time I power down even though there has been a good charge (6 hours) done. If I now go back in the Bootloader and try selecting the Recovery Mode I get the Android robot with the red warning triangle and the words “No Command” and that’s it. If I try the factory reset of power button & volume up from recovery mode I get nothing.
From the bootloader I see
Fastboot Mode
Product Name - grouper
Variant - grouper
HW version - ER3
Bootloader Version - 4.13
Baseband Version - n/a
Serial Number xxxxxxxxxxxxxxxxxxxx
Signing - not defined yet
LOCK STATE - UNLOCKED
Can someone advise what the best thing I can do to revive the 7? I don’t mind losing the data but I’m just unsure what to do next. I’ve read a few threads but none pointed me in the direction I think I need to be in…
Thanks in advance for any help given.

You might have to use the google factory images and restore it completely to default... Sucks, but I don't know what else you could do, have you tried to fastboot flash a new recovery mode?
Here is a link to the stock google images, it will completely restore your tablet though:
... opps, looks like i don't have enough posts to post a link, just google "factory nexus images" and it is the fist one on the list sorry!
you have to use fastboot to flash them, but since you can access your bootloader, that isn't a problem. There are some directions on the page to use the images.
Hope this helped! Sorry you will probably lose everything though!

Thanks for the help but do you have a step by step guide as to what I do next? I have the image but my PC don't see the 7 anymore I can't enable debugging...

http ://forums.androidcentral.com/nexus-7-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.html

klinkdawg24 said:
http ://forums.androidcentral.com/nexus-7-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.html
Click to expand...
Click to collapse
Thank you soooooooo much for this!!

Dr Asqueroso said:
Thanks for the help but do you have a step by step guide as to what I do next? I have the image but my PC don't see the 7 anymore I can't enable debugging...
Click to expand...
Click to collapse
klinkdawg24 said:
http ://forums.androidcentral.com/nexus-7-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.html
Click to expand...
Click to collapse
Why wouldn't you use the guides found right here in this very forum?
http://forum.xda-developers.com/showthread.php?t=1907796
There's one right there. On the same page as your duplicate posts
Sent from my Nexus 7 using Tapatalk HD

@Pirateghost Well I followed your advice and went over the guide you linked but I can't get the 7 to be seen from the CMD line.. any other ideas?

OP - please do not duplicate threads. Closing this one in favor of the larger thread here:
http://forum.xda-developers.com/showthread.php?p=41192802#post41192802

[Q] Hard bricked tablet - what happened and what to do now?

I believe I've hard-bricked my Nexus 7. I'm not stranger to flashing, etc., but something must have messed up this time. I was previously running stock Android 4.3 with TWRP recovery and my tablet took the OTA update. The update of course failed because of the root and recovery, but instead of going back to Android 4.3, it wouldn't boot past the fastboot screen (bootloader screen? with the green android).
So, planning to return to all stock, I downloaded the official Android 4.4 .tgz file and extracted it to my platform-tools folder for the Android SDK. I ran "flash-all.bat" as explained in this tutorial: http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Something must have went wrong because the screen went black and will not turn back on. When plugged into the PC, it is recognized as only an "APK" device. Sources online indicate that this is hard-bricked, as there is no "nvflash" openly available for the Nexus 7 to restore the bootloader.
1. What happened and how can others prevent this?
I think I should have flashed each partition individually (i.e. boot, recovery, system, etc) instead of "flash-all." Any idea what happened to the bootloader? Any other ideas on how to restore the bootloader?
2. What to do now?
EDIT: Apparently my device is out of warranty. Crap.
EDIT 2: Apparently I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi)... Opps!
There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
Thanks for your assistance in advance! This forum is great.

What about pressing and holding power button for more than 30 seconds?
Once it could boot and you could enter into fastboot mode, then I think you would get a chance to save it.
BTW, I did mess up when I was flashing KRT16O factory images, which was the earlier release for Kitkat.
At that time, I just used the flash-all.bat like you did. And in the second round, I still failed when following and typing the listed commands in flash-all.sh.
So I chose to use nexus toolkit after that.

Thanks for your reply.
I keep trying that, along with the various other combinations of power button and volume down and volume up. Nothing. The most that happens is when it's plugged into the PC, the PC makes the sound of something being connected and disconnected. I just tried unplugging the battery too. I'll let it charge over night and try again tomorrow.
When yours failed the first 2 times, you were still able to get into fastboot? You're right, if I can just get there then I'll be alright.
Thanks again.

I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
1. Any way to recover from this brick? My gf also has a Nexus 7 (2012). Anything I can copy from that to restore mine? (if she even lets me touch it after she hears about this!)
2. There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?

No problem,bro. I think you can always get responses here at XDA though I didn't help you out.
And yes, I could still enter into Fastboot at that time.
However, I was not able to reboot my N7 using the aforementioned methods since it got stuck in Google logo.
Hence I removed the batterysilly, booted it and used the key combination to get into Fastboot. And you know the rest, used the toolkit....

My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
I do this all the time just for fun
Let me give u step by step instructions.
1. Download this tool kit
http://forum.xda-developers.com/showthread.php?t=1766475
2. Download the proper stock image for ur device (make sure u pay attention when u download the file, u definately dont want to download wrong file and then redownload the file again)
https://developers.google.com/android/nexus/images
3. Install toolkit, Select your device and don't worry about android version because u have non rit now and install the proper drivers for fastboot to work.
4. From toolkit main screen, select (softbrick/bootloop) and accept the warning.
5. Now select (Other/Browuse option) and then select (I Downlaoded a factory image myself) option then it will ask for the image that u downloaded from google website (Step 2).
6. If u have done exactly as i said then ur phone should be detected in Fastboot mode and the flashing would start and after some time phone should show loading screen (os is booting) wait for it to boot and enjoy ur stock android.
7. Enjoy.
FYI u should have enough battery (around 50%) and to enter fastboot mode u just have to boot to bootloader (restart/ power on the device while pressing volume down button) u should see the screen with bunch of numbers e.g bootloader version etc.

zamboniman87 said:
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
1. Any way to recover from this brick? My gf also has a Nexus 7 (2012). Anything I can copy from that to restore mine? (if she even lets me touch it after she hears about this!)
2. There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
Click to expand...
Click to collapse
Hmm... there is a thread on making it unbrickable, but you have to do that ahead of time. If you were to buy a broken tablet, you'd probably need to replace the motherboard.
Sent from my Nexus 4 using XDA Premium 4 mobile app

xateeq said:
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
Click to expand...
Click to collapse
Thanks for your help, but unfortunately I can't even enter fastboot. I can only enter APX mode, which apparently is pre-fastboot.

korockinout13 said:
Hmm... there is a thread on making it unbrickable, but you have to do that ahead of time. If you were to buy a broken tablet, you'd probably need to replace the motherboard.
Click to expand...
Click to collapse
Thanks. I saw that thread, but of course it was too late at that point. Perhaps I'll look into buying one with a cracked screen, or sell mine for parts on ebay.

Plz dont tell me u flashed wrong bootloader, plz plz plz.

zamboniman87 said:
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
Click to expand...
Click to collapse
Dammit, I just made this exact same mistake. Came here to XDA looking for help, and it seems that this may be one of those things that you simply can't recover from... sad day!
---------- Post added at 11:40 AM ---------- Previous post was at 11:09 AM ----------
SteveRiley said:
Dammit, I just made this exact same mistake. Came here to XDA looking for help, and it seems that this may be one of those things that you simply can't recover from... sad day!
Click to expand...
Click to collapse
Well, now isn't this weird... I unplugged the USB cable from my PC and then plugged it into the wall charger. After waiting a while, I was able to boot the Nexus into the "wrong" bootloader. I immediately flashed the correct one, and now am running the latest factory image.
@zamboniman87 -- I did find a thread on Android Central describing a situation in which someone erased their bootloader. The thread contains a tool that a couple folks claimed to help fix the problem. You might give that a try.

Lucky you! This gives me hope though. I'll check it out. Thanks!

xateeq said:
Plz dont tell me u flashed wrong bootloader, plz plz plz.
Click to expand...
Click to collapse
yep.... I feel dumb. haha.

xateeq said:
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
I do this all the time just for fun
Let me give u step by step instructions.
1. Download this tool kit
http://forum.xda-developers.com/showthread.php?t=1766475
2. Download the proper stock image for ur device (make sure u pay attention when u download the file, u definately dont want to download wrong file and then redownload the file again)
https://developers.google.com/android/nexus/images
3. Install toolkit, Select your device and don't worry about android version because u have non rit now and install the proper drivers for fastboot to work.
4. From toolkit main screen, select (softbrick/bootloop) and accept the warning.
5. Now select (Other/Browuse option) and then select (I Downlaoded a factory image myself) option then it will ask for the image that u downloaded from google website (Step 2).
6. If u have done exactly as i said then ur phone should be detected in Fastboot mode and the flashing would start and after some time phone should show loading screen (os is booting) wait for it to boot and enjoy ur stock android.
7. Enjoy.
FYI u should have enough battery (around 50%) and to enter fastboot mode u just have to boot to bootloader (restart/ power on the device while pressing volume down button) u should see the screen with bunch of numbers e.g bootloader version etc.
Click to expand...
Click to collapse
I soft bricked my nexus 7 (2012), I was in Team Win Recovery and I selected Dalvik Cache, System, Cache, Data, Internal Storage and formated/deleted it , now I don't have system or recovery
img > https://www.dropbox.com/s/a7ojrr16lt8n27s/nexus bricked (3).JPG?dl=0
all I can load is fastboot mode
img> https://www.dropbox.com/s/jzmr7811w02r525/nexus bricked (2).JPG?dl=0
I will try to do all this steps that "xateeq" wroted and let you now how it went thanks!

psykg said:
I soft bricked my nexus 7 (2012), I was in Team Win Recovery and I selected Dalvik Cache, System, Cache, Data, Internal Storage and formated/deleted it , now I don't have system or recovery
img > https://www.dropbox.com/s/a7ojrr16lt8n27s/nexus bricked (3).JPG?dl=0
all I can load is fastboot mode
img> https://www.dropbox.com/s/jzmr7811w02r525/nexus bricked (2).JPG?dl=0
I will try to do all this steps that "xateeq" wroted and let you now how it went thanks!
Click to expand...
Click to collapse
hey it worked thanks!
at first there were problems with fastboot and drivers somehow usb 2.0 was a bit problematic but usb 1.0 was able to see device
after downloading many drivers (some from nexus tollkit some from web) , and after few restarts of device and bootloader, pc was able to recognize device and than I had to go 2 times with nexus tololkit >softbrick/bootloop
1st time failed
2nd time worked!
thank all!

[Q] Hard Brick D800 - Please Help! At a loss

Any help is appreciated! First some background:
Flashed device to stock using KK 4.4 version d80020c following steps found here http://forum.xda-developers.com/showthread.php?t=2432476. Successfully rooted using directions (and ioroot25) found here https://www.youtube.com/watch?v=HKuedInhdjU&noredirect=1.
Here's where I got into trouble...Downloaded TWRP 2.7 recovery img and flashed via Flashify. Since this step, my D800 has the exact same symptoms found on this thread http://forum.xda-developers.com/showthread.php?t=2582142.
- No download mode (tried many times)
- No recovery (tried many times also)
- Secure booting error
- LG detected as qhsusb_bulk in device manager
- Device is recognized as 15 different drives, one of which contains a folder named image with 79 different files being .B0X files and Microsoft Access Add-in Data files
- Upon restarting, LG logo with secure booting error, then the screen goes black while your phone is still on
I've followed the steps in the thread that matches my G2's symptoms, run ubuntu 13.1 in VM, apply usb filters for my device which is then recognized as either LG Electonics Inc. QHUSB_BULK or Unknown Device 05C6:9006 when running in VM.
Upon running command ls /dev/sd* in VM Ubuntu Terminal, all that is returned is /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 which are the partitions for Ubuntu, no LG.
I've tried to download and update the Qualcomm drivers, device manager tells me that the drivers were recognized, but cannot be installed and do not pass the hash check (Note: PC is running Windows 8.1).
I've spent over 12 hours on this trying to fix this problem, researched and searched everywhere. If I could get ubuntu to recognize the device, I would be able to continue on with the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2582142.
Links for windows 8 qualcomm drivers, suggestions on how to get the device recognized in ubuntu vm, experiences from others in similar situation, or any with experience working with LG to get a repair done if I'm SOL (as in eMMC is fried) would be so helpful right now.
Thank you all!

After flashing recovery did you flash a patched kernel to boot stock kk?
Sent from my LG-D800 using Tapatalk

I had the same, also with a lot of drives etc.
Screen is black but low backlighted?
Then try with pluged USB Cabel in Phone, hold Power button until screen is realy off, then hold the Power Up Button and plug Cabel into PC.
So I got download mode after I tryed many times

I had problems a few weeks ago getting mine to go into Download mode... turned out that the cable I was using was great for charging, but sucked for everything else. Once I switched to a different cable things worked fine and I was able to load D80010c on the device.
I was running D80020c this morning (with the D80010c boot.img to have a custom recovery) and decided to do an update. Since you can't load D80020k if you have the older bootloader I went all the way back to D80010c, updated to D80010o, D80010q, D80020c and finally D80020k. I was able to root that using IOroot and have restored everything back onto my phone.
-Daryel

Thanks so much for the responses! I've tried endlessly to get the device into download mode, and tried a new cable to no avail. Any other suggestions?

The URL you've linked to will help you solve your problem.
So once you power off your device, hold volume down and power till the lg logo shows, then release shortly and hold them again together till the white window with "factory reset appears", you should notice a text behind the white screen it's fine. So right now when you think it's gonna enter recovery mode the screen is gray(not black), now you connect your device to your ubuntu or whichever linux. You will notice the screen repeatelly blinking when linux is trying to automount the partitions. Figure out which device it is according to the messages it throws. (sdc, sdb, sdX)
This way you should proceed according to the instructions on the thread you linked.
d800 partitions are here

Still no luck
bender_007 said:
The URL you've linked to will help you solve your problem.
So once you power off your device, hold volume down and power till the lg logo shows, then release shortly and hold them again together till the white window with "factory reset appears", you should notice a text behind the white screen it's fine. So right now when you think it's gonna enter recovery mode the screen is gray(not black), now you connect your device to your ubuntu or whichever linux. You will notice the screen repeatelly blinking when linux is trying to automount the partitions. Figure out which device it is according to the messages it throws. (sdc, sdb, sdX)
This way you should proceed according to the instructions on the thread you linked.
Click to expand...
Click to collapse
Thanks for your advice.
I got the white screen asking whether or not I want to perform a factory reset. If I choose No, the phone sends me right to the LG Logo with the error screen. If I choose Yes, it does the same thing. If I plug my phone into my computer while on the white screen asking if I want to perform a factory reset, the device isn't recognized and the PC doesn't see it as plugged in or mounted. I'm not sure what you mean by the timing of when I should try to plug in my device. Thanks again for all your help.

Sneaky Elephant said:
Thanks for your advice.
I got the white screen asking whether or not I want to perform a factory reset. If I choose No, the phone sends me right to the LG Logo with the error screen. If I choose Yes, it does the same thing. If I plug my phone into my computer while on the white screen asking if I want to perform a factory reset, the device isn't recognized and the PC doesn't see it as plugged in or mounted. I'm not sure what you mean by the timing of when I should try to plug in my device. Thanks again for all your help.
Click to expand...
Click to collapse
As soon as in the background of the white menu (factory reset) the secure boot appear plug it in. I'm not sure how much usb filter helps you(maybe it does) but try installing ubuntu over WUBI installer so your win remains. Or at least try ubuntu from usb stick. So you can know for sure if it's working.

Hi Sneaky E. I have the same issue you have. I'll be following your thread. If I figure anything out I'll let you know. I am also having an issue getting mine to charge now. Have you tried downgrading your TWRP?

VirtualBox Error
VirtualBox recognizes the device is plugged in, but won't allow me to push the device for use in linux. I keep getting this error message:
Failed to attach the USB device LG Electronics Inc. QHSUSB__BULK to the virtual machine Ubuntu.
USB device 'LG Electronics Inc. QHSUSB__BULK' with UUID {d8db3712-b86c-4257-a87b-275cef04e5a3} is busy with a previous request. Please try again later.
Result Code: E_INVALIDARG (0x80070057)
Component: HostUSBDevice
Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
Click to expand...
Click to collapse
I've tried all USB ports, 2.0 and 3.0. I feel like if I can get past this there should be no reason linux can't see the partitions in the phone. Please Help!!!

Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!

Sneaky Elephant said:
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Click to expand...
Click to collapse
you are not alone dude. i had the same issue since sunday and i have spent almost 46 hours already trying to restore my LG G2 F320S korean model.
i followed that instruction in linux, everything went well but then I ended up with a phone not going past the LG logo. the screen no longer dims like how it used to with the secure boot fail error. again, it stucked at the LG logo and thats it.
pressing the 3 buttons though for 5 seconds shows a white screen with 3 options and a bar code under.
but all of these options will just take me back to the LG logo.
I went to a phone technician today, and they said the doing a JTAG fix is the only way to resolve the problem because after trying to fix it with linux, it is no longer identified by my PC.
what are your solutions so far?
anyways before this issue came up, i tried to flash TWRP using flashify, it failed. then went back up. tried to update the OS via OTA then thats it.
i home someone could help us out.

ambetdelarosa said:
you are not alone dude. i had the same issue since sunday and i have spent almost 46 hours already trying to restore my LG G2 F320S korean model.
i followed that instruction in linux, everything went well but then I ended up with a phone not going past the LG logo. the screen no longer dims like how it used to with the secure boot fail error. again, it stucked at the LG logo and thats it.
pressing the 3 buttons though for 5 seconds shows a white screen with 3 options and a bar code under.
but all of these options will just take me back to the LG logo.
I went to a phone technician today, and they said the doing a JTAG fix is the only way to resolve the problem because after trying to fix it with linux, it is no longer identified by my PC.
what are your solutions so far?
anyways before this issue came up, i tried to flash TWRP using flashify, it failed. then went back up. tried to update the OS via OTA then thats it.
i home someone could help us out.
Click to expand...
Click to collapse
What are the negatives to doing a JTAG fix?

Sneaky Elephant said:
What are the negatives to doing a JTAG fix?
Click to expand...
Click to collapse
Here is your fix.
follow exactly. LINK

ingoljosh said:
Here is your fix.
follow exactly. LINK
Click to expand...
Click to collapse
Followed steps already, still can't boot into recovery.

Sneaky Elephant said:
Followed steps already, still can't boot into recovery.
Click to expand...
Click to collapse
if your device is insured maybe report it lost and pay deductible and get a new one AND NEVER ROOT AGAIN

linux cant recognizy my lg g2 f320L
Sneaky Elephant said:
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Click to expand...
Click to collapse
HI Sneaky elephant........bro I am having the same problem with my lg g2(hard bricked) that its not recognised by Ubuntu...it just shows hssusb-hulk.....no partitions to mount.............
in ur next reply u said that issue solve.....
kindly tell me too that how ur issue resolved...........thanks......

dr jam said:
HI Sneaky elephant........bro I am having the same problem with my lg g2(hard bricked) that its not recognised by Ubuntu...it just shows hssusb-hulk.....no partitions to mount.............
in ur next reply u said that issue solve.....
kindly tell me too that how ur issue resolved...........thanks......
Click to expand...
Click to collapse
The same with me - UP

install ur Ubuntu sing VMware....then partitions will appear.........
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
install ur Ubuntu using VMware......then ur mobile will be recognised and partitions will appear.....

[Q] Screen cracked and unresponsive but display still visible. Need help getting data

Hi guys,
I recently dropped my Nexus 4 on the floor today and the screen cracked. As a result, the screen is completely unresponsive now but I am able to see its display when I press the power button. Could you guys help me/point me in the right direction regarding how to get the data I have on the phone (music, photos etc.) please.
My Nexus is unrooted/stock version. I tried connected it to my laptop via USB, but all it does it charge. I think I might have the USB debugging option enabled (as I remember enabling it before sometime ago). I'm running the latest firmware (5.0.1 I believe). Also the bootloader is locked.
Any help would be much appreciated.
Thanks
EDIT: I should note that I have a Password (PIN) for the lock screen.
I installed android sdk and tried to enter commands, but it didn't work. When I typed in 'adb devices', no serial came up (I checked sdk manager for the google usb driver, and it says it's installed). Also, when I tried typing in anything i.e. 'adb shell' it said error no devices found. I was attempting to follow a guide to set up adb for any other steps required to get my data from the internal storage. Bear in mind, I don't have much knowledge on these tools, all I'm doing is following any guides. Please can you help me how to get my photos or the contents of the sdcard.

The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.

oracle93 said:
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.
Click to expand...
Click to collapse
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.

jd1639 said:
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.
Click to expand...
Click to collapse
Ah that was what I feared ... I'm running the latest firmware (5.0.1). I wouldn't really care about the phone if it weren't for a few images (should have had it backed up!).
Now I need to decide whether or not to change the screen etc. for £35 or just look in the market for a new phone. If I did buy a new screen/digitiser/frame thing, would these be suitable (where I won't need to use heat guns or glue and stuff)?
ebay (dot) co.uk/itm/LCD-Screen-Display-Touch-Digitizer-for-LG-E960-Google-Nexus-4-Frame-Replacement-/331224787829?pt=UK_Replacement_Parts_Tools&hash=item4d1e892b75
OR
ebay (dot) co.uk/itm/For-LG-E960-Google-Nexus-4-LCD-Display-Digitizer-Touch-Screen-Frame-in-Black-/331227949021?pt=UK_Replacement_Parts_Tools&hash=item4d1eb967dd
Also, if I did change it using the above, would dissembling the phone and reassembling it cause my data to be lost?
Thank you for your help
Edit: I managed to save about 80 photos which were probably in the default images folder in the SD card using AndroidLost. I'm guessing the other images which were in other folders i.e. WhatsApp Images etc. aren't recoverable using the site