Database Develop

[Help] Install Magisk without TWRP on xCover 4

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

Magisk is not installed after flashing patched_boot.img

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!

Magisk Installer Error

Hello. I'm using Android 8.1 arm64-v8
I'm downloaded the magisk manager for magisk modules but, gives the error:
- Detecting target image
- Device platform: arm64-v8a
- Downloading zip
... 0%
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.025 secs (42541120 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/dev/block/mmcblk0p21]
HEADER_VER [0]
KERNEL_SZ [31739573]
RAMDISK_SZ [1602279]
SECOND_SZ [0]
EXTRA_SZ [0]
RECOV_DTBO_SZ [0]
OS_VERSION [8.1.0]
PATCH_LEVEL [2018-09]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 androidboot.bootdevice=7824900.sdhci earlycon=msm_hsl_uart,0x78B0000 buildvariant=user]
CHECKSUM [70e61de5f33b76a1e4678c3bedd6ba760fba206d]
DTB [22328275]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
- Checking ramdisk status
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
! Boot image patched by unsupported programs
! Please restore stock boot image
! Installation failed
How to fix this? Thanks
Sorry my English.

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

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.

Update using Direct Install doesn't update Magisk

I am on a POCO M4 Pro (Fleur).
I have updated the Magisk App to 25100, and am trying to update Magisk (the system) to 25100.
I click "Update" and select "Direct Install (recommended)" and it appears to work:
- Target image: /dev/block/sdc34
- Device platform: arm64-v8a
- Installing: 25.1 (25100)
- Unpacking boot image
Parsing boot image: [/dev/block/sdc34]
HEADER_VER [2]
KERNEL_SZ [10700167]
RAMDISK_SZ [20106515]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
DTB_SZ [130308]
OS_VERSION [11.0.0]
OS_PATCH_LEVEL [2022-04]
PAGESIZE [2048]
NAME []
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [c8138edce860b616048123e7d5f3ead3b3c3d79a000000000000000000000000]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
VBMETA
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Magisk patched boot image detected
Loading cpio: [ramdisk.cpio]
Remove [.backup]
Remove [.backup/.magisk]
Remove [overlay.d]
Remove [overlay.d/sbin]
Remove [overlay.d/sbin/magisk32.xz]
Remove [overlay.d/sbin/magisk64.xz]
Remove [.backup/.rmlist]
Move [.backup/init] -> [init]
Dump cpio: [ramdisk.cpio]
- Patching ramdisk
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Create directory [overlay.d] (0750)
Create directory [overlay.d/sbin] (0750)
Add entry [overlay.d/sbin/magisk32.xz] (0644)
Add entry [overlay.d/sbin/magisk64.xz] (0644)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Record new entry: [overlay.d] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk32.xz] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk64.xz] -> [.backup/.rmlist]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
Loading dtbs from [dtb]
- Repacking boot image
Parsing boot image: [/dev/block/sdc34]
HEADER_VER [2]
KERNEL_SZ [10700167]
RAMDISK_SZ [20106515]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
DTB_SZ [130308]
OS_VERSION [11.0.0]
OS_PATCH_LEVEL [2022-04]
PAGESIZE [2048]
NAME []
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [c8138edce860b616048123e7d5f3ead3b3c3d79a000000000000000000000000]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
VBMETA
Repack to boot image: [new-boot.img]
HEADER_VER [2]
KERNEL_SZ [10700167]
RAMDISK_SZ [20137863]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
DTB_SZ [130308]
OS_VERSION [11.0.0]
OS_PATCH_LEVEL [2022-04]
PAGESIZE [2048]
NAME []
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [f8b2da7b9c90934ce9d6a95c40f017fc576840f9000000000000000000000000]
- Flashing new boot image
RULESDIR=/dev/cyEUC5/.magisk/mirror/metadata/magisk
- All done!
Click to expand...
Click to collapse
So I click "Reboot" and the phone reboots. I open the Magisk app and I'm given the "Requires Additional Setup" message because the Magisk version doesn't seem to have updated:
{
"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"
}
Does anyone know why this doesn't work?
I have updated manually by:
- flashing the stock boot.img using fastboot
- patching the stock boot.img using Magisk
- flashing the patched boot.img using fastboot
I'd rather not have to do this every time.

same thing here. same action taken.
Lenovo Tab M10 HD TB-X306X
TB-X306X_S230294_220517_BMP

Could you add your device to the issue on GitHub to highlight the bug and aid in debugging?
Direct Install reports success but doesn't update Magisk · Issue #6051 · topjohnwu/Magisk
Device: POCO M4 Pro (Fleur) Android version: 11.0.0 Magisk version name: 9183a0a Magisk version code: 25101 I am trying to update to v25.1 so I update the Magisk App to the most recent debug build,...
github.com

i couldn't. new guy

Ah that's a shame! I'll note your device and link here.

tq sir

just to reinstate.
im having the same issue.
Lenovo Tab M10 HD TB-X306X
TB-X306X_S230294_220517_BMP
Android 11.
now using magisk 24.3 without any glitch.
unable to update to 25.1.
requires additional setup loop.
sigh.
please help

Can you reflash your stock boot.img, install Magisk 25.1, use it to patch your stock boot.img then flash that patched img?

yup, i am thinking of doing it later today.....my last resort before i accept the fate that this tab will be stuck with magisk 24.3 forever. thank you sir.

i will let u know the outcome

aricooperdavis said:
Can you reflash your stock boot.img, install Magisk 25.1, use it to patch your stock boot.img then flash that patched img?
Click to expand...
Click to collapse
yes sir. it works!!!! thank you so much. salute!!!

Yep same issue.. On Lenovos the Direct method does NOT work..