Related
Hi,
I have been using Xposed for a Long time. The first time I downloaded it and installed the latest version, it would keep saying in red that the latest version still needs to be installed. After installing it all different ways, it still didn't work so I discovered that older versions might work. Ever since I have been using version 2.5.1.
Recently, because of the older version, I couldn't download and activate a lot of the modules because they required the later Xposed version so I decided to try fix it and now I'm using version 2.6.1.
I disabled resource hooks and it seemed to work. I'm now using the later version of Xposed and the red message doesn't appear anymore. However, NONE of my modules seem to be working now and I can't figure out why.
If anyone can help me that would be greatly appreciated!
Device: HUAWEI G610-U20
Android 4.2.1 JellyBean
I have attached my latest log file from Xposed.
If any other further information is required I will be happy to provide!
EDIT: one of my modules seem to have randomly started working but the rest still do nothing. They are activated and I have rebooted multiple times.
Anyone?
MasterReturnz said:
I disabled resource hooks
Click to expand...
Click to collapse
According to the log file, multiple modules require those hooks in order to work.
Code:
Loading modules from /data/app/com.elesbb.snapchatfullcaption-2.apk
Loading class com.elesbb.snapchatfullcaption.Xposed
This class requires resource-related hooks (which are disabled), skipping it.
It seems to me that you need to enable the hooks. There are also some other errors, which I can't figure out right now (tired...)
Someguyfromhell said:
According to the log file, multiple modules require those hooks in order to work.
Code:
Loading modules from /data/app/com.elesbb.snapchatfullcaption-2.apk
Loading class com.elesbb.snapchatfullcaption.Xposed
This class requires resource-related hooks (which are disabled), skipping it.
It seems to me that you need to enable the hooks. There are also some other errors, which I can't figure out right now (tired...)
Click to expand...
Click to collapse
If I enable resource hooks then Xposed doesn't work, it says I need the latest version them even tough I already have it installed.
Is there a work around for this?
Im trying to manually flash the ZIP file but I can't actually seem to flash the Xposed installer.zip file. It keeps saying installation aborted in recovery mode. How do I fix this?
Newest version is 2.7 of Xposed Installer. http://repo.xposed.info/module/de.robv.android.xposed.installer
The problem with using the latest version is that it doesn't work. My modules don't work unless I disable resource hooks but then only like 2 of them work
I want to know how to successfully install the latest version onto my phone because currently I can't flash the .zip file to my device. I can't use any custom recovery because there is none that support my device currently.
hi, im running Xposed on lollipop v3.0 aplha 2 !
what is the default setting for the "experimental disabled resource hooks" ?
should it be ticked by default or should it be unticked !
what is the default setting ?
shaajrocks said:
hi, im running Xposed on lollipop v3.0 aplha 2 !
what is the default setting for the "experimental disabled resource hooks" ?
should it be ticked by default or should it be unticked !
what is the default setting ?
Click to expand...
Click to collapse
By default, it should not be ticked.
So yesterday I installed xposed framework on my Moto G XT1033 5.0.2, after the process i tried installing some modules with no success, "App not Installed". I rebooted my phone and tried installing again, this time it got stuck on " installing...". I have tried to install using lucky patcher and it gave an error saying that some directory didn't exist.
Please help
Similar problem on my LG L90. I installed version 86 and it's active. I'm able to download modules, but unable to install them.
It says, "Application not installed." I've tried this for several modules and received the same results.
In the installer logs section I have an error:
"E/Xposed ( 298): Cannot load any modules because /data/data/de.robv.android.xposed.installer/conf/modules.list was not found"
Any assistance would be greatly appreciated.
Hello, I also have the same problem with my Alcatel One Touch Fierce 2 running Android 4.4.2. I try to install the Xposed apk and its says "App not installed". Someone please help.
truthinallmighty said:
Similar problem on my LG L90. I installed version 86 and it's active. I'm able to download modules, but unable to install them.
It says, "Application not installed." I've tried this for several modules and received the same results.
In the installer logs section I have an error:
"E/Xposed ( 298): Cannot load any modules because /data/data/de.robv.android.xposed.installer/conf/modules.list was not found"
Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Hey there, did you find a solution for this problem since you posted this? I am experiencing this exact problem right now, it says that modules.list was not found in that directory. Framework is working, modules can be downloaded but not installed.
Thanks
reserve...
For an unknown reason I had the same issue. I was able to download and install from Xposed, and than one day it wouldn't allow me to press the "install button". Long story made short I was able to get it working by installing this app:
[XPOSED] [KK] [FIX] KitKat BUGS fixer
https://forum.xda-developers.com/xposed/modules/mod-service-bug-63793-fix-t2830732
Hope that helps someone and saves them time trying to figure out what happened.
I've had this problem and the way that I do it is by disabling the exposed framework then rebooting, then it will allow you to install apps. After, activate the module, that re eneble xposed, and reboot!
Hey
I was having the same issue but i fixed it.
This might be because google get to know that the phone is modified thats why no apps get installed so the fix it that download GMS PROTECTED app from xposed download and inatall it. Activate it and reboot. And if you're unable to install then simply turn the framework off and install the module that I've mentioned above.after installing the module activate it,turn on the framework and reboot the fone. Bang.... You're good to go
Hi, im new here and this is my first post, so i appreciate all the help and feedback you can give me.
im interested in using xposed in android TV Box's and Dongles, i've been reading and learning all about it for more than a month now. i've got it to work on most TV Box's and dongles that i have "RK based devices with android V 4.4 or less",but i still have a problem with one device which is an RK3288 based with android 5.1 that is already rooted.
i used twrp to flash xposed-v86-sdk22-arm.zip which was successful, than i wiped Dalvik/cache and rebooted, but the boot stuck on bootanimation, i disabled xposed by installing the uninstaller.zip and everything went back to normal. i tried it many times but with no use. i noticed that twrp doesnt mount internal SD, i installed an older version of bootloader which gave me the ability to mount the internal Sdcard, and i tried to install xposed again and this time it pass the animation and goes to a black screen where i can use the mouse but nothing else. with some research i found that UT3+ is based on firefly board and their original ROM is available for download and it has the same bootloader version that came installed with the device, after flashing the new ROM i was able to mount the internal Sdcard and i tried to install xposed again, and this time it gives me optimizing apps but after it finish the device reboot and get stuck again on bootanimation.
my question is, if there is a log for errors to know why the system/boot get stuck , where can i find them??
and if there is no logs how can i monitor the booting process to find the info i need??
also i know or read what bootloader is but i dont understand how it is effecting xposed installation.
Sorry for the long post, and thank you for your help in advanced
EDIT: i finally got adb connection with the device and used logcat to get the logs, but im not sure how to attach the files. if anyone can help i will gladly send the logs. thanks
Update 1
i was looking at the logs "didnt know what to search for im not a developer" and i noticed that everything is crashing and "Not granting permission" ,"Unknown permission " are everywhere .
sample of logs:
Code:
"com.google.android.partnersetup.permission.WRITE_APP_PROVIDER in
package com.android.vendingW/PackageManager( 4712): Not granting
permission android.permission.BIND_WALLPAPER to package
com.android.camera2 (protectionLevel=18
flags=0x58bc45)W/PackageManager( 4712): Not granting permission
android.permission.BIND_APPWIDGET to package com.android.launcher3
(protectionLevel=18 flags=0x583e45)W/PackageManager( 4712): Unknown
permission android.permission.READ_SETTINGS in package
com.android.launcher3W/PackageManager( 4712): Unknown permission
com.android.launcher.permission.READ_SETTINGS in package
com.android.launcher3W/PackageManager( 4712): Unknown permission "
so i decided to root again with KingRoot, and i tried installing xposed again, and it kinda worked. the system boot and the launcher opens but crashing messages keeps showing "Stresstest for 5.0 has stopped running" , "The process com.android.phone has stopped running", and others.
now im not sure about what im doing but i'll test two methods:
1- i will unpake ROM.img put xposed in the root and update the updater script to install xposed when i flash the ROM.
2- the device can run Linux version from SD card so i might run it and manually install xposed files.
if anyone have any tips or info please let me know. thanks
SOLUTION
For those who are having problems with their RK based android TV Box with android 5.1, if you get stuck on Boot animation or the system boots with black screen and you can use your mouse only, or if you getting errors when you boot the main problem would be your firmware is modified and up to Xposed V.86 is not supported because of the error "No implementation found for void dalvik.system.VMRuntime.clam" you can read more about it in this post https://github.com/rovo89/Xposed/issues/167.
and luckily dsa8310 made a modefied version of xposed, i tested it and it works you can find the download link here http://forum.xda-developers.com/showpost.php?p=67787484&postcount=325
viVaPale said:
luckily dsa8310 made a modefied version of xposed, i tested it and it works you can find the download link here http://forum.xda-developers.com/showpost.php?p=67787484&postcount=325
Click to expand...
Click to collapse
I can't get to the page with the link. (I get a noob alert) We want to try this xposed on a ugoos ut3s (android 5.1 with a rk3288)
Would someone please be so kind to post it here or tell me where I can download it.
Anyone that can compile Xposed v87 to fix this problem for RK3288 Lollipop devices?
https://github.com/rovo89/Xposed/issues/167
https://android.googlesource.com/platform/art/+/379d09fe3c3feb7c2a2fb5a3623689b5ace7e79b
Are there instructions somewhere so we can compile it ourselves?
The code above looks like it needs to be applied to Android source code, what must be changed in Xposed Github code to fix it and compile our own new Xposed only for our devices?
Thanks
humptydumpty said:
I can't get to the page with the link. (I get a noob alert) We want to try this xposed on a ugoos ut3s (android 5.1 with a rk3288)
Would someone please be so kind to post it here or tell me where I can download it.
Click to expand...
Click to collapse
Please try this link https://mega.nz/#!300ggYoJ!1vdLP0OyU2D1ky6pWv-Y3VJFH5paHSAqV3Y8A64bvkk
i recommend you download the xposed uninstaller in case something wrong happend
viVaPale said:
Please try this link https://mega.nz/#!300ggYoJ!1vdLP0OyU2D1ky6pWv-Y3VJFH5paHSAqV3Y8A64bvkk
i recommend you download the xposed uninstaller in case something wrong happend
Click to expand...
Click to collapse
Wow ! Work nice on my haier pad971 (ifive air clone) rk3288 5.1.1 !!
Thanks so much
does anyone know if there's an RK3288 enabled xposed v89 built to avoid the issues described by viVaPale? Tried the one from 3.1.5 installer, but after boot it doesn't load the launcher, only mouse can be moved around like viVaPale describes.
Hello.
Unable to flash magisk modules.
! /data/adb/magisk_merge.img mount failed.
Even via twrp recovery is no possible to flash magisk modules, says something like error 1.
The device is a doogee mix 2.
I was forced to install the normal xposed framework just to use it.
Root works; only modules have problems.
Can some expert find a solution, please?
Thank you in advance to everyone gives good news!
MasterSheea said:
Hello.
Unable to flash magisk modules.
! /data/adb/magisk_merge.img mount failed.
Even via twrp recovery is no possible to flash magisk modules, says something like error 1.
The device is a doogee mix 2.
I was forced to install the normal xposed framework just to use it.
Root works; only modules have problems.
Can some expert find a solution, please?
Thank you in advance to everyone gives good news!
Click to expand...
Click to collapse
Hi, Can you attach logs while flashing ?? from both MM and recovery
MasterSheea said:
Hello.
Unable to flash magisk modules.
! /data/adb/magisk_merge.img mount failed.
Even via twrp recovery is no possible to flash magisk modules, says something like error 1.
The device is a doogee mix 2.
I was forced to install the normal xposed framework just to use it.
Root works; only modules have problems.
Can some expert find a solution, please?
Thank you in advance to everyone gives good news!
Click to expand...
Click to collapse
Known issue on some MTK devices. Loop mounting doesn't work.
There are lots of reports like this for Doogee... There's been some investigating into it in the beta thread, but as of yet there's no solution, I believe.
Hello!
Yes, of course!
Logs of magisk installer and TWRP recovery here:
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
Ignore the crittografy error; I have tried to disable the crittografy and all is the same. Same problem.
In more, yesterday I had another annoying problem with magisk: before the options of the magisk app disappeared (there is the pic in the folder I attached. Then magisk is totally disappeared: magisk is not installed anymore in your device.
Tried to re-install magisk: nothing happens.
I have re-flashed the ROM and re- installed magisk: at moment is working.
Root files and SuperSU are not working.
I will open a new forum discussion for this problem.
Thank you in advance.
Greetings
MasterSheea said:
Hello!
Yes, of course!
Logs of magisk installer and TWRP recovery here:
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
Ignore the crittografy error; I have tried to disable the crittografy and all is the same. Same problem.
In more, yesterday I had another annoying problem with magisk: before the options of the magisk app disappeared (there is the pic in the folder I attached. Then magisk is totally disappeared: magisk is not installed anymore in your device.
Tried to re-install magisk: nothing happens.
I have re-flashed the ROM and re- installed magisk: at moment is working.
Root files and SuperSU are not working.
I will open a new forum discussion for this problem.
Thank you in advance.
Greetings
Click to expand...
Click to collapse
The file is not accessible
Sorry.
Try now, please.
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
MasterSheea said:
Sorry.
Try now, please.
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
Click to expand...
Click to collapse
Looks like recovery can't decrypt /data, so that's likely an issue there. But it'd be easier to tell if you had provided the recovery log rather than a screenshot (Advanced - Copy log after trying to flash).
And, it would also be very useful if you had provided a Magisk log rather than only installation logs.
But, it's probably a moot point anyway. Like I said earlier, this is a known issue with loop mounting on Doogee devices (and other devices using Mediatek). No solution as of yet...
Didgeridoohan said:
Looks like recovery can't decrypt /data, so that's likely an issue there. But it'd be easier to tell if you had provided the recovery log rather than a screenshot (Advanced - Copy log after trying to flash).
And, it would also be very useful if you had provided a Magisk log rather than only installation logs.
But, it's probably a moot point anyway. Like I said earlier, this is a known issue with loop mounting on Doogee devices (and other devices using Mediatek). No solution as of yet...
Click to expand...
Click to collapse
Same here, provide good logs
Ok, thanks.
I will try to send you good logs.
About encryption, I have tried to disable encryption and to install all without encryption: nothing changes.
Before I must understand why magisk disappears from system, then I will collect logs about modules installation. Magisk is the only way to root this damned phone, SuperSU does not works.
Thank you in advance
MasterSheea said:
Ok, thanks.
I will try to send you good logs.
About encryption, I have tried to disable encryption and to install all without encryption: nothing changes.
Before I must understand why magisk disappears from system, then I will collect logs about modules installation. Magisk is the only way to root this damned phone, SuperSU does not works.
Thank you in advance
Click to expand...
Click to collapse
There was no need to start a new thread about that... You've already got this one going.
The screenshot of the Manager you provided simply showed a Manager without internet access. Completely normal.
About losing root completely, make sure you don't have any aggressive battery optimisation on the Manager. More here:
https://www.didgeridoohan.com/magisk/Magisk#hn_Randomly_losing_root
Ok, good, I close the other thread
Yes true, that is a normal screenshot of magisk offline. Yesterday I did formatted data to disable encryption and I lost all the other screenshots, but was like this: before all options disappeared, then magisk disappeared.
No, no aggressive battery optimization running, but I have installed greenify and amplify... Perhaps one of this app makes problem?
I wish to close the other thread, but I do not know how to do it.
How to do it, please?
MasterSheea said:
Ok, good, I close the other thread
Yes true, that is a normal screenshot of magisk offline. Yesterday I did formatted data to disable encryption and I lost all the other screenshots, but was like this: before all options disappeared, then magisk disappeared.
No, no aggressive battery optimization running, but I have installed greenify and amplify... Perhaps one of this app makes problem?
Click to expand...
Click to collapse
Make sure the Manager is removed from Battery optimisation and that it isn't selected I'm Greenify. It's not certain that this is the issue, but it's worth ruling out.
Other than that, a logcat of it happening, or even just a screenshot of the Manager when things aren't working. A Magisk log is also useful, of course.
MasterSheea said:
I wish to close the other thread, but I do not know how to do it.
How to do it, please?
Click to expand...
Click to collapse
Just let it be...
Oki.
I removed magisk from battery optimization.
I hope that at least the root will work.
But I seen in another thread that there is a solution known as f2fs workaround bug fixer. But is still not working. I hope that someone will fix it soon.
Anyhow, thank you for all
Move to thread https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875. Flash last zip. Move to magisk manager, install updated (2018.3.6) version. All modules should now install fine.
Hello.
Thank you for the answer.
I have tried to flash the zip without success.
No magisk installation found or installed version is not supported.
Error process 1.
The magisk version I have installed is v16. - 5.6.4(112).
The last one, suppose.
Any suggestions, please?
Thank you in advance ?
I made also the this attempt: I have flashed a magisk module using flashify.
The flashing was successful, but the module is not in the magisk list.
Can be a permission problem? Someone knows where is the folder of installed magisk modules, please? Perhaps is a permission problem and changing permissions will work...
Download f2fs-loopback-bug-workaround-2018.1.31.zip from the thread. Place it in Download folder of internal storage. Reboot to recovery. Flash zip in twrp. Reboot. Open magisk manager. F2FS Loopback Bug Workaround should be installed in modules. I hope any module can be installed from now on.
Dear Pragnan Saha,
Thank you for your answer.
I have tried to flash f2fs-loopback-bug-workaround-2018.1.31.zip, but without success.
TWRP says: No magisk installation found or installed version is not supported. Error process 1.
Some suggestions, please?
Thank you in advance
Didgeridoohan said:
There was no need to start a new thread about that... You've already got this one going.
The screenshot of the Manager you provided simply showed a Manager without internet access. Completely normal.
About losing root completely, make sure you don't have any aggressive battery optimisation on the Manager. More here:
https://www.didgeridoohan.com/magisk/Magisk#hn_Randomly_losing_root
Click to expand...
Click to collapse
What thread? And is it about exact the same error ! /data/adb/magisk_merge.img ... What this thread is about?
Do you know if there's a fix already? I'm on ext4 so f2fs loopback makes no sense for me
And @MasterSheea do you have a fix?
I've got exactly the same error with flashing modules, after clean flask is possible to install modules but after 1 reboot it fails
I'm at my wits end trying to get Magisk back!
(The backstory is that I had been running a DirtyUnicorns OS for a year just fine, but then Pokemon Go started failing to login. So it was time to update.)
Using a Samsung Tab 4 (SM-T330NU)
Formatted and installed stock OS/boot
Used Odin to flash "twrp-3.0.0-3"
Used TWRP recovery to update to "twrp-3.3.1-0"
Installed "Lineage OS 17" (and added Gapps) - made sure it booted and all was well
Booted into TWRP recovery and installed the latest "Magisk-v20.4"
Wiped cache and rebooted
Installed the latest "MagiskManager-v7.5.1" and got "Magisk is not installed"
After a great deal of searching I learned how this is supposed to be corrected:
Took the boot.img from the Lineage OS 17 zip,
Used Magisk to patch it, creating "magisk_patched.img"
Used TWRP recovery to install "magisk_patched.img" to the boot section
Wiped cache and rebooted
Still getting "Magisk is not installed"
Booted into TWRP recovery and installed the latest "Magisk-v20.4" just in case
Still getting "Magisk is not installed"
This is all after roadblocks for hours a day for a week trying to pass safetynet using Magisk on Lineage OS 16 for about a week, so I thought this fresh start would be easier and now I'm pulling my hair out.
Any suggestions would be helpful. I just want to be able pass safetynet and my ctsProfile match fails. Which I can't even begin to work on without Magisk core.
Thanks in advance.
First thing I would check is if the Manager is installed to external/adoptable storage. The Manager can't work properly like that...
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed
Didgeridoohan said:
First thing I would check is if the Manager is installed to external/adoptable storage. The Manager can't work properly like that...
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed
Click to expand...
Click to collapse
Thanks for the quick reply!
How do I check to see where it's installed and/or reinstall it to the proper storage? Because that could be it.
There's no SD card or USB device plugged in and I couldn't find more information online (I even scoured didgeridoohan.com before posting here).
Also, and this may be helpful, it appears the device is not rooted. Fx file explorer and root checker apps confirm this. So it's possible even with the steps I followed that Magisk core really isn't installed and the apk is telling the truth (I'm just at a loss to know how that's possible after flashing the zip and flashing the patched boot file, both in twrp).
If you have no SD card installed adoptable storage won't be an issue.
You can easily verify through TWRP if the core Magisk files have been installed. Check in /data/adb/magisk. It should contain busybox, magisk, magiskboot and magiskinit binaries, together with addon.d, boot_patch and util_functions scripts.
Seeing the recovery log from when you attempt to install the Magisk zip in TWRP might show us something. Also try the could also be a good idea trying the Canary release to see if there's any difference from stable v20.4.
(This thread can be locked/(closed?)/answered)
I tried my damnedest and nothing worked. So I wiped/formatted lineage-17.1-20200512 and installed lineage-17.1-20200419. THIS was the ease with which I was accustomed to installing Magisk (Recovery install and immediately working on boot). Sadly, other problems abound and they are outside the scope of this subforum.
Just in case anyone reads this and cares:
- GPS Joystick was a no-go because apparently Lineage has a not-so-nifty feature that blocks the "draw over apps" android feature if your RAM is below some secret threashhold, which prevents the entire app from functioning.
- Fake GPS can take getting used to, and I'm used to it and love it, but the location and routing keeps crashing in the background, which means pogo closes when I tab back to start it back up again.
- Regardless of which I use I am rubberbanding back to my house... despite using all the tricks I can find or think of (yes, including 'smali patcher', specific app settings, systemizing the GPS app, setting off/on mock locations, etc)... but I think it's because this OS has no unique setting for the GPS data to be "device only".
Problems one and two are due to the ****ty ram on this Samsung tablet, which I've always known was an issue, so I suppose it might just be time to buy a phone specifically for this purpose. From what I read, the best cost effective option is an iPhone SE, and I'm truly not an Apple fan (I certainly would not risk my own phone being bricked or even merely wiped).
Not sure how I used it for the last year without this many issues, but it seems like that's over now unless I want to deal with DirtyUnicorn OS again, and that was it's own nightmare sometimes.
Thanks all for reading, but especially Didgeridoohan for replying and for all the resources on your pages and threads.