Do custom rooms on nougat update the mod platform to 1.6? - Moto Z Questions & Answers

Planning to get a new moto z from a carrier since theybare having a sale and not charging anything for the phone. Fiancé is planning to switch to that carrier anyway since her workplace and is switching all phones to it.
I liked the idea of the moto mod and was thinking of getting the new turbopower pack by Motorola instead of the incipio one. I read that the turbopower requires the moto mod platform to be at 1.6 for it to work. I believe the nougat update brings the platform to 1.6 right?
At the same time, I want to use custom roms on this phone and I read that going to official stock nougat updates the bootloader and brings problems to custom roms. So my question is, can custom roms update the mod platform to the latest while keeping the bootloader on marshmallow? Can we flash nougat custom roms while on marshmallow bootloader with no problems?

Related

[Q] Will newer versions of the stock android be available?

Hi,
I rooted my gs4 (MDK) Kernel because I didn't want to accept the update and not have the option to do what I want with my phone. However, I like the stock ROM and like the features of TouchWiz. As new versions of Android (4.3 and eventually Key Lime Pie) come out, will I be able to flash stock roms with touchwiz from this site, or will i have to wait around for Verizon to come out with an official release?
Is 4.3 available anywhere now?
thefederer said:
Hi,
I rooted my gs4 (MDK) Kernel because I didn't want to accept the update and not have the option to do what I want with my phone. However, I like the stock ROM and like the features of TouchWiz. As new versions of Android (4.3 and eventually Key Lime Pie) come out, will I be able to flash stock roms with touchwiz from this site, or will i have to wait around for Verizon to come out with an official release?
Is 4.3 available anywhere now?
Click to expand...
Click to collapse
Yes, most likely you will be able to flash pretty much all versions of android as long as the device is compatible. There are a lot of great devs out here who develop TW roms and AOSP roms. To answer your second question, there is a 4.3 rom floating out there somewhere but it doesnt work on our phone.

[Q] How can I update to 5.1?

I live in Colombia, and the OTA will probably take months to come. The recent apps bug has drove me up the wall, and I've read that the 5.1 update fixes the bug, aside from making the device faster. I don't want to lose the Moto Display, so I don't want to flash a custom ROM. I want to know, can I flash a stock rom with TWRP as if it were any other rom? Does the fact that the rom is for retail US phones make it unusable with Colombian carriers? Do you think it's worth to flash a custom ROM, even if it means I won't be able to use Motorola apps?

What's the best way to return to a fully stock firmware?

It's me again.
I've been seeing the development community of the Moto Z starting to pick up after the release of the Nougat source code, evident by the release of an unofficial build of LineageOS 14.1 and the rather quick pace of updates.
However, that ROM was built on the Nougat source code and while it was stated that it might work on Marshmallow bootloaders, it's not expected to be as stable.
You might know by now that my Moto Z is running the RETMX Nougat firmware but on the Marshmallow bootloader (this is done so that if anything goes wrong, I can easily go back to Marshmallow) with TWRP and systemless root via Superuser. However, with this new development, I am considering going back to full-stock and having the Nougat bootloader before flashing LnOS. I have no plans to flash it anytime soon, but I may do so after 1.5 years when official support for the Z will wind down.
So my questions for you guys now are as follows;
1) If an update comes out, would it make sense to just flash the entire factory image since I want to return to full stock?
2) What's the best way to do it? ADB or RSDLite? I used both and didn't have an issue with both, but I do prefer RSD's easier method, although I didn't use that to flash the N image as it would also update the bootloader (something I did not want at the time).
3) Would you recommend flashing the newest version of the software or simply flashing the oldest supported version by the bootloader and then accepting the OTA?
4) Would doing any of the specified methods relock the bootloader? (Hopefully not)
Thanks and I hope to get a good reply soon.

Stable rom 6.0+?

I just picked up a refurbished Moto E2 (Surnia) for ATT/Cricket, and I rather like it aside from the limited internal storage. Would love to flash a ROM that allows adoptable storage via SD card, but read some things about Nougat roms having issues with bluetooth and other little nagging bugs on some ported devices. Would love to stick with Marshmallow or anything stable enough for a trouble-free experience. I'm not necessarily looking for latest-and-greatest, if this phone shipped with Marshmallow, that'd be good enough for me honestly. Just need to move past Android 5.1 here.
Should I try to dig up an antiquated CM13 rom image? Seems like official links have been pulled in honor of lineage OS. Is LineageOS stable enough? Should I try that first?
Basically you have an AT&T device, which is unauthorized for bootloader unlocking, therefore flashing any custom ROMs is impossible. You're pretty much stuck with stock 5.1 firmware.
Oh well that just stinks. I already had a VZ Moto E2 that I've been using in GSM thanks to the tweaks for that, but was annoyed that I'm stuck on 5.1. Had an opportunity to grab the xt1527 for 99cents refurbished at Cricket, and figured I could replace it with this one and flash Marshmallow.
Fantastic. Now I have two Moto E2's with locked bootloaders.
Wasn't there an official 6.0 ROM that Moto released in markets other than US? Would I be able to flash that on my Xt1527 with a locked bootloader since it is an offically signed ROM, or will it reject?
Short answer, I presume it's not possible to flash the firmware released for a different phone variant, the phone's CID must correspond with its designated firmware.
I'm not 100% sure though, never had a phone with a carrier locked bootloader.

Confusion around Firmware versions for Custom ROMs

Hi all,
I recently purchased a Poco F1 and am planning a trajectory for flashing a custom ROM and kernel when the limit expires on unlocking. However, I'm having issues following what is the latest firmware, or MIUI version, or Android release for the unit. Let me explain:
This unit came with a MIUI 9 version that promptly got a two-step OTA to MIUI Global 10 10.0.6.0(OEJMIFH). It is running Android Oreo (8.1.0).
However, discussion in custom ROM threads as late as this week refer to MIUI 10 8.13.x builds and betas being the most recent firmware, and advise to use these firmwares that are based on Android Pie as the base for flashing custom ROMs based on Pie. Despite the older MIUI version number, the Android version is newer.
In addition, there are complaints around the touch performance of this device when using 8.12.x or earlier firmwares that I am not experiencing with this 10.0.6.0 firmware, and I don't want to introduce issues in the process of preparing this unit for a custom ROM.
Basically, I'm not sure what my trajectory should be if I wish to use a MIUI beta ROM, or if I wish to flash something like LineageOS while retaining or updating the touchscreen firmware appropriately. Can I simply unlock the bootloader, flash TWRP, then flash a custom ROM as I have done in the past on other devices? Can I update the touch firmware separately?
Any help would be much appreciated, thanks.
Crayphish said:
Hi all,
I recently purchased a Poco F1 and am planning a trajectory for flashing a custom ROM and kernel when the limit expires on unlocking. However, I'm having issues following what is the latest firmware, or MIUI version, or Android release for the unit. Let me explain:
This unit came with a MIUI 9 version that promptly got a two-step OTA to MIUI Global 10 10.0.6.0(OEJMIFH). It is running Android Oreo (8.1.0).
However, discussion in custom ROM threads as late as this week refer to MIUI 10 8.13.x builds and betas being the most recent firmware, and advise to use these firmwares that are based on Android Pie as the base for flashing custom ROMs based on Pie. Despite the older MIUI version number, the Android version is newer.
In addition, there are complaints around the touch performance of this device when using 8.12.x or earlier firmwares that I am not experiencing with this 10.0.6.0 firmware, and I don't want to introduce issues in the process of preparing this unit for a custom ROM.
Basically, I'm not sure what my trajectory should be if I wish to use a MIUI beta ROM, or if I wish to flash something like LineageOS while retaining or updating the touchscreen firmware appropriately. Can I simply unlock the bootloader, flash TWRP, then flash a custom ROM as I have done in the past on other devices? Can I update the touch firmware separately?
Any help would be much appreciated, thanks.
Click to expand...
Click to collapse
If you flash a custom ROM over what you have (Oreo), you will retain the existing firmware & modem. If it is compatible with the ROM flashed, you will not have any issues.
It is possible to flash firmware & modem alone at any time if it is available separately.

Categories

Resources