My device is rooted, and the typical "your device is unlocked and cannot be trusted" screen on my phone takes at least 35-40 seconds to go away before proceeding to boot into the device, even though it says that it'll continue booting in five seconds. What's up with that? Is anyone else experiencing this, or is your boot time actually around what it actually says?
I've decided to time just how long it takes for the bootloader unlocked warning to go away vs. the boot animation finishing.
Bootloader Unlocked Screen - 39.6 seconds
Motorola Boot Animation - 20.2 seconds
Total Time - 50.8 seconds
Nearly a minute for the device to boot! And just to confirm that I'm not crazy, here's times from an G5 Plus that isn't rooted. I used this video.
Motorola Unrooted Screen - 24.8 seconds
Motorola Boot Animation - 13.7 seconds
Total Time - 38.5 seconds
The time difference of the stock vs. rooted screen is 14.8 seconds! I understand that a device that is rooted has a lot more data on it that needs to be loaded, but this is the screen that shows before a lot more stuff appears. So, I backed up my device's data and reset it, leaving the bootloader unlocked. The time I recorded?
Bootloader Unlocked Screen - 38.6 seconds
Essentially no time difference. On a device that was just factory reset; nothing but an unlocked bootloader.
I may be missing out some important details, but I really am at a loss of what would explain this other than Motorola giving those with modified devices slower boot times.
Is 14 seconds once in a while really bothering you?
Karlinski said:
Is 14 seconds once in a while really bothering you?
Click to expand...
Click to collapse
It's not that it's bothersome, but rather strange that simply having an unlocked bootloader with nothing else modified adds that amount of time.
Count Your Blessings...
sticktornado said:
It's not that it's bothersome, but rather strange.
Click to expand...
Click to collapse
I also own a ZTE Zmax Pro..
It's Bigger
It's Faster
It has 1080p Screen That is just as good if not better..
It does not heat up No Matter What you are doing...
And the Battery last a day and a half.. with 7 hrs SOT with Moderate to Heavy usage.
And I only paid $39.99 for it Brand New on a promo sale..(Regularly $99.99)
But you know what it does not have? It does not even have access to the bootloader.. ZTE removed it entirely.. It's a TREMENDOUS value device.
But without Root Brother, you have nothing but another phone.. in a sea of phones..
So.. when you are waiting those 14 seconds.. think about the fact that you have a device with such GREAT Community Support.. and a device that YOU can control for the Money you spent.. unlike the Zmax Pro.. and that should outweigh those 14 seconds Every Time..
Related
Do you all have unusually long boot times on the mt4g?
From power button push to lock screen appearing my phone takes just under two minutes!
My wife's mt4g takes about 20 seconds less to start up, but she does have fewer apps and services. Can you post your boot times or recommend ways to reduce the boot time? I already have fast boot enabled. I'm just shocked that the boot time its so long. I'm pretty sure it's normal though...
do you have fastboot selected in settings?
darenihill said:
do you have fastboot selected in settings?
Click to expand...
Click to collapse
Yep. See post above. What's a typical boot time from power button press to lock screen?
I don't use fastboot but I can tell you that the boot time on the mt4g is long compared to other phones I've seen. Both mine and my wife's take around 1 1/2-2 mins. I think it's the mysense ui that does it.
Swyped on my rooted MyTouch4G
XfooYen said:
I don't use fastboot but I can tell you that the boot time on the mt4g is long compared to other phones I've seen. Both mine and my wife's take around 1 1/2-2 mins. I think it's the mysense ui that does it.
Swyped on my rooted MyTouch4G
Click to expand...
Click to collapse
Ya i believe you have to be using sense. From what i understand when in this mode the phone never really powers down, just goes into a hibernation state like laptops and therefore can "reboot" very quickly
When I had the stock rom boot time was quick, way faster than when I had my g2
Can someone post up their boot time(s) on a non-rooted stock sense mt4g?
My G2 is running the stock ROM, not rooted. I rooted my G1 and ran every ROM I could get my hands on, but with free WiFi tethering and a clean OS, I find no reason to root my G2... yet.
Lately, I've been encountering a really slow boot time - almost 2 minutes from power button to OS up and running. I do have a lot of widgets, but I don't have an excessive amount of apps. Do the widgets slow the bootup? They're not even ready when I unlock the screen (after the network becomes available), and I've already waited 2 minutes.
My wife's G2 takes about 20-30 seconds to boot up. What gives?
It's the widgets. The more you have, the longer the boot time will be in order for everything to load up!
Thanks! I got wise and rooted/installed CM7. Bout damn time. WAY faster than before.
Yeah I noticed the same thing when I tried out CM6 (which I'm using now).
Before it was taking more than a minute, now it's up pretty quick.
Anyone else think the xperia play has the longest ever bootup? It can take up to 5 minutes to load on mine!
how long does your phone take to boot?
Couple of minutes maybe, rooted & some bloatware removed.
My boot up time depends, maybe on the plays mood?, it's between 2-5 min? Never really the same boot up time
Really liked htc fastboot option, took less than 30 secs. Missing that one...
Regards Dousan...
mine takes exactly 4 min.... i never seen an android phone boot so slow....
Little over a minute after removing lots of bloatware.
Its so long that I want to root it just to remove the bloat.
mines is really random, sometimes it takes a minute, sometimes upto 2
when i gotit it took up to 5 lol
ive removed most apps btw
50 seconds. Used this thread to help identify a lot of bloatware:
http://forum.xda-developers.com/showthread.php?t=1046699
the boot time will depend on what you were doing before you switched your device off, for example if you had just installed lots of apps, the dalvik vm will have to rebuilld the DC on bootup so it will take longer ect
The other day I was using my att s4 active and it went off on me. I put it in recovery mode and it just keeps going off. I don't know for sure but I vaguely recall installing a custom rom a long time ago. I've replaced the battery and charged it so I'm sure that's not an issue. Occasionally it will come up with an ! saying the software is not for the phone, take it to att. Other times it will boot up and will stay on for like 5 seconds, just enough to pass the lock screen.
Sometimes it sticks on secovery boouing (weird) and yet other times it won't do anything. I'd really like to get my pictures off of the phone.
I would like to share my experience on how I saved my Nexus 6P which was bootlooping with bootloader locked and inaccessible recovery mode.
The problem started when I had updated my phone with latest OTA update 8.1.0 (Oreo). While I was browsing fb after the update, suddenly the phone froze and restarted. And ever since that moment it begun to bootloop. I tried to access recovery from Fastboot so that I can clear the cache which would most of the time resolve the bootloop issue however this time around I was unable to go to the recovery mode too. I wouldn't been able to flash from fastboot since bootloader was locked. There is no way to get around this unless I would be able to load the OS and go into Developer option to turn on "Enable OEM unlock" in the settings.
Since I would not be able to flash the stock ROM or get into recovery mode, I contacted Google support for help. They directed me to Huawei Support. Huawei told that since my phone is out of 1 year warranty they would not be able to service this phone and would cost me nearly $400 for getting me a replacement. Spending $400 for 20 months old phone was absurd.
I started to explore online what are the options available given the tight situation that I was into. I came across few forums discussing about using a heat gun above the finger print sensor to throttle the CPU which may stop the phone from bootlooping. I used a hair dryer to heat the phone while the phone is continuously bootlooping. I would heat for about 7 - 10 mins to an extent where I would not be able to hold the phone anymore. After nearly 7 to 8 failed attempts spread over 2 weeks, the magic worked.
The last attempt was slightly different. Here is what I did -
1. Battery was fully drained
2. I started to charge the phone while I kept it outside my window for about 20 mins. Temp outside was around 15 degrees Fahrenheit. (Did this step since I read somewhere that keeping the phone in refrigerator and restarting would resolve bootloop issue) However it continued to bootloop.
3. While the phone continued to bootloop, I allowed the phone to charge overnight.
4. Next day I saw that the phone did not restart like how it used to. It was stuck at GOOGLE and would not restart.
5. I disconnected from the charger. Went to fastboot and switched off the phone.
6. I started to heat the phone using hair dryer with the phone switched off for about 10 mins. I held it was a cloth since it gets hot pretty fast.
7. Paused for a sec, turned on the phone (it was bootlooping) and continued to heat the phone for another 5 mins. (by then I gave up)
8. Stopped heating. I left the phone and went out to work on something else. After half an hour, when i returned I saw that the phone was completely switched off and was not bootlooping. I got excited since I know that the phone was fully charged overnight and there is no way that the phone would have died due to battery drain.
9. I immediately turned on by holding on to the VOL down button. I selected recovery from fastboot. To my surprise for the first time in 2 weeks I was able to go into recovery mode. I cleared cache and restarted the phone in Normal mode.
10. Phone booted properly and loaded the OS.
11. First thing I did was to go into developer options and turn on "ENABLE OEM UNLOCK" option. (By now I knew how important it was to have this enabled. THIS COULD SAVE YOUR $549 PHONE!!)
12. Took a backup of all the files and unlocked the bootloader.
I downgraded the OS to 7.1.2 (Aug release) which I felt was a stable one for Nexus 6P. I also did a h/w check and all the tests passed CPU / Memory is fine. I am still not sure what could have caused the bootloop but the fact that it happened after the Oreo OTA would make me to stay away from upgrading the Android version beyond 7.1.2.
Working but not enough
Hey, first thank you so much for sharing your experience. It gave a guide to follow step by step which I really appreciate. I have tried the heating tecnique and has partially worked 3 times, google logo turns into the other google logo but at a really low speed, then it switches off my phone. I tried to start on Safety Mode as you said but it just says "Not command" nex to an android icon. Any aditional advice?. Thank you
Speed1908 said:
I would like to share my experience on how I saved my Nexus 6P which was bootlooping with bootloader locked and inaccessible recovery mode.
The problem started when I had updated my phone with latest OTA update 8.1.0 (Oreo). While I was browsing fb after the update, suddenly the phone froze and restarted. And ever since that moment it begun to bootloop. I tried to access recovery from Fastboot so that I can clear the cache which would most of the time resolve the bootloop issue however this time around I was unable to go to the recovery mode too. I wouldn't been able to flash from fastboot since bootloader was locked. There is no way to get around this unless I would be able to load the OS and go into Developer option to turn on "Enable OEM unlock" in the settings.
Since I would not be able to flash the stock ROM or get into recovery mode, I contacted Google support for help. They directed me to Huawei Support. Huawei told that since my phone is out of 1 year warranty they would not be able to service this phone and would cost me nearly $400 for getting me a replacement. Spending $400 for 20 months old phone was absurd.
I started to explore online what are the options available given the tight situation that I was into. I came across few forums discussing about using a heat gun above the finger print sensor to throttle the CPU which may stop the phone from bootlooping. I used a hair dryer to heat the phone while the phone is continuously bootlooping. I would heat for about 7 - 10 mins to an extent where I would not be able to hold the phone anymore. After nearly 7 to 8 failed attempts spread over 2 weeks, the magic worked.
The last attempt was slightly different. Here is what I did -
1. Battery was fully drained
2. I started to charge the phone while I kept it outside my window for about 20 mins. Temp outside was around 15 degrees Fahrenheit. (Did this step since I read somewhere that keeping the phone in refrigerator and restarting would resolve bootloop issue) However it continued to bootloop.
3. While the phone continued to bootloop, I allowed the phone to charge overnight.
4. Next day I saw that the phone did not restart like how it used to. It was stuck at GOOGLE and would not restart.
5. I disconnected from the charger. Went to fastboot and switched off the phone.
6. I started to heat the phone using hair dryer with the phone switched off for about 10 mins. I held it was a cloth since it gets hot pretty fast.
7. Paused for a sec, turned on the phone (it was bootlooping) and continued to heat the phone for another 5 mins. (by then I gave up)
8. Stopped heating. I left the phone and went out to work on something else. After half an hour, when i returned I saw that the phone was completely switched off and was not bootlooping. I got excited since I know that the phone was fully charged overnight and there is no way that the phone would have died due to battery drain.
9. I immediately turned on by holding on to the VOL down button. I selected recovery from fastboot. To my surprise for the first time in 2 weeks I was able to go into recovery mode. I cleared cache and restarted the phone in Normal mode.
10. Phone booted properly and loaded the OS.
11. First thing I did was to go into developer options and turn on "ENABLE OEM UNLOCK" option. (By now I knew how important it was to have this enabled. THIS COULD SAVE YOUR $549 PHONE!!)
12. Took a backup of all the files and unlocked the bootloader.
I downgraded the OS to 7.1.2 (Aug release) which I felt was a stable one for Nexus 6P. I also did a h/w check and all the tests passed CPU / Memory is fine. I am still not sure what could have caused the bootloop but the fact that it happened after the Oreo OTA would make me to stay away from upgrading the Android version beyond 7.1.2.
Click to expand...
Click to collapse
---------- Post added at 05:18 PM ---------- Previous post was at 05:09 PM ----------
I just waited like 5 or 10 minutes and my phone started in system. Just enough to activate stuff in developers options!
arkanthos said:
Hey, first thank you so much for sharing your experience. It gave a guide to follow step by step which I really appreciate. I have tried the heating tecnique and has partially worked 3 times, google logo turns into the other google logo but at a really low speed, then it switches off my phone. I tried to start on Safety Mode as you said but it just says "Not command" nex to an android icon. Any aditional advice?. Thank you
Click to expand...
Click to collapse
I just had this happen to me. Friday evening, I noticed an update and I usually read reviews prior to downloading, but I clicked anyways. All seemed fine until Saturday night, was in fb, watching a cooking video and clicked on a link for the recipe when my phone went blank and to the Google screen. tried for 2 days to reboot, get into boot-loader, recovery, anything!
Luckily, I have 9 more days on my Square Trade warranty. They required me to take to a fix-it store (all they could try was a battery pull, which was unsuccessful). Square Trade sourced me a replacement, so it came in last night and I am downloading all my apps and trying to get back "to normal".
I did do an Android update, at the urging of my son, since he has the same phone. Now I see one more, that is a small update. Worried if I should download or not?
I just found this forum and haven't yet gone searching for help on it.
This info is good to know.
Thanks and take care!
Thank you save my life again i have no hair dryer and place it on my rick cooking about 10 mins after that it boot slow gooe animated and i format factory and clear cach first try and succeeded