yashsingh1/xdaforums huggingface dataset:
[Magisk] Thehaluzer:
Hello!

Good question. I used the root checker which confirmed root access. Also i have the app called Systempanel which has also stopped working. Those two used to work now they don't work anymore. So I'm 100% as both this apps rely on root especially Systempanel
[Magisk] pndwal:
Ok, got this finally... Kept clicking, but no indication of scan completing... Box still empty... Finally saw next step and hit dropdown arrow to see device... Perhaps some text in box could make this more intuitive, or auto-open dropdown after a scan?

I do, but couldn't select .tgz... Only.zip (recovery ROM)?

Manually extracted and added...

Ok... get option 1 only.... So I typed in hidden Alpha gobeldegook for nothing; guess you should have said Restore Magisk upstairs! 🤪...

Ok, got 1,2,4...

Results and original image attached...

Was going to send recovery images patched w/ recovery mode selected for comparison also, but there doesn't seem to be a way to check that option...

Pleasure... PW
[Magisk] zgfg:
With Termux, PATH may not be set correctly and Termux would not find the magisk binary

Check if /system/bin is in the Termux path - and try to add it.

Anyway, play on your own with Termux (I use another Terminal emulator and won't bother with helping about Termux)

Edit: As suggested by @BillGoss, call directly

/system/bin/magisk -c

instead

---

Next, what was the version of Magisk that you had previously installed?

---

Did you ever do Hide Magisk App (Hide Magisk Manager if it was an ancient Magisk version )?

But it could have been made by that 'company'...

So, when you used Magisk app, what was the name of the app displayed by the icon (Magisk, Settings or something else)?

Or if you paid attention - was its package name com.topjohnwu.magisk or something scrambled?

---

Btw, install

TB Checker - Play Integrity - Apps on Google Play

All in one tools check android devices

play.google.com

and execute Run Root Check and please post the screenshot
[Magisk] zgfg:
Also, in addition to the questions from my previous post

Did you update/reinstall your ROM or performed Factory reset (wiping or formatting Data)?

In that case you would loose Magisk...

Then describe all steps how did you update Magisk (from TWRP, by updating Magisk app and patching and flashing, etc)

Please describe in details (otherwise who would know what went wrong or if some step was missed or made improperly)
[Magisk] mobileman88:
Reflash the stock boot image before this and you should be ok
[Magisk] kraoc:
I also already tried to full wipe / flash rom / gapps / magisk v3 / phh superuser v2 / boot / ... stuck...

Now I'm on Xposed v86.4 and Magisk v1...
[Magisk] mobileman88:
full wipe / flash rom / gapps / reboot / magisk v3/phh superuser v2/reboot/xposed-systemless 86.4/reboot should work
[Magisk] desztan:
Hi, I've just flask magisk v3 over v2 and Selinux Toggle still not able to stick. I'm on stock rom N915G rooted with phh supersu v2. Any advise would be helpful. TIA
[Magisk] kraoc:
Hi... I'll try soon maybe... But I already do a full wipe this week lol... And many apps to restore...

I think (maybe I'm wrong) that there is an incompability between Magisk v2/v3 and my rom... But I'll try your steps :)
[Magisk] mobileman88:
Keep the KISS principle.

Keep It Short & Simple .

Don't restore any apps.

- Just get gapps, xposed, and your ROm all sorted out first.

No sense restoring apps and then having to do it all over again.
[Magisk] kraoc:
Yeah... I know KISS :)

That's the way I plan to proceed :)

And restoring is by titanium... :)
[Magisk] IcyVeins:
Still the same problem on v3 on Huawei Mate S (all stock, Android 6.0).

I have uploaded the boot image, but could not upload a patched one, since it does not flash it (boot partition too small).

https://mega.nz/#!1M8TGIYL
[Magisk] devilloki:
[MENTION=4470081]topjohnwu[/MENTION]

magisk v3

my huawei honor7 has the same issue,,so sadly
[Magisk] topjohnwu:
Asus uses non-standard boot image. No proper tools can support it currently

Samsung do not support switching to permissive.

I thought this is wide known among Samsung users....., I never use Samsung and I figured it out recently
[Magisk] RandomPooka:
I've always heard it as

Keep It Simple, Stupid
[Magisk] sylvisj:
I'm still having issues with Magisk v3 on a Moto X 2014 (XT1095).

After flashing Magisk v3 over a stock boot.img, attempts to boot to system immediately send me to the bootloader.

The only warning/error message is:

Fastboot Reason: Fall-through from normal boot mode

I've uploaded the stock and modified boot.imgs for analysis.
[Magisk] topjohnwu:
Note: This post is posted here because more people look at this thread.

However, Android Pay and root discussion should be in this thread

OK guys, big news here.

A tester just confirmed that even with the simplest method of v1, Android Pay is working with successful transition.

So it's the best scenario now: Possible for Root Toggles and Xposed works with enabled

This is nice because we can now toggle root at ease instead of relying on a timeout.

So all the problems now specifically points to Nexus devices :)

Never though Nexus will one day become the issue for Android development lol, super sarcastic

People can still report Android Pay failures in this thread

I'll recruit many testers soon, please stay tuned to my threads (systemless Xposed, Magisk main thread, Magisk phh root).

I'll post the info to all threads so you won't miss it.
[Magisk] danielcr12:
Same issue on my Moto x once the phone boots it fails to activate all sensors, though I think the flash is failling here is my recovery logs
[Magisk] LLStarks:
Is there any ETA for this?

What kind of license are you looking at? BSD, GPL, MIT, IDGAF?
[Magisk] spartan018:
[MENTION=4470081]topjohnwu[/MENTION], this is what I've been seeing, too. Even if I select Normal Bootup in the bootloader, it just goes back to the menu with the error "Boot up failed". Occurs with every Magisk version, but Systemless SuperSU + Systemless Xposed works fine.
[Magisk] justforgot:
Thank you so much for your hard work. This is really useful for me.

Appreciate all your hard work. Thank you.
[Magisk] axiomofdarkness:
I have the same issue on a Droid Turbo (XT1254) running both stock 6.0.1 with a custom kernel and stock 5.1 with the stock kernel. [MENTION=4470081]topjohnwu[/MENTION] I can upload any information as well if you want.
[Magisk] PokemonTotalWar:
Is it possible to install system apps with Magisk? Like, install Titanium Backup to Magisk, or a SU management app?
[Magisk] joeyddr:
After the ap update I got today safety net passes and card add works but my transaction failed at the terminal. Running v3 on purenexus
[Magisk] waxler9311:
Well damn, that will ruin root for me for sure then. I can't even use snapchat anymore rooted.
[Magisk] topjohnwu:
phh superuser Update

This update fixes issues if binaries under /sbin is gone and require a restart (rarely, but possible).

Update is live on Magisk Repo.
[Magisk] turk.17:
How do you install Viper4Android with Magisk? I tried installing it from Magisk, installing the APK and rebooting my phone, but V4A doesn't work and it says "Enabled: No." I also tried installing BusyBox in both system/xbin and system/bin to no avail.

I'm on a rooted Galaxy S7 by the way.
[Magisk] yochananmarqos:
Magisk already includes busybox, but it's not accessible by apps. You'll need to copy (or symlink) the busybox binary from /data/magisk to /data/busybox.
[Magisk] turk.17:
That didn't work unfortunately. :(

I used FX's root explorer to go to /data/magisk and I copied the file named "busybox" to /data/busybox, but even after a restart, it still showed "Enabled: No." I even tried to rename audio_effects.conf to audio_effects.conf.bak in /ect, but that didn't do anything either.
[Magisk] rignfool:
Did you turn the master switch for the desired output on?

Did you install the driver?

Did you ask in the V4A thread since you have moved past the magisk part of the install?
[Magisk] PachiMc:
hi, i need help, i want to install it but i cant, i ahve a moto xt 1097 that is rooted with supersu twrp and i try to isntall from manager magisk but dont work (error boot up) so i unistalled the xposed and full unroot supersu and flashed from the twrp (first magisk v 8 and phh superuser r266-2) but the same error (error: fall throught from normal boot mode, boot up failed) i already try installed the stock firmware original. idk what more can i do :( pls help
[Magisk] Artim_96:
Well, you should fish your stock firmware, boot it, flash Magisk, bit system and then flash superuser. Then tell us at which step it fails with which error

PS: the release thread states that some Motorola devices have problems after flashing Magisk. So your device is probably not compatible
[Magisk] PachiMc:
i told that i already try isntalled the stock firmware original, and supersu work fine, so u think that is probleem with my device or something else ?

anyway some solution xd ?
[Magisk] Abhi142:
Is it support Android 7.1 if yes then how to install it?
[Magisk] Vinnom:
Our device isn't supported yet. I already tried v7 and v8 and reported to the OP that it is bootlooping.

What are you trying to achieve? For now, I just want to play pogo and I could using SuperSU SR1 + suhide 0.55 + rootswitch, but I'm very hyped with things that Magisk could do for us, so I'll still test the new versions when it rolls out.

Please, note that, if it is stated that some Motorola devices doesn't work with Magisk and you try and it doesn't work, you can't do nothing but wait.
[Magisk] PachiMc:
thx

thx u for reply i will wait and i hope that the dev fix it ;D
[Magisk] jascolli:
Looks like v9 just dropped. Thanks!
[Magisk] topjohnwu:
New Magisk v9 with massive updates is now LIVE!!

Safety Net passes! Grab it when it's still hot!!

Check the release post for super detailed info!
[Magisk] Kris6699:
[MENTION=4470081]topjohnwu[/MENTION] I hope you don't mind. I compiled your github.... My phone is now running its own Magisk V9....

EDIT OH COME ON!!!!!!! I JUST COMPILED IT!!!!!!!!
[Magisk] ghbuur:
GREAT work, you're a hero!
[Magisk] ss4rob:
Thanks topjohnwu, Captain Throwback, and nkk71 for your work - after flashing the latest three files, Android Pay and Pokémon Go! work great on my Nexus 6P running 7.1.1 beta preview!
[Magisk] Artim_96:
Wait... Are you telling me that you have supersu installed and try to install Magisk with phh's supersu?

Then reboot SuperSU, restore stock boot.img, fish Magisk and phh's supersu and reboot after every flashing to find out where the problem is.

Otherwise try it works with SuperSU better.

If that didn't help, your device is unsupported
[Magisk] Didgeridoohan:
v9 is working beautifully! Changing my cache module for screen density to work with resetprop was dead easy and the new Magisk Hide works for apps that the old one didn't. Amazing work [MENTION=4470081]topjohnwu[/MENTION]!
[Magisk] garthybarthy:
I would love to use Magisk but with every version I've installed it creates a deep sleep issue and my battery drains way too fast.

I have a Samsung Galaxy S6, I've tried different roms but it's still the same. As soon as I remove Magisk, deep sleep is back.
[Magisk] amk316:
i have this error massage when installing shamiko 0.7.1

shamiko files corrputed, please re-download form official sources

but no problem with shamiko 0.7
[Magisk] zgfg:
I don't have this problem (and don't remember that others reported anything similar).

Hence, did you redownload, reinstall and reboot
[Magisk] amk316:
yes
[Magisk] zgfg:
From here?

Releases · LSPosed/LSPosed.github.io

Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.

github.com

And does Magisk app display that Zygisk is up'n'running?

No other idea but try with firewall and/or adblockers disabled
[Magisk] HippoMan:
I don't use Termux for these kinds of tasks, either.

Termux is sort of like a mini-linux environment running within Android. It installs its own environment with its own PATH and some of its own utilities, and it therefore cannot be counted on to properly run scripts and other code which are meant to inspect the OS or make low-level changes to it.

One way to tell whether a given terminal emulator might be more useful for these kinds of sysadmin tasks is to do the following:

* From the desktop computer, do "adb shell".

* Type "echo $SHELL" and save the value that prints out, and also do "echo $PATH" and save that value, as well.

* Back in Android, get into the terminal emulator that you want to test and issue the same "echo $SHELL" and "echo $PATH" commands.

* Compare these results to what you got when you issued those commands via the adb shell. If the "echo $SHELL" results are not identical, you will almost certainly have problems in that terminal emuator with those kinds of sysadmin tasks.

* The results of "echo $PATH" don't need to be perfectly identical, but the more they differ, the greater the chance will be that these kinds of sysadmin tasks might fail.

I just now performed this test with Termux. It yields a completely different value for $SHELL than the value used under adb shell. Also, all of the standard directories that are in the $PATH for the adb shell run are totally absent under Termux's $PATH, which instead points to its own code. This shows how undesirable Termux is for these kinds of sysadmin tasks.

The terminal emulator that I use is the one that comes with the "JuiceSSH" app. Under that terminal emulator, $SHELL is the same as that of adb shell. And every directory that appears in the adb-shell $PATH appears in the same order in the JuiceSSH $PATH, and JuiceSSH only adds one extra directory to its $PATH.

Therefore, that particular Terminal emulator would be much better to use for sysadmin tasks than Termux. And I'm pretty sure that most other Android terminal emulators would also be much better for these kinds of tasks than Termux.
[Magisk] zgfg:
As said, I don't use Termux.

I use plain vanilla Terminal Emulator from NetHunter package. /system/bin, /system/xbin and other bin directories are in the path (and in the proper order) by default. No additional 'packages'. Hence I know that I can be in control and that my TE will run and will only run su, BusyBox applets, etc that were pre-installed by stock, or installed by Magisk and Magisk modules, with no surprises that it could call something 'unknown' from somewhere else instead

Still, recently I had an interesting problem with the wget utility.

I had a certain script that had to download something by use of wget on two my phones

Long story short, I eventually realized that on one phone a different version of wget was pre-installed by stock in /system/bin (and it had a precedence by PATH over the wget from BusyBox in /system/xbin) while on the second phone there was only the wget from BusyBox

And the two wget versions behaved differently in regards to the -c and -T options, resulting that download of a certain large file almost always failed on one phone, but not on the other
[Magisk] BillGoss:
@zgfg @HippoMan @amk316

If Magisk is correctly installed then all you need to do is type /system/bin/magisk -v in Termux and it displays the Magisk version. There's no need to complicate things by making changes to PATH.
[Magisk] badabing2003:
Thank you very much, appreciated.

I suppose you didn't resize the app, and you didn't see the console at the bottom?

It would display something like this.

2023-05-15 17:21:53 Scanning for Devices ...
3 Device(s) are found.
2023-05-15 17:21:57 No Device is selected!

Regardless, your suggestion is a very good one.

Added.

I'll add support for that,

You have a tgz link I can test with?

What do you mean by Recovery ROM?

Being able to select as ROM?

Correct, my bad, should have mentioned that Method 2 can only be used with non-hidden app, unless I find a way to access the data portion (need to find where and how it is stored) considering that your are rooted.

I suppose this 3boot_magisk_patched-26101_If370 is 4 and not 3.

If you send recovery.img and create a patch of it, what happens?

Do we need to do anything different other than passing it to Magisk?

1 and 2 are identical matches with the exception of RANDOMSEED. (expected)

Comparing 1 or 2 with 3 (ie 4)

I see one more difference. PREINITDEVICE

I need to read up and understand the implications (let me know if you already know).

With 3, it was cache, with 1, 2 it is userdata.

Thanks again
[Magisk] ipdev:
For the most part, any (newer) Xiaomi full fastboot downloads.

Xiaomi Firmware Updater - [website] - Link

Example:

Poco F2 Pro (Global).

Xiaomi Firmware Updater - [POCO F2 Pro Global MIUI V14.0.1.0.SJKMIXM Update] - Link​

Type: Recovery

- Is a flashable zip for recovery install.

Type: Fastboot

- Is a tgz of the full images for fastboot install.

Cheers. :cowboy:
[Magisk] pndwal:
Haha, no I didn't see that. 😜

Here are ROMs for Redmi Note 8T:

https://xiaomifirmwareupdater.com/miui/willow/

Select a fastboot type ROM...

.zip ROM for installation via recovery...

🤔... Can't select .tgz fastboot ROM (for installation via fastboot).

My understanding is that these are more complete, containing all factory images... To fix issues usrs should generally restore Fastboot ROM rather than recovery ROM. Eg I'm not sure recovery ROMs always include firmware drivers (baseband etc) and other partitions... Nb. for RN8T, F-ROM is 4GB, R-ROM is 2.6GB.

😜... badabing!

Yup... My bad! 🙁

Well guess you'd now have RECOVERY MODE=true since users see and must select Recovery Mode check box in Magisk Install menu.

I'm not sure what other changes this may make in image, but flag may affect booting; eg some devices seem to be able to boot via recovery automatically after an initial boot requiring recovery key combo... Other devices must always be booted via key combo with attention to key release timing to get system with Magisk rather than recovery... Reboot function may also be affected as reboot is now always booting system via recovery...

Patching a recovery image without recovery mode selected may work (apart from the booting issues it may cause), but Samsung devices definitely rely on this setting to patch /recovery image in AP binary rather than /boot.

There may be other factors too.

I believe this affects the recent major refactoring of location selection for selinux/module rules... Patching from booted system is needed to set this properly; not sure why PF gets different selections however, though I previously misunderstood that PF was in fact patching booted... 🤔

I can confirm it's set to cache on my device however using:

--preinit-device resolve a device to store preinit files

Result:

1|:/ $ magisk --preinit-device
cache

Further on 'implications', see this comment/PR for application in avbroot:

https://github.com/chenxiaolong/avbroot/pull/86#issue-1640702967

@osm0sis is also likely to be able to give you insight as he recently made a change to this to bypass the need for environment fix (reflash after .zip installation from recovery) for addon.d users... See his associated PR:

https://github.com/topjohnwu/Magisk/pull/6917

Welcome. 🙂 PW
[Magisk] osm0sis:
That's not merged yet, it's draft while I figure out the cpio sha1 -> config command rewrite (my attempt so far isn't working as expected, and my C++ isn't good so I'm not sure why yet), and it'll fix retaining PREINITDEVICE in the config when dirty flashing Magisk from recovery.
[Magisk] amk316:
hi...how to fix fingerprint has been tampered
[Magisk] pndwal:
Are you using MagiskHide Props Config module?... If so, remove and try just @Displax modded Universal SafetyNet Fix...

With no information on your device/setup, it's really all stabs-in-the-dark however... You really need to offer information to get help. PW
[Magisk] amk316:
no i am using safetynet-fix-v2.4.0-MOD_1.2.zip

and even uninstalling magisk i have this problem

magisk delta 25210 on a stock S20
[Magisk] pndwal:
Haha, thanks!

... Muddled that PR with your earlier fix...

Maybe you understand why @badabing2003's PF ADB interface causes (or might cause) booted Magisk to use PREINITDEVICE=userdata while manual Magisk App patching uses PREINITDEVICE=cache with my device however...

👍 PW
[Magisk] Thehaluzer:
Which terminal emulator are you using?

I think it was 25 something.

I know i did try to update the magisk and somehow it went into hiding. But that's like over a month ago. The issues started 2 weeks or something ago. The company did not hide i remember that clearly.

The name of magisk hidden was "settings" not sure about the package but i have seen that name before. You could be possible right.is there a way i can find out?

I added picture of me trying typing in what you said did not workout.

Also i added picture of all apps currently installed. I hope this will make it easier for you to help me out. If i can provide any additional information to further help out the investigation just tell me
[Magisk] pndwal:
I'm not familiar with many of Delta fork's differences... May be one for Delta users, but I don't think oficial Magisk would produce those detections...

Please say if you have other mods installed... PW
[Magisk] Thehaluzer:
Hello!

Here comes the posts from tb checker seems like the package is failing. Very interesting app good one.
[Magisk] amk316:
Samsung Galaxy S20

stock rom "G980FXXUGHWCG"

and no other mods

i tried office magisk 26.1 and i have the same problem
[Magisk] Thehaluzer:
Hello!

I have not updated any ROM. I have not done any wiping nor formatting. Also to mention I dont have TWRP. So no clue how to flash stuff. I hope this helps.
[Magisk] Thehaluzer:
Hello!

Where do i download this app?

I coped the name and pasted into Google play store and 0 results.
[Magisk] Thehaluzer:
Hello!

No such file directory sadly
[Magisk] BillGoss:
Magisk has changed over the last few years. Try to see any of these work:

/sbin/magisk -v
/system/sbin/magisk -v
/system/bin/magisk -v
/system/xbin/magisk -v
/su/bin/magisk -v
/magisk/.core/bin/magisk -v
[Magisk] osm0sis:
Not sure, but it must be some difference in the execution environment when it's running the command to determine the device.