Hey guys,
After replacing my broken screen and reflashing my M8 from GPe to the original Sense, my screen is behaving a bit erratically.
When booting up, everything works fine. The backlight (if set to auto) will dim and light up accordingly, it can be manually set to different brightnesses, et cetera. Phone is working fine.
Then, when the phone is locked and unlocked using the power button, there is a good chance that it will 'bug out', only lighting up the backlight without displaying the screen. After one or more lock/unlocks, the normal screen will come on and I can use my phone as usual. However, at this point the phone is no longer able to change brightness other than the maximum, and the unlocking bug will still occur most of the time.
I've tried flashing different ROMs, both Sense and GPe, but all exhibit the same problem. Changing the setting in the menus successfully changes the values in the system files, but the screen brightness doesn't change.
I suspect something went wrong with the firmware itself, so I'm trying to downgrade the phone to an official build, and work my way up from there.
- Does anyone recognise these issues or have any idea what may be causing this?
- What is the best way to ensure firmware files are re-flashed on a S-ON phone?
I tried logging the console from boot to the moment the error occurs, but haven't been able to make much sense of it (or even find the breaking point, it spits out log rules too fast!). Can add it if anyone is interested.
Thanks in advance!
Related
Yesterday I rooted my HTC Droid Incredible (AMOLED). Following that I installed Cyanogen Mod 7, Build 30. The rom was running perfectly until earlier today. Half way through the day, at a point at which I'm sure I still had battery power, the screen no longer functions. Restarting is responsive, but still leaves a blank screen. The same goes with the method of holding the volume down key and the power button.
How may I restore function to my phone, whether it be unrooting or however else? Whatever the method, how can it be done without a visual onscreen?
Less important but still of interest, what is the likely cause that transformed the phone from one working to bricked so randomly?
Thank you.
Did you drop it or get it wet?
Sent from my Incredible using XDA App
Were you ever able to use ADB before this happened? If so, then can you try it now. If you can at least see something, you could give that a try and try some trouble-shooting from within. I'd guess that if something serious happened to the actual screen or interface to it, that it might show up as a hardware error in the log. (#logcat, dmesg, ).
Have you yanked the sdcard and mounted it on a PC? (if you can, you might be able to save the content, reformat 'fat32' and maybe for starters just try to restart it with the blank reformatted card. If that works, well, you're OK.
Do you think it is booting fully, but just not able to output to the LCD or do you think it is only doing the first stage and dropping into the recovery screen? Was this thing overclocked? If so, have you tried a 'safe boot' yet (which disables anything past a vanilla startup like setcpu type things)? (instructions are around XDA somewhere).
Without seeing.. I suppose you can put a standard image on the phone (as in RMA) if you get the 'timing' down for when to push buttons, (assuming that is still doable).
So since all the other threads revolving around this issue seem to be nothing more than suggestions of things to try rather than trying to determine what the problem is, I wanted to start fresh.
Here's my issue regarding reboots on my Evo (Hw 003). Simply put the phone will reboot (typically under moderate/heavy use, I've not once seen it reboot on it's own, although I can't say it hasn't when I've been asleep).
This issue has persisted regardless of HBoot Version (I've been on 0.76 ENG, 0.97, and 2.10), PRI, Radios or ROM. Trust me, I've tried nearly every combination. It even persists when fully unrooted and returned to stock.
I've obviously tried every type of wipe (both through CW and Amon's Recovery and using Calkulin's WipeAll method in both recoveries) prior to flashing roms and after restart/crashes. I've tried eliminating SD Card issues, and these issues persist regardless of whether the SD card is in or out, or whether it's corrupted or not.
Here's the only things I can definitely say regarding the reboot issue (which I do have to believe is a HW issue, although it may have something to do with the early boot sequence...see my reasoning below).
When the crash occurs, the phone ALWAYS attempts to reboot itself. Very rarely it will do this successfully (but it seems to only be successful in doing so when on customs ROMs, specifically CM7 nightlies, which makes me think that those crash/reboots are unrelated and are actually just software issues with the rom/apps in question and should therefore be disregarded).
If my phone is currently set to S-OFF, the reboots always ends with under 5 seconds on the white HTC Evo screen, then display goes black and I get five vibrates and a flashing green power LED. When this happens and the phone is connected to my laptop via USB, right after the 5 buzzes, I get a Hardware Growl notification that a Qualcomm USB device has been connected.
If the phone is currently set to S-ON, the reboots result in a bootloop that again, shows the white HTC Evo screen for less than 5 seconds, then the screen goes black, phone restarts and starts the loop again. In these cases I don't get the Qualcomm/HW Growl message.
With S-OFF the only surefire way to get a working phone back is to remove the battery for a few minutes (seems like it needs at least 3-4 minutes, which makes me think some form of volatile chip/ram needs to drain to a certain point before working again). I can always get HBOOT/FASTBOOT though, even if I just remove the battery for a second. It feels like I can get into Recovery with the battery removed for less time than it takes to actually boot into the OS, although this may be an inaccurate observation on my behalf.
With S-ON, while removing the battery seems to yield the same results as when the phone is S-OFF, occasionally if I let the bootloop play out, it will eventually hang on the white HTC Evo screen for some time, then restart and boot like normal.
---------Conclusions----------
From what I can tell this whole reboot/crash issue people seems to be having (when it isn't caused by bad flashing or improper use of the phone) can be narrowed down to two areas.
1 - There is an issue with the phone's RAM. This would make sense since there is a difference in the results of removing the battery for a short time or long time when trying to recover from a crash.
2 - It's an issue with the phone's early boot sequence. Perhaps the phone's internal memory (specifically the boot partition or wherever HBOOT/FASTBOOT is stored, not 100% sure where that actually is) has bad sectors or is otherwise corrupt.
I'm leaning towards the RAM being the culprit though, since it seems to be the only thing linking all of the different crash/reboot scenarios. And although I've heard rumblings that it may be a CPU issue, I really doubt this since I can always get into HBOOT/FASTBOOT and because when it crashes and give the 5 buzzes (which some have speculated is a Qualcomm error code for CPU's) it then seems to be communicating on some level through the CPU and USB with my laptop.
While I obviously can't replace the phone's RAM to check this, I just wanted to see what the opinion of those who are a bit more familiar with the phones inner workings than I am have to say about this.
stefpap I have been experiencing the same systems that you describe here. I am currently on the Synergy rom, but I have also experienced this while on myn 2.2 . I have tried multiple reboots/resets and clearing of the sd card except for the rom itself. I want to say that the reboots happen while the GPS is running in maps and navigation. They also seem to happen while watching 15-20 min into a movie.
Have you made any headway on the issue? I also tend to believe that the memory is running away. I have found that the battery becomes a little warm when i remove it for the reset ( I dont know if it has anything to do with this issue)
One last thing, I cant remember this happening when I first received the phone. it also wasnt rooted and had different versions of apps, but who knows.... please let me know if you have found anything about this issue.
Well as an update I uprooted my phone and took it into a repair center, they saw what it was doing (see above) and ordered me a referb. Turns out the main board was causing reboot after getting to hot.
Sent from my PC36100 using XDA Premium App
Hi,
so I am finally at that point where I'm about to jump off a bridge.
My beloved HTC Desire has got weird problems and I really have no more idea, what I can do.
So here's the problem:
Sometimes (turning screen off sometimes helps), my phone registers an input (at a certain horizontal line, I will clarify that later) when I'm actually not touching that zone at all.
So (if you have the keyboard open), it always thinks it is touched at a horizontal line which is about there, where the 'a' is on the qwerty-keyboard. (I have a swiping keyboard on my phone, that always gives a nice blue line from 'a' to 'l'...).
The really weird thing about that is, that I don't actually have to TOUCH the screen. I can move that blue line on my keyboard (or change homescreens for that matter) while I am about 1-2 cm ABOVE the screen and I DON'T EVEN TOUCH IT. That really drives me crazy, as I don't even know whether that's physically possible...
That behaviour is totally random, sometimes I don't see it for 1-2 days, sometimes it won't go away for a couple hours.
Additionally, sometimes the Screen won't recognize my touches at all (only at lockscreen, turning on and off helps).
So I tried restoring various Nandroid backups from when I didn't have that problem, I tried flashing a new radio, a new rom, data, factory etc. wipe and nothing helps.
Pulling the battery when it's off and leaving it off for about 10min also won't help.
If you don't understand what I'm trying to say (I know it's difficult and I appreciate any efforts to help) I will try to record a video of it.
It is also difficult returning the phone as that failure is not reproducible.
I am running MIUI 1.5.20 on my S-OFF'ed HTC Desire with SLCD Screen.
I would be so thankful for any help,
Don
Maybe just an issue with the screen in general. You ever throught about contacting HTC or your carrier? See if getting a new screen would be better and stop these problems. Just be prepared to use an RUU though.
thanks Meaple,
anyone else got an idea?
:/
Hello All,
Yesterday I started having a strange issue.
I was trying to apply Zagg Screenguard on my HOX. So I moisted it with the application solution that they provided. But I feel I just put a little more solution that needed too and the screen got a little dampen. However I removed all excess moist and liquid solution asap after applying the screenguard.
However to my dreaded surprise I started having a strange issue since then. The phone boots up and screen and buttons all work perfectly. But if I let the screen sleep for say 30 secs or so and then try to wake it up again, the screen just remains blank. Capacitive buttons do light up showing the phone is on and not hanged or off. I have to restart the phone to again get the screen work.
I also tried removing the screenprotector suspecting there might be some moist still there causing the issue, but no help
I also installed the Maximux JB rom yesterday only just before applying the screenprotector. I know its far fetched , but do the rom can have anything to do with it.
Please guide me what to do asap.
Thanks in advance !
WOW.. no replies yet ...
OK.. I got more info to make the issue more clearer... I do think that the phone hangs before screen goes blank.. I think the issue is that when the phone kept in sleep for few minutes apparently it hangs then only and screen doesn't come up.
Also I checked the 'Stay awake while charging' option from Developers options settings and it seem to work ok till I charge the phone , but as soon as I pull it from charger within few minutes the same issue.
Now it is beginning to be more apparent to me that the issue is somehow related to voltage settings and its getting two low when at deep sleep. I have not changed the voltage setting as I'm using stock settings on maximus rom which is nearly stock.
Is there a way to recalibrate voltage settings by software. Maybe I should install a custom kernel and increase volatage scale? or do I have to take it to the technician to have a look at ?
Pl help ! I'm forced to use my secondary phone as regular one which I don't like very much !
Cheerio !!!
Do a nandroid backup.
Install official ROM.
Test it.
Decide whether it's the ROM or not.
Decide whether to restore your backup.
BenPope said:
Do a nandroid backup.
Install official ROM.
Test it.
Decide whether it's the ROM or not.
Decide whether to restore your backup.
Click to expand...
Click to collapse
Thing is I have upgraded to Hboot 1.28 to install JB maximus. So not sure if I can install official rom on this , until official JB is released.
Also I'm pretty sure now that issue is not software related. I have tried 3 different roms and different kernels that I can try and still the same issue.
Also I tried changing governers and voltage settings using voltage control, but no use.
I've been having a weird occurrence with my Z5 and I'm wondering if anyone can enlighten me as to whether I should be panicking or not.
I unlocked my bootloader, rooted on android 6, installed xposed and a few modules and then installed all of my apps from backups from my old Z2. The phone was working great, restarting perfectly, and I've been adding software to the phone.
I mount a lot of software on my phone and have a 200GB SD card, so I have a ridiculous amount of apps on it(~300 non system apps after debloating).
Recently when my phone has been rebooting it will load to the wavy screen, dim the screen to my brightness setting after it's nearly ready, un-dim itself back to the first brightness setting, then after a moment crash and go black screen. The LED flashes red a few times, then stays solid for a moment before the phone bootloops and begins trying again.
On the second attempt it will usually load correctly though it still does the bright-dim-bright which did not used to occur. If I kill the phone using power + vol up and load again, it doesn't load successfully on the second shot.
What does this LED pattern mean? Anyone with some expertise able to shed light on any of this? Anything would be hugely appreciated!