Related
Okay so hope this is the right spot to post this....
My phone about two hours ago was on working fine. At about 30% bat...
I took a nap and now when i plug it in to the charger it will not turn on at all.. only thing that happens is the LED blinks that orangy color over and over...
If i remove the battery and put it back in.. still nothing at all ever comes on the screen.
After removing the battery and while plugged into the charger if i hold the power button it will vibrate once and thats it...
not sure whats happening.
I was on gingeritis 1.0 and everything was great up to this point.
any ideas??
Let is attempt to charge for a while, maybe 2 hours. Then see if you can power up into the bootloader. See if that works.
I had that happen once as well. I just let it sit on the charger for about 15-20 minutes, and it booted up with no problems after that. In my case, it looked like the battery was just completely dead and needed to build up enough juice to last until after it booted up.
FreemanB said:
I had that happen once as well. I just let it sit on the charger for about 15-20 minutes, and it booted up with no problems after that. In my case, it looked like the battery was just completely dead and needed to build up enough juice to last until after it booted up.
Click to expand...
Click to collapse
Yup, ditto.
Sent from my ThunderBolt using XDA App
Questions like this do not belong in the development section.
Please post in the Q&A section.
http://forum.xda-developers.com/forumdisplay.php?f=1103
Wrong section brother.
^_^_^
Ditto, try pulling battery out for 5-10 seconds, put the charger. It will not blink, then it will flash orange blinks let it sit for some 15. Minutes. Remember that TB takes alot of juice to reboot sometimes 5%.
STAY AWAY FROM ALL GINGERBREAD ROMS
My phone got stuck on the white htc screen this morning all of a sudden without any perceivable reason at all. Luckily I was able to restore to a backup.. BUT... It wouldn't install any new roms on my phone anymore for some reason.. they all get stuck on the white htc screen.
My advice.. GB is f&&&ked somewhere deep down.. and which is probably why it isn't officially released yet. Keep off of it if you don't wanna brick your phones.
kriskmk said:
STAY AWAY FROM ALL GINGERBREAD ROMS
My phone got stuck on the white htc screen this morning all of a sudden without any perceivable reason at all. Luckily I was able to restore to a backup.. BUT... It wouldn't install any new roms on my phone anymore for some reason.. they all get stuck on the white htc screen.
My advice.. GB is f&&&ked somewhere deep down.. and which is probably why it isn't officially released yet. Keep off of it if you don't wanna brick your phones.
Click to expand...
Click to collapse
That's a sign of a hardware failure I had a bad touch screen and once it went out it wouldn't boot past the splash, I'm sure it's similar with other hardware failures so it's a bad device not the gingerbread roms
Atleast that's my opinion
>--The Game--<
kriskmk said:
STAY AWAY FROM ALL GINGERBREAD ROMS
My phone got stuck on the white htc screen this morning all of a sudden without any perceivable reason at all. Luckily I was able to restore to a backup.. BUT... It wouldn't install any new roms on my phone anymore for some reason.. they all get stuck on the white htc screen.
My advice.. GB is f&&&ked somewhere deep down.. and which is probably why it isn't officially released yet. Keep off of it if you don't wanna brick your phones.
Click to expand...
Click to collapse
Sounds like you didn't wipe data.
jcase said:
Sounds like you didn't wipe data.
Click to expand...
Click to collapse
But if he flashed Gingeritis, wouldn't the script have done in for him in cwr?
Sent from my ADR6400L using XDA Premium App
I had this happen to just a few ago.
Picked up the phone and screen was off,Normal, I hit power and nothing.
Pulled battery, went bootloaded mode recovery and wiped and loaded bamf.
I have all the roms on my SD now.
Serious now, that was the second time I loaded th3ory.
The first time, I went to uninstall something and when I hit uninstall the button started flickering wild.
I kept mashing uninstall,I got it to switch to the next screen where you hit ok.
Then got a pop up over and over, phone force close sorry.
Pulled battery and went recover and loaded bamf.
So th3ory came out with v4 I thought ok why not.
Then I had the dead phone problem like you are talking about.
I don't want to bash any dev or Rom but I'm not sure about th3ory Rom guys.
I posted because this just happend to me and many post are talking about battery.
I don't think its a battery problem guys
jcase said:
Sounds like you didn't wipe data.
Click to expand...
Click to collapse
Of course I did...and not just once.
Sent from my ADR6400L using XDA App
superchilpil said:
That's a sign of a hardware failure I had a bad touch screen and once it went out it wouldn't boot past the splash, I'm sure it's similar with other hardware failures so it's a bad device not the gingerbread roms
Atleast that's my opinion
>--The Game--<
Click to expand...
Click to collapse
If it was a hardware failure it wouldn't have worked with my froyo backup.
Sent from my ADR6400L using XDA App
tanium said:
I had this happen to just a few ago.
Picked up the phone and screen was off,Normal, I hit power and nothing.
Pulled battery, went bootloaded mode recovery and wiped and loaded bamf.
I have all the roms on my SD now.
Serious now, that was the second time I loaded th3ory.
The first time, I went to uninstall something and when I hit uninstall the button started flickering wild.
I kept mashing uninstall,I got it to switch to the next screen where you hit ok.
Then got a pop up over and over, phone force close sorry.
Pulled battery and went recover and loaded bamf.
So th3ory came out with v4 I thought ok why not.
Then I had the dead phone problem like you are talking about.
I don't want to bash any dev or Rom but I'm not sure about th3ory Rom guys.
I posted because this just happend to me and many post are talking about battery.
I don't think its a battery problem guys
Click to expand...
Click to collapse
For one all GB ROM have the data load issue when trying to uninstall. Second, if it was a issue, more people would have reported it.
Titanium Backup, a App you use in every ROM, CPU setting to low, not wipe to save some time, a multitude of things could cause you a issue.
In my defense, if it were my ROM, it would be heard.
Sent from my ADR6400L using XDA App
kriskmk said:
STAY AWAY FROM ALL GINGERBREAD ROMS
My phone got stuck on the white htc screen this morning all of a sudden without any perceivable reason at all. Luckily I was able to restore to a backup.. BUT... It wouldn't install any new roms on my phone anymore for some reason.. they all get stuck on the white htc screen.
My advice.. GB is f&&&ked somewhere deep down.. and which is probably why it isn't officially released yet. Keep off of it if you don't wanna brick your phones.
Click to expand...
Click to collapse
Dude. Stop bashing the GB dev Rom. You run the risk of bricking with any Rom. Plenty of people are using GB and the 2.5 radio with no problems, myself included. If it docent work right on your phone then put something else on it. Not every phone is going to react the exact same way to a flash. Your always going to have those few exceptions, even with OTA's.
Sent from my Rooted Remixed BAMF URBaN Thunderbolt.
kriskmk said:
STAY AWAY FROM ALL GINGERBREAD ROMS
My phone got stuck on the white htc screen this morning all of a sudden without any perceivable reason at all. Luckily I was able to restore to a backup.. BUT... It wouldn't install any new roms on my phone anymore for some reason.. they all get stuck on the white htc screen.
My advice.. GB is f&&&ked somewhere deep down.. and which is probably why it isn't officially released yet. Keep off of it if you don't wanna brick your phones.
Click to expand...
Click to collapse
Not good advice at all.
Check your charging cable! I just had a bad cable the other day and my phone was doing the same exact thing... light bliking on and off. I found if I plugged it in and then lightly pulled it half way out the orange light stayed solid, but it took some work.
Before you start freaking out, just try another cable... hopefully its not the connectors inside your phone.
RootandBoot said:
Dude. Stop bashing the GB dev Rom. You run the risk of bricking with any Rom. Plenty of people are using GB and the 2.5 radio with no problems, myself included. If it docent work right on your phone then put something else on it. Not every phone is going to react the exact same way to a flash. Your always going to have those few exceptions, even with OTA's.
Sent from my Rooted Remixed BAMF URBaN Thunderbolt.
Click to expand...
Click to collapse
no need to get your panties in a bunch.. My advice is only worth whatever it is.. (which may be nothing too).. and I am not thrusting it on anyone to follow it.
Where the hell do you figure I am bashing devs??? The more time one spends on xda the more you come across these noob "police figures" who go around poking into unrelated stuff getting all worked up for nothing.. Like I said.. it is probably something to do with how the alpha gingerbread works at the core level which is causing all these problems.. it has nothing to do with devs.. and look around you.. plenty of people are reporting the same. I didn't see anyone complaining when devs reported the same with the earlier GB and asked people to stay away from it. Were they doing it so that they can bash other devs who had their GB roms out before they did? I don't think so. So quit shooting from your hips and move along.
If the led is blinking it means the phone is totally dead. If you let it sit the light will eventually become solid and be fine
Sent from my ThunderBolt using XDA Premium App
I just tried to flash my phone with the preroot GB flash and it installed and when I rebooted my phone my touch screen will not work. so I tried to flash it back with the sbf and now im at the activation screen but the touch screen wont work. Any advice of what I can do?
try booting into stock system recovery and doing a data format and then try booting.
Someone On Rootzwiki Is Also Having This Problem Can't Get The Droid To Register Touch.
i believe most if not all of us occasionally lose touch responsivness until the screen is turned off and back on which only takes 2 seconds. But this problem is different of course...possibly related...
MikeJ92YJ said:
Someone On Rootzwiki Is Also Having This Problem Can't Get The Droid To Register Touch.
Click to expand...
Click to collapse
Thanks mike.
Ive been dealing with this same issue for atleast 5 hours now and im tired of sbf'ing............idk what to do.......
I booted into stock recovery and did a data reset and its still doesn't work. If I did a SBF will verizon be able to tell it was rooted? I don't want charged for a new phone I might just soak this one in some water.
vacobra1 said:
I booted into stock recovery and did a data reset and its still doesn't work. If I did a SBF will verizon be able to tell it was rooted? I don't want charged for a new phone I might just soak this one in some water.
Click to expand...
Click to collapse
If you sbf they can't tell you were rooted
Sent from my DROID X2 using XDA App
No Touch Response
Is you phone charging? I had the same problem, but when I unplugged from charger all worked well (until I plugged it back in). I unplugged, went into recovery, factory reset, then did SBF and presto changeo, My phone responded to my touch
Also...
I have sent many phones back to Verizon, still rooted, and have NEVER been charged. When I call I do not tell them it was rooted. With SBF, as long as you cleared data/Factory reset first, there will be no indication it was rooted ever.
my phone is charging I unplugged it and im going to do a factory reset with out it plugged in and see what happens
Thread moved to proper forum since this is not android development.
still nothing
Hardware problem, get a replacement
vacobra1 said:
still nothing
Click to expand...
Click to collapse
i still can't get mine to do anything either.......................and i thought i had good phone because i have NEVER had 1 single problem out of it like all these other people on these forums......
I have a replacement on its way. So tomorrow ill be up and running I think ill just wait for GB to come from verizon this time.
My wife has a Atrix (2.3.4) and not only does it randomly shut down but I can not seem to root it. For rooting I tried to Gingerbreak it with 1.20v, and I have tried the Superone Click. I made sure to enable USB debugging is on and that the SD card is in the phone. The drivers are installed on the pc that is doing the rooting but I can not get it to work. Gingerbreak just hangs till it dies, and SuperOne Click 1.6.5 just hangs.
The other issue is once unplugged the phone will shut off on its own even when she is on the phone with someone. These issues are tricky to me because I also have a Atrix that I was able to root and it doesnt have a shut down issue. You guys know why mine is Awesome and her's is crapping out.
Pudding will solve both problems, i havent had a shutdown/reboot issue since Alien. On a sidenote I am guessing you are experiencing a graphical shell crash, at least thats what I was told and I believe because on one "reboot" my call was never disconnected I carried on my conversation through the whole thing lol.
Edit: it was late last night.. That first sentence should read, I havent had issue since flashing Alien(#4). The way I wrote it sounded like I (had) issue with Alien but thats not the case, my Atrix has never run better. Now just holding out for fingerprint on CM.
WiredPirate said:
Pudding will solve both problems, i havent had a shutdown/reboot issue since Alien. On a sidenote I am guessing you are experiencing a graphical shell crash, at least thats what I was told and I believe because on one "reboot" my call was never disconnected I carried on my conversation through the whole thing lol.
Click to expand...
Click to collapse
I will give that a shot
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
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.