MY ADB has stopped Working
It happened after Installing the CWM And TWCR
Well What happened it was saying ADB was outdated while installing but it installed CWM and TWCR
Now if i enable ADB in the phone the windows doesnt read that there is a mobile nor anything detected not even charging
When i disable ADB I can see my phone charging and i can transfer files
I don't know what to do and I am very worried ...
Hope If any1 could help...
Tried installing ADB drivers and the Android SDK .. No luck
I think the problem is in the phone as it doesnt allow me to connect to the PC with ADB on
I read this http://forum.xda-developers.com/showthread.php?t=1917741
and found that ro.debuggable=0 in the Deafult.prob While it is enabled ...
And there is a question too how can i backup it so if i eddit it and get a bootloop I want to be able to restore using CWM or TWCR
John98Zakaria said:
MY ADB has stopped Working
It happened after Installing the CWM And TWCR
Well What happened it was saying ADB was outdated while installing but it installed CWM and TWCR
Now if i enable ADB in the phone the windows doesnt read that there is a mobile nor anything detected not even charging
When i disable ADB I can see my phone charging and i can transfer files
I don't know what to do and I am very worried ...
Hope If any1 could help...
Tried installing ADB drivers and the Android SDK .. No luck
I think the problem is in the phone as it doesnt allow me to connect to the PC with ADB on
I read this http://forum.xda-developers.com/showthread.php?t=1917741
and found that ro.debuggable=0 in the Deafult.prob While it is enabled ...
And there is a question too how can i backup it so if i eddit it and get a bootloop I want to be able to restore using CWM or TWCR
Click to expand...
Click to collapse
Can you use adb over other computers?
Also, try ADB over network. Goto Settings > Developer Options and turn "ADB over network" on. If prompted with a warning, press OK. Then you will see an ip address with a port number under ADB over Network setting. Now open cmd (or Terminal in Linux) and cd to the directory where the ADB files are present. Then type
Code:
adb connect <ipaddress>
Of course, replace <ipaddress> with the ip that you see in the Developer Options under ADB over network. It should be something like "192.168.1.2:5555", enter the whole thing. Then see if you are successfully connected by typing
Code:
adb devices
.
If you are using windows go to control panel and look for "hardware" or more specifically "drivers". It is somewhere there, just look around and you will find it. Then enable adb and connect phone. Then Select your device name from the list and right-click and select appt. drivers.
ayushag96 said:
Can you use adb over other computers?
Also, try ADB over network. Goto Settings > Developer Options and turn "ADB over network" on. If prompted with a warning, press OK. Then you will see an ip address with a port number under ADB over Network setting. Now open cmd (or Terminal in Linux) and cd to the directory where the ADB files are present. Then type
Code:
adb connect <ipaddress>
Of course, replace <ipaddress> with the ip that you see in the Developer Options under ADB over network. It should be something like "192.168.1.2:5555", enter the whole thing. Then see if you are successfully connected by typing
Code:
adb devices
.
If you are using windows go to control panel and look for "hardware" or more specifically "drivers". It is somewhere there, just look around and you will find it. Then enable adb and connect phone. Then Select your device name from the list and right-click and select appt. drivers.
Click to expand...
Click to collapse
Thanks for the reply I can't use ADB anywere ..
The phone doesn't even appear in the PC with ADB debuging enabled not even a connected sound or anything ..
I tried Wifi Kontect on the playstore as I didnt find "ADB over Network" But ADB wont connect....
Any Other solutions ... I dont mind if i have ADB over wifi the important thing is to have any ADB connection
www .mediafire .com/convkey/fb15/db3ykaaldgkqsd66g.jpg?size_id=5
www .mediafire .com/convkey/93e0/49f47ps6s9nbeyj6g.jpg
Remove spaces so you can see the images I cant post links yet
Fixed
I have fixed my probem thanks to @sijav !
Installing
http://forum.xda-developers.com/showthread.php?t=1687590
Fixed everything ! even after un-installing the app
Anyone with the new watch, the "LG Watch Sport", figured out how to get a USB or USB-like connection to a Windows computer? WiFi is greyed out and Bluetooth isn't an option on my Win box
BGot ADB up via Wi-Fi:
1) Connect watch and computer to same Wi-Fi network,
2) In Developer options (available after tapping 7 times on Settings > About > Build number)
Turn "ADB debugging" = on
3) Turn "Debug over Wi-Fi" = on
4) To get the watch's ip address go Settings > Connectivity > Wi-Fi
5) Tap on active Wi-Fi connection name
6) start command window
7) Type: adb connect [ip address of watch]
Easy, peezy!
BTW, it's an unbelievable battery killer. 30 min. = maybe 8 hours normal use.
Anybody know where the APN info's stored? Like to pull it, change it & push it back, if ATT didn't lock it down.
roebling said:
BGot ADB up via Wi-Fi:
1) Connect watch and computer to same Wi-Fi network,
2) In Developer options (available after tapping 7 times on Settings > About > Build number)
Turn "ADB debugging" = on
3) Turn "Debug over Wi-Fi" = on
4) To get the watch's ip address go Settings > Connectivity > Wi-Fi
5) Tap on active Wi-Fi connection name
6) start command window
7) Type: adb connect [ip address of watch]
Easy, peezy!
BTW, it's an unbelievable battery killer. 30 min. = maybe 8 hours normal use.
Anybody know where the APN info's stored? Like to pull it, change it & push it back, if ATT didn't lock it down.
Click to expand...
Click to collapse
If you have the watch, can you also check if fastboot can be put into wifi mode?
matejdro said:
If you have the watch, can you also check if fastboot can be put into wifi mode?
Click to expand...
Click to collapse
I've tried "fastboot oem unlock", "fastboot oem get_identifier_token" and "fastboot connect 192.168.1.9"--all fail with "< waiting for any device >"
With watch in bootloader mode, "adb connect 192.168.1.9" also fails, with:
"unable to connect to 192.168.1.9:5555: cannot connect to 192.168.1.9:5555: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (10060)"
Android Police on 2016/03/04 wrote that wifi fastboot mode exists on Moto G's fastboot menu. No menu option for that on this LG Watch Sport.
Yes I meant the thing from that Android Police article. Well that is a bummer, thanks for checking anyway!
---------- Post added at 03:56 PM ---------- Previous post was at 03:22 PM ----------
Just to clarify, there IS a fastboot menu, but it is a bit useless since there is no Wifi option and you can't connect the cable?
There's a way to load system images on these things, I just don't know what it is.
Know a Verizon tech or the AT&T Store repair guy? There's a code for Wi-Fi or a proprietary cord, perhaps attaching under the back. My money's on a funky cord.
no USB debugging for LG Sport?
Wifi debugging tends to be slow imho
In case anyone didn't know, you can use ADB to push custom ringtones to /sdcard/Ringtones. After rebooting, they'll show up in the ringtone picker. You can set a custom alarm, too. That's a pain in the butt though, requires sideloading ES File Explorer because there's no picker for alarm tones.
Sent from my LG V20 using XDA Labs
roebling said:
BGot ADB up via Wi-Fi:
1) Connect watch and computer to same Wi-Fi network,
2) In Developer options (available after tapping 7 times on Settings > About > Build number)
Turn "ADB debugging" = on
3) Turn "Debug over Wi-Fi" = on
4) To get the watch's ip address go Settings > Connectivity > Wi-Fi
5) Tap on active Wi-Fi connection name
6) start command window
7) Type: adb connect [ip address of watch]
Easy, peezy!
BTW, it's an unbelievable battery killer. 30 min. = maybe 8 hours normal use.
Anybody know where the APN info's stored? Like to pull it, change it & push it back, if ATT didn't lock it down.
Click to expand...
Click to collapse
I did that, but when I try to sideload an app it won't go through, and ADB devices brings up that it's unauthorized.
chrisrodsa210 said:
I did that, but when I try to sideload an app it won't go through, and ADB devices brings up that it's unauthorized.
Click to expand...
Click to collapse
When you first connect device to computer does watch display menu for authorization? If not, try "ADB devices". If so, scroll down to "Always allow connections..."
Picked up this watch last week and its exciting that people are already looking to unlock boot loader. Any idea of when it'll get its own dedicated forum on XDA?
NickWhit1992 said:
In case anyone didn't know, you can use ADB to push custom ringtones to /sdcard/Ringtones. After rebooting, they'll show up in the ringtone picker. You can set a custom alarm, too. That's a pain in the butt though, requires sideloading ES File Explorer because there's no picker for alarm tones.
Click to expand...
Click to collapse
I've connected my watch to my PC and when I command:
adb puch -p sdcard/Ringtones <file name>.mp3
cannot stay 'sdcard/Ringtones': No such file or directory
Can you please elaborate on the command to push through adb? Thanks!
Also, ive tried:
and push -p C:\<local drive>\<file name>.mp3 sdcard\Ringtones
Transferring: 100%
failed to copy '<filepath>\<file name>.mp3' to 'sdcard\Ringtones': couldn't create file: Read-only file system
Is there a way to make it not a read only system?
Maxninja said:
I've connected my watch to my PC and when I command:
adb puch -p sdcard/Ringtones <file name>.mp3
cannot stay 'sdcard/Ringtones': No such file or directory
Can you please elaborate on the command to push through adb? Thanks!
Also, ive tried:
and push -p C:\<local drive>\<file name>.mp3 sdcard\Ringtones
Transferring: 100%
failed to copy '<filepath>\<file name>.mp3' to 'sdcard\Ringtones': couldn't create file: Read-only file system
Is there a way to make it not a read only system?
Click to expand...
Click to collapse
Code:
adb push ringtone.mp3 sdcard/Ringtones
I put the ringtones in the ADB folder and used that for each one, and it worked fine for me. I don't know why it's not working for you, perhaps an update changed things. I forgot my watch at home today, or I'd try it again. If I remember when I get home tonight, I'll look into it.
Sent from my LG V20 using XDA Labs
NickWhit1992 said:
I put the ringtones in the ADB folder and used that for each one, and it worked fine for me. I don't know why it's not working for you, perhaps an update changed things. I forgot my watch at home today, or I'd try it again. If I remember when I get home tonight, I'll look into it.
Click to expand...
Click to collapse
I just pushed it through and used ES explorer to set the mp3 file as ringtone. I put in / for the ringtones instead of \ ; so now it works. Thanks!
Using developer options, and ADB debugging maybe, could this guide be used to change the LTE bands on our watches?
https://forum.xda-developers.com/gal...ds-to-t2886059
Bands
So still no news on getting bands unlocked on our devices?
roebling said:
BGot ADB up via Wi-Fi:
1) Connect watch and computer to same Wi-Fi network,
2) In Developer options (available after tapping 7 times on Settings > About > Build number)
Turn "ADB debugging" = on
3) Turn "Debug over Wi-Fi" = on
4) To get the watch's ip address go Settings > Connectivity > Wi-Fi
5) Tap on active Wi-Fi connection name
6) start command window
7) Type: adb connect [ip address of watch]
Easy, peezy!
BTW, it's an unbelievable battery killer. 30 min. = maybe 8 hours normal use.
Anybody know where the APN info's stored? Like to pull it, change it & push it back, if ATT didn't lock it down.
Click to expand...
Click to collapse
Hey, this article explains how to set the APN through adb: android.stackexchange.com/questions/117125/how-do-i-add-an-apn-via-adb
UPDATE: This is a better APN guide: forum.xda-developers.com/showpost.php?p=73558495&postcount=5
It is for the watch Urbane and freedomPOP, but I imagine that there is not a lot of differences between the two watches and it is, essentially, the same procedure. It does require an unlocked bootloader.
roebling said:
I've tried "fastboot oem unlock", "fastboot oem get_identifier_token" and "fastboot connect 192.168.1.9"--all fail with "< waiting for any device >"
With watch in bootloader mode, "adb connect 192.168.1.9" also fails, with:
"unable to connect to 192.168.1.9:5555: cannot connect to 192.168.1.9:5555: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (10060)"
Android Police on 2016/03/04 wrote that wifi fastboot mode exists on Moto G's fastboot menu. No menu option for that on this LG Watch Sport.
Click to expand...
Click to collapse
Have you tried bluetooth debugging?
Hey user "Grumps" managed to put the watch into download mode with a wifi connection. Could this be used to unlock the bootloader, root and modify the APNs?
URL:
forum.xda-developers.com/watch-sport/help/attempting-to-enter-recovery-mode-t3617141
justice89 said:
Hey, this article explains how to set the APN through adb: android.stackexchange.com/questions/117125/how-do-i-add-an-apn-via-adb
UPDATE: This is a better APN guide: forum.xda-developers.com/showpost.php?p=73558495&postcount=5
It is for the watch Urbane and freedomPOP, but I imagine that there is not a lot of differences between the two watches and it is, essentially, the same procedure. It does require an unlocked bootloader.
Click to expand...
Click to collapse
This only works if you have rooted your watch, otherwise you can't do the su command.
Does anyone know if someone is working on rooting this watch?
If, like me, you tried to update to Oreo while you were on Nougat rooted, you should have been greeted with some encryption problems, leading to an almost complete loss of data. Except Joocx posted a guide for how to get the data back, so you could get the data back. Nice, but how do we get a working phone back? Maybe you flashed Nougat again and restored your /data and internal storage backups, hoping it would work. It did work. Except Wi-Fi was broken and fingerprints didn't work.
If you haven't managed yet to get a working phone back, you can have a look here.
Restore Wi-Fi and fingerprints on Nougat or Oreo, without data loss
Reboot in TWRP (no matter which version, as long as you use 3.2.1-0 if you're on Oreo), and from your PC run the following commands.
If you feel like it, you can also run the three rm commands from the TWRP terminal, but it's hard.
Code:
C:\> adb shell
~ # rm /data/misc/wifi/wpa_supplicant.conf
~ # rm -rf /data/system/users/0/fpdata
~ # rm /data/system/users/0/settings_fingerprint.xml
Reboot to system, and voilà.
Update: 3DSammy has pointed out that plugging in your phone to your computer is actually not required. All the file management operations can be done using TWRP's file manager (in the "Advanced" section), the commands can be run directly on the phone using TWRP's terminal and OTG storage can be used for the ROM and Magisk. I had forgot about that file manager since I thought it was only for reading (not for writing/deleting).
Just so others know, TWRP under the "Advanced" menu item has a "File Manager" which allows you to remove each of these files. That's important for those who can't get to a PC with a working adb to mount the shell. I used OTG external storage to access the OTA and Magisk zips for flashing and storage of my nandroid backup.
Personally I would need the File Manger as I have a fully functioning PC fastboot but for some reason can't see my OP5 using adb. Not a big deal but there is a user-friendly built right into TWRP which always has "root" privileges to "/data".
zdimension said:
If, like me, you tried to update to Oreo while you were on Nougat rooted, you should have been greeted with some encryption problems, leading to an almost complete loss of data. Except Joocx posted a guide for how to get the data back, so you could get the data back. Nice, but how do we get a working phone back? Maybe you flashed Nougat again and restored your /data and internal storage backups, hoping it would work. It did work. Except Wi-Fi was broken and fingerprints didn't work.
If you haven't managed yet to get a working phone back, you can have a look here.
Restore Wi-Fi and fingerprints on Nougat or Oreo, without data loss
Reboot in TWRP (no matter which version, as long as you use 3.2.1-0 if you're on Oreo), and from your PC run the following commands.
If you feel like it, you can also run the three rm commands from the TWRP terminal, but it's hard.
Code:
C:\> adb shell
~ # rm /data/misc/wifi/wpa_supplicant.conf
~ # rm -rf /data/system/users/0/fpdata
~ # rm /data/system/users/0/settings_fingerprint.xml
Reboot to system, and voilà.
Update: 3DSammy has pointed out that plugging in your phone to your computer is actually not required. All the file management operations can be done using TWRP's file manager (in the "Advanced" section), the commands can be run directly on the phone using TWRP's terminal and OTG storage can be used for the ROM and Magisk. I had forgot about that file manager since I thought it was only for reading (not for writing/deleting).
Click to expand...
Click to collapse
Hey Z,
I was hoping you can walk me through this process as I'm still unable to fix this Wifi Issue. I've done exactly as you said in the guide but my wifi is still not working. It will turn on and everything but will not connect to a network. It just says "configuring ip address".
Dchoi229 said:
Hey Z,
I was hoping you can walk me through this process as I'm still unable to fix this Wifi Issue. I've done exactly as you said in the guide but my wifi is still not working. It will turn on and everything but will not connect to a network. It just says "configuring ip address".
Click to expand...
Click to collapse
Indeed, it's weird that it's still not working. But if I understood correctly, you are able to turn it on and scan networks, which is a step forward fixing the problem. The message you are getting means that there is a problem while requesting an IP address through DHCP. Try using a static IP on that network. If it works, then there may be a conflict it some other DHCP problem on your router. Otherwise, try on another WiFi network. If neither if those works, then I don't know.
zdimension said:
Indeed, it's weird that it's still not working. But if I understood correctly, you are able to turn it on and scan networks, which is a step forward fixing the problem. The message you are getting means that there is a problem while requesting an IP address through DHCP. Try using a static IP on that network. If it works, then there may be a conflict it some other DHCP problem on your router. Otherwise, try on another WiFi network. If neither if those works, then I don't know.
Click to expand...
Click to collapse
Thanks for the response Z! I just tried it and my wifi isn't stable at all when trying to connect to wifi. It's my workplace wifi that I usually have to sign into to access. It'll connnect and disconnect constantly. Is there anything you'd advise me to do?
Ok so I'm a little confused.
Are we running the command in one full line? eg:
C:\> adb shell ~ # rm /data/misc/wifi/wpa_supplicant.conf
My fingerprint sensor never died so I don't require that fix. I just cannot connect to wifi network. Detects it but once connection attempts in just reverts to 'saved' and tries to reconnect.
Also are you sure this is run once you boot into TWRP and not Fastboot mode?
Running from TWRP via ADB:
C:\>adb shell ~ # rm /data/misc/wifi/wpa_supplicant.con
/sbin/sh: /: Permission denied
From TWRP terminal manager I ran the same command and errored with sh: adb: not found.
I'm rooted and encrypted.
Cheers.
buzzfuzz1 said:
Ok so I'm a little confused.
Are we running the command in one full line? eg:
C:\> adb shell ~ # rm /data/misc/wifi/wpa_supplicant.conf
My fingerprint sensor never died so I don't require that fix. I just cannot connect to wifi network. Detects it but once connection attempts in just reverts to 'saved' and tries to reconnect.
Also are you sure this is run once you boot into TWRP and not Fastboot mode?
Running from TWRP via ADB:
C:\>adb shell ~ # rm /data/misc/wifi/wpa_supplicant.con
/sbin/sh: /: Permission denied
From TWRP terminal manager I ran the same command and errored with sh: adb: not found.
I'm rooted and encrypted.
Cheers.
Click to expand...
Click to collapse
Nah, the command is supposed to be run when the phone is in TWRP.
First, you use adb shell to open a terminal from your PC (ignore this step if you want to use TWRP's integrated terminal directly on the phone).
Then, when you're in the shell, run the rm command.
Well it seems this fix didn't work unfortunately :/ Wifi still cannot connect to any network.
Is the command simply deleting the file and it regenerates upon reboot?
buzzfuzz1 said:
Well it seems this fix didn't work unfortunately :/ Wifi still cannot connect to any network.
Is the command simply deleting the file and it regenerates upon reboot?
Click to expand...
Click to collapse
The file the command deletes is basically the "Wi-Fi" settings file, which contain identification settings for the network card amongst other things. If you keep the Nougat one while you're on Oreo, you can't turn on Wi-Fi, or use anything related to the Wi-Fi antenna; Thus, we delete it. That solves the problem "Wi-Fi doesn't turn on". Here, you've got another problem: "Wi-Fi can't connect". I have no clue of what could be causing this, this issue never happened to me. I'm gonna search a bit and update here if I find anything.
Hello,
I got my phone brand new about 4 months ago. I rooted it and got TWRP installed with no issues. Fastboot and ADB were working fine but now when I try to connect my phone via USB and use ADB I get unauthorized whenever I type adb devices. Typically this happens because your phone is prompting you to allow the computer to have root access but I am not getting that popup window at all.
Things I've tried;
Uninstalled ADB/Updated ADB
Deleted adbkey folder under C:\Users\name\.android
Stopped and Started the adb server again after computer and phone reboot
Deleted ADB_keys folder on android in \data\misc\adb folder on phone itself, followed by a restart
Turning off then back on USB Debugging
Turning off then back on USB Debugging & Developer Options
(Including Revoking USB Debugging Authorizations both times)
Even tried copying the following from PC to phone ~/.android/adbkey.pub inside the /data/misc/adb/adb_keys
Still no luck, I'm not sure why it would just stop working out of nowhere. Nothing has changed since I used it a few months ago.
Also another strange occurrence is that if I turn off USB Debugging / Developer Options then reboot. Once the phone gets to the home screen both USB Debugging and Developer Options are enabled again without me doing it.
Anyone else have a similar issue and figure it out?
vulcanrvn said:
Hello,
I got my phone brand new about 4 months ago. I rooted it and got TWRP installed with no issues. Fastboot and ADB were working fine but now when I try to connect my phone via USB and use ADB I get unauthorized whenever I type adb devices. Typically this happens because your phone is prompting you to allow the computer to have root access but I am not getting that popup window at all.
Things I've tried;
Uninstalled ADB/Updated ADB
Deleted adbkey folder under C:\Users\name\.android
Stopped and Started the adb server again after computer and phone reboot
Deleted ADB_keys folder on android in \data\misc\adb folder on phone itself, followed by a restart
Turning off then back on USB Debugging
Turning off then back on USB Debugging & Developer Options
(Including Revoking USB Debugging Authorizations both times)
Even tried copying the following from PC to phone ~/.android/adbkey.pub inside the /data/misc/adb/adb_keys
Still no luck, I'm not sure why it would just stop working out of nowhere. Nothing has changed since I used it a few months ago.
Also another strange occurrence is that if I turn off USB Debugging / Developer Options then reboot. Once the phone gets to the home screen both USB Debugging and Developer Options are enabled again without me doing it.
Anyone else have a similar issue and figure it out?
Click to expand...
Click to collapse
Go Here and download the Fastboot drivers. follow the directions on the razor dev portal. I had the same issue and this fixed it for me. https://developer.razer.com/razer-p...94.1708481542.1586624574-305520188.1586475530
If your adb-server is not started with root/admin rights, your phone will never prompt you for authorization unless you choose a different USB Mode (MTP, PTP, etc.) than Charge Only. I suspect this is done to prevent certain malicious actions being performed without the user being aware.
If you start your adb-server with root/admin rights (by typing "sudo adb start-server", make sure you've killed your existing daemons before doing so), you can use ADB while in Charge Only mode, provided you've subsequently authorized the PC to do so. However, unlike normal adb server, the fingerprint may occasionally change and you may need to redo the authorization again.