Database Info

USB not working after flashing Damage Control

So let me start by saying I have been researching these forums for the last 8 hours trying to following instructions on getting my phone to connect to my computer and with no luck, hoping someone out there can please help me step by step in correcting my problem.
1)I flashed DC's Rom, then flashed the most current radio, then flashed the most current Wimax.
2)I noticed that when I connect my phone to the computer, it says device is not recognizable. The phone charges but does cannot be seen by the computer as a disk drive (I'm trying to RUU to stock but the comp. will not see my phone and I've already tried running RUU but it also is having probs seeing the phone).
3)I've read Calculin's instructions in fixing the SD Card and USB as close as possible but also no luck. I've downloaded Android-SDK Tools and ran CMD with the Instructions saying type in "fastboot oem boot", from there, thats where I get stuck, it just says "waiting on device". Not sure where I go from there, I'm in Reboot mode where it has Fastboot on my evo screen.
Any help would be much appreciated, I'm just so frustrated and I'm trying to get back to square one.

Unplug your phone and restart it, then plug it back in. I had to do this 3 times before it started working again. Other than that, you might just need to download the new drivers.
And you posted in the wrong section.

Sorry about posting in the wrong section, what drivers should I install, are you talking about the new HTC Sync Files or something else? Can you point in the direction to get these files?

okay, I think I'm getting close, I have a box thats popping up now thats trying to located the Device Driver the phone. It says "Failed" next to the line "MY HTC" Where can I download the necessary drivers for this phone?

faquedado said:
okay, I think I'm getting close, I have a box thats popping up now thats trying to located the Device Driver the phone. It says "Failed" next to the line "MY HTC" Where can I download the necessary drivers for this phone?
Click to expand...
Click to collapse
You should be able to get the proper drivers from either Sprint or HTC's web site. There are links on both sites. Also, when you install / reinstall the sync drivers make sure anti-virus is disabled. If the situation continues and you've tried everything else other folks suggested look at program permissions in your anti-virus program. I was having something similar and CA anti-virus was not letting the program start-up. I had to toggle it to "allow".
Good Luck.

[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] Recovering photos from HTC One X in bootloop

Hey everyone. I couldn't find an answer to this that I could follow and that worked for me as I'm not very technically inclined.
My HTC One X recently died after having a low battery and now whenever I try to turn it on (even when it is fully charged), it gets to the lock screen, but I can only access everything for about 5 seconds before it restarts again. I know I have USB debugging enabled, and I can get to the screen that shows up when I hold down the power button and the volume-down button.
What I want to do, before doing a factory reset and praying that ends the bootloop, is recover my photos which I stupidly did not back up anywhere. I can connect my phone to my laptop, which runs on Windows 8, but it is not recognized as it normally would be (ie: I can't access files directly). I've gotten to the point where I can see "FASTBOOT USB" on my phone when it is connected and I've restarted my PC so that it is able to identify it in the Device Manager. I have also gone through the steps of downloading a universal naked driver and choosing the driver under the Device Manager, so when I use a command prompt my phone shows up in fastboot devices. (I used minimal fastboot and ADB)
But what can I do now? I have never tampered with my phone, so it is locked or unrooted. I'd like to keep it that way if possible, but I'm having a hard time understanding how I can retrieve my photos. Should I use ADB commands, and if so, how do I get to the point where my PC recognizes my phone under ADB devices? Or is there a better way? I'm also not very familiar with custom roms, TWRP, CWM, etc.
I'd appreciate a brief walk-through if possible as, like I said, I don't normally do this sort of thing. Thank you!

thepenrosesteps said:
Hey everyone. I couldn't find an answer to this that I could follow and that worked for me as I'm not very technically inclined.
My HTC One X recently died after having a low battery and now whenever I try to turn it on (even when it is fully charged), it gets to the lock screen, but I can only access everything for about 5 seconds before it restarts again. I know I have USB debugging enabled, and I can get to the screen that shows up when I hold down the power button and the volume-down button.
What I want to do, before doing a factory reset and praying that ends the bootloop, is recover my photos which I stupidly did not back up anywhere. I can connect my phone to my laptop, which runs on Windows 8, but it is not recognized as it normally would be (ie: I can't access files directly). I've gotten to the point where I can see "FASTBOOT USB" on my phone when it is connected and I've restarted my PC so that it is able to identify it in the Device Manager. I have also gone through the steps of downloading a universal naked driver and choosing the driver under the Device Manager, so when I use a command prompt my phone shows up in fastboot devices. (I used minimal fastboot and ADB)
But what can I do now? I have never tampered with my phone, so it is locked or unrooted. I'd like to keep it that way if possible, but I'm having a hard time understanding how I can retrieve my photos. Should I use ADB commands, and if so, how do I get to the point where my PC recognizes my phone under ADB devices? Or is there a better way? I'm also not very familiar with custom roms, TWRP, CWM, etc.
I'd appreciate a brief walk-through if possible as, like I said, I don't normally do this sort of thing. Thank you!
Click to expand...
Click to collapse
Try Power the Device Up in Safe Mode - HTC One®
Do you know the model number? Is it the AT&T or Rogers? s720e, G23, 720, 325...

sd_shadow said:
Try Power the Device Up in Safe Mode[/URL] - HTC One®
Do you know the model number? Is it the AT&T or Rogers? s720e, G23, 720, 325...
Click to expand...
Click to collapse
I tried going into safe mode and nothing changed! It didn't break the bootloop, so I guess it isn't an app that's causing the problem. It's with Rogers, but I don't know the model number... I got it in North America if that helps.

thepenrosesteps said:
I tried going into safe mode and nothing changed! It didn't break the bootloop, so I guess it isn't an app that's causing the problem. It's with Rogers, but I don't know the model number... I got it in North America if that helps.
Click to expand...
Click to collapse
It's likely a s720e then, but
I will request that this thread be moved to AT&T One X Q&A, Help & Troubleshooting
Where you should be able to find out for sure.
Next step is likely flashing a custom recovery like TWRP or CWM then you could, mount sd card/storage and copy photos.
see AT&T One X Q&A, Help & Troubleshooting Frequently Asked Questions by Heisenberg
[INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up (Updated 5/8/14) by redpoint73

Bootloader

Hello everyone
I've recently got an LG Q6 M700N, and I'm trying to root it, but I've came across a problem. Whenever I type in adb reboot bootloader, the phone simply reboots to the system. It won't go into bootloader. Have any of you encountered this issue? Can you give me a fix or a workaround? Developer options are ON, OEM Unlock is ON, drivers are installed, tried with multiple USB ports on my PC, adb sees the device in debug mode.
Thanks in advance!
If I've posted in the wrong thread: My bad! Sorry.

See thread in dev section

deleted

Botched Graphene install on Pixel 3A - need help restoring default settings

Hello,
I am hoping for some advice on how to revert my phone back to its original "factory settings" after a botched instal of GrapheneOS onto an unlocked Google Pixel 3A.
I got to the point at which I needed to Flash the Graphene Rom to the phone, but rather than installing, I received a message from Smart Screen MS edge asking if I really wanted to run as it's protecting my PC - I clicked run anyway and a blank command line window appeared for a second. Now my pc doesn't seem to be recognising the pixel 3A when I type ADB devices. My phone is currently in Fastboot mode "unlocked" and I'm hoping for some advice on what to do next. I'm total noob, so unsure how to start the process over (return the phone to it's previous state) before, maybe, trying again on a different PC.
I have since turned on my phone and Android 11 is still present and seems to work fine (however it gives me a warning on startup that the bootloader is unlocked.
Any help would be very much appreciated - thank you in advance.

Is all what happened that your phone now:
complains about "'maybe not safe bootloader unlocked".
This is just what android does when the bootloader is unlocked.
This you did before trying the flash.
If you want the warning gone simply lock it again.
However if you into the market for graphene OS then I would recomend: along with following their guide to a t to also read up here on xda about the general rooting unlocking thing a bit more so you get the overall process a bit better perhaps next time.
About windows. There are so many tools out there to help ya with disabling some of it's spying, turning off smartscreen, auto - uploads of all your data to M$oft, etc etc.
It's not hard to find.

Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.

Ignore

deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go

Tamsta_T said:
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go
Click to expand...
Click to collapse
Hey there,
This is brilliant - thanks for all the advice. Having this support is helping me gain the confidence to learn more, research more, and then give it a go.
All the best.

deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
thats if I am not wrongly remembering my experience:
because now your phone is in fastboot mode thus it won't show up with that command anymore.
Try: 'fastboot devices'
I imagine you put it into fastboot through: 'reboot fastboot' when you where in adb?
When in fastboot you can go on and flash the recovery and such.
Are you still in need of help here?

Hey, thanks for the clarification - been away and so haven't implemented all suggestions, yet.
I typed "adb reboot booloader" which I assumed put it into fastboot mode and then unlocked it using "fastboot flashing unlock".
I tried fastboot devices but the PC still doesn't see the phone. I'm going to try the update usb driver suggested by Tamsta_T and see how it goes.
Thanks for your help.