yashsingh1/xdaforums huggingface dataset:
[Magisk] AAnnunziato:
Hey guys, I'm new to this forum and to this world of rooting and stuff (sorry if I'm posting this on the wrong place).

I installed magisk in my phone and it was running perfectly, until I started to look for modules to install. I found a Zenfone 6 camera module and I downloaded and installed it. The thing is I'm stupid my phone is already a Zenfone 6 and I just downloaded it because I thought it would have some improvement. Obviously I was wrong so when I saw nothing has changed, I just deleted it from magisk.

After rebooting my phone I noticed I was without a camera app. The camera itself is still working on other apps, but I don't have a camera app. I tried to simply install it back at magisk, but the app gets stuck on a screen asking for permissions (see attachments). Even though I grant these permissions, it keeps asking for them and doesn't do anything.

Is there something I can do? Or the only solution is to factory reset it? will it work?

Ty in advance
[Magisk] zgfg:
Bad if developers don't do their work properly. Module can have uninstall.sh script to clean-up and revert changes at the time when module gets uninstalled from Magisk app

Uninstall again that module and reboot (that's important step for proper uninstalling - actually, only on the reboot Magisk will run that uninstall.sh script)

Then try to find your system Camera app.

Settings/apps, enable to show System apps and carefully look for. It's probably disabled and you will need to enable it.

There would be also an option to Delete all data for Camera app - you can try that too (I would back-up the photos from SD card in advance)
[Magisk] ipdev:
The chain of authorship is proper in Magisk.

If you want to compare by author, you can check the commits by author.

Magisk - GitHub - Commits - Link

Just select the user name from the commit and you will see all the commits they authored.

Example(s).

Each name below is a link to their commits.

topjohnwu

vvb2060

yujincheng08

canyie

Cheers.
[Magisk] pndwal:
Further to above, you didn't need to send Alpha telegram group link in Conversation message... If you keep up there you'd have seen my comments there also.

I said here back in July:

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

vvb2060 is still at the top of a list of 200+ Magisk contributors and does very valuable work, but has always contributed to the project, not competed.

His forks are very much for test purposes as mentioned above, his branches serve this purpose and are quickly deleted with the exceptions of Alpha and Lite. Even Lite is now 'stale', and Alpha, as the fork name suggests, is to be considered less stable (suitable for public release) than Beta. This is clearly by design.

https://en.m.wikipedia.org/wiki/Software_release_life_cycle

A new TJW he is not, nor do any of his builds purport to be Release candidate material.

A team player he is, and the team is both larger than many here appreciate and inextricably connected with LSPosed, Riru and other custom development projects, and each contributes to projects led by others. PW
[Magisk] toolhas4degrees:
I clearly know what a beta, alpha, canary, and stable build/rcs are thanks you didn't need to send that if you would have paid attention how long I have been a member here......
[Magisk] Golf c:
That's a bold statement! To put his career on the line for root. I highly doubt that.
[Magisk] pndwal:
No disrespect intended; I actually agreed with your original sentiment and thought the 'roadmap' for the OPs own repo solution and details about that might be appreciated.

However rather than acknowledging John's solution, something we are probably all anticipating here, you went off on a tangent minimising his recent effort. Then, despite my giving official stats you continued to promote fanciful theories about who may really be behind efforts / commits in various builds. 🤔 ... It just seemed to me you simply wanted to undermine confidence in OPs stated intentions regarding repo oversight and changes, and then the integrity of committed changes listed on GitHub etc, and I find that frustrating...

But you do seem to have been around the block a few times here 😛 ... Maybe I've completely misinterpreted what you meant... ? PW
[Magisk] Vision:
Yeah i know, but for some reason with latest magisk canary not work the CTS profile match , only this work when i add and universal safetynet fix the CTS profile match pass and google play store say device is certified
[Magisk] ATHUL SURESH123:
Hey all I am currently on arrow is A12. Whenever I am trying to enable magisk hide option it gets turn off automatically. Tried new canary build but same issue exist.
[Magisk] AAnnunziato:
Ty for replying!

That didn't work though. I can't find a Camera app on my settings (I looked one by one and the only thing that refers to camera is "calibrate camera angle").

For what I see on the module zip file, there is no Uninstall.sh. Maybe that's an issue?
[Magisk] Sup3rN1c:
I saw this image in more than one guide...

Thanks.

Nic.
[Magisk] napster113:
That's a screenshot of the old version, not the newest version which you've installed.
[Magisk] Sup3rN1c:
So it should be active always?

Unfortunately I can't use Pokémon Go... It starts, but it doesn't connect to the server.

Thanks for the help.

(And sorry everyone for the big image!)

Nic.
[Magisk] steveo17:
Not sure if it has been reported already, but Magisk V8 is working for me on my 6P with 7.1.1 (MR-1)
[Magisk] putridfoetus:
This is interesting, but I'm not adding any lib64 files, since my N6 is not an x64 device. Same kind of trouble, though; adding files in bin and lib make bootloop. Any idea if this is fixed in v8? I see op commented 17 days ago that it would be, but didn't see it mentioned in change log.
[Magisk] pirasalbe:
Hi,

I've a problem with Google Assistant Mod.

It keep telling me even after a reboot that "Module will be updated after next reboot"

I've tried to uninstall it but the button doesn't work for it, but it works for other mod

Does anyone know how to fix this??
[Magisk] tommy255:
I have exactly the same issue, came here to post it. I can't even remove the module
[Magisk] RonnYap:
Today i try funny thing after i read a few post from suhide n magiks.

Wat i do..

Flash systemless root

reboot

suhide 0.50

reboot

exposed 8.2

reboot

install root switch

tick su

disable root..

safetynet pass but fully unroot even tick root back. Need to reboot to get back root...

So i decided keep flashing n see wat happen..

B4 i flash magiks8, I uninstalled supersu..

Then go to recovery jus flash magiksv8..

continue with phhsuperuser..

reboot..

then i install phhsupersu..

Hahaha..

now i use switch root..

jus tick su n disable root..

Safetynet pass..

n my phone still root but hidden root.. i mean even show no su but still function my afwall root..n also just switch back to root when untick su..

no need reboot..

Now i on switch root

jus enable or disable root

su jus tick..( dont disturb)

Its funny flashing..

Thank to many ppl posting n i jus combine it..

sorry my bad English..
[Magisk] silvercat:
Use SuperSU v2.78 stable version instead of SR1
[Magisk] requiiiem:
The v4a dont work, say no processing :crying:

Nexus 6 7.0 full stock

Magisk v8 with busy box path

Phh su

V4a 2.5.0.5 by topjohnwu module
[Magisk] gocku:
I tried to install magisk after supersu 2.8 but the system goes into loop.

then I tried to uninstall and install only on magisk but goes into loop.

I then installed su and magisk system manager, asked me to update, ok, but then always in the loop.

and charges down the system I do uninstall magisk

Huawei GPLAY mini android 5.1.1 TWRP 3.0.2
[Magisk] aviraxp:
Device-Specific issue. Try to delete deep_buffer in audio_policy.conf.
[Magisk] edyny1:
which version phh superuser you used?
[Magisk] andrew2432:
[MENTION=4540020]AbiDez[/MENTION]

What phone? Does magisk v8 work for lollipop?

Anybody want to confirm steps?

1.full stock

2. Install twrp

3. Magisk v8 flash twrp

4. Phhsu flash in twrp, reboot

5. Magisk manager, activate magisk hide, reboot

6. Phhsu app

Any idea if gaining root access, debloating, moving system apps appropriately, assigning partitions; momentarily handling major root access functions, then removing root and files and/or restoring stock image will allow login? It should?
[Magisk] edyny1:
i believe all of the above is for marshmallow only.
[Magisk] hokiealumnus:
Confirmed Magisk Hide on vs985 G3 (Marshmallow so far; haven't tried Nougat with it yet), thank you!

1. Flash Magisk 8

2. Flash phh superuser 259 for Magisk.

3. Flash bump script (else the boot image won't boot on the g3).

4. Install phh superuser from play store.

5. Launch Magisk, grant root.

6. Enable Magisk hide, reboot.

7. Pass safety net with root. :D

Thank you!
[Magisk] mathy007:
You're right magisk works on 5.+ Am using HTC one M7 dual sim 5.0.2 and everything is fine except for suhide which requires 6.+
[Magisk] :
So Pogo and safetynet now pass for me after many failed attempts using both root methods.

And it seems for me the key is 3 things.

One is no exposed. I can pass with only flashing the xposed systemless 86.6 or 86.2 but as soon as the apk is installed it fails.

A clean boot.img. so either flashing stock rom or flashing supersu then doing a full cleanup and stock restore.

Both of these didn't have an effect until i flashed a permissive kernel. I used pheonix kernel although i have a few bugs with wifi.

On a galaxy s5 g900w8

Magisk v8 (magiskhide on)

Phh superuser 259

Chances are i will pass both root methods as long as my kernel is permissive.
[Magisk] Captain_Throwback:
I don't think it'll help most people, but you can give it a try, I guess. For arm/arm64 devices only, and I can only confirm that it works on my HTC A9 and 10. So of course, ymmv. I do know that it will only work along with magiskhide and phh's Superuser for Magisk in getting SafetyNet to pass - SuperSU isn't compatible.

I take no responsibility for any breakage that occurs as a result of this zip.

This module will automatically set ro.boot.verifiedbootstate to green. It also allows you to change other props, but currently it only changes the one ;). Please thank [MENTION=2605798]nkk71[/MENTION] for the binary and allowing me to post it here for testing.

NOTE: Both my devices are running Marshmallow - this will not work if you're running Nougat. Not sure about older Android versions, but those *should* work.
[Magisk] knipp21:
Any idea why, after flashing 259... None of my apps are requesting root access?

Running a n5x
[Magisk] pndwal:
You did well! - could have been easier though...

Did a bit of delving. Your screenshot shows system.prop in Safetynet-fix module directory. Since USNF 2.0.0 lacks this, I deduced that you are really using 2.1.0 or later, not 2.0.0!

Dates confirm it's actually latest, 2.1.1.

This is significant as 2.1.0+ Changes include:

• Added MagiskHide features that will be removed in future versions of Magisk, - and these in turn include changes for 'sensitive' props that can trigger SafetyNet failure.

These prop changes seem to be needed especially for older devices in addition to hiding 'root' from Google Play Services, which is why this fixes SafetyNet for you.

A more orthodox way of achieving this is in the post I linked in my original response:

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

If I am right, SafetyNet should still pass after removing safetynet-fix directory from data/adb/ simply by installing MHPC module.

Hope it helps. PW
[Magisk] zgfg:
I dont know how is Camera app on your phone and what that module does for the built-in Camera app - I was just guessing, if it could help (but didn't)

You could try to find package having camera in the name (if its name, don't know for your phone) by executing from adb:

adb shell pm list packages | grep camera

or from Terminal app:

su -c "pm list packages | grep camera"

Or you can check disabled packages:

adb shell pm list packages -d

But again, no idea what that module did (I suppised that it could have 'frouzen' the Camera app)
[Magisk] pndwal:
I guess main screen camera icon is missing too.

If you're tried uninstalling module through Magisk and removed folder from data/adb/ manually if it remains, I'd try dirty flashing ROM to retain data and see if that restores the camera app... I think it should. PW
[Magisk] vandyman:
I have lost autofill somehow after rooting. I not sure if it is the cause of Magisk or not.

(Pixel 6, Magisk Canary 23011)
[Magisk] pndwal:
Looks like this issue:

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

where @V0latyle already commented!

Likely your comments will help (but don't agitate the tiger further 😜) PW
[Magisk] V0latyle:
Yeah, I didn't open an issue there as I'm not entirely familiar with GitHub, and I wanted to make sure we establish this is a Magisk issue before doing so.

I opened a thread specifically on this issue here.
[Magisk] myc85:
Erro when bild magisk

I defined the vars env and is using the lastest Android Sdk, but always getting erros

My system: Ubuntu 20.04.3 LTS in a Virtual box machine

my env:

ANDROID_SDK_ROOT=/root/Android/Sdk

PATH=/media/android-studio/jre/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

He is the log:

./build.py ndk && ./build.py all

Downloading android-ndk-r21e-linux-x86_64.zip

Extracting NDK zip

Patching static libs

Building the stub app

Note: Some input files use or override a deprecated API.

Note: Recompile with -Xlint:deprecation for details.

Note: /media/Magisk/stub/src/main/java/com/topjohnwu/magisk/DelegateComponentFactory.java uses unchecked or unsafe operations.

Note: Recompile with -Xlint:unchecked for details.

No issues found.

Output: out/stub-release.apk

Building binaries: magisk magiskinit magiskboot busybox

make: Warning: File 'obj/local/armeabi-v7a' has modification time 1,4 s in the future

make: *** Deleting file 'libs/armeabi-v7a/magisk'

/root/Android/Sdk/ndk/magisk/toolchains/llvm/prebuilt/linux-x86_64/bin/arm-linux-androideabi-strip:./libs/armeabi-v7a/magisk: File format not recognized

make: *** [/root/Android/Sdk/ndk/magisk/build/core/build-binary.mk:774: libs/armeabi-v7a/magisk] Error 1

make: *** Waiting for unfinished jobs....

Build binary failed!
[Magisk] Nightf0x_007:
Can someone direct me to magisk 23001 canary debug apk and the magisk 23001 zip please, updated to a12 but will revert back to a11 need magiskhide and suffering from apps crashing

Tia
[Magisk] shoey63:
I have a Sony xz premium running los 18.1

EvalType is basic

Magisk canary 23001 with MHPC spoofing certified fingerprint passes safety net

Upgrade to canary 23011, enable zydisk, deny Google Play services (gms only, no gms.unstable to hide) and safetynet fails totally.

All magisk hide props are active in MHPC.

What am I missing?
[Magisk] Vision:
Thanks for answer, yeah i write by mistake 2.0.0, the version is the latest 2.1.1 safetynet fix, i don't have have test yet the MHPC module
[Magisk] danielxpa:
Hey guys.

I am new regarding rooting on mobile phones. I have bought several months ago a new Sony Xperia XZ2 compact with Android 10. Since my old phone was using Android 5 with root access I do not want to miss this feature as well. Since I informed me well that a good way to root is to open the bootloader and use magisk. I have rooted it about 3 months ago but unfortunately did recently an update to the new 23 version which I regreted since my banking app recognize the root access. Therefore I want to revert to previous version.

I tried to follow the description like here Tutorial. I tried to patch it as follows: ( I have no TWRP installed).

- Exctract boot image.

- Select the boot image and patch it.

- Take the patched file from the local storage and transfer it to my computer.

fastboot flash boot_a magisk_patched.img

fastboot flash boot_b magisk_patched.img

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a magisk_patched-22105_qlT0C.img

target reported max download size of 805306368 bytes

sending 'boot_a' (65536 KB)...

OKAY [ 1.680s]

writing 'boot_a'...

OKAY [ 1.343s]

finished. total time: 3.038s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_b magisk_patched-22105_qlT0C.img

target reported max download size of 805306368 bytes

sending 'boot_b' (65536 KB)...

OKAY [ 1.719s]

writing 'boot_b'...

OKAY [ 1.335s]

finished. total time: 3.054s

fastboot reboot

When I reboot my mobile phone I cannot see the module section. It also says that the Magisk is also not installed (n/a).

Can you explain what is missing?
[Magisk] Didgeridoohan:
Probably to first uninstall the Canary version. Either use TWRP (if available) or reinstall the release you were unhappy with and do a complete uninstall from the app.
[Magisk] AAnnunziato:
The camera icon appears if I install the magisk module but it doesn't open. If I uninstall the module, it disappears.

Noob question: I'm with stock rom installed. Can I dirty flash it normally? And would it uninstall magisk?
[Magisk] Didgeridoohan:
That's the problem... The "unstable" service is key and I'd be very surprised if it's actually missing on your device.
[Magisk] J.Michael:
Is the screenshot supposed to show you enabling Magisk Hide, only to have it turned off? I do not see it.
[Magisk] J.Michael:
You might do better asking about this on Github. (I do not know how welcoming they are to fledgling developers.)
[Magisk] danielxpa:
I uninstalled the new version via the apps overview and installed the old version and repatched the boot image. After a reboot Magisk still says that Magisk is still not installed.
[Magisk] Thfaro:
I figured I should post this here, and I am unsure if it is even supposed to happen. My phone is a XT1952-T, so a rebranded Moto G7 Play, and I am aware that the "bad key" and "N/A" appearing after an unlocked bootloader is normal. In my case though, these letters and numbers appear instead.

This always happens after flashing the magisk_patched file. Sometimes it ends up corrupting the phone, and other times it lets me get through, but Magisk still says N/A on installed. I am using the correct boot.img that I pulled directly from LMSA.

Whether I use TWRP or fastboot to flash it, this always ends up happening. I also flash the stock firmware with LMSA before flashing so that I ensure the previous test doesn't conflict with the next one. I don't ask for a fix, I am actually intrigued on why this happens, any ideas?
[Magisk] zgfg:
Sorry, I snswered to the wrong post
[Magisk] zgfg:
I think, you are missing the screenshot to prove that there is really no "unstable" on your phone

Did you click on Google Play Services to extract all its processes - than take the screenshot and please post here

Btw, do you have official Google Play Services or some open-source GApps?

With open-source GApps, don't even think about passing SafetyNet
[Magisk] toolhas4degrees:
I undermined no one. You are ranting and speaking down to people. But if you think John and his other people working on this don't talk then John makes a commit from them you are nuts
[Magisk] ipdev:
Device side actually. ;)

Combination of hardware firmware and software.

Android 11 introduced boot header v3.

This is the start of GKI (Generic Kernel Image) support and the introduction of the vendor boot image.

The device (vendor) specific info is moved into the vendor_boot.img instead of the main boot.img.

On boot everything is combined to hopefully 🙃 boot the device.

Android 12 introduces boot header v4.

This is the same as v3 with the addition of support for multiple ramdisks in the vendor boot image.

Again everything is combined on boot.

Since the 4a (5G), 5 and 5a were released with Android 11, they will use header v3 unless Google takes the time to update the build tree, kernel tree and blobs for each device to support v4.

So next year when Android 13 comes out, they will most likely still be using boot header v3. ;)

The 6 and 6 Prop are released with Android 12 so, they will use header v4.

Again unless Google takes the time to update the trees and blobs to support a new boot header version.

One of the security updates in Android 12 (SDK31) causes the boot failure when a different boot image is installed without a data wipe.

I thought I read something about it but, I can not find where I read it. :unsure:

Something about a change to the way the hash value is verified on devices using boot header v3 and newer.

Sad to say it is not a Magisk issue even though it affects Magisk.

Just unpacking and repacking the original boot image (no modification) will give the corruption error and force a data wipe if you install the repacked boot image. :(

Cheers. :cowboy:
[Magisk] Nekromantik:
I hope there is a way around it even if its not a magisk issue
[Magisk] pndwal:
That's certainly the issue! ... (com.google.android.gms.unstable in Google Play Services is the SafetyNet process.)

Personally, I've hidden this using various custom ROMs w/ sideloaded GApps with no issues...

But what is 'open-source GApps'? 😜🤪😁 PW
[Magisk] shoey63:
That was it. Didn't even realise a list dropped down.

It's there, now denied and Safetynet passes.

Thanks
[Magisk] zgfg:
Updated today to MagiskCustom cb3a210d 23011, and continue enjoying Zygisk disabled, MagiskHide, Riru, LSPosed
[Magisk] vandyman:
After looking into this. Google autofill is tied into safety net somehow.

I will have to setup safety net to find out.
[Magisk] toolhas4degrees:
If you don't know how to pass safety net on latest canary pm me
[Magisk] vandyman:
I'm good, thanks.

An updated Universal safety net fix with Zygisk will be coming down the road soon.
[Magisk] pndwal:
(I'm assuming you never had previous Magisk installation working on this device; please say if you did...)

Confirmed Issue:

Magisk cannot handle g7 play

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

You may want to keep an eye on progress here. 😉

Moto G7 issues:

https://github.com/topjohnwu/Magisk/issues?q=is:issue+is:open+g7

There are a number of open issues with Installed - N/A symptom that may give further clues:

https://github.com/topjohnwu/Magisk/issues?q=is:issue+is:open+n/a

🤠 PW
[Magisk] pndwal:
Ta... I have a vague recollection I read something about this too. But my photographic memory is old... still needs developing!

Still I'm curious... Please can you link info? 👍 PW
[Magisk] pndwal:
Official Applications / methods for installing Fastboot ROMs vary with OEM.

I'm not familiar with Zenphone, but should be able to see options to keep data (or uncheck Factory reset / Wipe data) and to retain unlocked bootloader (or uncheck Re-lock bootloader).

If you pay careful attention to these settings you can often successfully restore a corrupted OS and keep user data.

Stock usually installs boot image unless you have option to deselect, so Magisk root will be gone; Magisk data (modules, settings etc) is in /data/adb, so should be preserved for next Magisk instal; -Just flash back Magisk patched boot image.

🤠 PW
[Magisk] AAnnunziato:
Thank you very much for helping! I figured it would be easier just back up and factory reset my phone. Now my camera is back and I didn't lose anything important :)

And if I need I'll just reinstall magisk because that's pretty easy and will never mess up with system apks again.
[Magisk] Thfaro:
Ah, got you. No, I have not ever had any successful Magisk installs. I assume if I'm going to need to wait for a newer version to fix this issue, if it can be. Do you think older versions of Magisk would work? I had this idea because I looked at the releases of Magisk and one of them (Magisk v22.1) stated that it would be the last version to support Kitkat. When I tried a fix with the help of someone else, we tried ADB sideloading and I noticed that when I did it incorrectly, this returned:

adb: sideload connection failed: closed

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: closed

Though, I might just be making myself look dumb lol, Android modding is very new to me, but also very interesting. Thank you for helping me though.