Is it possible that sound mods such as V4a, sauron, adm lib cause bootloop?
I uninstalled each of them individually in twrp, but it was still in bootloop.
Was this caused by youtube vanced apk along with microg plugin?
jaspad1710 said:
Is it possible that sound mods such as V4a, sauron, adm lib cause bootloop?
I uninstalled each of them individually in twrp, but it was still in bootloop.
Was this caused by youtube vanced apk along with microg plugin?
Click to expand...
Click to collapse
I'm using V4A as well as the youtube vanced modules, none of them caused any bootloops, the only bootloop i did get was probably only when i used the xposed module.
Here's what you should try, Install magisk manager for recovery mode module and delete every other module, then check them one by one, if they cause bootloops. Install a module, reboot, don't install another one. If you do get a bootloop at any instance, go to recovery mode and open up the terminal in advanced and type in : /data/media/mm then just follow on screen instructions and disable the module causing the bootloop.
franz said:
I'm using V4A as well as the youtube vanced modules, none of them caused any bootloops, the only bootloop i did get was probably only when i used the xposed module.
Here's what you should try, Install magisk manager for recovery mode module and delete every other module, then check them one by one, if they cause bootloops. Install a module, reboot, don't install another one. If you do get a bootloop at any instance, go to recovery mode and open up the terminal in advanced and type in : /data/media/mm then just follow on screen instructions and disable the module causing the bootloop.
Click to expand...
Click to collapse
I guess it was due to multiple mods i flashed in one go. Im with v4a and yt vanced now for almost two days no prob now..
jaspad1710 said:
Is it possible that sound mods such as V4a, sauron, adm lib cause bootloop?
I uninstalled each of them individually in twrp, but it was still in bootloop.
Was this caused by youtube vanced apk along with microg plugin?
Click to expand...
Click to collapse
I have also installed Magisk and Arise Magnum Opus and now i am in bootloop.
I tried to restore my previous backup, but it was not success.
The phone directly boots into FASTBOOT if i flash LOS16 fresh image and if i flash Magisk along with LOS16, it doesn't show any FASTBOOT but stays in bootloop.
The vendor partition have some weird amount of memory looks like 17592186043943MB!
Please help to recover the issue asap.
I installed YouTube vanced from magisk manager and rebooted directly into recovery and then flashed the notification icon enabler from TWRP and was then just bootlooping to TWRP. I uninstalled the notification enabler with the disabler given by the same website but the phone still bootlooped. I uninstalled YouTube vanced from TWRP terminal but the phone still bootlooped. Tried to restore a nandroid backup but in vain.
The only thing that seemed to be working was uninstalling magisk using the official uninstaller and the phone booted to system but I obviously lost root.
Had to flash the ROM through fastboot which formats the phone and then unlock , install TWRP and root again.
Related
I installed systemless Xposed through magisk and it got my phone stuck in bootloop so I tried to fix it by using HWOTA8 and used the OTA.bat fixed the problem but when I installed Magisk again the problem happens again so is there anyway to delete all modules installed by Magisk from recovery?
CodeRida said:
I installed systemless Xposed through magisk and it got my phone stuck in bootloop so I tried to fix it by using HWOTA8 and used the OTA.bat fixed the problem but when I installed Magisk again the problem happens again so is there anyway to delete all modules installed by Magisk from recovery?
Click to expand...
Click to collapse
there is a mount magisk zip to flash in recovery. but don't have link ready, just search on google, should be easy to find
I rooted my phone this morning and flashed xposed on magisk right after. Also flashed the Google sans font module and the cloudfare module. And then I rebooted the device. But it has been stuck on the boot screen for almost an hour.
Does any one know what could have caused this? Any notable fixes?
Not all magisk modules and xposed are compatible. Flash stock firmware
Most probably its the xposed, there is no way right now to use XPOSED on miui based on 8.1 oreo.
zaydenQ said:
I rooted my phone this morning and flashed xposed on magisk right after. Also flashed the Google sans font module and the cloudfare module. And then I rebooted the device. But it has been stuck on the boot screen for almost an hour.
Does any one know what could have caused this? Any notable fixes?
Click to expand...
Click to collapse
Xposed is the culprit.
Here's how you uninstall problematic magisk module from twrp since you're stuck in bootloop
https://magiskroot.net/uninstall-ma..._Module_with_Magisk_Manager_for_Recovery_Mode
Thanks to everybody for their replies. I flashed the stock ROM using MiFlash tool and it worked. Thankfully didn't lose anything important in the process.
There's a list of "reliable" magisk modules for Poco F1? I just installed AnxCam (MIUI Cam Port) and Youtube Vanced and I'm impressed with'em.
If he uninstalled magisk instead as stated in link below, would that work? Isn't it systemless?
https://magiskroot.net/uninstall-magisk-module-twrp/
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.
—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 am on miui 11.0.4 & no gravity kernel.
When i flash magisk & reboot it stays at poco loading screen. The phone just doesn't boot.
Any Solution?
agentliquid47 said:
I am on miui 11.0.4 & no gravity kernel.
When i flash magisk & reboot it stays at poco loading screen. The phone just doesn't boot.
Any Solution?
Click to expand...
Click to collapse
I'm having the same issue. When I flash magisk uninstaller, it boots properly.
paprazzi95 said:
I'm having the same issue. When I flash magisk uninstaller, it boots properly.
Click to expand...
Click to collapse
I figured it out. One of the magisk module was causing this problem so i deleted all modules using twrp file manager.
Here is what you can try
Open twrp. Go to advanced the file manager then data/adb/modules and delete all the module and reboot to system. Then open twrp again and flash magisk 20.3. No Bootloop.
agentliquid47 said:
I figured it out. One of the magisk module was causing this problem so i deleted all modules using twrp file manager.
Here is what you can try
Open twrp. Go to advanced the file manager then data/adb/modules and delete all the module and reboot to system. Then open twrp again and flash magisk 20.3. No Bootloop.
Click to expand...
Click to collapse
Hi.
The data/adb/ folder is empty. There is no module folder in it.
agentliquid47 said:
I am on miui 11.0.4 & no gravity kernel.
When i flash magisk & reboot it stays at poco loading screen. The phone just doesn't boot.
Any Solution?
Click to expand...
Click to collapse
yea i have really bad experience with this kernel, did you install DTS:X ? maybe this one make you bootloop, i do have this issue also.
DOYANMAIN said:
yea i have really bad experience with this kernel, did you install DTS:X ? maybe this one make you bootloop, i do have this issue also.
Click to expand...
Click to collapse
Yes dts x was causing the issue just delete dtsx using twrp fike manager and you are good yo go.
i have installed bromite systemless webview magisk module and tried to install it this has stooped the magisk manager to stop and i tried to reboot my device and it is stuck on boot loop, i have acessed twrp and deleted the module which has caused the bootloop but to my dismay i am still at boot lop can any one please help me