yashsingh1/xdaforums huggingface dataset:
[Magisk] J.Michael:
Sometimes the .tar.md5 file is the .tar file, with the md5 of the tar file appended. That's what I got when I unpacked the zip file I downloaded, that's what I fed to the antediluvian Magisk I used. @zgfg's suggestion of checking the file size is a good start.

The talk about being unable to select a file (@xAxB said the files were all grayed out) makes me think it's some permission issue. I don't think the content of the file matters until after you've selected an inappropriate file.
[Magisk] xAxB:
I tried both Canary (23001), and 23.0 (23000) (21) (downloaded from Github and it does show. Perhaps it is as @pndwal mentioned, a per-device setting (the Tab S4 is 3 years old)?

On the plus side, I sorted out the greyed out thing. Basically you can't just tap on Galaxy Tab S4 / SD card and select the file from there (everything is greyed out), but select an external app (e.g. My File) from within Magisk, and select from there. Hope that makes sense for anyone who run into this issue (on Googling, I am not the only one who ran into this issue).

I would also like to confirm that the tar.md5 file is 4.05GB and this seems to be the way the AP are named, at least on the Tab S4.
[Magisk] timofonic:
Anyone willing to mirror those alphas here at least? I don't use Telegram, sorry.
[Magisk] pndwal:
Just tried this for fun:

- Downloaded SM-T830_2_20201216125534_g1kppegt0a_fac.zip (Stock Android 10 for Tab S4 Australia T830 ROM)

- Extracted on my Xiaomi RM8T (stock ROM, Alpha Magisk)

--> Result

- Patched AP_T830XXU4CTL2_CL19646842_QB36555982_REV00_user_low_ship_MULTI_CERT_meta_OS10.tar.md5 as is

--> Result

magisk_patched-23001_5zUJB.tar = 4.35GB.

I love a challenge, so I was disappointed not to have as much fun as I'd hoped for... No challenge at all... But I did learn something. 😛

Seems (to me) that .tar.md5 indicates a tar with a message-digest algorithm, a Cryptographic hash function. (Attackers are forced to decipher those hash values if they want to exploit them. Hashes slow down attackers.)

Edit: see the following is sorted now. 👍

[I'm now thinking permission issue (likewise) or file browser used by Magisk App....]

Hope this helps. PW
[Magisk] jons99:
I uploaded it in a post earlier look up or get it from github

GitHub - vvb2060/magisk_files

Contribute to vvb2060/magisk_files development by creating an account on GitHub.

github.com
[Magisk] pndwal:
Latest works fine as reported, and is on GitHub. You generally won't need Telegram as I said today:

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

It's best not to add unauthorised sources. (Countless are suspect.)

See 'earlier notes' here for GitHub link:

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

👍 PW
[Magisk] pndwal:
Great.

Did it flash / boot w/ Magisk root ok?... Also, I'm interested to know if 'Preserve force encryption' is checked or unchecked by default for your device. 👍 PW
[Magisk] pndwal:
FWIW, here's the criteria for several options showing / reasons for hiding per device:

www.twitter.com/topjohnwu/status/1297833910320021504

So seems Keep forceencrypt requires FDE (Full Disk Encryption - legacy) support to show / work. (Newer devices use File Based Encryption.)

Devices shipping with Android 4.4+ implemented FDE as an option. From Android 7.0, it was enabled by default.

Many devices shipping with Android 9 moved to FBE. Devices shipping with Android 10+ were required to move to FBE.

Samsung Galaxy Tab S4 shipped with Android 8.1. PW
[Magisk] ipdev:
@zgfg @pndwal @J.Michael @xAxB

It has been quite a while since I had Samsung.

Android 5.1.x days. ;)

Since then I have decompressed Samsung factory roms to borrow some prop(s) or ...

Samsung stock roms are always in .tar.md5 format.

OT:

If you are manually decompressing Samsung factory roms, you might run into a password protected compressed image.

Big thanks to Rick#2 for his post Here, helped saved me some time a few years ago. ;)​

Cheers all. :cowboy:
[Magisk] ipdev:
Magisk install differs between device and system builds.

Using Magisk Canary

My OnePlus 6T is still regular A/B device.

I get the option to Install to Inactive Slot (After OTA).​

My Pixel(s) have been updated to virtual A/B devices.

No option to Install to Inactive Slot (After OTA).​

I am not sure what I recently flashed, but I had the option to Preserve force encryption.

Might have been my Nextbit Robin (Lineage 18.1).

I leave it at work for streaming music. Will double check in a few days when I go back to work. ;)​

Wonder if Preserve force encryption still shows on older devices that have been updated to FBE. :unsure:

I know all I had to do was edit the fstab to remove forceencrypt on my Nexus (5X?) that was updated to FBE.

I am back on razorloves' builds for my Nexus 5, 5x and 6p so, back to FDE.​

Cheers. :cowboy:
[Magisk] jons99:
I'm not sure but I think you need to first uninstall magisk from the app then apply the ota and then you'll get an option to install to the other slot personally I never tried it as I always flash everything in fastboot
[Magisk] ipdev:
Normally I do not use the OTA updater. ;)

I normally use TWRP or fastboot to install full updates.

I only install TWRP on older devices.

I will normally boot into TWRP using fastboot boot on newer devices.

or use the custom recovery that is built/installed with the custom rom I am using.​

​

Recently, on my OnePlus 6T, I tried using the built in OTA update.

This was not a true OTA since I downloaded and used the full update instead of a partial update.

I was on OOS v10.3.10

No Magisk. No TWRP.

Downloaded v10.2.11 and upgraded using OnePlus's local update to install.

Copied update to /sdcard/

Installed Magisk (app), patched the v10.2.11 boot image and rebooted to bootloader.

Used fastboot to boot the patched image.

fastboot boot magisk_patched-23001_IWxOc.img​

Used Magisk (app) to install using the Direct install option.

Rebooted to make sure Magisk was active.​

Downloaded v10.3.12.

Deleted the 10.3.11 version in /sdcard/

Pushed 10.3.12 to /sdcard/ and used OnePlus's local update to install.

When done, I did not reboot.

Then flashed TWRP using Magisk's Module installer.

Then installed Magisk to inactive slot and rebooted from Magisk.

OnePlus 10.3.12 booted with Magisk installed and active.

Rebooted to recovery adb reboot recovery and I booted into TWRP.

From TWRP, I rebooted to system (using the power menu in TWRP) and I was back in OOS 10.3.12

Seemed to work on my OnePlus 6T. ;)

Android 10 (SDK29) Regular A/B device.

As I mentioned a while back, osm0sis found a way to do it with virtual A/B devices.

Post #45,597

To quote one of osm0sis's post linked in my older post.

Cheers. :cowboy:

Edit:

PS.

If I remember correctly, OnePlus OTA updater would detect root/modified system.

So it would download/install the full version instead of an incremental/partial update.[/I]
[Magisk] jons99:
OTA Upgrade Guides

The Magic Mask for Android

topjohnwu.github.io
[Magisk] ipdev:
In general yes.

This seems to be another device specific issue.

In the case of OnePlus 6T, you do not have to restore stock images first. ;)

I added a post-script note to my prior post.

Edit:

PS.

If I remember correctly, OnePlus OTA updater would detect root/modified system.

So it would download/install the full version instead of an incremental/partial update.​

​

Cheers. :cowboy:
[Magisk] osm0sis:
Depends on the device. On 8T and newer, which use the new "Google OTA" (Google Play services meditates the OTA) process, it'll do incremental regardless of root status. Also, to make it even more complicated, that's only on International/North American variant OOS and only on stable ROM channel.

Edit: Now that there's a working kebab TWRP my next trick will be to see if the post-reboot OTA checks might pass with it reinstalled in between, since then we could reroot while avoid the bootloader/PC steps; there's a chance it might since it's a recovery_a/_b device. I'll check into that with the next security update my 8T gets. 🙂🤞
[Magisk] jons99:
yeah since op otas contain all the original images you don't need to restore the original images (I happen to own the op6 as a secondary device to my pixel 5) but in google devices you need to restore the original images before you can install magisk to the inactive slot

on older op devices at least

cheers
[Magisk] spevil07:
As I sayd, I uninstalled only the Magisk app/icon.

I am at oxygen is and after every reboot I must uninstall the app/icon.
[Magisk] pndwal:
Sure. But I asked 1) 'how did you set up (install) the App?', and 2) if it's 'pre-installed with ROM' (Seems you have OnePlus device with OOS? Is that unofficial, or stock ROM? If unofficial, please cite link to ROM) or 3) if App is 'merged as a system app' (ie 'systemised') and 4) if you 'just deleted the home screen icon!...

You didn't answer any of these questions.😕

Please state specific device, ROM, Magisk version and installation method. 👍 PW
[Magisk] spevil07:
1. Installed Magisk over twrp

2. It's not pre-installed / oneplus stock oos A10

3. App isn't system app

4. Uninstalled Magisk app/icon as every app like WhatsApp

Oneplus 7 pro, stock oos, Magisk-23.0(23000), installed over twrp

I hope all questions are now answered
[Magisk] pndwal:
Not sure re. '4. Uninstalled Magisk app/icon as every app like WhatsApp' that you are not simply removing a launcher icon...

What happens if you go to device Settings, Manage apps, select 'Magisk' and uninstall from there?... Also, have you hidden the Magisk app in Magisk App settings? PW
[Magisk] jons99:
dude how do you even pass safetynet without magisk hide? I mean look at pndwal for example he doesn't uninstall magisk yet magisk is undetectable maybe instead of asking pndwal how to uninstall magisk ask him how to hide it properly

https://xdaforums.com/t/magisk-general-support-discussion.3432382/page-2339#post-85370757
[Magisk] J.Michael:
What about Magisk Manager app? Did you ever download the .apk file and then "install" *it*? Or was there a Magisk app in the app drawer as soon as you installed the system ROM?
[Magisk] ipdev:
I was a little confused but, I had an idea that I just checked.

The Magisk stub app seems to be reinstalled while Magisk is active.

I did not go all in and delete my magisk.db but, I assume the stub app would not be reinstalled.

or boot a non-magisk boot image.

This was a quick check.

Anyone can test it. Just uninstall the Magisk app and reboot.

It is the same result once Magisk is configured. Did not matter what device or Magisk installation.

Nexus 7 (2013)

ARM | Lineage 18.1 | Magisk (canary) installed by flashing in TWRP.​

Pixel 3aXL

ARM64 | abcROM (Android 11) | Magisk (canary) installed by patching boot image.​

I never had a reason to uninstall the Magisk app so, I never noticed it before.

I am guessing that if someone has time to look, they will find something in the Magisk release notes about it.

Cheers. :cowboy:
[Magisk] ipdev:
Once you configure Magisk, the app is not necessary.

Magisk settings are stored in magisk.db

You only need the app to configure Magisk.

MagiskHide will still be active unless you turned it off before uninstalling the app.

Root access will still be granted to the processes that you granted it to.

Modules will still load on boot.

I have never used them but, you can configure some Magisk options from command line.

Cheers. :cowboy:
[Magisk] pndwal:
I had a feeling it'd have something to do with stub, but I think you've put your finger right on it. 👍

Just tested, first with Alpha setup w/ App hidden. -

Uninstalled app, rebooted, checked and App / Magisk stub was gone from app draw, but Magisk stub was indeed still present in device settings / Manage apps.

Another reboot and stub shows in app drawer / launcher. Clicking brings dialogue asking to download/setup full app.

Next, tried after unhiding App, then uninstall and reboot -

Surprised to see stub still returns!

Had a thought it may be unique Alpha behaviour as this will use local stub when hiding App, so next reverted to regular Canary (both App and Magisk mask) and tried again w/ App hidden, then uninstall and reboot -

Stub still returns.

Next, tried after unhiding App, then uninstall and reboot -

Stub still returns.

(So seems official builds save stub locally also, but use server based stub when hiding!)

My feeling is that there should / may be a way to prevent stub being loaded on reboot, especially if Hide the Magisk app is not selected; probably an easy code edit for someone to identify / post. 😉

ATM I haven't investigated or discovered a a way to disable stub loading at boot time. PW
[Magisk] xAxB:
To answer your question, 'Preserve force encryption' was checked by default for my device. I bought this device second hand, and it has been upgraded to Android 10 on arrival. I am not sure if the upgrade in itself converted the system to FBE though.

Unfortunately, I am not able to confirm Magisk root works for the Tab S4, with the latest update as I am having trouble with Odin. I tried Odin 3.13.1 and 3.14.1, with three cables and 4 USB ports (though only one is USB 2.0) but while Odin detects my device fine, it simply won't flash the device (doing nothing at either initialisation or setup connection) , not even the most recent stock rom, so I am probably out of luck until I can find another computer to try on.

(Though I am leaning towards the issue being something about my setup not working well with Odin, part of me also wonder if there isn't something wrong with this second hand tablet that makes it not play nice with Odin.. not sure if that kind of issues happen)
[Magisk] pndwal:
Bit further on this; can I assume you tried using the standard 'Hide the Magisk app' function in Magisk App settings? - I'm not sure why this wouldn't work... PW
[Magisk] pndwal:
Ta. Is it also SAR = Yes?

Sounds like driver / permission issues on PC?

Not sure of Odin requirements... Take it you confirmed bootloader is unlocked... Have you tried with USB Debugging enabled and checked OEM unlocking is Allowed in Developer options?

A suggestion with ZERO Sammy experience. 😬 :

I saw several guides to root your device w/ Magisk and earlier OS builds, but all involved downloading a prepatched boot image (must be matched to specific ROM version), but imsmc, simply flashing patched boot image did work for your (originally non-SAR) device.

There are also TWRP implementations available.

Official TWRP specifies using Odin to install, but I see you can also get to ADB / Fastboot for this device. Here's a guide using Fastboot to unlock bootloader:

https://www.mobilewithdrivers.com/unlock-bootloader/samsung-galaxy-tab-s4-64gb-4gb-ram

So if you can obtain a .img format TWRP, you can likely flash or simply boot to it (I'd boot it rather than flash) using PC ADB Fastboot connection, then take a TWRP backup of boot.img, locate and rename backup .win file to .img, boot system and patch that from Magisk App, boot TWRP again to flash Magisk-patched image...

Again, I have no Sammy experience, but this (or a variation) may work for you. 😜

Could be, especially if you obtained it with bootloader unlocked... PW
[Magisk] jons99:
26 is out

Magisk alpha

1eb83ad8-alpha-26

t.me

The beta version does not send channels. Try to support oplus.fstab. No need to update the ones that are already available (translated changelog)
[Magisk] teddy0209:
I see you're using RR, did you remove inbuilt root prior to flashing supersu? Did you check if it was successfully installed as systemless? I suggest, you boot to system prior to flashing magisk and check in the supersu app under install as system app (you should see there if you have systemless)...
[Magisk] royaLred:
Sure it is.

http://xdaforums.com/attachment.php?attachmentid=3893658&d=1475527472

Gesendet von meinem SM-G935F mit Tapatalk
[Magisk] Kursem:
I flashed superSU 2.78 directly after flashing custom rom, which should have remove the inbuilt root and replace it with superSU. I've just checked with Link2SD and I have superSU installed in /system/app/SuperSU. Also, I didn't know how to check if it was installed as systemless or system mode, but I've read that superSU will install as systemless on Marshmallow or Nougat regardless. fyi I was using android 6.0.1_r72 (RR 5.7.4)
[Magisk] teddy0209:
That was your problem, you have to be systemless... The inbuilt root for RR is nonesystemless, so you have to remove it prior to flashing supersu... system/bin/su, system/xbin/su, delete them manually, or search for unsu zip, or you can even use the supersu app to full unroot...
[Magisk] Kursem:
Alright, this is what I did. Uninstall systemless Xposed (which strangely restore my root access), uninstall Magisk, trying to delete delete su but there's no su folder in /bin and /xbin, so I remove root using SuperSU full unroot. Flashed Magisk v7, then I flashed phh's SuperUser r259, then lastly I install systemless Xposed 86.6 through Magisk Manager. finally I can has Xposed with root access.

Does this also mean I can't use latest SuperSU with Magisk v7 ?
[Magisk] Captain_Throwback:
UPDATE - There's a workaround in the suhide thread to get SafetyNet passing again, without the use of RootSwitch.

It's also recommended to use the SafetyNet Playground app, as the other app produces inconsistent results.
[Magisk] edyny1:
Same one i have but when i click to change it to enforcing i get the notification that it changed but when i go to about my device ot still say permissive, even after reboot still says permissive
[Magisk] grep_i:
I'm using this method since last night and also switch to safetynet playground because safetynet helper told me I couldn't pass safetynet but I could use Pogo and Snapchat and Android pay.

Safetynet playground told me I could pass.

A couple of minutes ago I tried again but pressed the wrong icon safetynet helper instead of safetynet playground but this time it passed tried it multiple times with success now.

Edit: sorry for posting in wrong thread
[Magisk] rhyzan:
Bumping this.
[Magisk] aaronmil:
Did you end up finding a way to fix this? I have CM13 on my 2013 Moto X right now, so don't think reverting to stock boot.img is an option. Can I uninstall from recovery somehow? I can't even swipe to unlock currently.
[Magisk] YzRacer:
Sorry for the long delay, but I've been working and traveling. I finally got around to updating to v7 and updating my mod to the newest template. Now I have succeeded in installing the mod using Magisk Manager but after rebooting I still have softkeys at the bottom of the screen. I am running my script in post-fs-data and after a reboot I opened a terminal and used the getprop command to verify that qemu.hw.mainkeys=1.

The guide says non ro props need to be set in post-fs-data so unless I am reading something wrong it seems my mod is in order. Perhaps this prop is set too late in the boot process to take effect? What happens if I try to set this prop in post-fs?

Thanks for the awesome work! Magisk is working great with everything else,
[Magisk] Ninoh-FOX:
Erase for copyright XD sorry...

Enviado desde mi E5603 mediante Tapatalk
[Magisk] iscaela:
If you have a working recovery, you can just flash the uninstaller zip (worked for me) or manually dd the backup image (don't remember if it's in /data or /cache) or just reflash CM.

Otherwise, you can hopefully find a CM image to flash from fastboot.
[Magisk] Captain_Throwback:
You need to remove that link. [MENTION=631273]Chainfire[/MENTION] explicitly states not to redistribute suhide (which it why I didn't post a link to it in that thread).
[Magisk] Triviox:
Mod Edit: Links Removed.

Thanks! The software should be shared =)
[Magisk] Orochi77:
I am having issues with Magisk 7 and latest supersu.

Flashed latest supersu then latest magisk7, I get no root.

I've read that Magisk7 should detect and convert systemless supersu to one of its own modules. Not sure this is happening.

I want to use supersu because of flashfire app that lets you install OTA.

Anyone else has a similar issue?
[Magisk] Alxoom33:
Not according to [MENTION=631273]Chainfire[/MENTION]. You are going to ruin it for everyone. Please take down your dl link!
[Magisk] CrazyCypher:
I agree.. if we won't respect his wishes he will stop the development and we'll be screwed..
[Magisk] Triviox:
We use xposed systemless 86.2 that other develop.,

ChainFire post it cause the other develop have not problems to it; I think CF is a great develop, but all can contribuite to develop better tools /ways to all =)
[Magisk] Captain_Throwback:
Please remove the link from your quote, as the software is not allowed to be redistributed.
[Magisk] pndwal:
Thanks! I've now updated, all working fine on RN8T.

Latest @vvb2060 Magisk Alpha build (July 26, 2021) change:​

Chinese Translated:

Magisk (1eb83ad8-alpha-26)​

• Support oplus.fstab for Oppo series devices

Nb. This build is available only on Telegram at present. I'll post full Changelog here when available on GitHub.

Last GitHub build, notes, links:

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

🤠 PW
[Magisk] pndwal:
OP Wellbeing Report 😀 :

John's growing up / happy with work... 🙂

www.twitter.com/topjohnwu/status/1419562776767340547

... Sometimes I forget he's so young. 😛 PW
[Magisk] Devilsho:
every time i run any command this error came i googled tried everything solution but i dont know why this error.

i reinstall Magisk rooted again but stil this error

/system/bin/sh: pkg: inaccessible or not found

this error is not just for pkg update its for every thing.

Thanks in advance
[Magisk] dcarvil:
You have to run pkg from the normal (non-root) prompt. It is not the way you expect it to work, but that is how it works on my device.
[Magisk] Devilsho:
Thankyou for reply solved it🥰😎
[Magisk] xAxB:
A/B = No

Ramdisk = Yes

SAR = Yes

USB debugging is enabled and OEM unlocking is allowed in the developer options. I have a question though, if I am only trying to flash the current stock rom, a locked bootloader shouldn't be a problem right?

Truth to be said, I -do- wonder if my bootloader is fully unlocked. The Magisk installation guide mentions something about needing the IEM unlocked and greyed before it's truly unlocked (something to do with Samsung's 'Vaultkeeper'), but I following the steps to reproduce that from multiple guides, 'the volume up long press' option to enable 'Device unlock mode' in the warning screen (2:41 in this video, or in this guide) simply doesn't show for my device. As far as I know, the Vaultkeeper 'later' and I do wonder if it hasn't been introduced only from the Tab S5SE in the video and onward. but unfortunately I haven't been able to get any confirmation in the Tab S4 forum.

Thanks for that guide, I didn't come across it. I did wonder if there isn't a work around from having to use Odin, but all my searches pointed toward having to use it on Sammys. But first thing first, I just want to be able to restore to a stock ROM first. If I am not mistaken, this shouldn't need an unlocked bootloader, and if something goes wrong in the process, I should at least be able to restore the system.

On a sidenote, the device came with the bootloader locked and Knox hasn't been tripped. I just kind of wondering if the previous owner -really- wanted a rooted device but after spending hours doing all the things I am doing now, gave up and flogged the device and perhaps the issue is something to do with the USB-C port on the tablet (in reality, I think it is unlikely - both the assumption that the previous owner might've wanted to root the device and there is something wrong with the port even though it charges and transfer files perfectly fine). I am pretty sure that I am on the latest Sammy driver, but I guess I will double check.

There is also one more port on my PC that I could try, but it is USB-C, so I am going to have to do it with a USB-C to USB-C cable, and the port will clearly -not- be a USB 2.0 port as many recommends.
[Magisk] BillGoss:
That's because Termux won't let you run the pkg command as root because it screws up the the installation. You must only run pkg as user.

Nothing to do with Magisk.