Database Develop

Can't get past repacking boot image

My first time rooting my phone, and I'm trying to get magisk to work. But whenever I try to update from the Magisk Manager, I get the following:
- Detecting target image
- Target image: /dev/blocl/mmcblk0p15
- Device platform: armeabi-v7a
- Extracting files
- Unpacking boot image
- Checking ramdisk status
- Patching ramdisk
- Repacking boot image
! Unable to repack boot image !
Failed!
! Installation failed
I have no idea where I've gone wrong. If its any use, I use a Samsung Galaxy S5, with Magisk Version 16.
Thanks in advance.

jacobjbarker said:
My first time rooting my phone, and I'm trying to get magisk to work. But whenever I try to update from the Magisk Manager, I get the following:
- Detecting target image
- Target image: /dev/blocl/mmcblk0p15
- Device platform: armeabi-v7a
- Extracting files
- Unpacking boot image
- Checking ramdisk status
- Patching ramdisk
- Repacking boot image
! Unable to repack boot image !
Failed!
! Installation failed
I have no idea where I've gone wrong. If its any use, I use a Samsung Galaxy S5, with Magisk Version 16.
Thanks in advance.
Click to expand...
Click to collapse
Try with 16.7 or past version

Magisk 20.1 Canary, Android 10, Pixel 3: Unsupported/Unknown image format on boot img

Google helpfully updated my Pixel 3 (with Magisk) OTA to Android 10.
I've followed the instructions to move to the Canary/Canary Debug channel, updated Magisk Manager, uploaded to the phone both the OTA and recovery images, but Magisk is unable to patch:
Code:
- Device platform: arm64-v8a
- Copying image to cache
1618+0 records in
1618+0 records out
1656832 bytes (1.5 M) copied, 0.005972 s, 265 M/s
1085+1 records in
1085+1 records out
1111628 bytes (1.0 M) copied, 0.005266 s, 201 M/s
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
I've tried with these factory images:
blueline-ota-qp1a.191005.007-e5bf373b.zip
blueline-qp1a.191005.007-factory-c36610c6.zip
Extracting boot.img from either of those images, uploading to the phone "Download" directory and attempting to patch isn't possible. Magisk Manager does not show boot.img at all in the file selection list, even though it is there, verified by both Astro file manager as well as adb shell and PC file sharing.
Suggestion what to try next?

I gave it a shot and downloaded the factory image to test. Had no issues patching the boot image file with Magisk Canary 20001 on my OP3T using Manager 245. Something's obviously wrong (and you're not the only one reporting this), but I've no idea what...

Didgeridoohan said:
I gave it a shot and downloaded the factory image to test. Had no issues patching the boot image file with Magisk Canary 20001 on my OP3T using Manager 245. Something's obviously wrong (and you're not the only one reporting this), but I've no idea what...
Click to expand...
Click to collapse
Hi, I flashed coltos5.1 on my op3t yesterday to give a try with Android 10 but I'm unable to install magisk 20 (downloaded from Magisk Manager 7.3.5). I tried from TWRP and also by patching the boot file (extracted from the ROM). How have you been able to flash it ? Which ROM are you using ?

coolrick said:
Hi, I flashed coltos5.1 on my op3t yesterday to give a try with Android 10 but I'm unable to install magisk 20 (downloaded from Magisk Manager 7.3.5). I tried from TWRP and also by patching the boot file (extracted from the ROM). How have you been able to flash it ? Which ROM are you using ?
Click to expand...
Click to collapse
I have not yet tried 10 on my 3T. I merely tested patching the Pixel 3 Android 10 boot image, and that worked without problem. On my device, I have to add...
Right now I downloaded ColtOS and tried patching the boot image. That worked without issue (can't test flashing it though, of course), so what problems do you have?

Didgeridoohan said:
I have not yet tried 10 on my 3T. I merely tested patching the Pixel 3 Android 10 boot image, and that worked without problem. On my device, I have to add...
Right now I downloaded ColtOS and tried patching the boot image. That worked without issue (can't test flashing it though, of course), so what problems do you have?
Click to expand...
Click to collapse
Thanks for the quick reply - Patching was not a problem but then it doesn't boot. I got the oneplus logo but it doesn't go further (no bootloop, I stays on the logo and doesn't do anything).

coolrick said:
Thanks for the quick reply - Patching was not a problem but then it doesn't boot. I got the oneplus logo but it doesn't go further (no bootloop, I stays on the logo and doesn't do anything).
Click to expand...
Click to collapse
Getting off-topic... Replied here: https://forum.xda-developers.com/ap...systemless-t3432382/post80522263#post80522263

coolrick said:
Thanks for the quick reply - Patching was not a problem but then it doesn't boot. I got the oneplus logo but it doesn't go further (no bootloop, I stays on the logo and doesn't do anything).
Click to expand...
Click to collapse
I just refollow everything from the magisk guide (https://topjohnwu.github.io/Magisk/install.html#boot-image-patching) and retry the Boot Image Patching. This time it was OK - My OP3T endly boot up fine. Anyway, thanks for your help.

Magisk, TWRP and Android 10
coolrick said:
Hi, I flashed coltos5.1 on my op3t yesterday to give a try with Android 10 but I'm unable to install magisk 20 (downloaded from Magisk Manager 7.3.5). I tried from TWRP and also by patching the boot file (extracted from the ROM). How have you been able to flash it ? Which ROM are you using ?
Click to expand...
Click to collapse
I think Magisk and TWRP don't support Android 10 quit well. I got the same error message.

Magisk 20.4 failed to install through TWRP 3.3.1-0 on Samsung Galaxy S7

My phone has the TWRP custom recovery and ive attempted to install magisk on my Samsung Galaxy S7 device but it came up with an error and failed to install. I cant send links yet but this is what it said:
Installing zip file '/sdcard/Magisk-v20.4.zip'
Checking for Digest file...
***********************
Magisk 20,l.4 Installer
***********************
- Mounting /system
- Target image: /dev/block/sda5
- Device platform: arm64
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by unsupported programs
! Please restore back to stock boot image
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v20.4.zip'
Updating partition details...
...done
Anyone got any ideas on how to help? I am pretty new to this so its likely ive missed a step somewhere but this is my 3rd time trying and ive made sure ive followed every step

https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs

U must flash the zip ". no-verity-opt-encrypt-6.0.zip" and then flash zip magisk

Magisk v21 on android 11: bootloop at bootloader when flashing magisk patched img

I've been waited for Magisk v21 released by John Wu this morning, but I ran into some problems
What I've done
- download stock image file from Google official site
- follow the instruction given by John Wu at GitHub wiki
- run command
Code:
adb shell magisk --remove-modules
- when i flash the patched boot.img file, it stuck on the *G logo* with progress bar under it.
- After a certain period of time, it comes back to bootloader with a prompt saying: "no valid slot to boot".
What i've tried:
- redo all processes, no working
- switch active slot to both a & b, none working
- re-patch the stock boot.img file use different Magisk Manager version. The ones i tried: v8.0.0-Beta(offers Magisk v21), v8.0.0-Stable(offers Magisk v20.4), Canary version (offers Magisk Canary who claims to support android 11)
- change the command
HTML:
fastboot flash boot ***.img
to
HTML:
fastboot flash boot_a ***.img
&
HTML:
fastboot flash boot_b ***.img
then run
HTML:
fastboot reboot
. same result as said before
Basic info:
- Device: Pixel 3 (blueline), android 11 (build number RP1A.200720.009), latest android security update & Google play system update.
- Magisk: Magisk Manager v8.0.0 (released hours ago), Magisk v21 is suppose to be installed

Is patched boot.img filesize ~32 or ~64mb?

I ran into the same problem. My phone is a Pixel 2 XL running Android 11. However, I was not patient enough to wait for the "no valid slot to boot" message. After waiting for 5-10 minutes, I did a factory reset.
I followed the installation instruction that were posted by John Wu.. (As a new user, I am not allowed to post an outside link)
The displayed Magisk installation messages do not suggest a problem:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
- Checking ram disk status
- Stock boot image detected
- Patching ram disk
- Repacking boot image
***************************
Output file is written to
/storage/emulated/0/Download/magisk_patched.img
***************************
- All Done!
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version. For instance, with Magisk 20.4 and Android 10, the file sizes of boot.img and magisk_patched.img were 41943040 and 25747456, respectively. Thus, the patched file was smaller than the original.

done

dmk16 said:
Is patched boot.img filesize ~32 or ~64mb?
Click to expand...
Click to collapse
the stock & patched boot.img are both 65535KB large, which is weird and also mentioned by @red stapler

red stapler said:
I ran into the same problem. My phone is a Pixel 2 XL running Android 11. However, I was not patient enough to wait for the "no valid slot to boot" message. After waiting for 5-10 minutes, I did a factory reset.
I followed the installation instruction that were posted by John Wu.. (As a new user, I am not allowed to post an outside link)
The displayed Magisk installation messages do not suggest a problem:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
- Checking ram disk status
- Stock boot image detected
- Patching ram disk
- Repacking boot image
***************************
Output file is written to
/storage/emulated/0/Download/magisk_patched.img
***************************
- All Done!
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version. For instance, with Magisk 20.4 and Android 10, the file sizes of boot.img and magisk_patched.img were 41943040 and 25747456, respectively. Thus, the patched file was smaller than the original.
Click to expand...
Click to collapse
Seems like we're in the same boat here lol, is this enough proof for a legit bug issue to John?

red stapler said:
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version.
Click to expand...
Click to collapse
DaddyTony said:
the stock & patched boot.img are both 65535KB large, which is weird and also mentioned by @red stapler
Click to expand...
Click to collapse
The patched boot image is supposed to be the same size as the original now.
From the v21 changelog:
[MagiskBoot] Pad boot images to original size with zeros
Click to expand...
Click to collapse

nogaff said:
The patched boot image is supposed to be the same size as the original now.
From the v21 changelog:
Click to expand...
Click to collapse
Glad to hear, hope this indicates patch is successfully done?

Why not:
adb reboot bootloader
fastboot boot twrp-xxxx.img
adb push magisk-xxxx.zip /tmp
adb shell twrp install /tmp/magisk-xxxx.zip
adb reboot system
Let the magisk zip update script figure everything out...
Its what i do on Pixel 2 XL, works every time...10/11

So far, what we've seen that is causing issues with Android 11 and Magisk is usually either having incompatible modules installed (the brand new Safe Mode should take care of that, see the FAQ for details), or having TWRP installed to your device (it'll cause a conflict and the device won't boot, install the stock recovery and only use TWRP booted).

I forgot to mention that I didn't install or use a custom recovery, such as TWRP. Using the stock recovery.

73sydney said:
Why not:
adb reboot bootloader
fastboot boot twrp-xxxx.img
adb push magisk-xxxx.zip /tmp
adb shell twrp install /tmp/magisk-xxxx.zip
adb reboot system
Let the magisk zip update script figure everything out...
Its what i do on Pixel 2 XL, works every time...10/11
Click to expand...
Click to collapse
Sorry but i don't think Pixel 3 have Teamwin (TWRP) support of android 11?

Didgeridoohan said:
So far, what we've seen that is causing issues with Android 11 and Magisk is usually either having incompatible modules installed (the brand new Safe Mode should take care of that, see the FAQ for details), or having TWRP installed to your device (it'll cause a conflict and the device won't boot, install the stock recovery and only use TWRP booted).
Click to expand...
Click to collapse
I forgot to mention that i run this command before install magisk patched boot.img
Code:
adb pm shell magisk --remove-modules
I didn't have TWRP installed on my device, don't seem to have TWRP for Pixel 3 on android 11.

DaddyTony said:
Sorry but i don't think Pixel 3 have Teamwin (TWRP) support of android 11?
Click to expand...
Click to collapse
Theres no TWRP support of my Pixel 2 XL either, but it works
We just dont install it, we fastboot to it

73sydney said:
Theres no TWRP support of my Pixel 2 XL either, but it works
We just dont install it, we fastboot to it
Click to expand...
Click to collapse
Just tried boot into TWRP img, failed. It just says:
Code:
FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
Googled it & find out TWRP's a deprecated/no longer recommended way to install Magisk. And according to John Wu's installation instruction, it is no longer supported in modern models.
Due to this reason, we no longer recommend installing Magisk through custom recoveries on modern devices.
Click to expand...
Click to collapse
BTW he also said the "patch image" method is guaranteed to work 100% lol, should we let him know hhh
--------------------
edit:
Just find out Pixel 3 (blueline) has **NO** official support of TWRP v3.4+, but Pixel 3 XL (crosshatch) has it. How ironic.
and I wonder if TWRP v3.4+ support android 11?

DaddyTony said:
Just tried boot into TWRP img, failed. It just says:
Code:
FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
Googled it & find out TWRP's a deprecated/no longer recommended way to install Magisk. And according to John Wu's installation instruction, it is no longer supported in modern models.
BTW he also says the "patch image" method is guaranteed to work 100% lol, should we let him know hhh
Click to expand...
Click to collapse
Hmmm, disappointing
Ive literally tried the image patch method once, a lot of faffing about, I always use the TWRP method, easy peasy at least for older device
....we no longer recommend installing Magisk through custom recoveries on modern devices. The custom recovery installation method exists mostly for legacy support.
Download the Magisk installer zip
Reboot to custom recovery
Flash the zip and reboot
Check whether Magisk Manager is installed. If it isn’t installed automatically, manually install the APK.
Click to expand...
Click to collapse
Guess ill be happy to remain a legacy device user

This saved my day:
Code:
fastboot --set-active=b
You might need to use "a" instead.
In my case the kernel was loaded and started and Android startup was hanging.
I guess we have to wait until this is fixed.
Edit: Pixel 3a XL, latest Android 11

Hey all, i have a pixel 2 XL and I'm also stuck in bootloop. However i can't find how to do a factory reset. Could you help me?

polyxn said:
Hey all, i have a pixel 2 XL and I'm also stuck in bootloop. However i can't find how to do a factory reset. Could you help me?
Click to expand...
Click to collapse
Which version of Android?
Do you have TWRP installed?
If you do people have been posting that going to Advanced, then tapping Fix Bootloop may work
Otherwise find the boot image of the ROM you have installed, and flash that to the device
If youre on Android 11 on the Pixel, as i found out myself via bootloop, do NOT install TWRP, just fastboot to it to flash zips

M66B said:
This saved my day:
Code:
fastboot --set-active=b
You might need to use "a" instead.
In my case the kernel was loaded and started and Android startup was hanging.
I guess we have to wait until this is fixed.
Edit: Pixel 3a XL, latest Android 11
Click to expand...
Click to collapse
I used this command (and tried to boot in slot a), the patched img still won't boot.
Did you managed to flash Magisk with patched boot file?

Pixel 5 w/ Jan Update - Flash of patched boot.img = loop

Hi all,
I seem to be struggling with my usual process of getting root on my Pixel 5.
I installed the latest Canary build of the Magisk Manager and patched my base boot.img and then flashed it and the phones goes into an infinite loop. Only way to get out of it is to flash-all.bat (w/out the -w). Any ideas on why this process, which I've used even on my previous P2XL, is no longer working?
When I open the manager, it says my installed version is 8.0.4 (4770) and the latest version is 6d88d8ad (4770) (15) but I can't update.

I have the January release and the same magisk version, and my device boots fine. What steps did you do to patch the boot.img file and how did you flash the patched magisk_patched.img file?

Amd4life said:
I have the January release and the same magisk version, and my device boots fine. What steps did you do to patch the boot.img file and how did you flash the patched magisk_patched.img file?
Click to expand...
Click to collapse
This is the process I follow each month/followed for this update:
Download and extract FW
Edit flash-all.bat to remove the -w
Run flash-all.bat while at bootloader screen
Copy \redfin-rq1a.210105.003\boot.img to device
Open Magisk Manager Canary (latest) and click on "Install"
Select "Select and Patch a File"
Copy \download\magisk_patched_0eKAS.img to platform-tools folder on PC
At bootloader screen, run: fastboot flash boot magisk_patched_0eKAS.img
Reboot
I've been using that process for months, going back to my Pixel 2 XL and used that process (with different .img names obviously) last month even for the December update on this here Pixel 5.
Only way to get out of the loop is to re-run step 3.

IlyaKol said:
Hi all,
I seem to be struggling with my usual process of getting root on my Pixel 5.
I installed the latest Canary build of the Magisk Manager and patched my base boot.img and then flashed it and the phones goes into an infinite loop. Only way to get out of it is to flash-all.bat (w/out the -w). Any ideas on why this process, which I've used even on my previous P2XL, is no longer working?
When I open the manager, it says my installed version is 8.0.4 (4770) and the latest version is 6d88d8ad (4770) (15) but I can't update.
Click to expand...
Click to collapse
Have you tried using Magisk latest beta? I ended up using beta for January for whatever reason and had no issue. I'd upload my boot.img but I'm a Verizon user and not sure if it'll work for you. "magisk_patched_dnuD3.img"
Magisk v21.2 (21200)
Magisk Manager v8.0.4 (4768) (15)

andybones said:
Have you tried using Magisk latest beta? I ended up using beta for January for whatever reason and had no issue. I'd upload my boot.img but I'm a Verizon user and not sure if it'll work for you. "magisk_patched_dnuD3.img"
Magisk v21.2 (21200)
Magisk Manager v8.0.4 (4768) (15)
Click to expand...
Click to collapse
Let me give that a whirl in a bit.

IlyaKol said:
Let me give that a whirl in a bit.
Click to expand...
Click to collapse
andybones said:
Have you tried using Magisk latest beta? I ended up using beta for January for whatever reason and had no issue. I'd upload my boot.img but I'm a Verizon user and not sure if it'll work for you. "magisk_patched_dnuD3.img"
Magisk v21.2 (21200)
Magisk Manager v8.0.4 (4768) (15)
Click to expand...
Click to collapse
I installed 8.0.4 but when I try to patch the image with it, it fails. When I try to sideload 21.2 or 20.4, it says:
E:footer is wrong
E:Signature verification failed
E:error: 21
Install from ADB completed with status 2.
Installation aborted.

I was able to patch the image after changing to the beta channel. However, it started to loop again and eventually went back to bootloader with the reason being "no valid slot to boot". I've flash-all.bat'ed again and am back to working. I don't understand why I can't get this to work.

I also had an inability to boot after I tried to do the December update using Minimal ADB. No valid slot.
I switched to a new platform tools install, and the same procedure has now worked twice. How old is your platform tools install?

If anyone is having problems patching the stock boot.img, you can upload it and I can patch it and re-upload it for you.

earlgrey_44 said:
I also had an inability to boot after I tried to do the December update using Minimal ADB. No valid slot.
I switched to a new platform tools install, and the same procedure has now worked twice. How old is your platform tools install?
Click to expand...
Click to collapse
It was pretty new/latest version but I went ahead and just re-downloaded the factory image and platform tools and am trying again...
If it matters, I'm back to Canary manager and here is what my patch screen says:
Code:
- Device platform: arm64-v8a
- Magisk Manager: 8.0.4 (4770)
- Install target: 6d88d8ad (21201)
- Copying image to cache
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Repacking boot image
- Output file *path*
- All done!
My actual flash output is:
Code:
> fastboot flash boot magisk_patched_Mx5Yh.img
Sending 'boot_a' (98304 KB) OKAY [ 2.277s]
Writing 'boot_a' OKAY [ 0.312s]
Finished. Total time: 2.918s
UPDATE:
I got it working this time around using a fresh new factory image and platform tools download.
I'm actually wondering if, in my haste, I actually used the bootloader image, not the boot img...but wouldn't Magisk have complained? lol.
Who knows, but looks like my issue is resolved! Thanks all for having me try things like a new platform tools download.