Hi all,
I decided to install Asteroid OS on my LG G Watch, but I can't get ADB to recognize it. When I type "adb devices", It returns a string of question marks for the serial number and states "no permissions" beside it. What should I do to circumvent this? My computer is a Lenovo ThinkPad T420 running Zorin Linux. It's Ubuntu based, so Ubuntu commands usually work.
Okteta said:
Hi all,
I decided to install Asteroid OS on my LG G Watch, but I can't get ADB to recognize it. When I type "adb devices", It returns a string of question marks for the serial number and states "no permissions" beside it. What should I do to circumvent this? My computer is a Lenovo ThinkPad T420 running Zorin Linux. It's Ubuntu based, so Ubuntu commands usually work.
Click to expand...
Click to collapse
Have you tried to boot in fastboot first?
Reboot watch and at the lg logo swipe top left diagonal to bottom right.
Cheers
Sent from my Google Pixel using XDA Labs
Is the ADB turned on in the Developer Settings? Have you trusted the computer before that? Have you tried another usb port and drivers?
Thanks
Sgace said:
Have you tried to boot in fastboot first?
Reboot watch and at the lg logo swipe top left diagonal to bottom right.
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Thank you, I will try that!
Related
Hi anyone willing to help. I have had a friend's TF201 for about a month and have come to the point where I can't get any further. We believe heis device has been bricked during the OTA JB update. nvFlash was never added to device.
I can get it into fastboot, however the device does not show up in device manager or shows in ADB. I have confirmed ADB working by using another device that shows up. I know that it is currently on an ICS bootloader, since the NVIDIA logo is in the center bottom. We have tried a different cable and same results.
MOST IMPORTANTLY: which I have not been able to find any literature on is that when it is booted into fastboot only 2 icons appear: 'Wipe Data" and "Fast Boot" USB Icon. There is no Android icon...THIS confuses and scares me.
Is there any hope for this device? I have done so much research and time on this, but can not come up with anything else. Anyone??
Tried connecting in ADB in Win, Mac and Ubuntu. Not showing up? Totally stumped now.r
Bump.
ZeroLozen said:
Bump.
Click to expand...
Click to collapse
You do not have access to adb in fastboot. Only in a custom recovery or in the OS.
You do have access to fastboot commands tho if you have the drivers installed.
Having bricked a tf300t with the 4.2 Ota, I feel ya. Make sure you've got the correct drivers. Look at connected devices on your PC, it should say fast boot device, if it does, then your drivers are fine, going into fast boot, fastboot devices in cmd / however you have your fast boot set up. Look for your devices serial number.. It should show serial , if your drivers are correct..
Sent from my ASUS Transformer Pad TF300T using xda premium
I have tried all necessary things for drivers including the naked driver set for Win. Device wont show up in Linux or Mac environment either. it appears that the fastboot is ICS but it received the OTA JB update. Is there a way to recover from this? The other thing that concerned me is that in fastboot there is no Android Logo (just wipe data, and USB). Is this device recoverable from this state?
You have the upgraded bootloader. They removed a few things but it goes instantly to download mode..... when plugged in to pc. What does it say under control panel / hardware and printers. . When you plug it in. Does it make the tell tale sound?
Sent from my SPH-D710 using Tapatalk 2
Actually I think the incorrect fastboot had been loaded before I got it. To my understanding the OTA JB update was applied and then fastboot was added (but if the nVidia logo is in the center, that is the ICS fastboot correct?) So is my problem here that the incorrect fastboot had been flashed?
Howdy,
I am wondering what error in flashing process can make a device (I assume this is general behavior) not load the android GUI and leave the user at a prompt. Specifics follow.
I understand what buttons to press in order to flash things and have custom roms on my phones/tablets.
I have ug007 android stick, rk3066 with 2 usb ports.
THis time i tried putting finless ug802 ver1.8 with 2dark4u kernel on my ug007 stick. I'm told all the ug series sticks are the same.
I got the stick in flash mode and flashing seemed successful. When I rebooted the device, i saw the linux penguins and the startup countdown which stopped on mounting usb devices in the hub. and then it shows a prompt. No boot screen no android, just sit there and type it commands.
What went wrong please? What can I do now? I don't understand how to start the android from linux cli... but the fact that we get the prompt, did install go awry? Can I type it commands and get it in flash or adb mode?
Thanks for your insights,
Sent from my Nexus 4 using xda app-developers app
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
TjPhysicist said:
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
Click to expand...
Click to collapse
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
osikiri said:
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
Click to expand...
Click to collapse
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
TjPhysicist said:
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
Click to expand...
Click to collapse
Ok, does anyone know how to get my computer to recognise my watch in recovery mode? It's not about 'driver' the computer plain doesn't recognise that anything is plugged in at all.
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Wikiwix said:
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Click to expand...
Click to collapse
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
mrkrabs said:
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
The problem, as @osikiri stated, is that the device does not get recognized at all (no unknown devices in devicemanager and the sound that comes on plugging in a device does not come as well). Furthermore, afaik Linux does not even need any drivers
Had the same issue today... and the only way out way battery death and recharge
JaceAlvejetti said:
Had the same issue today... and the only way out way battery death and recharge
Click to expand...
Click to collapse
If this really helps (seems weird): I guess the exact setting could be necassary:
You simply ran out of battery while the watch was running(not recovery or fastboot) and then plugged it in and went directly (or not?) to the recovery?
Thanks in advance, would be really great to fix this!
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
MSigler said:
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
Click to expand...
Click to collapse
I'm doing the same thing and having the same issues!
Yeah, same issue for me as described.
Windows (Win7 x64 for me) doesn't even realise that the device is connected when it is in recovery mode. Although it will connected properly when booted normally.
+1 Any ideas?
Same issue for me. I've tried removing and replacing it on the cradle, killing and restarting the adb server, entering recovery by the touchscreen or by the adb/fastboot commands, clearing debugging keys, etc... Anybody have any other ideas?
---------- Post added at 07:25 PM ---------- Previous post was at 06:46 PM ----------
Ok, so it appears that the recovery img on 4.4w2 broke adb support or something. There are a few threads that suggest you can root and flash it or just wait for the OTA. We'll see whether I get the OTA before I have time to try this out.
Lollipop OTA Update: Download and How-To (Root Required)
I made a script that roots and updates your watch to 5.0.1 in a click.
[UTILITY][RESTORE][UNLOCK][ROOT] LG G Watch Tool
My way of doing it
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
fi thought it was finally the solution, but fastboot oem unlock bricked my sony smartwatch3. I see tomorrow if with my windows pc i can fix with sony companion, otherwise i'll have to use the warranty
willisc said:
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
Click to expand...
Click to collapse
Hi,
I got my Nexus 9 around launch date and used Wugs toolkit to unlock bootloader, root and install teamwin recovery.
I kept gettting OTA updates for 5.0.2 but they wouldn't install. After months of ignoring I thought I'd update.
It wouldn't update so I tried to use Wugs toolkit to 'Flash stock + unroot to latest version'.
This failed saying something about no fastboot device, although the device went to the white screen and seemed to be displaying hboot/fastboot as options...
I got frustrated and used TWRP to wipe everything, including the OS!
I'm used to Samsung so expected an Odin type program to flash over my mess... I can't seem to do anything now.
HELP! (Please!)
A reason I don't like tool kits. If they don't work as expected you have no idea what to do next. Follow the long method of this, http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 9 using XDA Free mobile app
Appreciate the reply but I can't enable anything within the device as there is no OS installed...
I have used vol down and power to select fastboot.... Is this "Boot your device into the bootloader" in your guide?
All I get is waiting for device in the cmd window
thanks
jotan said:
Appreciate the reply but I can't enable anything within the device as there is no OS installed...
I have used vol down and power to select fastboot.... Is this "Boot your device into the bootloader" in your guide?
All I get is waiting for device in the cmd window
thanks
Click to expand...
Click to collapse
Vol down and power does bring you into the bootloader. Do you have usb drivers setup? Go into device manager on your pc with the device connected. Do you have an icon with a yellow exclamation mark? If so right click on it and go to where you can choose a driver from a list on your computer. Choose Android adb composite interface.
Sent from my Nexus 9 using XDA Free mobile app
Sorry about the late reply, been on my honeymoon! For some reason it just wouldn't work on my PC, so I used my laptop and all was well.
Thanks.
Thread closed!
I attempted to install the custom OS, Asteroid, to my Zenwatch 2 (Sparrow) I followed the directions and now the watch will not boot, it is stuck at the Asus screen in a loop. I downloaded the recovery image, but I can not flash it do to Windows not recognizing the watch is connected. ADB gives me the error Device '(null)' not found. I have checked the device manager and there is nothing showing as an error (yellow !). Is there anyway I can recover from this?
jnelsoninjax said:
I attempted to install the custom OS, Asteroid, to my Zenwatch 2 (Sparrow) I followed the directions and now the watch will not boot, it is stuck at the Asus screen in a loop. I downloaded the recovery image, but I can not flash it do to Windows not recognizing the watch is connected. ADB gives me the error Device '(null)' not found. I have checked the device manager and there is nothing showing as an error (yellow !). Is there anyway I can recover from this?
Click to expand...
Click to collapse
go into fastboot mode and reflash your system.
dont work with fastboot / adb / root when you have no idea what youre doing!
matze19999 said:
go into fastboot mode and reflash your system.
dont work with fastboot / adb / root when you have no idea what youre doing!
Click to expand...
Click to collapse
The problem is that the watch is not being detected by Windows, therefore I am unable to reflash it, I clearly stated this in my original post.
jnelsoninjax said:
The problem is that the watch is not being detected by Windows, therefore I am unable to reflash it, I clearly stated this in my original post.
Click to expand...
Click to collapse
You said windows can't detect the watch in adb mode? What about the fastboot mode?
matze19999 said:
You said windows can't detect the watch in adb mode? What about the fastboot mode?
Click to expand...
Click to collapse
No, issuing the command: Fastboot devices shows nothing connected at all(the same goes for adb). It also does not show up in the windows device manager.
jnelsoninjax said:
No, issuing the command: Fastboot devices shows nothing connected at all(the same goes for adb). It also does not show up in the windows device manager.
Click to expand...
Click to collapse
Did you enter the fastboot mode?
matze19999 said:
Did you enter the fastboot mode?
Click to expand...
Click to collapse
The watch is showing CSC Fastboot Mode! So I would assume that it is in Fastboot mode
Were you able to get this fixed?
No, I have but been able to resolve this issue. It is not being recognized by Windows, therefore I can't flash the original os back to it.
Did you have TWRP installed prior to the failed flash?
CVertigo1 said:
Did you have TWRP installed prior to the failed flash?
Click to expand...
Click to collapse
No
I may have a way to get it working. I've had issues where Windows would not recognize a device, until I installed a cocktail of random drivers that eventually worked. What version of Windows are you running?
CVertigo1 said:
I may have a way to get it working. I've had issues where Windows would not recognize a device, until I installed a cocktail of random drivers that eventually worked. What version of Windows are you running?
Click to expand...
Click to collapse
I am running Windows 10 X64 build 1803
If you have the space, follow this: https://docs.microsoft.com/en-us/windows/wsl/install-win10
It allows you to run non-graphical Ubuntu on top of Windows. I've found sometimes my Windows 10 PC won't recognize things with adb or fastboot, but it works great in Ubuntu Bash. If you're familiar with Ubuntu at all, then it'll be a breeze to figure it out. If not, it's a pretty straight forward learning curve. It's also child's play to get adb and fastboot working right in Ubuntu, whereas it can be finicky in Windows.
Another alternative is to make a Linux Live CD using a USB drive, but that is a much more temporary solution.
---------- Post added at 10:17 AM ---------- Previous post was at 10:16 AM ----------
If none of those sound appealing, then I'd suggest deleting all drivers having to do with adb or fastboot, and start fresh by installing everything with this https://forum.xda-developers.com/showthread.php?t=2588979
CVertigo1 said:
If you have the space, follow this: https://docs.microsoft.com/en-us/windows/wsl/install-win10
It allows you to run non-graphical Ubuntu on top of Windows. I've found sometimes my Windows 10 PC won't recognize things with adb or fastboot, but it works great in Ubuntu Bash. If you're familiar with Ubuntu at all, then it'll be a breeze to figure it out. If not, it's a pretty straight forward learning curve. It's also child's play to get adb and fastboot working right in Ubuntu, whereas it can be finicky in Windows.
Another alternative is to make a Linux Live CD using a USB drive, but that is a much more temporary solution.
---------- Post added at 10:17 AM ---------- Previous post was at 10:16 AM ----------
If none of those sound appealing, then I'd suggest deleting all drivers having to do with adb or fastboot, and start fresh by installing everything with this https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
OK, I will mess around and see what happens! I will have to do it tomorrow, but I will play around and see what happens!
Let me know how it goes and I'll walk you through it some more.
Any luck?
Sorry for the long time to reply. I installed ubuntu in window and installed the appropriate packages, however both ADB and Fastboot show nothing connected, even though the device is in CSC Recovery mode. Is there anything else I can try?
I actually tried playing with a few things on one of my computers the other day to try tracking this down. I was running into an issue where adb worked normally when the watch booted, but it would not work in recovery, and fastboot did not work either. Here is how I fixed it. Open up device manager in Windows and delete any driver pertaining to Android phones or adb. In my example, an Asus driver was causing the problem. I deleted that and reinstalled the generic Google drivers using the 15 second adb/fastboot installer that I posted in this thread. After restarting the computer, adb works perfect in Android and recovery, and fastboot works perfect as well.
TL/DR Delete all Android adb drivers in Windows, then run the 15 second adb installer that I posted in this thread, restart, and get your watch back to normal.
Assuming your bootloader is unlocked, you can flash everything I have posted here to get it running. https://forum.xda-developers.com/zenwatch-2/development/sparrow7-1-1debloat-rom-t3800067 If the bootloader is not unlocked, fastboot oem unlock will do it.
CVertigo1 said:
I actually tried playing with a few things on one of my computers the other day to try tracking this down. I was running into an issue where adb worked normally when the watch booted, but it would not work in recovery, and fastboot did not work either. Here is how I fixed it. Open up device manager in Windows and delete any driver pertaining to Android phones or adb. In my example, an Asus driver was causing the problem. I deleted that and reinstalled the generic Google drivers using the 15 second adb/fastboot installer that I posted in this thread. After restarting the computer, adb works perfect in Android and recovery, and fastboot works perfect as well.
TL/DR Delete all Android adb drivers in Windows, then run the 15 second adb installer that I posted in this thread, restart, and get your watch back to normal.
Assuming your bootloader is unlocked, you can flash everything I have posted here to get it running. https://forum.xda-developers.com/zenwatch-2/development/sparrow7-1-1debloat-rom-t3800067 If the bootloader is not unlocked, fastboot oem unlock will do it.
Click to expand...
Click to collapse
OK, I got windows to see the watch via fastboot and I downloaded the image that you posted (bloat free) now the watch started to boot, but so far it is just showing spinning dots, and has been for ~5 minutes or so, is this normal?