Stock HTC One S got bricked sudenly? - HTC One S

so yesterday my unlocked T-Mobile HTC One S got bricked, before you ask i never touched the ROM of the device, it was pure stock HTC One S with a lot of apps.
basically it entered into a strange loop: first the T-Mobile greeting message appeared and then the HTC One S logo, over and over and over again. the only thing that i could do was to power button + volume down and do a factory reset.
This happened one day after i updated its firmware OTA, and in the same day that i downloaded a free app called AutomateIt.
i'm only upset about the fact that i lost the pictures and vids that i took in the 6 weeks owning it, but i am worried that if it did this once, it could do it again so i need to know if this is something common to Androids, my One S or something else.

Very strange!!!
Root the phone and make a nandroid backup. Stock Rom's sucks!!!
Sent from my HTC One S using xda app-developers app

Warmo said:
so yesterday my unlocked T-Mobile HTC One S got bricked, before you ask i never touched the ROM of the device, it was pure stock HTC One S with a lot of apps.
basically it entered into a strange loop: first the T-Mobile greeting message appeared and then the HTC One S logo, over and over and over again. the only thing that i could do was to power button + volume down and do a factory reset.
This happened one day after i updated its firmware OTA, and in the same day that i downloaded a free app called AutomateIt.
i'm only upset about the fact that i lost the pictures and vids that i took in the 6 weeks owning it, but i am worried that if it did this once, it could do it again so i need to know if this is something common to Androids, my One S or something else.
Click to expand...
Click to collapse
Did you let the phone die? the phone don't like to do that. Get Dropbox or Google+ that will sync your pictures online.

The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.

-janboy- said:
The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.
Click to expand...
Click to collapse
now thats interesting, my phone is also 4.0.4, and yes i did have ~20 saved WLAN's, i can't figure how wlan would have any connection to a bootloop, but then again i dont know anything about programming.
so you always delete the wlans once you are done using them? after you found out did it brick again?

Warmo said:
now thats interesting, my phone is also 4.0.4, and yes i did have ~20 saved WLAN's, i can't figure how wlan would have any connection to a bootloop, but then again i dont know anything about programming.
so you always delete the wlans once you are done using them? after you found out did it brick again?
Click to expand...
Click to collapse
yes, I take care that I don't have more than 5-10 in my list. since that it didn't brick again. but a few days ago I had ~10 in my list and it suddenly restarted again while I was in the wifi list screen and I was like pleeeaassse no bootloop! but fortunately it was no bootloop but my whole wifi list was reset. it must be an error in htc's software.. so we can only wait for updates..

I've had this happen with other Android devices, it's generally some rogue app that screws up the device and only a factory reset will clear it. I've never had more than 3 or 4 wifi points saved so can't comment on that as a possible cause.
It's not 'bricked' by the way, just slightly fubar'd

-janboy- said:
The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.
Click to expand...
Click to collapse
You are not the only one. I also encountered the same thing because of too much wlan connections and the only thing i could do is run into bootloader and restore factory settings, since i don't have a nandroid backup because i'm not rooted.. fortunately i synced my pictures thru dropbox, and a backup of sms in gmail.. but i don't know why it is happening to us, so this issue isn't an individual case..
Sent from my HTC One S4 using xda-developers app

Related

ON stock rooted and it keeps dropping to no signal

I am rooted and cwm recovery flashed. I have had a few instances in the past few days where it would drop from 2-3 bars 4g to X no signal. Just now it does it every time I attempt to download anything. I have tried enabling and disabling airplane mode etc and it does not help. I access the market with a couple of bars of 4g and instantly it will drop to X when I attempt to download or search the market.Any one else have these issues? Does anyone know what might be a fix for them(I know send the device back and wait for SSGII.LOL)
Send it back and wait. Thats waaaaayyyyy more fun. Heck you might even get an update one day. Of course I doubt it.
But hey its a nice phone.
Sent from my LG-P999 using XDA Premium App
I had the same thing happen a few times today. I noticed it more while checking facebook
Have you tried a factory reset?
I am rooted with cwm as well and have no such issues.
I have the same problem as well.
Very frustrating.
Who here HAS RETURNED a rooted phone?
Should it be a non-issue?
rooted, factory reset here as well. i guess i should update my Info
Mine does this every now and then, even with the Obrien fix. It's happened on the first 2 G2x phones I had, and happens on the one I currently have as well :/
OrganizedFellow said:
I have the same problem as well.
Very frustrating.
Who here HAS RETURNED a rooted phone?
Should it be a non-issue?
Click to expand...
Click to collapse
Well you should unroot it first, then return it LOL
I'm on my 3rd G2x, and the first 2 were rooted (as is this one). I just flashed stock recovery and did a factory reset, then unrooted through One Click.

Help please! Just installed Android Revoluation HD, now won't turn on?

I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
newr said:
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
Click to expand...
Click to collapse
Try to boot with adb.
Sent from my HTC Sensation Z710e using xda premium
Hi...I am trying to install the new SDK package...but I do have the older ADB and when I tried it..it first says ADB sever out of date...then started daemon...and attached list showed nothing?
When I plug the phone in...there's no response from the PC..it won't beep or show anything connected on USB!
I just tried to run adb after installing the latest sdk package. Running adb from the platform-tool directory...the device listed is empty....doesn't seem to be recognizing the phone!
Any other ideas? Is this completely bricked?
I wouldn't call it a brick per se, but this has happened to more Sensations than you may realize. Most people who've reported said they went to bed (phone on or off the charger) and when they wake up, it just won't turn on.
Honestly, I believe it's a random catastrophic hardware issue. I think some Sensations are faulty and have a lower temperature threshold or something, not sure, but what you described seems hardware related.
Edit: Just reread about that tone. A long tone? Although you were on a phone call so it's no guarantee, something like a long speaker tone or a screen spazzing out (I work in electronics) tend to mean something hardware related. Again, not 100% solid, but that's how it usually turns out.
Also, don't believe this happened because you flashed a different rom or something, there is just no way flashing a rom would kill a phone. If that were true, normal software updates or factory resetting could cause the same thing, and they simply don't.
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
newr said:
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
Click to expand...
Click to collapse
take off the battery, SD card, SIM card and then put them back again.....try to press power+volume down (even power+volume up & down, all buttons) to see if you can log into the recovery...I don't know if this works but since your phone is almost dead, you won't lose anything to try any method...Do you think so?
If anything you have tried does not enable the phone to work normally again, please try to turn to some body who can check and repair the hardware of your phone for help...It could take a long time to send it back to HTC.....
Hope everything is going well with you.
Nothing works..I've tried taking out Battery..talked with HTC and they tried that with me too...but basically the phone is completely unresponsive. I am just wondering if it's a problem with the ROM or if it's a hardware thing. It seems strange it booted up ok and then had this long beep/tone thing.
There seem to be one other person posted in Q&A experiencing exactly the same thing...he was using revolution 6.6.3 and also had that sound and now it won't turn on!
I have talked to HTC and got a repair ticket...not sure if anyone locally can fix it...just wonder if HTC will have problems with it being rooted and all.
He was running ARHD 6.6.3?! I just downloaded it, now I'm weary to flash O.O
@newr
can you try one thing?
Remove battery ,sdcard, then connect the phone to power outlet using usb then try to power on the phone.?
If it doesn't turn on then remove the back shell too and try to power it on again?
sent from my blazing fast pyramid through sonic waves
Thanks for the suggestion. But again nothing happened. I've tried taking out SD, SIM, battery...with or without cover. Nothing turns the phone on...also no light when charging. It's like the phone is just dead?
There's one other post by someone on the forum that says his phone doesn't turn on..and it seem to happen the exact same way. He said he was running 6.6.3 and then all of a sudden a long beep/tone...then stuck..so turned it off and won't turn on again. Haven't seen any update / resolution there neither!
I am still not sure if it's a ROM problem or if it's a hardware problem. The thing is, the ROM did get installed and was rebooted...in fact, I used Titanium to reinstalled all the apps...unless restoring some data for things like bluetooth settings, desktop etc..causes it...which was fine when I restored it for InsertCoin...I don't understand how a ROM could cause a phone not to turn on at all?
I guess unless there are other ways to fix this..looks like it's sending back to HTC...hopefully they can't fix it neither and just send a different phone since if they turn it on and notice I have it rooted and S-On..they might just blame it on that!

Boot Loop To Factory Reset to Nothing now Please Help!

Hi HTC inspire users,
I have a HTC inspire 4g on AT&T that was purchased around last year of March that has never been rooted (too worried about rooting), and a few weeks ago(just found this forum), my phone, to my belief, updated by it self over night. The next morning I found my phone not working at all, and was not able to start up to the home screen. However, the screen was black and lit and kept going through a boot loop. I freaked out, and asked for help on another forum (not phone related forum), and was told to turn off, and factory reset. I did this after removing the SD card so my personal data wasnt wiped. After I did the Factory reset, my phone continued to do the boot loop which has gotten me lost.
Ive been told to do a recovery from the menu by holding down the volume button while turning on the device. Even doing so my phone will not work.
Is there Any way possible to make the phone work again?
Thanks,
Matt
Theoutbackdream said:
Hi HTC inspire users,
I have a HTC inspire 4g on AT&T that was purchased around last year of March that has never been rooted (too worried about rooting), and a few weeks ago(just found this forum), my phone, to my belief, updated by it self over night. The next morning I found my phone not working at all, and was not able to start up to the home screen. However, the screen was black and lit and kept going through a boot loop. I freaked out, and asked for help on another forum (not phone related forum), and was told to turn off, and factory reset. I did this after removing the SD card so my personal data wasnt wiped. After I did the Factory reset, my phone continued to do the boot loop which has gotten me lost.
Ive been told to do a recovery from the menu by holding down the volume button while turning on the device. Even doing so my phone will not work.
Is there Any way possible to make the phone work again?
Thanks,
Matt
Click to expand...
Click to collapse
ok, pulling the sdcard to avoid deleting personal data is useless. When u do a factory reset all information is wiped except the sdcard..anyway, you have to flash this in fastboot usb.
To boot in fastboot you have to do this: pull the battery, then press volume down + power until you get a white screen with 3 androids at the bottom. Then press power to choose fastboot. Plug the phone to the PC and you should see fastboot usb in red in the cell. Run this exe file (is the official AT&T ruu):
http://dl4.htc.com/RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio_12.56.60.25_26.10.04.03_M_release_200368_signed.exe
If you are not having a hardware issue, then the phone it should reboot normally when done.
Thanks Glevitan!
Ill give this a shot, if something pops-up ill be sure to ask.
Got it working Thanks Alot!!!
However, when i did do the process, i had issue where I couldnt get into the Fastboot menu.. However, I left the phone charging all day and it seemed to cure it. And then the first time I tried to flash the software, it didnt work, second time it had no issues. Could this mean something?
Edit:
After using my inspire 4g for awhile one thing that does not go away is the immense lag from the App Drawer, with no new programs from the market, but the Factory apps.
Theoutbackdream said:
Got it working Thanks Alot!!!
However, when i did do the process, i had issue where I couldnt get into the Fastboot menu.. However, I left the phone charging all day and it seemed to cure it. And then the first time I tried to flash the software, it didnt work, second time it had no issues. Could this mean something?
Edit:
After using my inspire 4g for awhile one thing that does not go away is the immense lag from the App Drawer, with no new programs from the market, but the Factory apps.
Click to expand...
Click to collapse
Att Firmware Is a buggy as all the others. It Is weird that You end up in boot loop being stock.....maybe there's something in the hardware that Is messed. Just try to use it and assess the bebaviour of the device for a while, then if nothing Is failing You can try root it and run a custom ROM.....
Glad to have it back....:laugh:

Phone randomly rebooting in pocket

I never had a random reboot on ICS now on JB I'm having it at least once a week...not a lot, I know but still something is not right. The last time this happened I tried looking further into it and the only thing I see that may be causing the issue is signal loss. I am 100% stock and have maybe 25 downloaded apps, if that. Is there an app for STOCK that will backup some of my data? I really don't think a factory reset will help but I'll give it a shot. Any other ideas? I freaking love this phone and this is my only complaint....would love to fix the problem. Thanks.
Here's a shot of the signal before the reboot.
Is it worth trying a factory reset? I feel the chances of it doing any good are very slim. Switch to a different modem?
Sent from my SCH-I535 using xda premium
I'm having the same issue, and a reset did not help.
Sent from my SCH-I535 using xda app-developers app
Thanks for the reply. As long as it does not get worse it's not a huge deal. Maybe the next update will fix it?
Sent from my SCH-I535 using xda premium
Not sure what the right word is (hotboot?) but today my phone rebooted (not fully) while I was using it. No fc's or freeze ups, just the reboot. I'm currently on the no wipe leak which ended up being the official ota.... Since the no wipe was modified would it make any sense to install the full wipe version to see if the problem is resolved?
Sent from my SCH-I535 using xda premium
Flashed full wipe via Odin. In case anyone else has this problem I will post back with results in a week or so.
Sent from my SCH-I535 using xda premium
I'm having the same issue. It seems that something is causing JellyBean-enabled SGS3's to just jump into "interrupt heaven". It's always a quick boot, never resets the "Up time" counter, and only takes a few seconds to get back to normal, but it's a real pain in the arse!
Any ideas what the culprit is, guys? I'm running a newly replaced (ordered it on January 2nd and the first thing it does was download and upgrade to JellyBean "VRBLK3" before I could even start get it loaded, basically as soon as I activated the phone, it started to download the OTA before I could even get to anything else). I know in my case I have a couple of mods installed - maybe one or more of these is common amongst those of us having issues? I have the "4x5 scrolling" mod and the "BLK3 Logo fix" mod that removes the stupid VZW drum-beating and pulsating display on boot-up. Other than that, my phone is rooted (using method involving loading the older ICS bootchain so you can install the latest CWM recovery), has CWM Touch 6.0.2.3 and that's about it, other than your usual rooted toolkit programs. Anything common to the rest of you?
Oh, by the way - I've already tried reformatting the cache, blowing away the dalvik cache and even a complete factory reset, which seems to make it less jumpy, but it always comes back within a day or two if not just a few hours.
I had the same problem with mine rebooting when I had very bad signal. Last Friday I did a factory reset then Odin to 4.0.4 and let the phone update to 4.1.1 and the problem seems to have gone away. I am not willing to call it cured yet, but it hasn't rebooted since. This went from where I was rebooting constantly all day long at work and when on the road in bad signal areas.
So far so good.
By the way, I looked EVERYWHERE and couldn't find anyone complaining of this earlier so I figured it had to be a bad download of the update.
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Factory reset (and everything else) - it still reboots
ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.
ratledge said:
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.
Click to expand...
Click to collapse
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium
Ryno77 said:
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.
New SIM?
SlimSnoopOS said:
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.
Click to expand...
Click to collapse
Well, unfortunately I've done that - twice in the past ten days, the latest one came Tuesday afternoon. No change, still just reboots while I'm not even using the phone, and it's not the phone, it's the software. I can't say for absolute certain that it is in the VRBLK3 / JB code, but I can say for sure it _is_ something I am running, but the fact that it does reboot in safe mode indicates it's not anything downloaded or added to the base system as shipped.
ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?
6 Pebble Blue 32MB phones in about 8 months
jaymattt said:
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?
Click to expand...
Click to collapse
Heheh... Well, I got one on "day 1" by pre-ordering it from Verizon, after two months the power button fell off. They sent me a "CLN" one, it lasted ten days and started randomly rebooting (even if reloaded with 'virgin' unrooted OS), the third (another "CLN") was delivered with no power button and the volume rocker fell off while I was taking it out of the box. At that point, I got kind of pizzed and did the 'good customer for 10 years' and elevated it through three levels until I finally got them to ship me a brand new one. That one lasted two months until my wife left it on top of my car and I backed over it in my driveway. I used my Asurion (insurance) to get #5, which arrived rebooting from the moment I started it up. Within a few days after monkeying around with their tech support (they ain't the brightest bulbs - instructions include "remove the battery and dial yourself and hit the 'Send' key three times" - not kidding) I managed to get #6 shipped out, and it's first act of life was to suck down the VRBL3 (Jellybean) software update and I've mucked around with it for two weeks, tried loading it with various combinations of "No Wipe" and "Factory Reset" versions of VRBLK3, removed a bunch of programs I've had installed but never really used and it still just vibrates about once an hour (and it's totally random, sometimes lasts 6 hours, sometimes 6 minutes before rebooting), jumps to the "warm/quick start" and recycles without resetting the "time up" counter. I'm thinking it's something I fed it (i.e. a nasty program or interaction between programs) - but I've come up empty-handed so far as running it to ground.
Does anyone have any knowledge of known interactions or "bad programs" that just don't play well together under JB?
Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well, normally - I would agree. But this makes three phones that act exactly the same in a row. The first of which was my 2nd "New" GS3, updated OTA to Jellybean - which immediately started the rolling reboots. The problem with the "CLN" phones are that they were all defective in one way or another, or they wouldn't be recertified. I don't really think VZW does a good job recertifying these phones, there are just too many of them coming out every single day, and - lord knows Asurion probably is behind that curve. :silly:
All three phones have been identical in their behavior - "down to the letter" since VRBLK3 was released. :fingers-crossed:
Question: now that I've used my insurance, do I _have_ to go back to Asurion for replacement, or since I'm still in my first year, will VerizonWireless entertain sending me another? It seems like reading the information that comes with the Asurion phones, they are the ones that are now guaranteeing my phone for a full year from the time it was sent (that would be this past Monday).
The phone has an Asurion sticker inside it, not a VZW one...
And the winner is: battery replacement. Every single VZW marked battery causes it to reboot, but a plain old Samsung battery (made in Korea - I've noticed almost all the VZW branded SKUs are made in China) works 100% and gives me an average of 12 hours moderate usage. The batteries I had from previous phones, VZW and Asurion all have the Verizon markings on them, and every single one of them causes it to reboot. This new one I got today straight from Samsung does not.
Curious, huh? I have one out of five batteries with VZW markings, and it does the same as the other four "made in China" ones. You've gotta wonder...
Glad you found a fix. Is it possible the new battery is slightly larger? Wondering if the old batteries were maybe a bit loose.
Sent from my SCH-I535 using xda premium

[Q] HTC ONE E8 reboots itself

Hi experts, my 4 months old HTC One E8 dual SIM reboots every minute by itself. It displays a lot of application stopped working errors too. If I remove Youtube, it stays for a while,(may be a day if I dont go to gallery or camera or dont connect to PC etc.)When it reboots, it comes to a particular state and I lose any recent data. The same thing if I reboot the phone manually while fast boot disabled. Even if it is booting back with all old data even if I manually delete all of them. Looks like it is restoring data from a particular backup. Neither the reset to factory default works, as t is showing a red exclamation mark and boots to the same old state with all old data. Tried to follow some threads online(including HTC Dev website) to get it rooted (with my few weeks familiarity with Android system!) but again , it shows that annoying red exclamation mark and boots to the same old state with all old data.
Really got stuck! Any comments would be much appreciated. Thanks a lot
android version is 4.4.2
location is Middle east
Have you tried to hard reset the device? You can do that either from the menu, or from bootloader mode (if you can't make it, send me a pm)
I faced that 5 months ago and i sent to HTC service. Just do it.
ady_uaic said:
Have you tried to hard reset the device? You can do that either from the menu, or from bootloader mode (if you can't make it, send me a pm)
Click to expand...
Click to collapse
Thanks for the reply, yea, I have tried that too, again that red triangleappears and phone reboots with no changes at all. Cleared cache partition as well from the same bootloader menu.
lonelydra said:
I faced that 5 months ago and i sent to HTC service. Just do it.
Click to expand...
Click to collapse
I was a bit hesitant because it would take a couple of weeks to get it fixed by them. I had a chat their support people and could be due to a hardware issue as well. yea, like you said, I think thats the only possible way now.
raj971 said:
I was a bit hesitant because it would take a couple of weeks to get it fixed by them. I had a chat their support people and could be due to a hardware issue as well. yea, like you said, I think thats the only possible way now.
Click to expand...
Click to collapse
yup. because i've searched and tried many way to fix that (from google and xda) but unsuccessfully.

Categories

Resources