Hello All,
I've recently broken my LCD, not cracked, but the contrast material leaked into the screen, eventually turning everything black. I can still use the digitizer, but have no concept what's going on screen. Let's just say, I've been luck and unlucky. My though was to use a screen viewing tool via adb to grab some phone numbers of recent calls/texts before I send to Samsung for repair (the phone agent said they would wipe it back to stock). What I have been trying to do is enable ADB/USB debugging through recovery.
Here's what I've tried so far:
1) Boot to recovery
2) Mount /system as rw
3) pull default.proc and build.proc from their respective directories
4) add the following lines to each
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb (this line was already located in the default.proc file)
5) push files back to their respective directories
6) reboot
Upon reboot, I'm stuck in a loop. I can't tell what's going on, how far it's getting etc because no display. I assume I'm getting past the initial splash screen because I feel the initial power on vib, and then another short vibe, followed by a long-ish pause, and a reboot (I assume), another power up vib, and another short vib. If I leave connected to USB during this sequence, The PC tries to install the MTP driver, but then fails when it reboots.
I've got to admit, I'm somewhat of a noob when it comes to this device. I don't understand it as well as some of the other handsets I've had. I'm sure I've made a mistake someplace and would greatly appreciate any help/insight you could offer.
Best Regards
My screen broken, but usb debug disabled
I have the same problems, but usb debug disabled, (xplay vivo 510w)
touch pad have key sounds, seems only display cracked.
is there any way to enable usb debugging?
Some possible way:
1. Engineering code to enable usb debugging
2. Any setting screen snaps to enable usb debugging (developers option)
3. reboot to recovery mode (dangerous to data? )
4. Flash ROM (unfamily & not prefer)
Thanks for any help~!
Black Screen but phone appears to function, need to enable debugging
My phone is broken. Screen cracked and black so I assume the digitizer is also broken. I'd like to access the phone through my laptop so I can view the several important apps I have on there. I don't think I have debugging enabled and I have followed this but find it difficult as I'm a novice (I can follow step by step instructions fine) and also tried to follow this. How do I enable debugging with no way of know what's going on on the phone?
Thanks in advance x
Related
My Moto Droid A855 has a dead screen, but I can see it on my desktop IF I can get USB Debugging mode enabled, in which its off at the moment.
My screen is DEAD, nothing can be seen, but the touch screen works. *I was able to unlock the phone*
I flashed stock 2.2 back onto my phone but now debugging mode is off, and my screen is dead, so I dont know how to re-enable it.
Does anyone know how to enable it without a screen?
come on! any replies ? my phone is dead too! i accidentally uninstalled launcherpro which replaced my LGHOME and now stuck at android booting screen with debugging mode off!
I was hoping there was a way to enable USB Debugging with a dead screen myself.....after a bad Rom flash I lost my touchscreen functionality.....Bad move when I Hard reset and found that I am stuck on the "Touch Android" screen to activate... with no conceivable way to "touch Android..."
You can use ADB while inside the recovery. Why are you trying to turn on debugging if I may ask?
Find someone with the same phone. Pull the battery on yours and reboot the other one. Power yours up. Now that both phones are on, navigate the good phone to where the setting is to debug. The same time you're doing that, do the same screen presses on the one with the bad screen. Only problem is you said you flashed stock back on. It's going to want to activate the phone and set up Gmail info. Good luck!
Guys,
In short, i need to enable usb debugging without screen (work in blind touch).
pls capture 4 screenshots of atrix 2 JB 4.1.2 leaked for:
1. dropped top bar (where the setting icon)
2. Where the developer setting is (scroll to bottom end)
3. position where is usb debugging (if possible, without scroll)
4. any message if usb debugging is enable
Long version:
My Atrix2 dropped from 1 meter and the screen cracked.
The screen is not showing anything now except some vertical lines.
i can see it shows some touches dot (i always enable show touches).
i managed to patterned unlock it and enabled tethering to get online after numerous of tries.
i need to access some info from the phone and all i need is to enable usb debugging to get some apps to work.
i dont have HDMI cable to connect it to TV.
i opt for not to restart it in fastboot to flash some ADB setting (if i failed, i may not get tethering to work again)
so, could some one pls help me with above 4 screenshots?
regards
Lesson learn: Always enable this setting
finally got this worked
Hi,
An update.
i managed to enable usb debugging by capturing some screenshots (press and hold power+volume down key).
i have photos sync to facebook enabled. Thus, i can see these images.
i resized these images at monitor and guessed where should i touch.
using following app, i can see the screen again.
http://droid-at-screen.ribomation.com/installation/
thanks for those who tried to help.
i'm lucky, isn't it?:laugh:
My nvidia Shields screen messed up after a week of upgrading to lolipop and I am trying to bring it back to 4.4.2. The screen wasn't really damaged in example Water damage or being bent/smashed. The screen only works when you put it in a specific angle or open the lid and stop it at this one specific place which changes randomly. I am wondering what i have to do to flash the stock rom so it is back to normal. What are the steps and what do i need.
Edit: The screen doesn't display anything but black light. Is it possible to enable USB Debugging this way. Im not sure though, if I can browse the internal files of the shield through my laptop does that mean USB Debugging is enabled? And i cant start my shield into bootloader mode. when i type ADB Devices it shows the device and then says unauthorized.
Update: I was able to install update 72 for it which is kitkat but the screen is still black and is not working is it a hardware malfunction or is it just dead the keys and things are still responsive. Is there any place I can send it in for repairs in the U.S. Or can I fix it myself.
A while back, My old Stylo 2 stopped working due to a very strange (I assume hardware-related) bug that made the phone constantly press the same spots over and over and over, and the screen was entirely unresponsive otherwise. Only those few spots ( 1. About 25% up the bottom right side, 2. The very top right corner, and most prominently 3. Just right of the multitasking button, within its 'hitbox'.) have any effects on the screen at all, and I cannot find places on the screen that are 'touchable' due to the multitasking button being hit over and over and it constantly switching me between apps.
More than anything, I just want to change my USB mode to file transfer to get my pictures off the phone, but even as easy as that is in Android 7 (pull down the top menu, select USB settings, change to file transfer right?) I can't even get the top menu down most of the time, let alone get to the USB settings. On the rare occasion that I do get all the way there, either the multitasking button starts acting up again or the screen stops responding to everything altogether, making the one thing I need to select un-selectable. Much to my dismay, it also seems that I have USB Debugging turned off (I honestly have no idea why or how this was turned off, as I use ADB frequently), so I can't even use ADB to get a screen control app to run. Are there any ways to either force USB Debugging to be on via console (Win8) or otherwise, or control the screen and disable touch without the need for a third-party app?
Yes
007manyo said:
A while back, My old Stylo 2 stopped working due to a very strange (I assume hardware-related) bug that made the phone constantly press the same spots over and over and over, and the screen was entirely unresponsive otherwise. Only those few spots ( 1. About 25% up the bottom right side, 2. The very top right corner, and most prominently 3. Just right of the multitasking button, within its 'hitbox'.) have any effects on the screen at all, and I cannot find places on the screen that are 'touchable' due to the multitasking button being hit over and over and it constantly switching me between apps.
More than anything, I just want to change my USB mode to file transfer to get my pictures off the phone, but even as easy as that is in Android 7 (pull down the top menu, select USB settings, change to file transfer right?) I can't even get the top menu down most of the time, let alone get to the USB settings. On the rare occasion that I do get all the way there, either the multitasking button starts acting up again or the screen stops responding to everything altogether, making the one thing I need to select un-selectable. Much to my dismay, it also seems that I have USB Debugging turned off (I honestly have no idea why or how this was turned off, as I use ADB frequently), so I can't even use ADB to get a screen control app to run. Are there any ways to either force USB Debugging to be on via console (Win8) or otherwise, or control the screen and disable touch without the need for a third-party app?
Click to expand...
Click to collapse
Yes, but I'd appreciate a thanks for the solution! I give and give ...
First, what model number is your Stylo? For instance I have the Cricket variety (H634). Once you figure that out check out my link below with particular attention paid to the "how to enable usb debugging via dialup" step. I just tried it with my Stylo (H634), works great. The link pertains to the LG G6 but it will work on your LG Stylo as well.
https://forum.xda-developers.com/tmobile-g6/how-to/frp-unlock-lg-g6-using-headphone-jack-t3616166
Or just try this ...
Dial *#546368#*_ _ _# (Field Test Mode). Enter your devices model number in the three blanks. Mine for instance would be *#546368#*634# (H634 being the Cricket model number). Go to SVC>LDB> Enable usb debugging
Happy USB'n!
I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.
Hi, provided that you have already
- enabled adb debugging;
- installed adb.
Now you have to
1. enter fastboot mode;
2. in adb type
Code:
fastboot erase recovery
then, reinstall recovery if you want to.
s.0105._j said:
I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.
Click to expand...
Click to collapse
How about rebooting to system using volume buttons?