Hi,
Let me apologize in advance if this question seems familiar, my Google-fu is good and I've read hundreds of posts, thousands probably over the past year looking into this, so I'm finally posting out of well, not desperation exactly, but curiosity.
I have an S3 HTC One S, Ville C2 with TWRP recovery, (the only recovery that works), and Um let's see Luxandroid v4 giving Android v4.1.1 htc sense 4+ software version number 3.19.720.100
If I run the battery down, (I try not to), the phone won't start for a few days.
Well, not true, it is will start, it just won't display anything. I can run adb and see the phone, and it used to restart proper, display and all if I just rebooted it via adb.
That stopped. Now I have to wait until the battery is about 30% at least, this can take several days, start adb, give adb reboot, hold the volume up, and, justy lately, dance naked in the rain around a freshly made clay idol of the Gnome God, Jim, because it's a bit haphazard. (Obviously in the summer this is harder as it rains less.)
It's a completely robust phone the rest of the time, except for the occasional reboot when I've got all the mapping, phone, blue-tooth etc. on. It waits until I'm on the motorway to do this.
Main thing is, I thought it was related to some bug that I used to read about six months ago but which seems to have disappeared from searches. It's definitely is on, but the screen display isn't, "backlighting" isn't. (I know it's not back lit, but in the dark I can see very faintly that these is a display, of sorts).
Why is it doing this?
Can I put is back to stock reliably and would that work to stop this nuisance?
Is there a big words and picture version of putting it back to stock floating about somewhere and I've missed it?
Will I ever be able to put KitKat on it?
I'm not expecting instant answers or any answers, I just thought it was worth asking in the place where all the experts are. (Because I lurk here a lot, I screw up my Nexus 7 (2013) from time to time too).
I do program and teach for a living so I can follow reasonably complicated instructions.
Thanks,
Ania
Related
I've had the phone for a week without this happening, but yesterday when I went to check out the locations app it gave me some GPS error which I fixed up, but then decided I didn't want to use the app so I disabled the GPS satellite and dock feature when plugging in the phone for charging. Last night I realised this was happening a few times so I shrugged it off and just reset the phone which seemed to work for a bit, but then after leaving the phone on lock all night with no wi-fi, bluetooth, GPS or anything, I wake up to see the phone, after 8 hours of standby, to be at about 10% battery. Right now it's on charge, and a couple of minutes ago without touching it the screen turned on for exactly 1 minute.
At first I thought it was because of the locations app, but this doesn't seem to be the case since I force stopped it and it's still doing this.
What could be causing this? It's not that big of a hinderance, but when the phone quickly drains itself of battery because of it gets a bit annoying. Should I just wait it out for the android 2.4 update and hope it fixes itself? I was thinking of rooting the phone and going on from there to see if there's a method that'll fix it, but with the update coming in a couple of months I'd rather refrain from it (even though I have no idea what rooting would do in this situation).
e: locations seemed to have started itself up again. I think it IS the application doing this.
Boomey said:
I've had the phone.
Click to expand...
Click to collapse
Oh magic all knowing 8ball, what phone does he have?
*shakes magic 8ball*
*8ball glows and shows letters*
Plug your Moto RAZR into your computer, install android sdk, use adb logcat to read out the log files.
When your screen turns on again there will be some indication who requested your phone to wake up.
Sorry disregard that post. The Moto RAZR doesn't run android, so this can't be the solution...
I posted that in the HTC Desire HD Q&A forum, no idea why it was moved when it's a question about the phone. :\
But yeah, HTC Desire HD. I half expect no solution but I can still be hopeful.
In that case my suggested approach with adb logcat would work .
seems to be really very complicated and understand how to use the method. sorry im newbie
Not really there is a ****load of tutorial on the net how to install the android sdk.
Just use google.
Hello,
I read several threads over the span of five hours to still be left where I started (almost). I will explain the background to the situation I'm in; and the question will be clear towards the end.
A few days ago; my phone would not turn on UNLESS it was plugged in (wall/computer). I found this very unusual of course, and contacted Rogers. They explained that it would be a software or hardware issue; and to check if it's a software first.
I quickly backed up all my photos and things onto my computer, and began the Factory Restore tool. However; it did nothing besides clear me of all my apps; and settings (of course), yet I still remained at 2.3.3 Firmware.
Rogers continued to say to use Kies, and try to fix it through there. Then I completely forgot that my Infuse is with "EZUpdate" which is not even being picked up by the program itself which I later downloaded. I sat back in my chair to think for a bit, and thought; oh my goodness; a firmware update could have been a jail break I installed a few months ago (learning it's called Rooted for Androids). I instantly began looking online which led me to this site, and eventually learned that I can "un-root" my phone.
Now I'm in bigger trouble. PRIMARY QUESTION/CONCERN BELOW
I downloaded the GTG_s_Ultimate_Unbrick, and it actually worked. My phone turned on without the USB wire or anything. Then a sweat quickly rolled down the side of my face when I saw "AT&T" with a bright white screen. Shortly after it followed to the white "Samsung" with black screen background. After that, nothing else happens.
I am losing hours of sleep, and I work in three to four hours from now trying to figure out how to return this back to a Rogers phone.
Everything I'm trying from links like http://forum.xda-developers.com/showthread.php?t=1326143 and it's failing. I'm on the verge of tears that I have actually lost a phone that barely lasted me six months; and it's too costly to replace.
________________
Please help, I beg of you. If there is a solution; or a step by step process; please post here. I will get back to you as soon as possible when I return from work. I have already pinned my thread, and will be returning to it regularly.
Thank you very much for any future assistance, and have a wonderful day/evening in the meantime.
~ Yujiza
-.- go back to android development and download the rogers firmware. you used att firmware.
Sent from my SGH-I997 using xda premium
Yujiza said:
Hello,
I read several threads over the span of five hours to still be left where I started (almost). I will explain the background to the situation I'm in; and the question will be clear towards the end.
A few days ago; my phone would not turn on UNLESS it was plugged in (wall/computer). I found this very unusual of course, and contacted Rogers. They explained that it would be a software or hardware issue; and to check if it's a software first.
I quickly backed up all my photos and things onto my computer, and began the Factory Restore tool. However; it did nothing besides clear me of all my apps; and settings (of course), yet I still remained at 2.3.3 Firmware.
Rogers continued to say to use Kies, and try to fix it through there. Then I completely forgot that my Infuse is with "EZUpdate" which is not even being picked up by the program itself which I later downloaded. I sat back in my chair to think for a bit, and thought; oh my goodness; a firmware update could have been a jail break I installed a few months ago (learning it's called Rooted for Androids). I instantly began looking online which led me to this site, and eventually learned that I can "un-root" my phone.
Now I'm in bigger trouble. PRIMARY QUESTION/CONCERN BELOW
I downloaded the GTG_s_Ultimate_Unbrick, and it actually worked. My phone turned on without the USB wire or anything. Then a sweat quickly rolled down the side of my face when I saw "AT&T" with a bright white screen. Shortly after it followed to the white "Samsung" with black screen background. After that, nothing else happens.
I am losing hours of sleep, and I work in three to four hours from now trying to figure out how to return this back to a Rogers phone.
Everything I'm trying from links like http://forum.xda-developers.com/showthread.php?t=1326143 and it's failing. I'm on the verge of tears that I have actually lost a phone that barely lasted me six months; and it's too costly to replace.
________________
Please help, I beg of you. If there is a solution; or a step by step process; please post here. I will get back to you as soon as possible when I return from work. I have already pinned my thread, and will be returning to it regularly.
Thank you very much for any future assistance, and have a wonderful day/evening in the meantime.
~ Yujiza
Click to expand...
Click to collapse
Although after a little searching you would no doubt find this here is what you need:
http://forum.xda-developers.com/showthread.php?t=1326143
Thank you for the assistance you two!
I'm on the search for a retail version of gingerbread 2.3.3 for Roger's Infuse 4g.
Thanks once again,
~ Yujiza
Hi everyone,
I'm experiencing really wierd behaviour with my HTC Desire S. I'll try to tell the story as it happened, so you may have the best grasp on what's happening to me. Here's the thing: yesterday, I charged my HTC on the wall plug as almost every night (y'all know how it is with smartphones, always needing to be charged ). When I unplugged it on the morining, the green LED stayed on. Not cool. I can't really remember if it was turned on and stuck or already turned off at that time, but I had to reboot the phone. Okay, that can happen, phones have to reboot sometimes.
And then, it did not boot. Instead, it was stuck on the bootscreen. I looked around on the internets, but people seemed to have boot loops or devices stuck after the "quietly briliant" part. Actually, mine was stuck before that part. It didn't even play the funny sound and show the fancy animation: it was stuck on the blank screen with only the HTC logo.
I tried many things, like praying pagan gods and removing the battery, let it cool for a while, boot and wait to see what happens for more than 30 minutes, boot it while plugged on the wall plug... I think I was about to get to the "I'll have to make a factory reset, then" line when I tried to see what dmesg would tell me if I plugged the phone on my computer. Note to self: always try to plug to computer. It did boot completely. The victory dance was almost completed when I was invited to enter my PIN code. My touchscreen did not respond. Damn.
So I had to reboot. Again had to remove the battery (I don't like that, but what choice do I have?). Now it always boots completely (that's a good start), but my touch screen seems completely unresponsive. I can't access anything, can't enter my PIN code or unlock the phone when there's no SIM.
That's where this forum comes in: I've not given up. You see, my phone has USB debugging activated (yeah I know, the thread's title spoiled all the story). I'm pretty sure this means adb can help me in some way to troubleshoot my device. adb shell gives a nice UNIX-like shell, yay, that is relevant to my interests.
My phone has never been rooted. I've looked into it (that's why USB debuging was activated), but I wasn't 100% confident it would work, so I gave up before ending up bricking my phone (duh, too late, haha). It's running the last Gingerbread version distributed by HTC in Belgium (2.3.5, I think, without any certainty), with the last Sense version related (could it be 3.0.3?).
tl;dr: Unrooted phone with unresponsive touch screen, debugging mode enabled, trying to find what's wrong.
So here's what I'd like to know: is there any way to try to force start my touch screen with the help of adb? Where's the related log, the one that should display the error(s) that occur(s)? Should Bill Murray play in the next Batman? If root is needed, do I have a way to use a temproot exploit in order to fix my phone once and for all?
Any attempt to help will be greatly appreciated. This is my first post here, I hope it's clear enough, and not too nooby for you guys. Also, that I didn't break any rule (I watched/lauged at that video about noobs to xda). Btw, I'm quite confortable with UNIX shells, so don't avoid cli-related answers if that may happen to be helpful. Also, I'm not at home right now, but I'll follow this thread with a lot of interest anyways. I'm back on a regular connection next sunday.
Have a nice day! And sorry for the long post (but believe me, I'm even more sorry to admit I can't investigate further on my own, now that is frustrating).
Okay, I'm back.
It makes no sense. I let my phone on for a few days, then suddenly, probably out of boredom removed the battery, put it back and rebooted. I distractingly tried to unlock it… and it worked.
I have absolutely no single clue on what happened. And I'm still quite concerned, because this means it can happen again without any warning.
I'm gonna give a shot at HTC's support in order to ask them what I can do to locate the problem if there are traces. I'd really, really like to read all the logs (and logcat didn't show anything interesting).
If anyone has a suggestion, feel free to shoot it. I'll try to keep this thread updated in case someone has the same problem.
Duh, just got an anwser from HTC's support. Totally useless, they told me to try to reboot in Safe Mode in order to see if the problem happens again. Well, even in normal mode it has not failed for two days. GJ, guys.
I'm really willing to meddle in my system in order to see what could have gone wrong. I'd especially like to see if there is any way to see whether there are HW faults or not, since I'm suspecting a temporary TS chip failure, which can happen again at any moment. I'll be reading some documentation about Android's system and its logs.
Yeah, I know I'm talking a lot alone, but if someone ever has the same problem, he might be able to see what I've gone through, so I'm documenting as much as possible. =)
adb bugreport
Hi!
I have read a few threads about this general issue, but they are from a few months ago and wanted to see if anyone had new information.
Quick recap: Got into a hot tub/spa, that contained very chlorinated swirling hot water with my 1S in the pocket of my shorts. I was in anguish over the stupidity for days. First there was nothing (which was a horrible feeling because my 1S had survived a drop in the bathtub while it was on and it remained on after I took it out—I think there is something to say about non-removable batteries here!!), so first, realizing chlorine ions in the water would be far more corrosive than water alone, I flushed it with isopropyl alcohol (every vent and opening I could see)... Although C3H6OH dries rapidly, I ziploc'd it with a few bags of silica gel I found in some shoe boxes and let it dry for 36 hours. Then, just in case the silica gel was not working (the silica was old and I don't know if moisture in the air diminishes it's absorbtion ability), I left it out with the top back part off for 24 hours. After all of that I finally plugged it in, waited 5 minutes, and hit power. I got a perfect boot screen and animation, however, when I got to the home page, there was a bizarre horizontal scroll which reminded me very much of what bad TV reception used to look like. And then 3 seconds later it went black. But the LED light was on. So I left it for a few seconds, and heard a text message alarm... so I knew that only the screen was malfunctioning. Tried to reboot again, but this time screen did not illuminate at all. I decided to unplug and wait another 3 days, and then powered it, rebooted, and the screen illuminated perfectly again....until the home page where I saw the horizontal scroll and then seconds later it went black. I am slowly beginning to accept that whatever damage was done to the screen is permanent. [tl;dr: Screen not working, but phone is]
Mainly I have been apprehensive about calling Assurion because I had read so many reports they were impolite, uninformed, and careless. I thought if the 1S wasn't in stock, I might end up with an HTC One-V. Also my old phone had hboot 1.06, and I highly doubt this will be the case in a 1S replacement.
I think I read your could tilt the odds in your favor if you go online to file the claim and if they don't offer a 1S, to come back in a day and try again, and keep doing this until you get a 1S replacement. If true, this is good news. Secondly, is there a new bootloader that will prevent me from getting root, SuperCID, and S=off??
Basically, I just am looking for advice on dealing with Assurion... the only phone I want is a 1S (or maybe a Nexus 4..though I don't foresee this possibility), but I have to be able to install BakedBean (favorite ROM) or whatever is running the latest OS from Google/Android.... so I am just anxious. And just to confirm, as I am in Chicago/US, using TMO, there is no chance I will get the S3 chipset, right???
Any comments or responses are greatly appreciated!!
Paul
I can answer your second question. I S- offed from hboot 2.15. Now we're S-Off capable, the hboot issue is almost irrelevant.
I read that there were still some different things you can achieve with different hboots but if s-off it's a synch flashing a different one if you need to. Good luck with your claim.
Sent from my Liquid Smooth One S
ATSPerson said:
I can answer your second question. I S- offed from hboot 2.15. Now we're S-Off capable, the hboot issue is almost irrelevant.
I read that there were still some different things you can achieve with different hboots but if s-off it's a synch flashing a different one if you need to. Good luck with your claim.
Sent from my Liquid Smooth One S
Click to expand...
Click to collapse
Thanks.... that's good news.... I must have been a little out of the loop on how easy it has become because I was really dreading a replacement. So I'm glad to hear that.
So, there I was, eating dinner while my phone read me a book.* And suddenly, it stopped. Because my phone crashed. And the amount of a boot cycle it can get through before crashing has been decreasing ever since. A complicating factor: when I still thought it was possibly a software issue, I booted into recovery, and attempted to re-flash the OS (currently it's on 10.2.1). It crashed partway through the process.
On the off chance this was a humidity issue (and not having a lot of time to mess with it) I opened up the phone, removed battery, sim, sd and the small screws in the main body of the phone, and left it in a dry well ventillated place. Now it will get as far as the initial "samsung" splash screen the first time I've reinserted the battery, and won't boot at all beside that. (It's possible that the power button was behaving weirdly, but the phone's behavior was generally so erratic that I can't say that with confidence.) Also, sniffing at the keyboard there is ever so faint a smell of burnt electronics... maybe. Maybe just platicizers. (I've noticed a bit of
This is the same phone that had screen issues (assumed to be related to a small amount of water** though subsequent evidence suggested a loose connector as an alternative hypothesis) around the beginning of February. It's been fine ever since, discounting the occasional weird usb connectivity issues that seem to be common with this phone.
I'm pretty happy to take the phone apart, but other than a general decase everything and look for loose connectors or other obvious trouble, I'm not even sure where to begin. (Also, I have about twelve hours to put in an order if I want Amazon to send by a new phone by tomorrow. Which is kind of silly, but this is swiftly and impressively dead. And otherwise it'd be no phone until Tuesday, which wouldn't kill me, but which would annoy me mightily.)
Any thought regarding common problem areas for this phone? I'm hoping to be able to leave the lab early today, which should give me some hours of working time. Well set up for tools, always happy to have things to take apart.
* Text to speech is awesome, once you get used to the robo-voice.
** Really, not a lot - none of the moisure stickers showed anything, and I don't think it got into the main body of the phone.
The de-casing was fun, and yet there isn't an obviously damaged component. It was pronounced dead at 6:20 yesterday evening.
R.I.p.
Sent from my SGH-T699 using XDA Premium 4 mobile app
tylik said:
So, there I was, eating dinner while my phone read me a book.* And suddenly, it stopped. Because my phone crashed. And the amount of a boot cycle it can get through before crashing has been decreasing ever since. A complicating factor: when I still thought it was possibly a software issue, I booted into recovery, and attempted to re-flash the OS (currently it's on 10.2.1). It crashed partway through the process.
On the off chance this was a humidity issue (and not having a lot of time to mess with it) I opened up the phone, removed battery, sim, sd and the small screws in the main body of the phone, and left it in a dry well ventillated place. Now it will get as far as the initial "samsung" splash screen the first time I've reinserted the battery, and won't boot at all beside that. (It's possible that the power button was behaving weirdly, but the phone's behavior was generally so erratic that I can't say that with confidence.) Also, sniffing at the keyboard there is ever so faint a smell of burnt electronics... maybe. Maybe just platicizers. (I've noticed a bit of
This is the same phone that had screen issues (assumed to be related to a small amount of water** though subsequent evidence suggested a loose connector as an alternative hypothesis) around the beginning of February. It's been fine ever since, discounting the occasional weird usb connectivity issues that seem to be common with this phone.
I'm pretty happy to take the phone apart, but other than a general decase everything and look for loose connectors or other obvious trouble, I'm not even sure where to begin. (Also, I have about twelve hours to put in an order if I want Amazon to send by a new phone by tomorrow. Which is kind of silly, but this is swiftly and impressively dead. And otherwise it'd be no phone until Tuesday, which wouldn't kill me, but which would annoy me mightily.)
Any thought regarding common problem areas for this phone? I'm hoping to be able to leave the lab early today, which should give me some hours of working time. Well set up for tools, always happy to have things to take apart.
* Text to speech is awesome, once you get used to the robo-voice.
** Really, not a lot - none of the moisure stickers showed anything, and I don't think it got into the main body of the phone.
Click to expand...
Click to collapse
Get a new battery for it....had this issue before and placing new battery in it fixed my bootlooping and not being able to flash or get past samsung screen...the samsung batteries have an overcharge feature which has been known for causing errors such as this...