Slow boot up - Nexus 6 Q&A, Help & Troubleshooting

Anybody ever figure out why it takes so long for the nexus 6 to boot up after turning on? Is there a way to fix that (preferably not requiring root)?

toledodj said:
Anybody ever figure out why it takes so long for the nexus 6 to boot up after turning on? Is there a way to fix that (preferably not requiring root)?
Click to expand...
Click to collapse
Are you using an android 5.1 rom and kernel? Google supposedly sped up that process and I can definitely tell it doesn't take that long compared to what it did on android 5.0.1.
Sent from my Nexus 6 using XDA Free mobile app

Just did a test and mine booted in about 40 seconds. Doesn't feel long at all. I'm unencrypted though, that might be a factor...

Yeah, I'm running completely stock 5.1. Encryption is still enabled and unchangeable

I never thought it was a long boot up?! Seems about normal for me, using Euphoria rom and Leankernel also decrypted.

toledodj said:
Yeah, I'm running completely stock 5.1. Encryption is still enabled and unchangeable
Click to expand...
Click to collapse
Encryption is probably the reason and the solution would be to flash a modified boot image and then wipe your phone. No root needed.
How long does your boot up take?

It takes about a minute.

Related

Phone Encryption FYI

4.4 KitKat still has the same bug as previous releases as far as encrypting the phone goes. I had to attempt the process 4 times before the phone would actually encrypt. The first 3 times the Green Android popped up, but the phone didn't reboot to the "Encrypting Phone..." progress screen, it just went back to the lock screen. 4th time was a charm, so keep trying if it doesn't work for you.
Ronaldo Forenucci said:
4.4 KitKat still has the same bug as previous releases as far as encrypting the phone goes. I had to attempt the process 4 times before the phone would actually encrypt. The first 3 times the Green Android popped up, but the phone didn't reboot to the "Encrypting Phone..." progress screen, it just went back to the lock screen. 4th time was a charm, so keep trying if it doesn't work for you.
Click to expand...
Click to collapse
You using a custom recovery or stock?
Mine encrypted on the first try ...
Encrypting naturally makes the phone a tad bit slow though no? And to decrypt you have to do factory reset
Sent from my Nexus 5 using xda app-developers app
secondclaw said:
Mine encrypted on the first try ...
Click to expand...
Click to collapse
Stock recovery?
Sent from my Nexus 5 using Tapatalk
uh60james said:
Stock recovery?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, rooted only, but no other changes.
I've never had a problem encrypting with any recovery (CWM, TWRP, or stock), probably because it never boots to recovery while encrypting. It's probably a ROM issue.
Hey guys,
did you notice any significant performance impact after encrypting your N5?
How does an (stock) update work on encrypted N5? Do I have to wipe the phone prior to any update?
Just so you guys know there is a bug with kitkat encryption that will wipe your entire phone. Make backups of all the data you're keeping on your phone if you're going to encrypt. There's been a few users that have reported loosing everything due to encryption wiping out their phones. Just a friendly warning to whoever wants to encrypt.
Encryption does not slow down the performance. Only boots up slightly slower. Once you go through the password or pin, everything is decrypted until you lock your phone again.
I remember once you encrypt though...can't decrypt or need to reinstall stock.
Sent from my SM-T320 using xda app-developers app
my n5 was very picky about which cable and charger I was using before it would start the encryption process, with a N7 and a asus T100, it was hard to figure out which charger goes with which device.
Haven't noticed any particular slowdown since encrypting, except at boot.
The only thing I hated was not being able to use pattern unlock, using a PIN sucks. I worked around that by making a twrp backup right before the encryption process, change the security to PIN so encryption will work, then once it's done, boot into TWRP (which makes you enter the PIN to read inside the encrypted container), then restore the backup without wiping. So now I have a good length pin at bootup or entering twrp, pattern unlock for daily use. Maybe trading a little bit of security for convenience, but entering a 10+ character pin multiple times per day just isn't very usable.
I think it's the battery. The os shows another percentage than the recovery calculates. After some additional minutes of charging i hadn't that problem anymore. Thats just my opinion
I know that it is not possible to decrypt the data and that a factory reset is necessary to remove encryption.
I am just wondering if I can still update my system if I encrypt my phone?
What exactly is encrypted? Only /data?
Sent from my Nexus 5 using xda app-developers app
Encryption does not affect the OTA update or any kind of updates that push out offically. Phone itself decrypts once you go through personal lock screen. Since you can only update during unlocked stage, you won't have problem updating. It does encrypt everything except the media files such as videos, music's and etc. Correct me if I'm wrong though...
Sent from my SM-T320 using xda app-developers app
How long do you use the encryption now?
Do OTA updates still work?
Does adb work from TWRP recovery?
Sent from my Nexus 5 using XDA Free mobile app
FuMMoD said:
Just so you guys know there is a bug with kitkat encryption that will wipe your entire phone. Make backups of all the data you're keeping on your phone if you're going to encrypt. There's been a few users that have reported loosing everything due to encryption wiping out their phones. Just a friendly warning to whoever wants to encrypt.
Click to expand...
Click to collapse
Wish I had seen this!
[email protected] POS wiped EVERYTHING on my phone when I tried to encrypt.....EVERYTHING.
Was on latest TWRP, KangaKat and ElementalX
FAck U GOOGLE!
Globespy said:
Wish I had seen this!
[email protected] POS wiped EVERYTHING on my phone when I tried to encrypt.....EVERYTHING.
Was on latest TWRP, KangaKat and ElementalX
FAck U GOOGLE!
Click to expand...
Click to collapse
Ye when your phone running custom recovery, rom and kernel doesn't behave as intended, it's obviously Google's fault...
Seriously, if you change anything software related, you lose the right to blame the manufacturer.
I've heard of random passwords being generated so the user has to factory reset. Is this true????
# 47386

[Q] First-time flasher (ha), what am I doing wrong?

I finally decided to take advantage of having a Nexus 6 and flash a factory image. I downloaded Wug's NRT and commenced to flashing. I also wanted to disable forced encryption and Wug's NRT has an option to apply this during the flashing process. It appears to go through the process but when the phone boots back up, I'm still on the same build as when I started. What am I doing wrong?
Phone - Nexus 6, bought directly from Motorola
Carrier - Verizon
Toolkit - Wug's NRT 2.0.5
Build - LMY47D
Android version - 5.1
Goal - flash LMY47Z to get to 5.1.1 and no forced encryption
NRT says it can talk to my phone in all modes, has all the files it needs, etc. I've got to be missing something; just don't know what I'm doing wrong. Thanks in advance!
Lucky Armpit said:
I finally decided to take advantage of having a Nexus 6 and flash a factory image. I downloaded Wug's NRT and commenced to flashing. I also wanted to disable forced encryption and Wug's NRT has an option to apply this during the flashing process. It appears to go through the process but when the phone boots back up, I'm still on the same build as when I started. What am I doing wrong?
Phone - Nexus 6, bought directly from Motorola
Carrier - Verizon
Toolkit - Wug's NRT 2.0.5
Build - LMY47D
Android version - 5.1
Goal - flash LMY47Z to get to 5.1.1 and no forced encryption
NRT says it can talk to my phone in all modes, has all the files it needs, etc. I've got to be missing something; just don't know what I'm doing wrong. Thanks in advance!
Click to expand...
Click to collapse
what are you doing wrong? well thats an easy one, youre a first time flasher, what are you doing using a root toolkit? did you learn anything from it? did you learn how to flash the factory image the right way? no. that's your issue. it takes less than 5 minutes to flash a factory img the right way.
if you know how to do things properly, then its alright to use a toolkit. if you have no idea jow to do things right, a toolkit wont show you how.
Does NRT tell you it was successful? Usually there are quite a lot of messages...
To get a grip on what simms22's taking about, check out the faq thread:
http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Didgeridoohan said:
Does NRT tell you it was successful? Usually there are quite a lot of messages...
To get a grip on what simms22's taking about, check out the faq thread:
http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Click to expand...
Click to collapse
right, thats what i was trying to say
Thanks for the replies, guys. I was able to figure it out. I didn't have the bootloader unlocked. I know, noob mistake. I've got LMY47Z and no encryption now. Sure hope this fixes the jank I've been experiencing, which was the whole purpose of this little experiment.
But to answer your question, I used a tool because it automates the commands and makes the experience easier. Yes, I ran into trouble at first but I figured it out. In my defense, I did read that thread before posting that recommended issuing commands rather than using a tool. I was already vested in NRT so I figured I'd see it through.
Guess the joke is on me. Not only did my efforts NOT fix the lag and stutter I'm experiencing, but the internal storage was reported at 32GB rather than 64GB. So I ran through the tool again but this time I chose the "post-flash factory reset" option which wipes the user cache. The storage is now correct, I'm on LMY47Z, and no encryption. I only installed the Google apps and still had the lag.
This is a replacement device from Motorola (first one developed battery issues). I might do that again. At least I figured out what was wrong with the flashing process. Thanks again everyone!
Lucky Armpit said:
Guess the joke is on me. Not only did my efforts NOT fix the lag and stutter I'm experiencing, but the internal storage was reported at 32GB rather than 64GB. So I ran through the tool again but this time I chose the "post-flash factory reset" option which wipes the user cache. The storage is now correct, I'm on LMY47Z, and no encryption. I only installed the Google apps and still had the lag.
This is a replacement device from Motorola (first one developed battery issues). I might do that again. At least I figured out what was wrong with the flashing process. Thanks again everyone!
Click to expand...
Click to collapse
personally, the way that google sets up the cpu makes me unhappy. it does lag a bit at times. what i always do, and have done with every nexus, is unlock the bootloader, flash a custom recovery, and supersu. then when i boot up, i adjust the cpu my own way. only then does any remnant of lag disappear. i set up my cpu to have all cores online all the time(as of 5.1, google did this as well), i disable mpdecision(hate that google sh*t), and i use ondemand/dwadline
Lucky Armpit said:
Guess the joke is on me. Not only did my efforts NOT fix the lag and stutter I'm experiencing, but the internal storage was reported at 32GB rather than 64GB. So I ran through the tool again but this time I chose the "post-flash factory reset" option which wipes the user cache. The storage is now correct, I'm on LMY47Z, and no encryption. I only installed the Google apps and still had the lag.
This is a replacement device from Motorola (first one developed battery issues). I might do that again. At least I figured out what was wrong with the flashing process. Thanks again everyone!
Click to expand...
Click to collapse
To fix your storage issue, either factory reset or fastboot format userdata.
Evolution_Tech said:
To fix your storage issue, either factory reset or fastboot format userdata.
Click to expand...
Click to collapse
or just format the cache.
simms22 said:
personally, the way that google sets up the cpu makes me unhappy. it does lag a bit at times. what i always do, and have done with every nexus, is unlock the bootloader, flash a custom recovery, and supersu. then when i boot up, i adjust the cpu my own way. only then does any remnant of lag disappear. i set up my cpu to have all cores online all the time(as of 5.1, google did this as well), i disable mpdecision(hate that google sh*t), and i use ondemand/dwadline
Click to expand...
Click to collapse
Well, the joke's on me x 2, actually. There's all around UI lag (which isn't terrible, but it seems that it's worse than my original Nexus 6), with the biggest hesitation in the Messenger app. Reading the reviews of Messenger shows that I am not alone. That was definitely a smack-my-forehead moment as I didn't realize until then is that Messenger is the worst culprit. So I probably could have saved myself a lot of frustration, but it was a good exercise to go through. I know what to do (and what not to do) next time around.
You have some excellent suggestions, thank you very much! As far as the tuning you mentioned (cores, mpdecision), is that achieved with something like Kernel Tuner from the Play Store once I'm rooted?
Evolution_Tech said:
To fix your storage issue, either factory reset or fastboot format userdata.
Click to expand...
Click to collapse
simms22 said:
or just format the cache.
Click to expand...
Click to collapse
Sorry, didn't see this until after I replied. I formatted the userdata and that fixed the storage issues. I'm back to 64GB. Thanks!
Lucky Armpit said:
Well, the joke's on me x 2, actually. There's all around UI lag (which isn't terrible, but it seems that it's worse than my original Nexus 6), with the biggest hesitation in the Messenger app. Reading the reviews of Messenger shows that I am not alone. That was definitely a smack-my-forehead moment as I didn't realize until then is that Messenger is the worst culprit. So I probably could have saved myself a lot of frustration, but it was a good exercise to go through. I know what to do (and what not to do) next time around.
You have some excellent suggestions, thank you very much! As far as the tuning you mentioned (cores, mpdecision), is that achieved with something like Kernel Tuner from the Play Store once I'm rooted?
Click to expand...
Click to collapse
yea, any kernel/cpu control app should do. some have more features, some have less, but it would only matter if the kernel included those features. good luck
simms22 said:
yea, any kernel/cpu control app should do. some have more features, some have less, but it would only matter if the kernel included those features. good luck
Click to expand...
Click to collapse
Personally, I think the elementalX kernel tuner is the best. Trickster won't keep all of my settings stick after boot (like disabled mp-decision). When I had the elementalX app that worked great...that was a couple.months ago but when I wiped my phone the app wasn't available anymore lol I think the dev had to remove it from play. That was 4 bucks out the window and no working kernel tuner app... Haha
JNMM said:
Personally, I think the elementalX kernel tuner is the best. Trickster won't keep all of my settings stick after boot (like disabled mp-decision). When I had the elementalX app that worked great...that was a couple.months ago but when I wiped my phone the app wasn't available anymore lol I think the dev had to remove it from play. That was 4 bucks out the window and no working kernel tuner app... Haha
Click to expand...
Click to collapse
i still have the old elementalx app, and im still using it as my cpu control app :angel:

Is encryption borked?

So I turned on encryption today and it took about 5-10 to complete, yet it never asked for a password. I don't use key or gesture based passwords so it's kinda weird? Why would it encrypt without a password?
I've done some googling and it seems the default pass it "default_password". But that one doesn't work. I've done the same with my N7 2013 with the same story and my Optimus G test device does exactly the same.
It this a CM or TWRP bug since all my devices run both?
Sent from my XT1092
Sounds like a CM bug. In stock android when you encrypt it will ask you to choose a password or pin.
Sent from my XT1095 using Tapatalk
I see... Guess I'll just have to wipe the devices then and start over as I was planning on doing a clean install with october releases anyway.
Anyhow, I assume running stock is my only choice then? I'll start traveling around next month so having that extra layer of security is quite important in case anything happens.
PixelVixen said:
I see... Guess I'll just have to wipe the devices then and start over as I was planning on doing a clean install with october releases anyway.
Anyhow, I assume running stock is my only choice then? I'll start traveling around next month so having that extra layer of security is quite important in case anything happens.
Click to expand...
Click to collapse
I don't know if stock is your only choice. You would have to test various roms to see if it works. I just know stock works correctly because I just use a stock rom.
Sent from my XT1095 using Tapatalk

Nexus 6 shows 4,000% battery life after root?

I got my Nexus 6P for Christmas, and I decided to root my Motorola Nexus 6 from last year. I've been waiting to do this for a few months, and was excited to finally enable several of the options I couldn't otherwise enable (such as double tap to wake and auto rotate on the lock screen and Google Now launcher). About an hour ago I got around to rooting and done so with little issues. It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. I rooted following the steps in a YouTube video by DroidModderX and the device is running perfectly fine. The device hasn't died yet, and I'll be interested to see when it will die. The battery life seems to fluctuate between 4,001% and 4,204% (Those two figures being the highest and lowest figures respectively). Rebooting does not fix this error.
I know it's not a massive problem, but I'd like to know what's causing this issue and how to resolve it. I haven't flashed any custom OS's on my phone, I'm still running stock Android 6.0.1 Marshmallow with the latest December security patches. The device is carrier unlocked also. How can I fix this?
Thanks,
Eamonn.
sonic2kk said:
It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. being the highest and lowest figures respectively). Rebooting does not fix this error.
Click to expand...
Click to collapse
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
sansnil said:
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
Click to expand...
Click to collapse
Ah, thank goodness. I'll re-root tomorrow and post back if I have any problems. Thanks!
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Why did you need root for the Google now launcher?
mikeprius said:
Why did you need root for the Google now launcher?
Click to expand...
Click to collapse
What do you mean? I can run the Google Now launcher perfectly fine. Root works fine as well. The problem isn't with the Google Now launcher but with the warning on boot. I didn't need to root, I chose to. Am I misunderstanding?
Your original post made it seem like you need root for double tap to wake and Google now launcher.
sonic2kk said:
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24269982087021512 gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: https://www.androidfilehost.com/?fid=24340319927534323 (flash this also after you flash the bootstack).
HueyT said:
(removed url) gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: (removed url) (flash this also after you flash the bootstack).
Click to expand...
Click to collapse
Worked perfect. That got rid of the corrupt message. One last question: (This is the last one, I swear! ) Are you saying that Android Pay won't work at all after rooting or that it wouldn't have worked if that screen had have appeared on boot? I hope to use the service if and when it comes to the UK.
mikeprius said:
Your original post made it seem like you need root for double tap to wake and Google now launcher.
Click to expand...
Click to collapse
Ah, sorry for the confusion my friend ?
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
orangekid said:
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
Click to expand...
Click to collapse
Haha if it wasn't a display error I might have (Though it would have only been like 3 days on the Nexus 6 )
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Dalek Caan said:
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Click to expand...
Click to collapse
Sorry, I don't remember where I got the updated files now. I do remember sticking to looking on XDA and not just searching randomly online, maybe you could try searching the forums?
is it possible to root with chainfire root files. I did a clean install of the January security update, then flashed the latest boot.img from chainfire then flashed SuperSU 2.66.zip through TWRP, but im still getting this. I received this same issue with the last patch. Im at the point where it isnt worth rooting. Any help would be appreciated.

Should I downgrade my android version?

Hey, I am currently running 6.0.1 as my android version. Just asking but would it be suggested to downgrade the android version? If yes, than too which version?
Why do you want to downgrade?
The Nexus 6 came out with the 5.0, you can't go further back, even with custom roms. Actually I've head somebody trying to build KitKat for the shamu, but I don't know if he succeeded.
Also why would you like to downgrade, anyway?
Oh as far as why: I had enough with 6.0.1 freezing/slow/crashing on me. Sometimes it even freezes to the point where I cannot turn off the screen for a few minutes at times. I also have enough with the apps freezing or does not work and Chrome sometimes freezes as well.
Why not upgrading to android 7 instead of downgrading?
php111 said:
Oh as far as why: I had enough with 6.0.1 freezing/slow/crashing on me. Sometimes it even freezes to the point where I cannot turn off the screen for a few minutes at times. I also have enough with the apps freezing or does not work and Chrome sometimes freezes as well.
Click to expand...
Click to collapse
Why don't you try upgrading instead? Android 7.0 factory image has just been released.
Oh, has it been released? Does it causes those boot loop issues on Motorola branded phones just like it does with LG branded? And could I upgrade using the Wugs tool?
php111 said:
Oh, has it been released? Does it causes those boot loop issues on Motorola branded phones just like it does with LG branded? And could I upgrade using the Wugs tool?
Click to expand...
Click to collapse
If you want to flash the factory image then go here: https://developers.google.com/android/nexus/images#shamu
You will find the factory image for 7.0 there and also the instructions on how to flash it. If you are already on stock 6.0.1, you should bee recieving an OTA update soon. But since you say you have reboots and freezes I would take a backup of what every you need onto your computer and then start of fresh from the link above. That way you won't be haunted by old bugs that might be stuck because of previous versions.
php111 said:
Oh as far as why: I had enough with 6.0.1 freezing/slow/crashing on me. Sometimes it even freezes to the point where I cannot turn off the screen for a few minutes at times. I also have enough with the apps freezing or does not work and Chrome sometimes freezes as well.
Click to expand...
Click to collapse
These freezing/slow/crashing issues look very unique to you. Why didn't you try a factory reset, then add your apps back one by one, and look for those that give you trouble. Also are you rooted, do you use xposed or anything that modifies the basic system? Because I'm runnin 6.0.1 myself, and never had the issues you do.
The instructions on the developer page to flash looks too confusing. Well, it jumps right into it when myself I never done it before.
Everybody on this site once knew nothing about Android. Your safest bet is to just wait for the OTA to be offered (or proactively check for it) and accept it. If you're as novice as your posts suggest, I'm guessing that you're running a pure stock device, so you won't run into any problems with the upgrade. And if you do, you know where we are...

Categories

Resources