yashsingh1/xdaforums huggingface dataset:
[Xposed General] GRLDT:
Okay. I was here and I was saying that some modules didn't work on my device (grand 2 cm12.1 5.1.1_r4). I tried to reinstall those modules and reboot from xposed, and the modules work again. After my device rebooted (for no reason, maybe out-of-ram?), those modules didn't work again, and I got the same error message "file does not exist" in xposed logs. Does anyone got this exact issue? Please reply :)

Sent from my SM-G7102
[Xposed General] mayank22:
me too getting same error and bootloop after flashing xposed on latter cm12.1
[Xposed General] DroidIt!:
Just curious, what makes you think you're out or ram? Has it happened before? I've not ever ran into a ram problem so honestly I haven't experimented with what would open up ram, but maybe try greenify? Or if greenify doesn't do it, maybe try tibu and freezing apps, install & apply the modules you want first and then unfreeze the apps. One other thing is you could look at what apps are consuming the most ram and get rid of one or two if possible. Just some ideas off the top of my head. :)
[Xposed General] kindofabuzz:
Why is the title of the post not updated? I never knew there was an update until i saw a post on reddit mentioning it.
[Xposed General] ldeveraux:
What exactly do you want updated?
[Xposed General] danarama:
It matches the latest update in post 1.
[Xposed General] magnamentis:
search and read and you'll know, the newer version is not from the OP
[Xposed General] danarama:
The official unofficial version is. The one in the thread is unofficial unofficial, so never made it to OP :)
[Xposed General] GRLDT:
First, yes, this has happened before. Second, how do I freeze / disable apps when my phone is already rebooting. I use servicely and disable & uninstall some useless apps. I also use some ram tweaks before the "out-of-ram" thing happened. This issue occurred in previous builds of CM12.1 for my device. There's possibility that this will happen again after new builds, and it happened.

Sent from my SM-G7102
[Xposed General] danarama:
From adb shell

pm disable <package name>

That's all Titanium Backup does. Uses android default package manager
[Xposed General] GRLDT:
I couldn't interface with my phone when it's rebooting, not even adb. It's happened anyway, so nothing can stop it from happening, even when you know it's going to happen.
[Xposed General] magnamentis:
right, basically what i meant, semantics once again LOL, thanks however to put it in perhaps better words, i just thought it's clear we're talking about the one in the thread, that's how i understood the question :)
[Xposed General] muschiu35bv:
Nexus 7 2013 trouble

Hello Guys!I have installed xposed 5.1 on my Flo device but sometimes i does not want to boot.I will stay on logo screen without booting even if ive delete cache and dalvik cache.And sometimes is booting normal.I want to mention that i have multirom and my primary rom is stock lollipop.Anyone knows a fix for my problem?
[Xposed General] n0obpr0:
Will this work(I Hope) with the moto x 2013 5.1?
[Xposed General] aillez:
you a life saver...

kinda annoying after reboot then re-optimzing apps.

:good:
[Xposed General] danarama:
Do this...

Google <phone model> CPU?

- If CPU is Intel, you can't use an arm version.

Google <CPU name> arm version?

- if CPU is ARMv8 use 64 bit zip. Otherwise use other.

Answers....

Snapdragon S4

ARMv7

So you need the non-64 bit version.
[Xposed General] phoberus:
Ich habe das selbe Problem. Laut dem amplify thread ist es von Gerät zu Gerät sehr Unterschiedlich ob es funktioniert.

Hast du es in der Zwischenzeit geschafft?
[Xposed General] Ja_som:
English only, on this forum, read rules.
[Xposed General] atamig:
run this version only on 64bit devices?
[Xposed General] Se4fl0w3r:
dear friend

i signed the xposed-sdk22-arm.zip file with "sign em" software in pc and i success to flash this zip file in my recovery successfully, but i wait for boot to start my device a long time ,and nothing to start ! ( i wait for 15 min to start ! )

what's the problem ?!

rom candy5 android 5.1.1

device : xperia pro (mk16i)
[Xposed General] mielletseed:
When you look at the first post you will find two versions, one for "normal" arm devices (32 bit) and one for 64 bit arm devices. So the answer is: it depends ;)
[Xposed General] DroidIt!:
Heya [MENTION=2872010]danarama[/MENTION], completely OT but if you see somebody on G+, it's Kevin ;)
[Xposed General] danarama:
Cool
[Xposed General] Wakamatsu:
Are you asking his advice so you can disregard it again?
[Xposed General] herny66:
sorry but Xposed installer after installation in the info I read Alpha3,

where can I find the version alpha4 ... thanks
[Xposed General] magnamentis:
that's not the framework installer but the app. you have to install the framework via .zip file which you find in the unofficial xposed thread from romracer: http://xdaforums.com/xposed/super-alpha-posted-permission-xposed-t3072979
[Xposed General] matcho13579:
Today, I flashed a LMY48B build, after that I flashed Xposed and tablet is not booting (Nexus 7 2013, using OptiPop ROM).. previous build was working fine with Xposed flashed (LMY47V)
[Xposed General] quack75:
Are you sure? Last Xposed installer is Alpha2 I have read
[Xposed General] magnamentis:
hey guys, please start to read before filling the thread repeatingly with all together dozens of pages, arguing back and forth about alphaX and alphaY

there are better descriptions as to what you're talking about. the xposed installer is the app and the way to flash xposed is the sdk, so if you talk about flashing xposed framework it's and sdk.zip and if you want to install the app it's xposedinstaller.apk.

as to the version it's 3.0 please find the link below, while i think it should really not be that hard to keep track with only two threads of which one is updated once every few weeks only and else closed for good reason, to avoid exactly this kind of ignorant talk. should anyone feel offended, so what these are the facts:

http://xdaforums.com/showpost.php?p=58828974&postcount=1
[Xposed General] herny66:
ok thanks...I had read of alpha4 but installer is an alpha2...in material
[Xposed General] DPinched:
I updated the latest OTA on my one plus and can't install Xposed either.

I have downloaded the above link and can say it still gives "wrong sdk expecting 22" error.

:(

Thank you for trying.

Without Xposed installed I've forgotten how unusable the internet is on my phone, literally hundreds of ads appearing all over the screen, terrible :(
[Xposed General] quack75:
This is the reason why I asked which version of installer.apk

I follow this thread always and I installed everything correctly on different types of Rom , but there are in this thread and in many other, unofficial versions of sdk.zip and installer.apk deserve to be tested , so if it were possible share version Material design , I 'd be interested

I do not think anyone will be offended by such talk , and I do not consider these words ignorant
[Xposed General] DPinched:
I updated my OnePlus with latest OTA incremental YNG1TAS2I3 and was not able to install latest xposed framework... I went back to the official page and downloaded 3.0 alpha4 and the install worked!

Thought I'd share.

http://xdaforums.com/showthread.php?t=3034811
[Xposed General] mayank22:
You are running 5.0 or 5.1?
[Xposed General] gothicVI:
Yes, I solved the problem using the trick mentioned in the amplify thread: http://xdaforums.com/showthread.php?p=60994798
[Xposed General] phoberus:
Thank you, will try this
[Xposed General] Meneldur:
It doesn't hurt noting this and helping people find the post with the update. For me official alpha 4 has problems unofficial unofficial version doesn't.

I understand we all must search and walk our path but not saying anything just to follow rules I believe is pointless.
[Xposed General] dk_zero-cool:
Xposed SDK22 20150624

Rovo89 added a few new things 3 days after C3C076 posted some updated builds. Since the latest work has still not been posted here, I thought that I would, since I have already build it for myself. One of the most important changes, is that Native Methods can once again be hooked (Has been disabled in all ART versions since the first alpha). This is used by a number of modules, which until now, has been missing some features because of this on all Lollipop devices.
[Xposed General] 089man:
Is this for 5.11 and works with aosp rom?

I9100 Tapatalk, DU AOSP 5.1.1 Lollipop
[Xposed General] magnamentis:
great contribution, thanks a lot and special thanks for not giving the build a name like "alphaX" LOL i think everyone knows why. JK

BTW did you try to find out whether romracer would be willing to add this to the OP for the sake of the thread remaining less clogged as compared to what happened since the last [unofficial]unofficial build? hope it's a welcome suggestion. :good:
[Xposed General] dk_zero-cool:
This whole thread is for android 5.1, so it would be strange of me to add Xposed versions for other SDK's. This release is the same as the ones provided by romracer and C3C076, just with 5-6 additional commits by rovo89 since the last release post.

It's a fine suggestion, but C3C076 tried the same two weeks ago, and still no answer. Think he is busy at the moment. He might be one of those strange people with a real life and all that weird stuff :-p
[Xposed General] szunyi77:
I tried it, no problem. It works perfectly so far. Note 2 Blisspop 5.1.1. What does that mean exactly? To explain? "Has been disabled in all ART versions since the first alpha). This is used by a number of modules, which until now, has been missing some features because of this on all Lollipop devices.
[Xposed General] dk_zero-cool:
Some methods in Android (What is a method? Google it) are not real Java methods. They are just gateways that allows a java method to execute a native method/function (C, C++ etc). For example XPrivacy uses 3 of these to add some camara restrictions, but these restrictions has not been working on Lollipop, because Xposed for lollipop has rejected modules from adding hooks to this type of method. Rovo89 enabled this a week ago and this change is in my release.
[Xposed General] Dark Shire:
Thank you very much [MENTION=2476451]romracer[/MENTION] for the Super Alpha!!! Xprivacy works again !!!! Yipee
[Xposed General] magnamentis:
as a little heads up for all:

a) Sygic Navigation is now working as should be the first time since 5.1.1 + Xposed KUDOS

b) AppSettings module ( per app dpi on rom with built in system setting for global dpi still does not work ( did work until 5.0.2 + Xposed

c) as to the rest, working great, no issues found
[Xposed General] GieltjE:
Sygic now is an even bigger crash fest than before for me.
[Xposed General] gothicVI:
For some strange reasons I get wrong SDK version. I'm on cm12.1 5.1.1 samsung galaxy ace 2 and the last version (the one in the thread not the latest one in op) has been working fine. Any suggrstions or ppl experiencing the same?
[Xposed General] magnamentis:
sorry to hear that, no crashes anymore here, very interesting. just tried to install the same sdk.zip on my nexus 5 running the same rom like on the oneplus and it failed with an error "wrong sdk = 19, expected 22 ) but the zip file IS the same and it has the 22 name. i suppose it's on the rom side, some identifier or whatsoever. strange how things go sometimes :) thanks for the heads up, so it's not universally working and i'll not further spread the good news.

BTW did you clear app data and caches and then reboot ? often helps, good luck
[Xposed General] Yom:
Thank you for your efforts. Sadly, this did not even allow boot on my Note 3 HLTECAN running PAC-ROM. It reboots right back into recovery after POST.
[Xposed General] gothicVI:
I get the message can't find /system and wrong SDK version expecting 22 :confused:
[Xposed General] siealex:
Any news on random bootloops? Today my phone started dexopting again even without the ".booting" file.
[Xposed General] lulli1:
where did you look for the .booting file?
[Xposed General] siealex:
data/dalvik-cache/arm
[Xposed General] steviemch:
No problems at all on mako with chroma rom. Many thanks.

sent by neural subspace transceiver node.
[Xposed General] 089man:
Have Flash new version, no problems at all here too. Samsung s2, DU AOSP 5.1.1 ROM..

great work thanks so much...

I9100 Tapatalk, DU AOSP 5.1.1 Lollipop
[Xposed General] slixzen:
Is it safe to say that this does not work with Android 5.1.1?

I recently factory restored the device because my device was just randomly shutting down. So I upgraded to 5.1.1. After flashing SuperSU, rebooting, then flashing Cerberus to /system and then flashing xposed on my Nexus 5, my phone just stays at the boot animation screen.
[Xposed General] DaveX2012:
Sygic don't work here. Temasek cm 14.1 HLTE
[Xposed General] Wakamatsu:
Works fine for me. Can be hit and miss depending on the rom.
[Xposed General] magnamentis:
EDIT: as stated earlier sygig works perfectly well now for me on OnePlus One Blisspop latest version while it does not work on my nexus 5, also blisspop latest version. as mentione this is strange, but that's probably what alpha means LOL, so don't worry all those where it does not work, it's obviously intermittent and differs from device to device even on same ROM.

also as mentioned earlier i was at first not able to flash the latest SDK on my Nexus 5. for your information, i changed from philz recovery to cwm recovery and it was working. another strange thing because cwm is old and basically somehow outdated and still it worked with cwm.

due to the sygic issue i reverted back to latest nandroid and refrain from using xposed on that device ( according to personal priorities )

so as you all can see there is currently no rule and/or reliable statement to make, we all have to find our for ourselves what works and what doesn't on which rom/device etc. configuration. just posting my findings as to whom it may interesest and/or concern.
[Xposed General] DaveX2012:
Well we'll wait next xposed update or sygic update.
[Xposed General] LyuboA:
S4 i9505 AICP CM12.1 ROM getting wrong sdk shows sdk 19 expect 22 no problems with 20150609 build any fix??

EDIT: used TWRP instead Philz recovery 20150624 build flashed no problems
[Xposed General] Reechings:
Is it recommended to reflash/dirty flash your rom before flashing the updated sdk or should it be safe to flash by itself over the 6-9 version? Cheers
[Xposed General] pyrorob:
Hi everyone, i was having an issue installing the 6/24 build and being who i am, i looked over the zip and compared it to previous releases and noticed the installer scripts were different then previous, so i fixed the scripts and it installed perfectly, (btw the error was that sdk22 wasnt detected) so i decided to re-up it here.View attachment xposed-sdk22-arm-20150624_fixed.zip
[Xposed General] C3C076:
Yes, original update-binary as found in official rovo's XposedTools will fail on devices with very little free space on system partition (stock Nexus 5 is just one example).

Which then results in incomplete files and consequent boot loops.

[MENTION=2476451]romracer[/MENTION] modified it so the original files are collected and zipped outside system partition and only after that are transferred to system partition.

[MENTION=3147360]dk_zero-cool[/MENTION] is probably using the original update-binary so people should make sure they have enough space (let's say at least 5MB) free on system partition before flashing.
[Xposed General] danarama:
Ensure your system partition is mounted read / write.
[Xposed General] lulli1:
there is a new unofficial version of app settings in the apps thread. it was not pushed to the xposed repo. so you have to download and install as a apk file. with that version the DPI setting is working again here...(nexus5 stock 5.1.1) the "show on lock screen" option still doesn't work, but some other settings do now.

here is the link

http://xdaforums.com/showthread.php?p=58843003
[Xposed General] danarama:
Great news thanks.
[Xposed General] pyrorob:
thats the thing, i was getting the sdk error and i have over 500mb free on /system

the script in the zip mounts /system as r/w. the script does it.
[Xposed General] C3C076:
That's a different issue.

If your ROM properties return SDK lower than 22, and you're on LP 5.1 then it's an issue with the ROM.
[Xposed General] danarama:
Believe it or not, Im actually familiar with updater-scripts. :)

After troubleshooting with a few people who were getting wrong xx version errors, we saw that the values from the build.prop were not being parsed and even when I removed the build.prop checks from the updater-script (well, binary in this case) then they were getting unable to mount system errors.

Now, most people have been able to mount system read write using TWRP terminal.

mount -o ro /system
mount -o rw,remount /system

It didn't work for one user though. That seemed to be a recovery issue.

So yeah first thing to check is that the system is mounting properly

Edit. Well second thing actually. First is check the build prop holds the correct SDK version. It's obvious when it's a system issue as the error in recovery says..

"Wrong sdk version , expected SDK 22"

See the blank space after version?
[Xposed General] pyrorob:
but replacing the binary resolved that and it still checked the sdk version, as far as i can guess its like one script reads the prop from the bootloader (or recovery?) and the other reads from the roms build.prop, anyway replaceing one of the binarys with the other resolves this.
[Xposed General] matssa:
Thanks for the files! Works nicely on the latest CM12.1 nightly on my 1+1, with the latest version of TWRP.
[Xposed General] gothicVI:
I'm using philz aswell but getting wrong sdk but not exspecting 19 but a blank space...

I will try your version right away :thumbup:

It should be. I never had problems like this ever before :eek:

What exactly is the problem then and how to solve it?

Yes, what does that mean?
[Xposed General] danarama:
Means the updater-binary was unable to find an SDK string in your build.prop.

Either, there is a problem in your build.prop (i.e not displaying the sdk string properly.) or system isnt mounting properly.

FYI, the updater-binary that generates that error is:

ui_print "! Wrong SDK version: $API, expected $XMINSDK - $XMAXSDK"

and API is defined:

API=$(cat /system/build.prop | grep "ro.build.version.sdk=" | dd bs=1 skip=21 count=2)

Which basically says:

Look for "ro.build.version.sdk=" in build prop, then save next 2 characters as API$

So to troubleshoot, check that "ro.build.version.sdk=" exists exactly in build.prop and that there are 2 characters after it. If there are, then API should NOT be blank and probably means system is not mounting, in which case, you can try mounting system via the menus, though Philz is build on an out-of-date CM version now isn't it? Kit Kat? So I would probably recommend as Phil does, go to TWRP and test there.
[Xposed General] gothicVI:
I find:

ro.build.version.sdk=22

That is what I expected actually since it worked all the time before this "update"... :confused:

I will try to find twrp but I'm not sure if there is a recent version for my old phone :(
[Xposed General] danarama:
Try and mount system in Philz first
[Xposed General] Farrys:
Fixed zip worked

Just want to thank you for the fixed zip. Tried all versions on LG G4, always bootloop!

I flashed the fixed sdk... No bootloop!

I had to use the two lines of code, from Danarama further down this thread, and will thank him separately.

There is however an error message now: "...the apk has to be installed using recovery.."!

So still no Xposed Installer but getting there!

Any ideas? Thanks again.
[Xposed General] magnamentis:
hi, thanks for the additional input about binaries, i have 10GB free space, it flashes with cwm and twrp and thus far it seems to be a philz issue.

nevertheless good for everyone to know what the underlaying cause is.
[Xposed General] Farrys:
Been trying to install Xposed framework on LG G4 H815 for over a month. Could not get past the blessed bootloop.

Today I tried your code above in , TWRP.

At first it didn't work. "..not found system..".

I removed the last space and tried again: mount -o rw,remount/system

At last! it worked. Rapid re-boot, no bootloop.

I did factory reset just prior. So another thanks Danarama. Thought you might be interested to know.

Now trying to install XposedInstaller_3.0-alpha2.apk, I get:

"did you install the framework & reboot?". I did.

...and "...the apk has to be installed via recovery"!

How can you install an apk in recovery?

Any suggestions? Thanks again.

Framework error on reboot may be of use. It says:

/data/data/de.robv.android.xposed.installer/cache/busybox-xposed:not found

Reboot failed.
[Xposed General] Arun Av:
Working great on Androidone devices (mine is canvas a1) with official CyanogenMod 12.1 :) Thanks!
[Xposed General] magnamentis:
no, the apk does not have to be and to my knowledge cannot be installed via revovery, how to you come to this conclusion?

just double click the apk in a file manager and bingo. ignore any messages, just do it and then open the app and see if you have the two green numbers in the upper half of the framwork tab.
[Xposed General] gothicVI:
I will, but first I'll try the "fixed" version ;)

Will report all possible outcomes :laugh:
[Xposed General] danarama:
Thanks for the info.

Erm, apk is NOT installed via recovery. whoever told you that was tripping on gin and juice.

Yes please, the problem is here that many people do not report fixes or answer our questions so we never know what did and did not work for people so we appreciate you keeping us up to date.
[Xposed General] mayank22:
Which build you flashed?

The one in the op or latest unofficial unofficial?
[Xposed General] closee91:
Is anyone else having a problem with music streaming to a Bluetooth device? Like in a car or something? I wanna find out if its xposed or my rom. Thanks!

Sent from my LG D851 running Candy5

If I helped out, hit thanks! :D
[Xposed General] Farrys:
Thank you magnamentis. I should hope that by now I'll know how to install Apks!

In summary, thanks to dk_zero-cool and Danaarama, the boot-loop issue was fixed, and Xposed Framework (fixed zip 06/24) installed. When I run Xposed Installer however, under Framework heading of the welcome screen a msg shows in red :

"...Xposed not active... did you install the framework and reboot?"

A click on that msg yields another red msg.: "Installation only poss' manually via recovery for now".

Yes, I too was surprised. Clicking in the Reboot option below that msg. gives this error:

tmp-mksh:<stdin>: /data/data/de.robv.android.xposed.installer/cache/busybox-xposed: not found

Although in SuperSU, along with other root apps, Xposed Installer is listed as allowed.

OK.. you've made me work for this so you'd better come up with something!
[Xposed General] magnamentis:
yeah we can only reply to your text and not to unknowns or thougths and as well we cannot guess what you know and what not. however this red text does not mean you have to the apk because the text shows in the app which means that the app is already installed. it simply states that the framework cannot be outinstalled after rom updates but has to be installed manually. the framework is meant which is the sdk. it's very simple if you see 2 green numbers under active, a 61 and below that a 64 in green, your framework (xposed) is properly installed. next would be to install modules, activate them and reboot, best do a soft-reboot. in my case any reboot works but others had difficulties with normal full reboots.

BTW all this has been mentioned a countless number of times on the first few pages of the official xposed thread by rovo89 which you should read under all circumstances.

EDIT: 24 posts do not imply that someone knows it all, more on the contrary and the last sentence without a smily is slightly offensive so if you want or need help stay positive or the ignore list will grow by one