Hello,
I have a Problem with Xposed on My Blackview BV 6000
Xposed Installer says Xposed is active (ver. 86) but none of the modules are working.
The modules alwasy asking me to activate them in Xposed and reboot, if iam doing so its the same after the next reboot.
I Tried this with some modules and it seems like really none of them is working.
I tried:
Xprivacy
Audio Balance
CPU Temp
and some more others.
Im Using a Blackview BV6000
It is a Android 6.0 Device
Im using Xposed-v86-sdk23-arm64
APK is: XposedInstaller_3.0_alpha4
I´am Using SuperSu v 2.76
When i Try to Read the Logs In Xposed it says No Such File or Directory....
Hope somebody can help me...
noboby said:
Hello,
I have a Problem with Xposed on My Blackview BV 6000
Xposed Installer says Xposed is active (ver. 86) but none of the modules are working.
The modules alwasy asking me to activate them in Xposed and reboot, if iam doing so its the same after the next reboot.
I Tried this with some modules and it seems like really none of them is working.
I tried:
Xprivacy
Audio Balance
CPU Temp
and some more others.
Im Using a Blackview BV6000
It is a Android 6.0 Device
Im using Xposed-v86-sdk23-arm64
APK is: XposedInstaller_3.0_alpha4
I´am Using SuperSu v 2.76
When i Try to Read the Logs In Xposed it says No Such File or Directory....
Hope somebody can help me...
Click to expand...
Click to collapse
Hi.
You can try my grorkmod. It was created for the Telephone p9000, but works also for other chinaphones.
It look like mediatek (?) had a bug in their boot.img.
To be sure you can provide the following files:
/file_contexts
/seapp_contexts
Greetings
Vsrookie
Grorkmod v1.0
Sent from my P9000 using XDA-Developers mobile app
vsrookie said:
Hi.
You can try my grorkmod. It was created for the Telephone p9000, but works also for other chinaphones.
It look like mediatek (?) had a bug in their boot.img.
To be sure you can provide the following files:
/file_contexts
/seapp_contexts
Greetings
Vsrookie
Grorkmod v1.0
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
I installed my Backup to have a Clean Start, then i installed grorkmod like is in the discription in the grorkmod-thread.
I Looks like Xposed is Working fine Now.
Thank You very Much for your Hint!
I can confirm grorkmod to fix xposed on my BV6000 FW20160713.
What I did:
- Flash TWRP Recovery with the sp-flash-tool (I used Version 1628 linux)
- boot into recovery
- install Supersu
- boot into system
- install busybox
- generate a ZIP file within the busybox app (and copy it to external sd)
- power off
- boot into recovery
- wipe Dalvik/ART Cache
- wipe entire System/Data (factory reset)
- power off (either by entering halt in terminal or by holding down the power button)
- reflash 20160713_s12v55_jk_3m with sp-flash-tool, replacing recovery.img with the TWRP one. (I suppose you can just exclude it, as it is still installed)
- boot into recovery
- wipe cache again (don't know if necessary)
- install busybox, supersu, grorkmod, xposed
- reboot into system
- installed xposedinstaller
- rebooted (through normal system's power button, not xposedInstallers menu)
- activated xprivacy in xposedinstaller
- installed xprivacy
- rebooted (again the system way)
Success
The hardware reboot within xposedinstaller still returns the error:
sush: <stdin>[8]: /data/user/0/de.robv.xposed.installer/cache/busybox-xposed:not found
The software reboot did produce a bootloop, though that was before I found grorkmod. I do not intend to try it out again.
@vsrookie
What worries me a bit:
Understand this:
SELinux is a abbreviation for Security Enhanced Linux. That isn't just a name, it's the programm.
With this mod you will loose the S in the name.
Click to expand...
Click to collapse
Would it make sense to make a "grorkmod-lite" that only fixes the broken contexts? (I know this question might sound dump)
hanseatic2 said:
I can confirm grorkmod to fix xposed on my BV6000 FW20160713.
What I did:
- Flash TWRP Recovery with the sp-flash-tool (I used Version 1628 linux)
- boot into recovery
- install Supersu
- boot into system
- install busybox
- generate a ZIP file within the busybox app (and copy it to external sd)
- power off
- boot into recovery
- wipe Dalvik/ART Cache
- wipe entire System/Data (factory reset)
- power off (either by entering halt in terminal or by holding down the power button)
- reflash 20160713_s12v55_jk_3m with sp-flash-tool, replacing recovery.img with the TWRP one. (I suppose you can just exclude it, as it is still installed)
- boot into recovery
- wipe cache again (don't know if necessary)
- install busybox, supersu, grorkmod, xposed
- reboot into system
- installed xposedinstaller
- rebooted (through normal system's power button, not xposedInstallers menu)
- activated xprivacy in xposedinstaller
- installed xprivacy
- rebooted (again the system way)
Success
The hardware reboot within xposedinstaller still returns the error:
sush: <stdin>[8]: /data/user/0/de.robv.xposed.installer/cache/busybox-xposed:not found
The software reboot did produce a bootloop, though that was before I found grorkmod. I do not intend to try it out again.
@vsrookie
What worries me a bit:
Would it make sense to make a "grorkmod-lite" that only fixes the broken contexts? (I know this question might sound dump)
Click to expand...
Click to collapse
Hi.
Thank you for trying my mod.
This was a hint for the old version < 1.0.
In 1.0 everything is fine. It "only" fixes the needed files.
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
If you update firmware via official OTA to avoid boot loop uninstall xposed by flashing the zip xposed Uninstaller for marshmallow(on xda thread)! After first reboot u have to re flash supersu grorkmod and xposed (clearing caches). I've lost two hours to understand!
vsrookie said:
Hi.
Thank you for trying my mod.
This was a hint for the old version < 1.0.
In 1.0 everything is fine. It "only" fixes the needed files.
greetings
vsrookie
Sent from my P9000 using
Click to expand...
Click to collapse
Which version do you think (or know) will be better for BV6000 rooted with GizBeat manual? 1.0? or 1.1?
Xposed Bv6000 Android7
Hi
I rooted my BV6000 on Android 7.
Is it possible to install XPOSED?
And if, how? (no rom of android 7 available; people with bricked phones after downgrading)
Thanks for your help!!!
Cheers
Blackview BV6000 Flashing Android 7.0
Follow the link below if you wish to #FLASH your #BLACKVIEW #BV6000 with the latest official #Android 7.0 #NOUGAT firmware..
https://dreamworks75.blogspot.in/2017/08/rom-flashing-guide-blackview-bv6000.html
Related
I decide to share it there because I don't know better place for this...
This is an Xposed framework variant built for MIUI based devices running Android 5.0, 5.1 and 6.0.
Tested and working on latest ROM's on various devices.
Fully working resource hooking and themes.
Prerequisite:
- Custom recovery (CWM, TWRP)
Bugs report:
- If you get any lag, broken feature or any App force closing, post your Xposed logs.
- If you get a boot-loop, reboot and get the logcat with "adb logcat -v time".
Please pay attention:
Archive with Xposed installation contains some necessary information and it is very important to successfully installation to choose right archive.
- "arm" means the devices that are running arm32 operating system and uses ARM architecture CPU.
- "arm64" means the devices that are running arm64 operating system and uses ARM64 architecture CPU.
- "x86" means the devices that are running x86 operating system and uses x86 architecture (Intel) CPU.
- "sdk21" means Android Lollipop 5.0.x
- "sdk22" means Android Lollipop 5.1.x
- "sdk23" means Android Marshmallow 6.0.x
If you try to install wrong archive it will not installed and error message appears in TWRP installation log.
Magisk
Magisk (systemless) variants of archives separated only by Android versions (sdk21, sdk22 and sdk23). CPU architecture will be detected automatically.
How to install:
- Install Xposed Installer app
- Make a nandroid backup
- Copy the Xposed file and the uninstaller to your sdcard
- Flash "xposed-vxx-sdkxx-armxx-MIUI-edition-by-SolarWarez-xxxxxxxx.zip" through a custom recovery (TWRP/CWM...)
- Reboot and wait, it may take several minutes to boot up depending on your ROM size and installed apps amount. If phone still not boot after 5 minutes then you need get boot log by "adb logcat -v time", reboot into recovery and restore backup or de install Xposed
Attention!
Starting from v86 official version of Xposed become more compatibly with ROMs that use a Resources subclass for e.g. theming, like MIUI.
So, try firstly official Xposed on your device. If it will works well (take a look at themes, if they works well, then all Ok), then you doesn't need this version of Xposed.
But I suppose that on some devices official Xposed still may cause bootloops.
Donate to @rovo89
All credits go to @rovo89 for his amazing job on Xposed framework
Can you post your sources? Are the "Resources" and "TypedArray" the only changes?
Share your sources please
Thanks
in mi4c works perfect!!!thanks man
the only thing that ''breaks'' is edge utility!!!and another that dowload modules manual not from inside app(doesnt care at all) just mention it!!!thanks again!!!
Can't download MODULES directly from xposed app.
Sent from my MI 4S using Tapatalk
ViTAMiNCHEG said:
Can't download MODULES directly from xposed app.
Sent from my MI 4S using Tapatalk
Click to expand...
Click to collapse
That was always a issue with xposed and miui, even when I've used it on my nexus 4. Guess it have something to do with permissions with miui.
Line app unable to open photo selector activity https://drive.google.com/file/d/0B3TzmNRa2nE6RE1kbHhuNUV5Y2c/view?usp=drivesdk
Sent from my hermes using XDA Labs
Nice! I submitted a request for include this in Material Design Xposed Installer. It would be awesome!
If i already flashed v80, do i need to flash the uninstall.zip before flashing v83, or can i flash v83 directly?
dagger1 said:
If i already flashed v80, do i need to flash the uninstall.zip before flashing v83, or can i flash v83 directly?
Click to expand...
Click to collapse
Flash it directly without uninstalling
Sent from my MI 4S using Tapatalk
Hey bro i was using miui v80 on mi4 wile long but accidently i flashed official xposed v83 file from xposed installer and got boot loopbafter that i had uninstalled xposed with zip and rebooted phone!! My mi4 booted normaly but now if i am flashing miui xposed v80 which i previously used and clear dalvik cach than phone does not optimizing any apps and system apps crashing!! Cant do any opration!! Same is happen with v83 also and also i updated my whole miui devloper rom to new version thus i cant flash xposed got same error!! Plzzz help!!
Sent from my MI 4W using Tapatalk
saiyammorakhiya said:
Hey bro i was using miui v80 on mi4 wile long but accidently i flashed official xposed v83 file from xposed installer and got boot loopbafter that i had uninstalled xposed with zip and rebooted phone!! My mi4 booted normaly but now if i am flashing miui xposed v80 which i previously used and clear dalvik cach than phone does not optimizing any apps and system apps crashing!! Cant do any opration!! Same is happen with v83 also and also i updated my whole miui devloper rom to new version thus i cant flash xposed got same error!! Plzzz help!!
Sent from my MI 4W using Tapatalk
Click to expand...
Click to collapse
I had similar problem, fixed by deleting the xposed folder in /data partition
@SolarWarez Got bootloop after install xposed tweak (ROM: 6.4.28)
Firstly i was install xposed in my phone (arm x64 v83 hermes) and i just need to wait until it finished boot
Then i install extMIUIv7, check tickbox for enabled it, and reboot
And voila, i got bootloop
I tried to format art cache in TWRP and it fixed it.
Well this is weird seems global beta + xposed break ART Caching
Sent from my hermes using XDA Labs
Not working
Can't install on Redmi Note 2, MIUI 7.3.1 stable (Android 5.0.2).
Error is: "chown: /system/lib/libart.so.orig.gz: Read-only file system".
Manual mounting in r/w mode does not help =(
Actually, this file libart.so.orig.gz is not the first in batch and not the last, but error happens only with it.
update: I have modified SolarWarez's package, now installs normally. Tested, working.
(what i did is disabled script interruption on some errors while setting owner and permissions on files).
Download here: https://drive.google.com/open?id=0B4lahQDWFyqqOHJKaFFfbEtmZlE
How to uninstall Xposed?
I have flashed xposed-v83-sdk22-arm64-MIUI-edition-by-SolarWarez-20160428 but any downloaded and enabled module won't work (even after reboot).
Moreover my Xiaomi Redmi 3 Pro is laggy now.
How can I unistall it?
ROM MIUI 7 by miui.it 6.5.5 based on Android 5.1.1.
Edit:
Uninstalled flashing xposed-uninstaller-20150831-arm64.zip by TWRP
I'll use it when I buy my Xiaomi... in the future...
Hi just discovered a bug: when in stock browser I go to bookmarks/history browser force closes. This also happens when browser tries to show a dialog window (for instance, when you go to xiaomi.eu it asks to install tapatalk). Log attached
Edit: attached another log got when getting to copy text in stock browser
I have flashed xposed-v83-sdk22-arm64-MIUI-edition-by-SolarWarez-20160428 on MIUI7 using Lenovo A7000-a
Xposed give error, Phone freezes and I have to retart it by pulling battery of mobile phone. I am using Xposed for only XInternalSD because its mount SD Card as internal Memory.
When is v84 coming? Hope bugs get resolved and there's compatibility with miui 8
Hello, everyone!
TL;DR: You're about to perform a systemless root installation on your phone so make sure you have uninstalled Xposed Framework, uninstalled root, the device's bootloader is unlocked and your phone's boot image is in its untouched stock state. Then boot into TWRP and install SuperSU-v.279-SR3 or newer.
UPDATE 2017-01-19:
- Provided missing bootloader information regarding root. Thanks, @Charlita for the heads-up!
- Moved TL;DR section to the top.
UPDATE 2017-01-15:
- SuperSU-v.279-SR3 learned how to use systemless mode as default flashing method for Motos. This is great news as the installation process now is just a matter of flashing the SuperSU installer. The segmentation fault had been fixed on SR2 and this version also includes that fix.
- Included a TL;DR section.
UPDATE 2016-12-25:
- SuperSU-v.279-SR1 contains a regression bug regarding the "segmentation fault". Skip this version for now. I've already contacted Chainfire.
- suhide: as the Chainfire himself stated, the tool is a losing game so I'm not putting any further effort here.
UPDATE 2016-11-03:
- As of SuperSU-v2.78-SR3 boot image patching works out-of-the-box. Just install it and you're done!
- TWRP version 3.x works as expected.
- Unfortunately, SafetyNet checking fails as Google constantly updates the server-side code.
- WIP: Check if Chainfire's suhide are able to help here.
UPDATE 2016-08-08:
- Added a backup reminder.
- Added flashable zip systemless_root_enabler_by_glauberlima.zip.
After a few days playing with it, I finally managed to perform a systemless root install for our beloved Moto X 2014
Benefits:
- Install OTA updates when they arrive;
- SafetyNet checking will pass so Android Pay can be used (not available in Brazil yet).
Requirements (links below) :
- Android 6 Marshmallow
- Bootloader must be unlocked otherwise you won't be able to root your phone;
- Boot partition must be in its original untouched stock state otherwise, SuperSU installer won't be able to patch it;
- System partition must be untouched as well but a simple uninstall of applications that have changed it should be enough. This step is not mandatory but if your system partition remains changed SafetyNet checking will fail;
- Your device must be unrooted. SuperSU has the option "Completly remove root". Use it;
- If you have Xposed Framework installed, uninstall it;
- You'll need ADB and Fastboot in order to flash stock boot.img if applicable;
- TWRP. Version 3.0.2-2 works just fine. If you prefer 2x series, I highly recommend version 2.8.7.1;
- SuperSU-v2.79-SR3 zip installer (or a newer version). DO NOT TRY AN OLDER VERSION. WILL NOT WORK;
Install guide:
- Make a Nandroid backup first using TWRP;
- Uninstall Xposed Framework if applicable;
- Uninstall SuperSU;
- Connect your device to your computer via USB;
- Reboot into bootloader:
Code:
adb reboot-bootloader
- Restore stock boot partition (you can skip this step if you already been on stock boot):
Code:
fastboot flash boot xt1097_boot_stock_with_may_2016_update.img
VERY IMPORTANT: The binary file boot xt1097_boot_stock_with_may_2016_update.img is device dependent. I have extracted stock boot.img from victara May 2016 update full ROM package and put it here. If you are trying on the other variants, make sure you will use the right image.
- Reboot into Recovery (TWRP);
- Flash the attached zip file systemless_root_enabler_by_glauberlima.zip. This will set both variables SYSTEMLESS=true and BINDSYSTEMXBIN=false. Without these variables set, SuperSU will fail to systemless root the device. Feel free if you want to manually enter the commands in the Command Prompt:
Code:
adb shell "echo SYSTEMLESS=true>/data/.supersu"
adb shell "echo BINDSYSTEMXBIN=false>>/data/.supersu"
- Install SuperSU and reboot system. If the first boot fails, just wait - the second will work I promise you!
- As soon as Android UI shows up you should be systemless rooted;
- Confirm SuperSU is installed by recognizing the green icon on your app drawer;
- Open up any root app you have. The world-famous Superuser permission request dialog should pop-up;
- Install SafetyNet Helper, in order to attest your Android, is passing Google's SafetyNet checking: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Now you should be good. Congrats!
Go ahead and get some systemless apps:
- Systemless Xposed Framework
- Systemless Adaway
This procedure should work for the other variants too - all you need is the original boot.img
If you need any help feel free to ask.
Attached you can find the screenshots taken from my XT1097 after the procedure
Related links:
SuperSU-v2.79-SR3:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Latest stable SuperSU:
http://download.chainfire.eu/supersu-stable
Systemless Xposed Framework:
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Systemless AdAway:
http://forum.xda-developers.com/showthread.php?t=2190753
Material Design Xposed Installer:
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Minimal ADB and Fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP for Moto X 2014:
http://forum.xda-developers.com/mot...recovery-twrp-2-8-0-0-touch-recovery-t2911523
Thanks:
@Chainfire
Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk
rtrotsky said:
Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
Since your device already has the untouched stock boot you don't need to flash anything.
I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?
jbaumert said:
I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?
Click to expand...
Click to collapse
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.
glauberlima said:
Could you provide your recovery.log from TWRP?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip[code]
This will copy contents to the clipboard. Paste it in notepad then save and attach here.[/QUOTE]
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse
vpxf said:
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse
Hi @vpxf
The unmodified boot.img is a requirement for SuperSU as it tries to patch the boot image on-the-fly during the install process (by the time you flash it using TWRP). If the image is not in its original state, SuperSU will fail to install in systemless mode.
Regarding your question about custom ROMs compatibility I don't know if the SafetyNet checking will pass/fail. That's a good test to perform.
glauberlima said:
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.
Click to expand...
Click to collapse
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.
As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.
bertolehm said:
As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.
Click to expand...
Click to collapse
jbaumert said:
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.
Click to expand...
Click to collapse
As stated by @bertolehm I've discussed in the other posts the exactly same issue with the zip installer you have reported @jbaumert. Take a look at them:
http://forum.xda-developers.com/showpost.php?p=67792193&postcount=1193
http://forum.xda-developers.com/showpost.php?p=67805517&postcount=1233
Regarding your device being systemless rooted check with SafetyNet Helper Sample app. If everything turns green you are good
** Duplicated **
Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little
oyoyl said:
Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little
Click to expand...
Click to collapse
Which variant is your X?
glauberlima said:
Which variant is your X?
Click to expand...
Click to collapse
XT1092
oyoyl said:
XT1092
Click to expand...
Click to collapse
15 minutes... That's definitely too much.
I'm about to update this guide with my new findings so If you don't mind I'd like to suggest you this:
Repeat the steps but this time skip the update to latest version. After the reboot access SuperSU. It should display a message regarding your su needs update. Accept it.
Make sure your nandroid backup is up to date.
Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks
Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss
Hi! Hey, I followed the steps and my MotoX got stuck when rebooting after flashing. I'm trying to enter fastboot with power+Volume down but no luck so far, any idea? I hope you can help me!
oyoyl said:
Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks
Click to expand...
Click to collapse
OK. Just leave a reply by the time you have the result of your test.
guilhermoaraujo said:
Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss
Click to expand...
Click to collapse
One of your installed apps modified system partition. Did you test on a completly stock image?
Hi all!
So I recently bought a Cubot Max but cant get any Xposed Modules to work!
Specs:
Cubot Max
Android 6.0
FW v11
arm64
I got the zip and apk off the official thread and used the latest sdk23 arm64 version obviously.
I mainly need the modules "Youtube Adawy" and "Youtube background playback".
But for the sake of testing if the issue is a result of incompatibility I also installed the modules
"PinNotif" and "SlideBack".
None of them worked.
The UI of "SlideBack" seemd to work properly while the UI of Youtube Adaway said that the app was not actived, even tho i tried it several times.
The log file read "cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT" so i created the missing txt file and gave it - rw rw permissions.
Does anyone has a clue what causes this problem?
greets
wambooo23 said:
Hi all!
So I recently bought a Cubot Max but cant get any Xposed Modules to work!
Specs:
Cubot Max
Android 6.0
FW v11
arm64
I got the zip and apk off the official thread and used the latest sdk23 arm64 version obviously.
I mainly need the modules "Youtube Adawy" and "Youtube background playback".
But for the sake of testing if the issue is a result of incompatibility I also installed the modules
"PinNotif" and "SlideBack".
None of them worked.
The UI of "SlideBack" seemd to work properly while the UI of Youtube Adaway said that the app was not actived, even tho i tried it several times.
The log file read "cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT" so i created the missing txt file and gave it - rw rw permissions.
Does anyone has a clue what causes this problem?
greets
Click to expand...
Click to collapse
Exactly I am also facing the same problem.
Same here
Can we have a thread to get the Cubot Max working with Xposed? A 500+ page general thread is difficult to follow. Thanks!
Success!
I did it! This is what I did.
The problem is that there is a firmware error which affects a number of MTK6735 phones and stops Xposed from working. You have to install another module called grorkmod first, but this will not work if you have previously tried to install Xposed. So what I did was set the phone back to its initial state (after backing up data etc.).
1. Download the Custom TWRP and the Cubot Max official ROM from here:
mod edit: link removed
2. Unrar the official ROM, and, using SP Flash Tool, set to "Format and Download", Flash the ROM in full. You will now have an unrooted, untouched factory-set phone.
3. When I did this, the Firmware version (Build Number) was V04 — check this through your system settings as my phone originally arrived with Build Number V09. So, after unzipping the TWRP download, I had to use the older version of the Scatter file. So use SP Flash Tool again, and Flash TWRP and reboot the phone, you will have an unrooted phone but with TWRP installed. Do the usual stuff with becoming a developer and changing the necessary permissions.
4. Now you can transfer files to your phone's memory.
UPDATE-SuperSU-xxx,zip
grorkmod_v1.1+lite.zip
xposed-v87-sdk23-arm64.zip
XposedInstaller_3.1.1.apk
5. Boot to Recovery, and, from TWRP:
(a) Install UPDATE-SuperSU-xxx.zip but do not reboot.
(b) Clear Dalvik cache etc
(c) Install grorkmod do not reboot.
(d) Install xposed — this time reboot.
6. Run your file manager and attempt to install the .apk file. If you are diverted to give permission for this, change the settings and do it again.
Hope this helps.
Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
UPDATE: For now, if no other solution is found, bootloop can be bypassed by dirty installing the rom again. But it has to be an easier workaround...
We know now that the problem is caused because of two factors merging:
1- Using Magisk.zip installer through custom recovery
2-In the case that the custom recovery CMW/TWRP installed in the phone is very old (for instance, CMW automade for MTK6589X or TWRP 2.5.0).
While installing, Magisk tries to send commands to the custom recovery that cant be understood by it, leaving the installation incomplete after some modifications in /system (read below recovery log).
Acording to the recovery, it seems that Magisk did some modifications without running correctly survival script - Adding addon.d survival script ("Unrecognized option '-Xnodex2oat'") and .zip installer is not designed to revert actions in this case.
Also, Magisk couldn't reach the boot modification step, so boot is not damaged, therefore workarounds for restoring boot won't work.
Using Magisk Unistaller.zip is also not possible as the uninstaller is mainly designed for boot backup restoration, and again, this is not the case.
Currently needed: Find what's wrong in system due to the incomplete Magisk installation to revert it back to the original state (before faulty magisk.zip installation).
Recovery log:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'
up!
I' also having the same problem. My Samsung J2 Prime stuck at logo after updating to 18.1. Any tips on how to fix it without resetting my phone? Thanks.
Update: Bootloop fixed. I used TWRP to restore boot image. I then update Magisk by flashing zip file from TWRP. Everything went back to normal. Hope this help.
trol_sg said:
Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
Click to expand...
Click to collapse
If you have a backup of your boot image, you can just restore it using TWRP. But in case that you have no backup of boot image, you can try to get boot image from the internet and restoring using it. In my case, this is what I did.
1. Go to TWRP and then make backup of boot image of the faulty phone*. (Folder 1)
2. I used another J2 prime to create a boot image backup. (Folder 2)
3. Once that is done, copy and replace the files inside the Folder 2 into Folder 1.
4. Reboot to TWRP again then use that to restore the boot image on my stuck J2.
Tips: make backup in SD card so you can easily swap it in between the bad and good phone.
*This is to create a folder of the backup file. I did tried to directly copy and paste the backup boot image file from another good phone but TWRP didn't detect it. So this is the workaround that I come with. And it worked for me.
Thanks for your answer but I doubt your case is mine. Your device is much newer than mine and according to your comment, you've sucesfully installed previous version of Magisk without issues. This is not a problem while updating, as Magisk v. earlier than 18.1 was not compatible with android 4.2+. I think Magisk is not compatible with MT6589T even if they run 4.2 or 4.4.
I think that it cannot be a boot problem as TWRP/CWM displayed msg 'Boot cannot be found' while installing Magisk, so that I don't think boot was replaced or modified in any ways. Moreover, the bootloop is not in the boot loading, as phone can pass boot image without any problem, but it is stuck in android loading image. I'm thinking in some script or root modification that Magisk did before trying to unpack the boot, however I'm not that deep into the Magisk install to find the proper workaround.
I can restore boot backup and also I can take boot file from the original rom and flash, because in Mediatek-based devices, boot.img is inside de zip, but I dont think it will solve the problem. Anyhow I'll get back ASAP with the answer.
Any more ideas??
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
trol_sg said:
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
Click to expand...
Click to collapse
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues
Ato09 said:
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues
Click to expand...
Click to collapse
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
Here I attach recovery.log if someone is interested to see the detailed problem.
Also, here below I attach the lines concerning the installation. All other is uninstallation tries and so on:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'
dalvikvm: [options] class [argument ...]
dalvikvm: [options] -jar file.jar [argument ...]
The following standard options are recognized:
-classpath classpath
-Dproperty=value
-verbose:tag ('gc', 'jni', or 'class')
-ea[:<package name>... |:<class name>]
-da[:<package name>... |:<class name>]
(-enableassertions, -disableassertions)
-esa
-dsa
(-enablesystemassertions, -disablesystemassertions)
-showversion
-help
The following extended options are recognized:
-Xrunjdwp:<options>
-Xbootclasspath:bootclasspath
-Xcheck:tag (e.g. 'jni')
-XmsN (min heap, must be multiple of 1K, >= 1MB)
-XmxN (max heap, must be multiple of 1K, >= 2MB)
-XssN (stack size, >= 1KB, <= 256KB)
-Xverify:{none,remote,all}
-Xrs
-Xint (extended to accept 'ortable', ':fast' and ':jit')
These are unique to Dalvik:
-Xzygote
-Xdexopt:{none,verified,all,full}
-Xnoquithandler
-Xjniopts:{warnonly,forcecopy}
-Xjnitrace:substring (eg NativeClass or nativeMethod)
-Xstacktracefile:<filename>
-Xgc:[no]precise
-Xgc:[no]preverify
-Xgc:[no]postverify
-Xgc:[no]concurrent
-Xgc:[no]verifycardtable
-XX:+DisableExplicitGC
-X[no]genregmap
-Xverifyopt:[no]checkmon
-Xcheckdexsum
-Xincludeselectedop
-Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]*
-Xincludeselectedmethod
-Xjitthreshold:decimalvalue
-Xjitcodecachesize:decimalvalueofkbytes
-Xjitblocking
-Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace)
-Xjitclass:classname[,classname]*
-Xjitoffsetffset[,offset]
-Xjitconfig:filename
-Xjitcheckcg
-Xjitverbose
-Xjitprofile
-Xjitdisableopt
-Xjitsuspendpoll
Configured with: debugger profiler hprof jit(armv7-a-neon) smp show_exception=1
Failed to initialize runtime (check log for details)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/dev/bootimg]
No boot image magic found!
! Unable to unpack boot image
- Unmounting partitions
E:Error executing updater binary in zip '/sdcard/Magisk-v18.1.zip'
Error flashing zip '/sdcard/Magisk-v18.1.zip'
@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
Didgeridoohan said:
@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
Click to expand...
Click to collapse
Thank you so much for your answer. So it's the recovery, but can't find newer ones, sadly. Too old phones I know, but just curious if I could make Magisk working on them, lol.
I was going into the boot modification manually right now, but in order to patch the boot I need manager installed first, and phone couldn't boot so I did dirty flash of the rom to be able to boot into it again.
Lets see what happens then. I'll be right back.
Anyhow, this is not a solution to fix the problem of bootloop that I am requesting help in case someone could face the same and did not make a backup of the phone and didn't want to make dirty re-flash. Any idea?
Update: After I did dirty flash of the rom, and now Jiayu g3s android 4.4 booted.
UPDATE: So, after patching manually boot and installing (using restore in TWRP 2.5 as image flash is not yet implemented AFAIK), phone booted and yes Magisk is working.
Magisk installation .zip through a very old recovery is making the bootloop. So that, a thing learnt now.
But, for other people facing this bootloop, can we do a research to find what magisk.zip did to the phones to leave them in bootloop? Maybe we can revert without rom flashing easily if we knew what's the issue...
Thanks in advance!
Doing a bit more tests I found that magisk.zip did something in /system so that it is left in bootloop, but still no idea why/whats causing that...
There are delay complete boot like 4 5 second in j7 prime. I didn't love this version
any more help?? up!!
trol_sg said:
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
Click to expand...
Click to collapse
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.
Ato09 said:
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.
Click to expand...
Click to collapse
Hello, thanks
This method won't work in my case as in the step:
- installed magisk uninstall = gives error
Note 5 is much newer phone with a recent recovery TWRP that allows all Magisk.zips commands, but unluckyly not this case.
Also, this method is for wrong boot installation/damaged boot. In my case what Magisk damage is /system, not boot.
I wish it could be boot, because that is very easy to fix (flashing through fastboot/SP Flash tools in the case of MTK, recovering boot twrp "backup" even if you didn't make backup...) as you mentioned.
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.
Main post updated with all thread information. Up!
Nothing?? Up!!
trol_sg said:
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.
Click to expand...
Click to collapse
The only part of the Magisk installation that actually touches /system is if it installs the addon.d survival script. The log you posted earlier shows that it's trying to do this, for some reason, and failiing. I'd start looking there...
Since mm isn't working on new Magisk 19, I took it for inspiration and created a simple manager, just for bypass some "bootlooper" module.
Just install it using recovery and run on terminal /data/media/magisk.
v1.0 - Initial build. Enabling and disabling functions
v2.0 - Added module removal function
v2.5 - No need to use storage to work. May avoid issues. Some others minor changes.
All thanks to
- topjonhwu for Magisk
- VR25 for mm
- TWRP team
- Me? Idk
Great work dev[emoji106], thanks
doesn't works for me (doesn't list modules)
mrhamed said:
doesn't works for me (doesn't list modules)
Click to expand...
Click to collapse
To list modules the script needs to write on /cache or /data. It will choose by itself.
Please send some screenshot of issue.
Looks very promising, especially enjoy having a GUI for this.
mrhamed said:
doesn't works for me (doesn't list modules)
Click to expand...
Click to collapse
I'm working to make script use no external files, so script will depends completely on your recovery binaries.
Hope to release it soon.
I suffer a boot freeze because of a bad module.
Cannot use TWRP and don't have module like Magisk Core Only installed.
I cannot boot to rooted system because of bad module.
Can boot non-rooted system only.
For my device LYA (Mate 20 Pro) which for rooting is using root-through-recovery-boot I can patch boot image with whatever Magisk edition which I assume is the best way to recover the device without full wipe.
Can a Magisk version be easily built which will either skip loading custom modules or delete them during boot? After successfully booting rooted I would flash a standard Magisk.
mikeos said:
I suffer a boot freeze because of a bad module.
Cannot use TWRP and don't have module like Magisk Core Only installed.
I cannot boot to rooted system because of bad module.
Can boot non-rooted system only.
For my device LYA (Mate 20 Pro) which for rooting is using root-through-recovery-boot I can patch boot image with whatever Magisk edition which I assume is the best way to recover the device without full wipe.
Can a Magisk version be easily built which will either skip loading custom modules or delete them during boot? After successfully booting rooted I would flash a standard Magisk.
Click to expand...
Click to collapse
I don't know if I got it correctly.
Well... commonly modules won't survive after Magisk removal.
If you can't access TWRP for flash Magisk uninstaller or disable the problematic module, you can try to flash or even boot the ROM's stock kernel through fastboot.
But if such module did others modifications into data, so you'll have to reflash whole ROM.
Are you planning on publishing this on magisk repo?
This has saved my bacon at least 4 times since installing it, many thanks Adriano
Saved me from bootloop module, works like a charm!
Adriano-A3 said:
Since mm isn't working on new Magisk 19, I took it for inspiration and created a simple manager, just for bypass some "bootlooper" module.
Just install it using recovery and run on terminal /data/media/magisk.
v1.0 - Initial build. Enabling and disabling functions
v2.0 - Added module removal function
v2.5 - No need to use storage to work. May avoid issues. Some others minor changes.
All thanks to
- topjonhwu for Magisk
- VR25 for mm
- TWRP team
- Me? Idk
Click to expand...
Click to collapse
It gives me the error "WTF?! The directory was here just now! It's gone! Please try again... Exiting..."
Thx bro, you saved my day
PixelHead0_0 said:
It gives me the error "WTF?! The directory was here just now! It's gone! Please try again... Exiting..."
Click to expand...
Click to collapse
Same here, on Samsung S10+ with August update, latest Magisk and Twrp.
very useful for android 10, thank you sir !
I can't understand how to run it on the terminal
will it work with Magisk 20.0??
Sivabalan said:
will it work with Magisk 20.0??
Click to expand...
Click to collapse
have you tried it? does it work on magisk 20.1
Confirmed working with Magisk 20.1, thanks a ton for this!
working on 20.2 + android 10