Feel free and test it!
http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
tested on 5.0.2 brazilian but its failed with the error about system full, i readed on gpe 5.01 is working fine.
We dont have an uninstaller for .zip and now im trying to write system files to uninstall the zip flashed without lose of data.
for our moto when system displays low memory and can't instal xposed app just need to wipe cache and dalvik from recovery
plantator said:
for our moto when system displays low memory and can't instal xposed app just need to wipe cache and dalvik from recovery
Click to expand...
Click to collapse
This succesed for u? I installed it and got this error after succesed install. Then phone started to lagging so much and couldnt download anything. Error perfomed after install not before.
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
Also i am talkng abot the .zip part wich need to flash it manually via recovery, not about the apk
yes, have same too, reboot to reco, wipe cache and dalvik and turn on- error will disappear and next you can go install apk, if not work, reboot, flash again zip wipe caches and reboot, must work
Too buggy for me just yet. I'll let all you Guinea pigs go first lol!
hmno xposed is to buggy but modules has no converted and they make bugs, for me working amplify, partially grenify, cpufreq in statusbar, youtube background, force immersive mode, and partially gravitybox- chaange size of nav bar
I agree. We need to wait next 2-6 months so it will be stable and most important modules will be fully functional with lollipop. As for now it's really bad to install it.
Its working fine for me on xt1033 but lot of modules need to be updated to support lollipop
Ofc modules will need to be updated. do u thought will be compatible in first day of xposed release ?
No but without updated modules, it's more of less useless. So I'm not sure what the hype is about.
Tried on XT1033 with CM12 and the app always says I have to install framework manually. I've done it twice and did not work. I install zip, clean cache and did not work, then I install zip again, clean cache/dalvik and also did not work.
Related
Hello,
I upgraded my Verizon Galaxy S4 from CM11 to CM12 last night, using the nightly build from 1/7/2015. The upgrade went smoothly, except for gapps. I have not been able to get them to successfully run on Lollipop. I have tried the following builds of gapps:
PA GAPPS
2014-11-09
2014-12-20
I use the following installation process each time:
Boot into CWM 6.0.3.2
wipe data/factory reset
wipe cache partition
mounts and storage > format /system
wipe dalvik cache
install CM.zip
install gapps.zip
When I reboot the phone, it gets into the lock screen as expected, but when I swipe it to unlock, I instantly get a stream of errors ("Setup wizard has stopped", "Google+ has stopped", etc). The exact errors depend on which gapps version I install, since they come with (slightly) different apps in the packages.
Has anyone had success with the Lollipop gapps packages and CyanogenMod?
rowdypixel said:
Hello,
I upgraded my Verizon Galaxy S4 from CM11 to CM12 last night, using the nightly build from 1/7/2015. The upgrade went smoothly, except for gapps. I have not been able to get them to successfully run on Lollipop. I have tried the following builds of gapps:
PA GAPPS
2014-11-09
2014-12-20
I use the following installation process each time:
Boot into CWM 6.0.3.2
wipe data/factory reset
wipe cache partition
mounts and storage > format /system
wipe dalvik cache
install CM.zip
install gapps.zip
When I reboot the phone, it gets into the lock screen as expected, but when I swipe it to unlock, I instantly get a stream of errors ("Setup wizard has stopped", "Google+ has stopped", etc). The exact errors depend on which gapps version I install, since they come with (slightly) different apps in the packages.
Has anyone had success with the Lollipop gapps packages and CyanogenMod?
Click to expand...
Click to collapse
https://s.basketbuild.com/gapps
try that gapps which works for me very fine.
Factory reset
install Cm and then gapps. it should work all fine actually. :laugh: goodluck. reply here for further problems.
xDroidZz said:
try that gapps which works for me very fine.
Factory reset
install Cm and then gapps. it should work all fine actually. :laugh: goodluck. reply here for further problems.
Click to expand...
Click to collapse
I tried that one again - no dice. com.google.process.gapps crashes on startup, followed by a long list of other Google apps included in the package.
Same problem.
---------- Post added at 03:12 PM ---------- Previous post was at 03:01 PM ----------
Nexus 7 2013 WiFi
Any fix for this? I've been struggling with it for a whole day now.
I have not found a fix. I reverted back to KitKat since I needed to use my phone during the week.
Bump
I finally managed to fix the problem. All the clean flashes did nothing, and I made sure they were squeaky clean, so I decided to start from scratch. I ODIN'd back to stock, installed TWRP instead of Clockworkmod, and reinstalled the rom and gapps package. I booted into the setup wizard and all is right in the world. Thanks for all who helped me!
Do you know what version of CWM you were running? I might try updating it over the weekend and see if that works as an alternate solution.
Try this. This worked for me.
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
Gapps crashes
rowdypixel said:
I tried that one again - no dice. com.google.process.gapps crashes on startup, followed by a long list of other Google apps included in the package.
Click to expand...
Click to collapse
Before adding gapps after flashing cm-12 wipe dalvik and cache, flash ktoonz lollipop kernel then flash gapps for lollipop. This worked for me.
anonymousguy44 said:
I finally managed to fix the problem. All the clean flashes did nothing, and I made sure they were squeaky clean, so I decided to start from scratch. I ODIN'd back to stock, installed TWRP instead of Clockworkmod, and reinstalled the rom and gapps package. I booted into the setup wizard and all is right in the world. Thanks for all who helped me!
Click to expand...
Click to collapse
Hey I'm having the same problem, can you describe how in Odin you got back to stock? You flashed stock and lost your custom recovery? That's weird, I figured a custom recovery was like a bios
http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
I think is a good idea to say which rom are we using and how xposed works on it. Its still an alpha, and there are many mods that dont work too. Users as @mrnickel have reported that the phone gets REALLY SLOW, and some issues like low memory.
INSTALL (at your own risk) INSTRUCTIONS:
-Make a nandroid backup
-Install apk from the thread link above
-Flash the framework zip from the same thread (updated version, bridge version 61 or up, if you flash 60 it wont work)
-Wipe dalvik cache and cache
-Reboot
Confirmed "working" on 100% stock rooted. [Thanks @jabskii. @Jhyrachy @thdervenis]
Confirmed "working" on TitanPrime ROM (now even better, the dev implemented full support for xposed)[Thanks @pantu99]
All credits to @rovo89
I tried it. Don't do it. I installed from the recovery and this happens:
1st- My cellphone is now broken. Whatsapp won't work.
2nd- My cellphone now tells that I have almost all storage full when it's not possible (see attached screenshots)
3rd- Xposed won't work
oscillat0r.lfo said:
I tried it. Don't do it. I installed from the recovery and this happens:
1st- My cellphone is now broken. Whatsapp won't work.
2nd- My cellphone now tells that I have almost all storage full when it's not possible (see attached screenshots)
3rd- Xposed won't work
Click to expand...
Click to collapse
What Rom?
Whatsapp works for me. But I have those other two bugs...dat storage and xposed doesnt work
Whatsapp started working with a reset. My system lost its date and time.
I set that up again and it's working.
The OS is titanrom with lollipop 5.0.2. The OS is working really really slow right now. It sucks because I installed it before going to vacation, not so wise move.
GUYS! DON'T INSTALL IT!
oscillat0r.lfo said:
Whatsapp started working with a reset. My system lost its date and time.
I set that up again and it's working.
The OS is titanrom with lollipop 5.0.2. The OS is working really really slow right now. It sucks because I installed it before going to vacation, not so wise move.
GUYS! DON'T INSTALL IT!
Click to expand...
Click to collapse
Keep calm, de dont know how doest it goles con Cm12 or 100% stock
I flashed it a first time:
errors with clock and disk space
Then i reflashed it again and wiped cache.
Now it works !
Jhyrachy said:
I flashed it a first time:
errors with clock and disk space
Then i reflashed it again and wiped cache.
Now it works !
Click to expand...
Click to collapse
Did you wipe dalvik too?
Humm, too late now. I will try tomorrow flashing the zip and then wiping cache and dalvik for the lulz
oscillat0r.lfo said:
Did you wipe dalvik too?
Click to expand...
Click to collapse
yes
I installed it and flashed then wiped dalvik and cache and it worked and said it installed. After boot xposed said it was installed but when I rebooted again it says xposed
Framework not installed is anyone else getting this?
Flashed in stock rom got storage bug
Flashed in cm12 no storage bug but module doesn't work and it's not a problem with module.
Just installed on XT1068, stock 5.02.
Wiped Dalvik/Cache
WORKING
Burned Toast
BlackList Pro
Native Freezer
YouTube AdAway
No Safe Volume Warning
XGEL Settings
App Settings
Network Speed Indicator
Ringer and Notification unlink
YouTube Background Playback
Exchange Bypass for Xposed
NOT WORKING
Complete Action Plus
DoubleTapToSleep
Recent Apps Cleaner
Play Store in App Info
XInstaller
APM+
Very happy with Xposed Lollipop so far!
I will continue testing modules. I am sure that pretty soon module developers will bring them up to date with Xposed Lollipop.
Jhyrachy said:
yes
Click to expand...
Click to collapse
100% stock 5.0.2?
laureano97 said:
100% stock 5.0.2?
Click to expand...
Click to collapse
100% Stock + Root
Clean install 5.0.2 with fastboot flash and root. I use TWRP.
I flashed first time, booted, refleshed and wiped cache (both) and then all worked
A lot of modules are still not compatible :/
Please and step-by-step how to install and how to copy files for 5.0.2 stock rom root
Thanks in advance
half269 said:
Please and step-by-step how to install and how to copy files for 5.0.2 stock rom root
Thanks in advance
Click to expand...
Click to collapse
1-Install a custom recovery
2-Make a nandroid backup from recovery (to sdcard1 is better, more free storage I think)
3-Install the apk from here http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
4-Flash the zip from the same thread
5-Wipe cache and dalvik
6-Reboot
In case of bootloop or something gets wrong, boot into recovery and restore the backup you did before flashing
I think its obvious, but all credits to @rovo89
Its working on my XT1068 titan prime ROM
I downloaded the apk and the zip
Installed the apk
And manually installed zip in twrp
After installing I wiped cache/dalvik cache and rebooted. Working flawlessly
This app CPU temp in status bar works but you cannot enter the app. It shows up on my status bar when I enable it on xposed installer .. Other than that this is awesome ! Thanks @laureano97
Sent from my XT1068/69 using XDA Free mobile app
If you guys are having issues like enough storage space or modules not working
1)Flash the zip into your recovery
2)Wipe Cache and Dalvik Cache
That will get rid of your "enough storage space" error
If some modules won't work its because it hasn't been updated for lollipop to work but some modules can work by changing SELinuxMode to permissive
To do that just search "SELinuxModeChanger" in appstore then once installed open it and change it to permissive then reboot your phone.
App Setting is working on my 5.0.2 Stock Lollipop but I tried Greenify and it wouldn't recognize if I installed greenify so it probably hasn't been updated to work in Lollipop and maybe some modules is also the same
OP updated
It seems like the zip rovo89 fisrt uploaded didnt work fine...An hour later he updated it. That was the problem when I flashed it first time. Bridge must be 60 or up
Ok so the main reason for Xposed not working on Xperia Z2/Z3/Z3c Lollipop 5.0.2 was that it lacks recovery and Xposed for lollipop only installs via recovery, and manual pushing resolting in bootloop. Well a kinda found a solution for this. Its actualy simple. Here we go:
WARNING: DO THIS AT YOUR OWN RISK PLEASE MAKE A BACKUP YOU MIGHT NEED TO REFLASH
Requirements:
Z2/Z3/Z3c Rooted Lollipop 5.0.2 Stock Rom with unlocked bootloader
You need to download
1. Nut's Adv Stock Kernel with recoveryes (?) from here http://nut.xperia-files.com/ (Cick te XZDualRecovery Kernel tab in the right side of the site/ Click "Yes i have an unlocked bootloader / Select your model in the drop down menu (in this case its the Z2 D6503) / Select your firmware (in this case the 23.1.A.0.690 lollipop fw from all the way down in the drop down menu) / Click D6503_23.1.A.0.690_XZDRKernel2.8.3-RELEASE.flashable.zip and download.
2. Any 4.4.4 Kernel with recovery as boot.img
3. Flashtool
4. Xposed Lollipop Files from HERE Namely the xposed-arm-20150308.zip for flashing and XposedInstaller_3.0-alpha2.apk for running the modules.
And here we go:
1. After you download Nut's adv kernel and xposed zip file put them in internal memory
2. Install xposed for lollpop apk
3. First open Flash tool select Fastboot mode (without selecting anything yet), connect your phone (holding volume up) to your pc entering fastboot mode (while connected your phone led should be blue). Now in flash tool select kernel to flash and choose your 4.4.4 boot.img (kitkat kernel with actual working recovery) and flash.
4. After flashing the 4.4.4 Kernel reboot your device continuasly pressing the volme up button while rebooting (especialy when the sony logo appears) thus entering a 4.4.4 kitkat recovery.
5. After entering the recovery select flash zip from internal memory card, select the xposed zip file, flash and do not reboot, browse agan and search for nut's adv kernel select it and flash again but do not reboot device, WIPE ALL CHACHE'S especialy Dalvik/ART after that reboot
6. Reboot and wait util the apps update.
7. After that your phone will start as normal. Entering the Xposed App will show that it needs to be flashed via recovery. Select soft reboot. Selecting it resolts in a bootloop, dont panic
8. After entering the bootloop, power off your phone , flash 4.4.4 kitkat kernel with working recovery , after that enter the recovery, flash nut's adv kernel again, WIPE Cahe again (normal an dalvik) reboot , wait for the apps to optimize and woala. You have Xposed working.
NOTE.
1. Entering the xposed app my show that it needs to install via recovery, ignore that, the modules work. I'll upload a video for proof of a module working on 5.0.2 Lollipop
2. This is a temporary workaround, i dont know how much it will hold until a normal fix show's up
IF YOU LIKE IT HIT THE THKS BUTTON
AS I FOUD OUT AT SOME POINT WHEN YOU REBOOT YOUR DEVICE IT ENTERS BOOTLOOP UNLESS YOU CLEAR CACHE AND DALVIK CACHE AT BOOT UP... So..
Proof
https://www.youtube.com/watch?v=2jBvg5irGgA
Hey wanted to ask you about what happens if you reboot the phone? will it break?
Reboot bootloop
So I have bootloop issue once I reboot the phone after installing xposed apk. I removed .jar file and deleted .apk from CWM (using adb shell)
then it was fine.
Thanks for your instruction!
But as others, I have boot-loop problems too. I've done what you wrote, but everytime I rebooted, I got the boot-loop.
If I could wipe cache/dalvik-cache everytime before the phone started, xposed would work.
Somebody told me the boot-loop is related with Titanium Backup. Then I deleted TB, but the boot-loop came as usual...
So...How to make xposed work as normal?
Thanks again!
[email protected] said:
Thanks for your instruction!
But as others, I have boot-loop problems too. I've done what you wrote, but everytime I rebooted, I got the boot-loop.
If I could wipe cache/dalvik-cache everytime before the phone started, xposed would work.
Somebody told me the boot-loop is related with Titanium Backup. Then I deleted TB, but the boot-loop came as usual...
So...How to make xposed work as normal?
Thanks again!
Click to expand...
Click to collapse
the same to you,my phone is l50u,how about yours?
hubo19890319 said:
the same to you,my phone is l50u,how about yours?
Click to expand...
Click to collapse
放弃了……没准儿之后更新的时候能搞定……
其实现在主要问题也就是插底座直接横屏和状态栏颜色的问题……
[email protected] said:
放弃了……没准儿之后更新的时候能搞定……
其实现在主要问题也就是插底座直接横屏和状态栏颜色的问题……
Click to expand...
Click to collapse
English please !
Sent From My Z2 On LP 5.0.2 Full Debloated !
When can we expect a recovery for lollipop?
Pandemic said:
English please !
Sent From My Z2 On LP 5.0.2 Full Debloated !
Click to expand...
Click to collapse
Sorry for that.
Using native language sometimes can save a lot of space and time.
Please forgive my poor English.
It would be really kind if you can ignore what I wrote before.
@beniamin24 - do we need to clear Dalvik/ART cache after every reboot once Xposed running, or only two times as mentioned in the instructions?
Edit: after each reboot I've got bootloop, clearing of the cache does help, but it takes too long to optimise all the applications, not worth the regular usage yet
Well now we do have recovery again. Makes all this a lot easier
perfect @AndroPlus
Reb0rn said:
Well now we do have recovery again. Makes all this a lot easier
Click to expand...
Click to collapse
yes man :good:
Guys, you already changed selinux yet? It has to be permissive.
I have TWRP working along side with Stock ROM since yesterday, as AndroPlusKernel is now available for 5.0.
I got the boot.img off AndroPlusKernel and flashed it via fastboot, now I can access TWRP.
So after many experiments: (get xposed-arm-20150308-1.zip which works on SELinux enforcing not xposed-arm-20150308.zip)
Installed Framework > Restart > Fine
Installed Framework > Installed Xposed APK > Restart > Bootloop
Installed Framework > Installed Xposed APK > Restart to recovery > Wipe Dalvik Cache > Fine [This is really hideous process as it will start Optimizing apps]
Maybe if you can provide catlogs to the Xposed thread to see if they can do something about it.
Sent from my D6503 using XDA Free mobile app
themightydeity said:
I have TWRP working along side with Stock ROM since yesterday, as AndroPlusKernel is now available for 5.0.
I got the boot.img off AndroPlusKernel and flashed it via fastboot, now I can access TWRP.
So after many experiments: (get xposed-arm-20150308-1.zip which works on SELinux enforcing not xposed-arm-20150308.zip)
Installed Framework > Restart > Fine
Installed Framework > Installed Xposed APK > Restart > Bootloop
Installed Framework > Installed Xposed APK > Restart to recovery > Wipe Dalvik Cache > Fine [This is really hideous process as it will start Optimizing apps]
Click to expand...
Click to collapse
Could you please upload the file somewhere? It is not available on dropbox anymore. Thanks!
_mysiak_ said:
@beniamin24 - do we need to clear Dalvik/ART cache after every reboot once Xposed running, or only two times as mentioned in the instructions?
Edit: after each reboot I've got bootloop, clearing of the cache does help, but it takes too long to optimise all the applications, not worth the regular usage yet
Click to expand...
Click to collapse
Yes, after installing xposed and modules, Dalvik Cache must be wiped at every reboot or we get bootloop !!! It's not bearable...
This issue might be fixed if SElinux permissive mode would be enabled by default in the advanced LP kernel. I've just requested AndroPlus to do it.
_mysiak_ said:
Could you please upload the file somewhere? It is not available on dropbox anymore. Thanks!
Click to expand...
Click to collapse
Here you go:
[MEGA] xposed-arm-20150308-1.zip
[Mediafire] xposed-arm-20150308-1.zip
I have TWRP recovery and I've installed the Rom without any errors showing up but when I try to boot the phone up it doesn't go past the cm logo screen. It keeps pulsating slowly then goes faster then just stays there. I've waited about an 1hr or 1hr n a half for it to load but nothing happend I've installed gapps for 6.0 stock I have Jasmine ROM 7.0 installed with xposed framework.
Q) Do i need the stock Rom for this phone to install cm13
Q) Does it take a long time to load?
Q) Did I miss a step?
I used the forum http://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973/page406 and made sure I had everything I didn't change animation scales because couldn't find the setting, multi window is already on I belive n xposed was installed with Jasmine ROM and gapps.
I rebooted to recovery
Factory reset
Wipe > advanced > system, data, cache, dalvik
(I have a backup just in case)
Installed cm13
Wiped cache
Installed gapps
Wiped cache
Rebooted
Then it gets stuck at the cm13 logo that's pulsating.
My solution:
I downloaded the boot.img file provided by weard1212 https://dl.dropboxusercontent.com/u/9399595/boot.img
You will need it for it to boot up.
Reboot recovery
Wipe >advance >system,data,cach,dalvik
Install cm13
Wipe cache
Install Gapps
Wipe cache
Then go to home menu
Install click install IMG
Look for IMG file then install
Reboot
DONE
-spektor- said:
I have TWRP recovery and I've installed the Rom without any errors showing up but when I try to boot the phone up it doesn't go past the cm logo screen. It keeps pulsating slowly then goes faster then just stays there. I've waited about an 1hr or 1hr n a half for it to load but nothing happend I've installed gapps for 6.0 stock I have Jasmine ROM 7.0 installed with xposed framework.
Q) Do i need the stock Rom for this phone to install cm13
Q) Does it take a long time to load?
Q) Did I miss a step?
I used the forum http://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973/page406 and made sure I had everything I didn't change animation scales because couldn't find the setting, multi window is already on I belive n xposed was installed with Jasmine ROM and gapps.
I rebooted to recovery
Factory reset
Wipe > advanced > system, data, cache, dalvik
(I have a backup just in case)
Installed cm13
Wiped cache
Installed gapps
Wiped cache
Rebooted
Then it gets stuck at the cm13 logo that's pulsating.
Click to expand...
Click to collapse
Before flash cm rom You will need 5.1.1 stock lollipop bootloader to make in boot if you are on marshmallow 6.0..1 it wont boot.
Just flash 5.1 bootloader it will boot fine
-spektor- said:
I have TWRP recovery and I've installed the Rom without any errors showing up but when I try to boot the phone up it doesn't go past the cm logo screen. It keeps pulsating slowly then goes faster then just stays there. I've waited about an 1hr or 1hr n a half for it to load but nothing happend I've installed gapps for 6.0 stock I have Jasmine ROM 7.0 installed with xposed framework.
Q) Do i need the stock Rom for this phone to install cm13
Q) Does it take a long time to load?
Q) Did I miss a step?
I used the forum http://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973/page406 and made sure I had everything I didn't change animation scales because couldn't find the setting, multi window is already on I belive n xposed was installed with Jasmine ROM and gapps.
I rebooted to recovery
Factory reset
Wipe > advanced > system, data, cache, dalvik
(I have a backup just in case)
Installed cm13
Wiped cache
Installed gapps
Wiped cache
Rebooted
Then it gets stuck at the cm13 logo that's pulsating.
Click to expand...
Click to collapse
Don't flash the 5.1 bootloader, you need to flash the 7/24 build kernel from here: https://dl.dropboxusercontent.com/u/9399595/boot.img after you do the steps you have already done
---------- Post added at 07:21 PM ---------- Previous post was at 07:17 PM ----------
Trex888 said:
Before flash cm rom You will need 5.1.1 stock lollipop bootloader to make in boot if you are on marshmallow 6.0..1 it wont boot.
Just flash 5.1 bootloader it will boot fine
Click to expand...
Click to collapse
Flashing the stock bootloader on the Verizon note 4 will re-lock it and they are talking about hsbdr's cm13 on the Verizon form
weard1212 said:
Don't flash the 5.1 bootloader, you need to flash the 7/24 build kernel from here: https://dl.dropboxusercontent.com/u/9399595/boot.img after you do the steps you have already done
---------- Post added at 07:21 PM ---------- Previous post was at 07:17 PM ----------
Flashing the stock bootloader on the Verizon note 4 will re-lock it and they are talking about hsbdr's cm13 on the Verizon form
Click to expand...
Click to collapse
So all I have to do is flash the boot.img file through flash fire then install cm13 via TWRP?
I figured it out thanks for the help
Can i have that boot.img?
Can you Update the link please
I am having issues installing the xposed framework. I have rooted with Magisk successfully and I'm on the ElementalX kernel. When I try to install the xposed framework via TWRP, when I reboot back into the OS, it gets stuck in a hello moto bootloop. I can boot into the OS without issue by clearing the dalvik cache and the normal cache after installation, but when I get into the Xposed installer app, it says it's installed but not running. There is no log, so I assume it is because the Xposed folder doesn't have permissions. I give it permissions and reboot by pressing restart in the power menu, but when I do that, it gets in the bootloop again.
I would appreciate any help on this.
MineMasterHD said:
I am having issues installing the xposed framework. I have rooted with Magisk successfully and I'm on the ElementalX kernel. When I try to install the xposed framework via TWRP, when I reboot back into the OS, it gets stuck in a hello moto bootloop. I can boot into the OS without issue by clearing the dalvik cache and the normal cache after installation, but when I get into the Xposed installer app, it says it's installed but not running. There is no log, so I assume it is because the Xposed folder doesn't have permissions. I give it permissions and reboot by pressing restart in the power menu, but when I do that, it gets in the bootloop again.
I would appreciate any help on this.
Click to expand...
Click to collapse
I had this problem also, I would typically just long press the power button and let it complete a second normal boot, and then xposed would work after the second boot completed. (The second boot after initial bootloop would load up just fine.) However, after a few reboots, my phone became unstable and I had to reflash the stock ROM. I'm not sure how stable OREO xposed is on this device yet. It may have just been my modules. (GravityBox, Flat Color Keyboard, Bars, and Status Icons)
Drkmatr1984 said:
I had this problem also, I would typically just long press the power button and let it complete a second normal boot, and then xposed would work after the second boot completed. (The second boot after initial bootloop would load up just fine.) However, after a few reboots, my phone became unstable and I had to reflash the stock ROM. I'm not sure how stable OREO xposed is on this device yet. It may have just been my modules. (GravityBox, Flat Color Keyboard, Bars, and Status Icons)
Click to expand...
Click to collapse
I also have a Moto G5 plus and when I tried to reboot it a second time it was still stuck in its boot loop so I had to enter TWRP to flash the uninstall and if I try to install Xposed via Magisk I have to factory reset, I don't think it's me ROM because it's the same as a stock ROM (had to install the ROM because the one it came with got corrupted or something when I tried to install Xposed where I still had the boot loop problem). I am running 8.1.0 Oreo.
I think a lot of my problem was i was using a sprint variant also. I think a lot of other users are using the verizon/t-mobile variants. I never really did get xposed to work properly on oreo on the sprint variant of this phone no matter what i tried.
Any news on this issue?
I just updated to 8.1 and would like to get xposed up and running like I had it on Nougat. Has there been any fixes yet to this. Thanks to anyone for a reply.
I get bootloop when I install magisk & xposed.
I am using Xposed since months
Working fine
One thing you is that we've to do soft reboot instead of regular reboot