Develop Bugs

Adb problems on 4.2.2 ROMS

I can't connect adb on any 4.2.2 ROMS, i understand theres a new security feature in 4.2.2 that should prompt you to confirm your PCs RSA key, but i never get this prompt. Also, ktoonsez kernel seems to bypass the security, as it allows me to connect without ever seeing the prompt. But any other kernel, no prompt, and all adb commands show device offline.
I do have the latest version of adb (1.0.31) and the latest sdk etc.., i also can't connect to adb using the USB cable either. I've tried reinstalling drivers, rebooting... nothing seems to be working.
any suggestions?
Edit: got it working. Can't say i know exactly what i did to fix it, but i'll try to reiterate what i just did. Clean flashed a new ROM, in developer options > root access set to Apps and ADB, make sure Android debugging is enabled, make sure USB debugging notify is enabled, then turn on adb wireless. Then on my pc connect to adb using "adb connect 192.168.1.x", adb devices shows device still offline. Then connected my phone to my pc through usb and i got the prompt. FINALLY lol

I'm sure you already did this, but you didn't mention it.
In a lot of 4.2.2 ROM's, you have to go into Developer Options and change from "Root access for Apps Only" to "Root Access for Apps and ADB".
Not all 4.2.2 ROM's do this, but some of them do.
I could not ADB from my computer to my 4.2.2 until I changed that selection.
Also, some new ROM's have the built-in Superuser which includes an ADB option in its settings.

CZ Eddie said:
I'm sure you already did this, but you didn't mention it.
In a lot of 4.2.2 ROM's, you have to go into Developer Options and change from "Root access for Apps Only" to "Root Access for Apps and ADB".
Not all 4.2.2 ROM's do this, but some of them do.
I could not ADB from my computer to my 4.2.2 until I changed that selection.
Also, some new ROM's have the built-in Superuser which includes an ADB option in its settings.
Click to expand...
Click to collapse
Tried it, no luck.

Maybe try this?
https://plus.google.com/+CyanogenMod/posts/M2pVM7Y6MTq

CZ Eddie said:
Maybe try this?
https://plus.google.com/+CyanogenMod/posts/M2pVM7Y6MTq
Click to expand...
Click to collapse
I appreciate the input but all that post says is that you must be on the latest SDK version which I mentioned I already was

[Q] dpi oops

Changed the DPI using Android Tweaker 2 from 640 to 560, and when I rebooted somehow it set to 430, which is causing constant redraws of the screen (screen goes on off constantly) - the phone boots, and I can open the app, but it only gives me about 1 second to do something, and it's too quick for me to bring the keyboard up to set a different value.
How can I restore the default DPI or set it to 560 without reinstalling my phone. Is there a way I can do it on the computer?

Yes you can do it from your computer. You will have to edit a file called build.prop.
1: You will need ADB and the LG USB drivers. If you do not already have the Android SDK set up, download this tool to get ADB. You can get the USB driver here.
2: open a CMD window in the directory ADB is installed (seems the installer for ADB can also do this for you)
3: Go into your phone's Settings > About Phone. Tap the build number several times until it has said you have enabled developer options.
4: Go back to the main settings and go into Developer Options.
5: Find the "Android Debugging" option and turn it on. Find the "Root Access" option as well and set it to "Apps and ADB".
6: Connect your phone to your computer and type "adb devices" in the command prompt window. Hopefully, it lists a device on there.
7: Type "adb pull /system/build.prop %userprofile%\Documents"
8: Go to your computer's documents folder and open build.prop in your choice of file editor (Notepad works, but I wouldn't recommend it...)
9: Find the line "ro.sf.lcd_density" in build.prop. Change this to the number you want (540 or 640). Save the file.
10: Go back to the CMD window and type "adb push %userprofile%\Documents\build.prop /system/build.prop"
11: Reboot your phone. If all went well, your screen should be back to normal.

I can't seem to find Android Debugging or Root Access (I can only see USB Debugging which is enabled)
Also after typing "adb devices" in CMD, it lists mine but says offline.

Curleyyy said:
I can't seem to find Android Debugging or Root Access (I can only see USB Debugging which is enabled)
Also after typing "adb devices" in CMD, it lists mine but says offline.
Click to expand...
Click to collapse
USB Debugging will be the same thing.
Try typing "adb kill-server" and then "adb devices" again. Also try using a different USB port on your computer.

No Devices in ADB Prompt

I have a strange issue. After installing the Shield drivers, when I type in "fastboot devices" a number comes up. But when I type in "adb devices" it's completely blank. I cannot install SuperSu without it as I learned the hard way. Does anyone know why this is happening? Is it a possibility that using the Nvidia Shield TV 2017 version causes an issue with the ADB devices not showing up?

CrescentShield said:
I have a strange issue. After installing the Shield drivers, when I type in "fastboot devices" a number comes up. But when I type in "adb devices" it's completely blank. I cannot install SuperSu without it as I learned the hard way. Does anyone know why this is happening? Is it a possibility that using the Nvidia Shield TV 2017 version causes an issue with the ADB devices not showing up?
Click to expand...
Click to collapse
Did you remember to enable the hidden Developer
Settings (System > About Device > Build (7x Tap)), and then from those new Settings actually enable the USB Debugging? Otherwise yeah you're not getting far. Also not so sure if it applies to Fastboot per-se but, in the case of ADB you'll also have to confirm via a Checkbox that you want to log into the system that way.

Ichijoe said:
Did you remember to enable the hidden Developer
Settings (System > About Device > Build (7x Tap)), and then from those new Settings actually enable the USB Debugging? Otherwise yeah you're not getting far. Also not so sure if it applies to Fastboot per-se but, in the case of ADB you'll also have to confirm via a Checkbox that you want to log into the system that way.
Click to expand...
Click to collapse
I did enable USB debugging but have since learned a few things about using that software. Your device firmware has to be functional so ADB can see it, at least in my case. Now when I connect I can see it in ADB and TWRP. And if don't see it in TWRP you can always install the root manually.

[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.

Please i need an advice from you experts. I really appreciate any info

I have a Pixel 3a xl, I fix its screen after a crash but even though I have registered my finger print, I forgot the password. I've been learning how to use ADB and FASTBOOT, but with no success. I'm totally a beginner. I've tried to run "adb shell" but it shows me "closed" and the only way to list my device with "adb devices" is when I reboot my phone in "RESCUE MODE", I run adb devices and it shows:
List of devices attached
94GAX0DZ1U rescue
However when I run adb "shell" "usb" "backup" the response is always: ERROR: closed
My debug mode is probably unable, i do not remember if y/n
I'm using:
Android Debug Bridge version 1.0.41
Version 30.0.5-6877874
Installed as /Users/admin/Library/Android/sdk/platform-tools/./adb
add: unable to connect for backup: closed
I've read about TWRP but i do not know if it means erasing my userdata "which is what i want to keep on my phone" Photos/videos etc
Please, I really appreciate any help about what you recommend me to do

kristianss27 said:
I have a Pixel 3a xl, I fix its screen after a crash but even though I have registered my finger print, I forgot the password. I've been learning how to use ADB and FASTBOOT, but with no success. I'm totally a beginner. I've tried to run "adb shell" but it shows me "closed" and the only way to list my device with "adb devices" is when I reboot my phone in "RESCUE MODE", I run adb devices and it shows:
List of devices attached
94GAX0DZ1U rescue
However when I run adb "shell" "usb" "backup" the response is always: ERROR: closed
My debug mode is probably unable, i do not remember if y/n
I'm using:
Android Debug Bridge version 1.0.41
Version 30.0.5-6877874
Installed as /Users/admin/Library/Android/sdk/platform-tools/./adb
add: unable to connect for backup: closed
I've read about TWRP but i do not know if it means erasing my userdata "which is what i want to keep on my phone" Photos/videos etc
Please, I really appreciate any help about what you recommend me to do
Click to expand...
Click to collapse
stupid question did you enable USB debugging on your phone
tap build number till you see developer options, turn on USB degugging?
try using ADB link for windows you should be able to get bonito shell