Database Users

Problems booting

Since this morning, when I boot it will get stuck on that red eye screen. I've waited several minutes and it won't go on.
So I end up pulling the battery and usually that works. Sometimes I have to do this twice.
Not sure how to even diagnose this.

HoochieCoo said:
Since this morning, when I boot it will get stuck on that red eye screen. I've waited several minutes and it won't go on.
So I end up pulling the battery and usually that works. Sometimes I have to do this twice.
Not sure how to even diagnose this.
Click to expand...
Click to collapse
Are you rooted or completely stock?
Sent from my ADR6300 using XDA App

Rooted. I just tried restoring a backup from 3 days ago and had the same problem. So I restored back to the latest. When it finally does boot, it seems to run great.
I have a backup from further back, just not sure it will make a difference. Might give that so shot too.

I really think it is booting all the way, and just doesn't stop displaying the boot animation.
The reason I think that is because at some point the power button makes the screen go on and off, and there is haptic feedback in the same places where my lock screen tabs are.
At any rate, and this sounds unbelievable, but I pulled the sd card out and it booted normally. I put the card back in, and now it seems to boot normally. Can't explain it.

[Q] Tiamat ROM Xoom Reboots

I have never been able to get a tiamat kernel to work on my xoom. I followed a set of directions to completely start from scratch (again, plus formatted whole xoom 3-4 times before doing that) and flashed Tiamat ROM and it worked! I was even able to OC to 1.4, 1.5, then tried 1.7 which caused it to freeze and crash. Then it started acting funky so I did a restore and everything is fine until I turn the screen off or let it turn itself off with a timeout.
The system reboots into M screen and/or a black screen. A reset or two gets it rebooted. I increased the min freq and reset max to 1ghz. What can I do to fix this?? Thanks!
--- Update --- The browser causes a reboot as well. Random reboots into black screen. Def could use some help

ALWAYS stays on black screen when screen times out. Also does it after clearing data via honeycomb. Looking for a little help, can't post on the ROM thread yet

Well I would start from new wipe everything and reflash. Can't hurt. Sounds like something is broke. You can also try to fix promissions as well.

I've completely formatted the xoom including the sdcard and then started w/ 3.0.1 then did the 3.1 flash via CWR then the ROM install. The booting is better after complete wipe but screen still doesn't come back on after a time-out or i shut screen off manually. Browser also causes are boot which takes me to a 2-3 'M' reboot which then times out into black screen. 2 or 3 resets later and it boots up but then reboots within a couple minutes.
The official 3.1 update had my browser crashing which is why i said screw it, i'll flash new stuff. Could def use a hand

I am going through the same symptoms. Does anyone have any suggestions?
Random reboots and browser closes all of a sudden, no force close warning..

Me as well I've tried everythingeverything. Currently on tiamat 1.1. With rc4 3.3.0

go into wifi settings and make sure your wifi disconnect policy is set to never

2JZ GZE said:
I am going through the same symptoms. Does anyone have any suggestions?
Random reboots and browser closes all of a sudden, no force close warning..
Click to expand...
Click to collapse
+1
also occassionally find the xoom stuck on motorola boot screen without me trying to turn off or back on..

Ill try but I don't think the wiring has anything to do with the black screen. This will lock even if wifif is off

Mine didnt like 1.7 either, I ended up leaving it sat next to a desk fan for a while to cool it down whioe switched off, then very quickly when it booted managed to get into antutu widget to drop the speed down and hit apply before it locked up again, rebooted all fine now, set it to 1.2ghz to be safe..

Kippui said:
go into wifi settings and make sure your wifi disconnect policy is set to never
Click to expand...
Click to collapse
Dude. I think this worked. I switched my wifi disconnect setting to, never while charging..it was set as, never(uses more battery power). I am currently on Tiamat 1.4.5 with CWM (rc4)3.2.0. Just let it chill over night and charge after a factory reset and viola. Have booted the screen in rotation and a few power offs. Even running at 1.2 g with set CPU. Been running smooth for 2 hours and I can't force it to even freeze. Could it really be that simple. Hahahah. Well see.

Motorola Atrix Sleep of Death

I've been having the sleep of Death since I got my atrix I never use wifi so it can't be that it many happens whilst browsing the Internet once finished I lock phone leave come back to it say 5 minutes later and I can't wake the fone so I have to pull the battery out to get it started
Dose anyone else have the happen to them iv tried reset full flash but it's still there
And could I ask what FakeBlurXmppApp.apk is because since I renamed it I ant had a sod?

I think renaming is the reason of problem if it is the only change you did to phone.
Stock roms usually don't have problems like that.
Sorry for not giving you a real help.

AndroidON said:
I think renaming is the reason of problem if it is the only change you did to phone.
Stock roms usually don't have problems like that.
Sorry for not giving you a real help.
Click to expand...
Click to collapse
Na once I renamed it stopped going into sod

I had the same issue with my Motorola Photon 4G, people are having this issue, I don't understand why it keep doing this, how stupid?

The first time this happened to me I just plugged it in around 60% and went to bed and when I woke up in the morning there was nothing. Even taking the battery out and putting it back in, only the LED cokes on briefly but Jo other signs of booting and the only way I fixed it was by plugging it into a computer, or as I found out the second time an XBOX 360 so I'm thinking just something with a data connection, and pulling it out as soon as the LED flashes green then plugging it into the wall charger. Then the phone came up with the battery charging screen at 0%. After it charged I booted up like normal and it was fine for awhile until one time it died and I had to repeat the process to get it to come back up.

Send it in for a replacement, i had two do this to me and both ended up going out. They were unlocked but once they went out AT&T could not tell.

are you on a stock rom or custom rom? before calling for a new one try flashing 1.2.6 sbf and reroot and unlock the bootloader again.it wont say unlocked when you first flash the sbf reboot and reroot but it still is, itll say the boot loader is already unlocked when you go to unlock it thats fine just reboot and itll be back at the top. im saying this cause i had a similar problem and i couldnt turn the phone on or charge it at all i ended up using a different atrix to charge my battery when i turned it on it was stuck at the dual core boot logo. flashing this sbf fixed my brick and the no charging problem but youll be on the earliest firmware for the phone and have to redo all the rooting process. its worth a try and if it doesnt work then send it back.hope this helps.

I no don't think FakeBlurXmppApp.apk is making my phone sod as I've had it twice today its driving me nuts I don't no what's making it happen in another got no apps installed

Root/unlock causes this
I can tell you the issue is caused by either the unlocking of the bootloader or rooting. I unlocked, rooted, and installed a custom rom my 1st stock atrix and had this issue. I also had a hardware defect with the front camera lens so i returned it to stock via sbf prior to returning it. The problem disappeared. My new atrix worked perfect and after a couple days I unlocked and rooted but left the stock rom. Guess what, sleep of death returned, sbf to stock everything is fine. BTW I was using romracers recovery. So Im not sure if its rooting or unlocking or romracers recovery but it is one of the three. Hope that helps.
-Robert

i also have similar issues. it has some thing to do with deep sleep mode..as long as phone does not go in to deep sleep as son as screen is off the problem never happens.
so i tried wifi wizard and advanced wifi lock apps from market.wifi wizard switches on wifi when ever the screen is on. advanced wifi lock prevents phone from going into deep sleep.you can set a timeout.this works like a charm.i rarely get sod.
Sent from my MB860 using XDA App

Rooting isn't the cause. My first Atrix was rooted & I never had that problem. My second Atrix started right awaywith the SOD, shortly after the OTA update.
And I'm my opinion, unlocking is absolutely necessary. If I hadn't unlocked my previous Atrix so that my backup applications and data syncing would work properly, I would have really been screwed. But every other day my phone backs up my data and once I'm home, uploads out to my home pc.
Sent from my MB860 using xda premium

May be a little premature, but my current Atrix was have SOD & random reboot issues. I had given up & ordered a replacement. However, I changed the screen time out to never & I haven't had a freeze or reboot yet. I'm on day two & I've made a point to turn my wifi on and off. Hope this solves the problem. Guess I'll know if I make it through next week with no freezes.
Sent from my MB860 using xda premium

i bought my atrix within one month of the launch I have always had the sod it has nothing to do with the rom although some roms will make it not happen as much my wife got her atrix like in September and she has never had sod. i just put up with it i plan to leave att once my contract is up
EDIT... reminds me to see if it is up don't remember if its one or 2 yrears

SOD Fix
I was SOD free being rooted, BL unlocked, running rom racers recovery, CM7 then Neutrino 2.6 then my phone decided format its internal partition on me. My phone is back up running now and I was getting the SOD a couple times a day. I fixed it by following 1chris89's fix here. I've been SOD free so far on day two running an OC kernel. 1chris89's fix a bit involved, editing the build.prop file, and based on cm7 flavored ROMS, changing the performance settings. Be careful when messing with the build.prop file and make a backup before attempting! Check out Xploited's guide here for a less involved method to fix your SOD. Hope these help!

OK! But... where can I find this "cm7 performance menu"?

marcosvafg said:
OK! But... where can I find this "cm7 performance menu"?
Click to expand...
Click to collapse
I'm on Neutrino 2.6, to get to it I have to put a short cut on one of my home screens. First long press on your home screen and choose shortcut then choose cyanogenmod settings then choose performance settings.

would if i cannot even get into my phone to change the settings. Can someone with skillz put it into something that i can flash [1chris89's fix]?
it my just be a hardware issue for me also, but i did just get my know back from Motorola with a new screen installed.

When my phone does the SoD I can place a call to it, let it ring a few times, and then hang up. My display turns on and I can get get to the launcher to reboot the phone.
The SoD seems to get worse when I'm using the Bluetooth connection to my Sync system in my truck.

[Q] Randomly rebooting phone even in recovery mode....

Explanation:
Tuesday afternoon I was getting out of my car and dropped my phone like I have done hundreds of times but this time my N4 with the official bumper fell face-up into a small stream of running water on the side of the street. I quickly picked it up and wiped it off and tested it and everything seemed ok but I turned it off to be safe. I came home about an hour later and put it in a container of rice and let it dry overnight with a fan blowing over it. I booted it the next morning and everything was working as it was the day before.
At this point I was stock everything, no root and never been rooted.
Fast forward 2 days laters my device has been plagued with random restarts and/or turning off. At this point I had not installed any new apps or changed any settings so I'm pretty confident it was some rogue app causing this trouble. So I had planned on doing a factory reset but 4.4 was out so I decided if I was going to set everything up again I might as well try the update. I decided to try http://forum.xda-developers.com/showthread.php?t=2507021 and everything worked fine. I cleared the cache and everything, a fresh start. I had no errors trying to install CWM or the ROM and KitKat worked on my phone just beautifully but then it started rebooting/turning off again.
So I went back to stock. Erased the whole device and flashed the radio, bootloader and 4.3 hoping/thinking it was 4.4 causing the trouble but still the same thing. I don't know what else to do so I have come to you XDA!
Weird behavior I have noticed
phone will boot when charger is plugged in
sometimes can't turn on phone without the phone charging - fastboot or normal boot
When I say turn off I mean like the battery has been pulled out of it
Reboots are completely random, sometimes vary from a few minutes to couple of hours of booting up. It happens when the phone is idle and it happens when I'm using the device in more apps that I can remember.
Scenarios & Outcomes
Full boot in 4.3 - Turns off eventually
Full boot in 4.4 - Turns off eventually
Safe mode boot in 4.3 or 4.3 - Turns off eventually
boot into fastboot - Restart the first time then it works as expected
boot into stock recovery - Restarts
boot into cwm recovery 6.0.4.3 - Restarts
Turn on phone - Reboots after google logo shows and boots normally only to turn off eventually by itself

Overclocked too high? Rice blocking cooling, maybe blow compressed through it? Good luck!
Sent from my MZ601 using XDA Premium HD app

[Q] Nexus 4 -- Only working while plugged in...?!

Yeah... I'm not great at titling... Anywho...
I've come across a problem, of which I'll attempt to go through everything I did that leads to the point, which is; my Nexus 4 doesn't turn on without being plugged into, either the wall or any PC.
So my phone crashes, solemnly (probably because I have Cyanogen on my phone), but lately (lately is in this past week), it's been crashing 3-4 times a day. Then, a few days ago, I was on it and it crashed again, this time, it wouldn't turn on -- my brother was (and probably still is) under the impression that I bricked it -- I would still be thinking the same but seeing as the phone turns on whilst being plugged in I'm wondering if the battery is shot, the hardware is shot, they're both shot or something more undesirable is happening.
I'm not blaming the app for this, however, the frequent crashing did start to happen more violently after I installed and used "Google Camera" for no less than 5 minutes -- at which time, I uninstalled the app and went to the Default Camera App, only for it to also crash the phone, thereafter, the phone just started to crash no matter what I did.
The phone also chooses when to shut itself off; sometimes if I unplug it, it'll turn off immediately, other times I've noticed it'll actually stay on for awhile (the longest its gone so far is 5-10 minutes). I was playing around with wallpaper when I decided to see if I might be able to use the camera, to my dissatisfaction, the phone crashed -- I noticed this when I looked back at the screen.
So now, for the last 18 (give or take 4 hrs) hours, I've been using the phone 'normally' whilst plugged in.

JJBerryere said:
Yeah... I'm not great at titling... Anywho...
I've come across a problem, of which I'll attempt to go through everything I did that leads to the point, which is; my Nexus 4 doesn't turn on without being plugged into, either the wall or any PC.
So my phone crashes, solemnly (probably because I have Cyanogen on my phone), but lately (lately is in this past week), it's been crashing 3-4 times a day. Then, a few days ago, I was on it and it crashed again, this time, it wouldn't turn on -- my brother was (and probably still is) under the impression that I bricked it -- I would still be thinking the same but seeing as the phone turns on whilst being plugged in I'm wondering if the battery is shot, the hardware is shot, they're both shot or something more undesirable is happening.
I'm not blaming the app for this, however, the frequent crashing did start to happen more violently after I installed and used "Google Camera" for no less than 5 minutes -- at which time, I uninstalled the app and went to the Default Camera App, only for it to also crash the phone, thereafter, the phone just started to crash no matter what I did.
The phone also chooses when to shut itself off; sometimes if I unplug it, it'll turn off immediately, other times I've noticed it'll actually stay on for awhile (the longest its gone so far is 5-10 minutes). I was playing around with wallpaper when I decided to see if I might be able to use the camera, to my dissatisfaction, the phone crashed -- I noticed this when I looked back at the screen.
So now, for the last 18 (give or take 4 hrs) hours, I've been using the phone 'normally' whilst plugged in.
Click to expand...
Click to collapse
Have you tried to make a clean install and not restoring anything to check if that helps? If that doesn't help I would try flashing a factory image.

theminikiller said:
Have you tried to make a clean install and not restoring anything to check if that helps? If that doesn't help I would try flashing a factory image.
Click to expand...
Click to collapse
Yes I have tried to make a clean install, with a different OS as well, CyanogenMOD's take on Lollipop 5.1. The phone still turns itself off though.
What is "Flashing a factory image" mean?

JJBerryere said:
Yes I have tried to make a clean install, with a different OS as well, CyanogenMOD's take on Lollipop 5.1. The phone still turns itself off though.
What is "Flashing a factory image" mean?
Click to expand...
Click to collapse
You download the full stock ROM from Google, and use fastboot to flash it. Here is a guide on how to do it. http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

JJBerryere said:
Yes I have tried to make a clean install, with a different OS as well, CyanogenMOD's take on Lollipop 5.1. The phone still turns itself off though.
What is "Flashing a factory image" mean?
Click to expand...
Click to collapse
If you want a 100% clean flash, just download the factory image and flash it by executing the flash-all.bat (you are using windows I guess) script. It might be necessary to reboot into the bootloader first.
cheers

greg17477 said:
If you want a 100% clean flash, just download the factory image and flash it by executing the flash-all.bat (you are using windows I guess) script. It might be necessary to reboot into the bootloader first.
cheers
Click to expand...
Click to collapse
Tried this, didn't work.
My phone has basically been flashing red for awhile now and it doesn't turn on at all.

Your battery is dead, same happened with me 3 months ago.....
I took it to service centre, they just changed the battery (ask them specifically otherwise they will wipe data too, internal included)
Overall it cost me INR 1200 i.e approx $20

anupampb said:
Your battery is dead, same happened with me 3 months ago.....
I took it to service centre, they just changed the battery (ask them specifically otherwise they will wipe data too, internal included)
Overall it cost me INR 1200 i.e approx $20
Click to expand...
Click to collapse
Yeah, so I figured.
My father and I just replaced the battery with a Tablet's battery. Although probably not seen as proper. If it works, why fight about it? Haha.
Thanks.

JJBerryere said:
Yeah, so I figured.
My father and I just replaced the battery with a Tablet's battery. Although probably not seen as proper. If it works, why fight about it? Haha.
Thanks.
Click to expand...
Click to collapse
Your farther does not really worry enough for your health
https://en.wikipedia.org/wiki/Lithium-ion_battery#Safety