yashsingh1/xdaforums huggingface dataset:
[Magisk] J.Michael:
@pndwal If @lemonsqueeze can use a file explorer, he can boot Android, and /data/adb/magisk probably isn't an issue.

I got the impression he can't boot Android, so he can't install a different version of Magisk. (Well, maybe he can, but who would try to install Magisk without first confirming that he can boot?)
[Magisk] pndwal:
Exactly!; seems he can't boot, or it crashes / loops immediately after...

But please read what I suggested... That is precisely why I put suggestions (after describing a common reason for WiFi isues etc) in this order:

😛 PW
[Magisk] lemonsqueeze:
Thanks for the advice, tried flashing boot and recovery and uninstalling magisk, didn't help unfortunately.

Sh*t, wiped data accidentally and internal storage is encrypted. Encrypted files are still there but now can't access them from twrp anymore. I guess I just lost all data on this phone. Any chance to get them back or hopeless once key is gone ?
[Magisk] pndwal:
😬... How?... Any backup?... (Always back up data! / Do nandroid BUs if use twrp...)

If you did a backup including data described here it may be possible:

Have a look at this description "Mate 9 - how to retrieve encrypted files from a broken system (userdata partition)":

https://xdaforums.com/t/mate-9-how-...stem-userdata-partition.3894561/post-78782294

This will clearly be a complex undertaking...

Nb. Encryption key for any 'adopted' SD storage will also be in data/misc/vold.

----------​

If all this fails, a clean fastboot type ROM should get you booting again... (Fastboot ROMs are more complete than recovery ROMs.)... A dirty flash could/should work too if you can save your data...

🙃😛 PW
[Magisk] lemonsqueeze:
Did one too many wipes in twrp, usually i'm careful to do Wipe -> Advanced -> Cache & Dalvik only, but this time I hit the main Wipe button which also wipes data ...

Actually in twrp it says it should preserve internal storage, and the keys are still there in /data/misc so I guess all hope is not lost. Wonder why twrp can't access the files anymore then ... Some files i have a copy fortunately but i don't have a full backup so important things will be gone if i wipe everything, didn't think it'd come to that ! Thanks for the guide, insane what he went through to get his stuff back !! Encrypted storage seems like a good idea until you realize the potential to get locked out of your own data ...

I guess i'll dd the partition and /data from twrp to backup what's left in case i can recover it later and reflash the whole device, it's completely unusable now...
[Magisk] pndwal:
... Just be aware that as keys are tied to your hardware (generated in part from its unique numbers) your only hope (IIRC) to restore data will be on that device... It's a while since I read about this, but I'm sure this goes for adopted SD (encrypted) storage too, if you used that... PW
[Magisk] pndwal:
... Bit unsure what you wiped too... Long time since I used TWRP also...

If encrypted files are there, is it password protection for twrp (or system also) that's lost?... Someone else may be more clear on what's done / to be done / if a password bypass might help/work...

I'd be trying a dirty full fastboot ROM flash at this point in case data is still accessible when system boots... PW
[Magisk] zgfg:
You could dd and save for future attempt to restore, but:

IMHO, if you cannot boot (after wiping Data), you should first try with Format Data - to establish the new (encrypted) filesystem for Storage

Dirty flashing the ROM will not do that, and you'll still have unreadable Storage

The rest is just a reminder for everybody:

TWRP is not a stock tool provided by vendors, if we install and use, we have to be careful and we use on our own risk

Btw, Dalwik and Cache can be wiped also by root explorer (like with MiXPlorer) from the rooted System, by navigating to /data/dalwik-cache and /data/cache and deleting (only) those folders
[Magisk] LedgendaryEpics:
Shamiko was messing up my GPS, so if you don't want to be tracked effectively, then use that feature.
[Magisk] m0han:
didn't quite get this. :unsure: what feature? how to use?
[Magisk] lemonsqueeze:
Getting ready to fastboot flash stock rom.

I posted a twrp-specific-thread in case someone who knows twrp well knows what to do.

Thanks for all the help, really appreciate it.
[Magisk] pndwal:
Guess if Shamiko is actually messing up GPS location, you could use this behaviour as a 'feature' to prevent apps from tracking your device! 😁 ... Possibly...

Or just turn off GPS... 😜 PW
[Magisk] huskydg:
What if you want to use GPS while it sucks?
[Magisk] pndwal:
Why use GPS if it sucks? 😝 PW
[Magisk] pndwal:
... Anyway, what sucks is highly subjective...

Eg. what about this?:

https://t.me/c/1414270883/71229

🙃 PW
[Magisk] guhvanoh:
That's a private group...
[Magisk] huskydg:
You can't pass NapsternetV or VNPay without removing these props
[Magisk] dr4go:
I wonder which solution he'd/she'd alternatively have in mind. 🤔
[Magisk] huskydg:
If you are his fan, don't blindly tell me i am sucks. I have to use the dirty way.

https://t.me/HuskyDG/33

If the magisk alpha author has looked into it and found better solution, i am graceful to learn.
[Magisk] dr4go:
I hope you didn't quote the wrong person / misunderstood my last post. I'm a big fan of you @huskydg and am using Magisk Delta for a long time now. Thanks for everything! ❤️
[Magisk] huskydg:
If you are not in group...
[Magisk] huskydg:
I agree that my solution is totally sucks. That's the only easiest way i can think
[Magisk] pndwal:
Mate, I didn't... And I'm not blindly making any such statement...

This was a tongue-in-cheek (read not serious) comment about what sucks in the spirit of this whole conversation...

...But I'm glad to hear you'll take comments on board... That's kinda what I wanted to hear... Who's not learning here? 😛

Incidentally, the very first thing I ever said to you was 'love your work' (especially Bootloop Saver)... Still respect your work / contribution to Magisk community...

For clarity, this comment:

was simply to explain the light hearted (read joke) comment made by one member about Shamiko's usefulness to another member who hadn't understood (it seems) that it was not a serious comment... Of course we can't use it to block location / tracking!

Hope you / others can enjoy such banter and not take exception to comments where no offense is intended or implied... 😛 PW
[Magisk] huskydg:
@pndwal Please understand "What if you want to use GPS while it sucks" is just a funny answer to you and there are no bad intentions here 😉
[Magisk] pndwal:
Same same!...

Touché... PW
[Magisk] pndwal:
Sorry... Initial comment was about NapsternetV solution; first comment in husky's screenshot above (partially hidden)...

Comment I linked from admin (probably Canyie) was:

Nb. This TG group is renamed, but is the original Alpha Discussion group...

Also, if this is the best solution for NapsternetV then @huskydg makes a fair point... PW
[Magisk] huskydg:
That's vvb2060, i guess

Just take a look in chat style and pay attention to the admin tag, you will know who they are.

Example:

Anonymous admin without tag is vvb2060 or someone

Anonymous admin with "残页" is canyie
[Magisk] LedgendaryEpics:
You can still use it, you just have to remove and reengage the destination and for about 3 seconds you will have an accurate location and route. For a distance of about 1 mole, you'd be doing this about 15 times if you dont know the area too well so....
[Magisk] 73sydney:
Can someone either provide actual proof that zygisk/shamiko etc does anything to GPS (i havent had a single issue and i use it daily) or i dunno, maybe stop spreading FUD because of personal gripes you have against people on other platforms that dont take part here, and therefore wont get any of the swipes youre taking at them here that only further add to the aforementioned FUD.

We've all had our moments with those folk and its fine to mention the odd bit of spice you may come across when trying to submit an issue on github (ive done this myself), but to then to continually poison magisk proper/shamiko because of that person/persons taking part is not helping anyone. Thats a personal gripe, and shouldnt colour the entire magisk (proper) project/shamiko. What we dont need is spice here....

Please, you know who you are...

I think we've all had enough, now
[Magisk] zgfg:
Excellent - thanks

By the way, people put whatever to DenyList (all apps developed by Google, following dumb 'guides' from elsewhere that more is 'better'), and then draw their 'conclusions'
[Magisk] pndwal:
I guess since 40 poles = 1 furlong and 3 barleycorns = 1 inch, it would follow (if we don't mind our Ps and Q's) that a 'distance of about 1 mole' could equate to 1/320 mile + 1inch (0.00314078283 miles = 5.055 metres = 16 feet 7.016 inches) if it is assumed that 1 mole with fur long locates 3 barleycorns over the same distance... on average...

But even knowing the area, ie. that 1 acre = The area that could be ploughed by a team of eight oxen in one day and 1 hide = The area deemed to be able to support a typical peasant family, an accurate location may never be had simply because the mole must hide from the plough and no peasant family can afford a good Android device anyway (much less with GPS)... at least your 'typical peasant family'... And they can easily achieve straight harrowing by eye in any case...

Good point...

Could this be contributing to your issue @LedgendaryEpics?...

What do you have in denylist? PW
[Magisk] m0han:
Where/how can I get the latest version (v4.0?) of NoStorageRestrict module by DanGLES3? In FMMM, when I go to 'Description', I can see that there is an update available, but it is 'not available for updating'. Can someone share here?
[Magisk] zgfg:
Did you try Install from FMMM?

It should install the latest version as available on the repo
[Magisk] m0han:
that did it. 👍
[Magisk] m0han:
All fine on another device (A11). FMMM is the same - v0.6.5.
[Magisk] LedgendaryEpics:
This is just my experience, GPS could be totally fine for other devices. I'm using a caf version of pixel 3.
[Magisk] LedgendaryEpics:
I misspelled mile and I'm not too sure how to go about the deny list, I haven't had issues with Google pay since early August, I've removed the suspected Gmail account that was probably tipping off play integrity and have avoided most modules that spoof device specifications. For right now I'm neither in a good place nor a bad place.
[Magisk] J.Michael:
Could you elaborate on "suspected Gmail account"?
[Magisk] 73sydney:
To be fair, CAF is not mainstream, in all my years of Android, from the very first Galaxy onwards, ive literally never run a CAF ROM.....

Have you also modded your gps.conf for your local region? People have been doing that since the dawn of time too. My own (mod of a) GPS magisk module is attached. Feel free to open and edit the (4 = because original module catered for non-China ROM's as well) gps.conf files, edit the NTP_SERVER lines to your local NTP pool, and give it a bash

you can drill down as far as you like starting from the zones here:

pool.ntp.org: NTP Servers in Global, pool.ntp.org

www.ntppool.org
[Magisk] m0han:
my doubts expressed here are partly addressed, i guess. i don't use shamiko now, anyway. 😄
[Magisk] LedgendaryEpics:
I'll try it out
[Magisk] LedgendaryEpics:
Whenever I add the account to my device, suddenly I can't use gpay, I get the "device is rooted or modified" notice, and finally the "gpay is updating right now" notice. I haven't used the account since.
[Magisk] m0han:
deleting (only) those folders - outright? or only the contents therein? If outright, will all these folders be auto-created when/if required?
[Magisk] zgfg:
Delete the content or the whole folders, they will be recreated on reboot

I also delete /data/system/package_cache
[Magisk] pndwal:
Moving this here as it's probably OT in MHPC thread now...

A12 builds are probably passing for the same reasons; a plethora of Devs incl. yours are now sourcing code from @kdrag0n / @Displax fixs to integrate a SN / PI fix...

Re A13 bootloop issue, guess you mean it works clean but bootloops with Magisk...

Did you disable all modules before booting w/ A13 and Magisk?... (What modules did you have installed?)... Also, did you try with Magisk fully uninstalled (all files, ie previous configuration, removed from/data/ADB before installing Magisk)?... And have you tried with latest Canary build?...

I assume you patched extracted A13 boot.img successfully?... No issues in patching log?...

Is this Galaxy A32 4g?... Patching AP (Odin flash), or boot or recovery images?... PW
[Magisk] Captain_cookie_200:
yes it is A32. i patched the AP file thats it. The A13 gsi did not boot at all at a clean flash. and its a gsi so theres no boot.img. i wiped /data the cache internal storage and dalvik etc. works for every gsi everytime.
[Magisk] pndwal:
Oh... So GSI you said "was sooooo smooth" was Google A13 GSI?

I don't know much about GSIs, but I think you have boot img!... I think new A13 should use GKI boot.img too, so non generic parts are separated to vendor_boot.img etc...

So did you try formatting data, not just wipe?... And assume you're flashing all 4(?) binaries w/ Odin, not just AP?... And did transfer w/ ADB pull, not mtp...

And tried using latest Canary (or not)?... PW
[Magisk] Captain_cookie_200:
yes gsi was smooth.

google A13 and i just discovered LeOS beta based on android 13 works fine too but there are no google apps. it is very smooth. and yes i did flash all the other binaries along with the patched ap file. i also have twrp installed and vb meta disabler.tar flashed along with it. thats how i install gsi's through twrp
[Magisk] Traviscott:
If anyone knows... does the latest version of magisk work on Android 6...???
[Magisk] J.Michael:
The web site magiskapp.com declares (at the very bottom) "This Website Isn't Owned Or Affiliated With Topjohnwu". My immediate reaction is that it is the work of a parasite, and should be avoided.

Did this Samsung device come with /e/OS installed? If not, how did you isntall it?

The John Wu installation instructions describe using Odin. As far as I know, Odin (or Heimdall on Linux) runs on a desktop computer and downloads tar files to an attached device.

You should find an /e/OS forum to ask about what their recovery supports. It does seem reasonable to assume they will "flash" a .ZIP file the way TWRP does, but you know what "assume" does...
[Magisk] 73sydney:
#1 - dont reference anything on magiskapp.com

#2 - you'll need to use ODIN to flash to a Samsung if you want to do the boot.img malarkey - best place to find out how to do that for your Samsung is in the Samsung S7 threads for your device. Ideally you would look for a post on how to install custom Recovery (TWRP) and then just simply flash the magisk.apk (renamed to magisk.zip) from TWRP which would bypass all the patching malarkey and root you automagically....i still do this on my S20, rather than patch the boot image and flash via ODIN, because im notoriously lazy

Samsung Galaxy S7

The Samsung Galaxy S7 was released at Mobile World Congress in February 2016. It features a 5.1" Quad HD Super AMOLED display, with an "always on" function, used to display a clock and notifications. Under the hood, the Galaxy S7 is powered by either a Qualcomm Snapdragon 820 or Exynos 8890...

xdaforums.com

I would change topjohnwu's instructions to read (because patching a multi gigabyte AP file is a LONG wait - my devices AP is 7gb long) (my changes in orange, this is how i do it on my S20 if i do use boot image patch and ODIN):​

[On your PC] Use either samfirm.js, Frija, or Samloader to download the latest firmware zip of your device directly from Samsung servers

[On your PC] Install z-7ip

[On your PC] Unzip the firmware and extract the AP tar file. It is normally named as AP_[device_model_sw_ver].tar.md5

[On your PC] Open the AP_[device_model_sw_ver].tar.md5 from right click context menu select 7-zip -> Open Archive and extract:

boot.img.lz4​

vbmeta.img.lz4 (if its listed)​

[On your PC] Select both files and right click and from right click context menu select 7-zip -> Add To Archive

change Archive (name -1st box onscreen) to something like boot.tar and Archive Format to tar, and click OK to create tar archive

move boot.tar to mobile device

Press the Install button in the Magisk card

If your device does NOT have boot ramdisk, check the “Recovery Mode” option

Choose “Select and Patch a File” in method, and select the boot.tar file

Move the /sdcard/Download/magisk_patched.tar file to PC

adb pull /sdcard/Download/magisk_patched_[random_strings].tar)

Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP.

Your device should reboot automatically once Odin finished flashing.

Install the Magisk app you’ve already downloaded and launch the app. It should show a dialog asking for additional setup.

Let the app do its job and automatically reboot the device. Voila!
[Magisk] MorganXYZ:
@J.Michael I just used the auto-installer provided by /e/os - it worked like a treat, never had a more straight forward and easy flash of my device: What is the /e/OS easy-installer? I was really quite amazed.

Thanks @73sydney , that's going to take me a moment or two to work through - but, I'll be using heimdall/ heimdall-frontend - all this weird Samsung stuff is very disconcerting... Do you have any inkling whether that'll make much difference?

But, just reading more closely - those instructions are assuming that the device has Samsung software on it, but wouldn't that have all been blown away by the /e/os stuff?
[Magisk] 73sydney:
Ive never used heimdall because it seemed like a lot of faffing about, but perhaps youre using it because youre not on Windows? otherwise if you are on windows, you must just love punishing yourself and doing things the hard way :)

ODIN/heimdall doesnt matter, is just going to be writing a boot image, it doesnt know you dont have Samsung software on there...its not writing or looking beyond the boot block
[Magisk] MorganXYZ:
Haven't allowed Windoze to sully my life in 20 years ;)

This is what's in /e/OS: e-1.3-q-20220905216076-stable-herolte.zip :

$ unzip -l e-1.3-q-20220905216076-stable-herolte.zip
Archive: e-1.3-q-20220905216076-stable-herolte.zip
signed by SignApk
Length Date Time Name
--------- ---------- ----- ----
363 2009-01-01 00:00 META-INF/com/android/metadata
977107715 2009-01-01 00:00 system.new.dat.br
0 2009-01-01 00:00 system.patch.dat
2097640 2009-01-01 00:00 META-INF/com/google/android/update-binary
5368 2009-01-01 00:00 META-INF/com/google/android/updater-script
36689936 2009-01-01 00:00 boot.img
2445584 2009-01-01 00:00 firmware-update/F_cm.bin
40046256 2009-01-01 00:00 firmware-update/F_modem.bin
1218560 2009-01-01 00:00 firmware-update/F_param.bin
1777936 2009-01-01 00:00 firmware-update/F_sboot.bin
2445584 2009-01-01 00:00 firmware-update/K_cm.bin
38889200 2009-01-01 00:00 firmware-update/K_modem.bin
1525760 2009-01-01 00:00 firmware-update/K_param.bin
1777936 2009-01-01 00:00 firmware-update/K_sboot.bin
2445584 2009-01-01 00:00 firmware-update/L_cm.bin
38879280 2009-01-01 00:00 firmware-update/L_modem.bin
1525760 2009-01-01 00:00 firmware-update/L_param.bin
1777936 2009-01-01 00:00 firmware-update/L_sboot.bin
2445584 2009-01-01 00:00 firmware-update/S_cm.bin
38887888 2009-01-01 00:00 firmware-update/S_modem.bin
1525760 2009-01-01 00:00 firmware-update/S_param.bin
1777936 2009-01-01 00:00 firmware-update/S_sboot.bin
2445584 2009-01-01 00:00 firmware-update/W8_cm.bin
39115376 2009-01-01 00:00 firmware-update/W8_modem.bin
1218560 2009-01-01 00:00 firmware-update/W8_param.bin
1777936 2009-01-01 00:00 firmware-update/W8_sboot.bin
1184 2009-01-01 00:00 firmware-update/filemap
45320208 2009-01-01 00:00 firmware-update/recovery.img
1028 2009-01-01 00:00 install/bin/backuptool.functions
2233 2009-01-01 00:00 install/bin/backuptool.sh
794752 2009-01-01 00:00 install/bin/resize2fs_static
12651 2009-01-01 00:00 system.transfer.list
1456 2009-01-01 00:00 META-INF/com/android/otacert
--------- -------
1285984534 33 files
$

That doesn't seem to have anything like

But, does have boot.img

?

Can Odin/ heimdall be used to install boot.img to the correct partition? Which I'm guessing, looking at:

heroltexx:/ # ls -l /dev/block/by-name
total 0
lrwxrwxrwx 1 root root 15 2022-09-24 16:39 BOOT -> /dev/block/sda5
...

Above, would be /dev/block/sda5

?

(I'm really floundering around in the dark here...)
[Magisk] 73sydney:
Those modified instructions mentioning .tar files are for stock Samsung ROM's, i was pointing out a deficiency in johns instructions, it wasnt meant to be a direct roadplan for your particular issue.

All you need on that custom one is the boot.img, patch it and then send it to the correct partition, which i dont know how to do with heimdall as ive specifically avoided it since the dawn of Android time.

Just think, if you had windows, you’d have been done by now :)
[Magisk] Sarosh Ishfaq:
I have problem to update Magisk in samsung note 9 sm-n960f/ds. Please help
[Magisk] zgfg:
Boot.img patched by Magisk v22 - are you maybe using a custom ROM with the built-in (very old/deprecated) Magisk?
[Magisk] pndwal:
You need to do just as the message above states; download ROM corresponding exactly with current version (especially if you took OTAs since first Magisk installation), patch the AP binary and Odin flash all 4 binaries per 'Samsung (System-as-root)' section in Installation Instruction page under 'Upgrading the OS' (even though you're not 😉 ): Flash magisk_patched.tar as AP, together with BL, CP, and HOME_CSC...

(- Please say if you use a custom ROM... May have additional issues...)

This is needed because refactoring of magiskinit injection in 25+ has broken Direct Install (when updating previously patched boot images) in a number of 2SI boot type devices as images w/ patched fstab (no longer done) are now incompatible with magiskboot patching... Instructions for patching / flashing Magisk from unpatched images still works fine...

Further, since updating your legacy ramdisk boot type device to Android 10 it has been automatically updated to 2SI boot type... As such 'Samsung (System-as-root)' section (methods, precautions, warnings) has information pertinent to your device despite the message "If your Samsung device is NOT launched with Android 9.0 or higher, you are reading the wrong section". (- This was true at the time of writing however since no Sammy devices yet had A10)...

👀 PW
[Magisk] pndwal:
... Just a couple of thoughts:

ROM Devs properly don't distribute GApps with ROM if they care about Google's rules / licensing for proprietary code, however these are easy to 'sideload', and distributions for this purpose, ie. for personal installation by end user on certified (licenced) or Google Registered (whitelisted for custom ROM use by submitting Google Services Framework Android ID) devices, are permitted / sanctioned by Google... You should be able to install OpenGapps, BitGapps, NIKGapps or other distributions after installing a ROM lacking these...

If you can get a fastboot type distribution of your desired ROM you may have more success, and even with a recovery ROM you should be may be able to extract vbmeta partition and flash it with the following switches:

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

per official Magisk (optional) instructions:

https://topjohnwu.github.io/Magisk/install.html#patching-images

instead of using 3rd party vbmeta disabling methods... I really don't know if this will help, but may be worth a shot...

🙂 PW
[Magisk] m0han:
Today's update of TB Checker app works okay for Root check and Xposed check, but hangs on Play Integrity check, and then crashes.
[Magisk] zgfg:
Just updated TB Checker

For me ok, passing Basic and Device, failing Strong Integrity, not crashing

Xiaomi 11 Lite 5G NE, A12, Magisk Canary, Displax USNF
[Magisk] m0han:
Poco X3 Karna, AICP 17.1 (A12.1), latest Magisk Delta and modules, one of which (might) be having a conflict(?). But, the original app does it's job as expected. TB Checker continues to crash.