Develop Bugs

[Q] adb shell returning device offline

I have all the JDK and Android SDK components installed on my Windows 7 box. I have enabled USB Debugging and when I try to run adb shell I get the following error:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell
error: device offline
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb devices
List of devices attached
5099ba28 offline
Shows the device attached to my PC.
I have killed and restarted the adb server, rebooted my phone, no luck.
I have never had a problem before with adb. Do you need to use the USB 3.0 cord that was included with the Note 3 or will a regular mico USB work?

stevetrooper said:
I have all the JDK and Android SDK components installed on my Windows 7 box. I have enabled USB Debugging and when I try to run adb shell I get the following error:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell
error: device offline
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb devices
List of devices attached
5099ba28 offline
Shows the device attached to my PC.
I have killed and restarted the adb server, rebooted my phone, no luck.
I have never had a problem before with adb. Do you need to use the USB 3.0 cord that was included with the Note 3 or will a regular mico USB work?
Click to expand...
Click to collapse
regular should work. That is just the data transfer speed.
Have you tried this? http://forum.xda-developers.com/showthread.php?t=2247471

Figured out the problem, I needed to upgrade my adb to the latest version (1.0.31). When I ran the adb shell, a pop-up window appeared on the Note 3 and I confirmed. Now I am able to access.

stevetrooper said:
Figured out the problem, I needed to upgrade my adb to the latest version (1.0.31). When I ran the adb shell, a pop-up window appeared on the Note 3 and I confirmed. Now I am able to access.
Click to expand...
Click to collapse
Yeah, the new adb(d) (6 months back, iirc) added some security where you have to confirm the rsa fingerprint of each machine you connect to. It's a little annoying, because you HAVE to connect adb via USB first, and only then can you use adb via wireless, which is all I ever use anymore.
(edit: adb security added in 4.2.2, which was released in february)

spell check

Has any one got the red underline spell check working on their note 4 at&t varient ?
I have been doing some research and I think I have nerrowed down the issue just need some one who has spell check currently working on their device.
If you have then please do reply, it would be best if you have 6.0.1 update but I think android veraion wont matter at all.
:good:

Managed to fix it via ADB
- turn on developer options
- turn on usb debugging
- on your PC downlolad and install minimal adb and fastboot ( http://forum.xda-developers.com/show....php?t=2317790 )
- connect your device via usb to your PC, wait 2 minutes until adb drivers have been installed
- run the installed adb link in your start menu, a cmd window opens op
- enter: adb shell
- enter: settings put secure spell_checker_enabled 1
- close cmd, disconnect phone, spell checking is enabled

ADB working only via WiFi, with USB after su with command

Hello everyone
Recently (today exactlly) I tried restore/repair IMEI with method shown in this video (https://www.youtube.com/watch?v=y2lHFy7AciE).
IMEI is visible but after restarting D855 adb via USB no longer works. It's no longer visible in Devices Manager and of course I can't connect PC with phone anymore with cable.
ADB via WiFi works very well.
I found a way to make it work with cable after entering commands via WiFi. The commands I'm using to make it work:
Code:
adb connect #my_d855_ipadress
adb shell
su
setprop sys.usb.config diag,adb
The question is, what I have to modify in /system to make it work always without juggling commands with adb over wifi first.
If this question was asked, please let me know (I already used search).

I'm late to this thread, but luckily, as of Android 11 and up, adb works over wi-fi (without USB) on non-rooted Android phones via Developer options Wireless debugging switches.

Adb cannot detect my OnePlus 5T

i want to unlock my OnePlus 5T bootloader but when i type adb devices it doesnt show list of device
here is my setting
oneplus 5t driver installed
windows 10
usb debugging enabled
oem unlock enabled
adb ??i just extract it and place it on Local Disk C and run the cmd file as administrator

enzo2001 said:
i want to unlock my OnePlus 5T bootloader but when i type adb devices it doesnt show list of device
here is my setting
oneplus 5t driver installed
windows 10
usb debugging enabled
oem unlock enabled
adb ??i just extract it and place it on Local Disk C and run the cmd file as administrator
Click to expand...
Click to collapse
Install adb drivers. Having a adb folder doesn't mean anything. You need to install the adb drivers. Delete that and follow the steps from this thread
https://forum.xda-developers.com/showthread.php?t=2588979
All the best.

did your phone prompt up allow adb debugging window when you enter "adb devices"
To unlock bootloader, once you enable "oem unlock " option, you just simply need to restart phone to fastbootmode and enter "fastboot oem unlock" then select yes

update : i already fixed it by installing google usb driver and manually update my Android device driver using google usb driver file thanks tho for the effort to help me

Mine has been giving me a hard time to there was an windows adb update to

u have to accept the RSA key that pop ups on ur phone, if that does not show up it will not enter ADB mode

enzo2001 said:
i want to unlock my OnePlus 5T bootloader but when i type adb devices it doesnt show list of device
here is my setting
oneplus 5t driver installed
windows 10
usb debugging enabled
oem unlock enabled
adb ??i just extract it and place it on Local Disk C and run the cmd file as administrator
Click to expand...
Click to collapse
I found this to be the best solution, for anyone still struggling with this. https://forum.xda-developers.com/t/...ng-up-in-fastboot-mode-windows-10-11.4194491/

[HELP] "Your phone is locked because Payment Services was uninstalled"

While debloating Samsung Galaxy A70 (rooted) I've disabled something I shouldn't have, and now my phone is locked with a message "Your phone is locked because Payment Services was uninstalled without authorization". I don't have a Samsung Account, so remote unlocking is a no-go.
I need to somehow:
A) Backup my data from internal storage and do a factory reset. (Can't access storage without unlocking the device though...)
B) Unfreeze or reinstall the Payment Services / Samsung Pay app. (I found a guide for another device on how to do it via adb, but my device isn't detected via adb).
C) Re-flash stock firmware with all the stock apps using Odin, without wiping user and app data. (Is this even possible?)
EDIT: SOLVED via method B:
I managed to establish an adb connection. I was trying to do it with the portable version of "minimal adb and fastboot", but it didn't work. "cmd-here.exe" wouldn't show any devices. I tried using non-portable version of "minimal adb and fastboot", and used "cmd" to send commands to adb.exe. It still wasn't detecting the device. I found a fix though:
After unlocking the lock screen, you have a few seconds before the phone will re-lock itself. Use those few seconds to enable developer options (if you haven't already). After the phone locks itself again - reboot, unlock the lock screen, and quickly enable USB debugging before the phone re-locks. Reboot again, unlock the lock screen, request an adb connection (I used "adb devices" command) and click "allow" on the pop-up that appears when your device receives an adb connection. As long as you allow the connection before the device re-locks - it'll stay connected via adb.
Now you can send the adb command to re-enable Samsung Pay. The command in the guide I linked above was incomplete, so it didn't work for me and it took me some searching to figure out why. The full command is
adb shell pm enable --user 0 com.samsung.android.kgclient
Click to expand...
Click to collapse
If you did everything correctly, you should see the message in cmd showing that the package has been enabled.
Hope this helps for anyone with the same problem.

enquil said:
While debloating Samsung Galaxy A70 (rooted) I've disabled something I shouldn't have, and now my phone is locked with a message "Your phone is locked because Payment Services was uninstalled without authorization". I don't have a Samsung Account, so remote unlocking is a no-go.
I need to somehow:
A) Backup my data from internal storage and do a factory reset. (Can't access storage without unlocking the device though...)
B) Unfreeze or reinstall the Payment Services / Samsung Pay app. (I found a guide for another device on how to do it via adb, but my device isn't detected via adb).
C) Re-flash stock firmware with all the stock apps using Odin, without wiping user and app data. (Is this even possible?)
EDIT: SOLVED via method B:
I managed to establish an adb connection. I was trying to do it with the portable version of "minimal adb and fastboot", but it didn't work. "cmd-here.exe" wouldn't show any devices. I tried using non-portable version of "minimal adb and fastboot", and used "cmd" to send commands to adb.exe. It still wasn't detecting the device. I found a fix though:
After unlocking the lock screen, you have a few seconds before the phone will re-lock itself. Use those few seconds to enable developer options (if you haven't already). After the phone locks itself again - reboot, unlock the lock screen, and quickly enable USB debugging before the phone re-locks. Reboot again, unlock the lock screen, request an adb connection (I used "adb devices" command) and click "allow" on the pop-up that appears when your device receives an adb connection. As long as you allow the connection before the device re-locks - it'll stay connected via adb.
Now you can send the adb command to re-enable Samsung Pay. The command in the guide I linked above was incomplete, so it didn't work for me and it took me some searching to figure out why. The full command is
If you did everything correctly, you should see the message in cmd showing that the package has been enabled.
Hope this helps for anyone with the same problem.
Click to expand...
Click to collapse
Came here just to thank you for explaining this procedure: it allowed me to recover a debloat activity gone wrong. Thanks!

enquil said:
While debloating Samsung Galaxy A70 (rooted) I've disabled something I shouldn't have, and now my phone is locked with a message "Your phone is locked because Payment Services was uninstalled without authorization". I don't have a Samsung Account, so remote unlocking is a no-go.
I need to somehow:
A) Backup my data from internal storage and do a factory reset. (Can't access storage without unlocking the device though...)
B) Unfreeze or reinstall the Payment Services / Samsung Pay app. (I found a guide for another device on how to do it via adb, but my device isn't detected via adb).
C) Re-flash stock firmware with all the stock apps using Odin, without wiping user and app data. (Is this even possible?)
EDIT: SOLVED via method B:
I managed to establish an adb connection. I was trying to do it with the portable version of "minimal adb and fastboot", but it didn't work. "cmd-here.exe" wouldn't show any devices. I tried using non-portable version of "minimal adb and fastboot", and used "cmd" to send commands to adb.exe. It still wasn't detecting the device. I found a fix though:
After unlocking the lock screen, you have a few seconds before the phone will re-lock itself. Use those few seconds to enable developer options (if you haven't already). After the phone locks itself again - reboot, unlock the lock screen, and quickly enable USB debugging before the phone re-locks. Reboot again, unlock the lock screen, request an adb connection (I used "adb devices" command) and click "allow" on the pop-up that appears when your device receives an adb connection. As long as you allow the connection before the device re-locks - it'll stay connected via adb.
Now you can send the adb command to re-enable Samsung Pay. The command in the guide I linked above was incomplete, so it didn't work for me and it took me some searching to figure out why. The full command is
If you did everything correctly, you should see the message in cmd showing that the package has been enabled.
Hope this helps for anyone with the same problem.
Click to expand...
Click to collapse
I wish I could by you a beer Bro. I thought I was gonna have to factory reset my S22 Ultra with over 200GBs used. I had to disable then re-enable USB debugging to get it to work. Minmall ADB didn't work for me so I had to Powershell.