yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
News:

Upcoming major change to Magisk Distribution Method -

Merge Magisk install zip into Magisk Manager:

So,

- Totally offline installation AND uninstallation from package (I guess downgrading will also become simple matter of running / flashing appropriate APK package.)

- Single Magisk / Manager APK package.

- Target SDK API can be bumped beyond 28 (Details in Termux GitHub link). Already bumped to 30!

How will we flash APKs from Recovery?:

...Ready?... Coming, ready or not! PW
[Magisk] youngtjjones:
I Just tried it on my Mate 10 8.0. Still didn't work. 😔
[Magisk] nowster:
The AdAway vs Amazon Shopping App saga continues. I've been refining the whitelist. This is my current allowed list:

aa*.amazon.co.uk

aa*.amazon.com

fls-*.amazon.co*

...which seems to work. (Change amazon.co.uk to your local country's version.)
[Magisk] dipseeet:
Termux 105 i tried already and then i installed 104 ^^

Iam now on Magisk 21.3 and when i upgrade to 21.4

Termux will work again ...

yes but nothing else ...

Magisk Manager lists all my granted apps and some of them them work and 1 doesn't work.

When i uninstall Magisk completely and install Magisk 21.4 (with Manager 8.0.7)

at 1st boot after install i get prompts to grant root.

That's fine (some apps are starting at boot (SmartPack, AFWall)

Now i open root apps, i get a prompt (for each app) and i grant (them all):

Titanium Backup (works)

Total Commander (works)

SDMaid (works)

Termux (WORKS) ^^

MyAndroidTools (works) (i can enable/disable components)

In Manager it's all listed fine and i do NOTHING in the settings and NO modules are installed.

Now i do a reboot, after reboot i don't get toasts anymore.

In Manager they are still listed and i changed NOTHING in the settings.

All those apps listed above are working

except of MyAndroidTools.

(not able to enable/disable ANY components)

If i delete for example Titanium Backup in Manager (to grant root) and then i open it again i should get a new prompt to grant root, am i right?

But i don't get any prompt ...

Titanium Backup is still waiting get root access.

The same with all other (root) apps, i NEVER get a new prompt anymore.

This is how i noticed that something is not working well after a reboot.

That's why iam using Magisk 21.3.

With Termux i was able to get my .sh file working.

When i put my .sh file in the home folder of Termux and i type in Termux

su (now iam #)

and then

sh boot.sh (my file)

it's WORKING!!

wtf
[Magisk] dipseeet:
This is my result (:

~ $ which sh

/data/data/com.termux/files/usr/bin/sh

~ $ echo $PATH

/data/data/com.termux/files/usr/bin
[Magisk] farbara:
Hello, I'm using magisk manager 7.5.1. What should I write in the custom URL in the settings to install the magisk 20.4 version.

The program I am using only works on magisk 20.4. I would be glad if you help.
[Magisk] J.Michael:
Which Magisk?

Is this within (while running) termux?

Do your scripts "work"?

Do you have a reason for using termux? (As opposed to any other terminal emulator.)

I use Jack Palevich's Terminal Emulator for Android. I always assumed it was showing me the system the way everyone else sees it. (E.g., I see "sh" in "/system/bin".)
[Magisk] dcarvil:
I haven't tested it, but I think this will work.

https://raw.githubusercontent.com/t...5ffa9b079f3a411dd2c00a80a3d985ccc/stable.json
[Magisk] pndwal:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84351319

PW
[Magisk] pndwal:
Latest Canary Changelog:

Magisk (6951d926) (21402)

[General] Magisk and Magisk Manager is now merged

[General] The app name is changed from "Magisk Manager" to simply "Magisk". If you are currently hiding Magisk Manager, you would need to un-hide and re-hide to have the app label renamed properly.

[MagiskInit] Fixed a bug caused by typo (harmless to user)

[MagiskHide] Fix a bug when stopping MagiskHide does not take effect

How to Use the APK for Recoveries

In general, it is recommended to install and uninstall Magisk through the Magisk app. However, if you insist to use custom recoveries, rename the Magisk APK's .apk file extension to .zip. TWRP should then be able to directly flash the zip file. If you have trouble renaming the file extension on PC, rename the file with TWRP's built-in file manager. To uninstall in recovery, rename the zip file to uninstall.zip before flashing it.

👍 PW
[Magisk] contaoxxx:
download link?
[Magisk] pndwal:
New Canary updated seamlessly (direct update) on Xiaomi RN8T, and all working as before!

There may be less confusion with 'Latest Manager' now showing as N/A, and 'Latest Magisk' removed.

PW
[Magisk] pndwal:
For Canary, just take update w/ Canary selected as channel, or download Canary Magisk Manager from GitHub main Magisk page as before. (Main page is accessible from Magisk Manager, 'cat' symbol.) PW
[Magisk] contaoxxx:
my phone has no internet connection so I need an apk.

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84346715
[Magisk] nowster:
No guarantees:

https://github.com/topjohnwu/magisk_files/raw/canary/app-debug.apk
[Magisk] contaoxxx:
I think Magisk has broken some files. I can not fix it again.

Tomorrow I will make a backup and flash an wipe my Pixel 2.

I used Magisk and AFWall+ and after Magisk update phone crashed after turn on WI-FI. But all Wi-Fi networks are listed... Also freezes with mobile data...
[Magisk] DiamondJohn:
Thats not right, termux is not set up to run standard shell scripts in a normal way.

As said by @J.Michael use a standad shell / terrminal to run standard scripts.

and also check the reslts again from the previous test, within a standard shell/terminal. I also saw the mention of a termux bug above.
[Magisk] zgfg:
Did anybody try to update Magisk today to the new Canary - saying that Manager and Magisk are now merged

I've updated Manager but when I want to patch my boot img it alwys fails

Since Magisk and Manager are now merged to one, do I still need to update Magisk (as Manager asks me) or how?

Instead of patching should I opt for Direct update - but I don't want to risk a brick, I was always patching to have a choice to simply downgrade if new version brings new bugs)?!
[Magisk] dipseeet:
Magisk 21.3

Manager 8.0.7

I use Termux bcoz they have a Termux:Widget app where iam able to start scripts by just pressing a script file i added in the widget.

Those scripts i started to create bcoz i got *little* problems with Kernel Adiutor.

(now iam using SmartPack but the same problems)

In SmartPack i go to "Misc" for example:

I set Vibration value from '100' to '22' and i set *start at boot*.

After boot it's still 100 ... wtf

My idea was to write a little code to execute a command to change this value.

(don't like to open app etc.)

Just click and work is done (:

Termux:Widget helped me to do this.

These are the commands iam using in my script

(to change the Vibrator value):

su -c chmod 644 /sys/class/timed_output/vibrator/vtg_level

su -c echo 22 > /sys/class/timed_output/vibrator/vtg_level

su -c chmod 444 /sys/class/timed_output/vibrator/vtg_level

my first line is always

#!/system/bin/sh

in all my scripts.

My next idea was to execute it on boot.

Termux does have a Termux:Boot app but it didn't worked (don't know why?) for me.

This is why i installed Magisk bcoz since then i got those scripts working at boot.

(i put them in the service.d folder)

I don't really need those scripts but i learned quite a lot with all those googling n searching in xda n writing sessions.

Iam using BusyBox Installer by Stericson(?)

with version 1.31.1

BusyBox iam using since my beginnings of rooting (my samsungs) and i just click install.

I always (i think so) installed BusyBox into

/system/xbin

haha lol sorry ^^

Yes it says so.

When i open Termux iam first

$

next i type

$ whoami

i get

$ (name of the owner but not "root")

(here i think it's not possible to get my boot.sh running bcoz iam still not "root")

(ok it *is* running but the commands are not able to execute)

now i type

$ su

i get

#

and

# whoami

# root

iam "root"

now i type

# sh boot.sh

or just

# ./boot.sh

and it's running & working.

(:

It's just an app where i can execute scripts.

I installed it (2 days ago) and i just tested it.

It *is* the same (Termux too) as a Terminal Emulator

(:

Inside the script.

I was reading a lot across threads to figure out how to write a script almost correctly and to get them running.

But i still need more practice to understand

why is something working

and

why is something not working.

I'll test it now and will txt back asap ...
[Magisk] pndwal:
I did direct update which worked seamlessly.

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

Packaging is different, but AFAIUI, Magisk / Manager still function independently as before, so Magisk update is still needed to upgrade.

Guess there may be a bug w/ patching image method, but just wondering if you did this (I think you use hidden Manager):

"- [General] The app name is changed from "Magisk Manager" to simply "Magisk". If you are currently hiding Magisk Manager, you would need to un-hide and re-hide to have the app label renamed properly."... Then check Manager restarts properly before patching image (just in case this is an issue).

Nb. After restarting, I am seeing 'Latest [Manager] N/A', unlike your screenshot. PW
[Magisk] zgfg:
>> I think you use hidden Manager

No, I didn't have hidden Magisk Manager!

If I had, I would mention that (not a newbie here)

And if I would have it (when I was hiding it months ago), I would always unhide Manager before upgrades, to avoid any troubles (as Magisk usually had troubles with)
[Magisk] dipseeet:
Magisk 21.3

Manager 8.0.7

Yes

No.

When i type

$ sh boot.sh

it's starting my script but not with success.

Only when i first type

$ su

then i get

#

and now i type

# sh boot.sh

or just

# ./boot.sh

and then it works.

Like i wrote in my last post above :)

Bcoz they offer an Termux:Widget app:

On my homescreen i see my list with scripts and i just click on 1 of them and it's starting the script.

Like a shortcut. my idea was to have a shortcut and not to open any app to locate this file and select it to start it.

With SmartPack (my Kernel Manager) i change

"CPU" (CPU Boost and CPU Min/Max)

"CPU Hotplug"

"Low Memory Killer"

"IO Scheduler" (i only change 1 value)

"Thermal" (i disable all 3 options)

"Misc" (only Vibration value)

My scripts are commands able to make those changes *outside* the (SmartPack) app.
[Magisk] pndwal:
I'd be giving this a go for fully compatible, systemless solution:

GitHub - Magisk-Modules-Repo/busybox-ndk: busybox-ndk

busybox-ndk. Contribute to Magisk-Modules-Repo/busybox-ndk development by creating an account on GitHub.

github.com

From repo. PW
[Magisk] dipseeet:
(: thanks a lot

a few days ago i started using it ^^

and it saved my current system!!!

(after i uninstalled BusyBox with my BB Installer i wasn't able anymore to install it again)

With this module i have BusyBox back on my system.
[Magisk] DiamondJohn:
instead of deleting the line, change it to what / where termux is resolving sh to
[Magisk] youngtjjones:
Do you have to be rooted to use this build?
[Magisk] pndwal:
Sorry, just trying to help, and that was OTTOMH, just a low likelihood solution anyway...

You also asked about need to update, and if you should opt for direct update, and I indicated that updating directly works fine for me.

I also said "Guess there may be a bug w/ patching image method..."

I just had some time in a break, and tried patching image to check, and had exactly the same problem, so seems bug is confirmed.

A GitHub issue has also been made some 9 hours ago:

Latest version of Magisk canary does not work (21402) · Issue #3762 · topjohnwu/Magisk

Phone LG g6 h870 Android 9 Magisk log: -Device platform: arm64-v8a -Installing: 658d74e0 (21402) ! Installation failed - Copying image to cache ! Process error Boot image: orginal_boot.zip

github.com

Interestingly, I also now have the same 'latest' Manager build discrepancy mentioned here again. It initially showed, was replaced by 'latest N/A', then later returned. The debug apk available always gives the lower (earlier?) build number for Manager when reinstalling.

@vvb2060 is (self)assigned to this issue. Let's hope he solves it quickly. I expect he will since most of the commits for this update are his. PW
[Magisk] pndwal:
Seems you must at the moment. Direct Install w/ root works fine for me. I don't think Patching Image method is working for anyone.

See post above for details. PW
[Magisk] youngtjjones:
Looks like I'll be staying put with version 16 then 😂 when I update, I lose root.
[Magisk] pndwal:
That's life on Canary's bleeding edge!

Watch this space... I doubt it will take long to fix... PW
[Magisk] BillGoss:
No, you do not need to be rooted. If you don't have root, the install will ask you to patch a boot.img. You will then need to flash it.

If you have root, it will ask you to do a direct install.

The error people are getting with the patch process is because Magisk Manager hasn't been granted storage access in Settings>Apps>Magisk Manager>Permissions.

Once MM had been granted storage permission, the patch process works just fine.
[Magisk] pndwal:
Don't think we have Magisk Manager w/21402, only 'Magisk'

Anyhow, settings for this says 'no permissions denied', and Storage Permission is 'Allowed', but patching still fails... Are you able to patch w/ 21402?

Anyway, @vvb2060 is looking into it... PW

Edit: Looks like permission is in fact broken; @vvb2060 is seeking to merge this 'Fix Permission' commit:

Patch set by vvb2060 · Pull Request #3692 · topjohnwu/Magisk

github.com
[Magisk] BillGoss:
Yes, I patched the stock boot and then flashed it using TWRP. I'm running with it now.

I also intially did a direct install, but then I removed Magisk and did it the patching way to see if it worked.
[Magisk] J.Michael:
I wanted to start by finding out if the line is even needed.

Then I wanted to find out if just giving it a hint about which shell would cause it to find it in the PATH.

Now, I don't know what his problem is anymore, so I don't know what to try to fix.
[Magisk] J.Michael:
@dipseeet I'm lost.

Were you working happily with an earlier version of Magisk?

Did you upgrade the Android on your device? Did you just get the urge to use a newer Magisk?

What are you missing before you install Busybox?

Those commands bother me. If "/sys" is part of a read-only filesystem, you're not supposed to try to change files under it. Maybe having Magisk run a script as part of its initialization changes the rules, but I would expect you to have trouble testing such scripts long after boot. If everything you are trying to do was working under an older version of Android, but you are now using a newer version of Android, the rules might have changed.
[Magisk] pndwal:
Commit merged! "[App] Fixed storage permission issues when patching boot images on pre Android 11 devices"

Patching Image method should be all good now on new Canary v21403. 👍 PW
[Magisk] pndwal:
Latest Canary Changelog:

Magisk (4cc41ecc) (21403)

[App] Fixed storage permission issues when patching boot images on pre Android 11 devices

[General] Updated scripts to workaround issues with some modules using fully custom installation logic

How to Use the APK for Recoveries

In general, it is recommended to install and uninstall Magisk through the Magisk app. However, if you insist to use custom recoveries, rename the Magisk APK's .apk file extension to .zip. TWRP should then be able to directly flash the zip file. If you have trouble renaming the file extension on PC, rename the file with TWRP's built-in file manager. To uninstall in recovery, rename the zip file to uninstall.zip before flashing it.

Diff from v21.4

[General] Magisk and Magisk Manager is now merged

[General] The app name is changed from "Magisk Manager" to simply "Magisk". If you are currently hiding Magisk Manager, you would need to un-hide and re-hide to have the app label renamed properly.

[MagiskInit] Fixed a bug caused by typo (harmless to user)

[MagiskHide] Fix a bug when stopping MagiskHide does not take effect

👍 PW
[Magisk] pndwal:
As this seems to be a pre Android 11 issue, are you on A10 or earlier? PW
[Magisk] pndwal:
And maybe not! ☹

Have updated using direct Install fine once again.

Patching image is still ending with:

- Device platform: arm64-v8a

- Installing: 4cc41ecc (21403)

- Copying image to cache

! Process error

! Installation failed

Xiaomi RN8T, MIUI, Android 10. PW
[Magisk] zgfg:
I will try later today but I am on A11 where it failed for me?!
[Magisk] pndwal:
Yeah, Changelog says fix is for pre A11, but may actually be a more device specific issue. I just opened another issue for 21403. PW
[Magisk] zgfg:
Tried 21403, still the same error on patching.

I'm on A11 and I don't see any way to control Storage access for the app Magisk
[Magisk] pndwal:
Yeah, saw your issue comment... PW
[Magisk] zgfg:
Yeah. Direct method worked but because I already had root with earlier Canary 21401

On Friday I will receive OTA. If not fixed by then, I'll have to start with Stable 21400 to be able to patch/install (or to flash Canary through TWRP which is not recommended and I never liked nor practiced although I do have TWRP for my A11)

After Direct method it correctly shows 21403 installed
[Magisk] swangjang:
when i try to patch an image, I get:

- Device platform: arm64-v8a

- Installing: b1dbbdef (21404)

! Installation failed

- Copying image to cache

! Proces error

It used to work fine no problem but since today I'm getting this error.
[Magisk] zgfg:
Pls scroll back, discussed yesterday and today about the patching bug in 21402+

Btw I now also spotted 21404 but now (after successful Direct update by 21403) I cannot even update Manager: Parsing error
[Magisk] Didgeridoohan:
Had no issues here. Try restoring the hidden app (if it's hidden), or uninstall it and install again manually.
[Magisk] zgfg:
No hidden app for me, not using

After two times failing to update through Manager I spotted the notificatiin that 21404 was downloaded and then installed with no problem

Patching with 21404 still fails the same, Direct works

Apparently issues with A11 since 21402
[Magisk] zgfg:
To make things worse and really annoying, TJW immediately closed the issue "that he cannot reproduce" (and didn't find anything in the log)?!
[Magisk] Didgeridoohan:
Did you try a logcat?
[Magisk] BillGoss:
I'm on A10.
[Magisk] zgfg:
Everything back to normal/ok with 21405 for me:

- no more parsing the package error

- patching and flashing the image works again

👍👍👍
[Magisk] pndwal:
Yep, Patching Image method saga is over with this commit, merged in v21405 (See changelog in next post):

Fix patching files · topjohnwu/Magisk@07bd36c

Fix #3765

github.com

All happy now!

Incidentally, wanted to try 21404 when only Update (to 21405) button was available.

I simply turned off data, restarted Magisk (gotta get used to the new name!), and 'Install' (21404) was available offline!

Guessing this is the new method to flash selected builds (since merged Magisk/Manager distribution package change).

[Confirmed Patch method bug still extant in 21404] PW
[Magisk] negroxxx:
install SuperSU 2.78

magisk install zip v7

install apk v2

suhide install .54

and I still pass the safetynest
[Magisk] yoesazel:
I flashing magisk via twrp, fisrt boot take a long time to loading... And stuck in the home screen. Cant do anything... Whats wrong??? I am used RR rom on ZooL. Sorry for bad english. Can some help me??
[Magisk] knipp21:
No, you need to flash the chain fire version systemlessly

---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------

Did you type echo SYSTEMLESS=true>>/data/.supersu

BEFORE flashing 2.78?
[Magisk] negroxxx:
I did not write ....

I have to go do all the installation steps?
[Magisk] RandomPooka:
Your screenshot specifically shows you failing the Safetynet check
[Magisk] negroxxx:
Ok
[Magisk] knipp21:
Flash the unsu.zip...then type the commands, then flash 2 78, then the suhide
[Magisk] gudenau:
I am having issues installing Magisk Manager 2, my phone does not seem to think that it is an APK but it opens fine in 7-Zip.

Hashes:

File: MagiskManager-v2.0.apk
CRC-32: 3f44ed44
MD4: a34add10ebf9fd6a7674dba6baedd28b
MD5: 9051123d8269e08f41bf25c47209e6a0
SHA-1: 855244ef94a789c7538aa5e57edb69a1346e7513
[Magisk] Rhoban:
Does it have the apk extension?
[Magisk] gudenau:
Yes it does.
[Magisk] Rhoban:
And what exactly happens when you try to install it?
[Magisk] God Terrible:
I have this problem too.
[Magisk] RandomPooka:
I only mention it because your post says you pass, but the SS says otherwise. Which did you mean? I've heard of that particular testing app failing verification, while others used on the exact same system don't

---------- Post added at 01:58 PM ---------- Previous post was at 01:55 PM ----------

You could try using a different file explorer to open the apk. I've heard of some not properly opening an apk to install, but as an archive. Total Commander works well for me.
[Magisk] negroxxx:
Flash the unsu.zip. ?????

to which it refers to unsu.zip?
[Magisk] zeratos:
Can anyone tell me if flashing suhide + xposed still takes tons of ram memory from your phone? When I flashed the 0.53 version the phone started using 200 mb more ram without opening anything making every app crash for lack of memory, I am using a XT1032 so memory is really an issue.

Thanks in advance.
[Magisk] grep_i:
Wrong thread buddy, either go to suhide thread or Xposed thread.

Can't tell about that because I have Nexus 5 with enough memory so I never even cared for looking how much RAM is used.
[Magisk] Upstreammiami:
How do I add Snapchat to magisk?
[Magisk] Alxoom33:
It works! Also restores Stock recovery.
[Magisk] JensGoro:
Hi everybody.

I flashed a Stock Kernel and installed magisk. After doing this i install super su magisk Version, but magisk cant disable the root.

The app root is clickable to disable but it goes back to enable everytime.

I have no idea what i can Do more.
[Magisk] pndwal:
Latest Canary Changelogs / Release notes:

Magisk (b1dbbdef) (21404)

[MagiskInit] Fix bootloops on legacy rootfs devices

[General] Remove unneeded busybox redirection

Magisk (07bd36c9) (21405)

[MagiskInit] Fix bootloops on legacy rootfs devices

[General] Remove unneeded busybox redirection

[App] Fix bugs in patching either boot images or tar files

How to Use the APK for Recoveries

In general, it is recommended to install and uninstall Magisk through the Magisk app. However, if you insist to use custom recoveries, rename the Magisk APK's .apk file extension to .zip. TWRP should then be able to directly flash the zip file. If you have trouble renaming the file extension on PC, rename the file with TWRP's built-in file manager. To uninstall in recovery, rename the zip file to uninstall.zip before flashing it.

Diff from v21.4

[General] Magisk and Magisk Manager is now merged

[General] The app name is changed from "Magisk Manager" to simply "Magisk". If you are currently hiding Magisk Manager, you would need to un-hide and re-hide to have the app label renamed properly.

[MagiskHide] Fix a bug when stopping MagiskHide does not take effect

👍 PW
[Magisk] drivel2787:
21405 updates and patched fine, boot stuck on AT&Tn logo on Samsung Galaxy Note 10+ (SM-N975U). 21.4.2 works fine.
[Magisk] zgfg:
This is clever👍

I tried renaming to coffee.cup but didn't taste well🤩
[Magisk] 73sydney:
fwiw, i do the TWRP install way...

1) Renamed magisk.apk to zip

2) Fastbooted TWRP (cant install TWRP to a Pixel 2/XL in 11, otherwise bootloops)

3) Flashed ROM

4) Rebooted

5) Fastbooted TWRP again

6) Flashed G-Apps

7) Flashed magisk.zip

8) Rebooted system

9) Blank Magisk icon appears in launcher...um okay, thats new :)

10) Installed magisk.apk from sdcard

11) Ran magisk.... "needs additional setup" (all good used to this)..."will reboot in 5 seconds"

12) It reboots

13) All is well

Nothing to see here