yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Kawalpreet Juneja:
Thank you for your amazing project!

I was able to control my tablet with broken touch. (Touch isn't available in whole market)

Can you please port your project to Android? :p

You know there's already a method out to send ADB from a Android device with another Android device. Yes, I can easily send ADB command from my Note 4 to my Tablet and they work.

I suppose, your project work of executing different ADB commands on different function. So it would be a Christmas gift for me if you can port your program for Android device so that I can put OTG in my Note 4, attach a USB cable, check 'Adb device' from terminal emulator and than use your program :p

Thanks for your help!

This was the thread from where I learned to send ADB commands from one Android to another: http://xdaforums.com/showthread.php?t=2586472&p=48862832
[Android Software/Hacking General [Developers Only]] CoLdIcE42:
Working for stock devices ?

Is this working for devices who are stock (no custom rom / recovery etc.) and dont have adb shell enabled or do I need to do something like a ROM flash via Odin ?

In step 3 you describe mounting it via twrp but since I dont have that installed would I be able to mount the necessary partitions via

ls -l /dev/block/platform/dw_mmc/by-name/

mount -t ext4 /dev/block/mmcblk0p10 /data

*http://android.stackexchange.com/questions/39623/android-adb-shell-recovery-mounting

and what are the necessary partitions since the description just says "system and data partitions" ?

thanks in advance
[Android Software/Hacking General [Developers Only]] rtorresz:
After a couple of days looking for a way to enable USB Debugging with a broken screen I finally came up with a way that could be useful for many in similar situations and for those that are not familiar with flashing, using shells and commands.

I explain the detailed process in this thread https://xdaforums.com/general/xda-assist/guide-recover-data-broken-screen-t3538114

Hope it helps.
[Android Software/Hacking General [Developers Only]] TurricanM3:
My Note 5 screen broke. I had to dissasemble the phone to get it booting again.

I tried the ADB method but it can't find any devices. The phone is complete stock. I have no idea how to enable ADB. I think thats the problem. Any ideas? I tried fixing this for about 4 hours now, no success. =(
[Android Software/Hacking General [Developers Only]] lucaam:
Try via recovery, if the stock one is not working, flash via Odin TWRP and than proceed. Just search how to get adb via recovery and it's done.
[Android Software/Hacking General [Developers Only]] TurricanM3:
I tried with stock, no device found. Don't know if i'm doing something wrong?

I cannot flash TWRP or Philz. Tried different odin versions, TWRP 2.8.7.1, 3.2.0.2 none worked. It always fails with "(write) operation failed". =(
[Android Software/Hacking General [Developers Only]] lucaam:
Can you tell me the model number of your phone?
[Android Software/Hacking General [Developers Only]] TurricanM3:
SM-N920C. Thank you.
[Android Software/Hacking General [Developers Only]] lucaam:
Can you try to flash the file at this link: https://dl.twrp.me/noblelte/twrp-3.0.2-2-noblelte.img.tar.html ?
[Android Software/Hacking General [Developers Only]] TurricanM3:
Thanks but i already tried. After flash it fails:
[Android Software/Hacking General [Developers Only]] lucaam:
Can you use an older version? Maybe 3.09 or 3.10.

Edit: try with changing the cable, use the original one and if it's the one that you're using, try with another one. Make sure that it is not a cable for recharge only.
[Android Software/Hacking General [Developers Only]] TurricanM3:
I tried three cables, different USB ports, five different Odin versions. Nothing helps.

I can flash my note 3 without a problem. Flashing the stock firmware works:
[Android Software/Hacking General [Developers Only]] ashyx:
Device OEM unlocked?
[Android Software/Hacking General [Developers Only]] sattech200:
I have a verizon note 4 that I dropped and the LCD no longer works, I suspect the digitizer isn't working either. I did the developer root hack on it when it first came out which I believe has TWRP 3.??? for recovery and still on 5.1.1 I think(I know I didn't take it to version 6.x.x.x).

When I connect the phone to the same two computers that have used in the past few months I can see my sd card and phone show up with all the files accessible. Also have fingerprint lock enabled but I know i'm successfully unlocking the phone.

For some reason I'm not able to get adb to show any devices. I was at one point able to get it to show up in recovery mode (I think that's what it said) and tried running the commands to turn on debugging but it didn't seem to help. I'm almost certain that debugging should be/have been on anyways.

I've also set up and used sidesync but for some reason that won't connect either(I may have disabled that with luckypatcher but don't remember for certain) Can anyone give advice on getting ADB to work so I can follow instructions in this post or even just get sidesync to fire up. Would be incredibly appreciated. Sucks really bad not being able to see the phone to see what's going on.
[Android Software/Hacking General [Developers Only]] elias_ck:
hello, i have a samsung s2 on Android 2.3.6;; the problem is i can't unlock screen. usb debugging is enabled and the device is online.

can reboot and recovery power off too but nothing if i can't unlock screen.

help me!
[Android Software/Hacking General [Developers Only]] Galane:
Try Vysor. With Google Chrome, go to vysor.io That will give you a mirror of your phone screen on your computer and you can operate the phone from the computer. Worked great on my broken Galaxy S4 when the display and digitizer were destroyed.
[Android Software/Hacking General [Developers Only]] elias_ck:
thank you, but i tried it before and it seems that the app only supports android 4.1+ and not 2.3.6

tried the mouse thing but screen is black and the otg have just one port so i can't see what's happening.

thanks
[Android Software/Hacking General [Developers Only]] Slicka70:
Hello guys, I'm hoping someone can help me with my Note 5. It has a broken display (doesnt light up, no touch or anything). The device does work, I can hear it turn on and do stuff.

Im trying to use this program but the issue I'm having is my USB debugging in NOT enabled. It is a completely stock Note 5. I downloaded Android SDK and tried to use ADB to connect to my device but it say no devices are connected.

When I use ADB shell, it says the same thing. Can someone please guide me through the process of plugging a phone in with a broken display (No touch capacity) and enable USB debugging via ADB? Let alone make the device actually discoverable? I was plugging it in using a data transfer cable in a 3.0 port on my computer.

Would an MHL OTG adapter work as well? That way I could plug it into a second display and use a mouse to move around.

I do not have Side Sync or anything installed on the device either.

Thank you for any assistance guys!
[Android Software/Hacking General [Developers Only]] milosunknown:
Hi, i tried this app on my S3 ( screen locked )but app dont work, when lunch app it also lunch some .rar ( droidatscreen or something ) archive. Clicked on Disable pattern lock, and lock pattern is disabled, now i just swipe to unlock. I dont know is debbuging on my phone enabled but i tried some android assistant which also require it to work, and it work but i can only back up messages and calls. I really need screen of phone on my PC. What to do? Please I need to pull viber conversations.

When enter text in box and press enter, get few seconds cmd screen from screenshot.

when click on "return" button in app i hear that my phone vibrate, like it is pressed on phone. but no screen What is wrong?

PS can someone put link for latest version win7? I curently use 0., cannot download latest, links dont work. Thanks
[Android Software/Hacking General [Developers Only]] the.devil.hacker:
You could flash cwm and then enable usb debugging by booting into cwm and then using adb.
[Android Software/Hacking General [Developers Only]] bomboem:
Does this also allow you to control it when in recovery? My phone is completely unresponsive on touchscreen. Adb is enabled. Could i boot into recovery (vol up+power) and connect it to my pc, and then use Android Control in recovery mode?
[Android Software/Hacking General [Developers Only]] _DoomD_:
i stuck in step 2. when i ran adb shell, i got an error "device (null) not found". I already installed drivers and booted to twrp recovery.

how can i fix it? someone please help! thank you
[Android Software/Hacking General [Developers Only]] tarantules:
I tryied the app in both Galaxy S4 (4.4.2) and Galaxy S7 (6.0.1) with debbuging enabled but the screen doesn't apear on my desktop although I can control the devices.

In Droid@screen window , under the Devices name,type,etc doesn't apear any of my devices.I pluged in usb cable many times and open and close the app to fix this problem with no luck.

Both my devices screens are ok but I want this program in future in case I broke my screen.If I can't see the screen on my desktop I can't control the phones blindly.

Any suggestions what I do wrong?
[Android Software/Hacking General [Developers Only]] guardianknox:
Great simple tool! You are a life saver!
[Android Software/Hacking General [Developers Only]] jstoner:
I have an S5+ with a non-working screen and need to boot it just once, so that I can unencrypt the SdCard that contains important data.

I m on stock 6.0.1.

USB debuging is not enabled...

Am I totally out of luck?
[Android Software/Hacking General [Developers Only]] sremark:
Thanks to these instructions and your amazing tool (seriously, thanks) I was able to successfully use my shattered-and-black Galaxy S4 (m919 running AOKP MM) for about a day and a half. But I eventually found Vysor and after using it for about two hours, my phone seems to have crashed (I think) and after booting back up neither one will display the screen: Vysor won't connect at all, and D@S in your tool is showing the device as offline.

Is there a way to check if I lost the ADB authorization? Are these commands harmful to run a second time if they're no longer needed? What diagnostic steps I should be taking?
[Android Software/Hacking General [Developers Only]] jojo313:
Control with less delay

I'd highly suggest you install the TeamViewer Host App first, and the add on that comes with it, so that you can control it with minimal delay from another computer. Works very well for me. Not all devices can be controlled though, only Screen mirror may work. I'd connect a mice over a OTG hub then.

---------- Post added at 05:00 PM ---------- Previous post was at 04:58 PM ----------

I know you can check that over ADB, but don't ask me how. It's described in the first paragraph of the thread. If that doesn't work something else is probably broken too.
[Android Software/Hacking General [Developers Only]] polarstar:
I had a nexus 4 with android os v5.1.1 having non-responsive touch, I would better say it touch is broken not display ( I can see the display). I have enabled usb debugging thanks to this forum post on how to do that and got cwm recovery installed & supersu and adb connected. Now I am trying to control my phone through a PC over usb connection with Android Control tool

but the problem is have to authorize adb with my computer so I can do work on it but I cannot accept the RSA key when the dialog pops up because my touch screen is broken.

I have tried secure ADB method posted here (unclickable pop-up) workaround:

adb push adbkey.pub /data/misc/adb/adb_keys

But it didn't work moreover I can see via adb shell the keys are copied onto the phone but still I get this authorize pop-up. Anyone got this working? Any workaround which is working here....

Note: I am not sure if my phone is properly rooted, everytime I boot into recovery and exit, it give error, fix root (yes/no). I click yes.

PS: Thanks for such a great thread to help all people with broken screen...:good:
[Android Software/Hacking General [Developers Only]] enklast:
No, you are not. You can unscrew the back of your phone and remove cords and unscrew the screw that is tighten the circuit board to your broken digitizer(display). Then do the same on a healthy phone of the same model(borrow a friends or buy a second s5+ yourself, they can't be too expensive nowadays if you buy a used one).

Then you can enable USB debugging and/or, for the ease of use, do a backup of your important files.

After you're done - reverse the unscrewing :) and your done :good:

Now you can use your broken phone in a various different ways using adb. If you left debugging enabled that is. And of course, if it's encrypted, remove the encryption before you do screw it back to the broken digitizer(wipe and flash and enable debugging again).

Haha I guess you wasn't "done" afterall. :cyclops:

Yet.. you are now :fingers-crossed:

Here are my thoughts on how to use your old phone.

One thing is for sure, you'll never run out of juice if you've got a phone model with a removable battery. Just smash the display and buy a second one. There. Two batteries and one is "always" 100% charged.

::my smartphones::

n9005 note3 (using as a portable wireless access point "pwap" :cowboy: )

n9005 note3 battery charger+fresh battery(in my car)

n9005 note3 battery charger+fresh battery(at my office)

n9005 note3 battery charger+fresh battery(Home)

i9505 S4 play around phone - though this will be my primary phone soon. I'm getting sick and tired of my clumsy note3

i9506 S4 battery charger+fresh battery(in my Home)

And many more

Cheers! :cool:

enklast
[Android Software/Hacking General [Developers Only]] jstoner:
Thank you for the response!

I went to a shop and borrowed a functional screen. But then, somehow, the power button decided to stop functioning. I m certain it was working before, because the phone would vibrate after a long press of the power button...
[Android Software/Hacking General [Developers Only]] enklast:
Oh! I guess you did remove your board from the functional screen and then assembled the original board to the functional screen you borrowed to check if it's working as it should. If you haven't, please do so.

I can think of three reasons why you have a 'no go' when you press the power button.

1. All cables should be connected to the board. This is obvious, but re-assemble the old board to be sure that you are connecting all cables. Be careful and either use an ESD bracelet or keep touching an grounding/earthing point to remove any static charge your body might build up. I am touching my heating elements which should be connected to the water line and this will be a good grounding point. A zink of metal finish is also equally useful for grounding yourself.

Now, even though it sounds like I'm over exaggerate this. I'm for one, am just touching grounding point every once in a while, I never use an ESD bracelet (even though I'd like to, but I don't own one). Nevertheless, I have never destroyed an electric component by arcing it with static voltage. At least not one that I'm aware of. :angel:

2. Sorry about the 'static' wall.

3. Check the voltage in the battery. It should have AT LEAST the voltage that is stated on the battery. If you have lower voltage the battery is more likely to be drained. As long as there's voltage - it should charge when you connect a charger. And you should in a matter of seconds of charging measure a higher voltage, this indicates that there's nothing wrong with your battery. If this borrowed phone has been lying around and the owner did not connect the phone to a charger every third month or so. There's a chance that the battery won't build up a charge even though you try to charge it. A battery(li-po, li-ion. etc.) should never, under no circumstances be drained unless you just want a piece of counterweight.

4. Again sorry for the walls.

5. When you remove your back of the phone. You see the battery right? When you then remove all those screws you remove another "back" of your phone, right? If so. You need to assemble this back, it's not enough to just put the battery in and leave the back unassembled. That back is one piece of the circuit, without it, you'll have an open circuit. No phun in an open circuit. :crying:

6. Hmmm, I'm sure I forgot something to check.......

Yeah. Of course. Check the bloody power button. It's just a piece of plastic acting as a distance to the REAL power button on the display/digitizer board. Remove this plastic rubbish to be sure it is pressing the real button. There's a big chance it isn't lining up correctly to be able to press the real button down.

Remove it and press with a plastic whatever (no sharp harpoon).

I will take a few pictures of my phones, so you get what I mean. But first I need to be with my spouse. She is staring hatefully at me now :D

Cheers

/enklast
[Android Software/Hacking General [Developers Only]] jstoner:
Thank you enklast

I have followed all instructions as in this guide.

However, in regard to step 6, I really need to do something about the power button. I know the phone is not dead. When we put on the test screen, although the power button didn't work, when plugging in the charger, the charge icon shows up. Also tested that battery power output is good.
[Android Software/Hacking General [Developers Only]] enklast:
Sorry for late update... Here's what I meant with the plastic button that's the exterior button that one press to power on/off the phone.

First picture is the exterior plastic power button itself, removed from the phone.

Second picture illustrate the "real" button that trigger power on/off. This is the button I suggest you Press with a plastic tool.

Third image is the same as second but maybe a better picture?

PS. The first picture was accidentally uploaded two times. Unable to remove it by xda app gui.

Hope that helps

Cheers
[Android Software/Hacking General [Developers Only]] opkaybeatz:
please is there a way i can use the touchscreen directly on the phone that appears on the pc
[Android Software/Hacking General [Developers Only]] jdl512:
Help Enabling debugging

Please clarify the instructions in the OP for enabling USB debugging. The shell commands need to be ran from recovery?

I have a stock Verizon droid turbo so it is locked and debugging is not enabled. My laptop explorer sees the phone by model ID, but no files. ADB will also see the device. I have a second turbo with custom rom and tested my ADB install with it, which is good. That phone can be seen by ADB and Fastboot so my ADB install seems fine on the laptop as far as drivers go. I cannot see the screen on the broken Turbo, but touch seems to be working. I can turn power off with the touch screen. I have tried many times to blindly get into bootloader then into recovery from there using power and vol combos, but the shell command tells me the $ADB VENDOR KEY is no good when I try to run the shell command from where I think is the stock recovery screen. So, all I can do is see the device with the "ADB Devices" command.

Any help is appreciated as I have spent hours trying to make this work without seeing the screen.
[Android Software/Hacking General [Developers Only]] Hypexed:
Hi. WRT the above, does that just append to the prop file? Cause I'm wondering what would happen if those variables already exist? Unless build.prop has a custom handler in the system wouldn't this create duplicates? In the case they already existed.
[Android Software/Hacking General [Developers Only]] Cainnub:
What did u use to do that back up?

---------- Post added at 05:17 PM ---------- Previous post was at 04:35 PM ----------

What did u use for your iPhone?
[Android Software/Hacking General [Developers Only]] LeoTheRomRasta:
PIXL XL

Should this work with google pixl xl
[Android Software/Hacking General [Developers Only]] kunalvirk:
But is it possible without USB Debugging..??
[Android Software/Hacking General [Developers Only]] nberga:
Hi,

Cannot connect my phone, it's an Elephone S3, i open the droid@screen but there's no devices there.

I have the screen broken and no touch pad function.
[Android Software/Hacking General [Developers Only]] Galane:
Can't get hooked up to my broken phone with VYSOR now. It requires hitting the OK on the USB debugging authorization on the phone. To get this or any other software that requires hitting that OK, you have to use one *before* breaking the screen so that the phone stores the authorization for the computer.

So for extra insurance, get VYSOR and use it *before* your phone gets broken. Use it on *all* your computers. If you do anything to revoke authorizations on your phone, connect again to all your computers. Same for if you have to reinstall the OS on a computer. Maintain that lifeline to get your stuff off the phone.

If you don't have the same computer, reinstall its OS, revoke USB debugging authorization on the phone then break the screen - you're SOL. Samsung Kies can pull everything from a Samsung phone *without USB debugging* so why can't some free, open source, 3rd party software? Unlike Kies, Samsung Smart Switch *will* move many apps and for many of them their data, from another Android phone to a Samsung Android phone. It can also port data like contacts, logs, text messages, etc from iPhone and others to a Samsung phone. But still useless if your screen is broken.
[Android Software/Hacking General [Developers Only]] enklast:
I've been playing around with VYSOR, and on the surface this seems like the most complete and easiest way to control your phone without any need of screen interaction.

But this is not an option, at least if you are on a Samsung Galaxy note 3 (n9005) and the screen is dead/black).

Background: having 3 dead note 3's and one alive I'm able to setup the broken phone's if I'd transfer the motherboard to the working digitizer. So, on three different roms, with vysor setup and it works like a charm. However soon as I return the motherboard back to the broken digitizer(screen). And boot the phone, vysor launches as it should and I can see the screen as I could before. But the viewing resolution is about 64x64 or so. The Rom seem like it cannot adapt to the crazy low resolution and this causing it to only mirror one of the screens top corner. I can, however interact with what is displayed(mirrored) for me. Though, this render the phone quite useless.

This is NOT a VYSOR-bug.

This is also happening when using teamviewer. Anyone knows how to trick the phone into believing that it has got a screen connected, with a normal resolution to follow?

This is NOT a ROM specific bug.

Tested three different roms in three different phone's.

This is NOT a faulty setup of vysor.

Mirroring is fine until it's mirrored from a dead display. (VYSOR and TEAMVIEWER)

Debugging > simulate external display.

won't do any good

Vysor settings > change resolution.

doesn't do anything when mirroring from a dead display

Someone else have had this error and got a work around?

cheers

e.
[Android Software/Hacking General [Developers Only]] Srilal:
i have a display broken Samsung S4 (SHV-E330). will this work? its has stock Recovery so how can i enable USB Debugging?
[Android Software/Hacking General [Developers Only]] Hypexed:
Actually it's not full useless. I broke a Samsung G360G screen and damaged display controller so no hope to get another screen working without SMD skills and parts I don't have. That's also a rare unsupported phone. Apart from CF-AutoRoot nothing else is ported to it. Anyway I logged into Play store from my laptop. From there I was able to install Switch remotely onto the phone. I installed Switch to Windows as well. I opened up Switch on the laptop. I connected my phone over USB. It was able to connect to it and get data off. Oh yes, USB debugging was certainly not enabled. This would have been a done deal, except certain app data like game progress wasn't extracted nor passwords and what ever else. But it is a good start. It can be of help. :)