Xposed not working on new cm rom - Fire Q&A, Help & Troubleshooting

Just flashed the November cyanogen mod update. Xposed isn't working. I'm assuming that it's the November android security patch causing the problem, because it stopped working on my phone Saturday after I flashed an updated rom. From what I've found, the cm team doesn't support xposed, so xposed developers will have to find a work around, and all we can do is wait.

hooks024 said:
Just flashed the November cyanogen mod update. Xposed isn't working. I'm assuming that it's the November android security patch causing the problem, because it stopped working on my phone Saturday after I flashed an updated rom. From what I've found, the cm team doesn't support xposed, so xposed developers will have to find a work around, and all we can do is wait.
Click to expand...
Click to collapse
Known issue with Nov 16th security patch impacting (at least) CM 12.1 and CM 13 on multiple (likely all) device types. CyanogenMod does not officially support Xposed; will be interesting to see how this plays out. For now stick with 20161021 build of CM 12.1 if you want to use Xposed.

hooks024 said:
Just flashed the November cyanogen mod update. Xposed isn't working. I'm assuming that it's the November android security patch causing the problem, because it stopped working on my phone Saturday after I flashed an updated rom. From what I've found, the cm team doesn't support xposed, so xposed developers will have to find a work around, and all we can do is wait.
Click to expand...
Click to collapse
Davey126 said:
Known issue with Nov 16th security patch impacting (at least) CM 12.1 and CM 13 on multiple (likely all) device types. CyanogenMod does not officially support Xposed; will be interesting to see how this plays out. For now stick with 20161021 build of CM 12.1 if you want to use Xposed.
Click to expand...
Click to collapse
Problem resolved w/latest CM build from @ggow (here). Confirmed working. Yey!

Related

[Q] CyanogenMod version 10.1.1

CyanogenMod was updated to version 10.1.1 yesterday which addressed several major Android security exploits. Is that something that gets into next touchpad nighlty build or does it wait for next version release. Just wondering.
poqonos said:
CyanogenMod was updated to version 10.1.1 yesterday which addressed several major Android security exploits. Is that something that gets into next touchpad nighlty build or does it wait for next version release. Just wondering.
Click to expand...
Click to collapse
It should be merged into the nighties as the various devs pull the latest cm code

Unofficial build of CyanogenMod 11.0 for Galaxy Note GT-N7000

This is an unofficial build for all those who want to stay with CM11. The build is based on the pure CM code and does include the stagefright patches and other patches up to July 30.
It does run perfectly on my wife's N7000. However, use at your own risk.
https://www.mediafire.com/folder/wqacsxdn42n15d2,z707vvgb63q4b74/shared
New version available:
https://www.mediafire.com/folder/ygkv6tryc7v7bgs,6ay7smbzruwxxrr/shared
Since - again - a severe security issue has been patched since the last time, I encourage everyone to upgrade.
NeuDLi said:
New version available:
https://www.mediafire.com/folder/ygkv6tryc7v7bgs,6ay7smbzruwxxrr/shared
Since - again - a severe security issue has been patched since the last time, I encourage everyone to upgrade.
Click to expand...
Click to collapse
Please tell us what is the changes applied to the official version of Cyanogemod. You only says to test it, with no description? No , thanks!
Jack4L_ said:
Please tell us what is the changes applied to the official version of Cyanogemod. You only says to test it, with no description? No , thanks!
Click to expand...
Click to collapse
Well it's up to you if you use my ROM or not (basically you always have to trust anyone providing a ROM, because you cannot confirm the actually used codebase anyway!). In the meantime there is another official version out, so you can readily stick to that. I did not wish to wait with a severe security issue until someone built another official version. Last time it was 2 weeks between builds... which is far too long with such severe issues as recently.
Apart from that, your accusation is incorrect! Did you read the initial post? Apparently not, because it clearly stated that "The build is based on the pure CM code". This is still the case and will be if not stated otherwise. So there are NO CHANGES APPLIED TO THE OFFICIAL CM CODE, period! I just build it when an important patch is out but no official build.
no thanks
New version available. This includes the - not yet merged - patches http://review.cyanogenmod.org/112044 and http://review.cyanogenmod.org/112043. According to stagefright detector app this has removed the vulnerability CVE-2015-6602 (also termed stagefright V2). Here you go:
https://www.mediafire.com/folder/0t8784a5at6h9z4,opbklzsle9igxfv/shared
Official version of November 22 available. As a number of bugs have been remedied, everyone should upgrade.
Only thing is that Xposed does not work due to some patches. I will try to compile a new version including a fix for that next week.
New version available. All patches up to and including the one of November 23, and also including a fix for Xposed (taken from here: https://gerrit.omnirom.org/#/c/15695/).
https://www.mediafire.com/folder/xy7zd919cv04ohf,b081a5orcm8et49/shared
Hi NeuDLi,
after many test with cm12 i am now back to cm11 because i think cm12 use to much rom and our old n7000 will work very slow.
I have had many break down and automatik restarts. cm12 has no advantages for me.
the official cm 11 builds -i agree with you- will not quick updated.
now i give your rom a chance to work for me and my n7000. Thanks.
New version available. Includes official patches including December 8. Unless stated otherwise all further version will include the Xposed patch as of the previous post.
https://www.mediafire.com/folder/h2bo3o5b7uqn4gw,40qmwwyfu2cb477/shared

Is any developer working on AOSP Marshmallow Rom/ CM 13 for Titan

Is any developer working on AOSP Marshmallow Rom/ CM 13 for Titan, I guess it's possible to do so, if a developer has some (precious) time to work on it?? Some Non Nexus phones have got AOSP roms now
Yes they are. There are many reasons. 1. Minimal OS is on its Final 5.1.1 Build which suggests that the dev(Vatsal) is working on 6. 2. CM 12.1's First snapshot was released a while back and if you go to the thread you can see posts by devs showing screenshots of CM 13.
So does that answer your question.
p.s. Most probably we'll get CM 13 after this month but before November end (Just saying but its all up to the devs).
@LuK1337 is working on cm13
I'm thinking of working on complete vanilla AOSP, haven't started yet but probably will do sooner or later
He's doing great.. Love cm13.. 😍

CM 14

Is anyone currently working on building CM 14 for the Turbo/Maxx?
DREWHAMM974 said:
Is anyone currently working on building CM 14 for the Turbo/Maxx?
Click to expand...
Click to collapse
Our official CM dev @Skrilax_CZ is working on CM14 -- just like he did CM12, CM12.1 and CM13. No device has official CM14 yet, just stuff thrown together. CM team has not released any CM14 ROMs yet.
Due to his kernel work, he's the only reason we have any custom ROMs at all -- they all use his CM kernel in their ROMs. Even BHM27 kernel is based on CM code @Skrilax_CZ wrote.
santi1993 said:
Will u develop CM14 from Moto X Style sources?
Click to expand...
Click to collapse
Moto X Style does not have official CM14 yet. Yes, somebody has thrown together an unofficial CM14 for that device but lots of stuff doesn't work.
@ Skrilax_CZ will release official CM14 when it's ready.
Skrilax_CZ said:
I usually start porting when CM14 official nightlies start. CM14 is just too unstable right now. Although since I have 2nd MAXX, I might look on it a bit earlier
Click to expand...
Click to collapse
Cobra04 said:
Nexus 6 STILL doesn't have stock Nougat so no rush.
Click to expand...
Click to collapse
This is just speculation as to when the first official CM14 nightlies for any device will begin, not necessarily our Quark.
http://www.theandroidsoul.com/cm14-release-date/
CM14 Release Date?
Expected on: October 2016 (2nd week). Read the below to know why we think so.
As said above, the work has started on the CM14 ROMs over at Github, the central station of the code. We already have ports of CM14 ROMs available for numerous devices, which we tried to list out in separate section below. Mind you, CyanogenMod has yet to release a ROM, as these ports are self-cooked (unofficial) ROM by users using the code available from CyanogenMod team.
Stable release of the CM14 would definitely take some time. When ROMs are stable enough to be used as daily driver, CM team will release them themselves. But let’s try to find out expected release date of that happening.
Let’s take an example. A real one. For Cyanogenmod 13, which was based on Android 6.0, it took nearly over one and a half month.
Google started rolling out the Android 6.0 Marshmallow update on October 5 last year, and uploaded it to AOSP the same day too. But it was only on November 24 that Cyanogen team released their first build of CM13. So, that’s 50 days, around 1 month and 20 days it took CM team to fork out their first CM13 build for selected devices, while most of the devices received CM13 support only later on.
We can expect similar release gap between AOSP release of Nougat and CM14’s release. As Google released the Android Nougat as an OTA to Nexus devices on August 22, to which we add the Marshmallow time gap calculated above of 50 days, our expected CM14 release date would come to October 11, that is, second week of October 2016.
Click to expand...
Click to collapse
Ok, I greatly appreciate it. I just got my Turbo a couple days ago and was just looking around. Once everything has been built I should be able to use the repos to port other CM based roms over to the quark devices. I'm in the middle of getting my build environment set back up since I havent done anything in quite a while. Please note though, I am not a developer. I'm just someone who knows how to build from source using other peoples work on device repos.
DREWHAMM974 said:
Ok, I greatly appreciate it. I just got my Turbo a couple days ago and was just looking around. Once everything has been built I should be able to use the repos to port other CM based roms over to the quark devices. I'm in the middle of getting my build environment set back up since I havent done anything in quite a while. Please note though, I am not a developer. I'm just someone who knows how to build from source using other peoples work on device repos.
Click to expand...
Click to collapse
These are the Marshmallow ROMs currently available for our Quark devices, so you can keep up with what's being done for our device. Just a repost of mine from another thread. Once CM14 (Nougat) comes out, these will probably be updated. But there's tons of other ROMs out there people would love to have! So, thank you.
___________
http://forum.xda-developers.com/showthread.php?p=68810980
Here's the current custom Marshmallow Quark ROMs to choose from:
[ROM][All Quark][6.x.x]Resurrection Remix
Bliss Rom 6.4 by Team Bliss
[ROM][6.0.1][OFFICIAL][QUARK] MoKee OpenSource Project
[Rom] NEXUS EXPERIENCE 10.4 [MotoMaxx] (recently updated to Marshmallow)
AOKP - Android Open Kang Project[6.0.1][Marshmallow]
[Moto MAXX XT1225 / Droid Turbo XT1254][OFFICIAL] CyanogenMod 13.0
[ROM][2016-09-17][Quarks][CM 13.0 Unofficial][6.0.1] (hybrid of CM13 and Resurrection Remix)
That list is in no particular order.
_________________________
You can also install a Marshmallow stock ROM released by Motorola for the Brazilian Quark. @iiWoodstocK adapted it so it runs on ANY Quark, including the XT1254 Droid Turbo or XT1250 U.S. Moto Maxx (clone of the XT1254). It will use YOUR radio, whatever you have installed.
[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]
Stock 6.0.1 MPG24.107-70.2 (Brazil) for Verizon XT1254
http://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
I didn't include it in the list above, because while technically it is a custom ROM, the only "customization" was to allow it to be flashed via TWRP and to allow it to be used on ALL Quarks: XT1254/XT1250/XT1225. Otherwise, it's pure Motorola Marshmallow stock which was officially released for a Quark phone.
iiWoodstocK said:
this ROM is just factory Marshmallow with a modded build.prop. I didn't include any radio in the .zip, so it uses whatever is currently on the device. Aside from my build.prop tweaks, this ROM is even usable for Brazilian XT1225 users, but the device will say it's a Droid Turbo and contain useless CDMA build.prop lines.
Click to expand...
Click to collapse
iiWoodstocK said:
Major stock functionality that I have confirmed working as it should: Moto Display, Approach to wake, Wi-Fi, mobile data (LTE/3G), calls, etc. No Verizon VoLTE (yet). I have not tested Moto Voice as I do not use Moto Voice, but I see no reason why it wouldn't work.
Click to expand...
Click to collapse
Any questions go to those threads and ask.

Bootloop in all Xposed Modules

Guys, help me please
First of all, sorry for my bad english
Well, before, everything was working until I reset the phone
Now, all Xposed modules that I try to install result in bootloop
Already tried to use the newer and older versions, but it doesn't work
I don't know what to do
Just wanted at least the gravitybox
My phone is a Moto X 2014, and I use Cyanogenmod 13
guiga_jord said:
Guys, help me please
First of all, sorry for my bad english
Well, before, everything was working until I reset the phone
Now, all Xposed modules that I try to install result in bootloop
Already tried to use the newer and older versions, but it doesn't work
I don't know what to do
Just wanted at least the gravitybox
My phone is a Moto X 2014, and I use Cyanogenmod 13
Click to expand...
Click to collapse
Well likely that what happened was you looped after updating your cm13.
The new cm13 build as of November 14 comes with a new security patch that has blocked the use of xposed, in fact xposed is not currently being supported by cm13 because of this.
Find more about this in the discussion on xposed for marshmallow, they are trying to fix this and work around the next versions of xposed, since depending on cyanogenmod this is not going to happen for them. If you want xposed in cm13, try a build prior to November 13th. Or use some custom rom without the November security patch.

Categories

Resources