—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
Related
Hello !
I've tried to install Xposed with Magisk (the v3 beta version, notorious for provoking bootloops instead of the v4 which was the right one) and got stuck in a bootloop. I rebooted into TWRP and tried to restore a backup (system, system image, vendor image and ramdisk), and it still went in bootloop. I figured that, as Magisk was systemless, Magisk and Xposed were still there, so I flashed uninstall-magisk.zip.
Unfortunately, now I don't have access to TWRP (maybe flashing uninstall-magisk flashed the original erecovery over TWRP ?) and whenever I try to boot, I enter the eRecovery with written "Serious problems occured when the device boot" and the options I have are:
-Download latest version and recovery
-Wipe data/factory reset
-Reboot
-Shutdown
Should I use the "download latest version and recovery" ?
Should I try to flash TWRP with fastboot ?
I guess I can't do a factory reset since I updated before to BLA-L29 8.0.0.157(C432) from BLA-L29 8.0.0.120(C432) and downgrading seems to provoke a hard brick.
Thank you.
Edit: Thanks to ante0, I had access to TWRP (couldn't access it since USB was still connected). He suggested I use HuRUpdater TWRP script to update to the same build I have on my device now. I will report once, and if, I succeed in doing this. In the meantime, if anybody as ideas, I wouldn't mind hearing them !
Edit: Ante0 told me that I had to use the HuRUpdater TWRP script to update to the same build I was before bootlooping, so I did and everything went back to normal.
if u you want try xposed or any system less magisk modules be sure to have magisk manager for recovery mode
that's will ensure if u got bootloop to boot to recovery mode and only un tick xposed module or any module got ur devise to bootloop
FYI Xposed v90 beta 3 (which I think is the latest official build) is not compatible with EMUI 8.0 and will cause a bootloop. You need to install v90 beta 4.
https://forum.xda-developers.com/showpost.php?p=77269446&postcount=7439
https://github.com/rovo89/Xposed/issues/310
Antidote03 said:
if u you want try xposed or any system less magisk modules be sure to have magisk manager for recovery mode
that's will ensure if u got bootloop to boot to recovery mode and only un tick xposed module or any module got ur devise to bootloop
Click to expand...
Click to collapse
Didn't know that there was a Magisk Manager available for the recovery, if I succeed in unbricking the device I'll try it out before installing any Magisk Module, thanks !
thref23 said:
FYI Xposed v90 beta 3 (which I think is the latest official build) is not compatible with EMUI 8.0 and will cause a bootloop. You need to install v90 beta 4.
https://forum.xda-developers.com/showpost.php?p=77269446&postcount=7439
https://github.com/rovo89/Xposed/issues/310
Click to expand...
Click to collapse
I went on the official Magisk thread to get the latest build, absolutely forgetting about the v4 that I had seen on another thread a few hours before, unfortunately it was too late when I realized the mistake I had done by flashing the wrong version
Finally systemless Xposed works on Mate 10 Pro
thref23 said:
FYI Xposed v90 beta 3 (which I think is the latest official build) is not compatible with EMUI 8.0 and will cause a bootloop. You need to install v90 beta 4.
https://forum.xda-developers.com/showpost.php?p=77269446&postcount=7439
https://github.com/rovo89/Xposed/issues/310
Click to expand...
Click to collapse
MANY thanks indeed !! After days of searching on XDA and elsewhere...your link brought back Xposed on Ore0 8.0 Mate 10 Pro. Greatly appreciated.
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.
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
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
You have to be decrypted or flash DMverity for A12. I assume You mean Magisk 24.1 the current version is 24.3
Hi. This is what I did:
I downloaded and installed original firmware through fastboot (fastboot was still on).
I also installed original recovery through fastboot.
After that my oneplus 5t was in stock condition, apart from the bootloader, which was unlocked.
After that I managed to install TWRP through fastboot, and then lineage 19.
The thing is that TWRP doesn't support lineage 19, for one reason or another. Or it could be the other way around (lineage 19 doesn't support TWRP). In any case I had a phone which would only go in fastboot mode.
At least I knew what to do, as I did it already: reinstall stock firmware and recovery.
Long story short, I installed LOS recovery and lineage 19, and everything works fine.
Thanks everyone, and especially thaidroid, for the support.
Have a nice day.
miclombardo said:
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
Click to expand...
Click to collapse
Its not working cus you need to format data in recovery and then reboot it.
kirknado18 said:
Its not working cus you need to format data in recovery and then reboot it.
Click to expand...
Click to collapse
It wont boot cus your encrypted formatting data will allow op5t to boot.
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
paradoxiumwind said:
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
Click to expand...
Click to collapse
What recovery are you on? TWRP?
I use the one posted alongside each version: https://download.lineageos.org/dumpling
can you help?
I need to root so I can titanium backup everything. but I can't root. I suspect I might need to fully format and wipe and start again, I tried wiping data and doing a fresh install, but after sideloading magisk it just fails to boot every time now.
Does it boot regularly BEFORE installing magisk? I am trying to define the source of the problem.
I have installed lineage 19 and magisk, and I confirm you that it's possible
Yes. It boots fine if I just install lineage then nevermindthegapps. problem only occurs if I flash magisk. I tried installing the .apk and patching the .boot image manually in it and then fastboot flashing that, but same thing.
oh - one possible thing that it may be - is that I had a couple of modules loaded (I think a gcam fix mod and something similar) in magisk, and I read somewhere about people having them stuck 'installed' despite demoving all traces of magisk app. whether that is the problem I don't know.
This is very strange. That's what I did:
Sideload lineage recovery
Sideload lineage 19
Download magisk apk
Patched boot image from lineage 19.zip
Sideload the patched boot image
And that's it it all worked
May I suggest you to start all over again?
is wiping system data sufficient or do I need to format it? I'd rather not lose my appdata- but I can't rescue it without root / titanium backup :/
Try first without formatting, and see how it goes
I wiped system/cache, installed lineage-19.1-20220719-nightly-dumpling-signed.zip / mindthegapps, phone booted up fine - rebooted fine.
ok, good. Now download latest magisk app and patch the boot img.
do I click patch vbmeta in image?
Yes.
First extract the file called boot.img from lineage.zip you just installed.
Then in magisk select "patch vbmeta in image".
Magisk should produce a file named something like " magisk_pached-24300_f41h3.img".
That patched file should be sideloaded.
Installation is explained really well by topjohnwu
it wouldn't flash without selecting vbmeta, so tried with, flashed it, now i'm sitting looking at the boot logo.