Database Info

[Q] Looking for a way to turn on USB Debugging on phone w/ smashed screen

Hi,
was using this guide online to try to recover and move stuff around in my Nexus5 while it is broken as far as i know this is a LCD problem not a digitiser problem.
http://www.techlife.net/2014/09/access-your-android-device-after-breaking-your-screen.html/
http://forum.xda-developers.com/showthread.php?t=2786395
ran into a problem that I can't turn on USB Debugging on my phone without being able to see what i am pressing.
According to the end of the guide it told me to flash a kernel with USB debugging enabled by default but I am unsure of what this means.
Rooted: No (I dont mind if i have to)
Fastboot: No idea
Installed ADB on computer: Yes

The custom kernel will need to have USB debugging ON by default/on boot. Usually through a custom initrc.

If you manage to get rooted, you could try:
androidscreencast

- Flash TWRP if you haven't already
- boot to recovery
- adb shell
- mount system
- edit build.prop
- reboot
- figure out adbkey.pub stuff
I have gone the same way, but could not get a screen display. It was on my wife's Gnex though. The rest works.
Now to get debian or something installed...ultralow power wireless server.

You need to install ADB/Fastboot to your PC
GO HERE
Then you can
Enable usb debugging via recovery using the following ABD commands:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot

joegestes said:
You need to install ADB/Fastboot to your PC
GO HERE
Then you can
Enable usb debugging via recovery using the following ABD commands:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
Click to expand...
Click to collapse
OP, try this.

The two previous posts are forgetting you need usb debugging before you can adb shell.
Booting to recovery gives you access to your system and build.prop.

Bubble-be said:
The two previous posts are forgetting you need usb debugging before you can adb shell.
Booting to recovery gives you access to your system and build.prop.
Click to expand...
Click to collapse
recoveries have adbd enabled by default. what we're doing here is making the OS have adbd enabled.

Yes, we're on the same page there.
You can't just adb to your device to enable adb, get it ?
You need a way to access build.prop out of android, so booting to recovery will allow you this.
Just dugg up the link for the adbkey as well. http://forum.xda-developers.com/showthread.php?t=2408802

get a USB OTG cable and connect your mouse to your phone

Bubble-be said:
Yes, we're on the same page there.
You can't just adb to your device to enable adb, get it ?
You need a way to access build.prop out of android, so booting to recovery will allow you this.
Just dugg up the link for the adbkey as well. http://forum.xda-developers.com/showthread.php?t=2408802
Click to expand...
Click to collapse
Huh...
Even if display isn't coming on... You can 3bc to fastboot, press down twice (iirc) and press power. wait a few secs, custom recovery should be running.
`adb shell` .. out of android, adb running. profit.

I think the OP is not rooted, nor does he have a custom recovery.
In that case you will need boot temporarily into a custom recovery that will allow root ADB shell access.
Download the TWRP recovery image to you PC.
HERE
For simplicity, rename the file recovery.img
Place the renamed file in your \sdk\platform-tools folder on PC.
Turn off you phone and then hold volume up button while pressing power button to get into fastboot mode.
Then, open a command prompt from within the platform-tools folder and run the following command:
fastboot boot recovery.img
Your phone should reboot into TWRP recovery.
You can then run the ADB commands outlined in my first post to enable usb debugging:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
Best of luck

Bubble-be said:
The two previous posts are forgetting you need usb debugging before you can adb shell.
Booting to recovery gives you access to your system and build.prop.
Click to expand...
Click to collapse
This is incorrect.
I do not need usb debugging enabled to run ADB shell in custom recovery.
Bubble-be said:
Yes, we're on the same page there.
You can't just adb to your device to enable adb, get it ?
You need a way to access build.prop out of android, so booting to recovery will allow you this.
Just dugg up the link for the adbkey as well. http://forum.xda-developers.com/showthread.php?t=2408802
Click to expand...
Click to collapse
Huh
My post clearly stated via recovery
---------- Post added at 06:31 PM ---------- Previous post was at 06:13 PM ----------
4n3ver said:
get a USB OTG cable and connect your mouse to your phone
Click to expand...
Click to collapse
I've never tried this, but think you need to be rooted and install some hacks to get a mouse
to work via OTG.

Hello again,
Thanks for all the replies so far.
Unfortunately i'm still unable to enable USB debugging.
I'm getting stuck, I have managed to install adb and fast boot using the 15 second thing but am unable to get it to detect via "adb devices" and am currently troubleshooting this step
I can't upload images so i'm just gonna type what it says
Code:
C:\Users\blah> fastboot boot recovery.img
<waiting for device >
^C
C:\Users\blah> adb devices
List of devices attached
C:\Users\blah>
probably something to do with how my adb drivers are installed
Just to clarify my screen is impossible to use as its just coloured lines due to cracks in the LCD screen.
Hopefully all goes well and i'll be able to fastboot TWRP with the instructions you guys have given me.

fuzznuzz said:
Hello again,
Thanks for all the replies so far.
Unfortunately i'm still unable to enable USB debugging.
I'm getting stuck, I have managed to install adb and fast boot using the 15 second thing but am unable to get it to detect via "adb devices" and am currently troubleshooting this step
I
Click to expand...
Click to collapse
Your welcome.
It's probably just simple a driver issue. You will need to look in Device manager on PC while phone is connected.
Download the howto_driver.zip from the "15 seconds ADB Installer thread" and follow the picture tutorial contained in the zip file. This should fix your connectivity issues:good:
---------- Post added at 03:23 AM ---------- Previous post was at 02:58 AM ----------
If it helps, I don't have the "Android Bootloader Interface" driver option. So for me,
selecting "Android Composite ADB Interface" allows me to detect my Nexus5 in both ADB and Fastboot mode.
Keep in mind, my OS Win7 64bit and my 64 bit ADBdriver package may be entirely different than yours.

Okay i'm having some other problems now
can anyone help?

fuzznuzz said:
Okay i'm having some other problems now
can anyone help?
Click to expand...
Click to collapse
Your bootloader is locked.
Sent from my Nexus 5 using XDA Free mobile app

fuzznuzz said:
Okay i'm having some other problems now
can anyone help?
Click to expand...
Click to collapse
Locked bootloader
It is the first question I or anyone replying should have asked you.
Unfortunately, as far as I know, it's game over recovering any user data with
a busted non-viewable LCD, no USB debugging and a locked bootloader.
Unless, you can by some luck, miracle or Power of the Force, pull off using your touchscreen to enable USB debugging.
Then you could use Simple ADB Backup or Holo Backup to get your data.
If not and your data is important enough to you, then replacing the screen would be your last option.
Worth replacing IMHO because your Nexus 5 is still a really great phone with nice specs and plenty of power.
Found one HERE shipped from China for $46.76 or HERE from USA $69.99 from US on ebay.

didn't work
joegestes said:
You need to install ADB/Fastboot to your PC
GO HERE
Then you can
Enable usb debugging via recovery using the following ABD commands:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
Click to expand...
Click to collapse
i followed all these steps and adb devices shows nothing while phone is in recovery mode
fastboot devices shows my phone when in fastboot mode
just adb not working
help asap please

halo_95 said:
i followed all these steps and adb devices shows nothing while phone is in recovery mode
fastboot devices shows my phone when in fastboot mode
just adb not working
help asap please
Click to expand...
Click to collapse
Do you have a stock recovery or a custom one?
You'll need to boot a custom recovery, not the stock recovery.
Now that you don't have to install the custom recovery, just boot it.

Can't remove malicious app

I've installed a malicious app called "Game Launcher" which has forced my Galaxy s7 into secure mode.
I've tried every way of uninstalling it from inside the android system but nothing works.
Since my volume button is broken, I can't get into recovery mode to factory reset phone that way.
I thought about trying to remove the app or wiping/resetting the phone through ADB but it wouldn't recognize the device(probably because of the malware) even though it recognizes all other devices.
Does anyone have an idea how I could solve this?
Thanks for all replies!!

Enable usb debugging in developer options and
Dial *#0808# select DM+ACM+ADB.
Connect to adb and do:
adb shell pm uninstall packagenameofvirus
Done

kpwnApps said:
Enable usb debugging in developer options and
Dial *#0808# select DM+ACM+ADB.
Connect to adb and do:
adb shell pm uninstall packagenameofvirus
Done
Click to expand...
Click to collapse
Thanks for your help!
I've used "adb shell pm list packages -3 -f." to get all the installed packages and then I've removed them but the problem still persists. I was able to boot into recovery with adb intending to wipe the device that way, but then I couldn't navigate the recovery menu because my volume buttons are broken. Any ideas?

rekkio said:
Thanks for your help!
I've used "adb shell pm list packages -3 -f." to get all the installed packages and then I've removed them but the problem still persists. I was able to boot into recovery with adb intending to wipe the device that way, but then I couldn't navigate the recovery menu because my volume buttons are broken. Any ideas?
Click to expand...
Click to collapse
Connect to adb again while your phone is on and
Use adb shell am broadcast -a android.intent.action.MASTER_CLEAR

kpwnApps said:
Connect to adb again while your phone is on and
Use adb shell am broadcast -a android.intent.action.MASTER_CLEAR
Click to expand...
Click to collapse
When doing that, i get this output, "Broadcasting: Intent { act=android.intent.action.MASTER_CLEAR flg=0x400000 }
Broadcast completed: result=0" and nothing has changed.
I'm able to boot into download mode with adb so I'm thinking about downloading a stock rom and flashing it with Odin.
Read that it's supposed to wipe and reset when doing that.

Android 10 ADB

Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the

Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the
Click to expand...
Click to collapse
You can't see the device while on fastboot mode of you type adb devices.
You need to make sure debugging is on in the developer preferences.

ADB appears to be working just fine for me.

When using adb make sure you have debugging enabled and grant the popup on screen

adb is not fastboot. You can use adb on twrp or booted system. Fastboot is on bootloader mode.

Also need to make sure that the proper USB drivers on the computer are installed/updated.

Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
Click to expand...
Click to collapse
This is working exactly as intended, and not exclusive to Android 10, but rather has been the case as long as I can remember (Jelly Bean? KitKat? Maybe much earlier?):
adb: Only works when booted to OS or in TWRP. Debugging required to be toggle on in phone settings. Does not work in bootloader-fastboot mode.
fastboot: Only works in bootloader-fastboot mode. Debugging is not required to be toggled on.

D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...

Bringer1 said:
D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...
Click to expand...
Click to collapse
Sounds like another adb server is still running. What does adb kill-server and then trying again do

a second adb server was running.
TNX

Can I mount system rw using adb enabled recovery img from the following link:
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865

Poco X3 (India) with MiUi 12.0.5 bootloops as SMALLEST WIDTH changed to 1080 :silly:

Hi All,
Got a Poco X3 (Non-NFC); was just changing "smallest width" to 1080.
Meanwhile, the smartphone went on boot-loops after few seconds. Read many threads and Questionnaires.
I tried the following command: { adb shell wm density 400 && adb reboot }
But device shows unauthorized and so adb commands fail.
One option is Factory Reset, easy and convenient; but I don't want to lose my data.
Following are the scenarios:
1. USB Debugging is enabled (Although device is unauthorized.)
2. Connected to Mi PC Suite, but it didn't recognise my phone, although cmd shows device in "sideload" mode.
3. Bootloader is locked. Fastboot recognises device in fastboot mode.
I believe that if anyhow, ADB Device authorisation can be bypassed, then I can execute shell commands and reset density.
Any help/suggestion is appreciated.

How to escape TWRP? Activate ADB w/ broken screen?

So my screen broke on my Note 10+, leaving only the top 15% with display and the bottom 60% with touch. I am trying to activate ADB on it so that I can backup my internal storage.
I booted into TWRP so that I could backup the rest of my system, which I did successfully, but because of the bad touch screen I am unable to hit the ADB side load button. I'd like to reboot into the system because I have ADB enabled there, however I also cannot click the reboot to system button, only reboot to download and shutdown. Since I can't see most of the screen, it is also not possible to access the terminal and work from there.
Anybody know how I can escape TWRP or otherwise activate ADB? Thanks for the help.

Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload

jwoegerbauer said:
Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload
Click to expand...
Click to collapse
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.

AllanRSS said:
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.
Click to expand...
Click to collapse
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot

jwoegerbauer said:
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot
Click to expand...
Click to collapse
I can not use ADB. It is for this very reason I am asking how to enable ADB. But thank you for these valuable ADB commands, I'll be sure to reboot my system once I enable ADB