Database Info

[Q] Xoom won't boot

So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Update: I've been trying different cables. I found one where the computers will see that a devices is connected, but am getting "USB device not recognized" with either set of drivers that I have on both computers. Making progress, but could still use some help.

DiGi760 said:
So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Click to expand...
Click to collapse
I had a problem similar to that about a year ago, somewhere in these forums was the suggestion to remove the SD card and then do a factory reset, it worked for me. My xoom just stopped working, I thought at first it was a flat battery but after charging the symptoms were the same as yours, might be worth searching through the forums if you haven't already

There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?

DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
Sorry can't help , mine is just over 2 years old and except for that one problem have never had any issues so have never needed to even connect it to a PC

DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
I recently discovered these handy files when I needed to return to stock:
4G Xoom (MZ600) Restore
3G Xoom (MZ601/3) Restore
WiFi Xoom (MZ604) Restore
If you need to find out which Xoom model it is, power on whilst holding the volume down button, this will take you in to fastboot. Then (you sound like you'd know how do this, PM me if you don't) use "fastboot getvar all". This will return the model.
Unzip the file above, there's a batch file in there which will install the drivers, then fastboot the firmware over.
If you boot to fastboot, then run the batch file, it installs the drivers, then "adb device", then it asks if your device is connected - it won't show up cos it's in fastboot. Just ignore that and say yes, and it'll start flashing the files.
Sorry if I'm too late - don't visit these boards much these days. Good luck, let me know if this works.

Thanks for giving me something to try. I uninstalled the moto drivers I had and installed the ones included in the zip file and restarted my computers. The Windows 8 computer never recognizes that the xoom is connected in any mode. The 7 machine does see it in fastboot mode but as a "fastboot" device for which it fails to find drivers. When I run fastboot getvar all, all I get is <waiting for device>.
I do know that this is a wifi only (mz604) xoom. Thanks for the image files. If I can get this stupid thing to communicate with a computer, I think I'll be in business.

In fastboot mode (vol -) it won't acknowledge that it's connected. Just fastboot your image over and it will work.

If I try to do anything with fastboot, it just says "< waiting for device >". Fastboot doesn't see a device to flash to.

OK, it's either your cable or your driver. Many cables are for charging only, and have no data lines. I throw those away.
As to drivers, I'm Debian for 15 years so can't advise on Winduhs.
Oh, one more thing: I've noticed that on my old HP laptop I had to use a certain USB port, or else it wouldn't comm with my phone for fundamental actions like loading new firmware.

These were the drivers I used: https://motorola-global-portal.cust...sion/L3RpbWUvMTM4NjM1MjA0NC9zaWQvWEo3SWU5SGw=
They don't seem to be windows 8 certified though.
Sent from my Nexus 5 using Tapatalk

We finally got it. We used DriverEasy to look for drivers because we have a bunch of extra licenses and the drivers we had obviously weren't working. DriverEasy was able to install an "Android Bootloader" driver that must not be part of the SDK. Once that was installed, I was able to use fastboot to flash the images from above. The device is in good working order again and fully updated.
Thanks for all your help.

Always nice to hit the Thanks button for those who've helped.

[Q] ADB Not Detecting Moto G

Ok, I have this fairly serious problem and I've yanking the hair out of my head trying to solve it for the past 4 hours. I've finally resorted to your wonderful help. Please, please help. Allow me to explain.
I've had my Moto G for quite a long time and have run at least 5 custom ROMs on it. Just when I thought I was gettin' the hang of this ROM thing, I've had my first quite serious problem. In the past, the way I have installed my custom ROMs is by first, going to recovery (CWM Recovery) and wiping absolutely everything (data, system, etc.). Then, I would install the ROM and GApps via sideload. Everything was good up until this step. My problem is that ADB won't detect my Moto G.
If I type in "adb devices" I get a blank list. I've installed the Motorola Device Manager and the Google USB Drivers (from the SDK Manager). I've restarted my computer and phone multiple times. I've REinstalled the drivers. I've tried everything. If you guys have any suggestions that would be AMAZING!!!!
P.S. I can see my phone in fastboot when I type in "fastboot devices". But I really need access to ADB.
Thanks,
Mattkx4

[Q] moto g xt1031 isnt listed in adb devices

i have stock rooted moto g 4.4.2 i want to restore it to stock so i can update but it doesnt appear in adb devices. it does show up in device manager as motorola adb interface. adb is enabled on the phone. ive spent 2 nights googling and trying different stuff. i cannot get it to work. i have the same problem for a kindle fire 1st gen. but thats an unrelated note.

lolkidz said:
i have stock rooted moto g 4.4.2 i want to restore it to stock so i can update but it doesnt appear in adb devices. it does show up in device manager as motorola adb interface. adb is enabled on the phone. ive spent 2 nights googling and trying different stuff. i cannot get it to work. i have the same problem for a kindle fire 1st gen. but thats an unrelated note.
Click to expand...
Click to collapse
What is the phone booted into when you're entering the adb command? The phone is booted into Android or in recovery? If you're in bootloader you'll need to use fastboot commands. Such as fastboot devices

lolkidz said:
i have stock rooted moto g 4.4.2 i want to restore it to stock so i can update but it doesnt appear in adb devices. it does show up in device manager as motorola adb interface. adb is enabled on the phone. ive spent 2 nights googling and trying different stuff. i cannot get it to work. i have the same problem for a kindle fire 1st gen. but thats an unrelated note.
Click to expand...
Click to collapse
What os are you using on your PC? I had similar problems on Linux mint until I firgured out I had to add a line of code with the adb install
Sent from my Moto G using XDA Free mobile app

It doesnt show up when its booted into android, recovery or bootloader. I am running windows 7 home premium. Ive tried many different driver installers and nothing has worked.

ive just noticed also that when i have it connected and booted into recovery the driver "Android" couldnt be installed, but if its booted into android or bootloader the drivers are fine. i dont know what driver i should be installing for that, i went back and reinstalled my moto g drivers completely, i have philz touch recovery 6.55

lolkidz said:
ive just noticed also that when i have it connected and booted into recovery the driver "Android" couldnt be installed, but if its booted into android or bootloader the drivers are fine. i dont know what driver i should be installing for that, i went back and reinstalled my moto g drivers completely, i have philz touch recovery 6.55
Click to expand...
Click to collapse
I would suggest uninstalling whatever drivers you have installed. Disconnect your phone, uninstall drivers, restart, install drivers and connect your device then try again. When the phone is connected as mtp, adb, fastboot, it will install drivers for each type.
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050

i have done so and still to no avail. everything driver wise is working, but still the driver "Android" when in recovery could not be installed. still no trace of phone in adb devices when booted or fastboot devices when in bootloader.

lolkidz said:
i have done so and still to no avail. everything driver wise is working, but still the driver "Android" when in recovery could not be installed. still no trace of phone in adb devices when booted or fastboot devices when in bootloader.
Click to expand...
Click to collapse
Where did you DL the adb thing at? You could have a faulty adb download or just didn't install your correct api in the adb suite
Sent from my Moto G using XDA Free mobile app

Lost TWRP and ADB/Fastboot can't see phone to sideload. What can I do?

Basically what happened was:
After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
Booted system to find endless crash dialogs
Rebooted into recovery to find TWRP gone
Did a Full Wipe under stock recovery, hoping it'd fix things
I can now get back into system, but it's glitchy
Neither adb devices nor fastboot devices see the phone
Troubleshooting I've tried:
Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear
I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.
Does anyone know what's going on or any way to remedy the situation?
NOTE: I'm on a Mac

rajah sulayman said:
(crossposting from here as this looks like a more active sub and I'm desperate).
Basically what happened was:
After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
Booted system to find endless crash dialogs
Rebooted into recovery to find TWRP gone
Did a Full Wipe under stock recovery, hoping it'd fix things
I can now get back into system, but it's glitchy
Neither adb devices nor fastboot devices see the phone
Troubleshooting I've tried:
Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear
I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.
Does anyone know what's going on or any way to remedy the situation?
Click to expand...
Click to collapse
It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.
Sent from my PH-1 using Tapatalk

sd_shadow said:
It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.
Click to expand...
Click to collapse
But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.

rajah sulayman said:
But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.
Click to expand...
Click to collapse
do you know how to check which drivers are selected.?
Sent from my XT1254 using XDA Labs

sd_shadow said:
do you know how to check which drivers are selected.?
Click to expand...
Click to collapse
Is it through the Android Studio SDK manager? I remember using that way back when to get everything set up, but I haven't really used it since then.

Actually I just remembered that Mac don't need drivers, right? Per Google:
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. Instead see Using Hardware Devices."

Update: Pulled out my Windows laptop and installed everything (drivers, Android Studio, et al) to see if I'd have better luck there.
To test, I first plugged in my working Nexus 5X. Windows immediately recognized it. Pulled up a prompt and adb devices saw the phone no problem.
Unplugged the Nexus and plugged in my Pixel XL. Nothing. No "hardware plugged in" chime, nothing listed under Device Manager, nada. Likewise, the phone itself doesn't acknowledge that it's been plugged in because there's no Android System pulldown.
If it were a driver issue, Device Manager would still at least be able to see the phone (it just wouldn't know what it was). But I'm getting absolutely nothing.
I can only assume that the problem is indeed with the phone itself. I don't know what the problem is exactly, but I know it wasn't there before all of this. Either way, this means my only hope for a fix would have to be through the phone itself. But since Stock Recovery doesn't seem to offer me many options, I have no clue what to do next.
Is there some sort of "secret" key combo or command or something that'll do a low-level format of the phone or something? I'm grasping at straws here, I know, but I honestly don't know what else there is I can do.
-------
Update 2: If I plug it in while in Bootloader, Windows recognizes that a device was connected, but as an "Unknown USB Device (Device Descriptor Request Failed)"
None of the solutions I can think of (or Google) seems to work. Has anyone heard of this problem before? I'm vainly hoping there's a fix out there that I just haven't found yet.

Fastboot waiting for any device

Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay, probably need to reinstall recovery and flash a clean rom again. Try the "fastboot boot recovery.img" command and it's giving me a "waiting for any device". Googling says it's a driver error, but that's strange because I have used my phone on this computer before with ADB and fastboot. Fastboot and ADB commands work fine on my Oneplus 3T.

A week ago I also had the problems after the Magisk update. But connecting to the PC worked normally for me. Once you've installed the drivers, there shouldn't be any problems. You could use a different cable.
Incidentally, Magisk only messed up the boot image. It is sufficient if you flash your boot.img, then the twrp.zip, reboot into recovery, then the magisk.zip.
That was completely enough for me. Cell phone works normally again, without data loss.
Good luck!

Yeah that's exactly what I am trying to do, I can't even flash the boot.img to get into recovery, my computer won't recognize the device for some reason now. Do you know where I can find the drivers? I could only find shady 3rd party sites. Thanks!

Tried installing drivers from here, no change.
Download Latest OnePlus USB Drivers for Windows and Mac
Download The Latest OnePlus USB Drivers For All OnePlus Android Smartphones. We Have Included USB drivers for Both Windows And Apple MAC OS Users. Download Links Given Below.
www.getdroidtips.com

This is installed and works with me

ghost323 said:
This is installed and works with me
Click to expand...
Click to collapse
No joy, looks like that's the same file as the one I downloaded. Thanks for your help anyways.

Now I can't even turn my phone off lol. It woke itself up this morning magically and now whenever I hit power off in fastboot it just boots up again into fastboot. Might have to send it in...the horror

Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?

ghost323 said:
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
Click to expand...
Click to collapse
Haha yeah, it's like your kid who refuses to go to bed and is throwing a tantrum. Yeah two different computers that are known to have worked with this phone in the past (how I unlocked the bootloader in the first place). Different ports, different cables. It seems like I'm having the same issue that a lot of other people are having with the last Magisk update, except they're able to flash the recovery image in fastboot to get back running.

This is a ****ty situation! That was really a nasty magisk update. I wonder why its consequences are so different, even though it is the same cell phone.

fastboot cannot recognize device but adb can
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both. Oneplus 7 pro is running 10.3.0GM21AA >fastboot devices >adb devices List of devices attached 966c8016...
forum.xda-developers.com
Look at this. Maybe it will help you so that your computer recognizes the cell phone again.