so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
I've had that problem after a bad flash, but it still let me get into hboot and recovery without problems, so I doubt it was that. Don't have a clue what it could be though... at least you got him taken care of with a refurb. Maybe the inability to boot to recovery could be not having amon ra or cwm installed (never tried without one) and if he wiped /data or /system I don't know if factory reset would know what to reset to (again, never tried).
Edit: Also, with me, the phone never died. White HTC screen would stay up until I pulled the battery and it would still recognize the charger.
exactly! it's a problem after a bad flash. i wonder if this dude was lying and tried to flash something, his battery died, and it bricked it
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
edit - there is one difference: my battery never died. I took my phone out of my pocket at 5:40 to look at it, and it was fine. I looked at it again at around 5:50 and I had the white htc screen. At this point I pulled the battery and started googling.
second edit - could the forced update have something to do with it??
nope, he brought his in before the update.
have you gotten anything to work? when we called customer service, they just replaced his phone for him..i hope it works out for you, man. maybe try to get into fastboot and wipe the phone, or something? i know i was able to get into the bootloader..maybe you can push a factory reset from the comp
avertist said:
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
Click to expand...
Click to collapse
If you want to at least get the data off of it you can try using testdisk.
http://www.cgsecurity.org/wiki/TestDisk
I used it for my external sd card that wouldn't read in the phone or computer anymore and had all my nands and other backups on it. It seems like it won't work on Android but it will, but since I formatted it in the phone it didn't seem to have a volume name.
After you select the drive and it comes up with the partition table list, select [None].
Then select [Analyse]
I think that's when it will list all your directories.
You might be able to hook up your phone and get stuff off the internal card if you leave it at the white htc screen, not sure. But I have used testdisk successfully on a drive and the sd card that all systems said was unreadable and needed to be formatted. Anyway, it's worth a shot to see if you can get your stuff off it even if you have to return it.
jayochs said:
so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
Click to expand...
Click to collapse
Yeah I had a lot of white screen time when I had the Evo! A co-worker of mine had this happen on his Evo. It was from overheating. Now I realize this is the Rezound we're talking about but brilliant phones do think alike.
Sent from my ADR6425LVW using Tapatalk
happened to me when the kernel didn't flash but the rom did. Had to boot into fastboot and flash a kernel through a command prompt on my PC.
Just finished dealing with this after a bad flash. I couldn't boot, couldn't flash a new rom because of the Mainver error and couldn't get into recovery. Finally fixed it by deleting the PH98IMG.zip file. That let me get into recovery. Then had to flash back from ICS to Gingerbread. The I could follow the instructions to fix the Maiver error.
I had heard reports that people had data loss issues from the battery dying all the way in the rezound? Something tells me running the RUU on the phone would have fixed it.
Sent from my ADR6425LVW using XDA App
Related
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
MooseV2 said:
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1393519
Click on the software and tools link and use rsd lite to reflash the stock os onto the phone. If that doesn't work I would take it to the sprint store.
I assume you tried pulling the battery?
I'm downloading SBF now. Hopefully it works, because I live in Canada and we don't have Sprint stores.
And YES, I tried pulling the battery. Multiple times. With every combination (eg, plug in, turn on, then insert battery; put in battery, turn on, then plug in, etc)
the sbf should work but may i ask how you managed to brick your photon? when i just got mine i did everything wrong and i never got even a soft brick so i'm interested what i didn't mess up haha
Quick question: I should be downloading the most recent? Will it make a difference?
And damn, did I actually brick it?? I'm pretty new to this thing, this is my first Android and I've had it for less than a month...
And nothing should have triggered it. I added another line in build (ro.media.setting.1080p or something) and I added another setting in /system/etc/mediaprofiles.xml. I was trying to add 1080p to the camera (unsuccessfully). I didn't remove anything, and even after a reboot it was fine.
It wasn't until the battery died, where it stopped booting up. Just my luck :/
You should probably choose one of the newer ones, just becasue of bug fixes, etc. If you happen to know what version you were running before then I'd choose that. I cant stress enough, make sure the one you download is for the Photon and NOT Electrify! And technically yeah that is a brick lol but its extremely hard to legit brick beyond repair a photon due to the fact that we have RSD Lite and SBF files to bring it back.
Strangely, I found a thread depicting the same problem that I had, although with the electrify. http://forum.xda-developers.com/showthread.php?t=14813
Anyways, the problem is fixed, by reflashing the SBF using RSD Lite, everything is back to normal! Well, almost, just have to restore my backup
Thanks so much for your help guys, I wouldn't have been able to fix it without you all!
can you fix a bricked phone??
My Photon has done the same thing! I rooted her and did the Bootstrap Recovery thing. Everything was kosher until I tried to load that stupid Beats Audio. Something happened between me flashing it and the reboot where it locks the phone. I tried to do the Android recovery screen, I wiped, I did about everything I could find. No bueno.
I followed this forum and clicked the software and tools link as instructed. I tried with RSD 5.6, and tried several iterations of SBF's located here and here. I was using SBF - 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_MR-3-CM.
It lets me go into boot mode, and when I try to flash the SBF it appears to go through, but it always fails at the end. Which, the posts state it will do, but my phone will not reboot afterwords. After trying everything I could for a couple days, I decided to just take it to a Sprint store. Mind you I've had this under 30 days, but longer than 14 so they stated it would have to be replaced. They tried to flash, but said they were getting stuck too.
I know that a replacement is pretty much the answer, but just wanted to check one more time to see if anyone had any other ideas, or could point me to other forums maybe? Appears I've done what few have been able to accomplish...brick this joker.
Well I went to flash a test mod I made last night trying out the new vrtheme engine and pretty much bricked my phone. Not sure what happened worst I expected was a boot loop :silly:
I have a new one on the way but figured I'd give one last try incase I missed something. When flashing the mod I got an error, then rebooted the device to see if the mod took or not and my phone went dead and won't turn back on. I tried different batteries- fully charged (I have 3), using amonra so I know its not the CWM bug. I get nothing, no recovery or hboot, no adb or fastboot, No charge indicators, no physical mutations no nothing.
The only thing I get is 2 quick beeps when I plug it into my laptop. My work computer doesn't have the drivers so I get a device not recognized but nothing else.
Ideas anyone????
would like to know what happened so I don't do it again but I can't even check .
i did something similar.
i was attempting to build a rom and the phone booted then the screen went black and now pretty much the same thing, but i don't even get the 2 beeps.
it kills me, lol. I've flashed hundreds if not thousands of tests builds and "experiments" to my phones, done mods and themes for multiple phones never had an issue then something that is essentially a meta-morph breaks my phone, I'm more in awe than upset.
edit: please don't think that I'm blaming vr theme engine. I've flashed other vrthemes and was fine, this is something I did with a mod I was working on, just not sure what went wrong.
Run an RUU?
Tried, just waits for device for the exe version and cant get to hboot for the other. My phone was due to be returned at some point I had major heat issues saw the 150*f 's a few times and other quirks. Still think it was the mod though.
Well replacement just got here. It was nice of Verizon to ship out a replacement Incredible that is years old but now I have to wait 2 more days for my replacement Rezound....sigh @ Verizon....
Just got this same issue as well on my phone.
Only difference being that mine wasn't installing a theme.
I had just flashed the newest Ineffebilis Deus (1.1), had an issue where I only saw the menubar, rebooted, wiped and flashed again. Told it to restart, now it won't do anything. No charge light, etc. Using AmunRa, btw.
I have no other batteries to test with, unfortunately.
adb shows no devices and even the wall charger doesn't do anything.
Just my luck that it does this two days before I get on a plane, haha.
Phone shut off and will not turn on, will not charge, will not boot, nothing.... here's the backstory.
I root my girls EVO LTE for her just for the sake of backing up data and pictures and texts. She also enjoys Fresh ROM, but I never got around to putting it on this phone, bc at the time there was no need. Also, I never did get around to turning S-OFF, just rooted, stock rom, nothing else.
About 3 months ago, she had a random boot loop, which, after some googling, seemed to be a random problem that some people were experiencing, unrelated to root or anything. So we fixed her phone, updated it, at the time, and have since done nothing to it. A few weeks ago, she started have major problems. Texts would take 5 minutes to open, contacts would also, and sometimes she couldn't dial out. Problems that I hadn't gotten around to looking into.
Today, her phone just completely turned off and hasn't done anything since. Won't turn on, charging does not give it a light. I tried to boot into recovery etc. Is the phone completely BRICKED?
It's within the year warranty, but I know if sprint gets it back on and see it's rooted, they'll be assholes about it, even though it doesn't seem to be related.
jirafabo said:
Phone shut off and will not turn on, will not charge, will not boot, nothing.... here's the backstory.
I root my girls EVO LTE for her just for the sake of backing up data and pictures and texts. She also enjoys Fresh ROM, but I never got around to putting it on this phone, bc at the time there was no need. Also, I never did get around to turning S-OFF, just rooted, stock rom, nothing else.
About 3 months ago, she had a random boot loop, which, after some googling, seemed to be a random problem that some people were experiencing, unrelated to root or anything. So we fixed her phone, updated it, at the time, and have since done nothing to it. A few weeks ago, she started have major problems. Texts would take 5 minutes to open, contacts would also, and sometimes she couldn't dial out. Problems that I hadn't gotten around to looking into.
Today, her phone just completely turned off and hasn't done anything since. Won't turn on, charging does not give it a light. I tried to boot into recovery etc. Is the phone completely BRICKED?
It's within the year warranty, but I know if sprint gets it back on and see it's rooted, they'll be assholes about it, even though it doesn't seem to be related.
Click to expand...
Click to collapse
Does it show in device manager when you connect to a pc?
njfoses said:
Does it show in device manager when you connect to a pc?
Click to expand...
Click to collapse
Well I dont have the drivers installed bc I recently added an ssd and started from scratch, and like I said, I don't mess with her phone too often.
But it doesn't do anything when I plug it in via usb, doesn't make a sound, nothing pops up, and it doesn't try and connect. It's lifeless.
Some have had good results plugging into a wall charger for 6-8 hours and then it comes back to life.
It may work.
Sent from my PC36100 using xda app-developers app
Your timing is good, bricks tend to happen during major updates
Have your gf take her phone back to the Sprint store and say it won't turn on, charge etc. if the phone is truly bricked, they can't tell it was rooted or whatever. They should replace it because it's within the warranty period. If she has an SD card, take it out (especially if it had ROMs on it).
The key is have your girl friend do this, better would be to have someone's mother take it in.
bigmoogle said:
Your timing is good, bricks tend to happen during major updates
Have your gf take her phone back to the Sprint store and say it won't turn on, charge etc. if the phone is truly bricked, they can't tell it was rooted or whatever. They should replace it because it's within the warranty period. If she has an SD card, take it out (especially if it had ROMs on it).
The key is have your girl friend do this, better would be to have someone's mother take it in.
Click to expand...
Click to collapse
This is exactly what I done when I bricked downgrading firmware. An OTA had just been released and I told them I took the update and the phone died. They replaced it immediately no questions asked.
Sent from my EVO using xda premium
Ok, so my fiancee's at&t note is stuck in a bootloop. I had it running on Blackstar, and since giving it to her hadn't bothered messing with the setup as it was stable. On her way home from work she apparently left the phone in her truck while making a stop in 92 degree weather(Farenheit). Now it will show both Samsung screens and then bootloop. I did some searching here on the forums and have tried everything I can find/think of. Here's a list of everything I've done:
1. Booted into twrp recovery, wiped data, cache, and sdcard for good measure.
2. Got to lockscreen, bootloop.
3. Used ODIN to push Samsung stock files onto phone, including recovery.
4. Got to AT&T easy setup screen, bootloop.
5. Used stock recovery to do hard reset.
6. Still bootlooping from second Samsung screen.
7. Removed back of phone, cleaned power button.
8. Still bootlooping.
I should note that the phone never booted itself after a battery pull, but I figured cleaning the power button couldn't hurt any.
Is there anything else I can try before going to at&t to have it fixed?
UPDATE: Thanks rangercaptain for that. I had totally forgotten Kies had the Firmware recovery. Unfortunately, it didn't work. And AT&T, well, we all know how they are about out of warranty phones. So I'm seemingly stuck, but I did have a thought. If the battery overheated, and malfunctioned, could it cause this? Would it be worth the 10 bucks to order a replacement OEM battery on Amazon and see if it fixes it?
Kies emergency firmware upgrade. Factory cable. Rear (powered) usb port on pc. Battery fully charged. Serial and model number under battery (all capital letters). Pray.
Don't quote, reply. If you quote, edit.
The battery try might be worth a shot. If not.... Surely mobiletechvideos could fix it. If they can be brought back from the dead, surely they can be brought out of bootloop.
Sent from my SGH-I717 using Tapatalk 2
darthmalgus said:
UPDATE: Thanks rangercaptain for that. I had totally forgotten Kies had the Firmware recovery. Unfortunately, it didn't work. And AT&T, well, we all know how they are about out of warranty phones. So I'm seemingly stuck, but I did have a thought. If the battery overheated, and malfunctioned, could it cause this? Would it be worth the 10 bucks to order a replacement OEM battery on Amazon and see if it fixes it?
Click to expand...
Click to collapse
Definitely try the battery. I had exactly this same problem, and even though the old battery seemed to be taking a charge, it was still screwing everything up (in the same ways you described). A new battery fixed everything*.
* - Ok, it actually it took a couple ROM reinstalls, to fix everything I apparently screwed up while trying to fix the devices before switching out the batteries.
Thanks for the info. I went ahead and ordered a new bateery, it'll be here Monday, so hopefully that works. I have the phone flashed stock with Kies at the moment, so I would hope I don't have to do any more reflashing if the battery is the issue.
Yeah i have the same issue. I was running blackstar. I had some issues occasionally with it crashing, nothing major. decided to install JB once ATT had official out. Wiped, installed, gets to att logo and reboot... please post your fix if it works. I have a second battery. I'll give it a shot but I have been keepeing it plugged in while doing these things and it still doesnt work.
"Wiped, installed, gets to att logo and reboot..."
If you're getting to the att logo, it may not be a battery problem. I'd suggest reinstalling the update after manually wiping everything using CWM.
Matt Bernius said:
"Wiped, installed, gets to att logo and reboot..."
If you're getting to the att logo, it may not be a battery problem. I'd suggest reinstalling the update after manually wiping everything using CWM.
Click to expand...
Click to collapse
Tried a couple flashes, with the debloated and bloated Roms based on Official JB. I can get to the getting started screen sometimes. typically I hit the next button and it goes into bootloop. once or twice i was able to select the next button and get to the next screen before it crashed. I'm thinking it's dead but.... idk.
This fixed my issue...
Replaced battery and yeah. I'm all better. so odd.. shrug. The other wasn't giving any indication that it was actually defective.
Awesome ... final step ... change the title to include solved :victory:
So this morning I woke up and looked over at my phone as I usually do and the HTC white boot screen was showing. I decided to let it boot up thinking that overnight something happened. About 5 minutes later I went back and it was still at the boot screen. I decided to pull it from the charger and do a battery pull as I would usually do whenever something happens to this phone. After doing said battery pull... Nothing happened. I tried starting the phone up from essentially every single possible source I could think of. My laptop installed the drivers, but that was all that happened. I tried swapping batteries, but nothing happened either. This phone is a little over 2 years old so it may be the end of its life cycle, but I want to revive it just so I can back up everything onto my computer. I do have my media backed up to 3 different cloud sources, but it's better to have it on an actual folder rather than sorting through lord knows how many photos and putting them in separate folders. I am due for a new phone, but since I am 17, I do not have to ability to buy it off Swappa or any place so reviving the phone would be great. As of right now, the phone is still dead and may possibly be an aluminum brick.
NOTE: This phone is completely stock running on ICS 4.0.3 on Sense 3.6. I have done nothing with this phone in terms of flashing or rooting.
Your best chance would be to root it and flash a recovery and backup your data through the recovery, then you can try some fixes like flashing a rom or a RUU or just do a factory reset and see.. If you do a factory rest now you'll loose all your data
Sent from my HTC One using XDA Premium 4 mobile app