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

[pndwal]

Question - What is the safe/proper way of proceeding on Pixel 6 pro?
First run after boot, Magisk Delta asks for additional configuration steps to be done and gives following options:

1. Choose and patch file ( bootloader is locked with avbroot and I don't know how then incorporate patched file into OTA, as only OTA can be sideloaded).
2. Direct installation (recommended).
3. Install in inactive slot (after OTA).

Normal Magisk (not Delta) raise same request to perform additional tasks but didn't give any options, hence am unsure which one should I proceed with (tend to think about direct). With that said, it could be third (after OTA) as effectively I did sideload OTA.

Thanks for help!

....

Android Flash tool fails as it tries to unlock bootloader, which fails. I've tried from fastboot level directly.
The OEM Unlocking hasn't been touched (and should be enabled - allowing unlock).
For whatever reason it looks like it simply doesn't work. Not sure why - the only thing which did happen was that run of Magisk additional steps straight after which the system has been bricked.

Yes, I can't get to recovery either.

Do I have a hard brick now? Can I do maybe anything from fastboot level (having all images, including signed ones)?

Just now trying to understand your issue...

Seems this may have complicated by several unusual factors...

Please confirm:

Do you have Magisk installed using avbroot script and bootloader re-locked with custom keys registered?... Saw you mentioned that in other thread but can't see it mentioned here...

Did you also take Install → Install to Inactive Slot in Magisk App?... This is broken at least for late P6 and P7 ROMs as update engine now checks partition digests and will mark the partition as corrupted... Pixel users on recent ROMs have been avoiding this installation method for a while now...

... If you used avbroot it seems boot, recovery, or vendor_boot image may all be patched (to replace the OTA signature verification certificates with the custom OTA signing certificate) in addition to boot or init_boot being patched with magiskinit...
- Also, if OEM unlocking is disabled with locked bootloader and root when system became corrupt device is 'hard bricked' (fastboot flashing unlock will not be allowed)... From what you say you shouldn't be facing this however, unless you use a mod that messes with OEM Unlocking setting... Apparently some forks of USNF do disable this but @kdrag0n disapproved a merge request in official USNF...
- Regardless of OEM Unlock you can't perform 1) a regular (unpatched) A/B OTA update (you should have blocked this via a Magisk module etc) or 2) take the Direct install method for updating Magisk (Magisk updates must be done by repatching) or device will become unbootable and unrecoverable without unlocking the bootloader again (and thus, triggering a data wipe)...
https://github.com/chenxiaolong/avbroot#warnings-and-caveats

Further to avbroot pitfalls, if you're on Android 13 QPR2 Beta 1 (T2B1.221118.006) or later Betas (and possibly even latest stable), Magisk patching boot IMG has been failing due to Compression method of ramdisk in Pixel 6 boot image is incorrect #6441. This has meant that P6 series Beta ROM users have needed to use/patch a corresponding P7 series boot.img (yes, boot.img not initboot.img... Magisk actually adds the missing generic ramdisk) to have working Magisk... So P6 pro users would patch/flash boot.img from corresponding P7 pro Beta build...
- This issue was deemed by Magisk Devs a Google issue not to be fixed in Magisk, but this has just changed with this fix for the incompatible compression algorithm merged only hours ago: Force ramdisk format to lz4_legacy for v4. So with 25211, P6 users should no longer need to patch P7 images to use Magisk...

I have no experience with Pixel device at all, but as long as you haven't disabled OEM Unlocking it seems to me:
- You should be able to recover device at least by unlocking bootloader and fastboot flashing with factory reset (if OEM Unlocking is enabled)...
- You may even be lucky enough to be able to (dirty) flash without unlocking or data wipe if you have carefully avoided any operation that causes an unsigned or differently-signed boot image to be flashed.

Magisk with a locked bootloader was always going to be fraught (trouble)... Hopefully the above notes will be helpful however...

And Pixel users will be better able to advise on recovery options... PW

 

[shoey63]

@dkadds2
It seems that after flashing the signed AVB root images and relocking the bootloader, you forgot to enable OEM unlocking again after the obligatory factory reset.
That was your first mistake.
The second was taking the advice of another user to do a direct install of Magisk Delta. This changed the signature of the boot image and broke the chain of trust.
So as @pndwal has covered above, you have an unbootable system with no ability to unlock the bootloader and flash images or change slots, and no recovery to sideload an OTA zip.
It seems you now have an unrecoverable hard brick unfortunately.

 

[zgfg]

Magisk delta telegram link has gone read-only and can't see any of the questions and comments. There is another link but I just can't seem to find the missing word.

it simply won't give up to me.

i've let myself down

But I can't keep running around.

Quite annoying because I don't want to desert the gram.

Vexed I am as I don't want to say goodbye.



what have I missed?

There were always two Delta TG channels:

1) One for announcements eg on releases (with comments from users), polls, etc

2) The other for discussions

They also constantly change their names (?), currently the first is named "Magikisune" and the second "Clear sky and historical thunder" - see the attached screenshots

As long as you're subscribed to them, their ever changing names do not bother

You can find the first (read-only, announcements) by name (and if I recall, it used to be linked from Delta GitHub project)

Invitation link for the second channel (discussions) was somewhere in the first, I found now one link but it's expired
I don't know if you could find it by name and join then

---

Btw, there is also a third channel, open (regional discussions): "Magisk Forum[SFW][Unofficial]", its invitation link can be found also in the first channel

 

[Primokorn]

This is the one I use -

GitHub - pantsufan/BlockAds: Magisk module to block ads on android

Magisk module to block ads on android . Contribute to pantsufan/BlockAds development by creating an account on GitHub.

github.com

What's the point of using a Magisk module instead of AdAway?

 

[pndwal]

@dkadds2
It seems that after flashing the signed AVB root images and relocking the bootloader, you forgot to enable OEM unlocking again after the obligatory factory reset.
That was your first mistake.
The second was taking the advice of another user to do a direct install of Magisk Delta. This changed the signature of the boot image and broke the chain of trust.
So as @pndwal has covered above, you have an unbootable system with no ability to unlock the bootloader and flash images or change slots, and no recovery to sideload an OTA zip.
It seems you now have an unrecoverable hard brick unfortunately.

Do you know if any EDL option is available for P6 series?... I understand from P7 discussion that this may have been removed at least for A13 LV devices... PW

 

[zgfg]

What's the point of using a Magisk module instead of AdAway?

Some users claimed they have issues with Systemless hosts/AdAway

That module installs its own hosts file at the time of installation file and it uses then the same Magisk systemless mechanism to mount over the /etc/hosts file but not by the use of Magisk built-in Systemless hosts)

Its hosts file will be updated only by updating the module. It says on GitHub that module will be updated every month but the latest version there is from December

I don't use the module but some say here (or in the AdAway thread) that they are ok with

 

[asripath]

There were always two Delta TG channels:

1) one read-only, for announcements of releases, polls, etc

2) The other for discussions

They also constantly change their names (?), currently the first is named "Magikisune" and the second "Clear sky and historical thunder" - see the attached screenshots

As long as you're subscribed to them, their ever changing names do not bother

You can find the first (read-only, announcements) by name (and if I recall, it used to be link on Delta GitHub)

Invitation link for the second channel (discussions) was somewhere in the first, I found now one link but it's expired
I don't know if you could find it by name and join there

---

Btw, there is also a third channel, fully open (regional discussions): "Magisk Forum[SFW][Unofficial]", link can be found in the first

Magikisune as it's currently known...
The release channel used to allow comments on releases....
Very helpful to know how the build is working

Edit:
See that comments have been enabled again.
@huskydg

 

[shoey63]

Do you know if any EDL option is available for P6 series?... I understand from P7 discussion that this may have been removed at least for A13 LV devices... PW

I don't think so, but alternative methods have been tried to recover hard bricks.
None have been successful to date.

 

[dkadds2]

So as @pndwal has covered above, you have an unbootable system with no ability to unlock the bootloader and flash images or change slots, and no recovery to sideload an OTA zip.
It seems you now have an unrecoverable hard brick unfortunately.

Thank you @pndwal , @Lughnasadh, @shoey63, @zgfg.

Given it is confirmed to be a hard brick - how can this be recovered outside of sending it back to Google (and counting on them replacing the unit).
Could this be fixed by opening up the phone and flashing something directly to eMMC? I'm not familiar with this though maybe some repair shops around can be able to do this.

Is there anything possible or this piece of hardware can be now sold for pieces?

 

[zgfg]

Thank you @pndwal , @Lughnasadh, @shoey63, @zgfg.

Given it is confirmed to be a hard brick - how can this be recovered outside of sending it back to Google (and counting on them replacing the unit).
Could this be fixed by opening up the phone and flashing something directly to eMMC? I'm not familiar with this though maybe some repair shops around can be able to do this.

Is there anything possible or this piece of hardware can be now sold for pieces?

I'm not familiar with Pixels but I know (fortunately, I never needed) that eg for Xiaomi phones there are users (contacts can be found on TG, 'ads' for paid services are forbidden on XDA) that provide authorized EDL support. They can do it remotely (you know what does it mean, they must connect to your PC to install and run the tools remotely - potentially a security risk) but you have to physically open your phone to access the pins on the motherboard (they can't do remotely)

For some older phones firehose files can be found on the Net, and then by the low-level tools (for the particular chipsets like Snapdragons) you can flash and un-brick the phone yourself (and save money, but it needs then a higher level of hacking from yourself, potentially a Linux machine for the tools, etc)

Last but not the least, by opening the phone you loose the warranty (you cannot hide that, and there is always a risk that you physically break something). If things don't go well, at the end you would additionally have to pay in the service shop or buy a new phone

Hence it's an endeavor that can be fun and a chance to learn new skils, but with the risks and costs (for the beginning, for good tools to open the phone by not damaging the display, battery, etc)

 

[Lughnasadh]

Thank you @pndwal , @Lughnasadh, @shoey63, @zgfg.

Given it is confirmed to be a hard brick - how can this be recovered outside of sending it back to Google (and counting on them replacing the unit).
Could this be fixed by opening up the phone and flashing something directly to eMMC? I'm not familiar with this though maybe some repair shops around can be able to do this.

Is there anything possible or this piece of hardware can be now sold for pieces?

There are no low level tools publicly available for the newer Pixels (Tensor-based) that I'm aware of. Replacing the motherboard may be the only option (assuming that will fix it).

 

[HippoMan]

Thank you @pndwal , @Lughnasadh, @shoey63, @zgfg.

Given it is confirmed to be a hard brick - how can this be recovered outside of sending it back to Google (and counting on them replacing the unit).
Could this be fixed by opening up the phone and flashing something directly to eMMC? I'm not familiar with this though maybe some repair shops around can be able to do this.

Is there anything possible or this piece of hardware can be now sold for pieces?

<rant>
Thank you, Google, for continuing to give us "enhancements" (ha ha!) with every new OS version which make things more and more complicated and painful for us, and which give us an increasingly greater chance of hard-bricking our devices! We yearn for the day when you will get Android to the point of being as locked down as an iOS device ... and we pray that you keep going beyond that to finally get Android to the same level of user configurability as a traditional IBM 360 mainframe!
</rant>

 

[dkadds2]

Thanks again - would you guys be able to drive me where/how to find Pixel groups/people willing to do it remotely?
If phone needs to be physically opened, then I'll probably drop it to the phone shop and still then can have it done remotely by them. I'm just afraid that finding a local shop knowledgeable about Pixels hard-brick recovery might be not that easy - hence I'll need to merge two worlds.

Re toolset - am not affraid of Linux, well am super familiar, this is my desktop under which I run all VMs with Windows as needed, etc. Toolset wise - that's not a problem to give remote access, not sure if this can be VM based as some low level USB behavior requires physical system, anyway, I'd grab spare laptop for it.

It's more about where to find experts and for sure I already know it's not gonna be free or cheap and replacing a motherboard... omg. I'd think it might be cheaper to re-solder eMMC (storage) and the only question is what needs to be put on it/format of it.

 

[fma388]

Hi all,

I've rooted my Pixel 7 Pro with latest Magisk stable and I would like to switch to Magisk Delta but I don't know how.

Thanks !

 

[crypticc]

There were always two Delta TG channels:

1) One for announcements eg on releases (with comments from users), polls, etc

2) The other for discussions

They also constantly change their names (?), currently the first is named "Magikisune" and the second "Clear sky and historical thunder" - see the attached screenshots

As long as you're subscribed to them, their ever changing names do not bother

You can find the first (read-only, announcements) by name (and if I recall, it used to be linked from Delta GitHub project)

Invitation link for the second channel (discussions) was somewhere in the first, I found now one link but it's expired
I don't know if you could find it by name and join then

---

Btw, there is also a third channel, open (regional discussions): "Magisk Forum[SFW][Unofficial]", its invitation link can be found also in the first channel

Thanks.

It's the second one I was looking for... The three characters become clear on the video or maybe my message. But even then doesn't work. Hrumph

 

[crypticc]

Hi all,

I've rooted my Pixel 7 Pro with latest Magisk stable and I would like to switch to Magisk Delta but I don't know how.

Thanks !

Just install the apk. It'll then offer to update to the Delta. Choose direct install. Away you go.


Edit: reading the troubles of dkadds2 just checking that you have NOT used this module:

GitHub - chenxiaolong/avbroot: Sign (and root) Android A/B OTAs with custom keys while preserving Android Verified Boot

Sign (and root) Android A/B OTAs with custom keys while preserving Android Verified Boot - GitHub - chenxiaolong/avbroot: Sign (and root) Android A/B OTAs with custom keys while preserving Android ...

github.com

I don't even know what that module does but it sounds bloody dangerous and explicitly says don't use direct install, only offline patching (presumably also means cannot do patch of image and then fastboot boot that to gain temporary root.... And then direct install which is what I tend to do)


But if all you have is Magisk regular root then I would say as I've done is okay because that's exactly what I did.




Edit. And instructions.....

FAQ

 

[pndwal]

Thanks again - would you guys be able to drive me where/how to find Pixel groups/people willing to do it remotely?
If phone needs to be physically opened, then I'll probably drop it to the phone shop and still then can have it done remotely by them. I'm just afraid that finding a local shop knowledgeable about Pixels hard-brick recovery might be not that easy - hence I'll need to merge two worlds.

Re toolset - am not affraid of Linux, well am super familiar, this is my desktop under which I run all VMs with Windows as needed, etc. Toolset wise - that's not a problem to give remote access, not sure if this can be VM based as some low level USB behavior requires physical system, anyway, I'd grab spare laptop for it.

It's more about where to find experts and for sure I already know it's not gonna be free or cheap and replacing a motherboard... omg. I'd think it might be cheaper to re-solder eMMC (storage) and the only question is what needs to be put on it/format of it.

I have twice used an Xiaomi 'Authorised Account' holder to unbrick an older hardbricked MTK based device (Xiaomi MTK are notoriously easy to hard brick; even flashing a TWRPs build that's not properly matched will do this... QCom is recommended for modding and very brick-proof... Many custom mod projects on XDA for Xiaomi MTK were abandoned as Devs couldn't afford to run the risks)... I paid about $12 each time and gave permissions to the company in Vietnam after connecting with Team Viewer... Session, incl flashing while logged into Xiaomi thru connected Authorised account, took maybe 15 min each time... There are many sharks around but I'd checked out the special phone services offered by this small business carefully...

However I fear it won't be so easy now or for late Pixel...

EDL (Qualcomm) and similar were developed to the point where even unpowered (no battery connected) devices could be reflashed, but companies like Xiaomi began locking down EDL mode to Authorised agents citing security concerns (correctly in fact) as hack tests have demonstrated that by using certainly vulns and modified ROMs the data-wipe requirement when unlocking bootloader can be completely bypassed in emergency download modes and then data is easily accessible on stolen devices... please see my post re. critical device vulnerabilities using QCom's EDL mode and similar MTek Emergency Download protocol which effectively grant an attacker full device access due to these modes not simply allowing forced flashing of officially signed software, but also providing ability to disable secure boot and unlock the bootloader with NO LOSS of device data. https://forum.xda-developers.com/re...tuck-da-mode-authorised-t4000433/post81563925... The cited XDA article on exploiting emergency download flash protocol gives more details.

Seems EDL and similar modes are now prohibited for regular users by most companies for the same security reasons, and new designs like Tensor may not even enable such a mode at all... It seems that P6 series users have not yet found confirmable means to recover a hard-bricked main board... Even Xiaomi Authorized Account holding agents are now like hens teeth as Xiaomi has revoked accounts for most of these and began requiring per-session payments from agents... My Vietnamese agent no longer offers the service, and they may all in fact be gone...

In short (assuming you really didn't enable OEM Unlocking after wipes associated with re-locking bootloader and have really hard-bricked your device), I don't like your chances for a fix at least using 3rd party services... PW

 

[crypticc]

Magikisune as it's currently known...
The release channel used to allow comments on releases....
Very helpful to know how the build is working

Edit:
See that comments have been enabled again.
@huskydg

I can't see any comments yet in either that thread or the modules thread.

 

[asripath]

I can't see any comments yet in either that thread or the modules thread.

 

[fma388]

Just install the apk. It'll then offer to update to the Delta. Choose direct install. Away you go.


Edit: reading the troubles of dkadds2 just checking that you have NOT used this module:

GitHub - chenxiaolong/avbroot: Sign (and root) Android A/B OTAs with custom keys while preserving Android Verified Boot

Sign (and root) Android A/B OTAs with custom keys while preserving Android Verified Boot - GitHub - chenxiaolong/avbroot: Sign (and root) Android A/B OTAs with custom keys while preserving Android ...

github.com

I don't even know what that module does but it sounds bloody dangerous and explicitly says don't use direct install, only offline patching (presumably also means cannot do patch of image and then fastboot boot that to gain temporary root.... And then direct install which is what I tend to do)


But if all you have is Magisk regular root then I would say as I've done is okay because that's exactly what I did.




Edit. And instructions.....

FAQ

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 ?