My phone screen turned green and it's been 5-6 months... I want to back up and recover some important data, so that's why I want to keep it. The thing is the screen is completely green without showing anything. I did a quick research, the nearest problem I got is from this youtube channel: Screen Turns Green Suddenly? Here's How to Fix Android phone Green Screen Issues . But mine's worse than this problem. The youtuber's phone is completely green, but at least, somehow it manages to show icons and for some minutes seemed back to normal and could go to the setting or after restarting, the Samsung brand icon showing up. However mine's just green. Perhaps you might suggest buy a new one (but I need the data). I'm just upset when I have replaced the LCD twice, and this time, it only lasts for 1 or 2 months after replacing and the green screen reappears. I even lost money twice more than the original price of the phone (darn!, Sorry). I don't even know if my screen is showing the home page (on mode), or perhaps even it's on the off mode. I couldn't tell which is which... So how to resolve this problem? Replacing the LCD would cost 3/4 of a similar price to the phone when it's sold, but if that's gonna work, I'll do it. I care about my data... So could someone convince me safely that if I replace the LCD it would work again as usual? The condition of my phone while it's charged: It's Samsung Galaxy A73 5G, by the way, and yes, I posed a question before about 3 green lines (which was nothing serious compared to this one) and since then I have replaced the LCD but the second replacement (my first replacement was few months ago), it's broken again. I'm frustrated and not even sure whether the problem is on the screen or something about the motherboard or whatever it's called... Any good advice would really help.

So my Galaxy A51 finally gave up the ghost by refusing to turn on its screen anymore. I still got the (blind) use of the touch screen, as well as input via USB Keyboard/Mouse. Using that, I could, by blindly unlocking and authorizing USB Debugging, access the screen content via **scrcpy** and copy over all data files that are accessible via USB connection. HDMI over USB-C is not supported though. As a result, I already got at my personal data and chat apps. All chats, photos and contacts are safe. I can input any settings, commands and actions that are possible to input via the scrcpy adb connection. The last remaining problem is this: The scrcpy connection goes black as soon as what I assume are DRM/extra security protected apps are opened. This includes important 2FA Apps like Google Authenticator as well as all proprietary banking 2FA apps. I'd really like to get into them to backup their codes and re-setup them on my new phone. Any path to doing that?

Sadly, I have dropped my smartphone and the screen no longer properly responds to inputs (it seems to not react in certain regions and think other regions are always pressed). As such, I cannot unlock it and am struggling to backup the data from it. How can I backup a smartphone with a broken screen? The model is a Nokia C300 TA-1515. **Note**: There are a few resources online concerning backups, but almost *all* assume you are able to unlock the device from its screen. I use GNU/Linux and am fairly familiar with the command line but was uncertain if a tool like adb would assist in a situation like this. Thank you all so much for any help! I immensely appreciate it.

About a month ago, I dropped my Samsung Galaxy S21 Ultra about 10 cm above my sink, and it got a small dead pixel on the left edge near the top. The problem is that it has affected the whole area below the impact point, doing so that every time the light intensity gets too bright, for example, if I am accessing a white webpage with light intensity of 100%, the area below the dead pixel just turns black. But if I have the light intensity set to 10%, I can see the screen but the bottom area is still flickering. I thought I could live with it, but I can't use my phone outside if I can only have the light intensity on 10%. I know it's something to do with the screen, but I think it's weird that the top works completely fine, and everywhere beneath the impact point is broken. So I hope that it could be a loose cable or something and not the whole screen that has been destroyed due to a small dead pixel. My question is, do you think it could be a loose cable or another thing I could fix without buying a new screen that costs 270€? Because if that's the case, I think I will just hold on for another month and switch to a new phone.

I have an LG G2. The bottom 50% of the screen doesn't respond to touch. Right now, I am running BlissPop ROM, which allows 180-degree screen rotation, and that is currently my workaround. But I'd like to use the top half of the display only. What I'd like to do is use the top 50% of the screen, but rotated so that the 1080 pixel-wide side is oriented up/down, and have a shrunken phone in that top 50%. |What is going on right now|What I'd like to do| |-|-| ||| I've tried using adb shell wm overscan 0,0,0,960 but it breaks most apps (probably due to the weird resolution) How to get Android to assume my screen is rotated 90 degrees and only spans the top half? I'd prefer if the resolution was 4:3 so I could use more of my screen, but if 16:9 keeps better compatibility with apps, I will do that.

So, I'm making a little batch script to be able to automate the whole process of flashing new roms for my Galaxy S6. Since its screen is broke, I have to do everithing manually from the adb shell, and since i'm having so many troubles with all the roms, I decided to make a little script to make my life easier. This is what I got so far: @echo off setlocal enabledelayedexpansion REM Factory settings echo Formatting to Factory Defaults adb reboot recovery adb wait-for-usb-recovery adb shell twrp wipe cache adb shell twrp wipe dalvik adb shell twrp wipe data adb shell umount /sdcard adb shell umount /sdcard adb shell umount /data adb shell umount /data adb shell mke2fs -t ext4 /dev/block/platform/15570000.ufs/by-name/USERDATA adb shell reboot recovery adb wait-for-usb-recovery REM Rom Flashing Section set argCount=0 for %%x in (%*) do ( set /A argCount+=1 set "argVec[!argCount!]=%%~x" ) echo Wiping /system adb shell twrp wipe /system for /L %%i in (1,1,%argCount%) do ( adb wait-for-usb-recovery echo Flashing "!argVec[%%i]!" adb shell twrp sideload adb wait-for-usb-sideload adb sideload "!argVec[%%i]!" echo "!argVec[%%i]!" flashed echo. ) REM Debug enable adb wait-for-usb-recovery echo Enabling USB Debugging adb shell mount system adb shell "echo '' >> /system/system/build.prop" adb shell "echo '# Enable ADB' >> /system/system/build.prop" adb shell "echo 'persist.service.adb.enable=1' >> /system/system/build.prop" adb shell "echo 'persist.service.debuggable=1' >> /system/system/build.prop" adb shell "echo 'persist.sys.usb.config=mtp,adb' >> /system/system/build.prop" adb push C:\Users\ffpp2\.android\adbkey.pub /data/misc/adb/adb_keys REM Booting system echo Rebooting into system... adb shell reboot echo waiting for phone to boot up adb wait-for-usb-device echo Launch scrcpy "D:\Users\ffpp2\Documents\Celus\zeroflte\scrcpy-win64-v1.25\scrcpy.exe" Now, I want to be able to evaluate every adb shell ... return code, so if anything happens mid way I can stop execution and I can get to fix what didn't work. I havent been able to find anything regarding if adb shell forwards error codes back to the windows command prompt. Take a look at this: D:\Users\ffpp2\Documents\Celus\zeroflte>adb shell mount /system mount: mounting /dev/block/sda15 on /system failed: Device or resource busy D:\Users\ffpp2\Documents\Celus\zeroflte>echo %errorlevel% 0 D:\Users\ffpp2\Documents\Celus\zeroflte>adb shell ~ # mount /system mount: mounting /dev/block/sda15 on /system failed: Device or resource busy ~ # echo $? 255 ~ # exit D:\Users\ffpp2\Documents\Celus\zeroflte>adb shell cat asd cat: can't open 'asd': No such file or directory D:\Users\ffpp2\Documents\Celus\zeroflte>echo %errorlevel% 0 D:\Users\ffpp2\Documents\Celus\zeroflte>adb shell ~ # cat asd cat: can't open 'asd': No such file or directory ~ # echo $? 1 ~ # As you can see, no error code was returned. And, in theory, it should be returned, since I didnt used the -x argument: Android Debug Bridge version 1.0.41 Version 34.0.0-9570255 Installed as C:\Program Files (x86)\ADB and Fastboot++\adb.exe ... shell: shell [-e ESCAPE] [-n] [-Tt] [-x] [COMMAND...] run remote shell command (interactive shell if no command given) -e: choose escape character, or "none"; default '~' -n: don't read from stdin -T: disable pty allocation -t: allocate a pty if on a tty (-tt: force pty allocation) -x: disable remote exit codes and stdout/stderr separation emu COMMAND run emulator console command ... Has TWRP anything to do with this?

My phone screen broke. I can't see anything, and the touch screen doesn't work. I can't buy a new phone, so I'm not looking into backing up my data. I want to be able to use it from my pc. I have a Motorola Moto G2 running LineageOS 14.1 and TWRP custom recovery. Until now, I have been able to use my phone from my PC using [Vysor](https://vysor.io) , because I previously had USB debugging activated. However, **I accidentally deactivated it and now I'm stuck out**. I can access via ADB through recovery and **already have investigated how to activate USB debugging** again from the shell using these sources: - https://android.stackexchange.com/questions/112040/how-to-enable-usb-debugging-in-android-if-forgotten-pattern-for-screen-unlock - https://android.stackexchange.com/questions/120394/can-i-enable-usb-debugging-using-adb - https://android.stackexchange.com/questions/12834/broken-screen-while-debug-mode-was-disabled-how-can-i-re-enable-adb - [Enable USB debugging through Clockworkmod with adb ](https://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb/13332721#13332721) - https://android.stackexchange.com/questions/55674/how-can-i-enable-adbd-during-boot-on-cyanogenmod - [Manually enable adb debugging from recovery](https://forum.xda-developers.com/showthread.php?t=2335799) - [How to authorize adb service from boot](https://groups.google.com/forum/#!topic/mozilla.dev.b2g/epQ6qhIFZ50) But **none of these solutions have worked for me.** Here's a brief summary of everything I've tried: - I've set the content of /data/property/persist.sys.usb.config to mtp,adb - I've edited /data/system/users/0/settings_global.xml, setting adb_enabled, verifier_verify_adb_installs and development_settings_enabled to 1 - I've added these lines to /system/build.prop: `persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb` - I've used the following setprop commands: `setprop persist.service.adb.enable 1 setprop persist.service.debuggable 1 setprop persist.sys.usb.config mtp,adb` But when I reboot, I still can't see my device when I run adb devices Not only that, but then **everytime I reboot to TWRP recovery again, I notice that some changes are reversed:** - /data/property/persist.sys.usb.config content only says adb - /data/system/users/0/settings_global.xml remains almost intact but adb_enabled is back to 0 again - When I run getprop to all of the properties I've set before using setprop, it returns an empty string (which makes me suspect that the changes I've been making to /system/build.prop are being completely ignored) **It's as if everytime the phone boots, the system loads some default configuration and reverses some of the changes I've made and USB debugging remains deactivated**. Am I missing something? I really not know what else to do.

## Situation I have an old phone, it's been replaced, but it still has some photos on I want to recover. From the symptoms I presume it must be a hardware fault, and I am wondering what options are available to me. I have a friend who works as an embedded engineer who is willing to help me try get the photos off of it. The current possibilities they could think of are: - Buy a cheap new screen to connect to the phone to see if we can get the UI back - Attempt to connect via the JTAG pins and execute a script to extract the data Are there other options? Or should we go with one of these? ## More information If it's relevant, the phone is a Pixel XL. A possible silver lining is I was running LineageOS, so I unlocked the bootloader and was never able to re-lock it. The symptoms at the time of death were: - Phone would randomly restart every few weeks - This got more and more frequent - One day the phone restarted and never turned back on - If I held the power button to turn it back on, the phone vibrated yet the screen never turned on - When plugged in the red light didn't appear even though it was drawing Watts - Forced resets (holding power and volume down button for 30+ seconds) sometimes caused a vibration but nothing ever appeared - Plugging it into a laptop resulted in no devices being visible to the laptop (presumably I needed to enable file transfer via the UI which wasn't possible) It's since sat in a box for 2 years and now there is no vibration whatsoever, but it does still draw current when charging. (I contacted multiple places about data recovery in the last couple of years but never received a response.)

I had a Samsung Galaxy S8, and I dropped it. By the following day, my entire screen was black. However, just 5 minutes prior, I had turned my Bluetooth on paired and connected a brand new pair of JBL tune 512 BT earbuds. I found out online how to reset them, but first, they need to be unpaired from any other phones. I've tried pulling the screen down, but I can only see an eighth of an inch. I can't turn the Bluetooth off. I can't power it off because anytime I try to power it off, I have to hit okay on the screen before it powers off, which I can't do with a black screen. Any suggestions?

My Samsung Galaxy J6 (J600G/DS) touchscreen isn't responding this morning. I opened just one app and wanted to slide it off and then it just stopped moving for some reason. So, I just turned it off and now it still hasn't responded. I've charged it also and it remaining full 100%. I can't open or do anything really because I can't slide it open. I can't put it on power off because the touchscreen isn't responding. I've tried pressing the power button with the volume button but it didn't work. Please help.

I have a SenlinTech Android Tablet (pad6_ee). I factory reset the thing and now my touchscreen is not responding at all, and I can't get past this screen to even attempt a fix. I have searched high and low trying to figure out how to fix it. I have a phone and laptop as well. I've also been trying to 'update from adb' but I can't seem to work that out either. The Senlin site is useless and this tab just doesn't seem to exist. It's windiws 14. I thought of resetting again and I got this error. Is there a fix I can do using a phone/laptop?

I have a Poco X3 Pro with a broken screen (the screen doesn’t turn on, it’s just dimly lit in Fastboot and during boot) due to water damage, and I need to control it from my PC using scrcpy . The phone is unrooted, and I can’t access the UI due to the broken display. I can temporarily install TWRP (even though it reverts after reboot). I want to use scrcpy to control the phone, but to do so, I need to enable USB debugging (Security Settings), which I can’t do without access to the screen Here’s what I can do: - The phone can enter Fastboot mode, and I can temporarily install TWRP. - USB Debugging is already enabled. - USB Debugging (Security Settings) is disabled. (Xiaomi devices require this toggled on ) to be able to use scrcpy - I have no access to the screen or UI. Before making any changes, I’d like to back up all my important data (apps, system data, personal files) or do a full-phone backup as a precaution, in case the process is risky or anything goes wrong during the procedure.

My friend isn't tech-savvy and asked me to save his Android tablet. However, the problem is - the screen works but no longer registers touch, so in the current state, no internal setup can be performed with no input. Now we are both wondering how to set up the tablet for running e.g. calendar. We need to somehow connect an external device for input which requires no setup from the tablet. I know there is Anydesk for remote control of a device, but it needs to be installed on both to work. Not to mention Android isn't designed for keyboard nor mouse input. Is it possible to force a mouse connection on the tablet? Is connection to the mouse through the computer feasible? Any advice?

So, I've got a phone here with no screen, and adb isn't enabled (I'm not even sure if developer settings are enabled, to be honest) I'm looking to extract whatever data I can off of it at the least, and at the most, control the phone remotely from my computer. I've never done this type of thing without the use of adb, so any help would be greatly appreciated!

I've tried everything I could find on the internet (mostly on *StackOverflow*). These I've already tried without result: 1. [*Page not found - Stack Overflow*](https://stackoverflow.com/questions/51082608/is-it-possible-to-authorize-adb-on-my-android-phone-with-a-broken-screen) 2. [shell - How to solve ADB device unauthorized in Android ADB host device? - Stack Overflow](https://stackoverflow.com/questions/26213954/how-to-solve-adb-device-unauthorized-in-android-adb-host-device) 3. [android - running adb devices showing unauthorized device? - Stack Overflow](https://stackoverflow.com/questions/25236960/running-adb-devices-showing-unauthorized-device) **Both screen AND touch are broken so I can't see nor touch a thing.** (So the OTG mouse option can't be used in my case.) The device is a *Huawei Ascend P7 L10, Lollipop 5.1.1.* - It's rooted. - It has TWRP recovery. - USB Debugging is enabled. - I'm using the latest ADB version, updated from Android Studio. I entered recovery mode, done adb push adbkey.pub /data/misc/adb/adb_keys and rebooted, after reboot adb keeps saying devices isn't authorized. I entered recovery checked if the file copied on the device was still the same as the one in the *.android* folder, and it was the same key. If anybody has any idea I'm all ears. Thanks in advance.

I have an Android phone with a broken screen. When I try and unlock it, while attached to my monitor via USB-C, all I can see is a lock icon floating around. I roughly guess where the dots are for the pattern and usually I can get it unlocked. Now, there are also some apps that I use that ask me to enter a password. Again, the screen goes black and I cannot see what I am doing. I've tried entering the password with the keyboard but no luck. I imagine this is some type of security feature doing this. Is there a setting to turn that off so I can see these screens?

I have a Samsung Galaxy J5 2017 with a broken screen, the screen is black and unresponsive. I found an app that I can use to mirror my phone screen to my PC so I can recover my Google Authenticator codes for my accounts which requires USB debugging to be enabled. Unfortunately I don't have USB debugging enabled on this phone, I found a few ways to enable USB debugging but none of them work for me. I can't use an external keyboard / mouse or go into recovery mode because the screen is black. I also can't use the screenshotting method because the screen is unresponsive. Is there a way to enable USB debugging using my PC?

I have a Moto X (Lollipop 5.1) whose display is broken. I have some files and photos in it which are very important. Unfortunately, I didn't use Dropbox or Google Drive to backup my content. I tried the following ways to recover the data but with no help: - [Control a device with a broken screen](http://forum.xda-developers.com/showthread.php?t=2786395) but unfortunately USB debugging is not enabled. Also, the pc doesn't recoganize the device (I figured that out with lsusb on my linux). - The phone doesn't have any apps like AirDroid installed to allow it to be accessed remotely on a PC. The phone works and I was able to locate and ring it via Android Device Manager. Is there a way to get access to the phone's data in my current situation?

I'm here today because of a teeny tiny problem with my phone. As it got hotter and hotter (external factors, high usage, high temperatures on charging), the screen glue decided to abandon me, leaving my screen dangling with no protection. The flex cable connecting the mobo and the screen teared apart, hence leaving me with a phone without any visual input. I've decided to not repair it as it's not worth the cost, but I need to access the data from inside the phone. I already know that with ADB it should be pretty easy to access those. The only problem? When I usually connect the phone to my PC, it shows the pop-up window to select the connection mode (only charging, Android Auto, data transfer, etc) and I need to select the data transfer mode in order to activate ADB. Do you have a way for me to access ADB with only a cable and a PC or must I try to solder back the flex cable / change the screen? Thanks for reading and for the help!

Vertical Green Lines: I've been collecting information from any resources as to how to fix those sudden green lines (there's another colour) on the screen that appeared out of nowhere. My phone is Samsung Galaxy A73 5G with android 14. Previously, it was android 12 when I bought it 4 months ago. It has never been dropped on a hard surface nor fell in the water. It even has no scratches. Some resources say it was because overheating that caused the green lines. I refuse to believe that. My old J7+ with the same brand never got any issue such as those green lines. I even often used it to play a game with a charger plugged in! If it were because of the overheating, then why was my old phone just fine? The other possibility is water. They say that the water could cause the green lines. I don't believe it either. According to this site , samsung A73 is water and dust resistant. I barely let my phone get water on it. I even never dropped my phone in the water. Even my old samsung without water resistant has ever been dropped in the water several times never got green lines! Some sites suggest it was because of the update. So, I'm preparing to downgrade my software from 14 to 13 with the hope that it will remove the green lines. But, of course I need some advice if this were a right thing to do, were it? I'm even starting to think that all those vertical green lines are just marketing strategy from Samsung to get more money by forcing the users to replace their LCD! That was evil!