Hello.
I hope someone can help me with my oldish i9192. I've had it rooted and with CyanogenMod 12.1 for ages, and a few days ago, something happened with the display. First it was almost completely black all the time with a few pixels popping up. Later there were more and more random colored pixels on the screen. A day later, the whole screen was full with randomized colors of pixels. Finally, it went completely white all the time. Couldn't see even the splash screen either.
I thought the AMOLED screen was bust until I tried today to reboot into recovery. Recovery has the same white-ish screen. Then I booted into Fastboot/download mode. I could even see the Splash screen this time, as long as I'm trying to boot into recovery or fastboot. Fastboot works, I can read everything clearly.
I tried to flash a new recovery, cwm and twrp. Still the same issue.
Anyone has any idea what's happened to my phone?
Related
Edit: After 5 month passes I have hope that somebody came across this
problem as well in the meantime. It's quite annyoing not to see the screen
during boot and recovery since I'm flashing roms quite often.
Thank you in advance for any feedback.
Cheers
NDesire
Edit:
It seems I'm the only one having that kind of problem. :-(
Hi Everybody,
somthing very strange happend to me. I hope you can help me. After I broke
my AMOLED Screen, I replaced it with a new one. (Yes I ensured, that it is
an AMOLED and NOT a SLCD). After reassembling, everything seemed to work
fine. The Desire boots first with green HTC splash screen and then with my
monster boot animation from InsertCOIN. But then, after second reboot the screen remains black.
I could feel the vibration, so the phone seemed to start but no splash screen and no boot animation.
When the boot is finished, I can activate the screen by double pressing the power button.
After that, phone works ok without any flaws. However, when I reboot, same procedure again.
The screen remains black until the boot is finished. OK, phone is working but it is annoying that I can't
go into HBOOT or Recovery mode. Actually I found a work around by using Androidscreencast to go into
recovery and flash roms, but I'd like to do it from the phone direct without casting the screen to my PC.
After some investigation I found an issue with probably wrong display driver, but that's purely related to SLCD Desire.
Anyway I tried to flash the latest RUU and rerooted in order to see if it makes any difference. But no change.
I even tried to replug the display connector to the main PCB in the phone. Nothing helps.
Now I hope the community has an idea.
By the way I had Bootloader 0.75 before reflashing RUU. Now it is 0.93. I'm currently running InsertCOIN 2.0 with A2SD.
Thank you in advance for any useful hint beyond what I tried so far.
Cheers
NDesire
Hi all,
after 5 month passes I have hope that somebody came across this
problem as well in the meantime. It's quite annyoing not to see the screen
during boot and recovery since I'm flashing roms quite often.
Thank you in advance for any feedback.
Cheers
NDesire
Edit:
It seems I'm the only one having that kind of problem. :-(
Hi Everybody,
somthing very strange happend to me. I hope you can help me. After I broke
my AMOLED Screen, I replaced it with a new one. (Yes I ensured, that it is
an AMOLED and NOT a SLCD). After reassembling, everything seemed to work
fine. The Desire boots first with green HTC splash screen and then with my
monster boot animation from InsertCOIN. But then, after second reboot the screen remains black.
I could feel the vibration, so the phone seemed to start but no splash screen and no boot animation.
When the boot is finished, I can activate the screen by double pressing the power button.
After that, phone works ok without any flaws. However, when I reboot, same procedure again.
The screen remains black until the boot is finished. OK, phone is working but it is annoying that I can't
go into HBOOT or Recovery mode. Actually I found a work around by using Androidscreencast to go into
recovery and flash roms, but I'd like to do it from the phone direct without casting the screen to my PC.
After some investigation I found an issue with probably wrong display driver, but that's purely related to SLCD Desire.
Anyway I tried to flash the latest RUU and rerooted in order to see if it makes any difference. But no change.
I even tried to replug the display connector to the main PCB in the phone. Nothing helps.
Now I hope the community has an idea.
By the way I had Bootloader 0.75 before reflashing RUU. Now it is 0.93. I'm currently running InsertCOIN 2.0 with A2SD.
Thank you in advance for any useful hint beyond what I tried so far.
Cheers
NDesire
Hello
I recently flashed the Galnet 2.11.26 ICS framework based rom and all was fine until yesterday when I started experiencing graphical anomalies and the lock screen sometimes not showing up which I solved with a battery pull.
This morning though the screen would stay "black" constantly.
What I mean by this is that I dont see the boot logo on anything but a black screen.
The screen starts off rather white with some colored stripes here and there and then fades to black over time. This could be because of hboot's white background, but it always eventually fades to a mostly black screen with a coloured vertical stripe or two.
I am wondering if the HW acceleration part of the ICS based framework has somehow messed up my display drivers or is at all to blame for the problem?
I found other cases of black screens and they all replaced the phone under warranty. Since it is a public holiday I am unable to take it in even if I wanted to and while I wait I figure I might as well try fix it.
I have managed to blindly navigate in clockwork recovery to mount my usb storage and put a new (non-ics based) rom on, but I have difficulty flashing it. After searching around I tried to push a command txt file containing the line:
--update_package=/sdcard/update.zip to /cache/recovery/command (copied successfully) and then rebooting into recovery but it never seemed to flash the rom. It can currently still boot fully into the galnet rom and I can even managed to play music, but the screen stays black.
I have an HTC Desire Z with permaroot, cwm recovery and engineering hboot.
I replaced to galnet boot audio with an htc quietly brilliant one so that if I do take it in they will, hopefully, not realise a custom rom is flashed.
Any help would be much appreciated.
I was trying out using a keyboard with a cheap USB OTG cable, and all was good. Then all of the sudden the screen went buggy, where ever other line of pixels was shifted to the left or the right, almost like some sort of corrupted video file. It started to reboot itself, and it got to the black screen with the Google logo and then the screen fuzzed in the same way as before. It then starts to reboot and does the same thing over and over again. I find that I can get to the recovery screen with the scroll arrows. From there, if I tell it to reboot into recovery it goes back into the same Google logo bootloop. I then went back to the original recovery screen and I decide to try out adb to see if it works. Sure enough it does, and I unwisely start flashing a stock 4.2 bootloader image. However, while it is flashing the screen does the same fuzz thing and and stays fuzzed. Then it doesn't respond to anything. I take out the battery, and try to restart and with will not turn on at all, no vibration, no light from the screen, nothing. I tried a unbricking methods from there, and nothing can make it come back alive. Any ideas?
Additional info:
GSM tajkju
Bootloader unlocked
Running stock unrooted 4.2 that I flashed manually
Stock recovery
I tried flashing the Zeus kernel using CWM, but I failed to realize the kernel was for the Verizon S3. When I restarted after flashing, it displayed the Samsung logo for a split second and then went to a black screen. The screen was on, but it only showed black. At this point I passed out, and when I woke up it was still on the black screen. I pulled the battery and tried to restart, and got the same black screen. Then I tried every way I know of (except using a jig) to get into download mode to no avail. Now when I turn it on, it vibrates once, flashes the logo, and then the screen shuts off and is useless. I think there's a solid chance I've ruined it this time, but if anybody has any suggestions they would be greatly appreciated. Thanks!
Put the phone in dl mode. It's possible the screen will be black and you can't actually see it's in dl mode. Plug into your computer. Odin flash a stock Rom.
The fact that it's doing something means it is not completely ruined. It just may be harder to restore to working order.
Also, take a look at this thread
http://forum.xda-developers.com/showthread.php?t=1746665
Hello all!
I just want to make sure my watch actually is toast before I shed my final tears and move on.
Here's the situation. It worked fine up till a few weeks ago, then one night after it had completely died, I went to charge it and it was in a huawei logo boot loop. To be clear, I see the red logo for a few seconds, goes black, and repeat. I never see the android logo or anything like that. Every once in a while I can get it to show the low battery (the sliver battery, not the red X one). I CAN get into fastboot no problem. I tried doing factory reset from fastboot, same thing. I didn't have any custom imgs or anything on it, all stock OTA updates etc. So then I tried flashing probably 10 different images I found around the web including stock boot and recovery, twrp, etc etc (pretty much every img I could find). Nothing changes, as soon as I reboot after flashing, same red logo bootloop.
I'm guessing it's a weird hardware issue, or _maybe_ my last hope was just my charger is bad all of a sudden (getting another one just to see).
Any other thoughts? I did take it all apart, check connections etc, everything looked fine. Put it back together and same behavior.
Thanks for any help!
Update: A new charger did not help. I'm convinced it's something hardware related. I might pick up a few broken ones on ebay and mess with building a full working one. I'll update again if I get something to work.