Related
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/
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.
I have quite an old version of Android on my Nexus 6 (see attached). Is it safe to flash or fastboot to a 7.0 or 7.1 build without wiping? I am on rooted Project Fi. I don't necessarily need to keep root (though I prefer it for tap-to-wake), but I do need Project Fi compatibility since that is my carrier. Thank you!
You are going to have to wipe data and cache, flash bootloader and radio, and then you are clear to go to 7.0 or 7.1! *project FI is not a custom rom thing, its going to work now with any rom! Root is as easy is reflashing SU when done with upgrade, if you want root again.
While you probably can receive OTA updates until you get to Android 7.0, there's no guarantee that you'll get the required updates. Flashing one of the OTA images from the Google Developer website will get you there a lot quicker. But you want to back up your internal storage onto your PC before applying the OTA. Since there is a bootloader update involved, your device may end up wiped.
Darn. Can you link me to whichever bootloader, radio, and build would be best for me to use? I just want the base stock Project Fi build, so I'm not sure if I should get the Google build, or one in the dev forum.
I cannot utilize OTA updates: I click install, it reboots, and fails. Hence why I have been on 5.1 for years. I just haven't had the time (or desire) to do all of this manually. How should I go about the upgrade process? I understand the process of fastboot and all that (though it has been a while), but I need a little guidance on which file (or files) to use and where to download them. Any pointers on which website and which download(s) would be much appreciated, whether it is the official google file, or I need other files as well, etc.
This is a link to the 7.0 bootloader and radio, both flashable! http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
This is a link to a stock (project fi ready) 7.0 build, with radio / bootloader/ rom / gapps / everything. Perhaps it would be easier just to do this writeup! http://forum.xda-developers.com/nexus-6/general/android-nougat-nbd90z-flashable-image-t3474572
Excellent thank you. Regarding the second link:
a) This will work for 5.1 and a very old version of TWRP correct?
b) Also, what is the purpose of making a backup if this will wipe the storage anyway?
Of course it fails. OTA updates require the stock recovery to work. Had I known you had TWRP installed I would have had you flashing the factory image using fastboot.
a) no, while it may work, You should definitely update your version of TWRP
b) You aren't going to wipe your internal storage if you use TWRP. that's only when you're flashing via fastboot
If you use TWRP, you can wipe the system, data, and cache without touching your files. just dont' wipe internal storage
Yes. I do have TWRP. In that case, do you agree with the other post that the following link is the best upgrade path? http://forum.xda-developers.com/nexus-6/general/android-nougat-nbd90z-flashable-image-t3474572
Ohhh I see. My eyes immediately skipped to the "Method 2" content.
a) So I should first update TWRP, and then perform "Method 1" in that post, correct? Just want to make absolutely sure of the steps.
b) In the case that Method 1 is correct, since my data would remain, will my phone be wiped or not?
Yes.
It worked! I am now proudly on 7.0 without wiping!!! Thank you!!!!!! How do I mark this as the answer? Woohoo!!!
P.S. In case this should help anyone else (or maybe help myself in the future), I updated TWRP though the "TWRP Manager" app, did a full backup of the phone (took 822 seconds), then flashed that zip in that other thread. So far so good!!!
Woot!
I've tried to look for the sultan otas but haven't found so if I just flash the whole ROM I should be fine right? Is there some other way to get the OTA from the updater if that deletes stuff?
Escabrera said:
I've tried to look for the sultan otas but haven't found so if I just flash the whole ROM I should be fine right? Is there some other way to get the OTA from the updater if that deletes stuff?
Click to expand...
Click to collapse
You'll be fine. What you're doing is called dirty flashing. It's not always the most stable thing to do especially if subsequent versions have significant changes, but if the update is just adding things like security patches and minor bugs, go ahead. Be aware that it's best to clean flash, or wipe the system partition because there will be no chance of conflicting code. Even if you're unsure if flashing a whole ROM would delete data, you can always just make a backup on TWRP. In fact, always make a backup before doing something like this.
Inflection said:
You'll be fine. What you're doing is called dirty flashing. It's not always the most stable thing to do especially if subsequent versions have significant changes, but if the update is just adding things like security patches and minor bugs, go ahead. Be aware that it's best to clean flash, or wipe the system partition because there will be no chance of conflicting code. Even if you're unsure if flashing a whole ROM would delete data, you can always just make a backup on TWRP. In fact, always make a backup before doing something like this.
Click to expand...
Click to collapse
It's just that I'm getting Google play services crashes constantly and 2 patches ago it wasn't happening so I'm trying to reflash the newest release. So I'll probably do a TWRP back up first. Does it also back up stuff like downloads and files on the phone?
Escabrera said:
It's just that I'm getting Google play services crashes constantly and 2 patches ago it wasn't happening so I'm trying to reflash the newest release. So I'll probably do a TWRP back up first. Does it also back up stuff like downloads and files on the phone?
Click to expand...
Click to collapse
You should probably also be reflashing the gapps as well since you are having issues with play services. In the case of TWRP, it doesn't back up files on the phone; rather it backs up the system partition, data (excluding storage), and some other optional stuff. Even if you were to clean flash, you wouldn't need to worry about your files (that is in the partition Internal Storage) because you almost never need to wipe media. A clean flash only requires you to wipe Dalvik, system, data, and cache. What you're doing is dirty flashing, where you wipe nothing and flash your zips over the existing ROM. The backup is just insurance in the instance that something goes wrong and you soft brick the phone.
i tried to flash it again and old updates with the issue still being there so i just nuked everything. I'm just going to use titanium backup plus having the files on a computer to get back to where i was before.
AS OF RIGHT NOW THIS IS ONLY FOR T-MOBILE AND NOW SPRINT!
This is a stock rom for the retail brazil MotoZ(2) force ported over to our phone.
This is stock with only encryption and dm verity removed for support with twrp. (No more boot image including.)
Flashing instructions.
NOTE: CLEAN FLASH! This is a rom from another phone. I cant help you if you write me and say system fc's or any other fc's and you didnt clean flash.
1. Download rom and place it on sd card or internal.
2. Download oem.img and flash it (fastboot flash oem oem.img)
3. Reboot to recovery
2. Wipe system data cache.
3 Flash rom.
4. Reflash whatever root you had. (Magisk)
5. Profit.
As far as I know this does have all the latest fixings (KRACK,Bluebourne, ECT)
Includes VOLTE
Includes WIFI Calling
Usually all roms are pretty stable. IF there is any bugs post below and ill get to working on it.
Sprint install guide
Guide for Sprint users:
Go into Bootloader
Flash This oem.img (courtesy @joemossjr) "fastboot flash oem oem.img
Go into recovery
wipe system and data.
Flash rom
Tested this on my Sprint phone and everything works just fine and with Pantheon, you will pass Safetynet if you flash the image in bootloader.
note: for Sprint users, we NEED to flash the oem.img to not have dialer issues, so I will stress, flash that oem image and if you don't want the bloat, you can delete everything but oem.prop from /oem folder through root or recovery's file manager after you mount OEM.
FLASH ALL
Flash all has been made this includes T-Mobiles Modem with stock everything else. you wont be able to take otas on it due to modified Modem. But updates for thes roms come a lot faster then ours so when one comes out ill update it. Please flash the latest twrp. This is going to encrypt you so your gonna have to format data in twrp and flash this Unencrypt Zip
This will format data. Treat it as a flash all to get back to stock also if you dont want tmobile bloat. This rom in it self with twrp will pass safetynet without magisk as long as you dont modify oem partition. Other then that happy flashing. Download for flash all is below
Downloads: November
oem.img
November Flash all
CREDITS
Motorola Firmware Team
@SuperR. for providing a bad ass platform for Rom making.
@Uzephi for testing the Sprint side of things lol
First! ?
Pantheon works on this rom.
Edit: kernel upstream has KRACK and blueborne fixes in it ?
Edit: tried same install instructions. Works for Sprint phones and activates them
Edit 3: well had to do some dialer stuff, but everything else worked. Will give guide in the morning to get the rom 100%
Sprint install guide
Guide for Sprint users:
Go into Bootloader
Flash This oem.img (courtesy @joemossjr) "fastboot flash oem oem.img
Go into recovery
mount oem. (you can delete everything using file manager in /oem besides oem.prop)
wipe system and data.
Flash rom
Tested this on my Sprint phone and everything works just fine and with Pantheon, you will pass Safetynet if you flash the image in bootloader.
Edit: for Sprint users, we NEED to flash the oem.img to not have dialer issues, so I will stress, flash that oem image and if you don't want the bloat, you can delete everything but oem.prop from /oem folder through root or recovery's file manager after you mount OEM.
Edit 2: Wifi Calling will not work, that file is in sprint's OEM partition and it FC's when adding it or using sprint's oem.img, so if you want this rom, I advise WiFi calling will not work until further notice.
updated thread
ADDED Stock oem image
ADDED Sprint support per @Uzephi
joemossjr said:
updated thread
ADDED Stock oem image
ADDED Sprint support per @Uzephi
Click to expand...
Click to collapse
WiFi calling currently doesn't work for Sprint. Technical details: Sprint uses a different WiFi calling setup where a special Google dialer is in /oem to work. If you use this dialer or the included wifi dialer.jar file, it will just continuously FC and you can't do anything. To get Sprint models working we have to use the stock dialer which doesn't work with Sprint's WiFi calling. We will put a poll up to see interest in WiFi calling since this will take a bit of hackery to get working. I want to gauge interest before I take on this task.
My new T mobile Moto Z2 Force still has stock August image on it. I am waiting for my screen protector and case to arrive before I transfer my account to this phone. I am also waiting to unlock the bootloader and root the device. Now, should I flash your new Nov image since I want KRACK and blueborne fixes OR should I first flash the August image first, then upgrade to Nov image.
kendallgreen said:
My new T mobile Moto Z2 Force still has stock August image on it. I am waiting for my screen protector and case to arrive before I transfer my account to this phone. I am also waiting to unlock the bootloader and root the device. Now, should I flash your new Nov image since I want KRACK and blueborne fixes OR should I first flash the August image first, then upgrade to Nov image.
Click to expand...
Click to collapse
Either or honestly lol you can go to August for the updated firmware
So going from a brand new device on NCX26.7, how do we go about getting our phones ready to flash this? Unlock bootloader, root, then flash this and reroot? Then follow the instructions for TWRP in your other post?
swidger said:
So going from a brand new device on NCX26.7, how do we go about getting our phones ready to flash this? Unlock bootloader, root, then flash this and reroot? Then follow the instructions for TWRP in your other post?
Click to expand...
Click to collapse
Unlock bootloader, install TWRP, follow instructions in OP.
Moto Z2 Force Edition - T-Mobile
Unlocked Bootloader
TWRP 3.2.0-0
I keep trying to flash this ROM, and have succeed in the flashing process. However, whenever I boot up, I get "TMOConfig has stopped" and then I can close it. I notice, that cellular data is not active. I continue through setup as normal until the Moto Permissions screen. When I try to go through this screen, whether I accept or decline, "com.motorola.tmo.setupext has stopped" comes up. The only option is to open app again and it takes me to the prior screen for Google setup and gets stuck in this loop until I restart the phone.
I've followed the instructions exactly MULTIPLE times just to verify I got it right. I'm clean flashing as well, so no it's not cuz of that. I've even redownload the files three times just to ensure it wasn't the result of possible file issues. Anyone else having this issue? I'd greatly appreciate a second pair of eyes on this!
champ784 said:
Moto Z2 Force Edition - T-Mobile
Unlocked Bootloader
TWRP 3.2.0-0
I keep trying to flash this ROM, and have succeed in the flashing process. However, whenever I boot up, I get "TMOConfig has stopped" and then I can close it. I notice, that cellular data is not active. I continue through setup as normal until the Moto Permissions screen. When I try to go through this screen, whether I accept or decline, "com.motorola.tmo.setupext has stopped" comes up. The only option is to open app again and it takes me to the prior screen for Google setup and gets stuck in this loop until I restart the phone.
I've followed the instructions exactly MULTIPLE times just to verify I got it right. I'm clean flashing as well, so no it's not cuz of that. I've even redownload the files three times just to ensure it wasn't the result of possible file issues. Anyone else having this issue? I'd greatly appreciate a second pair of eyes on this!
Click to expand...
Click to collapse
you still have OEM stuff - you need to wipe oem partition and then flash.
byt3b0mb said:
you still have OEM stuff - you need to wipe oem partition and then flash.
Click to expand...
Click to collapse
Does formatting help wipe that? I've done wipes and formatting just to be safe
Gotta flash the oem.img then reflash
joemossjr said:
Gotta flash the oem.img then reflash
Click to expand...
Click to collapse
Just tried redoing everything again. I get cellular now, and it boots. But now the phone will randomly freeze after a few minutes and restart
Sorry for being such a noob... This is my first dual partition device I've worked with... I've gotten spoiled with OnePlus and Nexus devices lol
champ784 said:
Just tried redoing everything again. I get cellular now, and it boots. But now the phone will randomly freeze after a few minutes and restart
Sorry for being such a noob... This is my first dual partition device I've worked with... I've gotten spoiled with OnePlus and Nexus devices lol
Click to expand...
Click to collapse
Sorry I meant which slot/ota are you on
joemossjr said:
Sorry I meant which slot/ota are you on
Click to expand...
Click to collapse
To check this, go to TWRP and in the reboot menu it will tell you which slot you're on like the below screenshot of me on slot B
For sprint users, there is a poll to end on dec 8th asking if WiFi calling is a must for your rom. please answer it. I have tried a few methods but all fail. any further would require editing the framework.jar file in oem and some trickery that needs some serious coding done to work correctly. So I will take on the task if enough vote for it. (I do this in my free time for free and if not enough interest is given, I'd rather not waste the time as another update might break it, and it also takes me away from my EAS project which has a lot of interest.)
joemossjr said:
Sorry I meant which slot/ota are you on
Click to expand...
Click to collapse
Mine shows Slot A. Am I correct in assuming that should be Slot B?
champ784 said:
Mine shows Slot A. Am I correct in assuming that should be Slot B?
Click to expand...
Click to collapse
Slot A has less bugs than Slot B. I would stay slot A if you can. I would suggest wiping oem in TWRP, mount oem, wipe oem, then reboot to bootloader and flash the oem img in OP.