I'm currently running RR 7.1.2 (Nougat) which failed when trying to install Xposed Framework and I really want to give Xposed a full-fledged go so I'm wondering what marshmallow rom is the most compatible with Xposed with my xt1607 g4. Any help is greatly appreciated. I did some digging and I'm leaning towards CM13, which I understand is no longer supported, but please express your opinions. Thanks!
dave31g said:
I'm currently running RR 7.1.2 (Nougat) which failed when trying to install Xposed Framework and I really want to give Xposed a full-fledged go so I'm wondering what marshmallow rom is the most compatible with Xposed with my xt1607 g4. Any help is greatly appreciated. I did some digging and I'm leaning towards CM13, which I understand is no longer supported, but please express your opinions. Thanks!
Click to expand...
Click to collapse
Stock - works great with Xposed. Why mess around with a custom ROM if going w/Xposed which gives you complete control over everything except (arguably) theming.
Davey126 said:
Stock - works great with Xposed. Why mess around with a custom ROM if going w/Xposed which gives you complete control over everything except (arguably) theming.
Click to expand...
Click to collapse
I first rooted and flashed this phone months ago and have lost the stock rom since (rookie mistake, I know). Is it possible to find it online/is there a repository somewhere? I tried the cyanogenmod 13 and xposed which seemed to work flawlessly until I realized I couldn't make or receive phone calls. Just now got it all figured out and it was most definitely a doozy haha. Still not 100% on what went wrong but ya.
Edit: Just found a debloated/odexed version here on XDA. About to flash it and jump back into this nonsense that I enjoy so much hahaah. Thanks for the suggestion I'm excited to see where Xposed goes on a bare bones rom!
Hello everyone!
I just switched to an Axon 7 after previously using a HTC One M9. I have a few questions to people here that have more experience with this phone model.
- How is sound quality in LOS/CM based ROMs? Is the dolby DAC being used properly in custom ROMs ?
The reason I bought this phone is the headset sound quality, so far I am not dissapointed at all with the stock ROM quality
-Is there a maintained stock ROM?
I am interested in a clean stock ROM that's maybe debloated and tweaked.
-What about root and android O
I noticed the toolkit has an option to "revert to stock". I want to know what are the correct steps to take when the official MiFlavor android O update is live.
I assume I should revert to stock recovery and boot partition (since now my boot is r/w from rooting). is there anything else I should know ?
Thanks a lot in advance for your time reading this !
rzarectha said:
Hello everyone!
I just switched to an Axon 7 after previously using a HTC One M9. I have a few questions to people here that have more experience with this phone model.
- How is sound quality in LOS/CM based ROMs? Is the dolby DAC being used properly in custom ROMs ?
The reason I bought this phone is the headset sound quality, so far I am not dissapointed at all with the stock ROM quality
-Is there a maintained stock ROM?
I am interested in a clean stock ROM that's maybe debloated and tweaked.
-What about root and android O
I noticed the toolkit has an option to "revert to stock". I want to know what are the correct steps to take when the official MiFlavor android O update is live.
I assume I should revert to stock recovery and boot partition (since now my boot is r/w from rooting). is there anything else I should know ?
Thanks a lot in advance for your time reading this !
Click to expand...
Click to collapse
HI, good to know you unlocked and rooted your phone quickly.
The reason i did not take the LOS boat was because of the sound issues. In short : never left stock rom because of Dolby.
For some debloated stock ROMS i can mentioned kenet's ( MiFavor 5 though ) and mine (SLIM version) based on latest B06-stockrom (MiFavor 4, debloated, SuperSu...) : https://forum.xda-developers.com/axon-7/development/rom-slim-version-t3669355
:good:In a couple if days i'm planning to upload my latest AROMA Rom based om B06-SLIM² which can be debloated to zero, and a bunch of stuff you can choose from, but all based on STOCK. So feel free to look into it :cyclops:
Also take a look in Download Center. All the stock roms (for rooted users) are there under Bootstack+Stocksystem. Latest is the B06 version.
I'm trying to maintain all that stuf so all can choose from it
Good Luck !
Thanks so much for your answer!
I assumed the sound quality would be worse on LOS, it was the same situation with HTC and Sense ROMs, you were stuck with Sense if you wanted decent sound quality.
I am very interested in the Aroma ROM, I'll keep an eye out of that, thanks a lot for creating it.
At the moment I am a bit shy to start flashing just 3 days after getting the phone; however I think an Aroma installed ROM is a solid start
Cheers!
I want to be able to take an OTA or SD update if we get official Oreo so stayed stock but the temptation to root and debloat then unroot again is always there.
RobboW said:
I want to be able to take an OTA or SD update if we get official Oreo so stayed stock but the temptation to root and debloat then unroot again is always there.
Click to expand...
Click to collapse
I read an article saying Oreo will come officially in Q1 2018. That could very well be April 2018; that's why I gave in to rooting.
rzarectha said:
I read an article saying Oreo will come officially in Q1 2018. That could very well be April 2018; that's why I gave in to rooting.
Click to expand...
Click to collapse
Maybe.
It gives me a lot of time to work out whether I can go long term on stock ROM.
I don't want hassles with security compatability to use Google Pay and a couple of other apps that check for root.
One reason I won't install ViPER4Android on this phone. As is, it's stock and encrypted. Just as well it has 4Gb RAM because I think it really needs it.
I just went from latest Stock to LOS and honestly I don't hear much difference between them in my music I would say its at least 90% of the quality.
There is a slight distortion on max volume from the speakers. I will see how I like it maybe go back to stock I also bought this phone after an HTC tho mine was the M8 I don't think I will get a non stereo phone again lol.
The front firing speakers are the thing. I have an Oppo Find 7 at home, it has stereo rear speakers in portrait orientation. Good for music but who uses it for that on internal speakers?
The front landscape speakers are perfect for video and handy for VR too. So much more sensible. The Axon 7 is so affordable for so much function now. Quite the bargain!
I have also recently gotten this phone and I love it, compared to my previous phone. Xperia M4 Aqua.
I have tried a lot of custom roms and I found Dark Rom to be the best one overall, great stability, battery life(5-6h SOT compared to 3-5h in stock). However I couldn't keep using the custom rom(s) since a lot of apps and games that I want to run. Do not work under Xposed or Magisk Hide, even if I don't use them. They detect it's Android N and that breaks most of it. So I am using stock rom, there is no problem and I am okay with that until later.
The biggest downside with the stock rom is that the power saving feature is very clunky. It's not optimized for light gaming, it sets the phone on max and drains it very quickly.
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!!