yashsingh1/xdaforums huggingface dataset:
[Magisk] _litz:
Hi, no I'm a very very manual person when it comes to things like this ... I flash the updates directly from ADB/Fastboot, as well as directly patching init_boot from the app (and flashing it as well). Automated processes are nice, but ask anyone who's trusted their Tesla to drive for them how well that worked out ....

Root is working as designed in all aspects except for this. It's as if one of two things is happening ... the hosts file overlay is not present (despite AdAway not throwing any errors) or apps in general not seeing the overlaid hosts file (being presented with the default empty hosts file).

I only have zygisk (to allow for Universal Safetynet to function), bootloop protection, and magiskhide.
[Magisk] zgfg:
Assuming that AdAway was granted root and that you enabled Systemless hosts and rebooted

If running SuList mode, AdAway must be enabled in the Confgure Sulist (and reboot then)
[Magisk] _litz:
Correct, and in both cases yes. AdAway is not reporting any issues, in addition if I view the hosts file I'm seeing the proper number of entries (e.g. thousands of lines).
[Magisk] krakout:
Wow that's weird.
[Magisk] _litz:
Isn't it.

If I disable AdAway entirely, and DNS filter via AdGuard Public DNS -- using the SAME filters -- all ads vanish as expected.
[Magisk] krakout:
Just to make sure, how do you view the hosts file?
[Magisk] NippleSauce:
Gotcha. I do it all manually as well.

So long as you only patched the init_boot with Magisk/Delta and didn't flash it with Magisk/Delta, then you should be all good there. But regardless, the systemless host issue that you are facing likely requires a device wipe to be resolved. But, I know doing that really stinks =/.

I tend to update my P7P without the "-w" comment until I run into issues like the one which you are currently experiencing. Once something like that occurs, I tend to make another backup and then re-image my phone with the same factory image but with the "-w" command intact. After restoring from the backup, everything works normally again and I no longer face whatever issue I was running into.

Of course, the issue can probably be resolved with some root file manager by removing a few files or directories....I just don't know which ones would have to be deleted - hence why I wipe my phone and re-image.
[Magisk] _litz:
It's easier, frankly, to use AdGuard DNS ...

Wiping and reimaging is truly a nasty hassle, not the least of which is having to re-register all the Okta tokens for work.

So probably gonna just chalk this up to "we're doing something the manufacturer doesn't recommend" and move onwards.

Everything else works fine, so not that big a issue. Just weird.
[Magisk] samtron6:
Moto G play 2023. installed, flashed patched boot.img has bootloop. android 12.. reflashed with origianl patched boot.img from MAGISK and it boots.. idk if it didnt patch the .IMG right or what
[Magisk] kevinco1:
Instead of troubleshooting more just uninstall AdAway which will restore the default hosts file. Reboot and install again... That's helped me in the past.

AdAway has given me enough problems I now just use adblocking Magisk modules which don't require systemless hosts be enabled
[Magisk] krakout:
Like which one? I don't remember seeing any...
[Magisk] m0han:
@kevinco1, Is this one? https://github.com/pantsufan/Magisk-Ad-Blocking-Module/
[Magisk] krakout:
Basically this showcases the problem with Magisk modules - hasn't been updated in there months, hence hosts file is rather old...
[Magisk] quinzhy:
now i have successfully installed it, thanks for the instructions
[Magisk] m0han:
delta update available
[Magisk] huskydg:
Bootloop protection is going to be implemented
[Magisk] Jeroen1000:
So itsme app is working but Keytrade 5.5.13 keeps detecting something...

- I pass basic safetynet

- Keytrade has been added to Magisk hide (including splits)

- Google Play services fully added to Magisk Hide

- I installed LSPosed in order to be able use HMA. I have enabled all hide methods and added io.github.huskydg.magisk to additional apps invisible.

This used to be enough to fool Keytrade. Any tips on how to find out what it is detecting?
[Magisk] Eng.Raman:
In HMA, Don't enable all hide methods ( it will cause force closing the Keytrade app ).

JUST tick/enable Intent queries applied to a blacklist template of all your LSPosed modules,.

No need to add io.github.huskydg.magisk to additional apps invisible.

Good Luck.
[Magisk] zputnyq:
Hi @huskydg

I wanna switch to your delta built but I have a few question about it.

1. Is delta built for a specific device or its coverage is similar to the official version (android 6+) ?

2. I saw changelog of v25.1 delta 2 said that modules directory is changed, is this only for addon.d support or how actually ?
[Magisk] huskydg:
delta is synchronized with official source so there are so specific device

Magisk binaries moved to `/data/unencrypted/MAGISKBIN` and symlink back to `/data/adb/magisk` to fixes `/data` needed of addon.d when you update ROM.

Modules directory changed to `/data/unencrypted/magisk_modules` and symlink back to `/data/adb/modules` to let you manage the module from recovery with encrypted FBE.

Final word

You can keep using official if you are fine with current Magisk setup
[Magisk] m0han:
delta is synchronized with official source. so, folks don't have to hesitate to try delta. i don't.
[Magisk] Jeroen1000:
Thank you that worked like a charm. For others who stumble upon this thread. Previously, I did it your way (only block intent queries).

Some observations for Keytrade 5.5.13:

You do still need to hide the official Magisk binary for the using HMA.

Regardless of using Magisk Delta or the official Magisk, the only LSPosed module you need to hide using the (optional) template is HMA itself. But YMMV I am not using a lot of LSPosed modules.

I hope Keytrade staff is not reading this:-).

Itsme appears to be detecting Zygisk itself so it probably will not work when using the official Magisk
[Magisk] m0han:
f74eddef-delta

- Update script for Magisk installation to system partition

- Canary or Debug build now will tell you to update if version name is mismatched

- Update French translation

the dev @huskydg took note of this update issue that was reported earlier, maybe.
[Magisk] huskydg:
8c17f54d-delta

- Don't load custom sepolicy patch of modules when booting into core-only mode
[Magisk] Seb_Lz:
Currently running 25.1-delta-2 (25100) with MagiskHide ON and Zygisk OFF, all banking apps and ItsMe seems to work fine which is great.

Trying to get Google Pay to work, I noticed I wasn't passing CTS profile match:

As suggested earlier in this thread, I tried riru + safetynet fix 2.1.3 but this didn't help.

I thought about MagiskHidPropsConf (https://xdaforums.com/t/module-magi...p-edits-and-more-v6-1-2.3789228/post-86520843) but I got a message saying this isn't supported by magisk delta :

Any idea how to proceed further ?
[Magisk] huskydg:
MagiskHide Props Config is no longer maintained and no longer support MagiskHide.
[Magisk] Seb_Lz:
Ok thanks, and is there an alternative way to pass CTS profile match required for Google Pay ?
[Magisk] huskydg:
What is your device name?
[Magisk] Seb_Lz:
POCO F3 (alioth)
[Magisk] zgfg:
If stock/certified ROM, why would you need MHCP

Shouldn't latest Delta, Zygisk On, Magisk Hide , latest Shamiko and latest USNF be enough

I don't use GPay but with setup as above I do pass SafetyNet (additionally with MagiskHide + Hide My Apps I also pass several 'banking' apps)
[Magisk] huskydg:
Zygisk has no hide function and it just make hiding more complex and bloated
[Magisk] Seb_Lz:
This might get SafetyNet certification but I came here because ItsMe wasn't working and I'm afraid your suggestion will give the same result (not sure if you're using this app with that setup ?)
[Magisk] zgfg:
No I'm not using your app, and sorry cannot really bloat my phone for every app for every user who comes here and want a solution for his app (but does not want first to test himself solutions that already worked in other cases)

Recently I did install two apps and pass them with the setup as above - you could have read eg the confirmation today from another user for followed the suggestion and it also worked for him/his app

However, if you think that you 'know' in advance that something would not worki then your choice...

Anyway, sorry but I have to spend my time on other things
[Magisk] _litz:
Yes, that's why I switched to the adguard dns service, it offloads the blocking, and also since you can define lists, remains current.
[Magisk] RootedLee:
@zgfg if I may ask: on how many of your mobile android devices do you have Magisk Delta installed? And are you in general happy with HuskyDG's fork, compared to the original?
[Magisk] krakout:
Very.
[Magisk] zgfg:
I have Delta on my daily and official Canary on the spare phone

Previously I had the opposite way but since I was ok with Delta for several months, since it was ok (and since I needed better hiding), I put Delta to the daily driver
[Magisk] kevinco1:
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
[Magisk] kevinco1:
Yep, you beat me to it!
[Magisk] m0han:
I see you've used plural. What are the others?
[Magisk] Marucins:
Hi

Sometimes the phone through the wrong modules will pass the bootloop, booting the phone with the volume button pressed allows you to turn on the safe mode that disables all modules from the magisk

Applist Detector, Detects a hidden Magisk Delta app...

Will the delta version avoid such problems?
[Magisk] dkadds2:
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:

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).

Direct installation (recommended).

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!
[Magisk] krakout:
Direct.
[Magisk] dkadds2:
Upon reboot it gave me:

Trying to go to recovery has same effect.

Bootloader is locked and it shows up as fastboot device still.

Bootloader shows as Boot slot: b

Any hints how to recover?
[Magisk] dkadds2:
Tried to unlock bootloader - failed. Do I have soft or hard brick now?

I have a feeling that Magisk switched slot and that's where the problem lies.

How to switch it back to a with bootloader locked? Or should I try using Google flasher? Don't want to get to worse situation.

fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.042s]
finished. total time: 0.042s

And then

fastboot flashing unlock
...
FAILED (remote: flashing unlock is not allowed)
finished. total time: 0.044s
[Magisk] zgfg:
Magisk by itself does not switch slots, only if you switched the slot when flashing or the tool you used.

OTA may switch the slot

You have single Bootloader, it's locked or not no matter which slot you are

To switch slots:

fastboot --set-active=a

or

fastboot --set-active=b
[Magisk] dkadds2:
Switching slots didn't work:

fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: command (set_active:) is not allowed when locked)
finished. total time: 0.006s
[Magisk] dkadds2:
The slot then had to be switched earlier, as system booted fine and it only failed after running Magisk and selecting option as per above on first run to let it do additional tasks.
[Magisk] Lughnasadh:
You can't manually switch slots with a locked bootloader. If you took an OTA, that will switch your active slot. Sideloading a Full OTA image will also swich your active slot.

Do you have OEM Unlocking enabled in Developer Options? If so, you can use Android Flash Tool to reflash your firmware. It will unlock the bootloader during the process as long as you have OEM Unlocking enabled in Developer Options. The result you got when trying to unlock makes me think you may not have it enabled, however.

If you don't have OEM Unlocking enabled then you can try to sideload the Full OTA image as that does not require an unlocked bootloader. It will also switch your active slot, as stated earlier.

I would also suggest if you play around with avbroot and locked bootloaders, you should make sure you leave OEM Unlocking enabled.
[Magisk] dkadds2:
Thanks, I didn't touch OEM Unlocking and it should stay enabled. Being in current state I have no way to check that anymore as it doesn't boot at all, the most I get is bootloader.

How can I push Full OTA in this situation? (fastboot ... ?). Recovery doesn't load, claims same message - no OS.

No valid operating system could be found.
The device will not boot.
[Magisk] Lughnasadh:
As I stated above, if you have OEM Unlocking enabled you can try using Android Flash Tool. If you can't get into recovery you probably won't be able to sideload a Full OTA.
[Magisk] dkadds2:
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)?
[Magisk] crypticc:
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?
[Magisk] 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.
[Magisk] zgfg:
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
[Magisk] Primokorn:
What's the point of using a Magisk module instead of AdAway?
[Magisk] pndwal:
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
[Magisk] zgfg:
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
[Magisk] asripath:
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 👍
[Magisk] shoey63:
I don't think so, but alternative methods have been tried to recover hard bricks.

None have been successful to date.
[Magisk] dkadds2:
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?
[Magisk] zgfg:
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)
[Magisk] Lughnasadh:
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).
[Magisk] HippoMan:
<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>
[Magisk] 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.
[Magisk] 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 !
[Magisk] crypticc:
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
[Magisk] crypticc:
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 - chenxiaolong/avbroot

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