yashsingh1/xdaforums huggingface dataset:
[Magisk] Chizz3x:
Oh sorry, rushed a bit on this.

(Just for the record) The problem I am specifically having is left and right side of my touch screen are not detecting any input. The right and left sides though detect input if i drag my finger from somewhere else besides those sides into those sides. That can be debugged using the cursor in developer options. I have also tried adb shell commands like "ws" but that seems to be only for screen display adjustment, not input.

The device specifics are

Huawei P10 VTR-L29

EMUI: 9.1.0

Android: 9

BN: VTR-LGRP2-OVS

CPU: Hisilicon Kirin 960

It is one of my old phones i am just playing with and trying to learn some stuff about android devices. Here i am trying to root it using magisk. (This phone was bricked before lol)

My device has no ramdisk, as seen in the magisk app it shows ramdisk: no. I have found some guides online explaining that i need to extract boot/kernel and recovery/recovery_ramdisk images, patch them using magisk and the reflash them via fastboot. Which i did.

The exact procedure i took is in theres steps: https://xiaomi.eu/community/threads/guide-root-mi-9-lite-mi-cc9-with-magisk-no-ramdisk.64174/

More or less this is what i did, the only parts that dont match is how i extracted the image files from my device.

The steps i did:

1. Flashed a stock ROM and set it up

2. downloaded magisk app and installed it.

3. booted into bootloader and flashed compatibe twrp version into recovery_ramdisk

4. Loaded into recovery_ramdisk/twrp and bacaked up /dev/block/bootdevice/by-name/kernel and recovery_ramdisk images into my usb-org (using this because device cant read sd cards for some reason no matter the fs type)

5. booted into the system, opened magisk, with recovery mode checked patched recovery_ramdisk.img

6. The same way, with recovery mode **not** checked patched kernel.img

7. Transfered both patched images into my usb-otg

8. booted into bootloader and used fastboot flash kernel kernel_patched.img and fastboot flash recovery_ramdisk recovery_ramdisk_patched.img

9. Rebooted into the system normally, using adb rebooted into recovery_ramdisk which basically restarted the phone but with magisk according to the link above.

10. After a restart phone has root, except that one tiny problem with touch screen sensitivity.

Would like to know what am i doing wrong and how i can properly install magisk and get root access without getting my screen sensitivity chopped off or countless buggy reboots to have root access on my system.
[Magisk] zgfg:
The guide you quoted was from Xiaomi.eu Forum (?) and for Xiaomi phone (Mi 9 Lite)

However, I shortly googled specifically for XDA, your Huawei P10, A9, Magisk and found the Guide thread here on XDA. Basically, your procedure was ok - no Boot partition, patching recovery_ramdisk but interestingly there are reports about the similar touch-screen issues like yours

Suggesting you to take a look there and maybe ask there (but discussion was from 2019, don't know are there active users anymore), particularly see the following post with what seems to be a solution for your touchscreen issue (?):

Post in thread '[GUIDE] [EMUI 9] Magisk Root Huawei P10 VTR-L09 for Android PIE' https://xdaforums.com/t/guide-emui-...vtr-l09-for-android-pie.3916801/post-79332303

If so, seems to be something very specific for the particular Huawei Pie ROMs

(It's about P10 VTR-L09 there, yours is P10 VTR-L29 but if I remember correctly those Huawei shenanigans from 2017-2019 when I had P9, L09 vs L29 should be only a difference in memory size/configuration or so)
[Magisk] Chizz3x:
Well i be damned. Guess knowing how to google is a damn profession. This approach definitely fixed it and now touch screen issues are resolved. Also thanks for the info about the L09 and L29, I thought those are very different but if it's just memory size and configs i can use some of L09 guides.

Also, if i have magisk recovery patched, that means i can not use custom recoveries like twrp right? I know i read that somewhere. so i just wanna make sure.
[Magisk] zgfg:
You have a complete subforum on XDA for your model:

Huawei P10

Announced in February of 2017 at MWC, the P10 plus is the premium version of the P10. This Huawei flagship phone features a 5.5 inch display with 1440 x 2560 pixels. The Kirin 960 chipset has an octa-core (4x2.4 GHz Cortex-A73 & 4x1.8 GHz Cortex-A53) CPU and a Mali-G71 MP8 GPU. You'll have 64GB...

xdaforums.com

Q/A, Guides,Development (ROMs, Recoveries, etc)

and you can orobably find exact difference there between L09 and L29

Maybe (same thread/guide for rooting or another, Q/A ..) is it possible to patch/flash both TWRP and Magisk to ramdisk_recovery.

If possible, you would probably need to flash TWRP first and then patch Magisk - sonething like, install TWRP to recovery_ramdisk, backup that recovery _ramdisk and patch the backup with Magisk and flash back to recovery_ramdisk

In fact, if I recall correctly, Huawei EMUI phones used to have two Recoveries and you could even flash TWRP to one and Magisk to the other.

However, booting to that second Recovery is tricky and I would not advice to play with that second Recovery (actually, it's the lower/primary Recovery on Huawei phones) because that lower Recovery could save your ass if you brick the phone (that primary Recovery is needed to flash Huawei Service ROMs - last hooe for hard-unbricking if/when it happens)
[Magisk] Chizz3x:
Understood, thanks again. Also I have been digging through xda forums dedicated to my device model and i have failed to find much of useful information hence i lost hope. Seems like I should just dig deeper :P
[Magisk] pndwal:
Please say device/ROM... I assume it's an A-only device launched with Android 9 and you boot Magisk via key combo...

Edit: Sorry, missed the posts following and advice already given... Still, the following info may help understanding:

For one thing, you shouldn't have patched boot.img [guess that's ramdisk.img on your Kirin device?]... Magisk resides in only one boot image; in case of Ramdisk=No devices w/o bootloader support for ramdisk in /boot [or /ramdisk], the only supported boot image is recovery.img [or recovery_ramdisk.img]... You therefore patch that, not boot.img [or ramdisk.img], so [you should] flash back unpatched original boot.img [or ramdisk.img] and report if it's fixed... 🤠 PW

More in a post to follow...
[Magisk] pndwal:
@Chizz3x

So Huawei P10 VTR-L29...

Device launched with Android 7.0?...

Initially it seemed to me that you shouldn't actually need Recovery mode Magisk (as assumed above)... That was generally only needed for A-only A9 LV devices as mentioned.

... Now seems RAMDISK.img could in fact be patched and flashed to /ramdisk partition in Nougat and Oreo as expected, but something changed with Pie and users suddenly needed to patch RECOVERY_RAMDIS.img and flash to /recovery_ramdisk for P10 series devices...

Did Huawei remove /ramdisk partition altogether (presumably to retrofit SAR booting scheme)?... Or was there simply an issue with Magisk in /ramdisk after Pie update necessitating use of /recovery_ramdisk Magisk injection? (... I understand some partitions did in fact change.)

If /ramdisk partition does in fact still exist, I'd be interested if recent Magisk can now patch/flash that and work...

If the issue was simply that the method failed to root or bootlooped etc, it may well be fixed with the huge amount of refactoring Magisk has received recently, much of it for the sake of making more devices compatible... For example, some major changes were needed to made Magisk compatible with GKI requirements for devices launched with Android 13+ (Pixel 7 etc) which essentially separated generic ramdisk parts from the boot.img to a separate init_boot.img (vendor ramdisks had also been removed earlier) for project Treble and Mainland compatibility... And that is basically what Huawei seems to have already done from Nougat days with their unique separated partitioning, eg /kernel + /ramdisk instead of /boot etc, for Kirin devices...

If Huawei did actually remove /ramdisk partition (and moved to SAR booting scheme) w/ Pie update, you'll be stuck with Recovery mode Magisk (Magisk in /recovery_ramdisk partition) however. 🙃 PW
[Magisk] Galaxium:
How to sui with magisk
[Magisk] zgfg:
Open an app that wants Superuser access, it will ask to grant root - and grant

Use Terminal Emulator and type in su to run shell with root privileges (you will have to grant root to TE)

But make sure that Magisk is properly/fully installed - installing just the Magisk app does not mean that Magisk is installed and that you do have root. See Installation Instructions on Magisk GitHub
[Magisk] pndwal:
... On LSPosed going forward (from April 26):

🤠 PW
[Magisk] pndwal:
Payload dumper with performance gains (from May 9):

https://github.com/5ec1cff/payload-dumper

🤠 PW
[Magisk] pndwal:
www.x.com/GEEKCONTOP/status/1788167842191618193

... Wanna meet John (Hung-Lin) Wu and other team members in Singapore?... Better get a wiggle on/tickets... 2weeks!...

Go John! (But please don't harden Android too much 😜)

🤠 PW
[Magisk] zgfg:
A t-shirt with stop sign can do

Man Fools Waymo Self-Driving Cars With Stop Sign T-Shirt | Carscoops

A content creator with a stop sign on his t-shirt managed to stop Waymo's robotaxis in their tracks in Arizona

www.carscoops.com
[Magisk] bluegrass55:
"module suspended because zygisk is not enabled"

I have searched this forum for a solution without luck and have tried the following steps from online search suggestions without success.

(Zygisk is enabled in app settings)

Latest Alpha Magisk & Stable

Zygisk -Next module with built in Zygisk disabled as per instructions.

I need this enabled to use the Denylist module for Banking app.

Any advice appreciated.

Pixel 7pro

GrapheneOS A14
[Magisk] J.Michael:
Is there a setting in the Magisk manager app to enable Zygisk?

There is a Zygisk thread. Have you looked there? I could swear I just read about someone else having trouble activating Zygisk. I think he found a solution.
[Magisk] bluegrass55:
Yes there is a setting in the Magisk manager and I have enabled it and it shows enabled. However on the main page it says no.

I've tried looking for the Zygisk thread you mentioned without success. Most of the results comes with diffrent versions of it.

Would you kind enough to provide the link?

Thanks.
[Magisk] pndwal:
Not sure why... Requirement: • Built-in Zygisk turned off..m

... So what's disabled??

Maybe just turn off Built-in Zygisk?

If it's really disabled, behaviour almost seems to match what older ZygiskNext did, ie. showed modules suspended because app could only see inbuilt Zygisk is disabled... In fact ZygiskNext appears to be working; eg. "Shamiko is working in blacklist mode"...

However, since v4-0.9.0:

so seems Magisk App ("Manager") should now show Zygisk and module status properly...

So the issue may be your congratulation... I know KSU may have limitations when a non GKI or pre-5.10 kernel is used (and rely on non-official dev support and are built by user), however it looks like GraphineOS is probably issue... From another recent convo:

So Graphine Devs definitely don't support root as they're all about having a proper security model... Further, apparently Graphine modifies Zygote and their sandboxed version of PlayServices (with custom app.grapheneos.gmscompat compatibility layer) cause issues for normal Magisk use, and official Magisk and ZygiskNext Dev stance is that they won't support these implications unless they're adopted officially in AOSP although Kitsune Magisk Dev has...

Further, as I commented, current Android 14 (QPR2 beta+) changes broke the original GraphineOS specific fix in Kitsune Magisk as well as Zygisk in official Magisk. That was fixed in Dec, but Kitsune still hasn't fixed their GOS patch although lbdroid has supplied a working test build...

The experienced members I quoted above may also be able to help/comment further...

Personally, I'd be avoiding GraphineOS if you want root and associated benefits... Hope it helps. 🙃 PW
[Magisk] J.Michael:
Magisk - The Age of Zygisk is what I meant by "Zygisk thread".

I'm confused: You just said you have Zygisk enabled in the Magisk Manager app *but* it shows disabled on the main page. In an earlier post you said you had Zygisk disabled as per instructions. Which is it?

If Zygisk is disabled in the Magisk Manager app, doesn't it make sense that Magisk Manager reports "Zygisk: No", and Magisk modules flagged as requiring Zygisk are disabled?

Does the Zygisk-Next module have a UI where you can enable Magisk modules?

I did read @pndwal's post. Maybe that's the final answer: You can't use Zygisk with that ROM.
[Magisk] bluegrass55:
Without Zygisk-Next and with Zygisk enabled within the app, on main page it says "Zigysk: No".

With Zygisk-Next and Zygisk disabled in the app Modules don't work. The isn't a UI for Zygisk-Next.

Yes it does seem incompatible with Graphene.

Thanks for your help.
[Magisk] bluegrass55:
Thank you for all the links and info. The ROM its self is good and all my banking apps work without Root. The only reason I rooted was to re start using my call recorder. Graphene has a built in recorder, but doesn't record WhatsApp and Signal calls.
[Magisk] pndwal:
new safe mode ...

auto enable safe mode after failing to boot twice in a row

#7923 by vvb2060 was merged 4 hours ago

Great Stuff!! 👍 PW
[Magisk] J.Michael:
Glad I'm not the one trying to test it.
[Magisk] wilsonhlacerda:
I disable Safe Mode on my devices by using app Test DPC (others similar on Device Owner mode can do same, among other powerful stuff).

It will be interesting to known if Magisk auto enable can/will bypass that or not. The ones testing should consider that scenario.
[Magisk] wilsonhlacerda:
{Mod edit: Quoted post has been deleted. Oswald Boelcke, Senior Moderator}

Don't publish your IMEI! Edit your message.
[Magisk] pndwal:
Not quite sure what you're doing, but I think this new failsafe feature doesn't even activate system/Android Safe mode... It just means it'll boot full Android with Magisk in 'Safe Mode' in cases of modules breaking boot.

Magisk Safe mode is simply Magisk with modules disabled, (possibly Zygisk disabled also, like old 'core only mode, but I think this has changed)... Users can next remove suspect modules and re-enable others.

For Peace of mind when installing modules, knowing we'll simplify have to boot 3 times when it goes to custard. 👀 PW
[Magisk] wilsonhlacerda:
I disable Android's ability to boot in Safe Mode, the Android one. So no one can boot in Safe Mode by hardware keys or power menu/other software tools. Also I disable Factory Reset and other stuff.

I do that for security reasons - working together with an app locker and hider -, in my case because it is common in my country to be robbed and forced (with a gun in head) to quickly unlock device or have it snatched unlocked while using in streets/car. Without Safe Mode they can not bypass app locker / hider and later access critical apps like banks, email, SMS (that they use to gain bank access and transfer money).

This is also enforced on some corporate devices worldwide by using MDM platforms (same as I do with app Test DPC locally in my case for my personal device), to avoid employees/third parties disable spying/remote access apps, access critical data.

Obviously I do that because I also use a custom recovery (TWRP) so I can boot/decrypt thru it if necessary to format / recover files on unexpected scenarios (bootloop or whatever).

Concerning own Magisk Safe Mode (= disable modules only) I remember it, I'm on Magisk since its first days. But afaik lately Magisk use to trigger that only by booting Android Safe Mode. If that's what the new implementation is doing (thus not only disabling modules) then my concern is valid, and better test it also with Android Safe Mode disabled.
[Magisk] zgfg:
When Magisk detects that Android booted to Safe mode, Magisk creates a certain hiden file telling Magisk that on next boot (and all further, as long as the hidden file remains) Magisk must boot to the Core Only Mode (IMO, that's the proper name)

However, the same hidden file for Magisk can be created by other means. Like from TWRP or by some modules - search on GitHub

For the path/name of that hidden file look to the Magisk documentation. Maybe it was /cache/.disable_magisk but I don-t remember. Search on the Net. Or execute from Terminal Emulator (or use a root Explorer like MiXPlorer to create the file):

su -c touch /cache/.disable_magisk

and reboot to test

The fact that you disabled Android Self mode has nothing to do with the Magisk booting to its Core Only Mode. Totally different things. You just disabled one possibly useful way for you to trigger Magisk to boot to its Core Only Mode., but there are still other ways to trigger the same
[Magisk] pndwal:
Interesting scenarios... I think they'd still need gun-to-head approach to get password/pattern first right?...

I think you're recalling Core-only mode... I believe that disabled modules, root apps and Zygisk?... I think Magisk 'safe mode' only disables modules per FAQ description (but possibly Zygisk too?)... Take a look:

https://topjohnwu.github.io/Magisk/faq.html#q-i-installed-a-module-and-it-bootlooped-my-device-help

Actually, Magisk Safe mode can be triggered w/o entering Android system Safe mode at all as described. (BTW, the wording in "I installed a module and it bootlooped my device. Help!" Section from "please note..." is mine, after we diagnosed key detection issue on Xiaomi devices; I think it's destined for the chop soon however since key combo trigger will probably be redundant. 😂 ) It was supposed to trigger reliably after Android Safe mode was activated but simply detects the same key combo with different timing in practice as explained, causing Magisk daemon to create empty files named ‘disable’ in modules directories... The actual disabling occurs when full system is finally booted...

So as can be seen, Magisk Safe mode only 'piggy-backs' off Android Safe mode key combo, and intrinsically Android Safe mode itself is doing nothing even as things are now...

With next Magisk builds I expect Android Safe mode will not be invoked by the new Magisk Safe mode implementation because it's entirely unnecessary... Because the Magisk daemon is working (eg. detects key combos) before bootloop occurs, it can simply count and log boot attempts, then create empty files named ‘disable’ in modules directories after two bad boot attempts...

This is also better for users in general as Android Safe mode disables several Android functions that must be reconfigured later... That should no longer occur. Happy days!

Look forward to your test reports with bad/incompatible modules and your custom Dead-Safe-mode configuration... 🙂 PW
[Magisk] Rienquejefourretago:
Hello,

I installed magisk on the nvidia shield 2017 because I temporarily needed an app, renaming magisk.apk to magisk.zip on LOS recovery, and then installed from the magisk app via recovery

I would now like to uninstall it, is it enough if I do "complete uninstall" from the magisk application or do I have to reinstall the stock rom? Or it will be removed during the next lineageos OTA update ?

Thanks
[Magisk] zgfg:
Generally, Complete uninstall (and confirm if it asks you further) should be ok:

Alternatively, rename apk to uninstall.zip and flash through TWRP.

Or do both (in that order)
[Magisk] Rienquejefourretago:
Thanks i flashed uninstall.zip but magisk reappears

So i use the complete uninstall for now, does the OTA lineageos 20 update will clean magisk ?
[Magisk] zgfg:
I never use LOS

But FIRST of all, please be very precise when asking for help, what does it mean "magisk reappears"?

Are you talking about Magisk app, Magisk root/'mask'/su, modules, what?

And to assure that there is no mistake and missunderstanding, please provide screenshots, like from the Magisk app (if that "reappears") main screen where it shows is Magisk itself (service, mask - whatever you call it) installed or only Magisk app

You can execute magisk -c from Termina, and/or su and document what you get
[Magisk] boggdy:
Recently I'm having an issue with Android Auto. The box show unchecked in DenyList. If I open Android Auto it checks by itself right away. I close DenyList, I open it again and the box next to Android Auto is unchecked.

Same thing for Google Service Framework and MTP Host.

But the problem is that Android Auto won't connect to my car's stereo since I have this issue.

Pixel 8 Pro, May update.

Any help is appreciated.
[Magisk] zgfg:
OMG, why do you put every single Google app to DenyList?

Have you tested without, and all those apps do not work without?

Of the Google ones I have literally only three as on the screenshot

I rarely use AA, last time probably a month or two ago, but I never had AA in DenyList and so far it always connected for me
[Magisk] J.Michael:
If by "open Android Auto" you mean you tap on the Android Auto entry in the Deny List, and by "checks right away" you mean the opened-from-Deny-List dialog has a check box already filled in, look again, maybe there is an explicit Save button you need to click.

How are you dismissing the dialog where you see the check box already filled in?

Maybe it's the Deny List itself that has a Save button.

(I have no explanation for how you managed to check so many other boxes. Any chance you did them all one time, and *that* time you used the Save button?)

But listen to @zgfg, you shouldn't put anything into the Deny List without a reason. It is not "playing it safe" to just include everything, it is risking causing problems.
[Magisk] zgfg:
When you 'loose' AndroidAuto in DenyList, test by CLI from Terminal Emulator:

magisk --denylist ls

to see does it still list

com.google.android.projection.gearhead

ie, the package name of AndroidAuto as checked in DenyList

I think it's just a hide and seek game.

AA is something built-in, not really an app. Tthere is no icon to open AA, you can only open its settings. AA just 'connects' to the AA supporting head unit in the car

(Like when you have an app in DenyList but then you uninstall the app. It won't show in DenyList but it will be still listed if you check by CLI. You reinstall the app and it automatically reappears in your DenyList)

But I'm still not convinced about the purpose of putting AA to DenyList. Maybe if using Screen2Auto to show apps not allowed for AA (another cat and mice game between G and hackers), but what for else

---

Btw, DenyList has no Save button. It automatically saves when you check or un-check an app. That's why I'm always afraid when I open Configure DenyList and scroll down, that I may inadvertently uncheck some apps
[Magisk] pndwal:
Further to the above, be careful what Google apps are on DenyList, even with modules hijacking the list for hidelist mode unmounting...

Adding Chromium-based browsers or apps using WebView to the Magisk denylist or enabling unmount for them may cause them to crash or malfunction, so don't enable this feature for these types of apps. It seems Shamiko may now include a fix for this however...

This was first pointed out by TJW, but the root (pun intended) cause for has only recently been properly understood it seems... For those interested:

Spoiler content hidden.

👀 PW
[Magisk] woj_jas666:
Hi

After Oneplus 12 OTA update to oxygenOS PCH2581_14_0_0.610(EX01) i lost root access , Magisk has stopped working so i decided to reinstall it :

Here are steps that i've done:

0. Reflash modified img with fastboot , remove magisk from apps then:

1. I'm opening downloads folder

2. Im clicking install on Magisk-v27.0.apk

3. Im clicking "install" on installation question prompt

4. After notification that application is installed im clicking "Open"

5. I'm getting toast message -> something went wrong

I still can see that LSPosed module is available on my notifications bar so i think something stucked with magisk , how can i fix it ? If any log is needed i can provide it