Guys..
I'm stuck in the very first step in rooting my Explorer..
I installed HTC Sync(but it does not recognise my device) , Downloaded SDK tools but stuck in the step where we have to type
fastboot oem get_identifier_token in cmd..
After this step it just shows
< waiting for device >
and does not move further..
Tried installing various driver packages found in other posts, installing htc sync in compatibily mode but of no use..
P.S - I use WINDOWS 8 O.S in my PC
Thanks in advance..
The latest version of HTC sync works on Windows 8. You can also try installing the latest Google USB driver from SDK manager
Edit:
Try this:
http://forum.xda-developers.com/showthread.php?t=2211791
Related
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 found out the issue with the ADB environment & was able to finish off s-off , firmware upgrade & move to CleanRom 7 since yesterday and it is looking good.
For the masses, if it is of any interest. These are the steps I followed.
Pre-Requsite for S-OFF : Unlocked bootloader, Rooted etc.
a. Download the ADK (Android Dev Kit) ~470MB (This was the only option which worked for me)
b. Extract & copy the folder platform-tools to C:\ as android
c. Set the environment path to point to this folder. This would resolve all your *device not found* errors while running ADB.
If not, then
1. Remove all HTC drivers & sync software
2. Run a registry cleaner like Ccleaner to remove any leftout entries.
3. Download & run the latest HTC sync software.
4. Once Install has completed, connect your phone & switch on USB debugging. The PC would recognize the phone & install most drivers.
5. Fire up a CMD window in the Android folder & run "adb devices". If you see your phone listed, you're good to go.
Else,
6. Reboot the phone to bootloader & give it a wait. It should install the Android phone 1.0 device driver.
7. Boot the phone to Android & wait for system to install all drivers once more.
8. Run the command in step 5 again to verify that system recognizes your device.
If the above steps work, go ahead and s-off your phone. Then do the firmware upgrade if you wish & you should be able to run any ROM without issues.
Don't execute any steps while flashing ROMs if you don't see your device through ADB or don't understand what the step means :fingers-crossed:
Click to expand...
Click to collapse
I am currently trying to flash a new ROM on my One S, but can't set superCID or S-off as ADB won't recognise the device when in the bootloader. It is recognised in fastboot.
I'm using Win7 64-bit (though have also tried a Vista 32-bit computer) and have the latest version of TWRP on my phone. In device Manager it is listed under 'Android USB Devices' as 'MY HTC'. My drivers are the HTC ones, I've also tried installing drivers by installing the Android SDK, PDAnet and HTC Sync Manager - all not currently installed but when installed they didn't help.
Any ideas?
try removing ALL drivers you installed for the phone and try installing just the htc ones (not sync manager)
Sony instructions are awful, I downloaded both the Studio and the SDK tools and things are just... "off" ( f.ex., android_winusb.inf doesn't even exist anywhere in either Studio or SDK tools to be replaced with ).
So I downloaded minimal ADB and fastboot, and I'm having trouble getting the device to be recognized while in fastboot - in device manager, "S1 boot" is unrecognized - I've tried using the drivers I've downloaded from Sony to no avail. Downloaded Xperia software and flashtool, installed drivers from flashtool ( XZ wasn't included in the ****ing thing, of ****ing course it wasn't... ), same thing.
"fastboot devices" simply isn't procuring an answer, and trying to jump ahead and do the unlock, it says that it's pending for devices to show up ( obviously ).
Some help?
Try this guide: https://forum.xda-developers.com/xperia-xz/how-to/how-to-unlock-bl-kernel-twrp-root-t3541648
btw. Sony use custom adb/fastboot driver (link in guide). If I remember correctly, this driver works, however you have to manually point it in device manager (ignore prompt about being incompatible).
You could also try drivers available in Flashtool - in Devices -> Check Driver menu.
http://imgur.com/a/DYGuG
can't get Android WinUSB driver to install. Any help?
edit
when connected while on, it displays this in flashtool : http://imgur.com/a/SqzuB
bump
Did you try to manually select driver for fastboot device? You have to choose from all drivers, not using automated search. Windows will complain it's incompatible, but it should work.
Win10, in fastboot mode the device cannot be found, but it can be found in adb. I installed drivers from Sony's website. In fastboot mode the device manager shows under 'other', in adb it is normal and shows 'Sony sa0116 ADB interface driver'. As far as I know the driver is the same for adb and fastboot...my Pixel is recognised with no problem, only this Sony...anyone knows how to get it recognised in fastboot mode?
Sorted the driver issue... didn't install it properly...
Go to Windows device manager look for one called x-boot or android (your xperia) and open the driver details.
Klick update driver and next choose look for software on computer. Next window gives you the option to pick one of common devices. Install the sony driver for adb interface.
Could give a zip of it if needed.
After the manual driver update it should recognize your phone immediately - if you have checked the "fastboot devices" prompt before just repeat that (no reboot or reconnection necessary)
Win 10 seems to have problems. I downgraded to win 7 all sorted.
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
funkoot said:
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
Click to expand...
Click to collapse
unfortunatly, adb is the only way to install twrp.
the drivers (i attached) [from Sony by the way] need to be installed.
You need to install this driver/ file : android_winusb.inf
then boot your phone to fastboot (volume + [up] only) or with adb (adb reboot fastboot) and windows should detect "a new device" which (normaly) is called "android" with exclamation mark.
Tap "update driver"
Search on PC
select from list
ADB interface
Samsung Android ADB Interface is the driver you need to select for windows to detect the phone
And then theoretically it should work.
If that doesn't work, look if a USB port (either PC/Phone/Cable) is broken/damaged etc.