Related
My wife and I both have non-rooted TBs which started experiencing random reboots after the OTA. We went to the store and they ordered us two new ones. They'll be here Tuesday.
Yesterday my wife's TB rebooted, and got stuck at the HTC logo. She was unable to turn it off. I did a battery pull, and again, stuck at the HTC logo. I swapped my battery since hers was low, nothing. It's dead, Jim.
We called the store and they wouldn't swap it since one is already on order. My wife is a doctor, and being without a phone until Tuesday is not an option. So I loaned her mine. (Sigh).
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
ZBoater said:
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
Click to expand...
Click to collapse
Unfortunately, the only thing I would've suggested would be flashing the signed ruu.
You could try reverting to the pre-OTA firmware, but I'm not sure you'll be able to use ADB if you're stuck bootlooping. Check out the "NOT FOR ROOT USERS" section.
ZBoater said:
My wife and I both have non-rooted TBs which started experiencing random reboots after the OTA. We went to the store and they ordered us two new ones. They'll be here Tuesday.
Yesterday my wife's TB rebooted, and got stuck at the HTC logo. She was unable to turn it off. I did a battery pull, and again, stuck at the HTC logo. I swapped my battery since hers was low, nothing. It's dead, Jim.
We called the store and they wouldn't swap it since one is already on order. My wife is a doctor, and being without a phone until Tuesday is not an option. So I loaned her mine. (Sigh).
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
Click to expand...
Click to collapse
RIP poor TB
How long did you wait for the screen to clear?
Just curious because I know usually when I do any type of update or rom change, etc, since you normally wipe the data and cache, the boot up can take quite a long time on the initial boot up.
I know some people report as long as 10 minutes or so to get past the screen. I don't think mine ever took that long, but there have been times I think it's stuck and then a minute or so later, it gets past it.
Just my two cents.
This has happened to a few people already after the update. I don't know what is in this update but HTC screwed up majorly.
Sounds a lot like what happend to mine, but mine was rooted.
See here...http://forum.xda-developers.com/showthread.php?t=1090531
LOL, I welcome the breaks when I can't find my phone for the day.
you should just leave it on the htc logo until the battery dies or until it get wayy to hot.. just to see
will9512 said:
you should just leave it on the htc logo until the battery dies or until it get wayy to hot.. just to see
Click to expand...
Click to collapse
What would that accomplish?
Yeah your lucky you got a guy to order your phone because I wouldn't have because even the new ones are rebooting, when you get it I would suggest postponing the update if it comes without the Mr1 update, as far as your wives phone yeah I would check out the forum uptop on going back to old software other than I have had a few people come into the store with same problem and couldn't do anything( mainly because I have no access to anything), but ship a replacement, oh and one suggestion is if you don't want your wife to borrow your phone your local store does have emergency stock Android loaners that you use until you get your replacement in, and then you just send your phone and the loaner back in the FedEx box so if you really need a phone you can do that.
Sent from my ADR6400L using Tapatalk
I believe your random reboots are due to the new radio which is tied into the OTA. If you apply the OTA again your still going to have random reboots. I ever used the newer radios and have never had a random reboot.
Hello again everyone, im here with another new problem. Out of the blue.
This is what happens.
-Phone is on
Hold down power
Shut off
-Phone shuts off screen goes blank
5 seconds pass
-Phone boots up... never touch a thing....
WTF?
It will not stay off, no matter the rom, I pulled the batter,SD,SIM nothing will shut it off unless i pull the battery.
I've downgraded the phone with the ace hack kit, ive re-rooted. nothing. I've searched, nothing. Anyone out there got a clue? Cus I dont.
FYI:when the phone rebooted after it flashed the downgrade during re-rooting, the alarm was going off and had the snooze button and everything, no matter what it wouldnt go off. but I just went on with the root process and now its gone, but the phone still wont stay off, something just screwed up!
That's hilarious, and I don't mean that literally. I am laughing though, kind of. Why? Because the same thing just happened to me last night. I know I said the exact same thing you said, possibly more. I have been on the same rom for a week and the only thing I have done was update a couple of apps from the market last night. Nothing else was done. Suddenly I can not power off the phone, it simply shuts off for five seconds and then reboots. I have wiped, restored, and tried flashing and the issue still persists. I am heavily researching and experimenting on what could be the cause for this issue. If I figure it out I will be sure to let you know.
Wolf_2 said:
That's hilarious, and I don't mean that literally. I am laughing though, kind of. Why? Because the same thing just happened to me last night. I know I said the exact same thing you said, possibly more. I have been on the same rom for a week and the only thing I have done was update a couple of apps from the market last night. Nothing else was done. Suddenly I can not power off the phone, it simply shuts off for five seconds and then reboots. I have wiped, restored, and tried flashing and the issue still persists. I am heavily researching and experimenting on what could be the cause for this issue. If I figure it out I will be sure to let you know.
Click to expand...
Click to collapse
Lol that is funny, what apps did you update?
I also have a problem with charging the phone and not sleeping, i was starting to think that it was just finaly getting worst
The only apps that were updated were Battery Monitor widget, Elixir, Xfinity TV, and one more which I can't remember right now. If you do get your phone to shut off, which I have been able to do twice, it may not wish to power back up, which is what mine does now also. (Laughing hysterically now.) Just pull the battery out and put it back in and it will power up. My feelings are that this may have been caused by some kind of update. Possibly from the market or from ATT. I have tried three different roms and it is still doing the same thing. I am about to wipe and restore the phone back to stock and see if it does it still. I will keep you appraised.
Wolf_2 said:
The only apps that were updated were Battery Monitor widget, Elixir, Xfinity TV, and one more which I can't remember right now. If you do get your phone to shut off, which I have been able to do twice, it may not wish to power back up, which is what mine does now also. (Laughing hysterically now.) Just pull the battery out and put it back in and it will power up. My feelings are that this may have been caused by some kind of update. Possibly from the market or from ATT. I have tried three different roms and it is still doing the same thing. I am about to wipe and restore the phone back to stock and see if it does it still. I will keep you appraised.
Click to expand...
Click to collapse
I dunno, I already did that and it did nothing, but I guess its worth a shot for you...
And I dont have any of those apps
If I find something I'll post here
/me shrugs
I am very confused by this, but I will have to try a restore to stock to see what happens. I do find it strange that two different people had this happen to their phones at about the same time and day. I will let you know how things progress later.
Edit: What version of Clock Work Mod recovery do you have installed and which rom were you running? Trying to go through the variables with this issue.
Wolf_2 said:
I am very confused by this, but I will have to try a restore to stock to see what happens. I do find it strange that two different people had this happen to their phones at about the same time and day. I will let you know how things progress later.
Click to expand...
Click to collapse
Yeah it is odd, could be coincidence, could be related, dunno, I dont see how it could be an ATT update when nearly all the roms here have that function disabled. Then again maybe you know something I don't
What did you do to get it to turn off finally? I dunno if I wanna try now that you said it wouldn't turn back on.
Also, what rom where you on when it started, I was on CM nightly #121 or maybe #120 I forget
I just happened to come across this in the general section
http://forum.xda-developers.com/showthread.php?t=1145495
no fix though
I am restoring an old rom and I will try changing the date as someone suggested to see what that does. If it does not work then I will have to wait until later tonight to return the phone to stock and go step by step from there.
Wolf_2 said:
I am restoring an old rom and I will try changing the date as someone suggested to see what that does. If it does not work then I will have to wait until later tonight to return the phone to stock and go step by step from there.
Click to expand...
Click to collapse
Could this have something to do with partitioning the SD card? I think i remember reading that clockwork bricked some phones, is that true?
I believe CWM did have some problems partitioning before. Not sure if it still does. It seems like I have found a fix for myself. I turned off automatic system time and date and reset the date to January 2012. The phone seems to be working like it did before this occured. I will wait until tomorrow and change the date back to automatic and see if the power issue shows back up, but for now it seems ok.
Edit: I changed the time and date back to automatic and it is working like it should again. Did you get yours working again or is it still having problems?
Wolf_2 said:
I believe CWM did have some problems partitioning before. Not sure if it still does. It seems like I have found a fix for myself. I turned off automatic system time and date and reset the date to January 2012. The phone seems to be working like it did before this occured. I will wait until tomorrow and change the date back to automatic and see if the power issue shows back up, but for now it seems ok.
Edit: Did you get yours working again or is it still having problems?
Click to expand...
Click to collapse
This worked for me also.
im still having this phone wont shut off issue as well. i have set it to the same date as u and turned off auto and it still just reboots when trying to turn it off
Try leaving automatic off for a whole day. Then see if it is still having this problem. Also replied to pm but try this first to see if it gets past it and works..
willdo thanks a bunch
BAleR said:
Hello again everyone, im here with another new problem. Out of the blue.
This is what happens.
-Phone is on
Hold down power
Shut off
-Phone shuts off screen goes blank
5 seconds pass
-Phone boots up... never touch a thing....
WTF?
It will not stay off, no matter the rom, I pulled the batter,SD,SIM nothing will shut it off unless i pull the battery.
I've downgraded the phone with the ace hack kit, ive re-rooted. nothing. I've searched, nothing. Anyone out there got a clue? Cus I dont.
FYI:when the phone rebooted after it flashed the downgrade during re-rooting, the alarm was going off and had the snooze button and everything, no matter what it wouldnt go off. but I just went on with the root process and now its gone, but the phone still wont stay off, something just screwed up!
Click to expand...
Click to collapse
I had that problem, but it was the car app. I had to disable it in the settings.
seems this keeps happening more and more to people. i still have yet to solve my issue
well i retried setting the date on the phone but this time i chose 1/1/2011 and now the phone stays off when i turn it off which is nice but now i have to deal with having the wrong date
Welp,
There's no doubt in my mind that my Galaxy S3 just hard bricked
Looking for some advice on what to do.
I've had the phone for 20 days, I've been running Beans Custom Stock ROM Build 10 for over a week I think?
And this is how it happened:
I started sending a few texts to one of my brothers, with "Go SMS" , and my phone around the time I hit send decided to switch to 4G (which it hardly does because it's only 1-2 bars where I am) , I then went into the basement and my phone then went to show 0 bars of 4G, then looked like it was going to switch to 3G but then the SMS application hung. I tried closing it, but it wouldn't, so I held down the power button and as the boot menu was coming up, that hung, so I pulled down the notifications bar and tried shutting off data, but then that hung. So, I had no choice but to pull the battery.
I left the battery out for a little while and then put it back in. Held the power button, and the device hung on the "Samsung Galaxy S III" first boot screen. I pulled the battery again and waited for a really long while and took my Micro SDXC out.
Tried to boot but power button does nothing. There's no signs off life!
Plugging it into a wall charger does nothing and I'm sure there's still charge in the battery because when it died it was around 20-30%.
Only sign of life I can get is when I plug it into my PC and then put the battery in. THE RED LIGHT TURNS ON.
:crying:
I have no idea what caused this, and I have no idea what to do!
Will Verizon cover this since it bricked without question and it's been under 30 days?
Or maybe Samsung will cover it?
Or because I rooted, I pretty much screwed myself?
I've never had anything like this happen before so I'm stumped...................HELP!!!!!!!!!!! I used to love my S III but now it's just a really nice paperweight.............. :crying:
I guess this is an option also: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
mcappleman said:
Welp,
There's no doubt in my mind that my Galaxy S3 just hard bricked
Looking for some advice on what to do.
I've had the phone for 20 days, I've been running Beans Custom Stock ROM Build 10 for over a week I think?
And this is how it happened:
I started sending a few texts to one of my brothers, with "Go SMS" , and my phone around the time I hit send decided to switch to 4G (which it hardly does because it's only 1-2 bars where I am) , I then went into the basement and my phone then went to show 0 bars of 4G, then looked like it was going to switch to 3G but then the SMS application hung. I tried closing it, but it wouldn't, so I held down the power button and as the boot menu was coming up, that hung, so I pulled down the notifications bar and tried shutting off data, but then that hung. So, I had no choice but to pull the battery.
I left the battery out for a little while and then put it back in. Held the power button, and the device hung on the "Samsung Galaxy S III" first boot screen. I pulled the battery again and waited for a really long while and took my Micro SDXC out.
Tried to boot but power button does nothing. There's no signs off life!
Plugging it into a wall charger does nothing and I'm sure there's still charge in the battery because when it died it was around 20-30%.
Only sign of life I can get is when I plug it into my PC and then put the battery in. THE RED LIGHT TURNS ON.
:crying:
I have no idea what caused this, and I have no idea what to do!
Will Verizon cover this since it bricked without question and it's been under 30 days?
Or maybe Samsung will cover it?
Or because I rooted, I pretty much screwed myself?
I've never had anything like this happen before so I'm stumped...................HELP!!!!!!!!!!! I used to love my S III but now it's just a really nice paperweight.............. :crying:
Click to expand...
Click to collapse
Call verizon and they will send you an replacement. If its thats far gone theres no way they can check to see if its been modded.
Me too!!!!
Message removed
This happened to me after having mine for 3 days, i got mine replaced without a problem and i was rooted, cm10 custom kernel everything
fr8cture said:
This happened to me after having mine for 3 days, i got mine replaced without a problem and i was rooted, cm10 custom kernel everything
Click to expand...
Click to collapse
But I've had it for 20 days now and their website says they don't allow returns or replacements after 14 days. Or is this different because it randomly died?
Also. I don't get insurance on my phones because they always would charge me $10 or more a month and then when the phone died they would charge half the cost of the phone just to get it replaced!
Honestly I think I may just send it to MobileTechVideos.........
Unless I still have a chance with Verizon. Hard decision............
I'm pretty sure the 14 day timeframe is for refunds on the purchase. Most electronics have some sort of manufacturer's warranty.
Have you tried to get it into download mode? volume down, then home, then power, Hold them all together until it boots into download mode? Do this while plugged in maybe?
samsung s 3
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
cmars said:
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
Click to expand...
Click to collapse
You really give your phone number out to strangers like that?
Sent from my SCH-I535 using Tapatalk 2
cmars said:
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
Click to expand...
Click to collapse
Haha. Thanks!
Well, I ended up making a Google Voice account since my phone is dead and I called Verizon customer service. The first lady started having me go through the usual checklist like most companies do, I very nicely let her know that I've tried it all and I indeed know it's dead without explanation. She then sent me to someone higher up, we talked very briefly and she said it's covered under the manufacturer warranty, they're sending me a replacement for free. Only thing I paid for was a $12 upgrade to 1-day shipping!
I seriously was freaked out that I wasn't going to be able to get this replaced. Thankfully I can!
So, I guess, some advice to people that have hard bricked Galaxy S IIIs, CALL VERIZON BEFORE ANYTHING ELSE!
Thanks for the suggestions and help guys!
It's crazy how deep the brick went, the phone wouldn't even charge! Maybe I got a lemon? I hadn't even dropped or scratched it and I had 0 problems with unlocking/rooting it. I swear it was it hanging on trying to switch from 4G to 3G that killed it. Either way, stress is gone! phew! :fingers-crossed:
mcappleman said:
Haha. Thanks!
Well, I ended up making a Google Voice account since my phone is dead and I called Verizon customer service. The first lady started having me go through the usual checklist like most companies do, I very nicely let her know that I've tried it all and I indeed know it's dead without explanation. She then sent me to someone higher up, we talked very briefly and she said it's covered under the manufacturer warranty, they're sending me a replacement for free. Only thing I paid for was a $12 upgrade to 1-day shipping!
I seriously was freaked out that I wasn't going to be able to get this replaced. Thankfully I can!
So, I guess, some advice to people that have hard bricked Galaxy S IIIs, CALL VERIZON BEFORE ANYTHING ELSE!
Thanks for the suggestions and help guys!
It's crazy how deep the brick went, the phone wouldn't even charge! Maybe I got a lemon? I hadn't even dropped or scratched it and I had 0 problems with unlocking/rooting it. I swear it was it hanging on trying to switch from 4G to 3G that killed it. Either way, stress is gone! phew! :fingers-crossed:
Click to expand...
Click to collapse
So i didn't see it, but did you even try to get it into download mode?
Sent from my Synergized vzw S3!
silver04v said:
So i didn't see it, but did you even try to get it into download mode?
Sent from my Synergized vzw S3!
Click to expand...
Click to collapse
It's hard bricked. Will not charge, no booting, and download or recovery mode won't work. Will not show any indication of life except for plugging it into a power source without the battery and then putting the battery in. If the red light comes on when you do that, it means it's hard bricked? Correct me if I'm wrong?
mcappleman said:
It's hard bricked. Will not charge, no booting, and download or recovery mode won't work. Will not show any indication of life except for plugging it into a power source without the battery and then putting the battery in. If the red light comes on when you do that, it means it's hard bricked? Correct me if I'm wrong?
Click to expand...
Click to collapse
If you can't get into download mode then yea, most likely I guess or the battery died. I just didn't see that you said you tried to get into download mode.
Sent from my Synergized vzw S3!
Glad you got this fixed! Also i think its a 30 day replacement or swap for another phone if you don't like it. Thats what i was told when i got mine.
Hi All,
I'm hoping somebody can help me here. I have an N8010 which is stuck on a constant reboot cycle.
It displays the "Samsung Galaxy Note 10.1" Logo and then blanks the screen. After a couple of seconds, then it redisplays the same logo.
It first did this on Thursday after being in use for about 30 Mins. The Tablet just hung and rebooted. It got stuck in this loop until somehow I managed to turn it off. After about an hour, it started up and worked OK, but I didn't try prolonged use.
This morning, it did the same thing, hung (Editing contacts) and rebooted. This time it started back up, but almost immediately id hung again and now it's stuck in the Reboot/Logo loop. I cannot even turn it off - It's just displaying the Logo.
I can press and hold Power/Vol Down to invoke Odin. Selecting Restart Phone just returns me to the loop.
Earlier I could press and hold Power /Vol up to invoke the Reboot/Reset screen and I have done a factory reset.
Oddly - Now I can no longer use the Power/Vol up combination to get to the reboot/reset screen, but I have managed to use it to turn of the tablet.
Occasionally there are a number of corrupted pixels flashing on the screen.
I am assuming that there is some sort of dry joint/bad connection that is warming up and causing these issues.
This Note has not been flashed with any software at all - It's stock.
Anyone seen anything like this before or should I just return it
Thanks in Advance
Steve
Return it, don't try to flash anything to it.
Sent from my GT-N8010 using Tapatalk HD
If it is under warranty and you are on your stock market rom then give it to a service center
samir_a said:
If it is under warranty and you are on your stock market rom then give it to a service center
Click to expand...
Click to collapse
Did you try to root it or flash another rom? If not just send it to service.
gpgalanis said:
Did you try to root it or flash another rom? If not just send it to service.
Click to expand...
Click to collapse
Thanks guys - No didn't try to root or flash at all. I'm waiting for the JB update to see if I need to.
It's working perfectly right now, While it was rebooting endlessly, I managed to get the battery display to appear - It seemed to be completely discharged. (85% a few minutes before) . So I connected it to the charger.
After 35 mins, the charge was showing 92% and it booted and has been running happily ever since.
Exactly what it did on Thursday - showed empty and then charged after about 30 mins.
I think I'll take it back and see if they'll swap it for one with the 3G. Hope that they don't have to send it away, it's gonna be my Christmas present
Steve
Good luck! Since you didn't flash a custom rom or anything, there's no reason you should have to deal with that stress.. Just return it and demand an exchange or something. If you got it at a store, they'd probably be happy to exchange it. If you got it online, it'd be a little harder and more delayed, but still doable! Good luck again!
Unfortunately there are lemons in all manufactured goods, looks like you got 1... I hope it doesnt sour your attitude towards a really good product, as long as it works....
ultramag69 said:
Unfortunately there are lemons in all manufactured goods, looks like you got 1... I hope it doesnt sour your attitude towards a really good product, as long as it works....
Click to expand...
Click to collapse
I thought that I should let you guys know the outcome.
I was not soured at all, I took it back to the store, and was told that they would have to return it
So while I was there I bought a N8000
Jelly Beaned it, rooted etc This thing rocks
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
ricarpe said:
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
Click to expand...
Click to collapse
Same thing happened to me on Wednesday. Stock ROM, S-Off, perm root and a few minor modifications. Screen timed out as normal after a little bit of usage and about 40% battery life left, went to pick it up and turn it on and it was completely dead, for what ended up being about six hours or so. Called Verizon to have my old phone reactivated until I figure out what I'm going to do. Tried everything from pressing combo of buttons, charging, adb commands, no luck. HTC one came back on after I plugged it into the wall and held power. So I called Verizon to reactivate it. Verizon offered me a brand new device since I am still within my 2 week period for a return. I have until this Saturday to return the device, but everything has been fine these past couple days. Still not sure what I'm going to do. It's almost as if the device was completely stuck or frozen until the battery died, then when I plugged it in again it powered on and showed 1% charge. It might also have something to do with Verizons new XLTE. Either way, scared the crap out of me and I was pretty frustrated for awhile. Never experienced this before and I've been rooting and ROMing devices for about 4 or 5 years.
Thought I would add, that I was sitting next to my fiance and within the 5 minutes that this happened to my device, her old samsung stellar, which is rooted and rom'd, started vibrating and was stuck vibrating for about 15 seconds before she picked it up and turned the screen on. Very strange.
Happened to me as well. It was just one time a couple weeks ago. It did this in the middle of the night, while it was on the charger for sleep. I woke up and wanted to check the time and could not wake the phone with any gestures or button press combinations. I ended up having to hold down or up (don't remember which) plus the power button and the phone eventually turned on. Sucked because I doubt my alarm would have went off.
I haven't had this with my M8, but I've had it happen in the past with my Dell Streak 7 tablet. It was a software problem. Basically like an app not responding but on a system level. Only way to fix most times was to reset.
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Kuuroki said:
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Click to expand...
Click to collapse
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
I did grant permission at first without thinking about it, until I immediately thought why the hell is Verizon asking for root, so i went into the superuser app and permanently denied permission. It was days before this happened to me.
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
hgoldner said:
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
Click to expand...
Click to collapse
Interesting..I run paranoid android on my One, and as such, have gotten rid of the Verizon bloatware.
That's slightly worrying. Verizon scares me sometimes.
In my mind, this validates my decision to go over to the CM11 nightlies and never look back.
Happened to me a couple times I just hold both volume keys then power till it restarts to simulate a battery pull cuz I always assumed it just got stuck in sleep
Sent from my HTC6525LVW using XDA Premium 4 mobile app
I've had this happen a couple times with my M8. The first time it made me late for work because my alarm clock didn't go off. Just last week I woke up and unplugged it from the charger. When I looked at the phone I noticed that the green charging light was still on solid even though the phone wasn't plugged in anymore. I held the volume keys and the power button and eventually got it to start back up. It's concerning, but I don't want to return my phone because I have an expensive Spigen glass screen protector on it. I guess I'll just hope it's a software issue and HTC will eventually get it sorted out. I'm currently running CleanROM and the CodeCraft_Final kernel.
I was quickly able to avoid the Verizon root perms. First of all I always recommend disabling play store auto update. I very rarely update apps unless the update fixes a direct issue I am having. Once I heard about the root perms, I disabled the app in settings and carried on the s off process (eventually). I then searched carefully for a ROM w/o my Verizon included and flashed cleanrom and that's where I'm at now. All these threads are making me scared to reboot my device lol. Only hope I have in finding some info about this is a rogue Verizon employee
Sent from my HTC6525LVW using Tapatalk
It isn't necessary to hold both volume keys, just volume up and power.
Some kind of an issue with Verizon bloat acting up?
I disabled most of Verizon preinstalled bloat and I've never seen this issue.
andybones said:
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
Click to expand...
Click to collapse
I am a little disappointed.. you didn't take your phone with you into the bathroom? Lol. this happened to me after I tried an aosp Rom for the first time then went back to my stock rooted with soff and thinking about it now I accidentally allowed root permission to Verizon application which I quickly disabled in su. I didn't think much of it considering I thought it was something I had done or maybe battery died but it only lasted about 5 minutes rebooted and I was good. I remember on a previous HTC phone if you had a bad Rom and radio/kernel combo the phone would act vertually dead even if the battery was fully charged.
This just happened to my M8. I rebooted it and it didn't reboot. When plugged in, the LED didn't come on. Rooted, S-OFF, running pretty close to stock ROM with an unvervolted, overclocked kernel. I've let the phone sit for about 24 hours now. Have ordered a warranty replacement, but may try once or twice more to see if it springs back to life. Very strange. Can't get into hboot or any other key combination. For all intents and purposes it is a brick. (If it can't register a charge, it won't take adb).
Even if it does come back from the dead, I'm not taking a chance and swapping it out.
UPDATE: Truly bizarre. Returned to life and rebooted in response to power-volume up about 26 hours later. Battery had dropped from 80% to 40%. Rebooted like nothing had ever happened. Editing this on it now.
This happened to my first m8, what I believe is happening is they are going into the bootloader, but the backlight is off. I didn't notice until I held it under a bright light and saw there was something in the screen. Afterwards I was able to navigate to reboot the device. Or you can try simulating a battery pull. Just something to try before you write your baby off as dead.
Sent from my HTC6525LVW using XDA Free mobile app
Sounds like SOD.