ADB Help - Moto X Q&A

I formatted my system on Stock ROM. I found another stock ROM for sprint now i can't get the ROM i want on my phone because the PC won't read the phone (in CWM recovery). My question is...is there a way to get the ROM on the phone through ADB? Im not all that familiar with it. If so...whats the command?

adb push rom.zip /sdcard

nhizzat said:
adb push rom.zip /sdcard
Click to expand...
Click to collapse
says error device not found

Prestige_DOPE said:
says error device not found
Click to expand...
Click to collapse
You might need to go through a different set of instructions just to make sure the devices is recognized on ADB. Here are my instructions for backing up and restoring app data via ADB, and it includes pretty good instructions on setting up your phone with ADB (well, at least I'd like to think so).

DogzOfWar said:
You might need to go through a different set of instructions just to make sure the devices is recognized on ADB. Here are my instructions for backing up and restoring app data via ADB, and it includes pretty good instructions on setting up your phone with ADB (well, at least I'd like to think so).
Click to expand...
Click to collapse
Well. I have my phone right here and connected to the PC with ADB set up and all. The problem is my PC wont recognize my phone. I tried using fastboot and ADB (i guess they're the same) and it keeps saying the error i stated above your post. The plan is to get the ROM on flashed on my phone. I don't know any other way of doing that. I thought fastboot (adb) would be of assistance but i dont know much about it.

Prestige_DOPE said:
Well. I have my phone right here and connected to the PC with ADB set up and all. The problem is my PC wont recognize my phone. I tried using fastboot and ADB (i guess they're the same) and it keeps saying the error i stated above your post. The plan is to get the ROM on flashed on my phone. I don't know any other way of doing that. I thought fastboot (adb) would be of assistance but i dont know much about it.
Click to expand...
Click to collapse
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media

DogzOfWar said:
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
Click to expand...
Click to collapse
Well my phone wont bootup so thats not going to work but im in the moto x tool kit and i selected to push the ROM onto the sdcard now the whole tool kit froze...is that because its doing something or....

Try a different USB port? Then type adb devices.
Have you downloaded the Motorola Device Manager software? It contains all the necessary drivers. How about the Android SDK?

Prestige_DOPE said:
Well my phone wont bootup so thats not going to work but im in the moto x tool kit and i selected to push the ROM onto the sdcard now the whole tool kit froze...is that because its doing something or....
Click to expand...
Click to collapse
I misunderstood you're original question, sorry. I didn't realize it won't boot at all. I have done what you are asking for my Nexus 7 (which I had messed up). Typically, when you're in the recovery and you plug it into a PC, it will install drivers (separate from the ones when Android OS is running).
Maybe consider trying to use RSD Lite to at least get a functional OS back on there? This page lists drivers to use along with RSD Lite. Maybe that would help get things recognized to the point where you can copy over a ROM?

nhizzat said:
Try a different USB port? Then type adb devices.
Have you downloaded the Motorola Device Manager software? It contains all the necessary drivers. How about the Android SDK?
Click to expand...
Click to collapse
Didnt work...the more things that arent working the more scared i become

DogzOfWar said:
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
Click to expand...
Click to collapse
Installed RSDLite and literally screamed "What the hell is this". A little help here on how this is supposed to work?

Related

New Security Features for ADB in 4.2.2

After upgrading to 4.2.2, some N7 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N7 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 10 as well.
UPDATE: This turns out to be security. See below.
Sent from my Nexus 7 using Tapatalk HD
oldblue910 said:
After upgrading to 4.2.2, some N7 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N7 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 10 as well.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Just waiting for more ppl to confirm this problem. I still stay at 4.2.1
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
No problems here. USB debugging turned on, transferring my data back to my storage now. Tho I did update my SDK tools to the latest the other day. You will see a new pop up message to allow debugging pop up.
Sent from my Nexus 4 using xda premium
rayford85 said:
No problems here. USB debugging turned on, transferring my data back to my storage now. Tho I did update my SDK tools to the latest the other day. You will see a new pop up message to allow debugging pop up.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Ah this may be my issue...I may need to update my SDK tools. I haven't done that in months.
Confirmed breakage usb debugging and adb on my nexus 7
I just installed the 4.2.2 update on rooted stock and after installation root no longer worked. When I went to re-root I could not connect. It showed my tablet but it said it was showing as turned off or unavailable even though it was connected so then I restored back to 4.2.1 unrooted and tryed to connect and same problem. You can connect and send media files but anything else is not working at least for me.
So for my device I can confirm adb and usb debugging seems broken for now. I have the first production run 16 wifi model. I can also say wifi performance seems improved. The signal seems slightly boosted and also seems to stream content smoother farther away from the router. I do not have any bluetooth devices to confirm those fixes. Seems fast and stable for me so far.
I will probably revert back to a custom rom since I like the rooted apps but this release initially seems pretty solid.
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
robbbzilla said:
I just installed the 4.2.2 update on rooted stock and after installation root no longer worked. When I went to re-root I could not connect. It showed my tablet but it said it was showing as turned off or unavailable even though it was connected so then I restored back to 4.2.1 unrooted and tryed to connect and same problem. You can connect and send media files but anything else is not working at least for me.
So for my device I can confirm adb and usb debugging seems broken for now. I have the first production run 16 wifi model. I can also say wifi performance seems improved. The signal seems slightly boosted and also seems to stream content smoother farther away from the router. I do not have any bluetooth devices to confirm those fixes. Seems fast and stable for me so far.
I will probably revert back to a custom rom since I like the rooted apps but this release initially seems pretty solid.
Click to expand...
Click to collapse
There's a new security feature in 4.2.2 to keep "adb thiefs" off your device. http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
After you enable USB debugging and plug the device in, you should get a prompt to allow the computer access to your device.
Sent from my Nexus 4 using xda premium
Wouldn't exactly say "it's broken" considering:
http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
It's a new addition to the ADB security and I'm sure as time passes we'll learn more about the inner workings.
Disclaimer: I installed 4.2.2 this morning just after it was released and I had no issues with ADB or USB debugging in the 2-3 hours I was testing it - I was pure stock across the board from 4.2.1 to 4.2.2 and had no problems.
Bleh, post above me covered it just as I did, only a few seconds faster.
Definitely not a bug
... it's a security feature, as mentioned above. I was pulling my hair out over it at first, until I rebooted my computer and restarted adb, and got the familiar dialog. You have to activate it for each machine you plug it into, it seems.
rayford85 said:
There's a new security feature in 4.2.2 to keep "adb thiefs" off your device. http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
After you enable USB debugging and plug the device in, you should get a prompt to allow the computer access to your device.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I know about the security feature. It did not prompt me. I even turned usb debugging on and off, turned pc and device on and off. I cleared cache and no difference. I did not get any prompt.
Maybe it is just me.
I will reflash and reboot and update it again and see if it works but for me it doesn't work. Not sure about broken just not working for installing root. I can transfer media files fine.
Just run the Android SDK Manager and update everything. Fixed.
Always remember, new version? Use ADB? Update SDK.
Also Wugs Toolkit will work again if you replace the adb files that comes with his kit.
r00t4rd3d said:
Just run the Android SDK Manager and update everything. Fixed.
Always remember, new version? Use ADB? Update SDK.
Also Wugs Toolkit will work again if you replace the adb files that comes with his kit.
Click to expand...
Click to collapse
I will give it a shot. Sometimes I forget to do basic things thinking I know about something I don't. So many more knowledgeable people here. Thanks for the help.
R
oldblue910 said:
After upgrading to 4.2.2, some N7 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N7 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 10 as well.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
It was working for me,I used adb to pull the system of the nexus 7.
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
Updating adb fixed my N10 but not the N7. On the N7, with USB debugging enabled, adb devices shows no devices and will not show up as a media device. If I disable USB debugging, it will show up as a media device, though. Also, adb sideload works fine in stock recovery. Any thoughts?
Sent from my Galaxy Nexus using Tapatalk 2
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
Yes, be sure to update your SDK to API17. There is a glitch on the SDK manager though that I had where I had to refresh the list twice to even have API17 appear. Otherwise it ended at API16/4.1
Sent from my Nexus 7 using Tapatalk HD
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
r00t4rd3d said:
Just run the Android SDK Manager and update everything. Fixed.
Always remember, new version? Use ADB? Update SDK.
Also Wugs Toolkit will work again if you replace the adb files that comes with his
Where can I find the adb file I need to 'replace in wugs kit?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
tdizzle404 said:
Where can I find the adb file I need to 'replace in wugs kit?
Click to expand...
Click to collapse
The data folder of where ever you installed Wugs tool kit too. I replaced 4 files, adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll. You get these 4 files from the Android SDK platform-tools folder after you update the SDK.
-
Perhaps the title of this thread should be changed from
"Warning: 4.2.2 Breaks ADB and USB Debugging"
to
"New Enhanced Security Feature with 4.2.2"
Just a thought..
r00t4rd3d said:
The data folder of where ever you installed Wugs tool kit too. I replaced 4 files, adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll. You get these 4 files from the Android SDK platform-tools folder after you update the SDK.
-
Click to expand...
Click to collapse
Cheers, that was just the info I needed to reapply root after upgrading to 4.2.2. I couldn't work out why ADB could connect but not Wugs toolkit.
ingenious247 said:
Perhaps the title of this thread should be changed from
"Warning: 4.2.2 Breaks ADB and USB Debugging"
to
"New Enhanced Security Feature with 4.2.2"
Just a thought..
Click to expand...
Click to collapse
Exactly ADB Debug has always been a huge glaring security hole for Android devices, some third party apps have been developed or added functionality to disable ADB Debug when the screen is off, etc, to close this hole.
Thanks
r00t4rd3d said:
The data folder of where ever you installed Wugs tool kit too. I replaced 4 files, adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll. You get these 4 files from the Android SDK platform-tools folder after you update the SDK.
-
Click to expand...
Click to collapse
you made it possible for me to be rooted again ... wish i could thank you more than once ... that was getting frustrating ... now after that whole ordeal im considering going back to aokp jb mr1 B3 over staying stock ... but maybe ill just wait ... depends on how long i can stand using the GNEX with a cracked f'n screen lol ... man can the SG4 hurry up??? idk what to do right now .. i need something to flashhhhhhh!!!

[Q] Update witout PC

Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks
ryan4a said:
Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks
Click to expand...
Click to collapse
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.
simms22 said:
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.
Click to expand...
Click to collapse
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option
ryan4a said:
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option
Click to expand...
Click to collapse
thats the easiest way. i dont own a computer nor laptop, so i try to do everything from the phone. but its easier to update via recovery anyways. one thing though, since you are on the stock rom, you will have to wipe your data before flashing a custom rom, since the majority are aosp based, and wont flash over stock.
Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....
doitright said:
Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....
Click to expand...
Click to collapse
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.
ryan4a said:
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.
Click to expand...
Click to collapse
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
For a driver, it isn't a question of seeing it. Its a question of knowing how to talk to it. Further, one of the reasons I suggest he use something that runs linux, is because it avoids this whole driver problem altogether. The other reason is that it is actually consistent, and trivial to determine whether the devices itself actually made a connection, i.e. "dmesg -w", plug it, and see if it says anything.
simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.
ryan4a said:
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.
Click to expand...
Click to collapse
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.
simms22 said:
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.
Click to expand...
Click to collapse
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.
As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!
ryan4a said:
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.
Click to expand...
Click to collapse
i wouldnt be able to help you there, as i dont own a computer. but there are many that can help out. maybe someone else will see this thread..
ryan4a said:
As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!
Click to expand...
Click to collapse
Like I said, TRY LINUX.
No drivers required. Everything is built into the kernel.
Fedora even has an "android-tools" package that includes adb. You just install it with "yum install android-tools" -- even on the livecd (it will install to ramdisk).
Quit screwing around with wondoze and TRY IT.
Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?
killall said:
Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?
Click to expand...
Click to collapse
I'm using Windows 7. Don't think I'll be using Linux either. I'm running out of options for upgrading android versions without a PC. I'm highly considering installing CM12. I'd rather not because it's seems unnecessary on a Nexus device, but don't know what else to do.
There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.
Definitely sounding more and more like hardware
ryan4a said:
There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.
Click to expand...
Click to collapse
I have the same delay when plugging in a charger. But my PC recognizes my N6 without any problems.
On my Droid Maxx I had driver issues. I asked on XDA and got it figured out. I can't check now but have a look at my posts and you may find your answer.
Back to V-Day.

"Error: device not found" when in Recovery - can't figure it out

Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
cam30era said:
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Click to expand...
Click to collapse
Hi cam30era, I tried that but it didn't help. I didn't try it after using Wug's toolkit so it's worth another shot.
Xplicit84 said:
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
Click to expand...
Click to collapse
Hi Xplicit84, I used the Wugs toolkit provided in the NRT to install the proper drivers (it worked fantastic, by the way... mad props to Wug). That didn't help unfortunately.
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
apristel said:
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
Click to expand...
Click to collapse
Hi apristel, yup, tried that too, as I had read that perhaps there may be an issue with USB 3.0 ports. I don't think I have USB 3.0 ports (my laptop is a 2012-era Alienware M17x R3) but I tried a different port for the sake of doing it and it didn't make a difference.
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
teddyearp said:
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
Click to expand...
Click to collapse
Hi teddyearp, I downloaded it from a link on Droid-Life. I don't remember the exact name of the file because I renamed it to something much shorter, but here's where I got it from -
http://www.droid-life.com/2015/03/1...s-for-nexus-devices-4-5-6-7-9-10/#more-163271
Edit - Here's the direct link (the one I used) - http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Any luck, having the same problem and it's driving me nuts.
Mongo23ny said:
Any luck, having the same problem and it's driving me nuts.
Click to expand...
Click to collapse
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
apristel said:
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
Click to expand...
Click to collapse
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Mongo23ny said:
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Click to expand...
Click to collapse
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
apristel said:
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Click to expand...
Click to collapse
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Gage_Hero said:
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
Click to expand...
Click to collapse
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Mongo23ny said:
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Click to expand...
Click to collapse
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
How do I install it properly? I got rid of some old drivers as well
Mongo23ny said:
How do I install it properly? I got rid of some old drivers as well
Click to expand...
Click to collapse
Well you can just change them in the device manager.
I'm willing to use team viewer and show you how. (you'd see everything i do) It's hard to write it out for me right now..just had hand surgery this morning and my hand is still completely numb. If you want to download this and run it http://download.teamviewer.com/download/TeamViewerQS_en.exe
PM me the id and password and i'll connect up and show ya. Just so you know, it'd be a one time thing connecting, your password changes everytime and you'd have to have that running to connect. I own a computer repair store and use it frequently.
apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Lucky Armpit said:
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Click to expand...
Click to collapse
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
apristel said:
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
Click to expand...
Click to collapse
PM sent. Thanks

N6 recognized in fastboot but not in ADB. MAC OS X 10.10.5

I am asking for some help on this. I have always previously used toolkits to root and install recovery but I have a new N6 and I would like to learn to use ADB and fastboot. I have read several help guides and it all seems pretty straight forward except when i query the N6 with "adb devices", it does not return anything. However, if I enter the boot loader and query with "fastboot devices", it recognizes my N6. I have tried several different cables and ports, switching from mtp to ptp, resetting RSA keys, all with no success. I am using the latest adb, version 1.0.32 and my phone is stock 5.1.1. I am not a MAC power user by any means, so if someone can help, please use the simplest terms possible. Many Thanks
Update!....I had used EasyTether a few years ago and it was still in my extensions folder. I had unloaded it but not removed it with no success. Today, I removed it completely and now ADB recognizes my N6!! Thanks to all who commented.
jacksradio said:
I am asking for some help on this. I have always previously used toolkits to root and install recovery but I have a new N6 and I would like to learn to use ADB and fastboot. I have read several help guides and it all seems pretty straight forward except when i query the N6 with "adb devices", it does not return anything. However, if I enter the boot loader and query with "fastboot devices", it recognizes my N6. I have tried several different cables and ports, switching from mtp to ptp, resetting RSA keys, all with no success. I am using the latest adb, version 1.0.32 and my phone is stock 5.1.1. I am not a MAC power user by any means, so if someone can help, please use the simplest terms possible. Many Thanks
Click to expand...
Click to collapse
Did you enable USB debugging in Developer options for Android ADB?
danarama said:
Did you enable USB debugging in Developer options for Android ADB?
Click to expand...
Click to collapse
Yes, I forgot to say that in OP.
jacksradio said:
Yes, I forgot to say that in OP.
Click to expand...
Click to collapse
Is the android screen lock unlocked when you type the command?
jacksradio said:
Yes, I forgot to say that in OP.
Click to expand...
Click to collapse
Follow this guide, works like a champ. It's just like windows, CD to the location that contains your adb and fastboot (tools) and open terminal there.
ADB devices
danarama said:
Is the android screen lock unlocked when you type the command?
Click to expand...
Click to collapse
yes
jawmail said:
Follow this guide, works like a champ. It's just like windows, CD to the location that contains your adb and fastboot (tools) and open terminal there.
ADB devices
Click to expand...
Click to collapse
what guide?
Additional information......I keep seeing a reference to device drivers but I always thought Mac's did not require a driver to use ADB. Am I correct? Also, Android File Transfer works perfectly when I connect my N6 so the computer itself seems to be recognizing it. It also shows up as a Nexus 6 under "USB" in the system report.
This is the guide I used to set up ADB https://www.google.com/url?q=http://forum.xda-developers.com/showthread.php%3Ft%3D1917237&sa=U&ved=0CA4QFjAEahUKEwjvraDV2K7IAhWEoogKHbJPAxc&client=internal-uds-cse&usg=AFQjCNFwMzlRqY6AK7bv2ue6HmnF74sPjw
jacksradio said:
Additional information......I keep seeing a reference to device drivers but I always thought Mac's did not require a driver to use ADB. Am I correct? Also, Android File Transfer works perfectly when I connect my N6 so the computer itself seems to be recognizing it. It also shows up as a Nexus 6 under "USB" in the system report.
This is the guide I used to set up ADB https://www.google.com/url?q=http://forum.xda-developers.com/showthread.php%3Ft%3D1917237&sa=U&ved=0CA4QFjAEahUKEwjvraDV2K7IAhWEoogKHbJPAxc&client=internal-uds-cse&usg=AFQjCNFwMzlRqY6AK7bv2ue6HmnF74sPjw
Click to expand...
Click to collapse
Drivers I'm not sure. For linux, sometimes we have to do extra work (UDEV rules) but I can't say for Mac. What are these references to drivers and where are you seeing them?
danarama said:
Drivers I'm not sure. For linux, sometimes we have to do extra work (UDEV rules) but I can't say for Mac. What are these references to drivers and where are you seeing them?
Click to expand...
Click to collapse
I have been researching and reading guides on this site for almost 2 days just gathering infomation. Today I used the guide i referenced in above post to install ADB on my Mac. Most of the information and guides written on this site are for PC users, so that is where I kept seeing a reference to device drivers, but I just wanted to clarify in case I missed something that was assumed I should already know about using a Mac to root. I am guessing that since my computer recognizes my N6 in system report, that it does not need a driver, but since I am very much a novice, I wanted to ask.
jacksradio said:
I have been researching and reading guides on this site for almost 2 days just gathering infomation. Today I used the guide i referenced in above post to install ADB on my Mac. Most of the information and guides written on this site are for PC users, so that is where I kept seeing a reference to device drivers, but I just wanted to clarify in case I missed something that was assumed I should already know about using a Mac to root. I am guessing that since my computer recognizes my N6 in system report, that it does not need a driver, but since I am very much a novice, I wanted to ask.
Click to expand...
Click to collapse
Fair enough. In my adb and fastboot thread, there is a link to a tool that installs adb and fastboot on mac and that is literally all it does, so I don't think there is anything else for you to do. It seems to me that the issue may be on the device side, but unless you have parallels or bootcamp, I'm not going to be able to help you troubleshoot that.
danarama said:
Fair enough. In my adb and fastboot thread, there is a link to a tool that installs adb and fastboot on mac and that is literally all it does, so I don't think there is anything else for you to do. It seems to me that the issue may be on the device side, but unless you have parallels or bootcamp, I'm not going to be able to help you troubleshoot that.
Click to expand...
Click to collapse
Thank you for trying, I appreciate it and hopefully someone else may have some insight
jacksradio said:
Additional information......I keep seeing a reference to device drivers but I always thought Mac's did not require a driver to use ADB. Am I correct? Also, Android File Transfer works perfectly when I connect my N6 so the computer itself seems to be recognizing it. It also shows up as a Nexus 6 under "USB" in the system report.
This is the guide I used to set up ADB https://www.google.com/url?q=http://forum.xda-developers.com/showthread.php%3Ft%3D1917237&sa=U&ved=0CA4QFjAEahUKEwjvraDV2K7IAhWEoogKHbJPAxc&client=internal-uds-cse&usg=AFQjCNFwMzlRqY6AK7bv2ue6HmnF74sPjw
Click to expand...
Click to collapse
That's what I meant to attach No drivers needed for your Mac btw.
---------- Post added at 07:16 AM ---------- Previous post was at 07:12 AM ----------
OP did you get your ADB working?
jawmail said:
That's what I meant to attach No drivers needed for your Mac btw.
---------- Post added at 07:16 AM ---------- Previous post was at 07:12 AM ----------
OP did you get your ADB working?
Click to expand...
Click to collapse
I did not. However, I was able to root and flash recovery using fastboot. I can't for the life of me figure out why ADB isn't working though. I stumbled across an article which referenced EasyTether and how that can interfere with ADB and I remembered a few years ago, I had used that app on a different phone. I looked in the folder mentioned in the article and sure enough, the file extension was still there, so I unloaded it but even that did not help. I am wondering if there might be something else associated with EasyTether affecting it, but have no idea where to look or even how to completely uninstall it.
SOLVED
How do I marked thread solved?

bootloop with locked bootloader

Hello
So I recently brought a second hand nexus 6 for cheap since it was described as bootlooping and the owner couldn't fix it. I already have a fully working nexus 6 so decided to get this as a potential source for spares assuming I couldn't get it working to be used as a 2nd phone. Having received it today, I found that when turned on, it would get stuck at the white "google" screen and go no further than that. I can access the bootloader and the stock recovery. The bootloader is locked and since the "allow oem unlock" option has been added to lollipop (which I had not even heard of till looking into why I couldn't unlock this device), I can't seem to unlock it, so i'm at a loss. So far i've tried;
-unlocking the bootloader using fastboot oem unlock
-fastboot format cache/data (both saying the BL needs to be unlocked, even though people have said they've managed with it locked)
-flashing roms via fastboot (that obviously didn't work)
-using the "apply update from adb" option to install a stock zip from google (error "signature verification failed")
-same as above, but with custom roms (gave the error "failed to verify whole-file signature")
-same as above again ,but with the OTA of the next android version, in the hope I could continue flashing these till I reached a major one and then it would work (came back saying "system partition has unexpected contents)
-making a nandroid of my working phone, and making a bootable zip of that ("signature verification failed")
I've basically reached a point now where I imagine it's probably not ever gonna work and i'm gonna have to give up, but I figured requesting here can't hurt and I don't wanna give up knowing that something could work, I just never found out about it. I also can't help but think that given I have a working nexus 6, there must be something I can do with that to make the new one work (the only idea I had was the nandroid of it, but there may be something else)
Cheers
Cameron
That phone is not pining for the fjords. It's an ex-phone.
istperson said:
That phone is not pining for the fjords. It's an ex-phone.
Click to expand...
Click to collapse
What do you mean by "pining for the fjords"?
I wondered, is it possible to use wugfresh to push system files to the device (while removing old ones) making it seem to have a clean system partition, then try the ota again via adb sideload. Even if i took the system files from my functioning nexus. The faulty one is on lmy47z at the moment.
call-of-monst3r said:
What do you mean by "pining for the fjords"?
I wondered, is it possible to use wugfresh to push system files to the device (while removing old ones) making it seem to have a clean system partition, then try the ota again via adb sideload. Even if i took the system files from my functioning nexus. The faulty one is on lmy47z at the moment.
Click to expand...
Click to collapse
http://www.google.com/search?q=pining for the fjords
And, I'm sorry, but no, you can't do more with toolkits than with adb and fastboot. Toolkits are just front-ends for those two tools.
You have already tried everything possible, and since the bootloader is locked and you can't boot into Android to enable unlocking, all you have is just spare parts. I'm sorry.
istperson said:
And, I'm sorry, but no, you can't do more with toolkits than with adb and fastboot. Toolkits are just front-ends for those two tools.
You have already tried everything possible, and since the bootloader is locked and you can't boot into Android to enable unlocking, all you have is just spare parts. I'm sorry.
Click to expand...
Click to collapse
Thanks for the help, I've never heard of that phrase before and I thought i had heard them all given what my mums like
When the phone is in recovery, when the update via adb is selected, the phone is detected as an adb sideload device when "adb devices" is entered. Can I push/pull system files when it's detected as sideload? Because I noticed wugfresh supports pushing/pulling of files between the device and pc, but I wasn't sure if it could do system files when the device is detected as sideload
Thanks for the help, i would really like to make it work, and given its not exactly a device I rely on, I'm happy to spend more time working on it and trying more unusual/new ideas
Cameron
call-of-monst3r said:
Thanks for the help, I've never heard of that phrase before and I thought i had heard them all given what my mums like
When the phone is in recovery, when the update via adb is selected, the phone is detected as an adb sideload device when "adb devices" is entered. Can I push/pull system files when it's detected as sideload? Because I noticed wugfresh supports pushing/pulling of files between the device and pc, but I wasn't sure if it could do system files when the device is detected as sideload
Thanks for the help, i would really like to make it work, and given its not exactly a device I rely on, I'm happy to spend more time working on it and trying more unusual/new ideas
Cameron
Click to expand...
Click to collapse
Here it is how sideload works. But as I understood it's only for updates on working phones:
http://www.androidcentral.com/how-manually-upgrade-your-nexus#slide5

Categories

Resources