Magisk 22.0 update killed phone will only boot into fastboot

[Xdpker06]

Is it possible for fastboot to get corrupted somehow? Tried on 2 different computers, same problem. Oneplus 3T gets recognized no problem with the fastboot devices command.

 

[fullydeveloped]

Is it possible for fastboot to get corrupted somehow? Tried on 2 different computers, same problem. Oneplus 3T gets recognized no problem with the fastboot devices command.

You should be able to hold the power + volume down buttons while powering on to boot into recovery mode. Hard to imagine a corrupted boot.img would break that functionality.

 

[Xdpker06]

You should be able to hold the power + volume down buttons while powering on to boot into recovery mode. Hard to imagine a corrupted boot.img would break that functionality.

Yeah, unfortunately it goes right into fastboot. Selecting the recovery option in fastboot also brings it right back into fastboot.

 

[fullydeveloped]

Yeah, unfortunately it goes right into fastboot. Selecting the recovery option in fastboot also brings it right back into fastboot.

It looks like power + volume down actually sends you to (most likely) fastboot, where they expect you to select recovery from there. Try power + volume up, or last option all 3 buttons. Obviously ensure you're holding them the entire time, from before the device powers off until it's fully on.

If OP7 doesn't have the hardware buttons available to enter recovery directly, that's indeed a huge oversight.

In the meantime keep scouring online for people with fastboot connecting to pc issues - there might be a solution out there.

 

[Xdpker06]

It looks like power + volume down actually sends you to (most likely) fastboot, where they expect you to select recovery from there. Try power + volume up, or last option all 3 buttons. Obviously ensure you're holding them the entire time, from before the device powers off until it's fully on.

If OP7 doesn't have the hardware buttons available to enter recovery directly, that's indeed a huge oversight.

In the meantime keep scouring online for people with fastboot connecting to pc issues - there might be a solution out there.

The 7 pro does have hardware buttons, but I tried different combinations, no joy. This morning the phone woke itself up and now I can't even turn it off. Selecting power off in the bootloader will just turn off the phone momentarily before the phone boots right back up into it.

 

[Zincoshine]

Had my phone not failed with the updated 22.0 manager I would have updated magisk itself as well and ended up with a brick. Holy crap I am so thankful to my phone right now. Time to make a backup.

 

[DJBhardwaj]

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices

C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully


C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot recovery
< waiting for any device >

Don't use Minimal ADB, it might be using outdated binaries of platform-tools.

Download the latest binaries from here and launch the command-line inside the working directory.

 

[dynamo1950]

Experienced a similar issue with my Moto G Power XT2041-4 (sofia) after flashing the January update (QPMS30.80-63-6-8-5) a few days ago. Flashing the the Magisk v22.0 patched boot.img causes bootloop. Then flashed Magisk v21.4 patched boot.img results in bootloop as well. Flashing the stock boot.img from this update allows phone to boot normally but, of course, without root.

The phone worked fine with the November update (QPMS30.80-63-6-8-3) running Magisk v22.0. I updated from v21.4 to v22.0 using the Magisk app direct install while on this update.

I suspect there may be some changes in the new boot.img that conflict with the changes Magisk makes when patching it.

Any thoughts???

 

[ineedroot69]

After flashing the January update (QPMS30.80-63-6-8-5) to my Moto G Power XT2041-4 (sofia), Magisk v22.0 patched boot.img from this update causes bootloop showing the blue Android logo indefinitely. Then flashed Magisk v21.4 patched boot.img results in bootloop as well. Flashing the stock boot.img from this update allow phone to boot successfully.

The phone worked fine with the November update (QPMS30.80-63-6-8-3) running Magisk v22.0. I updated from Magisk v21.4 to v22.0 using direct install in the Magisk app successfully last month.

I suspect there may be some changes in the updated boot.img that conflict with the changes Magisk makes when patching the boot.img.

Any thoughts???

Flash stock boot.img

 

[mon0theist]

This happened to me too on my LG V30. I was able to get into TWRP and re-flash my stock ROM zip. Not sure if I should try Magisk v22 again or just stick with 21.x

 

[Aashirg]

@teknomedic Check my post here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84550015

this solution worked for me, thanks very much

 

[naveen_reloaded]

Flash stock boot.img

I did and now twrp doesnt mount slot a or b..
also currently i tried to install twrp latest version (twrp-3.4.0-10-guacamole-) ,it installed on both slot a and slot b as per the messages/logs it showed , but when i boot into recovery its showing "twrp-3.4.0-09-guacamole" , one version older .. and its failing to load both slot a and b , so where is twrp booting from or into ?

Please help.. being without phone for past two days and its killing my day to day activity...

 

[naveen_reloaded]

I extracted the boot.img from havoc OS which my phone was last running. After that twrp fails to load both the slots since they are encrypted(?)

 

[naveen_reloaded]

Even tried to change slot using fastboot and trying to boot - its showing circle animation only.
The boot.img i flashed changed something ? or isnt showing the right path for twrp to boot properly ? twrp only boots into "unmodifid system partition" , from there i cant mount userdata / internal storage

 

[naveen_reloaded]

Solved :

extracted Boot.img was one version older than the one on the phone.. so after flashing correct boot.img through fastboot , i was able to get the phone back on..

Thanks to a kind heart on telegram.

 

[dynamo1950]

Experienced a similar issue with my Moto G Power XT2041-4 (sofia) after flashing the January update (QPMS30.80-63-6-8-5) a few days ago. Flashing the the Magisk v22.0 patched boot.img causes bootloop. Then flashed Magisk v21.4 patched boot.img results in bootloop as well. Flashing the stock boot.img from this update allows phone to boot normally but, of course, without root.

The phone worked fine with the November update (QPMS30.80-63-6-8-3) running Magisk v22.0. I updated from v21.4 to v22.0 using the Magisk app direct install while on this update.

I suspect there may be some changes in the new boot.img that conflict with the changes Magisk makes when patching it.

Any thoughts???

------------------------------------
Anyway, I discovered the solution to my dilemma mentioned above by searching thru forums and Youtube. This may be helpful to those who have flashed the latest ROM update for their phone, then flashed the Magisk patched boot.img and now the phone is unable to boot to the OS.

It appears that the bootloop caused by flashing the 'Magisk_v22.0_Patched_boot.img' was due to installed Magisk modules. This is what worked for me:

1. Boot into TWRP from fastboot.
2. Using the File Manager in TWRP navigate to the '/data/adb/modules/' folder where the Magisk modules reside as folders. Delete all of them.
3. If Magisk is NOT installed then flash 'Magisk_v22.0_Patched_boot.img' as Boot or 'Magisk_v22.0.zip' in TWRP and boot phone to the OS.
4. Open the Magisk app to configure Magisk and install the Magisk modules.
5. Reboot.

The phone is now running the latest ROM, rooted with Magisk v22.0, passes safety net all without erasing user data...

 

[choppedartisan]

Let me add my update. I didn't read all the comments.
I came across the same situation. Now my phone works. It's mediatek. It also has a messed up usb connector pin. I thought my phone was bricked when I flashed Magisk with Twrp. I couldn't boot into recovery. I could only get into fastboot. I am not sure if the reason why I couldn't flash boot.img or recovery.img was because of the wonky usb connector. I even tried SP flash tool, but to no result. By then, it was hard bricked, compared to soft bricked when I flashed Magisk 22. I left my phone on the shelf for a few days.
I had read somewhere that if I open up my phone (in hard brick state) and do some tinkering, I could force it to boot. I went and bought a screwdriver set today. It was wasted money. I tried a last time to boot before opening the phone up. SP Tool detected my phone. I flashed the boot.img and recovery.img. It's fine now. I did some quick research for the uninstall file for Magisk and came across this thread.

 

[naveen_reloaded]

For those who are still searching for an answer .. Here

Latest Magisk messed up my boot. Can I recover without losing everything?

Hi - I tried updating Magisk this morning, and it semi-bricked my OP7P. When I rebooted my phone, I got stuck in FastBoot Mode. I'm running the latest Android 10 OOS. My first step at that point was to do a fastboot boot...

forum.xda-developers.com

REMEMBER ONE THING ..

You should extract the boot.img file from the ROM which was used on the phone before bricking. In my case it was "Havoc-OS-v3.12-20201219-guacamole-Official-GApps"

Download payload extractor
Open your ROM zip file and extract payload.bin file
Copy this file into payload extractor "input" folder and run the extractor. It will extract the boot.img to "output" folder
now use this boot.img to flash . remember to place the boot.img file in android sdk folder or where your adb.exe and fastboot.exe is installed folder.





put phone into fastboot mode. If you cant , try "Tool All in One" tool , which might help you to put phone into fastboot mode/Bootloader , or from twrp reboot into bootloader.

After than connect phone to pc and run following commands. "better to start cmd inside the folder where adb , fastboot and boot.img is residing."
then run the following commands
Thanks to "D E E P" on TG for the following

fastboot flash boot_a boot.img

fastboot flash boot_b boot.img

fastboot reboot

When done properly , this will now boot into your OS and from there dont touch anything . Reboot into TWRP and follow instructions from here https://forum.xda-developers.com/t/...thout-losing-everything.4238147/post-84546903

Many thanks to @
ghost323
D E E P on TWRP TG group.

 

[piekny]

I am a total layman. Please help.
How to flash twrp.zip after booting the phone through

fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot

from the post above

Put fone in fastboot mode ?
What commands?

fastboot flash recovery xxx.img
and then
fastboot boot xxx.img
fastboot reboot ????


Maybe other commands. I'm totally lost. I will be grateful for any explanation.

Maybe this is good:

WARNING Magisk v22 soft bricks Oneplus 6T !!!! · Issue #3924 · topjohnwu/Magisk

Hey guys. Was running magisk over years without major issue. Sadly v22 bricked my Oneplus 6T phone and others: https://forum.xda-developers.com/t/rom-stock-fastboot-op6t-stock-fastboot-roms-for-one...

github.com

 

[mon0theist]

Have never had an issue went to update to latest Magisk app, followed directions and restored it first, everything seemed fine, then went to flash Magisk itself from the app (Direct install) like always, didn't seem to do anything, checked the Magisk log, said unknown image type and that it failed, rebooted phone, phone will now only reboot into fastboot mode. Not the quality I've been accustomed to and certainly does not belong in the stable branch. Now can someone please tell me what I should do to fix this hot mess?

Edit: Fixed boot with backup boot image. Included log of attempted but allegedly failed update.

Hey OP see my thread here:

PSA: Magisk v22 seems to soft brick, stuck in Fastboot

Magisk seems to have made major changes with the newest v22 release, and I discovered this morning after installing it that upon reboot, you get stuck in the Fastboot screen. Looks like the only way to fix is to re-flash Stock from LGUP and...

forum.xda-developers.com