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.
Related
...And for the most part, I love it. Or did until the Nougat update. I wanted to like Nougat, but like so many others have reported, it just ruined my tablet. I tried:
Resetting to factory defaults (no effect)
Unlocking the bootloader and going back to the latest Official 6.0.1 build (worked, but wanted to give Nougat another shot, so...)
Installed the latest official Nougat from fastboot (worked for a while, but after a week, it was already starting to slow down, heat up, and crash)
Back to latest official Marshmallow via fastboot (current setup)
I like staying with the official builds for now, but I am open to rooting and going custom ROM. I also wondered what just installing a custom Kernel (ElemantalX?) over top of an official build would do for me? Ideally, I would have NTFS/exFAT support, which I know the custom kernal would do for me.
Thoughts and suggestions? I know this question has been asked before, but it has been a while, and there are now new variables (7 is several updates in, 7.1 is on the horizon, etc.)
Thank you all, love the community!
What you don't like about Nougat?
My phone is currently using VipreOneM9 3.5.0, my Android version is 5.1 Lollipop, and my HTC Sense version is 7.0. My carrier (and thus where I got my phone) is Sprint.
I've rooted plenty, but I've never had to unroot or update, usually by the time I feel the need to upgrade my phone's version it's time to just upgrade my phone anyway. I'd like to upgrade to Nougat, but I'm not sure exactly what I need to do and I want to make sure I don't screw it up and possibly brick my phone. I'm also wanting to upgrade to ViperOneM9 6.0, and since it's such a big jump I was told to just treat it like a new install instead of an upgrade.
Scaevus said:
I'd like to upgrade to Nougat
Click to expand...
Click to collapse
I've been on AOSP for awhile now, did the official HTC Nougat update finally drop for Sprint M9's?
For LineageOS 14.1 builds by @irocevo, you'll need to:
Have, at the very least, an unlocked boot loader
Have TWRP 3.0.3-0 installed
Since you're currently on a Sense ROM, start from scratch (wipe boot, system, data, etc)
Don't forget the Nougat 7.1 GApps for ARM64
Lacedaemon said:
I've been on AOSP for awhile now, did the official HTC Nougat update finally drop for Sprint M9's?
For LineageOS 14.1 builds by @irocevo, you'll need to:
Have, at the very least, an unlocked boot loader
Have TWRP 3.0.3-0 installed
Since you're currently on a Sense ROM, start from scratch (wipe boot, system, data, etc)
Don't forget the Nougat 7.1 GApps for ARM64
Click to expand...
Click to collapse
I'm not sure if it dropped or not, but either way I would actually like to just upgrade in general to whatever my phone has at the moment!
I unfortunately don't have my original OS also, so I can't flash to it. :/
Scaevus said:
I'm not sure if it dropped or not, but either way I would actually like to just upgrade in general to whatever my phone has at the moment!
I unfortunately don't have my original OS also, so I can't flash to it. :/
Click to expand...
Click to collapse
I'm not sure what your preference is when it comes to Sense vs AOSP, but until HTC's Nougat update drops, the very latest that I am aware of is the LineageOS 14.1 I mentioned.
You don't need your original OS for LineageOS.
Scaevus said:
My phone is currently using VipreOneM9 3.5.0, my Android version is 5.1 Lollipop, and my HTC Sense version is 7.0. My carrier (and thus where I got my phone) is Sprint.
I've rooted plenty, but I've never had to unroot or update, usually by the time I feel the need to upgrade my phone's version it's time to just upgrade my phone anyway. I'd like to upgrade to Nougat, but I'm not sure exactly what I need to do and I want to make sure I don't screw it up and possibly brick my phone. I'm also wanting to upgrade to ViperOneM9 6.0, and since it's such a big jump I was told to just treat it like a new install instead of an upgrade.
Click to expand...
Click to collapse
The first thing you should do is install the latest stock update for your device. Then you can upgrade to the latest version of Viper or any other Nougat that has support for Sprint handsets.
Dark Stranger said:
The first thing you should do is install the latest stock update for your device. Then you can upgrade to the latest version of Viper or any other Nougat that has support for Sprint handsets.
Click to expand...
Click to collapse
Go to this thread, in this forum, [RUU][Firmware][Stock Rooted ROM]Sprint HTC One M9 | 3.41.651.41 | Updated 12.14.16. Download the RUU 3.41.651.41. Follow the instructions in the OP. To the best of my knowledge, this is the latest firmware for the Sprint M9. Run the RUU first, then the ROM and everything else.
Completely stock Sprint M9 here - NO Nougat update as yet . . .
davidtm0 said:
Completely stock Sprint M9 here - NO Nougat update as yet . . .
Click to expand...
Click to collapse
Sprint has not released a Nougat rom as of this time, so no there isn't a completely stock Nougat rom. However, I have Sprint HTC M9 and I am running a Nougat rom. Update your firmware to the latest, see a post or two above this. It is critical that you are on the latest firmware. Then after flashing TWRP, go to the HTC M9 thread, not the Sprint M9 thread. There are a couple of different Nougat roms in that thread. I am running the Vipre V6, flashed it a couple of days ago.
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.
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?
Hello,
I have searched a lot on xda and google and didn't find any answer thus far. Maybe somebody knows this.
I have Griffin model 1650-03 I believe. It was running 7.1 stock RETEU. I have unlocked the bootloader, and proceeded to install the 8.0 a whole ago RETUS (I believe it was the december one). Worked fine, installed magisk and it bootlooped. No problem, I'll just install a custom 8.0 ROM (currently RRO), working fin for months, but now, for reasons and mods, I got to install stock. I usually don't use this device, my main is a Google, so I have read countless posts about how dangerous it is to install stock back, devices bricking left and right. I came across an unbricking solution just in case, but sadly that is for nougat faults, oreo is no-go. And all the guides I've found here and on Google are for 7.1 and I'm on 8.1 with feb security patch. I believe I still have the bootloader from that RETUS update.
TLDR, what is a safe way to return to stock from Custom 8.1 rom?
Thanks
I think since the stock rom is 8.0 it might brick your device... Not sure though.
snsone said:
Hello,
I have searched a lot on xda and google and didn't find any answer thus far. Maybe somebody knows this.
I have Griffin model 1650-03 I believe. It was running 7.1 stock RETEU. I have unlocked the bootloader, and proceeded to install the 8.0 a whole ago RETUS (I believe it was the december one). Worked fine, installed magisk and it bootlooped. No problem, I'll just install a custom 8.0 ROM (currently RRO), working fin for months, but now, for reasons and mods, I got to install stock. I usually don't use this device, my main is a Google, so I have read countless posts about how dangerous it is to install stock back, devices bricking left and right. I came across an unbricking solution just in case, but sadly that is for nougat faults, oreo is no-go. And all the guides I've found here and on Google are for 7.1 and I'm on 8.1 with feb security patch. I believe I still have the bootloader from that RETUS update.
TLDR, what is a safe way to return to stock from Custom 8.1 rom?
Thanks
Click to expand...
Click to collapse
Restore the TWRP backup you did for the stock rom, if you didn't do a TWRP backup you should be fine flashing stock rom the same version you had before installing custom ROMs. Remember if you get a brick it means you are most likely downgrading or upgrading (upgrade should be done with OTA and incrementally to stay safe)
Vcek said:
Restore the TWRP backup you did for the stock rom, if you didn't do a TWRP backup you should be fine flashing stock rom the same version you had before installing custom ROMs. Remember if you get a brick it means you are most likely downgrading or upgrading (upgrade should be done with OTA and incrementally to stay safe)
Click to expand...
Click to collapse
Hello, thank for replying,
So I should be fine if I install via fastboot the same stock RETUS I did before going custom. Should I ota over motorola's software or fastboot? Also, can I be able to OTA RETEU over RETUS?
Thank you
snsone said:
Hello, thank for replying,
So I should be fine if I install via fastboot the same stock RETUS I did before going custom. Should I ota over motorola's software or fastboot? Also, can I be able to OTA RETEU over RETUS?
Thank you
Click to expand...
Click to collapse
I would recommend OTA through the device but it's not reversible (once you flash it you can't downgrade because of bootloader upgrade)
Flashing reteu over retus should be fine as long as you are doing it manually and are aware which partitions you are flashing and which you are omitting. I don't recommend this because sometimes it can break certain things like wifi or data signal (especially if you are on stock rom) and doing OTA later through the device can cause errors
Tldr;
If you want to stay on stock rom, flash back to stock then update everything through rom
If you need root or play around with custom ROMs then don't flash anything just reinstall a stock-like custom ROM
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-install-official-oreo-t3768712 this is the guide i've used to update to oreo (which is RETUS and my device is RETEU), then installed RRO. My guess is I have to install all oreo partitions again (I installed all as stated in that guide) and let it do its OTAs. I had no problems with IMEI and signal on RRO.