yashsingh1/xdaforums huggingface dataset:
[Magisk] jcmm11:
If you want to try and pursue this further you'll need a logcat showing exactly what's happening. It is, however, a longshot at this point.

You should, however, be able to use adb backup and restore to do what you want. It's been a long time since I used it but you should be able to back up apps + data to your PC and then restore them, without needing root.
[Magisk] mj084:
Hello,

need some help with patching boot image from Samsung Galaxy S7 (Stock Oreo Firmware)

Extracted boot.img.lz4 from downloaded firmware via ODIN - unpacking was successfull but repacking fails - see the logs...

Wrong boot image or whats the error?

- Copying image locally
- Target image: /data/user_de/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_de/0/com.topjohnwu.magisk/install/boot.img]
KERNEL [33053088]
RAMDISK [4564219]
SECOND [4043309312]
EXTRA [654314440]
PAGESIZE [8]
OS_VERSION [41.68.0]
PATCH_LEVEL [2000-01]
NAME [RPOI17A000KU$]
CMDLINE []
CHECKSUM [675ab2650018cbbf8863f2f513959ae1010054a500068ba6004891c60400d154]
DTB [14406282]
Segmentation fault
- Checking ramdisk status
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_c1b24eb74c3dfea107851f69c82fecae9e24c630.img.gz]
cp: can't stat 'ramdisk.cpio': No such file or directory
- Patching ramdisk
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]
Save SHA1: [c1b24eb74c3dfea107851f69c82fecae9e24c630] -> [.backup/.sha1]
Record new entry: [init] -> [.backup/.rmlist]
Dump cpio: [ramdisk.cpio]
- Repacking boot image
MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
KERNEL [33053088]
RAMDISK [4564219]
SECOND [4043309312]
EXTRA [654314440]
PAGESIZE [8]
OS_VERSION [41.68.0]
PATCH_LEVEL [2000-01]
NAME [RPOI17A000KU$]
CMDLINE []
CHECKSUM [675ab2650018cbbf8863f2f513959ae1010054a500068ba6004891c60400d154]
DTB [14406282]
Segmentation fault
! Unable to repack boot image!
Failed!
! Installation failed
[Magisk] Lownita:
What's the easiest way to uninstall a magisk module from recovery if boot fails?
[Magisk] romantissm:
https://xdaforums.com/showpost.php?p=72542167&postcount=242
[Magisk] Didgeridoohan:
Segmentation fault... Have you tried changing to the beta update channel and see if v16.7 works?

Personally I prefer the Mount Magisk zip. But, I do like to be very hands on.

Besides the linked module uninstaller above, and the Mount Magisk script, there's also the Manager for recovery.

Pick whatever suits you best...
[Magisk] mj084:
Same:/

- Copying image locally
- Target image: /data/user_de/0/com.topjohnwu.magisk/install/boot.img
- Device platform: arm64-v8a
- Extracting files
- Unpacking boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
KERNEL [33053088]
RAMDISK [4564219]
SECOND [4043309312]
EXTRA [654314440]
PAGESIZE [8]
OS_VERSION [41.68.0]
PATCH_LEVEL [2000-01]
NAME [RPOI17A000KU$]
CMDLINE []
CHECKSUM [675ab2650018cbbf8863f2f513959ae1010054a500068ba6004891c60400d154]
Invalid DTB detection at 0x11c8716: header tag of first node != FDT_BEGIN_NODE
Invalid DTB detection at 0x11d97e6: header tag of first node != FDT_BEGIN_NODE
Invalid DTB detection at 0x11ea63b: header tag of first node != FDT_BEGIN_NODE
Invalid DTB detection at 0x11fb48d: header tag of first node != FDT_BEGIN_NODE
Segmentation fault
- Checking ramdisk status
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_c1b24eb74c3dfea107851f69c82fecae9e24c630.img.gz]
cp: can't stat 'ramdisk.cpio': No such file or directory
- Patching ramdisk
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]
Save SHA1: [c1b24eb74c3dfea107851f69c82fecae9e24c630] -> [.backup/.sha1]
Record new entry: [init] -> [.backup/.rmlist]
Dump cpio: [ramdisk.cpio]
- Repacking boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
KERNEL [33053088]
RAMDISK [4564219]
SECOND [4043309312]
EXTRA [654314440]
PAGESIZE [8]
OS_VERSION [41.68.0]
PATCH_LEVEL [2000-01]
NAME [RPOI17A000KU$]
CMDLINE []
CHECKSUM [675ab2650018cbbf8863f2f513959ae1010054a500068ba6004891c60400d154]
Invalid DTB detection at 0x11c8716: header tag of first node != FDT_BEGIN_NODE
Invalid DTB detection at 0x11d97e6: header tag of first node != FDT_BEGIN_NODE
Invalid DTB detection at 0x11ea63b: header tag of first node != FDT_BEGIN_NODE
Invalid DTB detection at 0x11fb48d: header tag of first node != FDT_BEGIN_NODE
! Unable to repack boot image!
Segmentation fault
Failed!
! Installation failed

Edit:

mistake found --> since Oero, Samsung compressed FW-files with lz4 --> decompressed it to get real boot.img --> patching and repacking done --> flashed it via AP in ODIN --> no more boot --> reset was recommended:eek:

flashed whole AP via ODIN --> booting fine and all data there :)
[Magisk] barrack1:
How to I install the beta version of the Magisk framework (16.7 currently) without breaking OTA? Because 16.0 causes bootloops which is solved by the beta version. If I were to install Magisk using the "direct" method, it will download+install 16.0 automatically (instead of 16.7beta).

Installing it via flashing the 16.7 zip would modify the system partition and break OTA would it not?
[Magisk] Didgeridoohan:
Installing Magisk won't modify /system, no matter what way you use (direct, patching boot image, zip, recovery).

For your query, take a look in the Manager settings - Update Channel.
[Magisk] jenslody:
No installing directly does the same as installing via Manager.

But to install the beta, just switch to beta channel in the update-channel settings in MagiskManager's settings.
[Magisk] barrack1:
Thanks for the help.

How is it possible for flashing the Magisk framework zip not to affect /system? I thought I saw /system, /vendor being modified in the TWRP logs.
[Magisk] DanGLES3:
Magisk will just patch the boot.img but it needs to mount the /system /vendor so it can get their mount points it won't actually modify the system
[Magisk] DroidJP:
I pretty much given up on trying to get helium to work with magisk and just stick to using adb backup instead. (which is awesome actually) The only catch is adb does have one rule that the app developer can turn on or off at will in their apps. Basically, they can disallow their apps from adb backups.

You will still see the app in helium but will refuse to backup if this rule is in place. So far the apps i have that are disallowed are one banking app and netflix and even smart switch. But all my games are adb allowed....yet lol. All it takes is an app update to change this rule.

Well, at least got magisk to be triggered by the app by symlinking. Progress made at least lol

Thanks for your help.

One more thing, since my phone is rooted. Is there a way to keep or enable adb backup for helium without having to connect to a pc every time on reboot? Been trying to logcat the moment it activates the app but no dice. All i know that usb debugging must be enabled for the desktop app to send the command for it to work.

Once again, thanks
[Magisk] guest4711:
Boot into TWRP, open a terminal. Enter the command as shown, finish by pressing enter/return

touch /cache/.disable_magisk

. Then reboot. Magisk starts without loading any module ("core only mode"). Now you may disable the culprit(s) in MagiskManager, disable "core only mode" in settings of MM and reboot.

If you like more comfort: Install "Magisk Manager for Recovery" as a standard module, so you may disable and enable modules in TWRP...
[Magisk] Lownita:
That's great to know, thanks!
[Magisk] Dreamer(3MF):
In-Case Of Facing A Bootloop Issue Due To Flashing Any Module, Use The Following Module CoreOnlyMode4Magisk From This Thread https://xdaforums.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366.
[Magisk] yochananmarqos:
Thing is, Magisk Manager won't let you disable modules in core only mode because technically they're already disabled. I just ran across this the other day.
[Magisk] guest4711:
So you have to disable "core only mode" after restart, then disabling the modules ... (without restarting in between)
[Magisk] crows:
Hi hope I'm not posting in the wrong thread..if so please disregard my post.

I've read the basic trouble shooting guide and did the things that were suggested but still have issues with one app.

The app is called optus sport and is a subscription service for viewing sport.

The problem I have is that it works on one custom Rom with magdisk (Repulse Rom) but not on DrKetan Rom for Note 8.is there something I can test that will assist with what is causing the issue. The issue is only when trying to stream video. I'm hoping because it's working on one it may assist in fault finding whether it's a magdisk issue or the Rom.

Thanks
[Magisk] Dreamer(3MF):
Yes, But You Need After Removing/Disabling The Modules Which Caused The Bootloop/Issue To Reboot The Android To Load The Rest Of Modules. Kindly Check This Thread https://xdaforums.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366.
[Magisk] BurnedDrake:
Why not use titanium backup?
[Magisk] hungvip2001:
Hi guys, which modules can boost my phone 's performance, gaming experience? Thank you.
[Magisk] martyfender:
I'm not sure about modules, but lspeeds performance profiles combined with tuning in Kernel Aduitor,

may

help you.

https://xdaforums.com/apps/l-speed/tweak-l-speed-v1-0-02-02-2015-t3020138
[Magisk] Immortal0907:
Yo guys, my phone is not encrypted but "Preserve force encryption" is checked in Magisk Manager. So sould I disable it or something ? My device is Redmi Note 4 Snapdragon running Miui 9 and TWRP. I used also some script to disable dm-verity after flashing TWRP if its somehow rilated to this.
[Magisk] Coldstream:
Magisk 16.0, 16.4, 16.6 and 16.7 all cause a bootloop on every treble ROM with my device, a Moto G6 Plus. Stock ROM gives no problems with Magisk at all. Any ideas what i can try?
[Magisk] Pkt_Lnt:
The troubleshooting guide states that clearly.

https://www.didgeridoohan.com/magisk/MagiskHideHelp
[Magisk] DroidJP:
It is a nice app and can replace all other backup and restore apps hands down and the ability to restore adb backups from non rooted devices, and restore from nandroid backups.I will definitely give titanium backup a try and maybe go pro if i like it.

But Despite all this, i will still need helium to be able to restore to non rooted devices when it is time for an upgrade. This is assuming if helium will work on oreo or android p.
[Magisk] BurnedDrake:
Titanium Backup can also create a flashable zip of you app backups so you can flash them in recovery
[Magisk] DiamondJohn:
Sorry for OT. but in the past I also used a little free app called ZipME to create flashable zips not just of apps/data but also for extra files such as my GPS.conf and init scripts etc.
[Magisk] Coldstream:
Okay here is it with the template from the website,

The things i did, i tried flashing Magisk 16.0, Magisk 16.4, Magisk 16.6 and Magisk 16.7 on quite a few Treble roms.

They all end up getting a bootloop with the simple Moto logo, i suspect the ROM simply doesn't start anymore after flashing TWRP.

With the stock rom i can patch the boot image just fine, and magisk has no problems at all..

For the details: Moto G6 Plus, trying magisk on basically every CGI rom, All Android 8.1 based, Stock gives no problems with Magisk.

Tried flashing straight after flashing the ROM, tried flashing after ROM was flashed and booted, nothing works.

Logcat of booting is not possible, waiting for device.

There is also no Magisk log in /cache

All i can supply, as attachment is the instalation logcat from flashing it with TWRP.

I have no idea what i can try, it seems that there are quite a few errors with installing though.

Edit: patched original boot.img all possible ways with manager, all stuck at moto logo / bootloop

I probably van get the recovery log through adb or TWRP, but i don't know what is needed.. i would be happy with any help, magisk works on none of the treble roms right now for Moto G6 Plus...
[Magisk] martyfender:
Maybe this is not true for all devices, but when I flash Magisk on my devices, encryption and dm_verity are disabled, by default. I, however, had encryption disabled before I ever flashed Magisk for the first time, back at the first of year, so I am not sure how it behaves if you didn't format data and cache in fastboot, or do a factory reset, before reboot. I do however know that to decrypt a device, the encrypted userdata must be deleted for a new, unencrypted data partition to be created, after reboot.
[Magisk] angelillom:
Sorry I use Google translator

Perdon utilizo traductor Google

Install Magisk 16.0 version in my Huawei P20 Lite by Minimal ADB fastboot, I also have TWRP installed in the same way since it is a new mobile and I fail the SafetyNet, I worked in a test but now it fails ctsProfile: false and basicintegrity: false, Without Xposed installed

There's a solution ?

Please Help and THANK YOU

Instale Magisk 16.0 version en mi Huawei P20 Lite por Minimal ADB fastboot ,tambien tengo TWRP instalado de la misma manera ya que es un movil nuevo y me falla el SafetyNet , me funciono en una prueba pero ahora falla ctsProfile:false y basicintegrity:false , sin Xposed instalado

¿Hay solución ?

Porfavor Ayuda y MUCHAS GRACIAS
[Magisk] martyfender:
Since this is an English only forum, why do you also post the Spanish? Just copy and paste the English, please.

Thanks
[Magisk] Dreamer(3MF):
To Fix Uncertified Status In PlayStore & Pass The SafetyNet, Download DeviceSpoofingTool4Magisk From This Thread https://xdaforums.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435 & Do What Are Mentioned In The General Steps.

For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To The Latest Version Which Is Currently v16.7(1671).
[Magisk] BillGoss:
As per the rules (#4): "You're free to include your original message in your own language, below the English translation."

Including the original is often helpful when Google Translate does a poor job. It also can provide clarity. For example "instale" was translated as "install" but the correct translation is "I installed".
[Magisk] lupix7:
Goodmorning everyone. I installed the Dr. Keran 011P Rom with root Magisk and Magisk Manager 5.8.3, safety net works perfectly with Magisk v. 16.7.In Magisk Ide I put the apk to which I intend to hide the root but with 2 apk I can not hide it and make it work ... These are: Timvision (streaming Italian film) - Premium Play (streaming film serietv etc. Italian). If someone has already solved with these apk can give me help, or help me to make them work because they are not very practical with Magisk ... Thanks
[Magisk] cmch:
i dont know if this is the right place to ask this question but can u please tell me how to install xposed module

i have magisk beta latest version

miui9.6.x global stable rom

redmi 3s marshmallow os
[Magisk] Coldstream:
Any chance u can help me, i've posted some details and log file
[Magisk] Didgeridoohan:
This would be the place to ask:

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268

But as far as I've seen, MIUI and Xposed don't mix very well.

Moto G6 Treble? Sounds like a ROM incompatibility... But you've already figured that.

The recovery log or Manager installation log, together with the stock and patched boot image might help in figuring things out.
[Magisk] Coldstream:
Yes, Moto G6 Plus, EVERT, i'll get the logs and will post them, had to relearn a thing or two last night haha, anyway i will post them.
[Magisk] LucasNoob:
Universal Ambient Display

For users as me using LeEco. Branded software 6.0 marshmallow is not possible to get ambient Display on. I looking for someone who know how to make it work for me and loot of user ( China LeEco 1.300 milions users... There is loot of people around the world else...... My phone led is too small ?
[Magisk] Coldstream:
Here are a few logs, i included the magisk bak because that might give more info from when it's booting..

i have the Boot files uploaded to my gdrive..

Thanks for the effort

edit: renamed the backup .bak to .bak.log, i think that's a log when it was booting, and freezing.. Not sure, but that's what i think?

I've also included a logcat from the TWRP flashing.
[Magisk] DroidJP:
Question. Is there a way to keep the advanced settings in magisk manager active when offline? I realized boot patching only works when there is an internet connection. Should have a secondary way of patching offline if you have the magisk flash zip at hand.

Just a thought. Awesome job of what magisk has become. Keep it up[emoji106][emoji106]
[Magisk] Mateus109:
Santander app seems to have stopped working; recognises rooted phone. All other banking apps still OK. (Magisk v16 5.8.3)
[Magisk] jcmm11:
Try 16.7. Hide Magisk Manager if plain Magisk Hide doesn't work. Make sure that after applying Magisk settings you force stop the Santander app and delete it's data before restarting it. (Apps sometimes store the results of a root check rather than checking every time).

For more information see https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] angelillom:
HUAWEI P 20 Lite ROOT

All repaired , installed and works well, THANK YOU for your help, sometimes the translator changes the phrases and is not well understood, that's why I put the translation

I repeat THANK YOU

Todo reparado , instalado y funciona bien ,MUCHAS GRACIAS por tu ayuda , en ocasiones el traductor cambia las frases y no se comprende bien , por eso pongo la traduccion

Repito GRACIAS
[Magisk] Elvisnazareth:
Hi I had installed 16.4 magisk and Lloyds and Halifax worked for a while on my rooted ramrom note.Suddenly both apps stopped working (hadn't even updated any app). Have updated magisk 16.7 and still the apps won't work. Tried all combos as per https://www.didgeridoohan.com/magisk/MagiskHide

Still no success. Any help most welcome.

Android pay works tho.
[Magisk] J4jks:
After reboot all module disappear and after other they load normally, on my Moto G 2,encrypted data,, los 14.1, Magisk 16

Log is shown below

01-09 02:46:04.650 205 205 I Magisk : Magisk v16.0(1600) daemon started

01-09 02:46:04.656 205 210 I Magisk : post-fs mode running

08-05 13:45:37.384 205 454 I Magisk : late_start service mode running

08-05 13:45:37.386 205 454 I Magisk : * Running service.d scripts

08-05 13:45:37.386 205 454 E Magisk : opendir: /sbin/.core/img/.core/service.d failed with 2: No such file or directory

08-05 13:45:37.386 205 454 I Magisk : * Running module service scripts

08-05 13:45:38.246 471 471 E Magisk : read failed with 104: Connection reset by peer

08-05 13:45:38.371 505 505 I Magisk : * Creating /sbin overlay

08-05 13:45:38.374 505 505 I Magisk : * Mounting mirrors

08-05 13:45:38.375 505 505 I Magisk : mount: /sbin/.core/mirror/system

08-05 13:45:38.375 505 505 I Magisk : link: /sbin/.core/mirror/vendor

08-05 13:45:38.380 505 505 I Magisk : bind_mount: /sbin/.core/mirror/bin

08-05 13:45:38.380 505 505 I Magisk : * Setting up internal busybox

08-05 13:45:38.472 505 505 I Magisk : Magisk v16.0(1600) daemon started

Any Workaround for this?
[Magisk] breacherman:
I'm pretty new to magisk, this may be a known issue, even though a search didn't come up with any results.

I keep having to reinstall magisk on my rom, because apparently it's corrupted, unable to install modules etc. The issue, and I've done this 3 times to make sure, magisk uninstaller keeps encrypting my data, rendering twrp half useless for me. So, every time I reboot after flashing uninstall zip, "preserve force encryption" is checked on the main magisk screen. I always checked b4 hand to make sure it wasn't ticked b4 I ran the uninstaller. Would be surprised if this wasn't a known issue....
[Magisk] Didgeridoohan:
Try uninstalling and reinstalling. You could also give the v16.7 beta a shot, it has quite a few improvements over v16.0.

The uninstaller in itself won't encrypt your data.

Magisk can patch the forced encryption flag, meaning you'll be able to format /data and it won't be encrypted after that. As soon as you run the uninstaller, the stock boot image (with the forced encryption flag enabled) will be flashed to your device and on the subsequent reboot your device will be encrypted. Only way to remove encryption again would be to patch the encryption flag (with Magisk or another zip) and then format /data.

The check box in the Magisk Manager will only do something when you're patching a boot image or doing a direct install. When uninstalling it does nothing... In recovery you can run this in the recovery terminal before flashing the Magisk (installer) zip, to disable the encryption flag:

echo KEEPFORCEENCRYPT=false>>/cache/.magisk
[Magisk] breacherman:
The uninstaller in itself won't encrypt your data.

Magisk can patch the forced encryption flag, meaning you'll be able to format /data and it won't be encrypted after that. As soon as you run the uninstaller, the stock boot image (with the forced encryption flag enabled) will be flashed to your device and on the subsequent reboot your device will be encrypted. Only way to remove encryption again would be to patch the encryption flag (with Magisk or another zip) and then format /data.

The check box in the Magisk Manager will only do something when you're patching a boot image or doing a direct install. When uninstalling it does nothing... In recovery you can run this in the recovery terminal before flashing the Magisk (installer) zip, to disable the encryption flag:

echo KEEPFORCEENCRYPT=true>>/cache/.magisk

[/QUOTE]

Thanks for the reply.

That was a lot to digest, I believe I mostly understand. SO by the "recovery terminal" do you mean the one under advanced in twrp? If so, I did enter your command line, and I'm getting the message "sh: can't create /cache/: Is a directory" I do something wrong? I'm quite sure I entered the command correctly.

And one other question, even though you indicate that it isn't the magisk uninstaller that's encrypting my data, is there no way for me to run that zip (in the future) with out the encrypting taking place?
[Magisk] jenslody:
Did you type the command correctly?

Note: the ".cache" is part of the command.
[Magisk] Didgeridoohan:
Don't reboot until you've flashed something that disables forced encryption (Magisk, noencrypt zip, custom kernel, etc).

You could try flashing a noencrypt zip before flashing Magisk. That way the backup boot image that will be restored when flashing the uninstaller will also have the flag disabled. Also a good idea to keep your own backup of the completely stock boot image...
[Magisk] breacherman:
Ahh ok that's what I was looking for, "Don't reboot until you've flashed something that disables forced encryption". I had been rebooting after flashing uninstall zip. I already had a backup ready so I just wiped data, installed backup, flashed uninstaller followed by Magisk. Good to go now, thanks man.
[Magisk] martyfender:
I would like to emphasize something that you stated, that some users don't seem to understand.

Some are under the mistaken belief that their existing data will some how be magically unencrypted. That is not the case. Only by deleting the data partition, can a new, unencrypted partition be created, on reboot, with the encryption flag and dm_verity disabled in the boot.img, by Magisk, or other means, such as AIK. So the backup of important data is a must.

To disable forced encryption, shouldn't the above command be:

echo KEEPFORCEENCRYPT=false>>/cache/.magisk