Develop Bugs

booting forever after rooting oxygenOS 3.2.8

So I was on rooted 3.2.6 with xposed installed and decided to upgrade to 3.2.8.
I dirty flashed the full ROM 3.2.8 onto my 3.2.6 (without flashing SU or xposed because I wanted to use Snapchat with snapprefs again so I i flashed 3.2.8 without root , logged into Snapchat etc. )
after that I flashed superuser and xposed and since then my phone doesnt boot.
I interrupted the first try because it took over 20 minutes then tried it again after clearing cache and dalvik but it still doesnt boot ( i see the two circles and red dot)
Hope someone can help me
PS: I didnt make a backup because it would be too large, on the other hand I have the full 3.2.8 on my internal storage as well as the latest superSU

solved it
If someone experiences the same problem you need the newest xposed version v87. Flash it normally and wipe cache/dalvik , thats it !

I had that, I fixed it by boot to twrp flash the xposed uninstaller zip to remove xposed, then the phone should boot normally, I then found a newer version of xposed (the November security patch in 3.2.8 doesn't like older versions) and flashed it via twrp again, all my modules were still there and didn't need setting up again either.
Hope that helps

J_The_Nerd said:
I had that, I fixed it by boot to twrp flash the xposed uninstaller zip to remove xposed, then the phone should boot normally, I then found a newer version of xposed (the November security patch in 3.2.8 doesn't like older versions) and flashed it via twrp again, all my modules were still there and didn't need setting up again either.
Hope that helps
Click to expand...
Click to collapse
thats exactly what I did and it works perfectly now. Thanks.

magisk not working on all OOS OREO ROMS

Hello xda community.
I got some knowledge about flashing stuff on my oneplus 3. But Since I use Android oreo beta 29, 30, or stable 5.0 OOS version even when I use the aroma installer from Freedom OS. Magisk doesn't install propobly. .
Im using latest Twrp from Bluespark 3.2.1 -X
I can flash most off the magisk versions 15.0 - 15.1 - 14.6 without bootloops. I tried alot off them but when I boot the phone magisk is not installed.(there is no Magisk app)
When I install the magisk apk. the magisk is also telling me magisk is not installed.
On beta 29 SuperSU was working didn't try it yet on beta 30 but I really want to use Magisk.
I'm reading the forums here also on the OP community but seems like I'm the only one with this problem.

uninstall magisk app from the rom, flash rom again and then flash magisk 15.3... works fine

theduke7 said:
uninstall magisk app from the rom, flash rom again and then flash magisk 15.3... works fine
Click to expand...
Click to collapse
Thanks for your reply.
I did a clean flash Beta 29 also on 30.
15.3 is not working to for me....

Ghost123NL said:
Thanks for your reply.
I did a clean flash Beta 29 also on 30.
15.3 is not working to for me....
Click to expand...
Click to collapse
flash the rom then reboot to recovery then flash magisk... don't flash immediately after the rom ....

theduke7 said:
flash the rom then reboot to recovery then flash magisk... don't flash immediately after the rom ....
Click to expand...
Click to collapse
Also not working.
same steps with supersu is working only

Ghost123NL said:
Also not working.
same steps with supersu is working only
Click to expand...
Click to collapse
maybe the only way to make sure is to wipe everything , did you try with custom kernel?
try to flash rom reboot to recovery, then derp kernel (tested and works on latest beta) , then flash magisk... that worked for me at 1st try.

Flash magisk 14.0 and boot see magical working and then update magisk15.3 via magisk manager application.

Use OOS debloater from the themes and apps section to remove some apps from the system. Then reinstall magisk. Problem solved. We have a lot less space left in the system partition and that's the reason magisk is silently failing to install.

Facing same issue

OOS 5.1.0 Bootloop After Flashing Magisk

As the title says I am unable to boot after flashing Magisk (tried v16 and v15.3). It boots fine without magisk but of course no root and no custom recovery. Any help would be appreciated. Didn't have any problems on the previous stable build.

You need to first flash OOS 5.1 let it boot, then go to fastboot and flash twrp then go to twrp and flash magisk, only way to get root

hello, that's what I did and it worked well

this has happened here since 5.0.4

Try to use lastest blu-spark's TWRP, then flash 5.1 & Magisk without extra boot in the middle.

Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan

ToucanSam said:
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
Click to expand...
Click to collapse
It's not broken. The vendor error message is because it was recently updated to work better with Project treble, which uses a hidden partition for the vendor. You can simply ignore the error and it will work fine. Or if you flash a treble ROM, the error will then go away.

I just got the phone. Format it in recovery.
Flash latest blu spark twrp (v.8.73).
Flash the Oos ob06.
Reboot to system. Set the phone, instal apps from Play.
Reboot to Fastboot.
Reflash recovery.
Reboot to recovery.
Flash Magisk 15.3. Reboot to system. OK.
Updated Magisk with Magisk.

Hi, Can anyone help me. in my oneplus 5T after installing new rom it is working smooth but i can't upgrade to new updates. in recovery mode the files seems to be decrypted and cant find any folders where i copied the updation . instead new files are found and can't access and find any of the folders of my own. this happened after i input the security lock. i wiped the entire data and installed new roms still it seems so. somebody please help me to find a solution for this

Installing Magisk results in bootloop

I'm not new to these things, but this time it seems I'm totally stuck.
What have I done till now?
- unlocked bootloader
- checked Anti-Version -> 4
- followed step 5 in this thread
What have I gained?
- I'm able to boot into TWRP and also to install several ZIPs. But every ZIP I install goes into bootloop. I have to flash the uninstaller-versions and then my phone works totally normal.
- I tried to install Magisk v16.0, v16.3 and v16.7, no success with each of them.
- I patched boot-image through Magisk itself -> also no success, still bootloop
What haven't I done yet?
- used lazyflasher to permanently flash TWRP as recovery
What are my phones creds?
- I'm on MIUI 9.6.3.0
If I'm right I can't flash any MIUI-version below 9.5.19.0 because of Anti 4. How will I be able to install Magisk and have a working phone? I found a thread where several links were included, one of them showing to some kind of ROM-kitchen, where I'd have the choice to create a custom ROM-zip with Magisk included (among other things like wallpapers, ringtones, which ROM-Version) but I can't find the link anymore. Would that be a possibility? Installing a MIUI beta 10?

just try using lazy flasher...

Ok, maybe I identified my problem: I have to booot into TWRP and flash the recovery within TWRP and afterwards I can install Magisk.
Can someone please confirm?

Tischbein said:
Ok, maybe I identified my problem: I have to booot into TWRP and flash the recovery within TWRP and afterwards I can install Magisk.
Can someone please confirm?
Click to expand...
Click to collapse
Yes exactly..

Thanks, worked this way.

Question Bootloop after magisk on 12.5.3.0.RKHEUXM

Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you

suloku said:
Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you
Click to expand...
Click to collapse
Try flashing the older patched boot.img on the new stock firmware.

On the 12.5.3.0 ill patched boot.img from 12.5.1.0 and all right.

Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended

i have the same issue of auto updated and lost my root access.
Which boot.img I should Magish'd to get the root access again?
Currently installing my twrp
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
if Flash Current TWRP fails, go to Backup > Refresh Sizes and try Flash Current TWRP again
Click to expand...
Click to collapse
Currently at the Resizing stage
Edit 1: failed, I have the error bootctrl error that prevent me from installing after resizing.
I have flashed the twrp3.5.2 directly to boot resulting in bootloop and needed to install the Boot.img from the 12.5.1 from the previous bulit
Edit: actually I can ignore that error.
Magisk installed but safety checked failed even I have the "universal safety check module installed "
Also the app thoax isn't working

I'd try removing all magisk modules, installing stock 12.5.3, then using magisk apk to create patched boot.img and flash it with fastboot (fastboot flash boot magisk_boot_patched.img)
Also, maybe try flashing bot boot_a and boot_b? I had a problem were my active boot partition changed and phone became even more broken.

suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
Might wanna also uncheck Automatic system updates in the Developer settings to be safe.

suloku said:
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
There is a setting in the Xiaomi system updater that had by default checked auto-update. That setting need to be disabled/unchecked as well.
Since you have root with Magisk, can also Force stop or debloat the updater app, so the system will not update itself.

suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
I had the same issue on Redmi Note 9 Pro (joyuse). Based on your tip I've removed some modules from `data/adb/modules` and my device is finally booting normally. Thanks!