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!

[Q] Error Device not found while using ADB.

Trying to use adb to root my phone that is on 1.85.
I start up adb just fine but when I try to do anything else I get Error device not found. Here are all the things I've tried and noticed.
1. I tried using the commands "adb kill-server" and then "adb start-server" to no avail.
2. I tried uninstalling then restarting the google usb drivers to no avail.
3. Under device manager the phone isn't recognized as a debugging device.
Any ideas what I should next? I feel like I have tried everything. I had no problems using it with my GS2.

I had an issue last night with it not recognizing my phone from the start. I had to install the HTC Sync software and it updated the drivers. After that, it recognized my phone... well, it did when I finally check debugging mode.
You can also kill adb by going into task manager and killing it, then cmd back into your adb folder and and run "adb shell" to restart it and it then should recognize your device.

Red5 said:
I had an issue last night with it not recognizing my phone from the start. I had to install the HTC Sync software and it updated the drivers. After that, it recognized my phone... well, it did when I finally check debugging mode.
You can also kill adb by going into task manager and killing it, then cmd back into your adb folder and and run "adb shell" to restart it and it then should recognize your device.
Click to expand...
Click to collapse
I tired the latter and that didn't work either.
I'll install the HTC Sync software and report back.

I would download the official HTC drivers for the phone start there.
Cant post outside links yet but ya goto the htc website.
Then make sure you kill the HTC in your taskbar. Or you will get a different error if two ADB's are running.

Red5 said:
I had an issue last night with it not recognizing my phone from the start. I had to install the HTC Sync software and it updated the drivers. After that, it recognized my phone... well, it did when I finally check debugging mode.
You can also kill adb by going into task manager and killing it, then cmd back into your adb folder and and run "adb shell" to restart it and it then should recognize your device.
Click to expand...
Click to collapse
Installing the htc sync software then restarting the computer worked.
Did a adb devices command and it showed up.
Thanks.
Now on to rooting 1.85 (which apparently is a doozy)

Struggled w/ same issue last night using Windows 7. Tried everything, reinstalling drivers etc. Drove me nuts for about an hour & 1/2. Woke up this morning to find this tool. Was unlocked in 10 minutes.
http://briefmobile.com/how-to-unlock-att-one-x-bootloader
Sent from my HTC One X using xda premium

doin-it said:
Struggled w/ same issue last night using Windows 7. Tried everything, reinstalling drivers etc. Drove me nuts for about an hour & 1/2. Woke up this morning to find this tool. Was unlocked in 10 minutes.
http://briefmobile.com/how-to-unlock-att-one-x-bootloader
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
He's on 1.85 which is not rooted yet (well it can be which is what hes trying to do now). That unlock tool wont work for him because hes not rooted.

[Q] Can't root Indian Atrix 2 running OTA ICS 4.0.4

I have an Indian Atrix 2 running the official OTA ICS 4.0.4
I haven't rooted the phone before it updated and was trying to do it now using the files and instructions from here
http://forum.xda-developers.com/showthread.php?t=1742879
I've done all the basics:
-Checked that USB Debugging was on
-Checked that Unknown Application Sources were allowed
-Made sure I had the latest drivers
However the root batch file only says that the "daemon started successfully" but nothing happens after...
I've attached a couple of screenshots
Also I noticed that after connecting my phone to the computer and running the command 'adb devices' my phone doesn't show up in the devices list, this probably has something to do with it, but I don't know what or how to rectify it.

Try different cable or computer usb port.

I've yet to successfully root mine as will but i would also suggest running as administrator
Sent from my MB865 using Tapatalk 2

tried both suggestions, unfortunately to no avail.

How about reinstalling adb??
If nothing works i would suggest doing a factory reset and trying again.
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...

Same Problem
I too am in India and on the same update. I am facing the same problem. Till now i have tried this on 3 different PCs and it hasn't worked. I don't want to go for a factory reset as i will loose all my apps and data.

[email protected] said:
I too am in India and on the same update. I am facing the same problem. Till now i have tried this on 3 different PCs and it hasn't worked. I don't want to go for a factory reset as i will loose all my apps and data.
Click to expand...
Click to collapse
This problem has been seen in Indian Atrix 2.many have got it working after factory reset.about the data you can easily backup and restore it without any worries using say titanium backup
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...

deveshmanish said:
This problem has been seen in Indian Atrix 2.many have got it working after factory reset.about the data you can easily backup and restore it without any worries using say titanium backup
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...
Click to expand...
Click to collapse
But doesn't that require root itself the google play page says so. I have never installed it earlier cuz of that.
https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup&feature=search_result

Instructions from the post below worked for me.
http://forum.xda-developers.com/showpost.php?p=28441420&postcount=1

athani said:
Instructions from the post below worked for me.
http://forum.xda-developers.com/showpost.php?p=28441420&postcount=1
Click to expand...
Click to collapse
still the same for me. wil have to reset this weekend it seems

---------- Post added at 06:14 PM ---------- Previous post was at 06:10 PM ----------
[/COLOR]
Kryptyle said:
I have an Indian Atrix 2 running the official OTA ICS 4.0.4
I haven't rooted the phone before it updated and was trying to do it now using the files and instructions from here
http://forum.xda-developers.com/showthread.php?t=1742879
I've done all the basics:
-Checked that USB Debugging was on
-Checked that Unknown Application Sources were allowed
-Made sure I had the latest drivers
However the root batch file only says that the "daemon started successfully" but nothing happens after...
I've attached a couple of screenshots
Also I noticed that after connecting my phone to the computer and running the command 'adb devices' my phone doesn't show up in the devices list, this probably has something to do with it, but I don't know what or how to rectify it.
Click to expand...
Click to collapse
seems driver issue, the phone is not recognized..

I rooted it using the attached RazrRoot file. I saw it somewhere on XDA but I am unable to find that thread. So I am uploading it again.
All the credits goes to original developer. I am just uploading it again.
For me, there was no problem in rooting the device. I rooted it as soon as I updated to ICS. So good luck to you all.
PS: I won't be responsible for any damage caused to your device

Still error
androiddecoded said:
I rooted it using the attached RazrRoot file. I saw it somewhere on XDA but I am unable to find that thread. So I am uploading it again.
All the credits goes to original developer. I am just uploading it again.
For me, there was no problem in rooting the device. I rooted it as soon as I updated to ICS. So good luck to you all.
PS: I won't be responsible for any damage caused to your device
Click to expand...
Click to collapse
I tried everything even reset my phone. Now i am getting the attached error. PLease help guys..

check your connection mode
When you connect the phone using the USB cable, what mode is activated? Try selecting mass storage mode and then run the root script. (Other modes like MTP etc won't work I think)
Also try reinstalling the drivers before trying this out.

Doesnt work
badbomb said:
When you connect the phone using the USB cable, what mode is activated? Try selecting mass storage mode and then run the root script. (Other modes like MTP etc won't work I think)
Also try reinstalling the drivers before trying this out.
Click to expand...
Click to collapse
I tried it and it didnt work. I also have read somewhere that u have to connect via MTP only.

[email protected] said:
I tried it and it didn't work. I also have read somewhere that u have to connect via MTP only.
Click to expand...
Click to collapse
I've tried all the suggestions, out of which none seem to have worked. I think it is a driver issue, however I uninstalled the driver from the Windows Device manager and re installed the latest moto drivers, which hasn't solved the problem. So now I'm out of ideas

Kryptyle said:
I've tried all the suggestions, out of which none seem to have worked. I think it is a driver issue, however I uninstalled the driver from the Windows Device manager and re installed the latest moto drivers, which hasn't solved the problem. So now I'm out of ideas
Click to expand...
Click to collapse
How long did u wait after running the root file ?
It does take time to move ahead from daemon started successfully.. and ur phone will reboot twice after the darmon starts.

anikadam said:
How long did u wait after running the root file ?
It does take time to move ahead from daemon started successfully.. and ur phone will reboot twice after the darmon starts.
Click to expand...
Click to collapse
If u see the screen shot i have attached in a reply above u will see that it goes till the end without rooting the phone

download the razr root file and try again, maybe some problem with the download. im sorry cant help you with anything else.. maybe a hard reset should do it.
try following this again,
download the moto driver
Moto Drivers
download the razr root from here again, this is the one i used
Razr root 4.0.4
Connect phone in MTP mode
USB debugging enabled
Right click on the root.bat file and Run as administrator..
This is how ive rooted, twice, and also one of my friend.. the difference is that im on the latest leak, 672.1.18.en.03 ( but thisis also the OTA for AsiaRetail MB865) So this Should probably work.. If not maybe research some more and if nothing helps maybe a hard reset is your last option..

See if this helps
Firstly I don't know since you already attempted a root method which didn't work out yet how & up to what extent it alters your phone though not rooted. If your phone is working I feel the first step now would be for you to do a factory reset assuming you are on ICS OTA (OTA remember & nothing else) & I am repeating one of my post for what's it worth to you cause it was successful for me, so here it is :
Here's what I did :
1) Installed the latest USB drivers (in my case Motocast) from Moto site.
2) As a double check executed the Motorola Device Manager program (basically the USB drivers) again from the Moto site (which gives option of repair or uninstall & I selected repair since I initiated the install process) atop the prior installation of the Motocast.
3) Cold boot the computer (shutdown & then restart & not just restart {being paranoid })
4) On phone ensure screen timeout to never, screen always on while charging, usb debug on, allow non market apps install check then plug in to back port and when the Moto USB transfer GUI pops up, right click the icon @ system tray & check do nothing when phone is plugged in. Unplug phone
5) Once again cold restart phone & computer
6) After phone restarts killed all google processes manually, disabled anti virus, vpn's & other non critical apps
6) Once rebooted both devices, selected MTP mode, plug in phone & click on Jim's root file
7) Root - Cut thru like hot knife thru butter
One most important point was since I was absolutely bone stock I did not do factory reset before plugging in phone and in case if any kind of tinkering has been done ensure factory reset to make sure you go absolutely bone stock & then follow above steps. Hope this helps.
Post your final update. Good Luck!

[Q] Unbricked successfully, ADB broken?

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.

Adb tools keeps showing error device not found ?

I keep getting error device not found with adb tools on two different verizon m8's ?
I was using adb tools 1.0.31 and never had any problem until tonight and my one m8 I had obtained s-off on it a bit over a week ago with no problem at all. I tried to firewater s-off another m8 that belongs to a friend and his keeps getting error device not found and mine does the same thing. My computer has froze up 2 times in the last 2 days I"am on windows 7 I used system restore and went back 5 days no difference.
I even tried another version of adb tools, then I tried my other computer which it never freezes up and same deal on it with multiple versions of adb tools. I have updated all drivers and done all that rebooted over and over I have even removed java on both computers and installed new versions. Really pulling my hair out on this. Even tried multiple usb ports on both computers.
I have also constantly been checking device manager and there are no conflicts on anything and all drivers keep showing that they are the newest driver.
I could see if it was doing it on just the one m8, but on mine also which it was working fine on it just days ago.
Anyone have any ideas ?

You did remember to enable USB debugging, did you? [emoji6]
Sent from my HTC6525LVW using Tapatalk

berndblb said:
You did remember to enable USB debugging, did you? [emoji6]
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Yes I even tried unchecking it then powering off restarting and rechecking it, actually did that all a couple times to rule it out.

Do you see the Android ADB interface in device manager, or are there any yellow exclamation marks there?
For ADB to work you need:
- ADB access on in Developer Settings (USB Debugging)
- The ADB application
- Drivers for your Windows PC for the ADB device to be recognized
You've stated you've done point 1, I don't doubt you have point 2, you need to work on point 3.
Note: The last possibility is you have some external program blocking your access. I've seen some draconian firewalls block USB.

jskup said:
Do you see the Android ADB interface in device manager, or are there any yellow exclamation marks there?
For ADB to work you need:
- ADB access on in Developer Settings (USB Debugging)
- The ADB application
- Drivers for your Windows PC for the ADB device to be recognized
You've stated you've done point 1, I don't doubt you have point 2, you need to work on point 3.
Note: The last possibility is you have some external program blocking your access. I've seen some draconian firewalls block USB.
Click to expand...
Click to collapse
If your talking about my htc it showed working fine and I tried to update the driver and it showed I have the newest driver available. I went through everything on device manager and everything was working fine, and no exclamation marks. Like I said it was working fine as I used it to firewater s-off an at&t m8 2 weeks ago and it worked fine for it. And I did the firewater on 2 other htc phones in the last 2 months. Also I have used the same adb tools for like the last year with no problems. Also I have not changed any programs, and I have used the same antivirus and firewall for the last 2 years so it should not be blocking it.
This is all why it has me stumped ?

It's not as bad as all that.
The next thing I'd do would be to uninstall and reinstall whatever method gave you the drivers. If you installed the HTC Sync software, uninstall and reinstall. If you used some other method, such as the Minimal ADB and Fastboot package, I'd uninstall and reinstall it.
I have to deal with drivers all the time at work. This sort of thing can happen. Windows makes this process more complicated than it is in Linux.

Roefastford said:
I keep getting error device not found with adb tools on two different verizon m8's ?
Click to expand...
Click to collapse
Have you tried a different USB cable?

Doc Ames said:
Have you tried a different USB cable?
Click to expand...
Click to collapse
Yes tried multiple cables and multiple usb ports. With android system running they pick up the phone as a storage device also. It makes no sense. Going to try unistalling drivers and reinstalling as the other guy suggested.

jskup said:
It's not as bad as all that.
The next thing I'd do would be to uninstall and reinstall whatever method gave you the drivers. If you installed the HTC Sync software, uninstall and reinstall. If you used some other method, such as the Minimal ADB and Fastboot package, I'd uninstall and reinstall it.
I have to deal with drivers all the time at work. This sort of thing can happen. Windows makes this process more complicated than it is in Linux.
Click to expand...
Click to collapse
I will try uninstalling and reinstalling the drivers and see if that fixes the problem, thanks.

Figured it out. I was trying to run firewater from bootloader lol, and not with android running. Ok I guess I really messed that up lol.