Related
From searching, it looks like tons of people are having random reboot issues with the HTC EVO. Let's make one thread to put everything so maybe we can figure this out.
Side note, it looks like the HTC desire has the same issue:
http://forum.xda-developers.com/showthread.php?t=676402&highlight=rebooting
So post what you've tried that hasn't worked.
If you think you have a solution, share
One thing I've noticed is it seems heat related.
I've installed temperatures monitors and it seems around 32 degrees Celcius is around when it reboots. It will reboot loop usually. This can be cured by pulling the battery and waiting for it to cool down, or just put it in the freezer for 4-5 minutes.
I've tried underclocking it with the screen dimmed way down, and running it without the back cover and it still overheats.
For me, the problem came out of nowhere. I had the device for over a month with heavy usage and no problems. My current GUESS is it must be a physical problem. Not enough thermal grease or something...
It looks like the HTC Desire users may be getting replacement motherboards to fix their issue.
Does the HTC EVO and Desire share parts?
From other threads it looks like:
Root or Stock - Doesn't matter
Radio version - Doesn't matter
Rom version - Doesn't matter
GPS Fix - Doesn't matter
GPS turned off - Doesn't matter
3G data, 4G data turned off - Doesn't matter
Hard Reset - Doesn't matter
Found this on the HTC Desire reboot thread:
Latest test list for HTC Desire RR (Random Reboot) problems:
-All phones with s/n HT03 to HT07 can get this problem (Minor problem from SH09 so far)
-Starts around 1.5 to 3 months after use
-Reboots get worse over time
-Firmware and android version doesn’t matter which you have
-Force apps2sd doesn’t matter if you use it or not
-PVT1 or PVT3 or whatever doesn’t matter
-Screen type, doesn't matter if you have AMOLED or SLCD
-There seems to be an antenna/radio/simcard issue also
-Overheating causes reboots too
-Reboot is not always temp related
-SD card size doesn’t seem to matter
-Having apps on SD or not doesn’t matter
-Size of files on SD doesn’t matter
-Rooted or not doesn’t matter
-Motherboard changed after repair doesn't always fix it
-Sim locked or not doesn't matter
-Provider doesn't matter(vodafone, kpn/hi, T-mobile etc all got it)
-Most likely hardware issue, sense flashing won’t fix it, yet changing motherboard will
-Restarting doesn't fix it
-Factory resetting doesn't fix it
-Changing/buying new battery Doesn’t fix it
-Using app killers or shutting down some services yourself doesn't help
-Leaving all settings on default doesn't fix it
-Plugged into car charger in the past doesn’t matter
-Hboot version probably doesn't matter (still not fully tested)
-Having a phone cover or not doesn’t matter
Click to expand...
Click to collapse
wifes phone has been doing it very bad...one that has never been rooted...
was going to root it and try new rom but seems to be a hardware issue.
any other comments on this subject?
My stock rooted Rom just rebooted for the first time today. I really don't rememebr what I was doing st the time....but this has never happened before. I assume there's no event log to check.
Sent from my PC36100 using XDA App
I had been facing this with increasing frequency. I got the phone on launch day, and the problem started over the last month, getting worse all the time. I agree with the OP that there does not seem to be any obvious cause -- sometimes it is heat related, sometimes not. Any time I push the phone (run psx4droid, or navigation + anything else), and sometimes even with lighter usage, like on a phone call. Unrooting did nothing to stop the problem.
After extensive searching, I found three possible causes: bad battery (I tried a new one and the problem continued, but this seems a good starting place), bad memory blocks, or bad processor.
I was unable to find any solution to this problem. I took my phone to Sprint today, and they told me that their tests didn't show a problem. Then I made it happen in front of them (launch navigation to anywhere, then a couple more apps, then boom, reboot) a couple times (really, after the first time, letting it turn back on pretty much caused it to happen again).
After that, they agreed to replace it. I do have the TEP, but they assumed that the problem was hardware related so I don't know if you have to have it for them to replace it.
Strangely, they gave me a white one as a replacement.
I haven't had any problems with the new (well, re-manufactured) one, and I hope it stays that way, but I guess only time will tell.
I'm currently experiencing the problem as well, funny thing is every time it happens, the phone is NOT in use, simply sitting on table or desktop in standby. This happens about once every two days.
Currently running rooted evio2 1.3.1
Wow, I was about to start this thread, when I saw this. I guess I was like 10 minutes late. Either way, i believe something messed with the hardware. My little bro cracked my screen badly, so I am getting a new evo anyway, but will I be able to get one free bcuz of this? This is really a terrible problem. Somebody needs to de-assemble their precious evo and see if there is an obvious problem. thanks a bunch. Subscribing.
same here.
happens mostly when on the charger and i am using it at the same time. so heat related seems likely.
can anyone get a logcat of it happening?
I called sprint support and they said it's defective to return it.
Taking it in for replacement today.
Sprint replaced mine for $35 [a refurb]. That's the end of that.
But now, I can only use the speaker to hear my callers. Gotta go back and get another!
My guess is the new update could be putting a lot of strain on the battery but who knows? I haven't experienced it but maybe its because I'm using the extended mah 3500 seido battery.
Sent from my PC36100 using Tapatalk
thlinx said:
My guess is the new update could be putting a lot of strain on the battery but who knows? I haven't experienced it but maybe its because I'm using the extended mah 3500 seido battery.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
No, I've got the 3500mAh Seido battery too.
I don't think it's strain since mine has gotten worse. AKA the amount of usage it take to make the phone reboot has gone from hours of use to minutes.
.jond said:
No, I've got the 3500mAh Seido battery too.
I don't think it's strain since mine has gotten worse. AKA the amount of usage it take to make the phone reboot has gone from hours of use to minutes.
Click to expand...
Click to collapse
Actually I just had a reboot lol.
Sent from my PC36100 using Tapatalk
Same thing here. I posted my issue in the rom threads i used, and everyone ignored the issue, lol.
For me, I noticed it about a week after using roms with the new software update (3.29). It happened with navigation, launching multiple apps, running quadrant, etc.
So yesterday I installed DC 3.5 from scratch, turned nav on and let it sit for a couple of hours. NO reboots. Before, after 10 mins of the screen and nav being on, I'd get a reboot. Has anyone else tried this (or willingly to try it)? I switched back to my nand backup, ran quadrant -> bam, reboot.
I bought my EVO on launch day (HW Version 002), and have not had any problems until around Oct 13.
I took the phone on a trip to Orlando, and as soon as I got off the plane and turned on the phone, the problems started happening. It has been happening ever since, even since I returned home.
I bought my phone at Best Buy, and have had their Geek Squad send it back to try to fix it. I also added the complaints about screen separation to the workorder so that they would be more likely to replace the device. Hopefully, this fixes the issue.
I also think it is heat related, but I don't know why it is just now becoming an issue. Just to make sure the folks at BB could see the issue happening, I put the phone in front of my car's heater for a few minutes, then started up Google Earth, and was able to make the phone start boot looping while I walked into the store.
I tried hard reset, soft reset, update prl, underclocking, GPS Reset, new battery, new SD Card, and none of those things worked. I wonder if the removal of the 30 fps limit in the last update caused some type of heat damage?
I just had a reboot last night while trying to look at a picture I'd just taken in the Camera app on CM6.0.0. Only the 2nd or 3rd time it's happened. Still annoying though. Hope it doesn't get worse.
.jond said:
I called sprint support and they said it's defective to return it.
Taking it in for replacement today.
Click to expand...
Click to collapse
How much they charged you?
Sent from my PC36100 using XDA App
MedSchool26 said:
Same thing here. I posted my issue in the rom threads i used, and everyone ignored the issue, lol.
For me, I noticed it about a week after using roms with the new software update (3.29). It happened with navigation, launching multiple apps, running quadrant, etc.
So yesterday I installed DC 3.5 from scratch, turned nav on and let it sit for a couple of hours. NO reboots. Before, after 10 mins of the screen and nav being on, I'd get a reboot. Has anyone else tried this (or willingly to try it)? I switched back to my nand backup, ran quadrant -> bam, reboot.
Click to expand...
Click to collapse
I reset mine back to stock. Unrooted it and everything.
Didn't fix the issue for me.
Now I did try erasing all the stuff that's erasable inside recovery and it seemed to go a few days without a reboot. Not sure if that was a fluke or not.
Hello everyone. First of all, I want to write a small disclaimer saying that I have already searched multiple forums in order to find specific answers to my questions, but haven't managed to find the answers I needed. Furthermore, I am a first-time user on XDA so I also wanted to say Helloooo!!!
Here's the story. Two-days ago I have purchased an HTC One X from Orange, so it's the Tegra 3 international version. I need to point out that this is my very first smartphone. I haven't owned one until now because I felt like all I needed was a small box to speak in. However, times change and I am finally living in the present .
Needless to say, I love this device. However, I have a few questions regarding the handset, and handsets in general.
- First, the temperature. I have searched forums and I have learned that some smartphones get hotter than other, and that it's a normal thing. However, since I am not used with a hot device in my hands (literally and figuratively) it got a bit scared and I have searched the web for answers. The thing is, I wasn't able to find what is the exact safe-zone for this specific device. Keep in mind that this is a Tegra 3 version, and from my understanding Tegras it gets hotter than Snapdragons. Also, I have noticed that on many threads and forums, people mix-up battery and CPU temperatures…I simply want a clear answer. I want to know the safe-zone for both the CPU and battery, separately.
As a side note, I don't really care if the device feels warm in my hands when running demanding apps and games (normally the device is quite cool). However I am afraid I will damage the device if I play heavy 3D games….I don't want that to happen.
I was also wondering whether or not it's safe to use the phone with a protective case on, like otterbox defender. Wouldn't that rubber make the temperatures even higher?
====
- Second question: I ran StabilityTest because I got paranoid and I wanted to see if my device was stable. I ran the first CPU test (unrooted) for about 15 minutes and got no errors. However, I have noticed that on screen it said the cores run at 1,000 MHz…Wasn't this supposed to run at 1,5 Ghz?
=====
- Third. I have also learned yesterday evening that some HTC One X units have a screen ripple issue…I tested mine and indeed I have the same problem.
However, it slightly ripples mostly on the left side. The thing is, it doesn't bother me because it only ripples if I press the glass on its very edge, and I can't see a reason why I would do that when using the device normally. I admit, I haven't pressed too hard because I really like the device and I don't want to damage it.
So what I was wondering is this. Is it normal for every One X to get this ripple effect? I have searched an older thread somewhere, and opinions were mixed. People have said that as long as it doesn't affect the rest of the screen, it's normal. Others (probably those owning another device) claimed it's not normal and the owners should replace the device.
However, the thread was a few months old and I wanted to get some newer answers. Has HTC answered this issue? Is it or is it not normal? I mean, I know no ripples > some ripples, but still. Is it dangerous? Will the problem get worse with the passage of time?
The thing is, someone claimed they have returned the device only to get an even worse one…I am not bothered by how my display ripples. It's nothing annoying, so as long as everything remains the way it is, I see no reason to return the device.
Will it get worse in time…?
Also, is the HTC One X the very first device to experience this issue? If not, how did the situation developed for other handsets experiencing ripple issues?
====
- Lastly, some people claimed that a certain update addressed a certain overheating issue. I am running software version 1.29.401.11 and it says I'm up to date (again, international version). Was this bug-fixing update released on the international version already, or am I running a version that overheats my device? Or, was this problem present on the international version to begin with?
Thank you so much for having the patience of reading my wall of text. I apologize if any information was already out there, I simply couldn't find the answers I needed. Well, I found some.
Regards,
Neevar.
i really want to thank you for asking these questions. many of my questions will be answered too. i am waiting for the latest batch coz i believe i will get a perfect HOX. my basic issue is battery life is short. dint you face any problem like that? or wifi problem?
anyways. i am using N900. it is the most hackable device. i do many hacking and testing with it. can all these be possible with HOX. i am sorry but HOX will be my first android device so i know very little about android.
1) is it possible to hack WEP and WPA (with dictionary) wifi network?
2) is there MDK3 for android?
3) dsniff, dnspoof, etc
4) MITM attack.
if i buy HOX i will really miss my N900 for all these. is it possible to use them in android?
muid02 said:
i really want to thank you for asking these questions. many of my questions will be answered too. i am waiting for the latest batch coz i believe i will get a perfect HOX. my basic issue is battery life is short. dint you face any problem like that? or wifi problem?
anyways. i am using N900. it is the most hackable device. i do many hacking and testing with it. can all these be possible with HOX. i am sorry but HOX will be my first android device so i know very little about android.
1) is it possible to hack WEP and WPA (with dictionary) wifi network?
2) is there MDK3 for android?
3) dsniff, dnspoof, etc
4) MITM attack.
if i buy HOX i will really miss my N900 for all these. is it possible to use them in android?
Click to expand...
Click to collapse
First of all, thanks for arranging all these questions in nice manner.
I'll surely keep track of this thread, as I'm also having similar doubts, which are not yet clear even after reading many threads and posting threads....
Looking forward to buy a new HOX here, preferebly from latest batches....
And a kind request to members those who are replying;
kindly give an unbiased opinon, and pls dont mix up any other issues...
muid02:- buddy, Please read what the thread is for....dont mix up unnecessay issues here, like your N900, adroid and other stupid stuffs...If you want clarification in those issues, start a new thread....
Neevar said:
Hello everyone. First of all, I want to write a small disclaimer saying that I have already searched multiple forums in order to find specific answers to my questions, but haven't managed to find the answers I needed. Furthermore, I am a first-time user on XDA so I also wanted to say Helloooo!!!
Here's the story. Two-days ago I have purchased an HTC One X from Orange, so it's the Tegra 3 international version. I need to point out that this is my very first smartphone. I haven't owned one until now because I felt like all I needed was a small box to speak in. However, times change and I am finally living in the present .
Needless to say, I love this device. However, I have a few questions regarding the handset, and handsets in general.
- First, the temperature. I have searched forums and I have learned that some smartphones get hotter than other, and that it's a normal thing. However, since I am not used with a hot device in my hands (literally and figuratively) it got a bit scared and I have searched the web for answers. The thing is, I wasn't able to find what is the exact safe-zone for this specific device. Keep in mind that this is a Tegra 3 version, and from my understanding Tegras it gets hotter than Snapdragons. Also, I have noticed that on many threads and forums, people mix-up battery and CPU temperatures…I simply want a clear answer. I want to know the safe-zone for both the CPU and battery, separately.
As a side note, I don't really care if the device feels warm in my hands when running demanding apps and games (normally the device is quite cool). However I am afraid I will damage the device if I play heavy 3D games….I don't want that to happen.
I was also wondering whether or not it's safe to use the phone with a protective case on, like otterbox defender. Wouldn't that rubber make the temperatures even higher?
====
- Second question: I ran StabilityTest because I got paranoid and I wanted to see if my device was stable. I ran the first CPU test (unrooted) for about 15 minutes and got no errors. However, I have noticed that on screen it said the cores run at 1,000 MHz…Wasn't this supposed to run at 1,5 Ghz?
=====
- Third. I have also learned yesterday evening that some HTC One X units have a screen ripple issue…I tested mine and indeed I have the same problem.
However, it slightly ripples mostly on the left side. The thing is, it doesn't bother me because it only ripples if I press the glass on its very edge, and I can't see a reason why I would do that when using the device normally. I admit, I haven't pressed too hard because I really like the device and I don't want to damage it.
So what I was wondering is this. Is it normal for every One X to get this ripple effect? I have searched an older thread somewhere, and opinions were mixed. People have said that as long as it doesn't affect the rest of the screen, it's normal. Others (probably those owning another device) claimed it's not normal and the owners should replace the device.
However, the thread was a few months old and I wanted to get some newer answers. Has HTC answered this issue? Is it or is it not normal? I mean, I know no ripples > some ripples, but still. Is it dangerous? Will the problem get worse with the passage of time?
The thing is, someone claimed they have returned the device only to get an even worse one…I am not bothered by how my display ripples. It's nothing annoying, so as long as everything remains the way it is, I see no reason to return the device.
Will it get worse in time…?
Also, is the HTC One X the very first device to experience this issue? If not, how did the situation developed for other handsets experiencing ripple issues?
====
- Lastly, some people claimed that a certain update addressed a certain overheating issue. I am running software version 1.29.401.11 and it says I'm up to date (again, international version). Was this bug-fixing update released on the international version already, or am I running a version that overheats my device? Or, was this problem present on the international version to begin with?
Thank you so much for having the patience of reading my wall of text. I apologize if any information was already out there, I simply couldn't find the answers I needed. Well, I found some.
Regards,
Neevar.
Click to expand...
Click to collapse
Temperature - it does get hot. A lot of people say don't play games whilst charging the device, as it will get hotter.
I personally don't believe in this. The phone should have safeguards (similar to a PC) to specifically stop it overheating - infact it does, when it gets too hot, it stops charging. If it overheats and dies (which is a big if, i've certainly not heard of anyones hox dying from overheating), then this would be covered under warranty anyway. Which I believe is 2 years. It would be reallllly stupid for HTC not to test for heat issues before release. I'm sure they had a fleet of devices all running stress tests just to make sure they didn't melt.
I don't know the 'safe zones' all i know is that HTC confirmed that reaching a temperature of 55c is normal and nothing to worry about. I have since read of people reaching higher temps (72c) but I don't think even that had any adverse effects
The CPU underclocks itself for power saving. This is a separate feature from the companion core. This can be modified, you have to create a shortcut (easiest way is to use minimalistictext, and create a widget, that on tap will open the power saving settings shortcut.) It does run at 1500 however. You haven't been conned at least
Most hox's i've had (6 in total) had the screen ripple, the general rule on whether it is normal or not - if you have to push really hard to get it to ripple, then it's fine. It's only when it ripples on a very gentle touch that you might want to get it replaced/repaired. (a gentle touch does fall into normal use, and this ripple imo shouldn't happen under normal use.)
Do be sure that if you send back the device, that it IS a hardware problem, and that it is a bad enough issue to warrant possibly getting another, but worse problem. Note that I've been through 6 hoxs, each one of them with different (and some of the same) problems. The 6th one, is also defective, and is due to be replaced soon.
I don't believe the HOX is the first device to suffer from screen ripple. My DHD did it. The difference was i had to push unbelieveably hard to make it happen the slightest bit. So clearly there is some sort of design flaw here, particularly on those hoxs that just need a slight touch for it to happen.
Regarding the update that addresses overheating, somebody correct me if I'm wrong, but i think thats the 2.05 update, which hasn't been officially released yet, only leaked. You can install a custom rom with the 2.05 base, but otherwise just be patient and we shall soon have the update OTA.
Hope this helps
lawrence750 said:
Hope this helps
Click to expand...
Click to collapse
Thank you so much for the detailed reply Lawrence. Your feedback really cleared some things in my mind.
Regarding the temperature, I have never seen the LEDs go red or anything like that. It just feels warm, that's all. I just checked the temperatures and right now while idling it shows 39 degrees, but considering the fact that my room temperature is around 33 degrees, I suppose that's a good value (yeah, AC broke, I run a big fan in my face lol). While playing GTA 3 for about 30 minutes last night the temps reached 50 degrees. I have seen older posts claiming that 50 degrees is really bad, but those posts were after or even before the handset launched in certain regions, and most people claiming this were comparing the One X with their own handset. Now that you've said HTC confirmed that 55 is a normal temperature, I think mine performs quite well to be honest...
Note* I haven't played while charging.
About the screen ripple. It doesn't happen on normal use. but if I focus in holding my fingernail on the very edge of the screen and drag it from top to bottom, i do see faint ripples. as I've said, it doesn't bother me as long as it won't get worse... do you have any idea if it can get worse somehow with the passage of time?
I am rather afraid to replace it since yes, I might end up with an even worse unit... so, for me at least it all depends on whether or not the ripples can get worse or if it can damage my display in time. I really don't know what to do here...I certainly don't want to replace my phone for more than one time...
Since you already replaced your HTC One X 5 times now, can you tell me how the process works? Will they replace my phone at the Orange store or do they need to check on it for a frikin week before deciding to give me another?...
Regarding the update, if it's not out then I'll just wait. Considering the fact that according to HTC my temps are in check, and considering the fact that I never got a warning and / or reboot, I should be safe, I hope.
Neevar said:
Thank you so much for the detailed reply Lawrence. Your feedback really cleared some things in my mind.
Regarding the temperature, I have never seen the LEDs go red or anything like that. It just feels warm, that's all. I just checked the temperatures and right now while idling it shows 39 degrees, but considering the fact that my room temperature is around 33 degrees, I suppose that's a good value (yeah, AC broke, I run a big fan in my face lol). While playing GTA 3 for about 30 minutes last night the temps reached 50 degrees. I have seen older posts claiming that 50 degrees is really bad, but those posts were after or even before the handset launched in certain regions, and most people claiming this were comparing the One X with their own handset. Now that you've said HTC confirmed that 55 is a normal temperature, I think mine performs quite well to be honest...
Note* I haven't played while charging.
About the screen ripple. It doesn't happen on normal use. but if I focus in holding my fingernail on the very edge of the screen and drag it from top to bottom, i do see faint ripples. as I've said, it doesn't bother me as long as it won't get worse... do you have any idea if it can get worse somehow with the passage of time?
I am rather afraid to replace it since yes, I might end up with an even worse unit... so, for me at least it all depends on whether or not the ripples can get worse or if it can damage my display in time. I really don't know what to do here...I certainly don't want to replace my phone for more than one time...
Since you already replaced your HTC One X 5 times now, can you tell me how the process works? Will they replace my phone at the Orange store or do they need to check on it for a frikin week before deciding to give me another?...
Regarding the update, if it's not out then I'll just wait. Considering the fact that according to HTC my temps are in check, and considering the fact that I never got a warning and / or reboot, I should be safe, I hope.
Click to expand...
Click to collapse
I don't think the ripple gets worse over time, I can't say for sure really because I haven't had one long enough to see, however I can say that it does appear to be the way they are assembled that causes the issue, and its that that defines how bad the ripple is, rather than it getting worse over time.
My most recent hox, didnt have very bad ripple, and now after 'repair' it does, and also has a dead pixel in a different place. I suspect they actually replaced the screen, and it so happens that this screen has bad ripple. The other one didn't.
If I could find out for definite what they did it would kinda confirm whether the ripple gets worse over time or not, but they didn't log anything about the repair (tracking site never updated) and HTC can't tell me anything other about it than 'we're still waiting for it in repair center'
The replacement process (this applies to UK):
Sales of goods act states that if there is a fault with the device, in the first 6 months after purchase, it is the retailers responsibility to repair, replace, or refund the purchase, unless the retailer can prove that you caused the fault yourself.
If the repair option is chosen, then this mustn't significantly inconvenience the buyer. IE if they send it back unrepaired, they don't really have a choice from then, other than to replace it or refund you.
However there is also a cooling off period.
http://whatconsumer.co.uk/cooling-off-and-cancellations/
Depending on whether you bought the phone from an Orange shop (from actually within the shop) or bought it via internet/phone/mail, it differs slightly.
I'm pretty sure you don't actually
If you bought it online, or by phone, but not in the shop, then you will have a 7 day cooling off period, from the conclusion of the contract
If the service was activated before the 7 day cooling off period, then you have given up the right to a cooling off period, but this must have been clearly communicated and with your agreement.
Orange must also send you written confirmation of the contract and any other additional information applicable. If this doesn't arrive within the 7 days, but before 3 months after purchase, then the cooling off period doesn't start until these confirmations have arrived.
Assuming you're out of this 7 day period, and also assuming that you haven't accepted the goods yet(see below) then you can reject the goods if they aren't as described, fit for purpose, or aren't of satisfactory quality.
Customers are considered to have accepted goods when they:
tell you they have accepted them
alter them
keep them for a reasonable length of time - this varies according to the nature of the goods
Click to expand...
Click to collapse
I'm just looking for the cooling off period when bought in a shop, but my head hurts lol, if you do a bit of searching on google should come up fairly easily
Even if there isn't a cooling off period, which you don't need a reason to cancel, then you can reject the goods as mentioned above, on the basis they aren't of satisfactory quality, and in this instance orange will possibly replace, but they aren't obliged to at this point. Appeal to their goodwill, but they may well insist on sending it for repair.
I have read before than if CPU ran at 80 + degree every time then it can last for 2 years , so no worries about heat guys. The money which we have paid is worth.
Sent from my HTC One X using Tapatalk 2
forumhookersdotcom said:
I have read before than if CPU ran at 80 + degree every time then it can last for 2 years , so no worries about heat guys. The money which we have paid is worth.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
But can the adjacent components withstand that heat emitting from the CPU?
Sent from my HTC One X using xda premium
stuart0001 said:
But can the adjacent components withstand that heat emitting from the CPU?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
they use the foil layer to spread the heat over the device, so yes i expect that any nearby components would be fine.
I'm starting to get pissed off.
I got in touch with an HTC technical agent via their online form, and I have received an email where the agent told me that the battery temperature should not go over 50 degrees Celsius. If that happens, then he advised me to return the phone immediately.
He also said that ripples are not normal and once again, I should return the phone.
So I ran Glowball for about 20 minutes and my battery has gone up to 61 degrees Celsius....
I decided to take my phone back to the store where I have bought it. Those dudes raised their shoulders and told me to go to the company that deals with warranties in order to get a paper, then return to them.
I asked them if I can cancel my contract and get a refund, but no, apparently it too much time has passed since I made the purchase.
I have called the company and a clueless lady answered then cut me off mid-sentence when I started talking about technical stuff. She was clearly clueless but asked me if I have been at the store with my phone...derp...
Then she told me that I should go there on monday and see what's what....
What an incompetent way of doing things. I am 99% certain that I won't go anywhere with these monkeys, either that or I'll waste at least a whole month trying to get a hold of a HOX that works as intended.
This being my very first smartphone, I am very disappointed and I'm fearful I have just got myself a two year contract with a carrier, for a phone that doesn't work and with which I'll probably stuck with because of these idiots.
And by the way, why hasn't HTC recalled or announced every carrier and company that deals with warranties that every phone that has ripple and overheat issues need to be recalled and replaced as soon as someone like me shows up in their store with a faulty device in their hands???
htc one x cpu and battery
Hi,
I have the following problem:
I have a HTC One X and have the BinDroid 5.0.0 Rome installiert.Der battery goes down quickly and the system hangs, no matter what I want ... the problem was with Coredroid V4.0 and BinDroid 4.0.0 already ... Not even in Whatsapp I can write without it hangs and the battery will not work correctly if it depends on the charger as soon as I use some program ... no matter what, whether whatsapp or other app's ... in the car when it depends on the charger, it produces the error message "Unable to load, the unit will be more current than the charger can charge" <- something like that ^ ^
now my question: it may be that generally run all CPUs instead of one CPU and the other can be switched on when it is necessary, as it should be normal, according to HTC?
What can or should I do that my HTc one x fluent running again?
Am very satisfied with BinDroid and in my opinion is the best ROM for the HTC One X
Simply stated, I am seeking a way to make this device a dependable phone, as I am stuck with it at the time being. I loved my original GNex, but what Verizon keeps sending me is garbage.
I have had quite a strand of bad luck with this device. I am averaging a warranty phone about once every six weeks. I have actually tried talking to Verizon about exchanging the phone for one of equal or comparable value, and they won't do anything. I am convinced that these certified like new devices are junk.
Issues that keep causing me to warranty the phone are:
- Charging Issues
The phone quits accepting a charge. I have replaced the battery.
- Phone Locking Up
Recently, while using apps, the phone has developed a habit of where it locks up, and the quits accepting input. It's like it goes to sleep, but it doesn't wake up. The only way to get it to function is to remove and reinsert the battery.
- Phone turning off on its own
Self Explanatory
- Radio Failure within the device
I'm not against rooting the device, I have kept them stock, and wouldn't know what to get, I just want to do something that will make this a dependable device and possibly solve any problems I may be having. They seem to be reoccurring problems with each handset they send me Any tips would be greatly appreciated as I have another one due to arrive tomorrow!
I don't think these refurbished headsets go through much, if any, testing before they are re-issued. What I would suggest is to begin with flashing a factory android image via the boot loader. There are plenty of guides to doing this. This step will ensure that any problems that you may be experiencing are not software related. A stock image reflag should do the job for the most part, but if you find yourself looking for more you can flash an alternate ROM, these won't solve any issues that you may still experience in a stock ROM however.
The best part about spending 30 minutes typing a post is having your browser crash. Anyway, if you have any further questions because this is going to be a bit brief, let me know.
My background: Fairly well-versed in Android, custom ROMs, flashing, rooting, doing development work on Android, reading directions, decent google-fu and RTFMing. But I really need help on this one. The phone in question is my primary phone, which I actually like to keep as stock because I don't want anything mucking up on it. It's 20 months old (daily usage), running stock 4.1.1, which was rooted about 17 months ago with cf autoroot, which I needed for development purposes. For the past 10 months, I have been using an extended aftermarket battery, because when traveling and thusly using navigation, gtranslate, lots of messaging, and whatnot with a bright screen whilst outdoors, I was tired of having my phone leave me without a communications device at 8pm.
Recent changes to phone: Several weeks ago, before another bout of traveling, I did my usual *#197328640# perso256 disable (one of the reasons that I like keeping my phone at 4.1.1), and voila -- carrier unlock.
What happened: Things were going swimmingly for a few weeks, when one day, I was out and about, typing something into google translate, and the screen just went black. It was early midday, and the phone was at 90% battery (extended battery life ftmfw). Every now and then, when doing serious multitasking (and, mind you, since the early days of owning this phone, as well as through the entire life of my GS1, which still works, by the way), my GS3 would occasionally reboot of its own accord. I thought nothing of this, except it just being a hallmark of samsung phones, and a minor inconvenience, at worst. This time, however, it failed to power back on. I removed the battery, held in power button in an attempt to discharge any residual power, and put the battery back in. Nothing. Panic. No ssung logo, no vibration, no lights, nothing. Just the black screen staring back at me. There was no moisture, and no trauma to the phone... nothing, save for a ridiculous sinking sensation.
Symptoms: Phone completely unresponsive. I tried a charged stock GS3 battery, and the symptoms are the same. If I plug the phone in without a battery, the led lights up red for a time, and that's it. Even though I haven't modded this phone at all, with the exception of the rooting almost 2 years ago, I tried everything I could think of and read online. vol up + power + home. vol down + power + home. Leaving the battery out for a while. So much reading through these forums and some others online. When I plug it in in windows (even though I primarily use linux), I get the QHSUSB_DLOAD problem, so I do not think it is a problem with the power button? Or maybe the power button can be permanently depressed or something that would cause this? Anyway, I've installed QHSUSB_DLOAD windows drivers, but don't want to start flashing things until I know there isn't another longshot option to get this to work. I even loaded up linux and ran pblclear, which allegedly attempts to knock HTC phones out of being stuck in QHSUSB_DLOAD mode. Didn't work, but figured it was worth a shot, and seemed relatively harmless.
Why I don't even know if it's SDS: The reason I'm asking this is because I'm completely at a loss. SDS appears to affect i9000s after 150-200 days, OR when people incorrectly flash a ROM, or something happens during flashing or modification. My phone is an ATT i747 has been fully operative for 600+ days, and I haven't done any flashing, rooting, whathaveyou in nearly two years (and it was just that simple autoroot that I ran once).
What I'm wondering: I really want to get this phone working, because of hundreds of images, notes, data, etc. that I have accrued over the past few years. Most of my videos and larger files were on my sd card, but literally hundreds of memories and works in progress that I would do insane things for were saved to the phone. I'm an idiot for not backing it up, but I wasn't doing anything to the phone, so wasn't expecting such a catastrophe. Will JTAG work? What about a debricking microsd image? Most of the ones I can find are for 4.1.2 or 4.1.3 -- are there any for 4.1.1? I'm nearly certain 4.1.1 is my version, because IICR 4.1.2 and 4.1.3 don't even have the perso256 disable menu, and it's why I had not upgraded to them. It seems like the microsd rewrites would wipe the contents, and then I would have to quickly attempt a recovery on the data? Or have there been any cases with similar failures that are something else dying on the board? To be perfectly honest, if it appears to be an issue with the board, it's not beyond my ability to perform BGA rework and remove the emmc entirely, and transplant it onto a new board, but I would ///really/// like to avoid that.
Thanks for reading... :angel:
Edit:
Additional information: I forgot to mention that I have found pages such as this samsung-galaxy-s3-sgh-i747-i747m-repair-dead-boot-1755452 [I'm afraid you'll have to google it because I can't post links if you want to look TT^TT] which have files that say, for example, "Samsung SGH-I747 Repair Boot Supported" if using JTAG. So, if there aren't suggestions about how I can fix my phone with an sdcard unbrick, or something else, does anyone know whether or not doing a boot repair will unbrick a phone without wiping the ROM itself? Thanks again~~
Top5a said:
The best part about spending 30 minutes typing a post is having your browser crash. Anyway, if you have any further questions because this is going to be a bit brief, let me know.
My background: Fairly well-versed in Android, custom ROMs, flashing, rooting, doing development work on Android, reading directions, decent google-fu and RTFMing. But I really need help on this one. The phone in question is my primary phone, which I actually like to keep as stock because I don't want anything mucking up on it. It's 20 months old (daily usage), running stock 4.1.1, which was rooted about 17 months ago with cf autoroot, which I needed for development purposes. For the past 10 months, I have been using an extended aftermarket battery, because when traveling and thusly using navigation, gtranslate, lots of messaging, and whatnot with a bright screen whilst outdoors, I was tired of having my phone leave me without a communications device at 8pm.
Recent changes to phone: Several weeks ago, before another bout of traveling, I did my usual *#197328640# perso256 disable (one of the reasons that I like keeping my phone at 4.1.1), and voila -- carrier unlock.
What happened: Things were going swimmingly for a few weeks, when one day, I was out and about, typing something into google translate, and the screen just went black. It was early midday, and the phone was at 90% battery (extended battery life ftmfw). Every now and then, when doing serious multitasking (and, mind you, since the early days of owning this phone, as well as through the entire life of my GS1, which still works, by the way), my GS3 would occasionally reboot of its own accord. I thought nothing of this, except it just being a hallmark of samsung phones, and a minor inconvenience, at worst. This time, however, it failed to power back on. I removed the battery, held in power button in an attempt to discharge any residual power, and put the battery back in. Nothing. Panic. No ssung logo, no vibration, no lights, nothing. Just the black screen staring back at me. There was no moisture, and no trauma to the phone... nothing, save for a ridiculous sinking sensation.
Symptoms: Phone completely unresponsive. I tried a charged stock GS3 battery, and the symptoms are the same. If I plug the phone in without a battery, the led lights up red for a time, and that's it. Even though I haven't modded this phone at all, with the exception of the rooting almost 2 years ago, I tried everything I could think of and read online. vol up + power + home. vol down + power + home. Leaving the battery out for a while. So much reading through these forums and some others online. When I plug it in in windows (even though I primarily use linux), I get the QHSUSB_DLOAD problem, so I do not think it is a problem with the power button? Or maybe the power button can be permanently depressed or something that would cause this? Anyway, I've installed QHSUSB_DLOAD windows drivers, but don't want to start flashing things until I know there isn't another longshot option to get this to work. I even loaded up linux and ran pblclear, which allegedly attempts to knock HTC phones out of being stuck in QHSUSB_DLOAD mode. Didn't work, but figured it was worth a shot, and seemed relatively harmless.
Why I don't even know if it's SDS: The reason I'm asking this is because I'm completely at a loss. SDS appears to affect i9000s after 150-200 days, OR when people incorrectly flash a ROM, or something happens during flashing or modification. My phone is an ATT i747 has been fully operative for 600+ days, and I haven't done any flashing, rooting, whathaveyou in nearly two years (and it was just that simple autoroot that I ran once).
What I'm wondering: I really want to get this phone working, because of hundreds of images, notes, data, etc. that I have accrued over the past few years. Most of my videos and larger files were on my sd card, but literally hundreds of memories and works in progress that I would do insane things for were saved to the phone. I'm an idiot for not backing it up, but I wasn't doing anything to the phone, so wasn't expecting such a catastrophe. Will JTAG work? What about a debricking microsd image? Most of the ones I can find are for 4.1.2 or 4.1.3 -- are there any for 4.1.1? I'm nearly certain 4.1.1 is my version, because IICR 4.1.2 and 4.1.3 don't even have the perso256 disable menu, and it's why I had not upgraded to them. It seems like the microsd rewrites would wipe the contents, and then I would have to quickly attempt a recovery on the data? Or have there been any cases with similar failures that are something else dying on the board? To be perfectly honest, if it appears to be an issue with the board, it's not beyond my ability to perform BGA rework and remove the emmc entirely, and transplant it onto a new board, but I would ///really/// like to avoid that.
Thanks for reading... :angel:
Edit:
Additional information: I forgot to mention that I have found pages such as this samsung-galaxy-s3-sgh-i747-i747m-repair-dead-boot-1755452 [I'm afraid you'll have to google it because I can't post links if you want to look TT^TT] which have files that say, for example, "Samsung SGH-I747 Repair Boot Supported" if using JTAG. So, if there aren't suggestions about how I can fix my phone with an sdcard unbrick, or something else, does anyone know whether or not doing a boot repair will unbrick a phone without wiping the ROM itself? Thanks again~~
Click to expand...
Click to collapse
same thing just happened to my 20 month old att s3.i unlocked the bootloader and flashed a twrp recovery.the phone was on 4.1.1 and rooted.
now just a lifeless phone
thorur said:
same thing just happened to my 20 month old att s3.i unlocked the bootloader and flashed a twrp recovery.the phone was on 4.1.1 and rooted.
now just a lifeless phone
Click to expand...
Click to collapse
Did it die closely after the unlocking/flashing? Or a long time after? Or was the unlocking/flashing an attempt to save the phone? Ever get it fixed? I'm so anxious!
I never heard of qualcomm chips doing this. There is a app called emmc brickbug check on the market though it won't be of much use to you now.....but it allows you to check the mem. Controller chip and check if its a "sane chip" and allows you to probe the memory for any bad sectors.....its really quite a nice app
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
I never heard of qualcomm chips doing this. There is a app called emmc brickbug check on the market though it won't be of much use to you now.....but it allows you to check the mem. Controller chip and check if its a "sane chip" and allows you to probe the memory for any bad sectors.....its really quite a nice app
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
Well, thanks for the input! Makes me feel a better hopefully the emmc isn't completely fried. I just really want my files, and am continually irritated at myself for having been so stupid to not make backups.. although I have phones from 10+ years ago that have never completely died in such an unexpected manner. It's quite the agonizing wait for a JTAG programmer to come in the mail. If I can manage to get it to boot from SD, which I haven't been able to do so far, do you think it's logical for me to simply reflash the bootloader/CWM, then attempt boot? It shouldn't erase files, right?
You can try a bootloader and recovery flash which might yield results.....and the plus side of that is that it won't wipe the memory unless you format the /data partition or you do a full Odin restore with ROM kernel and everything
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
You can try a bootloader and recovery flash which might yield results.....and the plus side of that is that it won't wipe the memory unless you format the /data partition or you do a full Odin restore with ROM kernel and everything
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
I've also searched everywhere for a debrick image for 4.1.1 AT&T... anyone know where I can get one? All I can find are ones for 4.1.3 =\
EXACT same problem here, let me know if you find anything
(Btw, my phone also had the "power button stuck down" issue, but your phone will vibrate when you put the battery in if this is the issue.)
If I'm not mistaken you will be able to Odin to 4.1.1 while using the 4.3 SD card debrick (again this is just guessing)
Sent from my ATT Samsung Galaxy SIII using TapaTalk
I've tried the SD card debricks for 4.3, and still nothing happens. Yea, I also don't get vibrate. As a long shot, I actually installed the qualcomm drivers and ran the qdload.sh script to attempt to send a signal which kicks the phone out of that mode (works on some... I want to say, HTC, phones), but, yea, I think the emmc just failed somehow. I'm hoping that the failure is just in the bootloader segment, and that by jtag reflashing the bootloader area, I should be able to boot. Either that, or even if one of the memory sectors died, hopefully it's not the one with my data partition. I still can't believe this ! Out of all the electronics I've ever used, aside from a hard drive or two, I've never had something like a phone just kick the bucket with no warning. gha !
Also, thanks for all the tips and stuff, guys and gals. Tell me if you figure out anything, and I'll let you know if I get it fixed with jtag.
OK plz let us know how it goes! I don't want to sound rude but your phone would be the only snapdragon I have ever seen fail....and I've been using snapdragons since the s1 on a HTC wildfire s
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
OK plz let us know how it goes! I don't want to sound rude but your phone would be the only snapdragon I have ever seen fail....and I've been using snapdragons since the s1 on a HTC wildfire s
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
ZOMG SO RUDE > haha, j/k ;P Yea, no problem, dude/dudette! I know how it feels reading threads with no followup... I'm actually surprised that people have come out of the proverbial woodwork mentioning having similar problems to me ! It really sucks spending inordinate amounts of time reading threads and not arriving at a definitive conclusion... so, yea, I especially want to let people know if there is a fix, and/or how I did it.
So, with regard to what you said about the snapdragons not failing... yea. This is rekking my mind, tbh, because I've just never had a device insta-fail on me like this (aside from some old computer hard drives that were server backed up, but yea that's essentially par for the course on that medium [yay for S.M.A.R.T.]). Especially a device that I'd only had for less than 2 years, and though my GS3 has heavy usage, I treat it very well (no drops, water, etc.)... so, yea.
Also, a minority of people with whom I have spoken via the æther have also experienced similar emmc failures on i747s, as well ! Which I was not expecting. It's still insane, though, to believe that, out of such a small percentage of phones that could potentially experience SDS, and then which ones actually do experience it... and then to not even have an i9000 and /still/ experience it on an i747... I feel as though I've won the lotto. Except ****ty.
I'm waiting on parts to come in, then surgery will commence.
Did you try going into download mode? If you can so that then the phone is fine. Another thing is try reflashing stock Odin which will erase msgs and stuff but not music or pics unless u tick "repartition".
Sent from my SGH-I747M using Tapatalk
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [Samsung I747 V1.0.5095.46594]
Connecting to the dead body...OK
Detected dead body ID: 0xhexhereisOK[redacted] - CORRECT!
Set I/O Voltage reads as 1.81V, TCK Frequency is 1 MHz
Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK
Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0100 (000000, 0x000400000000 Bytes = 16.00 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0100 (000000, 0x000000080000 Bytes = 0.50 MB)
No Resurrection Data is available for the eMMC Chip with Capacity = 16.00GB
WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14,68GB
Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: Stopped due to multiple communication errors. Terminating at 0x0003AB3FBE00
Had to reduce the speed to that 2MHz/1MHz to get communication to work. So, 0x51 is a DCC power failure problem... but it is able to detect the initialized chips. So.. not really sure how to proceed at this point. I haven't checked the signal quality on my NRST line, which apparently can cause problems. Some people have increased the voltage from 1.8 to say 1.9, but doing something like that requires me to actually make my own resurrection file, which I haven't had the time to do yet.
Anyone seen a problem with something like this before?
The 000000 is somewhat unsettling, as the chip is apparently supposed to report some ID#? Although, the failures that I'm getting don't seem to be the typical ones that happen when the emmc becomes completely toasted.
Oh, yea... I can't seem to figure out wth is up with --> WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14,68GB
Like..... ??? I think I'm using the most up to date resurrector?!
EDIT: Dumping out the entire contents of the emmc (haven't had errors so far, but it will take a while at 1 MHz), into a bin file (this avoids the bad sectors in the bootloader).
Does anyone know what to do with the resultant *.bin file? I think that if I got another surrogate GS3, I'd be able to write that onto the phone, essentially cloning my dead phone. I'd like to avoid having to do that, though -- does anyone know how to write one of DCC bin jtag file dumps into a readable file system?
[Q] "Retroactive Bricking" or "spontaneous" hardware fault? [Xpost One X/X+ Help]
*PSA: This will be crossposted in xda GenerAL Q&A and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
Poll is in "General QA" Forum original post: http://forum.xda-developers.com/general/help/retroactive-bricking-spontaneous-t2948954
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!