Database Users

[Q] adb offline nexus 7 4.2.2

Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:

Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?

how to do that?
compty said:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
Click to expand...
Click to collapse
how to unlock bootloader 4.2.2?
yes usb debugging is enabled

I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.

google toolkit error trying to unlock
compty said:
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
Click to expand...
Click to collapse
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally

Same problem
leo9252 said:
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Click to expand...
Click to collapse
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.

Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981

further problems
sicameron32 said:
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Click to expand...
Click to collapse
So I was going to do it the old fasion way by following this guide
http://forum.xda-developers.com/showthread.php?t=2150661
I didn't quite get step four because the nexus 7 doesn't have an SDcard, but I copied the zip to the root of the device.
When I did step 7 the device did not go to Fastboot, it didn't go anywhere other than a black screen. I think I have a faulty unit, or the holding of the volume buttons with the power is really not the way to get to fastboot, either way I am looking at a brick right now. Any thoughts will be welcome. I messed around with it for 10 min now and got the device to re-boot. Not sure if I should try the fast boot option again.

Are you on Windows 8 by any chance?
Because I couldn't get it to work on Windows 8 and had to use Windows 7.

You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.

everyone i got it working! adb offline fixed
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.

leo9252 said:
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
Click to expand...
Click to collapse
It won't let me download and install anything from the 4.2 list...did you do anything else?

myleb said:
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
Click to expand...
Click to collapse
FWIW, here is my experience:
PC: Win7 Pro x64 SP1 - SDK platform-tools 16.0.1 - SDK Tools 21.1 - ADB v 1.0.31
N7: JDQ39 Stock *
( *OK, i diddled default.prop in my boot image to set "ro.secure =0". I don't know if that could make a difference or not )
The Nexus 7 asks for confirmation of inbound adb sessions for every new adb server invocation on the client PC.
When it does ask for credentials, you have to get to the on-screen display pretty quickly - a couple of seconds at most. If you don't the device will be reported as "offline" by the first invocation of
adb devices
If you accept the connection, the next time you run "adb devices", the status is back to normal (reports "device" instead of "offline").
You can test this out yourself - just iterate in a loop these three commands:
adb devices
adb devices
adb kill-server
Nothing that can't be understood by someone who knows what is going on; but I suppose that all the toolkits are running adb underneath the hood, so it is certainly possible to get tripped up when using a toolkit if you aren't Jhonny-on-the-Spot when that dialog pops up on the tablet.
Also, for the adventuresome:
I note that the new stock JDQ39 (4.2.2) ramdisk has a new line in the default.prop that was not in JOP40D (4.2.1) :
Code:
ro.adb.secure=1
I suppose that could be toggled off if you have a favorite kernel/ramdisk setup and you don't want to be bothered by this stuff. But it does mean unpacking/repacking your boot images.
cheers

I'm having the same problem. Never recognizes an ADB device. When it does it shows my serial number followed by "offline."
Any ideas? I'm ready to return this thing.
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
Out of curiousity what driver are you using and how are you installing it?
Also where is your device coming up in the device manager?
I've tried so many things that I think I'm getting off track. Sadly my motorola phones were much easier to root.

how come you cant?
LucentBirch said:
It won't let me download and install anything from the 4.2 list...did you do anything else?
Click to expand...
Click to collapse
How come you can't download and install from the SDK manager?
That's how my problem got fixed.

Worked
jibdev said:
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
Click to expand...
Click to collapse
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.

you're welcome
sicameron32 said:
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
Click to expand...
Click to collapse
I knew someone would find this useful.
:laugh::good:

leo9252 said:
I knew someone would find this useful.
:laugh::good:
Click to expand...
Click to collapse
The sad thing is I have no idea what finally got it to work. Maybe just an extra reboot I had forgotten at some point. I do know however that I had to add a few extra lines (hardware ID) to the .inf file in the usb driver. Not sure which did the trick. I also used a combo of the toolkit to unlock and the manual method to root. Also I am unable to boot my device into the bootloader/fastboot via windows and rather have to manually (physically) shut down the device and enter the bootloader via the physical buttons. Probably an issue with the windows drivers again, but at least I have full functionality once in fastboot.
Only thing is now I can't get access to the storage via windows. And there's no way in hell I want to change the ADB drivers without knowing which finally worked for me. I'm thinking though that this is an entirely different device in device manager (I'm obviously not that knowledgeable).
Also I'm kinda annoyed by the unlocked padlock symbol on startup. I suppose that should be a welcome sign of achievement after spending all day trying to unlock/root, especially for such an unlearned person as myself.

did you clear this issue?
leo9252 said:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Click to expand...
Click to collapse
if not, pls gimme a mesg.
cause I'm a noob, I cannot use link here. :crying:
This issue is included in 4.2.2, and ADB is disabled by default for security.
I tested on my Nexus 4, 4.2.2 running. :fingers-crossed:

Okey. So to summarise: there is this new security feature in android 4.2. that makes the device show a popup if you want to allow the connected computer to use the adb = debugging bridge. But for this to work, you need to have the newest adb binary, which needs to print 1.0.31 when you run "adb version"
(found that info here --> http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ )
Under linux when you try to do it the old-school google-recommended way and download the huge "adt-bundle-linux-x86_64-20130219" and use the "android" tool to find new updates to the platform tools, it will tell you you already got the latest version which is rev 16.0.2 which contains an adb binary which will print version 1.0.26 which will not work with this new android 4.2.2 security feature.
So after searching for a linux adb 1.0.31 binary, I found it here:
https://github.com/mozilla/r2d2b2g/commit/2eefcc05366173ca51635da8f542fd8473ba0fea -->
https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/adb-1.0.31-linux.zip
with that binary I finally can use adb on my nexus 7 again.

Need help... cannot figure rooting out

Hi all,
Long story short, I accidentally bought a Kindle Fire HD 7. I was hoping to root it but I've had nothing but difficulty. Can anyone help me with the things below? ** Please don't reply if you can't - the disorder and unmoderation of this forum is part of the confusion problem **
- The apps that are given on this site mostly don't work for 7.2.3. Is this an issue with the version?
- I kept getting permission denied errors. Nothing that pushes over, pushes successfully - yet it says it does
- When I finally got something "rooted", my status bar and home bar (at the bottom) are all gone. I can pretty much do nothing with it
- I can't figure out how to restore. I can get into FastBoot mode fairly easily, but when I try to do anything I get "waiting on device" errors. Any ideas?
- I'm a Mac guy, but running Windows 7 to do this. I've tried various versions of drivers posted on the board, but W7 is just a PITA to work with. When it goes into Fastboot, it comes up as an "unrecognized device" in Device Manager. Would this be part of the problem? I've tried to associate drivers with the unknown device, but it keeps saying the driver it has is the best (even though I've removed it).
And while I admit, an emotional rant after spending way too long having to do the above..:
- This forum is a complete mess.. can people with KF HD 8.9's get out of the forum and quit replying or giving advice on the wrong device? Mods, please shut down or move KFHD 8.9 posts. For people trying to find out info, it's seriously a mess.

lordmuggins said:
Hi all,
Long story short, I accidentally bought a Kindle Fire HD 7. I was hoping to root it but I've had nothing but difficulty. Can anyone help me with the things below? ** Please don't reply if you can't - the disorder and unmoderation of this forum is part of the confusion problem **
- The apps that are given on this site mostly don't work for 7.2.3. Is this an issue with the version?
- I kept getting permission denied errors. Nothing that pushes over, pushes successfully - yet it says it does
- When I finally got something "rooted", my status bar and home bar (at the bottom) are all gone. I can pretty much do nothing with it
- I can't figure out how to restore. I can get into FastBoot mode fairly easily, but when I try to do anything I get "waiting on device" errors. Any ideas?
- I'm a Mac guy, but running Windows 7 to do this. I've tried various versions of drivers posted on the board, but W7 is just a PITA to work with. When it goes into Fastboot, it comes up as an "unrecognized device" in Device Manager. Would this be part of the problem? I've tried to associate drivers with the unknown device, but it keeps saying the driver it has is the best (even though I've removed it).
And while I admit, an emotional rant after spending way too long having to do the above..:
- This forum is a complete mess.. can people with KF HD 8.9's get out of the forum and quit replying or giving advice on the wrong device? Mods, please shut down or move KFHD 8.9 posts. For people trying to find out info, it's seriously a mess.
Click to expand...
Click to collapse
Ok what is the state of your KFHD? 7"? I would try to use this toolhttp://forum.xda-developers.com/showthread.php?t=1951254 to restore your kindle and getting back to a working state. If you have any questions post them in here or that forum and I will try to guide you through anything. You should not try to use an automated root tool if it isn't for your specified version(7" 7.2.3) and using a automated tool, I think personally, is just not good in general. What does the device manager specifically say when you are in fastboot? It shoulde look like this:

Thanks for getting back to me. I have indeed also tried that, but I encounter the Fastboot problem mentioned above. I can get it into FB mode fine, but when I go to do anything, it gets stuck at "waiting for device". I'm wondering what I'm doing wrong?
I'm using Windows 7 (gah)... just for the purpose of this. Believe me, it reminds me why I've left Windows looonngg ago
PS All automated tools were specific to my model and version #.. i wouldn't do otherwise.

And I forgot to say, it shows the yellow triangle warning signs.
I have however installed all the right drivers that I got on various places on the forums. Any ideas why it's doing that? (USB debugging/ADB is enabled of course)

lordmuggins said:
And I forgot to say, it shows the yellow triangle warning signs.
I have however installed all the right drivers that I got on various places on the forums. Any ideas why it's doing that? (USB debugging/ADB is enabled of course)
Click to expand...
Click to collapse
Try to reinstall the appropriate drivers.. first uninstall the ones you have now then reinstall.. if you have the yellow triangle in device manager the drivers are not installed correctly

I've tried that.. not sure what I need to do now. (I hate Windows)
The drivers appear fine when not in Fastboot (ie regular ADB) just not when in Fastboot

lordmuggins said:
I've tried that.. not sure what I need to do now. (I hate Windows)
The drivers appear fine when not in Fastboot (ie regular ADB) just not when in Fastboot
Click to expand...
Click to collapse
You do know that ADB and Fastboot are different.. Correct? They are two different cmd lines to execite comds to your kindle..does your kindle boot? What is its state? what are you seeing or does it even run at all>

I thought I made this clear in other posts, sorry
My Kindle boots fine normally, but in my attempts to root it, it's screwed something up (my menubar doesn't appear). I wished to restore it using the tool above.
I can get it into Fastboot, but I can't actually perform any actions due to it saying "waiting for device". Most ADB functionality works fine, i.e. to push apps. But I also can't get it rooted.
My issue is that when it is in Fastboot...not when it's not. That is what I'm trying to figure out.

lordmuggins said:
I thought I made this clear in other posts, sorry
My Kindle boots fine normally, but in my attempts to root it, it's screwed something up (my menubar doesn't appear). I wished to restore it using the tool above.
I can get it into Fastboot, but I can't actually perform any actions due to it saying "waiting for device". Most ADB functionality works fine, i.e. to push apps. But I also can't get it rooted.
My issue is that when it is in Fastboot...not when it's not. That is what I'm trying to figure out.
Click to expand...
Click to collapse
Have you tried Kindle Fire First Aide tool and the restore option of you version?

Yes, I have.
And my issue remains - when in Fastboot mode, it also gets stuck on "waiting for device".
When normal boot, ADB functions are fine. It communicates.. things happen
When in fastboot (I have a WordArt looking 'fastboot' logo on the screen) then nothing appears to communicate, and my Device Manager claims it has an "Unknown Device" that it wont let me manually install drivers for.
Windows 7 is x64 if that makes a difference

lordmuggins said:
Yes, I have.
And my issue remains - when in Fastboot mode, it also gets stuck on "waiting for device".
When normal boot, ADB functions are fine. It communicates.. things happen
When in fastboot (I have a WordArt looking 'fastboot' logo on the screen) then nothing appears to communicate, and my Device Manager claims it has an "Unknown Device" that it wont let me manually install drivers for.
Windows 7 is x64 if that makes a difference
Click to expand...
Click to collapse
Try a factory reset on the device and if that doesn't work go to Chris's thread, KFFirstAide and post your problems that you having with the software. He will help you figure out if something is wrong with your device or its the software. I would think its user related, in the nicest way possible. A lot of times we get are selves all worked up over this stuff and forget to specific steps, I am guilty as well. Maybe take a step back for a few hours and then give it another shot.. Sorry I couldnt help more but I currently don't have my KFHD bc I just got a new one shipped to me and still waiting for it to arrive.. If i had my device in front of me I would probably be able to find you a solution.. Its been three weeks since I have seen a Kindle and my memory is vanishing

How do you propose I do a factory reset?

lordmuggins said:
How do you propose I do a factory reset?
Click to expand...
Click to collapse
right.. menubar is gone.. how the F did that happen.. I don't get all these people having so much problem with rooting their devices and $hit disappearing.. Can you download soft keys? I don't remember if you need to be rooted or not too..

If I knew the answer to that question, I wouldn't be here. I do not see how I can download soft keys.. unless they're in the Amazon store?

lordmuggins said:
If I knew the answer to that question, I wouldn't be here. I do not see how I can download soft keys.. unless they're in the Amazon store?
Click to expand...
Click to collapse
Hey man just trying to help you.. I'm not the one with the problem, although I am making my problem bc I am trying to help. Go over to either thread KFFirstAide or KFHD system.img resotre tool and post your problem.. good luck

So I got it restored; I had to execute the app open in adb to get into Settings. Still can't figure out how to get the Win 7 to recognize it in Fastboot mode.. I just get "waiting for device"

lordmuggins said:
So I got it restored; I had to execute the app open in adb to get into Settings. Still can't figure out how to get the Win 7 to recognize it in Fastboot mode.. I just get "waiting for device"
Click to expand...
Click to collapse
Do you mean you get that when you select the option to reboot into fastboot mode, or that you are already on the fastboot screen but nothing is happening?
I had the exact same issue with missing status bar and softkeys, cazy annoying. So hopefully I can remember exactly what I did, depending on your answer to my question though

In regular mode, I had missing status bar and softkeys. I restored factory settings (by using adb to get into the settings screen). They are now back.
Now, I have it rooted (well, I have Superuser loaded at least and it appears to be working)... but that is all. It still feels half-done to me.
With the FirstAide tool I'm getting into Fastboot and then I was going to use it to restore it using the Restore Tool here: http://forum.xda-developers.com/showthread.php?t=1951254
But it doesn't work.. I can load into the Fastboot screen (wordart logo) but it doesn't connect to the device... I just get "waiting for device" and that's where it stops. The WIndows 7 PC I'm using just says that an unknown device has connected and leaves it there.
Ideally, I wish to load Google Play etc, but I can't do that using the First Aide tool. It throws a lot of permission denied errors at me.. reboots several times, says it has been successful but none of the apps are there.
Ideas? I feel like I'm getting closer... perhaps..!

Have you tried running a app that needs root and seeing if the "grant permission" window pops up when you run it. There is a root checker app that you could install from the Noobs Guide to rooting, which should do the trick. SUChecker.apk http://forum.xda-developers.com/showthread.php?t=2069117
If you have managed to get the UI bars back, how come you want to use the restore tool to reset the whole kindle?
If you root is working fine, and you want to install google play then follow the Alternative Manual Install from here http://forum.xda-developers.com/showthread.php?t=2069329 instead of using the first aide tool, which seems to be giving a few issues at the moment.
Another random solution is make sure you are using a usb2 port instead of a usb3 port(if you have one)

Help an idiot flash a factory image

So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??

You can't use adb commands in fastboot. You should use fastboot commands and flash the factory image
Sent from my Nexus 5

Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
Well, I had a serious issue with something similar, after trying to update (not flash the factory image) to KitKat it produced an error and now it's bootlooping and, worse, my computer won't recognize the device, so I can't flash the factory image whatsoever. Your problem is much more light, as your computer is actually recognizing the device. What I'd suggest is using the Nexus Root Toolkit by WugFresh. Yes, I know, a lot of people here don't like using it but it's extremely useful when you have drivers issues.
It's actually a pretty straight forward procedure, you install the toolkit and it will ask you for your device model, android version, etc., then take you through the process of updates and stuff. Then, on the main window, you have this wizard "Full Driver Installation Guide" that will give you 4 ways to get your device working. You can find the Toolkit here: http://www.wugfresh.com/nrt/. Good luck!

I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5

Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
It's also difficult when trying to assist somebody... they're using the vocabulary of toolkits (which I'm not familiar with)... and I'm going on about fastboot... which they don't understand. It's like there are now two different languages... TOOLKIT and FASTBOOT.
Makes it very difficult to assist people.
Maybe I should have a tinker with Wugfresh... if for no other reason than to at least get an insight into how these things work.
Rgrds,
Ged.

The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5

Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.

GedBlake said:
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.
Click to expand...
Click to collapse
Basically yeah.
I have a feeling a good portion of the hesitation comes from the command line being scary to most people.
Sent from my Nexus 5

In the tgz file you download there is a 'flash-all.bat' file that does everything for you. If you open it in notepad, you see exactly what it does and in what order.
Yes, drivers are probably the issue, they were for me at least. I ended up using NRT (wugs toolkit) to install drivers (and root later, but that's a new topic)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jwr66y.zip
echo Press any key to exit...
pause >nul
exit
This is a Google way to flash the factory image.
---------- Post added at 10:02 PM ---------- Previous post was at 09:59 PM ----------
Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
The idea is great, try writing it
I'm sure it'll be greeted with appreciation.

Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
As long as you can still boot into bootloader mode, it is still fixable. Try reinstalling fastboot drivers.

Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah, because that was really helpful to him. I didn't tell him to use the toolkit to flash, root, unlock, or anything of the sort. For drivers issues, I do recommend (and will continue to do so) using the toolkit when official drivers don't work, because it has helped me a lot in the past, but I haven't used it to flash anything.

Download the image for your device and extract it into a folder
Download the zip below and move the files into the folder you created above
http://forum.xda-developers.com/showthread.php?t=1484407
Switch device off. Hold volume down and turn it back on, so it's in fastboot mode
Plug device into computer
Run "flash-all.bat" in the system image folder you extracted first

Want to thank everybody for their replies. Have had a family emergency so havent had a chance to try any suggestions, but didnt want to just ignore the thread i started.

[GUIDE] Simple Root Nexus 7 2013 LTE (deb)

Preamble
As a crotchety old man, my eye twitches and my back hurts every time I read a guide with superfluous steps, a root toolkit or an autoroot script for a nexus device. So, at the request of @thejmannnc, here's my simple root guide for Nexus 7 2013 LTE (deb).
NOTE: this will work just as well for the WiFi only version (flo), so long as you download the specific custom recovery for your device.
If your bootloader is locked (e.g. if this is your first time rooting this device)YOU WILL LOSE ALL YOUR DATA. There is no way around this.
Prerequisites
NOTE: I'm not writing a guide for these prerequisites
Prerequisite 1: "Fastboot" on a machine running a desktop operating system
Fastboot is one of the platform tools you can get from the android software development kit (SDK). You will need to install it. You can install the complete SDK, the platform tools, the two most basic platform tools (fastboot and adb), or, in theory, just fastboot.
*If you want to use adb as well, you will need to enable developer options and USB debugging on your N7. See the end of this post.
The SDK from Google:
http://developer.android.com/sdk/index.html
An XDA created tool for adb and fastboot. I haven't used it, but I'm told it works:
http://forum.xda-developers.com/showthread.php?p=42407269
A guide for installing the SDK for Windows 7:
http://forum.xda-developers.com/showthread.php?t=1830108
A guide for installing the SDK for Mac OS X:
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
Prerequisite 2: IF you use a Windows machine, USB DRIVER
Driver from Google. Note, the Google driver may not work for Windows 8:
http://developer.android.com/sdk/win-usb.html
If that doesn't work for you, try this driver:
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Prerequisite 3: A custom recovery .img file
Download a custom recovery .img file to your computer (or any machine with a USB port that runs a desktop operating system). Place the file in the same directory (folder) that houses fastboot. I recommend TWRP custom recovery.
TWRP for deb (LTE):
http://techerrata.com/browse/twrp2/deb
TWRP for flo (WiFi only):
http://techerrata.com/browse/twrp2/flo
THE ACTUAL GUIDE
Step 1: Unlock your bootloader
Power down your Nexus 7. Once you've totally powered down, hold down the power and volume down key on your nexus 7.
Plug your Nexus 7 into your computer.
Open a command prompt (Windows) or Terminal window (Mac OS X, Linux) in the directory that houses fastboot (or navigate to that directory using the command cd, or, if you've properly set up your platform tools in Mac OS X, don't pay any attention to the directory).
Type the following command (this is the step that wipes your device.):
Code:
fastbot oem unlock
Follow the prompts. Then reboot your Nexus 7 by pressing the power button when the menus says "START". During the reboot your N7 will go through a factory reset.
Step 2: Download the superuser binaries:
On your Nexus 7, download from this link:
http://download.chainfire.eu/
Step 3: Install TWRP and superuser binaries
Reboot into bootloader as you did for step 1:
Power down your Nexus 7. Once you've totally powered down, hold down the power and volume down key on your nexus 7.
Plug your Nexus 7 into your computer.
Open a command prompt (Windows) or Terminal window (Mac OS X, Linux) in the directory that houses fastboot (or navigate to that directory using the command cd, or, if you've properly set up your platform tools in Mac OS X, don't pay any attention to the directory).
Type the following command:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img
If you downloaded a different version (or the recovery for flo), replace "openrecovery-twrp-2.6.3.1-deb.img" with the file name for the image you downloaded.
Once you've flashed recovery, you should still be in the bootloader. Use the volume keys to navigate to "Recovery mode". (Hint, it's two taps of the volume down button. Press the power button to reboot into recovery mode.
Once recovery reboots, you'll see a menu with 8 buttons in a 4x2 grid. Tap "Install".
Navigate to your Download directory, where you'll find the file "UPDATE-SuperSU-v1.75.zip" (or whatever version was current when you downloaded it). Tap that file.
Swipe to confirm flash.
Once the superuser binaries have installed, tap the "Reboot System" button.
Congratulations! You're now rooted.
Epilogue:
If you want to use the android debug bridge (adb) you'll need to enable developer options and usb debugging.
Under settings, about tablet, tap build number 7 times to enable developer options, back out to settings, developer options, check USB debugging

You are the Man!! Thank you for taking the time to help me make this process so easy on me. You have definitely simplified the process. There's not alot of people in this world that would take their time and knowledge to help out a stranger. Not many people out there left like you! Im sure this will also help out countless others out there like me as well.
Cant say thanks enough,
Jimmy aka thejmannnc

thejmannnc said:
You are the Man!! Thank you for taking the time to help me make this process so easy on me. You have definitely simplified the process. There's not alot of people in this world that would take their time and knowledge to help out a stranger. Not many people out there left like you! Im sure this will also help out countless others out there like me as well.
Cant say thanks enough,
Jimmy aka thejmannnc
Click to expand...
Click to collapse
Your welcome. Please let me know if you have any trouble.
Sent from my Nexus 6 using Tapatalk 4

I had done the step above, however I am in boot loop now. I can not seem to get out of it.
I had tried to Factory Reset within TeamWin Recovery, however it is giving me a failed message.
Please help
---------- Post added at 12:06 AM ---------- Previous post was at 12:06 AM ----------
I had done the step above, however I am in boot loop now. I can not seem to get out of it.
I had tried to Factory Reset within TeamWin Recovery, however it is giving me a failed message.
Please help

xdhall said:
Your welcome. Please let me know if you have any trouble.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Hello,, I just got the nexus 7 and it immediately wamts to update to 4.4. Should I let it? Didnt know if this would affect using the guide you created. I wont touch anythimg until I hear from you to be on the safe side.
Thanks,
thejmannnc

cs378 said:
I had done the step above, however I am in boot loop now. I can not seem to get out of it.
I had tried to Factory Reset within TeamWin Recovery, however it is giving me a failed message.
Please help
---------- Post added at 12:06 AM ---------- Previous post was at 12:06 AM ----------
I had done the step above, however I am in boot loop now. I can not seem to get out of it.
I had tried to Factory Reset within TeamWin Recovery, however it is giving me a failed message.
Please help
Click to expand...
Click to collapse
To recover from bootloop, turn off your device, let it sit for a couple of minutes, reboot into recovery and wipe cache/dalvik cache.
If this doesn't work, verify that you downloaded the correct TWRP image for your device. (Deb = LTE, flo = Wi-Fi only).
Sent from my Nexus 6 using Tapatalk 4

thejmannnc said:
Hello,, I just got the nexus 7 and it immediately wamts to update to 4.4. Should I let it? Didnt know if this would affect using the guide you created. I wont touch anythimg until I hear from you to be on the safe side.
Thanks,
thejmannnc
Click to expand...
Click to collapse
Yes. Update to 4.4. It won't impact the guide.
Sent from my Nexus 6 using Tapatalk 4

xdhall said:
Yes. Update to 4.4. It won't impact the guide.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Ok. Thanks for getting back to me so quickly, would have been just my luck!!

xdhall said:
Yes. Update to 4.4. It won't impact the guide.
Sent from my Nexus 6 using Tapatalk 4[/QUOT
For some reason I am having trouble installing the driver. Downloaded, extracted, now stuck. Maybe im just tired and stressed but never had trouble with drivers before. Well at least the tablet was delivered today! Am I missing something simp
e?
Click to expand...
Click to collapse

thejmannnc said:
xdhall said:
Yes. Update to 4.4. It won't impact the guide.
Sent from my Nexus 6 using Tapatalk 4[/QUOT
For some reason I am having trouble installing the driver. Downloaded, extracted, now stuck. Maybe im just tired and stressed but never had trouble with drivers before. Well at least the tablet was delivered today! Am I missing something simp
e?
Click to expand...
Click to collapse
You don't need to enable USB debugging to root with fastboot, but it's possible that you need to in order to install the drivers. I don't use a Windows machine, so I don't have specific knowledge of the driver installation procedure. Enabling USB debugging is described in the guide epilogue. If that doesn't work, you'll have to ask someone with more experience on a Windows machine (or find a machine running a Linux based OS like Mac OS X or Ubuntu--they don't need drivers). Wish I could be more help.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse

xdhall said:
thejmannnc said:
You don't need to enable USB debugging to root with fastboot, but it's possible that you need to in order to install the drivers. I don't use a Windows machine, so I don't have specific knowledge of the driver installation procedure. Enabling USB debugging is described in the guide epilogue. If that doesn't work, you'll have to ask someone with more experience on a Windows machine (or find a machine running a Linux based OS like Mac OS X or Ubuntu--they don't need drivers). Wish I could be more help.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Got it all taken care of! Time to relax!!! Thanks for all your help!! If your ever in NC look me up and ill buy you a beer!!
Have a good one!
Thejmannnc
Click to expand...
Click to collapse

Thank you for such a easy to do guide. Android amateur is now rooted and ready to install custom ROM onto his 2013 LTE
I did the Mac part of guide. No problems.

LG G2 Fastboot

Everything I found on this says volume + and power, which kicks me into download mode, not fastboot.
I've gone into adb and typed adb reboot bootloader, but that just restarts the phone and turns in on like normal.
I google the how to enter fastboot mode on LG G2 and can find plenty of post about being stuck in fastboot, but nothing on how to get into fastboot in the first place.
Found a tutorial here about setting up and using fastboot and thought I was set until I got to the part about "and using fastback", where it just says:
Make sure you have android debugging turned on in your phone (not really needed for fastboot but you do need for ADB), plug it into your computer and boot into fastboot mode...
I felt like watching "Much ado about nothing" when Denzel says; "The learned constable is too cunning to be understood"
Any direction is appreciated.

Hmm, I may have written that guide... Just checked and yeah should have been more clear I'll change that up. It should have read the USB debugging was needed for adb (not for fastboot) so when you can issue
adb reboot bootloader
But after that I did mention to check device specific forum for answers on how to get into fastboot/bootloader and being I've never held an lg g2 I took a quick look around.
Unfortunately the only way that I found that people said works every time is to wipe recovery to get into bootloader mode as the recovery you guys currently have disables something due to a patch getting custom recoveries to work
So yeah, I would advice to speak with someone knowledgeable about your specific device before you just wipe recovery
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Click to expand...
Click to collapse
the current thing I've been trying to straighten out is that despite being rooted and installing TWRP, I can't install ROMS. I tried CM 11 and Hellfire so that I could put kitkat on, but gave the following:
Error executing updater binary zip.
One of the answers I found said that I had to go back to TWRP 2.3 (I'm using 2.6) and I believe that's where the whole bootloader thing came into play, because it was the way to 'downgrade' -
So then I found Philz touch 6 (as I understand it a mode of CM 11), but here he talked about fastboot and lokifying items. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2554053
In the end it still comes back to the "can't load ROMs" issue. Just want a completely stripped down Kitkat that I can add the stuff I want without the bloatware.
Thanks in advance.(and the thanks button was hit on your reply)

For KitKat you should need a newer recovery with SELinux support which I believe is 2.6.x and newer for twrp, 2.3 I doubt would work if there even is one for your phone
But yes fastboot is often the best way to change recoveries but not the only way.
If there is a flashable.zip you could install new recovery from old
If your current ROM supports the flash image binary you can use a terminal emulator
You can use adb to install
Or even apps from the market
I would look for the latest recovery for your device, twrp, cwm, shouldn't matter so long as its new and then find what way works best changing for your phone.
The update-binary issue is often a sign that you need to change recoveries
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Click to expand...
Click to collapse
Thanks again. I have adb and the script for loading TWRP 2.6.xx. I unrooted and rerooted the phone, because I wasn't sure how to replace the recovery... Now I think I realize that I could just find another recovery image and place it in the same file as the loki flash and that will flash it (At least that's what I understand at present).
If that's the case, then downloading the Philz touch 6 would work... but not wanting to brick it, I'm still asking and reading.

Hello Guys.
I am having a similar issue. I have a new ROM that will not run because of a faulty lg set up wizard that always force closes and I can not get passed it and a nandroid that for some reason is corrupted. So. This fastboot seems to be a dead end it looks like a quick learning curve of ADB is the only viable answer. I have installed all SDK Manager with ADB Tools and also the required Jarva JDK and LG drivers. The phone is turned on (at the beginning of the faulty setup wizard) In CMD my device is found when typing in 'adb devices' So. I am already to push a new ROM over to the phone.
Do either of you guys know the adb command?
Help would be appreciated.
Thanks

You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app

I found that the best way was to load flashify, that did the trick so I could start trying out ROMs... so no on to the next step - finding a 4.4.2 stripped down stock and the LG stuff I actually like.... thanks again.

demkantor said:
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks

dodge3003 said:
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
Click to expand...
Click to collapse
I HAVE SOLVED THE ISSUE! Thanks for your assistance mate but in the end I just went back to stock using this amazing thread:-
http://forum.xda-developers.com/showthread.php?t=2432476
in conjunction with this amazing video;-
http://www.youtube.com/watch?v=IixQjo_hyz8
So! I am now un rooted and back to stock. Time to start the rooting ana ROMing all over again.lol
Thanks

Glad to here!
You need a space after push
But it usually easier not to enter the location of a file while pushing so cd to the directory first like
cd C:\Users.....
Then once there adb push /nameoffile /locationonphone
But if you don't want to cd, I see you have widows, depending on version you can just right click in the folder your file is located and choose open cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app

Need Help
As I thought I bought LG G2 D-802, but it was D-800 and I accidentally install the lollipop of D802 and now it's in bootlap.... I can only get into fastboot and whenever I try to flash .img of D-800 or D-802 it just stuck at "writing .img"
What to do to unbrick the phone and bring it back to live. I tired the adb and fastboot cmd method on windows 10 and windows 7 but no success. It's just stuck at writing .img file.