yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Just did the same to ensure forced app removal occurs even with same build App installation... It did...

So seems we do have forced app removal for App when hidden stub App is present in addition to when signing keys differ or App has a lower version than Magisk daemon...

Man, Magisk Devs are trying hard to protect us from ourselves! (Not sure I need my hand held this much)... Except that when this fails to work as expected we may need protecting from them! 😶😲🙃 PW
[Magisk] pndwal:
... But regarding this:

Just uninstalled hidden App (on latest Canary) again, reinstalled Canary Magisk App, then took Hide the Magisk app, and once again process failed to uninstall full app, asks for superuser permission for Magisk App etc ... As usual, simply ignoring requests and uninstalling the full App restores hidden app functions...

😬 PW
[Magisk] J.Michael:
What did you do?

install Magisk APK

find boot image

patch boot image

use Odin to install patched boot image

allow Android to update

find new boot image

When did you make the screenshot showing Magisk: No, Package: com.topjohnwu.magisk?

When did you make the screenshot showing Magisk: Yes, Package: gibberish?

When you update Android, do you look for a new boot image? Do you

patch the new boot image? Do you install the new patched new boot image?
[Magisk] pndwal:
Samsung compatibility

Fix for Magisk on new A13 LV Samsung (S23 Ultra etc) devices coming soon!

Add init_boot.img patching for Samsung tar firmware packages #6586 opened 6 hours ago by BlackMesa123• Approved

- Ckecks now passed, tested, ready to merge. 😋 ... Thanks @BlackMesa123 and @dr.ketan!

👀 PW
[Magisk] ipdev:
As for competing managers.

I was going off of memory from when it used to happen to me every now and then.

Both the regular (not hidden) and hidden (renamed) would show Magisk N/A.

All I had to do was uninstall one of them.

Normally I uninstalled the hidden (renamed) one and rebooted.

Then the regular (not hidden) one would show Magisk installed again. Then I could hide (rename) the manager again.

It was hit or miss if I uninstalled the regular one and rebooted.

Sometimes the hidden one would still show N/A. If so, then I had to uninstall it and reinstall the regular version again.

Then hide (rename) the manager again.

---

I wasted a bit of time tonight trying to get two Magisk manager apps to run currently.

The best I got was an error with Magisk Stable v25.1 on my Pixel 4a.

The initial hiding gave me issues with setting permissions and such.

Once the hidden app was installed, the regular version was removed.

The hidden version showed Magisk installed and active but, would keep throwing errors telling me to restore the Magisk app and hide again.

So I did and no issues the second time around.​

Cheers. :cowboy:

Edit:

@pndwal I did not read your last couple of posts before testing.

When I have time (tomarrow) I will see if I can duplicate it. 🙃
[Magisk] ipdev:
Like I said I have been using Manger apps way too long to not refer to them as the Manager. 🙃

Instructions

You can install/update phh's SuperUser in Magisk Manager's Download section

If you have no root in the first place, please flash the zip in the attachment through custom recovery

A root solution is part of a proper Magisk installation.

After phh's SuperUser is installed, please install the SuperUser manager Application through the Play Store

phh's SuperUser Manager​

Guess I am turning into the "Old Man".

Next I will be yelling at kids to keep of my lawn. 🤪

Cheers. :cowboy:
[Magisk] IronTechmonkey:
The combination of app and on-device services (root) could be called Magisk The Gathering. :D:D:D
[Magisk] Telperion:
It's been a long, long time since I've paid attention to how rooting works on a technical level with modern devices.

I have an Android 10 head unit that I'm trying to get a working userspace root solution onto. The bootloader is locked, but I have root via both a wireless ADB shell as well as serial console. I have read/write access to /system. I don't have the ability to unlock the bootloader and flash a patched boot image. Is it possible to get Magisk working?
[Magisk] J.Michael:
I'm going to guess "No": If you can't unlock the bootloader, and the bootloader being locked means what I think it means, then you can't possibly patch any of the system.

You could try naming the manufacturer -- somebody might have an idea of how to unlock the bootloader.

Why do you think you need root access?
[Magisk] pndwal:
I always thought it best to try to understand / adapt to a Devs parlance / nomenclature if only to avoid reinventing the wheel, which could be considered a bad omen... If the Dev/creator wanted to reinvent the wheel however, I was happy to let 'em...

But let's throw out convention; I'm with you guys... Let's go with the "Magisk The Gathering" app!... @ipdev's a Dead head and The Gathering has been described as 'coming off like a cheap mix between "The Omen" and "The Dead Zone".... Gotta work for all of us no? 😁 PW
[Magisk] Telperion:
Respectfully, you either didn't read my whole comment or didn't read it clearly. I already have root access via wireless ADB and using a USB-UART bridge I can connect via Putty to a serial console and I have root. I can read, write, modify, etc, the system partition.

I'm wondering whether I can get Magisk running.
[Magisk] m0han:
I'll take 'The Exorcist' for a change. ;)
[Magisk] J.Michael:
The system partition is not the one that needs to be modified to install Magisk. In fact, Magisk's claim to fame is the virtual modification of the system filesystem -- after Magisk has been installed.

You still have not identified your device.

Magisk used to be installed in the boot partition. Sometimes in the recovery partition. Recently new partitions have been invented and one of them might be where Magisk needs to be installed.

If you have no fear of losing your data, try installing Magisk manager app apk and using it to patch a copy of your boot image. Then try to overwrite your boot partition. See if you can boot.

Do you have any idea whether you will still have ADB root access if you are unable to boot Android?
[Magisk] Telperion:
Roco K706.

I've already tried using dd to write a patched boot image. UBoot fails when it kicks off the partition verification process and the device doesn't boot any further, so that isn't a viable option.
[Magisk] meric57:
Hello J.Michael, you are talking about firmware and security updates, I redid the modification with magisk as explained by Johnwu with adb pull and odin.

I hid the magisk app, no worries, I'm going to restore it to see, restoration ok.

The problem comes when I install an application or an update see a module on restarting the device I open magisk is I see application still install my magisk and zygisk not available, I would like to know if I can recover more quickly magisk no available either by flash or adb see other recovery mode.

I haven't yet tested uninstalling the magisk app and restarting, I'm waiting for the new smartphone to experiment with the S10 afterwards.
[Magisk] meric57:
Hello ipdev, you are talking about an application like root checker when I open to see phh's SuperUser I come across page not found.

As explained above hidden magisk app no problem or restored, just losing magisk after restarting my S10.

I will restart it after restoring the magisk app I see not available see magisk capture not the magisk app.

a problem or conflict
[Magisk] pndwal:
Looks like others tried, failed, bricked but got new main board from seller:

https://xdaforums.com/t/hizpo-3c-roco-k706-root-and-general-help.4376445/

😬 PW
[Magisk] NEOVerse!XChara:
magisk ruined my wifi (crDroid custom rom (last) | Redmi 8 - olive)

logs: (may be helpful)

02-07 15:26:31.123 E/AudioSystem-JNI(2886): AudioSystem::listAudioPorts error -19

02-07 15:26:31.123 W/AudioManager(2886): updateAudioPortCache: listAudioPorts failed

02-07 15:26:31.125 W/DPMJ (4352): |SERVICE| DPM received unexpected action: android.intent.action.ANY_DATA_STATE

02-07 15:26:31.126 I/Telephony(2142): isRttCurrentlySupported -- regular acct, hasVoiceAvailability: false

02-07 15:26:31.126 I/Telephony(2142): isRttSupported: false

02-07 15:26:31.126 I/Telephony(2142): alwaysAllowWhileRoaming: false

02-07 15:26:31.126 I/Telephony(2142): isRoaming: false

02-07 15:26:31.126 I/Telephony(2142): isOnWfc: false

02-07 15:26:31.134 I/CarrierServices(7608): [43] faf.handleMessage: RcsEngineImpl[DUAL_REG]:[d8be370e-3c66]>Handler: handleMessage processing message:[NOTIFY_UPTIME_IGNORE_STATE_CHANGED] with [non-null]:RcsEngineImpl reference

02-07 15:26:31.138 I/CarrierServices(7608): [44] egs.c: Connected state: [1], networkType: [MOBILE]

02-07 15:26:31.141 I/TetheringManager(1995): startTethering caller:com.android.systemui

02-07 15:26:31.147 I/CarrierServices(7608): [43] ewq.f: No RCS Configuration was found in Bugle for simID: redacted-pii:sim_id[chars:20,last3:918]

02-07 15:26:31.149 I/SystemUpdate(3994): [Execution,ExecutionManager] Action pending executed for 0.05 seconds.

02-07 15:26:31.159 I/Telephony(2142): isRttCurrentlySupported -- regular acct, hasVoiceAvailability: false

02-07 15:26:31.159 I/Telephony(2142): isRttSupported: false

02-07 15:26:31.159 I/Telephony(2142): alwaysAllowWhileRoaming: false

02-07 15:26:31.159 I/Telephony(2142): isRoaming: false

02-07 15:26:31.159 I/Telephony(2142): isOnWfc: false

02-07 15:26:31.161 I/WifiService(1263): startTetheredHotspot uid=1073
[Magisk] pndwal:
Are you patching boot.img or recovery.img?... How did you obtain boot image to patch?... PW
[Magisk] NEOVerse!XChara:
i'm having no ramdisk, i'm having root via recovery.img and boot.img patched with root, i have the recovery.img from the unofficial forum TWRP in latest version, it is patched via magisk manager with turned on recovery mode opnion
[Magisk] NEOVerse!XChara:
btw, while i'm opening whatsapp and trying to Make a call Whatsapp crashes...
[Magisk] J.Michael:
Were you able to recover?

Did Magisk say "Ramdisk: Yes"?
[Magisk] NEOVerse!XChara:
me?
[Magisk] NEOVerse!XChara:
anyway if you said it to me it said no 💀
[Magisk] martyfender:
From my experience having to wifi or other devices may mean you didn't patch the boot image from the new rom. Did you by chance use an older boot.img from a previous rom. the rom and kernel versions must match.
[Magisk] NEOVerse!XChara:
i have just opened the .zip file of my ROM and putted it in magisk :|
[Magisk] pndwal:
Bit confusing what you did... You extract and patch one boot image only; either boot.img (WITHOUT selecting Recovery mode) or recovery.img with Recovery mode set, NOT both! ... To access rooted system in recovery mode you will always need to boot via recovery with recovery key combo but release all buttons at splash screen to bypass recovery and boot to system with root...

Nb. Recovery mode means Magisk in recovery ramdisk... It has nothing to do with flashing via custom recovery (TWRP etc), and can't be flashed that way in any case...

In your case you can simply ignore Ramdisk = No! This is because Xiaomi bootloaders are (inexplicably) compatible with ramdisk in boot partition despite the OEM not installing one in A-Only legacy SAR devices, and Magisk always installs basic ramdisk where OEM Randisk is missing... (Magisk continues to display Ramdisk = No to indicate No OEM Ramdisk in boot.)

This means you extract and patch your boot.img (Ensure Recovery mode is NOT selected) and flash the resulting image to boot partition.

To fix you device, simply fastboot flash both unpatched boot.img and recovery.img then check device boots/operates normally again.

Next, ensure you have ROM package corresponding exactly to current running OS version and extract boot.img to patch/flash as above... Alternatively, you can install TWRP and make a backup of boot partition, obtain that from Backups and use this image. You may not even need to rename .win extension as .img, but can if you wish...

Please read John's Installation Instruction page carefully also because all necessary information is actually treated there...

Hope this helps... Please report results. 🙂 PW
[Magisk] pndwal:
He was talking to the Roco user... PW
[Magisk] meric57:
Bonjour, j'ai regardé dans les modules fox manager pour voir à quoi sert certain module.

Quelqu'un peut-il m'expliquer à quoi servent ces 4 modules que je vais citer et m'aider un peu avec mon souci de perte de magisk comme expliqué dans mes posts.

Assistant TRWP - gestionnaire de magisk pour le mode de récupération (mm) -SSH pour magisk - protecteur de boucle de démarrage magisk.

Je pense qui doit en avoir un ou plusieurs qui vont m'aider avec mon problème, non
[Magisk] NEOVerse!XChara:
i tried to flash stock boot.img adn TWRP.img but if i flash the TWRP (No Ramdisk) phone just loads in recovery, and i flashed the recovery with the recovery option, then via magisk i have patched boot (didn't flashed it by myself, magisk did)
[Magisk] pndwal:
I don't really understand much of this... Is this stuff you've done since my response to you? Or before? 🤔

Sorry, I have no idea what this means... What's 'adn'? 🤔

So are you trying to flash TWRP?... Why?... And what does 'phone just loads in recovery' mean?... 🤔

What does 'flashed the recovery with the recovery option' mean?... Flashed TWRP with some option??... Or flashed a patched or stock recovery?... What 'option'?

So you mean Direct Install did it?... So you must have had root already. (??)..

Anyway, did you try what I recommended?... Because it doesn't sound like it at all...

If you just do these parts:

you'll fix your issues... 🙃 PW
[Magisk] NEOVerse!XChara:
and* typo :|

my phone loading to recovery instead of rom

in the magisk i patched my "stock" TWRP with enabled "recovery mode"

i'm having the su perms, but i don't have any connection to internet (i'm making thoose all from notebook)
[Magisk] pndwal:
I can't really follow what you've done, but seems you've patched and flashed both boot.img and TWRP.img or stock recovery.img...

Restore stock recovery or unpatched twrp for reasons I've given, then, without root, patch stock boot.img only and fastboot flash that...

I repeat, If you just do these parts:

you'll fix your issues... 🙃 PW
[Magisk] NEOVerse!XChara:
as i said when i'm trying to flash stock TWRP (TWRP without ramdisk) my phone can't load to the crDroid

it's just booting into recovery
[Magisk] NEOVerse!XChara:
i'm naming my TWRP without ramdisk "stock TWRP"

if it's not then "TWRP"
[Magisk] pndwal:
Ok, forgot you use custom crDroid... so fastboot BOTH TWRP and boot.img from crDroid (both unpatched) and see if system can boot again... Should be no issues now... If there is, try dirty-flashing crDroid ROM again...

Next, patch that same crDroid boot.img in Magisk App with Recovery Mode DE-SELECTED! (Boot mode, not Recovery mode) and flash from TWRP... System should then boot with root... PW
[Magisk] NEOVerse!XChara:
i have tried all of them, i don't know much about dirty-flashing, say how to do it

i have patched the boot image like that you said it now, but i didn't got the su perms :(
[Magisk] rodken:
The bootloop protector works by disabling certain Magisk modules that may be causing the bootloop, and then re-enabling them one by one to identify the specific module that is causing the problem. Once the problematic module is identified, it can be removed or replaced, and the device should be able to boot normally.

With Magisk Manager for Recovery - if you end up with a bootloop, you can just disable the module from recovery. This app is used in a recovery terminal only (e.g. TWRP), not in Magisk by itself.
[Magisk] NEOVerse!XChara:
woah, where you know that all?
[Magisk] pndwal:
IINM, it disables all modules after (and denylist?) after several failed boot attempts (loops) similar to invoking safe mode but automatically/more reliably... Then user needs to enable selectively again...

👍 PW
[Magisk] rodken:
There is also the SystemUI Bootloop Protector that in theory, fixes SystemUI bootloops by detecting when SystemUI crashes (due to a Magisk module such as Substratum,) and reboots your device into safe mode automatically to disable Magisk so you can correct the faulty module.
[Magisk] pndwal:
Just means flashing ROM without data wipes / factory reset... Clean flash means at least factory reset wipes, sometimes formatting data / other partitions first...

Try reflashing ROM dirty... Flash unpatched TWRP if ROM doesn't include recovery partition...

Could be an issue with crDroid ROM but doubtful... Pretty sure patching/flashing boot will work for stock Olive... PW
[Magisk] rodken:
Semi-random searching for websites and or videos, images, etc. that match my interests, similar to a random web search utilizing various search engines and meta search engines with the help of using search operators.
[Magisk] NEOVerse!XChara:
who

who x2

bro, i'm just losed my wifi or i'm a bit (yeah, yeah bit) dumb
[Magisk] pndwal:
Who? You!.. You said "i don't know much about dirty-flashing, say how to do it"... I said how to do it...

You x2!... May fix ability to access root in boot img...

Dunno mate ... PW
[Magisk] zgfg:
In the Fox MM, scroll to the given module, click on Description, it will open the GitHub page for that module

Developers usually try to put some helpful description what for the module is and how it works.

If useful description is missing, skip the module
[Magisk] J.Michael:
Doesn't it bother anyone else that @meric57 says he's going to ask about five modules and then proceeds to name four?
[Magisk] J.Michael:
I think in this context "who" is pronounced "whoah", like getting a horse to stop.
[Magisk] J.Michael:
Please tell us exactly what and how you do.

Start with explaining "flash":

do you use "fastboot"?

exactly what command did you type?

what command did you use to flash the patched TWRP?

Then explain what you mean by "TWRP with no ramdisk". How many TWRPs do you have?
[Magisk] NEOVerse!XChara:
"quotes hari ini" be like:
[Magisk] NEOVerse!XChara:
yes

fastboot falsh boot cd_stock_olive.img

fastboot flash recovery rr_twrp_olive.img

(cr - crDroid; rr - RamdiskRecovery)

fastboot flash recovery rr_twrp_olive.img (as shown above)

"Stock" TWRP - Unpatched (No RamDisk)

TWRP - RamDIsk patched
[Magisk] J.Michael:
Explain

I still do not understand "TWRP no ramdisk". Are you saying TWRP does not have a ramdisk until Magisk adds one when you patch TWRP? That seems unlikely.

Have you ever tried

fastboot boot some-image-file

?

Maybe you should stop trying to install TWRP. Can you install Magisk without installing TWRP?
[Magisk] Lughnasadh:
For all those who are wondering, Magisk is working on Android 14 Developer Preview 1 on my Pixel 6 Pro, although I had to patch and flash the Pixel 7 Pro boot image to make it work. Apparently the "bug" that was present on A13 QPR2 Betas 1>2.1 ("fixed" in Beta 3) on the Pixel 6 series is back on A14 DP1.
[Magisk] NEOVerse!XChara:
quotes today:

TWRP no RamDisk - i didn't patched the "Stock" TWRP via magisk to flash it onto device, btw i'm calling it "Stock" TWRP

i know this command but i think it's will not add RamDisk for su perms

i have installed it successfully :|

and no, when i just flashed the boot.img it didn't gave mee su perms
[Magisk] pndwal:
Temporary boot w/ root is possible... PW
[Magisk] NEOVerse!XChara:
W/???
[Magisk] zgfg:
It's PW=pndwal
[Magisk] J.Michael:
"w/" is an abbreviation for "with"

"w/r" is "with respect" (in case it comes up)
[Magisk] J.Michael:
No fastboot command will "add ramdisk". ramdisk is something some "systems" include, it is involved in the process of booting; really it is just a way to make a filesystem available. A system that has been packaged with a ramdisk might only use the ramdisk briefly before switching to some more substantial, more traditional filesystem; but it is possible that after booting the ramdisk filesystem is still available. It doesn't really matter.

The "fastboot boot" command might let you test a boot image (or a recovery image -- any image that is the first step to booting a computer) without installing it. Whether it works or not, you haven't changed your system, the next time you boot you are back to the "old", installed, system.

If Magisk is installed in the recovery partition, you might have trouble installing TWRP. One approach is to *not* install TWRP, and just "fastboot boot twrp.img" when you want to use TWRP.

When you plan to install Magisk in the boot image, you can test the patched image with "fastboot boot magisk-patched-image". You will never bootloop because the patched image will only be used once -- if there's a problem, there's nothing to uninstall.

I have lost track of what problem you are trying to solve.
[Magisk] NEOVerse!XChara:
pndwal??? wth
[Magisk] NEOVerse!XChara:
wait, ok i think i hjave got that you was trying to text me, so... what i will do next to fix my problem to wifi? do i need to do a dirty flash? and how to install su perms then?
[Magisk] NEOVerse!XChara:
a wait, i have found the VoidUI based on Android 13, will magisk work on android 13? or i should stay for now on android 11?
[Magisk] zgfg:
Yes. That's good for:

1) to test (before patching by Magisk) if the extracted boot.img really works (belongs to the ROM being used)

2) to test if the boot.img patched by Magisk will be good for use, does the system boots and if the root is obtained

Of course, one should always test first (1) - instead of testing only (2) and then complaining that maybe Magisk wrongly patched the boot.ing, whereas his extracted boot.img was wrong from the beginning

On devices that do not have separate Recovery partition but Recovery is integrated to Boot partition, one must first install TWRP (custom recovery), then backup that Boot partition (with TWRP already installed), then patch by Magisk the backed-up boot.emmc.win and flash it back to Boot - then, he would have both the TWRP and Magisk in that same Boot partition

I have also lost track what @NEOVerse!XChara started with, but it seems to me that at least parts of that do not belong to this Magisk thread (issues with his specific custom ROM and/or his TWRP) - things like that should be discussed under the particular device subforum and/or under the channels specific to that ROM or TWRP (like how to install that TWRP, where from to extract the boot.img, or to report if something is wrong with their TWRP or boot.img)
[Magisk] zgfg:
Magisk works perfectly for me and many other users here with Android 13

However, it does not guarantee that it would work on your device and with your (probably custom) ROM and A13

Things are not generic for A11/A12/A13 but usually specific per devices and specially per (custom) ROMs

And for things like that, you should find the subforums on XDA specific to your device (or thread or TG channel corresponding to eg that custom ROM) and to see there what and how the other users do to avoid/overcome the problem or to fix it
[Magisk] zgfg:
You were quoting posts from pndwal and asking (or what, frankly I don't understand your reports, questions, etc and wonder if the others do) what PW stands for - "pndwal" user signs his every post by "PW" (initials, abbreviation for his nickname, whatever). Look again to his posts, like all his answers to you
[Magisk] m0han:
https://xdaforums.com/m/pndwal.7550078/#recent-content
[Magisk] NEOVerse!XChara:
i have started that all due to the calls connection to the internet hotspot and etc. problem after installing su perms with magisk
[Magisk] NEOVerse!XChara:
btw i'm now think i can actually have android 13 with su perms, so idk, i think it can be unsuccessfully, and if it do (due to the mi439 thing) i'm will REALLY stuck :( i'm gonna flash orange fox and flash the VoidUI instead of crdroid v7.14 to try magisk in that rom
[Magisk] NEOVerse!XChara:
wait, WAIT THAT WAS THAT EASY? bruh, i just watched yt tutorial and i should rename the magisk.apk to magisk.zip, then install from recovery and reboot to system, update magisk with magisk itself and done 🤦‍♂️ i'm really dumb