Related
im pretty happy with kk, but i do want to be on 5.0, so i just wanted to make a few thing clear first.
1. if anything goes wrong with flashing a captured ota, how to restore my kk as it is now? will simply restoring a twrp backup do the trick on any stock rom?
2. where can i find the stock rom? the motorola site links arent working for me.
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
5. are there any bugs that seriously affect most users?
i am planning to root immediately so root only mods are fine.
im on a rooted unlocked bootloader xt1063,
thanks for your time,!
1. Just flash the stock ROM via fastboot.
2. I guess are some links on the Development section.
3. in 5.0, unfortunately not.
4. I guess no :/
5. Only a bootloop that happens with the newest versions of SuperSU (the only versions that works with 5.0), no major bugs..
Sent from my XT1063 using XDA Free mobile app
thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?
Kobro said:
thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?
Click to expand...
Click to collapse
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.
Kobro said:
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.
Click to expand...
Click to collapse
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.
Kobro said:
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
Click to expand...
Click to collapse
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!
Flash custom rom and enjoy lollipop
pastorbob62 said:
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.
Click to expand...
Click to collapse
your right for stating everything clearly, my bad
anomalyconcept said:
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!
Click to expand...
Click to collapse
yes that works, and has been since 4.3, on my custom rom devices it just is not so comfortable on a 5" device i was thinking more of something like pull down from right.
these responses motorola about the model xt1068
Catherine: Hi, my name is Catherine. How may I help you?
ENRICO: good morning
are to hold model xt1068, I wanted to know when will the update to Android 5
Catherine: Hi, at the moment we do not have a release date for Lollipop in Europe. It is currently going through testing before release but we are working hard to get it out as soon as possible. You can find the latest information at http://www.motorola.com/updates
ENRICO: thanks
Catherine: No problem, is there anything else that I can help you with?
ENRICO: no thanks
Catherine: Ok, have a nice day!
ENRICO:
pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.
Kobro said:
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.
Click to expand...
Click to collapse
Don't need it now, but good to know should I have to reflash in the future. Thanks for the info. :good:
My Nexus 6 has finally shipped! It should be here Friday!
This is my first Nexus and I have never rooted, unlocked, flashed, etc. any of my previous phones.
I have been doing a lot of research and have been considering running CM12.
My question is, should I run my Nexus 6 with stock android for a few weeks and then try CM12? Or should I just root, unlock, and flash CM12 as soon as I get it?
I know that if I wait then I will need to back up all my data because it will factory data reset but I am not worried about that... I understand it is easier to do it right out of the box because you don't have to worry about loosing anything but I can just back my info/apps up so that isn't a big deal.
Also, would you guys suggest something over CM12? Right now I am planning on using CM12 and just getting it setup how I like it then leaving it. I don't plan on always flashing and making changes but I might get sucked into it lol
Thanks everyone!
Has CM moved to 5. 1 yet?
What version android came your phone?
Depending on those two answers you have to ask yourself if you want to downgrade your phone. At least version wise
Sent from my Google N6 on VZ
DebianDog said:
Has CM moved to 5. 1 yet?
What version android came your phone?
Depending on those two answers you have to ask yourself if you want to downgrade your phone. At least version wise
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Good point! I don't know if CM is on 5.1 yet. I just assumed it was but I will look into it. This is all new to me so thanks for pointing that out, didn't even think about that!
I won't know what version is on the phone until Friday. But even if it is on 5.0 I am sure it will notify me that 5.1 is ready to download as soon as I boot up the phone.
On my other phones I usually got rid of the stock and was on a custom ROM a pretty quick. I have tried a few ROMs on this phone as well. in my experience if you want to be on 5 .1 currently the best way to go is stock with debloating . Or use one of the clean/vanilla ROMs. Of course I did not test them all there are so many out there. Good luck with your new toy.
I will try CM after its been out a few weeks on 5 .1
Sent from my Google N6 on VZ
I'd recommend updating to 5.1 if it doesn't ship with 5.1. Then, I'd run stock for at least a few days to get a baseline for comparison. I think this is useful especially for bugs. That way you can get an idea of the issues that exist in stock 5.1 before using a custom ROM.
DebianDog said:
On my other phones I usually got rid of the stock and was on a custom ROM a pretty quick. I have tried a few ROMs on this phone as well. in my experience if you want to be on 5 .1 currently the best way to go is stock with debloating . Or use one of the clean/vanilla ROMs. Of course I did not test them all there are so many out there. Good luck with your new toy.
I will try CM after its been out a few weeks on 5 .1
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Okay, thanks for the info!
Since I ordered my phone directly from Google, do I need to debloat? Or is that just for carrier versions?
mlin said:
I'd recommend updating to 5.1 if it doesn't ship with 5.1. Then, I'd run stock for at least a few days to get a baseline for comparison. I think this is useful especially for bugs. That way you can get an idea of the issues that exist in stock 5.1 before using a custom ROM.
Click to expand...
Click to collapse
Another great point! I knew you guys were the people to ask! lol
What about rooting and unlocking? Would you suggest waiting on that as well? Is there really any reason to unlock and root if I won't be running CM? I was going to root so that I could decrypte but it sounds like the lag from encryption is fixed in 5.1.
Well I would guess you WILL want to unlock and root because who does want to be able to run a root level ad blocker? Who wants to wait on OTA for an update? Not me.
I got mine from Google, as well, and heres what I did:
Played with the phone in stock form for like an hour saw it was still on 5.01 even after updating
Decided this is not for me. I wanted my root apps and I wanted to copy all the stuff off my old phone with Titanium backup to the Nexus
Looked on the interwebs for the easiest way to get root
Found a tool from my old buddy WugFresh (I knew him in the Droid X days)
Prepared myself for a giant PITA night. Download, drivers, and programs, reading various sites, etc, etc, etc
Was freaking SHOCKED that the tool did ALL THIS for me. I mean I literally plugged in my phone and it collected and set up everything. (It also has a console if you feel the need to type in adb commands)
Was unlocked, upgraded, rooted with a custom recovery with all my apps copied over in less than an hour
Sent Wuggy some $$$ and a thank-you note
You only need to decrypt, IMO, if you are running high end games that demand that level of performance. I have not seen any lag myself. Again this is my own personal experience. Your results may vary. 5.1 has optimized out many of the issues I heard about in 5.01 or so I have been told.
CFrance said:
Another great point! I knew you guys were the people to ask! lol
What about rooting and unlocking? Would you suggest waiting on that as well? Is there really any reason to unlock and root if I won't be running CM? I was going to root so that I could decrypte but it sounds like the lag from encryption is fixed in 5.1.
Click to expand...
Click to collapse
I unlocked and rooted right away, mainly for the ability to use Titanium Backup to setup my phone and in the event that I installed a custom ROM. Outside of TB, I haven't really needed or used root, but it sure is nice to have. I played with a few custom ROMs before 5.1 came out but mostly felt that I preferred the stock experience. I downloaded the MCR modpack found here: http://forum.xda-developers.com/showpost.php?p=58019266&postcount=1 but have yet to install it. If/when I do, root will become more of a requirement for my uses.
I came from a Verizon Note 4 which could not be rooted. I got used to not playing with my phone and just using the stock experience. Its nice that the stock experience on the N6 is so fantastic and stable. It makes it easy to just use the phone without worry of fixing, modding, and adding features, though I still enjoy those aspects too which is why I'll likely use MultiROM next time I decide to install something custom.
Dude are you somehow tied up with this Tool Kit? You`re promoting it on so many threads i`am starting to get the impression you`re not quite objective about it There is no harm in using toolkits by xperienced users and i`am sure its well build, but for newbies its very dangerous because they`re lost if something should go wrong.
gee2012 said:
Dude are you somehow tied up with this Tool Kit? You`re promoting it on so many threads i`am starting to get the impression you`re not quite objective about it There is no harm in using toolkits by xperienced users and i`am sure its well build, but for newbies its very dangerous because they`re lost if something should go wrong.
Click to expand...
Click to collapse
Which is exactly why I'm promoting it it is almost bulletproof. what's the alternative loading all the different tools and drivers they need and following some instructions found on the internet.
And as I explained in my post you can just download the tool to make sure you have all the drivers and connections. use it to get the proper files you need and then run the command line like a power user if you want to feel better about yourself.
Sent from my Google N6 on VZ
DebianDog said:
Which is exactly why I'm promoting it it is almost bulletproof. what's the alternative loading all the different tools and drivers they need and following some instructions found on the internet.
And as I explained in my post you can just download the tool to make sure you have all the drivers and connections. use it to get the proper files you need and then run the command line like a power user if you want to feel better about yourself.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I will never use/promote a Toolkit even if it seems very good for the reason i posted earlier. Flashing manualy in fastboot doesn`t take more time and makes users more aware about their phone and knowledge of it and gives you control over whats happening Just my 2 cents.
My two cents. I don't think you've dealt with enough newbies. on another forum it was me and a group of others that would help people get their phones out of boot loops and soft bricks. I have literally helped hundreds of people get their phone back.
even if you look here on XDA you'll see people trying to flash the wrong files download files that are not even for their phone, are following a dated instruction or don't really understand how directories work.
Sent from my Google N6 on VZ
DebianDog said:
Well I would guess you WILL want to unlock and root because who does want to be able to run a root level ad blocker? Who wants to wait on OTA for an update? Not me.
I got mine from Google, as well, and heres what I did:
Played with the phone in stock form for like an hour saw it was still on 5.01 even after updating
Decided this is not for me. I wanted my root apps and I wanted to copy all the stuff off my old phone with Titanium backup to the Nexus
Looked on the interwebs for the easiest way to get root
Found a tool from my old buddy WugFresh (I knew him in the Droid X days)
Prepared myself for a giant PITA night. Download, drivers, and programs, reading various sites, etc, etc, etc
Was freaking SHOCKED that the tool did ALL THIS for me. I mean I literally plugged in my phone and it collected and set up everything. (It also has a console if you feel the need to type in adb commands)
Was unlocked, upgraded, rooted with a custom recovery with all my apps copied over in less than an hour
Sent Wuggy some $$$ and a thank-you note
You only need to decrypt, IMO, if you are running high end games that demand that level of performance. I have not seen any lag myself. Again this is my own personal experience. Your results may vary. 5.1 has optimized out many of the issues I heard about in 5.01 or so I have been told.
Click to expand...
Click to collapse
Thanks for the info! I actually had just downloaded this program over the weekend and was planning on using it once I do decide to root... which I am thinking will be as soon as I get the phone. lol other than that I think I am going to run it on stock for a while at first and wait until CM is on 5.1 for a while....
mlin said:
I unlocked and rooted right away, mainly for the ability to use Titanium Backup to setup my phone and in the event that I installed a custom ROM. Outside of TB, I haven't really needed or used root, but it sure is nice to have. I played with a few custom ROMs before 5.1 came out but mostly felt that I preferred the stock experience. I downloaded the MCR modpack found here: http://forum.xda-developers.com/showpost.php?p=58019266&postcount=1 but have yet to install it. If/when I do, root will become more of a requirement for my uses.
I came from a Verizon Note 4 which could not be rooted. I got used to not playing with my phone and just using the stock experience. Its nice that the stock experience on the N6 is so fantastic and stable. It makes it easy to just use the phone without worry of fixing, modding, and adding features, though I still enjoy those aspects too which is why I'll likely use MultiROM next time I decide to install something custom.
Click to expand...
Click to collapse
Thanks! I am planning on rooting and unlocking right away for TB and maybe a couple other little things like lightflow just for fun. Being the nerd that I am, I have a feeling that once I start playing with the whole rooting, unlocking, and flashing stuff I am going to really enjoy it.
gee2012 said:
I will never use/promote a Toolkit even if it seems very good for the reason i posted earlier. Flashing manualy in fastboot doesn`t take more time and makes users more aware about their phone and knowledge of it and gives you control over whats happening Just my 2 cents.
Click to expand...
Click to collapse
Thanks for the reply! I see what you are saying, I had already come across Wug's toolkit over the weekend and was planning on using that because it seemed so simple.
However, seeing how I still have two and a half days until my phone will be here, maybe I will look into the manual way a little more to decide which route I want to go.... Any suggestions on where to start? Threads, videos, etc?
Thanks!
Boot into download mode, Unlock bootloader, reboot, boot back into download mode, fastboot twrp recovery, boot into recovery, reboot via recovery and install su when prompted. When you boot into android you will be prompted to update su. You now are rooted. Only other thing I would think about when you first get your device is if you want forced encryption. You will be required to wipe SD data if you decide to go with non forced encryption.
I loved cm on my previous touchwiz devices because I like stock/asop style. I find cm has bugs in early os update releases. I would only install cm if i took advantage of themes which I don't.
CFrance said:
Any suggestions on where to start? Threads, videos, etc?
Thanks!
Click to expand...
Click to collapse
You can waste a lot of time while you're waiting for your phone in this thread http://forum.xda-developers.com/showthread.php?t=2992769
ROM Reviews (5.1) + Nexus 6 Hacking: NRT · Apps · Utilities [3.22.15]
Sent from my Google N6 on VZ
Hey there,
I got quite a serious problem. Since i updated to 5.1 my phone sometimes suddenly restarts, followed by a message which says "optimizing apps", which ranges from 30 to 150 apps. At first, it was no big problem, now it occures nearly every 10 minutes, so currently i can't really use my phone.
What i tried to do:
Factory reset, reflash 5.0 - 5.1.1 (every single image available)
The problem is still there.
Now my question, is it a Softwareproblem, which will be updated soon (should i try Android M (what about the warranty?))?
Or is it quite a serious hardwareproblem (i read somewhere that it could be because of overused RAM modules)?
I tried to use the searchengine, but i didnt find a specific thread in this subforum.
The optimising is a software issue caused by a random reboots. The reboot itself could be caused by anything though
danarama said:
The optimising is a software issue caused by a random reboots. The reboot itself could be caused by anything though
Click to expand...
Click to collapse
Thank you for your quick reply. I continued reading and as it seems there are quite a number of users with the same problems as me. Although no one has gotten a solution till now. It doesn't matter if it's a Nexus 4, 5 or 6 but all the Nexusphones seem to be affected once updated to 5.1 or newer.
Unluckily sending it in to repair is not a good solution because they told me it would take 2-4 weeks which is not possible for me... How can Google not release a proper update after 5.1.1 which fixes it? Are they so focused about Android M? I still can't overcome myself to install the Android M because i fear to lose my warranty.
Haabiii said:
Thank you for your quick reply. I continued reading and as it seems there are quite a number of users with the same problems as me. Although no one has gotten a solution till now. It doesn't matter if it's a Nexus 4, 5 or 6 but all the Nexusphones seem to be affected once updated to 5.1 or newer.
Unluckily sending it in to repair is not a good solution because they told me it would take 2-4 weeks which is not possible for me... How can Google not release a proper update after 5.1.1 which fixes it? Are they so focused about Android M? I still can't overcome myself to install the Android M because i fear to lose my warranty.
Click to expand...
Click to collapse
Dude, it's a Nexus. Warranty isn't an issue as long as you return to stock and relock before a warranty claim.
If flashing a factory image didn't fix it, either you're not wiping or formatting the cache correctly or you have a hardware issue.
Don't be so quick to blame Google when thousands of others, myself included, have taken the update without issue.
Evolution_Tech said:
Dude, it's a Nexus. Warranty isn't an issue as long as you return to stock and relock before a warranty claim.
Click to expand...
Click to collapse
Thanks, I didn't know that.
Evolution_Tech said:
If flashing a factory image didn't fix it, either you're not wiping or formatting the cache correctly or you have a hardware issue.
Click to expand...
Click to collapse
I did the factoryreset via fastboot, also i used the nexus toolkit to do a proper stock reset so i don't quite get how it could be an incorrectly done reset. So the hardware just breaks during the updateprocess?
Evolution_Tech said:
Don't be so quick to blame Google when thousands of others, myself included, have taken the update without issue.
Click to expand...
Click to collapse
I am usually quite quick in blaming others if there are also many people with excactly the same problem, sudden reboots with app optimization right after the update to 5.1 or 5.1.1, some even before at 5.0 or 5.0.1.
I'm going to try the Android M Update, maybe that will help.
Haabiii said:
Thanks, I didn't know that.
I did the factoryreset via fastboot, also i used the nexus toolkit to do a proper stock reset so i don't quite get how it could be an incorrectly done reset. So the hardware just breaks during the updateprocess?
I am usually quite quick in blaming others if there are also many people with excactly the same problem, sudden reboots with app optimization right after the update to 5.1 or 5.1.1, some even before at 5.0 or 5.0.1.
I'm going to try the Android M Update, maybe that will help.
Click to expand...
Click to collapse
Personally, I'd boot to bootloader and do:
fastboot format cache
Evolution_Tech said:
Personally, I'd boot to bootloader and do:
fastboot format cache
Click to expand...
Click to collapse
Already done and i also reflashed the whole cache image. I hope the Android 6 Update will help solve my issues. The problem is, that i usually get really upset about little stuff like that just because i don't get why it's happening.
I updated monday evening to the Android M Preview, for now it only restarted once to, as it said, install a update (?), since then no reboot at all. It worked like a charm yesterday. I really hope the problem is fixed that way.
Just wanted to let you know if you have a same problem.
Hello guys. Just bought 2 days a go a new Nexus 6. Blue with 32Gb, unlocked.
Tottaly sealed, broke the seal myself, straight from Google.
But the phone says it is updated, and finds no new update. Im on LMY47D with Android 5.1 and I dont even receive 5.1.1
Tried factory reset without SIM Card, cleaning Framework and reboot without card, everything. To no avail.
Any idea what is going on? Shouldnt I get at least Android 5.1.1?
PS: I know I can sideload it, but still, something is clearly wrong, and I would like very much to sort it out.
Thank you very much.
Same issue here. Only I'm on 5.0 and can't find any update and I would prefer to not sideload already.
if you want your phone to check for an update, you have to be on WiFi. if in youre on network instead, itll always say up to date.
I'm on wifi. It still shows no update.
Same situation, on Wifi offcourse.
tryklon said:
Same situation, on Wifi offcourse.
Click to expand...
Click to collapse
Try a factory reset, then remove your carrier SIM and power up on WiFi. My bet is that your N6 will start churning through OTAs in sequence. Not sure that you will get all the way to Marshmallow 6.0, because that last OTA is still being rolled out.
Already did it... waste of time, no updates
If your not willing to simply download and flash the images from googles website, that is your choice... but there is nothing to do but wait.
Hi Guys I am in the same boat, brand new n6 on 5.0.1 and saying up todate . In uk and carrier is Virgin if that helps.
Mal
Something strange is definately happening with Google update servers...
same dilemma and same version as op..
Personally I was like you all. I got my nice shiny new n6 from verizon (free upgrade...) Got it home kept pressing check for updates. Tried all the clearing app data from frameworks and all that.
But in the end I sideloaded it. I documented it over on the OTA url post. It is not that hard, just need some time. If you don't want to wait it might be your only option.
Total time invested was probably 1.5 hours. Downloaded all the files to my laptop and started using WUGFresh.
Stop waiting and update manually? It's not difficult, you can even save your userdata by not flashing it. There are different (and possibly easier) ways to install an update other than sideloading. especially when you can skip all the OTAs and flash directly to 6.0.
No need for a tool kit and it won't take much longer than the time it takes for you to download the factory image and extract the files.
The point is that there might be something wrong with Google's OTA servers.
Or maybe something is wrong about these phones ?
Sent from my VS985 4G using Tapatalk
Thats my point exactly. What if theres something wrong with the phone?
Google should clarify why old updates are not being delivered... not even questioning 6.0, but 5.1.1
same issue on new nexus 6 of my girlfriend. I manually sideloaded up to 5.1.1 (it's the international version) and now she's waiting for 6.0
europeanpaul said:
same issue on new nexus 6 of my girlfriend. I manually sideloaded up to 5.1.1 (it's the international version) and now she's waiting for 6.0
Click to expand...
Click to collapse
Why not sideload 6.0
jdice said:
Why not sideload 6.0
Click to expand...
Click to collapse
Why is Google not delivering OTA updates to these N6 owners ?
Sent from my VS985 4G using Tapatalk
Because there were a couple of security updates between 5.1.1 and 6.0 (as far AS I remember on my N6) and because I want to be sure OTA works!
This issue is becoming more and more coomon. Lot's of people complaining on several forums about this issue.
At least its easy to see something is clearly wrong with the OTA's, since no one is getting any. There is people stuck on 5.0, 5.0.1, 5.1, etc whichever came preinstalled stays without updates.
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.