Ever since I updated to the Dec. 2016 patch I haven't been able to get themes to work. I really miss having my phone blacked out. Someone please help!
Using XT1575 24.49-18-8 /w Systemless Root, Systemless Xposed, & Frankenclark 0.14
I'm feel for you.. https://forum.xda-developers.com/moto-x-style/themes-apps/december-1-2016-security-update-t3559554http://.
Seems like there isn't a solution yet. I really regret updating the software
Using XT1575 24.49-18-8 /w Systemless Root, Systemless Xposed, & Frankenclark 0.14
From what I've read, Substratum is catering to the 1.5% of the phones out there running Nougat, and giving up on the Marshmallow crowd which makes up 20%, seems to be the norm once a new version comes out, everyone drops the last version
Sent from my XT1575 using XDA-Developers Legacy app
Once you do a security update, you can't go back right?
Using XT1575 24.49-18-8 /w Systemless Root, Systemless Xposed, & Frankenclark 0.14
Not without a complete fastboot flash back to the last update OS, the Return to Stock tool, found here https://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905, and even if you do, Mot will just send you those annoying Update messages every 5 minutes until you do..
Marshmallow is found on 30.7% of all android phones out in the world compared to 0.3% of Nougat as of 2/6/17 found here https://developer.android.com/about/dashboards/index.html.
I can see the changeover to Nougat but some support for MM for at least another 6 months would be great, I know Lenovo / Motorola will not be upgrading the X Pure XT1575 until sometime in April if at all, and some of us would still like to get Root, which I am not sure if that would be possible until the developers get a copy of the API for the XT1575. We all know how Microsoft rushes new OS to market only to have it crash and burn in the first month.
---------- Post added at 06:35 PM ---------- Previous post was at 06:29 PM ----------
I love Substratum https://play.google.com/store/apps/details?id=projekt.substratum with the Spectrum Theme from Jeremy https://play.google.com/store/apps/details?id=com.jerbeck24.Spectrum, but even Jeremy said he can promise it would work in MM since the new security update is preventing some of the functionality to work properly.
Can't I just flash a backup from TWRP? I think I'm gonna go back to the February update.
Using XT1575 24.49-18-8 /w Systemless Root, Systemless Xposed, & Frankenclark 0.14
Nvm i figured it out. Good thing I had a nandroid backup.
Using XT1575 24.49-18-4 /w Systemless Root, Systemless Xposed, & Frankenclark 0.14
Is this true. Dec update does not work with substratum?
I can not get past the Boot Animation after applying Substratum Theme Engine -> Spectrum Theme. I have to flash " SubstratumRescue_Legacy.zip " from TWRP in order to get back into my MXPE, it was working before the update.
StankFiss said:
Is this true. Dec update does not work with substratum?
Click to expand...
Click to collapse
Substratum doesn't work at all anymore unless you have a nandroid backup saved with the theme. I tried even with an older firmware and it doesn't work either.
dkeepitabuck said:
Substratum doesn't work at all anymore unless you have a nandroid backup saved with the theme. I tried even with an older firmware and it doesn't work either.
Click to expand...
Click to collapse
Please help me understand. You said older firmware. Is that Substratum or Moto x firmware. You also stated that it works only with nan droid back up. So your on DEC update with a working Substratum theme?
StankFiss said:
Please help me understand. You said older firmware. Is that Substratum or Moto x firmware. You also stated that it works only with nan droid back up. So your on DEC update with a working Substratum theme?
Click to expand...
Click to collapse
Substratum doesn't work at all anymore. Around the time the May update was released Substratum supported the Moto X and/or Marshmallow. Recently I tried Substratum on May, Sept, & Dec from a fresh install and it doesn't work.
I went back to the May update where my Domination theme was already applied on my nandroid backup
dkeepitabuck said:
I went back to the May update where my Domination theme was already applied on my nandroid backup
Click to expand...
Click to collapse
Ok then its just you. I'm on Sept update with no problems. Just had to do fresh install just before Dec update was released. I have no problems with Substratum. Sorry to point that out. I'm not going to bother with DEC until Nougat. BTW any one needs to stop OTA. Go to etc/security otacerts.zip change it to otacerts.zip.bak so far no ota update warning.
Substratum and it's themes are unstable in my experience. Far too many options to available the majority of the themes, and the default settings in a lot of these themes are ugly at best, making things unreadable in a lot of instances. The only theme I use is Destiny which doesn't have many options to change things and provides a subtle change in colours. (custom rom, not the out of date rom provided by the useless Lenovo!)
StankFiss said:
Ok then its just you. I'm on Sept update with no problems. Just had to do fresh install just before Dec update was released. I have no problems with Substratum. Sorry to point that out. I'm not going to bother with DEC until Nougat. BTW any one needs to stop OTA. Go to etc/security otacerts.zip change it to otacerts.zip.bak so far no ota update warning.
Click to expand...
Click to collapse
Can you tell me how you got substratum to work? Like a step by step guide. The only reason I'm still using the May update is bc I have no problems with anything. My snapprefs stop working when I updated so I reverted to my old set up
Using XT1575 24.49-18-4 /w Systemless Root, Systemless Xposed, & Frankenclark 0.14
dkeepitabuck said:
Can you tell me how you got substratum to work? Like a step by step guide. The only reason I'm still using the May update is bc I have no problems with anything. My snapprefs stop working when I updated so I reverted to my old set up
Using XT1575 24.49-18-4 /w Systemless Root, Systemless Xposed, & Frankenclark 0.14
Click to expand...
Click to collapse
Installing it the usual way. I'm stock with Theme ready and Gravity box. Installed substratum and gave it root access that's it. Below show you I'm on Sept. update. I'm using spectrum and deity, both working fine. I would uninstall Substratum and make sure you delete any residue folders. Then davlik/cache wipe. Then reinstall. Good luck.
I'm gonna try this from scratch after flashing the Sept update. The theme ready apps are only compatible with a certain version of Google Apps right?
Using XT1575 24.49-18-4 /w Systemless Root, Systemless Xposed, & Frankenclark 0.14
Anyone have any problems with Snapprefs after updating their firmware?
Using XT1575 24.49-18-4 /w Systemless Root, Systemless Xposed, & Frankenclark 0.14
Related
http://forum.xda-developers.com/showthread.php?t=3034811
Its finally here! Thanks Rovo
Working great on the 5x with the few modules I have tested.
Seems to have successfully installed, we are arm64 if anyone is unsure.
Which modules are working so far?
What rom are you using? Which version of v76 did you flash?
You'll want v77 (yes, v77) arm64, guys.
stu5797 said:
What rom are you using? Which version of v76 did you flash?
Click to expand...
Click to collapse
Pure NeXus with ElementalX kernel.
And v76 worked for me, but it's been superseded by v77, which is also working fine.
Hmmm I have pure nexus with elemental kernel and 76 didn't work. It booted but didn't work.
V77 is working perfectly though
Anyone know of a module that allows us to change the wifi / network strength status bar icons? I prefer the look of the older icons. First few I tried couldn't make the change.
I'm using greenify. Seems to be working fine. Wondering if its necessary with doze feature
Sent from my Nexus 5X using Tapatalk
Version 78 is already out with some bugfixes. Whats the difference between SDK 22 and 23?
Should we install xposed-v78-sdk23-arm64.zip ?
Just found the answer myself:
Sdk 21 - Lollipop 5.0
Sdk 22 - Lollipop 5.1
Sdk 23 - Marshmallow 6.0
Once the "No Device Check" module is working we will be able to use Android Pay on rooted devices without having to unroot before hand. I know it's also possible to use Android Pay if you use Chainfire's Systemless Root. Unfortunately, custom AOSP ROMs don't use this root method so you either have to stay on stock rooted with the systemless root or use workarounds.
However, once this module is fully working Android Pay should work no matter what ROM/root method you choose.
http://repo.xposed.info/module/com.pyler.nodevicecheck
FYI - GravityBox is now available for Marshmallow too.
sn0warmy said:
Once the "No Device Check" module is working we will be able to use Android Pay on rooted devices without having to unroot before hand. I know it's also possible to use Android Pay if you use Chainfire's Systemless Root. Unfortunately, custom AOSP ROMs don't use this root method so you either have to stay on stock rooted with the systemless root or use workarounds.
However, once this module is fully working Android Pay should work no matter what ROM/root method you choose.
http://repo.xposed.info/module/com.pyler.nodevicecheck
Click to expand...
Click to collapse
So this module is still not working? I didn't find anything about it in description...
Sent from my Nexus 5X using Tapatalk
Is version 78 working well so far? About to flash this and find out myself.
blinkin said:
So this module is still not working? I didn't find anything about it in description...
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It wasn't working for me. Android Pay kept coming back with a security error. I suppose I could have been doing something wrong though.
Anyone using xposed on android OS v6.0.1?
bryanus said:
Anyone using xposed on android OS v6.0.1?
Click to expand...
Click to collapse
Yes along with GravityBox [MM], latest stable release. Everything works perfectly.
sn0warmy said:
Once the "No Device Check" module is working we will be able to use Android Pay on rooted devices without having to unroot before hand. I know it's also possible to use Android Pay if you use Chainfire's Systemless Root. Unfortunately, custom AOSP ROMs don't use this root method so you either have to stay on stock rooted with the systemless root or use workarounds.
However, once this module is fully working Android Pay should work no matter what ROM/root method you choose.
http://repo.xposed.info/module/com.pyler.nodevicecheck
Click to expand...
Click to collapse
I can't waaaaaaaaaait
Squier 51 said:
Yes along with GravityBox [MM], latest stable release. Everything works perfectly.
Click to expand...
Click to collapse
Works like a charm!
Which version do I need for my nexus 5x to install framework?
I know that this is still in the experimental phase, and mostly for just Nexus devices at the moment, but has anyone attempted to make a modified boot.img for systemless root on the MXP? I would imagine that this type of root will become common place on the MXP once MM drops. The main advantage I'm thinking of here is the ability to use Android Pay while still maintaining active root. I've also read that Xposed + the systemless root doesn't seem to hinder Android Pay functionality.
This is pretty much what is keeping this phone from being perfect for me. But for now, I can hold out by enabling/disabling root when needed for Android Pay
It has been done
http://forum.xda-developers.com/moto-x-style/development/rom-indian-marshmallow-variants-t3253684
http://forum.xda-developers.com/moto-x-style/general/marshmallow-ota-zip-t3250253/post63922983 post #260
rsa 329 said:
It has been done
http://forum.xda-developers.com/moto-x-style/development/rom-indian-marshmallow-variants-t3253684
http://forum.xda-developers.com/moto-x-style/general/marshmallow-ota-zip-t3250253/post63922983 post #260
Click to expand...
Click to collapse
I don't believe that is the experimental systemless root. I believe that is the standard mm root.
Doktaphex said:
I don't believe that is the experimental systemless root. I believe that is the standard mm root.
Click to expand...
Click to collapse
I could be wrong, but i'm pretty sure this is the beta system less root method.
they are using super su beta 2.52 in this method which is not the systemless root. Systemless is beta 2.56
timde9 said:
they are using super su beta 2.52 in this method which is not the systemless root. Systemless is beta 2.56
Click to expand...
Click to collapse
I am gonna have a little look see into the boot.img etc and see if I can get a systemless root going
Last night I was having problems with my linux partition on my desktop. Gonna reinstall tonight and mess about over the weekend.
I didn't see this posted here so FYI: As announced here, there are currently some issues with SuperSU 2.80 and 2.81 that are being worked on and Chainfire has recommended staying with SR3-SuperSU-v2.79-SR3-20170114223742.zip for now while he works the issues out.
If you have already flashed 2.80 or 2.81 and lost root it is safe to flash back to SR3-SuperSU-v2.79 using TWRP (according to the thread and it worked fine for me). Hopefully this prevents some from flashing a few different versions trying to get root working again.
You should switch to Magisk, more features and less issues
snowrelyt said:
You should switch to Magisk, more features and less issues
Click to expand...
Click to collapse
Interesting, I'll look through the treads. Thanks for the infos!
Switching from SuperSU to Magisk is pretty easy. I've done it on my N5, N6 & N10.
BACK UP FIRST. Did I need to say that...?
Unroot with Osmosis' Unsu.zip, make sure that you have the original boot image, which in case of doubt you can extract from your ROM and flash (or your preferred kernel - see edit below), then flash Magisk and install the Magisk Manager apk. Note: you must flash Magisk after the boot/kernel, as it does a similar unpack/tweak/repack/install to SuperSU's processing. If you flash the boot/kernel after, you'll lose root.
Just to add to the fun, there are two versions - the stable v12/Manager 4 and a project v13/Manager 5. My N5 & N6 work fine on v12. I couldn't get v12 to work on my N10, but v13 runs perfectly and all three devices pass Safetynet.
I guess you're here because you like tinkering. Magisk is well worth the fun...
Edit: All three devices are on Pure Nexus. The N10 has the stock kernel, and the others have ElementalX. You should be able to use your preferred kernel.
If you do decide to install Magisk, at first sight you may think you haven't achieved root - until you realise (as I did, duh) that you need to check Settings/Magisk Hide.
Once it's up and running, it works as well as SuperSU.
And why did I switch? Only possibly groundless worries about the change of ownership from Chainfire to a company.
I switched to Magisk because of the analytics fiasco, brought about because of inadequate communication from CCMT. As I noted in a now-deleted post, while the analytics may seem a trivial reason to switch, I believe the gatekeeper to the system root must be incorruptible to remain trustworthy. Had CCMT been honest about the analytics in the first place, I might not have switched.
snowrelyt said:
You should switch to Magisk, more features and less issues
Click to expand...
Click to collapse
I agree. That's what I did. I switched from SuperSu to Magisk and it's working fine on Stock 7.1.1.
---------- Post added at 08:53 PM ---------- Previous post was at 08:36 PM ----------
dahawthorne said:
Switching from SuperSU to Magisk is pretty easy.
Once it's up and running, it works as well as SuperSU.
And why did I switch? Only possibly groundless worries about the change of ownership from Chainfire to a company.
Click to expand...
Click to collapse
You are so on point.
I switched from SuperSu to Magisk. Was a little hesitant to do so at first because I've been used to using SuperSu and Magisk was unchartered territory for me. But I decided to make the change and I'm glad I did. Magisk is working very well on my Shamu running Stock 7.1.1. I've installed a few modules, including Viper4Android and wow, what a big difference in sound quality (although those front firing speakers are very good in and of themselves, Viper4Android does indeed make a difference).
All in all, I'm happy to have Magisk installed on my Nexus 6.
Btw, I wasn't too thrilled the way the whole thing went down with SuperSu and CCMT. Not really trusting of that app anymore. To each his own, but I'll stick with Magisk.
For some reason Magisk is gone from play store.
mal13 said:
For some reason Magisk is gone from play store.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=72508849&postcount=21
I moved to magisk, too, thanks for recommendation. I would not even know about magisk that I have not read about it the last days. It seems a much better alternative, I doubt that I will not go back to SuperSU at this situation with CCMT etc. I'm upset with the last supersu's updates, I see, they do not want to do anything that would solve problem as soon as possible. What's the phh's superuser (I guess it's better to stay on magisk for now.)? I have never tried it. [emoji106] [emoji482] [emoji122]
Forgot, use PureNexus, all stock. [emoji122]
Sent from my Nexus 6 using Tapatalk
nemanja066 said:
What's the phh's superuser?
Click to expand...
Click to collapse
It's another open source root solution. MagiskSU is based on phh's superuser which in turn is based on koush's superuser.
After 4 1/2 years I finally killed my M8 and am having a HTC 10 with Nougat delivered tomorrow. My M8 was stock rooted with xposed and that's what I would like to do to the 10. When I set up my M8, I unlocked via HTC dev, flashed TWRP, TWRP rooted the device and then I flashed xposed. I would like to do the same to my 10 but am unsure if it's possible or how to do it. I tried googling but a lot of the results were a year old and and I'm not sure that they still apply today. Do I still unlock via HTC dev or should I use sunshine? Will TWRP still install a version of Chainfire's SuperSiu or do I need to use Magisk to root? Is xposed still possible?
me_three said:
After 4 1/2 years I finally killed my M8 and am having a HTC 10 with Nougat delivered tomorrow. My M8 was stock rooted with xposed and that's what I would like to do to the 10. When I set up my M8, I unlocked via HTC dev, flashed TWRP, TWRP rooted the device and then I flashed xposed. I would like to do the same to my 10 but am unsure if it's possible or how to do it. I tried googling but a lot of the results were a year old and and I'm not sure that they still apply today. Do I still unlock via HTC dev or should I use sunshine? Will TWRP still install a version of Chainfire's SuperSiu or do I need to use Magisk to root? Is xposed still possible?
Click to expand...
Click to collapse
You can still unlock via HTC Dev. S-off via Sunshine is also possible and you can leave your bootloader locked, as well. You'll need to use the latest SuperSU, as well as the latest version of TWRP. Can't comment on Magisk versus Xposed because I don't use either one.
Xposed is not possible on Nougat. What were you using it for? I use Magisk for all the mods I used to use (adblocking, YouTube background playback, etc.). Magisk is pretty cool, and Magisk's SU replaces SuperSU for all intents and purposes that I'm aware of.
If you want / need S-OFF, you'll need to pay for Sunshine. If you don't, just unlock via HTCDev, run the latest RUU if necessary (a new update just came out today), install TWRP, boot up into your home screen, install Magisk Manager, use that to download Magisk root, and go about your merry way.
I just jumped from stock (Bad Boyz) to Pure Fusion AOSP from the main HTC 10 forum, and I'm really loving being back on AOSP.
SilverZero said:
Xposed is not possible on Nougat. What were you using it for? I use Magisk for all the mods I used to use (adblocking, YouTube background playback, etc.). Magisk is pretty cool, and Magisk's SU replaces SuperSU for all intents and purposes that I'm aware of.
If you want / need S-OFF, you'll need to pay for Sunshine. If you don't, just unlock via HTCDev, run the latest RUU if necessary (a new update just came out today), install TWRP, boot up into your home screen, install Magisk Manager, use that to download Magisk root, and go about your merry way.
I just jumped from stock (Bad Boyz) to Pure Fusion AOSP from the main HTC 10 forum, and I'm really loving being back on AOSP.
Click to expand...
Click to collapse
There is Xposed for Nougat, albeit recently and it's listed as unofficial.
https://www.xda-developers.com/flashable-xposed-framework-android-nougat/
Magnum_Enforcer said:
There is Xposed for Nougat, albeit recently and it's listed as unofficial.
https://www.xda-developers.com/flashable-xposed-framework-android-nougat/
Click to expand...
Click to collapse
Well how about that? I just skimmed but it looks like the original dev behind Xposed is leery of this implementation, but I don't understand all of that. I guess just the fact that it's possible will be encouraging for a lot of people.
Even so, I'm quite happy with Magisk.
I just jumped from stock (Bad Boyz) to Pure Fusion AOSP from the main HTC 10 forum said:
I'm using Lee's rom at the moment and have thought about the Pure Fusion one, but I keep seeing some issues with wifi and radio signal. Are you having any of these issues?
Click to expand...
Click to collapse
biker57 said:
I'm using Lee's rom at the moment and have thought about the Pure Fusion one, but I keep seeing some issues with wifi and radio signal. Are you having any of these issues?
Click to expand...
Click to collapse
None at all that I've noticed. I mainly use LTE but I switched to wifi for a few hours last night, no problems on my end.
Thank you all for your help, I'll hold out on magisk for a bit to see how the new xposed comes along.
me_three said:
Thank you all for your help, I'll hold out on magisk for a bit to see how the new xposed comes along.
Click to expand...
Click to collapse
I haven't tried it myself but be careful, several people have told me the Sprint HTC10 has more problems being unlocked than other US versions, especially when it comes to flashing the radio to use on different carriers. Specifically I've been told trying to flash the Verizon radio will not only fail but has the potential to permanently disable your radio.
Gang,
The May 2019 update is now rolling out.
You should get an OTA update any time soon.
Main update topics:
- Android Generic
https://source.android.com/security/bulletin/2019-05-01.html
- Pixel Specific
"There are no Pixel security patches in the May 2019 Pixel Update Bulletin. "
"All Pixel devices running Android 9 will receive an Android 9 update as part of the May OTA. This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices."
https://source.android.com/security/bulletin/pixel/2019-05-01.html
Have fun
OTA Screenshot
What took you so long? I installed it more than two hours ago.
Seems nothing changed only security updates. However At-a-Glance widget now have only three options again.
No smart notifications and no Reminders notifications in the options.
Another update and no changes.. Well disappointing
100rabh7791 said:
Another update and no changes.. Well disappointing
Click to expand...
Click to collapse
Oh, there are changes, Google is just getting lazy documenting them. How often to you see app updates that only state "bug fixes and performance improvements". I think they just cut & paste that into everything these days...
Pkt_Lnt said:
Oh, there are changes, Google is just getting lazy documenting them. How often to you see app updates that only state "bug fixes and performance improvements". I think they just cut & paste that into everything these days...
Click to expand...
Click to collapse
Haha lets find them out then
1) battery % on the bottom of always on displays looks a bit bigger
The android security patch now says May! :silly::laugh:
I think Google focusing on Android Q and at this point make no sense to add improvements for Android P.
Android Q Beta 3 will be released after/during Google IO event. There will be a lot of announcement and new features for Android Q. Maybe a good time to upgrade.
Any of you guys rooted with magisk? It seems the may updates killed magisk and bootloops, at least for me.
Here's one change i noticed. Charging my device doesn't slow down until 95% full. ampere app shows 1020ma using a QC 3.0 enabled charger, not like before once the device hits 80% it slows down the charging from 1020ma to 600 to 700ma.
agplugged said:
Any of you guys rooted with magisk? It seems the may updates killed magisk and bootloops, at least for me.
Click to expand...
Click to collapse
Same here. I'm running unrooted because of bootloops
Can someone tell me exactly how to update, im on april update stock magisk rooted with twrp recovery and custom kernel, cuz last time i updated from march to april update i messed up my phone and ended up wiping everything from it
agplugged said:
Any of you guys rooted with magisk? It seems the may updates killed magisk and bootloops, at least for me.
Click to expand...
Click to collapse
I checked and made sure everything is in the latest version, and failed like you. John Wu is going to Apple to get a internship, maybe the update for the new version of magisk would not came out that fast as before. And now I choose to stay in the April update.
zenjedi said:
Same here. I'm running unrooted because of bootloops
Click to expand...
Click to collapse
naive_tode said:
I checked and made sure everything is in the latest version, and failed like you. John Wu is going to Apple to get a internship, maybe the update for the new version of magisk would not came out that fast as before. And now I choose to stay in the April update.
Click to expand...
Click to collapse
The easiest fix to regain root is....go to twrp, flash the magisk uninstaller.zip, then immediately flash the magisk 18.1 zip. You'll have to install your modules again, but that's not too big a deal :good::good:
---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------
Nightf0x_007 said:
Can someone tell me exactly how to update, im on april update stock magisk rooted with twrp recovery and custom kernel, cuz last time i updated from march to april update i messed up my phone and ended up wiping everything from it
Click to expand...
Click to collapse
Fastboot the May factory image with the -w removed from the flash-all.bat file, and let it boot up. Go back to fastboot mode, and fastboot twrp, I use the 323-1 version since I didn't have any luck with the 330-0 version. Once in twrp, flash the twrp installer zip, then flash the magisk uninstaller zip, then flash magisk 18.1 zip, boot up, install your magisk modules again, and done :good:
If I am going to do a clean install (with wipe) do I still need to uninstall magisk in order to prevent bootoops w current version?
Cowbell_Guy said:
If I am going to do a clean install (with wipe) do I still need to uninstall magisk in order to prevent bootoops w current version?
Click to expand...
Click to collapse
Not really since your phone will be completely wiped anyways. You may need to use magisk 18.1 though. The May update and magisk 19+ versions did not work for me :good:
agplugged said:
Any of you guys rooted with magisk? It seems the may updates killed magisk and bootloops, at least for me.
Click to expand...
Click to collapse
Works fine for me . I had to change to partition a this time to though
There is a UI change which I don't really like, though i will get used to it - probably for the best.
There's a new loading arrow symbol on all apps and pages that are loading. It uses the colour theme of the app.
See attached .
Everyone else notice this?
I want to update but dont want bootloops