Okay so i cracked the screen on my phone, i buy another HD to swap screens since i can't turn mine in to insurance because i can't get the new one unlocked. Once i installed the new screen my phone will get to the CyanogenMod boot screen, load for varying amounts of time, and then keep rebooting until it decides it's ready and fully boots up to CM11. I've tried factory reset and full data wipe but it still doesn't fix the problem. Is it possible to get a logcat of the boot sequence to see what's making it hang and bootloop?
Disregard folks, i opened up the phone to double check the ribbon connections since the proximity sensor/light sensor wasn't working either. Turns out the main ribbon wasn't all the way connected, re-hooked it up and the thing booted up first try.
Related
ok, weird issue.
Yesterday I came back to my TF having left it inmy bag for the day, and it would not turn on at all.
I tried various things and then decided that the battery must be totally dead.
I left it to charge over night, and come the morning was able to watch it booting.
However once It finished boot it goes to black screen. Pressing the power button sometimes gives a flicker of backlight and then goes blank again. sometimes it even gives a glimpse of the screen.
Plugging in the power sometimes gives a longer blink of the booted ROM.
I have tried a cold boot, a full data wipe and I have used NV flash to fully reinstall the ROM (Prime 1.8)
After the full reinstall I go through the Google initial setup process without a problem, as soon as the rom boots I am back to the flicker of screen going off..
Does anyone have any ideas??
Still got the problem, does this sound like hardware to anyone else?
if the screen doesnt work during boot it is hardware problem. flash ur rom again or wipe it
chatch15117 said:
if the screen doesnt work during boot it is hardware problem. flash ur rom again or wipe it
Click to expand...
Click to collapse
Screen works fine during boot
Done both of your suggestions unfortunately, as I stated in my original posting.
I am going to try going back to Stock, and assuming its an app NOT restore any during the rebuild process.
Today I noticed I couldn't hear incoming calls, but they could hear me.
I have cyanogenmod 9 alpha 3 release, and tried reformatting, and reinstalling alpha 5 to no avail. Even called tmo to check if it was a network issue with no luck. Then I noticed my screen go shut off upon opening the keyboard. It would go on and off as if the connection was loose. Now it is permanently off so I followed the directions to factory reset through hardware buttons and am pretty sure it did reset. However, this will just keep me stuck at the recovery mod screen as I know from previous wipes.
My questions are the following:
Is my phone gg'd?
If I hook up a tv out cable to the audio jack, will I be able to see the screen on a tv for reformating to stock rom for tmo replacement?
If I send in my phone with a dead screen, will they know I installed a custom rom and tell me this was my fault?
That's about it.
Thanks.
=(
This issue make absolutely no sense to me, and only started yesterday.
First, I am stock, unrooted, no mods, no crazy sideloaded apps, just a good old Nexus 5.
When I go to wake the phone, I have noticed that the lock screen is 100% unresponsive. I cannot enter a pattern lock. I then switched to a PIN lock, thinking maybe there was an issue with the pattern. Again, unresponsive screen. So I took my screen lock off completely, thinking there is maybe an issue with the lock screen in general. Again, even with no lock screen, I cannot swipe screens, open apps, nothing. This also includes the soft keys at the bottom.
I decide to factory reset my phone. I update only my Google apps, and again notice the same issue. The screen is totally unresponsive, but then 2 white lines will flash at the top, and the screen will work.
Once those white lines flash, the screen is completely responsive like normal, there are no other issues until the phone goes to sleep again. Sometimes the little lines flash 2 seconds after waking up, sometimes 30 seconds, sometimes I have to hard reset the phone.
I also am linking to a YouTube video that I recorded of the issue in case I am not making sense.
So can anyone explain this to me? What could cause this issue on a phone that has never been rooted or flashed or anything?
Thanks in advance for the help!
https://www.youtube.com/watch?v=2r3U9MhZuG0&feature=em-upload_owner
Weird. Issue. Maybe you should stick everything from your sd to your pc.
And flash a factory image from fresh install from here - https://developers.google.com/android/nexus/images - if you're lucky the drivers maybe corrupt and not the hardware
Sent from my Android 5.0 Nexus 5
Could also be a loose connection. Maybe the flex cable to from your screen wiggled its way out a bit. I've never seen that before on any phone. I'd back everything up and flash a factory image. If the issue persists, contact Google and see if you can RMA the device.
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.
So, first I thought my brother's A51 was water damaged because it was wet a little bit and charging was being interrupted. I left the phone turned off for the night and wanted to look at it again the next morning. The problem is that the screen or something else stopped working.
The screen works fine in Download mode, Recovery mode, or at splash screen with phone's model name, the problem begins when it's booting to Android. It's still stuck at the splash screen. no boot animation, no lock screen visible, just a model name. It's not bricked, because I can still unlock the phone (didn't have a password) and I can hear the unlock sound or charging sound (it started working again).
I tried factory reset through recovery - didn't help, flashing fresh firmware from Frija - didn't help. The only thing that changed is now the splash screen brightness goes down a bit and I noticed that until I am touching the screen so the phone can't lock itself it doesn't turn off the splash screen, but when I press the lock button it turns off the screen and I can't turn it back on, but the phone still works because I can hear charging sounds and it shows up in Device manager.
I also opened it because I wanted to see if there's any water damage, but I didn't see any water marks or burnt components. I cleaned the charging board with alcohol and let it dry but that didn't help.
I'm worried that there's something wrong with the motherboard or the charging board because it has a screen connector.
I can also see that some people here have similar issues:
Unbrick A51 - Stuck on samsung logo
Hi, My phone is stuck on A51 logo for days now it charges - I can enter download mode easily - I can sometimes enter recovery mode some other times it doesn't let me I tried flashing different stock ROMs of android 10, 11 for the phone with...
forum.xda-developers.com
black screen after splash and unable to factory reset, possibly frp?
Apologies for formatting, typing up on my phone during my break at work. To be more specific, I have a samsung a51 that recently had a black screen of death with no known cause. The samsung splash screen as well as the recovery menus alll work...
forum.xda-developers.com
I should also add that I don't have access to settings so I can't unlock OEM and flash custom recovery / ROM. I also cannot downgrade to Android 10 (duh)
I have exactly the same behaviour here.
I ordered a "defect" A51 on Ebay which was not working. I opened it an saw a water damage at the USB-C charging board. Since there was a lot of oxydated parts I ordered a replacement for this board.
After cleaning an replacing the charging board I have the same issue as szerbi. I see the charging screen (while powered off), I can enter download mode and transfering stock firmware using Odin, I can enter recovery mode. While all these states the display works well and I cannot see any damages like a broken display.
I even got it working correctly after several Odin firmware update and recovery mode / factory reset attempts and I could install some apps and set up my google account. I was very happy. But after some hours again: no screen while Android is running.
Now, when Android is running I hear the charging and the screen shot (pressing volume-down + power buttons) sounds and the phone will be visible as a storage device while connecting to a PC.
Conclusion: The display is black while Android is running. Since it was shortly active I assume either a loose contact on one of the flex cable connetions or a water damage at the displays flex board. Unfortunately latter cannot be checked without dividing the display from the display frame. I assume this is an irreversible process.