Database Users

Xposed Installer for Lollipop in ON!

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.

XPOSED For Z2 Lollipop 5.0.2 (Maybe Z3/Z3c) (Temporary)

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

Cannot install any app on miui 7 rom

I just installed MIUI 7 ROM on my Lenovo A6k . First I wiped everything then I installed the patch and then the ROM . everything works fine but I couldn't install the gapps but when I open rom I see everything fine. And all gapps are there but I can't install anything from play store or my sdcard it says app not installed. Pls help

Exactly the same issue i am facing.
Tried wiping dalvik cache ,flashing rom and patch many times.
Can anyone help?
This rom is my first love.

ShakuniMama said:
I just installed MIUI 7 ROM on my Lenovo A6k . First I wiped everything then I installed the patch and then the ROM . everything works fine but I couldn't install the gapps but when I open rom I see everything fine. And all gapps are there but I can't install anything from play store or my sdcard it says app not installed. Pls help
Click to expand...
Click to collapse
1. Install xposed framework from recovery.
2. Enable all module in xposed installer app.
3. Reboot / soft reboot

If you want MIUI 7 so bad. Use MIUI 7 KK. It's same with LP version. But KK use dalvik runtime and LP use ART.
you can use MoStock kernel to MIUI 7 KK. No bug

Issue fixed, all things are working fine .Started loving this rom.
But there is one problem .4G is not working. But internet is working fine.
Any fix for that?

Ok i got it !! I was using third party gapps. SO first flash the gapps given in the thread and then the xposed in the thread and then done ! It now fine but a lil bit laggy

i installed miui 7 in a6000 .
it is working fine.
now iam unable to flash other Roms.
unable to remove miui logo i tried to remove bootanimation.zip but its not working.
any solution

Besant George said:
i installed miui 7 in a6000 .
it is working fine.
now iam unable to flash other Roms.
unable to remove miui logo i tried to remove bootanimation.zip but its not working.
any solution
Click to expand...
Click to collapse
Use es explorer for that. And go to options>>tools>>root manager>>switch it on and then click on it>>Mount R/W>>select "/system and /" or any other.
Then go to /system/media/ and replace bootanimation.zip

Acquiring root after Temasek's CM 13 marshmallow install

Hello, I've recently installed Temasek's CM 13 nightly marshmallow build to my bootloader unlock note 3. I'm having a difficult time acquiring root after the install. I've flashed SuperSu to no avail. I've even tried the Aramaic tool method with no luck. Is there anything I can do to get root back on this phone or am I screwed?

Look for SuperSU in the settings menu.
Not sure if you need to turn on developer options for it to appear there or not.
[Edit]Did you install CM with a custom recovery, or with flashfire?
Your post doesn't say one way or another, but if you have an unlocked bootloader you can flash a custom recovery using Odin... meaning that you always have root, so long as you preserve the unlocked bootloader.
Having only a single root (locked bootloader and no custom recovery) and using FlashFire to install a ROM puts you at constant risk of root loss.
.

Thanks for your reply. I have TWRP 3.0.2 installed. I didn't check to see if it was installed under settings but I have since restored back to my stock rooted ROM. I will reinstall CM again and let you know if SuperSu shows up in settings.

cblendz said:
Thanks for your reply. I have TWRP 3.0.2 installed. I didn't check to see if it was installed under settings but I have since restored back to my stock rooted ROM. I will reinstall CM again and let you know if SuperSu shows up in settings.
Click to expand...
Click to collapse
Hey.
Just to make sure I'm being clear - you do have to flash SuperSU along with the ROM flash - root is not "baked in" to CM.
For some reason CM "hides" the SuperSU app so that it only shows up in the Settings menu and not in the app drawer.
It wasn't clear from the way you described things if that's what was going on, but I remember having the same (?) experience ... I thought the install of SuperSU was somehow missing due to the fact it didn't show up in the app drawer.
.

bftb0 said:
Hey.
Just to make sure I'm being clear - you do have to flash SuperSU along with the ROM flash - root is not "baked in" to CM.
For some reason CM "hides" the SuperSU app so that it only shows up in the Settings menu and not in the app drawer.
It wasn't clear from the way you described things if that's what was going on, but I remember having the same (?) experience ... I thought the install of SuperSU was somehow missing due to the fact it didn't show up in the app drawer.
.
Click to expand...
Click to collapse
I've just tried reinstalling the cm13 ROM again and this time I checked to see if SuperSu was installed in settings. It didn't show up there either. I don't know what's going on with it. I wipe everything then flashed the ROM then wiped dalvik and cache. Then flashed open Gapps. Wiped dalvik and cache and flashed 2.78 SuperSu and reboot to system.

cblendz said:
I've just tried reinstalling the cm13 ROM again and this time I checked to see if SuperSu was installed in settings. It didn't show up there either. I don't know what's going on with it. I wipe everything then flashed the ROM then wiped dalvik and cache. Then flashed open Gapps. Wiped dalvik and cache and flashed 2.78 SuperSu and reboot to system.
Click to expand...
Click to collapse
I don't know if this would make a difference, but somewhere in that thread trader418 mentioned that you had to flash the ROM after the Gapps to take care of an issue with some init.d scripts. As in the sequence: wipe - ROM - gapps - ROM - supersu - first_boot.
I'm not sure if that's related or not. It's been long enough ago that I can't remember the exact details, but I remember thinking "hey, where did it go, I know I flashed it!".
Maybe it would be best to ask this question in that thread.
.

bftb0 said:
I don't know if this would make a difference, but somewhere in that thread trader418 mentioned that you had to flash the ROM after the Gapps to take care of an issue with some init.d scripts. As in the sequence: wipe - ROM - gapps - ROM - supersu - first_boot.
I'm not sure if that's related or not. It's been long enough ago that I can't remember the exact details, but I remember thinking "hey, where did it go, I know I flashed it!".
Maybe it would be best to ask this question in that thread.
.
Click to expand...
Click to collapse
Thanks a lot that was it. Finally got root. I wish CM would bake root in their Roms but all is good now. Thanks.

About latest Magisk v13.

Hello everyone.
So like many I was using Magisk for root purposes on my device, more specifically v12.
It was working flawlessly until now, only thing was that Google updated their safety and safetynet would fail for a couple of weeks but I didn't mind much.
I got a notification last night that v13.1 is out and I tapped on it and tapped download and install now.
I did just that, rebooted the device and to my surprise Magisk had stopped working.
Once I entered the manager app the app would force close, i tried multiple times opening it and the result was the same.
I tried flashing the uninstaller and the un-su zip and flashed v13.1 again but the same thing happened.
I tried clearing cache and dalvik cache but it didn't help.
I even tried going back to v12 but to my surprise again v12 was force closing too!
I ended up flashing the trusted old SuperSU but I really need magisk for some modules I use.
I searched the magisk subforum but couldn't find anything that fixed it for me.
Had anyone had the same experience?
Is magisk v13.1 working for you?
How did you update? (if you were running v12)
EDIT:
Thanks to @seko85, anyone who had this issue disable all substratum themes and also do this:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)

Clear Data from Settings - Apps - Magisk Manager.

mobidor said:
Clear Data from Settings - Apps - Magisk Manager.
Click to expand...
Click to collapse
I did that, enabled any permissions required as well.
Are you using v13.1?

If you're on B25, MagiskSU force closes when allowing a "new" app root, so that could be behind the crashes

Make sure that you have the latest version of magisk manager installed. Since the app got removed from the playstore you have to update manually.

Cyb3rzombi3 said:
Make sure that you have the latest version of magisk manager installed. Since the app got removed from the playstore you have to update manually.
Click to expand...
Click to collapse
I did yeah, the latest version is 5.0.4?

Yeah got 5.0.4 as well and latest magisk is running fine.
If that is not the problem then I don't know what else it could be
Which rom do you have installed?

nfsmw_gr said:
I did that, enabled any permissions required as well.
Are you using v13.1?
Click to expand...
Click to collapse
Yes, and no problem. Installed with TWRP.

nfsmw_gr said:
Hello everyone.
So like many I was using Magisk for root purposes on my device, more specifically v12.
It was working flawlessly until now, only thing was that Google updated their safety and safetynet would fail for a couple of weeks but I didn't mind much.
I got a notification last night that v13.1 is out and I tapped on it and tapped download and install now.
I did just that, rebooted the device and to my surprise Magisk had stopped working.
Once I entered the manager app the app would force close, i tried multiple times opening it and the result was the same.
I tried flashing the uninstaller and the un-su zip and flashed v13.1 again but the same thing happened.
I tried clearing cache and dalvik cache but it didn't help.
I even tried going back to v12 but to my surprise again v12 was force closing too!
I ended up flashing the trusted old SuperSU but I really need magisk for some modules I use.
I searched the magisk subforum but couldn't find anything that fixed it for me.
Had anyone had the same experience?
Is magisk v13.1 working for you?
How did you update? (if you were running v12)
Click to expand...
Click to collapse
I had the same situation. The solution was:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Root is working and passed safety net. Unfortunately I couldn't manage to run Dolby Lee Pro 3 by ahrion and I suppose that also war mod is not working (post data script is not working, using Magisk v12 I saw in Magisk log that war mod was executed now with Magisk v13.1 I don't see such message).

seko85 said:
I had the same situation. The solution was:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Root is working and passed safety net. Unfortunately I couldn't manage to run Dolby Lee Pro 3 by ahrion and I suppose that also war mod is not working (post data script is not working, using Magisk v12 I saw in Magisk log that war mod was executed now with Magisk v13.1 I don't see such message).
Click to expand...
Click to collapse
Alright that advice step by step was great!
Gonna try this once I get home and post back, thanks man!

Update, thanks to @seko85 and disabling any substratum theme (dunno which made it work, could be both together as well) I managed to fix the issue.
Magisk v13.1 is up and running.
Also thanks to everyone who replied.
Peace, out.