Hi,
EDIT: Ok, it seems that the first boot process needs about 10-15min. I just had to be more patient and now it works fine.
just tried to install Xposed on my Z2P (ZUI 2.0; Rooted+Unlocked), but I got into a bootloop and I could only recover my device by restoring a backup done before the Xposed installation (uninstalling Xposed didn‘t help).
What I did:
1. Downloaded Xposed framework (v86-sdk23-arm64), uninstaller and the latest apk.
2. Flashed the framework zip.
3. Cleared dalvik cache
4. Reboot
Result: boot sequence hangs on the blue "ZUK" logo. Wait for about 10-15min and it boots totally fine.
Does anyone else have this problem?
Is there any solution to this?
Thanks in advance and best regards
Tek
I assume it's the dalvik cache being created.
cannot see the apps
Hello,
I wanted to install xposed framework on my Zuk Z2 pro but I don't for which reason, I can't see the apps in my drawer.
I downloaded the zip, started the recovery, install, wipe, restarted but nothing is showing up!!! Even it the apps list...
Am I missing something?
Edit: OK I just forgot to install the apk after the zip install ... Working now!!!!
I used AICP ROM, in case it is an useful info.
I installed xposed with the classic method via TWRP. Just flash the correct sdk version "arm64". (Stock ROM 2.1.120 ST)
Related
I am rooted with customer TWRP recovery. I have a custom ROM installed based on the latest touchwiz, few actual changes. ROM is [ROM][Kernel][G900F|I|M|T|W8][XXU1ANH6][26Sep] Omega v9.0●Omega Files.
I have had problems with unexpected SystemUI crash on v.8.1 of Omega, so I updated to Omega's v.9 when it was released a few days ago, no issues at first. But two nights, as I was grabbing my phone to plug it in, it was in this loop again trying to boot but giving the "unfortunately your systemui has closed". So, I managed to boot to recovery from the power menu (not easy as the error flashes every second), installed the ROM again (no wipe). Installed the latest Framework (which seems to always need an install and re-boot when I install the ROM), the ROM worked again for a few minutes, and then the errors started.
So I installed the ROM with a clean install, full wipe. Can't boot at all after the initial boot when I activated the framework. At first I thought it was one of the modules. I had the following modules installed:
Application Settings
Disable clear defaults dialog
Greenify
Wanam
Xposed G Touchwiz
So I did another full wipe install, ONLY installed the framework, activated the Xposed framework, and it won't boot, same error. I try clearing the cache, dalvik cache, nothing works. So I was forced to do another full wipe install and I'm now running without Xposed. A few other people are having the problem on the OMEGA S5 forum, but it seems very rare and most people running Xposed without a problem. I have the Canadian G900W8 version of the phone, don't know if that's the difference.
harry_fine said:
I am rooted with customer TWRP recovery. I have a custom ROM installed based on the latest touchwiz, few actual changes. ROM is [ROM][Kernel][G900F|I|M|T|W8][XXU1ANH6][26Sep] Omega v9.0●Omega Files.
I have had problems with unexpected SystemUI crash on v.8.1 of Omega, so I updated to Omega's v.9 when it was released a few days ago, no issues at first. But two nights, as I was grabbing my phone to plug it in, it was in this loop again trying to boot but giving the "unfortunately your systemui has closed". So, I managed to boot to recovery from the power menu (not easy as the error flashes every second), installed the ROM again (no wipe). Installed the latest Framework (which seems to always need an install and re-boot when I install the ROM), the ROM worked again for a few minutes, and then the errors started.
So I installed the ROM with a clean install, full wipe. Can't boot at all after the initial boot when I activated the framework. At first I thought it was one of the modules. I had the following modules installed:
Application Settings
Disable clear defaults dialog
Greenify
Wanam
Xposed G Touchwiz
So I did another full wipe install, ONLY installed the framework, activated the Xposed framework, and it won't boot, same error. I try clearing the cache, dalvik cache, nothing works. So I was forced to do another full wipe install and I'm now running without Xposed. A few other people are having the problem on the OMEGA S5 forum, but it seems very rare and most people running Xposed without a problem. I have the Canadian G900W8 version of the phone, don't know if that's the difference.
Click to expand...
Click to collapse
Took some advice in the S5 developers forum. Backed up my SD card. Formatted all partitions on phone. Re-formatted SD card with FAT32 in Windows. Made sure everything was cleared out. Copied the ROM (in a PC reader) to the newly formatted SD card. Re-inserted card. Installed 9.1, including Xposed Framework and all the modules I use. Restored my backed up files (pictures, music, TB backup files) to my SD card. After boot I did NOT get the systemui closed error that have been plaguing me for 3 days..
So, it may be that there was something in my configuration, either prior to using Omega or on an earlier version of Omega that caused these problems when I installed Xposed. Hoping that's the end of it. Will let you know.
Lesson for everyone, if there is an issue that is not generally being experienced by everyone else, don't just to a full wipe install, delete everything from everywhere with formats, including your SD card.
Good Day,
After installing Xposed (v80_sdk21_arm64), the Xposed Framework it's detected and it works well; but I can't update or install anything.
I've tryed to mount the system partition from the TWRP recovery; but after reboot it doesn't get mounted.
Please help
Thanks in advice,
I tryed the following:
Uninstall the Xposed Framwork, re-install the Xposed Framework and clean Dalvik/Caché, then reboot. But it doesn't work.
Also, I tryed to mount system from TWRP on the next reboot, but still doesn't work.
Thanks in advice for your help.
The way I fixed it
I've got the M4 Aqua, so I flashed the whole ROM again, then rooted it, and then installed TWRP, and the the Xposed Framework.
Then, right after installing the Xposed Framework did a wipe of the Caché and Dalvik Caché, then booted (waited about 15 mins) and it worked.
Now I'm able to install, uninstall and modify everything in the /System.
NOTE: In Sony devices like mine, you encounter a problem whit the stock camera and/or Album applications; you fix it by de-odex the apk and then but it back again; I fixed it following this post.
Hi everyone !
I'm currently running XPosed on my One Plus 3 (Oxygen V4.5.0, Android 7.1.1), but impossible to use Xposed installer. I try to flash from recovery to install Xposed, and also from Xposed Installer. But when the installation is "finish", an my phone reboot, if I go on Xposed Installer to search for modules (better with modules I guess...), impossible to install anyone. The download start and stop a 64Kb, and no install button even if I download manually the apk. I also try to install from apk, but the module "must be activated". I try activae it from XposedInstaller, and also look in root folder for the "disable" file (see this solution on another thread) but none of these worked.
Also, I install Xposed 88.2, and when I open xposedinstaller, it's always saying to me a little notification "Please update Xposed Installer".
I try everythink, wipe my phone twice, reboots, wipe only cache after every step, reboots, reinstall Xposed, reboots, reinstall module manually, reboots, and also some reboots.
Do anyone can help me ?
Thank's a lot, and pardon my English
Solved by installing the unofficial Xposed Installer
So i recently decided to try out some of the different roms that were released for the moto e4. I decided to go back to Resurrection Remix, and when i tried to install the modules I had been using, found that some of them weren't working properly. There are no errors when they install, but seem to have no effect, such as the volume step increase, or the injected youtube background player...
other modules, like the app systemizer seem to be working just fine...
HigherStateD said:
So i recently decided to try out some of the different roms that were released for the moto e4. I decided to go back to Resurrection Remix, and when i tried to install the modules I had been using, found that some of them weren't working properly. There are no errors when they install, but seem to have no effect, such as the volume step increase, or the injected youtube background player...
other modules, like the app systemizer seem to be working just fine...
Click to expand...
Click to collapse
Did you do a clean install? (Completely wipe data and not restore it again in twrp). Some ROMs have trouble with some modules. Get logs and ask in the modules threads (the ones not working).
Clean install, full wipe, same as before, modules worked fine last install on the same rom, restore failed to boot, which is why I needed to reinstall the previously working modules
HigherStateD said:
Clean install, full wipe, same as before, modules worked fine last install on the same rom, restore failed to boot, which is why I needed to reinstall the previously working modules
Click to expand...
Click to collapse
I had a similar-ish problem on Moto g4 plus RRO.... If you still can't get it to work, here's what I did:
Rom, gapps, boot (usual steps)
Download Magisk APK from XDA
Give it storage permissions
From Magisk Manager, select install
It should ask of you want to direct patch (recommended)- select this option
Reboot and try modules again
I think it's something to do with storage permissions etc. When Magisk tries to patch boot IMG. Check your file systems too. Data partition should be fsfs and all others ext4.
If the steps above don't work try the fsfs Magisk loopback module. It's in the repo and mentions some of the Moto devices having issues with with patching boot img etc for Magisk. The module is installed via TWRP.
:good:
Got it working, somewhat similar process, ROM, gapps, MM apk, then uninstalled the magisk that came built into the ROM, and used the manager installer... Then encrypted, and then opt-enceypt... A script in sbin for my fingerprint from the original ROM and got safetynet passing.
Hi guys,
I'll try to be short..
After a while, I whipped MIUI and Installed Pixel Experience Go on Redmi 4x. Everything was fine, until I tried to install Adaway and it showed me on Magisk Manager that the phone was not root (It was before that). I tried to install the new version 19 over 18.1, but it showed error on TWRP that there was an error installing the zip, because system was not mounted.
I tried to uninstall Magisk with the zip provided in github, and again some error occurred. Then I cleared cache and dalvick and rebooted, but I'm stuck on MI logo. I'm able to access TWRP and see all my files, but cannot boot into the system.
My mistake I did not make recovery or backup and now all my settings and apps (banking, pictures and so on) are about to be whipped.
Any suggestions?
Thanks in advance.
zmeiq said:
Hi guys,
I'll try to be short..
After a while, I whipped MIUI and Installed Pixel Experience Go on Redmi 4x. Everything was fine, until I tried to install Adaway and it showed me on Magisk Manager that the phone was not root (It was before that). I tried to install the new version 19 over 18.1, but it showed error on TWRP that there was an error installing the zip, because system was not mounted.
I tried to uninstall Magisk with the zip provided in github, and again some error occurred. Then I cleared cache and dalvick and rebooted, but I'm stuck on MI logo. I'm able to access TWRP and see all my files, but cannot boot into the system.
My mistake I did not make recovery or backup and now all my settings and apps (banking, pictures and so on) are about to be whipped.
Any suggestions?
Thanks in advance.
Click to expand...
Click to collapse
You can try to flash this boot.img from PE Go build from 08.04.2019. Thats the latest i found but dont know if 8 April is latest PE GO build.
https://drive.google.com/folderview?id=1-4OIUayydgXjF_kXdUL9tE8ohdu-bRrv