Digitizer is broken, but I can see the screen. I need to enable debugging but I have absolutely no touch response.
I know that debugging is enabled in a custom recovery but I need it to be enabled on the os level. Is there a ROM that has USB debugging enabled by default? A backup image of a stock image with usb debugging enable would work too. (I am not trying to enable MTP or pull data, I am trying to establish adb and lunch a program with os running"
I have tried enabling it via terminal in recovery but its not working; I can't seem to find the path to change the value.
Thanks in advance.
I actually have the same exact issue. The screen is smashed to hell, but it still turns on and off. I still get calls, texts, and all other notifications...but the touch screen is totally unresponsive and I can't get to my files through my computer because I can't unlock the phone. If there's anyway around this, I'd much appreciate the help too.
Thanks.
frankyredz said:
I actually have the same exact issue. The screen is smashed to hell, but it still turns on and off. I still get calls, texts, and all other notifications...but the touch screen is totally unresponsive and I can't get to my files through my computer because I can't unlock the phone. If there's anyway around this, I'd much appreciate the help too.
Thanks.
Click to expand...
Click to collapse
well your problem is easy...well easier.
unlock the bootloader flash a custom recovery (cwm) you can enable SD card via the recovery and move your files using MTP. search the forum for "how-tos"
Why not use a mouse or keyboard?
ace7196 said:
Why not use a mouse or keyboard?
Click to expand...
Click to collapse
No otg and you need your screen to setup a Bluetooth connection, right?
otg http://forum.xda-developers.com/showthread.php?t=2181820
also, use the google. tons of people have busted their digitizers. http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
ziddey said:
otg http://forum.xda-developers.com/showthread.php?t=2181820
also, use the google. tons of people have busted their digitizers. http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
Click to expand...
Click to collapse
No otg without external power*
Better?
ace7196 said:
Why not use a mouse or keyboard?
Click to expand...
Click to collapse
no native OTG, Enabled debugging ROM would solve my problem much easier
ziddey said:
otg http://forum.xda-developers.com/showthread.php?t=2181820
also, use the google. tons of people have busted their digitizers. http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
Click to expand...
Click to collapse
I actually stumbled upon this but only saw the first part. and had the same problem where the value would not stick. Didn't see the second part; will try. Still, a rom that has debugging enabled would be ideal and is originally what I asked for in the op. Nevertheless, thank you.
estallings15 said:
No otg without external power*
Better?
Click to expand...
Click to collapse
LOL. this.
Bump. None of the above has worked. Is there a ROM that adb is enabled by default? CM?
Sent from my Nexus 4 using xda app-developers app
Thread Necromancer requires assistance!
frankyredz said:
I actually have the same exact issue. The screen is smashed to hell, but it still turns on and off. I still get calls, texts, and all other notifications...but the touch screen is totally unresponsive and I can't get to my files through my computer because I can't unlock the phone. If there's anyway around this, I'd much appreciate the help too.
Thanks.
Click to expand...
Click to collapse
Sorry for dredging up a dead post from ages long forgotten, but I was hoping to find some semblance of help here.
I am fully aware of the fact that this is for the Nexus 4, but I'm optimistic in my approach to find answers regarding the absolutely decimated screen and digitizer of my (otherwise undamaged) AT&T Exhilarate (i577) android.
It'll be about a week before I can get in to get them replaced, so I was hoping to at least read the texts that I've since received or scavenge my contacts via [email protected] due to situational intensity ((family member health issues)My Google account does not hold this information), and I've followed all of the setup walk through found here: droid-at-screen.ribomation..com/installation/
My issue now is that I cannot load my device from the [email protected] application, presumably caused by a severe lack of USB debugging enabling.
My phone is not rooted or modded in the least.
Is there any hope for me?
Thanks in advance!~
I was in the same situation with a HTC Sensation.
I had to S-OFF to get superCID and get the screen calibration to work.
But juopunutbear required to be in normal mode and ADB enabled. I finally get it working by installing CWM recovery, which has ADB, and enable the adb debugging.
adb shell
mount -a
(if the following two commands show error "file doesn't exist", don't worry, it's ok!)
rm /data/property/persist.service.adb.enable
rm /data/property/persist.sys.usb.config
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"
/system/xbin/sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value='1' where name='adb_enabled'";
/system/xbin/sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value='1' where name='development_settings_enabled'";
sync
reboot
Click to expand...
Click to collapse
If the sqlite3 command shows error (command not found) then your phone doesn't have sqlite3 installed.
Still, you can do it!
First extract settings.db:
adb pull /data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Copy that file to a usb drive or whatever.
Now you need linux. It's ok to use a live Ubuntu DVD, but you need to be connected to internet.
http://www.ubuntu.com/download/desktop
I recommend to use the 32bit version for compatibility.
Usually sqlite3 is not installed by default.
In ubuntu:
sudo apt-get install sqlite3
Click to expand...
Click to collapse
You will be asked for the root password!
Now we can edit the settings.db:
sudo sqlite3 /path_to_your_folder/settings.db
update global set value='1' where name='adb_enabled';
update global set value='1' where name='development_settings_enabled';
.exit
Click to expand...
Click to collapse
Now we have the settings.db changed and ready!
Copy that settings.db again to a pen drive or whatever, go back to windows or keep in linux if you already have a working ADB.
adb push settings.db /data/data/com.android.providers.settings/databases/
adb shell "chown system.system /data/data/com.android.providers.settings/databases/settings.db"
adb shell "chmod 644 /data/data/com.android.providers.settings/databases/settings.db"
sync
reboot
Click to expand...
Click to collapse
Done! ADB should work when in starts.
I had to use "mass_storage,adb" because "mtp,adb" or just "adb" didn't work. Thought, the phone was not working in mass storage, but who cares! ADB was!
thanks @dabyd64 , i was in a similar situation of dealing with an htc evita, basically a corrupted rom made the display useless, so had to enable debugging via recovery, I used twrp. And its enabled now.
Thanks @dabyd64!!!! I also was in a similar situation of my Samsung Xcover 2 S-7710. I succesfully enabled the debuging mode
Wow, I'm working with something old... My old Nexus 7 2013 is having touch screen problems so I tried the sqlite3 option. The commands executed fine but now I'm in a boot loop. It's been booting for twenty minutes. Any advice?
Wow this is OLD !
Make a factory reset,that should fix the bootloop .
And then try again?
I was trying this recovery screenshot tool http://forum.xda-developers.com/showthread.php?p=50029759#post50029759 without installing adb. I followed the instructions and wrote the width 240 and the height 320 (I am not at all sure of those) and when it tried to take the framebuffer i got the error "adb is not properly connected" and asks me to try to unplug and reinsert the usb cable. I then installed adb using this procedure http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 and after successful installation i got the same error.
thanks in advance
maged rifaat said:
I was trying this recovery screenshot tool http://forum.xda-developers.com/showthread.php?p=50029759#post50029759 without installing adb. I followed the instructions and wrote the width 240 and the height 320 (I am not at all sure of those) and when it tried to take the framebuffer i got the error "adb is not properly connected" and asks me to try to unplug and reinsert the usb cable. I then installed adb using this procedure http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 and after successful installation i got the same error.
thanks in advance
Click to expand...
Click to collapse
Make sure you have USB debugging enabled in your phone settings
You can test if adb is connected by doing the following
Open a command prompt where you have adb.exe
Type the following
adb devices
You will then get a list of devices connected
Remember not all kernels support adb in recovery mode
not all kernels?
marcussmith2626 said:
Make sure you have USB debugging enabled in your phone settings
You can test if adb is connected by doing the following
Open a command prompt where you have adb.exe
Type the following
adb devices
You will then get a list of devices connected
Remember not all kernels support adb in recovery mode
Click to expand...
Click to collapse
I have the debugging mode enabled and when i tried the "adb" devices command in the adb.exe directory it didnt show that there is any device connected.
about the "not all kernesupport adb" note how about stock kernel? and what best kernels work with adb and doesnt affect my systemfile and other things?
Edit: i flashed savie's kernel and i think it works
problems with the tool
I now have a problem that when i try to make a configuration file all screenshots in the pixel_formats folder are disturbed in a certain pattern (every line is a bit compressed vertically and the line is with a slope so the picture is completely disturbed)
I managed to get a clear screenshot using manual mode but the problem there that i sometimes scroll to something in the recovery and i take the screenshot i found it didnt scroll i then try to open a menu or so and take the screenshot it gives me a hollow screenshot with only the background of the CWM it happens nearly always so i cant get proper screenshots what i can do? and also i found the manual mode is a bit hard as i have to change the setting every time isnt there any tool easier than this
thanks in advance
maged rifaat said:
I have the debugging mode enabled and when i tried the "adb" devices command in the adb.exe directory it didnt show that there is any device connected.
about the "not all kernesupport adb" note how about stock kernel? and what best kernels work with adb and doesnt affect my systemfile and other things?
Edit: i flashed savie's kernel and i think it works
Click to expand...
Click to collapse
It's the kernel & cwm build - I don't know exactly what has to be enabled in the kernel & the CWM build but unless they support adb in recovery it won't work
Think manual mode is the best way as the galaxy y is ldpi - There probably are other tools out there you just have to search around
thanks !
marcussmith2626 said:
It's the kernel & cwm build - I don't know exactly what has to be enabled in the kernel & the CWM build but unless they support adb in recovery it won't work
Think manual mode is the best way as the galaxy y is ldpi - There probably are other tools out there you just have to search around
Click to expand...
Click to collapse
I cant thank you enough whenever i have a problem i find you helping me really thanks
My commands on Terminal Emulator do not work. I've already tried to change de dpi (wm density) and screen resolution (wm size) and nothing happens.
Here's what it shows.
Could there be something to do with 'Busybox on rails'? 'Busybox'? 'Build.prop Editor'?
Is there any other way to change the screen resolution?
Thanks.
(PS: Android MM 6.0)
(PS2:Yes, I'm rooted. Yes, I typed "su". Yes, I tried multiple emulators)
I want to do what "thedicemaster" explained here
I need to extend the automatic lock delay to more than 30 minutes. Does anyone have experience with this? I have installed ADB and installed an app called "Secure Settings" but I don't see the option to extend the delay.
Anyone an idea on how to do this?
I did it through Tasker and Plugin "SecureTask". To be found in category "Secure Settings"
You have to grant 4 permissions for the plugin, mentioned inside the app.
It's been years already but I have a way to get it to work without root without installing any apps. I hope it helps some one.
You will need adb and usb debugging on. Open cmd / terminal and execute these 2 commands:
Code:
adb shell settings put secure lock_after_timeout_rollback 86400000
adb shell settings put secure lock_screen_lock_after_timeout 86400000
86400000 = 24 hours in miliseconds. You can change to a number that you find suitable.
This secure settings will survive after reboot so you only need to do once.
Can you give this command to work on new Android devices (I have android 12 and it shows that there is no put command
alex.do said:
It's been years already but I have a way to get it to work without root without installing any apps. I hope it helps some one.
You will need adb and usb debugging on. Open cmd / terminal and execute these 2 commands:
Code:
adb shell settings put secure lock_after_timeout_rollback 86400000
adb shell settings put secure lock_screen_lock_after_timeout 86400000
86400000 = 24 hours in miliseconds. You can change to a number that you find suitable.
This secure settings will survive after reboot so you only need to do once.
Click to expand...
Click to collapse
alex.do said:
It's been years already but I have a way to get it to work without root without installing any apps. I hope it helps some one.
You will need adb and usb debugging on. Open cmd / terminal and execute these 2 commands:
Code:
adb shell settings put secure lock_after_timeout_rollback 86400000
adb shell settings put secure lock_screen_lock_after_timeout 86400000
86400000 = 24 hours in miliseconds. You can change to a number that you find suitable.
This secure settings will survive after reboot so you only need to do once.
Click to expand...
Click to collapse
Sorry for the more-than-one-year-late reply. I just saw this post now.
I have tried these commands on my Android 11 device. Both run with no error, but they do not alter the screen-turning-off timeout on the lockscreen. I ran them both with and without root mode.
I also tried lower timeout values, such as 30000 (30 seconds), and the commands still seem to have no effect.
But I have good news: I run "Gravity Box", and I discovered that it allows certain settings to be modified via its "Advance Tuning" facility. It allows the "System UI" setting called config_lockScreenDisplayTimeout to be modified, and that indeed controls this particular screen-turning-off timeout on the lock screen, at least on my A11-based device (not a Samsung device, so I don't know if it will work for you).
However, any change to this timeout value when the device is running is ignored until the next reboot.
XA1 SCREEN ISSUE EDGES
Download ADB Drivers link ADB
install it on c Drive
open CMD with admin rights
go to phone unlock programistic tools 5 times on kernel version
USB DEBUGGIN Must be turned on
Go to cmd
type
Cd c:/adb
adb devices
go to phone and click checkbox
in cmd type
adb shell wm size 710x1500
download microsoft swiftkey keboard after this go to setting and microsoft keyboard settings
click layout and position and you can prepare keyboard for yourself left edges and right transfer little bit to the center
after this type in cmd this adb shell wm size 760x1500
and everythings works!!!!
if you have problem with notification toolbar to slide down download shortcut app >>> notification
DONATION Buy me beer