Please read the OP (below). I am in serious need of assistance. I am attaching an updated Logcat to this Edited OP. Please read through the Log if you do not mind, and let me know what all you think may be going on here. I am getting a little frustrated to be honest. There is rarely that time when I have run across a problem that I could not fix with a bunch of reading, and study. But, this quite frankly is a bear that won't go away. I will not leave this problem unresolved. And I hope that with the friendly folks here at XDA that together we can resolve one more issue. I know there are others that are suffering from a similar issue. People just get too intimidated to ask questions sometimes. I can say that after almost 3 weeks of reading, I am far from afraid of asking for an assist. So, again, Thank You to anybody willing to help. I will attach the Logcat to this Edited post.
edit:20131128_0747mst-ev_attachment(1)
Briefly: I had the honor of meeting a fellow XDA Member in person by total accident. Together we have been attempting to troubleshoot her DNA. She has been working to resolve the following issue for a couple of months, and I have been reading endlessly & searching endlessly for a solution to the following problem. Please give any advice that you are capable of giving. Thank you.
The issue we are having is that once we get the ROM completely loaded (Venom v. 2.01) & the device boots up completely, as soon as the screen is touched the phone flashes back to the white HTC screen and begins to bootloop! I had the wise idea to check inside the phone thinking it may be a grounding issue. Sure enough there were 3 screws missing. Still this did not solve the problem.
Is there a step we are missing? Is there another issue that others may have had that is similar or that you have resolved prior?
We have even reflashed the stock RUU by relocking the bootloader, then unlcoking, reloading the recovery, and again the ROM. Still have the same issue. Anybody have any input? I know this is kind of a brief explanation, but I tend to get long winded. Below is the information for what is currently running.
Unlocked,MONARUDO PVT SHIP S-OFF, CID=22222222, H-Boot - 1.33.0001, Radio - 1.00.00.1023_3, OpenDSP - v4.120.240.0920 eMMC-booT, Oct 23, 2012, 21:34:05, Running TWRP Recovery v 2.06 ROM - ViperDNA 2.01 Sense5
P.S. I have a similar issue with an HTC Sensation that I have been working on for a while. However, the issue with the Sensation is something to do with the aftermarket digitizer and the firmware loaded on the chip on the digitizer and something to do with the diagnostic software. I am stuck there too as I am unable to get the pyramid.nbh file to load correctly.
Did you have this problem with stock rom?
Please you should get a logcat from this phone. I am guessing a problem with the touch screen or battery.
WellTrainedVC said:
Briefly: I had the honor of meeting a fellow XDA Member in person by total accident. Together we have been attempting to troubleshoot her DNA. She has been working to resolve the following issue for a couple of months, and I have been reading endlessly & searching endlessly for a solution to the following problem. Please give any advice that you are capable of giving. Thank you.
The issue we are having is that once we get the ROM completely loaded (Venom v. 2.01) & the device boots up completely, as soon as the screen is touched the phone flashes back to the white HTC screen and begins to bootloop! I had the wise idea to check inside the phone thinking it may be a grounding issue. Sure enough there were 3 screws missing. Still this did not solve the problem.
Is there a step we are missing? Is there another issue that others may have had that is similar or that you have resolved prior?
We have even reflashed the stock RUU by relocking the bootloader, then unlcoking, reloading the recovery, and again the ROM. Still have the same issue. Anybody have any input? I know this is kind of a brief explanation, but I tend to get long winded. Below is the information for what is currently running.
Unlocked,MONARUDO PVT SHIP S-OFF, CID=22222222, H-Boot - 1.33.0001, Radio - 1.00.00.1023_3, OpenDSP - v4.120.240.0920 eMMC-booT, Oct 23, 2012, 21:34:05, Running TWRP Recovery v 2.06 ROM - ViperDNA 2.01 Sense5
P.S. I have a similar issue with an HTC Sensation that I have been working on for a while. However, the issue with the Sensation is something to do with the aftermarket digitizer and the firmware loaded on the chip on the digitizer and something to do with the diagnostic software. I am stuck there too as I am unable to get the pyramid.nbh file to load correctly.
Click to expand...
Click to collapse
Logcat from DNA
removed
Still having this issue. Even with the Stock Rom. I am also unable to upgrade via OTA to the newer firmware releases as I am unable to keep the phone on long enough to use it, plus the touch screen/digitizer I believe is the main problem.
I read another article online about how HTC utilizes a digitizer which uses resistive (sp sorry) feedback on their touchscreens. It really has me thinking that this issue can be similar to the issue I am having with my Sensation. That issue is digitizer related, and happens with aftermarket digitizers. There is a way to fix the issue with the sensation however. I can post another logcat if any member is willing to lend me their eyes & knowledge? Or you can just use the logcat above.
Thinking about joining another discussion in the mean time. I am slightly concerned for this thread is a developer thread, and I don't quite have the chops to hang with the dev's. Although I do understand a majority of what they are saying, and can even put into practice the things they are doing. Ability to read & comprehend is a wonderful gift.
Still Having Issue
Still having this issue. Even with the Stock Rom. I am also unable to upgrade via OTA to the newer firmware releases as I am unable to keep the phone on long enough to use it, plus the touch screen/digitizer I believe is the main problem.
I read another article online about how HTC utilizes a digitizer which uses resistive (sp sorry) feedback on their touchscreens. It really has me thinking that this issue can be similar to the issue I am having with my Sensation. That issue is digitizer related, and happens with aftermarket digitizers. There is a way to fix the issue with the sensation however. I can post another logcat if any member is willing to lend me their eyes & knowledge? Or you can just use the logcat above.
Thinking about joining another discussion in the mean time. I am slightly concerned for this thread is a developer thread, and I don't quite have the chops to hang with the dev's. Although I do understand a majority of what they are saying, and can even put into practice the things they are doing. Ability to read & comprehend is a wonderful gift.
Related
So guys I have a HD2 but sadly the LCD is cracked so it's annoying me a fair bit. The price is a bit steep to get it repaired too (€150+). So was looking online for a replacement and seen this
I have for sale the above phone. I'm selling for 200 for this reason. The phone keeps rebooting and sometimes doesn't come on. I've tried to flash a different rom and the phone booted into windows ok but then stopped coming on again.
Click to expand...
Click to collapse
Does this sound fixable by flashing a different ROM or maybe MAGLDR and running Android or is it a most likely a hardware issue? AFAIK it boots to HSPL okay.
Not really easy to tell from distance. Some more information would be helpful.
Yes, in many cases, bad flashes can cause many errors. Also, especially in the recent past, many people flashed wrong SPL/HSPL or Radio ROM versions. In addition, some Android builds, if this was used, seem to leave a certain electronic footprint on the device´s memory, all of which could be solved more or less easily.
But then again, there are quite some users, especially with irregular restarts, who had their HD2´s fixed or replaced due to mainboard problems.
As tictac said, its hard to tell.
The fact that the seller mentions trying to correct the problem by reflashing suggests that they at least have a basic knowledge of this kind of thing and how to correct it so personally I would jump to the conclusion that its a hardware probem.
You might get lucky and find that they just arent following the correct steps to fix a software issue but if your patient you could grab a fully functional HD2 from ebay for the same price.
That said, if you were to buy it and find you couldnt fix the problem then you could always put it back on ebay and more than likely break even on what you paid....
Personally though, I'd wait it out.
He said it could be easily fixed but he doesn't have the time and he's not bothering as he has an iPhone 4. I'm going to ask him to try install MAGLDR and if he can should it be okay?
Btw, what sort of information should I ask for?
That just makes me suspicious becase if it could be easily fixed then why wouldnt he just fix it if it can be fixed by flashing then its a 10 minute job. Even someone with a really tight schedule can find 10 mins...
If its been reflashed and the problem persists then theres a good chance its hardware.........
He says the phone boots but stays on white screen. Is this fixable? Funnily enough, I have the same problem with mine at the moment, can't even do a Task29, it stalls at 0%. :s
Hi,
Please forgive me if there is already a thread existing for this, as I am new here.
I have a question regarding my HTC Sensation XL, which is currently running Android 2.3.
I rooted my phone some time after I got it. I'll admit that my knowledge of such things is extremely limited, so I may have done something stupid. Anyway, I used some sort of one-click-rooting program (I honestly can't remember what it was called) to root my device. The root was successful and I was happy with this. However, I found that this caused my phone to show the bootloader menu, whenever I turned it on.
This caused an issue when I attempted to update my phone to Android 4.0. I could download the update, but the installation would be interrupted upon reboot, due to the bootloader menu showing up (or so it would seem).
To fix this, I attempted to unroot my phone using an app called 'Ginger Unroot', which seemed to work. However, the issue with the bootloader menu interrupting the update still occurs.
I'm aware that I've probably done something very stupid by opting for these one-click methods of rooting/unrooting, as many sites seem to suggest different, more complex methods. This is probably a lesson for me not to mess around with things that I don't quite understand.
Anyways, does anyone have any advice on how I may go about either solving or getting around this problem?
Your help is most appreciated!
N.B: My device has recently started turning itself off for no apparent reason, if that has anything to do with the problem at hand.
Alright, guys; I need some help. I previously had the classic all to well known problem with my digitizer, where I was missing about a half inch of touch input on my screen. I had gotten used to just rotating it to type, cause I was out of warranty, and I'm upgrading soon.However, more recently, I have developed a much bigger problem. My touch screen no longer works, AT ALL.
The issue first started when I attempted to install "Someone's ROM" with "That libs". I got screen fade-out that some other users reported, so I pulled the battery and flashed back to my EPinter's CM10 backup. After it had booted, I went to unlock the screen, and NOTHIN'. Not registering any presses or swipes what so ever. I then went into recovery and cleared everything, still nothing. Hooked it up to my PC, ran a FULL wipe (OS included), and flashed a fuitcake. After booting; still no touch screen. A helpful member of this forum suggested I try the PDS fix, so I did. Still left with the same result.
So, my question is... Is there any way that someone MUCH smarter than I can look at some type of statistic I can pull from my phone to see if there's a software problem causing this issue? And if so, is there any way I can retrieve said info with out being able to use the phone it's self? I really don't want to go the next 2 weeks with a flip phone. heh.
EDIT: If anyone can figure this out and get it fixed, I would be more than happy to donate.
Mast likely your digitizer is just broken!
Happens quite a lot on that phone.
They are not that expensive! (see for example http://www.amazon.com/Motorola-Screen-Digitizer-Replace-broken/dp/B004Z0UO8O)
If you can't change it yourself see if you find someone to do it.
Yup. Sounds more like a hardware issue since you already did all recommended procedures.
Sent from that Atrix.
Yeah, I figured as much. Just hard to accept that it's finally completely gone out on me. Especially since it happened at the exact second I tried flashing experimental, untested firmware. I am aware of how simple a digitizer replacement would be, but I don't want to spend $40 on a new one, when I'm about to dump another $300 into a new phone in two weeks, ya know?
Hi all, thanks in advance for any assistance you can provide me. I have looked for similar posts but could not find any (maybe I just don't know what my issue is called). I bought an HTC EVO 4g LTE from a friend that had put meanbean on it (I assume it was the latest). I went through all sorts of steps loading twrp and getting s-off and whatever else I needed to do to load cyanogenmod 10.2. I was able to do this fine but the gapps I loaded would not show. I tried it together and separately and nothing would work. So I loaded (I believe) 3.16.651.3_stock_rooted_odex_CPTB.zip so that I could use my phone again with the gapps while I was waiting for some assistance on the cyanogenmod forums, which never came unfortunately. Everything was fine for about the past 10 days.
Today I used my phone all day and had no problems (extra info: I installed one app to access my bank info which went fine), but hours later and all of a sudden my screen basically got stuck. It looks like millions of randomly chosen colors for each pixel. The screen will turn on and off if I hit the top button (or let the display "timeout"), and I can hear the tones when I press the up and down volume buttons. This is telling me it's not bricked, but it is completely useless to me as is. When I reboot the phone, I don't see anything on the screen until the colors come up (which is after the vibration during the bootup sprint screen as far as I know). I was able to get fastboot to see it once but haven't been able to get back into the bootloader (there's nothing on the screen so I don't know what I'm doing).
Basically, nothing on my screen while it is booting up until it gets to the point where my laptop detects the USB connection, and the crazy colors comes on. BTW, as random as it seems, it's the same colors in the same exact position each time and it never changes. I haven't tried flashing any roms with fastboot because it seems my issues is bigger than a rom... I can't even see anything when I had it in the bootloader... This is my only phone and I use it every day. I'm really quite desperate and could use any and all help you're willing to provide. I've attached a zip with a picture of my screen so you all can see what I'm talking about. Thanks in advance...
just an update, got my laptop to see my device with fastboot so I'm gonna leave it hooked up. Could really use some advice on how to proceed because I'm at a loss. Thanks...
From what I've seen in the past, it looks like the digitizer in the phone is bad. If you're good with your hands you can replace it yourself.
Sent from my HTC M8
Magnum_Enforcer said:
From what I've seen in the past, it looks like the digitizer in the phone is bad. If you're good with your hands you can replace it yourself.
Sent from my HTC M8
Click to expand...
Click to collapse
So can you say with any certainty that my issue is not due to the programming on the phone?
Magnum_Enforcer said:
From what I've seen in the past, it looks like the digitizer in the phone is bad. If you're good with your hands you can replace it yourself.
Sent from my HTC M8
Click to expand...
Click to collapse
I just thought I would see a similar screen in the bootloader if it were a physical hardware issue.
I'm basing my information off of previous posts with the same type of picture, and the replies that followed. All of those posts suggested that the digitizer was bad and that the issue was not software-related.
Magnum_Enforcer said:
I'm basing my information off of previous posts with the same type of picture, and the replies that followed. All of those posts suggested that the digitizer was bad and that the issue was not software-related.
Click to expand...
Click to collapse
Okay great thanks for the reply... the touchscreen portion of the phone still works (I was able to answer a phone call today even though I couldn't see where I was touching). I saw some videos online so I'll watch carefully and order a new screen/digitizer or whatever. Thanks again
Okay, a dual question here. One specific and one general but they are both related and one will help the other. Hopefully if anyone provides good answers others will find this post useful. I have a Asus Zenfone Selfie which has begun boot-looping. The phone is rooted and has TWRP installed. Once in a while it boots up as far as the home screen, then sometimes only up to the Asus logo. I have flashed several different ROMs (stock and custom) and again, it boots up to the setup screen then only up to the Asus logo so I was assuming this must mean it's hardware related. However, I can boot into TWRP and stay there for hours with no bootlooping. If it were hardware then it should bootloop for TWRP too so it must be software related, right? One more thing: I usually flash in TWRP but many times it crashes during the flash process. Sometimes it does succeed with no issues though. On my PC I might be running some disk or RAM checking tools to see if there was a bad sector or track on my hard drive or a bad module... Yeah, I'm confused. Why is it bootlooping and what, if anything, can I do to fix it?
This leads to my general question. Over the past 20 years I have had several phones, many of which ended up bootlooping. I know the LG G4 & G5 had a hardware flaw that cased them to bootloop and I know screwy flashes can cause bootlooping. But what about all my phones? Some were new, well, only a year or two old, some were 6 or 7 years old. Some were Android, some were Windows Phone. Some were rooted, some were unrooted, some were stock, some were custom ROMs. Some had updated or recently got new apps installed, others hadn't had anything new in ages. Some were in use when they started bootlooping, some were just sitting there. Some had a full charge on the battery, some were close to empty. What can be done to prevent this? What can be done once it has started, especially with one of these newer phones that they STUPIDLY like to make with sealed in batteries. And the given button combination just reboots the phone - again. Depending on who I talk to (or where I read) they say one thing or the other. It's software related. Okay, how? Why? I know on my PC Windows will sometime crash and reboot just for the hell of it, but that's usually just MS fixing an issue with a PC that runs too smoothly. And when that happens, it can be fixed. As an aside to any software developers reading this, I know you may not want to take the time to rewrite everything to work on Linux but you could take a little bit and make your software work with WINE, just a thought guys.
Anyway, so if it's software related, what can really be done to fix it? I can understand the big companies may like it if your phone bootloops so you'll need to buy a new one, but there are tons of developers out there making great custom ROMs. I know they don't have the resources to really fix all the bugs but I assume they would do a better job than certain big companies right? And why would the software suddenly crash like that? Sometimes literally NOTHING is happening, so why the sudden desire to bootloop? What about hardware? Can't we design software to work around the flaw? I would think manufacturers would want to fix problems to make their products as good as they can be but from what we have seen, I guess not. If you read my list above, many of those phones have nothing in common except the bootlooping. So where is the error coming from? Is there really nothing that we can do?
Any ideas and explanations would be appreciated, as would any help on my more recent bootloop device the Asus Zenfone Selfie Z00UD/z00T. Just to mention, that is a newer phone. It may not be now but it bootlooped probably a little over a year ago. It takes me a while to get around to things sometimes, like writing a letter to post on a forum. I had in mind to take it to this one repair shop (they had to replace the USB charging port maybe 3 months before the bootlooping so I assumed there might be a connection) but when I finally got there they told me it was software related and wouldn't look at it. Also, I don't want to make it sound like all my phones bootloop. I have had many many phones that died due to other issues and many more that are still in use, even old ones. I just want to try to understand and grasp any common factors that cause some phones to bootloop, and to maybe use that knowledge to prevent future phones from bootlooping even if I can't repair the ones that already do.
Thanks for your time in reading this and in advance for your answers. If you googled your way here, I hope there is info here that can help you too.