Bricked Xoom built a program cable but fails to install drivers when connected. I tried going to devices and troubleshooting searched for drivers but none were found.
Any idea of what i can try next?
Have you downloaded drivers from motodev?
Prior to the bricking, could you connect to your computer?
It will connect but it just shows up as APX in the devices and says its missing drivers. I went to moto and downloaded USB drivers but still does the same thing. The xoom does nothing when plugged in.
Windows 7 or XP?
Sent from my MB860 using xda premium
Windows 7. I did manage to get some drivers to install. Don't know if their the rite ones though. I clicked on let me choose such drivers, found some in SDK for htc,Samsung,and Motorola. Chose Motorola and it had several adb drivers clicked next and they installed. So now it just shows it as APX in the devices but no longer has the missing drive issue. Still no sign of life when trying adb or fastboot.
What mode is it in when you are attempting to connect it to your computer?
Sent from my MB860 using xda premium
It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.
ericman77 said:
It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.
Click to expand...
Click to collapse
I have the same problem.. doing my head in trying to fix it. I have tryed everything i can think off. Anyone out there know how to fix it in apx mode using a factory cable ?
Did you ever find a solution to this issue?
I currently have a black-screen bricked Xoom. I have tried all the 'soft-unbrick' methods, I can _NEVER_ get anything to appear on screen. The only signs of life are with a 'factory cable'
With this 'factory cable' I am able to see 'APX' in my Device Manager. I can make it 'reboot' by doing the volume up + power which makes the device disappear and reappear. No other key combinations have any effect.
I am able to install either the Nvidia NVFlash drivers. However NVFlash doesn't work. Possibly due to a lack of SBK (Secure Boot Key).
I am also able to install the "Universal Naked Driver" which makes the device show up as an "Asus Transformer APX" However neither fastboot or adb seem to see the device.
Does anyone have any suggestions how I can unbrick my Xoom?
ericman77 said:
Bricked Xoom built a program cable but fails to install drivers when connected. I tried going to devices and troubleshooting searched for drivers but none were found.
Any idea of what i can try next?
Click to expand...
Click to collapse
ericman77 said:
It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.
Click to expand...
Click to collapse
darchiuk said:
I have the same problem.. doing my head in trying to fix it. I have tryed everything i can think off. Anyone out there know how to fix it in apx mode using a factory cable ?
Click to expand...
Click to collapse
qoole33 said:
Did you ever find a solution to this issue?
I currently have a black-screen bricked Xoom. I have tried all the 'soft-unbrick' methods, I can _NEVER_ get anything to appear on screen. The only signs of life are with a 'factory cable'
With this 'factory cable' I am able to see 'APX' in my Device Manager. I can make it 'reboot' by doing the volume up + power which makes the device disappear and reappear. No other key combinations have any effect.
I am able to install either the Nvidia NVFlash drivers. However NVFlash doesn't work. Possibly due to a lack of SBK (Secure Boot Key).
I am also able to install the "Universal Naked Driver" which makes the device show up as an "Asus Transformer APX" However neither fastboot or adb seem to see the device.
Does anyone have any suggestions how I can unbrick my Xoom?
Click to expand...
Click to collapse
Dear all,
I got the same thing.
I installed the driver from nvflash drivers. And I ran several commands to try, it showed no bootloader was specified. I guess maybe I damaged my bootloader. Does any of you unbricked your xoom?
Here is a link to my post, which showed my tries.
http://forum.xda-developers.com/showthread.php?t=1838002
Anyone could help us? Thanks a lot.
Wow, i've been on that Wagon for a long time. http://forum.xda-developers.com/showthread.php?t=1838002 Now I just gave up cause I don't think anyone has gone past installing the drives after it detecting as APX.
Thanks for your kindly reply.
So, you mean there is no hope.
Actually, I sent it to another MOTO local service center again. After one week, they told me they tried to restore the software in two steps, but only the first could be done, and then went back to brick again. And they thought there might be some damage on “the kit” of motherboard, and if I want to repair, the whole motherboard must be replaced totally.
If you still have the bricked XOOM, would you please try to draw the BCT and config.cfg from your device?
Again, I did another search. Although there is no available bootloader.bin, BCT and config.cfg for XOOM, I guess there might be possible to use SAMSUNG P7510's files, because the hardwares are almost same, and it's heard that P7510 could use XOOM's ROM.
Sent from my ZTE U970 using xda app-developers app
Related
i've just flashed prime 1.9 mobile data ver over CWM. have to say the whole proccess ended faster then normal. after rebooting i get nothing. black screen.
tried holding power for 10-20 sec, even 30. nothing.
so tried going into APX mode and nvflashing through pc. but when i'm doing that the pc recognizing it as "unknown device" and not an APX.
so i've realy got nothing. and i cant communicate with pc to nvflash.
obviously i tried manualy install APX driver from nvflash folder. but still get unknown device.
please help!
what should i do?
im not a newbie i've done those things dozens of times. (nvflash, apx, cwm..) but i've never faced a totall brick
so you already had nvflash connected to device before it is bricked so you are sure all is setup corectly ?
cause it is a real pain in the but that when the tf is in apx it just looks dead.
If that is the case than I dont have a clue because nvflash is kind of a last resort
Uninstall the drivers, reboot, install the drivers again and try for apx, if its a no go then reboot pc and try for apx.
Sorry i cant be more help.
Edit - Make sure the TF actually has some juice in it. Leave it on charge for a couple of hours.
i've done nvflash before and i'm familiar with the procedure.
about uninstalling drivers and rebooting, maybe will help altough i've tried going into apx with other computers with no success aswell.
please help!
no one knows maybe theres a reset button or something inside the transformer. just a way to bring APX back!
if you can get back into revovery, try to flash again.
check md5sum yo make sure you have a good file
Sent from my Transformer TF101 using Tapatalk
thats the thing. ive got nothing. the screen just stays black no matter what. so i thought maybe APX will rescue me but i now dont have even APX. is it even possible?
apx mode on ming leaves the screen blank and off. leave your tablet on a charger for a while to make sure it is charged, a couple of hours at least reduce as many errors as you can. if you have the apx drivers installed right when you plug it in to windows you will hear a beep saying you plugged a device in. You could also try to install the apx drivers again.
http://forum.xda-developers.com/showthread.php?t=1123429
this will tell you how to do it.
http://forum.xda-developers.com/showthread.php?t=1185104
this thread has better instructions though.
have you ever installed nvflash drivers before...or is this the first time?
ive already told yall. i done this proccess before (nvflash and going into APX. i know the screen should stay off and only the computer should say APX device been detected or something like that. but the message im getting from pc is "unknown device" connected. and when i try to manually install the apx drivers from device manager by directing it to the nvflash folder where the drivers should be- it just stays unknown device and says that the most updated drivers for it is already installed
I'm having the same issue. I can't get into APX mode anymore. Just appears as "Unknown Device" in device manager.
I'm currently running PRIME 1.7. My clockwork recovery also fails to recognize the SD card, so I can't flash a new ROM that way either. I really want to switch to Revolver, but with no APX, it's not going to happen.
hmm maybi you can try it on a other pc. if you have luck it can be recognizedd
Unknown Device......?
Uninstall the drivers, reboot pc, reinstall fresh drivers, reboot pc, connect TF101
Next time use the search function or google.
I am working on a LG G2x LG-999dw which seems hard bricked. I've tried to NV Flash on multiple machines (with multiple cables) but it doesn't work. I got so desperate that I did a clean install of WinXP Pro one of my machines... just to make SURE it wasn't a driver or Windows update issue.
I've scoured our Forums and google'ed til my fingers hurt. NOTHING I have found has made a difference.
The computers recognize the G2x in APX mode. I get the NVidia Recovery driver loaded, no problem. When I start the flash.bat (included with the 3 different NVFlash based packages I've found) it loads the Fastboot, but then stalls at on 'Waiting for Bootloader to initialize".
I was hoping to push the recovery.img via ADB. Even TonyP's modified driver is loaded, ADB still doesn't see the device.
I've seen more than a few posts from people in situations like this one. However no one really says HOW they got it to work.. just that they did.
This is my boss's phone AND my review is next week!
Please help me?
Thank you in advance!
Maybe the files youre trying to push are corrupted? I jad this little problem last night
Sent from my LG-P999 using xda premium
Yup. Make sure your nvFlash software isn't corrupt. To my knowledge, our phone is pretty damn near impossible to "brick". nvFlash has always been our savior.
New2my8125 said:
Yup. Make sure your nvFlash software isn't corrupt. To my knowledge, our phone is pretty damn near impossible to "brick". nvFlash has always been our savior.
Click to expand...
Click to collapse
Each time I have tried, I have downloaded them anew. I downloaded the files again at home last night. I brought them into work today via thumbdrive. Same result. Do you have a link to a set of files you KNOW is good?
I have tried One-Click, CWM via NVFlash, and AIO Wipe Tool. They ALL respond the same way. They ALL hang at 'Waiting for Bootloader to initialize".
i know we can do ADB when the phone is in CWM recovery, however, is it even POSSIBLE to get ADB communication when the phone is in this state?
karlnorth said:
Each time I have tried, I have downloaded them anew. I even downloaded the files again at home and brought them into work today via thumbdrive. do you have a link to a set of files you KNOW is good?
Click to expand...
Click to collapse
These are the ones I've used in the past.
http://forum.xda-developers.com/showthread.php?t=1056847&highlight=nvflash
New2my8125 said:
These are the ones I've used in the past.
http://forum.xda-developers.com/showthread.php?t=1056847&highlight=nvflash
Click to expand...
Click to collapse
I'd downloaded those countless times in the past week. My finger tips are bruised from holding the buttons down. lol I've resorted to using thick rubber bands to hold them down instead. :silly:
I wish there were some way to just get ADB working in this state. Then I could just push the recovery file across, etc.
Even with adb, it's impossible to install via adb or terminal. NVflash is the only way.
Have you try this? http://forum.xda-developers.com/showthread.php?t=1248644
Sent from my LG-P999 using xda premium
gripninerz said:
Have you try this? http://forum.xda-developers.com/showthread.php?t=1248644
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Yes, that is one of the methods I have tried. It fails in exactly the same way.
Tried a different cable? Different computer?
Usually different cable/USB does the chick.
It happened to me and wouldn't load the boot loader until I used a different cord.
Your using one of the usb slots directly on the motherboard right? (at the back)
Sent from my LG-P999 using xda app-developers app
You'll probably have to reinstall the firmware, etc., with a .kdz file if you can't reload the kernel and rom. Which version of the baseband or Android was your boss using? Also, uninstall the LG drivers and reinstall them.
tahahawa said:
Tried a different cable? Different computer?
Click to expand...
Click to collapse
My original post states "I've tried to NV Flash on multiple machines (with multiple cables) but it doesn't work."
This thing is driving me absolutely insane. I'm not a newb. I've been doing this for a LONG time. This is only the 2nd phone I've worked with that had caused me this much headache and consternation. (The first was an older Verizon Droid)
Core Memory said:
You'll probably have to reinstall the firmware, etc., with a .kdz file if you can't reload the kernel and rom. Which version of the baseband or Android was your boss using? Also, uninstall the LG drivers and reinstall them.
Click to expand...
Click to collapse
I have tried the .KDZ file method already. I can't get the app to recognize that the phone is connected. Is there some trick to that? I've tried the APX & modded ADB drivers on 3 different machines. Neither driver allowed the app to "see" the phone in this mode.
im having this problem exactly like yours
karlnorth said:
I have tried the .KDZ file method already. I can't get the app to recognize that the phone is connected. Is there some trick to that? I've tried the APX & modded ADB drivers on 3 different machines. Neither driver allowed the app to "see" the phone in this mode.
Click to expand...
Click to collapse
Did you try a different USB cable? Is the phone in "USB debugging" mode? If the drivers are installed correctly, your phone should be recognized.
Core Memory said:
Did you try a different USB cable? Is the phone in "USB debugging" mode? If the drivers are installed correctly, your phone should be recognized.
Click to expand...
Click to collapse
Yes, I've tried 3 different cables on 4 different PCs. I've tried 2 different batteries from a pair of working G2x's. The phone DOES NOT BOOT. It stays on a Black Screen. If I hold both buttons and plug in the USB the PC recognizes it in APX mode. That's ALL it does.
karlnorth said:
Yes, I've tried 3 different cables on 4 different PCs. I've tried 2 different batteries from a pair of working G2x's. The phone DOES NOT BOOT. It stays on a Black Screen. If I hold both buttons and plug in the USB the PC recognizes it in APX mode. That's ALL it does.
Click to expand...
Click to collapse
This is without the battery, right? To properly use NVflash, it's without the battery. Except for rare cases. Either way the NVFlash ROM that was linked here previously should do the trick. If even without the battery (And volume buttons held) it does this, then the device itself might've been a lemon from the start. Because I've never had trouble on linux or windows NVFlashing.
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
AdvanceArg said:
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
Click to expand...
Click to collapse
PC operating system?
Drivers for fastboot and adb loaded?
Look at my signature about universal naked drivers.
Also about getting into your bootloader menu.
APX will be useless to restore.
tobdaryl said:
PC operating system?
Drivers for fastboot and adb loaded?
Look at my signature about universal naked drivers.
Also about getting into your bootloader menu.
APX will be useless to restore.
Click to expand...
Click to collapse
W7 x64
Used exactly those naked drivers.
Cant access to bootloader.
AdvanceArg said:
W7 x64
Used exactly those naked drivers.
Cant access to bootloader.
Click to expand...
Click to collapse
Did you actually use the link to attempt the bootloader access?
Did the drivers properly install?
Do you have an sdcard for this tablet?
tobdaryl said:
Did you actually use the link to attempt the bootloader access?
Did the drivers properly install?
Do you have an sdcard for this tablet?
Click to expand...
Click to collapse
i installed ADB Interface Drivers, but i cant Android Bootloader Interface Driver because 'vol down + up + power' doesnt work.
AdvanceArg said:
i installed ADB Interface Drivers, but i cant Android Bootloader Interface Driver because 'vol down + up + power' doesnt work.
Click to expand...
Click to collapse
I'll assume that means all ten methods to get into the bootloader failed.
If the adb drivers installed we may have a chance.
You didn't say about the sdcard.
At the moment are you still stuck in apx or bootlooping.
Sorry but I need a place to begin.
tobdaryl said:
I'll assume that means all ten methods to get into the bootloader failed.
If the adb drivers installed we may have a chance.
You didn't say about the sdcard.
At the moment are you still stuck in apx or bootlooping.
Sorry but I need a place to begin.
Click to expand...
Click to collapse
i have a sd, it doesn't have info [isn't from tf300, it doesnt came with]. When i introduce it into eeepad i can't access the storage from windows.
I can only interact with the tablet when i turn it on with VOLUP + POWER then is when windows ask me for drivers, now i have installed ADB drivers.
sorry for all dude. And thanks.
AdvanceArg said:
i have a sd, it doesn't have info [isn't from tf300, it doesnt came with]. When i introduce it into eeepad i can't access the storage from windows.
I can only interact with the tablet when i turn it on with VOLUP + POWER then is when windows ask me for drivers, now i have installed ADB drivers.
sorry for all dude. And thanks.
Click to expand...
Click to collapse
No problem we just need to get a starting place and have as much in our favor as possible.
I don't believe adb works in apx mode but we'll give it a shot.
No sdcards come with the tablet.
Go into apx mode (volume + power).
Go to your adb folder with cmd and type
adb devices - press return or enter
If it is working we should get your serial number in return.
Now get out of apx mode.
type
adb devices - do not press return yet
watch your unit and when the screen goes black and before it lights(rebooting) now press return
Tell me what is returned each way.
tobdaryl said:
Go into apx mode (volume + power).
Go to your adb folder with cmd and type
adb devices - press return or enter
If it is working we should get your serial number in return.
Now get out of apx mode.
type
adb devices - do not press return yet
watch your unit and when the screen goes black and before it lights(rebooting) now press return
Tell me what is returned each way.
Click to expand...
Click to collapse
No serial. only ''List of devices attached''
Tried with Asus Trasnformer Prime APX Interface [naked drivers] and ADB drivers.
AdvanceArg said:
No serial. only ''List of devices attached''
Tried with Asus Trasnformer Prime APX Interface [naked drivers] and ADB drivers.
Click to expand...
Click to collapse
[FONT=TimesNewRomanPSMT, serif]Download 10.4.2.9 JB from this thread post #3[/FONT]
[FONT=TimesNewRomanPSMT, serif]unzip once and you should still have a zip if you get a blob then do not unzip.[/FONT]
[FONT=TimesNewRomanPSMT, serif]rename to EP201_768_SDUPDATE.zip and copy to sdcard and place sdcard into your tablet.[/FONT]
[FONT=TimesNewRomanPSMT, serif]Power tablet and hope![/FONT]
nothing. Renamed US_epad-user-10.4.2.9 to EP201_768_SDUPDATE.zip, throwed it into sd and turned tablet on. Stuck on ASUS logo.
AdvanceArg said:
nothing. Renamed US_epaduser_10_4_2_9_UpdateLauncher.zip to EP201_768_SDUPDATE.zip, throwed it into sd and turned tablet on. Stuck on ASUS logo.
Click to expand...
Click to collapse
I have some bad news for you.
Without adb or fastboot access I don't know of anything else to be done.
If you could have gotten into the bootloader menu we would have had a chance.
Maybe someone else will read this thread and have more ideas.
I'm sorry.
Good Luck!
same problem here. i have a tf300t and can only access apx interface.
I got into this mess, after by "accident" choosed the "wipe data" option present on the bootleader.
!! adb, fast boot do not work!! "power key + down button" dont do anything!
i'm getting a bit resteless because no matter were i search on the web i can not find anything suitable on how to resolve this issue...
there are some youtube videos that show a solution for tf100. it seems the same problem.
http://www.youtube.com/watch?v=CwvfNIHCYlQ
there is also a tool for tf100, called easy flasher. to bad it does not work for tf300t
http://forum.xda-developers.com/showthread.php?t=1688012
i think it is a question of seaching and waiting. someone will help and get or point to a solution. because if we google for tf300t bricked that are lots and lots of links stating this issue...
what a mess...
AdvanceArg said:
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
Click to expand...
Click to collapse
Do you see anything after resetting by holding volume down and the power button? If you can get the tablet into fastboot mode you may able to revive it. If you can, ask the previous owner which version stock Android he was running before he tried to root it (it matters!).
This method worked for me!
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps guys. Good luck!
Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following Buster's guide I was able to successfully reflash stock firmware and the device runs fine when booted up now.
However, now ADB is not detecting my device. At all. I have tried running the kill-server and start-server commands to see if that would do the trick to no avail. I'm not even receiving an error saying "device not found." Rather, the device listing is left blank whenever I enter the devices command into the command prompt. I can still send commands via fastboot, but I'm concerned that there's something here that I'm missing, or that I have somehow managed to completely bork the motherboard. I have already tried uninstalling and reinstalling the Asus usb drivers, in addition to the ADB drivers/software to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.
Does usb debugging is on?
Graiden05 said:
Does usb debugging is on?
Click to expand...
Click to collapse
Yes, USB debugging is enabled; yes that was the first thing I checked.
Any other ideas?
If You use asus drivers it worth to try universal naked driver.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I'll give that a shot this evening.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I just installed the naked drivers and tried again, but that didn't work either. Fastboot still works just fine, but I'm still at a complete loss as to how to get adb working again.
Thanks for your help thus far.
Hmm... How windows show tablet when You connect it to PC?
Graiden05 said:
Hmm... How windows show tablet when You connect it to PC?
Click to expand...
Click to collapse
Yeah everything *looks* normal, and appears to be acting normally whenever I have the tablet plugged in. When my tablet is booted up and connected to my pc, I can transfer files to and from with no issue. Also when it's plugged in, there are two different entries under the device manager (one for adb and the other for the tablet itself). It's only when I have my tablet running in bootloader mode that things don't seem to want to work correctly.
I even ran netstat last night to see if there were any programs/services using the same port as adb, and even that turned up nothing. Is it possible that I somehow inadvertently altered the settings on my tablet's motherboard when I installed a bad version of CWM, per my original post?
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Graiden05 said:
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Click to expand...
Click to collapse
It wasn't a problem until I flashed the wrong version of CWM, got stuck in a boot-loop and fixed the problem using fastboot to completely wipe my tablet and start over from scratch.
Edit: I suppose I could try a fresh install of Windows.
Try first remove all drivers and software for tablet. Then install universal naked driver.
Graiden05 said:
Try first remove all drivers and software for tablet. Then install universal naked driver.
Click to expand...
Click to collapse
Update: finally got adb to detect my device. Ended up removing everything Android-related from my desktop and re-downloaded/installed everything, including usb drivers. That did the trick.
Thanks again for the help.
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.