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.
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!
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:
Hey guys,
just replaced my screen by myself and it isn't working. It boots and the screen lights up for a few seconds but thats it. So it seems like I ****ed up somewhere. :/
Now I've got some questions for you guys.
1. What could cause this error? Since it's already not working I don't mind taking it apart some more and trying to fix it.
2. Do you think if I send it to the support from OnePlus they will take a look at it?
3. The whole reason I did this was to get my data back. Is there any way to access the data on the phone without the touchscreen? I encrypted it using CynogenMod. USB-Debugging is enabled.
Thank you so much guys, I'd really appreciate some help. This **** is really tearing me down since it was a lot of work.
I did this on my own phone but Idk about OPO. If you use the power+voldown method to boot into recovery (yes ik nothing on screen) then connect a usb and see what happens
If you power it on, wait 5 mins then call it and if the phone rings you should be able to rule out the display and speakers and storage, obvs if the display is still not on at this point it is probably the display.
you can also adb from recovery and or fastboot so you should be able to see it in there if it is still working (make sure you change the phone for a decent amount of hours before you do any of these) If the display is dead its likely its been on for the last day and dead
Sorry for the late answer, really appreciate your help!
So if I connect the phone to the PC (tried it in recovery and in normal mode) windows detects the phone under "Devices" but sadly if I type in "adb devices" in cmd it doesn't detect the device.
But still, windows is detecting the phone so it seems to still function. I booted into recovery and I could use the touscreen and the lower buttons. I couldn't see anything but it was vibrating whenever I was using the touscreen. So it seems like only the display part is broken.
Can't call the phone since it's fully encrypted so I need to type in a password before booting anything (recovery, normal mode, ...)
I'll try to contact the vendor of the display and see what he has to say.
If anyone got any more tips I'd appreciate them. I'm a pretty big noob so I even appreciate "common sense" tips.
I know this may be a "common sense" thing to say, but double check your connections. Sometimes the connectors aren't made properly and a pin could be covered so you can try connecting and disconnecting several times to see if it clears up.
Since the touch screen was registering and vibrating, then it could be the backlight that's broken. Try holding a flashlight at an angle and see if you can make out anything on screen. If it's the backlight, then you can probably back up your data in case your phone does end up breaking.
reconnected everything multiple times and also tried the flashlight trick. sadly with both no luck
but something good:
adb recognizes my phone in "recovery"
bad news: no commands work, most likely because the phone is encrypted. if I enter a command nothing happens, it looks like its loading forever.
any ideas?
Hey!
I also had the same problem after I replaced OPO's screen about one year ago. The replacement screen was from ebay.
I could see the Cyanogen logo but after a few seconds the screen became black. Booting into recovery mode worked well.
On the video also ROM boots well but the screen stays black.
https://www.youtube.com/watch?v=VcWDCJIkPKQ
Eventually, the screen was defective and I returned it and bought new one.
Hello, I appologize if this is not the right place to post this in.
Now, My xperia Z3 has had a very hard time... with 3 bodge wires running thorugh it, and eventually a faulty screen (Sometimes it would turn off, sometimes half off, sometimes colors get inverted) which lead to it getting cracked by my thumb(!) and then to me accidentally shorting out the backlight....
When the screen cracked and was partially broken, i connected an otg mouse and removed the lock screen. I also made sure USB debugging was on. so i should be good and dandy right?
The computer recognizes it but nothing shows up. i know that it automatically sets itself to charge only...
I try to use visor, which works perfectly on my new phone, but it tells me that the phone doesnt have USB debugging on, I know for a fact that the phone is displaying a prompt telling me if I want to allow the computer, the RSI fingerprint and all.....
Phone is stock, no recovery. i have no experience with ADB commands but open for experimentation. all I want is the whatsapp media folder. Thank you!
I appologize for the bad original title. I hope someone can help me now?
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.