I'm trying to apply an update to my watch usind adb sideload because the watches OS is currently screwed and bricked
but when i issue adb sidelad update.zip i get the following back; "device not connected"
When i plug the watch into the PC it makes the sound of a connection, but adb doesnt recognize it
Related
Background:
Phone OS:
Evo 4G, unrooted, latest OTA update.
Computer OS:
Fedora 13
Just noticed that issuing an 'adb reboot recovery' seems to load the correct screen on the phone - the red triangle/exclamation point.
'adb devices' shows the HTC* offline.
adb kill-server / adb start-server shows the same thing.
Going into recovery mode 'manually' (aka Vol Up / Power at boot, then loading to recovery) adb devices still shows nothing.
Will try from a Windows PC on Monday just to verify it's not a Linux issue, but curious if anyone else has run into this? Hoping this isn't something else the OTA screwed - already pissed that my stock Android Launcher was removed (running LauncherPro now, so eh - thanks HTC?)
this is something the update *fixed*
btw wrong section.
Sorry for that. So the update 'fixed' this? No way around it, I suppose?
That happens to me occasionally. Usually I remedy it by some combination of switching between disk drive mode and back to charge only, or rebooting the phone, and sometimes switching usb ports.
sorry thats all I can offer
It seems many of us are affected by this "adb devices offline" trouble :
http://www.google.com/cse?q=adb+off...ub-2900107662879704:fs7umqefhnf&ie=ISO-8859-1
I had to plug the usb cable again to put the device online,
but do you know a way to reset the usb bus of a linux box ?
http://forum.xda-developers.com/showthread.php?t=735994
http://stackoverflow.com/questions/7322843/reboot-offline-android-device-remotely/7685184#7685184
http://android.stackexchange.com/questions/12491
--
http://rzr.online.fr/q/android
Hello all.
This is my first post and my first experience with android devices so please go gentle.
I recently purchased for £20 a kindle fire 2nd gen otter.
The reason it was so cheap was that it is stuck in a bootloop.
The friend I bought it from intended to bring it back to life and install CM to the device but never got round to it. So I took it on as my little project.
I have been scrolling through pages and pages of google and this site for research but have hit a brick wall.
I purchased a factory or fastboot cable knowing I may well need it. I also have the original cable.
When trying to boot the device I get the usual kindle and fire logo orange as of it's booting then every 10 seconds or so the screen will go black and back to the kindle fire bootloop.
I have tried to use the normal cable to link to my desktop on windows 7. When doing this the device will not show up in device manager at all.
When I plug it via a fastboot cable it boots into fastboot with a green flashing light on screen and is recognised as an otter prod 04 on device manager.
I have installed the latest sdk. Also fastboot.
I have changed the windows environment variables under path on the PC and can successfully run fastboot in a command window. I can also issue adb commands through also a dos command window so I know both are working correctly on my PC.
I have typed in fastboot devices
I have also typed in adb devices.
When I issue either or these commands my device will not be found through the command window. It just returns a blank.
I know this is due to drivers not working correctly so have opened device manager. Update driver , have tried the android sdk path for drivers have also tried my adb drivers. I have also downloaded the latest Google USB driver and none will install. I have a programme running that allows any unsigned driver to be installed on win 7 so I know it's not that.
All I have returned is cannot install drivers for otter prod. 04
The only thing it will accept is choosing from a list of devices, Then android. And installs as adb device or adb composite device, this is obviously useless as I can't boot device into normal mode to be able to use it as adb or issue commands to it.
I have tried everything. I know this kindle is save able I just don't know how. My end result is make it bootable, root device and install CM
I have trawled through loads of pages of info and tried tried and tried for answers but nothing works. Can anybody shed some light on the issue for me.
Many thanks in advance
Just thought id add, I have also tried all timed variations of holding down the power button
I have also let device run flat and recharge. Have also tried a different PC and USB port.
Hello Vincent,
ADB stands for Android Device Bridge (Just wanted to point that out since you are new to Android).
The ADB Composite Device driver lets your computer and your Kindle Fire device communicate with each other. This includes ADB as well as fastboot.
Install the ADB Composite Device driver in Device Manager and then go to the command line window and type fastboot -i 0x1949 devices and it should now show up in fastboot.
Now flash the stock bootloader, recovery, and system img files to your device. After that, you should see it boot successfully.
Hope this helped, and don't be afraid to ask me more questions about your device!
phiftyopz
Sent from my iPhone using Tapatalk
Has anyone gotten their computer find their G4 through cmd (adb devices). I cant get the adb message on my phone to allow access to my computer. I turned on and off usb debugging several times but i still don't see the message on my phone to allow access. I let me computer download the drivers when plugging up my G4 as well as allowing the install of PC drivers.
yes, working great for me. Do u have updated and right drivers? u find tread here with right drivers..
Sent from my unlocked and rooted LG-H815
I was having the same problem..
You need to install the LG Drivers and then your phone will connect via adb..you will be asked on your phone to allow the port connection after installing the proper LG drivers. Verify and you will be good to go..
I used these ones below in the attatchment or you can grab them from.....
http://www.theandroidsoul.com/download-lg-g4-driver-for-windows-and-mac-mtp-adb-download-mode-77723/
I think I found the issue. I had Note 3, 4, Nexus 6, S6 edge, and G4 all still on my computer in the device manager. I uninstalled all of them plus I uninstalled the adb driver in device manager. Plugged my G4 back in and ran the PC driver update via G4 and it worked. I can now see my G4. Don't know if I had to do all that to get it working but hey it worked for me.
I was having issues with this myself and didn't find a solution. I found out that I was having better luck switching it to Camera PTP from the notification dropdown. Sometimes I have to toggle to MTP back to PTP, The dev notifcation should appear when it is actually connected.
1. PTP
(1a. switch to MTP back to PTP if it doesn't work)
2. 'adb kill-server'
3. 'adb devices'
-If you see your device, you can try to 'adb connect **IP**' but it will most likely say it was unable to connect
4. give it your adb commands you want
It's the only way I've been able to get adb, hope this helps!
I was having this issue also. After install win10 then adb connection to my LG G4 (h818) was not detected. Back to android.com, it said that if general USB driver doesn't work then we must find OEM driver to the producer web. LG ADB Driver was about 17MB. After installed the driver then it was immediately detected. Thank God, finally.
I have silly problem. I bought used G4 LG from someone found in online forum. Checked all series on phone (sticker), on software "about phone" all showing LG H815 software version H81510H, but by adb ( linux machine ) showed H812xxxxxx .... set on developer option debugging the command "adb reboot bootloader" just send device into android boot ( device boot ). I wish to unlock the bootloader and put CM. Hard button option > pushing vol up + power button simultaneously did nothing, vol up + power button then > connect to PC via usb, did nothing ( just send phone to device boot ) ..... I have no windows machine
Pushed the fbmode file to it and got it into fastboot, but the device doesn't show up in device manager even as unknown or other. In USB View it shows up as Android ADB Device and it did recognize that a kindle was connected in Virtual box but was unable to connect it to my linux VM.
Edit: After hours of looking for a solution it ended up being solved from this post, my KFU being in my download directory and not in the root of C.
Hello my friends can someone help me with my problem? I have a LG G pad 10.1 v700 with broken/missing touch screen and LCD and I want it to connect to my monitor with vysor and/or [email protected] The problem is that I need to accept dialog windows when appears on my tablet when connecting to vysor, but i cant for obvious reason. I have installed ADB universal drivers, LG drivers, Android Studio and am trying with adb commands like "adb devices" to make some connection with my tablet but it says that my devices is unauthorized and don't accept adb commands at all. I read over the INTERNET that i need to boot in TWRP mode and than I can use adb commands there without authorization. I have previously installed TWRP recovery and also debugging mode is enabled, but when i am supposedly in TWRP mode (I don't hear LG boot sound sometimes after Power + Vol down button combination) my tablet doesn't recognize at all from Windows 10 and "adb devices" command show "error: no device". Can you help me?
My tablet is with android Kit Kat, rooted, Debugging mode is enabled, TWRP is installed
In Windows Device Manager I see in Android Devices - LG ADB interface, also in Portable Devices - V700
sinan.ismailov said:
Hello my friends can someone help me with my problem? I have a LG G pad 10.1 v700 with broken/missing touch screen and LCD and I want it to connect to my monitor with vysor and/or [email protected] The problem is that I need to accept dialog windows when appears on my tablet when connecting to vysor, but i cant for obvious reason. I have installed ADB universal drivers, LG drivers, Android Studio and am trying with adb commands like "adb devices" to make some connection with my tablet but it says that my devices is unauthorized and don't accept adb commands at all. I read over the INTERNET that i need to boot in TWRP mode and than I can use adb commands there without authorization. I have previously installed TWRP recovery and also debugging mode is enabled, but when i am supposedly in TWRP mode (I don't hear LG boot sound sometimes after Power + Vol down button combination) my tablet doesn't recognize at all from Windows 10 and "adb devices" command show "error: no device". Can you help me?
My tablet is with android Kit Kat, rooted, Debugging mode is enabled, TWRP is installed
In Windows Device Manager I see in Android Devices - LG ADB interface, also in Portable Devices - V700
Click to expand...
Click to collapse
Although I have personally not done so specifically for this purpose, you could try connecting a USB mouse via USB-OTG adapter and use the mouse pointer so select the check box and hit the correct button without using touchscreen... do provide feedback if you have success...