[Q] Galnet ICS Black Screen - G2 and Desire Z Q&A, Help & Troubleshooting

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.

Related

[Q] Black Screen only during boot after display repair

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

[Q] FXP failure to boot

Hello again. This is sort of a continuation from my previous thread about trying to replace the touch screen, but it's an entirely new problem, so I figured it warranted it's own thread. Since the replacement screen that I received didn't allow touch to work, I thought I'd try going back to the old cracked screen to see if it was the screen, or the hardware. I got all the way through the process of swapping the screens, and put it back together.
Now when I try to boot up, I get the Free Xperia Project boot up screen. After about 20~30 seconds, the purple LED comes on. At that point, I'm used to seeing the Cyanogen Mod boot animation, but now it just sits on the FXP screen. After a short wait, the screen dims and there's a very tiny vibration, even shorter than the power-up vibration. If I tap Volume down during the FXP screen, and try to enter CWM, all I get is a screen full of randomized snowy rainbow colored pixels
I've tried disassembling and reassembling the phone several times. I've tried reflashing the boot image in fastboot mode, which I don't seem to be encountering any trouble with. Does anyone have any advice for me at this point? Or should I just give up and get a replacement? Thanks.
ProcyonSJJ said:
Hello again. This is sort of a continuation from my previous thread about trying to replace the touch screen, but it's an entirely new problem, so I figured it warranted it's own thread. Since the replacement screen that I received didn't allow touch to work, I thought I'd try going back to the old cracked screen to see if it was the screen, or the hardware. I got all the way through the process of swapping the screens, and put it back together.
Now when I try to boot up, I get the Free Xperia Project boot up screen. After about 20~30 seconds, the purple LED comes on. At that point, I'm used to seeing the Cyanogen Mod boot animation, but now it just sits on the FXP screen. After a short wait, the screen dims and there's a very tiny vibration, even shorter than the power-up vibration. If I tap Volume down during the FXP screen, and try to enter CWM, all I get is a screen full of randomized snowy rainbow colored pixels
I've tried disassembling and reassembling the phone several times. I've tried reflashing the boot image in fastboot mode, which I don't seem to be encountering any trouble with. Does anyone have any advice for me at this point? Or should I just give up and get a replacement? Thanks.
Click to expand...
Click to collapse
Did you follow the instructions and do you have a unlocked bootloader? ? Did you use flashtool to update the xperia play to the 2.3.4 before flashing FXP? Did you wipe dalviche cache, data reset, and cache during Clockwork mod recovery before installing the zip file? Did you download the correct zip for the Zesus file? If you downloaded zesusc =CDMA varient and zesus = GSM varient.
chery2k said:
Did you follow the instructions and do you have a unlocked bootloader? ? Did you use flashtool to update the xperia play to the 2.3.4 before flashing FXP? Did you wipe dalviche cache, data reset, and cache during Clockwork mod recovery before installing the zip file? Did you download the correct zip for the Zesus file? If you downloaded zesusc =CDMA varient and zesus = GSM varient.
Click to expand...
Click to collapse
Thanks for your concern chery2k, but this didn't happen as a result of the FXP installation. I have been successfully running FXP for around a year now. This all started because my touch screen got stepped on and cracked, and I had the bright idea that I could buy a touchscreen replacement for $30 and do the installation myself. While I was successful (somewhat) at replacing the screen, the touchscreen itself was defective (no touch), so in my impatience, I attempted to put the cracked screen back. Once the phone was reassembled, this was the outcome. Even though nothing about the process should have directly contributed to the state of the phone, there's no telling how the frequent assembling and disassembling may have damaged the electronics or ribbons, despite how careful I tried to be.
I have regrettably downgraded back to my old HTC Eris. I'm due for an upgrade, and looking at the HTC Droid DNA, but the lack of a card slot bothers me. The SGN2 seems just too big for me as a phone. As much as I'd love more powerful hardware, it looks like I may have to find an Xperia Play on eBay or something, and pay to have the bootloader unlocked

[Q] Screen Issues Lead To Bricked Device

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

[Q] White-red-ish screen, in big trouble?!

Hey,
so I just recently bought the Oppo Find 7 (2560x1440) and just wanted to root it and install a custom ROM. When I attempted to flash another recovery it failed, I assume due to resolution issues (it only showed half of the recovery while flashing incredibly).
Then I managed to get nameless' recovery which apparently has the right resolution and could work with it. But it was already reddish / white from the get go, didn't think much of it and kept using it.
Now, when booting up the device, there's a white/red corner around the whole screen, that is supposed to be black and I can see elements from nameless' recovery.
Also flashed CM12 onto it and everything is white/red, when pressing the power button to lock / sleep the device, and pressing it again screen stays black.
Any help would be appreciated.
Problem solved. Thread closed at OP's request.

White screen on anything but Splash/Fastboot

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?

Categories

Resources