yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Well seems either it isn't, or folder has been deleted...

Please confirm you use stock ROM, and which Android version...

Seems we still don't have Android 12 compatible TWRP, so this may well be your issue if on Android 12 or 13...

Please give link to this vbmeta... I believe it's best to use image from your own ROM w/ switches per instructions if disabling verity etc is still necessary...

Seems this is really only to make TWRP persist after reboots however... It's likely not needed, especially w/ recent Magisk...

If on A12 and above, I'd be ditching TWRP; leave recovery as stock after next ROM flash and use recommended Magisk installation for SAR devices (in-app patching, fastboot flashing)... Try without vbmeta flashing first... Don't use recovery mode; patch boot.img despite ramdisk=no (see below)...

Actually, I'd favour this method regardless of Android version... Old .zip/recovery installation method was designed for legacy ramdisk boot-type devices... For your SAR device, in-app patching is recommended and .zip method discouraged/depreciated exactly for the reasons you are now aware of...

Yes... Dirty flash of complete ozip should fix things in that case especially if it includes all the extra images you listed above... If not you may need to flash them in addition...

Nb. Both recovery type ROMs and fastboot type are available for many devices... Recovery ROMs usually exclude the extra OEM images but fastboot ROMs are complete...

So seems device is OEM Ramdisk=no, but like Xiaomi boot mode Magisk is working on your device... This must be because the bootloader (inexplicably) accepts a manually added ramdisk (Magisk does this) in boot partition...

Found this (seems you've been there too):

https://xdaforums.com/t/realme-x2-p...very-magisk-canary-safetynet-pass-fp.4127835/

Those familiar with this device/ RealMe in general will likely be of more help... Wanna pitch in @Eng.Raman?...

🙃 PW
[Magisk] metropical:
the NYC Transit system and other public WiFi sometimes don't show log in, though they "link" to it.

I assume this is coz I have a rooted phone.

For the most part, we have good coverage in NYC, but in the subways not.

NYCT has provided a public WiFi, but as yet I have been unable to log in as no prompt shows itself, other than a log in link that goes no where.

Anyone know a way around this issue?
[Magisk] pndwal:
Why do you assume that?... 🙃 PW

I tink me moretropical... at least more dan you in NYC!
[Magisk] zgfg:
Turn of adblockers or firewall apps if you have - they can cause problems to open login page, not Magisk
[Magisk] Sir Backe:
OK, let's talk about reinstalling ROM.

I already did so. No it does not wipe out data when following the standard procedure. I installed the latest official rom for this phone, the RMX1931EX_11_C.38 version from realme website, vbmeta and magisk, following the standard procedure as usual. It did not boot. Just stuck at logo.

I use stock ROM from this site

Android Version 10

VBMETA

TWRP 3.4.0 Mauronfrio

Instructions with links

I did. Just flashed OZIP in TWRP and then rebooted into system. Stuck at yelllow logo....

THen I installed the other files with adb

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot flash system system.img

fastboot flash vbmeta vbmeta.img

fastboot flash vendor vendor.img

Result: It did not even boot to yellow logo, but directly into TWRP

I re-installed OZIP in TWRP. Now it stucks again at yellowlogo.

I followed this

Thank you!

@Eng.Raman
[Magisk] pndwal:
In general:

Dirty flashing a full (fastboot type) ROM will remove most custom mods (Ie. those done by custom ROMs, recoveries, Magisk, most Magisk modules; there may be exceptions, etc) with the exception of their data...

Magisk and general module data (exceptions may be where a module installs apps) is all stored in /data/adb (partition backups are in magisk_backup_xxx folders in /data in addition) so if if these contents are removed the device with be clean of such mods...

If things are still not working with a dirty full ROM flash and /data/adb removal, the issue is likely to be that you have flashed a different ROM to the one you were using and some data that ROM used is incompatible...

You should be trying only to boot the ROM you were using when Magisk update caused bootloop unless you do a clean ROM install... ROM data incompatibility is a common issue!...

Hope this helps... PW
[Magisk] J.Michael:
You did not say what "handy" was before the spill chucker got through with it.

It bothers me that you have never said "I installed one of the ROMs and booted and the device works fine."
[Magisk] Sir Backe:
Sorry. Handy means Smartphone in our area. So in this case it is the Realme X2 pro.

OK I didn't write it, but I've done it several times. No chance. Stuck every time at the logo.

Now, I made dirty install 5 or so. No chance.

Now, I made a clean install. No chance. Data are gone.

Now, I made a new install. No chance.

I made all these installations without vbmeta special and magix. Just the ROM.

Result: the phone (handy) does no more boot at all, except into TWRP.

Completely new situation. 😖😖😖
[Magisk] J.Michael:
Have you tried all three of the ROMs in the thread you referenced? There was some talk of the ROMs not being interchangeable because of different partition sizes.

How does Realme intend for an ozip to be installed?

Have you ever successfully installed an ozip?

Did you use the original recovery?
[Magisk] Sir Backe:
@J.Michael , @pndwal

It works! 👍👍 👍

First of all thank you both so much for your efforts! Really really great!

I don't know what actually helped at the end.

What I did:

Dirty Flash ROM

Clean Flash ROM

Deleted in TWRP most partitions

Formatted data

Reinstalled a nandroid backup from few days ago

Flashed Boot.img, recovery.img, system.img, extracted from latest ROM for this phone.

Result: after most steps it always said: corrupt boot/recovery partition. Flash correct versions or contact customer service.

One last trial: I flash once more boot.img and it booted!

Who the heck knows why. But it did.

Now I have an untooted phone WITH data, but without files from sdcard. But I do have a copy of this folder on USB Stick!

Now my hopefully last question to you professionals:

I need TWRP back, and Magisk, and the data to the sdcard.

Shall I root as usual and copy back the sdcard-folder to the phone, or do you have a safer suggestion how to do it? I'm very much afraid that the phone is possibly not stable and will crash again when doing something wrong.

I also feel unsafe which versions of TWRP, VBmeta and Magisk I shall use, because there were so many special versions for this phone and it seems, that the latest Magisk are no more compatible.

Would appreciate very much your opinion and thank you once more for all your time and efforts!
[Magisk] Chris4711:
Sorry, indeed I have been inaccurate. As I have only one Magisk module installed (XPrivacyLua), I have set Magisk and the module the same.

So, with data I mean (in the main) contacts and calendar entries that XPrivacyLua can hide from specific apps. If Magisk is uninstalled, all apps might get access to those data.
[Magisk] zgfg:
Ok, true

But eg, on my MIUI 13/A12, permissions (native Settings, Apps, Permissions)

are highly granulated.

If I disable permission for WhatsApp to read Contacts, then WA shows numbers instead of finding the corresponding names from my Contacts
[Magisk] Sir Backe:
I tried one other, guess C32, but then stayed wit C38, since this was the one I had before.

I didn't hear about that re partition sizes. Maybe there were differences between the EU and CN versions. They are not just interchangeable.

Actually it is OTA. Since my phone is rooted I have to download from website and install through recovery. In my case TWRP.

ALL OZIP installations withe TWRP were successful. Most of them at the first sight.

To install C38 at the end I had to use original recovery which suddenly was there, and TWRP has gone. Possibly my luck. The first attempt failed, then I just did it a second time. Both times from OTG stick because the copy I copied to the phone was corrupt.
[Magisk] Eng.Raman:
Then you are still on stock A10 ( C.38 firmware ), to get rid of stuck at boot logo do the following steps:

1. Flash twrp-3.4.0-10-RMX1931-mauronofrio then boot to recovery.

2- Flash C.38 firmware.

3. Reboot to Bootloader then format data using the command line: fastboot erase userdata

4- Flash the A10 patched vbmeta ( attached ) Directly: fastboot flash vbmeta vbmeta.img

5- ( Optional ) If you need to root your device use the latest magisk available now ( Official TJW stable / canary ) OR any unofficial one BUT the latest one.

( Don't flash magisk < v25.0 ).

Good Luck
[Magisk] pndwal:
Latest libsu:

www.twitter.com/topjohnwu/status/1569645665080459265

changelog:

https://github.com/topjohnwu/libsu/blob/master/CHANGELOG.md#503

👍 PW
[Magisk] metropical:
the only adblocker I have, per se, is - dns.adguard.com. is that included in your response?
[Magisk] J.Michael:
Congratulations.

You said you formatted data, then installed a nandroid backup. Did that backup include "/data"?

You said "WITH data, but without files from sdcard". What is "sdcard"? An external SD-card? Or "/sdcard", the magical link/bind maintained by Android to be almost accessible from a PC?

How did you install Magisk the first time? (Please don't say "the usual way".)

Whatever "sdcard" means, you do not need Magisk to copy files to it.

Your original problem might have been using the wrong boot image when trying to install Magisk on the newer ROM. In which case, installing Magisk now should go smoothly. But note the comments by @Eng.Raman indicating that there is at least one version of Magisk that you should avoid.
[Magisk] zgfg:
Turn of and try. What is the problem to test
[Magisk] metropical:
Genius mate! That was it. Thanks for the suggestion.
[Magisk] smgoller:
Hi, I'm trying to get Magisk installed on a fresh Nexus 5. I flashed it to the latest factory image (December 2016), then manually installed the latest release (25.2). I uploaded the boot.img from the factory image and patched it. I flashed the resulting boot.img to the phone and rebooted. When I subsequently run Magisk, the mask logo appears and it stays that way, I've left it alone for over an hour and nothing. Any ideas?
[Magisk] pndwal:
Could have something to do with this change:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-87128039

Quite a lot of issues like this with older android and 25+...

Assuming patching was done with the same App you are trying now (didn't patch with Canary?; App version must not be older than daemon version with recent Magisk), try using latest Debug App... It works for some... I'd also be interested to know if Canary build works (would indicate issue is fixed)...

Here's an open issue (similar, for Samsung):

https://github.com/topjohnwu/Magisk/issues/6257

Debug build worked but member hasn't been able to assist with latest logging data requested per:

https://github.com/topjohnwu/Magisk/issues/6257#issuecomment-1246157980

Perhaps you could assist there with debugging?... 👍 PW
[Magisk] Carne92:
nobody can help me?
[Magisk] Biz92k:
I never activated magiskhide because I don't need it... What's wrong my magisk?
[Magisk] X46X:
Hi, I installed Viper4Android in magisk manager but i don't have a Viper app installed. So i must install this app itself or there is something wrong?
[Magisk] xander33:
hard to know :(

i have this issue caused by magiskhide and many user here have reported that the cause is magiskhide

so my configuration is:

1-magisk v8

2-phh superuser 259

3-phh superuser app

4-magisk manager 2.1

5-xposed systemless

supersu 2.78 systemless on my phone as never worker (huawei p8 lite)
[Magisk] Biz92k:
I just enabled and disabled magiskhide, we'll see if that fixes the thing... I'll let you know!

I'm gonna go back to phh solution instead of SuperSU if that keeps to be unstable...

Thank you by the way! :)
[Magisk] licht77:
Hi!

I got problems getting Magisk running on a Xiaomi Mi5s - using the same procedure I used successfully on a Nexus 5.

I already started a device-specific thread here: http://xdaforums.com/mi-5s/help/mi5s-magisk-t3488955/post69381620#post69381620

Is there anything I can do to supply log files or further information to track down the problem?
[Magisk] grep_i:
Try to add 'root switch' to your setup or even 'Magisk hide', one of them should do the trick probably.
[Magisk] daskalakisp:
I follow this:

Download the latest Magisk zip file

Download the latest Magisk Version phh superuser from this thread:

[Magisk] [2016.10.4] phh's SuperUser

Flash both zips in custom recovery

Install the latest Magisk Manager for a complete Magisk experience

All good so far but i cant find root/unroot switch like Magisk Manager v. 1.2 i have root but icant play pokemon go or use android pay any help?
[Magisk] andrew2432:
That's over. No more switch, it's now magisk hide. Do you have phh gui app? Su permissions granted?

The next step is to go to magisk manager, settings/utilities, tick magisk hide and reboot. This should pass sn. If not, good luck in the forums.

http://xdaforums.com/apps/magisk/discussion-pokemon-magisk-discussion-t3465722

Pgo problems here ^^
[Magisk] daskalakisp:
ok all good...thanks :)
[Magisk] Biz92k:
Actually my phone didn't lose root since this trick... Maybe it's early to say that, but looks like I fixed it! :D

Looks like magiskhide is still unstable with supersu...
[Magisk] andrew2432:
Samsung galaxy s5 sprint version doesn't want to pass SN with magisk installed. enabled hide,did some wipes, and just with magisk installed it makes it fail. Not even trying xposed yet.

The only thing I can figure revolves around my kernel. It's stock but I have tried to use trickster mod and things. With magisk installed, I get a "set warranty bit: kernel" message. Some claim having permissive se Linux status will allow passing on smg devices, I'll report if I find anything there.

[Question]

Does the magisk Uninstaller also remove the phh version x files as well?
[Magisk] mathy007:
Anyone with systemless Xposed 86.2 by topjohnwu ? Should please help me with it
[Magisk] villo88:
Need help to fix it

Inviato dal mio Redmi Note 2 utilizzando Tapatalk
[Magisk] :
Mine was working up to about 15 mins ago.

Looks like a safetynet update detects root again.
[Magisk] AbiDez:
That sucks so much.... After 15 min everything runs fine... But yet :(

Argh....

CarHDRom V.25 by Carotix S6edge
[Magisk] negroxxx:
safetynet can already detect magisk

* all have the same problem

safetynet is red
[Magisk] villo88:
I was reading about an official update for safetynet but the test is passed, in fact it seems that some few devices get this error related to cts

Inviato dal mio Redmi Note 2 utilizzando Tapatalk
[Magisk] KrisDroid:
+1 Google, tweaked SN again. [emoji20]
[Magisk] requiiiem:
Clic the buttons...
[Magisk] smgoller:
For sure, I can help out. I'll try the canary build.
[Magisk] smgoller:
Canary build shows the same behavior. I can try with the debug build. Anything specific I should do?
[Magisk] pndwal:
I kinda expected that...

Consider GitHub issue?... Can't say more than Canyie did...

https://github.com/topjohnwu/Magisk/issues/6257#issuecomment-1242639704

Give it a try!

Separate suggestion:

You could try deleting contents of /data/adb (in case Magisk config files got corrupted), then reboot and Daemon will rebuild config fresh... This is a long shot really / bottom of barrel stuff...

😛 PW
[Magisk] smgoller:
I reflash the factory image every time now so I know I'm starting from a known state. About to install the debug build, will let you know if it works.
[Magisk] smgoller:
Debug build works. Did as requested in that issue: https://github.com/topjohnwu/Magisk/issues/6257#issuecomment-1248964967
[Magisk] veku DAZO:
I needed a question answered fast, sorry if it isnt appropriate here.

I found a "boot-gki.img" inside of my rom. Is it safe to patch it with a lower version of magisk, 23.0 to be precise
[Magisk] J.Michael:
This is not a web site for "safe".

If you have successfully flashed this ROM, you will probably be able to flash it again to recover from any failed experiment. Just don't count on your data surviving.

Is this the only .img file whose name starts with "boot"?

So you know what "gki" stands for?

Why do you want to patch it?

Why with a lower version of Magisk?

Have you successfully patched with the latest version of Magisk?

(I am assuming that "patch" does not mean just "patch a file with Magisk manager app", but also means flash the resulting file and manage to boot.)
[Magisk] veku DAZO:
There is another .img with name "vendor_boot.img"

Got some info on gki, no general idea on its impact yet.

Patching to flash via fastboot.

Lower version for the magisk hide feature, zygisk didnt quite work out for me

Yes, it successfully patched. And on the brink of flashing it, so yes your last paragraph is the info i need.
[Magisk] 73sydney:
you can try to temp boot the image

fastboot boot <boot.img file>

which is dfferent from flashing:

fastboot flash boot <boot.img file>
[Magisk] zgfg:
I don't know how the partitions are organized on your phone but generally be careful, boot and vendor_boot are different partitions, I don't really know what for is vendor_boot.

Maybe their images are the same in your case, who knows (you should check yourself for your phone)

Generally, installing Magisk requires to patch boot.img, not vendor_boot.img, and of course it must be flashed to boot, not to vendor_boot.

I have never seen a guide (specially, not in the official Installation doc on GitHub), talking about patching vendor_boot

I can only tell you for my phone (Xiaomi, MIUI 13/A12):

It's A/B device, hence having two slots, and therefore I have boot_a and boot_b, but then also vendor_boot_a and vendor_boot_b

You can inspect that eg from Terminal emulator:

su
ls /dev/block/bootdevice/by-name | grep boot

They are linked to different /dev/block/sde*

and by extracting and taking checksums, I see that their images are different - hence I would never flash vendor_boot to boot or so

And again, I patch and flash boot partition (only), never touched the vendor_boot

---

One more: if you use Magisk v23, then there is no Zygisk and you would not be able to properly use the modded USNF fix to pass Play Integrity

Also, be careful if going back and forth between Magisk v23 and v25, they have different database structures - to avoid ghosts issues, do clean installs
[Magisk] pndwal:
Can you say device and link ROM / version?...

I believe ROM distributions should include boot.img, even for GKI's; does yours include this in addition to boot-gki.img?

If boot-gki.img is actually the generic boot image as opposed to vendor boot image it should work as boot.img...

Some info:

Generic Kernel Image (GKI), is a complex change that rolled out in several stages starting with the v5.4 kernels in the Android 11 platform release.

The Generic Kernel Image (GKI) project addresses kernel fragmentation by unifying the core kernel and moving SoC and board support out of the core kernel into loadable vendor modules. GKI also presents a stable Kernel Module Interface (KMI) for vendor modules, so modules and kernel can be updated independently...

In Android 12, the generic boot image, referred to as Generic Kernel Image (GKI), contains the generic ramdisk and the GKI kernel.

For devices launching with Android 13, the generic ramdisk is removed from the boot image and placed in a separate init_boot image. This change leaves the boot image with only the GKI kernel.

With Magisk 25.0 we also have

• [MagiskInit] Support Android 13 GKIs (Pixel 6)

Spoiler content hidden.

👀 PW
[Magisk] ipdev:
Hi all. 🙂

A little OT but, since it has come up in discussion recently.

Generic Boot Partition (Android 12 and newer) - [source.android] - Link

PW already posted a link to the above.​

Ramdisk Partitions (Android 11 and older) - [source.android] - Link

Vendor Boot Partitions - [source.android] - Link

Cheers all. :cowboy:
[Magisk] lemonsqueeze:
Hi,

Just updated to latest Magisk on a Redmi 7A (Stock rom, Android 9, MIUI Global 10.2.5). Was working fine until now with an old version of Magisk from 2 years ago (never updated until now).

Now takes a long time to boot and reboots as soon as I try to turn on wifi like in #3715. I'll try to list the exact versions, but tricky now ! (reboots after a few seconds using the device !). Magisk is 22100 right now.

Anyone knows if there's a way to make it work with newer versions, or should I revert back to the old one ?

Also any bootloop fixes without flashing the whole device ? I'd rather not lose everything !

Thanks !
[Magisk] lemonsqueeze:
Ok so the new Magisk version I installed 25.2 and everything is hosed now, device reboots after 20s after lock screen.

How do I get rid of it ?? Everything I tried so far failed. Tried uninstall.zip method from twrp, no luck. Flashing boot.img no luck. Flash + Install + uninstall no luck... Install previous working Magisk, no luck. Something is really f*cked up !!

Seems some people report only way to properly uninstall 25.2 is from the app itself, not twrp. True or not ? Can't even try that anyway, reboots before I have a chance to open the app.

logcat before reboot shows some uncrypt stuff, encryption issue ??

/system/bin/uncrypt: received command: [--prompt_and_wipe_data
/system/bin/uncrypt: --reason=RescueParty
/system/bin/uncrypt: --locale=fr_FR
/system/bin/uncrypt: ] (59)
Perf : Connecting to perf service.
RecoverySystemService: uncrypt setup bcb successfully finished.
/system/bin/uncrypt: received 0, exiting now
ShutdownThread: Notifying thread to start shutdown longPressBehavior=1
[Magisk] pndwal:
Looks likely that users in this issue have restored previously patched boot.img after taking OTA etc resulting in mismatched kernel (it's in boot.img of course, and is updated with OTA)...

After any OTA (stock images should have been restored before taking OTA), users (on A-only devices anyway) should have downloaded corresponding full ROM and extracted / patched / flashed the newer boot.img...

Maybe you did something similar?

If you updated, why do you think Magisk is still 22100 (22.1)?

Please say if you have have magisk in boot; (most Xiaomi devices support this despite Ramdisk: No). Did you ever take update / flash with Recovery mode selected (Ie. patched Mqgiskinit to recovery ramdisk)?

In case something is messed up as above, I'd be trying to restore stable boot by flashing both unpatched boot.img and recovery.img from fastboot... Make sure you download full ROM corresponding to current ROM (especially if you've taken OTAs) to extract images... Alternatively, dirty flash the ROM.

If you believe you've ever decrypted data, you may need to format data (factory reset) to restore encrypted data partition...

After you restore stable boot, uninstall old Magisk app(s) including hidden/stub app if you took Hide the Magisk app option, install latest App and patch / flash extracted boot.img. Nb. De-select Recovery mode!

Reboot and check Magisk is installed.

If you were able to keep your data, install a root explorer and delete all contents of /data/adb in case your previous Magisk configuration was borked in any way (highly likely)... Reboot and Magisk configuration will be rebuilt clean...

A Please report progress. Hope this helps! 👍 PW
[Magisk] pndwal:
Further, I just saw your issue (bot closed) here:

https://github.com/topjohnwu/Magisk/issues/6271#issue-1376805565

If the above doesn't help (you've wiped magisk installation at /data/adb and definitely patched boot.img corresponding to installed ROM), you could/should open issue again...

You'll need to install Debug build and indicate this in first post as required. - Debug uses verbose logging etc, and issues won't be analyzed on release builds... Debug also corresponds to latest Canary, so will save wasted time if issue is already fixed downstream. (Did you try with Canary release version yet?)... Also, supply logs as required or issue will probably be closed immediately by Devs anyway until provided.

https://github.com/topjohnwu/Magisk#bug-reports

👍 PW