[Help] Install Magisk without TWRP on xCover 4 - Magisk

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

Related

[MOD] Magisk v12.0 for Android x86 7.1-rc2

Hello there.
First of all, let me thank this incredible tool made by @topjohnwu, it's really a nice idea and implementation. I don't own any of the code here, it's just a modification to be able to install and run under Android-x86.org latest Nougat version (as of now, 7.1-rc2). It may work with other versions, including RemixOS and PhoenixOS, but I have not tested it. It was tested using a normal installation on a FAT32 partition, and should work with either a RW or RO system image.
Newer versions of Magisk don't use magic_magisk.sh anymore, that's why I've chosen v12.0 (it can be downloaded from the official thread on XDA). If topjohnwu want to add patches to the source code, I would be more than glad to help. But probably it's not worth the trouble... Another log is created on cache called logtmp.log if you want to check more info about what's going on.
The first step is to make a "fake" boot.img for the installer can patch the ramdisk.img. In order to do this, you will need the handy tool mkbootimg from this other XDA thread:
https://forum.xda-developers.com/showthread.php?t=2319018
Copy both kernel and ramdisk.img from the original installation and use this command (all files must be in the current directory, of course):
Code:
./mkbootimg --kernel kernel --ramdisk ramdisk.img -o boot.img
then copy the resulting boot.img to the Magisk v12.0 folder you will use to install it on your Android x86 installation. The easy way is use a flash drive connected to USB, and I will assume from now on that you have downloaded and decompressed the Magisk files to the root of your flash drive, creating a folder Magisk-v12.0 on it.
After that, if you still have su working on your installation, do the steps bellow after calling "su" (Magisk installer will remove the original su, so if you do not have it you should still be able to access root using the ALT+F1 terminal):
Code:
cd /dev
mkdir tmp
mkdir tmp/magisk
cd tmp/magisk
cp -r /storage/YOUR-FLASH-DRIVE-ID-HERE/Magisk-v12.0/* .
mv boot.img /data
sh ./META-INF/com/google/android/update-binary
YOUR-FLASH-DRIVE-ID-HERE must be replaced with your drive's unique ID. Alternatively you can copy the folder using a file manager to you internal storage (/sdcard) and then use this command instead:
Code:
cp -r /sdcard/Magisk-v12.0/* .
If everything goes well, you should see a message in the end that the new ramdisk.img is ready in the current directory, move it to somewhere else you can replace the installed one. The easiest way is moving it to a flash drive, boot on another system and replace the original one. If you can't do it, you can also move it to /data then boot in DEBUG mode and replace it on /mnt after you type "exit" once. then reboot. Also, delete boot.img from /data, it won't be necessary anymore.
This should result in a full installation of Magisk v12.0. Be aware that current modules for Magisk V14.0 won't work, so you have to dig old ones compatible with v12.0. Also, as many have asked me, probably SafetyNet won't work because it's an old version and Android x86 is a debug version anyway, you must "fake" a lot of things to pass SafetyNet test.
Attached are the modified files:
- updater-script
- magic_mask.sh
- magisk.apk (I had to use 4.3.3 for better compatibility, do not upgrade or it make break installation)
Have fun!
I do everything according to the instructions, but I can not.
Displays the following message.
I ask for help.
android-x86_64-7.1-rc2x
Code:
/dev/tmp/magisk # sh ./META-INF/com/google/android/update-binarg
unzip: can’t open [.zip]
***************************
Magisk v12.0 Boot Image Patcher
*******************************
0) /dev/tmp/magisk/common /-/
- Mounting /sistemro), /cache, /data
- Device platform: x64
chmod: /dev/tmp/magisk/chromeos: No such file or directorg
chmod: /dev/tmp/magisk/X64: No such file or directorg
- Constructing environment
cp: bad ’/dev/tmp/magisk/x64/busgbox’I No such file or directorg
cp: bad ’/dev/tmp/magisk/Xfié/magiskboot’I No such file or directorg
cp: bad ’/dev/tmp/magisk/xfié/magiskpolicg’I No such file or directorg
cp: bad ’/dev/tmp/magisk/common/init.magisk.rc’I No such file or directorg
cp: bad ’/dev/tmp/magisk/common/custom_ramdisk_patch.sh’I No such file or directorg
chmod: chmod ’sepolicy_inject’ to 120755: No such file or directorg
./METH-INF/com/google/android/update_binarg[280]: /dev/tmp/magisk/x64/busgbox: not found
./METH7INF/com/google/android/update7binarg[289]: /dev/tmp/magisk/X64/magiskpolicy: not found
- Creating /data/magisk.img
/dev/tmp/magisk/common/file_contexts_image: No such file or directorg
mount: ’/’ not in /proc/mounts
mount: ’/’ not in /proc/mounts
! Magisk image mount failed...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Done independently. It was necessary to take the original Magisk-v12.0, in which it was necessary to replace the files from the post above and then install it.
free39 said:
I do everything according to the instructions, but I can not.
Displays the following message.
I ask for help.
android-x86_64-7.1-rc2x
Done independently. It was necessary to take the original Magisk-v12.0, in which it was necessary to replace the files from the post above and then install it.
Click to expand...
Click to collapse
I think you were successful in the end, but just to clarify: you're correct, one must first download v12.0 from the official thread then replace the files with the ones attached to OP, and only then use it. :good:
@lfom
Can you please make a video and upload to YouTube. So we can learn how to do it exactly. I did try on my pc, not work. DO wee need linux for make boot.img? Can you please explain us about more detail, if possible with video please.
@lfom
Can you give a bit more detailed guide?
Like, do we have to reboot into Android partition with debug flag enabled in the kernel, then run the magisk script?
harkaman said:
@lfom
Can you please make a video and upload to YouTube. So we can learn how to do it exactly. I did try on my pc, not work. DO wee need linux for make boot.img? Can you please explain us about more detail, if possible with video please.
Click to expand...
Click to collapse
Sorry, I cannot make a video now. It's not that simple because I cannot use a screen recorder for many steps. But it's basically what is written in the tutorial. I have used Linux, but the original thread says it should work with Cygwin., although I haven't tested, it should work are long as you have the correct files as you only need one executable (mkbootimg).
https://en.wikipedia.org/wiki/Cygwin
silv3rfox said:
@lfom
Can you give a bit more detailed guide?
Like, do we have to reboot into Android partition with debug flag enabled in the kernel, then run the magisk script?
Click to expand...
Click to collapse
No, you don't need debug mode. To run the magisk install script you need superuser rights, so the easier way it to open the console mode using ALT+F1 (you need either an external keyboard or maybe a custom keyboard that allows ALT commands, like Hacker's Keyboard).
I'll try to answer questions as soon as possible, so the information is clear enough so anyone can do it.
lfom said:
Sorry, I cannot make a video now. It's not that simple because I cannot use a screen recorder for many steps. But it's basically what is written in the tutorial. I have used Linux, but the original thread says it should work with Cygwin., although I haven't tested, it should work are long as you have the correct files as you only need one executable (mkbootimg).
https://en.wikipedia.org/wiki/Cygwin
No, you don't need debug mode. To run the magisk install script you need superuser rights, so the easier way it to open the console mode using ALT+F1 (you need either an external keyboard or maybe a custom keyboard that allows ALT commands, like Hacker's Keyboard).
I'll try to answer questions as soon as possible, so the information is clear enough so anyone can do it.
Click to expand...
Click to collapse
Would these steps work for the latest magisk 14.0?
Sent from my ONEPLUS A5000 using Tapatalk
the_mentor said:
Would these steps work for the latest magisk 14.0?
Click to expand...
Click to collapse
No, it won't. As stated in OP, v12.0 was the last version to use the magic_mask.sh. Newer versions use binaries so it's much more difficult to mod unless you change the source code and re-compile the tool.
It works :good: tried on two different pcs. Windows users can use Android Image Kitchen for creating boot.img
maxriter said:
It works :good: tried on two different pcs. Windows users can use Android Image Kitchen for creating boot.img
Click to expand...
Click to collapse
I have createed bootimg . what shell i do next? do i need to copy and go in android x86?
harkaman said:
I have createed bootimg . what shell i do next? do i need to copy and go in android x86?
Click to expand...
Click to collapse
follow steps from OP, download magisk, replace files in magisk with that from the attachment, copy magisk along with boot.img to sdcard or usb drive, boot to android-x86, run the commands from OP, as a result you will get a patched ramdisk.img, copy this ramdisk to usb drive, boot back to windows, replace the original ramdisk from android x86 with the patched one.
hi.
I have installed magisk in android x86 and new ramdisk is created. BUt where and how can i copy, since i lose root. How can I copy new ramdisk?
Code:
x86_64:/ $ su
x86_64:/ # cd /dev
x86_64:/dev # mkdir tmp
x86_64:/dev # mkdir tmp/magisk
x86_64:/dev # cd tmp/magisk
x86_64:/dev/tmp/magisk # cp -r /storage/B6B4-79A3/Magisk-v12.0/* .
x86_64:/dev/tmp/magisk # mv boot.img /data
x86_64:/dev/tmp/magisk # sh ./META-INF/com/google/android/update-binary
unzip: cannot find or open , .zip or .ZIP.
*****************************
Magisk v12.0 Boot Image Patcher
*****************************
0) /dev/tmp/magisk/common /-/
- Mounting /system(ro), /cache, /data
! System installed root detected, mount rw :(
- Device platform: x64
- Constructing environment
- Creating /data/magisk.img
Creating filesystem with parameters:
Size: 67108864
Block size: 4096
Blocks per group: 32768
Inodes per group: 4096
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 16384
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/4096 inodes and 1294/16384 blocks
losetup: /data/magisk.img
losetup: /data/magisk.img
losetup: /data/magisk.img
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /data/boot.img
- Unpacking boot image
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/boot.img]
IMG [AOSP]
KERNEL [6098096] @ 0x10008000
RAMDISK [1795598] @ 0x11000000
SECOND [0] @ 0x10f00000
DTB [0] @ 0x10000100
PAGESIZE [2048]
NAME []
CMDLINE []
COMPRESSION [gzip]
Decompressing to [ramdisk.cpio]
- Checking patch status
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
- Backing up stock boot image
15424+0 records in
15424+0 records out
7897088 bytes (7.5MB) copied, 0.067583 seconds, 111.4MB/s
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Compressing to [/data/stock_boot_1b72ffffff9317ffffffdaffffffe6ffffffe7ffffff8870ffffffc0ffffffabffffff8dffffffc4fffffff356ffffff937e7c16ffffffb0.img.gz]
- Patching ramdisk
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Dump cpio: [ramdisk.cpio]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Dump cpio: [ramdisk.cpio]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Extracting [init.rc] to [init.rc]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init.rc] (0750)
Dump cpio: [ramdisk.cpio]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Extracting [sepolicy] to [sepolicy]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [sepolicy] (0644)
Dump cpio: [ramdisk.cpio]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Create directory [magisk] (0755)
Dump cpio: [ramdisk.cpio]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init.magisk.rc] (0750)
Dump cpio: [ramdisk.cpio]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [sbin/magic_mask.sh] (0750)
Dump cpio: [ramdisk.cpio]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Loading cpio: [ramdisk.cpio.orig]
Entry [init.magisk.rc] is new
Entry [init.rc] missmatch
Entry [magisk] is new
Entry [sbin/magic_mask.sh] is new
Entry [sepolicy] missmatch
Dump cpio: [ramdisk.cpio]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
- Repacking boot image
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/boot.img]
IMG [AOSP]
KERNEL [6098096] @ 0x10008000
RAMDISK [1795598] @ 0x11000000
SECOND [0] @ 0x10f00000
DTB [0] @ 0x10000100
PAGESIZE [2048]
NAME []
CMDLINE []
COMPRESSION [gzip]
Repack to boot image: [new-boot.img]
Compressing to [ramdisk.cpio.gz]
KERNEL [6098096] @ 0x10008000
RAMDISK [1851668] @ 0x11000000
SECOND [0] @ 0x10f00000
DTB [0] @ 0x10000100
PAGESIZE [2048]
NAME []
CMDLINE []
COMPRESSION [gzip]
Boot partition too small!
! Boot partition space insufficient
! Remove ramdisk backups and try again
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Remove [.backup]
Remove [.backup]
Remove [.backup]
Remove [.backup]
Dump cpio: [ramdisk.cpio]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/boot.img]
IMG [AOSP]
KERNEL [6098096] @ 0x10008000
RAMDISK [1795598] @ 0x11000000
SECOND [0] @ 0x10f00000
DTB [0] @ 0x10000100
PAGESIZE [2048]
NAME []
CMDLINE []
COMPRESSION [gzip]
Repack to boot image: [new-boot.img]
Compressing to [ramdisk.cpio.gz]
KERNEL [6098096] @ 0x10008000
RAMDISK [1797690] @ 0x11000000
SECOND [0] @ 0x10f00000
DTB [0] @ 0x10000100
PAGESIZE [2048]
NAME []
CMDLINE []
COMPRESSION [gzip]
Boot partition too small!
! Boot partition size still too small...
Do not worry, it's fine...
New ramdisk.img ready - /dev/tmp/magisk/ramdisk.img
Copy it to an external drive to replace Android boot one
- Done
x86_64:/dev/tmp/magisk #
Replace installed system.img from the one in android-x86 iso, and repeat the procedure.
Copy this new ramdisk: /dev/tmp/magisk/ramdisk.img to your usb drive: /storage/B6B4-79A3/ and reboot to windows.
A standard android-x86 iso contains initrd.img, system.img/sfs and ramdisk.img + kernel (used to create the boot.img)
installed somewhere in your pc. Replace this ramdisk.img with the patched one from the usb drive.
Thanks for the guide !
I managed to get magisk v15.3 work on latest CM 14.1 x86 on my "tesco connect 7" , a z3735g atom bay-trail based tablet.
inorder to make the patched ramdisk.img I used virtualbox and ran lubuntu x32 16.04 - since I couldn't used mkbootimg on the android directly:
A. because the linked tool is for x64 systems, so x86 android can't run it.
B. because I was emulating android on virtual machine so I ran it as "live", making system as read only I think.
C. although on my x86 virtual android it doesn't work, on my virtual ubuntu x32 it does ( guess it can run x64 binaries somehow ).
once I make boot.img I moved it to android's sdcard ( on my virtual machine running the same image as my tablet ) -> installed magisk manager ( v5.5.5 -the current latest ) then I picked install -> install -> direct install -> picked my boot.img from /sdcard -> then magisk created SDcard/MagiskManager/patched_boot.img.
* in retrospect, a very similar guide can be found here.
then once I had patched_boot.img I moved it to my virtual ubuntu, and ran "unkbootimg patched_boot.img".
this gave me a "ramdisk.cpio.gz", which is actually the "ramdisk.img" needed for the android's iso ( i.e booting using grub ).
so i've rename it "ramdisk.img" and replaced the one found on the android iso root folder.
then I rebooted that modded iso ( i.e with the modded ramdisk.img ) on my virtual -> installed magisk manager -> AND IT SHOWS IT IS INSTALLED !!!!!
now I need to replace my current ramdisk.img on my tablet to actually "magisking" my tablet.
@gps3dx Thanks, your method works. Updated Magisk from 12 to 15.3!
maxriter said:
@gps3dx Thanks, your method works. Updated Magisk from 12 to 15.3!
Click to expand...
Click to collapse
nice to hear.
I suggest you check the magisk log to see if any issue like non-mounted error occurs.
Although magisk reports installed, I have issues - but I see from the magisk beta thread that i'm not the only one... so I guess it's the specific version fault and not the way I install it.
also make sure that you've got magisk files under /data/magisk that resembles (not 1:1) the magisk zip...
i.e that you've got files like "magiskinit", "magiskboot".... I think that if you don't do "direct install" these files won't appear, since I don't think that patching the boot.img alone installs these files on the device.
/data/magisk (ln to /data/adb/magisk ?) does contain those files, I can use root related functions and magisk hide works. Seems good so far.
Moreover i updated from 12 to 15.3, so there is that.
gps3dx said:
nice to hear.
I suggest you check the magisk log to see if any issue like non-mounted error occurs.
Although magisk reports installed, I have issues - but I see from the magisk beta thread that i'm not the only one... so I guess it's the specific version fault and not the way I install it.
also make sure that you've got magisk files under /data/magisk that resembles (not 1:1) the magisk zip...
i.e that you've got files like "magiskinit", "magiskboot".... I think that if you don't do "direct install" these files won't appear, since I don't think that patching the boot.img alone installs these files on the device.
Click to expand...
Click to collapse
do you know Android x86 special mount ?
mount /dev/xxxx on /mnt
mount /mnt/$SRC/system /android/system
mount /mnt/$SRC/data /android/data
https://forum.xda-developers.com/showpost.php?p=75345518&postcount=4926
P.S my android is NOT running from an img or sfs file, since i've expanded and extract the system onto my tablet's hdd ext4 partition.
Click to expand...
Click to collapse
your Android system is hdd ext4 partition /Android-x86/system folder.
so "Mounting mirrors,Magisk : mount /dev/block/mmcblk1p5->/sbin/.core/mirror/system",even though success,no use.
if you use system.sfs or system.img,"Mounting mirrors,Magisk : mount /dev/loop0(or /dev/loop1)->/sbin/.core/mirror/system",must failed,should be mount /dev/block/loop0(/dev/block/loop1)
if you understand magisk 12 magic_mask.sh
SYSTEMBLOCK=`mount | grep " /system " | awk '{print $1}' | awk '{print substr($0,6)}'`
busybox mount -o noatime /dev/block/$SYSTEMBLOCK $MIRRDIR/system
if you not use magisk dummy,you needn't magisk mirror system.
for example,this example must use mirror system.
PHP:
Replace with dummy: /system/app
New directory: /system/app/ChromeCustomizations
Replace with dummy: /system/app
New directory: /system/app/com.google.android.apps.nexuslauncher
Replace with dummy: /system/app
New directory: /system/app/com.google.android.nexusicons
New directory: /system/priv-app/Greenify
Replace with dummy: /system/priv-app
Clone skeleton: /system/priv-app/AnalyticsService
Clone skeleton: /system/priv-app/AudioFX
Clone skeleton: /system/priv-app/BackupRestoreConfirmation
…………
…………
Clone skeleton: /system/app/AndroidTerm
Clone skeleton: /system/app/BasicDreams
Clone skeleton: /system/app/Bluetooth
…………
Does this work with ubuntu? I'm opening the terminal in the folder where every file is but after entering the first command it says file or directory not found. Also i'm running it from a live usb.
youling257 said:
do you know Android x86 special mount ?
mount /dev/xxxx on /mnt
mount /mnt/$SRC/system /android/system
mount /mnt/$SRC/data /android/data
https://forum.xda-developers.com/showpost.php?p=75345518&postcount=4926
your Android system is hdd ext4 partition /Android-x86/system folder.
so "Mounting mirrors,Magisk : mount /dev/block/mmcblk1p5->/sbin/.core/mirror/system",even though success,no use.
if you use system.sfs or system.img,"Mounting mirrors,Magisk : mount /dev/loop0(or /dev/loop1)->/sbin/.core/mirror/system",must failed,should be mount /dev/block/loop0(/dev/block/loop1)
if you understand magisk 12 magic_mask.sh
SYSTEMBLOCK=`mount | grep " /system " | awk '{print $1}' | awk '{print substr($0,6)}'`
busybox mount -o noatime /dev/block/$SYSTEMBLOCK $MIRRDIR/system
if you not use magisk dummy,you needn't magisk mirror system.
for example,this example must use mirror system.
PHP:
Replace with dummy: /system/app
New directory: /system/app/ChromeCustomizations
Replace with dummy: /system/app
New directory: /system/app/com.google.android.apps.nexuslauncher
Replace with dummy: /system/app
New directory: /system/app/com.google.android.nexusicons
New directory: /system/priv-app/Greenify
Replace with dummy: /system/priv-app
Clone skeleton: /system/priv-app/AnalyticsService
Clone skeleton: /system/priv-app/AudioFX
Clone skeleton: /system/priv-app/BackupRestoreConfirmation
…………
…………
Clone skeleton: /system/app/AndroidTerm
Clone skeleton: /system/app/BasicDreams
Clone skeleton: /system/app/Bluetooth
…………
Click to expand...
Click to collapse
I don't understand what do you think I need to do inorder to make it work ?
Also, you're wrong... my "system" folder sits at the root of my android partition...
so it's /dev/mmcblk1p5 partition... which after I mount it... I have "System", "data" and kernel, ramdisk.img & initrd.img files AT THE ROOT of that partition....
Gionikva said:
Does this work with ubuntu? I'm opening the terminal in the folder where every file is but after entering the first command it says file or directory not found. Also i'm running it from a live usb.
Click to expand...
Click to collapse
try ubuntu x64...
I use 'ubuntu-16.04.3-desktop-amd64.iso'

Magisk is not installed

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

Magisk installation problem on stock firmware

Hello,
I have a problem installing Magisk. I have a tablet Oysters T74Mai 3G with MTK processor and stock android 5.1 with unlocked bootloader and without root. There is no any custom recovery for that model.
I installed Magisk Manager 5.8.3 and let it patch the stock boot image. After that I flashed the patched image with fastboot, but when the tablet is powered on, it is stuck on the boot animation. When I flash the stock boot image back with fastboot, the tablet boots normally. I tried to patch the boot image with Magisk 16.0 and 16.7, but the result is the same - stuck on the boot animation.
This is the log from Magisk Manager when patching the boot image:
Code:
- Copying image locally
- Target image: /data/data/com.topjohnwu.magisk/install/boot.img
- Device platform: armeabi-v7a
- Extracting files
- Unpacking boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
KERNEL [7094175]
RAMDISK [668173]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [91065cd3c70eaa74d173a4806f64db3b07f2b3c9]
DTB [23079]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
- Checking ramdisk status
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_21f9cec6deb5897d8707666e6b64e5c29055ed76.img.gz]
- Patching ramdisk
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]
Save SHA1: [21f9cec6deb5897d8707666e6b64e5c29055ed76] -> [.backup/.sha1]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Dump cpio: [ramdisk.cpio]
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Loading dtbs from [dtb]
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
- Repacking boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
KERNEL [7094175]
RAMDISK [668173]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [91065cd3c70eaa74d173a4806f64db3b07f2b3c9]
DTB [23079]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
KERNEL [7094175]
RAMDISK [928004]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [10c3a516cc474a38eed500fe1208f27707cce10a]
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Cleaning up...
****************************
Patched image is placed in
/storage/sdcard0/MagiskManager/patched_boot.img
****************************
- All done!
This is the /cache/magisk.log
Code:
08-09 01:38:39.369 204 204 I Magisk : ** Initializing Magisk
08-09 01:38:39.370 204 204 I Magisk : * Creating /sbin overlay
08-09 01:38:39.685 204 204 I Magisk : * Mounting mirrors
08-09 01:38:39.687 204 204 I Magisk : mount: /sbin/.core/mirror/system
08-09 01:38:39.687 204 204 I Magisk : link: /sbin/.core/mirror/vendor
08-09 01:38:39.687 204 204 I Magisk : bind_mount: /sbin/.core/mirror/bin
08-09 01:38:39.687 204 204 I Magisk : * Setting up internal busybox
08-09 01:38:39.770 210 210 I Magisk : Magisk v16.7(1671) logger started
08-09 01:38:39.771 207 207 I Magisk : Magisk v16.7(1671) daemon started
08-09 01:38:39.779 207 212 I Magisk : ** post-fs-data mode running
08-09 01:38:39.780 207 212 I Magisk : * Mounting /data/adb/magisk.img
08-09 01:38:40.085 207 212 I Magisk : * Running post-fs-data.d scripts
08-09 01:38:40.086 207 212 I Magisk : * Running module post-fs-data scripts
08-09 01:38:40.086 207 212 I Magisk : * Loading modules
08-09 01:38:40.086 207 223 I Magisk : * Starting MagiskHide
08-09 01:38:40.086 207 223 I Magisk : hide_utils: Hiding sensitive props
08-09 01:38:40.087 207 223 I Magisk : hide_list: [com.google.android.gms.unstable]
Does someone know what can be the reason for this problem and how I can solve it?
The fact that you have a Magisk log is a good sign.
You could try enabling "Preserve dm-verity" when patching the boot image to see if it makes a difference. Right now I can see you have it disabled. It's also possible that the "Preserve forced encryption" option could help, but be careful with this if you have previously removed encryption on your device. It'll re-encrypt...
Since you have a Magisk log, you could also try grabbing a logcat via ADB during boot, to see where it hangs.
Thank you very much for your reply.
I have patched the boot image with "Preserve dm-verity" enabled, but again it is stuck on the boot animation.
This is the log from Magisk Manager when patching the boot image:
Code:
- Copying image locally
- Target image: /data/data/com.topjohnwu.magisk/install/boot.img
- Device platform: armeabi-v7a
- Extracting files
- Unpacking boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
KERNEL [7094175]
RAMDISK [668173]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [91065cd3c70eaa74d173a4806f64db3b07f2b3c9]
DTB [23079]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
- Checking ramdisk status
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_21f9cec6deb5897d8707666e6b64e5c29055ed76.img.gz]
- Patching ramdisk
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[false]
Save SHA1: [21f9cec6deb5897d8707666e6b64e5c29055ed76] -> [.backup/.sha1]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Dump cpio: [ramdisk.cpio]
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
- Repacking boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
KERNEL [7094175]
RAMDISK [668173]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [91065cd3c70eaa74d173a4806f64db3b07f2b3c9]
DTB [23079]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
KERNEL [7094175]
RAMDISK [928008]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [8dd621ec0dbb737eeedadbf8b8681f6a04b6409b]
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Cleaning up...
****************************
Patched image is placed in
/storage/sdcard0/MagiskManager/patched_boot.img
****************************
- All done!
This is the /cache/magisk.log
Code:
08-09 12:30:31.285 203 203 I Magisk : ** Initializing Magisk
08-09 12:30:31.286 203 203 I Magisk : * Creating /sbin overlay
08-09 12:30:31.599 203 203 I Magisk : * Mounting mirrors
08-09 12:30:31.601 203 203 I Magisk : mount: /sbin/.core/mirror/system
08-09 12:30:31.601 203 203 I Magisk : link: /sbin/.core/mirror/vendor
08-09 12:30:31.601 203 203 I Magisk : bind_mount: /sbin/.core/mirror/bin
08-09 12:30:31.601 203 203 I Magisk : * Setting up internal busybox
08-09 12:30:31.686 209 209 I Magisk : Magisk v16.7(1671) logger started
08-09 12:30:31.687 206 206 I Magisk : Magisk v16.7(1671) daemon started
08-09 12:30:31.695 206 211 I Magisk : ** post-fs-data mode running
08-09 12:30:31.696 206 211 I Magisk : * Mounting /data/adb/magisk.img
08-09 12:30:31.912 206 211 I Magisk : * Running post-fs-data.d scripts
08-09 12:30:31.912 206 211 I Magisk : * Running module post-fs-data scripts
08-09 12:30:31.912 206 211 I Magisk : * Loading modules
08-09 12:30:31.913 206 222 I Magisk : * Starting MagiskHide
08-09 12:30:31.913 206 222 I Magisk : hide_utils: Hiding sensitive props
08-09 12:30:31.914 206 222 I Magisk : hide_list: [com.google.android.gms.unstable]
I have attached the logcat via ADB during boot. It seems that there is a pattern that repeats forever. Any thoughts?

Magisk Manager Flashing Problem

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

Unable to repack boot image

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.

Categories

Resources