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
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 two days ago my rezound started randomly rebooting...I thought it was the new ICS rom I had just put on (the newest leak) so I desided to nandroid back to an older ICS that ran smoothly before. Same reboots... and the phone gets hot. So I figured I would just let it rest a night and took the battery out. No Joy.
Today, I RUU'd back to stock and things were running ok for a while... but as soon as I plugged it in my car... reboot after reboot.
I bought it at Best Buy as they had a better deal and better insurance. My only concern is that big ReLocked on the bootloader.
Has anyone successfully returned the phone after unlocking? Hoping doing that didn't negate that insurance. I guess I don't mind stepping on accident on it if need be.
Have you tried this fix?
http://forum.xda-developers.com/showthread.php?t=1394659
No, I hadn't until now... will try tonight, but the phone will stay operational for a while... just seems to be when I charge it from the wall or car charger... charging using USB trickle charge, it doesn't reboot as much. I don't hink is has to do with the network connecting thing....as it does boot up and I can make calls... and search online, and use the navigator... until it just gets to hot.
Xsoldier2000 said:
No, I hadn't until now... will try tonight, but the phone will stay operational for a while... just seems to be when I charge it from the wall or car charger... charging using USB trickle charge, it doesn't reboot as much. I don't hink is has to do with the network connecting thing....as it does boot up and I can make calls... and search online, and use the navigator... until it just gets to hot.
Click to expand...
Click to collapse
I know this might be a long shot but since our devices don't have s-off, restoring nandroid backups don't restore the boot.img. did u try flashing the stock kernel? I'd try flashing the latest GB kernel, then flash the latest GB stock ruu? I had a similar issue and found out it was the kernel I was using. Was on anthrax kernel
Sent from my ADR6425LVW using XDA
Well, I RUU'd back to the OTA...renamed the .zip to PH___.zip and rebooted into fastboot and it updated everything. I then restart and everything is back to square one, like I just opened the box and activated it.
I presume the RUU flashes over the right kernel as released by Verizon.
I'm really thinking the battery is crapping out. can't hold a charge more the 42% and gets hot...then run out in like 20 minutes... throw in a couple reboots...and higher blood pressure ensues.
Xsoldier2000 said:
Has anyone successfully returned the phone after unlocking? Hoping doing that didn't negate that insurance. I guess I don't mind stepping on accident on it if need be.
Click to expand...
Click to collapse
I don't have insurance, but I returned a relocked Rezound to VZ online for overheating a couple months ago with no problems.
99 out of 100 times, the rep will not check to see if the phone is relocked, let alone if he knows how to check it.
You're worrying over nothing. If the device is defective due to manufacterer defect, and breaks down becaue of said default. They will honor warranty/exchanges since they are the ones at fault. Now if you fragged your phone because of an oc, bad flash, wrong software, that's your own bad and you're on your own. Unless you have insurance and the phone met its untimely end under your vehicle.
Thanks for all the help... I went and bought a new battery for it, and it does the same thing. Re-locked and bringing it back to best buy today. Fired up my ole OG and flashed the newest MIUI release... the phone is still kicking!
So, two days without the rezound and I'm tweaking..... need to flash a Rom! (Maybe this will be good for me.....)
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
Hello everyone,
I have a stock Verizon Galaxy S4 that is having some issues and wont stay on and sometimes gets caught in a bootloop. I have been able to get into recovery and wipe cache / do a factory reset, but the phone keeps doing the same thing; reboot, sometimes start but then reboots again. I have had it for almost 2 years and thought it was the battery, so I bought another one and the phone still does the same thing. If I boot into safe mode, it lasts a little longer that way, but will eventually turn off and get caught into the bootloop again.
Any ideas on what the cause is and possibly how to fix it? The is completely stock and has never been rooted, unlocked, or anything like that. I looked in the forums, but it looks like they all have to do with flashed roms and non-stock options, which is why I am posting a new thread.
All help is appreciated. Thank you.
It sounds like your power button may be on its way out. I had the same issue with my phone. Couldn't get it to boot past the splash screen. If your is intermittent it may or may not be this issue. However if the problem gets worse, its more then likely the cause. After a lot of use the insulation inside the power button can wear away causing a short. If you google it there are several articles describing symptoms to help figure out if that is indeed the problem. If you run in to a boot loop, pull the battery and reinsert it. If the phone powers on without pressing the power button, that is your problem.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Eclipse ROM fatness!
MyColorScreen
I know it has been a few weeks but I wanted to provide an update. I have a friend who runs a cell phone repair shop. I took it to him and they did all sorts of tests and such, so we replaced the power button. After replacing the button, the phone still did the same thing.
I would pull the battery, but the phone would not turn on by itself. I would power on the phone like normal and would make it to the splash screen in which the phone would then power off. At that point, it would not try to restart, but rather would act like it was on and the phone / battery would get really hot. I would pull the battery and start again, with the same result.
Any other ideas? My friend, the co-owner of the business, and myself are all out of ideas.
Thanks!
Edit: Also I called Verizon and Samsung to see if I could work out a warranty through either of them. Since the phone is almost 2 years old, we all know the answer to that. Sammy wanted $70 just to look at it, let alone additional charges to fix it if the problem wasnt what they thought it was.
poda13 said:
I know it has been a few weeks but I wanted to provide an update. I have a friend who runs a cell phone repair shop. I took it to him and they did all sorts of tests and such, so we replaced the power button. After replacing the button, the phone still did the same thing.
I would pull the battery, but the phone would not turn on by itself. I would power on the phone like normal and would make it to the splash screen in which the phone would then power off. At that point, it would not try to restart, but rather would act like it was on and the phone / battery would get really hot. I would pull the battery and start again, with the same result.
Any other ideas? My friend, the co-owner of the business, and myself are all out of ideas.
Thanks!
Edit: Also I called Verizon and Samsung to see if I could work out a warranty through either of them. Since the phone is almost 2 years old, we all know the answer to that. Sammy wanted $70 just to look at it, let alone additional charges to fix it if the problem wasnt what they thought it was.
Click to expand...
Click to collapse
I have to say I'm shocked its not the power button. My only other suggestion would be to flash the stock firmware to the device using Odin. It could be a software problem. Your guess is as good as mine. However flashing the stock image is definitely cheaper then hassling with Sammy or big red. Not that voiding your warranty would matter at this point but make sure you flash whatever firmware your on right now. If you go backwards you may run into a problem since your phone has the Knox boot loader. Check out the i545 android development section here at XDA for tutorials on how to do so. There are a few of them out there. I'm not completely familiar with that process since I'm still on MDK firmware. But there are plenty of knowledgeable guys that can help you on those threads if need be. Good luck!
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Eclipse ROM fatness!
MyColorScreen
Well, I ended up selling it for $130 to some one for parts. I made full disclosure of what the phone was doing and even showed the buyer exactly what it was.
My father had an older Droid X2 that we are using for the time being. Our contract ends in less than 30 days in which we will be moving to T-mobile anyways. I get literally zero signal where I work and my wife gets very limited service where she works. However, the T-mobile service is excellent in both our respective buildings and in the Phoenix metro area where we live.
I appreciate your thoughts on trying to resolve this. One of the many reasons why I love XDA and the community.