Magisk General Support / Discussion

[J.Michael]

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

I think in this context "who" is pronounced "whoah", like getting a horse to stop.

 

[J.Michael]

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

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?

 

[NEOVerse!XChara]

"quotes hari ini" be like:

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

 

[NEOVerse!XChara]

• do you use "fastboot"?

yes

• exactly what command did you type?

fastboot falsh boot cd_stock_olive.img
fastboot flash recovery rr_twrp_olive.img
(cr - crDroid; rr - RamdiskRecovery)

• what command did you use to flash the patched TWRP?

fastboot flash recovery rr_twrp_olive.img (as shown above)

Then explain what you mean by "TWRP with no ramdisk". How many TWRPs do you have?

"Stock" TWRP - Unpatched (No RamDisk)
TWRP - RamDIsk patched

 

[J.Michael]

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

Explain

"quotes hari ini" be like:

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?

 

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

 

[NEOVerse!XChara]

Explain

quotes today:

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.

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

Have you ever tried

fastboot boot some-image-file

?

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

Maybe you should stop trying to install TWRP. Can you install Magisk without installing TWRP?

i have installed it successfully :|
and no, when i just flashed the boot.img it didn't gave mee su perms

 

[pndwal]

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

Temporary boot w/ root is possible... PW

 

[NEOVerse!XChara]

Temporary boot w/ root is possible... PW

w/

W/

W/???

 

[zgfg]

W/???

It's PW=pndwal

 

[J.Michael]

W/???

"w/" is an abbreviation for "with"
"w/r" is "with respect" (in case it comes up)

 

[J.Michael]

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

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.

 

[NEOVerse!XChara]

It's PW=pndwal

pndwal??? wth

 

[NEOVerse!XChara]

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.

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?

 

[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?

 

[zgfg]

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
I have lost track of what problem you are trying to solve.

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

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.

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 lost track of what problem you are trying to solve.

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)

 

[zgfg]

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

 

[zgfg]

pndwal??? wth

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

 

[m0han]

pndwal??? wth

.... "pndwal" user ... Look again to his posts

https://forum.xda-developers.com/m/pndwal.7550078/#recent-content

 

[NEOVerse!XChara]

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)

i have started that all due to the calls connection to the internet hotspot and etc. problem after installing su perms with magisk