Hey guys, following problem. I rooted my device succesfully and installed some magisk module. But by accident i installed a module i knew will push device in bootloop if i reboot. When i reboot i stuck in a bootloop, but when i boot the original boot image i am able to boot up succesfully, do you guys have any idea how i can uninstall the module (we dont have any twrp) or how i can use the stock boot image even after reboot? Thx in advance
fritzcola said:
Hey guys, following problem. I rooted my device succesfully and installed some magisk module. But by accident i installed a module i knew will push device in bootloop if i reboot. When i reboot i stuck in a bootloop, but when i boot the original boot image i am able to boot up succesfully, do you guys have any idea how i can uninstall the module (we dont have any twrp) or how i can use the stock boot image even after reboot? Thx in advance
Click to expand...
Click to collapse
Only option I found to work without twrp is a factory reset from settings while booted on a unpatched bootimage
Sent from my HD1913 using Tapatalk
UPDATE: i used "fastboot flash boot boot.img" and now it stays unrooted even after reboot. But if i want to re-root i gues i have to wait till twrp is released...
Related
So hey! I successfully booted into the TWRP and used it to flash the DISABLEFORCEENCRYPTION file, right after. I decided to reboot to recovery (Cause I think that would be great just after you flash something in TWRP) but then after it finishes showing the pocophone booting screen rather than showing TWRP recovery. It showed the stock MIUI recovery! someone please help! I just finished flashing magisk and a custom rom by using the method of: Everytime I need to flash something using TWRP I would just open adb and fastboot boot recovery it again so that I could use the TWRP!
Thank you in advance!
GGerniWhite said:
So hey! I successfully booted into the TWRP and used it to flash the DISABLEFORCEENCRYPTION file, right after. I decided to reboot to recovery (Cause I think that would be great just after you flash something in TWRP) but then after it finishes showing the pocophone booting screen rather than showing TWRP recovery. It showed the stock MIUI recovery! someone please help! I just finished flashing magisk and a custom rom by using the method of: Everytime I need to flash something using TWRP I would just open adb and fastboot boot recovery it again so that I could use the TWRP!
Thank you in advance!
Click to expand...
Click to collapse
I decided to fix this problem after I flashed a rom cause I think I would run into future problems involving magisk and it's use of the TWRP recovery.
GGerniWhite said:
I decided to fix this problem after I flashed a rom cause I think I would run into future problems involving magisk and it's use of the TWRP recovery.
Click to expand...
Click to collapse
If you already have the ROM installed, use adb to flash TWRP and without booting flash Magisk and then boot to system. If you are on stock ROM, follow THIS.
For entering into TWRP, use the key combination of volume up + power buttons.
You can use the encryption compatible TWRP (search for it) instead of the official one.
—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
I had a boot loop trying to install a module.I am in build 11.0.11 without twrp.I used the command adb wait ... to remove modules via adb but the problem didn't solve.After that I reinstalled the stock rom and the phone reboots. But when I tried to reinstall magisk using the patched img via adb I had bootloop again so I reinstalled again the rom. What can I do to solve the problem?
You are probably flashing the wrong boot.img for the firmware you are on perhaps?
Make sure it is the patched.img from here you flash https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/post82207833
Credits: @Sapper Morton
Thanks for the answer, but it isn't the boot.img, the specific module (sony music!) was the problem..
At last I installed twrp using the q- base twrp.img and I disabled this module via twrp and the magisk manager for recovery....The phone booted normally with the others modules to work fine...
Hey guys, so I had the forced update to Android 10 about 1 month ago, and I lost root, which I didn't found about until I tried installing something today.
As this isn't my first time losing root I just followed the steps I always do on this guide (https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509) and I managed to successfully install TWRP, but the phone is now stuck on the orange MI logo when I reboot to system. Someone pls help!
Edit: For anyone curious, I just used the Fix Recovery Bootloop inside TWRP and it worked! I still don't have root tho...
Edit 2: After trying to flash Magisk installer for the second time I determined it to be the problem. Can anyone help me with that?
Use the magisk patched boot.img from here that corresponds with your firmware version and follow to guide to flash in fastboot https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page40
garylawwd said:
Use the magisk patched boot.img from here that corresponds with your firmware version and follow to guide to flash in fastboot https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page40
Click to expand...
Click to collapse
Just tried that, the phone is stuck again on the orange MI logo and now when I try to boot into TWRP it shows an android laying down with the message "No command" PLEASE HELP
garylawwd said:
Use the magisk patched boot.img from here that corresponds with your firmware version and follow to guide to flash in fastboot https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page40
Click to expand...
Click to collapse
Just tried that, the phone is stuck again on the orange MI logo and now when I try to boot into TWRP it shows an android laying down with the message "No command" PLEASE HELP.
Edit: I just flashed TWRP on flashboot and I was able to solve this. I can't still fond what's the issue with magisk tho.
SirAerion said:
Just tried that, the phone is stuck again on the orange MI logo and now when I try to boot into TWRP it shows an android laying down with the message "No command" PLEASE HELP.
Edit: I just flashed TWRP on flashboot and I was able to solve this. I can't still fond what's the issue with magisk tho.
Click to expand...
Click to collapse
What Magisk modules do you have installed? They might be preventing the phone to boot up.
_mysiak_ said:
What Magisk modules do you have installed? They might be preventing the phone to boot up.
Click to expand...
Click to collapse
Afaik the only module I HAD installed before the forced update was Smali patcher for POGO. But I can't check the modules now because the option isn't there in the manager.
SirAerion said:
Afaik the only module I HAD installed before the forced update was Smali patcher for POGO. But I can't check the modules now because the option isn't there in the manager.
Click to expand...
Click to collapse
Well, the module "only" patches framework from the phone, so you're trying to boot Android 10 system with Android 9 framework. It doesn't get uninstalled automatically even if you remove Magisk from boot image.
Either flash Magisk uninstaller from TWRP or flash correct patched boot file, connect phone to the PC, type in this command and reboot the phone.
adb wait-for-device shell magisk --remove-modules
I'm looking for help getting Magisk installed on MIUI 12.1.1. If I use the boot.img and pass it to Magisk manager and flash it, the system just reboots to recovery after a few minutes.
Does anyone have it working or a recovery that works with 12.1.1 global?
moffa~ said:
I'm looking for help getting Magisk installed on MIUI 12.1.1. If I use the boot.img and pass it to Magisk manager and flash it, the system just reboots to recovery after a few minutes.
Does anyone have it working or a recovery that works with 12.1.1 global?
Click to expand...
Click to collapse
By "passing it to magisk", do you mean patching the boot.img and getting a magisk_patched.img? Do you have the latest magisk app? It's no longer called magisk manager (v22).
Edit: You probably just hot the patched boot from the wrong boot.img
Tulsadiver said:
By "passing it to magisk", do you mean patching the boot.img and getting a magisk_patched.img? Do you have the latest magisk app? It's no longer called magisk manager (v22).
Edit: You probably just hot the patched boot from the wrong boot.img
Click to expand...
Click to collapse
Hi, thanks for responding.
Yes, I mean I take the boot.img from the MIUI fastboot package and select it in Magisk (no longer manager). I then reboot to bootloader mode, then run "fastboot flash boot magisk_patched_sLsab.img " but after running fastboot reboot it just ends up in recovery mode.
The only way to recover is to use fastboot to flash the original boot.img back over
I finally figured out that I had magisk modules left over before the upgrade which broke everything. A factory reset wiping all data has fixed it.