Database Info

[Q] Root Problems

I am coming from the Galaxy S Vibrant and so far I am not impressed by the whole rooting process for the Skyrocket. I have tried on 3 different windows computers and every time it says it is unable to recognize device. I installed the drivers but I don't believe they were installed correctly. When I click root in super one click, the application stops responding.
I made sure to select debugging and when I connect the phone to the computer nothing prompts me on the phone. Is there something I am missing in order to get the Skyrocket recognized by Windows?

eshewski said:
I am coming from the Galaxy S Vibrant and so far I am not impressed by the whole rooting process for the Skyrocket. I have tried on 3 different windows computers and every time it says it is unable to recognize device. I installed the drivers but I don't believe they were installed correctly. When I click root in super one click, the application stops responding.
I made sure to select debugging and when I connect the phone to the computer nothing prompts me on the phone. Is there something I am missing in order to get the Skyrocket recognized by Windows?
Click to expand...
Click to collapse
You need to be patient. the program stopped responding for nearly 5 minutes for me before it started going again and my PC is lightning fast.
Try installing Samsung kies. Should give you all the drivers you need.
If your computer doesn't recognize the phone at all then you most likely dont have the drivers installed correctly or a USB hub driver issue in which case no USB devices would work. Like I said, try installing kies. Once you can get the PC to recognize the phone as a storage device, you should be good to run the root program.
Sent from my SAMSUNG-SGH-I727 using XDA App

I tried Kies already and it didn't help. I can connect my Vibrant with no problem to my computer as well.

eshewski said:
I tried Kies already and it didn't help. I can connect my Vibrant with no problem to my computer as well.
Click to expand...
Click to collapse
Can you connect other USB devices to your computer? USB drives etc
Sent from my SAMSUNG-SGH-I727 using XDA App

i had somewhat the same problem , I rooted my old vibrant first incase i screwed something up , no big loss , it went smooth as butter , then I hooked the SR up and it took forever , 3 try I unplugged alot of my other usb devices , restarted the pc and tried , it hung for a few minutes and I left it alone , it eventually worked the last time. I also have a pretty solid pc , running win7 64bit , unplugging alot of my usb devices seemed to be the thing that really helped.
hope that helps ya

eshewski said:
I am coming from the Galaxy S Vibrant and so far I am not impressed by the whole rooting process for the Skyrocket. I have tried on 3 different windows computers and every time it says it is unable to recognize device. I installed the drivers but I don't believe they were installed correctly. When I click root in super one click, the application stops responding.
I made sure to select debugging and when I connect the phone to the computer nothing prompts me on the phone. Is there something I am missing in order to get the Skyrocket recognized by Windows?
Click to expand...
Click to collapse
rooting this device is easier then posting that on the forum =)
1) If you are still 2.3.5 (and didn't do the OTA upgrade) -> use doomlord's script (DooMLoRD_v3_ROOT-zergRush-busybox-su) or newer if there is one:
-if you did do the OTA upgrade - search the forum for another way to root.
2) install KIES (if its installed, continue to 3)
3) extract the DooMLoRD_v3_ROOT-zergRush-busybox-su.zip to anywhere (maybe c:\doom )
4) open a command prompt (run as administrator if your not running windows XP)
5) goto c:\doom\files\
6) type "adb devices"
- if it finds your device - just run the script , it will root your phone
- if it does NOT find your device, troubleshot kies (uninstall it, reboot, reinstall, disable anti virus/firewall, etc etc) because if it can't find the device then the problem is someplace on your computer.
good luck!

[SOLVED] USB still not recognized (ICS Leak)

Edit:
This problem has been solved. For any of you that are having issues with ADB recognizing your phone, even after you have uninstalled and reinstalled the correct drivers (As I had done several times on 2 computers), a factory reset might be your answer. So, if you are on ICS leak, and the last thing you want to do is try to FXZ back to 2.3.6...Try wiping data/factory reset first. It solved my problem once and for all.
------------------------------------------------------------------------------------------------
First, I must say that I have already found similar threads of this type, and some even with solutions, but I still cannot fix this problem.
I am on ICS Leak on my AT&T Atrix 2 and everything is running great, aside from one thing. I cannot get my computer to recognize my device. When I plug it in, it will charge, but I get no USB options in my notification bar on my phone. I have tried other solutions, and I have installed the necessary drivers, (Windows 7), I have uninstalled and reinstalled, and rebooted with no luck. If anyone could help me, that would be great! Let me know if any more details are needed...

Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?

I had to uninstall drivers and all moto services. Then plug in phone let it look for install drivers. It failed on one of them. I then installed the moto portal disconnected my phone, rebooted computer and phone, plugged it back in and it worked. Good luck.
Sent from my MB865 using Tapatalk 2

Garnerj013 said:
Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?
Click to expand...
Click to collapse
First off if you found similar threads post in them, no need to start a new thread
I'm guessing you are trying to root?
if you are, the script takes a while to run your phone will reboot several times it will tell you when it is done

Garnerj013 said:
Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?
Click to expand...
Click to collapse
adb devices command showing your device? If so, try again.. and wait, like drgravy said.
Or do what leif said and switch between the 3 different usb connection types and wait for the drivers to install.. and try putting it in mtp or ptp mode to run the root batch file..
Sent from my phone's mind

Drgravy said:
First off if you found similar threads post in them, no need to start a new thread
I'm guessing you are trying to root?
if you are, the script takes a while to run your phone will reboot several times it will tell you when it is done
Click to expand...
Click to collapse
Sorry about the new thread. Blame it on the n00b status. I have rooted with this method before on the same model phone with ICS leak and it worked after a few unsuccessful tries. It usually shows some activity in the command prompt, but this time it is hanging at *daemon started successfully*
alteredlikeness said:
adb devices command showing your device? If so, try again.. and wait, like drgravy said.
Or do what leif said and switch between the 3 different usb connection types and wait for the drivers to install.. and try putting it in mtp or ptp mode to run the root batch file..
Click to expand...
Click to collapse
I've tried in every connection mode, and I have the drivers installed. I've been trying every way possible. Also, for simplicity sake, could you tell me how to use the adb devices command? I'm tech savvy but pretty green to the development/programming side of things.

leifemagnuson said:
I had to uninstall drivers and all moto services. Then plug in phone let it look for install drivers. It failed on one of them. I then installed the moto portal disconnected my phone, rebooted computer and phone, plugged it back in and it worked. Good luck.
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Also, once i uninstall Motorola Device Manager, do I have to manually uninstall more drivers, or does that get them all? If not, how do I manually uninstall the drivers?

http://forum.xda-developers.com/showthread.php?p=29609879
I was having the exact same issue where it was hanging at daemon started successfully. Was totally a driver issue. Follow the link in my link...
I would suggest completely uninstalling everything Moto from your PC, rebooting and then follow the steps again, being sure to install those new drivers that are linked in that post.
Edit: I'm trying to remember when I did it....but I seem to recall having a bit of weirdness when I installed the new drivers. I had the install driver wizard pop up while I was installing the drivers from the moto driver executable. I just let the wizard sit there and wait while the moto driver installer did its thing.

So, instead of uninstalling all that is Moto on my laptop, I moved the Moto Device Driver executable and the batch files (with Su and Superuser.apk and all the extras to my desktop. Ran the moto executable and plugged my phone in to install the drivers and rebooted the computer. Still nothing. Do i need adb on my desktop to root my phone? I'm getting flustered with this. It really should be working one way or the other....

Same issue for me..i reinstalled drivers and connected the phone in media transfer mode..rest of procedure same..am successfuly rooted now
Sent from my MB865 using xda app-developers app

devilhunter47 said:
Same issue for me..i reinstalled drivers and connected the phone in media transfer mode..rest of procedure same..am successfuly rooted now
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
I tried and tried to reinstall the drivers, and even installing them on a different PC didn't work. Finally, I did a factory reset, and the phone was recognized by ADB. Thankfully, I am now rooted and on SCv7!! (Thanks to Jimbridgman, Ikrasner, and a couple other devs.) Thank you all.

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.

Bricked OP7P USB Issues

Hi all,
I am have bricked my device, its in fastboot mode but wont do anything anymore.
Ive tried literally everything possible, ive read numerous manuals, seen tons of video tutorials but nothing works.
The main issue I am facing now is that MSMDownloader tool does not recognize my phone because of an Driver issue.
However, whatever I am doing I cant get the correct driver to function on my Windows 10 machine.
Whatever I do, it either does not recognize the device, or shows it as Kedacom USB Device / Android Bootloader Interface.
I have manually removed the drivers from the device manager as well as removing them manually with pnputils, it does remove the driver and then shows it as Android Device.
If i then scan the folders (whole windows is in testing mode like many manuals tell me to) it just wont install the driver and if i do that manually using pnputils it changes nothing.
The only moment it changes is when I connect to the internet and search for a driver and the old samer driver will be installed.
I have tried the OnePlus driver installer, I have tried the All In One tool, I tried the Qualcomm QDLoader HS USB Driver, I tried it totally disconnected, i rechecked if i was running cmd and the msmdownload tool as administrator, i have rebooted and updated my pc, rebooted and tried again.
I am pretty sure its an driver issue, but apparently whatever I do i cant seem to be able to fix it, and another way of fixing this phone is probably not gonna work as whatever I do with the volume, power buttons, how many times i reboot i just keep getting the same Fastboot/Download screen.
Does anyone have any other idea, am i missing something? I really have no idea. I have followed several manuals step by step, googled and found people with similar issues tried those solutions, i am now busy for like over 12 hours and am really getting the idea that i cant fix it

This can be closed, I have used the info from this thread:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
It helped me revive my phone without having to deal with the USB issues and MSMDownloader.

schorrie said:
This can be closed, I have used the info from this thread:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
It helped me revive my phone without having to deal with the USB issues and MSMDownloader.
Click to expand...
Click to collapse
THREAD CLOSED on request of OP!

Phone unrecognized in download/recovery

So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.

chaosrde said:
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
Click to expand...
Click to collapse
Strange suggestion but try a different pc. My phone isnt recognised when I try to install magisk on my phone on my home pc but it works on my work pc.
I got about 9 different USB ports on my home PC and none work
Also download platform-tools_r29.0.2-windows for fastboot etc.

While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.

Icculus760 said:
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Click to expand...
Click to collapse
I am using the OEM cable, straight out the box. I'm gonna try meddling with it again when I get home and see if I can get it working.

bigAL99 said:
Also download platform-tools_r29.0.2-windows for fastboot etc.
Click to expand...
Click to collapse
Ive done a fair bit of searching but I can't find anywhere to download older version of platform tools, I have the current build 29.0.5.