yashsingh1/xdaforums huggingface dataset:
[Magisk] AquilaDroid:
Thanks again for trying! This is way above my "pay grade" <G>...

Here's the output from my last try:

C:\Users\aquil\Desktop\August Platform Tools\platform-tools>adb shell

redfin:/ $ ls -Ral data/adb/modules

ls: data/adb/modules: Permission denied

1|redfin:/ $ "ls -Ral data/adb/modules"

/system/bin/sh: ls -Ral data/adb/modules: inaccessible or not found

127|redfin:/ $ "ls -I /data/adb/modules"

/system/bin/sh: ls -I /data/adb/modules: inaccessible or not found

127|redfin:/ $

Permission denied? I'm obviously doing something wrong but not getting anywhere!

Just has another look - it's not connected?

127|redfin:/ $ adb devices

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

127|redfin:/ $

I'll start the adb tutorial later today...
[Magisk] pndwal:
I'm not sure why things worked fine for @ipdev / redfin / August update... He did boot to pre-patched Magisk image from earlier (July?) build before using direct install method to update Magisk w/ latest redfin ROM however.

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

...Not sure if this round-about method is actually needed for some reason. 🤔

Perhaps @ipdev could chime in here; could perhaps supply you working patched image. 😜 PW
[Magisk] rodken:
Here are my files.
[Magisk] Triviox:
Done fuhrer.

Edit : someone did PM to me asking for THIS topic, but i dont use talpalk..can PM me here in XDA if you like. And i speak better spanish than english xD
[Magisk] zeeBomb:
How would Magisk work for Nougat then? Just install with the latest version of SuperSU, reboot and Done? I would like to use this in conjunction of Viper4android!
[Magisk] Ninoh-FOX:
Link erase... Sorry for this...

Enviado desde mi E5603 mediante Tapatalk
[Magisk] miguelrivas:
I have already root with systemless Supersu, can i install magiskmanager.zip with flashfire? flashfire no detect it to flash.

this device havent custom recovery avaible yet.
[Magisk] fabi_92:
sorry guys, i can't delete xbin/su with root explorer then i can't flash suhide.

how i can solve?

thanks
[Magisk] Artim_96:
Do you mean you can't uninstall system supersu? There is an unsu zip fit made osmosis.

Otherwise get TWRP and do it from its file manger
[Magisk] fabi_92:
with twrp gave me an error 1

my steps are:

flash rom

flash 2.78 super su

boot

flash magisk

boot

remove xbin/su

flash suhide

done.

it was good some day ago but now ive some difficulty
[Magisk] toyds:
i try to install it with resurrection remix ROM(dior) and it seems successful but when I uncheck phh usersu in magisk manager then reboot I cannot open the magisk manager anymore :(

also when I login to pokemon go(0.41.4) it says unable to authenticate.can someone please help me how to fix this one?

thank you very much
[Magisk] jonnyneto:
I cant iniciate pokemon go someone can help? Plss?
[Magisk] ryaniskira:
Is there any fix for this? All I ever get is "This zip is not a Magisk module!!!1!1!1!111"
[Magisk] Artim_96:
When you installed SuperSU as systemless, you shouldn't reckoner xbin/su, that would break SuperSU
[Magisk] fabi_92:
without this, i can't install su hide and pokemon go
[Magisk] Artim_96:
Then you do something wrong. Or is it about removing SuperSU completely? Then flash the unsu zip
[Magisk] fabi_92:
i haven't remove super su. only flash 2.78 + magisk like above..

you mean i need to make the old method?

thanks
[Magisk] Artim_96:
When SuperSU was installed in systemless mode, just flash suhide on top. Removing xbin/su (you didn't even told from where, /xbin/su does not exist) is never good.

And also, this is nothing that belongs here. If you have problems with suhide, go to its thread
[Magisk] toyds:
can someone help us how to alter the system so that we can play the latest pokemon go?thanks a lot
[Magisk] foxsprout:
Hello! Forgive my ignorance but I can't seem to find the solution to my problem. I find that Magisk (or phh superuser, or even systemless Xposed) is keeping the kernel when I installed it on.

Say I installed Magisk and all of its companions on a beta2 kernel. Now, I'm flashing the final build of my kernel and I'm good except I'm losing Magisk capabilities (since it's systemless), therefore I flash all of them over my kernel's final build and now I'm back with beta2. Anyone care to explain and give a solution?

P.S. I tried using Magisk uninstaller before flashing my kernel and it's giving the same result
[Magisk] Artim_96:
Maybe restore the stock boot.img, flash the kernel and remove the stock_boot_******.img.gz

The only reason why it's reverting to the kernel you had before would be because it uses the backuped boot.img which contains the kernel (I don't know if it actually does but that would explain it, since there wouldn't be any other way to get the old kernel back when the new one is installed)
[Magisk] Rhoban:
I say start with a clean flash. Flash ROM, flash final kernel, flash Magisk. That should get everything going.
[Magisk] foxsprout:
Yes, I realized that the first time I installed Magisk the log stated that a new backup is created and I was searching for the backup-ed kernel. I read along the lines that should be the file name but I can't find it in /data/, only stock_boot.img, which I'm not sure which kernel is that. Any idea where to find it??

---------- Post added at 07:48 PM ---------- Previous post was at 07:46 PM ----------

Forgive me, but I believe that is not a solution. Reinstalling everything surely eliminates every problem.
[Magisk] zgfg:
Please check PM/Conversation
[Magisk] ipdev:
I completely spaced-out on this. 🙃

The Start option would be the same as fastboot continue

The only difference in the bash (sh) script and the batch (bat) script is some local command terminology.

Slight differences between unix/linux based OS(s) vs. dos/Windows

The fastboot command is a binary (compiled slightly different) but the options should be the same.

You should be able to do the same change I do with the flash-all.bat as I do with flash-all.sh version.

If you want. ;)

Cheers. :cowboy:
[Magisk] ipdev:
Something is borked. :(

Not sure where but it has to be the Magisk install.

- Might be the patched boot image ?

- Might be something in /data/adb ?

It has to be something early in boot that Magisk still runs even in safe mode.

---

I did a little screwing around last night with booting into safe mode.

Sets a boot flag, so the next boot will be into safe mode.

When booting a Magisk patched boot image into safe mode, most of Magisk is disabled.

None of the modules or boot scripts in post-fs-data or service run.

Even the Magisk app was not active while booted into safe mode.

Same if you uninstall the Magisk app before booting into safe mode.

Magisk will not install the stub app when booting into safe mode by the way.

Cheers. :cowboy:
[Magisk] ipdev:
You did nothing wrong with the command.

adb shell normally has a little higher security than user but, not always.

adb shell will not have high enough permissions to access /data/adb/ on a factory release user build.​

ls is the list command, same as dir in the dos/Windows world.

The -l option will display in list format.

The -a option will display all.

The -R option is recursive. (Extends the ls command thoughout all the subdirectories.)

rm is the remove command, same as del in the dos/Windows world.

The -r option is recursive. (Adding this will delete everything including subdirectories.)

---

The prompt redfin:/ $ shows that you are already connected via adb shell.

The 127 is showing because the prevous command exited with an error.

127|redfin:/ $

PS.

You would need to exit adb shell and call adb devices from you computer command line. ;)

Unless you install adb on the device but, that is a different story.

Cheers. :cowboy:
[Magisk] ipdev:
@AquilaDroid

I uploaded the patched July and August boot images (stock and patched) that I am using.

gDrive - Link

If you upload your stock and patched images, I will give them a try and see if they boot for me.

Cheers. :cowboy:
[Magisk] ipdev:
Looks like I need to clarify my steps a bit. ;)

Most of my devices allow me to fastboot boot a boot or recovery image.

Pull the boot.img from the system (ROM) zip that I am installing.

Rename it so I know what it is.​

Push the boot image file to the device.

adb push NameOfFile.img /sdcard/Download/​

Patch the boot image using the Magisk apps's Patch File option.

Pull the patched boot image.

adb pull /sdcard/Download/magisk_patched-NameOfFile.img

Rename it so I know what it is.​

Reboot to bootloader.

Boot the patched image to make sure it boots and nothing is broken.

fastboot boot NameOfPatchedFile.img

This is only a temporary boot for testing, magisk is not installed yet.​

If everything seems to be good.

Install Magisk by using the Magisk apps's Direct install option.

The last step is just the easiest way to install Magisk at this point.

No need to reboot into bootloader, flash boot and reboot to system.

Cheers. :cowboy:
[Magisk] AquilaDroid:
Stock boot.img - https://drive.google.com/file/d/1XeiUolsipFAGheYiPSyB_2eCF_P5I4G-/view?usp=sharing

Patched boot.img -

magisk_patched-23001-redfin-rq3a.210805.001.a1-boot.img

drive.google.com

@AquilaDroid

Just downloaded. Then MD5 is different than the one I've been getting so I'm going to flash it and see what happens. Thanks to all of you for hanging in there, it's way beyond expectations (even for XDA!).
[Magisk] AquilaDroid:
No joy... bootlooping. I knew it was a LONG shot.

And...back to safety.

MD5s match on your stock boot.img and mine.

https://drive.google.com/file/d/1XeiUolsipFAGheYiPSyB_2eCF_P5I4G-/view?usp=sharing, https://drive.google.com/file/d/1Y5-C_UMQ8U-rQm1TMPv0JU27GfWGeErw/view?usp=sharing
[Magisk] ipdev:
Sharing is not turned on for the patched image. ;)
[Magisk] ipdev:
Both md5sum and sha256sum match on the stock image.

md5sum: 8e17a3b77eccd7035bd9be3cbcb8897d

sha256sum: 5be8eba8d4848794184bb1207f56a4c82bd15c8fd397e7f4e0af2c5d513ac41f

Cheers. :cowboy:
[Magisk] AquilaDroid:
Should be now, sorry (again!).
[Magisk] zgfg:
AFAIK, your adb ommands (and more generally, access to /data/adb) require root privileges. But your Magisk is broken, hence you cannot boot with Magisk to grant it root (or to ask a user for)
[Magisk] ipdev:
I was able to boot your patched image just fine.

I see it is patched with stable (23000).

Mine is patched with canary (23001).

The md5sum and sha256sum match when I patch with stable (23000).

md5sum: 7a4e96f106137b01ddd27ccb4f90cce9

sha256sum: 9119e7d501f8559fbb3ac67e4e16c2e5ca27371e84980da471582876b09c0cae

So the boot image/patching is not the issue. :)

So something is something messed up in /data/adb/ :(

Custom recovery to the rescue. :D​

If you have not already, just to be safe.

Backup what you want to save and store it off device.

Copy it to your computer, cloud storage, USB, ...​

---

I checked twrp-3.5.0-0-test8-redfin.img and it boots fine for me with the stock boot image installed.

Touch works so, no need to install a different kernel.

Download TWRP.

[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [REDFIN] [TESTING] - xdaThread - Link

With the stock boot image installed.

Since we have adb root in TWRP, we have access to /data/ :sneaky:

We have options since we can access data in TWRP.

Small Hammer

Boot into TWRP and delete magisk.db

fastboot boot twrp-3.5.0-0-test8-redfin.img
adb shell rm -rf /data/adb/magisk.db
adb reboot

Then do the steps to start in Safe mode.

Power button, hold power, select Safe mode and hold volume down during reboot.

Then fastboot boot Aquila magisk_patched-23000_59UWF.img and that should hopefully boot.

All modules will be disabled until you re-enable them.

Big Hammer

(Nuclear Option.) :p

Boot into TWRP.

Delete adb all together.

/data/adb will be recreated if needed.

fastboot boot twrp-3.5.0-0-test8-redfin.img
adb shell rm -rf /data/adb
adb reboot bootloader
fastboot boot Aquila magisk_patched-23000_59UWF.img

Cheers. :cowboy:
[Magisk] AquilaDroid:
You are incredible! Looks like I have a long night ahead of me...

What are the best back-up options? I'm primarily concerned with all the setup options (one of the most important is to backup Nova launcher settings, I guess). I routinely back up to Google, so are there any other things I'm missing. (I now owe you a keg (!) of beer...)
[Magisk] zgfg:
Isn't then easier for him:

- download Magisk v23 apk and rename to (exactly as that): uninstall.zip

- install/flash TWRP as you suggested

- have also the patched boot img flashed

- boot to TWRP and install uninstall.zip (from the first step)

After that, Magisk, its db and all modules will be removed, hence @AquilaDroid would just need to flash the patched img again and to configure his Magisk, modules, root grants, Magisk Hide settings, and voila

No need for adb, for backup and restore (no Factory reset or so)

PS: Even if manually deleting old Magisk (instead of simply flashing uninstall.zip):

- again, adb is not needed since TWRP must have Advanced, File Manager to delete stuff from /data/adb

- I would not delete just /data/adb/db (database) but the whole /data/adb folder (i.e., also all modules, scripts, everything)
[Magisk] ipdev:
Backup(s) are device/app specific.

Quite a few apps have an option to save/export settings.

I have not used Nova too much recently.

Nova had an option to export/import configuration/settings.

So you want to backup/save the exported settings file.

I use SMS Backup & Restore for Phone and Messages.

I store it locally and then pull the backup to my computer.

SMS Backup & Restore - PlayStore - Link​

Outside of exporting app settings and pulling them to my computer.

I generally dump /sdcard (adb pull /sdcard/) to my computer so I can pick though it.

Basically, a backup it is saving what can not be recreated. ;)

Cheers. :cowboy:
[Magisk] ipdev:
If you want to fully uninstall magisk, then maybe. ;)

I am still a little confused with Virtual A/B devices. 🙃

Since we are not installing TWRP and only booting it using adb..

It is easy to delete the files manually from command line.

I prefer using a real keyboard and monitor vs. the touch screen keyboard and small device screen. :p

I suggested deleting magisk.db (Small Hammer) to see if it was only something corrupt within Magisk's database.

By booting into Safe mode after deleting magisk.db, modules and boot scripts in post-sf-data or service should not run.

With access to /data/adb in TWRP, you could go though everything and figure out what is causing the problem.

The Big Hammer approach is a fast removal of everything Magisk.

Note: On Pixel 5 (SDK30) there is nothing else in /data/adb/ so it is safe to just delete the whole adb directory.

Cheers. :cowboy:
[Magisk] HA3APKA:
I can't update magisk, magisk 19.4, manager 7.3.4. Device Xiaomi Note 4x global. When i trying update i see "syntactic mistake". I has custom MIUI 11. All of this installed by master, but now this master is go out of my country. I want know how to update this, how to fix (it's important for me, and i can't find anything about this problem in Internet). Reply or quest more information from me on mail bogdazars@gmail.com or on this platform, i will cheking sometimes after post this (my first times using this platform and i'm not developer, sorry)
[Magisk] BillGoss:
You can read up on it here: https://source.android.com/devices/tech/ota/virtual_ab

It only applies to what used to be /system in "the good old days" 🙂
[Magisk] pndwal:
Well you do need later Magisk for Android 11...

I get this translation from your image using OCR:

"source: manager

at syntactic analis packet happened

mistake (malfunction)

When parsing a package, a

malfunction"

So appears to be simply a conflict updating app due to file signing etc. This may be resolved simply by unhiding / restoring Magisk Manager in settings.

However, 22.1 is NOT the latest Magisk in any case; Your old Magisk is pointing to latest json file in now archived repository for legacy builds:

https://github.com/topjohnwu/magisk_files

Current repo (for new single-package delivery builds) is:

https://github.com/topjohnwu/magisk-files

Caution: Before proceeding, disable ALL modules as some may be incompatible with later Magisk / Android 11

You could simply try updating App after unhiding / restoring current Manager.

Also, you probably have 22.1 App that failed to install in downloads, so you could try to install that after uninstalling current Manager (nb. settings / modules will be preserved) if update still fails after unhiding.

I'm guessing after update to 22.1, you will see 23.0 as latest public build App / Magisk as 22.1 build is duplicated in current archive. You should then be able to Update App again (to latest 23.0) and take Direct Install method to Update Magisk (mask) to 23.0 also.

If the above fails, try this (Nb. This should also work immediately):

- Uninstall current Manager

- Download latest Magisk 23.0 package from:

https://github.com/topjohnwu/Magisk#downloads

- Install apk.

- Open App and take Direct Install method to Update Magisk (mask) to 23.0 also.

🤠 PW
[Magisk] pndwal:
Thanks for clarification and efforts!...

I didn't distinguish boot from install clearly, but method makes perfect sense now. 👍

I think you've nailed it with TWRP & small hammer, BIG/nuclear hammer, ... Or even uninstall zip...

Hope so... if you like beer. 😜 PW
[Magisk] zgfg:
I'm also not familiar with A/B, that's why I suggested flashing uninstall.zip (believing, it knows better how to deal with properly)

Since he had bootloop even in Safe mode, I'm not sure if Magisk did it to disable modules - that's why @AquilaDroid should have now TWRP to inspect, and to put "disable" files if needed

Besides db (root apps granted and MagiskHide apps) and modules, there are folders post-fs-data.d and service.d with scripts to be executed on booting/initializing Magisk (hence, they can also account for bootloops!!!) and I'm not sure if (and by which mechanism) Magisk in Safe mode disables them for future (I don't want to test since Android Safe mode makes mess with at least widgets on home screens - one must set-up them once again)

Nevertheless, those scripts depend on what you install (modules should put their scripts into their respective folders), they're not device/ROM (like Pixel 5) specific.

E.g. root apps like Chainfire's Live Boot Log puts the same script 0000liveboot.sh to both folders (probably a redundancy and to catch up with diff ROMs and Magisk versions - timing of execution the scripts in one folder vs another is different).

Similarly the officialVanced YT root puts its mounting script to post-fs-data.sh, etc

PS: De gustibus non disputandum est (Latin) - our preferences are different. I prefer to not rev up the PC/laptop (e.g. for adb, fastboot), hence prefer to do as much as I can with MiXplorer and TWRP.

Similarly, I prefer to discuss here from XDA app (altough not perfect) while using PC and browser would be a way more comfortable.

Specially, I don't want to use the PC at work for those actions
[Magisk] AquilaDroid:
THANKS @zgfg, @ipdev & @pndwal and others!

I spent a couple hours last night (before collapsing!) on what I saw was the inevitable wipe data scenario. After reading your "overnight" comments, if I can gather my few remaining wits about me I'll have a go at the "small hammer" (TWRP) approach. Thanks to all for their patience - I'm sure that my "old age brain fog" is making this much more difficult that it really is!
[Magisk] AquilaDroid:
Just decided to try this, BOOTLOOPING after the following session! (What did I do wrong???)

C:\Users\aquil\Desktop\August Platform Tools\platform-tools>adb devices

adb server version (39) doesn't match this client (41); killing...

* daemon started successfully

List of devices attached

0B101FDD40001R device

(Put phone into fastboot mode manually)

C:\Users\aquil\Desktop\August Platform Tools\platform-tools>fastboot boot "C:\Users\aquil\Desktop\August Platform Tools\platform-tools\twrp-3.5.0-0-test8-redfin.img"

Sending 'boot.img' (98304 KB) OKAY [ 2.263s]

Booting (bootloader) boot.img missing cmdline or OS version

OKAY [ 2.567s]

Finished. Total time: 4.975s

C:\Users\aquil\Desktop\August Platform Tools\platform-tools>adb devices

adb server version (39) doesn't match this client (41); killing...

* daemon started successfully

List of devices attached

0B101FDD40001R recovery

C:\Users\aquil\Desktop\August Platform Tools\platform-tools>adb shell rm -rf /data/adb/magisk.db

C:\Users\aquil\Desktop\August Platform Tools\platform-tools>adb reboot

C:\Users\aquil\Desktop\August Platform Tools\platform-tools>fastboot (FLASH?) boot "C:\Users\aquil\Desktop\August Platform Tools\platform-tools\magisk_patched-23000_59UWF.img"

Sending 'boot.img' (98304 KB) OKAY [ 2.273s]

Booting (bootloader) boot.img missing cmdline or OS version

OKAY [ 1.709s]

Finished. Total time: 4.377s

What's the line:

Booting (bootloader) boot.img missing cmdline or OS version

I assume that the second flash (the magisk_patched.img) should be fastboot flash boot now that I've read up on the difference between fastboot boot and fastboot flash boot.

Trying again, stay tuned.
[Magisk] zgfg:
Why don't you install TWRP and do things easily through TWRP instead of having problems with adb
[Magisk] AquilaDroid:
Thanks (seriously!) for the great tutorial. It's been very annoying to me to have such clutter on the output, I'll fix that from now on if I ever flash anything again <G>! Actually it's only the 'eyesore" that's a problem as I drag and drop all the files into the command prompt window.

I've just tried the TWRP flash/etc that @ipdev suggested (a couple times), still no joy.
[Magisk] AquilaDroid:
Latest update: (Thanks @73sydney for waking me up to the mess I've been posting!)

Did the suggested series of TWRP flash, etc. (twice) and still in the same place. I'm overwhelmed by the support here, not sure I've tried everything that's been suggested. I have spent some time preparing (best I can) for the clean flash...

C:\platform-tools>adb reboot bootloader

adb server version (39) doesn't match this client (41); killing...

* daemon started successfully

C:\platform-tools>fastboot boot "C:\platform-tools\twrp-3.5.0-0-test8-redfin.img"

Sending 'boot.img' (98304 KB) OKAY [ 2.285s]

Booting (bootloader) boot.img missing cmdline or OS version I can't find any information when I google this (error?).

OKAY [ 2.320s]

Finished. Total time: 4.668s

C:\platform-tools>adb shell rm -rf /data/adb/magisk.db

adb server version (39) doesn't match this client (41); killing...

* daemon started successfully

C:\platform-tools>adb reboot

C:\platform-tools>fastboot flash boot "C:\platform-tools\magisk_patched-23000_59UWF.img"

Sending 'boot_b' (98304 KB) OKAY [ 2.317s]

Writing 'boot_b' OKAY [ 0.375s]

Finished. Total time: 3.692s

C:\platform-tools>fastboot reboot

Rebooting OKAY [ 0.047s]

Finished. Total time: 0.047s

C:\platform-tools> BOOTLOOPING

C:\platform-tools>fastboot devices

0B101FDD40001R fastboot

C:\platform-tools>fastboot flash boot "C:\platform-tools\image-redfin-rq3a.210805.001.a1\boot.img"

Sending 'boot_b' (98304 KB) OKAY [ 2.317s]

Writing 'boot_b' OKAY [ 0.375s]

Finished. Total time: 3.693s

C:\platform-tools>fastboot reboot

Rebooting OKAY [ 0.047s]

Finished. Total time: 0.047s BACK TO SAFETY