When I try to run the spoof-cid. It says the following...
Restarting ADB
Pulling files
Checking files
Couldn't pull files from device.
Press any key to continue . . .
It is rooted, and it does have usb debugging enabled. Mildly frustrating to say the least.
Following instructions from Here http://briefmobile.com/how-to-unlock-att-one-x-bootloader
Do you have ADB set up properly? you can check by running adb devices and see if your device gets listed. Also, you can go to your device manager and see if your phone shows up to check if your drivers are set up properly by looking for "myHTC" or "android device".
Related
Okay this is four newbie that can't get there phone into download mode,or if your phone is stuck on the a&tt screen or whatever reason you need to go into download mode
1st thing you are going to need android-sdk if you do not have. You need to put all the files on your C: drive in a folder called android-sdk.There is the link to the sdk site.
http://developer.android.com/sdk/index.html
Step 1 go to setting then to Application I always select mass storage,but i guess ask on connection will work.Then in applications select Development,and them usb debugging.Then plug your phone into your computer
Step 2 open the start window in windows vista and 7 user type cmd into the search.XP you go to run and then type cmd.
Step 3 once inside cmd type cd\ enter.this will bring you to the c drive and should look like this.Now it should look like this.
C:/>
step 4 next type cd then (space) android-sdk\tools\ enter it should look like this.
C:\>cd android-sdk\tools\
Step 5 type adb (space) devices.Now it should look like this.
C:\android-sdk\tools>adb devices
* daemon not running. starting it now on port whatever *
* daemon started successfully *
whatever # your phone is device.
now if it doesn't say this you probably don't have the proper drivers install,but if your are rooted you should.I will include a zip folder anyways.
Step 6 adb (space) reboot (space) download enter.It should look like this.
C:\android-sdk\tools>adb reboot download
After hitting enter your phone will reboot into download mode.
Here is a link for the drivers.
http://www.sendspace.com/file/dbh299
Make sure that you have ADB in the tool folder if not here it is
Actually step 1 would be to enabled usb debugging in settings/applications/development section otherwise none of this will work.
Theres also the adb reboot recovery command.
peachpuff said:
Actually step 1 would be to enabled usb debugging in settings/applications/development section otherwise none of this will work.
Theres also the adb reboot recovery command.
Click to expand...
Click to collapse
Thank dude I always have my phone in debugging i'll edit now
From my experience if you flash a rom it will no longer have usb debugging enabled so if you get boot loop or something adb wont work. I know you don't specifybut I personally have not heard of a device being stuck unless the person was flashing.
This is my captivate. There are many like it buy this one is mine.
You might also consider adding the instructions for adding the tools folder to PATH for those that would use this frequently.
flashman2002 said:
From my experience if you flash a rom it will no longer have usb debugging enabled so if you get boot loop or something adb wont work. I know you don't specifybut I personally have not heard of a device being stuck unless the person was flashing.
This is my captivate. There are many like it buy this one is mine.
Click to expand...
Click to collapse
I have had my phone,Plus my girls virbrant stuck on the att%t screen\t-mobile screen and this as worked for me.I have had a few boot loops, but that was cuz i was changing the framework-res.apk,but was able to go into download mode via the rom I was on. I will look into this and see if i need to update.
Completely unresponsive
I have a galaxy s7 and my phone is completely dead. It does not show up in list of devices connected. I have tried all key combinations to start my phone but it is completely unresponsive. Can anybody help me out please.
Hello all,
I have installed android sdk, google usb drivers etc. I am using windows Xp. My phone is upto date as per the Sony PC companion installed in windows. When I try to connect my phone in usb debugging mode to adb, its not showing up. when I give adb devices it doesn't list any devices.
when I give adb shell, it says device not found. I tried all methods like kill-server, start-server and killing adb.exe etc. after I went thru the existing threads in this forum. Nothing works !!
And the interesting thing that I could not figure out is about the device manager. After I try all methods it says drivers not installed. I try to install google usb drivers as well by browsing the folder in my android sdk . It was displaying like 'nothing found to install'
Any ideas please ??
One update.
Google usb drivers were not being installed correctly. When I update driver and browse to the Android SDK folder where the Google USB drivers present (My case .... Android SDK-> Extras-> Google -> usb_driver) it says 'nothing to update'
Then I edited android_winusb.inf file there and included my device ID (as showing up in Device manager). And it installed the drivers.
Then I opened adb again. And gave 'adb devices' and finally I could see my device listed !!!!
But still one major problem exists. That the device is getting disconnected continuously from adb and each time I would have to restart the adb and this makes it useless....
Not able to figure out why ...
Try using this: adbdriver . c o m
If it does not work try flashtool's drivers
I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.
Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.
As the title says.
I'm trying to unlock the bootloader on my XZs so I can root it.
My device is listed normally when turned on w/ the command window, but in fastboot mode it disappears and when I try a command, an error comes up saying ""error: no device/emulator found". (see attached image)
As far as I'm concerned, I have all the necessary drivers, I've tried on another PC, the result is always the same.
And when I try to change the drivers (Via Device Manager>Update Driver>Browse My Computer...>Let me pick...>Have Disk...)
I get yet another error saying "The folder you specified doesn't contain a compatible software driver for your device..."
Can someone please give me a solution. This has been asked before on XDA by someone else (that thread has no replies). It seems it's always us little guys with actual problems which need solving who get little to no help at all here.
Reinstall driver again.
It doesn't work. The problem is I want to install the Google USB drivers for my Xperia phone but Windows 10 will not let me and driver signing seems to be impossible to disable (currently typing this on my laptop while it's in test mode).
1. Turn off your phone. Boot in to fastboot mode and plug the cable. After your heard the sound from the computer for new device found. Go to device manager look to usb S1 device. Reinstall driver by manual choose (do not search) from the menu with the name is Android Google. When prompt for install. Choose install anyway. After successful install driver, please check status from flashtool to make sure your device show connected in fastboot.
2. Change the usb port. Sometimes you get problem with usb port 2.0 and 3.0
Hope you can fix it asap.
Nothing by the name of 'Android Google' appears in the menu when selecting new drivers.
I clicked on 'S1boot Fastboot' under 'other devices' in Device Manager and clicked on update driver
>Browse Computer
>Let me pick
- and then there's something similar called 'Android Device' but no 'Android Google' so I click on that
- then I get three options:
Android ADB Interface Version 11.0.0.0
Android Bootloader Interface Version 11.0.0.0
Android Composite ADB Interface Version 11.0.0.0
None of them worked when I tried.
I think the solution is to have the phone on, with USB debugging enabled, connect via USB to PC, test your adb devices again, if all good, go ahead and
Rich (BB code):
adb reboot fastboot
This is because some phones use Fastbootd (notice the d..).
Hello Everyone,
I would like to learn how to remove bloatware Apps from my Android phone.
I have tried using "ADB commands" but for some reason my computer doesn't recognize/find my Android phone when I connect it to it.
Please help.
Thanks in advance
Download drivers for samsung and enabled adb developer option then type following "adb devices" press enter and should see serial number indicating phone connected via adb
petiolarissean said:
Download drivers for samsung and enabled adb developer option then type following "adb devices" press enter and should see serial number indicating phone connected via adb
Click to expand...
Click to collapse
Hello, and Thanks
I have done that exactly, but it still doesn't work.
And I can't figure out why is not working.
I have installed the Samsung driver, allowed the ADB function on my phone from "Developer Options" etc.
In addition to the advices by petiolarissean , check whether the driver works well, please.
In the 'Devices Manager' of your Windows, check the driver for your Android phone.
If this doesn't work yet, change an usb cable and then try again.
Only to have mentioned it:
So-called bloatware typically is housed in Android's locations /system and/or /system/priv--apps what only can get accessed by Android's root-user after successfully mounted as RW.
James_Watson said:
In addition to the advices by petiolarissean , check whether the driver works well, please.
In the 'Devices Manager' of your Windows, check the driver for your Android phone.
If this doesn't work yet, change an usb cable and then try again.
Click to expand...
Click to collapse
Thanks for your help
I think I will buy a new USB cable and give it a try, hopefully it will work.
Have a nice day
Sorry late reply.I have like 5 different phone.Hard core modder.
This question help alot
Even though you csnt get adb working
Can you still move files from your phone to pc or computer.Or nothing ay all.Your answr will tell me your problem