My HTC U ultra fell down and started boot looping until the power got depleted. I've tried booting it up but it has refused, I've tried everything on the internet and nothing has worked. ( Was using lineage os android 12l)
You may have damaged the mobo... if you're lucky it's a dislodged connector. Always use a case to protect the phone from flexing and high G loading impacts.
blackhawk said:
You may have damaged the mobo... if you're lucky it's a dislodged connector. Always use a case to protect the phone from flexing and high G loading impacts.
Click to expand...
Click to collapse
Sorry for the late reply, so the phone booted up, charged and went to the recovery without any issues but upon flashing a rom it still boot looped.
w4lk3r: 0254 said:
Sorry for the late reply, so the phone booted up, charged and went to the recovery without any issues but upon flashing a rom it still boot looped.
Click to expand...
Click to collapse
You flash a known good stock rom?
If so it sounds like a hardware issue.
Remove SD and sim cards, try again.
Is the battery known to be good and fully charged?
blackhawk said:
You flash a known good stock rom?
If so it sounds like a hardware issue.
Remove SD and sim cards, try again.
Is the battery known to be good and fully charged?
Click to expand...
Click to collapse
The rom that I flashed was a custom rom (lineage os 19).
Yeah the battery is good though when I was flashing the rom it wasn't fully charged.
w4lk3r: 0254 said:
The rom that I flashed was a custom rom (lineage os 19).
Yeah the battery is good though when I was flashing the rom it wasn't fully charged.
Click to expand...
Click to collapse
Flash a known good stock rom.
If that fails you likely have a hardware fault.
Generally Android firmware doesn't go corrupt without a reason. In 12 years I never had to force flash any of my Androids due to corruption.
A single event upset could do it but they are rare and don't damage the hardware.
blackhawk said:
Flash a known good stock rom.
If that fails you likely have a hardware fault.
Generally Android firmware doesn't go corrupt without a reason. In 12 years I never had to force flash any of my Androids due to corruption.
A single event upset could do it but they are rare and don't damage the hardware.
Click to expand...
Click to collapse
Ok I'll do so, thanks so much.
Related
the phone is freezing often
slow touch responce
programs force closing
yahoo mail doesnt work anymore
its shutting down on its own randomly
and some other problems i cant remember.
its a nand CMYLXGO stock desire HD v1.1.3
is this a common problem, if so where can i find info aout it i searched for dead battery and didnt show much.
Maybe some data got corrupted. So you should reflash or flash another build. Maybe even your radio to be sure.
why does it happen? i thought we wouldnt have this problem with nand builds.
fuzzysig said:
why does it happen? i thought we wouldnt have this problem with nand builds.
Click to expand...
Click to collapse
well, lot of roms use the data2sd method for storing data on SD, for me its pure nonsense (app2sd is fine). With data2sd the risk is very high that you get data corruption and then all the weird force close madness begins. Now if you run out of battery your device doesnt shut down properly/cleanly, its the same as you would just pull a cable to shut down a pc. So running out of battery is the same as pulling the battery.
wow
I'm using CMYLXGO's BlueTopia (NAND) and the battery widget got to 0% i think... i was worried since charging MADGLR 1.3 requires me to activate the screen / turn on the phone....luckily it did the GO GO GO thing and started to boot .... i plugged in the charger and now all is well.... lucky me I guess...
PS .. I guess the battery widget is a showing a percentage or two off
kiki_tt said:
I'm using CMYLXGO's BlueTopia (NAND) and the battery widget got to 0% i think... i was worried since charging MADGLR 1.3 requires me to activate the screen / turn on the phone....luckily it did the GO GO GO thing and started to boot .... i plugged in the charger and now all is well.... lucky me I guess...
PS .. I guess the battery widget is a showing a percentage or two off
Click to expand...
Click to collapse
That's what it does for everybody.
the phone also started to have SOD.
i plug it in at night to charge, in the morning it would not wake up.
the alarm would go off but the screen is blank.
now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?
fuzzysig said:
now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?
Click to expand...
Click to collapse
Been there. The only solution that worked for was to flash it from scratch once again.
Dunno why the phone is acting this way but now I always charge or turn off my phone when my battery is down on 10 %. Better to be safe than sorry.
I'm using MDJ's CM7 v. 2.6 so I think this is an issue on many builds if not on everyone.
fuzzysig said:
now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?
Click to expand...
Click to collapse
Since u are aware u can reinstall it again then simply do so...Yeah its a real pain but just tk time out n do it...I've been using CMY's builds for so long and have never encountered such an issue..but dats just me...
i see u r still using V 1.1.3, CMY has released a much more better build (but then u already know that), so go download dat...perform a Task 29 ,install MAGLDR ( u know d works) etc...
As 4 y a dead battery will cause this on a custom build and not on a factory installed ROM? ...Me thinks u already know d answer (stick 2 stock WinMo if u think its better)..
P.S. Remember charging ur battery to 100% b4 starting..gives u a fairly calibrated battery.
you could also try to wipe the battery information via magldr?
you choose recovery in magldr > clockworkmod recovery > advanced > wipe battery stats.
tried that didnt work
isnt there another way besides reinstalling everything over and over?
wow i mean we went so far as to have it working on the phone but nobody knows why a dead battery causes corrupted system on a custom rom but not on the original?
fuzzysig said:
wow i mean we went so far as to have it working on the phone but nobody knows why a dead battery causes corrupted system on a custom rom but not on the original?
Click to expand...
Click to collapse
?! it has been answered in this thread...
There is no way to rule out GB as the cause of this failure right now. All we have is theories and the best fitting one is an emmc chip failure. Until we can find a user with a brick, who is still s-off, we can not learn more.
DO NOT FLASH OVER BRICKS, We need you to have s-off for trouble shooting.
UPDATE
We need info from brickers and non brickers please see
Please see here http://forum.xda-developers.com/showthread.php?t=1098363
--old post--
It has came to our attention, over the last few days that the recently leaked Gingerbread radios maybe causing a oddly large number of bricked phones.
This can affect any Thunderbolts running Gingerbread (except CM7 users), even after running fine for several days.
The cause at this point is not completely understood, and AndIRC as a whole recommends you revert back to Froyo until we understand it, or have a new leak.
When bricked, the phone is sent into an endless bootloop, no matter if you are booting into Android itself, or into the recovery. Trying to revert after the bootloop does not fix this issue.
Theories:
GB Radio causing corruption on the emmc:
Undisclosed chipset issue (Sorry no details will be coming unless verified)
GB miss reporting battery stats, aka just dead battery (Debunked by ryan2600 and I)
"Not sure if its the radio, i got a bootloop experience this morning after tethering my tablet on a freshly charged tbolt, few minutes later the phone died and stuck in a bootloop, there are times i can go to bootanimation sometimes it goes up to HTC screen and dies, I can go to HBOOT but before i can do anything the phone dies.
Good thing i have a 2 extra battery and an external charger from ebay, I swapped the battery and my phone is back to life, it seems like the GB roms are not charging the battery properly and reporting that the battery is around 80-90%" http://www.reddit.com/r/Android/comments/hk54l/if_youre_using_the_leaked_gingerbread_build_or/
Does this affect current users or just new flashers of the gb stuff?
Sent from my ADR6400L using XDA App
I was under the impression that a bricked phone was a phone that doesn't turn on at all... Wouldn't you be able to put the PG05IMG file on your SD card through your computer if this ever happens and then do a battery pull and boot into bootloader and revert then?
*edit* I've also had an endless bootloop on GB and flashing a new ROM after wiping data/cache/dalvik fixed it... No more reboots yet at least.. maybe it wasn't the same thing that you're talking about!
Awww fiddlesticks! Well at least I get my baby back. Landscape Rosie is the girl for me.
swimminsurfer256 said:
I was under the impression that a bricked phone was a phone that doesn't turn on at all... Wouldn't you be able to put the PG05IMG file on your SD card through your computer if this ever happens and then do a battery pull and boot into bootloader and revert then?
*edit* I've also had an endless bootloop on GB and flashing a new ROM after wiping data/cache/dalvik fixed it... No more reboots yet at least.. maybe it wasn't the same thing that you're talking about!
Click to expand...
Click to collapse
The instructions are for reverting for those who are not bricked.
These bricked phones will turn on, but we can not find a way to prevent them from bootlooping nor repair them.
You cant wipe data/cache/dalvik when you are in this type of reboot loop, as recovery reboots as well.
Wow this sucks, I don't really wanna go back to froyo
Thanks jcase and Team AndIRC! I nearly flashed the latest BAMF GB update. I'm glad that I stuck with 1.6.3
Wow, mine just started 2 mins before this thread went up. I was sitting at my desk and saw it reboot and now it won't stop. It actually loads up Android entirely, gets to Lockscreen and then restarts.
zskate311 said:
Does this affect current users or just new flashers of the gb stuff?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Anyone using the GB Radios (ie everyone on GB but CM7 users)
jcase said:
The instructions are for reverting for those who are not bricked.
These bricked phones will turn on, but we can not find a way to prevent them from bootlooping nor repair them.
You cant wipe data/cache/dalvik when you are in this type of reboot loop, as recovery reboots as well.
Click to expand...
Click to collapse
Ah didn't see that. Does bootloader not work?
Well crap, back to froyo I go then, just to be safe.
*sighs at jcase*
What happened to, "They will blame you and I" conversation?
/me goes off to cry in a corner.
I actually think I read about this somewhere else in the forums. I don't know if he was running gb but I'm guessing so. Thanks for this, I'll be reverting back later.
Sent from my ADR6400L using XDA Premium App
adrynalyne said:
*sighs at jcase*
What happened to, "They will blame you and I" conversation?
/me goes off to cry in a corner.
Click to expand...
Click to collapse
It's all your fault.
Sent from my ADR6400L using XDA Premium App
reverting now... can I just flash a froyo radio and rom or do I have do the whole process in OP?
Thanks for looking out for us
Sent from my ADR6400L using XDA App
Thanks for the heads-up!
Might as well Nandroid my Ginger builds so I have them for when we get a more stable radio release. Curses Verizon! I will miss my Sense 3 elements!
This sucks! Thanks for the heads up, though, Justin!
Bootloader works. I ran into this problem once. Have a backup of the ruu handy. It will get you back to a stock rooted froyo state
Btw...I'm staying on gb. Ill take a risk.
Hi
So I've tried several things the past days and nothing seem to work properly.
I found several threads with same topic, however this is really random crashing.
My EU HD2 is pretty much unusable:
- Sometimes it won't boot, just vibrates constantly 5 times or so
- Loads into MAGLDR, but gets FATAL HIT when attempting to boot.
- Crashes randomly when used, either android or wp7.
I first experienced these issued with NAND android, using skinks clean desire v1.2
Then i reformatted, using task29, installed MAGLDR again, and then wp7 nodo (stable). But the issues kept on going, and now I'm not really sure if it boots. The battery pins look okay to me, and i have tried several different batteries.
Anyone experienced this before, is it gone or is it possible to fix?
all help greatly appreciated!!
rubikum said:
Hi
So I've tried several things the past days and nothing seem to work properly.
I found several threads with same topic, however this is really random crashing.
My EU HD2 is pretty much unusable:
- Sometimes it won't boot, just vibrates constantly 5 times or so
- Loads into MAGLDR, but gets FATAL HIT when attempting to boot.
- Crashes randomly when used, either android or wp7.
I first experienced these issued with NAND android, using skinks clean desire v1.2
Then i reformatted, using task29, installed MAGLDR again, and then wp7 nodo (stable). But the issues kept on going, and now I'm not really sure if it boots. The battery pins look okay to me, and i have tried several different batteries.
Anyone experienced this before, is it gone or is it possible to fix?
all help greatly appreciated!!
Click to expand...
Click to collapse
main board is fubar. Warranty or sell for parts
Too bad, guess ill have it in on warranty then.
Thanks for quick answer!
rubikum said:
Too bad, guess ill have it in on warranty then.
Thanks for quick answer!
Click to expand...
Click to collapse
np, make sure you flash stock via SD card before you send in for warranty.
SD card flash didn't work for me so I flashed stock rom and then reset spl.
Phone won't boot now anyway so..
rubikum said:
SD card flash didn't work for me so I flashed stock rom and then reset spl.
Phone won't boot now anyway so..
Click to expand...
Click to collapse
I would try the fridge flash from SD just to be sure.
Guess ill try once more then
Does the card need to be formatted in order to do so?
When I tried last time i just put the leoimg.nbh onto are the card but nothing happened.
rubikum said:
Guess ill try once more then
Does the card need to be formatted in order to do so?
When I tried last time i just put the leoimg.nbh onto are the card but nothing happened.
Click to expand...
Click to collapse
Format fat32 and make sure the card.is 8gb or less. Also make sure the file is called leoimg.nbh
Sent from my HTC HD2 using XDA App
Maybe you have bad blocks
orangekid said:
main board is fubar. Warranty or sell for parts
Click to expand...
Click to collapse
what is fubar?
im sorry my english isn't good
khaled1994 said:
what is fubar?
im sorry my english isn't good
Click to expand...
Click to collapse
Fubar means F'ed Up
Serious_Beans said:
Maybe you have bad blocks
Click to expand...
Click to collapse
I think you should stop pointing random problems on bad blocks.
I understand that these are the symptoms observed by people with high number of bad blocks, but i'm running sense 3 roms with 8 bad blocks and no problem/random freeze/reboots till now.
Also, this guy is not running android/WP7 which are believed to be unable to manage bad blocks (assuming as he posts in HD2 General).
most probably hardware problem. i've had bad experience about this too. send it for warranty at the end
I dropped my Note2 today so the battery & backcase came out. When i started up the phone it wouldnt boot gave me kernel error. Tried sevral times, same thing.
So i went to cwm recovery and flashed the rom again.
How can a fall cause this? I mean either u get a hw damage or u dont!
it might have hit some kernel related component?
you didn't state what happened after the cwm flash?
anyway, your question implies that after the flash your phone was ok again
(as before the drop)!
what can cause this? when you dropped the phone the battery went out,
and this was no proper shutdown! some files may have been damaged,
and your re-flash wiped them, so you got back to normal.
that's the reason why not proper "shutdowns" should be avoided...
God did it.
TML1504 said:
you didn't state what happened after the cwm flash?
anyway, your question implies that after the flash your phone was ok again
(as before the drop)!
what can cause this? when you dropped the phone the battery went out,
and this was no proper shutdown! some files may have been damaged,
and your re-flash wiped them, so you got back to normal.
that's the reason why not proper "shutdowns" should be avoided...
Click to expand...
Click to collapse
This makes sense. Thanks.
Ps: yes .everything was fine again after a flash
Steve Jobs is haunting you and trying to make you by some ijunk.
Sent from my SPH-D710 using xda premium
Hey i recently flashed a faux kernal and everything was running fine then all of a sudden my phone turned off and i cant turn it back on if i try nothing happens and when i plug in the the usb a red light appears and keeps flashing then after a awhile a battery pops up as if its charging then just disappears. I am able to get into the boot loader but i cant get into recovery or do anything else can someone help me !
Also every now and then booting does work but it only goes to the Google screen then turns off again and goes back to the battery then just keeps restarting from there
Keep the phone plugged in and see if you can boot up. Sounds like your battery died.
Anyways, if you can get into bootloader, you should be able to use fastboot to flash a stock image or get to recovery to flash another ROM/kernel.
ZzzZ
Stryder5 said:
Keep the phone plugged in and see if you can boot up. Sounds like your battery died.
Anyways, if you can get into bootloader, you should be able to use fastboot to flash a stock image or get to recovery to flash another ROM/kernel.
Click to expand...
Click to collapse
How would i flash a stock rom using fastboot ?
Bosnianwog said:
How would i flash a stock rom using fastboot ?
Click to expand...
Click to collapse
Using the fastboot flash command. Google it
Sent from my Nexus 4 using Tapatalk 2
to be honest, RMA time!
ntt1409 said:
to be honest, RMA time!
Click to expand...
Click to collapse
Yep. I think this is the third post with the exact same issue. Be sure to try and re-lock your bootloader before sending it in for RMA or you'll probably be charged for another device.
Sent from my Nexus 4 using xda premium
Yeh i think i will just send the phone back to them hopefully they replace it for me :crying:
This is now at least the third post I've seen about people bricking their devices with the faux kernel.
I think everyone else should stay away from that kernel for a while.
Clarkster said:
This is now at least the third post I've seen about people bricking their devices with the faux kernel.
I think everyone else should stay away from that kernel for a while.
Click to expand...
Click to collapse
Agreed wait until a stable build comes out.
Bosnianwog said:
Hey i recently flashed a faux kernal and everything was running fine then all of a sudden my phone turned off and i cant turn it back on if i try nothing happens and when i plug in the the usb a red light appears and keeps flashing then after a awhile a battery pops up as if its charging then just disappears. I am able to get into the boot loader but i cant get into recovery or do anything else can someone help me !
Also every now and then booting does work but it only goes to the Google screen then turns off again and goes back to the battery then just keeps restarting from there
Click to expand...
Click to collapse
Happened to a few people already. Here's my thread on it.
Unlucky man i know how you feel and what are you going to do about it?
Bosnianwog said:
Unlucky man i know how you feel and what are you going to do about it?
Click to expand...
Click to collapse
Called Google and ordered a replacement yesterday. They said it should be here in a few days.
It's not bricked, do this hold down volume down and power till you see the bootloader then volume up till it says restart recovery, boot into recovery, wipe cache then dalvik cache, redownload faux kernel from his site, then reboot into bootloader, flash new kernel with fastboot, reboot and you should get into Android, I had the same issue with the red light after flashing his new kernel, this fixed it.
Clarkster said:
This is now at least the third post I've seen about people bricking their devices with the faux kernel.
I think everyone else should stay away from that kernel for a while.
Click to expand...
Click to collapse
Exactly, with all the respect to faux, whom is a well known developer and a very good one too...
Sent from my Nexus 4 using Tapatalk 2
djkinetic said:
It's not bricked, do this hold down volume down and power till you see the bootloader then volume up till it says restart recovery, boot into recovery, wipe cache then dalvik cache, redownload faux kernel from his site, then reboot into bootloader, flash new kernel with fastboot, reboot and you should get into Android, I had the same issue with the red light after flashing his new kernel, this fixed it.
Click to expand...
Click to collapse
Thank you for trying to help, but please stop suggesting things if you don't thoroughly understand the issue. I'd hate to waste your time and mine going over the things I have already with other people. Just read my op to learn why what you're saying will not work.
kaiowas82 said:
Exactly, with all the respect to faux, whom is a well known developer and a very good one too...
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I really dont think their devices are bricked, my heart stopped when I had the non-booting red led issue after installing his 005 kernel, but a wipe of cache and dalvik then reflash fixed the problem, of course im not using the OC kernel version, which might be causing all these issues.
djkinetic said:
I really dont think their devices are bricked, my heart stopped when I had the non-booting red led issue after installing his 005 kernel, but a wipe of cache and dalvik then reflash fixed the problem, of course im not using the OC kernel version, which might be causing all these issues.
Click to expand...
Click to collapse
You don't think it's bricked, because you don't understand the problem. My post in this very thread explains why this is a hardware issue of a defective battery, and not a software one.
@OP
Please use your head... this is alpha software, built blind... unless you know exactly what you're doing don't flash software that can/will brick your phone.
And don't send back phones on warranty when it's not a manufacturing defect. Overclocking exceedes the manufacturing specs and thus you voided your warranty, don't steal from google.
abnormalreply said:
You don't think it's bricked, because you don't understand the problem. My post in this very thread explains why this is a hardware issue of a defective battery, and not a software one.
Click to expand...
Click to collapse
I understand the issue, and your line Doing "fastboot getvar battery-voltage" does not give an output, meaning my overclocking (to 1.6Ghz) fried something involved in the battery communicating with the motherboard. implies your hardware was functioning properly before you flashed the OC kernel...which then means that the malfunction happened from software not hardware...of course if something is fried then yes...YOU borked the hardware and it would need replacing...I had a similar issue and was just reporting what fixed my issue with the Red LED and not being able to boot.
abnormalreply said:
You don't think it's bricked, because you don't understand the problem. My post in this very thread explains why this is a hardware issue of a defective battery, and not a software one.
Click to expand...
Click to collapse
You're in the same boat mate, you're sending the phone back on warranty, when it's your overclocking that broke it. There is a reason why its pegged at that speed. I mean if you want to argue it was a manufacturing defect that was only found via overclocking that is fine, but it doesn't help the case that you ran the phone outside of spec. Don't steal from google.