Its been a while since i tried last but have been wanting to update magisk, currently on 20.4(still). But when i direct update through the magisk app and reboot it throws me into a bootloop. The only way im able to fix it is by flashing magisk 20.4 again via TWRP. Im on A6013 Fajita with OOS 10.3.4. only other thing i have installed that i think might be conflicting is edxposed 0.5.2.2 4683 yahfa. Recently tried flashing orig boot.img and patching via magisk and flashing but gets a bootloop and have to flash a backed up custom kernel to fix. Also im currently booted in slot b cause slot a starts to boot for literally half a second and then reboots back to slot b. I've tried to get some kind of log back to see where it hangs but its too soon for adb logcat and when i am able to keep it in the inactive slot a, it brings me to a screen that looks like the "bootloader unlocked" screen but says "device is corrupt" blah blah blah. If anybody knows a way i can get that 'half a second' log that would be great too, but when i can keep it on slot a before it boots back to slot b, the most i get is fastboot. Thank you in advance!
Related
I dont understand why I got this bootloop, can someone help me figuring it out???
To update to Oreo, I followed this guide: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
I installed the second December security patch using the exact same steps and I didnt had any problems at all. I dont understand why this time i got a bootloop, what I did wrong?
I restored the image in Magisk before updating to Oreo, then when the step 2 of the installation was beginning, I installed Magisk to the second slot (as instructed in the guide). I rebooted the phone but i entered in an infinite bootloop.... why?
I had the latest magisk apk and version... now I am flashing via fastboot and MI flash the latest fastboot image (Nougat, second december update), and ITS taking SO long, already 2300 seconds have passed and the progress bar is already full since a while ago, but it still has "flashing" status. Does it take so long to actually flash via MI flash? (this is my first time)
Thanks
I had the same problem. I am not sure why the Magisk instructions did not work. I fixed the bootloop by flashing the stock boot image from Oreo OPR1.170623.026.7.12.29 available here (via). Use the batch file or run the commands below.
Code:
fastboot flash boot_a boot-stock.img
Code:
fastboot flash boot_b boot-image.img
The magisk update work for me for 3 prevoius security patch update, but didn't work on oreo .
---------- Post added at 01:07 PM ---------- Previous post was at 12:59 PM ----------
dbgt said:
I dont understand why I got this bootloop, can someone help me figuring it out???
To update to Oreo, I followed this guide: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
I installed the second December security patch using the exact same steps and I didnt had any problems at all. I dont understand why this time i got a bootloop, what I did wrong?
I restored the image in Magisk before updating to Oreo, then when the step 2 of the installation was beginning, I installed Magisk to the second slot (as instructed in the guide). I rebooted the phone but i entered in an infinite bootloop.... why?
I had the latest magisk apk and version... now I am flashing via fastboot and MI flash the latest fastboot image (Nougat, second december update), and ITS taking SO long, already 2300 seconds have passed and the progress bar is already full since a while ago, but it still has "flashing" status. Does it take so long to actually flash via MI flash? (this is my first time)
Thanks
Click to expand...
Click to collapse
I got the same problem with MiFlash too. It say "$fastboot -s e1696a51 set_active a " on the status. I just reboot the phone using "fastboot reboot" and it start normally. If didnt work, you can try change to clean all without locking bootloader
I have followed these instructions but haven't rebooted yet, so I have the notification prompting me to reboot. How can I install Oreo now without losing data? Because when I next reboot I'll get stuck in this bootloop. MiFlash tool maybe? EDIT: completely unroot, restore stock boot images then reboot?
Thinking that there are some modules that are installed that aren't oreo compatible. I would say remove all modules within Magisk first, then do the Oreo update. I wasn't rooted but I guess I have some incompatible Magisk modules as when I try to load a patched boot.img (with magisk already there), I get stuck at the Android One loading and never get to the OS.
The problem here may be the Magisk module adding EIS & Camera2API is not updated to work with Oreo, users in that thread are reporting not being able to boot and saying this module is the problem.
I only had 1 module installed.
I fastboot flashed the nougat second december update, installed root again, all my apps, and i will better wait to update to Oreo.
In case I screw it up again, how can i do a full backup of my device now that is stable? with TWRP? will that affect the partitions or affect the OTAs?
After updating to the latest software I found that with the exception of the first time I tried it which weirdly enough worked, I can't for the life of me successfully boot after rooting.
I rooted once and had to uninstall magisk because of a conflicting module but now no matter what I try I always get stuck on essential's splash screen.
Does anyone else have this problem? If I flash the stock boot image I can boot just fine.
have you try flashing update, then boot image then magisk consecutively before any reboot? I'm out of the country at the moment w/o access to my PC, and I can't even risk a soft brick while traveling.
Are you getting as far as installing magisk again? cause from what you've written it sounds like it is working but the module that caused the original issue is still there. you can remove magisk by flashing the stock boot image but the magisk image with all installed modules is still there.
If that is the case then there are a few tool out there to mount the magisk image and remove the module.
I tried a few when I had a similar issue and the only one that worked was this one.
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
what you would need to do is flash twrp. boot into recovery. (decryption never works for me so would recomend either sideload or adb push to /data/media)
flash the stock boot image back.
then reinstall magisk
flash the magisk recovery manager
once loaded go to the advanced section of twrp select terminal and type mm and follow the on screen instruction to remove the afflicted module then reboot and you should be sorted.
Although that being said if that isn't the issue you're having then can you explain how far you get with trying to reinstall and whats going wrong.
Ibanez33 said:
Are you getting as far as installing magisk again? cause from what you've written it sounds like it is working but the module that caused the original issue is still there. you can remove magisk by flashing the stock boot image but the magisk image with all installed modules is still there.
If that is the case then there are a few tool out there to mount the magisk image and remove the module.
I tried a few when I had a similar issue and the only one that worked was this one.
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
what you would need to do is flash twrp. boot into recovery. (decryption never works for me so would recomend either sideload or adb push to /data/media)
flash the stock boot image back.
then reinstall magisk
flash the magisk recovery manager
once loaded go to the advanced section of twrp select terminal and type mm and follow the on screen instruction to remove the afflicted module then reboot and you should be sorted.
Although that being said if that isn't the issue you're having then can you explain how far you get with trying to reinstall and whats going wrong.
Click to expand...
Click to collapse
I can't believe I hadn't thought of that. The conflicting modules were still there and I just had to remove them. Thanks so much man, I was about to wipe my phone out of frustration!
I've messed everything up and now I'm devastated!
My S8 stucks at the very first screen (where it says: SAMSUNG GALAXY S8 - powered by android). It doesn't boot further this very specific screen. I have tried to update Magisk and Magisk Manager but only Magisk Manager seems to get updated successfully while the app suddenly says that the latest version of Magisk Manager required Magisk V19.XX hence I've tried to install it via TWRP. According to log screen, I've managed to install magisk via TWRP but after booting up, I opened Magisk Manager where it now says that Magisk isn't installed. I therefore boot into TWRP and tried to fix it since some apps of mine that required root access wasn't working anymore. So, I thought I must have lost root access. I once again boot into recovery, I uninstalled magisk and install an older version of magisk and magisk manager and also the no_verity patch. After that my Galaxy S8 won't boot up. It just stucks at the very first screen. My S8 (international version) is still on Nougat stock samsung firmware and I can enter TWRP but the phone remains freeze and stubbornly refused to boot up.
I'm quite devastated and I hope you guys can help me fix this issue!
Thank you!
Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...
tosmaniac said:
Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...
Click to expand...
Click to collapse
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!
cocolish said:
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Have you tried just flashing stock rom only to see if it boots up. You may have to do a clean install.
Problem sounds like you haven't decrypted phone and flashed no verity zip file.
You won't need to flash a custom rom to fix this.
As for magisk have a look through this very helpful guide for installs and troubleshooting.
https://www.didgeridoohan.com/magisk/HomePage
I've managed to solve this issue by myself. But still, thank you so much! It's the thought that counts ? And yes, I've figured out that I haven't decrypt my S8. But everything is absolutely fine now and I feel extremely relieved. It took me 1 day to fix this major issue and I've encountered lots of difficulties while trying to fix this like bootloops, system won't boot up and managed to stuck at the very first booting screen again and the phone boot past the first booting screen and stucks at the second booting screen, and also bootloader error and stuffs like where realization hit me that I can't restore my nandroid backup while still on Nougat because after restoring it won't boot up. I therefore managed to flash Android 9 and twrp. My S8 is now on Android Pie with custom recovery and rooted (via Magisk).
Anyone been able to get rooted with Magisk yet?
Flashing the zip with TWRP just causes the system to continually kick me into the bootloader.
Tried flashing the old vmbeta_skip.img like back with 8.2.3 doesn't help either.
Seems that It also does not want to retain TWRP in the recovery partition. After a while, it reverts to the stock Droid Mascot with "No Command" displayed on screen. Have to keep reflashing it through fastboot.
Thank you for sharing your experience, I have same issue and vmbeta_skip.img doesn't help either.
I install microg magisk module on LineageOS 17 but I encountered black screen!
Also I install official microG release: https://download.lineage.microg.org/mdarcy/lineage-17.1-20220110-microG-mdarcy.zip but I encountered black screen too!
LazorBlind said:
Anyone been able to get rooted with Magisk yet?
Flashing the zip with TWRP just causes the system to continually kick me into the bootloader.
Tried flashing the old vmbeta_skip.img like back with 8.2.3 doesn't help either.
Seems that It also does not want to retain TWRP in the recovery partition. After a while, it reverts to the stock Droid Mascot with "No Command" displayed on screen. Have to keep reflashing it through fastboot.
Click to expand...
Click to collapse
by this post https://forum.xda-developers.com/goto/post?id=86181925 the @masset12 could do it
Its been a while since i tried last but have been wanting to update magisk, currently on 20.4(still). But when i direct update through the magisk app and reboot it throws me into a bootloop. The only way im able to fix it is by flashing magisk 20.4 again via TWRP. Im on A6013 Fajita with OOS 10.3.4. only other thing i have installed that i think might be conflicting is edxposed 0.5.2.2 4683 yahfa. Recently tried flashing orig boot.img and patching via magisk and flashing but gets a bootloop and have to flash a backed up custom kernel to fix. Also im currently booted in slot b cause slot a starts to boot for literally half a second and then reboots back to slot b. I've tried to get some kind of log back to see where it hangs but its too soon for adb logcat and when i am able to keep it in the inactive slot a, it brings me to a screen that looks like the "bootloader unlocked" screen but says "device is corrupt" blah blah blah. If anybody knows a way i can get that 'half a second' log that would be great too, but when i can keep it on slot a before it boots back to slot b, the most i get is fastboot. Thank you in advance!