After waiting over a year for the Nougat update (still nothing) and almost a year for a security patch (nothing since Dec 2016), and now knowing Moto will probably never patch the KRACK wpa2 bug, I'm officially done with Motorola and their carelessness with our security.
My questions:
I assume if I load a custom ROM, I will be able to stay up to date with patches and new Android versions? True?
Which one do you all recommend?
Edit: A solution which can pass Safetynet is HIGHLY preferred
I don't need anything fancy, I just want everything to work properly like the stock ROM, but be able to stay up to date
I don't even need root, as in the past I've had some apps stop working if I was rooted, although with systemless root, that night not be a problem anymore. I guess it would be nice to be able to root if desired, but have it as an option only.
Edit- probably should have mentioned I'm on the US Moto X Pure Edition (XT1575)
Thanks for any help.
xdafan15 said:
After waiting over a year for the Nougat update (still nothing) and almost a year for a security patch (nothing since Dec 2016), and now knowing Moto will probably never patch the KRACK wpa2 bug, I'm officially done with Motorola and their carelessness with our security.
My questions:
I assume if I load a custom ROM, I will be able to stay up to date with patches and new Android versions? True?
Which one do you all recommend?
I don't need anything fancy, I just want everything to work properly like the stock ROM, but be able to stay up to date
I don't even need root, as in the past I've had some apps stop working if I was rooted, although with systemless root, that night not be a problem anymore. I guess it would be nice to be able to root if desired, but have it as an option only.
Edit- probably should have mentioned I'm on the US Moto X Pure Edition (XT1575)
Thanks for any help.
Click to expand...
Click to collapse
First off it's a 2 year old phone. That's a normal end of update cycle. Second the 7.0 update is out for the 1575 but for some reason only Sprint Sims seem to have gotten it so far. It's still coming to your phone. Custom roms are nice for updates to a point but safety net still doesn't like them if I recall properly. I switched from the pure to a Moto Z play and have loved it. About to get the October security patch and they're already working on Oreo for it. The pure was the last phone before Lenovo took over. There were issues with the hand off but they seem to have it together mostly now.
@xantanion, thanks for your post. I could argue with you about whether the phone was updated on a timely basis over the last 2 years, but I don't want to get into that right now.
Good point about safetynet. If I'm going to go custom ROM, I'd like to be able to pass safetynet, whether by using Magisk, not rooting, using a custom kernel, whatever options are available/necessary.
With this in mind, any suggestions for a solution?
Not getting security patches (my current situation) is not acceptable.
I'd like to squeeze another year out of this phone before replacing. Thanks for any suggestions
xdafan15 said:
@xantanion, thanks for your post. I could argue with you about whether the phone was updated on a timely basis over the last 2 years, but I don't want to get into that right now.
Good point about safetynet. If I'm going to go custom ROM, I'd like to be able to pass safetynet, whether by using Magisk, not rooting, using a custom kernel, whatever options are available/necessary.
With this in mind, any suggestions for a solution?
Not getting security patches (my current situation) is not acceptable.
I'd like to squeeze another year out of this phone before replacing. Thanks for any suggestions
Click to expand...
Click to collapse
I'd switch to Dirty unicorns. I retired this phone a couple of months ago, but they maintain it regularly, and release monthly security patches. As for safety net, magisk works great. Since on Android 7.0 + even an unlocked bootloader trips safety net, then you actually NEED magisk to patch that and then pass safety net. DU is an unrooted ROM but just flash magisk afterwords.
xdafan15 said:
@xantanion, thanks for your post. I could argue with you about whether the phone was updated on a timely basis over the last 2 years, but I don't want to get into that right now.
Good point about safetynet. If I'm going to go custom ROM, I'd like to be able to pass safetynet, whether by using Magisk, not rooting, using a custom kernel, whatever options are available/necessary.
With this in mind, any suggestions for a solution?
Not getting security patches (my current situation) is not acceptable.
I'd like to squeeze another year out of this phone before replacing. Thanks for any suggestions
Click to expand...
Click to collapse
Lineage OS 14.1 (based on nougat 7.1.2) gets security updates monthly. It's close to vanilla android and doesn't come with all the bells and whistles of unicorns or aicp. This is good for those happy with the stock android features like myself. I don't need custom themes and crazy config options. Never needed a custom kernel. Battery and performance is exceptional as is.
https://download.lineageos.org/clark
Rooting with Magisk 14 will pass safetynet. I use android pay daily with no problems.
https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356
I run with a fairly minimal OpenGApps 7.1 arm64 aroma installation. I use the aroma installer and pretty much only check the boxes for a few apps to be pre installed. If I really need something I can grab it from the play store or apk mirror. My base config for OpenGApps aroma is here: https://drive.google.com/drive/folders/0B2lKWOIH0bTqMEQ1cmo2QjlydDA?usp=sharing
https://github.com/opengapps/arm64/...71102/open_gapps-arm64-7.1-aroma-20171102.zip
If the new stock 7.0 nougat release is what you're after you can get a twrp backup here you can restore from. Keep in mind this is 7.0 not 7.1.2 and security patch up to only September 2017. This will be the last update to the Moto X Pure/Style. So no further security patches.
I tried stock 7.0 for a few days but went back to Lineage OS. I missed the long press on icons to get actions menu that isn't in 7.0 (among other things).
Spencervb256 said:
I'd switch to Dirty unicorns. I retired this phone a couple of months ago, but they maintain it regularly, and release monthly security patches. As for safety net, magisk works great. Since on Android 7.0 + even an unlocked bootloader trips safety net, then you actually NEED magisk to patch that and then pass safety net. DU is an unrooted ROM but just flash magisk afterwords.
Click to expand...
Click to collapse
ptn107 said:
Lineage OS 14.1 (based on nougat 7.1.2) gets security updates monthly. It's close to vanilla android and doesn't come with all the bells and whistles of unicorns or aicp. This is good for those happy with the stock android features like myself. I don't need custom themes and crazy config options. Never needed a custom kernel. Battery and performance is exceptional as is.
https://download.lineageos.org/clark
Rooting with Magisk 14 will pass safetynet. I use android pay daily with no problems.
https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356
I run with a fairly minimal OpenGApps 7.1 arm64 aroma installation. I use the aroma installer and pretty much only check the boxes for a few apps to be pre installed. If I really need something I can grab it from the play store or apk mirror. My base config for OpenGApps aroma is here: https://drive.google.com/drive/folders/0B2lKWOIH0bTqMEQ1cmo2QjlydDA?usp=sharing
https://github.com/opengapps/arm64/...71102/open_gapps-arm64-7.1-aroma-20171102.zip
If the new stock 7.0 nougat release is what you're after you can get a twrp backup here you can restore from. Keep in mind this is 7.0 not 7.1.2 and security patch up to only September 2017. This will be the last update to the Moto X Pure/Style. So no further security patches.
Click to expand...
Click to collapse
Thanks, @Spencervb256, for the recommendation and comments on Safetynet and security patches.
Double thanks, @ptn107, for the helpful recommendations and files. I really appreciate you sharing that info.
If you'll continue to put up with my ignorance, do I correctly understand how to restore to stock if I choose to do so later as listed below. I'm still on MPHS24.49-18-16. I didn't update to 7.0.
1) According to this thread, the MotoX Pure can only be returned to the stock firmware it was running before switching to a custom ROM, or to a newer version. You cannot go back to an earlier version.
2) There isn't a firmware .zip available for 24.49-18-16, so according to this post, you flash the 24.49-18-8 .zip (which IS available) and then sideload the .zip from @annoyingduck to update to 18-16 to get back to where you started.
3) Alternately, since the file for Nougat 7.0 is available, I could also update to 7.0, then load a custom ROM, and later return to 7.0 using the available file.
Am I understanding this process correctly?
Thanks in advance for your help.
xdafan15 said:
Thanks, @Spencervb256, for the recommendation and comments on Safetynet and security patches.
Double thanks, @ptn107, for the helpful recommendations and files. I really appreciate you sharing that info.
If you'll continue to put up with my ignorance, do I correctly understand how to restore to stock if I choose to do so later as listed below. I'm still on MPHS24.49-18-16. I didn't update to 7.0.
1) According to this thread, the MotoX Pure can only be returned to the stock firmware it was running before switching to a custom ROM, or to a newer version. You cannot go back to an earlier version.
2) There isn't a firmware .zip available for 24.49-18-16, so according to this post, you flash the 24.49-18-8 .zip (which IS available) and then sideload the .zip from @annoyingduck to update to 18-16 to get back to where you started.
3) Alternately, since the file for Nougat 7.0 is available, I could also update to 7.0, then load a custom ROM, and later return to 7.0 using the available file.
Am I understanding this process correctly?
Thanks in advance for your help.
Click to expand...
Click to collapse
I'm not extremely knowledgeable on the whole returning to stock unfortunately...but if you're currently on 6.0, almost all the custom roms are compatible with that firmware, and only a SELECT FEW (such as a lineage os test build) are compatible with the newer 7.0 stock firmware. Paging @dzidexx for a better explanation
Spencervb256 said:
I'm not extremely knowledgeable on the whole returning to stock unfortunately...but if you're currently on 6.0, almost all the custom roms are compatible with that firmware, and only a SELECT FEW (such as a lineage os test build) are compatible with the newer 7.0 stock firmware. Paging @dzidexx for a better explanation
Click to expand...
Click to collapse
Thanks again, @Spencervb256.
So you're saying that the Android version of my custom rom has to match the version of the stock rom that I'm coming from? No mixing marshmallow and nougat?
Also, if I stay on marshmallow and want to return to stock and unroot, I wonder if I can just flash the available nougat firmware and restore the stock recovery. Maybe @dzidexx can help with that question, too.
Wish I was more skilled in all this. Thanks for the help.
xdafan15 said:
Thanks again, @Spencervb256.
So you're saying that the Android version of my custom rom has to match the version of the stock rom that I'm coming from? No mixing marshmallow and nougat?
Also, if I stay on marshmallow and want to return to stock and unroot, I wonder if I can just flash the available nougat firmware and restore the stock recovery. Maybe @dzidexx can help with that question, too.
Wish I was more skilled in all this. Thanks for the help.
Click to expand...
Click to collapse
No haha it's hard to explain. But until about a month ago, no custom roms could be flashed if users were running stock 7.0 from Moto. Now there are a couple builds of roms which can be flashed over stock 7.0, with no bootloops. This is because Motorola upgraded the modem firmware in stock 7.0, so the custom roms did not work with it.
You can 100% mix the two, so if you are in stock 6.0, you can install any rom you like, as they are made to work with the 6.0 firmware. Even though they are nougat roms.
When stock 7.0 was released, people had issues with installing custom roms over that, because of the modem upgrade, but now there are a couple builds that will install over this firmware and not result in a bootloop.
I will try and find a few links for you which can explain some things, this is all from my mediocre memory haha
If that confused you even more then just stay tuned, I'll send you a pm soon with links to some reading in different threads which explain it much better than I can!
@Spencervb256, I think I understand you. Most of the custom ROMs, whether MM or N, use the stock radios released with MM. When Moto updated to N, they also changed the cellular radio, so the custom ROMs don't work properly unless they are updated to be compatible with it.
So then, if I stay on MM, I can use any custom ROM, if I would've updated, I'd be limited to the few ROMs that were updated.
xdafan15 said:
@Spencervb256, I think I understand you. Most of the custom ROMs, whether MM or N, use the stock radios released with MM. When Moto updated to N, they also changed the cellular radio, so the custom ROMs don't work properly unless they are updated to be compatible with it.
So then, if I stay on MM, I can use any custom ROM, if I would've updated, I'd be limited to the few ROMs that were updated.
Click to expand...
Click to collapse
Pretty much...
xantanion said:
First off it's a 2 year old phone. That's a normal end of update cycle. Second the 7.0 update is out for the 1575 but for some reason only Sprint Sims seem to have gotten it so far. It's still coming to your phone. Custom roms are nice for updates to a point but safety net still doesn't like them if I recall properly. I switched from the pure to a Moto Z play and have loved it. About to get the October security patch and they're already working on Oreo for it. The pure was the last phone before Lenovo took over. There were issues with the hand off but they seem to have it together mostly now.
Click to expand...
Click to collapse
aybarrap1 said:
Pretty much...
Click to expand...
Click to collapse
My rule of thumb is simply wait for the official supported OS version. This means everything (including modem) will work - the community will then hack and modify from there.
xdafan15 said:
@Spencervb256, I think I understand you. Most of the custom ROMs, whether MM or N, use the stock radios released with MM. When Moto updated to N, they also changed the cellular radio, so the custom ROMs don't work properly unless they are updated to be compatible with it.
So then, if I stay on MM, I can use any custom ROM, if I would've updated, I'd be limited to the few ROMs that were updated.
Click to expand...
Click to collapse
That's exactly it! You nailed it. Explained it better than I could, so yeah, you got it!!
Related
Hi guys,
Not sure if this is the right place to post this but unless I am missing something, I have yet to find a thread or instructions on how to do this.
I am on Pure Nexus, but I posted here because I'm guessing the answer applies to virtually any custom ROM. What are the steps involved in upgrading from a custom 6.0 ROM to the newly released Android 7.0? Is there a way to do this while keeping root?
Thanks,
speedemonV12 said:
Hi guys,
Not sure if this is the right place to post this but unless I am missing something, I have yet to find a thread or instructions on how to do this.
I am on Pure Nexus, but I posted here because I'm guessing the answer applies to virtually any custom ROM. What are the steps involved in upgrading from a custom 6.0 ROM to the newly released Android 7.0? Is there a way to do this while keeping root?
Thanks,
Click to expand...
Click to collapse
There's roms you can flash, other than that just wait for the images to release and there will be alot options
So if it's a custom ROM based on 7.0 I can go ahead and flash using that specific ROM instructions?
I thought the official 7.0 came out yesterday, that's why I was wondering if I could update to the official and keep root and how to do that.
speedemonV12 said:
So if it's a custom ROM based on 7.0 I can go ahead and flash using that specific ROM instructions?
I thought the official 7.0 came out yesterday, that's why I was wondering if I could update to the official and keep root and how to do that.
Click to expand...
Click to collapse
I'd Mae a backup send it to PC and try tupac4us rom or digitalhighs . They have vendors built in the zip .
I was on Benzo rom and this is exactly what I did; I restored back to stock rom only leaving bootloader unlocked. I joined the Android beta and the N ota was ready to install. I then flashed the latest twrp. I made sure to do a full nandroid and physically backed up anything important to my laptop before I restored to stock. I noticed until I flashed ditialhighs N rom my twrp would not "stick" but no big deal I just flashed it and went into recovery. It seems Android Pay is working with digitialhighs rom, you just toggle off root, use it, toggle back. Good luck
Which guide did you use for restoring to stock while keeping the bootloader unlocked?
i was on pure nexus 6.1 i used this guide to revert everything back to stock then i subscribed to the developer program and got 7.0 update in seconds, section 14 is pretty much all you need
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Scanning the forum today, I came across this:
[ROM] Z.A.D.Mix7 -Stock Base Rom-
Click to expand...
Click to collapse
It looks like it would solve all the issues I'm having with my A7:
Enable multi-user mode
Enable on-screen buttons
Replace ZTE's built-in apps.
Is this a safer route to go in general than installing Cyanogenmod (when it's ready)? I've got CM on my Nexus 4, and yes, there's nice stuff there that's probably not here, but is a de-bloated stock ROM more likely to be bug-free? More likely for the camera and sound system to work fully? Also, will a debloated ROM allow for OTA updates - or allow for them to be sideloaded? I guess I'm asking, if I were to install this, what would be the procedure to get Nougat once ZTE comes out with it? Wipe and re-flash? Or wait for a de-bloated ZTE nougat ROM and flash that?
In order to flash a ROM on your axon 7 you need to unlock your bootloader which causes your warranty to be void and you can no longer receive OTA updates. Also if you are running a custom ROM you will have to wipe your phone before flashing an OTA update. However if you are running the stock rom you will probably only need to flash the update. I've tried both CyanogenMod and Z.A.DMix7 and honestly Z.A.DMix7 is definitely the way to go. In my experience using Z.A.DMix7 it seemed to be as stable as the stock rim and didn't have any major bugs. The only problem I had with it is that since it it rooted there is no way to log into Snapchat. How ever if you don't want root I think there may be an way to remove root from the ROM however I haven't tried it so I'm not sure if it'll work.
I use the debloated rom with android n-ify, xStana, and gravitybox and it is much better than the stock rom. I haven't tried the cm rom. You would have to flash the stock rom and recovery to get OTA updates.
Hello,
It's been almost a little over a year since I was last really into android customization. Since it's been so long it has become clear to me that my phone is outdated in many ways. I'm still running OxygenOS 2.2.1 with Android 5.1.1. I've been wanting to update up to Android N (7.x.x) for a long time now, but haven't seen any real stable roms or haven't really had the time to look for one. Now I've finally found my self with free time and ready upgrade my rom. I've just faced couple of problems, I can't really find what should I do when upgrading from 5.1.1 to 7.x.x since no-one is really doing that anymore. I remember reading sometime back that if you dont have the right firmwares you'll brick ur phone, and I wouldn't really want to go through that hassle at the moment. Is it still a thing or should it be just fine for me to flash a new rom just on top of this? (Ofc with clearing memory etc) Other question that is in my mind is that is there any critical bugs in Android N roms? It's bit unclear to me since there are such many roms that have their status as work in progress or beta etc, but some roms have status as stable. Are there any roms that I should clearly avoid? Im not new to this so I don't really need any deep info how to do everything etc, just a bit of a oversight on how things are going atm.
Thanks.
first of all is ur device rooted?? If yes then install the latest twrp recovery...then take a backup.. and flash any nougat rom which u like...If at all u would need Volte support then u l have to flash the 3.5.7 firmware..or else the 3.1.0 firmware works fine with most of the nougat roms..some nougat roms i would recommend are AICP, Resurrection Remix and AOSP extended .... In my suggestion u should probably first upgrade the Oxygen Os on ur device through official updates via OTA atleast upto the 3.5.6 firmware
there's no need to update until 3.5.6, unless you aren't going to plan staying with OOS [the only "stable" firmware which provides you VoLTE working, but it's still M-based and not N].
as @mhd athiq said, unlock your bootloader [just in case you still haven't done it before] then update your TWRP recovery to the latest version.
then flash the incrementals OTAs until OOS 3.1.x and you are good to go to flash any custom ROM which is N-based.
to avoid any mistake, please make a EFS backup via terminal [just to have a backup of your modems] and save the files to a safe location.
I don't have a specific ROM to suggest to you, but in my experience I have found the CAF/AOSP-based ones to be the ones with the best battery backup and less bugs then LOS-based ones.
I have used happily for a few months CypherOS version 3.5.1 [not the latest one, I find it quite unstable as the developers tried to implement OMS].
sidenote:
flashing N-based custom ROMs upon OOS 3.5.6 firmwares gives random reboots and unstable network in many cases/scenarios.
so don't update to that OOS version unless you have a mandatory VoLTE feature required [but you'll have to live with random reboots and poor network stability].
I seem to remember reading something some weeks ago that Samsung did something in their latest few updates for the S8+ that made it impossible to root them... is that true?
I'm running a SM-G955F - DTM here... and I'd rather keep it rooted. I'm using magisk to root my devices.
Any insights for me?
AFAIK, as long as if you have twrp installed, you can update to whatever you want.
you then can:
make a full backup with TWRP, and Samsung can't do anything against you just restoring the full backup (with the old update and root)
just flash whatever (custom)ROM you want.
You already are rooted, so OTAs aren't a thing for you. I don't know if there even exists a twrp flashable stock ROM, but why don't you just switch to a custom rom (with the newest updates installed)?
Honestly, the only custom rom i know of is lineage (nee cyanogenmod), and at least on my old S5 I found that the fingerprint reader does not work on cyanogenmod. also, anything that checks safetynet does not work either.
[Lemmy] said:
Honestly, the only custom rom i know of is lineage (nee cyanogenmod), and at least on my old S5 I found that the fingerprint reader does not work on cyanogenmod. also, anything that checks safetynet does not work either.
Click to expand...
Click to collapse
LieangeOS isn't even available for our device (infact it is, but unusable).
The custom roms available right now are all stock touchwiz roms with slight modifications (most of them aren't even necessary, thx to aroma).
Look over to a thread like the one from Renovate ICE, most of the time roms like these are based on the newest sources from Samsung with the newest security patch level. It has root (Magisk or SuperSu) included and also passes safetyNet.
As I said in the post above, you always can make a full twrp Backup, try a ROM like Renovate Ice and if you don't like it, just go back to your stock ROM in minutes. :fingers-crossed:
What you guys suggest!? I want to root my Phone but I am waiting for The Oreo Update
Should I wait Further or not!?
Personally I was wondering the same, but decided a week or so ago to unlock the bootloader and install lineage 14.1. Happy with my decision, it actually fixed a bug I had with NFC only working occasionally. Also good to be able to use my root apps again. I won't upgrade to Oreo until after the official Oreo release and developers have had a chance to fix the issues there seems to be with Bluetooth calling, votle, imei, etc.
So my answer would be sure go ahead, as long as you know what you're doing it for and understand the risks.
I agree with NZedPred, nothing wrong with rooting and installing custom rom, but I wouldn't install any Oreo rom until/if official Oreo for this device gets released. Just too many problems.
Same here waiting for Oreo before root
Rutambh said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post76427271
Click to expand...
Click to collapse
If you can fix the various common problems that may come with custom ROMs, go ahead. Otherwise, you could stay stock and wait for the update. It all depends on you if you want to have the latest Oreo (8.1 and the latest security patches).
If you just want to root, it's fine too but you'll still lose warranty.
Not sure, i have zero problems on ResurrectionRemix Oreo.
I was thinking the same and now i'm glad that i did it. RR working like a champ.
some custom rom are stable and u can use for daily driver
I'll wait. There's nothing revolutionary about Android 8, the custom roms are almost always buggy, and also all these reports of IMEI 0 are troublesome.