Database Users

phone turned booting up issue

im curious about a issue i may be having. lets say i decide to turn off the phone for whatever reason. when it finally turns off completely when i try to boot it back up it wont turn on! i have to go pull out the battery and put it back on for it to boot up. is that a issue? could it have to do with anything iv done to the phone?

I have the same issue, and my evo is stock with the exception of unrevoked and wireless tether. Would love any input as to why this is happening.
Sent from my PC36100 using XDA App

Mu5ic92 said:
im curious about a issue i may be having. lets say i decide to turn off the phone for whatever reason. when it finally turns off completely when i try to boot it back up it wont turn on! i have to go pull out the battery and put it back on for it to boot up. is that a issue? could it have to do with anything iv done to the phone?
Click to expand...
Click to collapse
I've had the same issue myself, I think it's because I tried to turn the phone back on too quickly after it turned off. Sometimes I have to hold the power button down a little bit longer than I would expect to.

I've experienced the same problem, mine is 100% stock and it usually takes a number of tries to turn it back on...most times i just end up pulling the battery as you said.

yea im not sure if this is a good cause for concern. maybe down the road the battery may start to give out issues?

Didn't notice this. Went through the boot marathon after the update ... I turned it off and set it down for a while and forgot to turn it back on. Powered right back on.

After perma root phone won't shut down completely.

After getting perma root and installing Bacon bits 0.3, when I want to turn my phone off completely it instead just boots back up into the recovery. Does anyone else have this problem or have any ideas how to resolve it?
Sent from my T-Mobile G2 using XDA App

I have no idea, but noticed it too...
Sent from my T-Mobile G2 using XDA App

I am apparently having this problem as well now. I never noticed it before and even after a battery pull my phone seems to boot back into recovery. Any help with this problem would be greatly appreciated. Thanks in advance!

One thing to note is that you need to make sure that you don't have it plugged in and charging. It's known to boot on its own when you do that. I'm not sure if that is a bugged feature or not, but I also have Bacon Bits installed and can shut down fine.
Although, my phone stays on all the time.
Sent from my T-Mobile G2 using XDA App

Ok just tried to turn off my phone with it unplugged and it did not turn on to recovery. So kind of a boo bug for now but I am sure that it will get worked out.

Heh... I'm guessing you all have Clockwork Recovery installed? That's the problem. At least, when I switched to the test keys recovery, it wouldn't constantly start back up with any power regardless of how I shut down.

hmm..i have baconbits installed and dont have this problem. ill look into it

stuck in bootloop on stock Evo =(

I have an Evo that isn't rooted, but is stuck in a bootloop. The battery was getting low and then all the sudden after i charged it some and turned it back on it just loops the boot animation.
I have tried a few things and still can't really figure out why this came out of nowhere. I was running the official 2.3 update for a few days now and this came out of nowhere.
any idea or tips?

Jddroid9 said:
I have an Evo that isn't rooted, but is stuck in a bootloop. The battery was getting low and then all the sudden after i charged it some and turned it back on it just loops the boot animation.
I have tried a few things and still can't really figure out why this came out of nowhere. I was running the official 2.3 update for a few days now and this came out of nowhere.
any idea or tips?
Click to expand...
Click to collapse
So you're 100% stock, huh? (adjusting my thinking to stock type)...
Were you running any new apps or anything before this happened? It was literally out of the blue? I would take the battery out of it, and let it sit for a while (10-20 mins) Then put the battery back in and see if it will boot up. If not, try taking your SD card out and then try booting. If that still doesn't work, I'd suggest doing a factory wipe from your bootloader, then try booting. To do that, power the phone down completely. Hold your volume down and power buttons simultaneously until the hboot screen comes up. Navigate down to 'clear storage', and select it. This will completely wipe all of your user data from the phone. If it still won't boot up after that, I would take it to sprint. Normally I'd suggest using an RUU, but since you're on the OTA, there is no RUU for it yet, and you can't downgrade it, unfortunately. Good luck.
Again, if the phone's super hot, let it cool down with the battery out for a while.

k2buckley said:
So you're 100% stock, huh? (adjusting my thinking to stock type)...
Were you running any new apps or anything before this happened? It was literally out of the blue? I would take the battery out of it, and let it sit for a while (10-20 mins) Then put the battery back in and see if it will boot up. If not, try taking your SD card out and then try booting. If that still doesn't work, I'd suggest doing a factory wipe from your bootloader, then try booting. To do that, power the phone down completely. Hold your volume down and power buttons simultaneously until the hboot screen comes up. Navigate down to 'clear storage', and select it. This will completely wipe all of your user data from the phone. If it still won't boot up after that, I would take it to sprint. Normally I'd suggest using an RUU, but since you're on the OTA, there is no RUU for it yet, and you can't downgrade it, unfortunately. Good luck.
Again, if the phone's super hot, let it cool down with the battery out for a while.
Click to expand...
Click to collapse
That phone is stock (my gf uses it)
I myself have rooted my last few phones (Tbolt right now). yea I'm gunna let it sit for a while now, i tried the SD card thing but its a no go. I'm going to try to let it sit for a while like you said. leaving it alone can work miracles sometimes.lol
Hopefully were good because I don't think she wants to start all over in all of her games!lol
Thanks for the advice!

Jddroid9 said:
That phone is stock (my gf uses it)
I myself have rooted my last few phones (Tbolt right now). yea I'm gunna let it sit for a while now, i tried the SD card thing but its a no go. I'm going to try to let it sit for a while like you said. leaving it alone can work miracles sometimes.lol
Hopefully were good because I don't think she wants to start all over in all of her games!lol
Thanks for the advice!
Click to expand...
Click to collapse
You're welcome. I hear ya about not wanting to lose the stuff, but a reset may be the last resort if it won't boot up. It's better to get it booting and lose all her stuff, than to not have the thing even turn on! Hopefully after it sits for a while it'll fire up for ya though. If not, I'd pay sprint a visit and tell them that the OTA borked the phone!

[Q] EPIC random shutdowm

Ok odd thing keeps happening. My epic will randomly power off but will not power back on until i do a battery pull. I am currently running 2.2.1 RandomRom 2.2 Final EC05. I dont think it is the rom but who knows. Any Ideas would be great! Thanks Everyone in advance.

Do you use setcpu or anything like that? Some phones dont like to run below 200mhz.
Posted by Mr. Z's Epic 4G via Tapatalk

Nope not running anything. It only does it when the phone is not charging. If its on the charger it stays on. If i pull it off the charger it could turn off 20min to 3 hrs later.

harmhimself said:
Nope not running anything. It only does it when the phone is not charging. If its on the charger it stays on. If i pull it off the charger it could turn off 20min to 3 hrs later.
Click to expand...
Click to collapse
My last one did that, but it was because I dropped it. Have you ruled out a hardware problem?
Posted by Mr. Z's Epic 4G via Tapatalk

Not that i know of. Its never been dropped. I wonder if i should factory reset and start all over. I just dont know what else it could be.

It's most likely that it's a third party app causing the issue.
That said, the best way to exonerate the software is to ODIN to the stock EC05. If it does it with that, it's probably a hardware issue. If it doesn't, it's probably a ROM or kernel issue.
P.S. it's humorous that RandomROM might be causing RandomREBOOTS.

Haha.....yea. I liked it at first but guess its back to finding something new.

Yeah I'm having a similar problem also but only recently like no more then a couple weeks... my phone doesn't shut down completely but it randomly restarts itself and the ODD thing is that when it would power back up it would be in AIRPLANE mode. No matter how many times I tryed to disable airplane mode it just would not turn off! Even after I would shut down my phone and power back up it was still in airplane mode. So I took out the battery for a couple of seconds and put it back in, powered up and every thing works fine again... its only happened about 3 times I'm running that new gingerbread leak so that might be the issue but I've been rnning it for a while now and only recently had this problem with the phone.

I run ACS Frozen 1.2 have the same issues, I've had the same issue since froyo sourced roms have come out.... phone randomly powers off..... only happens maybe once or twice a week. It happened extremely more frequently before I changed back to RFS and turned journaling on. It didn't completely correct the problem, but it helped a lot.
Nothing like waiting for a text back from your GF only to find out that your phone has turned off sometime in the last hour since you sent out a text. I call it "The Samsung **** Block"

this happens to me sometimes, if you have journaling off, something might be corrupted. when the phone tries to access the corrupted data it puts the phone in an infinite loop, you might notice a huge decrease in battery life when you do reboot. A fresh clean install is the best way to fix it.

mrhocuspocus said:
this happens to me sometimes, if you have journaling off, something might be corrupted. when the phone tries to access the corrupted data it puts the phone in an infinite loop, you might notice a huge decrease in battery life when you do reboot. A fresh clean install is the best way to fix it.
Click to expand...
Click to collapse
Thanks. I've noticed this.
Sent from my SPH-D700 using XDA Premium App

[Q] My Nexus 7 just exploded. What do I do?

Hey XDA,
I received my 16GB Nexus 7 from Google 4 days ago. I immediately updated to 4.2.1, rooted, and then flashed franco.Kernel. I was running the latest update to franco's kernel, and had left the settings untouched from the defaults with interactive governor. Yesterday I flashed the latest nightly for Cyanogenmod.
I was using the Facebook app when my tablet ran out of battery (I intentionally let it die), and after it powered itself off, I plugged it in with the charger provided to me by Asus/Google. Because I am new to this tablet, I wasn't aware that plugging the charger in meant that the device would power on. Anyways, it did power on, and I had no plans to turn it off now that it had turned itself off. I went to turn the wi-fi off so that it would charge with less power drain, but just before I turned the wi-fi off, the device began to power down again (The charger is still plugged in, and it didn't become unhooked at any time). I begin to walk away to do other things while it turns off again, but I stop when I hear a weird grinding noise. It's hard to explain, other than it sounded like a kettle getting progressively louder and then shutting itself off when it reaches its desired temperature, only it sounded like gears and not a kettle.
A little worried, I wait a bit and then I turn it on. I'm relieved when I see the Google logo appear, and then the Cyanogenmod logo appear. After a long boot, I'm greeted by a black screen with what tiny white flashing dots randomly appearing. I turn the device off, and restart it. Same thing, only now it seems like there may be more flashing white dots than the last boot. I unplugged the device from the wall, and force shut it off (power + volume keys).
I've never heard of this happening before, which is why I'm hoping someone can give me some advice. Obvious things for me to do would be to flash stock 4.2.1 onto my Nexus 7. The reason I haven't done this is that I'm worried that my device may now be dangerous (battery melt, processor malfunction). Does XDA have any recommendations before I phone Google? I'd like to avoid Google because I've voided my warranty with them by rooting and flashing a custom kernel, so any other help is MUCH appreciated.
Thank you so much for reading my essay, and for taking the time to help,
Robert

Do your very best to revert it back to stock os and kernel and re lock the bootloader. Yes it is possible. Look for the nexus 7 toolkit. Then send it to google/asus. Best I can think of dude.
Sent from my MB612 using xda app-developers app

I have heard people with similar issues start device in bootloader and leave it there to charge to prevent the on/off loop and after a few hours when charged boot normally.
Hope this helps
Sent from my SGH-I927 using xda app-developers app

The screen with white dots has turned into what appears to be a screen with no signal like you see on tv's.
This is even happening while I'm in recovery mode, it'll just randomly happen.
What's going on?

Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195

BlackFire27 said:
Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195
Click to expand...
Click to collapse
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert

Trewyy said:
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert
Click to expand...
Click to collapse
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.

BlackFire27 said:
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.
Click to expand...
Click to collapse
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert

Trewyy said:
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert
Click to expand...
Click to collapse
Anytime man! PM me if you have anything else man.

It's 4 days old. Send it back as defective.

turn it off, let it charge for long time, after tha download toolkit and revert it back to stock.
You should be good to go.

I'd bring it back, as it is possible to cause an injury to you. Better to be safe than sorry.
Its new so just bring it back (or send) and get a new one.
Sent from my Nexus 7 using xda premium

Try to relock it and flash the stock rom.
After that, phone up Google and explain what happened AND ask for a compensation. This could have harmed you, and Google/ASUS IS responsible for it. Unless, of course you have messed something up while rooting or flashing the custom rom.
Anyway, you should be able to get a compensation, maybe a 32GB version.
This is not something that should happen to a 4 days old device.

did you void the warranty by flashing? i don't actually know.
granted, this sounds like a hardware malfunction (again, i don't know, could be a kernel), but, modder beware. this is a risk we take.

I'd put it back in the box and return it if possible. Save some time. If they are jerks about it then proceed:
If you can flash anything to it through recovery, download the updated Galaxy Nexus (Samsung) JB Bootloader and flash it.
I have a Galaxy Nexus and a Nexus 7. I killed my first N7 by getting confused and flashing it to my N7. It won't even power on afterwards. That should screw up your partitions enough where it won't be recoverable without a full format/reflash.

I had this issue when my battery died. I took off the back cover and unplugged the battery and plugged it back in. Put it back together and charged it up for a few hours. All has been well since, I'm pretty sure its a common issue with N7's when the battery gets low.

Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app

Do your best to revert it back to factory and call them up about that possible firecracker before something else can happen
keep us informed about what happens too if thats ok

Stock - and the same problem...
Hi, my N7 is two months old and worked perfectly. It's clear stock - never rooted, modded etc. Today I suddenly can't run it - it boots, battery level is 24% (on bootscreen), and after few seconds shows 1% and starts to snow - sometimes with sound. I haven't installed anything new for few weeks, so I'm sure it's not a virus, trojan etc. WTF?
PS. Sorry for my English...

djexacto said:
Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I confirm that. I had this issue already a lot of times. When the battery is completley discharged it seems that the display or the graphics hardware is not able to start as expected. I just left it powered of (or in that charging screen) for some time (>1h) without using it. Then it started normal.
But also for me, no noise, just the screen like on an old TV without signal.