Related
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 went to take my break at work, phone in hand, working, put it in my pocket. Signed out, proceeded to the elevators to go downstairs, take it back out and no response. Okay. Fine. Hold power...nothing. Pop the battery out for 30ish seconds, back in, case on...power...still nothing. Get to my car thinking maybe it died even though it had 50% left to the battery. Plug it into my car mount and the LED doesn't light up. I work minutes away from a Verizon store so I decide to stop by. I explain to the rep what was going on, he plugs it in and nothing. He tries a different battery and nothing. We both tried vol up + power + home and nothing.
I have not rooted my phone, and the only thing I did recently was factory reset it over the weekend just to give it a "fresh start."
After I got home not too long ago, plugged the phone in using the cable I usually take with me (just happened to leave it home today of course) and no response from the phone. However, if I remove the back cover and take the battery out the LED light DOES come on if I plug the phone in again for several minutes and then it goes out.
From what I've read here and elsewhere there was something about a bad EMMC chip that caused phones to just suddenly die, could this possibly be it?
Thanks.
Sounds like a hard brick to me. Try this
http://m.youtube.com/watch?v=dU5H8NJ7vTM&desktop_uri=/watch%=dU5H8NJ7vTM
Sent from my SCH-I535 using Tapatalk 4
If ur not rooted wat so ever then jst get a warranty replacement
If you don't have the ability to software flash it or if you honestly think its a hardware issue you could try getting a warranty replacement through your carrier as suggested or if you'd like to keep your phone and not get a refurb and are willing to wait a couple weeks, you could always send it to Samsung for warranty repair.
Feel free to pm me if you wanna troubleshoot
Sent from CM 10.2 optimized sph-l710
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.
Hu guys. Long story short. I was out for awhile yesterday and when i got home i could not connect to my wifi. I tried turning wifi off and back on but it would not even turn off! When i toggled wifi to off nothing would happpen..................almost as if it got 'stuck' and also some apps started randomly forced quitting. I turned the phone off and back on and all was fine again
Then last night i woke in the middle of the night and hit the power button to wake the phone so i could check the time but the phone didnt respond. Puzzled i figured i must have turned the phone off accidentally so i pressed again but this time holding the button down as if to power on the device but again, nothing! I started getting worried at this stage and eventually though wait, the battery must be dead (no idea how but it must be) but when i plugged in the charger again nothing happened! It was as if the device was literally dead! I went back asleep and figured i would just have to bring the phone into the store i bought it from and hopefully be given a replacement but when i woke up this morning i decided to hold the power button and the volume button (a hard reset?) anyways the phone vibrated as if to be revived back to life and then powered on and has been fine ever since??
Should i be worried or what? Anyone have any ideas what happened? I can honestly say i havent tampered with the phone or tried to root or anything like that so i have no idea what happened! Iam just worried incase its a problem with the device as i have it around 3 weeks now and i think it has to be returned as faulty within 31 days to get a replacement! The weird thing is, its working fine again now with no issues?
if it's the sleep of death whilst charging, try a free app called safe charge from the store - admittedly, this doesn't account for the wifi issue though - I'd roll with it, but then take it back if there's any recurrence - 12 month statutory guarantee minimum presumably?
deepershades said:
if it's the sleep of death whilst charging, try a free app called safe charge from the store - admittedly, this doesn't account for the wifi issue though - I'd roll with it, but then take it back if there's any recurrence - 12 month statutory guarantee minimum presumably?
Click to expand...
Click to collapse
It wasnt while charging! Its as if the phone just died for no reason and wouldnt respond to anything until the following morning when i did a rest i think its called ( press the power and volume button together) Hopefully its not a serious problem as Vodafone are difficult to deal with when it comes to faulty handsets! I was told before the device has to be returned as faulty and confirmed THREE times before they will give you a replacement! In other words iam not entitled to a new phone . Iam only entitled to have it sent away for repair (which can take 2/3 weeks) and ive no insurance so not entitled to a replacment phone until it comes back! They will only hand out a new phone if the current one is verified as being faulty after THREE attempts to fix the issue! This is what i was told at least although i was told this 3/4 years ago
Blaalad12 said:
It wasnt while charging! Its as if the phone just died for no reason and wouldnt respond to anything until the following morning when i did a rest i think its called ( press the power and volume button together) Hopefully its not a serious problem as Vodafone are difficult to deal with when it comes to faulty handsets! I was told before the device has to be returned as faulty and confirmed THREE times before they will give you a replacement! In other words iam not entitled to a new phone . Iam only entitled to have it sent away for repair (which can take 2/3 weeks) and ive no insurance so not entitled to a replacment phone until it comes back! They will only hand out a new phone if the current one is verified as being faulty after THREE attempts to fix the issue! This is what i was told at least although i was told this 3/4 years ago
Click to expand...
Click to collapse
You're not entitled to a new phone - you could well get a repair or a refurb. Are you sure you've not enabled stamina mode, or one of its variants, and it was just offline overnight?
I was just using it normally today,
The battery was down to some 23%, charged it a bit to aprox 40%
then suddenly every locked up, and it went dim, and then dead
I plugged it into the Quick charger (original HTC factory and original cable), and it's still unresponsive.
it was rooted and running Viper ROM 1.4
Currently it's cold as ice, normally while charging it should be Warm.
Tried the Button Down + Power Button for 15 sec, many times unsuccessfully.
Normally that will bring it back from whatever lock up, but this time nothing, totally unresponsive.
AllGamer said:
I was just using it normally today,
The battery was down to some 23%, charged it a bit to aprox 40%
then suddenly every locked up, and it went dim, and then dead
I plugged it into the Quick charger (original HTC factory and original cable), and it's still unresponsive.
it was rooted and running Viper ROM 1.4
Currently it's cold as ice, normally while charging it should be Warm.
Tried the Button Down + Power Button for 15 sec, many times unsuccessfully.
Normally that will bring it back from whatever lock up, but this time nothing, totally unresponsive.
Click to expand...
Click to collapse
Did you update to Viper ROM 1.6 and have you tried booting into Download Mode?
8bitbang said:
Did you update to Viper ROM 1.6 and have you tried booting into Download Mode?
Click to expand...
Click to collapse
it wont even turn on.
I was with HTC tech support for the past hour, and we tried everything.
so, now it's going straight for warranty
it wont charge, it wont turn on, it doesn't accept any of the known keys combinations to get it into the download mode.
the weird thing is that everything was working just fine and normal, until moments before I left office.
it was hard to turn on, so i though oh no problem, I'll just restart it.
Restart it went, it came back, but then shortly later it went again into that annoying deep sleep mode, and was able to bring it back on, once more
but by the time I walked from the office to the car, the phone turned off again, and it remained dead since then.
apparently it's a "Known Issue" since it's in the most asked FAQ list in HTC support help page.
hmm... funny they just hid that FAQ, and replaced it with http://www.htc.com/ca/contact/produ...ent=GUID-780CE6E8-1156-4527-8980-445582D60A70
there was another similar one, but it was specific to some power issues, similar to this one http://www.htc.com/ca/contact/produ...ent=GUID-599060AE-0591-4FA1-B77F-C6A635196E49
AllGamer said:
it wont even turn on.
I was with HTC tech support for the past hour, and we tried everything.
so, now it's going straight for warranty
it wont charge, it wont turn on, it doesn't accept any of the known keys combinations to get it into the download mode.
the weird thing is that everything was working just fine and normal, until moments before I left office.
it was hard to turn on, so i though oh no problem, I'll just restart it.
Restart it went, it came back, but then shortly later it went again into that annoying deep sleep mode, and was able to bring it back on, once more
but by the time I walked from the office to the car, the phone turned off again, and it remained dead since then.
apparently it's a "Known Issue" since it's in the most asked FAQ list in HTC support help page.
hmm... funny they just hid that FAQ, and replaced it with http://www.htc.com/ca/contact/produ...ent=GUID-780CE6E8-1156-4527-8980-445582D60A70
there was another similar one, but it was specific to some power issues, similar to this one http://www.htc.com/ca/contact/produ...ent=GUID-599060AE-0591-4FA1-B77F-C6A635196E49
Click to expand...
Click to collapse
It does sounds like a hardware problem. I hope they send a replacement phone soon.
ShyamSasi said:
It does sounds like a hardware problem. I hope they send a replacement phone soon.
Click to expand...
Click to collapse
That's the thing that sucks
it's already after 30 days, so they can't do a straight swap
that means i'll need to mail it in for warranty repair, which takes several weeks, plus the shipping back and forth that's at least 6 to 8 weeks down time
AllGamer said:
That's the thing that sucks
it's already after 30 days, so they can't do a straight swap
that means i'll need to mail it in for warranty repair, which takes several weeks, plus the shipping back and forth that's at least 6 to 8 weeks down time
Click to expand...
Click to collapse
It has been 6.5 weeks for me. Had to send it in two weeks after receiving it with a different problem. Repair actually took 2.5 weeks, while the spare parts sent right from Taiwan needed 4.5 weeks to arrive in Europe.
Return period in Germany is only 14 days so I had to take the warranty repair as well.
Sent from my HTC U11 using XDA Labs
5m4r7ph0n36uru said:
It has been 6.5 weeks for me. Had to send it in two weeks after receiving it with a different problem. Repair actually took 2.5 weeks, while the spare parts sent right from Taiwan needed 4.5 weeks to arrive in Europe.
Return period in Germany is only 14 days so I had to take the warranty repair as well.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
where you have bought ?
andrea1493 said:
where you have bought ?
Click to expand...
Click to collapse
o2 Germany. Repair center is in Poland.
Sent from my HTC U11 using XDA Labs
AllGamer said:
That's the thing that sucks
it's already after 30 days, so they can't do a straight swap
that means i'll need to mail it in for warranty repair, which takes several weeks, plus the shipping back and forth that's at least 6 to 8 weeks down time
Click to expand...
Click to collapse
I think if you make enough noise at the support or escalate it maybe through Social media, then they might send you a replacement device instead of a repair. Sometimes these support centers would have escalation processes in place for such situations but won't really honor it until the customer start making noise. Especially HTC would try and minimize bad PR.
Yesterday the same happend to me.
I had the feeling that the battery connector wasn't properly connected/disconnected, so I searched for a picture to see if by pushing on the back of my device i could reconnect the battery connector (see this pic and this pic). Luckily this worked for me so now i can backup my data and exchange it (also luckily, im still within the voluntary 14 day returning period of my provider).
Hope this helps someone else too.
Mine is gone 2 days ago too.
When I woke up in the morning, I saw it's still on the charger, but soon I found the device is gone and I checked some log (I have configured Syncthing to do some backup to my PC, unfortunately, I only paired the device but no task is configured yet.) and found the device is just gone around I woke up.
Tried all combinations including vol+ & vol- & PWR for 30secs~2mins, none of them work. Pressing around battery connector doesn't work still.
Its cold as a brick. No response when I plug it to my MacBookAir, but shown as an unknown device on my Windows7 Desktop.
Now I'm waiting for it self recovery since I still not backed up my internal storage yet, and my data won't be guarantee if I send it back to HTC.
No solution yet. Just an echo for the topic.
A small update.
So, after I sent it in for Repair... damn HTC finally fixed the phone and send it back to me after 6 months.
The worst experience ever.
I got the same issue as well. My phone just went dead on me today. It does response to anything at all. May I know from those who experienced before what is the cause of the problem? What did the service center do to help out?
Happened to me today. After having it 5 months,warranty exchange.
Mine HTC U 11 turned off since 23-01-2019. Not charging . not turning. Nothing is working. I am from India. I could not find any authorized service center for HTC here too. .
What to do now.
Please suggest me what to. If any one can.
Mail : [email protected]