How To Root Android Using Magisk

[Lacy Tortelli]

Ihave tried the encryption setting, but it didn't (possibly) go well, as I ended up having short (possibly) 30 seconds soft restarts with my phone after the encryption process completes, and the only way to end this soft bootloop was to do one hard reboot. I also saw some missing apps (such as Maps) after the (faulty) encryption process. Furthermore, and this is the most important and annoying thing I found, is that once I set a password/pattern/pin after the encryption, and add the option to require it after booting, it will not be changed later, even if I changed it later on and added the same option of requiring it on reboot, the first would still persist.

I would like to know if there are steps (and possibly better ROM suggestions) that I could do to achieve full security using device encryption, while still benefiting from Magisk's systemless root that has the option of Magisk hide (using MagiskSu)?

I don't want to expose my data to thieves, as booting into recovery mode would show all my personal information as if I am running the device on root, and with that, you can easily wipe the lockscreen password by deleting the password database.

This was an old problem with Lineage OS based ROMS, where the encryption just didn't work properly. The problem is that ones the encryption is set, it cannot be changed in the GUI. However, I had a success in the past where I changed my encryption key through vdc cryptfs changepw command that can be run on the Terminal app from the developer menu (or any terminal emulator) with a required root access, and you can only change an old password to a new password, an old pattern to a new pattern, ...etc, but not a pattern to a password, ...etc.

I'd like to achieve that too. However, I keep running into issues. The problem I'm trying to solve now is that the expected mount points are not available after configuring a new connection. I can use rclone ls to list the contents of a server and that succeeds so I know the connection is working. But there are no mount points under any of these locations:

I have rclone-mount working on two different Android devices now. Both are rooted, of course, but one runs the stock Samsung firmware and the other runs LineageOS. The rclone Magisk module did not work correctly for me on either device. I used Termux:Boot to implement a nice automatic rclone-mount solution on my LineageOS device. On the other device, I had to implement my own simple script.

I would not say I have a final solution for using rclone-mount on Android, but at least I have something that is working for now. It works with both pCloud (suggesting it should work with any cloud storage) as well as my own SFTP server.

Great that I have finally found a person who is in the exact same situation as me. I too wonder the same. I am following the same procedure as everyone, but it doesn't work for me alone. It doesn't show me any error too, but the expected mount points are not available, although rclone ls lists the files on my remote server properly.

Hello, i'm having issue with running rclone mount on Android. Currently, i'm rooted with magisk and installed rclone mount via magisk's "module store". When i send the mount command to mount google drive, the first error is: "ERROR: error reading avalible plugins: Error creating: /.cache/rclone/webgui/plugins/config"

After a few seconds, another error appears: "Failed to save config after 10 tries: Failed to create temp file for new config: open /.rclone.conf094870642: read-only file system"

I tried to grat permissions to rclone via magisk's Mount Namespace Mode (i set it to global) but it didn't work. Also, i tried putting "su" before the command but when i click enter, nothing happened and just entered a new line for command entering. I copied the config from my PC (Windows 10) to Android because of faster setup.

With the rclone module by piyushgarg, the config gets read at install time. Copy your conf file to /sdcard/.rclone and reinstall the module. You don't need to run the mount command, your remotes should mount at /mnt/cloud immediately (or after a reboot)

I am using Fiddler, and I have to insert a CA Cert to decrypt the SSL certificate coming out of my device. My device running Android 13 is rooted, and when I installed my cert, it went into the user's section (as expected).

There are ways to get around this though - I've written a detail write-up of how Android HTTPS works generally and how to modify this using root here, and the details of some notable very recent related changes in Android 14 here.

If that doesn't work, check if you have a /apex/com.android.conscrypt/cacerts directory. If so, you have the Android 14 version of Conscrypt installed, and there's some extra steps. See the 2nd article above for full details, but in short: you need to use nsenter to add a bind mount for that /system/etc/security/cacerts path into the APEX path for every single running app process on the machine, including the Zygote/Zygote64 processes (which launch new processes in future, who will inherit this setting). That looks like this:

Alternatively, if that's too fiddly to do manually, you can use HTTP Toolkit which is a modern version of Fiddler I've built, that does HTTPS interception too but automates all the setup down to one click. That's all open-source, so if you want to see the full details of how this works so you can automate it yourself just follow the code from here.

The Pixel 3a came out of nowhere and flexed its muscles to show the industry that you can have a great phone without a hefty price tag. Since Pixel smartphones are first-party devices straight from Google, you can be sure you'll have root access one way or another. For right now the method used to get your Pixel 3a rooted will take a few steps, but they go by real quick.

Rooting your phone with Magisk opens up the world of mods like never before with a variety of benefits. One of the best things to come from Magisk is the ability to keep Google's SafetyNet flag from being tripped, which could stop you from using certain apps. With the platform continually evolving and getting better all the time, now's the perfect time to get started.

Of course, before you can get started with modding your Pixel 3a or rooting with Magisk, you'll need to unlock your bootloader. If you haven't done so yet, visit the guide below and get your bootloader taken care of before moving on with this guide.

There are two methods for rooting your Pixel 3a, and you can pick whichever one works better for you. The easiest and most beneficial of the two is done through the custom recovery environment via TWRP, which is the one most people will use for ease of access. The manual method is for when a device doesn't have TWRP support or for someone who prefers the old fashioned install process.

Using TWRP is the method that works best since it was created to make our lives easier in the first place by reducing the overall steps required for gaining root access. If you'd rather not waste any extra time with unnecessary manual steps, using a custom recovery to gain full root access is the way for you without a doubt. It doesn't get any easier than this!

Once your bootloader is unlocked, you need to grab the image file required to boot your Pixel 3a into TWRP. As mentioned previously, the benefits of installing Magisk on your system via TWRP provides the quickest route for gaining full root access. Having a custom recovery also means you can then install any ZIP file you want without having to rely on a computer when installed permanently.

The next thing you need to do is install the Magisk framework and the Magisk Manager app onto your system via a single ZIP file. This file will be installed within TWRP, and will patch your system to grant you full root access while passing Google's SafetyNet checks. Download the file below and place it in the "Download" folder on your phone's storage.

Now you need to boot your phone into Fastboot Mode so that you can access the TWRP recovery menu. There are other ways of booting into TWRP, but the universal method will always be to boot into your device's native Fastboot Mode via the power down method. If you're unfamiliar with the process or need a refresher, you can hit the link below and complete the step real quick before moving on.

Once you're in Fastboot Mode, navigate the menu with the up and down volume keys to make your selection. After you highlight "Recovery Mode" tap the power button to confirm the action. The device will immediately boot right into the TWRP main menu if all went well.

At this point, you should be sitting at the main screen of TWRP and ready to install Magisk onto your phone. From the main menu, tap "Install" then navigate to the "Download" folder where you stored the Magisk ZIP file. Once you have located the Magisk file, tap it once, then initiate the "Swipe to confirm Flash" slider to begin installing it.

The Magisk framework will automatically start doing its thing and will patch the boot image on your system partition. This means your phone will have full root access and still pass Google's SafetyNet, as mentioned previously. Once Magisk is finished installing on your system, tap the "Reboot System" option to boot back into Android.

Last but not least, after your phone reboots, head back into the Magisk Manager app. You'll want to then make sure you have both green check marks for "Latest Version" and "Installed Version." You'd also want to tap the arrow next to "Tap to start SafetyNet check" to ensure you pass Google's SafetyNet check. All set! Enjoy root access on your Pixel 3a.

Once you have your bootloader unlocked and ready to go, you'll then need to download the factory image for your specific device model. Head to a computer for this part to keep things simple. Click the download link below for the newest version for either your Pixel 3a or 3a XL. You'll have to scroll down past the flashing instructions section to find where the downloads section starts.

3a8082e126