[Q] Problem while rooting Sony Tablet S - Sony Tablet S

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:

Related

Does the driver have to show ASUS Android Composite ADB Interface? Mine doesnt. Help.

Hi!
I keep reading that the driver shows ASUS Android Composite ADB Interface but mine shows Transformer Prime TF201 instead.
I have been able to root, unlock and flashed TWRP.
Before flashing Roms I want to install NVFLASH but I am worried that my driver is not showing that ASUS Android Composite ADB Interface name.
I tried updating as I have read but whenever I select the folder with the drivers I want I get the message that Windows has determined that my software is up to date...
Every time I try to select the folder with the drivers I get "the folder you specified doesn't contain a compatible driver"
Any idea?
UPDATE: I used the other option to install drivers and selected the ASUS Android Composite ADB Interface from a list and it installed it. I am able to access my files on the phone.
Is there a way to test fastboot and adb to make sure I am good to try nvflash?
This is Windows 7 64bit
shaolin95 said:
UPDATE: I used the other option to install drivers and selected the ASUS Android Composite ADB Interface from a list and it installed it. I am able to access my files on the phone.
Is there a way to test fastboot and adb to make sure I am good to try nvflash
Click to expand...
Click to collapse
I always test the connection using the commands "adb devices" or "fastboot devices", it will tell you if any devices are connected.
You could also push a small file to the tab (eg. baba.txt with "adb push baba.txt /sdcard/") and find it on your tab, just to make certain.
Are you using Universal Naked Drivers? Asus ones suck...
http://forum.xda-developers.com/showthread.php?p=20995229
Striatum_bdr said:
Are you using Universal Naked Drivers? Asus ones suck...
http://forum.xda-developers.com/showthread.php?p=20995229
Click to expand...
Click to collapse
I am not but I can sure try those.
But before I do, if the test passes then it I should be fine with the current drivers?
I am done with nvflash!
I followed this video to do it in case someone has the same issues
http://www.youtube.com/watch?v=J3ypzUaKxvo
CODE 10 on all 5 naked adb drivers
No matter which I choose i get told that they cannot start. I have tried all 5 options in the naked set to no avail. this is a windows 7 ultimate pc. I am trying to fix my tf201 as it just keeps looping to a TWRP screen and gives me the key driver missing message

ADB device show empty

Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
But when I reboot my tablet as USB mode and from my laptop I run cmd as Administrator, and run "adb devices" command, it just show me "List of devices attached" and then the command prompt.
I have already unlock and rooted my tablet.
Why I can't see my device id ? Please help
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yeah this process is correct. Even I've experienced this.
What I did is:
Removed the USB cable connection and reconnect.
Kill adb.exe
Restart adb.
Then device was shown to be connected.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yes, I did that but still the same. Any other suggestions?
If on windows make sure your driver's are installed.
Type in cmd
adb kill-server
adb start-server
If that doesn't work try a different usb slot. You could also try moving adb and it's dependencies to your system32 folder. It's where all your commands are stored for cmd. You won't have to navigate to the android sdk tools.
Sent from my SPH-L710 using Tapatalk 2
Have you enabled Debugging on in your phones Developer settings?
ngaisteve1 said:
Yes, I did that but still the same. Any other suggestions?
Click to expand...
Click to collapse
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
no need for that.
close any adb process either from task manager or by typing: "adb kill-server" in adb console
close everything and use this customized adb file I attached, it'll show your device.
it also has instructions and necessary files for rooting your device.
Problem
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
I have LG Optimus G (E975) i wipped all from the device and now i can't put cm11 on it, adb sideload do not work, and list of devices attached is empty. what must i do to put CM11 on my phone?:crying:
I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???
I have the same issue on my nexus 4. Yesterday it showed up with adb devices, now it's an empty list. I have USB debugging enabled and tried restarting the server. Nothing works. Any ideas?
ldemon360 said:
I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???
Click to expand...
Click to collapse
unplug the device and adb kill-server then replug the device and try
turn debugging off and then on again
I had the same problem. In my case, i had forgot to enable usb debugging after new rom.
ngaisteve1 said:
Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
Click to expand...
Click to collapse
In your case just disable USB debugging and then enable again.
fix the driver
I had this issue.
In my case when I went to device manager I could see the Device and wasn't installed correctly and could not load the drivers even after having installed them on the PC.
SO I clicked update drivers.
Select that will chose the drivers to install and select the Android Devices - ADB driver.
You will get a warning, but just ignore it and load the ADB driver for the phone.
Ensure you are in the sideload option of the recovery
Now
adb devices
it should show up as Sideload
Now sideload
Cheers
Dirk
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Thanks, this worked for me.
Just add ur device id in adb.ini
Same issue was faced by me on my micromax Q334 and xolo era, I search lot for that and finally just adding hardware id the device are detected under adb.The steps are clearly shown in my video below..
It will definitely going to sort this problem..
For that just right click on adb driver ,navigate to detail tab and search for hardware id then add to adb.INI
I have also uploaded video on that YouTube: Fix adb connection issue(Adb driver installed, but device not listed)
device listed as "? recovery"
hey,
am trying to connect honor 6(h60-L04) but am not able to see the proper name for my device is just showing "? recovery" and am trying to update the android version coz of the device is in reboot-loop so help me out here
if there is any other option to recover device give me link.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
not work my friend, the list of devices is empty
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
See below... I found there are two versions of adb.exe I was using. PTP is not the problem, but adb.exe has to be the right one or it just says offline.
vern.zimm said:
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
Click to expand...
Click to collapse
ALSO!! Get the newest driver pack from LG "LGMobileDriver_WHQL_Ver_4.1.1". The driver packs in the roots that I downloaded aren't new enough. After Windows got the right drivers I was able to see the COM ports properly.
I'm not sure if I have the root working currently. The "Newest root method V03" where you click on root.bat seems to pick the wrong COM port. When I try to do it manually with Send_command.exe using the other COM port it seems like the root process doesn't work properly. It eventually completes, but no info about what it did etc.
I'm using an LG Transpyre VS810PP with Android 5.1.1 currently, and a Windows 10 64-bit machine.

How to fix driver problems

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

[Q] [LG VS930] Unable to get ADB commands to work

Alright, I've tried installing the drivers from Verizion and also using the drivers from the Android SDK and either way I have the same problem. ADB devices shows my phone, however whenever I try to push, pull, or reboot (the only commands I have any use for atm) the command prompt hangs like it's trying to access the device but no matter how long I leave it the device will not reboot, nor will any files appear in the correct folders on either the device or my computer.
I'm trying to root my phone and this is a pretty major roadblock.
Note:
USB Debugging enabled
ADB drivers installed
Phone shows up on "adb devices"
There is no error or any other output in the console. The best way to describe this problem is that ADB hangs.
I'm running Windows 8.1 and my phone is running Android 4.1.2
Also, I don't know if this is normal but, In order to get the notification that "USB debugging connecting" I have to use the internet connection option on the phone. When using MTP, Charge only and PTP that message doesn't appear and I don't see an ADB device show up in device man.
Things I've Tried
Uninstalling all Android drivers and redownloading/installing them after restart
Restarting my phone multiple times
Running adb kill-server / adb start-server
Changing USB ports7
Thanks!
Try installing drivers from LG. This seems the right one but double check:
http://www.lg.com/us/support-mobile/lg-LGVS930

Device in Fastboot mode not recognized at all as USB device

Hey everyone,
im trying to unlock the bootloader of my LG G5, but am unable to do so as the phone is not detected at all when in fastboot mode.
While it is recognized just fine as an adb device, after rebooting into fastboot mode via adb reboot bootloader it is not recognized as an USB Device in Windows (The device manager does not show any device with wrong drivers and does not react to replugging the device). I also tried it on a different machine with the same results.
Ubuntu also does not recognize the device at all, lsusb does not output the device anywhere. It also does get recognized as an adb device when booted up normally.
I installed the necessary (I tried LG and Google) drivers and tried different USB ports (2.0 and 3.0) and cables. The phone just is not noticed as an usb device at all when in fastboot mode.
Could this be due to a broken usb port? Which seems odd because the phone is recognized when not in fastboot mode.
What else could cause this weird behaviour?
Thank You!
Just to be clear. After you booted into fastboot mode, did you try
Code:
fastboot devices
and it just showed nothing?
holgers0n said:
Hey everyone,
im trying to unlock the bootloader of my LG G5, but am unable to do so as the phone is not detected at all when in fastboot mode.
While it is recognized just fine as an adb device, after rebooting into fastboot mode via adb reboot bootloader it is not recognized as an USB Device in Windows (The device manager does not show any device with wrong drivers and does not react to replugging the device). I also tried it on a different machine with the same results.
Ubuntu also does not recognize the device at all, lsusb does not output the device anywhere. It also does get recognized as an adb device when booted up normally.
I installed the necessary (I tried LG and Google) drivers and tried different USB ports (2.0 and 3.0) and cables. The phone just is not noticed as an usb device at all when in fastboot mode.
Could this be due to a broken usb port? Which seems odd because the phone is recognized when not in fastboot mode.
What else could cause this weird behaviour?
Thank You!
Click to expand...
Click to collapse
Do you have usb debugging on because some devices require it to be on in order to be able to use fastboot on the computer.
In addition to ADB and Fastboot you have to install the "Android USB Driver" that is suitable to your phone, too, to get Fastboot working.
I forgot to mention that, oem unlock and USB debugging is enabled.
I tried installing the LG and android USB driver. But there is no way I can install these drivers to my fastboot device, as it is not recognized as an USB device at all, its like I'm plugging an USB cable with nothing attached to it into the computer.
QUOTE="User699, post: 84602251, member: 11475773"]
Just to be clear. After you booted into fastboot mode, did you try
Code:
fastboot devices
and it just showed nothing?
[/QUOTE]
Fastboot devices does not show anything.
holgers0n said:
I tried installing the LG and android USB driver. But there is no way I can install these drivers to my fastboot device, as it is not recognized as an USB device at all, its like I'm plugging an USB cable with nothing attached to it into the computer.
Click to expand...
Click to collapse
The "Android USB Driver" is a Windows OS driver, hence it must get installed in Windows OS.
jwoegerbauer said:
The "Android USB Driver" is a Windows OS driver, hence it must get installed in Windows OS.
Click to expand...
Click to collapse
Yes i am aware of that. As mentioned i installed the driver, my phone is recognized as an adb device. I have seen some solutions suggesting installing the driver manually when the fastboot device is not recognized correctly but the device is not recognized at all. I also tried installing the drivers as legacy hardware (Android ADB interface, Android Bootloader Interface etc.) via device manager, which results in an error ( error code 10, device can not be started)
No more clues by me.
@holgers0n
I tried lsusb on my Xiaomi (I don't have lg) and it worked in fastboot also.
Since it doesn't show anything if you do fastboot devices, you could try to do the standard things:
1) Change usb port on your computer
2) Try another cable
3) If it's a usb type c, plug it into your smartphone, try if it works and if it doesn't, try around that cable and retry.
I am not 100 % sure but since you said
Ubuntu also does not recognize the device at all, lsusb does not output the device anywhere. It also does get recognized as an adb device when booted up normally.
Click to expand...
Click to collapse
maybe you need to install non-free firmware as well.
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Narrry84 said:
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Click to expand...
Click to collapse
I'm also having the same issue with my Poco F1, it is recognized just fine as an ADB device, but not in fast boot mode. My laptop has both USB 2.0/3.1 ports hence I tried both but the result was just the same not recognised in fastboot mode
holgers0n said:
I also tried installing the drivers as legacy hardware (Android ADB interface, Android Bootloader Interface etc.) via device managerr, which results in an error ( error code 10, device can not be started)
Click to expand...
Click to collapse
yea I also manually installed USB drivers for my Poco F1 but in my case, I had no error
The same thing is happening to me on my LG g5, did you find a solution?
akashrathi7978 said:
I'm also having the same issue with my Poco F1, it is recognized just fine as an ADB device, but not in fast boot mode. My laptop has both USB 2.0/3.1 ports hence I tried both but the result was just the same not recognised in fastboot mode
yea I also manually installed USB drivers for my Poco F1 but in my case, I had no error
Click to expand...
Click to collapse
try linux, same thing has happened to me.
sanfi9 said:
The same thing is happening to me on my LG g5, did you find a solution?
Click to expand...
Click to collapse
try it on linux, install adb on linux and run "fastboot devices" I used to have the same problem.
akashrathi7978 said:
I'm also having the same issue with my Poco F1, it is recognized just fine as an ADB device, but not in fast boot mode. My laptop has both USB 2.0/3.1 ports hence I tried both but the result was just the same not recognised in fastboot mode
yea I also manually installed USB drivers for my Poco F1 but in my case, I had no error
Click to expand...
Click to collapse
Have you tried linux?
hellofriendlymanveriosns said:
Have you tried linux?
Click to expand...
Click to collapse
No, but i got it fixed with this AMD FASTBOOT FIX guide as i was using AMD Ryzen 5 5500U.
My laptop have both USB 2.0/3.1 ports hence it worked for me on USB 2.0 port (otherwise buy a USB 2.0 hub) after running that ".bat" file as "admin" it recognised my phone.
Keep in mind i uninstalled all 3rd party "adb tools" then rebooted my laptop and used Google's official Adb tool (approx 12mb) then ran "cmd" on the same path (keep the adb tool in :c drive)
akashrathi7978 said:
No, but i got it fixed with this AMD FASTBOOT FIX guide as i was using AMD Ryzen 5 5500U.
My laptop have both USB 2.0/3.1 ports hence it worked for me on USB 2.0 port (otherwise buy a USB 2.0 hub) after running that ".bat" file as "admin" it recognised my phone.
Keep in mind i uninstalled all 3rd party "adb tools" then rebooted my laptop and used Google's official Adb tool (approx 12mb) then ran "cmd" on the same path (keep the adb tool in :c drive)
Click to expand...
Click to collapse
STEPS I did to solve this issue on my Laptop with AMD CPU
🗃️POCO F1 Ultimate Collection & Guides📚
Welcome to POCO F1 Ultimate Collection! 🗃️ (beryllium) OFFICIAL STOCK MIUI ROM ©️ You can check my Guides for installation. Recovery ROM V12.0.3.0.QEJMIXM Fastboot ROM V12.0.3.0.QEJMIXM POCO F1 Global Stable ROM Library / POCO F1 MIUI...
forum.xda-developers.com
holgers0n said:
Hey everyone,
im trying to unlock the bootloader of my LG G5, but am unable to do so as the phone is not detected at all when in fastboot mode.
While it is recognized just fine as an adb device, after rebooting into fastboot mode via adb reboot bootloader it is not recognized as an USB Device in Windows (The device manager does not show any device with wrong drivers and does not react to replugging the device). I also tried it on a different machine with the same results.
Ubuntu also does not recognize the device at all, lsusb does not output the device anywhere. It also does get recognized as an adb device when booted up normally.
I installed the necessary (I tried LG and Google) drivers and tried different USB ports (2.0 and 3.0) and cables. The phone just is not noticed as an usb device at all when in fastboot mode.
Could this be due to a broken usb port? Which seems odd because the phone is recognized when not in fastboot mode.
What else could cause this weird behaviour?
Thank You!
Click to expand...
Click to collapse
Hello I have exactly the same problem. I know all the right drivers are installed, because I already flashed it from CN Rom to EEA ROM a few weeks ago. Usb debugging is activated, bootloader unlocked, etc . Nothing works.
Have you resolved the problem since?
Had the same problem after running:
adb reboot bootloader
Tried to run a fastboot command e.g. `fastboot getvar unlocked`, it gave the message `< waiting for any device >`
Solution
Assuming you have the bootloader driver installed, but its not connecting.
After running " adb reboot bootloader " with the device plugged in and in the bootloader follow these steps.
Open Device Manager => Win + R => devmgmt.msc .
Find the device called Android that has a yellow warning sign on it.
{
"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"
}
Open the properties and hit update driver.
Select "Browser my computer for drivers"
Select "Let me pick from a list..."
Select "Android Device"
(If this option doesn't show up, then you don't have the drivers installed)
Select Android Bootloader Interface
(If this option doesn't show up, then you don't have the drivers installed)
Click next and the the bootloader driver should be working.
This solution does need to be repeated when ever the device goes into bootloader mode i.e. when you want to run fastboot commands.
Mmm, just stumbled here to say that I had this problem since loong ago I unlocked the bootloader of my Z2121, and didn't know why. The reason is that I was using the Minimal ADB and Fastboot tool, because after reading the threads Bootloader driver issues on Windows 10? and [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows subsequently, and of course using fawazahmed0's Latest ADB Installer, my problem was solved.
The BAT installer in the thread downloads the actual BAT installer file whose download path you can find inspecting it, and that other actual installer file for now sets the installation folder name as "platform-tools", and also adds its path into your system's user Path variable to allow running ADB and Fastboot commands from whatever folder location. For this reason you must also change the Path variable along with the folder's name if you wish to do so, or edit and modify the actual installation BAT file to change the folder name (there are a few entries).
Hope this is of help.

Categories

Resources