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.

[Q] Bricked phone, any way to fix it?

I installed deodexed 4.2.2 stock when i was running deodexed 4.2.1 stock. i felt that it was buggy, so i went into cwrecovery and wiped it and i was about to begin reinstalling deodexed 4.2.2 again when i noticed i forgot to put it onto my phone. then i tried to use my phone, and it would be stuck at "unfortunately, system ui has stopped". it never leaves that popup, so i can't enable usb debugging. i can't use recovery mode, because when i do, the android with a triangle caution sign is there, but no options to select from. i can enter fastboot mode, but that's about it.

CM9onmyMoPho said:
I installed deodexed 4.2.2 stock when i was running deodexed 4.2.1 stock. i felt that it was buggy, so i went into cwrecovery and wiped it and i was about to begin reinstalling deodexed 4.2.2 again when i noticed i forgot to put it onto my phone. then i tried to use my phone, and it would be stuck at "unfortunately, system ui has stopped". it never leaves that popup, so i can't enable usb debugging. i can't use recovery mode, because when i do, the android with a triangle caution sign is there, but no options to select from. i can enter fastboot mode, but that's about it.
Click to expand...
Click to collapse
Reflash a factory image in fastboot, flash CWM/TWRP in fastboot, reroot and reflash the dedexed rom. Your phone isn`t even a bit bricked fortunately.

gee2012 said:
Reflash a factory image in fastboot, flash CWM/TWRP in fastboot, reroot and reflash the dedexed rom. Your phone isn`t even a bit bricked fortunately.
Click to expand...
Click to collapse
How can I reflash the factory image? and where can i find instructions? where can i find the link to download the factory image? thanks

CM9onmyMoPho said:
How can I reflash the factory image? and where can i find instructions? where can i find the link to download the factory image? thanks
Click to expand...
Click to collapse
Look in my signature line 2 and 3.

gee2012 said:
Look in my signature line 2 and 3.
Click to expand...
Click to collapse
thanks. will i lose any personal things such as photos?

CM9onmyMoPho said:
thanks. will i lose any personal things such as photos?
Click to expand...
Click to collapse
Everything will be lost. Considering your phone is bricked there is no way to pull the pictures from your device.
Edit: you might not have to flash full stock, just the system.img that will allow you to overwrite the current system and maintain your sdcard.

i do not know if this is the best place to post this considering i am brand new (i hope so) but i have a soft bricked nexus s 4g that i am trying to fix.
it was loaded with the helly bean 4.2.2 custom rom from nexus hacks (sorry no links) after the reboot it went to a black screen.
what ive tried:
odin: flashing a new rom, this resulted in odin not finding the device (usb debugging is not on and i cant turn it on)
fastboot: (i have all the files but i cant seem to get it set up, i type in adb or fastboot (no device recognized)
nexus root toolkit: (wouldnt find the device and found no options to help with usb debugging)
dfs: (couldnt read the device)
plugging in the phone to the computer: it makes the noise that it is plugged in, comes up as f drive but it is greyed out and i cant click on it (says insert disc)
clock work recovery: i did a full data wipe and required wipes cache and delvik or something along those lines: it reboots into the rom and nothing has changed.. my guess is because there is no back up of the original rom and the cfw is trash, it just wipes the bad rom back to factory and that is still a problem.
pda net: wont recognize the device
galaxy nexus toolkit: nothing useful since the usb debugging is not enabled.
ive worked for 6 hours as of last night to figure this out. i have spent most of those hours in forums and delving further into this phone then id imagined (its not mine) so if there is anyone out there that can suggest anything id appreciate it. this has got me stumped and amazed how such easy fix can really be this complicated.. i will thank any and all answers given to me

theblackrose666 said:
i do not know if this is the best place to post this considering i am brand new (i hope so) but i have a soft bricked nexus s 4g that i am trying to fix.
it was loaded with the helly bean 4.2.2 custom rom from nexus hacks (sorry no links) after the reboot it went to a black screen.
what ive tried:
odin: flashing a new rom, this resulted in odin not finding the device (usb debugging is not on and i cant turn it on)
fastboot: (i have all the files but i cant seem to get it set up, i type in adb or fastboot (no device recognized)
nexus root toolkit: (wouldnt find the device and found no options to help with usb debugging)
dfs: (couldnt read the device)
plugging in the phone to the computer: it makes the noise that it is plugged in, comes up as f drive but it is greyed out and i cant click on it (says insert disc)
clock work recovery: i did a full data wipe and required wipes cache and delvik or something along those lines: it reboots into the rom and nothing has changed.. my guess is because there is no back up of the original rom and the cfw is trash, it just wipes the bad rom back to factory and that is still a problem.
pda net: wont recognize the device
galaxy nexus toolkit: nothing useful since the usb debugging is not enabled.
ive worked for 6 hours as of last night to figure this out. i have spent most of those hours in forums and delving further into this phone then id imagined (its not mine) so if there is anyone out there that can suggest anything id appreciate it. this has got me stumped and amazed how such easy fix can really be this complicated.. i will thank any and all answers given to me
Click to expand...
Click to collapse
You need to be in the bootloader for fastboot to work. Reboot to bootloader and try flashing a recovery.img using this command.
fasboot flash recovery recovery.img

It blows my mind when a user gets all this great help and hasn't given any thanks to the helpers.
Sent from my iPad 4

mitchdickson said:
It blows my mind when a user gets all this great help and hasn't given any thanks to the helpers.
Sent from my iPad 4
Click to expand...
Click to collapse
Happens all the time. I'd have 1000 extra thanks if people new how to use the button or were remotely grateful.

estallings15 said:
Happens all the time. I'd have 1000 extra thanks if people new how to use the button or were remotely grateful.
Click to expand...
Click to collapse
i am sorry i was getting sdk tools set up watching an online tut. i am very greatful for your help my problem was that i had not installed java. so if anyone finds that sdk tools is not coming up. install java and it will work like it is supposed to. i will give a thank you just like i have promised. you guys on this site are the best techs hands down
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
is there a thread on here about adb shell and pushing a new rom onto a nexus s 4g? basically the commands?

theblackrose666 said:
i am sorry i was getting sdk tools set up watching an online tut. i am very greatful for your help my problem was that i had not installed java. so if anyone finds that sdk tools is not coming up. install java and it will work like it is supposed to. i will give a thank you just like i have promised. you guys on this site are the best techs hands down
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
is there a thread on here about adb shell and pushing a new rom onto a nexus s 4g? basically the commands?
Click to expand...
Click to collapse
adb push nameofrom.zip /sdcard/
Sent from my Nexus 4 using xda premium

ran sdk tools tried adb shell and nothing it wont read the device. we tried to push the .tar files to the phone using samsung galaxy nexus tool kit. it didnt work so hes going to take it to a repair but i think the device is toast on the account that usb debugging mode is no where in sight. if it does get fixed ill be sure to report how it got fixed. so anyone else who runs into the problem can get this fixed without a 20 dollar repair bill.

heat361 said:
Everything will be lost. Considering your phone is bricked there is no way to pull the pictures from your device.
Edit: you might not have to flash full stock, just the system.img that will allow you to overwrite the current system and maintain your sdcard.
Click to expand...
Click to collapse
will my computer even detect my phone? usb debugging is off and i can't see the phone's storage from my pc.

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

[ROOT] Guide for the Moto Maxx XT 1225

Updated guide rewritten here: http://forum.xda-developers.com/showpost.php?p=68538891&postcount=1
WARNING: THIS IS FOR THE MOTO MAXX ONLY. I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT MIGHT HAPPEN TO YOUR BELONGINGS.
@respider made a custom recovery for us. It's not even beta, it's alpha. What it means is that it's the first attempt to make a custom recovery. Bugs are expected.
To root, you can use the attached datroot, or SuperSU
Before anything, go to the Motorola website and unlock your bootloader.
1. Download the file attached. Download the recovery
2. Leave the maxxpatched.img in your PC and put datroot.zip in your phone.
3. Open a terminal with adb and fastboot. If you don't know what i'm talking about, Google it.
4. In terminal use:
Code:
adb reboot bootloader
Your phone will reboot and you'll see the fastboot screen.
5. Unzip the recovery and rename the file to recovery.img
Code:
fastboot boot recovery.img
6. Now you'll boot into the recovery. Press simultaneously Power and Vol UP to show the commands.
Some users say the best way is to hold the Vol UP and then press and release the Power.
7. Install > click on the datroot.zip/supersu.zip> let it install > clear cache and dalvik
8. Reboot system.
9. You've got root.

glad to see the recovery is being useful... I hope we manage to get a working TWRP or CWM soon

Do I need to unlock the bootloader first??

ellopr said:
Do I need to unlock the bootloader first??
Click to expand...
Click to collapse
If he says no, he just earned like over 5 grand.

Maxx only were his first words, yes you must unlock your bootloader first.

Did this couple of days back, worked perfectly!! Now waiting for custom recovery and roms
---------- Post added at 10:48 PM ---------- Previous post was at 10:45 PM ----------
Hey since some of us are rooted, any body with knowledge care to look into trying to boost the sound of this baby a little?

tested
NOT WORKING ON DROID TURBO

prking07 said:
Did this couple of days back, worked perfectly!! Now waiting for custom recovery and roms
---------- Post added at 10:48 PM ---------- Previous post was at 10:45 PM ----------
Hey since some of us are rooted, any body with knowledge care to look into trying to boost the sound of this baby a little?
Click to expand...
Click to collapse
Bummed i aint' got root. Anyway. 'mixer_paths.xml' search xda for the proper values to modify. Its super simple and should dramatically increase the volumes. I've used this method on a bunch of phones running stock 4.x.x. Will work on 5.0 also. Tested on my nexus 7 2nd gen.

I'm sure Danger2u was 'reporting' and not 'complaining'.. easy enough to understand. it's way impossible OP would have been trying this on a turbo either,...

There needs to be a Moto Maxx forum. Seeing this in the turbo forum from my turbo just makes me sad.

alexcreto said:
5.
Code:
fastboot boot maxxpatched.img
6. Now you'll boot into the recovery.
Click to expand...
Click to collapse
When I get to step 5 and try to boot into recovery, only a resting android with a red exclamation point is shown.
And a text that says "Ningún comando" which means "No command".
I can't do anything else, after a while the phone reboots itself into my homescreen.
What should I do? What could be wrong?
UPDATE: Ok, after a while I found the solution:
When it shows "no command", press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key. It will display additional menu options.
Click to expand...
Click to collapse
Thanks to sbdc003 in androidforumshttp://androidforums.com/
Thanks @alexcreto, great tutorial!

ImpheOtus said:
When I get to step 5 and try to boot into recovery, only a resting android with a red exclamation point is shown.
And a text that says "Ningún comando" which means "No command".
I can't do anything else, after a while the phone reboots itself into my homescreen.
What should I do? What could be wrong?
Click to expand...
Click to collapse
Oh, my bad...
I'm so used to that I forgot to mention.
Press simultaneously Power and Vol UP

alexcreto said:
Oh, my bad...
I'm so used to that I forgot to mention.
Press simultaneously Power and Vol UP
Click to expand...
Click to collapse
Thank you!
I'm comming from Galaxy SII and S4 and I had never had to do this so it's my first time with fastboot, ADB and custom recoveries.

ImpheOtus said:
Thank you!
I'm comming from Galaxy SII and S4 and I had never had to do this so it's my first time with fastboot, ADB and custom recoveries.
Click to expand...
Click to collapse
Don't worry man, glad you enjoyed.

i understand very well that the guide is for Moto Maxx and NOT for Droid turbo.
but like some cases a method works on other phone that are similar
so i tested and just say that is not working on Droid turbo
in this way other users will not try on their Turbo
and i don t make any flame or other

frankeegee said:
I guess there is a reason for your name, eh? ?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I try, but my xt 1225 is not recognized, no drives installed? I have de MDM 2.4.5, but in Windows 7 not Works. How to download latest version of drives to Motorola xt1225?
adb devices not list my xt1225. I try with minimal adb and fastboot and Android SDK.
How to fix this? I need unlock bootloader.
Thanks
Thanks

muccioli said:
I try, but my xt 1225 is not recognized, no drives installed? I have de MDM 2.4.5, but in Windows 7 not Works. How to download latest version of drives to Motorola xt1225?
adb devices not list my xt1225. I try with minimal adb and fastboot and Android SDK.
How to fix this? I need unlock bootloader.
Thanks
Thanks
Click to expand...
Click to collapse
In the control panel, access the device manager and find your phone among the connected devices.
(Im not running Win right now, so Im gonna try to tell you the steps by memory)
You have to right click and install updates to it.
Instead of letting it find them over the net, you'll choose the option to choose one from the list.
In that list find and pick the Moto Comp ADB
That should make it work.
If I switch to Win later today I'll update this post.
Hope it helps....

alexcreto said:
In the control panel, access the device manager and find your phone among the connected devices.
(Im not running Win right now, so Im gonna try to tell you the steps by memory)
You have to right click and install updates to it.
Instead of letting it find them over the net, you'll choose the option to choose one from the list.
In that list find and pick the Moto Comp ADB
That should make it work.
If I switch to Win later today I'll update this post.
Hope it helps....
Click to expand...
Click to collapse
Many thanks, but,
Do not have Moto Comp ADB in the options.
I try again use SDK, show message Daemon not start. Start daemon in port 5037. Daemon start. But nothing is happening. Don not show my device.

muccioli said:
Many thanks, but,
Do not have Moto Comp ADB in the options.
Click to expand...
Click to collapse
I remember that there was a parent called Motorola and a parent called Android ADB. Did you check both?

help
well im in the same position of the non recognized adb drivers i can't get my unlocked bootloader, and i wanna ask. after achieving root, can i install xposed framwork an then the gravity box, to make some changes??

Problems unlocking bootloader

Hello all, hope you're all doing well. I've come across some problems when trying to unlock the bootloader on the Nexus 6P. Whenever I execute
Code:
fastboot flashing unlock
in the bootloader, my command prompt stays at
Code:
< waiting for device >
and never seems to progress after that. I have also tried
Code:
fastboot oem unlock
, but it still stays on
Code:
< waiting for device >
. I have already done some research on this problem and I have tried to troubleshoot by checking if I have the latest SDK update, and I do, but still no luck. My main purpose of doing this is to install the official 7.1.1 factory image. How can I fix this problem?

Does it say anything in cp when you type devices? Is there a serial number that returns
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
It's either driver issue or maybe you don't have usb debugging checked. Cause it can't see your device

I know that in the beginner's guide, we are told not to use minimal adb. Unlocking bootloader is the first step. Even though my device was recognised, bootloader just simply refused to unlock. I had latest SDK tools installed and everything. So, I resorted to minimal adb and bootloader unlocked without any fuss. For everything else that followed, I used normal fast boot.
You can try this at your own risk. It worked for me. Just sharing.
Edit: if you haven't done anything to your phone, can't you just check for update and install 7.1.1 the normal way, since this is all you want?

Yeah and also if what your using is not up to date (previous adb) you can have problems with that just like that guy up there said

Thanks for reaching out and taking time to try and help out everyone.
dontbeweakvato said:
Does it say anything in cp when you type devices? Is there a serial number that returns
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
It's either driver issue or maybe you don't have usb debugging checked. Cause it can't see your device
Click to expand...
Click to collapse
I've forgot to mention that when I run
Code:
adb devices
when the operating system is up, ADB recognizes it. However, when I'm in bootloader, like you mentioned, it doesn't see it. I've tried switching off and on the "OEM unlocking" and "USB debugging" in the "Developer options", however the problem persists.
tropical cactus said:
I know that in the beginner's guide, we are told not to use minimal adb. Unlocking bootloader is the first step. Even though my device was recognised, bootloader just simply refused to unlock. I had latest SDK tools installed and everything. So, I resorted to minimal adb and bootloader unlocked without any fuss. For everything else that followed, I used normal fast boot.
You can try this at your own risk. It worked for me. Just sharing.
Edit: if you haven't done anything to your phone, can't you just check for update and install 7.1.1 the normal way, since this is all you want?
Click to expand...
Click to collapse
Doubt minimal adb will fix this, but worth a try. I'll also try running ADB on a different computer if that might help. Also, the reason why I want the official 7.1.1 release is because my device is currently running the developer's version. In addition I tried checking for update; no use.
dontbeweakvato said:
Yeah and also if what your using is not up to date (previous adb) you can have problems with that just like that guy up there said
Click to expand...
Click to collapse
Yup. I did mention that my SDK tools are the latest release in my first post.
Edit: Never mind everyone I've found the solution! For some reason the device didn't have the Google USB drivers installed when the device is in the bootloader screen. After days of researching and trial and errors, here is the article that helped me:
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/3/
Note: If you're experiencing this similar problem with the "< waiting for device >" message in the command line, you must acquire the Google USB driver .zip file.
Thanks to everyone that offered help!

Yep driver issues. Classic.