Title says it all. When I flash xposed, everything goes good. But anytime I try to enable any xposed module, the phone just bootloops and I end up having to flash the xposed uninstaller zip for it to boot up. This has happened on the cm13 nightly just released today, as well as on another cm 13 based ROM that I flashed a few days ago, mokee open source. On an older cm13 nightly or an older build of a cm13 based ROM, this doesn't happen. Is there a fix for this?
does anyone know a fix to this
Same issue on htc m7 since the release of cm13. No problem flashing xposed but unable to reboot after activating any modules.
kdeacs said:
Same issue on htc m7 since the release of cm13. No problem flashing xposed but unable to reboot after activating any modules.
Click to expand...
Click to collapse
I fixed it look at this thread
http://forum.xda-developers.com/showpost.php?p=69702111&postcount=4526
Related
Hi Guys!
Today I need your help. My moto e runs perfectly on kitkat roms only. When I flash lp or mm roms, it's system ui starts force closing. This is how the problem started:
I was on cm13 nightly and I decided to update my twrp from play store. So, I downloaded the twrp manager app from play store and updated my recovery to 3.0.0. And the phone worked perfectly until the next day, when it started giving Fc's all of a sudden. I rebooted to recovery and made a full wipe including internal storage. Then I flashed cm11 and flashed gapps. The ROM booted up perfectly and had no fc's at all. So I decided to flash mm again. I flashed AOKP marshmallow but it again started giving me FC's. So, I reverted back to cm11and found no fc's again.
Here's the list of ROMs I tried and was unsuccessful each time:
AOKP(MM)
AOSP(MM and LP)
Cm13
Cm12.1
Blisspop(MM and LP)
Tesla ROM(LP)
Crdroid(MM)
ZephyrOS(MM)
AICP(MM)
Here's the list of ROMs I flashed and the device didn't give any fc's:
Cm11 nightly
Stock ROM Optimized
Stock ROM Full
CrDroid(kitkat)
Please guys I am in need of Deliberate help. Please do not post condolence comments like,"Strange issue mate, Sorry I don't know, Best of Luck". Please post only if you know the method or you have any links to the method.
In need of your help,
Regards,
PoseidonKing
I had the same issue with other MM roms. I got no fc error on CM13 and Resurrection Remix MM rom. Only these two mm Roms worked for me.
It's surely a device hardware issue. If only kitkat based roms work in your condor, then maybe it doesn't properly support art framework. So your last resort maybe going to service center
Sent from my Moto E
Try flashing factory image
Sent from my Moto E using Tapatalk
i think the problem is in the recovery. download cwm recovery img and flash it with fastboot and after that wipe everything including internal storage (do not reboot recovery at that tyme or before installing rom ) do not wipe ur sd card and then install rom without gapps and boot up after sucessful boot then again boot to recovery and install gapps... if problems remains same then try downloading other gapps package for 6.0 (preferred open gapps).
no need all of this, just record the logcat and post here, surely you'll get proper fix!
I think Twrp 3.0 is causing this revert to old 2.8 version.It is nothing to do with hardware if it is a hardware related problem then you can't even switch on phone.
Agreed! Custom recoveries known to, often cause these sort of problems.. Give the twrp 3.0.2 by magdoez or 2.8.7 a try.. These are the ones that work perfectly for me.
Try updating recovery from your current recovery itself & reboot.. Then try the aforementioned mm roms..
piku 123 said:
I think Twrp 3.0 is causing this revert to old 2.8 version.It is nothing to do with hardware if it is a hardware related problem then you can't even switch on phone.
Click to expand...
Click to collapse
Thanks bro, but the method ain't working. I am currently on TWRP 2.7.1.0 and I still face the same problem...
Adarsh1998 said:
no need all of this, just record the logcat and post here, surely you'll get proper fix!
Click to expand...
Click to collapse
Okay, thanks! But how the hell do I record a logcat??
PoseidonKing said:
Okay, thanks! But how the hell do I record a logcat??
Click to expand...
Click to collapse
Refer this thread: http://forum.xda-developers.com/showthread.php?t=1726238&page=28
Sent from my Moto E using Tapatalk
Hi guys,
Thank You everyone for your generous and quick help. My Moto E is fixed now. I flashed cyanpop mm and then tried the adopted sd option. Rebooted the device and now it is working perfectly. Though it wouldn't have been possible without my brother's help @Andy1911. Thank you once again to all of them who helped me.
Regards,
PoseidonKing.
Please help me!When ever i am trying to install any new update of cm 13 other that 20161007 build of otus i get stuck in bootloop!!
Ayush Jaipuriyar said:
Please help me!When ever i am trying to install any new update of cm 13 other that 20161007 build of otus i get stuck in bootloop!!
Click to expand...
Click to collapse
It is a known issue. U can now either flash cm14.1 or an older version of cm13.
Dev_Mashru said:
It is a known issue. U can now either flash cm14.1 or an older version of cm13.
Click to expand...
Click to collapse
Yeah but can't I flash new versions of cm 13. Since cm 14.1 in currently unofficial, I don't want to flash it right now.
I have tried installing the boot.img file from computer but I still get stuck bootloop
Ayush Jaipuriyar said:
Yeah but can't I flash new versions of cm 13. Since cm 14.1 in currently unofficial, I don't want to flash it right now.
I have tried installing the boot.img file from computer but I still get stuck bootloop
Click to expand...
Click to collapse
Cm14.1 is official. I'm using it. It's mostly on stable part and can be used as a daily driver.
I hadn't checked the updates recently .
I just installed cm14.1 , and it worked thank you Dev_Mashru
I have officially unlocked my phone and installed Strix's latest TWRP and the official CM 14.1 with firmware and all that but I got the bug where battery percentage would not change until a reboot.
So I tried to install the Radon custom kernel to fix it, but alas I got stuck in a bootloop.
I have tried both versions of Radon both the nougat versions and I tried AssassinX kernel too.
If anyone knows of a solution for this it would be much appreciated.
Check the radon thread, there is a problem with the latest Strix's TWRP.
Edit: -
Umang96 said:
Try strix July 1 recovery, latest is causing bootloop.
Click to expand...
Click to collapse
corkiejp said:
Check the radon thread, there is a problem with the latest Strix's TWRP.
Click to expand...
Click to collapse
Thanks <3
Hey guys, I want to switch to LOS14.1 by TheStrix, because it is now stable and bug-free.
There are some other things i want to flash too, so I just wanted to clear things up a bit.
I want to flash radon kernel, Arise sound mod, and magisk, because apparently magisk will allow me to use banking apps.
From referring to other people on the forum, i have the following:
1)Flash CM14 Firmware
2)Flash ROM
3)Flash GAPPS
4)Flash Radon Kernel
5)Reboot and setup phone
6)Flash magisk
7)Enable hide root
8)Flash Arise sound mod with arise magisk compatibility module.
So I have some questions regarding this procedure.
Do I have to flash supersu before flashing Magisk?
Is it worth it to switch data and cache to F2FS?
Do I need to switch recoveries to do this?
Is this the right order to flash the ROM and accompanying zips?
I am using the snapdragon redmi note 3 with fpc fingerprint sensor.
I have an officially unlocked bootloader.
I am currently on RR_MM official.
I would test it out myself, but i'm in college, so i don't really have time to do that.
If anyone would share their experiences or give me some pointers, it would be much appreciated.
No you must switch to RR n
[email protected] said:
No you must switch to RR n
Click to expand...
Click to collapse
Why is it a must to switch to rr n over los?
I actually don't really mind using either ROM, but I wanted to test out LOS for a while.
No its laggy too much
what i just did in the beginning was to wipe everything except the external sd card.
i would suggest to run the rom the rom first time without new kernel. i just updated my RR Nougat to todays release and wanted to flash radon just ahead, had some errors in recovery doing so. did a reboot, new rom was there but no radon. again flashing within recovery and no problems. with arise i have no clue, i dont use it
Quote from the Radon kernel v4.3 changelog, applicable to your step 4, 5 and 6.
Umang96 said:
If your rom uses magisk root, then don't flash radon immediately after rom, first boot to system once.
Click to expand...
Click to collapse
Been a user of CM and then Lineage for years.
Unfortunately the lineageOS in Oreo we have at the moment are not quite working entirely.
Are there any long established roms, on Oreo, that work 100% and receive updates?
the only other I've tried is Nitrogen, where I had issues with an encryption error (where I wasn't encrypting) and not sure was getting updates at that stage..
xd4d3v said:
Been a user of CM and then Lineage for years.
Unfortunately the lineageOS in Oreo we have at the moment are not quite working entirely.
Are there any long established roms, on Oreo, that work 100% and receive updates?
the only other I've tried is Nitrogen, where I had issues with an encryption error (where I wasn't encrypting) and not sure was getting updates at that stage..
Click to expand...
Click to collapse
Official LOS is not updated anymore with fixes.
Use oficial Aosp extended rom. It has official inbuild updater like Los. its very customizable and best rated rom.
Flash latest twrp 3.2.3
First Format data
Then. Wipe data reset
Flash Aex rom 5.8
Flash latest august open gapps nano
Reboot
Sent from my kenzo using XDA Labs
xd4d3v said:
Been a user of CM and then Lineage for years.
Unfortunately the lineageOS in Oreo we have at the moment are not quite working entirely.
Are there any long established roms, on Oreo, that work 100% and receive updates?
the only other I've tried is Nitrogen, where I had issues with an encryption error (where I wasn't encrypting) and not sure was getting updates at that stage..
Click to expand...
Click to collapse
Give Omnirom a try. May not be the most feature rich, but its one of the most stable ROMs that I've tried. Updated regularly as well.
xd4d3v said:
Been a user of CM and then Lineage for years.
Unfortunately the lineageOS in Oreo we have at the moment are not quite working entirely.
Are there any long established roms, on Oreo, that work 100% and receive updates?
the only other I've tried is Nitrogen, where I had issues with an encryption error (where I wasn't encrypting) and not sure was getting updates at that stage..
Click to expand...
Click to collapse
You can use Mokee, only issue Xposed pre installed and not systemless. Hence won't pass safetynet even if you use Xposed uninstaller
naik2902 said:
Official LOS is not updated anymore with fixes.
Use oficial Aosp extended rom. It has official inbuild updater like Los. its very customizable and best rated rom.
Flash latest twrp 3.2.3
First Format data
Then. Wipe data reset
Flash Aex rom 5.8
Flash latest august open gapps nano
Reboot
Sent from my kenzo using XDA Labs
Click to expand...
Click to collapse
i have nougat nitrogenOS at the moment, do i need to flash another firmware before flash aospextended 5.8?
jorgealheiro said:
i have nougat nitrogenOS at the moment, do i need to flash another firmware before flash aospextended 5.8?
Click to expand...
Click to collapse
Just be on the latest firmware. No need to worry for firmware before every rom u flash.
Sent from my kenzo using XDA Labs
naik2902 said:
Just be on the latest firmware. No need to worry for firmware before every rom u flash.
Click to expand...
Click to collapse
i installed aos extended 5.8 and magisk 16.6, but my phone lags so hard, i´ve already have lag problems on android oreo. do you know why? it is related to kernel or firmware?
jorgealheiro said:
i installed aos extended 5.8 and magisk 16.6, but my phone lags so hard, i´ve already have lag problems on android oreo. do you know why? it is related to kernel or firmware?
Click to expand...
Click to collapse
I m on cardinal Aosp 5.8 Treble rom. I dont use magisk.
You should check laggyness without magisk.