yashsingh1/xdaforums huggingface dataset:
[Magisk] HippoMan:
I have a question about using Magisk with the crDroid ROM. I have already asked my question in crDroid XDA forum as well as in the crDroid TG group, but there have been no responses, so now I'm trying here, because this is a general Magisk support discussion group.

I want to install Magisk on a Pixel 7 Pro ("Cheetah") that is running the latest compatible crDroid version (A13 version). I know how to install crDroid itself on that device, and I am not asking about that here in this question. I know that such a crDroid Pixel 7 installation is an easy and straighforward process.

My question is specific to Magisk. Does anyone here have Magisk successfully running on a Pixel 7 Pro running the latest crDroid A13 version? If so, I'd like to know ...

... which version of Magisk were you successful with? "official"? "alpha"? "delta"?

... which release number of that particular Magisk version were you successful with?

... what detailed, specific installation steps were successful for you to get that particular release of that Magisk version properly installed on that device and that OS?

The reason that I'm asking is that I am not convinced yet that it's even possible to get Magisk running on the latest A13 crDroid version on a Pixel 7 Pro ("cheetah"). Therefore, if there isn't at least one person who can report that they have indeed performed this particular Magisk installation successfully, I don't want to spend the hundreds of dollars neecessary to purchase the Pixel 7 Pro in the first place.

And given that I haven't found a "cookbook-like" set of instructions for specifically installing a version of Magisk successfully on a crDroid A13 OS on a Pixel 7 Pro, I'd very much appreciate being pointed to a detailed set of instructions like that, if such instructions exist.

Thank you in advance for any thoughts and suggestions.
[Magisk] Wishmasterflo:
Better wait with trying to boot Orangefox on Pixel 7a for now. I guess I need to wait more until a useful release can be done so I have actually not really much hope right now that this Orangefox Version will actually boot now on the Pixel 7a.
[Magisk] HippoMan:
I never said that I believe that to be intentional.

It's just one of the unintended consequences of Google's continued "improvements" (ha ha!) of Android coupled with the increased usage by more and more developers of root-blocking and mod-blocking technologies.

Yes, Google is in business to make money with its advertising dissemination and with devices and OS's and services which facilitate that. They have a right to make money in this way and in countless other ways that they might choose. And developers have the right to choose how to make money with their own apps, as well.

It's just that Google's and many developers' Android-related products and services continue to grow increasingly unappealing to me.

I still find Android to be less onerous than iOS, but the undesirability gap between them continues to get narrower and narrower for me.
[Magisk] HippoMan:
Up until Android 11, none of these new innovations did much damage to our abilities to ...

(1) ... root our devices.

(2) ... mod our devices.

(3) ... perform full nandroid backups and restores.

But since A11, it has become much more complicated, confusing, and painful to perform items 1 and 2, and for developers of utilities like TWRP and OrangeFox to build software for performing item 3.

Of course, this pain and this confusion aren't things that Google planned or consciously intended to foist upon us. But also, they didn't make even a small effort to ameliorate this damage.

Google could have thrown us a bone (or better stated, tossed a bit of cheese to us mice) to offer us rooters and modders and nandroiders at least some relief from the pain that their recent "innovations" are causing us.

One example out of several: Google could have architected a way for full system backups and restores (like nandroid) to still be easily performed ... or perhaps they could even have provided an official Android utility for doing so.

But they obviously have no intention to provide anything like that to help us.

Again, I know this isn't any kind active action against rooters, modders, and nandroiders. It's simply benign neglect.

And I see no evidence that Google has any intention to stop instituting further innovations that will keep making things continually worse for us.

And I would love to be proven wrong about this.
[Magisk] EtoileLabrie:
Thank you for the reply.

I assumed since A11 the root is at 100 %

My aim was to remove things from /system and edit /etc/hosts. Let me explain, in another A11 device I did the following

(Hope I did not make a xy problem....)

adb shell su -c mount -o rw,remount /
adb shell su -c mount -o rw,remount /product
adb shell su -c rm -fr /system/system_ext/priv-app/DuraSpeed
adb shell su -c rm -fr /system/app/AudioRecorderStoneoim

Then I dumped the corresponding / partition

adb shell su -c dd if=/dev/block/dm-2 of=/storage/emulated/0/system-dm-2.img
adb pull /storage/emulated/0/system-dm-2.img ./
du -sk system-dm-2.img
# e2fsck -f P50-dm-2.img
# resize2fs P50-dm-2.img 1342320K

mount P50-dm-2.img /mnt/1
# now edit hosts file

apt-get install attr
ls -Z /mnt/1/system/etc/hosts
setfattr -n security.selinux -v u:object_r:system_file:s0 /mnt/1/system/etc/hosts
umount /mnt/1

# adb reboot bootloader
# fastboot reboot fastboot
# fastboot flash system P50-dm-2.img

This is what I am trying again to achieve. I also replace the dialer/music/messaging apps from AOSP and some of them need to be placed in /product or /system (like AOSPGallery)

- Secondly, after deleting things from /product like /maps/duo/crap I use fastbootd to flash the debloated-product.img. I usually flash the original (non-magisk) boot.img. This way even banking apps work well.
[Magisk] HippoMan:
Google has the right to make whatever enhancements they want to make. I'm just not happy with how some results of these enhancements affect the usability of Android in ways that are important to me.

Google is a producer and I'm a consumer. Their products and services are much less desirable to me nowadays than they used to be, and as a consumer, I wish I could take my business elsewhere. But their only meaningful competitor in the mobile-device/OS market is even worse, so for the time being, I just have to hold my nose and stick with Google.
[Magisk] sawdoctor:
Off topic but google does do some stupid things. They give us monet but cripple it, you can only theme icons on your homescreen not app drawer why? . Some google apps are themable but other hardcoded so you can't theme them why? Google roll out new features like call screening but only in America. Most of us wouldn't need root if google didn't intentionally cripple some of their features
[Magisk] pndwal:
Guess you mean GKI related changes?... Maybe more complicated, but more efficient also... Or maybe Dynamic partitions (within /super)?

No?... But they've provided pretty extensive details... eg GKI:

There's so much on this... Here's just Generic Boot info for A12/A13 that Magisk Devs needed to understand to inject init into generic ramdisk for A13 LV devices:

https://source.android.com/docs/core/architecture/partitions/generic-boot

Also many pages on Dynamic partitions:

Available from Android 10-

https://source.android.com/docs/core/ota/dynamic_partitions/implement

Wider takeup from Android 11-

https://source.android.com/docs/core/architecture/partitions#dynamic-partitions

... But they did no damage!... Just made better Android!

Sure it's more complex, but that's progress... Car modders now need specialist training to understand new component interactions too. 🙃

C'mon... Only the same pains as always...

Well they provide for data backup with caveats:

https://support.google.com/android/answer/2819582?hl=en#zippy=,what-gets-backed-up

Full nandroid backups are for modders... Are you saying they should be doing our modding for us?!

Poppycock... Google lets us mod (incl. root), even properly provides for that, but why should they provide modder's utilities?...

Fair suck of the sav...

Not sure why you would be contemplating getting the latest Pixel 7 Pro then...

... Maybe you should get one then. 🤪 PW
[Magisk] zgfg:
You can edit /etc/hosts by enabling Systemless Hosts in Magisk app settings, then reboot

After that you edit the file:

/data/adb/modules/hosts/system/etc/hosts

and Magisk will mount your edited file to /system/etc/hosts

---

You can edit on /vendor (similarly on /product) like James DSP does - install the module and inspect in:

/data/adb/modules/ainur_jamesdsp/system/vendor/

Similarly Viper4Android (since they both have to edit audio effects)

Or install

GitHub - Magisk-Modules-Alt-Repo/SystemlessDebloater: Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP

Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP - Magisk-Mo...

github.com

and check how the script:

/data/adb/modules/SystemlessDebloater/service.sh

debloates selected stock apps $MountApk

by replacing them with a $DummyApk:

mount -o bind $DummyApk $MountApk

---

And/or install modules for BusyBox or ToyBox and inspect how they add applets to /system/(x)bin (similarly like V4A and James DSP)

All that is based on Magisk that will mount the changes ON EVERY REBOOT

---

If too complicated (?) then install (if it would work on your ROM)

Releases · HuskyDG/magic_overlayfs

Make system partition become read-write (it is also possible without Magisk) - HuskyDG/magic_overlayfs

github.com

And with that module you can make changes on the System on the fly, through eg MiXPlorer or Terminal emulator

Magisk will DYNAMICALLY (immediately, without the need for rebooting) mount your changes

And/or inspect how that module internally works - more complicated 😁

---

All the above works for up to A13 (and I don't see why they wouldn't work on A14 but I had no chance to test)
[Magisk] HippoMan:
My latest message, above, contains this statement ...

The Pixel 5 device is on the road to deprecation, and also, my own Pixel 5 has some apparently unfixable issues. So, I would soon need to upgrade to *something* as I continue to hold my nose. Pixel 7 Pro is a possibility because crDroid supports it.

I'd go with an Xiaomi device instead, if it could run properly on 5G in the U.S. with T-Mobile, without my having to play with firmware hacks. But as far as I''ve been able to determine after investigation, no Xiaomi properly runs out of the box with U.S. T-Mobile 5G.
[Magisk] rodken:
+1

Or Verizon 5G Ultra Wideband or C-band spectrum for that matter.
[Magisk] HippoMan:
I found the answers to these questions.

See this post:

https://xdaforums.com/t/rom-13-cheetah-crdroid-9-8-official-19-08-2023.4604965/post-88994085
[Magisk] HippoMan:
Of course I'm not saying that. You seem to simply be agreeing with me that Google is exhibiting benign neglect towards modders.

And anyway, providing something nandroid-like would not be "doing our modding for us". It's merely a tool that modders (and also non-modders) could benefit from.

And please don't (mis-)interpret my previous paragraph as my saying anything like, "Google SHOULD be giving us something nandroid-like". It would simply be a "nice to have" which would make recent and future versions of Android less onerous to deal with.
[Magisk] lenoid:
Thanks guys, I got it working again with v26.1. Here is the way I went:

First, rooting on 2016 Sony devices is a bit more difficult when you want wo use a saved TA (Trim Area/DRM-Keys).

So I made a boot.img with Rootkernel and my TA and flashed it into boot partition. After that I flashed v26.1 zip via TWRP and at least after a small Direct Installation in Magisk app and a reboot, I got root again.

After that I flashed v26.3 via TWRP and root was gone again. Direct Install also wasn't possible anymore. Therefore I made the same procedure as before (flashing my boot.img and installation of 26.1 via TWRP) and everything works fine.

So I can confirm, that 26.3 is the problem. If you need information if this bug has been introduced with 26.2 or 26.3, please tell me and flash 26.2.

BTW: on my Galaxy Note 8.0 (GT-N5110) the last working Magisk (for LineageOS) is 24.1 I think.

So sadly new Magisk versions regularly break something.
[Magisk] zgfg:
But if you upgrade from v26.1 to v26.3 with Direct install (nit through TWRP) and before you un-check Recovery option (if it checks it automatically by default), I think it should work
[Magisk] portsample:
Hello

I am using a Sonim XP8 phone with a Qualcomm SDM630 chipset. Bootloader is A/B.

The bootloader is locked on these devices. However, I have been able to root Android 7.0 to 8.1 versions by using the Qualcomm emergency download (EDL) toolset to make a copy of boot image and then using Magisk to modify this image and then reloading the patched boot image on the device using EDL. Following this I have root. However, this does not work after Android 10. There is a vbmeta.img on the device. It is locked, so I am unable to "--disable-verity --disable-verification" per your instructions using fastboot. However, I can make a copy of this file, so if Magisk had the ability to --disable-verity and --disable-verification on vbmeta.img, I could build a patched vbmeta.img and possibly gain root control of these devices with the Android 10 OS.

Is this a possibility? Are there other ways to skin this cat?

Thanks in advance for reading this.
[Magisk] zgfg:
Yeah, Magisk v26301 is really wrong with my A only phone from 2019 or so

It's the phone where Magisk always used to display Ramdisk No (known case for a range of devices) but when patching, it properly unpacked boot.img, found and patched Ramdisk there, and repacked.

And after that, it displayed again Ramdisk No although it did patch to Ramdisk in Boot (and it did save the original boot.img for later Uninstallation purposes, hence it did have a mechanism to know that Ramdisk was found in Boot)

But now with Magisk v26.3 it went worse. On Direct Install, it automatically checks-in Recovery option - I don't oversee, so I manually uncheck and then it correctly patches to the Boot

And now also one more related issue. When I install any module and click to Reboot, Magisk v26.3 reboots to Recovery instead of to the System, thinking (again), I guess that it/Magisk has patched to Recovery and hence that it should better reboot to Recovery)

First I was afraid that it rebooted to Recovery due to a Bootloop, but there was no Bootloop and I tested more and found that it is now 'regular' behavior for Canary 26301 on my 'Ramdisk No' phone.

Even Reboot from the main Magisk window reboots to Recovery now instead of back to the System
[Magisk] lenoid:
I don't get this option. When I upgrade Magisk app from v26.1 to v26.3, I get these options:

After flashing boot.img and v26.1, I get this option for finalizing v26.1 installation (which works fine):
[Magisk] la_people:
Hi guys, I'm having a problem with last update, I already uninstall all and re install it. But still getting this when I try to enable"magisk Hide" . [IMG="ss"]http://i.imgur.com/wNgibvN.png[/IMG]
[Magisk] sk8lucas:
Hi, I have this error when I'm trying to use magisk hide on Nougat

** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

Preparing modules

Bind mount dummy system

Bind mount module items

Bind mount system mirror

Mount: /system

Bind mount mirror items

** Magisk late_start service mode running...

service: /magisk/phh/service.sh

phh: Live patching sepolicy

phh: Mounting supath

phh: Starting su daemon

** Removing tampered read-only system props

** Starting Magisk Hide

MagiskHide: Error occurred...

Thnx
[Magisk] jcrompton:
When this happens do you still have root?
[Magisk] SDMU:
Did you reboot after enabling magisk hide ?

Also what did you uninstall ?
[Magisk] fefuzzo:
thanks...there is a possibility to have systemless supersu for my device????
[Magisk] SilverSix:
I have to chime in on the no root issue. Updated from Magisk v6, phh 255, Magisk Manager 2.0 to v9, 266-2, and 2.5 respectively. I enabled hide before rebooting (idk why) and root has been gone ever since. I reflashed phh to no avail. I disabled magisk hide, mounted magisk on recovery, and deleted the enable file, and still no good. Upon every reboot Superuser tells me the binary is out of date and I have no root access.

No modules found on Magisk Manager but Systemless Xposed 86.6 is active.

Device: Samsung Galaxy S3 Virgin Mobile

ROM: Exodus 6.0 2016-10-08 nightly (Android 6.0.1)
[Magisk] SDMU:
Yes , you can flash these zips

http://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page1

in order to have magisk and then flash either phh's SuperUser or Chainfire's SuperSU :)

---------- Post added at 05:59 PM ---------- Previous post was at 05:56 PM ----------

I think it may have to do with magisk v9 deleting the cache modules
[Magisk] cohiba90:
Thanks but i made it again and i still have the same problem.
[Magisk] Nomelas:
Is magisk hide strictly for superuser and not compatible with superSU?
[Magisk] :
MagiskHide is for magisk and whatever other app you wish to hide through its interface.

Magisk works with both root options.

I had no problem with root when i tried both, but neither would pass SN.

Not to say it won't work for you because clearly some people have success. All you can do is try. But make sure you can pass SN without root first before installing anything is my suggestion.
[Magisk] Didgeridoohan:
Uhm... Yes it is. I'm gonna quote the man himself: "So in order to hide root (here I'm only referring Magisk phh superuser, as SuperSU users shall always rely on CF's suhide, not MagiskHide), I had to change the way things works."
[Magisk] ericotena:
[MENTION=1162986]Captain_Throwback[/MENTION] [MENTION=4470081]topjohnwu[/MENTION] It seems I can't flash the zip file. It says:

! Failed: Unable to extract zip file!

E: Error executing updater binary in zip '/external-sd/Download/Magisk-v9.zip'

Error flashing zip '/external-sd/Download/Magisk-v9.zip

I'v tried downloading the file again but same result.
[Magisk] arasky:
In recovery, Flash the magisk uninstaller, Flash Magisk V9, flash phh r266-2, reboot and you should be back to normal. That's exactly what I did when I was in your situation and root is back.
[Magisk] garthybarthy:
OK Sir..
[Magisk] westeight:
Magisk v9 works fine with SuperSu 2.78-SR3 and SuHide.
[Magisk] Captain_Throwback:
Recovery log?
[Magisk] android_htc:
Hi guys,

Installed Magisk v9, phh SU 266-2 Andersen latest version of magisk manager... but safety net check fails.

See log below:

** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

Preparing modules

Bind mount dummy system

Bind mount module items

Enabling systemless hosts file support

Mount: /magisk/.core/hosts

Enabling BusyBox

Mount: /magisk/.core/busybox

Bind mount system mirror

Mount: /system

Bind mount mirror items

** Magisk late_start service mode running...

service: /magisk/phh/service.sh

phh: Live patching sepolicy

phh: Mounting supath

phh: Starting su daemon

Any suggestions will be appreciated
[Magisk] Captain_Throwback:
Enable Magisk Hide.
[Magisk] :
Didn't see magiskhide in your log..

So go into magisk manager settings and check magiskhide and reboot.

Then look at the log again to see if it is listed and running.

Oops Cap got it.. :)
[Magisk] J.Michael:
Try following Select and Patch a File, that's the path I used, and I think it is past that point where I was offered a chance to "Check" the Recovery box.
[Magisk] J.Michael:
Samsung delivers a ROM as a set of "tar" files. When Magisk is asked to patch a "tar" file, at least for a Samsung ROM, it produces a new "tar" file in which it has patched boot, recovery, and vbmeta.

Maybe if you make a "tar" file containing your boot and vbmeta, then have Magisk patch the tar file, it will patch the vbmeta appropriately. (Extract files from the patched tar file and compare them to the originals.)
[Magisk] HippoMan:
Actually, full nandroid backups are quite helpful for non-modders, as well.

Consider the following ...

A typical non-modding Android user on a standard, factory, non-rooted ROM on a standard Android-approved device applies standard, approved OTA updates when they are offered.

But after one such OTA is successfully applied, the user then realizes that the system has been modified in one or more ways that he or she doesn't like, and the user therefore wants to roll back the OTA update.

If there was a utility which would have allowed the user to have taken a full nandroid-like backup right before initiating the OTA update, he or she could then easily and relatively quickly use that utility to restore the system back to the exact state it was in right before the OTA.

Again, I'm not saying that Google SHOULD offer a such nandroid-like backup/restore utility, but it certainly would be nice to have. And if such a standard Android utility was offered by Google, this would save countless person-hours of development efforts for the creation of numerous versions of TWRP and OrangeFox for all the various device/OS-version combinations out there.

But this is little more than a pipe dream, given that Google is extremely unlikely to ever offer such a thing.
[Magisk] pndwal:
Yup... Google don't want users to downgrade anyway; Updates generally bump security patches and fix vulns...

If warranted, bootloader updates may increment the anti-roll back version in bootloader and an attempt to revert to old OS may cause brick. See:

https://source.android.com/docs/security/features/verifiedboot

As I said, full nandroid backups are for modders... Maybe for developers... But I can't see that Google would want to open that can of worms for the general end user... 😬 PW
[Magisk] wittymav:
Greetings.

I need help. It seems rebooting my Samsung Galaxy A70 and Redmi Note 8 devices breaks the root because Magisk wouldn't load. However, if I reboot from within Magisk, everything works well. If I force a reboot using volume down and power button, it works well too. However, my volume down button is spoilt and I can't use that method when system UI freezes up, which it does so often.

So, how can I use ADB to trigger a reboot that matches cum emulates the reboot from Magisk, please? If there are other methods too, I'll be glad to know.

Thank you.
[Magisk] zgfg:
adb reboot

is the adb command to reboot. Which 'way' would it work on your phone (you say that various reboots work differently for you), you must try

There is no way from adb to force Reboot option from inside the Magisk app

You can also install some root apps that offer you menus to reboot (System, Recovery, Fastboot)

PS: Volume DOWN + Power should usually force reboot to Fastboot (?!)
[Magisk] J.Michael:
You've damaged the volume button on two phones?

What you describe sounds like on both devices you have Magisk installed in recovery.

Can you say whether Magisk was installed in recovery?

The original instructions stated that once Magisk was installed in recovery, in order to boot Android with Magisk active it would be necessary to boot using the button sequence that boots recovery, but release the buttons at just the right time to signal to Magisk that you did not really want to boot recovery.

On my Samsung tablet (SM-T290) it turned out that a complete shutdown followed by a normal boot (just holding the power button until the tablet responded) was enough to boot Android with Magisk active. I never heard an explanation of why it was so much easier than advertised, so I have no idea what subset of devices enjoy this convenience.

You might get the desired effect by booting to recovery from adb. I think I've seen the command "adb boot recovery", but I've never used it.

But really, if you consistently get Magisk active by doing a full shutdown followed by a power-on reboot, isn't that the simplest way?
[Magisk] wonkxin473:
updated Magisk 26.1 to 26.3 and now get bootloops with my Samsung Galaxy M51 SM-M515F. For Direct Install and Select and Patch a File (Odin)