[Discussion] Magisk Delta - Another unofficial third-party Magisk fork

[zgfg]

Thanks a lot !

Of course I read the official instructions but I want to be sure it was also simple

Do I have to uninstall the manager of Magisk stable before install the one of Delta ?

Yes, Magisk Delta comes with different package name, hence its app will not replace/update the official Magisk app (manager)

 

[crypticc]

came back overnight thanks

 

[crypticc]

Yes, Magisk Delta comes with different package name, hence its app will not replace/update the official Magisk app (manager)

I did mine after. But yes, at some point you need to uninstall the other apk

 

[uschipower]

I just installed and TrebleDroid-GSI on a TB-X605F.
Where do I find a compatible Version of Delta Magisk which can be used with TD-GSI?

After I had successfully installed GSI, I made a backup of all partitions with TWRP.
I installed DeltaMagisk-Apk and selected the boot-partition-file from TWRP-backup for Patching DeltaMagisk.
Then I installed the patched boot, but Device will not start with this boot-file.

Whan can I do?
Where did I make a mistake?

 

[Roidred]

I just installed and TrebleDroid-GSI on a TB-X605F.
Where do I find a compatible Version of Delta Magisk which can be used with TD-GSI?

After I had successfully installed GSI, I made a backup of all partitions with TWRP.
I installed DeltaMagisk-Apk and selected the boot-partition-file from TWRP-backup for Patching DeltaMagisk.
Then I installed the patched boot, but Device will not start with this boot-file.

Whan can I do?
Where did I make a mistake?

you should try to rename the file from .apk to .zip and then flash the same file from twrp itself.

 

[uschipower]

you should try to rename the file from .apk to .zip and then flash the same file from twrp itself.

just tried this way too, do everything in TWRP.
The device doesnt boot any more after DeltaMagisk has modified boot-partition

Whan can I do?
Where did I make a mistake?

 

[zgfg]

just tried this way too, do everything in TWRP.
The device doesnt boot any more after DeltaMagisk has modified boot-partition

Whan can I do?
Where did I make a mistake?

Use the same boot.img that you patched, but the original, not patched img file

And flash to restore. There will be no Magisk but the phone should boot if it was indeed the correct/corresponding boot.img from your ROM

 

[uschipower]

Use the same boot.img that you patched, but the original, not patched img file

??
For GSI-Image, I have downloaded a *.xy-File to PC and extracted it. There was a *.img-File in archieve.
I flashed this *.img to "system" with TWRP.

You think of I should extract boot-partition from *.img-File?
How does this work?

Or do you think of boot.img from stockRom which is basis for GSI-Images?

 

[zgfg]

??
For GSI-Image, I have downloaded a *.xy-File to PC and extracted it. There was a *.img-File in archieve.
I flashed this *.img to "system" with TWRP.

You think of I should extract boot-partition from *.img-File?
How does this work?

Or do you think of boot.img from stockRom which is basis for GSI-Images?

Generally, System and Boot are different partitions and flashing System image to Boot partition is a way to brick the phone

However, in that case Magisk should have recognized that the given img file cannot be patched and should have printed an error (did you watch what Magisk wrote when patching!) - but there should be also no patched img then

Anyway, instead of flashing permanently the img file (patched or not) to Boot, it is always good to test it first by one-time booting to:
fastboot boot <IMG file>

Now, to un-brick, you should try to dirty-flash the ROM again, it should fix your Boot partition

Btw, ROMs may come with the compound payload.bin and one must use Payload Dumper to extract particular images - but again, Magisk should IMO report an error when trying to patch the payload.bin

 

[uschipower]

However, in that case Magisk should have recognized that the given img file cannot be patched and should have printed an error (did you watch what Magisk wrote when patching!) - but there should be also no patched img then

I do not patch img, i install gsi-img over stockrom. And then, I made a backup of boot partition with TWRP. This file I used for patching with DeltaMagisk.
This patched boot partition file do not work

Now, to un-brick, you should try to dirty-flash the ROM again, it should fix your Boot partition

I do not have to make a dirty flash. I restore unpatched boot from TWRP and device does boot.

Generally, System and Boot are different partitions and flashing System image to Boot partition is a way to brick the phone

Do GSI-Images only modify system partition, do they not contain boot partition?

If yes, boot-partition is part of stock rom, not GSI-Image part, right?

As far as i know, Magisk and DeltaMagisk only modify boot partition.
When I flash stockrom without GSI, DeltaMagisk can modify boot partition and device can boot.

When flashed GSI, it should be still the same boot partition. But when I modify boot partition the same way, device doesnt boot.
So i suppose there is a problem with GSI



When using official magisk, there is a notice that for GSI-Images you have to use a special version:

Magisk-Phh

Magisk fork with some addition needed for phh-treble gsis. - Magisk-Phh

github.com

As you can see, the main developer of GSI/TrebleDroid, Phh, made the last version 2 years ago. Now he is retired in that project.
I suppose, he never made a modified Delta-Magisk version.
So it would be kindly if HuskyDG makes a Version working with GSI-Images.

 

[Abdul ssaleh]

Please how do I get rid of this third party

 

[pndwal]

I do not patch img, i install gsi-img over stockrom. And then, I made a backup of boot partition with TWRP. This file I used for patching

This is a good method... Will always get matched image...

I do not have to make a dirty flash. I restore unpatched boot from TWRP and device does boot.

When flashed GSI, it should be still the same boot partition. But when I modify boot partition the same way, device doesnt boot.

Did you try with patched image made without GSI?... See comments below re wipes needed too...

So i suppose there is a problem with GSI

Yup, these need special fixes in Magisk it seems... More below...

When using official magisk, there is a notice that for GSI-Images you have to use a special version:

Magisk-Phh

Magisk fork with some addition needed for phh-treble gsis. - Magisk-Phh

github.com

As you can see, the main developer of GSI/TrebleDroid, Phh, made the last version 2 years ago. Now he is retired in that project.
I suppose, he never made a modified Delta-Magisk version.
So it would be kindly if HuskyDG makes a Version working with GSI-Images.

Doubt you need that old mod of Magisk 23.0... many GSI compatibility fixes (and newer GKI and other Treble compatibility fixes) have been added in official Magisk since (like this important one: Skip loading Magisk when detecting DSU)... In the past Magisk was basically incompatible with GSIs... Some issues likely still exist... Some users find phh builds are more difficult to get to boot than Google GSIs, even w/o Magisk patching... Apparently wiping /data, dalvik etc is often needed to get Magisk booting w/ GSIs...

Try wipes, try a Google GSI for comparison... PW

 

[kevinco1]

Delta in the future needs to be updated with fixes to work with GSIs properly. PHH builds do not install Delta properly for me as well as various other GSI builds

 

[uschipower]

It happened again.
Tan-App for german bank comdirect found a way to detect root again.

comdirect photoTAN App - Apps on Google Play

for free TANs

play.google.com

they released a new version a few days ago.

Would you be so kindly and fix the detection again?

 

[zgfg]

It happened again.
Tan-App for german bank comdirect found a way to detect root again.

comdirect photoTAN App - Apps on Google Play

for free TANs

play.google.com

they released a new version a few days ago.

Would you be so kindly and fix the detection again?

I can get up to the following with Delta, Zygisk, SuList, Sensitive Props and App Data Isolation

I have kein Konto to continue

 

[eliezerjk90]

It happened again.
Tan-App for german bank comdirect found a way to detect root again.

comdirect photoTAN App - Apps on Google Play

for free TANs

play.google.com

they released a new version a few days ago.

Would you be so kindly and fix the detection again?

Change the filename of /system/addon.d/99-magisk.sh to anything that doesn't contain magisk. Reboot and it will work

 

[useroso987]

Hi, i just installed LineageOS 20 and will proceed to root.

Should i take Official or Delta one?
Is there any list of differences between them?

Thanks.

 

[Timmmmaaahh!]

Hi, i just installed LineageOS 20 and will proceed to root.

Should i take Official or Delta one?
Is there any list of differences between them?

Thanks.

No silver platters here
It's a personal preference. For some applications, official will work better, for others Delta will do the trick. Why don't you just try the one that seems best to you, it's possible to switch later. Also, read the documentation and FAQ, those will likely answer most of your questions.

 

[shadyrexman]

Pixel 6 Pro T3B2 here, tried many times to root my p6p and failed , I patched the p7p boot.img and fastboot it, after restarted and I press direct install. After reboot then the root is gone. Any suggestions? Thanks a lot .

 

[zgfg]

Pixel 6 Pro T3B2 here, tried many times to root my p6p and failed , I patched the p7p boot.img and fastboot it, after restarted and I press direct install. After reboot then the root is gone. Any suggestions? Thanks a lot .

On your screenshot it says:
Magisk
Installed Delta 25210
Zygisk Yes
Ramdisk Yes

Hence, as per that screenshot, Magisk (and the root) is installed