Stock Rom - Nexus 6 Q&A, Help & Troubleshooting

Does anyone know of a stock, un-encrypted, no root, nougat ROM? Tried a few "stock" roms and removed SU within the actual file. But all that does is cause issues. Any ideas?

Factory images of Android 7 were just released and Google makes them readily available to everyone. Download one and flash it using Fastboot. Problem solved.
I misread your post and missed that you were looking for an unencrypted ROM. There isn't one that I'm aware of...yet. Wait a few days and Pure Nexus should be released.

Use the factory image with a custom kernel/modified boot image that doesn't force encryption.

So like ElementalX Kernel. All I would have to do is, flash factory and than ElementalX and I should be ok?

Related

[Q] Rooted 5.0.1, OTA update to T-mo 5.1 offered, failed. How to proceed?

Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
a phone that is pure stock can take an ota. a phone that has any files changed, or not pure stock can not flash an ota, doesnt matter how many otas you try. you will have to flash the factory img.
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
you cant flash it in twrp. you can flash the factory img via fastboot while youre in the bootloader. or you can flash a 5.1 custom rom, that will be easier.
RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
If you want to take the OTA, do the following:
Download the 5.0.1 factory zip.
Extract all of the files.
To unroot, fastboot flash the system.img.
Fastboot flash the stock recovery.img.
If you are unencrypted, fastboot flash the stock boot.img.
RanceJustice said:
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
Click to expand...
Click to collapse
Please take a bug report and find the OTA link inside. Instructions here: https://www.reddit.com/r/nexus6/comments/2zlqid/psa_if_you_receive_the_tmobile_51_ota_update/

Unroot, return to stock and update to Android 6.0

Hi all,
I've been a long long time rooter of phones. The Nexus 6 was no different. I'm running Temasek's CM12 rom and it's been great, but I'd like to go back to stock and run the Marshmallow rom unrooted. It seems like with Doze and other features it would be better for me at this time.
I have the ATT version of the Nexus 6 and the latest TWRP installed. What would I need to do to install the latest stock 6.0 rom (safely?). Im a technical person but rather than throw things at the wall and see what sticks, I'm looking for a couple of testimonials to make me feel better about doing this
Thanks!
Flashing the factory images from Google is likely your best bet. You can flash everything separately, skipping the userdata image if you don't want to format your data partition, and skip the recovery image if you want to keep TWRP. I am sure there are guides on site to assist with this if you aren't sure how to accomplish this.
You will likely have to factory reset in TWRP as going from CM > stock will likely cause some problems. Also, if you have disabled encryption and want to stay that way, you will want to flash a custom kernel that removes the force encryption before booting into Android.

Nexus 6 NEWB help installing Marshmallow

Hello All,
A few months ago I got a Nexus 6 as a replacement for a Moto 2014. I love Nexus devices and used to flash roms back in the day and now I am a little lost. I followed some instructions when I first got the device on how to set up Root using WUGFresh Root Tool Kit: http://www.wugfresh.com/nrt/ I also installed TWRP recovery. I can't remember how I actually got here because I did it a while back. I rooted and set up a custom recovery.
I am on 5.1.1 at the moment.
Kernel Version: 3.10.40-gc16a3c6
[email protected] #1
Tue Jul 28 17:58:25 UTC 2015
Build Number:
LMY48W
Im on AT&T
I can't remember how I actually got here because I did it a while back. I rooted and set up a custom recovery (I think) and I basically started from scratch and had to reinstall everything. I want to update to Marshmallow and I have a few questions.
1.) If I do update it to the Marshmallow 6.0.1 will I lose all my data and installed programs?
2.) Where can I get the closest to stock Marshmallow 6.0.1 or 6.0 for the Nexus 6?
3.) Whats the best way to install it?
4.) If I get an OTA should I install it? What will happen if I do?
Sorry for all the NEWB questions. I got so lost in all the documentation, references, XDA developers, multiple versions of custom recoveries I can't figure out what I did anymore and I can't figure out what to do!
TLDR: I have a Nexus 6 on 5.11 LMY48W, phone is rooted, I have TWRP, how can I get step by step instructions to install the best and most up to date Marshmallow for Nexus 6?
First and foremost: Please, don't use rootkits and toolkits, the Marshmallow updates come fast, toolkit developers will always be a step behind. Not to mention, that if something goes sideways (and wirh Marshmallow it probably will), you won't have the knowledge to fix it.
So:
4) You're rooted, you won't get an OTA
1) Since you won't get an OTA, you must flash by hand, and you should always do a clean install when doing a version upgrade
3) Now you can decide if you do a full factory setup, with flashall, or you can choose to learn how to flash images one by one, then if you don't flash userdata, and you do the factory reset from a custom recovery, you'll have all your files intact. But the stock recovery deletes everything when doing factory reset.
https://developers.google.com/android/nexus/images?hl=en#instructions
2) https://developers.google.com/android/nexus/images?hl=en#shamu
Scroll down to the most recent one: 6.0.1 (MMB29K)
istperson said:
First and foremost: Please, don't use rootkits and toolkits, the Marshmallow updates come fast, toolkit developers will always be a step behind. Not to mention, that if something goes sideways (and wirh Marshmallow it probably will), you won't have the knowledge to fix it.
So:
4) You're rooted, you won't get an OTA
1) Since you won't get an OTA, you must flash by hand, and you should always do a clean install when doing a version upgrade
3) Now you can decide if you do a full factory setup, with flashall, or you can choose to learn how to flash images one by one, then if you don't flash userdata, and you do the factory reset from a custom recovery, you'll have all your files intact. But the stock recovery deletes everything when doing factory reset.
https://developers.google.com/android/nexus/images?hl=en#instructions
2) https://developers.google.com/android/nexus/images?hl=en#shamu
Scroll down to the most recent one: 6.0.1 (MMB29K)
Click to expand...
Click to collapse
Thanks. Since I am using the Nexus 6 do you recommend that I set it back to factory settings to get the OTA updates? If so what is a good link for instructions to do that? Thanks!
As long as you are going from stock to stock, you can skip the factory reset - I've done that all this time, and have never had an issue. Just flash using fastboot (don't use flash-all), and skip the step to flash userdata.
shibed said:
Thanks. Since I am using the Nexus 6 do you recommend that I set it back to factory settings to get the OTA updates? If so what is a good link for instructions to do that? Thanks!
Click to expand...
Click to collapse
Nevermind I saw your link. I should have read that a little closer. Thanks! I will try the factory image.
istperson said:
First and foremost: Please, don't use rootkits and toolkits, the Marshmallow updates come fast, toolkit developers will always be a step behind. Not to mention, that if something goes sideways (and wirh Marshmallow it probably will), you won't have the knowledge to fix it.
So:
4) You're rooted, you won't get an OTA
1) Since you won't get an OTA, you must flash by hand, and you should always do a clean install when doing a version upgrade
3) Now you can decide if you do a full factory setup, with flashall, or you can choose to learn how to flash images one by one, then if you don't flash userdata, and you do the factory reset from a custom recovery, you'll have all your files intact. But the stock recovery deletes everything when doing factory reset.
https://developers.google.com/android/nexus/images?hl=en#instructions
2) https://developers.google.com/android/nexus/images?hl=en#shamu
Scroll down to the most recent one: 6.0.1 (MMB29K)
Click to expand...
Click to collapse
Dude! Just as an FYI I want to thank you and let you know I was able to successfully sort out my issues using your guidance.
shibed said:
Dude! Just as an FYI I want to thank you and let you know I was able to successfully sort out my issues using your guidance.
Click to expand...
Click to collapse
I'm glad I could help.

Updating to MMB29K 6.01 Causing Bootloop from MRA58X 6.0.0

I tried 6 ways to sunday to update to 6.01 on a shamu nexus 6 to no avail :crying
I am unlocked, no encryption, rooted on MRA58X 6.0.0. When I try to upgrade it just bootloops.
I am fastbooting new MMB29K 6.01 bootloader.img, new radio.img, new system.img, new unencrypted boot.img, and flashing in TWRP SuperSu v2.61 prior to first reboot.
Can someone tell me what is up???? I want to stay encrypted
Thanks, Mark
There is another thread that talks about a particular flashing order. I wonder if that is your problem?
Sent from my Nexus 6 using XDA Free mobile app
Deckard_9732 said:
I tried 6 ways to sunday to update to 6.01 on a shamu nexus 6 to no avail :crying
I am unlocked, no encryption, rooted on MRA58X 6.0.0. When I try to upgrade it just bootloops.
I am fastbooting new MMB29K 6.01 bootloader.img, new radio.img, new system.img, new unencrypted boot.img, and flashing in TWRP SuperSu v2.61 prior to first reboot.
Can someone tell me what is up???? I want to stay encrypted
Thanks, Mark
Click to expand...
Click to collapse
These contradict each other, no?
Out of curiosity, what are you coming from, 6.0? Were you running any ROM of any sort?
Last question...when TWRP is about to reboot and it asks if you want it to install root, you're choosing 'No' right? 2.61 is the system-less root, and if TWRP is trying to flash it's version it'll cause problems.
I know some of these may seem simple and 'duh' moments, but I just spent the past 60 minutes trying to find out why I couldn't update only the radio......it was the radio for the N5, so we've all been there
I'm coming from MRA58X 6.0.0 and no custom rom. I do have the hells core kernal v11 ... and no I select 'No' when rebooting from TWRP to install SuperSu. Shamu Nexus 6 works great with MRA58X 6.0.0 unencrypted and rooted with hells core v11 kernal and SuperSu v2.52. I dont know how to upgrade to 6.0.1 and stay encrypted? hells core has v12 kernal 6.0.1.
Deckard_9732 said:
I'm coming from MRA58X 6.0.0 and no custom rom. I do have the hells core kernal v11 ... and no I select 'No' when rebooting from TWRP to install SuperSu. Shamu Nexus 6 works great with MRA58X 6.0.0 unencrypted and rooted with hells core v11 kernal and SuperSu v2.52. I dont know how to upgrade to 6.0.1 and stay encrypted? hells core has v12 kernal 6.0.1.
Click to expand...
Click to collapse
I haven't been modding my N6 much at all, but I do remember reading something about when using custom kernels. I cannot remember exactly what it was, but there was an issue when you would use a custom kernel then trying to go back to stock.
Did you flash the new custom kernel before you ran into the bootloop? If so, I'd try booting it up bone stock and see if you can get it going that way. Then make one mod at a time and see what's causing the issue.
hayzooos said:
I haven't been modding my N6 much at all, but I do remember reading something about when using custom kernels. I cannot remember exactly what it was, but there was an issue when you would use a custom kernel then trying to go back to stock.
Did you flash the new custom kernel before you ran into the bootloop? If so, I'd try booting it up bone stock and see if you can get it going that way. Then make one mod at a time and see what's causing the issue.
Click to expand...
Click to collapse
That would force encrypt it again.
But the way is to back to stock as much as possible. No root, no custom kernel, factory reset. The only thing needed is a modified stock boot.img with the fstab changed to encryptable.

lineage or google stock rom?

i know twrp is still in testing but is anyone working on lineage or maybe porting over the google edition rom thats on the x4? just surprised to see very little development. i know the a/b partition scheme can be a PITA.
I have started vendor bringup, and know of a few others who are planning build once the tree is up.
TWRP has been ready for flashing ROMS since day 1... just struggles with *stock* decrypt. But with custom ROMs we can choose how to handle encryption.
I have everything except the META-INF for a flashable debloated stock ROM... kind of lost interest since 8.0 dropped but maybe will revisit
mightysween said:
I have started vendor bringup, and know of a few others who are planning build once the tree is up.
TWRP has been ready for flashing ROMS since day 1... just struggles with *stock* decrypt. But with custom ROMs we can choose how to handle encryption.
I have everything except the META-INF for a flashable debloated stock ROM... kind of lost interest since 8.0 dropped but maybe will revisit
Click to expand...
Click to collapse
thanks man. ive tried the twrp and it doesn't seem to flash any zips for me, as in it flashes but when i boot into android it doesn't appear it was successful.
a stock google rom would be killer for this device.
fix-this! said:
thanks man. ive tried the twrp and it doesn't seem to flash any zips for me, as in it flashes but when i boot into android it doesn't appear it was successful.
a stock google rom would be killer for this device.
Click to expand...
Click to collapse
Weird... I have flashed dozens, probably hundreds of zips and images with no trouble. What kind of zips did you flash? Assuming you are unencrypted.
Grab a recovery log and I will take a look.

Categories

Resources