I'm very new to magisk and I've had my 8 pro rooted with magisk for about a week now. A few days ago I updated my phone to the newest firmware and used the "install to inactive slot after ota" option in magisk like I seen in Max Lee's youtube video. And it worked perfectly, last night I seen there was a new update for the magisk manager and magisk version. So I updated both of them and I selected install to inactive slot again. Which I know that's probably where I screwed up because I did not update my phones firmware, just magisk. Is there any way to rollback a magisk version from my pc using fastboot or something? Because I can access the bootloader fine, I just cannot boot up completely. Any advice would greatly help.
Same issue here, just updated Magisk and now in a boot loop
Related
Is someone had more luck with Magisk than me ?? I have a rooted LON-L29C432B225. Was trying Magisk 13.3 but without luck. Phone restarts automatically during magisk installation through twrp.
I have finaly made it Magisk is working without problems on Mate 9 Pro (LON-L29C432B225).
1. Install latest twrp recovery - https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
2. Unroot rom, easy way i to download boot.img and flash by fastboot flash boot boot.img (https://www.dropbox.com/s/sj5su702r8omp2u/BOOT.img?dl=0)
3. Thanks to @ante0 (https://forum.xda-developers.com/member.php?u=2247733), he made a modified magisk package - https://mega.nz/#!QhMmRDgC!c3UqYIoaGtsekmJbWoP5x90spHbXVhircmmA_68s3pY
4. Flash magisk in twrp
5. After reboot you receive info about magisk update to 13.3. Mark in magisk manager settings "keep force encryption" and allow to update.
6. After next reboot you shuld have working magisk and SafetyNet status green
I hope it will help someone
On AL00 mate 9, followed the same procedure except downloading the boot.img as restored by huawei eRecovery, only unlocked the bootloader and didn't do anything else. Can install 13.2 modified version but safetynet fail, update to 13.3 with keep force encryption then bootloop. Checked the magisk log nothing seems wrong when can boot. Root works fine. Any help? Thanks
Guys any updates on Magisk v14 with xposed on our phone? fw B225
Hello friends, I am trying to install Magisk on a Galaxy s4 gt-i9515, non-rooted, with TWRP recovery device.
I tried both methods described in the official thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Both tries failed. I will now explain in more detail what I've done.
Before, note that I have a TWRP recovery of the state before flashing any zips/boot.img s, so I am constantly going back to the previous state which passes safetynet.
First try:
I simply took the magisk-v14.zip file and installed through TWRP. The installation had no errors and in the end TWRP claimed "success". TWRP asked me to reboot now.
I clicked on "Reboot", and then TWRP told that "My device is currently not rooted" and asked if I want to install root or reboot anyways. I rebooted anyways (I didn't let TWRP install his own root).
When the device boot up, I got into magisk manager, but sadly it was written that I am not rooted, and I don't have a magisk installed. Now, it also failed to pass safetynet.
At this point I used my Backup and got back to the state which I could pass safetynet (I've checked it again to make sure).
Second try:
I got the boot.img of the stock firmware I am currently using (I recently flashed this firmware, so it has to be the right boot.img).
I got into Magisk Manager and patched the boot.img. Magisk patched it into a file called "patched_boot.img.tar".
I got into download mode on my device, and flashed the .tar file via ODIN (AP option, ODIN version 3.12.3).
The device rebooted after the installation was "complete" according to ODIN: <OSM> All threads completed. (succeed 1 / failed 0).
When the device booted up, I entered the Magisk manager, and still, no root + no magisk installed. This time tho, it passed SN.
I used my backup again.
Now I am stuck. I really don't know what can I try anymore. Please suggest me ideas.
Up. I still need answers.
i have mnanaged to install latest stable version of magisk using latest twrp 3.1.1.0, and root management is in function. however, i cannot install any magisk module, tested xposed api21 but it does not install, also greenify4magisk still nothing to be noticed, unfortunately as there is yet no response i suppose its a lost cause, well lets just root manually supersu or things like that.
hi, Samsung S4 i 9505 I have not solved with Magisk and I don't even try "patched_boot.img.tar" the problem in it is apk and not the file it TWRP starts I remember apk EdXposed 2 years ago there were failures I thought about installing stock firmware/Rom with Frja Tool we talk about android 10/11 is android 5.0.1 I think there is only one way is SuperSu this root does not pose problems there is a saying: the more cooks around a dish, the more they ruin it"
I was able to install Magisk v24.3 today on my Galaxy S4 Mini LTE (GT-I9195) using partially the "Patching Images" method and TWRP 3.2.3. I had Magisk v23 installed but since a couple of weeks ago it kept crashing. So, I did the big mistake of uninstalling it to update to the latest version. It costed me half a day around this.
I could not flash zips in TWRP recovery (it always failed with Updater process ended with ERROR:1)
1 - Get a copy of the boot.img (for this step I had to find the installation file of my ROM. I did not know for sure which was it since it was installed 2 years ago. I have an AOPK based ROM and all the files from their website are not available anymore. All I could find was an older one on androidfilehost "aokp_serranoltexx_pie_unofficial_2020-01-18_1053.zip". Uncompress this zip to get the boot.img file.
2 - Copy the boot.img to your device filesystem.
3 - Power on the phone with "vol down+home+power" to enter TWRP, choose Install, Image, and flash boot.img, reboot
4 - Download and install the latest Magisk v24.3 apk
5 - Press the Install button in Magisk app (this means pressing the second “Install”, the one on front of App.)
6 - It should ask you to choose “Select and Patch a File”. Search and select the boot.img
7 - If all goes well, it should create a file named magisk_patched_[random_strings].img
8 - Power on the phone with "vol down+home+power" to enter TWRP, choose Install, Image, and flash magisk_patched_[random_strings].img, reboot
9 - Reboot and confirm in Magisk app if it says “Installed 24.3 (24300)“.
Now I get a warning "Your device needs additional setup for magisk to work properly... reboot" when entering Magisk, but it seems to work fine.
I have a bottle of champagne saved for the day when windows laptops are miniaturized and android is discontinued from the market. Bootloaders, recoveries, ramdisk, getting root, knox, odin, oem unlockings, CSCs, APs, customs kernels, adb, vbmeta, adoptable storage, se policies, fastboot modes, download modes... damn. They couldn't make it more complex if they tried.
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?
hi there,
my redmi just updated automatically over night to the new rom V10.2.1.0.MBEMIXM.
it is rooted and i had magisk v18.0(18000) running with manager v6.1.0(165)
(i did the patched stock boot image method with fastload).
i thought ota updates are not possible, but anyway..
funny thing is, magisk also got new updates over night.
magisk manager v7.0.0 and magisk v18.1(18100)
now my question is, what is the right way to reinstall magisk?
can i just again patch the stock boot image from the previous rom V10.1.1.0.MBEMIFI with the new magisk v18.1(18100) and flash this, because there is no fastboot image for the new V10.2.1.0.MBEMIXM.
or should i try to dump boot image with adb, so i can patch it?
I've recently installed a custom rom(finally) on my redmi note 7, and after around a week I decided to install magisk and root it aswell... When i first installed magisk through twrp it booted successfully into android, and after trying to install a module and reboot my phone it got into a bootloop, is there any way to solve it?
aviv903 said:
I've recently installed a custom rom(finally) on my redmi note 7, and after around a week I decided to install magisk and root it aswell... When i first installed magisk through twrp it booted successfully into android, and after trying to install a module and reboot my phone it got into a bootloop, is there any way to solve it?
Click to expand...
Click to collapse
Maybe you already found a solution. But you can try going into twrp and flashing magisk uninstaller zip
i have faced this same problem and i did unroot through twrp so the problem solved . then recently i flashed magisk again but iam facing that problem again,.. I can't boot into system !
komiker said:
i have faced this same problem and i did unroot through twrp so the problem solved . then recently i flashed magisk again but iam facing that problem again,.. I can't boot into system !
Click to expand...
Click to collapse
I too had the same problem a few days ago. I had tried to update magisk but after flashing the latest version via twrp, the phone got stuck on bootloop. I uninstalled magisk using the uninstaller zip file then flashed the old version I had before (v19.3) and everything was back to normal.