Related
he guys!
i need a little help and i can't seem to find a thread that might help me.
i have an htc desire (root+s-off) and two days ago tried to flash a new rom. and as i was already at it flashed the newest radio version and an sd-alignment, because i had just before had had to flash the original shipped rom because my phone didn't react anymore. so i did the root and s-off again, flashed all three zips and rebooted. after that my display went black and nothing happened for a while so i removed the battery and tried to restart the phone but it didn't. i tried to connect it to my computer and it doesn't recognize the device anymore.
either i removed the battery too early and bricked it or it was a bad idea to flash 3zips at the same time.
has anybody encountered this before and is there sth i can do?
any help will be greatly appreciated.
Can you boot into the bootloader through Vol - and Power button?
unfortunately no.
device does not react at all. i can push any button but the phone stays dead. screen stays black, no LED flashing, doesn't vibrate, nothing!
Maby its time to part as equals and donate it to the dev team?
Do you want to help out developers? Got a broken device?
the desire won't help them because it has a snapdragon cpu.
is there really no possibility to fix this?
maybe a too simple solution, but could the battery be dead or empty?
since you get absolutely no reponse...
I considered that too but the battery was NOT empty when the phone died.
I thought it might still be that the battery is just broken but I read that when you take out the battery and connect the phone to your computer or plug in the charger the LED still flashes. And with my phone it doesn't.
Your led won't flash if your phone is off. Try taking out the battery and plugging the phone in to the charger and see if it turns on.
Sent from my Desire running Ice Cream Sandwich using the xda premium app
Did that already and unfortunately phone stayed dead.
ElZeck said:
Did that already and unfortunately phone stayed dead.
Click to expand...
Click to collapse
How long do you let it charge before trying to turn on? If its right dead, then you should probably leave it plugged in for ten minutes or so before trying to turn it on.
Sent from my Desire running Ice Cream Sandwich using the xda premium app
But if I take out the battery how can it charge?
I thought if I take out the battery and plug it in, it should come back to life immediately?
But if you think that could help, I'll be happy to try.
So let me sum this up to be sure I got it right:
I take out the battery, plug it in, wait for a couple minutes and then try turning it on, right?
YOu should take the battery by pluging it at least 5 - 10 minute for sure it is already charging then try to turn on your phone again, this might work
im not sure the phone will work at all without the battery in place (haven't tested)
But i think that Kenny means, putting the battery in and letting it charge for a little while before trying.
bl0m5t3r said:
im not sure the phone will work at all without the battery in place (haven't tested)
But i think that Kenny means, putting the battery in and letting it charge for a little while before trying.
Click to expand...
Click to collapse
The phone will work while plugged in without the battery. But try what Kenny suggested.
Sent from my Desire running Ice Cream Sandwich using the xda premium app
tried everything, nothing worked...
Sorry to hear. I have no other ideas.
Sent from my HTC Desire using Tapatalk
I bricked my HTC desire S. When i open it will stuck to bootloop, drained the battery, i cannot charge the phone. it always turn off.
Can someone help me fix this?
Just wondering how often are people experiencing this problem when the phone become completely unresponsive (unable to turn on, unable to detect, no light when charged).
I had this problem and never had it resolved and just sent the phone back for repair. It seems more and more people are posting they have this problem. Is this a ROM problem or does the HTC phone just get fried? Mine happened after I installed Revolution 6.6.2..it rebooted fine...and reinstalled apps with titanium..then all of a sudden a long tone while I was on phone and the phone unresponsive, turned off...and never turned on again.
Anyone with same problem...would appreciate your experience..and maybe we can figure out why it's happening. And I mean...the phone is just dead...no bootloop, no adb...nothing.
I ''had'' rooted Sensation Juopunutbear S-OFF,I filled the battery full...and install AOKP ROM Everything is working fine....After resetting the phone,
He did not respond...do not want to boot,does not want to even turn on,I tried everything from taking the battery to charge...no signs.....
when connecting phone to computer,sound is heard...and requires some drivers QHSUSB_DLOAD
removing battery sim sdcard and connect to power outlet and tried to switch it on-nothing...not react
is still under warranty....9 months old
I asked no one knows why it happened
I sent it to the service and I hope will not notice that he S-OFF and ROOTED :\
there are still a lot of people this problem here http://forum.xda-developers.com/showthread.php?t=1618683
Hmmm..at least yours is detected on computer. Mine was completely unresponsive...nothing worked. Some had similar problem as mine when not even the computer detects it.
IT seems to be happening quite often..and I am not sure if it's a ROM problem....but it seems it's not only from a specifice ROM.
I had one just like the op except it was stock with s-off, no custom rom yet. I turned it off and it never came back, so got a new one!
From another similar thread:
Charge your phone for 20 minutes. If you're using a Sense ROM, disable fast boot in Settings>Power. Fastboot doesn't actually power off your device, just puts it into sleep, like in Windows. This means the battery drains, even while it's "off".
On this forum, we see it atleast once a week. Something was going totally fine, no biggy, then suddenly it won't turn on, seemingly won't charge, no LEDs, not recognized by PC, etc etc.
The odds are low that it'll happen to you, but more so than other phones.
sshede said:
On this forum, we see it atleast once a week. Something was going totally fine, no biggy, then suddenly it won't turn on, seemingly won't charge, no LEDs, not recognized by PC, etc etc.
The odds are low that it'll happen to you, but more so than other phones.
Click to expand...
Click to collapse
But is this related to hardware issue or a custom ROM / firmware problem? My question is....should I try to root and do the same thing again if my phone get replaced?
If it's related to custom ROM/firmware pb...maybe it needs to be looked at? Especially when everything is running fine like many people report...
Well it would be nice if ALL of these occurrences were logged into a single thread and each user listed their firmware, rom, and kernel (which I'm most interested in)...
well i got the same problem . while playing a game phone got stuck and automatically turned off with some sound . now its desnt turning on and cant charge it coz led doesnt working ( what should i do?? going to use a another battery . if not :s idk (
Experience Senseless
HTC sensation XE with beats audio
Unlocked -Revolutionary
Pyramid Pvt S-off
Hboot 1.27.0000
Radio 11.22.3504.07_m
CID 11111111
Hi to all,
I'm in a similar situation, yesterday I updated the 4ext recovery the beta (sorry dont know what version it is) and it worked fine on the phone.
Until I thought hmm, I try [ROM][04/26/12] Virtuous Inquisition v4.0.2 :: AOSP-Experience Senseless ICS (4.0.3). I was going through the software and I've done a format on the microSD card though virtuous, and done a REBOOT on the phone, no Reboot at all. By the way while running the OS lights for the Home, Menu, Back and Search weren't truned on.
Now my phone wont turn on (although I can hear the USB being connected to my windows7 X32 bit PC). When connected to Pc or power outlet there is no indication of my phone is charged or being recharged, no light indicator.
Ok, so what if I tried using ADB commands to see if my phone still beeing detected.
I used ADB under Administrator
adb devices
*daemon not running. starting it now on port 5037 *
*daemon started successfully*
List of devices attached ( although i dont get the model number of the phone)
fastboot reboot
waiting for device
fastboot reboot-bootloader
waiting for device
fastboot flash recovery recovery.img
waiting for device
Ok no luck. Now tried to do install with the RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R_Radio_11.69.3504.00U_11.22.3504.07_M_release_251961_signed.exe
Runed under Admin again, so still no luck, all I get was an Error[170] usb connection Error. So the utility rom still could not detect the phone.
By the way when the phone is off, then I press volume down and power button, my phone is AOSP-Experience Senseless indeed, can't switch nothing on.
All well see what happens.
Yes..I think it's good to have a thread about this problem...maybe some more experienced DEVs can see why this is happening especially if this is occuring because of ROM/firmware or more hardware problems.
I am waiting for my phone to be sent to HTC and see what they say..hope they'll fix/replace one!
Battery, Brick or Senseless
By any chance, did anyone tried to use some friends or family they have the same phone, and use their battery. Maybe battery needs replacing?
Hopefully I can here someone says that I'm right, battery problem.
Also I'm looking at other websites to see whats the alternative to our situation.
Or maybe its just a brick, I will wait and see the Developers of this thread
http://forum.xda-developers.com/showthread.php?t=1522351
[Release coming next week. With a surprise!] Sensation Unbricking Project
hopefully will have a solution I feel lost without my phone, AOSP-Experience Senseless these two days.
God bless them hope they can do it.
barascus said:
By any chance, did anyone tried to use some friends or family they have the same phone, and use their battery. Maybe battery needs replacing?
Hopefully I can here someone says that I'm right, battery problem.
Also I'm looking at other websites to see whats the alternative to our situation.
Or maybe its just a brick, I will wait and see the Developers of this thread
http://forum.xda-developers.com/showthread.php?t=1522351
[Release coming next week. With a surprise!] Sensation Unbricking Project
hopefully will have a solution I feel lost without my phone, AOSP-Experience Senseless these two days.
God bless them hope they can do it.
Click to expand...
Click to collapse
For some it could be battery problems....but I think most of the ones reported it's not. As with mine..the battery was fully charged 100% when it happened...I think it was actually plugged in even.
The thread is for bricked phone that had this driver thing when it plugs into the computer...but if the phone is completely unresponsive...it's not goign to work!
I kept my phone charged for few hours, although my battery was full as well, the phone remained cold.
i had a similar problem last week on 04/19... battery was charging over night... at morning i turned the alarm off and after that the phone was dead... i sented it to support and now i have a new board inside and totaly new problems...locked bootloader and an unkown H-BOOT version (1.29.0000)
i also tried my battery in a other phone with no problems.
i had revolutionary 6.3. on it
:crying: any ideas ?
everything was working perfectly and i didn't do anything , just when my first battery ran out , i shut it down and switch second battery then it just doesn't boot up anymore ... even with data cable connect with charger or PC, because usually it will show a charging animation when system isn't booted up ...
and one thing strange is that when i plug in my battery , phone doesn't boot up but it still heat up like i am using it ...
a little help please ...
qtwrk said:
:crying: any ideas ?
everything was working perfectly and i didn't do anything , just when my first battery ran out , i shut it down and switch second battery then it just doesn't boot up anymore ... even with data cable connect with charger or PC, because usually it will show a charging animation when system isn't booted up ...
and one thing strange is that when i plug in my battery , phone doesn't boot up but it still heat up like i am using it ...
a little help please ...
Click to expand...
Click to collapse
the same happen to me week ago! i think its jellybean...
Cascabreu said:
the same happen to me week ago! i think its jellybean...
Click to expand...
Click to collapse
how did you fix it?
i am using the unbrickable resurrector , but it keep shows device not found, no device detected
qtwrk said:
i am using the unbrickable resurrector , but it keep shows device not found, no device detected
Click to expand...
Click to collapse
Same issue with mine. Yesterday, 8/20/12, I broke a sim card connector pin and Nexus S wouldn't recognize sim card after a reboot. Rebooted the device again after the warning message: Sim card not detected/found.
Now Nexus S won't boot. Computers (Windows & OSX) can't recognize it's connected and 5 different charges won't show that the battery is charging. Battery still has a charge as I tested it in another Nexus S. When the battery is in, the device heats up. When connected to a power source, the device heats up.
Used Unbrickable resurrector with no success. UR shows: Device not found, No device detected.
Finally, I was running Jelly Bean from OTA update and not rooted. I noticed that in the past week or two the stock Andoird keyboard would cause force closing of apps or exceed processor threshold of 35% even if there was no program running. Google Now was also sucking the battery after the JB update. Turned that battery drain off on the other Nexus. Also, the Android Media process was taking a drain on the processor. Usually running at 40-50%.
Bought this used from CowBoom and hoping the extended warranty will replace or fix the broken sim card connector and unbrick the phone.
Luckily I have an iPhone 4S and a 2 yr old HTC Desire to turn to.
I've read on another thread, perhaps?, that two other users in the past week or so have had this same problem.
nexus s GT-I9020T Bricked after JellyBean
qtwrk said:
i am using the unbrickable resurrector , but it keep shows device not found, no device detected
Click to expand...
Click to collapse
Same happened to me. The Unbrickable resurrector also didnt detect the phone. so i made the Unbrickable Hardware Mod (httpxx://forum.xda-developers.com/showthread.php?t=1566475) remove the xx from httpxx. now my phone is being detected and the tool is able to load its files. but still the phone is dead, no thing happens and the tool shows no device found after it loads the files. but when i picked GALAXY S from the drop down menu. the tool loads the files and now both the tool and the phone shows download mode with an android shoveling dirt. heimdall now detects the phone but it doesnt work caz its not a GALAXY S. So let us know what happens if u try this mod. cheers
The exact same thing happened to me. Strangely, it's happening with JB roms. And yeah, i told my problem in a very educated way on the ROM topic and they simply deleted the post, how nice.
Anyway, i just sent the phone to the warranty almost three weeks ago, i'm waiting for them to fix it or give me a new one.
djdeepblue said:
The exact same thing happened to me. Strangely, it's happening with JB roms. And yeah, i told my problem in a very educated way on the ROM topic and they simply deleted the post, how nice.
Anyway, i just sent the phone to the warranty almost three weeks ago, i'm waiting for them to fix it or give me a new one.
Click to expand...
Click to collapse
no , i was running 4.0.4 , AOKP M6 , as matter fact , it seems to be a problem of latest BOOTLOADER
dokugan ryu said:
Same happened to me. The Unbrickable resurrector also didnt detect the phone. so i made the Unbrickable Hardware Mod (httpxx://forum.xda-developers.com/showthread.php?t=1566475) remove the xx from httpxx. now my phone is being detected and the tool is able to load its files. but still the phone is dead, no thing happens and the tool shows no device found after it loads the files. but when i picked GALAXY S from the drop down menu. the tool loads the files and now both the tool and the phone shows download mode with an android shoveling dirt. heimdall now detects the phone but it doesnt work caz its not a GALAXY S. So let us know what happens if u try this mod. cheers
Click to expand...
Click to collapse
well ... i don't have these tools to do hardware level of modifications ...
anyway , i just send to repair , i think , the motherborad or something should be replaced ...
i was thinking about buying a new phone such as Galaxy Nexus if my Nexus S can not be repaired or way too expensive to repair...
i had same issue a few days after upgrading to JB JRO03E. i got the main board replaced under warranty. took about 2 and half weeks.
the phone came back with GB installed but OTA'd to ICS then JB JRO03L.
I had the same issue running cm10-0823. Screen froze while sitting idle. Pulled and replaced battery, and phone won't come back.
Looks like cm10/jb is causing some burn-out in circuit board; cpu, memory...?
_android_ said:
I had the same issue running cm10-0823. Screen froze while sitting idle. Pulled and replaced battery, and phone won't come back.
Looks like cm10/jb is causing some burn-out in circuit board; cpu, memory...?
Click to expand...
Click to collapse
as i have heard is that new bootloader messes with hummingbird CPU ...
I have exactly the same problem I flashed Codename Android ROM 3.4.1, done some overclocking (only 1200 MHz) and the device crashed. Well, nothing unusual. But I removed the battery, I think it was just when the device was rebooting - I think display turned on, I noticed some flash when the battery was already removed.
I tried to turn on the device, but it's dead. Display doesn't turn on, UnBrickable Resurrector says device not found.
I can send the phone to the warranty, but it's unlocked. Do you think they will find out it's unlocked? Even if the download mod doesn't work etc?
What should I do?
Well, I happened to end up with the same problem. Installed latest cm 10 nightly, started rebooting my phone. The moment I restarted it from CWM I realised that I forgot to flash some mod in CWM so I pulled the battery to go into recovery. Phone bricked, no input at all. Sent my phone on warranty, I hope they won't mind it had unlocked bootloader and cm10 on it ;P
That's just a bit stupid to be honest, pulling the battery while booting why not just wait?
Sent from my Nexus S
Now I know it's stupid. Do you think they will repair it even though it's cm flashed and unlocked?
i sent mine to repair and they fixed without paying a dime!
Cascabreu, you just made my day Well, I just have to wait now
nexususer1 said:
Now I know it's stupid. Do you think they will repair it even though it's cm flashed and unlocked?
Click to expand...
Click to collapse
The mainboard is fried. No way of knowing previous state of your phone. They will just replace the board.
Sent from my Nexus S using XDA Premium HD app
_android_ said:
The mainboard is fried. No way of knowing previous state of your phone. They will just replace the board.
Click to expand...
Click to collapse
I had the same issue back in August just after I flashed 4.1.1/JRO03E. It just died one day while listening to music. Took about 3 weeks to get the mainboard replaced under warranty. It came back bootloader unlocked and with Gingerbread 2.3.3 installed.
I am using vanilla rootbox 4.2.2 yesterday i flashed the kernel 3.0.80 from cm10.1 threat and today i had only 30% of battery and my phone had a little lag so i turned off the phone and removed the battery again i tried to turn on the phone and it never turned on, I had a doubt on battery so i checked the voltage and it showed 2volt i tried charging the phone for more than 5 hrs but nothing happened
so wat is the problem? ??? i cant access my recovery, hboot or anything have i bricked my phone???????
balajithegreat said:
I am using vanilla rootbox 4.2.2 yesterday i flashed the kernel 3.0.80 from cm10.1 threat and today i had only 30% of battery and my phone had a little lag so i turned off the phone and removed the battery again i tried to turn on the phone and it never turned on, I had a doubt on battery so i checked the voltage and it showed 2volt i tried charging the phone for more than 5 hrs but nothing happened
so wat is the problem? ??? i cant access my recovery, hboot or anything have i bricked my phone???????
Click to expand...
Click to collapse
Bricking HTC phones got very less chances .....like out of 100% HTC phones won't brick for 99.99% .
So try changing your battery...might help
Sent from my HTC Explorer using xda premium
It's definitly no a brick 'cause you did flashed your kernel and ROM successfully after rooting it. I've never heard of anyone who bricked his phone while he rooted it succesfully and had a working custom ROM on it.
Have you overclocked it, may the battery/chipsets died this way? Any scripts or tweaks on it?
Mhmmm...found this:
http://lifehacker.com/5853519/how-do-i-fix-my-bricked-android-phone
It says sth. about phones that won't turn on anymore
Dude ... Yeah Firstly .. trying changing The Batt. cause .. i have a feeling ur Battery has gone Bad ... :/ n try to clean ur like golden slots in battery .. Check if there is Carbon type thing in those ..
This may be the first case of bricking i've seen for Pico. Have a look at your battery, or the port in which your charger plugs in.
Do you charge with USB? I had a problem with my USB wire, it did not charge when connected to adapter, so i used my Samsung charger and charged the phone. So check your charging apparatus.
If everything is in vain, go to HTC Store and play dumb (i.e. "Sir i was using it and suddenly it did not start")
and Rule 1 in playing dumb: Never utter the "root" word, nor bootloader, its best if the store guy thinks you're a noob
Trust me, most of the time if you are within the warranty time they wont bother and give you a new phone, my friend once did with Micromax, and got it repaired free of cost.
Hi, I let my friend use my HTC Sensation around a week ago and he was playing a game when suddenly it turned off and did not turn on again.
I suspected it was the battery being drained to 0% as the battery was quite hot.
After getting home I plugged it into the charger with no LED showing or the phone turning on so I reseated the battery, tried charging the phone for 6 hours, tried taking out the battery for two days and leaving it and I also tried plugging it into my laptop with HTC Sync Manager only to find the QHUSB (Or something like that) issue. I am really worried and the only other things I could possibly think of doing is sending my phone to HTC (although warranty expired) or trying a new battery.
Please help
P.S
My HTC is rooted S-OFF (By factory)
and running ViperS 5.1
Thanks in advance
owner eod said:
Hi, I let my friend use my HTC Sensation around a week ago and he was playing a game when suddenly it turned off and did not turn on again.
I suspected it was the battery being drained to 0% as the battery was quite hot.
After getting home I plugged it into the charger with no LED showing or the phone turning on so I reseated the battery, tried charging the phone for 6 hours, tried taking out the battery for two days and leaving it and I also tried plugging it into my laptop with HTC Sync Manager only to find the QHUSB (Or something like that) issue. I am really worried and the only other things I could possibly think of doing is sending my phone to HTC (although warranty expired) or trying a new battery.
Please help
P.S
My HTC is rooted S-OFF (By factory)
and running ViperS 5.1
Thanks in advance
Click to expand...
Click to collapse
remove battery,simcard and sdcard and charge the device as it is for 4-5 hours
put them back and switch on the device
if it fails then see here
http://forum.xda-developers.com/showthread.php?t=1522351