I wanted to start a thread to see if we can get some ideas going on how to fix this flicker of epic preportions some of you are having running AOSP on the 3.4 kernel.
Anyone can participate flicker or no flicker we need your help, Please list the following:
Hboot:
Hboot Engineering or normal:
Super CID / Back to normal:
which recovery are you using:
Are you S-off or S-on:
Are you Dev unlocked or not:
Do you use the SD swap hack or not:
How bad is the flicker (1 not at all / 2 some flicker/ 3 anime fight scene):
What is your base band:
(please copy the template above into your post and answer the questions)
Hboot: 1.15.1111
Hboot Engineering or normal: Engineering
Super CID / Back to normal: CID-VZW_001
which recovery are you using: TWRP 2.6
Are you S-off or S-on: S-off
Are you Dev unlocked?: No
Do you use the SD swap hack or not: No
How bad is the flicker (1 not at all / 2 some flicker/ 3 anime fight scene): 2
What is your base band: 1.53.06.0919
Hboot: 1.15.0000
Hboot Engineering or normal: (do not know what this means)
Super CID / Back to normal: CID-VZW__001
which recovery are you using: TWRP 2.5.0.0
Are you S-off or S-on: S-off
Are you Dev unlocked?: Yes
Do you use the SD swap hack or not: Yes
How bad is the flicker (1 not at all / 2 some flicker/ 3 anime fight seen): I've seen the whole spectrum, mostly 2 (some flicker), but sometimes none.
What is your base band: 1.53.06.0919
My info
Hboot: 1.15.0000
Hboot Engineering or normal: normal - used HTCDev unlock process (although had to change CID from Verizon first)
Super CID / Back to normal: should be normal - VZW_001
which recovery are you using: Clockwork 6.0.3.3
Are you S-off or S-on: S-ON
Are you Dev unlocked or not: yes
Do you use the SD swap hack or not: no
How bad is the flicker (1 not at all / 2 some flicker/ 3 anime fight scene): 3
What is your base band: 1.53.06.0919
Here's what my HBOOT screen says:
*** TAMPERED ***
*** UNLOCKED ***
FIREBALL PVT SHIP S-ON RL
HBOOT-1.15.0000
RADIO-1.53.06.0919
OpenDSP-v29.1.0.45.0622
eMMC-boot
Aug 1 2012, 12:05:25
MY serial is HT26KS312867
I flashed 9/20 this morning (without even clearing anything but cache) and got the new Cyanogenmod setup screens, though I just Next'd through them. The flickering is still there, and is really bad on specifically on the color grey (or when, for instance, opening a page that's white and then dragging down from the top which shades out the white underneath) but is much, much less noticeable below 25% brightness. I'm going to run at that level of brightness for a while and just see how it works.
We need to post in the Android general section or something and ask for help. As mower said, this is a developer forum overall and I'm sure there's got to be some people out there willing to take a look into it or offer some ideas.
Hboot: 1.15.1111
Hboot Engineering or normal: Engineering
Super CID / Back to normal: CID-VZW__001
which recovery are you using: TWRP 2.6.3.0 Official & ClockworkMod Touch 6.0.3.3 Official
Are you S-off or S-on: S-OFF
Are you Dev unlocked or not: NO
Do you use the SD swap hack or not: NO
How bad is the flicker (1 not at all / 2 some flicker/ 3 anime fight scene): 1
What is your base band: 1.53.06.0919
HT26YS S/N
logcat output of bootup for my device (which flickers)
In the 10.2 thread (which I don't have authority to reply to) brianr134 asked if someone could post bootup logcat output from a device with a flickering panel. here it is! it's from the 9/20 nightly which i've been running all day. not too bad to use, although i've noticed bluetooth output has some weird knocking sounds sometimes and its a little unstable (but i did _NOT_ do a complete wipe, it was an upgrade from 10.1 simply because I wanted to quickly see how bad the flickering was, etc). I hope it helps!
"Show Surface Updates" on mdm05 vs nightly cm10.2
I just noticed that "show surface updates" has different behavior as well under these two - under mdm05 you can click "show surface updates" and not see any flashing to indicate updating. But when you do this under the cm10.2 nightlies, the status bar updates wildly in the same pattern as the flickering. I had turned this on under 10.2 briefly just to see if that had anything to do with it, and I initially thought it wasn't related. But I'm back on mdm05 now and the difference in the behavior is striking. The question is, why would it make some panels flicker and others not?
Since I have no idea how the "flicker" appears, does it come immediately at boot (visible in the CM animation) or part way through? Is it only in the gray colors?
Can someone else post another logcat?
brianr134 said:
Since I have no idea how the "flicker" appears, does it come immediately at boot (visible in the CM animation) or part way through? Is it only in the gray colors?
Can someone else post another logcat?
Click to expand...
Click to collapse
I can't get you the logcat, but I can tell you how it appears. First, mdmower discovered that if you never let the device's screen go off, the flicker will never appear. Obviously your screen has to go off at some point though. So once that happens, you will eventually start to see flicker. The best way to notice it is to turn brightness up. If you use auto brightness and you're in a dark setting you may not notice it right away. It starts as a mild flicker, mostly only noticeable on light grays. It eventually progresses worse and worse over a couple hours and you'll always see it. It's pretty much the edges of the screen flickering. If you stay on that build for a long time - maybe over night - the flickering will be super intense.
Related
My cousin asked me to replace his Aria's cracked digitizer and I did. When I tried turning it on to see if it worked, the screen had backlight but it was black and the orange led light kept flashing. It didn't move from there. I took off the battery and tried it again and it went to what looked like S-On HBOOT FASTBOOT screen. It wont respond to the volume keys to go down or up on the selection menu and the power button won't select anything. I tried plugging it to the computer but it only does the same thing and sometimes the orange led light doesn't flash it'll just be orange.
This is exactly what it says
LIBERTY PVT SHIP S-ON
HBOOT-0.57.0000
MICROP-031b
TOUCH PANEL-STN21_00
RADIO-7.08.35.06
May 8 2010,03:56:58
HBOOT (this part is highlighted in blue and when i connect the usb to the pc it'll say HBOOT USB PLUG)
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT(This is highlighted in blue)
RECOVERY (not highlighted but is green colored)
CLEAR STORAGE
SIMLOCK(not highlighted but colored blue)
then it has three android bots on skateboards at the bottom
I tried putting the Original shipped file as a zip in the sd card but when it checks to see if there's any to flash it doesn't recognize i guess because it doesn't tell to me to continue with the installation or anything.
IDK what to do ?
Please help ! Thanks in advance!
Is it possible you have the wrong digitizer? I noticed this line:
TOUCH PANEL-STN21_00
Click to expand...
Click to collapse
Mine says TOUCH PANEL-STN21_03, and any other images I can find on Google are the same
I know there are two types for Liberty, Synaptics & Atmel.. I'm not sure if the hardware detects which one is installed and switches over, but if it doesn't you may have an Atmel one and the phone came with Synaptics.
It might be something for a different phone too
(Libertys with Atmel are something like "TOUCH PANEL-ATMEL224_16ab")
Does it work and boot with the old one put back in? (if that's possible.. I haven't had to replace any digitizers, so don't really know what happens)
WinSuk said:
Is it possible you have the wrong digitizer? I noticed this line:
Mine says TOUCH PANEL-STN21_03, and any other images I can find on Google are the same
I know there are two types for Liberty, Synaptics & Atmel.. I'm not sure if the hardware detects which one is installed and switches over, but if it doesn't you may have an Atmel one and the phone came with Synaptics.
It might be something for a different phone too
(Libertys with Atmel are something like "TOUCH PANEL-ATMEL224_16ab")
Does it work and boot with the old one put back in? (if that's possible.. I haven't had to replace any digitizers, so don't really know what happens)
Click to expand...
Click to collapse
But my little aria is
LIBERTY PVT SHIP S-OFF
HBOOT-6.02.1002
MICROP-031b
TOUCH PANEL-STN21_00
RADIO-7.13.35.13
Nov 4 2010,23:12:58
and I am used Revolutionary to let it S-OFF
By the way,my aria is made in Taiwan and bought it in Taiwan,too
ishow0806 said:
But my little aria is
LIBERTY PVT SHIP S-OFF
HBOOT-6.02.1002
MICROP-031b
TOUCH PANEL-STN21_00
RADIO-7.13.35.13
Nov 4 2010,23:12:58
and I am used Revolutionary to let it S-OFF
By the way,my aria is made in Taiwan and bought it in Taiwan,too
Click to expand...
Click to collapse
Hmm I guess that doesn't matter then
It could still be wrong and the boot loader doesn't change though
Hello
I have a serious problem with my phone , started yesterday when i restarted my phone on the button in the system ( like restarting a computer). After that it has started but system booted only to htc welcome screen and no further, so rly help me
Methods i have tried:
- battery pull
- htcdev unlock bootloader ( so my bootloader is now unlocked )
nothing works ;(
SHOOTER_U VT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
What rom did you flashed, being s-on will cause issues flashing the kernel, you must have 4ext recovery with smart flash enabled
(Don't ask me for help as I couldn't care if your phone explodes, eh!
I have the exact same problem. Been using my phone issue free for a year and a half. Today I noticed the gps was on but it was not enabled in the "toggles" menu. I rebooted the phone and now it's in an ENDLESS loop that wont pass the white / green HTC logo boot screen.
I can not access recovery it just reboots.
I have tried:
1) flashing stock RUU through fasboot which did go to 100% ... phone still reboot loops
2) flashing latest stock ICS through fastboot (did not work said CID error)
3) Pulled battery and let phone sit
4) s-off with HTC dev unlocker
At this point I'm not sure what to do... I think this may be a catastrophic hardware failure.
Well I do believe my device is a lost cause.
1) I was able to flash 2.17 via RUU but it didn't change a thing.
2) Did the "Brick" method and downgrade to HBOOT 1.40 Still same behavior.
3) flashed 1.13 fully 100% via RUU.. still same thing.
No matter what I do the phone will not get past the white HTC splash screen. It stays on that screen for about 20 seconds then reboots. Also the phone feels really hot behind the cameras (not the battery) I think it's toast. Luckily I have an old HTC hero for a backup so I'm not completely FUBAR but I'll be on craigslist tomorrow looking for something new. Thinking of jumping ship to PagePlus this might be just the right time.
I made a terrible rookie mistake and foolishly updated my Google Edition HTC one to 4.4 over OTA. However, my device at the time was unlocked and rooted running TWRP and a rooted 4.3. I am beating myself because not only did I update recklessly, but I failed to make a backup before doing so. I have learned a few lessons so far from this folly and I anticipate to learn many more.
Right now when my device restarts it quickly flashes the "google" logo on black screen then transitions to a cyan screen with little green and red lines. When I boot into recovery mode and make my way to fastboot, this is what is shown:
***tampered***
***unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSP-v31.120.274.0617
0S-3.07.1700.1
I've been scouring the internet for options and have tried the following with various forms of failure. I've tried flashing various recovery files (I ultimately get "FAILED (remote: signature verify fail)"). Then I tried turning S-OFF and that wouldn't let me push the revone due to the "binary being unable to execute." I've unlocked and rooted multiple times before, but all the errors I keep getting have me stumped. I'm happy to try these and more ideas again because chances are high I missed a crucial step.
I would really appreciate if I could get some guidance on how to proceed to even get back to stock android (I'm willing to abandon any info on my SD card as I cannot seem to figure out how to save any of it at this point).
Apologies in advance for posting this in the wrong place, not providing proper information, making major noob moves, etc. Please show me pity and offer any guidance/help you may have. I will very much appreciate it.
Thank you so much!
Hello,
please excuse my poor english. I have a stock Evo3D which ends up in a bootloop after starting it. I have never rooted / installed a custom rom on it.
I wanted to gift my evo 3D to my little sister, after turning it on to check it i realized my batterie became too weak to start the phone so i replaced it with one i found on ebay.
Since then i coudn't boot properly.
I spend about 12 Hours to solve this problem but it just wont work regardless of what i do.
Here are some informations the bootloader shows:
***LOCKED***
SHOOTER_U PVT SHIP S-ON RL
HBOOT- 1.53.0007
RADIO- 11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.0202
eMMC-boot
May 22 2012, 01:06:07
The first thing i tried was to reinstall a stock ROM using a RUU, this didn't work i did a couple of attempts and then realised it has a Vodafone branding, next thing was using a Vodafone RUU
it didnt work aswell, i read on another forum that it has to be a ICS RUU with Vodafone CID which appearently doesn't exist. So my next attempt was to change the CID in which i needed to unlock the bootloader.
So i went to htcdev.com and did everything step by step, i thought "man this is easy", i got to last step where i could choose if i really wanted to unlock the phone or not. I choose yes and the phone was supposed to reboot.
The problem now is it doesn't, it freezes with the red light and black screen, i cant access the bootloader unless i remove the battery and put it back in. If i do so it still is locked.
Now im out of ideas and feel bad for my sister, cause i promised to give this phone to her if she gets good grades.
If you have ANY ideas please let me know i would really appreciate it.
xbluemonkeyx said:
Hello,
please excuse my poor english. I have a stock Evo3D which ends up in a bootloop after starting it. I have never rooted / installed a custom rom on it.
I wanted to gift my evo 3D to my little sister, after turning it on to check it i realized my batterie became too weak to start the phone so i replaced it with one i found on ebay.
Since then i coudn't boot properly.
I spend about 12 Hours to solve this problem but it just wont work regardless of what i do.
Here are some informations the bootloader shows:
***LOCKED***
SHOOTER_U PVT SHIP S-ON RL
HBOOT- 1.53.0007
RADIO- 11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.0202
eMMC-boot
May 22 2012, 01:06:07
The first thing i tried was to reinstall a stock ROM using a RUU, this didn't work i did a couple of attempts and then realised it has a Vodafone branding, next thing was using a Vodafone RUU
it didnt work aswell, i read on another forum that it has to be a ICS RUU with Vodafone CID which appearently doesn't exist. So my next attempt was to change the CID in which i needed to unlock the bootloader.
So i went to htcdev.com and did everything step by step, i thought "man this is easy", i got to last step where i could choose if i really wanted to unlock the phone or not. I choose yes and the phone was supposed to reboot.
The problem now is it doesn't, it freezes with the red light and black screen, i cant access the bootloader unless i remove the battery and put it back in. If i do so it still is locked.
Now im out of ideas and feel bad for my sister, cause i promised to give this phone to her if she gets good grades.
If you have ANY ideas please let me know i would really appreciate it.
Click to expand...
Click to collapse
Is it a sort-by-lowest-price battery? if so it could be (again) a battery problem! In my experience most used batteries for evo 3d are stock ones by htc and Anker ones
Snoob25 said:
Is it a sort-by-lowest-price battery? if so it could be (again) a battery problem! In my experience most used batteries for evo 3d are stock ones by htc and Anker ones
Click to expand...
Click to collapse
Thanks for the quick reply, it was a mid priced battery with sold by a high rated seller.
I've dealt with a similar problem. Try booting into the bootloader and leave it there until the battery dies. Pull the battery for -several minutes-, then replace and plug in. Give it a while to charge, then start again with the ruu.
Edit:
Also with a similar problem, had some luck running the ruu multiple times consecutively without letting it boot all the way / rebuild the dalvik cache between flashes.
Hi everybody. I just bought an HTC one m9 (att) sight unseen through local classified ads It will not boot into an OS. It has TWRP 2.8.6.4
When I hold down and power I get:
HTC download mode
*** UNLOCKED ***
htc_himaulatt PVT S-OnLK-1.0.0.0000
RADIO-01.01_U1440221_62.05.503206_F
OpenDSP-v20.2.6-00452-M8994-0216
OS-1.32.502.31
Mar 23 2015,02:02:54(506785)
Here are my challenges:
It does not seem to charge.
When I attempt to boot the OS I get "this build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action"
It stays on this screen until the battery dies.
I attempted, based on the readme thread, to download the corresponding Ruu and convert it to a 0PJAIMG.zip. The phone recognizes this when I boot to download mode, but my volume up button does not work.
What should I try next to go from a paperweight to a usable phone.
swing4thefence said:
Hi everybody. I just bought an HTC one m9 (att) sight unseen through local classified ads It will not boot into an OS. It has TWRP 2.8.6.4
When I hold down and power I get:
HTC download mode
*** UNLOCKED ***
htc_himaulatt PVT S-OnLK-1.0.0.0000
RADIO-01.01_U1440221_62.05.503206_F
OpenDSP-v20.2.6-00452-M8994-0216
OS-1.32.502.31
Mar 23 2015,02:02:54(506785)
Here are my challenges:
It does not seem to charge.
When I attempt to boot the OS I get "this build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action"
It stays on this screen until the battery dies.
I attempted, based on the readme thread, to download the corresponding Ruu and convert it to a 0PJAIMG.zip. The phone recognizes this when I boot to download mode, but my volume up button does not work.
What should I try next to go from a paperweight to a usable phone.
Click to expand...
Click to collapse
Update:
I updated TWRP to 3.2.3.0 and was able to flash Lineage OS 13, but now my recovery mode freezes and the rom bootloops. When recovery freezes, the screen goes crazy, kind of like it looks when the digitizer underneath is broken.
I managed to log in long enough to downgrade twrp to 3.0.0.0 but the screen problems are the same and set in even faster.
Now what?