Database Info

[Q] Bricked? Or just battery acting up?

Hi guys
I've had the Sensation for about 3months now, and suddently yesterday it stopped working. It wont charge, no LED's and wont start at all. There have not been any waterdamage, drops or rough use.
I've read a lot concerning similar problems on this forum, but none of the solutions has worked for me.
What I can tell is that I have tried after searching the forums:
- SDK, ADB and try to reboot the device via USB-connection (device not found)
- Win7 (32bit) can't recognise the phone (asking for drivers which are not found in HTC Sync, QHSUSB_DLOAD)
- Trying to enter recovery mode (Volume Down + Power up)
- Charge the battery overnight
- Charge the battery with a plastic-piece covering the two middle pins on the battery (As suggested in a thread)
- Battery out for 1min and then put it back in and start up
Neither of these worked, so are there any other good ideas? Or is it bricked?

Hi guys,
i have exactly the same problem, already have tried all of these solutions, nothing have worked for me... Please help.
PS:sometimes my screen lights up <black totally, but lights up>... when plugged into usb cable or charger... but not now anymore...
I have bought this phone in china, there is S/N but i guess that here in UK i cannot do anything about it since HTC's warranty is not global...

listenger said:
Hi guys
I've had the Sensation for about 3months now, and suddently yesterday it stopped working. It wont charge, no LED's and wont start at all. There have not been any waterdamage, drops or rough use.
I've read a lot concerning similar problems on this forum, but none of the solutions has worked for me.
What I can tell is that I have tried after searching the forums:
- SDK, ADB and try to reboot the device via USB-connection (device not found)
- Win7 (32bit) can't recognise the phone (asking for drivers which are not found in HTC Sync, QHSUSB_DLOAD)
- Trying to enter recovery mode (Volume Down + Power up)
- Charge the battery overnight
- Charge the battery with a plastic-piece covering the two middle pins on the battery (As suggested in a thread)
- Battery out for 1min and then put it back in and start up
Neither of these worked, so are there any other good ideas? Or is it bricked?
Click to expand...
Click to collapse
Have you tried a different battery?

I just ordered a new battery... Takes a couple of days before I recieve it

listenger said:
I just ordered a new battery... Takes a couple of days before I recieve it
Click to expand...
Click to collapse
Also keep note of which recovery you are working off of. There have been charging issues with certain recoveries.

Yeah, I read several threads and posts about recovery-issues... Unfortuantly I cant check what version I got myself, as it wont start up at all :/

listenger said:
Yeah, I read several threads and posts about recovery-issues... Unfortuantly I cant check what version I got myself, as it wont start up at all :/
Click to expand...
Click to collapse
I would suggest to go to a store that sell's the Sensation and ask if you can test one of their batteries out to see if your phone has either a battery issue or something else. If you are stateside, of course try a tmobile store, but without knowing where you are located, this is a hypothetical at this point.
I know I had an issue with my Nexus1 not booting up from a kernel I had flashed. But I noticed my charging led was flashing three times and then stop. I researched this here on xda and found that it just needed to be put into recovery again somehow. I ended up just plugging the phone into the wall and remove the battery. Try to power it on there and then reinsert the battery and try the power + volume down button. That time it booted for me. But again, this was for my Nexus1 not with this phone.

same happened to me, sent to HTC and had main board replaced, lcd, flex cable etc. the driver the phone looks for is the equip HTC use to jtag... I am not sure if this is a hardware failure or boot corruption...but even though it was s-off via alpha rev it was that damaged they didnt complain... i say hardware failure. the thing is even when i have s-off i didnt change the rom. I have a riff box on order so if this happens again we can surely see if this failure is software or hardware..

Yeah, do what kpjimmy said; go to a store where Sensation's are sold and ask if you could use a battery to test it out to see if it's bricked. It it's not, you'll need a new battery (try getting one for free from HTC, citing warranty. I did it with my battery cover). If it doesn't work, you're mostly likely bricked, unfortunately. Refer to anarchy's post for more info on that side of things

Same problem here yesterday.. can't charge. But phone heat. I just pull out battery, n put back.keep repeated that. Finally can on. U use custom kernal?

arifafzan said:
Same problem here yesterday.. can't charge. But phone heat. I just pull out battery, n put back.keep repeated that. Finally can on. U use custom kernal?
Click to expand...
Click to collapse
Havn't had the time to really do any custom ROM or the like, so the phone was all original from the factory...

BRICKED! Never thought it could happen to me

Well I think I finally bricked my Nexus S. What's weird is that it's been working fine. Had JellyBro 20120817 installed for the past few days with no issues. Last night I plugged my phone in to charge and went to bed. Woke up this morning and clicked the power on button to see what time it is and it showed just fine. 20 minutes later I went to check the time again and NOTHING. Pulled battery, tried every button combo, everything. My wife has a Nexus S also, so I tried her battery with the same results. No lights, vibrations, nothing. Plugged it into my computer to see if I could get any response and still nada. Tried Fastboot and device is not found. UGH. If anyone can give me any advice on what to try feel free to chime in. I've been around long enuff to realize that I'm pretty sure it's toast. Either way... it's been a nice run.

d_phekt said:
Well I think I finally bricked my Nexus S. What's weird is that it's been working fine. Had JellyBro 20120817 installed for the past few days with no issues. Last night I plugged my phone in to charge and went to bed. Woke up this morning and clicked the power on button to see what time it is and it showed just fine. 20 minutes later I went to check the time again and NOTHING. Pulled battery, tried every button combo, everything. My wife has a Nexus S also, so I tried her battery with the same results. No lights, vibrations, nothing. Plugged it into my computer to see if I could get any response and still nada. Tried Fastboot and device is not found. UGH. If anyone can give me any advice on what to try feel free to chime in. I've been around long enuff to realize that I'm pretty sure it's toast. Either way... it's been a nice run.
Click to expand...
Click to collapse
Take it off charge and pull the battery out. Let it sit for a while (1 hour at least) without the battery. Put your wife known working battery in and cross your fingers.

polobunny said:
Take it off charge and pull the battery out. Let it sit for a while (1 hour at least) without the battery. Put your wife known working battery in and cross your fingers.
Click to expand...
Click to collapse
Tried that and still no dice. So yeah... It's done.

d_phekt said:
Tried that and still no dice. So yeah... It's done.
Click to expand...
Click to collapse
This is paranormal stuff, you have no recollection of having messed around with it flash-wise?

dinuvali said:
This is paranormal stuff, you have no recollection of having messed around with it flash-wise?
Click to expand...
Click to collapse
LOL Yeah I'm a crackflasher, but I hadn't flashed anything for a few days. It was working just fine and POOF... done.

Try odin.
Sent from my Nexus S using xda app-developers app

d_phekt said:
LOL Yeah I'm a crackflasher, but I hadn't flashed anything for a few days. It was working just fine and POOF... done.
Click to expand...
Click to collapse
I don't imagine it shows as charging when plugged in? Otherwise I'd send it for repair or just buy a new phone. :/

polobunny said:
I don't imagine it shows as charging when plugged in? Otherwise I'd send it for repair or just buy a new phone. :/
Click to expand...
Click to collapse
No it doesn't show as charging at all. Won't find device in adb, no lights, no vibration when trying to power on, nothing. It does get warm when the battery is in it tho. And it is discharging somehow, because I tried my battery in my wifes phone and it showed 33 % when I know it had a full charge before it died. GNex is on its way.

i just have had same problem days ago , unfortunately i tried all , even Odin , just non-responsive
i also tried that unbrickable tool run under Ubuntu , still no good ...
i just send it to repair... Gosh

qtwrk said:
i just have had same problem days ago , unfortunately i tried all , even Odin , just non-responsive
i also tried that unbrickable tool run under Ubuntu , still no good ...
i just send it to repair... Gosh
Click to expand...
Click to collapse
Yep, I tried the unbrickable tool also... didn't find device there either. SUX!

nexus s GT-I9020T Bricked after JellyBean
d_phekt said:
Well I think I finally bricked my Nexus S. What's weird is that it's been working fine. Had JellyBro 20120817 installed for the past few days with no issues. Last night I plugged my phone in to charge and went to bed. Woke up this morning and clicked the power on button to see what time it is and it showed just fine. 20 minutes later I went to check the time again and NOTHING. Pulled battery, tried every button combo, everything. My wife has a Nexus S also, so I tried her battery with the same results. No lights, vibrations, nothing. Plugged it into my computer to see if I could get any response and still nada. Tried Fastboot and device is not found. UGH. If anyone can give me any advice on what to try feel free to chime in. I've been around long enuff to realize that I'm pretty sure it's toast. Either way... it's been a nice run.
Click to expand...
Click to collapse
Same Problem here. It was working fine on jelly bean and rooted with clock work recovery. I removed the battery out to change the sim and now it wont power on, fastboot doesn't work and the USB JIG also doesn't work, doesn't show the charging animated when plugged in.
i tried AdamOutlers Resurector tool, it didnt detect the phone, so i made the hardware mod and now it detect the phone, but still dead after the tool loads the files. but when i choose GALAXY S from the drop down menu, the tool and the phone, both shows download mode, heimdall detect the phone but doesnt work as it is not a GALAXY S.

At least now you have a reason to upgrade. But that sure sucks, if you still want to revive it you could give this a shot... http://www.youtube.com/watch?v=Ecp8jKmm48k

Three people with Nexus S's with Jelly Been roms just spontaneously get bricked phones? Just flashed mine to CM10 Nightly yesterday...
Hmmmm

I'm not sure if I would call mine a true bricking since most bricks happen directly from a rom flash. Mine was actually working fine for a couple of days after my last flash and then suddenly stopped working. It was an almost 2 year old phone and heavily abused internally with almost daily rom/kernel flashes and overclocking. I think maybe it just got tired LOL. Oh well...we have 2 other Nexus S's in our house, so now we have a decent parts phone since externally the phone is flawless.

Try cleaning your the phone's usb slot with a toothbrush and medical alcohol. also after removing your battery, try pressing the power button for 10 Secs(without battery) this cleans any extra charges in your phone. Gd luck!

Sounds more like hardware failure than bricking.
Sent from my Crespo using xda premium

i read something that is problme of bootloader that messes with hummingbird CPU or something , i don't know
i had flashed the latest bootloader and 4.1 once it came out , but then i back to 4.0.4 and decided wait for AOKP JB.
and , my phone was also unable to power up after i pull out and change a new battery ! , first of all i was thinking battery's unstable output current damaged hardware or something , but now i am more convinced it should be the problem of bootloader as i read before

[Q] May Have Bricked...

Forgive me if I'm missing something obvious; this is the first time I've rooted, so I'm still a bit new to all of this (though I have been reading around for weeks now).
So I just received my One X back from HTC today (needed to be fixed, don't ask), and, seeing that 2.20 had finally been rooted, got right to work in unlocking the bootloader. An hour later, I had CM10 flashed, installed, and running great (including separately flashing the boot.img). Installed most of my old apps, configured settings, everything was working great (tested calls, texts, HSPA+, and wifi). While I was setting a new voicemail message through AT&T Visual Voicemail, I started talking to a friend of mine (not on the phone), and the phone went to sleep. No big deal, I figured. However, I can't get the screen to turn back on now, and I'm a bit concerned. I don't think the phone's off, because it won't boot into bootloader (nothing happens when I press the power or the volume keys, no matter how long I hold for), and nothing happens when I plug into my computer either (the LED charging light doesn't even change). The only strange thing I can think of that could have caused this is that I had originally installed AOKP Milestone before going to CM10, and though I did a factory reset and reflashed boot.img before installing CM10, I didn't do a complete system wipe.
Does anybody have any idea what's going on? I sincerely hope I haven't bricked my phone... I'm going to try plugging it into a wall outlet for a little while and see if that makes a difference. Thanks in advance for any help!

So it just rebooted itself... I don't think I had anything to do with it; I'm pretty sure I wasn't pressing anything at the time. So at the very least, I have a working phone; however, I'd like to figure out what happened so that I can prevent it from happening again, particularly at a time where I actually need to call someone. Anybody have any idea what could have happened?

i heard VVM has problems with aosp roms.

Visual voicemail is getting trouble.. at the same time, it sounds like a good case of the sleep of death.. I tend to keep mine over clocked with a minimum of at least the 500's.
Sent from my One X using Tapatalk 2

InflatedTitan said:
Visual voicemail is getting trouble.. at the same time, it sounds like a good case of the sleep of death.. I tend to keep mine over clocked with a minimum of at least the 500's.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
How would overclocking help with this problem? Sorry for cluelessness, I'm just really new to this stuff.

flash the roms stock kernel

Sort of the same issue
My phone has been completely black for about 3 hours now. when i hold the power button none of the lights flash. I rooted my phone today and installed CM10 but it didn't work right so i decided to try another one. I used icecoldjelly and later found out that it was only for the international version. i tried to reboot my phone through TWRP and now it won't turn on. at all so i can't do anything with it. when it's plugged into my computer and i hold the power button, I hear the connect, then disconnect sound repeatedly until i let go. but there is no response on the phone.:crying:
help please. this is an expensive paperweight that i have here.

cakeballs said:
My phone has been completely black for about 3 hours now. when i hold the power button none of the lights flash. I rooted my phone today and installed CM10 but it didn't work right so i decided to try another one. I used icecoldjelly and later found out that it was only for the international version. i tried to reboot my phone through TWRP and now it won't turn on. at all so i can't do anything with it. when it's plugged into my computer and i hold the power button, I hear the connect, then disconnect sound repeatedly until i let go. but there is no response on the phone.:crying:
help please. this is an expensive paperweight that i have here.
Click to expand...
Click to collapse
Lucky for us, absolutegrim wrote a guide on how to unbrick. Head over to the general section and look for the "unbricking Evita" thread, it may be down a few pages.

Ice Cold Jelly strikes again....
cakeballs said:
My phone has been completely black for about 3 hours now. when i hold the power button none of the lights flash. I rooted my phone today and installed CM10 but it didn't work right so i decided to try another one. I used icecoldjelly and later found out that it was only for the international version. i tried to reboot my phone through TWRP and now it won't turn on. at all so i can't do anything with it. when it's plugged into my computer and i hold the power button, I hear the connect, then disconnect sound repeatedly until i let go. but there is no response on the phone.:crying:
help please. this is an expensive paperweight that i have here.
Click to expand...
Click to collapse
bricked it is but hopefully not permanently see here http://forum.xda-developers.com/showthread.php?t=1966850

Ouch
cakeballs said:
My phone has been completely black for about 3 hours now. when i hold the power button none of the lights flash. I rooted my phone today and installed CM10 but it didn't work right so i decided to try another one. I used icecoldjelly and later found out that it was only for the international version. i tried to reboot my phone through TWRP and now it won't turn on. at all so i can't do anything with it. when it's plugged into my computer and i hold the power button, I hear the connect, then disconnect sound repeatedly until i let go. but there is no response on the phone.:crying:
help please. this is an expensive paperweight that i have here.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1966850

Right now, there isn't a fix for an ICJ brick. Absolutelygrim makes note of this on the last page of the thread. He is working like a mad man to get it.
I hate to be blunt, but read the threads carefully, pay attention to some of the posters signatures. There are multiple threads and multiple people who have links in their signatures to those threads(see mine). Just check back to the unbrick evita thread frequently. It will get fixed. I turned my phone over to grim and let hum brick it on purpose to downgrade my Hboot. So the method that's posted in the thread, works... Just not for ICJ, yet.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz

Unless I get ahold of a bricked phone.. Then I can bring a JTAG into this.. Neither my method or yarr's method will work for an ICJ flash on 2.20..
We are probably 5 feet away from a brick wall while traveling at 80 mph.. That's the best way to put it, we are almost out of ideas

absolutelygrim said:
Unless I get ahold of a bricked phone.. Then I can bring a JTAG into this.. Neither my method or yarr's method will work for an ICJ flash on 2.20..
We are probably 5 feet away from a brick wall while traveling at 80 mph.. That's the best way to put it, we are almost out of ideas
Click to expand...
Click to collapse
It's really looking like JTAG will be the only option, and even then it still might not work...
Sent from my HTC One XL cellular device over clocked to 1.9Ghz

[Q] Bizarre HTC One X Charging/USB problem!!

I'm hoping some of you wise heads on here might be able to help me out with a problem that has got me totally and utterly stumped!
Last week I was using my One X and noticed the battery was down to aorund 14%. I plugged it into a charger and nothing happened...no light...nothing. I tried various different chargers and cables to pc etc and nothing seemed to do anything.
After leaving the phone plugged into the mains for a few hours, I noticed that a very slow/long flashing red/amber light appeared. It kind of stays on for 5 seconds and then off for the same amount of time. I left the phone in this state for about 14 hours and when turning on it would say battery was somewhere between 0%, 1% and 2% and would promptly switch itself off.
I messed about for hours on end trying many different button combinations, sim in/out and came to this bizarre conclusion.........If I plug the phone into the mains for a few minutes, then press power and volume down to get to the HBOOT menu then hold power in again to reboot, the phone reboots into the OS and is functional. It still reads as having 0% or 1% battery and shows as not charging, but it must be getting some juice for it to be working. If I leave the phone in this state for a while I can then unhook it from the charger and use it as normal, even though battery is displaying as 0%. I can use the phone like this for some time, although the battery does not appear to last as long.
Also, the phone is not recognised at all by the PC when plug in via usb when in android os - nothing at all shows in device manager, but it is recognised from the fastboot menu and tries to install device drivers.
Has anybody got any clue if I can save my HOX or am I without a paddle?? Many thanks in advance

Baz030385 said:
I'm hoping some of you wise heads on here might be able to help me out with a problem that has got me totally and utterly stumped!
Last week I was using my One X and noticed the battery was down to aorund 14%. I plugged it into a charger and nothing happened...no light...nothing. I tried various different chargers and cables to pc etc and nothing seemed to do anything.
After leaving the phone plugged into the mains for a few hours, I noticed that a very slow/long flashing red/amber light appeared. It kind of stays on for 5 seconds and then off for the same amount of time. I left the phone in this state for about 14 hours and when turning on it would say battery was somewhere between 0%, 1% and 2% and would promptly switch itself off.
I messed about for hours on end trying many different button combinations, sim in/out and came to this bizarre conclusion.........If I plug the phone into the mains for a few minutes, then press power and volume down to get to the HBOOT menu then hold power in again to reboot, the phone reboots into the OS and is functional. It still reads as having 0% or 1% battery and shows as not charging, but it must be getting some juice for it to be working. If I leave the phone in this state for a while I can then unhook it from the charger and use it as normal, even though battery is displaying as 0%. I can use the phone like this for some time, although the battery does not appear to last as long.
Also, the phone is not recognised at all by the PC when plug in via usb when in android os - nothing at all shows in device manager, but it is recognised from the fastboot menu and tries to install device drivers.
Has anybody got any clue if I can save my HOX or am I without a paddle?? Many thanks in advance
Click to expand...
Click to collapse
Is your phone completely Stock? or is it bootloader unlocked/rooted? I'm pretty positive this is a hardware issue, you can rule it out by RUUing if you're Stock. If you're not stock, you can still RUU but if you should S-OFF first.

exad said:
Is your phone completely Stock? or is it bootloader unlocked/rooted? I'm pretty positive this is a hardware issue, you can rule it out by RUUing if you're Stock. If you're not stock, you can still RUU but if you should S-OFF first.
Click to expand...
Click to collapse
Thanks for the quick repIy. I was hoping you weren't going to say a hardware issue :crying: The phone is totally stock and unrooted. This might be a stupid question, but if I RUU will I lose all the data on my phone? Also any idea which RUU to use? My HOX is an unlocked, unbranded version bought in the UK.

Baz030385 said:
Thanks for the quick repIy. I was hoping you weren't going to say a hardware issue :crying: The phone is totally stock and unrooted. This might be a stupid question, but if I RUU will I lose all the data on my phone? Also any idea which RUU to use? My HOX is an unlocked, unbranded version bought in the UK.
Click to expand...
Click to collapse
Sorry for the bad news, I would repost in the international one x forum as you have a different phone as us Quad core VS Dual core. I don't think the response will be much different but they should also have the proper RUU links for your phone. Good Luck.

Ok I'll do that. Thanks for the advice, it is greatly appreciated.

Baz030385 said:
Ok I'll do that. Thanks for the advice, it is greatly appreciated.
Click to expand...
Click to collapse
Hello there!
I have same issue, but when I flash a kernel. I flashed the AlexV 2.4 RC kernel and usb masstorage works again. BUT becuse I wipe battery status some times now if y boot the phone chargin, it sais that is chargin, but when I disconnect the cable still chargin
Anyway, I have HTC One X tegra 3 quadcore from argentina. And all this chargin issues is about the kernel/rom tweaks. If you boot on recovery and the phone charge ok (sho the led) and the mount of the sd on recovery works, its 100% rom/kernel problem.

deftoner said:
Hello there!
I have same issue, but when I flash a kernel. I flashed the AlexV 2.4 RC kernel and usb masstorage works again. BUT becuse I wipe battery status some times now if y boot the phone chargin, it sais that is chargin, but when I disconnect the cable still chargin
Anyway, I have HTC One X tegra 3 quadcore from argentina. And all this chargin issues is about the kernel/rom tweaks. If you boot on recovery and the phone charge ok (sho the led) and the mount of the sd on recovery works, its 100% rom/kernel problem.
Click to expand...
Click to collapse
You're in the wrong forum dude, this is the HTC One XL forum.
Sent from my Evita

woops, sorry. My bad.
But I guess is the same for almost any smartphone.
thanks and sorry
---------- Post added at 04:09 AM ---------- Previous post was at 04:07 AM ----------
woops, sorry. My bad.
But I guess is the same for almost any smartphone.
thanks and sorry

[Q] Htc mini appears to be totally dead ?

Hi guys.
so just picked up my phone (was connected to charger) to realize that is dead! the screen is totally black,no charging/notification lights and touch buttons are not illuminated and wont power on or take a charge. tried to connect to pc but adb keeps saying "waiting on device" and thats it.
the phone is unlocked,rooted, jmz TWRP recovery and cm11.....has been running fine for the past week.
it appears to have died a sudden death....any ideas guys ???
cheers
EDIT: dunno what the hell happened as nothing was turning it back on BUT after after holding down power button and volume down for about a minute the damn thing booted up SORTED!!

Braddison said:
Hi guys.
so just picked up my phone (was connected to charger) to realize that is dead! the screen is totally black,no charging/notification lights and touch buttons are not illuminated and wont power on or take a charge. tried to connect to pc but adb keeps saying "waiting on device" and thats it.
the phone is unlocked,rooted, jmz TWRP recovery and cm11.....has been running fine for the past week.
it appears to have died a sudden death....any ideas guys ???
cheers
EDIT: dunno what the hell happened as nothing was turning it back on BUT after after holding down power button and volume up for about a minute the damn thing booted up SORTED!!
Click to expand...
Click to collapse
Can you get into recovery mode?

Hi,
I have the exact same problem.
I cannot get into recovery. I tried Power + Vol. Up but that did not work (yet).
Did you leave it plugged into the wall charger while doing this, Braddison?
Also it does not show up on PC.

milchmaennchen said:
Hi,
I have the exact same problem.
I cannot get into recovery. I tried Power + Vol. Up but that did not work (yet).
Did you leave it plugged into the wall charger while doing this, Braddison?
Also it does not show up on PC.
Click to expand...
Click to collapse
If I remember correctly I had it on charge and held down power and vol up. It did take a couple of minutes continuously holding down the buttons. Been fine ever since
If that fails try power and volume down for about 30seconds, I'm sure that's meant to hard reset phone

Thanks for your quick answer. I will try once more.

Same dead HTC One Mini here...two days ago the phone suddenly turned off (with somewhat of 80%-90% battery) and since then its dead. No LED, no charging, it even doesnt get warm when its being plugged into the charger. Pressed Power+Volume down (plugged or non-plugged) more than 2 minutes, and also Power+Volume Up more than two minutes.
adb shows no device. If i plug the phone into an USB-slot in a linux-machine dmesg doesnt says anything. So its dead or not? Since its not more than a half year old it should have warranty, but i think i wont get my photos and stuff. So this is an advioce to myself: never ever buy a phone without micro-sd-slot again!!!
cheers, jennix

jennix said:
Same dead HTC One Mini here...two days ago the phone suddenly turned off (with somewhat of 80%-90% battery) and since then its dead. No LED, no charging, it even doesnt get warm when its being plugged into the charger. Pressed Power+Volume down (plugged or non-plugged) more than 2 minutes, and also Power+Volume Up more than two minutes.
adb shows no device. If i plug the phone into an USB-slot in a linux-machine dmesg doesnt says anything. So its dead or not? Since its not more than a half year old it should have warranty, but i think i wont get my photos and stuff. So this is an advioce to myself: never ever buy a phone without micro-sd-slot again!!!
cheers, jennix
Click to expand...
Click to collapse
I would try again after putting on charge for a few hours, ensuring that power and volume down are pressed simultaneously. i have read that its best to do this while in a bright room or shining a torch on the sensor, seems strange i know but its worth a try
good luck

Braddison said:
I would try again after putting on charge for a few hours, ensuring that power and volume down are pressed simultaneously. i have read that its best to do this while in a bright room or shining a torch on the sensor, seems strange i know but its worth a try
good luck
Click to expand...
Click to collapse
Its a bit esoteric, isnt it? But nevertheless i tried it (at least the bright room) but it doesnt work. I will send it to T-Mobile and then i will hope that they didnt find that it has a CM11 on it...
thx, jennix

hi all,
while hanging on the phone for a few minutes, it switched off.!
now:
Braddison said:
the screen is totally black,no charging/notification lights and touch buttons are not illuminated and wont power on or take a charge. tried to connect to pc but adb keeps saying "waiting on device" and thats it.
the phone is unlocked,rooted, jmz TWRP recovery and cm11.....has been running fine for the past week.
it appears to have died a sudden death....any ideas guys ???
cheers
Click to expand...
Click to collapse
abzboi said:
Can you get into recovery mode?
Click to expand...
Click to collapse
NO, unfortunately, i cant...
i see a few of you have the same problem - have you found any help yet?
Braddison said:
EDIT: dunno what the hell happened as nothing was turning it back on BUT after after holding down power button and volume down for about a minute the damn thing booted up SORTED!!
Click to expand...
Click to collapse
really? how nice of it!
did you cheer your mini up while switching on.?

I have the exact same issue right now, just 1 day after ive installes the latest cm11 nightly. gonna charge it for a few hour and hope it helps. Do you guys have any advice?

LQi said:
I have the exact same issue right now, just 1 day after ive installes the latest cm11 nightly. gonna charge it for a few hour and hope it helps. Do you guys have any advice?
Click to expand...
Click to collapse
No, dont have an advice. My Mini One is dead and it seems to stay so But can it be that all dead Minis in this thread are flashed with CM11?
cheers, jennix

jennix said:
No, dont have an advice. My Mini One is dead and it seems to stay so But can it be that all dead Minis in this thread are flashed with CM11?
cheers, jennix
Click to expand...
Click to collapse
Could be. But did even leaving the phone of the charger for a few days so the battery totally dies, and then recharging not work?
thanks anyways:cyclops:

hi all,
i got rid of the problem by going to my carrier. (a1 - vodafone, austria)
htc fixed it on guarantee (although i flashed a cm11-nightly)
the problem was: a damaged mainboard, which got replaced - took about two weeks..
cheers, and good luck..

schischeux said:
hi all,
i got rid of the problem by going to my carrier. (a1 - vodafone, austria)
htc fixed it on guarantee (although i flashed a cm11-nightly)
the problem was: a damaged mainboard, which got replaced - took about two weeks..
cheers, and good luck..
Click to expand...
Click to collapse
thanks! Just sent mine to HTC, hope they fix it within warranty. Can I ask if ur data on the internal SD is stil intact or did you lose it all? And again someone with cm11 installed. Anyone with Sense had the same problem?

I have the exactly same problem, my phone was rooted with CM11 nightly when it died. I sent it to my carrier, but now they want me to pay 200$ for a new motherboard, because they found it was rooted and the warranty is voided. Even when I pay 200$, i still will have no warranty. And I had more than 1 year left. Is there a problem with CM11? How comes that they replace it for some people for free, and for some not? Please, give me a tip how to proceed and do I really have any options from this point?

These horror stories make me wanna stick to stock based roms. I'm a big fan of CM, but not if there's a chance it could fudge my mainboard.. real shame
or is this another example of another design fault with this phone?....
Sent from my GT-I9000 using Xparent Green Tapatalk 2

As they have to replace the motherboard it is an hardware issue, where I live rooting doesnt void warranty if there is an hardware issue. They have to give you warranty. Could you ask your carrier what exactly caused it and why the motherboard had to be replaced?

LQi said:
Can I ask if ur data on the internal SD is stil intact or did you lose it all?
Click to expand...
Click to collapse
all data gone!
i got it back with latest firmware installed (4.4. ) and sense of course.
and all that bloatware you dont need but cant delete,.

J0ro said:
I have the exactly same problem, my phone was rooted with CM11 nightly when it died. I sent it to my carrier, but now they want me to pay 200$ for a new motherboard, because they found it was rooted and the warranty is voided. Even when I pay 200$, i still will have no warranty. And I had more than 1 year left. Is there a problem with CM11? How comes that they replace it for some people for free, and for some not? Please, give me a tip how to proceed and do I really have any options from this point?
Click to expand...
Click to collapse
Hey. I sent it directly to AVARTO (service center here in Germany) they too wanted to charge me (around $ 240). Then I asked what exactly the problem was and they revised their statement. Sent it back for free within warranty. On the repair sheet it than said "not turning on. constantly".

Hi.
Another dead mini. S-OFF, TWRP, CM11.