Heloo and sorry in advance if i'm making a thread that has allready been made
I have followed all the steps from the Installation Instructions (i do not have a rooted device or a custom room installed)
After flashing the patched boot image trough adb,rebooting then opening hte magisk manager i still see the Magisk is not installed
Also i am a beginer so i may not know how to post logs or where to get them
If any other information is needed please let me know
You don't use ADB to flash a boot image. Depending on your device it'll be fastboot, Odin, or whatever's applicable. What is your device?
Didgeridoohan said:
You don't use ADB to flash a boot image. Depending on your device it'll be fastboot, Odin, or whatever's applicable. What is your device?
Click to expand...
Click to collapse
My device is an allview x3 soul lite(i'm pretty sure it's a rebranded version of gionee f103 pro)
Onelas said:
My device is an allview x3 soul lite(i'm pretty sure it's a rebranded version of gionee f103 pro)
Click to expand...
Click to collapse
Ok... Don't know anything about that device... :laugh:
Fastboot is probably the way to go:
Code:
fastboot flash boot patched_boot.img
Have you used the above command?
Useful information to provide would be an installation log from when you patch the image in the Manager (there's a button for it in the Manager flashing window), what you do to flash the image, and the output when flashing.
Didgeridoohan said:
Ok... Don't know anything about that device... :laugh:
Fastboot is probably the way to go:
Code:
fastboot flash boot patched_boot.img
Have you used the above command?
Useful information to provide would be an installation log from when you patch the image in the Manager (there's a button for it in the Manager flashing window), what you do to flash the image, and the output when flashing.
Click to expand...
Click to collapse
yes i did
Here is the log from patching the boot image
- Device platform: arm64
- Extracting files
- Boot image is signed with AVB 1.0
- Unpacking boot image
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]
KERNEL [7470696]
RAMDISK [1897650]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465232768]
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [a741fb925935959ee34c60f918f1e9206c987a99]
DTB [79446]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
- Checking ramdisk status
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_494e60652653221568df3d6988887666e1386970.img.gz]
- Patching ramdisk
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[true]
Remove pattern [,verify]
Remove [verity_key]
Save SHA1: [494e60652653221568df3d6988887666e1386970] -> [.backup/.sha1]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [fstab.mt6735] -> [.backup/fstab.mt6735]
Backup mismatch entry: [init] -> [.backup/init]
Backup missing entry: [verity_key] -> [.backup/verity_key]
Dump cpio: [ramdisk.cpio]
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Loading dtbs from [dtb]
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Patch @ 00EC8DBB [736B69705F696E697472616D6673]->[77616E745F696E697472616D6673]
- Repacking boot image
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]
KERNEL [7470696]
RAMDISK [1897650]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465232768]
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [a741fb925935959ee34c60f918f1e9206c987a99]
DTB [79446]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
KERNEL [7474614]
RAMDISK [2282725]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465232768]
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [53c61054ade95d565748766a0d93ea7873ffc362]
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Cleaning up...
- Signing boot image with test keys
*********************************
Patched Boot Image is placed in
/storage/emulated/0/MagiskManager/patched_boot.img
*********************************
- All done!
Log looks fine. What was the output when flashing the patched boot image?
Didgeridoohan said:
Log looks fine. What was the output when flashing the patched boot image?
Click to expand...
Click to collapse
this is the first time i got this error
target reported max download size of 134217728 bytes
sending 'boot' (9533 KB)...
OKAY [ 0.922s]
writing 'boot'...
FAILED (remote: download for partition 'boot' is not allowed
)
finished. total time: 0.952s
until now the failed part has never shown
Onelas said:
this is the first time i got this error
target reported max download size of 134217728 bytes
sending 'boot' (9533 KB)...
OKAY [ 0.922s]
writing 'boot'...
FAILED (remote: download for partition 'boot' is not allowed
)
finished. total time: 0.952s
until now the failed part has never shown
Click to expand...
Click to collapse
Is your bootloader unlocked? It needs to be... Keep in mind that doing that will likely wipe your device.
Didgeridoohan said:
Is your bootloader unlocked? It needs to be... Keep in mind that doing that will likely wipe your device.
Click to expand...
Click to collapse
done,i have unlocked it(i had a button for it in the developer menu)
target reported max download size of 134217728 bytes
sending 'boot' (9533 KB)...
OKAY [ 0.925s]
writing 'boot'...
OKAY [ 0.283s]
finished. total time: 1.212s
waiting for it to finish booting,i just hope i didn't brick it
Aaaand it's working now,thank you verry verry much for taking your time to help me
Hiya, Is/would Magisk work on the Essential Android P? My bootloader is unlocked, but I keep getting the Failed boot image is signed with AVB 1.0 message
Fixed: Just had to read a bit closer.
Onelas said:
Aaaand it's working now,thank you verry verry much for taking your time to help me
Click to expand...
Click to collapse
You have to run the right adb command for your device to unlock the bootloader after enabling in dev options something like
fastboot oem unlock
Related
HEllo everybody
MAGISK V15.3 installed on Samsung TAB S2 SM-T810.
I tried to install MAGISK v16.O with MAGISK installer
Installation failed with this log
- Device platform: arm
- Extracting files
- Patch boot/ramdisk image: /dev/block/mmcblk0p9
boot_patch.sh: ./util_functions.sh: line 15: ps: Permission denied
boot_patch.sh: ./util_functions.sh: line 15: grep: Permission denied
boot_patch.sh: ./util_functions.sh: line 15: grep: Permission denied
boot_patch.sh: ./util_functions.sh: line 16: grep: Permission denied
boot_patch.sh: ./util_functions.sh: line 16: grep: Permission denied
boot_patch.sh: ./util_functions.sh: line 17: id: Permission denied
boot_patch.sh: ./util_functions.sh: line 17: grep: Permission denied
boot_patch.sh: line 75: chmod: Permission denied
boot_patch.sh: line 78: ./magiskinit: Permission denied
- Unpacking boot image
boot_patch.sh: line 87: ./magiskboot: Permission denied
boot_patch.sh: line 117: ./magiskboot: Permission denied
boot_patch.sh: line 148: ./magiskboot: Permission denied
boot_patch.sh: line 150: rm: Permission denied
boot_patch.sh: line 177: ./magiskboot: Permission denied
- Checking ramdisk status
- Patching ramdisk
- Repacking boot image
! Unable to repack boot image!
Failed!
! Installation failed
Any Idea ?
Thanks for your help
I have Samsung S5 g900w8
Identical problem.. my log file is exactly the same.
Try uninstalling v15.3 first and then install v16.0 clean.
I have uninstalled magisk 15.3, then installed magisk 16.0 with twrp.
Its perfect !
Thanks for your help
I did the Uninstaller /clean install method, which did update me to v16. Unfortunately now it fails safety net and apps can all detect root.
Lem0ns said:
I did the Uninstaller /clean install method, which did update me to v16. Unfortunately now it fails safety net and apps can all detect root.
Click to expand...
Click to collapse
It seems like some users have had issues with MagiskHide after updating to v16... Try toggling MagiskHide off and on. If that still doesn't work, navigate to /data/property and delete the file persist.magisk.hide, if it exists.
Uploading a Magisk debug log would also be useful.
Didgeridoohan said:
It seems like some users have had issues with MagiskHide after updating to v16... Try toggling MagiskHide off and on. If that still doesn't work, navigate to /data/property and delete the file persist.magisk.hide, if it exists.
Uploading a Magisk debug log would also be useful.
Click to expand...
Click to collapse
I've tried toggling everything off /on. I've Uninstalled and reinstalled twice.
The persist.magisk.hide file wasn't there.
I'm not sure how to install the beta version in order to get the debug log.
If I just go back to an older version, will this fix?
Lem0ns said:
I'm not sure how to install the beta version in order to get the debug log.
Click to expand...
Click to collapse
Change update channel in the Manager settings you beta and press install...
If I just go back to an older version, will this fix?
Click to expand...
Click to collapse
No it won't (well, maybe for you, but the underlying issue won't be).
Please at least provide the debug log before reverting. Make sure you've done a SafetyNet check before saving the log.
Didgeridoohan said:
Change update channel in the Manager settings you beta and press install...
No it won't (well, maybe for you, but the underlying issue won't be).
Please at least provide the debug log before reverting. Make sure you've done a SafetyNet check before saving the log.
Click to expand...
Click to collapse
First, thank you for all of your help. I'm still not able to get a debug log. I have toggled 2 Beta And pressed install but it's still just downloads the same file version 16 and won't install internally (see above post). When I install with TW RP it messed up the boot partition and I had to restore from backup. The next attempt it seemed to install fine but there is no log file in the ADB directory. How can I tell if the beta is installed?
I wish I hadn't tried to update. The previous version worked great and I only updated because it was nagging me 200 times a day and I have a hard time not updating to the newest version of things.
Just in case something helps here's a timeline of what I tried.
-direct install from previous version several times (failed with unable to repack boot image error)
-install via zip in TWRP - success - fails safety net + hide doesn't work
-toggle all settings on/off etc. (side note... sometimes settings don't "stick". like I toggle the hosts file setting on or off and then close the menu and when I open it it's back on/off as if I hadn't changed it)
-try just reinstalling - boots right to odin/download mode
-restore boot partition from backup - boots fine, still fails safety net
-try "core function only" mode - magisk asks to reboot manually... try this and it comes up in regular mode... toggle the switch again and reboot and it seems to work. I get SU access but still fails safety net.
-try uninstalling, reboot, re-install via TWRP.. no luck.. try formatting system partition and restore from backup.. reinstall magisk.. same result.
-toggle to beta update path, click install. Not sure what is supposed to happen here. It appears to download exactly the same file as the non beta. It won't install direct and when I flash with TWRP it doesn't appear different. Still fails safet net. When I browse to data/adb there are no log files.
I grabbed the 15.2 version and installed it. Everything seems to work now.
Thanks again for your help. Maybe I'll try again on the next update.
sumsung J720F with Oreo 8.0.0
magisk installed
patching the boot.img and at the end i have
! Unable to repack boot image!
! Installation failed
any help idea plz ???
here is the full log of Magisk
Code:
- Copying image to cache
- Device platform: arm64-v8a
- Downloading zip
... 0%
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.027 secs (39389925 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [22504320]
RAMDISK_SZ [4067161]
SECOND_SZ [4278190336]
EXTRA_SZ [738199576]
RECOV_DTBO_SZ [3489687392]
OS_VERSION [41.68.0]
PATCH_LEVEL [2000-01]
PAGESIZE [8]
NAME [RPRA09A001KU]
CMDLINE [ndroidboot.selinux=permissive ��_�]
CHECKSUM [c6]
Invalid DTB detection at 0xe936a2: header tag of first node != FDT_BEGIN_NODE
Invalid DTB detection at 0xe9e587: header tag of first node != FDT_BEGIN_NODE
Invalid DTB detection at 0xea93ad: header tag of first node != FDT_BEGIN_NODE
Invalid DTB detection at 0xeb4133: header tag of first node != FDT_BEGIN_NODE
Segmentation fault
- Checking ramdisk status
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_2f3acf3530c9d7aafc3a2370f747a32ea107f0a3.img.gz]
cp: can't stat 'ramdisk.cpio': No such file or directory
- Patching ramdisk
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[true]
Segmentation fault
- Repacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [22504320]
RAMDISK_SZ [4067161]
SECOND_SZ [4278190336]
EXTRA_SZ [738199576]
RECOV_DTBO_SZ [3489687392]
OS_VERSION [41.68.0]
PATCH_LEVEL [2000-01]
PAGESIZE [8]
NAME [RPRA09A001KU]
CMDLINE [ndroidboot.selinux=permissive ��_�]
CHECKSUM [c6]
Invalid DTB detection at 0xe936a2: header tag of first node != FDT_BEGIN_NODE
Invalid DTB detection at 0xe9e587: header tag of first node != FDT_BEGIN_NODE
Invalid DTB detection at 0xea93ad: header tag of first node != FDT_BEGIN_NODE
Invalid DTB detection at 0xeb4133: header tag of first node != FDT_BEGIN_NODE
Segmentation fault
! Unable to repack boot image!
! Installation failed
Hi,
Today I was try to install magisk root using Magisk Manager. I am having problems installing it.
My Android version: 6.0
The log:
- Copying image locally
- Target image: /data/user/0/com.topjohnwu.magisk/install/boot.img
- Device platform: arm64-v8a
- Extracting files
- Unpacking boot image
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
! Unable to unpack boot image
Failed!
! Installation failed
Thank you
Hello i want to install magisk on my SM-G390F, on android 8.1.0, baseband G390FXXU2BRH3, when i patch the boot.img i get this errors
Code:
- Copying image to cache
- Device platform: armeabi-v7a
- Downloading zip
... 0%
- Extracting files
boot_patch.sh[73]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
KERNEL [14758304]
RAMDISK [2478705]
SECOND [0]
EXTRA [376832]
PAGESIZE [2048]
OS_VERSION [8.1.0]
PATCH_LEVEL [2018-08]
NAME [SRPPK23A000KU]
CMDLINE [androidboot.selinux=permissive androidboot.selinux=permissive]
CHECKSUM [72c35f6755e256251a06f7f26c7d0d111dc8ceeb]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
boot_patch.sh[98]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
boot_patch.sh[120]: can't create /proc/self/fd/: Is a directory
boot_patch.sh[120]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_445cd3cd8b66e965c8ab1fc3850aab7d36aef5a8.img.gz]
boot_patch.sh[126]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]
Remove pattern [,verify]
Replace pattern [forceencrypt] with [encryptable]
Save SHA1: [445cd3cd8b66e965c8ab1fc3850aab7d36aef5a8] -> [.backup/.sha1]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [fstab.samsungexynos7570] -> [.backup/fstab.samsungexynos7570]
Backup mismatch entry: [init] -> [.backup/init]
Dump cpio: [ramdisk.cpio]
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Loading dtbs from [extra]
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Patch @ 00CD8752 [736B69705F696E697472616D6673]->[77616E745F696E697472616D6673]
boot_patch.sh[169]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
KERNEL [14758304]
RAMDISK [2478705]
SECOND [0]
EXTRA [376832]
PAGESIZE [2048]
OS_VERSION [8.1.0]
PATCH_LEVEL [2018-08]
NAME [SRPPK23A000KU]
CMDLINE [androidboot.selinux=permissive androidboot.selinux=permissive]
CHECKSUM [72c35f6755e256251a06f7f26c7d0d111dc8ceeb]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
KERNEL [14758304]
RAMDISK [2722538]
SECOND [0]
EXTRA [376832]
PAGESIZE [2048]
OS_VERSION [8.1.0]
PATCH_LEVEL [2018-08]
NAME [SRPPK23A000KU]
CMDLINE [androidboot.selinux=permissive androidboot.selinux=permissive]
CHECKSUM [72d64a95fd6cd020abf973d2d081b0c9b0cdf320]
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Cleaning up...
****************************
Patched image is placed in
/storage/emulated/0/Download/patched_boot.img.tar
****************************
- All done!
My boot.img and the patched boot image links are bellow as the files are to big to attach, if anyone can help me out that will be great.
https://www.dropbox.com/s/i2jtq7cxtf8rw7z/boot.img?dl=0
https://www.dropbox.com/s/i2jtq7cxtf8rw7z/boot.img?dl=0
If i ignore the above and go ahead and flash the patched image trough odin i get this after the phone boots
https://i.imgur.com/hkrbddB.jpg
Now i reseted the phone , restart funny i still have magisk 17.1 installed but my problem now is that my imei is gone and so my network connection so i'm not able to get any signal from any mobile network (ee,o2,vodafone etc)
If i try to install a module from magisk i get the fallowing error: Unable to extract zip file. Installation failed!
Root on the other hand is working.
If i reflash the stock all comes back to normal
Can anyone give me hand with this.
Many Thanks,
George
Right i found a half way, i installed a twrp even if my phone was going in boot loop with it then installed magisk reboot then my phone started just fine and with the magisk
FreeTheWeb said:
Right i found a half way, i installed a twrp even if my phone was going in boot loop with it then installed magisk reboot then my phone started just fine and with the magisk
Click to expand...
Click to collapse
Hi ! Can you help me to install TWRP and Magisk on my Xcover 4 ? I can't find any TWRP version for it ... thanks
Hi this is what i used
https://drive.google.com/file/d/1CS9DIdUyw_QmhYcorcUwYZGZCGGYfolz/view?usp=sharing
FreeTheWeb said:
Hi this is what i used
https://drive.google.com/file/d/1CS9DIdUyw_QmhYcorcUwYZGZCGGYfolz/view?usp=sharing
Click to expand...
Click to collapse
Thanks but it does not work ..
I got "fail to open recovery no such file or directory"
"no support single sku"
"E:unknown volume for path [/odm]"
"E:unknown volume for path [/vendor]"
maybe cause i'm on android 8.1 ?
I will try to install magisk without TWRP with the "boot.img" trick...
Thanks alot FreeTheWeb
You saved my phone, i have been trying 20 different ways in 30 hours and finally i got into TWRP.
Used: G390FXXU2BRJ1 Firmware from sammobile.
I also have Xcover 4 on 8.1 oreo and I have the same problems. Patching boot causes no signal range, TWRP is missing for this model, and installing this from a thread causes a message like the user of Doc_Emmett_Brown. At Nougat, I had root patching boot.iso without any problems, and here Oreo are the problems. Please help.
Zdzisław said:
I also have Xcover 4 on 8.1 oreo and I have the same problems. Patching boot causes no signal range, TWRP is missing for this model, and installing this from a thread causes a message like the user of Doc_Emmett_Brown. At Nougat, I had root patching boot.iso without any problems, and here Oreo are the problems. Please help.
Click to expand...
Click to collapse
Hi! Can you explain how do you get root at Nougat on Xcover4? I have this one and I can't find any working solution.
Read my previous posts to get magisk on your xcover.
Zdzisław said:
I also have Xcover 4 on 8.1 oreo and I have the same problems. Patching boot causes no signal range, TWRP is missing for this model, and installing this from a thread causes a message like the user of Doc_Emmett_Brown. At Nougat, I had root patching boot.iso without any problems, and here Oreo are the problems. Please help.
Click to expand...
Click to collapse
i have the same problem, after flashing patched boot img, im getting no signal bug
Works on Xperia XZ1? ?
Sent from my Sony H9436 using XDA Labs
Hi guys,
I'm sorry for this new thread but I'm trying to install Magisk without any custom recovery but I have obtained poor results for now.
I'm working on a single-board computer i.MX7D with Android Things 1.0.8. I have installed Magisk Manager, I have patched the new boot.img e next I have flashed it into boot_a and boot_b partitions using fastboot:
fastboot flash boot_a patched_boot.img
Code:
target reported max download size of 419430400 bytes
sending 'boot_a' (14720 KB)...
OKAY [ 0.490s]
writing 'boot_a'...
OKAY [ 0.604s]
finished. total time: 1.094s
fastboot flash boot_b patched_boot.img
Code:
target reported max download size of 419430400 bytes
sending 'boot_b' (14720 KB)...
OKAY [ 0.481s]
writing 'boot_b'...
OKAY [ 0.636s]
finished. total time: 1.117s
The system reboot correctly, but Magisk is not installed.
What I am wrong?
This is the install log:
Code:
- Copying image to cache
- Device platform: armeabi-v7a
- Existing zip found
- Extracting files
- Unpacking boot image
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [9741613]
RAMDISK_SZ [5083265]
SECOND_SZ [0]
EXTRA_SZ [0]
RECOV_DTBO_SZ [0]
OS_VERSION [8.1.0]
PATCH_LEVEL [2018-10]
PAGESIZE [2048]
NAME []
CMDLINE [init=/init androidboot.hardware=imx7d vt.global_cursor_default=0 consoleblank=0 rootwait ro earlyprintk loglevel=7 console=ttymxc4,115200 androidboot.console=ttymxc4 buildvariant=userdebug]
CHECKSUM [3db586c24cd1a96871cf6bec185525a1f83a4249]
Invalid DTB detection at 0x1b31: size (16793940) > remaining (9734652)
DTB [45509]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
- Checking ramdisk status
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_722068a856e0e11321dbd6254b18f03fd754e3e9.img.gz]
- Patching ramdisk
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[false]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
- Repacking boot image
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [9741613]
RAMDISK_SZ [5083265]
SECOND_SZ [0]
EXTRA_SZ [0]
RECOV_DTBO_SZ [0]
OS_VERSION [8.1.0]
PATCH_LEVEL [2018-10]
PAGESIZE [2048]
NAME []
CMDLINE [init=/init androidboot.hardware=imx7d vt.global_cursor_default=0 consoleblank=0 rootwait ro earlyprintk loglevel=7 console=ttymxc4,115200 androidboot.console=ttymxc4 buildvariant=userdebug]
CHECKSUM [3db586c24cd1a96871cf6bec185525a1f83a4249]
Invalid DTB detection at 0x1b31: size (16793940) > remaining (9734652)
DTB [45509]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
HEADER_VER [0]
KERNEL_SZ [9741613]
RAMDISK_SZ [5328429]
SECOND_SZ [0]
EXTRA_SZ [0]
RECOV_DTBO_SZ [0]
OS_VERSION [8.1.0]
PATCH_LEVEL [2018-10]
PAGESIZE [2048]
NAME []
CMDLINE [init=/init androidboot.hardware=imx7d vt.global_cursor_default=0 consoleblank=0 rootwait ro earlyprintk loglevel=7 console=ttymxc4,115200 androidboot.console=ttymxc4 buildvariant=userdebug]
CHECKSUM [76fc9c4cf236a4b64329fbc2d9fffbd129c41d65]
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Cleaning up...
****************************
Patched image is placed in
/storage/emulated/0/Download/patched_boot.img
****************************
- All done!
Trying to patch a bootloader image. Error message: Unable to repack boot image.
Magisk Manager 7.4.0 (253). G6 Play XT1922-4 Pie. Screenshot attached.
Code:
- Device platform: armeabi-v7a
- Copying image to cache
1566+0 records in
1566+0 records out
1603584 bytes transferred in 1.006 secs (1594019 bytes/sec)
1045+1 records in
1045+1 records out
1070668 bytes transferred in 0.020 secs (53533400 bytes/sec)
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
PXA_BOOT_HDR
HEADER_VER [0]
KERNEL_SZ [1986939136]
RAMDISK_SZ [1869570592]
SECOND_SZ [543516513]
EXTRA_SZ [169964133]
PAGESIZE [1635151433]
NAME [lid page size
]
CMDLINE [sing kernel image: start
oting normally]
CHECKSUM [007265626f6f74696e6720746865206465766963650a004f4b4159007265626f]
Segmentation fault
- Checking ramdisk status
- Stock boot image detected
- Backing up stock boot image
- Patching ramdisk
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[true]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
- Repacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
PXA_BOOT_HDR
HEADER_VER [0]
KERNEL_SZ [1986939136]
RAMDISK_SZ [1869570592]
SECOND_SZ [543516513]
EXTRA_SZ [169964133]
PAGESIZE [1635151433]
NAME [lid page size
]
CMDLINE [sing kernel image: start
oting normally]
CHECKSUM [007265626f6f74696e6720746865206465766963650a004f4b4159007265626f]
Segmentation fault
! Unable to repack boot image!
! Installation failed
Any ideas?
It works for boot.img
And there's your answer...
You're not supposed to do anything to the bootloader. Only boot image, or if you have an A only SAR device the recovery image.
Ok. Thank you.