Database Users

problems getting adb to read in recovery mode?

on the tutorial for how to root nexus 7 it says to try killing the sever and starting it again but no luck it will not work in recovery mode i managed to unlock it but thats it any ideas?

Try using msambra root toolkit. Worked perfect for me. Simple and straightforward. If you already unlocked, then make sure you choose that option. It'll flash superuser or superSU(your choice) to your device. It'll only take a min. Or two and you're done. Here's the link to that thread.
http://forum.xda-developers.com/showthread.php?t=1742919
I'm assumings you have adb drivers already installed. If not, they are included in the toolkit. Alot more simple to install than other kits. Just choose if you're using 32 or 64 bit wondows, then click on your one and it'll install needed drivers for aadb to work properly with your nexus. Nothing that has do with servers is needed with this toolkit. Also has link to YouTube video in that thread for reference.

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

[Q] How do you brick your phone?

Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice

dreseansr said:
Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
Click to expand...
Click to collapse
Nexus devices are hard to brick. Just to be on the safe side, just follow the videos, follow instructions and you'll be fine.
"Riddle me this, Riddle me that."

It's importanto to be sure that alla drivers are working correctly and if you are able root manually from the command line ( it's easy ).I'm going to root too,and I'm trying to understand if my drivers are working but with no results

Federico_96 said:
It's importanto to be sure that alla drivers are working correctly and if you are able root manually from the command line ( it's easy ).I'm going to root too,and I'm trying to understand if my drivers are working but with no results
Click to expand...
Click to collapse
Just install the WUG's nexus root kit, all needed drivers are included there. Or if you want to do it manually, download the adb and fastboot drivers.
Or you can try this: http://forum.xda-developers.com/showthread.php?p=42878983
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"

I used wugfresh's toolkit for the n7 and the n4 with absolutely no trouble. Other than not letting the drivers install automatically drivers. Once I let them go on auto it worked like a charm windows xp.
Sent from my Nexus 4 using Tapatalk 4 Beta

Th3RiddL3r said:
Just install the WUG's nexus root kit, all needed drivers are included there. Or if you want to do it manually, download the adb and fastboot drivers.
Or you can try this: http://forum.xda-developers.com/showthread.php?p=42878983
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Click to expand...
Click to collapse
Is there a way to check if adb has been installed correctly? I'm using wugfresh toolkit,i already made the drivers test and it went fine,but i don't know if adb has been included in this test too,and I noticed that even if the drivers test said that all is ok,in my device manager i still see a yellow exclamation mark near to the MTP device...another question,if i plug my device with usb debugging on, should i be able to transfer files in the memory? beacuse i can't see my device
With a command prompt i moved in the adb directory and typed adb devices,it said daemon not running,daemon started running successfully,and it showed a serial number and "offline", is this correct?

dreseansr said:
Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
Click to expand...
Click to collapse
download the 4.2.2 factory images and keep them handy for emergencies, setup and learn fastboot, and never flash anything for another device/not meant for the N4. if you do this, you will never brick it.

Federico_96 said:
Is there a way to check if adb has been installed correctly? I'm using wugfresh toolkit,i already made the drivers test and it went fine,but i don't know if adb has been included in this test too,and I noticed that even if the drivers test said that all is ok,in my device manager i still see a yellow exclamation mark near to the MTP device...another question,if i plug my device with usb debugging on, should i be able to transfer files in the memory? beacuse i can't see my device
With a command prompt i moved in the adb directory and typed adb devices,it said daemon not running,daemon started running successfully,and it showed a serial number and "offline", is this correct?
Click to expand...
Click to collapse
You need to update the adb driver if it's showing offline. Try searching the new updated adb driver in google. I think it's also here in the N4 forums, not quite sure where.
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"

Th3RiddL3r said:
You need to update the adb driver if it's showing offline. Try searching the new updated adb driver in google. I think it's also here in the N4 forums, not quite sure where.
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Click to expand...
Click to collapse
OK so now typing adb devices i get a serial number and "device", i suppose that now adb is working,and now i installed mtp drivers using this guide

Th3RiddL3r said:
Just install the WUG's nexus root kit, all needed drivers are included there. Or if you want to do it manually, download the adb and fastboot drivers.
Or you can try this: http://forum.xda-developers.com/showthread.php?p=42878983
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Click to expand...
Click to collapse
what's the difference between auto root and manual? which is better?

Questions: 1.Difference between manually rooting and auto-rooting
2. This thing say we can root without unlocking bootloader, is that really legit and if so will our stuff be wiped or no?
3.How to back up my phone? Which program to use?
4.Long does it take to root?

dreseansr said:
what's the difference between auto root and manual? which is better?
Click to expand...
Click to collapse
1) Download either Clockwordmod http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-mako.img or TWRP http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img recovery image and move the file to the folder that contains adb and fastboot.
2) Open a command prompt in the folder that contains adb and fastboot type fastboot oem unlock and install a custom recovery by typing fastboot flash recovery recovery-image-name.img.
3) Boot into recovery and install SuperSU.zip downloaded from http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip.
4) Reboot your phone, search the Play Store for BusyBox, and install BusyBox.
Now your Nexus 4 is fully rooted. If you intend to flash a custom ROM, superuser and busybox will be included in the ROM.

BobWalker said:
1) Download either Clockwordmod http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-mako.img or TWRP http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img recovery image and move the file to the folder that contains adb and fastboot.
2) Open a command prompt in the folder that contains adb and fastboot type fastboot oem unlock and install a custom recovery by typing fastboot flash recovery recovery-image-name.img.
3) Boot into recovery and install SuperSU.zip downloaded from http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip.
4) Reboot your phone, search the Play Store for BusyBox, and install BusyBox.
Now your Nexus 4 is fully rooted. If you intend to flash a custom ROM, superuser and busybox will be included in the ROM.
Click to expand...
Click to collapse
Wait I'm confused, Clockwordmod is to backup my stuff?

dreseansr said:
Wait I'm confused, Clockwordmod is to backup my stuff?
Click to expand...
Click to collapse
Clockworkmod and TWRP are recovery software. Either can be used to perform nandroid backups of all system files, applications and data, and boot image installed on the phone at the time of the backup. Recovery may also used to flash custom ROMs or kernels and to install some software directly from a zip file and to wipe cache, Dalvik cache, and system before flashing a new ROM.
At a minimum, you should perform a nandroid backup of your phone when you have it rooted and have all essential programs installed so you have an image of your phone in a working state as insurance in case you do something wrong and need to restore your phone to normal operation.

BobWalker said:
Clockworkmod and TWRP are recovery software. Either can be used to perform nandroid backups of all system files, applications and data, and boot image installed on the phone at the time of the backup. Recovery may also used to flash custom ROMs or kernels and to install some software directly from a zip file and to wipe cache, Dalvik cache, and system before flashing a new ROM.
At a minimum, you should perform a nandroid backup of your phone when you have it rooted and have all essential programs installed so you have an image of your phone in a working state as insurance in case you do something wrong and need to restore your phone to normal operation.
Click to expand...
Click to collapse
hm ok so is there any video showing the steps of how to back up my phone or using this programs?

You need to do more research on your own all this info u need is on this site and on YouTube please read for yourself
Sent from my Nexus 4 using Tapatalk 4 Beta

dreseansr said:
hm ok so is there any video showing the steps of how to back up my phone or using this programs?
Click to expand...
Click to collapse
You Tube videos for using TWRP to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=laBKgRCpMeI and at http://www.youtube.com/watch?v=bGgTkzLHzHo respectively.
You Tube videos for using Clockworkmod to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=36cihz4l-vk and at http://www.youtube.com/watch?v=Gvi0cbMz1V8 respectively.

dreseansr said:
Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
Click to expand...
Click to collapse
Well I think there is an forum rule that says we're not supposed to discuss about things such as how to brick your phone. And the most, if not all, of the bricks on the Nexus 4 are recoverable anyways.
That being said, before you flash anything, especially kernel or bootloader, be absolutely sure the file is made for your device
Sent from my Nexus 4 using xda app-developers app

nelsonator1982 said:
You need to do more research on your own all this info u need is on this site and on YouTube please read for yourself
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
If you have read the thread you will see that i've done that already but since he/she is informing me on a program that they used, i am simply asking for a video that showed them how to do it so i know everything is legit.

BobWalker said:
You Tube videos for using TWRP to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=laBKgRCpMeI and at http://www.youtube.com/watch?v=bGgTkzLHzHo respectively.
You Tube videos for using Clockworkmod to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=36cihz4l-vk and at http://www.youtube.com/watch?v=Gvi0cbMz1V8 respectively.
Click to expand...
Click to collapse
Thank you

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

[Q][Answered] Have I screwed up? (Fastboot not seeing the Tablet)

Okay, I bought a Nexus 10 off someone, and they had already rooted the device. Bootloader is unlocked and whatnot. That's where my problems start. I can not for the life of me get fastboot or adb to see this thing.
Here's my info:
Google Nexus 10 (Samsung)
ClockworkMod Recovery 6.0.4.3
Bootloader Version: MANTALJ12a
Windows 8.1 Pro x64
Full Android SDK
Samsung drivers installed (I rooted my Galaxy Nexus without issue).
USB has a direct connection
Before I decided to format and try to install a stock .zip, I could access the tablet as a media (That's how I got the .zip on the device).
Steps to how I got here:
Flashed Cyanogenmod 10.2 or whatever. Didn't want JB, wanted Lollipop.
Pushed the (what I thought was correct) .zip to /sdcard
Booted into recovery
Formatted /system, /cache, /data, /factory
Reflashed the .zip
Failed. Miserably.
I named the .zip as something simple and just overwrote it. I wouldn't have this issue if it wasn't for that. I know I did a bad there.
But still, nothing I can do will get fastboot/adb to see the device. It makes the sounds that it's connected when I plug it in. I'm using an elevated prompt as well, but it will not pull the device. How do I get myself out of this hole? If I could push a new .zip to somewhere on /sdcard I could at least use the recovery to reflash.

Wrong device ? [emoji14]

Khaon said:
Wrong device ? [emoji14]
Click to expand...
Click to collapse
No, I was going to put it in the general help thread, may be better here since this may not be a simple question (Please prove me wrong).

Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.

gothmog1065 said:
Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.
Click to expand...
Click to collapse
You don't have access to have os then? How did you push your zip if you don't have access to adb?
I have seen people who couldn't get adb and fastboot working on their windows and switching to another computer solved the issues.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.

Khaon said:
You don't have access to have os then? How did you push your zip if you don't have access to adb?
Click to expand...
Click to collapse
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
Click to expand...
Click to collapse
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Click to expand...
Click to collapse
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.
Click to expand...
Click to collapse
It's a Wifi tablet, no cellular data and IMEI etc.
edit: As a side note, I've been thinking about reformatting my computer, though it'll be a huge pain to get it back to here as I've got to go from 7 - 8.0 - 8.1 on the upgrade paths to get it back here again.

gothmog1065 said:
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Click to expand...
Click to collapse
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
Click to expand...
Click to collapse
Installed universal adb drivers? Nothing shows up in the device manager?
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Click to expand...
Click to collapse
You might try odin.
Usb mtp doesn’t work from recovery?

Khaon said:
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Installed universal adb drivers? Nothing shows up in the device manager?
?
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.

gothmog1065 said:
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.
Click to expand...
Click to collapse
Did you deleted all samsung vendor, etc from the usb program, you know what i am talking about?
You can force to install drivers from device maanger, don't remember how, when installing manually, you must do some step , install from floppy or file, get inf files or so, you will get a prompt telling you it might be harmfull and it will force installation. Might be the solution?
The culprit is definitely software-sided.
Does the mount internal storage (mtp) work?

Would this be easier in Linux? I could pop open my Ubuntu VM and do this if it'd be easier?
Beyond that, are you telling me to try and install the drivers from the driver files created by the Samsung vendor .exe?
I have tried to 'mount USB storage' from recovery, but it doesn't seem to do anything. /system /cache /data /factory are all mounted ATM and nothing is showing.

You've already got more advanced advice than I can offer but when I tried to update to 5.0.1 from 4.4.4, I couldn't get my windows computer to see my device. I was trying the adb fastboot but it I couldn't get it to work.
Wug's toolkit got it all straightened out (http://forum.xda-developers.com/showthread.php?t=2015467)[*]. There was an option on his interface that asked whether the device was working properly or not (a!most missed it as a choice). Checked that box and it went through much of the process I had done (installing adb, updating drivers etc). Long story short, it worked.

Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?

gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
You're right. I confused the heading but choosing that option got my computer and my Nexus "talking." After installing the factory image I think you can then push a cusom ROM to you Nexus (http://forums.androidcentral.com/go...acks/264619-wugs-nexus-toolkit-questions.html).

gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
Problem solved ? I always had less issues with fastboot and adb on Linux you can install a ppa that install for you adb and fastboot
Hovewer if you are using 2.8.2.0 you will need 1.0.32 and the ppa includes 1.0.31 so only adb sideload fails.
Sent from my nexus 10