Database Users

My phone booted completely with sense loaded in less than 2 seconds this morning

It was the weirdest thing ever. I literally mean 2 seconds.
The phone was COMPLETELY off. It showed the short sprint boot animation at lightning speed and went immediately to my lock screen. I proceeded to enter my code to find sense already loaded and most of my background processes/notifications loaded or loading.
I had to share this with the community. I don't know how it happened.
I'm running stock, rooted gingerbread without a custom kernel.
When I turned off my phone, I did it by holding the power button and shutting it down. Normally I just pull the battery.
Also, it normally takes about 3-4 mins for my phone to boot up just to the lockscreen (it stays at the "4G" animation frame).
Has anyone else had this lightning fast boot?!

You probably have fastboot on lol. You'll find it in settings, then applications.
Sent from my PC36100

Dirk beat me

Yeah, I see it is checked.
I didn't even know fastboot existed. Is this a new gingerbread feature?
Why wouldn't this ALWAYS be on by default?
And I wonder why it hasn't done it before?
I've been on gingerbread for about a week now, and I haven't checked that box manually...hmmm

kyelerner said:
Yeah, I see it is checked.
I didn't even know fastboot existed. Is this a new gingerbread feature?
Why wouldn't this ALWAYS be on by default?
And I wonder why it hasn't done it before?
I've been on gingerbread for about a week now, and I haven't checked that box manually...hmmm
Click to expand...
Click to collapse
Yes its a GB feature. I don't use it as it doesn't play nice with all apps. I'd rather do a normal reboot.
Sent from my PC36100

Yeah your phone wasn't completely off. It sort of hibernates but still keeps things in memory. Turn it off and pull the battery. It won't boot up as fast

I really wish they named it something else, like "QuickBoot" or whatnot. Now it just creates confusion when talking to users about fastboot (what you can use while in the bootloader).
Also, this feature seems to make it harder for people to reboot into recovery if they used to use power + voldn. Since the phone isn't all the way off, it won't put you into the bootloader. -- Easily worked around by turning it off, or using an app or using adb reboot recovery, of course.

sirmx said:
I really wish they named it something else, like "QuickBoot" or whatnot. Now it just creates confusion when talking to users about fastboot (what you can use while in the bootloader).
Also, this feature seems to make it harder for people to reboot into recovery if they used to use power + voldn. Since the phone isn't all the way off, it won't put you into the bootloader. -- Easily worked around by turning it off, or using an app or using adb reboot recovery, of course.
Click to expand...
Click to collapse
I couldn't agree more!! As soon as they mentioned fastboot I immediately became confused: That's an option in the bootloader......?!! hahah
This would also explain why I've had trouble sometimes entering the bootloader using the keystrokes.
And yes, I did a battery pull, and it takes the normal 3-4 mins to boot.
Thanks again for the replies guys! Really did explain a lot! I did a search and nothing came up, so hopefully this can be used as a reference!

You'll want to uncheck that, if you ever want to be able to boot into recovery

HipKat said:
You'll want to uncheck that, if you ever want to be able to boot into recovery
Click to expand...
Click to collapse
or use quick boot from the market.

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.

Major software issues with stock Nexus 7 FLO and how to deal with them

It seems that there are some major issues with the new Nexus. This is unrooted, with locked bootloader.
People are reporting not being able to turn theirs on, or having random reboots.
My first boot never got past the Nexus X, and I had to hold the power button to restart.
Then I have had several times where the screen wouldn't come back on after sleep. Again, holding the power button down to restart worked fine.
Then I had gcore and gapps quit unexpectedly, followed by a reboot. I had just rebooted, and only opened one app: Evernote.
So I used the factory wipe option in the settings. Within seconds of completing and booting up the same processes quit unexpectedly.
I tried to reboot into recovery (by holding volume down and power) and got "no command". I tried 'adb reboot recovery' and got the same.
As far as I can tell, the factory ROM is not available for download at https://developers.google.com/android/nexus/images yet.
I obviously don't want to risk unlocking or installing anything custom if there's something wrong with the device.
I will probably have to return it to Amazon.
I haven't found much in the way of information out there, just a few complaints. If there are any well developed threads about how to deal with these issues, please let me know.

I've had a few apps quit on me and one time at the very first boot after the ROM update I had to force restart BUT I hardly consider these as "Major Issues".

There are always bad ones. Shipping, heat, cold, lightning, the chupacabra, darth vader, moisture, the blob, gremlins, or the Jaberwoky could have caused these "major" issues you have,
You're thread is bunk. Return it....

In stock recovery (when it says no command) have you tried pressing Vol+ to get the recovery menu.

I had the launcher force close on my Nexus 4 a few times shortly after I updated but after a few restarts it went away. Other than that I haven't had any issues with my Nexus 7.
Sent from my Nexus 7 using xda app-developers app

idheitmann said:
It seems that there are some major issues with the new Nexus. This is unrooted, with locked bootloader.
People are reporting not being able to turn theirs on, or having random reboots.
My first boot never got past the Nexus X, and I had to hold the power button to restart.
Then I have had several times where the screen wouldn't come back on after sleep. Again, holding the power button down to restart worked fine.
Then I had gcore and gapps quit unexpectedly, followed by a reboot. I had just rebooted, and only opened one app: Evernote.
So I used the factory wipe option in the settings. Within seconds of completing and booting up the same processes quit unexpectedly.
I tried to reboot into recovery (by holding volume down and power) and got "no command". I tried 'adb reboot recovery' and got the same.
As far as I can tell, the factory ROM is not available for download at https://developers.google.com/android/nexus/images yet.
I obviously don't want to risk unlocking or installing anything custom if there's something wrong with the device.
I will probably have to return it to Amazon.
I haven't found much in the way of information out there, just a few complaints. If there are any well developed threads about how to deal with these issues, please let me know.
Click to expand...
Click to collapse
Had I had these issues off the bat I would have returned the device for exchange or refund (if non where available for exchange). Definitely would not have rooted if I was experiencing issues, right back to the store I would of been.
Mine works very well and I LOVE it!

Thanks for all the encouraging words guys
I'm pretty sure the problem originated when the first boot failed and I forced reboot. The OS update must not have installed cleanly.
Anyway I just installed CleanROM and everything is peachy now. I guess whether shipping improperly flashed devices is a major issue or not is a matter of opinion, but I would expect better quality control from Google. I hope it's not too wide spread, and that anyone suffering this issue has the know how and confidence to install a stable ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta

Here's a major issue. Do NOT install widget locker, and then turn on talkback! You can no longer unlock the tablet!
I thought it was a goner, and that I was going to have to return it, but I googled and found out about safe mode, and then once I got that running, found another link on how to turn off talkback.
My God, is that the most annoying feature you could ever think of!
I was reading the google library information, and it said you had to turn an assessibility feature on in order for google books to readbooks out loud.
I'm back to square one with that now... anyone know how to accomplish this?

No issues here. I absolutely love the device!!
Sent from my Nexus 7 using Tapatalk 2

I have had the launcher die a few times, but that's the only issue I've noticed on mine (and since it comes back, it isn't that big a deal).

mmc_read failure Note 4 n910w8 Rogers!!

Here is the story,
I flashed Marshmallow on my note 4 n910w8 via odin (I had 5.1.1). After it was done I noticed that the phone got laggy and warm. It would sometimes not boot/restart or it would shut down after it freezes for sometime. I would get the download page with mmc_read failure in red, I would pull out the battery and try again.
What I did:
*Unrooted the phone through SuperSu and flashed Twrp throughout (because it gave other errors and I had to do it again and again after each attempt)
*I tried flashing through twrp but I got the "no md5" error
*Flashed the stock ROM 6.0.1 with PIT since it gave the PIT error on odin
*Wiped cache/data/factory reset multiple times.
*I used both Kies and Smartswitch and was not successful (either read or write failure)
*Flashed the stock 4.4.1 (the original, It could not boot up once) so I returned to the stock 6.0.1
*The phone boots up 3 out 5 times and I was able to watch a full movie on Netflix and browse the web and google maps. But as soon as I locked it, It shut off and did not power up (until i took out the battery and let it cool down).
Where I went:
*A Samsung repair agent here in Montreal said that most of the time it is the Mob and that it would cost 300-400$ CAD to replace
*I went to other repair shops, a few hinted that it might just a matter of reprogramming the Mob and that it involved a risk of bricking the phone for good.
N.B: It is not under warranty and I'm not on contract, It is my own phone.
My question(s): Is there something else I could try? Is there someone who fixed the issued (Assuming it is not hardware) maybe and unbrick fix or something? And also, it there anyway to thoroughly wipe out the old installations so I could start anew?
Also I consider myself pretty knowledgeable. Or I at least learn quick. Do not hesitate to suggest something coarse for me to try. Worse comes to worse, Ill sell it on eBay for part, since it it in mint condition.

It's definitely a hardware issue, trust me.
But all the problems can be bypassed by rooting your device and installing Wake Lock app from the playstore and activate PARTIAL_WAKE_LOCK, enable the notification and start on boot. This will fix all the lag and the crashes.
This will not, however, fix the boot problems. So if your device ever runs out of battery or turns off, booting it is gonna be a hassle still as before. If you ever get stuck trying to boot it properly to homescreen however, I discovered a foolproof method for that with 10/10 success rate.
I know it might sound weird, but I'm seriously not trolling you. Take out the battery and place the phone & the battery in your fridge for at least 5 minutes until your device gets cold. Put the battery back in and boot into 'download mode'. You'll notice that it'll goes into download mode perfectly. Take out the battery again and just boot normally. You'll be back into homescreen in no time. This is how I know it's a hardware problem, lol.
With these alternative fixes, I'm hoping that I can keep my phone alive for at least another 2 years. Better than forking out another $500~ for a new device imho.

The Sponge said:
It's definitely a hardware issue, trust me.
But all the problems can be bypassed by rooting your device and installing Wake Lock app from the playstore and activate PARTIAL_WAKE_LOCK, enable the notification and start on boot. This will fix all the lag and the crashes.
This will not, however, fix the boot problems. So if your device ever runs out of battery or turns off, booting it is gonna be a hassle still as before. If you ever get stuck trying to boot it properly to homescreen however, I discovered a foolproof method for that with 10/10 success rate.
I know it might sound weird, but I'm seriously not trolling you. Take out the battery and place the phone & the battery in your fridge for at least 5 minutes until your device gets cold. Put the battery back in and boot into 'download mode'. You'll notice that it'll goes into download mode perfectly. Take out the battery again and just boot normally. You'll be back into homescreen in no time. This is how I know it's a hardware problem, lol.
With these alternative fixes, I'm hoping that I can keep my phone alive for at least another 2 years. Better than forking out another $500~ for a new device imho.
Click to expand...
Click to collapse
Thank you very much for your reply, I take it you have the same problem? I will try Wake Lock. And also I'm way ahead of you in the freezing game. Leave for 10mins in the freezer and you can basically flash anything. Also, do you a custom ROM would help?

Charge Screen missing

When the phone is off and you plug in the usb cable to charge, before it used to go to the coffee mug screen on. Now it just stays on the Essentials logo screen, I can manually boot it by holding the power button down a few seconds, or boot it normally with the USB cable out. I'm not sure if this is because of the Pie update and Essentials broke it by accident, or it's due to Magisk/unlocked bootloader, or bad RTS flashing. Other than that, the phone is fine. Is anyone else experiencing this?

I am able to replicate this on my phone running the latest version of Pie. I first discovered it when I plugged my phone into the stock charged and attempted to power it off. Instead of powering off and showing the charge screen, the phone acted like it was going through a reboot process. It would display the unlocked bootloader warning and initial splash screen and it gets stuck on this screen. It requires me to power cycle the phone by holding the power button for several seconds. Prior to updating the phone to Pie I know I was able to power it off while the charger was connected without experiencing this behavior. I bought two of these phones so I will try it out on the other one when my girlfriend gets home tonight.

This is the same thing i'm experiencing so at least that should rule out bad flashing. Were you able to check the other phone to see if it also happens on it and is it stock? If it's stock and does the same thing then i'll send an email to essentials to ask if they are planning to fix it.

winggndm1 said:
This is the same thing i'm experiencing so at least that should rule out bad flashing. Were you able to check the other phone to see if it also happens on it and is it stock? If it's stock and does the same thing then i'll send an email to essentials to ask if they are planning to fix it.
Click to expand...
Click to collapse
I did test the other phone and it behaved the same as mine. I tried using both of our adapters as well as my S8 adapter with the same results. I tried to power it off while it was plugged in via recovery but it begins to reboot then gets stuck on the "Powered by Android" screen. I'd appreciate you letting me know their response to the issue.

So restoring the stock boot image fixes the issue. I reflash twrp, the stock boot image and installed the zip, and back to the same behavior. So magisk must be modifying the image incorrectly and breaking it. I'll report this on the magisk thread.

https://forum.xda-developers.com/showpost.php?p=77402354&postcount=6560
it seems that using 16.6 works. Something broke in 16.7 and affects also Pixel users.

winggndm1 said:
When the phone is off and you plug in the usb cable to charge, before it used to go to the coffee mug screen on. Now it just stays on the Essentials logo screen, I can manually boot it by holding the power button down a few seconds, or boot it normally with the USB cable out. I'm not sure if this is because of the Pie update and Essentials broke it by accident, or it's due to Magisk/unlocked bootloader, or bad RTS flashing. Other than that, the phone is fine. Is anyone else experiencing this?
Click to expand...
Click to collapse
I'm experiencing this too. Any updates?

I just downgraded to Magisk 16.6 and the charging icon is back. I can confirm that it is working. Thank you for the headsup!!

Same exact issue here.
Now on Magisk 17.1, Pie Oct, Stock Kernel, permanent TWRP.
Was happening on 16.7 as well prior to permanent TWRP.
I never used Magisk below 16.7 so I can't comment on that.
Also noticed that the phone gets pretty hot when charging while off, with the "stuck" Essential logo screen.
Anyone else's phone get pretty hot while charging "off"?

ultrasuper said:
Same exact issue here.
Now on Magisk 17.1, Pie Oct, Stock Kernel, permanent TWRP.
Was happening on 16.7 as well prior to permanent TWRP.
I never used Magisk below 16.7 so I can't comment on that.
Also noticed that the phone gets pretty hot when charging while off, with the "stuck" Essential logo screen.
Anyone else's phone get pretty hot while charging "off"?
Click to expand...
Click to collapse
Update magisk to the canary build

rignfool said:
Update magisk to the canary build
Click to expand...
Click to collapse
I'd rather wait for the stable release to come in.
This issue seems to be only a cosmetic issue (I hope).

Maybe it's real, maybe it's coincidence, but my Pixel XL was having the same issue. Once night, I turned of the phone, the issue occurred, and the next morning my screen would not turn on. The LED at the top would light, but no screen. I took it to be repaired per Google, and was told they tried 3 screens and none would work. They believed it was something with the motherboard. Coincidence or fact? I do not know, you be the judge.