yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Actually, I'm rethinking my earlier comments a little...

Realised that as launched with A7.0, if B/Ls has not been updated (?) device likely still has old Verified Boot rather than the new/enhanced Android Verified Boot... I hadn't considered launch version but guess running A10 doesn't necessarily mean having AVB... This may account for modified boot image working w/ 8.1 locked... I guess signing keys may not be checked with Android 10 either if B/Ls remain the same...

This means it's possible that other (vbmeta hash/hashtree?) checks may in fact be the issue... I don't understand how newer vbmeta partitions interact with old VB (A4.4+) as seems they were designed for AVB (A8+)... It is strange that @badabing2003 found stock vbmeta is already zeroed out; that's usually done to bypass AVB... but maybe A10 requires vbmeta partitions so dummies are used since device only has VB (not AVB)?...

Also, the checks being bypassed by zeroing working in stock configuration really means they should with Magisk too...

Also, yours is a strange/interesting beast in other ways it seems... Is it definitely an A/B slot device ?... I thought that Pixel was the first to have legacy SAR and A/B updates w/ 7.1, but yours seems to be earlier than the Google model/flagship with 7.0?! 🤔... most other devices with the exception of OnePlus didn't have A/B (SAR) till Android 9...

So nothing springs to mind by way of a logical solution...

I would like to see Magisk 'Detected device type' info from top of a Magisk log saved to selected download folder (must save, doesn't appear in brief log on screen)... Want to know if it's really legacy SAR or was legacy ramdisk type (those are converted to modern ramdisk 2SI 'SAR' on updating to A10...

Another long shot, since it patches and boots just without root, I wonder if all the recent major Magiskinit injection refactoring might be a problem... To test this, I'd go way back and try booting with Magisk 24.3... in that version Magisk actually did patch vbmeta for 2SI devices in order to patch fstab... now (with refactoring) it patches the original init to redirect the 2nd stage init file to magiskinit and executes it to mount partitions...

🤠 PW
[Magisk] portsample:
...complete Magisk log file was attached to previous post :)
[Magisk] berrynddonut:
Greetings! Is there any chance there will be a Realme C55 module any time soon? Also, is rooting your device any good in general? Thanks
[Magisk] zgfg:
What do you mean by "Realne C35 module? Module for what (for camera on that phone, for BT on that phone, something for WiFi for that phone, etc)

Magisk is generic. If you are new to Magisk, please start by reading the installation instructions on the Magisk GitHub page
[Magisk] berrynddonut:
Ah sorry, i think that was the tldw recovery tool or smth

Isn't that necessary tho?

They don't have a module for REALME C55 phones!
[Magisk] zgfg:
Again I don't understand what are you asking for?

Are you asking for TWRP (custom recovery) for your phone

Try to find a subforum on XDA devoted to your phone. Look to the guides there, under ROMs there and other development, post your question under Questions

That's the place where you can find the accurate info related to your phone

This is here a general/generic thread about Magisk. There is no specific Magisk for Realne or some other phone

Eg, I have Xiaomi, many others have Pixel or Samsung, etc - you will hardly find here an info, like you're asking, if somebody is developing a "module" for your phone
[Magisk] berrynddonut:
Yes I'm asking about the TWRP tool

I thought it had something to do with magisk.

Now I'm confused too!

Is there any difference between a regular downlaod and a recovery option?

Because when i try to download TWRP i don't think they have a version for my phone, I can't find a version for Realm c55.
[Magisk] zgfg:
Magisk is generic and Magisk can be installed WITHOUT TWRP.

Again, did you read Instructions on the Magisk GitHub - TWRP is not the recommended way

I googled and in less than a minute found this - did you, and did you read eg:

https://www.getdroidtips.com/root-realme-c35-rmx3511-magisk/

TWRP must be ported to a particular phone. That's why I told you to try to find a (sub)forum, TG channel or something where ppl are discussing about that particular phone. I have no idea are their some unofficial or beta TWRP, OrangeFox or SHRP ports for your phone.

And I doubt you will reach here in this Magisk thread somebody else who will know that

So if you looked for TWRP for your phone (it's not called a module but anyway), then probably there is no one.

It takes time to develop. And usually it starts that some developer buys himself that phone, finds that there is no TWRP yet and starts developing

But nevertheless, Magisk can be installed without TWRP, see above
[Magisk] berrynddonut:
Just wanted to make sure, but if it's not recommended than no need for it i suppose, as for my phone it's c55

Not 35

But that doesn't matter much!

I will read the instructions on the GitHub and downlaod the root, hopefully nothing goes wrong as I'm not experienced with backing up my android and I'm going without backup,

What could go wrong!?

Anyways, thanks for the help!
[Magisk] Nergal di Cuthah:
Step one of rooting anything is bootloader unlock which WILL wipe yoir phone
[Magisk] zgfg:
Good luck in "downloading root"

I really suggest you to take time, to read, learn and then to decide

Yes, things can go wrong - you download and flash a wrong 'module' or wrong 'root' and you will brick your phone

The warranty will not apply. Un-bricking the phone requires even more deep knowledge, and a specific knowledge for that phone/vendor, and sometimes the tools that are very specific per phone, and that can be hardly found or not available for free

Even searching on the Net for a PAID HELP (they can do it remotely , by connecting to your PC) might be frustrating for a novice
[Magisk] badabing2003:
Why do people mod and experiment with their own devices? :)

Yes this would be correct, but as you pointed out later:

What I don't understand is why vbmeta is all zero, which means it does not factor into play other than just needing it to be there,

Unless the current active slot is B, and we only have the vbmeta of slot a.

@portsample why aren't you dumping both slots?

My limited understanding aligns with yours.

No you got it in your last post, the bootloader or the ro portion of the old device is not forward proof probably.

What's the difference betweeb stock_boot.img and boot_a.img, and where is the boot_b.img file?
[Magisk] portsample:
Same same. Renamed only for patching. Only been patching boot_a.img...I have not been touching boot_b.img.
[Magisk] badabing2003:
stock_boot.img SHA1: e84bb8cfe0eae099b43d5210528147b78d1cb0d9

boot_a.img SHA1: 209cb9fe9063e51ef45ffebecacdd969d323c87a

Not the same

Only been patching boot_a.img is not good enough.

If you have A/B phone, and your active slot is B

if you dump A, create a patch from it and flash that to either A or B (B by default if you don't specify and B is your current) you won't get root.

Which could be the root of your issues and not vbmeta.

Connect your phone to PixelFlasher and see what it detects, what is your current slot, you can also hit the Device Info button and get additional details.

If you want to create a patch using PixelFlasher

In your case because you don't have full firmware or full OTA, you'd have to use the needle icon to create a patch

Make sure you create a patch from current active slot's dump of boot.img

Also make sure to dump vbmeta.img of the current active slot.

So far have you tried flashing patched boot.img on Android 10?

if so, do you just bootloop?

If you have not yet tried, please don't blindly flash any patch you create, you want to make sure vbmeta / AVB is truely not in play otherwise you could end up bricking your phone.
[Magisk] pndwal:
I saw your magisk_install_log... doesn't contain what I asked for...

In proper (complete) magisk_log... you should see like this at top:

🙃 PW
[Magisk] badabing2003:
Where do you see these logs?

in logcat or the one displayed on screen by Magisk when patching which is optionally saveable.

To be honest I have not seen these myself in any of my patching.

Perhaps it is device or version specific.

in any case, we know his device is A/B and it has Ramdisk
[Magisk] pndwal:
Actually, I'm sorry if my previous post seeded to contradict... I think we're really on the same page here, and your comment zeroed vbmeta in stock setup confirmed it...

I really just wanted to know what I was missing (as I asked) as seemed whole approach still focused on patching/stripping vbmeta.. I think it's a red herring, but quite ok to be proven wrong... Seems it really belongs with AVB, but appears we have it with old VB due to updates so I may be conflating/confusing things... 😆

A/B (and SAR?) before Pixel is even more surprising/confusing... PW
[Magisk] pndwal:
Magisk one when optionally saved... Much more verbose when saved... 😜 PW
[Magisk] pndwal:
Member said:

My guess is that leaving 'dummy' (empty) vbmeta alone should be fine if it was stock... Should mean verity and verification are disabled anyway IINM... PW
[Magisk] badabing2003:
Yep, we're on the same page.

I'll check again, when developing PF and testing, I saved those files quite often.

I suspect, he's patching boot from inactive slot which would still be on 8.1 and applying it to 10.0 boot and causing bootloop, just a guess, we'll know more when we get dump of both partitions both boot and vbemta (just to make sure both are zeros).
[Magisk] portsample:
Okay...attached is the patch created using Magisk 24.3, as well as the stock boot it was built from and the generated log file(s).
[Magisk] portsample:
Okay. Here is the aforementioned Magisk log. My apologies for the delay. Thanks.
[Magisk] zgfg:
Patching with Canary 26301.

Screenshot and logs attached

I don't have your "Detected device info" block (and I never saw)
[Magisk] pndwal:
Again, that's a magisk_install_log...

Please just save and find a magisk_log...

👍 PW
[Magisk] pndwal:
Very interesting... "isAB=true, isSAR=true"...

Either they had SAR and A/B before first Pixel, or they managed to retrofit A/B updates... Can you say if device was A/B when on A7 or 8?... 👍 PW
[Magisk] zgfg:
Ok so you mean this

Spoiler content hidden.
[Magisk] pndwal:
Did you try booting with that? PW
[Magisk] pndwal:
FWIW, seems Devs have now fixed the Shamiko issue in Alpha-only private Shamiko test build:

... Hold your horses folks... 😋 PW
[Magisk] portsample:
Was not A/B before A8.
[Magisk] portsample:
Not as yet. When these devices were updated to A10 several years ago, others tried using the then available Magisk to root and were unable to. Those methods had worked fine previously on A8.1.
[Magisk] rockingondrums:
Hello Magisk people, it's been several years.

Pixel 7 Pro.

I just clean flashed [ROM][13.0_r82][OFFICIAL] Evolution X 7.9.8 [09/19/2023]. Despite what their OP says, I was not able to flash Magisk as either apk or zip in recovery. So I booted, restored from my damaged phone, and installed app to patch image as instructed here: https://topjohnwu.github.io/Magisk/install.html

I wasn't sure if I had to or should disable verity / verification. I tried to boot without doing so. Bad boot (back to bootloader). Reflashed patched image and also vbmeta. Bad boot again.

It appears there are missing steps or notes because I have followed instructions exactly.

I'm going to dirty flash the rom to restore working boot and try again

Any help greatly appreciated! TY
[Magisk] pndwal:
Are you patching init_boot.img as instructed, NOT boot.img?... PW
[Magisk] rockingondrums:
Oh I patched init_boot, I just flashed it to boot 🤕💀

Would you be so kind as to explain the verity thing? Why would I want to disable it? Why wouldn't I want to?
[Magisk] pndwal:
Best to check/ask/follow here:

https://xdaforums.com/t/september-1...er-root-pixel-7-pro-cheetah-safetynet.4502805

for your device... Read opening posts carefully... Very helpful bunch... 🙂 PW
[Magisk] ZG_DEV:
hey

how can i update from magisk 26.1 to the latest

i tried to patch boot.img+ direct flash using magisk, did not update

i tried to patch stock then flash, i got a bootloop

it seems that i am a newbie on updating magisk ToT
[Magisk] pndwal:
Do you mean you see old version or N/A?...

If N/A and you had hidden Magisk in stub app (taken Hide the Magisk app), locate previous hidden app as you named it (default name is 'settings') in system settings, Apps, and uninstall it, then try opening new full app... If not that, please give details about device, ROM etc... 👍 PW
[Magisk] DaOldMan:
You were correct. I supplied all info in a bug report on github and the bug is already recognized and fixed. I had to recompile the rom with a fix and then also compile Magisk with a fix and now there is a fix for my rom in the next version of Magisk. Great. Thanks for sending me in the right direction.

Cheers.
[Magisk] pndwal:
Nice resolution... Any progress on the S/N, PI deviceIntegrity front?... Tried both @Displax modded USNF and @chiteroman PIF?

Good to see new dev help on Magisk Github too... Wang Han (@aviraxp) and Howard Wu (@howardwu, @Howard20181) ascending... 👍 PW
[Magisk] DaOldMan:
ViperOS is 7.1.2 . Most of those modules don't support android 7. For now I can't pass safetynry 😪
[Magisk] pndwal:
Displax mods should... try 2.4.0 mod 1.3 if haven't...

You can use modded USNF but don't really need it for pre A8 (keymaster 3) launch version devices... No need for main fake keystore registration (triggers exception --> fallback to basic only attestation on device) function or prop based mismatches to bypass server side hardware-backed verdict enforcement... Only need the fingerprint prop for custom ROMs not setting this, hiding root from GMS Droidguard process and 'sensitive' prop settings...

For you, just adding Google Play Services Droidguard/attestation (com.google.android.gms.unstable) process to denylist and setting "sensitive" props in ROM or by installing MHPC module to reset these to non-suspicious values (no need to configure this; does it by default) should get both S/N ctsProfileMatch and PI deviceIntegrity passing as long as you also have a working fingerprint prop set in ROM or selected from MHPC list...

🤠 PW
[Magisk] DaOldMan:
Excellent. Works just fine. Just put gsm.unstable to denylist and that's all. Thanks a lot.
[Magisk] pndwal:
So your ROM must have already been passing!... You must have had fingerprint and any sensitive props set properly already... All that's needed after installing Magisk is to hide root from that Droidguard GMS process... 😜

Aside: If you ever update ROM to A11, you'll need to add main GMS process (com.google.android.gms) also... PW
[Magisk] RockerAlex:
Hiding Debugging seems impossible but what is this other error? Anybody know what it refers to?
[Magisk] sawdoctor:
Not sure if this will help or not but it's supposed to hide developer mode

GitHub - Xposed-Modules-Repo/xyz.xfqlittlefan.notdeveloper: 我不是开发者 / IAmNotADeveloper

我不是开发者 / IAmNotADeveloper. Contribute to Xposed-Modules-Repo/xyz.xfqlittlefan.notdeveloper development by creating an account on GitHub.

github.com
[Magisk] RockerAlex:
Doesn't hide from Momo sadly
[Magisk] hanschke:
Android 14 QPR1 Beta dont work for me or is this my Pixel Fold problem only?​
[Magisk] sawdoctor:
Your going to have to give a bit more information than that. What doesn't work? Does it fail to root ? Which magisk version?Do you have any logs if magisk fails?
[Magisk] hanschke:
I have taken latest build and stuck on bootloop. No addons. How to log IT?
[Magisk] sawdoctor:
Latest stable or canary and are you using fastboot or pixelflasher? Pixelflasher will automatically get the logs, this thread will help with magisk logs

MagiskHelp:Magisk and MagiskHide Installation and Troubleshooting guide

didgeridoohan.com

The more information you can provide the more people can help identify the issue. I've seen some people struggle with root others have had no issues with the latest beta
[Magisk] amadraeika:
i wanted to install Magisk Module without root/magisk installed. it is will work? can i patch using recovery?
[Magisk] Fishawy:
Magisk = root.

Modules cannot be installed without rooting your device, which is the whole point behind Magisk in the first place.
[Magisk] portsample:
Success! (of sorts)

Installing a patched boot.img on boot_a AND boot_b has resulted in root privileges.

But now I have no wifi.

Suggestions for how to resolve this?
[Magisk] ben_deez:
I have a OnePlus 7 Pro and Magisk 26.3 broke my System UI. Is there any fix for the latest update of Magisk for the OnePlus 7 Pro? The update renders my phone useless and I have to restore a backup of my Boot Partition and downgrade to version 26.2 to get it to work again. But now the Magisk app constantly gives my an "Update warning notification"....... But I don't dare to update it.

Magisk 26.3 breaks my System UI on my OnePlus 7 Pro. I have no nav bar and no settings app. I have to re-install 26.2 and restore a backup of my boot partition. I wonder if these issues are related in some way?
[Magisk] Nergal di Cuthah:
Please dont post multiple times the same question, especially on that short amount of time. Someone will answer if you give them a chance but I've come back here three times in 30 min to read the same question. It also might be better to post your question in the device specfic board for your device as it sounds like an incompatibility with your software.
[Magisk] ben_deez:
Listen bro.... I've tried to delete the multiple posts and there is no option to do so..... so either tell me how to delete them or move along. Thank you
[Magisk] zgfg:
Click to Report and explain to moderator that you want a post to be deleted
[Magisk] BillGoss:
Given that the OP 7 Pro is a 64-bit device, then No, the issues aren't related.

Also, I see that that you've been having this problem since April this year when you posted https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88432199 and that would have been when Magisk 26.1 came out, right?

And I assume that you managed to fix the problem back then. And that you also successfully updated to 26.2.

So, it seems to be that there's something about your setup, rather than Magisk itself.
[Magisk] pndwal:
... Ah, forgotten details... locked bootloader still? Using EDL to flash?... Are you definitely patching a boot image exactly matching running ROM?...

Issues like that are classic symptoms of mismatched boot.img, eg user updates ROM then flashes previously patched boot.img... Many system updates require corresponding changes in kernel which resides in boot.img... PW
[Magisk] pndwal:
John has always been vocal about properly enforcing Linux security enhancements, especially as they're quite compatible with root... So why not enforce it properly?:

Do not support systems without SELinux

topjohnwu committed 5 hours ago

... What else would you expect?... He works for Android platform security... 😁

Good stuff... Root as secure as possible... 👍 PW
[Magisk] rodken:
I suppose that the migration into Rust is moving full steam ahead.
[Magisk] kullurumanoj:
Hello Everyone, Can anyone guide me of there is a solution for my issue already. I'm using OnePlus 9 pro Indian variant.

It was all working fine until 26.1. Now when I have tried to install with that version(26.1) and the latest 26.3 and 26.2 none of these works for me. I can temporarily boot into the device with root but while doing a full setup i.e the app asks to do a full setup I'm losing the root.
[Magisk] zgfg:
You didn't describe which way are you.installing: TWRP, Direct install or Patch and Flash
[Magisk] kullurumanoj:
My bad missed adding it, I'm flashing patched magisk via fastboot. No twrp involved
[Magisk] zgfg:
Is your Magisk app showing Randisk Now

If so, when you open Install, before patching or Direct install, untick Recovery option

Maybe it will help (if previous attempts did not already make more mess) - that's a known (confirmed here couple of times) regression bug in v26(.3)
[Magisk] BillGoss:
I've come across the situation with another user who had a similar issue and it turned out to be one of the Magisk modules they had installed that caused the problem.

I would suggest deleting/disabling all modules other than USNF* and then trying again.
[Magisk] andrew2432:
Downloaded a factory image, unzipped the boot to my phone, installed magisk APK, tried to patch the boot file, says failed. Already screwing up and haven't started...lol

Haven't unlocked my bootloader but I'm just trying to patch the boot to start?
[Magisk] andrew2432:
Ok I have a pixel 7 so i downloaded the entire bootloader not the boot image, great job tjw for preventing me from fknxksnknssknsin up my phone

EDIT: Follow instructions
[Magisk] bombadier:
Look for a pixel rooting guide you need to patch the init_boot.img and not the boot.img on the Pixel 7

https://xdaforums.com/t/september-1...r-root-pixel-7-pro-cheetah-safetynet.4502805/
[Magisk] sawdoctor:
If you are unsure/want an easy way to root and update your phone then use pixelflasher
[Magisk] zgfg:
Question about shortcut for LSPosed (Parasitic manager)

I remember in the good old days, LSPosed gave you the option to set shortcut to the home screen (or it did automatically), hence you were free to uninstall LSPosed app (for Parasitic manager functionality)

I uninstalled and reinstalled LSPosed, and now I cannot set that shortcut anymore - I looked into the LSPosed manager settings, there is no option to set the shortcut

And LSPosed app complains/suggests to use the shortcut (screenshot) but it doesn't set it?!

---

Btw, I know that I can open LSPosed from the permanent notification (hence also no need to leave LSPosed app installed), but I do want to also have a shortcut on the home screen

Btw, I have attached below screenshots for all settings (LSPosed and Android System), what must be allowed to have that permanent LSPosed notification active (once I disabled that notification in Android Systems and when I lost the shortcut, I had to spend time to find how to allow the notification back)
[Magisk] asripath:
Lsposed settings - force apps to show launcher icons
[Magisk] zgfg:
No use for me - I have it (screenshot) and I also have allowed LSPosed to create shortcuts in the Settings/Apps/LSPosed but LSPosed does not create the shortcut
[Magisk] asripath:
Perhaps a regression from 6990 to 6999?

Edit

Did you use the root-data-adb-lspd-manager.apk to install the manager?

Per my understanding...

If you enable status notification no shortcut will be created
[Magisk] vudungcom:
Hi all,

pls help me to bypass banking app, it detect rooted device and refuse to run.

https://play.google.com/store/apps/details?id=vn.com.techcombank.bb.app&hl=en&gl=US

it use Magisk latest and add it on denylist, hide magisk but did not bypass,

could you give it a try.

Many thanks.
[Magisk] zgfg:
Manager.apk form /data/adb/lspd is the same that is in the LSPosed zip.installation package and that LSPosed installs when installing the module

Yes, I tried by reinstalling the apk zillion times but it doesn't attempt to create shortcut - it just suggest to better install the shortcut

Btw, on the other phone I have both shortcut and notification, hence one should not exclude the other. Btw, in its own Settings, LSPosed has options to independently allow both, shortcut and notification
[Magisk] zgfg:
Solved by installing Zygisk-LSPosed v1.9.1 (7001)

It has Create shortcut option in the app Settings
[Magisk] HippoMan:
I learned that I can get into the LSPosed manager by running this ...

/system/bin/am start -c org.lsposed.manager.LAUNCH_MANAGER com.android.shell/.BugreportWarningActivity

If you're using Tasker, you can create a task to invoke this via the "Run Shell" action, and then you can export that action as an apk file which will install a shortcut on your Home screen which runs that Tasker action.

I did that, and I can now run that shortcut to get into the LSPosed manager, just like the parasitic manager lets us do.

I'm guessing that there might be other utilities in addition to Tasker which also let us create shortcuts to run scripts like this.