I'm looking to install Xposed on a Mi Max 2.
Already have TWRP installed
Rooted with SuperSu after dm-disable-verity
Prereq of busybox is installed.
Official Xposed installer causes bootloop, whether installed through TWRP or not.
Edit: The answer was to let it loop for SEVEN MINUTES. Wow. A couple loops, then it just sat there, and eventually booted. Works great now, the only thing I was missing was patience.
Related
Hi, I'm pretty sure I flashed the correct Xposed, but then it started to bootloop and I had the option to "Download and recovery",
So now I'm downloading.
Any other solution?
Boot to recovery and flash Xposed uninstaller. If you try to install Xposed again make sure you choose correct version. You need "xposed-v85.1-sdk23-arm64-custom-build-by-wanam-20160530".
yiftach said:
Hi, I'm pretty sure I flashed the correct Xposed, but then it started to bootloop and I had the option to "Download and recovery",
So now I'm downloading.
Any other solution?
Click to expand...
Click to collapse
I bought this phone yesterday. I could never start using a device unless I unlock bootloader, root and install xposed. I managed to unlock bootloader, flashed TWRP and also flashed systemless SuperSu (2.74-2). Also, I installed systemless xposed (i have shared link below). Phone took sometime and making me to think it is stuck in bootloader. I switched off and start in TWRP. Wiped art/dalvik and cache. Restarted normally. Everything worked fine.
Someone suggested here how to install official xposed (http://newesc.com/es/instalar-xposed-huawei-p9/).
But I installed systemless xposed (see here: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268) which works fine without the need of any changes in /system/emui/base/prop/local.pro with this line "ro.config.hwtheme=1" as mentioned in the link I shared above.
Thank you guys!
Hi all,
I just received an update to my OnePlus 2 - Oxygenos 3.5.5. The update removed the the recovery, root, Magisk and Xposed so I went ahead and flashed the TWRP again and then installed Magisk + phh's SuperUser.
All went fine, the phone booted OK. Then I decided to put back the Xposed and installed it via Magisk Manager and rebooted the phone. The phone got stuck at booting. I suspect that the new OxygenOS update + Xposed are the reason. I am able to uninstall the Magisk using the uninstaller and then can get back to the Magisk + root, but whenever I try to install Xposed the phone gets stuck when booting.
Any idea how to fix this?
6opuc said:
Hi all,
I just received an update to my OnePlus 2 - Oxygenos 3.5.5. The update removed the the recovery, root, Magisk and Xposed so I went ahead and flashed the TWRP again and then installed Magisk + phh's SuperUser.
All went fine, the phone booted OK. Then I decided to put back the Xposed and installed it via Magisk Manager and rebooted the phone. The phone got stuck at booting. I suspect that the new OxygenOS update + Xposed are the reason. I am able to uninstall the Magisk using the uninstaller and then can get back to the Magisk + root, but whenever I try to install Xposed the phone gets stuck when booting.
Any idea how to fix this?
Click to expand...
Click to collapse
https://github.com/rovo89/XposedBridge/wiki/Bugs#how-can-i-get-logs
Get a adb logcat on boot stuck with xposed installed, put it on pastebin and link here to see why isn't booting.
dcastro172 said:
https://github.com/rovo89/XposedBridge/wiki/Bugs#how-can-i-get-logs
Get a adb logcat on boot stuck with xposed installed, put it on pastebin and link here to see why isn't booting.
Click to expand...
Click to collapse
Hi dcastro172,
Unfortunately adb logcat does not give any info. At this boot stage the device is not detected yet by adb, hence no logcat possible. Is there anything I can collect differently?
Here are two logs from /data/data/de.robv.android.xposed.installer/log/
Perhaps this helps?
6opuc said:
Hi dcastro172,
Unfortunately adb logcat does not give any info. At this boot stage the device is not detected yet by adb, hence no logcat possible. Is there anything I can collect differently?
Click to expand...
Click to collapse
You see bootanimation or only splash logo?
Enviado de meu SM-G900M usando Tapatalk
6opuc said:
Hi all,
I just received an update to my OnePlus 2 - Oxygenos 3.5.5. The update removed the the recovery, root, Magisk and Xposed so I went ahead and flashed the TWRP again and then installed Magisk + phh's SuperUser.
All went fine, the phone booted OK. Then I decided to put back the Xposed and installed it via Magisk Manager and rebooted the phone. The phone got stuck at booting. I suspect that the new OxygenOS update + Xposed are the reason. I am able to uninstall the Magisk using the uninstaller and then can get back to the Magisk + root, but whenever I try to install Xposed the phone gets stuck when booting.
Any idea how to fix this?
Click to expand...
Click to collapse
Xposed v87?
I guess it is boot animation. It it like a clock with moving hands....
Yes. 87
6opuc said:
Yes. 87
Click to expand...
Click to collapse
Looks like update break Xposed, bunch of errors in log, open a issue at Xposed github.
So i sucessfully rooted my Huawei P8 Lite and installed TWRP. Then i tried to install Xposed v.89 for sdk23 (Android 6.0). The installation worked and it rebooted sucessfully, but after i installed the App on my phone it said xposed framework is installed but not active. So i tried to reboot my phone once more and this is when my phone started to be stuck in the huawei starting logo. I revoked everything and tried it a couple of times again and tried v85. It didnt change anything.
Can anyone help me with this because the virtual sensor module doesnt work without xposed framework being active and i just cant find a way to get it active and have the phone not get stuck while starting
My Huawei p8 Lite is running on android 6.0 with an ARM64 CPU
I hope anyone can help me with this.
Have you tried the uninstall zip?
You also shouldn't install a different Xposed zip if the one meant for your version didn't work. The others definitely won't work then.
Also, did you install any modules and tried to activate them? Maybe the module you activated is what caused the bootloop.
Sent from my Nexus 6P using Tapatalk
Hi,
I need some help
Today I successfully installed the newest stable Xiaomi.eu-ROM on my finally unlocked Mi8, using TWRP from here: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-1110-t3869729
TWRP is working flawlessly, but I didn't succeed in making root with Magisk to work.
What I did:
- I booted into TWRP
- formatted data
- rebooted back into TWRP
- flashed DM-verity disabler from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
- flashed Magisk v18.0 right after from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- wiped dalvik cache
- rebooted the phone
But everytime I did it, I didn't had root access (checked with Root Checker app) when the phone finally booted up to MIUI 10.1.2.0 (PEACNFI).
I even didn't have Magisk Manager showed up.
Can you tell me what I did wrong? I don't have a clue
Thanks a lot and best regards
Mischa
what does magisk manager tell you about your magisk installation status?
Strange thing...
After I rebooted the phone, there was no Magisk Manager nor the phone was rooted, what I checked with Root Checker app.
Then I used it a couple minutes before it became really laggy. My chosen theme disappeared back to stock theme, scrolling was nearly impossible and the screen went black.
I was not able to wake up the display again, so I held down the power button a couple seconds until the phone rebooted.
Now I saw that the Magisk Manager was installed, without me doing anything else than rebooting after the phone got unusable.
Weird, right? I read that there might be lags after installing Magisk, but that it's going to be like that was surprising.
Anyway, I have root now, TWRP works, Magisk v18 is installed. Now I only have to find some must-have-modules, e.g. like stereo-mod.
BTW, could it be that Netflix isn't working on rooted phones? I always get error 14 saying that the Netflix-service is not reachable even though I have internet connection.
hey dude i know this isnt a guide
but i followed your kind of direction after spending the whole afternoon and few hours in the evening to figure how to root this phone and finally it worked (so far)
thanks a lot my man
and i didnt even format after flashing twrp i hope it didnt **** up my phone
Hi everyone.
So I had a moto x4 for about year and a half before fricking up the charging port. So I recently acquired another one. Everything went smoothly the first month or so, with twrp properly installed and magisk too, but then I tried to install a magisk module and the phone bricked. I tried restoring via twrp backup but it didn't work and I ended up in a bootloop. So I flashed a stock rom. And when I wanted to install twrp it just didn't stick after a reboot and magisk would just get my phone stucked on the splashscreen.
I realized that, for whatever reason, a previous version of magisk would work (magisk 18.1) but I've no idea why. Magisk 18.1 is the only version that works. If I flash any other version from twrp my phone gets stuck on the splashscreen, same if I update magisk via magisk manager. And if I try to install any magisk module my phone won't start. But root permission works fine on other apps i.e. system app uninstaller, root explorer or swift installer.
Does anyone have any idea? It'd be greatly appreciated.
Thanks!!
Organics said:
Hi everyone.
So I had a moto x4 for about year and a half before fricking up the charging port. So I recently acquired another one. Everything went smoothly the first month or so, with twrp properly installed and magisk too, but then I tried to install a magisk module and the phone bricked. I tried restoring via twrp backup but it didn't work and I ended up in a bootloop. So I flashed a stock rom. And when I wanted to install twrp it just didn't stick after a reboot and magisk would just get my phone stucked on the splashscreen.
I realized that, for whatever reason, a previous version of magisk would work (magisk 18.1) but I've no idea why. Magisk 18.1 is the only version that works. If I flash any other version from twrp my phone gets stuck on the splashscreen, same if I update magisk via magisk manager. And if I try to install any magisk module my phone won't start. But root permission works fine on other apps i.e. system app uninstaller, root explorer or swift installer.
Does anyone have any idea? It'd be greatly appreciated.
Thanks!!
Click to expand...
Click to collapse
Please help me to root Moto X4, bootloader unlocked
hrushikesh.inc said:
Please help me to root Moto X4, bootloader unlocked
Click to expand...
Click to collapse
Wrong thread.
https://forum.xda-developers.com/moto-x4/help/moto-x4-f-q-s-thread-t3814393