Status: Touch still works but the screen is completely dead.
I dropped my Pixel 6 and there was a tiny crack on the upper left corner. After some weeks black spots started to slowly fade in, then over a couple days the entire screen became fully black and died.
Access: Phone is always unlocked; USB debugging authorization is enabled to my computer; I can access and control the phone through scrcpy.
During the ongoing dying process I backed up my data and tried to leave the phone as unlocked and accessible as I could.
Now I have a screen-less working Pixel 6. I can find some uses for it as it is a very capable device but many of them would require root access. That's where the issue comes up: I did not unlock its bootloader and rooted the device, it's a fully stock Pixel 6.
I have rooted other devices before but will avoid the hassle of trying to do it "in the dark" by going slow and guess-tapping where I should tap on the screen by following a video. There's a substantial risk of unexpected behavior getting in the way of completing the steps and totally losing access to the phone.
Is there any rooting method with minimal screen interaction available nowadays?
Also, how to proceed to grant USB debugging authorization after a factory reset in this case? Can it be done in fastboot or recovery mode?
If not I'll probably end up just fixing the screen and selling it, as I replaced it with another phone already
Replace the display. Don't compound the mess.
Always use a good case in the future. $aves time and data.
Related
I'm trying to help a friend of mine recover some vital files (that for whatever reason, have no other backups) on a LG Optimus F3 (vm720) phone that has had water damage.
The phone turns on, and boots up to the home screen. Problem is, we cannot interact with the screen at all. I supposed that the digitizer might have been damaged, so I bought a replacement, but found that to not work. Pulling out the motherboard revealed that the circuitry that is on the obverse side of where the digitizer plugs in to, is completely fried (See attached.) So, I believe that there is no way we will ever get a touch screen working on this phone again. So, are there other options?
The file we need to access is in app protected storage, for a particular application. I know, that's going to complicate things even moreso.
It appears this device does not have any HID support, so I cannot plug in a USB mouse like I can on my nexus 7.
So a few more ideas, that have their own associated questions:
Is there any low level tool that can dump the app protected memory? (I doubt it, that seems like a security bug)
If we could bring up the application itself, and interact with it, we can retrieve the file we need. But is there anyway to do that through usb/bluetooth/some other way? As far as I can tell, the only buttons that work are: HOME, volume up/down, and power.
Is there any professional services that can desolder the memory board and retrieve files that way? Price is not really a concern here unless it's astronomical.
I can get into the recovery mode, holding down the volume button while powering on, but I'm pretty sure if I were to flash a new ROM that had ADB enabled, it would wipe the app protected storage in the process. I don't think the phone is unlocked either, so that may not even possible at all.
The phone is non-rooted, and does not appear to have ADB turned on.. so this might be a lost cause. :crying:
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.
Hi all,
I dropped my OnePlus 6 and the screen is completely blank. The device seems to be working(vibrations and screen unlock lock sounds)
I am on Stock OOS with the latest update installed, completely unmodded(bootloader locked, no TWRP installed, no custom ROM)
I thought I had USB debugging enabled but it seems I have not as 'adb devices' says unauthorized.
I need to pull some data from the phone, what are my best options in this case?
I am ready to flash any TWRP/custom recovery to do this.
Biggest problem is screen is completely blank.
Thanks
Did you check whether the touchscreen still reacts to touch input? Although not the easiest solution but you might try to either authorize it by tapping on the screen multiple times or compare screenshots of where it should be to authorize it. The "Allow" button should be a little bit down further from the vertical center and a little bit to the right. You could just tap dozens of times unless you press "Cancel" on the left side.
You could do this with TWRP as well but there is a risk you tap on the wrong parts and maybe wipe your device accidentally.
Unfortunately, the OnePlus 6 doesn't support HDMI outputs and DisplayLink adapters require an app on the device to work.
Macusercom said:
Did you check whether the touchscreen still reacts to touch input. Although not the easiest solution but you might try to either authorize it by tapping on the screen multiple times or compare screenshots of where it should be to authorize it. The "Allow" button should be a little bit down further from the vertical center and a little bit to the right. You could just tap dozens of times unless you press "Cancel" on the left side.
You could do this with TWRP as well but there is a risk you tap on the wrong parts and maybe wipe your device accidentally.
Unfortunately, the OnePlus 6 doesn't support HDMI outputs and DisplayLink adapters require an app on the device to work.
Click to expand...
Click to collapse
@sigma_p As suggested by Macusercom, you have to somehow enable adb. After that you can try
Scrcpy tool to display your phone on your PC and retrieve your data.
https://github.com/Genymobile/scrcpy
Good luck?
I'm attempting to run a google pixel 3 without the physical screen. The phone will be used in remote management, so I have a remote management utility installed on the device as well.
Everything works flawlessly when the screen is installed - all apps and configurations work as they are intended. However, once the screen is removed, the phone doesn't work. On a pixel 3a I was able to attach just a ribbon cable for the screen without the actual screen, and when I pulled it up in airdroid, it would only display a condensed screen about 1/3 the height. On the Pixel 3 it doesn't load up at all.
I've connected the phone to my computer with USB debugging enabled. Without the screen it shows up in the devices list. But with the screen it doesn't even show up in the devices list. The only way to make the phone operational is to remove the battery cable then restart the phone. About 30% of the time it displays a message upon boot "This device failed to boot, do you want to factory reset", with an option of "yes" and "reboot" (selectable through the volume and power buttons).
Also of interesting note, if I power on the phone without the digitizer connected, I can use AirDroid just fine, but it won't register my clicks on the remote view screen. Which leads to believe the phone is registering the hardware of the screen and digitizer upon boot.
If I disconnect the digitizer and LCD after the phone is booted up, I can attach them both and it'll work. It's just when they're disconnected from the phone during the initial boot phase.
I tested this with a Galaxy S8 previously, and that phone worked just fine without the screen attached, and ran fine that way.
Does anyone have any ideas on how to "register" the hardware correctly? I'm not certain that's what's happening, but it appears to be something with the hardware not registering correctly, or something like that. What's odd, is that it doesn't work even with the ribbon cables attached. It requires the full screen to be connected to the ribbon cables.
I've searched up and down google, but there doesn't appear to be much information available on this, as it appears to be a very specific problem which not many people encounter.
Thanks!
Samsung Note 10, SM-970F
Magisk Rooted
Android 10, N970FXXS6DTK8
It's my GF's, and she uses a pattern unlock along with fingerprint. No new apps were installed or settings changed that she recalls.
Began as phone locking immediately after correct pattern was entered, but using fingerprint would unlock correctly.
With this immediate locking, the phone will by itself turn off the screen then turn it back on for two seconds as though the power button was pressed, then turns the screen off again.
When entering incorrect pattern, it says incorrect pattern and does nothing else.
She tried restarting the phone, which disabled the fingerprint unlock feature until the phone is successfully unlocked once.
Phone still locks immediately after entering correct pattern, and now she can't unlock it using fingerprint.
Now unable to unlock phone.
EDIT: If I repeatedly enter the correct pattern, after a random number of tries it will go to the 'starting phone' screen, but then will either restart by itself or sit there until I restart the phone. It really is random, once it took 7 tries, another time 20 tries. The phone doesn't show up on my windows PC as a mounted device during any of this.
USB debugging was not enabled, so I don't believe I can run any ADB commands. She didn't backup her phone and our focus is at least to get the photos off the camera, at which point doing a factory reset would be acceptable.
I've tried:
Entering a lot of bad patterns, trying to get to an option of unlocking with the google account associated with the phone, but the option never comes up.
Removing the phone case, only external item on the phone now is the stock screen protector.
Starting into recovery, clearing cache, repairing apps.
Starting into safe mode.
Booting in and out of root.
Letting the battery discharge completely to do a hard power cycle.
But no luck. The phone still locks immediately after entering the correct pattern. I haven't tried taking the phone's stock screen protector off, but will probably do that in case there is something wrong with the proximity sensor.
This is the international two SIM version of the Note 10, the only Note 10 variant which was rootable. I haven't worked on the phone for at least a year since it was rooted and setup.
SEU or a hardware failure. Either way when this happens your only option is to backdoor in. If it was a SEU after resetting you're good to go. If hardware it will likely reoccur... Even with a hardware failure many times nothing happens if no lock is set, you still have access. Setting a lock password introduces added failure modes.
SEU's are very rare but they do happen, randomly and just one bit of data is flipped. Interesting they cause no hardware damage. Higher altitudes elevate the risk as does exposure to man made high energy particles. That's one reason why spacecraft have 3 or more redundant computers. Apollo fights have logged half dozen or more SEU's per flight.
I never screen lock my N10+'s, double tap on/off. This is one reason why. Same with PC bios, no password is ever set. Once bitten, twice shy as the user is always the most likely person to get locked out... as I learned the hard way
@blackhawk, I hear you on getting burned with device security. And for any electronic device, secured or not, backups and redundancy are the only reliable difference between your device being useful and useless. It's been hard not to say any 'I told you so' about this, since I was telling her both to use a pin instead of pattern and to let me setup a regular backup. I don't know that a pin would have been different, but I think it would have since the fingerprint was working before the restart.
Do you have any resources you could point me to on how to backdoor into an android with a password/encryption? I know you can unlock a device using ADB, but I believe you need USB debugging enabled first and I don't know how to make that happen without first unlocking the phone.
mc_squirrel said:
@blackhawk, I hear you on getting burned with device security. And for any electronic device, secured or not, backups and redundancy are the only reliable difference between your device being useful and useless. It's been hard not to say any 'I told you so' about this, since I was telling her both to use a pin instead of pattern and to let me setup a regular backup. I don't know that a pin would have been different, but I think it would have since the fingerprint was working before the restart.
Do you have any resources you could point me to on how to backdoor into an android with a password/encryption? I know you can unlock a device using ADB, but I believe you need USB debugging enabled first and I don't know how to make that happen without first unlocking the phone.
Click to expand...
Click to collapse
Samsung repair can do it. A local shop or yourself, maybe. If there's an associated Samsung or Google account, start there. I never had to do that but the information isn't hard to find. The data will likely be lost though.
Meh, it's a very rude surprise.