Try this first:
Uninstall (and delete if possible) the driver then reinstall it
Install the USB-Drivers from the Android SDK first (should automatically be checked to install when opening the SDK Manager)
If the above fails here is how to manually install the drivers for USB-debugging:
Method 1:
Download the Google USB drivers from here
Extract the ZIP anywhere
In the Windows Device Manager right click "G Watch" and select to update the drivers
Select search for drivers on the computer (2nd option)
Point Windows to that folder you just extracted (should be called "usb_driver")
Select that folder and Windows should install the correct drivers. You might have to restart the PC.
If method 1 fails (which was the case for me) go to method 2
Method 2:
Again in the Windows Device Manager right click "G Watch" and select to update the drivers
Select search for drivers on the computer (2nd option)
Select choose driver from a list of device drivers on this computer
Choose "Android Device" and click next
Select "Google" as manufacturer and "Android ADB Interface Version X.x.x.x" (newest one, for me it is 9.0.0.0) as model then click next
Select yes in the next dialogue
Windows should now manually install this driver
Remember that you also have to allow USB debugging on the watch first and also accept the warning on the phone that will appear after the watch drivers are correctly installed, else ADB will not work.
The options might not always be accurate as my computer language is set to german and I just freely translated
Make sure you have an up to date ADB version as well. I updated both driver and platform-tools from SDK manager. I loaded the COMPOSITE ADB version 10 driver.
Also you may have to turn on Bluetooth Debuging in Wear App and on Watch before you can get a prompt to authorize your PC ADB connection. This will likely show on the Phone not the watch to accept. (I ran into this issue last night)
spiderflash said:
Try this first:
Uninstall (and delete if possible) the driver then reinstall it
Install the USB-Drivers from the Android SDK first (should automatically be checked to install when opening the SDK Manager)
If the above fails here is how to manually install the drivers for USB-debugging:
Method 1:
Download the Google USB drivers from here
Extract the ZIP anywhere
In the Windows Device Manager right click "G Watch" and select to update the drivers
Select search for drivers on the computer (2nd option)
Point Windows to that folder you just extracted (should be called "usb_driver")
Select that folder and Windows should install the correct drivers. You might have to restart the PC.
If method 1 fails (which was the case for me) go to method 2
Method 2:
Again in the Windows Device Manager right click "G Watch" and select to update the drivers
Select search for drivers on the computer (2nd option)
Select choose driver from a list of device drivers on this computer
Choose "Android Device" and click next
Select "Google" as manufacturer and "Android ADB Interface Version X.x.x.x" (newest one, for me it is 9.0.0.0) as model then click next
Select yes in the next dialogue
Windows should now manually install this driver
Remember that you also have to allow USB debugging on the watch first and also accept the warning on the phone that will appear after the watch drivers are correctly installed, else ADB will not work.
The options might not always be accurate as my computer language is set to german and I just freely translated
Click to expand...
Click to collapse
Yes, worked Thanks!!
i can finally get adb to see my g watch, but it only comes up as unauthorized, i can't seem to get past that point,
fixed.
tomh1979 said:
i can finally get adb to see my g watch, but it only comes up as unauthorized, i can't seem to get past that point,
Click to expand...
Click to collapse
take the watch off the charger. turn the screen of your phone on. then place the watch on the dock connected to the pc again. there should now come up a warning on the phone about accepting the usb debugging. accept it and your done.
you probably didn't see the notification before as it comes up on the phone and not the watch so when your phone screen is off you won't see it.
I always get a 'Code 28'-error. Any ideas? It says: "The drivers for this device are not installed. (Code 28)"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BTW: ADB access was already accepted on my phone.
Any ideas? Thanks in advance.
brakke97 said:
I always get a 'Code 28'-error. Any ideas? It says: "The drivers for this device are not installed. (Code 28)"
Any ideas? Thanks in advance.
Click to expand...
Click to collapse
Which driver did you select exactly?
Same problem... Can't install driver
So here's what I did.... I downloaded the latest google usb drivers. Putted the usb drivers folder into C disc in a folder android... So C//android/usb_drivers (I don't know if the line I typed is written right but you know where it is and what I'm talking about )
Then I plug in my watch (usb debugging already checked), right click the G watch in device manager. Update drivers.... Search manually to the downloaded usb driver folder (android/usb_drivers).
If I press next it fails. So I have to select my device... The only device closest to what I think is the right device is the Samsung android device.
So I press next it completes but still not properly connected.
Read about the Samsung android device issue... So deleted the drivers completely... Again... Reconnected my watch but it always shows as Samsung android device....
Tried it on Windows 8 and 7...no luck so far...
Haven't tried it with the sdk manager but it's not so clear to me... It is only to download the USB drivers? Or also to install them properly?
Pls help! I wanna root this bit**
Thanks!
liobeir said:
So here's what I did.... I downloaded the latest google usb drivers. Putted the usb drivers folder into C disc in a folder android... So C//android/usb_drivers (I don't know if the line I typed is written right but you know where it is and what I'm talking about )
Then I plug in my watch (usb debugging already checked), right click the G watch in device manager. Update drivers.... Search manually to the downloaded usb driver folder (android/usb_drivers).
If I press next it fails. So I have to select my device... The only device closest to what I think is the right device is the Samsung android device.
So I press next it completes but still not properly connected.
Read about the Samsung android device issue... So deleted the drivers completely... Again... Reconnected my watch but it always shows as Samsung android device....
Tried it on Windows 8 and 7...no luck so far...
Haven't tried it with the sdk manager but it's not so clear to me... It is only to download the USB drivers? Or also to install them properly?
Pls help! I wanna root this bit**
Thanks!
Click to expand...
Click to collapse
Have u tried @Tomsgt G watch toolkit?
dude1981 said:
Have u tried @Tomsgt G watch toolkit?
Click to expand...
Click to collapse
please help me drivers adb for G WACHT , 2 METOD FAILED
no popup on phone
Hi should the popup come upon every phone I have tried rebooting phone factory reset watch reboot computer delete and re install drivers I just cant get the popup to come up on phone when i enable adb I ave tried over and over
i dont even get the chance to install the driver. i am getting the connect/dissconnect sound all the time. i dont believe that my device or the charging station is broken. pins look fine
liobeir said:
So here's what I did.... I downloaded the latest google usb drivers. Putted the usb drivers folder into C disc in a folder android... So C//android/usb_drivers (I don't know if the line I typed is written right but you know where it is and what I'm talking about )
Then I plug in my watch (usb debugging already checked), right click the G watch in device manager. Update drivers.... Search manually to the downloaded usb driver folder (android/usb_drivers).
If I press next it fails. So I have to select my device... The only device closest to what I think is the right device is the Samsung android device.
So I press next it completes but still not properly connected.
Read about the Samsung android device issue... So deleted the drivers completely... Again... Reconnected my watch but it always shows as Samsung android device....
i wanna use the android wear apk installer. but it won't conect to the watch...
Tried it on Windows 8 and 7...no luck so far...
Haven't tried it with the sdk manager but it's not so clear to me... It is only to download the USB drivers? Or also to install them properly?
Pls help! I wanna root this bit**
Thanks!
Click to expand...
Click to collapse
same is this a problem. cause it keeps saying samsung adb drivers. i wanna load some apk on it...
hum seems to work maybe i need root
just unlocked bootloader XD
help!!
So I bought my Lg G Watch off some dude and it turns out the watch was Rooted. I tried to reset to factory default but it wouldn't let me and then i was told that I had to unroot it first but to do this I need to install the Lg G Watch Drivers which is where my problem lies! When I open device manager my device does not appear anywhere there, I have ADB debugging turned on but apparently I have to have it paired to a phone which I also can't do because in order to pair it to a new phone I have to factory reset it. I'm stuck, someone please help Ive also tried to do the Android SDK way of installing the drivers but nothing there either.
Jonathan3440 said:
So I bought my Lg G Watch off some dude and it turns out the watch was Rooted. I tried to reset to factory default but it wouldn't let me and then i was told that I had to unroot it first but to do this I need to install the Lg G Watch Drivers which is where my problem lies! When I open device manager my device does not appear anywhere there, I have ADB debugging turned on but apparently I have to have it paired to a phone which I also can't do because in order to pair it to a new phone I have to factory reset it. I'm stuck, someone please help Ive also tried to do the Android SDK way of installing the drivers but nothing there either.
Click to expand...
Click to collapse
You don't need to unroot the watch to reset it. On the watch just go to settings -> factory reset
Does not appear in device manager
OK I have tried my best to resolve this, but need to ask for help....
My g watch (LG-W100) does not appear on the device manager.... unless in fastboot mode.
I have, in the past, unlocked the bootloader, ghoma'd it (is that a thing?) but as support has now stopped, i returned my watch to stock using the ghoma tool.
I didn't change anything on my 2 pc's that I have used, so I assume it's a "watch" thing, my "about" says...
Software Version 5.0.1 (want to update this)
Build number LWX48P
Android Wear 1.0.5.1627902
Things i have tried....
Reset watch...3 times. enabled adb debugging, enabled bluetooth debugging.
Revoked permissions (was hoping to see a request on my phone, but nothing).
Put watch into fastboot mode (the only time the PC "see's" the watch) and followed the usb driver guides.
Tried to adb from recovery mod, the watch disappears from the device manager then so no adb.
Tried running "OTA Update to Lollipop 5.0.2 from kitkat KNX01Q" whilst in fastboot... no go.
Tried running "LG G Watch Restore Tools" whilst in fastboot... no go.
Cleaning the contacts on the watch and cradle (although as it shows up in fastboot, I don't think this is a problem).
Hitting it.... no go.
Swearing at it... no go.
REALLY Swearing at it... no go!
Last resort, looking on google for solutions... no go
Just to be clear, this is not a "see it in Device manager, click on it, driver update etc".... it does not appear on Device manager unless in fastboot.
Has anyone else come across this? If so, please help!
Thanks for sticking with it this far!
Boyzdad said:
OK I have tried my best to resolve this, but need to ask for help....
My g watch (LG-W100) does not appear on the device manager.... unless in fastboot mode.
I have, in the past, unlocked the bootloader, ghoma'd it (is that a thing?) but as support has now stopped, i returned my watch to stock using the ghoma tool.
I didn't change anything on my 2 pc's that I have used, so I assume it's a "watch" thing, my "about" says...
Software Version 5.0.1 (want to update this)
Build number LWX48P
Android Wear 1.0.5.1627902
Things i have tried....
Reset watch...3 times. enabled adb debugging, enabled bluetooth debugging.
Revoked permissions (was hoping to see a request on my phone, but nothing).
Put watch into fastboot mode (the only time the PC "see's" the watch) and followed the usb driver guides.
Tried to adb from recovery mod, the watch disappears from the device manager then so no adb.
Tried running "OTA Update to Lollipop 5.0.2 from kitkat KNX01Q" whilst in fastboot... no go.
Tried running "LG G Watch Restore Tools" whilst in fastboot... no go.
Cleaning the contacts on the watch and cradle (although as it shows up in fastboot, I don't think this is a problem).
Hitting it.... no go.
Swearing at it... no go.
REALLY Swearing at it... no go!
Last resort, looking on google for solutions... no go
Just to be clear, this is not a "see it in Device manager, click on it, driver update etc".... it does not appear on Device manager unless in fastboot.
Has anyone else come across this? If so, please help!
Thanks for sticking with it this far!
Click to expand...
Click to collapse
OK, problem solved....
I stumbled over root junky's youtube vid, a comment from a user had a similar problem, root junky's advice, get "LG G Watch Restore Tools V8.zip" from here... Root Junky's excellent site!. Now...
1) Put watch into fastboot mode (hold reset button for 10 seconds, and then when the LG logo come up, swipe from top left to bottom right).
2) Run "1 LG G Watch Tools for Windows.bat"
3) Ensure your watch (device) is shown.
4) Select "6" (Restore your G watch to stock)... let it do it's thing.
5) My watch got stuck in a boot loop....so...
6) Reset into fastboot, then recovery mode (tap ">" twice then tap "o") .
7) When in recovery mode, "wipe data/factory reset" (swipe down twice then right, then OK).
8) Back in recovery mode, "wipe cache partition" (swipe down 3 times then right).
9) Finally "reboot system now"..... my watch then showed up on windows as all tutorials
I then updated firmware from root junky's site (link above)... all good, thanks root junky!
Hopefully this will help someone!
Thanks a million.. method 2 worked for me
Related
Hello, I'm facing a problem while trying to root my Sony Tablet S. Using "S.onyTablet.S__ALLinONE__v6.3" I can't start rooting my device because I get stucked when it says "waiting for device", nothing happens even if I wait 10 minutes.
I installed the ADB drivers and executed "adb devices" command, all went fine. I can see my tablet on my PC and have access to storage.
Is there sonthing I'm missing ? I tried other root methods using the same script but same result, once "waiting for device" and in other time "path specified inaccessible"
I hope you can guide me. Thanks
webdzdz said:
Hello, I'm facing a problem while trying to root my Sony Tablet S. Using "S.onyTablet.S__ALLinONE__v6.3" I can't start rooting my device because I get stucked when it says "waiting for device", nothing happens even if I wait 10 minutes.
I installed the ADB drivers and executed "adb devices" command, all went fine. I can see my tablet on my PC and have access to storage.
Is there sonthing I'm missing ? I tried other root methods using the same script but same result, once "waiting for device" and in other time "path specified inaccessible"
I hope you can guide me. Thanks
Click to expand...
Click to collapse
Go into tablet's Settings > Developer Options and set USB Debugging to ON.
Cat McGowan said:
Go into tablet's Settings > Developer Options and set USB Debugging to ON.
Click to expand...
Click to collapse
I already did that and checked for "unknown sources" as well.
do not run AiO directly from archive - unpack it, best location is root of C:\ for example.
then try to root. if it still fails, then try to right-click - run as admin.
if you have still problems - run task manager on pc, and check if some adb process exists,
if yes - kill it, then try again to use AiO.
I also had similar problem when had installed Droid Explorer - it runned in background,
with its adb - which caused some problems with communication.
oh, and always use newest ver - currently v6.4 (not 6.3).
br
condi
condi said:
do not run AiO directly from archive - unpack it, best location is root of C:\ for example.
then try to root. if it still fails, then try to right-click - run as admin.
if you have still problems - run task manager on pc, and check if some adb process exists,
if yes - kill it, then try again to use AiO.
I also had similar problem when had installed Droid Explorer - it runned in background,
with its adb - which caused some problems with communication.
oh, and always use newest ver - currently v6.4 (not 6.3).
br
condi
Click to expand...
Click to collapse
Same here, Droid Explorer became a disappointment because of that unfortunately.
Sent from my Nexus 4 using xda app-developers app
Thank you for your advices, so :
-updated to 6.4........................................ok
-adb process kill from task manager..........ok (didn't find any)
-unpack root software in C:\....................ok
- run as admin.....................................ok
- Root..................................................Failed, still getting stuck on "waiting for device"
Nonetheless, I noticed when running root software, I killed adb process created by the software and there for one second it recognized my tablet but the adb process turned on again and I got "error device not detected"
I am getting crazy, I rooted many phones without any problem, but this tablet........Grrrrrrrrr.......any suggestions?
Try changing the adb files from another source. That was solved my problem.
Sorry for bad English.
webdzdz said:
Thank you for your advices, so :
-updated to 6.4........................................ok
-adb process kill from task manager..........ok (didn't find any)
-unpack root software in C:\....................ok
- run as admin.....................................ok
- Root..................................................Failed, still getting stuck on "waiting for device"
Nonetheless, I noticed when running root software, I killed adb process created by the software and there for one second it recognized my tablet but the adb process turned on again and I got "error device not detected"
I am getting crazy, I rooted many phones without any problem, but this tablet........Grrrrrrrrr.......any suggestions?
Click to expand...
Click to collapse
Connect tablet to computer.
Power on tablet. Best to have tablet connected to charger or at least, fully charged.
Open Windows Device Manager.
In Device Manager, check to see if these two devices are shown.
Android Phone > Android Composite ADB Interface
Portable Devices > Sony Tablet S
If either is missing or has a yellow triangle next to it, ADB drivers need to be installed/reinstalled or the USB cable is defective.
If both are shown, then run adb.exe to see if it detects your tablet.
Open a command window in Condi's AiO's \files directory; e.g., C:\S.onyTablet.S__ALLinONE__v6.4\files.
Type the following.
adb kill-server
adb devices
The following should be displayed.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
2755010100xxxxx device
(Note: xxxxx added by me to hide actual serial number.)
Before closing the command window, type the following.
adb kill-server
If nothing was shown under "List of devices attached", then either the USB cable is defective or the adb.exe supplied with Condi's AiO is not compatible with your tablet (unlikely) and you will need to install and use a different version of adb.exe.
Good luck.
I ended up having to install Koush's universal ADB driver to get it to work with mine, however that may be because I have drivers from Samsung, HTC, and Sony for ADB on my computer already.
Cat McGowan said:
If nothing was shown under "List of devices attached", then either the USB cable is defective or the adb.exe supplied with Condi's AiO is not compatible with your tablet (unlikely) and you will need to install and use a different version of adb.exe.
Good luck.
Click to expand...
Click to collapse
Thank you very very very much, at last I rooted my tablet, indeed it was adb drivers which was a little daizy, I installed it manually and every thing went smooth.
Thanks to all of you.:good::good::good:
Cat McGowan said:
Connect tablet to computer.
Power on tablet. Best to have tablet connected to charger or at least, fully charged.
Open Windows Device Manager.
In Device Manager, check to see if these two devices are shown.
Android Phone > Android Composite ADB Interface
Portable Devices > Sony Tablet S
If either is missing or has a yellow triangle next to it, ADB drivers need to be installed/reinstalled or the USB cable is defective.
If both are shown, then run adb.exe to see if it detects your tablet.
Open a command window in Condi's AiO's \files directory; e.g., C:\S.onyTablet.S__ALLinONE__v6.4\files.
Type the following.
adb kill-server
adb devices
The following should be displayed.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
2755010100xxxxx device
(Note: xxxxx added by me to hide actual serial number.)
Before closing the command window, type the following.
adb kill-server
If nothing was shown under "List of devices attached", then either the USB cable is defective or the adb.exe supplied with Condi's AiO is not compatible with your tablet (unlikely) and you will need to install and use a different version of adb.exe.
Good luck.
Click to expand...
Click to collapse
good afternoon I have a problem with the root, the program detected the tablet but I stay in this
R5A fw detected using new root method!
* Waiting for device
* Device found
* pushing exploit
* But it does not progresses
device manager and portable devices (sony tablet) brand me a yellow triangle please help need to be root: Llanto:
velgeek said:
good afternoon I have a problem with the root, the program detected the tablet but I stay in this
R5A fw detected using new root method!
* Waiting for device
* Device found
* pushing exploit
* But it does not progresses
device manager and portable devices (sony tablet) brand me a yellow triangle please help need to be root: Llanto:
Click to expand...
Click to collapse
With your tablet connected to your computer, open Windows Device Manager, then right-click on the device with the yellow triangle and select "Update Driver Software" to re-install the device drivers. If the drivers were previously installed and working, they should re-install without problem. If they don't, re-install them using the tool or method you used the first time you installed them.
Cat McGowan said:
With your tablet connected to your computer, open Windows Device Manager, then right-click on the device with the yellow triangle and select "Update Driver Software" to re-install the device drivers. If the drivers were previously installed and working, they should re-install without problem. If they don't, re-install them using the tool or method you used the first time you installed them.
Click to expand...
Click to collapse
I have installed the drivers but to stay in pushing exploit
not if they are bad drivers to install, if you have them please put some link to the original drivers for windows 8 64bit
Here some pictures of the problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and whether aparese me if I remove the USB debugging
velgeek said:
I have installed the drivers but to stay in pushing exploit
not if they are bad drivers to install, if you have them please put some link to the original drivers for windows 8 64bit
Here some pictures of the problemView attachment 2091987
and whether aparese me if I remove the USB debugging
View attachment 2091988
Click to expand...
Click to collapse
From the images you posted, the ADB drivers appear to be installed and working; however, here is a link for downloading the ADB drivers and instructions for installing them on Windows 8.
BluechipJ's Automated ADB Driver Installer for Sony Tablet S and P
Also, USB Debugging must be set ON during the process.
Cat McGowan said:
From the images you posted, the ADB drivers appear to be installed and working; however, here is a link for downloading the ADB drivers and instructions for installing them on Windows 8.
BluechipJ's Automated ADB Driver Installer for Sony Tablet S and P
Also, USB Debugging must be set ON during the process.
Click to expand...
Click to collapse
Thank you very much as I could, was the usb cable was damaged but the change and has been perfect, now I'm root
probleeemm!!!!! helpmee
hello I have a problem and I have root on my tablet XD thanks, but now try to update my tablet sony flasher tool, but you mistakenly install the Sony Tablet P and now I can not return it and try to ordinary restore factory wing And Also try Correctly installed, but when it finishes flashing and restarted, does not change anything. Could anyone please tell me how to fix it: Llanto:
today i reflashed my phone with stock 4.0.4 french ftf and it is working fine with usb debugging off but with debugging on, my computer doesnt see the phone! what should i do?
i have reflashed it but still usb debugging mode is not working! help! please what can the problem be?
plz help !
im stuck on stock! no root! nothing good!
First: Don't Panic.
Second: Check your drivers. If not properly installed, try one from sony (just google your device together with "adb driver").
Third: after a complete flash it's like you've never touched your device, means you have to re-root your device normally.
i hope this helps.
murderered said:
First: Don't Panic.
Second: Check your drivers. If not properly installed, try one from sony (just google your device together with "adb driver").
Third: after a complete flash it's like you've never touched your device, means you have to re-root your device normally.
i hope this helps.
Click to expand...
Click to collapse
no its not working!
ive installed a new windows on virtualbox but there also no usb debugging is working!
and how do you install the adb drivers in the zip?
even though it is in debugging mode..when i try to root, it says please connect your phone in debugging mode
Can't say if it generally works with virtualbox. try to get drivers for your native system.
So the question is now: What's your host system?
If it's Windows, get Flashtool and install included driver (found in <FlashtoolInstallDir>\driver) just for rooting the device.
If you're using linux you can look if your device was recognized properly with lsusb it should be listed there.
You can try it too in virtualbox, but i don't trust the USB-driver (i would not flash or so through it) and do not recommend it.
murderered said:
Can't say if it generally works with virtualbox. try to get drivers for your native system.
So the question is now: What's your host system?
If it's Windows, get Flashtool and install included driver (found in <FlashtoolInstallDir>\driver) just for rooting the device.
If you're using linux you can look if your device was recognized properly with lsusb it should be listed there.
You can try it too in virtualbox, but i don't trust the USB-driver (i would not flash or so through it) and do not recommend it.
Click to expand...
Click to collapse
i am using windows 7 32 bit
ive already have flashtool and have tried to install the drivers but nothing works!
Ok, you've installed (i assume) the right adb drivers for your device through the installer located in <FlashtoolsInstallDir>\driver.
So is there any Android/Sony (Ericsson) named device in your device manager? What does Flashtools write if you connect? If your device is listed in device manager, does it show an error, if yes which error?
murderered said:
Ok, you've installed (i assume) the right adb drivers for your device through the installer located in <FlashtoolsInstallDir>\driver.
So is there any Android/Sony (Ericsson) named device in your device manager? What does Flashtools write if you connect? If your device is listed in device manager, does it show an error, if yes which error?
Click to expand...
Click to collapse
in flashtool it shows the same thing in on and off
the 2nd one is debugging on and 3rd with off
Please post output of "adb devices" (if not recognizing, try again after "adb usb"). If no serial number/device is shown then do following:
There is a newer version of Flashtool available, update to 0.9.11, http://androxyde.github.io/
check after reinstallation (of drivers, too)
Maybe you have to try sonys driver from the zip. So extract them (all files).
right click at your device in the device manager
click to "update driversoftware" (or something like that, i don't have english windows)
click "search on my computer for new drivers"
choose from list
display all devices
click the button below the list (i have no idea what there could be written, it's not "windows update")
search for the inf-file extracted and choose the "sa<somenumbers>adb.inf"
if not already installing, choose "Sony Ericsson saXXXX ADB Interface Driver"
reboot (pc)
check again
Ive been trying to root my device for over a month now, and i havent had any luck. Ive used different USB drivers software and Hardware. Ive used different cords from stock to the ones from my job and friends yet i still have failed to root it. ADB reconizes my device no problem when its booted up, but as soon as i boot into FASTBOOT mode my computer doesnt reconize the device. What am I doing wrong or am I doomed to have an unrooted device?
I had the same issue with windows Vista.
Grab the attached file. Unzip to wherever.
Plug your phone into the pc IN fastboot mode. Open Device Manager.
Find the messed up driver, usually indicated with a yellow symbol in the list.
Right click it and update driver. Don't let it auto search for one. Manually tell it where that driver is that you just unzipped. It will show a list and chose the android bootloader one. It will warn you stating it's not correct, ignore that warning.
If you need more detailed instructions just holla.
Peace.
Did you try fastboot commands when in the bootloader? Remember that adb is only for when the device is booted up normally. Just making sure...
Sent from my LG-H901 using XDA-Developers mobile app
open device manager, you will see the device with the yellow symbol, right click and select update driver software
after browse my computer for driver software --> let me pick from a list of device drivers in my pc --> android adb interface! . click on yes. this worked for me
Once you got into android modding, an unrooted phone becomes almost useless.
Now my problem is that I´ve got one.
Couple of days ago my Elephone P9000 arrived from amazon but I can´t connect it to a PC since it says that no device is detected.
Yes, the drivers are installed properly!
I thought that isn´t a problem because there is Kingroot.
Turns out the following rooting apps don´t work for me:
Kingroot (Kingoroot), iRoot, z4root, Framaroot, Towelroot, Oneclickroot, Universal Androot, Root Genius, Baidu
Custom Recovery isn´t installed because, of course, no root.
Now how do I root?
ThisIsMyMaster said:
Once you got into android modding, an unrooted phone becomes almost useless.
Now my problem is that I´ve got one.
Couple of days ago my Elephone P9000 arrived from amazon but I can´t connect it to a PC since it says that no device is detected.
Yes, the drivers are installed properly!
I thought that isn´t a problem because there is Kingroot.
Turns out the following rooting apps don´t work for me:
Kingroot (Kingoroot), iRoot, z4root, Framaroot, Towelroot, Oneclickroot.
Custom Recovery isn´t installed because, of course, no root.
Now how do I root?
Click to expand...
Click to collapse
The first thing you need to accomplish is to get your PC to recognize your phone, rooting from there is going to make life easier, but yes, I know you already know that. If your using windows 10, maybe check this thread out on Elephone Forum:
http://bbs.elephone.hk/forum.php?mod=viewthread&tid=12240&page=1&ordertype=1#pid129322
jotei66 said:
The first thing you need to accomplish is to get your PC to recognize your phone, rooting from there is going to make life easier, but yes, I know you already know that. If your using windows 10, maybe check this thread out on Elephone Forum:
(link removed)]
Click to expand...
Click to collapse
That´s the tutorial that I was going to do but when my phone is shut down, my pc doesn´t detect the device and flash tool neither.:crying:
ThisIsMyMaster said:
That´s the tutorial that I was going to do but when my phone is shut down, my pc doesn´t detect the device and flash tool neither.:crying:
Click to expand...
Click to collapse
Firstly is your PC finding your phone ok with the PC on? If yes.. all good - if no you need to sort this out first.
Then, ensure you have installed the MTK driver on your PC (these are the Media Tek drivers which will find your phone when it is off) instructions here:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Then flashtools should work fine with your phone off.
Just a tip using FlashTools (Im on windows 10 - I dont know if this applies to other windows)
In flashtools, press download first (without phone connected), give it 5 secs and then connect your phone to your PC with the volume up button pressed at the same time. Once you see FlashTools starting to flash your phone, release the volume button. I have to do this all the time in order for my phone to be found on Windows 10.
jotei66 said:
Firstly is your PC finding your phone ok with the PC on? If yes.. all good - if no you need to sort this out first.
Then, ensure you have installed the MTK driver on your PC (these are the Media Tek drivers which will find your phone when it is off) instructions here:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Then flashtools should work fine with your phone off.
Just a tip using FlashTools (Im on windows 10 - I dont know if this applies to other windows)
In flashtools, press download first (without phone connected), give it 5 secs and then connect your phone to your PC with the volume up button pressed at the same time. Once you see FlashTools starting to flash your phone, release the volume button. I have to do this all the time in order for my phone to be found on Windows 10.
Click to expand...
Click to collapse
To start of, I am using Windows 10 as you do.
When I connect my phone when it´s turned on, I get the small icon in the taskbar that allows me to remove the device safely or open devices and printer.
There, my device is put to a section called not specified and it has a small yellow icon.
Only is it called "P9000" which is alright.
Windows explorer acts like no device is connected at all.
When I connect my phone as it is turned off, I still get the notification "USB Device wasn´t recognized." and
windows explorer still doesn´t care as well as the flash tool.
The link you gave me isn´t the one I previously used to install the drivers so I gave it a try.
There are two different ways mentioned in the posts #1 and #4 so I started with the first one.
(Spoiler: Both don´t work for me!)
Everything worked until a step almost at the end where I am told to connect my off-switched phone to the pc.
The tutorial tells me that there should now be a preloader unknown device or something at Device Manager > Ports (COM & LPT) that I would need to proceed further.
I didn´t get that one.
Dead end for me so I went on to the next tutorial in post #4.
In that post I am told to remove a MTK USB Port at Device Manager > Ports (COM & LPT) right after installing the .inf driver files (Yes, I installed the 64 bit version and do have a 64 bit PC).
Ignoring that step didn´t help any of the problems I had before so I got a dead end here, too.
The "Volume-Up-Trick" did help me neither, probably cause of the not working drivers.
ThisIsMyMaster said:
To start of, I am using Windows 10 as you do.
When I connect my phone when it´s turned on, I get the small icon in the taskbar that allows me to remove the device safely or open devices and printer.
There, my device is put to a section called not specified and it has a small yellow icon.
Only is it called "P9000" which is alright.
Windows explorer acts like no device is connected at all.
When I connect my phone as it is turned off, I still get the notification "USB Device wasn´t recognized." and
windows explorer still doesn´t care as well as the flash tool.
The link you gave me isn´t the one I previously used to install the drivers so I gave it a try.
There are two different ways mentioned in the posts #1 and #4 so I started with the first one.
(Spoiler: Both don´t work for me!)
Everything worked until a step almost at the end where I am told to connect my off-switched phone to the pc.
The tutorial tells me that there should now be a preloader unknown device or something at Device Manager > Ports (COM & LPT) that I would need to proceed further.
I didn´t get that one.
Dead end for me so I went on to the next tutorial in post #4.
In that post I am told to remove a MTK USB Port at Device Manager > Ports (COM & LPT) right after installing the .inf driver files (Yes, I installed the 64 bit version and do have a 64 bit PC).
Ignoring that step didn´t help any of the problems I had before so I got a dead end here, too.
The "Volume-Up-Trick" did help me neither, probably cause of the not working drivers.
Click to expand...
Click to collapse
Ok first things first, lets make sure your P9000 is fine with your phone on. You said:
When I connect my phone when it´s turned on, I get the small icon in the taskbar that allows me to remove the device safely or open devices and printer. There, my device is put to a section called not specified and it has a small yellow icon.
Only is it called "P9000" which is alright.
Click to expand...
Click to collapse
(make sure in dev options on your phone USB debugging is ON and USB config is MTP)
So from that you simply need to (In Device Manager) right click > Update Driver Software > Browse My PC for Driver Software > Let me pick from a list of device drivers from my PC > then choose MTP USB Device
Once windows installs this, a box should pop up showing your P9000 internal storage and SD Card (if you have one in phone)
To ensure that your PC is now finding your phone ok, restart PC and plug your phone in - you should be prompted by windows to choose a default action when this device is connected (I choose transfer files or something similar). Then everytime you connect your phone, a box will pop up showing allowing you to access your P9000.
Now onto when your P9000 is switched off... (the important part for flashing etc)
I followed the instructions at post #4 as I believe due to the anniversary update on windows 10 (the January update I believe) .. if you do not have the January update installed on your PC you would use the instructions #1
Don't worry too much if you receive "USB device not recognised" initially, (from what I have understood this is normal with the Anniversary addition of windows 10) it should disappear after few seconds or so. From what I worked out following post #4 you are kinda installing a MTK device (just so you can install the drivers) and then uninstalling that device BUT keeping the drivers installed (its VERY important when you uninstall the device you untick the delete drivers too, otherwise you have essentially deleted the MTK drivers & would have to start from scratch from post #4)
For me, when I connect my p9000 when its off it still shows "USB device not recognised", then after a few seconds this goes away and I dont have any errors under Device Manager > Ports (COM & LPT) & flashtools works fine as long as I press vol up as I connect my phone.
Hope this helps, I had a headache when I tried to install MTK drivers with my windows 10 (Anniversay Update Edition) - good luck, it was kinda trial and error
jotei66 said:
Ok first things first, lets make sure your P9000 is fine with your phone on. You said:
(make sure in dev options on your phone USB debugging is ON and USB config is MTP)
So from that you simply need to (In Device Manager) right click > Update Driver Software > Browse My PC for Driver Software > Let me pick from a list of device drivers from my PC > then choose MTP USB Device
Once windows installs this, a box should pop up showing your P9000 internal storage and SD Card (if you have one in phone)
To ensure that your PC is now finding your phone ok, restart PC and plug your phone in - you should be prompted by windows to choose a default action when this device is connected (I choose transfer files or something similar). Then everytime you connect your phone, a box will pop up showing allowing you to access your P9000.
Now onto when your P9000 is switched off... (the important part for flashing etc)
I followed the instructions at post #4 as I believe due to the anniversary update on windows 10 (the January update I believe) .. if you do not have the January update installed on your PC you would use the instructions #1
Don't worry too much if you receive "USB device not recognised" initially, (from what I have understood this is normal with the Anniversary addition of windows 10) it should disappear after few seconds or so. From what I worked out following post #4 you are kinda installing a MTK device (just so you can install the drivers) and then uninstalling that device BUT keeping the drivers installed (its VERY important when you uninstall the device you untick the delete drivers too, otherwise you have essentially deleted the MTK drivers & would have to start from scratch from post #4)
For me, when I connect my p9000 when its off it still shows "USB device not recognised", then after a few seconds this goes away and I dont have any errors under Device Manager > Ports (COM & LPT) & flashtools works fine as long as I press vol up as I connect my phone.
Hope this helps, I had a headache when I tried to install MTK drivers with my windows 10 (Anniversay Update Edition) - good luck, it was kinda trial and error
Click to expand...
Click to collapse
I am running the Anniversay Update Edition and don´t get an popup window when connecting my phone turned on.
As far is I can tell, a working connection with the device running is more important in the first place.
Now I don´t quite understand your instructions at this point:
jotei66 said:
So from that you simply need to (In Device Manager) right click > Update Driver Software > Browse My PC for Driver Software > Let me pick from a list of device drivers from my PC > then choose MTP USB Device
Click to expand...
Click to collapse
In Device Manager right click, but where?
Blank space? Definetly not.
According to the linked tutorial, I´d have to right click on something like "unknown device" or something similar.
But that doesn´t show up in my list.
In the next section you said:
jotei66 said:
you are kinda installing a MTK device (just so you can install the drivers) and then uninstalling that device BUT keeping the drivers installed
Click to expand...
Click to collapse
I can understand the point but after installing that driver package, there is no MTK device in my device manager that I could uninstall.
I seriously need to thank you for wasting so much time on me:angel:
When you plug your p9000 (while its turned on) into your laptop/pc... in Device Manager, probably under Universal serial Bus Controllers do you see a unknown device, or anything with a question mark / unknown device beside it ? If so, that's where you right click and follow instructions above to get your PC to recognize your handset. At this point just concentrate on getting pc to recognise while its on, then hopefully we can then move to setting up when its off.
I seriously need to thank you for wasting so much time on me
Click to expand...
Click to collapse
lol its all cool
PS: Just to make sure, in device manager, press View from top menu and "show hidden devices".. maybe it could be hidden?
jotei66 said:
When you plug your p9000 (while its turned on) into your laptop/pc... in Device Manager, probably under Universal serial Bus Controllers do you see a unknown device, or anything with a question mark / unknown device beside it ? If so, that's where you right click and follow instructions above to get your PC to recognize your handset. At this point just concentrate on getting pc to recognise while its on, then hopefully we can then move to setting up when its off.
lol its all cool
PS: Just to make sure, in device manager, press View from top menu and "show hidden devices".. maybe it could be hidden?
Click to expand...
Click to collapse
I can´t believe how stupid I am...
jotei66 said:
Just to make sure, in device manager, press View from top menu and "show hidden devices".. maybe it could be hidden?
Click to expand...
Click to collapse
Well, that solved all of my problems...
Almost...
Drivers are fully working for me now so I wanted to flash TWRP with SP Flash Tool to be able to flash the superuser .zip file.
Since drivers work now, flash tool started flashing and gave me the error you can see in the attached screenshot.
Fortunately, my phone isn´t bricked or anything.
Edit: After a couple of reboots of all my devices, I get back to where I was before: USB Device wasn´t recognized and Flash Tool doesn´t do anything.
ThisIsMyMaster said:
I can´t believe how stupid I am...
Well, that solved all of my problems...
Almost...
Drivers are fully working for me now so I wanted to flash TWRP with SP Flash Tool to be able to flash the superuser .zip file.
Since drivers work now, flash tool started flashing and gave me the error you can see in the attached screenshot.
Fortunately, my phone isn´t bricked or anything.
Click to expand...
Click to collapse
All cool & its an easy thing to miss when your not looking for it (or for that matter if you dont know that menu even existed)
That error is a preloading error, I'm assuming your flashing TWRP Recovery and like you I had similar issue - I shared a simple solution here that worked for me here (it should work fine as long as you are on Stock Elephone 2016810 Base onwards so I believe, Elephone changed the preloader or something like that in later ROMS)
So Basically, you download the Stock Elephone 2016810 Base ROM from HERE & unzip
Grab Flash Tools ver v5.1612 (if your not using that version) HERE - https://www.androidfilehost.com/?fid=24591000424940027
Then download TWRP_3.0.2.8.zip HERE & unzip
Copy the the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_2016810 Rom folder.
In Splash Tools, first flash the Elephone_P9000_2016810 Rom open "MT6755_Android_scatter" from _810 file & ensure the recovery section location points to "recovery.img" in the _810 folder also
Once your stock _810 ROM is flashed successfully, you then flash TWRP (with only recovery ticked) and ensure the recovery location points to "recovery_TWRP_3028_P9000" and your TWRP should flash fine. Make sure your using Flash Tools ver v5.1612, that worked fine for me.
There maybe an easier solution someone can point you too, but I know this worked for me no problems - you should now have TWRP recovery on stock _810 ready for you to flash your chosen ROM
jotei66 said:
All cool & its an easy thing to miss when your not looking for it (or for that matter if you dont know that menu even existed)
That error is a preloading error, I'm assuming your flashing TWRP Recovery and like you I had similar issue - I shared a simple solution here that worked for me here (it should work fine as long as you are on Stock Elephone 2016810 Base onwards so I believe, Elephone changed the preloader or something like that in later ROMS)
So Basically, you download the Stock Elephone 2016810 Base ROM from HERE & unzip
Grab Flash Tools ver v5.1612 (if your not using that version) HERE - https://www.androidfilehost.com/?fid=24591000424940027
Then download TWRP_3.0.2.8.zip HERE & unzip
Copy the the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_2016810 Rom folder.
In Splash Tools, first flash the Elephone_P9000_2016810 Rom open "MT6755_Android_scatter" from _810 file & ensure the recovery section location points to "recovery.img" in the _810 folder also
Once your stock _810 ROM is flashed successfully, you then flash TWRP (with only recovery ticked) and ensure the recovery location points to "recovery_TWRP_3028_P9000" and your TWRP should flash fine. Make sure your using Flash Tools ver v5.1612, that worked fine for me.
There maybe an easier solution someone can point you too, but I know this worked for me no problems - you should now have TWRP recovery on stock _810 ready for you to flash your chosen ROM
Click to expand...
Click to collapse
I´m going to try this now.
Do I have to go back to Stock 20160810 if I have 20161107?
Do I have to go back to Stock 20160810 if I have 20161107?
Click to expand...
Click to collapse
I guess if you download the 20161107 ROM it should work, I'm really unsure, its a newer ROM so I guess it should
jotei66 said:
I guess if you download the 20161107 ROM it should work, I'm really unsure, its a newer ROM so I guess it should
Click to expand...
Click to collapse
It didn´t work.
I did all the steps you´ve told me and ended up with the exact same problem I´ve experienced before: USB Device not recognized and SP Flash Tool doesn´t do anything after pressing the download button.
I was going to reinstall the drivers like you told me form post #4 here: https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
That didn´t do anything, I still have the same problem of my pc not recognizing my phone.
At least connecting my phone when it´s running works now.
you have to press and keep vol + when connecting the turned off phone to the computer after clicking download in FlashTools.
Regards
Fran Montero said:
you have to press and keep vol + when connecting the turned off phone to the computer after clicking download in FlashTools.
Regards
Click to expand...
Click to collapse
Tried it, didn´t help
ThisIsMyMaster said:
Tried it, didn´t help
Click to expand...
Click to collapse
MMmmm .. have you tried a different USB port? maybe a different lead if you have one? (I have two leads and I know one doesnt work for me, dunno why)
Also, after pressing download in SplashTools.. count to say 7-10 secs and then press Vol UP and connect your phone.... (I know this sounds bit stupid, but it works for me, if I connect straioght away I get errors too ref driver )
jotei66 said:
MMmmm .. have you tried a different USB port? maybe a different lead if you have one? (I have two leads and I know one doesnt work for me, dunno why)
Also, after pressing download in SplashTools.. count to say 7-10 secs and then press Vol UP and connect your phone.... (I know this sounds bit stupid, but it works for me, if I connect straioght away I get errors too ref driver )
Click to expand...
Click to collapse
No, that doesn´t help either.
I think it has to do something with installing the drivers cause after installing them, in Device Manager no new drivers are displayed except for two Mediatek Preloader USB VCOM Port (COM5) and (COM6).
But those only become visible when I check "show hidden devices".
The tutorial said that some more things should have been installed but I didn´t get any error messages so I don´t understand what shouldn´t have worked.
Sorry Im at a loss really, maybe follow this tutorial my brother followed to reinstall the MTK and try again with all the above steps, good luck
https://www.youtube.com/watch?v=NbJCbdfPlF8
Make sure your PC is in driver signature disable mode when flashing etc btw
jotei66 said:
Sorry Im at a loss really, maybe follow this tutorial my brother followed to reinstall the MTK and try again with all the above steps, good luck
https://www.youtube.com/watch?v=NbJCbdfPlF8
Make sure your PC is in driver signature disable mode when flashing etc btw
Click to expand...
Click to collapse
Didn´t help either.
Current state:
Phone On > Everything working, I get the popup window and data transfer works :good:
Phone Off > USB wasn´t recognized, Flash Tool isn´t working, no recognition in windows explorer, phone is charging, vol+ doesn´t help
MTP and USB Debugging are activated
While installing the drivers I got no error messages and everything looked same as in the tutorial
ThisIsMyMaster said:
Didn´t help either.
Current state:
Phone On > Everything working, I get the popup window and data transfer works :good:
Phone Off > USB wasn´t recognized, Flash Tool isn´t working, no recognition in windows explorer, phone is charging, vol+ doesn´t help
MTP and USB Debugging are activated
While installing the drivers I got no error messages and everything looked same as in the tutorial
Click to expand...
Click to collapse
Good to hear you can atleast use your phone to transfer etc while on
Just curious (although Im sure you have followed the video / other tutorials to the letter) but
(1) did you ensure when following video tut that when uninstalling the legacy device you unticked the driver box to ensure the drivers were actually kept installed?
(2) Check Device Manager, under the Ports (COM & LPT) section and remember you shouldn't have anything referring to a MTK device in there - ie like MTK USB Port (Com 3) ? (If you have it needs uninstalling)
(3) Seems obvious I know but you are connecting your phone and using FlashTools when your Windows Driver Enforcement is disabled? ( Literally restarting with advanced options & choosng Disbale Driver Enforcement) Many users think once you have installed the driver you can use it with Windows Drivers enforcement enabled, but you have to be in disabled mode.
Finally if you doubled checked all of those, then maybe try a different version of FlashTools (worth a try) and also try running FlashTools as Administrator when you open it - good luck
Hi,
My Nord 2 have latest update DN2103_11_A.17, and I wanted to enable VoLTE.
My computer can't detect my phone in ADB when in recovery mode, it detects only when just powered on normaly and connected.
I have latest Android plateform tools installed on computer.
Any Idea of what's wrong ?
Thanks
Adb drivers and permissions.
Try in Linux, easier
I have exactly the same problem on my OneNeplus Nord 2. I installed the MediaTek_Preloader_USB_VCOM_Drivers drivers in auto mode and even in manual mode under Windows 10. When I type adb reboot recovery the smartphone reboots in recovery mode even if it tells me seems strange see photo (sorry very small text...) but then no other orders are accepted. Same problem in bootloader mode. So I can't unlock the bootloader. Any help is welcome...
Hey I had the same issue with fastboot device not showing up. Fastboot with other devices on my PC had never been an issue.
This Fixed it for me:
Open "Device Manager" from the Windows start menu.
Your device should be listed there as "Android Device" (with a yellow indication for missing driver)
Right click the device and select "Update Driver".
Click Browse my computer for drivers.
Click Let me pick from a list of available drivers on my computer.
From the list select "Android Bootloader Interface". It is possible that you need to deselect the "Show compatible hardware" button.
Good luck.
cukierkas said:
Adb drivers and permissions.
Try in Linux, easier
Click to expand...
Click to collapse
Hi, thanks I'll try. Any specific driver for Linux?
I've read that adb in recovery mode doesn't work since A.14 update, and I'm on A.17. Anyone Can confirm that?