My mother recently bought a Droid Incredible and prefers my sister's setup with Cyanogen. They both received their phones on the same day and are both SLCD.
For my sister, I used unrevoked and a custom image to handle the SLCD problem (Recovery with black screen/white border.). I installed Cyanogen and all is well.
Today, I ran the new unrevoked that claims to accommodate SLCD screens. No blackscreen or white borders to start, but when I went to install the Google Apps addon that Cyanogen provides I started getting the black screen with white borders again.
Any help would be keen.
Related
Hey guys,
picked up my desire a few weeks back, only just started using it the other day (was researching best way to transfer PIM data from HD2).
anyway, i was playing around with some of the built in apps and junk last night...in a room with the light off, and noticed that when the screen was black (on/illuminated, but not colour - the desk clock screen).. there is a reasonable strong green tint down the right hand side of the display. i have done a little research and have read some people have complains of green/blue/pink hues to their entire display.. but my green stain is only on part of the screen.
anyone else have this problem?
i went back to the store i got it from, they said that HTCs exchange policy requires me to send my device back, they will look at it and either repair or replace. seeing as the reason i bought the desire is to desperately escape WINMO, i figure the slight bug of a green stain is less of an inconvenience than using my HD2 for a few more weeks.
cheers.
Could be down to having a SLCD screen as opposed to an AMOLED one
The blue tint to the amoled screen is there on purpose, blue led's die alot quicker than other ones, samsung make there screen to over display blue, as your device gets older this blue will slowly die to a yellowy colour! Maybe the green tint is related?
Sent from my HTC Desire using Tapatalk
EddyOS said:
Could be down to having a SLCD screen as opposed to an AMOLED one
Click to expand...
Click to collapse
Does he have a slcd screen lol ignore my last post then xdaers lol
Sent from my HTC Desire using Tapatalk
I'm assuming so if it was only purchased a few weeks ago, could be wrong
yeah guys... i got the SLCD version.
i dont think its a natural screen 'quirk'.. as it only appears on a small portion of the screen.
cheers for the replies though ey.
I have the same problem on both my desires. One of them has a finish tint in the middle of the screen and this one has like a brighter spot on the top right of the screen. I have the SLCD screens. I bought the phones in Wisconsin.
Off topic
I feel so alone on this forum because everyone talks about the GSM version. Is there any news about froyo update for this phone on US Cellular? I love the phone but getting tired of waiting all the time. I just heard there's 3.0 coming out on the 11th of November. But not for Desire. I'm sure it will be there when my contract is over. Lol.
Sent from HTC Desire 2.1
i also have an slcd desire
but i have a pinkish tint in the top right
it's kidney shaped :d
black lcd
hi
Solution to you brick
Past details of HTC bravo
Android 2.3
Hboot 1.02.001
I tried to unlock the bootloader by
1- HTC dev method
I started by the same procedure given on the
website. But the procedure didn't work for me,
when I commanded adb devices it never
showed my phone then when I commanded '
get oem identifier token ' I got another error. I
got frustrated
2- Then I went on to the mini_adb method by
using shell, Su commands
It neither worked
3- After that I came across the downgrade and
boot method, it resulted into a brick
But no worries my pals !!
Unbricked successfully !!
basically it was an Indian phone so some strong
securities
first installed this to my phone which had 2.3
android and hboot 1.02.001
RUU_Bravo_hTC_Asia_India_1.21.720.4_Radio_32.36.00 .28U_4.06.00.02_2_release_127705_signed.exe
then my phone got bricked due to downgrade.
the led screen blackout happened and a vibrate
was at the startup and can navigate volume
buttons only*
then i got worried after that i installed this thing
to unbrick back
RUU_Bravo_hTC_Asia_WWE_1.19.707.7_Radio_32.36.00.2
8U_4.06.00.02_2_release_126179_signed.exe
then to no help after that this one
RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.
05.00.11_release_122704.exe
and wahhoo!! unbicked my phone to 2.2
android, dont worry the phone will popup an
update notifier after you start your phone
So i got a new replacement phone after dropping and shattering my old one, its an amoled model (trust me I checked) and when in recovery its just a black screen with white bars, I've flashed recovery multiple times to no avail
isn't that the slcd problem ppl been having? I know you said amoled but im not so sure
Sent from my ADR6300 using XDA App
Garrett07 said:
So i got a new replacement phone after dropping and shattering my old one, its an amoled model (trust me I checked) and when in recovery its just a black screen with white bars, I've flashed recovery multiple times to no avail
Click to expand...
Click to collapse
that same problem is with the slcd screens..how did you check to see if you had the AMOLED screen?
That was the problem the SLCD models have...
Trust me, I have one.
Never mind figured it out lol, i do have an slcd flashed the fix and were good to go sorry, mod you can close this thread or delete it.
Ok so I bought the wife a new G2 about a month ago from T-Mobile. The phone is great and we have both been loving it. Earlier this week the wife mentioned that she was unable to use her phone a couple times because she couldn't get the screen to come up. I messed around with it for a while and eventually it started acting up again. While using the phone, the screen would start to flicker (go between the expected image and a black screen), almost as if the backlight was going out (yes I know there is no backlight with OLED), and then the screen went blank. The screen was black for almost half an hour. I tried pulling the battery and rebooting, the screen never came on and the phone booted up completely. Since it was still useless I went ahead and pulled the battery again. I let it sit for 3-5 minutes and powered it back up. The screen came on, started to flicker a bit and then went black (this is at the HTC boot screen). Eventually the phone came back and now it hasn't exhibited the problem in a couple days. I have noticed that this doesn't seem to be a problem with the Z-hinge (seemed like a likely cause at first), as playing with the hinge doesn't seem to make it flicker or reduce the flicker when its happening. At this point I am 90% confident this is a hardware issue unrelated to the z-hinge. Perhaps a faulty LCD driver chip or a improperly seated ribbon cable on the motherboard side. Feel free to offer any other suggestions.
so... the phone has been rooted and has Cyangenmod installed. In order to get a warranty claim on this I will need to flash the phone back to the original TMO rom. This should be as simple as just flashing the stock .nbh file through the boot loader right? I need to do this before the screen permanently dies on me and I have an expensive paperweight. My other question is if anyone knows whether T-Mobile will send me a new phone replacement for this? I'm under the impression that when you do a warranty exchange you are sent a refurbished model that has been repaired. The phone is only 1 month old and I don't want a refurbished 6 month old phone to replace it, although I don't know if I really have many options.
Okay what method of prem root and s-off did you do? Because if u used the 1st method of prem rooting and s-off useing unforgivens way you need to hex edit to properly flash the PC10IMG.zip stock rom or u will get simi bricked phone. Am not familer with rage so I can't really explain that. As for gfree method you should be fine flashing the orginal stock rom but have more procedure to turn on S-on
Sent from my HTC Vision using XDA App
I used the gfree method described here http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 using the full method that does the radio S-OFF, Super-CID and simunlock.
Hopefully I can just do something like what they discuss here: http://www.addictivetips.com/mobile/how-to-unroot-t-mobile-g2-htc-desire-z-complete-guide/
Thanks
I advice following this
http://forum.xda-developers.com/showthread.php?t=835971
It worked for me. Well hope everything works out
Sent from my HTC Vision using XDA App
The backlight may very well be faulty. This is not an OLED screen. Its just a standard LCD display.
I would get it exchanged if I were you.
Sent from my T-Mobile G2 running Cyanogenmod.
Just got the new G2 in the mail, rooting it now. I was under the impression that the H2o had an amoled display and not a standard backlit lcd. Is this incorrect?
Sent from my HTC HD2 using XDA App
No the g2 has a normal lcd
Sent from my HTC Vision using XDA App
The G2 has an S-LCD. An better LCD screen developed by Sony.
HTC started to use S-LCD because samsung couldn't make enough AMOLED screens for HTC's Desire phones.
Has anyone here broke their screen and replaced it. I have replaced a few screens now on the Verizon M7 and have found that you need the right lcd/digitizer installed for twrp to work. I first thought is was the red shell I was converting to, Until I dropped it and broke the screen and replaced then twrp worked again. I started having issuses with my screen and had it replaced under warranty. I installed the replacement screen today and again like 2 screens ago twrp will not load.
So, if anyone breaks their screen, be advised some of the replacement screens out their do not get along with twrp or cwm for that matter. I guess, try to make sure you getting genuine htc replacement parts when ordering a new screen.
I was excited to install a brand new lcd/digitizer and then I saw the new rom with sense 7.0 and I went to load twrp and not loading. Has anyone else out there replaced the screen and twrp stopped loading? I mean what good is having a s-off rooted phone the will not boot into recovery.
I don't think I can rma the screen over twrp not loading.....................
I haven't had issues with TWRP, but I have replaced 3 screens on Verizon M7s & M8s and non have worked, yet the original cracked screens work fine. I'm wondering if there are model/carrier specific screens that need to be used?
Hey guys, long time lurker, first time poster. Been rooting and running custom roms for some time, so I was farily confident in what I was doing (previous devices were G1, HTC Desire, 2012 Nexus 7, Nexus 4, and Samsung Galaxy Express). I bought myself a G3 off Swappa (D851, I'm still rocking that $30/month Nexus 4 plan through Tmobile) did my some research, rooted, installed xposed, and was enjoying it until I noticed that I could not change the background on the lock screen from that stock pink & blue ink/cloud thing. Granted it's a stupid cosmetic thing, but I'm OCD...
Any how, followed the procedures to install the latest 20B version of BlissPop (http://forum.xda-developers.com/tmobile-lg-g3/development/rom-1-11-15-t3000137), did a full wipe and got it up and running only to then notice that over time the screen started tearing, like some one had cut the displayed image in half and stuck them back together out of alignment; right through the middle of my screen. I knew this was a software issue.
I of course was not a fan of this and decided to go back to the stock rooted 20B (http://forum.xda-developers.com/tmobile-lg-g3/development/rom-tmo-d851-lollipop-20b-stock-t3096479). I again followed the instructions, full wipe, flashed boot assist, then flashed stock image. Now it won't boot; the black abyss of the once beautiful screen reflects my own loss for words. Tried booting into recovery, tried the hold power button for 2 minutes thing, rain dance, blood sacrifice, and nothing.
The device goes into download mode just fine and I tried the softboot repair method (2015 TOT Method! listed here: http://forum.xda-developers.com/showthread.php?t=2785089) and the thing won't even flash. I'll snag a screen shot of the error later when I get home. Tried all 8 of my usb cables and all 6 of the USB ports on my computer; it's like hotdogs (packaged in 8) and buns (packaged in 10). I guess what I'd like to know is has anyone have any luck restoring functionality with a similar situation? Or have I bricked it and have no choice but to attempt to RMA through T-mobile or bite the bullet, rape my wallet, and buy anther one? I guess if I have to suffer through a harsh lesson learned then it is what it is, but I figure at least checking with a community that is as open as this is worth a shot.
AW1985 said:
Hey guys, long time lurker, first time poster. Been rooting and running custom roms for some time, so I was farily confident in what I was doing (previous devices were G1, HTC Desire, 2012 Nexus 7, Nexus 4, and Samsung Galaxy Express). I bought myself a G3 off Swappa (D851, I'm still rocking that $30/month Nexus 4 plan through Tmobile) did my some research, rooted, installed xposed, and was enjoying it until I noticed that I could not change the background on the lock screen from that stock pink & blue ink/cloud thing. Granted it's a stupid cosmetic thing, but I'm OCD...
Any how, followed the procedures to install the latest 20B version of BlissPop (http://forum.xda-developers.com/tmobile-lg-g3/development/rom-1-11-15-t3000137), did a full wipe and got it up and running only to then notice that over time the screen started tearing, like some one had cut the displayed image in half and stuck them back together out of alignment; right through the middle of my screen. I knew this was a software issue.
I of course was not a fan of this and decided to go back to the stock rooted 20B (http://forum.xda-developers.com/tmobile-lg-g3/development/rom-tmo-d851-lollipop-20b-stock-t3096479). I again followed the instructions, full wipe, flashed boot assist, then flashed stock image. Now it won't boot; the black abyss of the once beautiful screen reflects my own loss for words. Tried booting into recovery, tried the hold power button for 2 minutes thing, rain dance, blood sacrifice, and nothing.
The device goes into download mode just fine and I tried the softboot repair method (2015 TOT Method! listed here: http://forum.xda-developers.com/showthread.php?t=2785089) and the thing won't even flash. I'll snag a screen shot of the error later when I get home. Tried all 8 of my usb cables and all 6 of the USB ports on my computer; it's like hotdogs (packaged in 8) and buns (packaged in 10). I guess what I'd like to know is has anyone have any luck restoring functionality with a similar situation? Or have I bricked it and have no choice but to attempt to RMA through T-mobile or bite the bullet, rape my wallet, and buy anther one? I guess if I have to suffer through a harsh lesson learned then it is what it is, but I figure at least checking with a community that is as open as this is worth a shot.
Click to expand...
Click to collapse
where does the tot method fail?