Related
So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.
stealth.kid said:
So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.
Click to expand...
Click to collapse
It reminds me Desire S problem - fried emmc chip... If your phone has no valid warranty, I'm suggesting to see phone's internals and inspect emmc chip.
The phone still has warranty, I will try to have it repaired/replaced. The only thing I'm concerned about is the fact that it was S-OFF and running a custom ROM... And I don't have the knowledge or equipment to try to take it apart and fix it myself
If you have warranty just use it they won't be able to ckeck if phone was unlocked or not since it can't boot up.
Hello Everyone,
I'd be eternally grateful for any technical advice and wisdom anyone that can help with my issue! I have a previously rooted phone that I have to return for a warranty, but the bootloader is unlocked and I can't lock it again.
Here is the problem, my phone completely shuts off about 10 seconds after the screen turns off. It's a full shut down, not just the screen not turning back on.
Some other symptoms:
My phone won't power on while it's plugged into the wall outlet. I have to remove it from the charger for it to turn on. But it will charge while the phone is ON and I plug it into the wall outlet afterwards.
My phone will automatically shut off when I plug it into any USB cable connected to a computer that's on (however, it doesn't automatically shut off if I plug it into the wall charger while it's on)
When I press power and volume down for ODIN or volume up + volume down for the bootloader screen, both screens will only show up briefly, then the phone will immediately shut down. I can't access either menus.
I have tried swapping out my battery with my wife's, and it does the same thing. Her phone works perfectly fine with my battery, mine doesn't work with either. (We have the same phone).
I rooted my phone a little less than a year. It became unrooted quite a while back when I accidentally ran a stock update. I never messed with it since. I'm EXTREMELY rusty with rooting and custom firmware and flashing, etc., so I apologize in advance.
I'm terrified because I'm sending out my phone under that Samsung warranty because all of my tech sense tells me there's a hardware issue going on; it's not my fault. However, aren't they going to see the big "Unlock" icon under the google logo when they get my phone, and immediately say I have a voided warranty? The representative said they'd charge me $300 if they phone was "damaged".
I almost wish my phone were a complete brick and wouldn't turn on at all. But at this point without access to a bootloader menu and my phone being unrooted and not able to work with it on my computer, I'm not sure what I can do.
It's already restored completely to factory defaults through the android interface. But that "unlock" icon is still there when it boots.
Anyone have any advice for me at all? Again, if my terminology is off or I'm not being clear in some way, I apologize. Let me know and I'll clarify and/or give any more information required.
I have about three days to figure this out before the prepaid shipping box and my new phone gets here.
Thanks so much in advance.
Sincerely,
Darkencypher
Just for clarification, its the Samsung Galaxy Nexus SCH-I515.
Thanks
Darkencypher
Last chance
As I'm running short on time before my new phone gets here, I figured I'd give it another shot at seeing if anyone out there knows how to help me.
I'm nervous that the "unlock" logo that appears below the Google logo when I boot my samsung galaxy nexus means that my warranty is void. I was able to restore it back to factory defaults, but I can't remove that "unlocked" icon because the phone is so severely disabled in its current state do to some hardware problem that keeps it shutting off.
I'd settle for anyone even knowing how to turn my phone into a paperweight at this point. I'd rather it not turn on at all when they get it lest they see I've unlocked my phone and void my warranty even though I'm certain I have a hardware problem due to manufacturer defect.
Also, on a side note if anyone reads this and knows a little bit more about troubleshooting phones based on symptoms: I downloaded a program called Wake Lock and set it to keep the CPU running in the background even when the screen is off. It doesn't appear to shut off anymore when the screen turns off.
Thanks again,
Darkencypher
Hi, I know there's some threads about this already, but they don't seem to answer my problem.
Okay so my AT&T HTC One XL won't turn on
Here is what happened. I was watching a video on youtube with the phone charging from the outlet and all of a sudden it shuts off. I'm on a custom rom so I just figured it crashed. That or it shut off because I remember the phone being kind of hot. Either way I was able to turn it on again without any problems and the battery was at 20%. I started using it normally for a while and then it shut off again. This time it didn't and hasn't turned on again
When I plug it in to the wall charger no led lights, light up and when I try Power + Volume Down to turn it on nothing happens either. I did notice though that when I plug it into my PC it recognizes it (makes the usb connecting noise), but then it immediately disconnects and continues to make the disconnecting noise.
So is there any way possible to revive this phone or do I have to replace the battery or motherboard or something?
P.S. I was on KarbonKat v1.0-4, stock kernel, hboot 2.14, S-Off and I did not perform any rooting or flashing of any kind when this happened.
You might just be experiencing a power management bug. Plug the phone into an AC charger and leave it connected for eight hours or so (don't be tempted to touch it), try to power it on using the normal method, and with the volume down + power button combo, try both of those methods with and without the device connected to the charger. If you can't revive it then chances are you have a brick. But, I'd connect it again and leave it for a day or so and try again.
Sent from my Evita
Could he also utilize safe mode? To see where his issues are ?
Sent from my Inspire 4G using Tapatalk
If the phone won't boot I don't see how that will work though. Usually if you can get the device to boot after this it'll be fine.
Sent from my Evita
mudcat242000 said:
Hi, I know there's some threads about this already, but they don't seem to answer my problem.
Okay so my AT&T HTC One XL won't turn on
Here is what happened. I was watching a video on youtube with the phone charging from the outlet and all of a sudden it shuts off. I'm on a custom rom so I just figured it crashed. That or it shut off because I remember the phone being kind of hot. Either way I was able to turn it on again without any problems and the battery was at 20%. I started using it normally for a while and then it shut off again. This time it didn't and hasn't turned on again
When I plug it in to the wall charger no led lights, light up and when I try Power + Volume Down to turn it on nothing happens either. I did notice though that when I plug it into my PC it recognizes it (makes the usb connecting noise), but then it immediately disconnects and continues to make the disconnecting noise.
So is there any way possible to revive this phone or do I have to replace the battery or motherboard or something?
P.S. I was on KarbonKat v1.0-4, stock kernel, hboot 2.14, S-Off and I did not perform any rooting or flashing of any kind when this happened.
Click to expand...
Click to collapse
You can find my thread from a little over a month ago in this section but I experienced a similar thing and well it's fatal I bought a battery and tried that but it didn't help, it's currently in the hands of datarecovery.com who are looking at it before giving me a quote to get everything off of it. I don't want to give you false hope but odds are it's toast and it seems like something that's happening more often with the XL now that it's closing in on 2 years for most people.
I read that it could because faulty power button.
Sent from my Inspire 4G using Tapatalk
timmaaa said:
You might just be experiencing a power management bug. Plug the phone into an AC charger and leave it connected for eight hours or so (don't be tempted to touch it), try to power it on using the normal method, and with the volume down + power button combo, try both of those methods with and without the device connected to the charger. If you can't revive it then chances are you have a brick. But, I'd connect it again and leave it for a day or so and try again.
Sent from my Evita
Click to expand...
Click to collapse
I tried this and unfortunately it didn't work.
I also doubt it is a power button issue because when i plug it into my PC and hold the power button it makes the usb connected noise.
I think it's safe to say that I have a new paperweight. I would just like to know if there's any guess that could be made as to why my phone died (ex: battery, motherboard, etc.) and how the PC detects it if its supposedly dead.
mudcat242000 said:
I tried this and unfortunately it didn't work.
I also doubt it is a power button issue because when i plug it into my PC and hold the power button it makes the usb connected noise.
I think it's safe to say that I have a new paperweight. I would just like to know if there's any guess that could be made as to why my phone died (ex: battery, motherboard, etc.) and how the PC detects it if its supposedly dead.
Click to expand...
Click to collapse
Your phone is possibly not completely dead, you might be able to get a jtag repair done on it. It's definitely worth a try, especially seeing that you still get the connection sound when you hook it up to your PC.
Sent from my Evita
Why is it that no one here ever suggests sending the phone to HTC? My phone bricked once (QHSUSB_DLOAD); I contacted HTC and told them my phone shut off and wouldn't come back on, which was the honest truth and seems to be your problem, and they fixed it for free (I had to pay for shipping.) Other users here have reported similar outcomes from contacting HTC, all with unlocked bootloaders. Before shelling out for JTAG I'd definitely recommend contacting HTC.
nem1yan said:
Why is it that no one here ever suggests sending the phone to HTC? My phone bricked once (QHSUSB_DLOAD); I contacted HTC and told them my phone shut off and wouldn't come back on, which was the honest truth and seems to be your problem, and they fixed it for free (I had to pay for shipping.) Other users here have reported similar outcomes from contacting HTC, all with unlocked bootloaders. Before shelling out for JTAG I'd definitely recommend contacting HTC.
Click to expand...
Click to collapse
HTC routinely charge $200 for a motherboard replacement on devices that have been modified. Plus, the vast majority of Evitas are out of their warranty period now.
Sent from my Evita
http://forum.xda-developers.com/showthread.php?t=2071358&highlight=wip
http://forum.xda-developers.com/showthread.php?t=1651149
http://forum.xda-developers.com/showthread.php?t=2319085
Call and ask first. As with others and myself, HTC has fixed devices that were outside of the warranty (both due to time and unlocked bootloader) at no cost to the owners. At worst they'll tell you it's outside of the warranty, or you'll have spent $5 in shipping for them to tell you that they can either send it back to you, or replace it for the ~$200 timmaaa has suggested.
It's definitely worth a try.
Sent from my Evita
timmaaa said:
It's definitely worth a try.
Sent from my Evita
Click to expand...
Click to collapse
I called last month and it was min $90 and nothing would be backed up all data would be wiped.
@mudcat. If you have HTC repair it ,could you ask the RMA team what exactly what your issue was, and then post here their answer? We would appreciate it.
Thanks
marknoll said:
@mudcat. If you have HTC repair it ,could you ask the RMA team what exactly what your issue was, and then post here their answer? We would appreciate it.
Thanks
Click to expand...
Click to collapse
I will definitely do that for you.
Thank you to everyone for all the help. I will contact HTC and see what they can do for me and keep you all posted.
Is there a specific HTC repair website that I go to or do I just call their number?
HTC.com
mudcat242000 said:
I will definitely do that for you.
Thank you to everyone for all the help. I will contact HTC and see what they can do for me and keep you all posted.
Click to expand...
Click to collapse
Very interested to hear what they say, please update when possible
Any update?
Hello everyone,
This morning while I was having coffee, my phone started playing jokes on me. At first it got really slow while doing the easiest things, like checking a mail, send a text and make a phone call. 10-15 After that I get a notification, Phone was locked, I tried to unlock it. I did spam the button like 5-10 times, Screen won't come up, but notification LED was working. At that point I thought that the power button was pretty much done for. Nope not the case. I held it down for 10 seconds, phone actually powered down. No chance in hell I could turn it back on. At that point I just went home. Got home plugged the phone into my PC. As soon as I did that, Windows started to check for a driver, had to wait almost 5 minutes to find QHSUSB_BULK.
Now, doing a bit of a search I found out that this could be the result of different problems, One that has to do with the memory just dying cause yeah, Nexus 5 and the eternal memory problem +Lollipop screw around with Data partitions, another that has to do with Roms, another that had to do with custom recovery.
What the hell is in my case? I run a custom Rom and a custom recovery, Atm I have Cyanogenmod 12.1 and lateste TWRP recovery.
I have a handful of tools at my disposal, a Cable, a good keyboard and a iron will.
In this case, Can I do something to fix my phone from home? Can't really send into warranty as I have custom software that's running on it and I'll just get a generic response that basically tells me that my warranty was voided due to custom software running on the terminal. We all love generic response like that, Don't we?
TLR: Phone died this morning, I couldn't unlock the screen and I thought it was the power button be cause, the notification led was still working. At that point I just powered it down by holding the power button down for 10 sec.
I wasn't able since to power it back on. If I connect it to my PC I get QHSUSB_BULK.
Hopefully there's some one who can point me in a direction ASAP. I have no backup phone atm and I really need this one to actually be ALIVE again.
Can't send it to Warranty because I run custom software on it. GSM Services/Fix Shops are out of the question too.
Pls halp ASAP
Will pay in Galactic Credits.
Thanks!
Your best bet is to try this, http://forum.xda-developers.com/showthread.php?p=51823398. Good luck, your device is not in a good state.
Sent from my Nexus 9 using XDA Free mobile app
metalheadbk said:
Hello everyone,
This morning while I was having coffee, my phone started playing jokes on me. At first it got really slow while doing the easiest things, like checking a mail, send a text and make a phone call. 10-15 After that I get a notification, Phone was locked, I tried to unlock it. I did spam the button like 5-10 times, Screen won't come up, but notification LED was working. At that point I thought that the power button was pretty much done for. Nope not the case. I held it down for 10 seconds, phone actually powered down. No chance in hell I could turn it back on. At that point I just went home. Got home plugged the phone into my PC. As soon as I did that, Windows started to check for a driver, had to wait almost 5 minutes to find QHSUSB_BULK.
Now, doing a bit of a search I found out that this could be the result of different problems, One that has to do with the memory just dying cause yeah, Nexus 5 and the eternal memory problem +Lollipop screw around with Data partitions, another that has to do with Roms, another that had to do with custom recovery.
What the hell is in my case? I run a custom Rom and a custom recovery, Atm I have Cyanogenmod 12.1 and lateste TWRP recovery.
I have a handful of tools at my disposal, a Cable, a good keyboard and a iron will.
In this case, Can I do something to fix my phone from home? Can't really send into warranty as I have custom software that's running on it and I'll just get a generic response that basically tells me that my warranty was voided due to custom software running on the terminal. We all love generic response like that, Don't we?
TLR: Phone died this morning, I couldn't unlock the screen and I thought it was the power button be cause, the notification led was still working. At that point I just powered it down by holding the power button down for 10 sec.
I wasn't able since to power it back on. If I connect it to my PC I get QHSUSB_BULK.
Hopefully there's some one who can point me in a direction ASAP. I have no backup phone atm and I really need this one to actually be ALIVE again.
Can't send it to Warranty because I run custom software on it. GSM Services/Fix Shops are out of the question too.
Pls halp ASAP
Will pay in Galactic Credits.
Thanks!
Click to expand...
Click to collapse
Have you tried booting into secondary boot loader?
Sent from my Nexus 5 using XDA Free mobile app
But the phone won't turn on.
jd1639 said:
Your best bet is to try this, http://forum.xda-developers.com/showthread.php?p=51823398. Good luck, your device is not in a good state.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I have the exact same problem but this answer doesn't help. This solution requires that you can turn your phone on in the first place. He specifically said he can't turn the phone on at all. Same with me, no matter what I've got nothing. Need help!
metalheadbk said:
Hello everyone!
Click to expand...
Click to collapse
this is what you are looking for http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
bitdomo said:
this is what you are looking for http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
Click to expand...
Click to collapse
Thanks to everyone.
I used the board diag - clicked Start and... it said "failed to open partition from EMMC". The test aborted. I think my phone is gone for good.
Oh and I had to take the battery out, plug it in, and sometimes re-attached to latch that goes over the battery several times before I could even get it to read anything in Device Manager. Before that it would say "failed USB connection".
This all started yesterday when the phone just spontaneously put itself into a boot loop while on charge. I tried to do a factory reset but it froze. After several hours I tried to cancel it. The Nexus went full brick.
Thanks again
leopoldstotch25 said:
Thanks to everyone.
I used the board diag - clicked Start and... it said "failed to open partition from EMMC". The test aborted. I think my phone is gone for good.
Oh and I had to take the battery out, plug it in, and sometimes re-attached to latch that goes over the battery several times before I could even get it to read anything in Device Manager. Before that it would say "failed USB connection".
This all started yesterday when the phone just spontaneously put itself into a boot loop while on charge. I tried to do a factory reset but it froze. After several hours I tried to cancel it. The Nexus went full brick.
Thanks again
Click to expand...
Click to collapse
I am afraid the emmc tied then. You have to buy a new motherboard.
Tapatalk-kal küldve az én Nexus 5-el
Thanks for your help.
I posted this on the tmobile site but can't seem to get an answer. I have no idea what to do.
So I've had my phone on for at least 7 days. A notification from Samsung's plus app told me to reboot it because blah blah it helps or something.
So I turned it off.
Now it wont turn back on. Tired holding power plus volume down. Tried booting into recovery. Don't have a Windows PC irght now to plug into and try things , but will install windows on a mac via bootcamp.
When I plug it into any charger. Nothing.
When I set it atop a wireless charger. The wireless charger detects it, meaning it lights up. But the phone itself doesn't give any LED notification.
Phone gets warm while on wireless charging pad also. So it may be charging.
What is going on? Any advice?
Plug it into a charger, hold the vol down and power button for like 30 seconds then the screen should turn on saying its charging, then just power it it on.
Nothing. It gets warm when charging. But nothing.
Am I pressing it wrong maybe?
Strange that usually worked for me when i couldn't turn on my phone normally, can you get into download mode? Vol up + home + power.
Well this sucks i can't turn my phone on now, the battery was depleting somewhat rapidly so i rebooted the phone, once it got to the unlock screen it froze. Now no matter what i try i can't get it to turn on.
Today it managed to start charging, but when I turn it on when it's charging the screen freezes into a garbled mess, without charging it manages to boot.
peachpuff said:
Today it managed to start charging, but when I turn it on when it's charging the screen freezes into a garbled mess, without charging it manages to boot.
Click to expand...
Click to collapse
Same charging from PC?
Tried a different cable?
I have a Lumia 535 that messes up touch if I use my Sammy charger, same if I use my Raspberry Pi charger on my Windows tablet, the touch screen goes mental
Try a different charger / USB lead
I used various cables/chargers so that wasn't it. I went to a Samsung repair center and they suggested that... I have too many apps installed and that's causing the issue? Oooooook, granted this was just a rep and not someone doing the actual repairs.
Again my battery was low and I decided to reboot it and I can't start it again, very strange. If I get it working again it seems easy to duplicate if I goto Samsung again.
Called my credit card company and they have extended warranty on all purchases so i'm safe, the samsung store suggested to bring it in if happens again and they'll extend my warranty 3 months too.
peachpuff said:
I used various cables/chargers so that wasn't it. I went to a Samsung repair center and they suggested that... I have too many apps installed and that's causing the issue? Oooooook, granted this was just a rep and not someone doing the actual repairs.
Again my battery was low and I decided to reboot it and I can't start it again, very strange. If I get it working again it seems easy to duplicate if I goto Samsung again.
Called my credit card company and they have extended warranty on all purchases so i'm safe, the samsung store suggested to bring it in if happens again and they'll extend my warranty 3 months too.
Click to expand...
Click to collapse
Too many apps installed... how do these guys get the job in the first place, even as a rep?
It does sound hardware related, I'd probably use your 3 months ext warranty before it expires and the S7 finally commits suicide
Don't think knowledge is a requirement for these types of jobs, phone died again after a reboot and I can't start it anymore, going to the repair center after work.
It would seem not
Hopefully you get someone with at least some knowledge to help this time, likely you'll be needing a new motherboard / phone, unless it's something a bit less drastic like a dodge USB port
I thought it would be the usb port too but i tried using my wireless charger and the light on the charger was on meaning it was charging but it still wouldn't power up, i had it plugged in the whole day today and its completely dead.
Anyway it seems samsung warranty goes by build date + 1 year + 3 months leeway, unless you give them a receipt and then its just one year, so mine was built in feb 2016 so it has warranty till the end of may without a receipt.
Ah well, I suppose at least you get a new phone / board out of it, even thought it's a PITA RMAing your phone
Mine was manufactured 2016.08.16, just two weeks before I got it, so I guess that means November this year without a receipt, but pretty sure I still have the receipt anyway
They replaced the board and all is well now, first time any of my phones failed like this, and it had to be the pricey one.
They did it there and then for you? Was expecting a few days at least, nice job
Yea I've not had any failed phones to date either, hopefully not this one either
I dropped it off at 4 yesterday and it was ready by 7, i was a bit surprised by the speed too, seems they got all the parts in stock.
Can't complain about that service, makes you wonder if they have them in stock and can replace them in such a short time for a reason though... hope it's not a common fault