I cracked my screen a few months back and am just now getting around to attempting to replace it. After going through the steps to replace it, I began to experience a blank screen when attempting to boot into the rom.
The screen works just fine in bootloader mode, or in recovery. If I attempt to boot into the rom, the screen will go blank after a few seconds of showing the rom logo. I can tell the N7 is on as I have it connected to my laptop.
Although, my screen was cracked, I was not having this type of issue prior to replacing the screen. I attempted to flash into stock on the off chance that it is a software issue, with no change in the situation. I am wondering if maybe I damaged some component while attempting to replace the screen.
Any advice or assistance is appreciated. Thank you.
Related
I have installed Cyanogenmod on my MT4G, it was working fine for few months, but now it is developing a strange problem with the display. The symptoms include:
The screen is pixelated when displaying text, and colors are distored (at first a reboot took care of the problem, but now the problem no longer goes away)
No display of the myTouch 4G splash screen
When boot into recovery, I can see the recovery menu VERY briefly, then the screen goes dark, completely black
When boot into bootloader, the screen is completely blank. Can not see anything.
I was thinking the problem may caused by Cyanogenmod, however, because now the screen is completely blank, I can not even restore to stock using the Power+Volume down method. I do know that it still entered bootloader mood since I can see the device using adb/fastboot command.
Any pointer as to what may have caused this or help getting me restored back to stock would be greatly appreciated.
Note, I have wipe the phone, I have tried Cyanogenmod 7.1, nightly build 252 and 7.2RC1, and the problem is still there. I was not able to flash a stock rom using rom manager.
My tablet screen froze when I was using it. I pushed the reset button after the screen was unresponsive for a few minutes and it wouldn't go past the boot screen. I went into recovery but was unable to mount anything. Doing a little research I went and wiped the data but it still wont boot. I used APXflash tool, entered by SBK, and now the tablet turns on but no boot screen, no recovery, nothing.
Does this sound like the memory died, or am I making it worse by trying to fix it. I was running cwm recovery and omni rom light when this all went down.
Any help?
I messed up with my LG G2 D802 and i need help because i believe it's a software problem.
When i was installing the latest cm12.1 nightly, after trying a few other roms, i also installed, by mistake, an old jb bootloader/bootstack.
As result the phone entered in Bootloop, but not a normal bootloop, on the screen start appearing some crazy interferences and then the phone boot up, but the screen not. The phone made sounds and the touchscreen work, but the screen was black/off.
I've managed to solve the problem with an unbrick method, but now i have a huge problem: the screen, on the rigth side, from the top to the botton has 6/7 black lines. I have no idea how to solve this and if is a hardware problem ... I've read it's an kernel problem, not hardware, but don't know how to solve the problem :/
Picture:
https://meocloud.pt/link/58d13900-ffa8-4114-8957-8c4b973bad1a/IMG_20150916_020454.jpg/
I feel your pain
Hi mate
Same thing happened to me.
Background info: I had successfully upgraded to CM12.1 , was running fine for a few days then I wanted to update my TWRP, updated the recovery and just went to check that I had OTG cable support then boom, boot loop.
It didnt just loop it just loaded loaded loaded, then the screen made some funny sounds. and then shut down. I hard reset to recovery and reinstalled CM12.1 and was able to successfully exit the loop. but damage to screen had occurred in the exact same place, and method right side of the screen.
Tried rinstalling original jellybean software from my backup. no success, and also flashing other versions of CM12.1 nothing.
After some research I saw that this is a manufacturing fault and that this occured quite often. it appears that the best solution is to buy a new screen as it is the actual hardware that is damaged in the screen digitizer. I might be wrong, and I pray that I am because I want to fix it too. in the end I just bought a new note 4 (not note 5 as i wanted SDcard storage). Phone was 2 years old and a new screen costs a fortune. But i miss my little G2 and its super fast speed and simpleness. :crying::crying:
If someone else has the solution to this problem on the forum we are all ears.
Hi,
I have a Note 4 t-mobile that is "brick" right now. and I hope if anyone offer assistance.
It is running Android 6. Ever since the last upgrade the phone would freeze and reboot on its own. I fixed that problem by installing Wake Lock. After that it would still experience sluggish at time but the phone is still very much usable.
Lately, after watching a bit of streaming video the phone would slow down so much that a reboot is needed. But yesterday my last reboot turned my phone into a brick. After that reboot the phone rebooted itself to the download mode. So I took the battery out, waited for a few minutes and put the battery back in and started the phone. Instead of booting normally the phone displayed the message including "set warranty bit: recovery" and then followed by the flashing TWRP splash screen. By "flashing TWRP splash screen" I mean the TWRP splash screen ( with the TEAMWIN logo) would be shown on the screen for a second, then the screen black out for a couple of seconds, then the splash screen is back on for a second, and the screen black out for a couple of seconds, etc, and never successfully boot into TWRP recovery. I had left the flashing splash screen overnight and nothing changed. Connect the phone to my pc via usb and fastboot wouldn't recognize my phone when phone was flashing the TWRP splash screen. So I tried to flash TWRP again by starting my phone in download mode "volume down + power". When I connected my phone to my pc Odin recognized my phone. But when I tried to flash a custom recovery (TWRP or CWM) it seems the download started but never finished (on the phone I could see the progress bar started but never progress further).
Any suggestions would be greatly appreciated1
Additonal info
I just wanted to add that my phone is still running the stock ROM.
Problem solved
Problem solved. Once I used a different cable and the download process actually worked and I was able to flash stock ROM using Odin.
Hi all. I recently fixed up my old G900F that had been sitting in my closet for years in need of a screen replacement. All went well with the repair but after booting up the phone, it goes through the android optimizing apps screen, but then the device reboots and just sits on the Samsung boot animation. Occasionally the device will vibrate and the recents and back button light up, almost as if the device booted successfully, but it ends up staying in this loop. I let the device keep looping for over an hour but it still never booted successfully. I have also tried to install other stock Roms using Odin, which flash successfully, but do the same loop.
Any help would be appreciated. Thanks!
Did you replace the battery?
It may not have enough available watts to boot up. The current draw on boot up may be heavy...
Also clear the system cache.
If all that fails the firmware image may have been corrupted, factory reset or reflash if that fails, but replace the battery first.
If that fails the mobo may have been damaged by what broke the display. Any impact sufficient to damage the display or bend the frame can take out the mobo as well.