Alright, so I just flashed MRA58N yesterday, and today there is a new MRA58R image added? What's the difference here? The first build was a security update, but what's this new one? And why only a day difference? Thanks!
Sent from my Nexus 6
Changelogs aren't made readily available.
Perhaps this script will help people who update their local AOSP repo's will help.
https://groups.google.com/forum/#!msg/android-building/0DtsHawjs4k/And8o3Dni_UJ
Obviously some modification will be required
I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html
Quetzalcoalt_Lp said:
I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html
Click to expand...
Click to collapse
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6
I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.
Rektifying said:
I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.
Click to expand...
Click to collapse
What kernel are you using?
H4X0R46 said:
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6
Click to expand...
Click to collapse
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.
scryan said:
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.
Click to expand...
Click to collapse
I never do a dirty flash just to avoid conflict, but I guess it couldn't hurt to try right? So not wiping userdata should work?
Sent from my Nexus 6
If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...
I have always had zero issues applying newer stock images over older stock images on a Nexus device. I do this all the time when the OTA is not available and only the main updated Google Factory image is available.
I think the trick is to always wipe dalvik and cache after a flash of system and use TWRP that supports encryption. When you wipe the dalvik and cache the system acts like an OTA and performs an upgrade on all your apps. I *think* it effectively rebuilds the cache for all apps, but it never touches the app data or user data (sdcard/pictures/etc).
I also always flash the radios and bootloader *IF* they are updated from the last image. I used to flash the stock boot images too, but now that looks like from a going forward point we won't be able to do this and have root. I do look forward to system-less root
scryan said:
If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...
Click to expand...
Click to collapse
Cool dude! Thanks for the advice! Yea, I use ElementalX kernel on my device, unencrypted device makes no noticeable difference for performance to me, but the battery life is another story! ElementalX has superb battery life!
Sent from my Nexus 6
Any word on the changes between this and previous build yet?
Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.
dahawthorne said:
Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.
Click to expand...
Click to collapse
The security updates were also in the previous build, MRA58N.
All we really know for sure is that the OTA for MRA58R is being pushed out by Verizon. The OTA path skips MRA58N.
Pushed out by big red.... I think that's something I'll definitely wait on.
jbeezley said:
Pushed out by big red.... I think that's something I'll definitely wait on.
Click to expand...
Click to collapse
I've never had a problem with their updates and, realistically, this is actually a Google update. I'm just impressed that they're leading the charge.
I'm on MRA58K after sideloading the first Marshmallow OTA. I just noticed there's an OTA from K to N but there's nothing from any Marshmallow build to R.
I'm on N and haven't seen anything detailing what's different in R. I'm just a bit suspicious of anything pushed by Verizon, although you are correct @GilmourD3. It's Google's update, but why would Verizon spearhead the rollout? I would rather just stay on N awhile until we have someone in the know look over the details of the update to R.
I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.
H4X0R46 said:
I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.
Click to expand...
Click to collapse
Anything change from K to N? I might just sideload the N OTA since I'm currently on K and I'm not finding an OTA path from K to R.
R is apparently the OTA update to 6.0 and the November security update for Verizon Nexus 6. My wife got it Thursday and her build and security date both changed.
Related
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.
mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
FWIW: I would recommend that you:
1) Unlock bootloader
2) Decide if you want uncrypted kernel, or not (since it wipes data, just like unlocking bootloader).
3) Fastboot flash TWRP recovery.
4) Download SuperSU .zip and flash it in recovery.
5) Now, when a new OTA comes out, they usually show up here > http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493
6) You can download your current factory image here > https://developers.google.com/android/nexus/images
7) Unzip your current factory image. Fastboot flash the system.img and that will unroot and restore the stock recovery.
8) Fastboot flash the stock boot.img if you have a custom kernel (or an unencrypted stock kernel).
9) Relax and wait for the OTA.
RW-1 said:
Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.
Click to expand...
Click to collapse
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!
mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.
mad_rulzzz said:
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!
Click to expand...
Click to collapse
What he just explained is what I said, unroot and take the OTA.... He listed how as well.
RW-1 said:
What he just explained is what I said, unroot and take the OTA.... He listed how as well.
Click to expand...
Click to collapse
Yup.
@rw_1 @cam30era thanks guys
I would do what gee2012 said.
From what I have seen the OTA and the images are released pretty close together.
Instead of flashing images to get back to stock and waiting for the OTA. and then re-rooting
Just download the image files from Google. Manually flash all the files EXCEPT user data if you want to keep your data.
Re-root.
You are now updated and don't have to wait for OTA.
Either way works so it depends on which you are happier with.
mad_rulzzz said:
@rw_1 @cam30era thanks guys
Click to expand...
Click to collapse
Welcome. And BTW: there's a button for that.
gee2012 said:
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.
Click to expand...
Click to collapse
Just to be sure I understood right:
If I don't care about app data or settings ( I have titanium backup),
1)I can just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
one last thing... Does Google upload factory images after each OTA happens?
cam30era said:
Welcome. And BTW: there's a button for that.
Click to expand...
Click to collapse
My BAd!!
mad_rulzzz said:
If I don't care about app data or settings ( I have titanium backup),
1)Can I just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
Does Google upload factory images after each OTA happens? i.e; If Nexus 6 receives an OTA to 5.2, will they upload the 5.2 factory image soon?
Click to expand...
Click to collapse
When you unlock the bootloader it will wipe the contents of your SD card. Make sure it is backed up on your PC.
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.
cam30era said:
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.
Click to expand...
Click to collapse
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.
mad_rulzzz said:
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.
Click to expand...
Click to collapse
Correct. M is intended for T-Mobile. My point, though, is that Google doesn't always, 100% of the time publish a factory image for every OTA.
Finally ! Straight from Google DEVS
"nakasi" for Nexus 7 (Wi-Fi) 5.1.1 (LMY47V)
I found 5.1 official stock quite laggy on mine, coming from 4.4.4 official stock. So I wonder if there is a silver lining on this 5.1.1 or not. I won't hold my breath, but surprised that Google is willing to upgrade it despite it doesn't perform very well (similar to my iPad 1st gen taking 5.1.1, ironically, now same version number).
fortissimo said:
I found 5.1 official stock quite laggy on mine, coming from 4.4.4 official stock. So I wonder if there is a silver lining on this 5.1.1 or not. I won't hold my breath, but surprised that Google is willing to upgrade it despite it doesn't perform very well (similar to my iPad 1st gen taking 5.1.1, ironically, now same version number).
Click to expand...
Click to collapse
I believe this was to fix the memory leak that was still present.
Installed via fastboot and rebooting now. Will update when I know more.
I do know that removing Facebook appears to help with performance, but there was still a performance issue on 5.1 that required a reboot at times.
I just think that this Nexus 7 (2012) is too old for LP.
iBolski said:
I believe this was to fix the memory leak that was still present.
Installed via fastboot and rebooting now. Will update when I know more.
I do know that removing Facebook appears to help with performance, but there was still a performance issue on 5.1 that required a reboot at times.
I just think that this Nexus 7 (2012) is too old for LP.
Click to expand...
Click to collapse
I think the memory leak still hasn't been fixed yet, or it seems Google have found a fix but it STILL hasn't been released so it won't be in the 5.1.1 update.
https://code.google.com/p/android/issues/detail?id=170151&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
gsmyth said:
I think the memory leak still hasn't been fixed yet, or it seems Google have found a fix but it STILL hasn't been released so it won't be in the 5.1.1 update.
https://code.google.com/p/android/issues/detail?id=170151&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
Click to expand...
Click to collapse
thats for the Nexus 5 though, I havent seen anything for the N7 yet.
2 of mine are bricked (one APX mode, the other corrupted emmc but seems to "work" - sort of - with all F2FS rom), I bought a board for $40 to replace one of them but the digitizer clamp and pins flaked off on contact when trying to reassemble it so Im reluctant to do anything with it without touch capability. its just going to sit there with my blutooth mouse for kitchen-netflix for now. Im thinking of selling them all "as is" but Im curious if this update pans out, I might keep the touchless one.
There's a lollipop rom for F2FS??
Varnak said:
There's a lollipop rom for F2FS??
Click to expand...
Click to collapse
Every lollipop rom can be run with f2fs on data and cache with an appropriate kernel. I use rastapop and franco kernel r82 in with f2fs and its golden
JerryPi said:
Every lollipop rom can be run with f2fs on data and cache with an appropriate kernel. I use rastapop and franco kernel r82 in with f2fs and its golden
Click to expand...
Click to collapse
ok thanks. But i need to format system with normal partition?
Varnak said:
ok thanks. But i need to format system with normal partition?
Click to expand...
Click to collapse
You leave system partition on default ext4.
JerryPi said:
You leave system partition on default ext4.
Click to expand...
Click to collapse
How can i check wich partition are f2fs? i used a zip from this thread to convert http://forum.xda-developers.com/showthread.php?t=2678140
Varnak said:
How can i check wich partition are f2fs? i used a zip from this thread to convert http://forum.xda-developers.com/showthread.php?t=2678140
Click to expand...
Click to collapse
With the newer versions of twrp that zip is really not necessary to convert your partitions to a different file system.
To check and change format of your partitions go in your twrp recovery under wipe -advanced wipe - choose your partition - then repair or change your file system - there it says wich file system you are using and you can change it accordingly.
in twrp when you are changing the filesystem, it tells you which is the current.
Edit: just saw JerryPi's post
Two days in, 5.1.1 clearly better than 5.1 on my 32gb n7 2012 wifi.
Stock load/kernel/ext4 filesystems maintained, factory reset, full device restore/reinstall from cloud backup, rooted via TWRP, updated with SuperSU.
Nova Launcher, I just prefer it, no functional reason over stock Launcher.
Kindle app runs noticeably better, heck the Zinio reader app seems to work well too.
Google sheets/docs/presentation seems good.
TapaTalk Pro works well, as does Feedly. Notably less latency on network i/o and page transitions.
Facebook app doesn't seem to bring it down, even without any services disabled.
Haven't tried Chrome yet, and need to reload my music/video content to see how Rocket Player does.
disclaimer: I've taken to running "Trimmer (fstrim)" on an automatic schedule, daily, to keep nand free block lists healthy. That probably helps. I was doing that on 5.1 though.
If this keeps up I'd consider it a completely reasonable upgrade from KK.
Hi, what to do with the tgz file ? No zip to flash in custom recovery ?
Regards.
Marcovanbasten said:
Hi, what to do with the tgz file ? No zip to flash in custom recovery ?
Regards.
Click to expand...
Click to collapse
You need to flash via fastboot.
(sorry for my bad english I'm french )
Hi everybody,
I have received a new Nexus 6 32GB... No, sorry, a 64GB model (thanks to my resailer.. he make a mistake in the command, so I have won 32GB more! ).
But, I have few software problems with it...
At each OTA update, I get an error (at the robot opened screen). With almost all versions. This error get me a bootloop after update...
So I must to flash the official Google Image manually, partition by partition (else with NRT, I get an error at system writing step... I don't know why).
When I have fixed Android, finally, I have only.... 23.03 GB... With all versions.
So I must resize it in TWRP at each update (OTA or not).
For the last update, my bootloader have displayed at boot "Your device is corrupted. Blah blah blah..."
I actually make a new OTA update (6.1 I think). But I have an error one more time...
But I have no bootloop this time. The system reboot perfectly but in the old version. And few minutes later, the OTA is notified... Etc etc.
But, if a new system update is available, do you think I will get the same problems?
My system seems to be clean now... But during my multiple trys, my system has been clean too...
Without that, all is good and functionnal. Android, Wifi, LTE, screen, sound..... All!
This is very mysterious... Mostly for a new phone, non-rooted.
I did not want to root it while Google support it, but without root, my phone would still be blocked. That's not normal.
Should I be worried about it?
Thanks everyone!
1. Learn how to use ADB and Fastboot. Toolkits may get the job done, but you learn nothing in using them.
2. If flashing individual images from the system image, NEVER flash userdata.img as it resets your storage to 32GB. Formatting your internal storage using ADB, Fastboot, or in TWRP will restore the missing storage.
3. The system corruption message likely will disappear after you format internal storage and flash the stock images from Google. It will return however if you modify /system by adding files. To permanently remove it requires a custom kernel.
4. This a developer phone. You should be able to root it without losing the warranty.
Strephon Alkhalikoi said:
1. Learn how to use ADB and Fastboot. Toolkits may get the job done, but you learn nothing in using them.
2. If flashing individual images from the system image, NEVER flash userdata.img as it resets your storage to 32GB. Formatting your internal storage using ADB, Fastboot, or in TWRP will restore the missing storage.
3. The system corruption message likely will disappear after you format internal storage and flash the stock images from Google. It will return however if you modify /system by adding files. To permanently remove it requires a custom kernel.
4. This a developer phone. You should be able to root it without losing the warranty.
Click to expand...
Click to collapse
First thanks for your answer!
Oh yes for the 1 and the 4, my precedent phone is a Nexus 4, I know these phones and the steps to root/unroot/flash custom rom/recovery etc.. ^^ (I have made that a looooooot of times on my N4 without any problem, with and without NRT)
And this is for that I am surprised by the bad reaction of my Nexus 6 to this simple actions I request to it. (flashing image files)
I don't make anything I don't know, I am scared to brick my phone because I have made something that I master.
Yes I have forgot this point about userdata.img... But this is not a problem, I have resized my partition after flashing my phone with TWRP =)
The point that are interesting for me is the third point. I want to flash a stock image from Google. It's my goal. (I will flash custom ROM when Google will have stopped the update support)
In fact, my principal big problem is why the OTAs have been failed whereas I just start my phone, out of the box, with no modification and no root.
I'm not a specialist but for me, this is not normal when the phone is out of factory.
I will retry to flash another factory image from Google. This time with the flash-all script.
Thanks =)
Kermi78 said:
(sorry for my bad english I'm french )
Hi everybody,
I have received a new Nexus 6 32GB... No, sorry, a 64GB model (thanks to my resailer.. he make a mistake in the command, so I have won 32GB more! ).
But, I have few software problems with it...
At each OTA update, I get an error (at the robot opened screen). With almost all versions. This error get me a bootloop after update...
So I must to flash the official Google Image manually, partition by partition (else with NRT, I get an error at system writing step... I don't know why).
When I have fixed Android, finally, I have only.... 23.03 GB... With all versions.
So I must resize it in TWRP at each update (OTA or not).
For the last update, my bootloader have displayed at boot "Your device is corrupted. Blah blah blah..."
I actually make a new OTA update (6.1 I think). But I have an error one more time...
But I have no bootloop this time. The system reboot perfectly but in the old version. And few minutes later, the OTA is notified... Etc etc.
But, if a new system update is available, do you think I will get the same problems?
My system seems to be clean now... But during my multiple trys, my system has been clean too...
Without that, all is good and functionnal. Android, Wifi, LTE, screen, sound..... All!
This is very mysterious... Mostly for a new phone, non-rooted.
I did not want to root it while Google support it, but without root, my phone would still be blocked. That's not normal.
Should I be worried about it?
Thanks everyone!
Click to expand...
Click to collapse
Next time you flash and go into twrp make sure to select the "leave system read-only" option. Otherwise twrp will patch /system to survive a reboot and any modification to /system will break the next ota.
Kermi78 said:
...
But, if a new system update is available, do you think I will get the same problems?
Click to expand...
Click to collapse
Flash the latest TWRP 3.0 and the lite stock ROM of @Danvdh. This ROM has all you need, including root and OTA.
StykerB said:
Next time you flash and go into twrp make sure to select the "leave system read-only" option. Otherwise twrp will patch /system to survive a reboot and any modification to /system will break the next ota.
Click to expand...
Click to collapse
I have tried this. Thank you for this tip. I did not know Bootloader and OTAs fail depends of /system state. (I have never modified official google image. If I modify a device, it's with a custom rom like CM for example. Without my problem at the first start I would not have modify anything on my phone)
First, I don't have the bootloader message, that's a half good news
I download actually the MRA58N OTA update. Crossing fingers! =)
NLBeev said:
Flash the latest TWRP 3.0 and the lite stock ROM of @Danvdh. This ROM has all you need, including root and OTA.
Click to expand...
Click to collapse
My goal is to use the official Google Nexus Factory Images with official bootloader, etc.... Exactly the state of a normal Nexus out of the box.
But thank you. In last resort I will think of your tip.
StykerB said:
Next time you flash and go into twrp make sure to select the "leave system read-only" option. Otherwise twrp will patch /system to survive a reboot and any modification to /system will break the next ota.
Click to expand...
Click to collapse
So after my last try of OTA, 2 times, the update has been succeded!
Just thanks a lot! :good:
I notify this thread resolved
Kermi78 said:
My goal is to use the official Google Nexus Factory Images with official bootloader, etc....
Click to expand...
Click to collapse
Than you can't use layers. You have to live with the white Google ui, battery drain and hurting eyes.
NLBeev said:
Than you can't use layers. You have to live with the white Google ui, battery drain and hurting eyes.
Click to expand...
Click to collapse
Oh no that's good for me, I love Android Stock and I hate layers
For the battery... You see, my last phone was a Nexus 4. So the battery life of Nexus 6 is so wonderful for me!
In all cases, my phone is now stock and functionnal. Just that I want for the moment... I will see later for install other roms on it
I want to be simple things.
Kermi78 said:
(sorry for my bad english I'm french )
Hi everybody,
I have received a new Nexus 6 32GB... No, sorry, a 64GB model (thanks to my resailer.. he make a mistake in the command, so I have won 32GB more! ).
But, I have few software problems with it...
At each OTA update, I get an error (at the robot opened screen). With almost all versions. This error get me a bootloop after update...
So I must to flash the official Google Image manually, partition by partition (else with NRT, I get an error at system writing step... I don't know why).
When I have fixed Android, finally, I have only.... 23.03 GB... With all versions.
So I must resize it in TWRP at each update (OTA or not).
Click to expand...
Click to collapse
DON'T INSTALL THE userdata.img file and this won't happen.
Hello everyone.
I`ve got rooted Nexus 6 with Franco kernel. From time to time it shows system security updates, which I install`s. But I notices on my android security patch level stops on January 2016 and still want to install February updates. Everytime N6 tries to install February updates. Does anybody know whats going on? Maybe it`s because I locked with security password on my twrp? After rebooting twrp show`s and I really dont know are updates installed well. I quess not. Can someone help?
And another question, does this android security updates will remove my root?
Shantarien said:
And another question, does this android security updates will remove my root?
Click to expand...
Click to collapse
Security updates will not work; unless the device is completely stock.
You should look at installing the OTA from this page - instructions are provided. If you want to retain the kernel,TWRP & and root you'll have to re-flash them when you're finished.
https://developers.google.com/android/nexus/ota
If you're unencrypted (I'm not - I prefer the security to an extra 10 minutes of battery life) do some reading first - I'm not sure how the OTA works with an unencrypted device. Maybe other members can advise both of us on this point.
Thx for answer`s.
Correct me if I wrong, but I`ve got stock rom, but with Franco kernel, and root, but it`s still stock, right? Does this could be a reason? All my data are encrypted, so maybe this could be a reason ( however after every update reboot I decrypt`s my data), I`ll switch off encrypting my N6 and try again update it.
----------EDIT------------
Guess, NLBeev was right. I can`t make an OTA update when my N6 is rooted, only manually method. I really afraid of this manually updates, because of losing something from my phone, or even brick it.
fear is something that xda can not help you with. itll happen through out life, in many situations. the only thing that you can do is deal with it and move on.
I manually update mine every update and have yet to have an issue.
I f you're encrypted (good!) then my earlier concern is irrelevant. Sideload the newest OTA at the link I gave you. I've done it now several times with two Nexus 5s and a Nexus 6. It's quick and simple and doesn't touch your data.
But I still always take a TWRP backup first and copy it to my laptop. Can't be too careful...
Once again thanks for help! I`ll try install them manually, as fast as I make backup by twrp.
Ach, I forgot, last question, which update should I download? I`ve got January system security updates, so should I download every single one by one? Or just last one (July 6.0.1 (MOB30O))?
Regards!
By "manually' do you mean extracting the separate components (system, radio, boot...)? I strongly recommend the OTA sideload method. Fast and simple, with no data loss.
You need only do it once. Download the MOB30O OTA and sideload it. Then if you want you can flash TWRP and root.
Hi guys,
I tried a couple of years ago disabling encryption on my Nexus 6 and the performance was great, but as updates were released it turned out to be a pain to keep up always having to manually update the phone. My nexus 6 now is crawling and I'm thinking about trying to disable encryption. I could not find any sort of reports if it can be done on 7.1.1
Has anyone tried? Is there any guide? Thanks!
Mephisto_POA said:
Hi guys,
I tried a couple of years ago disabling encryption on my Nexus 6 and the performance was great, but as updates were released it turned out to be a pain to keep up always having to manually update the phone. My nexus 6 now is crawling and I'm thinking about trying to disable encryption. I could not find any sort of reports if it can be done on 7.1.1
Has anyone tried? Is there any guide? Thanks!
Click to expand...
Click to collapse
It's no different. If your bootloader is not unlocked, unlocking it will wipe the user data partition. If the bootloader is already unlocked, you'll need to wipe the user data partition.
*IN EITHER CASE YOU WILL LOSE YOUR DATA. DO A BACKUP FIRST
Then flash a ROM with an included kernel that doesn't force encrypt. Or, just flash a kernel that doesn't force encrypt.
Now that I've answered your question, IMHO, it's not worth the effort. If your phone is crawling, do a factory reset. On a stock ROM, go to Settings > Backup & Reset and make sure you have your Google backup settings enabled. Use the Factory Data Reset button to actually reset. READ through the information and confirm. This will cause your phone to reboot with a wiped system partition.
If your on a custom ROM I'm going to assume you know how to wipe through recovery.
ktmom said:
...., IMHO, it's not worth the effort. If your phone is crawling, do a factory reset.....
Click to expand...
Click to collapse
My 7.1.1 uses the lite stock rom of Danvdh.
I think you're right about the hassle. Only decrypting is not enough. But debloating and removing unused stuff and decrypting the data partition did raise performance on my N6.
Yeah, I know it is a bit of a hassle, but considering there will be no more updates after 7.1.1 it should be a once only process right? Is possible to disable encryption on 7.1.1. without rooting?
I'm happy to unlock the bootloader and wipe the phone, not a problem.
Mephisto_POA said:
Yeah, I know it is a bit of a hassle, but considering there will be no more updates....
Click to expand...
Click to collapse
Don;t forget the monthly security updates.
I am using the lite stock room of Danvdh. It's a pre-rooted stock room.
But I think updates can be dirty flashed because the system, radio and bootloader will not change anymore.
So root and install TWRP to flash the updates
the problem with rooting is that many apps will not work, I'm cool staying without root and vanilla android, I just want to get rid of the encryption
Mephisto_POA said:
the problem with rooting is that many apps will not work, I'm cool staying without root and vanilla android, I just want to get rid of the encryption
Click to expand...
Click to collapse
In that case the post of @ktmom is applicable.
I am on 7.1.1 and have used the fed patcher mentioned on this site and it has worked nicely on custom and stock ROMs. But u have to be rooted.
NLBeev said:
In that case the post of @ktmom is applicable.
Click to expand...
Click to collapse
I'm a bit illiterate in this aspect, apologies. but I could not find a vanilla android for nexus 6 with just encryption disabled and no root. I would really appreciate if you could give me some directions?
The NEXUS 6 ANDROID DEVELOPMENT and NEXUS 6 ORIGINAL ANDROID DEVELOPMENT seems both to have only modified versions. I'm a bit confused
Mephisto_POA said:
I'm a bit illiterate in this aspect, apologies. but I could not find a vanilla android for nexus 6 with just encryption disabled and no root. I would really appreciate if you could give me some directions?
The NEXUS 6 ANDROID DEVELOPMENT and NEXUS 6 ORIGINAL ANDROID DEVELOPMENT seems both to have only modified versions. I'm a bit confused
Click to expand...
Click to collapse
Plain vanilla unencrypted would be google factory image plus a non forced enforcing kernel. B14CKB1RD, Franco there are others.
Custom ROM that is close to vanilla but comes with a non forced encrypting kernel would be Pure Nexus.
Mephisto_POA said:
I would really appreciate if you could give me some directions?
Click to expand...
Click to collapse
I have only one direction for you and that's the lite stock rom of Danvdh.
The kernel is the modified part. (no forced encryption).
After flashing this rom, you can unroot by uninstalling supersu.
https://forum.xda-developers.com/showthread.php?p=59561445/
NLBeev said:
I have only one direction for you and that's the lite stock rom of Danvdh.
The kernel is the modified part. (no forced encryption).
After flashing this rom, you can unroot by uninstalling supersu.
https://forum.xda-developers.com/showthread.php?p=59561445/
Click to expand...
Click to collapse
Hi, I also want to remove encryption from my Nexus 6 Stock as it is a stuttering mess.
I have rooted and installed the stock rom of Danvdh, but to my disappointment on boot up the phone is still showing as encrypted.
Have I done something wrong?
saltyzip said:
Hi, I also want to remove encryption from my Nexus 6 Stock as it is a stuttering mess.
I have rooted and installed the stock rom of Danvdh, but to my disappointment on boot up the phone is still showing as encrypted.
Have I done something wrong?
Click to expand...
Click to collapse
That was an answer to a different question.
The ROM you installed I believe has a non-force encrypting kernel. But just installing a non-force encrypting kernel isn't enough. You need to wipe user data and install a kernel that doesn't force encrypt.
Please read back a page to two for the whole recent conversation that has more details, like the fact that you'll lose all of your data in this process.
saltyzip said:
Hi, I also want to remove encryption from my Nexus 6 Stock as it is a stuttering mess.
I have rooted and installed the stock rom of Danvdh, but to my disappointment on boot up the phone is still showing as encrypted.
Have I done something wrong?
Click to expand...
Click to collapse
Got it working, just followed this:
Just because forced encryption is disabled doesn't mean it decrypts you. You have to do that yourself by formatting data either through TWRP (TWRP > Wipe > Format Data button) or through fastboot (fastboot format userdata), which will wipe out your app data and your internal storage partition so make the appropriate backups.
saltyzip said:
Got it working, just followed this:
Click to expand...
Click to collapse
You going to take credit, you should at least use your own words ?
I've gone with your guys suggestion with stock lite, working like a charm, very snappy. The phone feels indeed light, and multitasking is way smoother now, thanks!!!
just on a side note, after you install the rom you need to wipe the data partition to get rid of the encryption
Installed twrp on bn Nexus 6 os 5.1 OTA for 7.1.1 encrypted it
No clue how to fix this I'm a noob unlocked bootloader unencrypted Android 5 then it OTA updated to 7.1.1 and now can't get to twrp to wipe encryption how can I get this going again phones working just can't use cable to computer have the SD card reader micro SD any help would be appreciated
kudabee61 said:
...just can't use cable to computer...
Click to expand...
Click to collapse
Get your phone's USB port fixed, then you can fix the ROM issue.