Hello,
I'm trying to root my old Moto E 2nd Gen and install the xposed framework.
However, I keep getting stuck in a bootloop.
These are the steps I'm taking..
- Wipe device
- Flash stock firmware, Android 5.1
- Install TWRP to recovery
- Flash Magisk through TWRP
- Open Magisk, install Magisk Manager
- Download Xposed Framework through Magisk and install
- Upon rebooting, I'm stuck in a bootloop.
I've also tried rooting via SuperSu and the same thing happened.
Also note, the first time I tried install xposed I got it to work, but messed something else up and had to restart. Since then I've been getting the bootloop - ie. the phone stays frozen on the "OEM unlocked" screen.
Any help? Am i missing a step?
Related
A while ago, I had TWRP and magisk working. I decided to try and install xposed from the magisk repository, which ended in a bootloop, so I restored the phone using eRecovery.
After this, I installed TWRP and attempted to install magisk again, which led to a bootloop once again - this happens every time I install magisk.
I have tried using uninmod, which just displays no modules to uninstall when I use it in the terminal, and I have tried mounting magisk.img to a folder, but this just contains "lost+found" and no modules.
It would be a great help if someone could offer some advice on how to fix this, because I hope to flash EMUI 9.
Just some quick instructions that helped me with issues with Magisk 19 most recently.
Problem: you updated the ROM, flashed Magisk and now the phone always reboots to recovery within a few seconds of unlocking it.
Solution:
- Flash Magisk 17.3. this should get you back to a stable system with root, but without working modules.
- Install Magisk Manager 6 to use with 17.3
- Use Root Explorer and go to /data/adb
- Delete all files called Magisk and the modules folder
Reboot and reflash Magisk 19
- update Magisk Manager
I almost gave up and would have started from scratch. I don't know why Magisk 19 corrupted after the update but even after deleting only the modules folder it wouldn't work. The phone finally worked normal again after just deleting all things Magisk in the /data/adb folder.
Unfortunately TWRP doesn't mount the encrypted /data partition yet so you can't use Magisk Recovery or Magisk uninstaller from TWRP. I found this workaround finally fixed my issues and I hope it is helpful to someone else on the forum.
Best of luck!
mrchrister said:
Just some quick instructions that helped me with issues with Magisk 19 most recently.
Problem: you updated the ROM, flashed Magisk and now the phone always reboots to recovery within a few seconds of unlocking it.
Solution:
- Flash Magisk 17.3. this should get you back to a stable system with root, but without working modules.
- Install Magisk Manager 6 to use with 17.3
- Use Root Explorer and go to /data/adb
- Delete all files called Magisk and the modules folder
Reboot and reflash Magisk 19
- update Magisk Manager
I almost gave up and would have started from scratch. I don't know why Magisk 19 corrupted after the update but even after deleting only the modules folder it wouldn't work. The phone finally worked normal again after just deleting all things Magisk in the /data/adb folder.
Unfortunately TWRP doesn't mount the encrypted /data partition yet so you can't use Magisk Recovery or Magisk uninstaller from TWRP. I found this workaround finally fixed my issues and I hope it is helpful to someone else on the forum.
Best of luck!
Click to expand...
Click to collapse
Had this issue a while back and ended up starting with a clean install. Nice that you found a fix, should come in handy if I ever face the same problem again...
Hi,
I have similar issue as you but slightly different. Whatever I tried to flash (e.g: twrp (multiple version) or patched magisk boot img). It always reboot to mi official recovery.
Do you face this issue before and how you fixed it?
Info:
Mi 9 EEA rom
cutesniper22 said:
Hi,
I have similar issue as you but slightly different. Whatever I tried to flash (e.g: twrp (multiple version) or patched magisk boot img). It always reboot to mi official recovery.
Do you face this issue before and how you fixed it?
Info:
Mi 9 EEA rom
Click to expand...
Click to collapse
Take a look, if your bootloader is unlock!
Maybe it is relocked.
I had the same issue today, what I did is quickly opened up Magisk manager, and clicked uninstall. It still rebooted in the middle of the process, but after I flashed 19.1, it never rebooted again!
bombername said:
Take a look, if your bootloader is unlock!
Maybe it is relocked.
Click to expand...
Click to collapse
No, I can confirmed it's unlocked because I'm able to flash global rom into mi 9 china phone.
Hi
i have huawei p20lite
Ive unlocked bootloader, have twrp as recovery, installed magisk (rooted)
Now everytime i try to install xposed framework i get bootloop. Ive tried the module within magisk and flashing the zip with twrp.
yet every time bootloop.
if anyone has succsessfully installed xposed framework or has any insight on how to i would really appreciate it.
—Problem—
Boot loop... is there anyway to solve this problem without a reset?
—generel Infos—
Device: OnePlus 5 (rooted)
OS: oxygenos 9.0.3
Recovery: TWRP
Other: using EDXposed &
Nethunter Kernel
—the reason?—
I think it was the experimental setting in GravityBox Pie. There was a warning but I didn’t read it because ... I don’t know. The setting required a reboot but after that I stuck in the boot loop.
—what I ´ve tried—
I saw a guide on xda how to disable xposed modules via twrp. The problem was that I was using EDXposed. It was a different. But I deleted a similar file via twrp file manager ( /data/data/com.[IdontKnowTheExactPackgeName].xposed.manager/shared_prefs/[SomethingWithModules])
I tried to reboot but without success
I installed mm ( a for twrp to disable/enable magisk modules and more)
In mm I disabled the EDXposed Module und riru Core Module ( Im not sure if I was riru)
I tried to reboot but without success
I flashed magisk uninstaller and after flashing was done( magisk couldn’t restore boot image or something like that but the flash worked so I ignored it) I got the error: error creating fstab ( the same error occurred when wiping cache/dalvic)
I tried to reboot but without success
I wanted to flash EDXposed but it didn’t work because I haven’t magisk installed
So I flashed magisk again ( this solved the fstab error) and after that the EDXposed uninstaller. Both flashes worked
I tried to reboot but without success
Now I gave up and hope that you have an ansewer
Master Luca said:
—Problem—
Boot loop... is there anyway to solve this problem without a reset?
—generel Infos—
Device: OnePlus 5 (rooted)
OS: oxygenos 9.0.3
Recovery: TWRP
Other: using EDXposed &
Nethunter Kernel
—the reason?—
I think it was the experimental setting in GravityBox Pie. There was a warning but I didn’t read it because ... I don’t know. The setting required a reboot but after that I stuck in the boot loop.
—what I ´ve tried—
I saw a guide on xda how to disable xposed modules via twrp. The problem was that I was using EDXposed. It was a different. But I deleted a similar file via twrp file manager ( /data/data/com.[IdontKnowTheExactPackgeName].xposed.manager/shared_prefs/[SomethingWithModules])
I tried to reboot but without success
I installed mm ( a for twrp to disable/enable magisk modules and more)
In mm I disabled the EDXposed Module und riru Core Module ( Im not sure if I was riru)
I tried to reboot but without success
I flashed magisk uninstaller and after flashing was done( magisk couldn’t restore boot image or something like that but the flash worked so I ignored it) I got the error: error creating fstab ( the same error occurred when wiping cache/dalvic)
I tried to reboot but without success
I wanted to flash EDXposed but it didn’t work because I haven’t magisk installed
So I flashed magisk again ( this solved the fstab error) and after that the EDXposed uninstaller. Both flashes worked
I tried to reboot but without success
Now I gave up and hope that you have an ansewer
Click to expand...
Click to collapse
Try reflashing rom you are using again in recovery.so dirty flash over existing one
Sent from my LEX820 using Tapatalk
bilausdaniel said:
Try reflashing rom you are using again in recovery.so dirty flash over existing one
Sent from my LEX820 using Tapatalk
Click to expand...
Click to collapse
Still in boot loop ( I let it boot for 18 min )
Did you tried to disable xposed on booting?
There is key combination when system boots up, to disable xposed, and so all modules.
Go into recovery, and boot up again from there (normal boot), and when logo appears click at least 3 times power button, and xposed will understand it need to disable itself.
That should work.
And if you have some data in phone, you can make app backup from recovery and if you have files you can connect to PC and copy those files on PC.
I am currently having this problem. Some fully updated systems on some devices won't boot into safe mode. Among those devices are many Xiaomi Devices. I can only boot into fastboot mode.
I've got Orange Fox so theoretically I should be able to delete Riru, effectively disabling exposed, however, Orange Fox is asking for a decryption password and I can't access files to delete them.
ADB sideload failed.
Not sure if I can even do a wipe back to default state.
brasscupcakes said:
I am currently having this problem. Some fully updated systems on some devices won't boot into safe mode. Among those devices are many Xiaomi Devices. I can only boot into fastboot mode.
I've got Orange Fox so theoretically I should be able to delete Riru, effectively disabling exposed, however, Orange Fox is asking for a decryption password and I can't access files to delete them.
ADB sideload failed.
Not sure if I can even do a wipe back to default state.
Click to expand...
Click to collapse
go in twrp and to android/adb/modules.. module there reboot phone
bilausdaniel said:
go in twrp and to android/adb/modules.. module there reboot phone
Click to expand...
Click to collapse
delete that module in there
Waking up with a sleepy head I wanted to swipe the new version notification away, but didnt swipe well enough and it actually upgraded. I need to downgrade to v23 again but for whatever reason, its not working. Here's what I tried:
1. Reboot to fastboot and do fastboot boot magisk_patched.img (boot img with magisk 23 I use after OTA's). This boots but its not rooted. Magisk mgr is 24 though.
2. Rebooted to system, uninstalled Installed magisk manager 24, rebooted and retried the above. Installed Magisk mgr 23. No root.
I then unpacked the latest full oos 11 for my phone with payload_dumper, copied the boot.img to my phone and patched it using magisk manager 23. Copied it back to the PC.
retried step 1. No root.
Rebooted to fastboot again, checked current slot, its A.
fastboot flash boot magisk_patched.img (the new one I patched in the step above).
Rebooted, no root.
What am I supposed to do to get Magisk 23 back on my phone?
The reason is I'm dependent on riru/lsposed for a couple of xposed modules. If I disable zygisk in magisk 24 I won't have root hide, if I enable that, riru/lsposed isn't working.
Thanks for the help!
Yeah I had a similar issue on A12 rom, Magisk 24 just doesn't allow me to pass safety net due to Google play services in Magisk 24 deny list unselects after a reboot, so downgrading to 23 which just works after using hide list.
I had to disable and remove any modules, unhide Magisk 24 then restart.
Use Magisk 24 uninstall in the app and restart.
Install Magisk 23 and Install to boot image file to payload Boot.img, restart to Fastboot and flash as you did.
Then again in Magisk install select Direct Install then restart.
Reapply Magiskhide to apps google pay/services etc restart and check root.
I still have an issue with Magisk hiding the app installs the proxy app but it doesn't open so isn't working, so still working on this. Root is working tho with the above.
Thanks, I still cant get it to work though.
I can patch the boot.img, but when I try to boot it I don't get root.
When I flash and boot it, there still is no root available.
Possibly i had the same issue, no root after flashing the 23-modified boot image. I solved it by, upgrading the app to 24.3, patch the boot image, reboot to fastboot, flash it, reboot it so i was back at Magisk 24.3 Then i did a full uninstall of Magisk, via the app. Then installed app v23. Patched the boot image etc as per https://topjohnwu.github.io/Magisk/install.html#patching-images
Key here was, i think the full removal of Magisk 24 before downgrading.