I have a rooted/unlocked Photon Q with a partially functional display. The initial warning "Your phone has been unlocked" comes up fine. When I put it in bootloader mode, the fast boot messages appear fine. On regular boot the screen is either black or on one occasion showed some randomly scattered pixels. Booting into recovery (TWRP) results in a black screen. In all cases adb/fastboot are able to properly communicate with the phone. I was able to test if the screen was on or off using adb commands, as well as turn it on/off. The commands did register and showed the screen correctly or or off though this was not reflected in the visual screen output. When toggling on/off state I saw some activity - it almost looked like the brightness was set to 0, but I verified that with adb as well and even set it to 100 to be sure with no change in the display behavior.
So my suspect is the graphics card, but it must be just some video modes given that fastboot diagnostic and initial warning can be displayed. I am about to replace the motherboard, but I am just curious about what exactly is wrong (and if by chance it can be fixed without replacing the motherboard). I also looked around for documentation on the video modes of the Photon Q graphics adapter, but could not find anything relevant - if somebody could point me to the right source this would be appreciated.
I would not mind writing some C code to poke around on the low level, but it would be nice to start from some sample code rather than from scratch.
Related
My Vibrant fell this morning face down flat on the screen, I picked it up and was happy to see that the gorilla screen was perfect, not a scratch on it, but that turned to disappointment when I went to turn on the phone and saw a purple hue across my screen, but things were still visible but barely.
About 30 mins later, the screen is now not visible at all except for a small line near the bottom that is very bright (almost seems like the entire image of the screen is squished into this thin line).
Here is the problem. I need some of the stuff that is on my phone but have a pattern lock-screen on it and I cannot see the screen to put the pattern in, I have tried numerous times and get nothing. I was thinking if I can get it hooked up to a PC I can copy everything off. Is there some other way to maybe boot the phone in a mode to connect to a PC?
Other alternative is to buy just a screen and replace it with my broken one. Does anyone know where I can buy just a screen? I don't want to spend too much because I am a couple weeks away from getting the new Galaxy S II when it releases on T-Mobile Oct. 12th, I don't care to completely fix this Vibrant, I just want my data/apps off of it.
Thanks for any help.
mgiusto
I just need instructions on how to boot into ADB mode without being able to see the screen at all. Can someone please help?
Thanks!
Assuming your phone is rooted and have USB debugging enabled you can always try using "Droid Explorer" for windows. Within this program you can copy files without having to mount your sd card...you just need to have USB debugging enabled though otherwise it will not work. You can also access an emulator within this program called android screencast which will basically emulate your phone allowing you to navigate through your phone with ease. Your best option will be to download this Droid Explorer program for windows or you can also try adb but I don't know the commands so sorry.
From time to time, my Infuse 4G for various reasons seems to stall on a black screen but this isn't about that phone in particular as others do it too.
When stuck on a black screen or frozen screen image, I can connect via adb get access that way. I can look around, su and reboot it works just fine. I wish I knew what in particular was failing in order to restart it's process and if it were the VM it wouldn't really matter since a reboot would accomplish the same thing. More information from the OS is always better, in my opinion, though.
Point of this thread: When the screen goes black, I am not sure what is actually being displayed or what is doing the displaying, be it an app (if full screen), the whole VM or neither of these. If it is the whole VM or just the black/void background to whatever simple graphics server runs for android, could it be possible to insert simple wallpaper-like error-message images to the root of both the simple non-X graphics server AND to the VM's root so that when nothing is being shown it will be seen?
I don't know for sure, but I imagine if the VM dies it gets restarted immediately. If it gets stuck is another thing...
If this were to work, it wouldn't accomplish much but let the end user of the rooted phone know a little more about what state the phone is in and what needs to be eviscerated from the malfunctioning device. To those more knowledgeable about the Android system setup itself, can this be technically done?
Your thoughts?
Thanks.
My partner recently dropped her SGS3 from about 2 feet onto the floor. It was in a rubber case (ZeroLemon battery case) but the screen is now black. It's not cracked at all and the digitizer still works fine and the phone rings and if you touch the screen in the right place you can answer calls etc.
For a few days prior to this there were occasional lines on the screen and I suspected a loose connection at the time. After the drop and the screen going black I took it apart and sure enough the ribbon cable to the screen had popped off. I have put the cable back on but the screen is still black. When turning the phone off and on, the backlight does flicker on for a split second but there is no graphics on the screen visible. Even booting into download or recovery mode nothing is visible on the screen.
It was running CWM recovery (I can't remember which version) and CyanogenMod 10 (unsure of the exact version) and we desperately need to access some data from the phone, particularly the contacts and text messages. Is there a way we can recover this or gain remote control of the phone from a computer at all? I've seen several posts about using the SDK and ADB to do this but USB debugging is disabled so this wouldn't be an option. I've also read that it's possible to get an adb shell to enable debugging from CWM but can't seem to find any clear instructions on how to do this, I've booted into CWM and tried the adb tools but it does not list the phone.
Can anyone advise why the screen wouldn't work after plugging it in again? Or is there any other way to control the phone from a computer without usb debugging being enabled? My partner is desperately trying to access her google account and this phone is the only device that's logged in and is her only hope to recover the account.
Hey, thanks for clicking hopefully you can help,
I have a One Plus 5.
Here are the symptoms, screen is just black with a couple flashes of blue sometimes lot of physical damage, trying to get the screen to work is definitely not an option. The phone plugs in and charges and the LED seems to work only when the screen is "off" (should be), the three main buttons seem to work, they vibrate when I press them.
I have tried to follow a couple adb guides on how to enable debugging like this but am having a hard time.
when I type '.\adb devices' it shows an 8 letter device name that is 'unauthorized'.
My guess is that there is something to do with the fact that my USB transfer mode is not file, I can't even access any of my phone's files on my PC.
I have no idea what to do past this point, although I have tried a couple of code pasting which didn't result in much.
Any lead would be appreciated, you guys probably know how important a phone is nowadays, with every authentication and bank payment authorizations done on mobile I am quite lost.
Thank you for any info.
bump
one last bump in desperation
i'm not sure what forum to put this or if i'm even allowed to ask here but ummm okay here goes..
a week ago or so my g7 maxx fell and the screen broke and went crazy constantly jumping tap marker and nonresponsive with only about 15% of the screen visible but hard to make out and constantly waving..
i ordered a new phone the same type hoping i could just transfer the settings apps and service to the new phone. but to start the backup/transfer i have to go on the google app on the broken phone and i'm unable to do this. i've tried lots of things but have had no luck.
i know dev mode is on but i'm unsure if i had usb debugging on.
is there anything i can do?
https://ibb.co/hfcm5r8 picture of the screen . cant unlock it as the screen is unresponsive. btw phone isnt upside down in the pic or set-up weird yes the time is in a very wrong place for it to be
bump* . (am i allowed to do this?)
The door to Android is ADB. Why not simply run command
Code:
adb devices
to check whether ADB is working?
that kinda stuff is new to me.
would i just plug it in via the usb/type c and then type it in cmd?
it makes no reaction when plugged in unless i boot it to clockwork so i was assuming even though dev mode is on that the debugging wasnt