Related
POST IS UPDATED REGULARLY.
LINK 1 - Parallel Space: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl&hl=en[/URL][/URL]
LINK 2 - Parallel Space 64-Bit Support: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl.arm64&hl=en[/URL][/URL]
Salutations. (That means 'Hello').
NOTE: For those who are interested, I will include background information about how I came to the solution. All that other jazz too. First and foremost however; the fix!
SOLUTION:
Right at the top of the post, you will find two links. This being a new account and all (don't ask), until I create 10 posts I cannot include any outside links. So once I've done so, I will update the post.
STEP **: So at the top of the post, there are clearly two links. 64-Bit Android devices are becoming increasingly common. This architecture may pose a few problems. give the application framework. Should you own a 64-Bit device, I recommend installing this application too (LINK 2). This will theoretically prevent any obstacles.
Pre-requisite(s): Make sure you have the 'Snapchat' application installed. It is recommended to have installed the latest update from the Google Play Store.
STEP ONE: Download the application appended to LINK 1. This is called Parallel Space. You might recognize the name (its creators are the same who allow you to seamlessly virtualize Windows OS on Mac OS).
STEP TWO: Launch the application.
STEP THREE: You should be prompted with a grid-like interface. Here you will be greeted with a range of familiar icons. In the top right corner of each icon, you will notice a blue check-mark. Make sure that there is one next to the 'Snapchat' icon. This will ensure that the app is 'cloned'.
STEP FOUR: In the 'Parallel Space' app, tap on the 'Snapchat' icon. This will launch the application.
STEP FIVE: From here it is pretty self-explanatory. You are greeted by the standard 'Snapchat' interface. Tap on 'Log In'. Then proceed to do so.
STEP SIX: 'Snapchat' should be functioning as normal.
STEP SEVEN (BONUS): During testing, this worked on and off. --
Remain logged-in to the 'cloned' 'Snapchat' application within the 'Parallel Space' application.
Then proceed to launch the stock 'Snapchat' application.
Next attempt to 'Log-In'.
Should this operation be successful, you are then free to uninstall 'Parallel Space' and any related assets from your device.
HOWEVER, I personally do not recommend this. When logging out or updating the 'Snapchat' application, errors may be re-encountered.
Instead, I recommend that if possible, do use the stock application, but leave 'Parallel Space' installed. Using the stock app will improve efficiency and reduce the load on system resources. But keeping the 'Parallel Space' application on the device, well; you get the point.
Enjoy the fix! If it does not work, please let me know [Device Name and Model No.]. I've tested on various devices, succeeded every-time. Do keep in mind that this is a loop-hole, so may be patched in future or not work at all for some devices.
Background (Because I know someone will ask): The idea came to mind while using a LG G5 as a daily driver. I had tested every custom ROM available for the device. The problem was that with custom ROM's, there was always an issue, Malfunctioning sensors, camera's not working persistently, etc , etc.
The G5's stock ROM left me wanting more. The overbearing interface made it a living hell. Plus, the device just being rooted (NO XPOSED) meant that 'Snapchat' did not work. I looked for fixes for a time, but could not find any.
Development of ROM's for the device is on-going, and I am an active member. But I just couldn't handle not being able to use the camera (one of the device's best features) and no accelerator, screen-rotation, etc. So I went back to stock again. Do keep in mind that I was alternating/dual-booting between custom and stock ROM's just because of the camera; mainly.
This most recent time. instead of flashing stock MM, I flashed stock N for the G5. For 850, it has been officially released in some countries, and a manual flash via TWRP was a peice of cake.
This update is a lot better. I am running Nova Launcher again. So it makes it look a little better. Themes have also been improved. I am using an in-built dark one which makes the device look a lot better aesthetically. Additionally, I'm rocking a white carbon-fibre skin on the exterior; improving grip and overall security. The only issue was again, no 'Snapchat'.
After a few days, I had the idea to attempt this. I tested my theory and it worked! That's it.
Please do keep in mind that I will update this post as often as possible.
P.S This was tested just after updating to the latest version of 'Snapchat' which was a significant update. It included Shazam, Groups, etc. So you know, pretty cool that it worked.
Did not work on Google Nexus 5 running Android 7.1.1. Still gives error message saying that I can't connect to the server.
Same here, not working on freshly reinstalled and rooted 7.1.1 Nexus 5x. No Xposed, no nothing. I get the infuriating "temporarily failed" message in both cloned and regular modes.
It didn't worked. S7 edge exynos (6.0.1)
Holyphe said:
It didn't worked. S7 edge exynos (6.0.1)
Click to expand...
Click to collapse
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
hot_potato said:
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
Click to expand...
Click to collapse
Whats the name of it?
Holyphe said:
Whats the name of it?
Click to expand...
Click to collapse
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
AndroidFL said:
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
Click to expand...
Click to collapse
That's the only solution I've seen working so far. unroot and reroot. Root cloak doesn't work, parallel doesn't work. I should've logged in before rooting and I hate to do it again.
Any work arounds yet? I've seen ppl do it using titanium backup but I'm not sure if that works. Can anybody help?
Samsung s5 G900v Not working
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Dukeboyty said:
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Click to expand...
Click to collapse
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Okay. I will try this on monday and will let youknow how it goes. Right now I decided to unroot to use snapchat, so I didn't loose my streaks. Thanks in advane will let you know how it goes.
immorality said:
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Click to expand...
Click to collapse
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Dukeboyty said:
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Click to expand...
Click to collapse
Snapchat detects xposed framework.
Though at a time they did do root they since moved to blocking xposed due to the security concerns with money and also privacy of the user.
Though with certain phones and ect that could be the case I am using a s5 and have no issues.
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
ahmedsasker said:
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
Click to expand...
Click to collapse
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Fnn.09 said:
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Click to expand...
Click to collapse
make a nandroid backup if u want
1- full unroot by opening supersu and going to settings and press Full unroot and wait till it finishes and restart
2- download xposed uninstaller if u have xposed framework installed and flash it
3- install magisk manager from playstore
4- download and flash last magisk which is (12v) now from : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
5- flash magisk v12.0 which you downloaded now your phone will have systemless root
6- go into magisk manager app and go to settings and toggle "Magisk Hide" (ON) and restart now your root is hidden
7- remove your current xposed app and install this one : https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
8- flash systemless xposed : https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
9- reboot and go to the xposed installer app and toggle the xposed off or on as you want when u restart it won't take time optimizing apps like before so fast now
your root is hidden now but xposed is not but you can disable it and enable it easily
Instead of using Parallel Space (which I believe to be insecure) use Island to clone your apps. It's a little more advanced to setup, but it's a lot more secure. It works for rooted and non-rooted devices. On the 1st page of the thread, it explains how Parallel Space and others repack the apk file locally, which is dangerous. https://forum.xda-developers.com/android/apps-games/closed-beta-test-incoming-companion-app-t3366295
Island never repack apk file locally, which is inherently insecure for users, since all your app data (including password input) are technically in the hand of MoboClean. (The same applies to other similar tools, e.g. LBE Parallel Space)
Instead, Island takes advantage of the underlying mechanism used by "Android for Work". This ensures that all your apps run natively in Android system and their data are securely stored in internal location of Android which is never accessible by Island. It has the same level of security as "Android for Work".
Click to expand...
Click to collapse
Be sure to read the disclaimer!!! The app is still only available in closed beta at the time of writing this, and could possibly cause you're device to bootloop or even possibly brick it, but root, xposed, or other modifications {in my opinion) has a higher chance of bootloops or bricking your device.
You follow the same steps in island to clone snapchat as you would in Parallel Space to login to snapchat. It might be possible to use the play store inside island to download snapchat inside island and login that way. I can't remember exactly how it works. I believe that island is a good way to test apps in a "sandbox environment" to keep the data excluded, safe and secure from the regular apps that you have installed outside of island.
I use Magisk now which bypasses SafetyNet which is what snapchat uses to "block access" to modified/rooted devices.
Probably the easiest method is to download Casper which is an alternative snapchat client that allows you to save snaps, and many other features that the official snapchat client can't do. Find Casper at www.casper.io
FYI Netflix has started to change how they do things as well by hiding the app's play store page from devices that have been modified or rooted, but it's still possible to simply sideload Netflix for now.
THIS PROJECT IS NO LONGER SUPPORTED.
# Magisk Manager for Recovery Mode (mm)
## LEGAL
Copyright (C) 2017-2019, VR25 @ xda-developers
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
## DISCLAIMER
Always read/reread this reference prior to installing/upgrading this software.
While no cats have been harmed, the author assumes no responsibility for anything that might break due to the use/misuse of it.
To prevent fraud, do NOT mirror any link associated with this project; do NOT share builds (zips)! Share official links instead.
## DESCRIPTION
- Manage your Magisk modules from recovery (e.g., TWRP) -- run "sh /sdcard/mm" on recovery terminal.
Features list
- Automatically fix magisk.img (e2fsck -fy)
- List installed modules
- Toggle
- Core only mode
- Magic mount
- Disable
- Remove
## PREREQUISITE
- Magisk 17-19
## SETUP
- Install
1. Flash live (e.g., from Magisk Manager) or from custom recovery (e.g., TWRP).
- Uninstall
- Use Magisk Manager app or mm itself (supports `uninstall.sh`, too).
## USAGE
- First time (right after installing/updating) - run `mm` or `sh /sdcard/mm` on recovery terminal.
- Next times (while in recovery) - no need to re-flash the zip; simply run `sh /sdcard/mm` on recovery terminal.
- Follow the instructions/wizard. Everything is interactive.
- Pro tip: lazy people can try running `*/mm` instead of `sh /sdcard/mm`.
## LINKS
- [Donate](https://paypal.me/vr25xda/)
- [Facebook page](https://facebook.com/VR25-at-xda-developers-258150974794782/)
- [Git repository](https://github.com/Magisk-Modules-Repo/mm)
- [Telegram channel](https://t.me/vr25_xda/)
- [Telegram profile](https://t.me/vr25xda/)
- [XDA thread](https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165)
## LATEST CHANGES
**2019.4.4 (201904040)**
- Complete redesign
- Magisk 17-19 support (including `uninstall.sh`)
- Toggle core only mode
- Updated information (copyright, documentation, and module description)
**2018.8.1 (201808010)**
- General optimizations
- New & simplified installer
- Striped down (removed unnecessary code & files)
- Updated documentation
**2018.7.24 (201807240)**
- Fixed modPath detection issue (Magisk 16.6).
- Updated documentation
Archive
Hey not sure whether this is right thread to ask, if not please redirect me.
I'm on AOKP, banking apps are detecting root and not allowing to access it, so I was asked to use Magisk.
Can you tell me how do I install it? Can I just download Magisk Manager and Magisk flash it via twrp? I'm noob to all rooting man
BackToAndroid said:
Hey not sure whether this is right thread to ask, if not please redirect me.
I'm on AOKP, banking apps are detecting root and not allowing to access it, so I was asked to use Magisk.
Can you tell me how do I install it? Can I just download Magisk Manager and Magisk flash it via twrp? I'm noob to all rooting man
Click to expand...
Click to collapse
Yeah... You took a serious wrong turn.
Start by reading these threads:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
And if you need help, post here (with lots of details):
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
Sorry, maybe for my language, but I can not understand what this module is doing.
Enviado desde mi MI 5s Plus mediante Tapatalk
Hi,
Great idea! I'll check and comment. :good:
Please, add it to the official repository.
It includes one option to enable/disable Magisk Core Mode Only?
And one suggestion: provide a ZIP file for launch directly the "mm" command without opening the Terminal (or use Aroma Installer).
Nitram08 said:
Sorry, maybe for my language, but I can not understand what this module is doing.
Enviado desde mi MI 5s Plus mediante Tapatalk
Click to expand...
Click to collapse
You should at least have basic understanding of what Magisk is and how it operates before jumping onto this thread. If you don't know what I mean by "Magisk Manager for Recovery Mode," then you've been skipping steps. I can't help you before you help yourself.
manos78 said:
Hi,
Great idea! I'll check and comment. :good:
Please, add it to the official repository.
It includes one option to enable/disable Magisk Core Mode Only?
And one suggestion: provide a ZIP file for launch directly the "mm" command without opening the Terminal (or use Aroma Installer).
Click to expand...
Click to collapse
Currently limited to the features listed. New capabilities will be added over time. The ability to manage Magisk settings is already in the works. Repo submission status -- awaiting approval.
Firstly, thank you. I've used another mod that allows using terminal to get rid of modules but it's not as fluid in usage as this one. However, i have one question; While i was able to use it in recovery, I'm not sure I understand clearly about whether or not this can be used while the system is fully loaded. I tried accessing the app through the os terminal but it acts as if I'm entering the wrong command. In twrp i did as you said and typed "mm" and it pulled right up. Yet, when i try the instructions that follow afterward to access the module while in the os, it tells me it can't be found. Am i missing something or is this only available through recovery?
dodgyme said:
Firstly, thank you. I've used another mod that allows using terminal to get rid of modules but it's not as fluid in usage as this one. However, i have one question; While i was able to use it in recovery, I'm not sure I understand clearly about whether or not this can be used while the system is fully loaded. I tried accessing the app through the os terminal but it acts as if I'm entering the wrong command. In twrp i did as you said and typed "mm" and it pulled right up. Yet, when i try the instructions that follow afterward to access the module while in the os, it tells me it can't be found. Am i missing something or is this only available through recovery?
Click to expand...
Click to collapse
The "module" part is only meant for updating the tool through Magisk Manager.
So, you don't have to constantly check XDA/GitHub for newer versions.
@Nitram08, if that's what you meant, sorry about the first answer! Next time, PLEASE give more detail, or you might get very similar reactions.
A basic rule of thumb:
- Poor info = "nothing happened -- bad post".
Hmmmmm
So, just to clarify, it can only be used in twrp? If not, what's the exact command to use when I'm actually in the Android system using whatever terminal app I might be using...???
I ask because this part of your instructions confuses me:
"Else (after installing & rebooting) -- run `. /data/magisk/mm`."
My understanding suggests I can use it while in the actual system but when I use my terminal app it tells me it's not found...
dodgyme said:
So, just to clarify, it can only be used in twrp? If not, what's the exact command to use when I'm actually in the Android system using whatever terminal app I might be using...???
I ask because this part of your instructions confuses me:
"Else (after installing & rebooting) -- run `. /data/magisk/mm`."
My understanding suggests I can use it while in the actual system but when I use my terminal app it tells me it's not found...
Click to expand...
Click to collapse
Yeah... that line should be "after installing & rebooting into recovery". So, this is built for use in recovery mode only.
Instead of re-flashing every single time you need it, you simply run ". /data/magisk/mm" That is "dot space /magisk/mm".
In short
- First time (right after installing/updating) -- run "mm" (on recovery terminal)
- Next times (while in recovery) -- no need to re-flash the zip; simply run ". /data/magisk/mm" on terminal.
VR25 said:
Yeah... that line should be "after installing & rebooting into recovery". So, this is built for use in recovery mode only.
Instead of re-flashing every single time you need it, you simply run ". /data/magisk/mm" That is "dot space /magisk/mm".
In short
- First time (right after installing/updating) -- run "mm" (on recovery terminal)
- Next times (while in recovery) -- no need to re-flash the zip; simply run ". /magisk/mm" on terminal.
Click to expand...
Click to collapse
Understood, I appreciate your feedback and this little gem greatly. Thank you!
Type wrong, please ignore
I just want to thank Op for this. I can't tell you how many times I have gotten a bootloop from a faulty module making me have to delete magisk.img (always trying new things ). This makes it so much easier. Thanks much OP.
Thanks a bunch OP. This will be a life saver for those who don't take TWRP backups in TWRP before flashing a module, including me.
Sent from my Honor 8 Pro using XDA Labs
Magisk log: "e 432:569 sendfile failed with 2: No such file or directory"
Any Modules can not find after install this
New modules installs but not works and not shows on list of android magisk manager.
Very Poor soft! Need to repair system after that!
Unistall_magisk.zip not repair this error!
I lost my system???
Android AOSP (Aex) latest 7.1.2
Xiaomi redmi 4x
Amazing module, allows me to manage magisk in TWRP without issue. This is an essential module for every magisk user - if you can't boot after a module install, you can just remove the module and not worry about restoring a backup.
As an aside, also always have the Magisk uninstaller zip handy, it'll save your ass when your phone / tablet goes to **** when you're flashing modules like a meth addict.
Great module, but I found something weird on my phone...
Is there any reason why a removed/disabled moduled would appear as such in the current TWRP session or just after rebooting from TWRP to recovery, but reappear after powering off and then booting to recovery via bootloader?
This (strange) thing happened to me minutes ago and the only way to remove the module (and boot Android again) was uninstalling and then reinstalling Magisk...
Disable modules
I'm trying to disable a module but I don't entirely understand the commands. I start Magisk Manager and select "e" to enable/disable modules. Then it shows:
<Toggle Module ON/OFF>
Greenify4Magisk (ON)
aik-mobile (ON)
mm (ON)
Input a matching WORD/string at once
- Press RETURN when done (or to cancel)
-- CTRL+C to exit
What command do I have to use to disable Greenify4Magisk?
iqubik said:
Magisk log: "e 432:569 sendfile failed with 2: No such file or directory"
Any Modules can not find after install this
New modules installs but not works and not shows on list of android magisk manager.
Very Poor soft! Need to repair system after that!
Unistall_magisk.zip not repair this error!
I lost my system???
Android AOSP (Aex) latest 7.1.2
Xiaomi redmi 4x
Click to expand...
Click to collapse
Really good way of providing "useful" information...
You're dealing with different issues not related to this module in the first place. Could you describe exactly what you did and what actually happened afterwards?
njascgil said:
Great module, but I found something weird on my phone...
Is there any reason why a removed/disabled moduled would appear as such in the current TWRP session or just after rebooting from TWRP to recovery, but reappear after powering off and then booting to recovery via bootloader?
This (strange) thing happened to me minutes ago and the only way to remove the module (and boot Android again) was uninstalling and then reinstalling Magisk...
Click to expand...
Click to collapse
Odd...
Could you describe in details what you did to remove/disable the module in question?
beavis5706 said:
I'm trying to disable a module but I don't entirely understand the commands. I start Magisk Manager and select "e" to enable/disable modules. Then it shows:
<Toggle Module ON/OFF>
Greenify4Magisk (ON)
aik-mobile (ON)
mm (ON)
Input a matching WORD/string at once
- Press RETURN when done (or to cancel)
-- CTRL+C to exit
What command do I have to use to disable Greenify4Magisk?
Click to expand...
Click to collapse
You simply type a "matching WORD/string" and press ENTER. For example, to disable Greenify4Magisk, I would input "Green" or "4" or "Magisk" (whatever is unique to Greenify4Magisk).
I have two G9+ phones, both rooted with Adaway installed. One has the stock ROM (Android 10) & the other has LineageOS 18.1.
On the phone with Lineage there are no ads when running a particular game. The same version of the game on Moto Android 10 has ads.
There is some app I don't understand called Moto GameTime that appeared when I started the game but I have disabled it. (I tried to move GameTime out of system using system/app mover but I got an error: "Could not remount /system".)
Still, Google ads appear with the stock ROM despite having Adaway.
Everything looked ok in Adaway. It tells me its three sources are up to date. When I try to reload & reinstall hosts from those sources I get an error: "Unable to copy hosts file to /system partition. Please check Magisk systemless module is enabled the reboot." (Magisk Manager shows Magisk 23.0 is installed.)
Something is causing problems that seem to involve lack of access to the /system partition. I don't know if that is related to the appearance of ads on the stock ROM, but any thoughts? How can I fix this?
As I've stimulated no response here, I took the ugly step of wiping the phone, flashing the experimental LineageOS and restoring everything from backup (not a fully successful process because the data for certain apps was not backed up by Super Backup & Restore).
At least there are now no ads getting through onto the phone.
The issue you are having is related to stock Android 10. It does not allow you to make any changes to the system partition, as it won't allow you to mount it as r/w. There is a workaround for it (currently in development stages). It's a flash able zip script that dumps the super partition "fixes" it and flashes it back. Your phone must have the bootloader unlocked and be rooted for it to work. It currently works for A only devices without any issues, but is throwing an lpmake error 73 for mysterious/unknown reasons, but a fix is in the works. I will post a link when I get home.
I assume the phone is rooted with Magisk which is a systemless root method. Even with older devices /system remains unmodified. All changes are only overlays/modules managed by the Magisk App.
doktorspin said:
(I tried to move GameTime out of system using system/app mover but I got an error: "Could not remount /system".)
Click to expand...
Click to collapse
This could also be done with a own module. See instructions here.
Keven11 said:
The issue you are having is related to stock Android 10. It does not allow you to make any changes to the system partition, as it won't allow you to mount it as r/w.
Click to expand...
Click to collapse
Thanks. I decided to replace the stock ROM with LOS18.1. That problem solved. (Got a new one: can't use data over the phone connection.)
doktorspin said:
Thanks. I decided to replace the stock ROM with LOS18.1. That problem solved. (Got a new one: can't use data over the phone connection.)
Click to expand...
Click to collapse
I fixed the issue by ditching Android 10 for LOS 18.1. But thanks for the pointer.
doktorspin said:
Thanks. I decided to replace the stock ROM with LOS18.1. That problem solved. (Got a new one: can't use data over the phone connection.)
Click to expand...
Click to collapse
I'm glad you got it figured out. The data issue, along with many other bugs will be rectified any day now with the new release. The issue you are having with LOS 18.1 is because at the time of development the kernel for A11 hadn't been released by Moto yet. However, they did finally release it a little under 2 weeks ago. So the new version of it will be much much better. It will be linked to the same link I posted. It's just a matter of time now, and not much of it.
Telegram Odessa Devs and testers group: https://t.me/joinchat/SaZ2BX0M8bQmkioW
Hey everyone,
after some trial and error, I was able to pass Safety Net.
I just want to mention what I did in the process to get there. May have been a combination of things or just one...
1. I followed this guide, but make sure you notice that It's for the Pixel 5 not 5a. But the process is similar. This process didn't fix the issue. However, it's also a good how-to on how to root. I did also modify the props to the 3a.
How to Root the Pixel 5 & Still Pass SafetyNet — Full Guide for Beginners & Intermediate Users
The Pixel 5 is a great value proposition in this era of $1,500 phones. With its reasonable price tag, fully open-sourced software, and unlockable bootloader, it's also an ideal phone for rooting.
android.gadgethacks.com
2. When that didn't work, I followed this video, and hid all my banking apps besides the Google Play Services:
3. When that didn't work, I installed these both using Magisk from this post:
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
4. Cleared my data and cache with Google Play and GPay + any other banking apps.
That worked for me!
EDIT: IF GOOGLE MAPS reports the wrong location, its likely XPrivacy-LUA, Google Services. Uncheck some of them.
Oh man....the only thing holding me back is the safety net thing, and it looks like we have a work around tell someone has an actual method made for this phone. Not sure if I'm ready to actually mess with this yet...but thanks for the post, bro!
anubis2k3 said:
Oh man....the only thing holding me back is the safety net thing, and it looks like we have a work around tell someone has an actual method made for this phone. Not sure if I'm ready to actually mess with this yet...but thanks for the post, bro!
Click to expand...
Click to collapse
Didnt think it was that big of a deal to me. But it was fun with a new phone with nothing on it.
This was the Magisk module that worked to pass safety net for me. I didn't need any others.
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Google Pay "appears" to be working too. Haven't gone out and tried it yet though.
joemommasfat said:
Google Pay "appears" to be working too. Haven't gone out and tried it yet though.
Click to expand...
Click to collapse
That's the part that I use the most, and the reason I haven't rooted yet. Please let us know if it works. Much appreciated!
I can confirm that using google pay (newer GPay app) on my rooted 5a works at merchants. I've already used it several times over the last week or so with no problems.
Deadmau-five said:
3. When that didn't work, I installed these both using Magisk from this post:
Click to expand...
Click to collapse
Why? Isn't the shim version just for Samsungs? Either way, it's the same mod, just different versions.
Someone who actually knows what they're doing needs to write up a tutorial. Following instructions posted by people who have no idea what they're doing but "it works" for them is dangerous.
borxnx said:
Why? Isn't the shim version just for Samsungs? Either way, it's the same mod, just different versions.
Someone who actually knows what they're doing needs to write up a tutorial. Following instructions posted by people who have no idea what they're doing but "it works" for them is dangerous.
Click to expand...
Click to collapse
You're absolutely correct about the dangers in following instructions posted by who knows who. I'll go further and say when it comes to root and associated items stay away from anything posted on a site other than XDA. In many cases even if the instructions were correct at some point in time they may well be outdated now.
I haven't rooted yet for a few reasons yet but will, hopefully sometime very soon. In the meantime I can state the following:
They're is no need to modify props. Modifying props to identify as a different phone would only be required for custom ROMs that don't handle it themselves (or some non-certified Chinese phones, which doesn't apply here). If you're running stock just leave that portion alone. And, if I'm not mistaken (although not 100% certain) I think safetynet-fix takes care of that for you in any case.
You will definitely need kdragOn/safetynet-fix.
Hopefully that's all you need.
I'm not sure which version of Magisk you'll need. Unless you know what you're doing and how to get out of trouble I recommend staying away from the current alphas, they're extremely cutting edge and you can expect problems.
Best best is to check the following threads and see what's going on:
Actually see this post and the 2 posts immediately following
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
That should pretty much cover things for the moment. If nobody else (@hfam ?) has done it by the time I get around to rooting I'll write something up specific for the 5a.
I only mentioned what works for me since there was no step-by-step guide.
Dangerous how? Doing any mods to your phone is "dangerous". I fail to see how this is more so than others. Modifying your phone is risky.
If it didn't work I wouldn't have posted this guide. I only mentioned the steps that I took. It's not really a guide, just how I passed safety net.
But, my 5a has still been working great since then. GPay included.
jcmm11 said:
You're absolutely correct about the dangers in following instructions posted by who knows who. I'll go further and say when it comes to root and associated items stay away from anything posted on a site other than XDA. In many cases even if the instructions were correct at some point in time they may well be outdated now.
I haven't rooted yet for a few reasons yet but will, hopefully sometime very soon. In the meantime I can state the following:
They're is no need to modify props. Modifying props to identify as a different phone would only be required for custom ROMs that don't handle it themselves (or some non-certified Chinese phones, which doesn't apply here). If you're running stock just leave that portion alone. And, if I'm not mistaken (although not 100% certain) I think safetynet-fix takes care of that for you in any case.
You will definitely need kdragOn/safetynet-fix.
Hopefully that's all you need.
I'm not sure which version of Magisk you'll need. Unless you know what you're doing and how to get out of trouble I recommend staying away from the current alphas, they're extremely cutting edge and you can expect problems.
Best best is to check the following threads and see what's going on:
Actually see this post and the 2 posts immediately following
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
That should pretty much cover things for the moment. If nobody else (@hfam ?) has done it by the time I get around to rooting I'll write something up specific for the 5a.
Click to expand...
Click to collapse
Just a quick note to say I just finished with everything (new Pixel 5a 5G, rooted + Safety net, restored all my apps, etc) and it's a flawless victory, ALL banking apps work great, SafetyNet passes, no hiccups.
I'd be happy to craft up a step by step and post it if there's some interest. It's not often I get to give back to this outstanding community, so it's the least I can do jumping on the opportunity. UFC 266 Main card is just starting, so I'll get started right after the fight and post it here in this thread.
Great to see ya again @jcmm11! Coming back to root a new phone feels like a family reunion, so great to see many of you active folks still here helping out!!
hfam
Alright, as promised, here is my writeup for a step-by-step tutorial for rooting your new Pixel 5a and getting SafetyNet up and going. I know it looks like a book, but I wanted to put it into plain language and attempt to explain the process for everyone, even absolute first timers. I know when I first started I really appreciated when the person helping didn't presume I had any knowledge, so for those that may have some experience, sorry for the wordiness. I'll also include how I apply updates when a new Android security update is pushed out. I understand that there are now elegant ways to accept OTA updates, but that is out of the scope of this tutorial as I have always had issues with OTA, and have to catch up on how that works myself. I can attest to years of using this method though (using a full factory image) to perform the "monthly" security updates, and I have never had anything but full success, so I'll share that here below the rooting tutorial.
*Disclaimer and heads-up* this is for an UNLOCKED PIxel 5a purchased directly from Google Store. At the time of this writing that is the only place I'm aware of which currently offers the PIxel 5a. Once carriers like Verizon, etc, offer this device, there may be some changes to the process, so just know up front this is for the unlocked Pixel 5a*
*WARNING*! When you unlock the bootloader on your phone it WILL WIPE YOUR PHONE and reset it to factory. If you've already used your phone and set it up, you're going to lose that setup. If you can't bear it, then the rest of this isn't for you, as root cannot be achieved without unlocking the bootloader.
First, you'll need a few things
- https://developers.google.com/android/images
and download the latest FACTORY IMAGE for "barbet", which is the Pixel 5a. You want to download the SAME VERSION that is currently installed on your device. At the time of this writing, it's the September release.
From that same page, you will need the ADB+Fastboot platform tools which will allow you to perform the required tasks, download from this link:
- https://developer.android.com/studio/releases/platform-tools.html
I use Windows 10, and extract this tools download to a folder in the root of C: called "platform-tools". You will then need to add "c:\platform-tools" to your environment path.
On the Pixel 5a, you need to enable developer options. Go into Settings/About Phone/and tap "Build Number" 7 times. This enables developer options and it will let you know when you've unlocked this as you tap 7 times. Once developer options is unlocked, go back to Settings/System/Advanced, and you'll see Developer Options is now available.
Select Developer Options, and enable "USB Debugging" and also enable "OEM Unlocking".
(**NOTE** For now at least, until you decide how you want to proceed with handling updates in future (more on that later), I strongly recommend turning OFF "Automatic System Updates" as well, just a few items below "OEM Unlocking". This prevents any updates happening automatically on a phone reboot. You don't want to wake up and find an OTA update pushed out and removed root, or worse. You can always turn it back on later.)
Plug your phone into a USB port on your PC. Allow the PC to do it's thing. You can open up Computer Management on the PC (right click the windows menu button icon lower left of your toolbar and select "Computer Management". Select "Device Manager" on the left panel. You should see "Android ADB Device" appear at the top of the right pane list of devices. if not, then visit:
Install OEM USB drivers | Android Studio | Android Developers
Discover links to the web sites for several original equipment manufacturers (OEMs), where you can download the appropriate USB driver for your device.
developer.android.com
and download the appropriate USB driver for your system and retry the above directions.
First thing we have to do is unlock the bootloader.
On the PC, open a command prompt and change directory to "C:\platform-tools" as discussed above.
Now, type in "adb reboot bootloader". The phone will reboot into bootloader. (you may receive a dialog on the phone which says something to the effect of not recognizing the PC. Go ahead and allow it, check the box to allow it in the future, and proceed.
Phone is now at the bootloader, and shows you some info letting you know it's so, including that the bootloader is locked. Also, look at the Device Manager we opened earlier and confirm that you see Android ADB Device (or similar) which confirms your PC recognizes the phone and setup for ADB commands .
To unlock the bootloader, in the command prompt type:
fastboot flashing unlock
This will unlock the bootloader, you will likely see a warning that it's going to wipe the phone. Proceed and allow the unlock. The phone will then reboot and take you to your wiped phone just as you received it out of the box, except the bootloader is now unlocked and Developer Options are still available. Let the phone continue through it's first-time setup, and leave the phone plugged into the PC. If you unplugged no biggie, but we're going right back to the PC shortly and it will need to be plugged back in before the next step to accept the file we're going to push to it.
Now, you want to open a browser on the phone and go to (at the time of this writing, v23.0 is the current stable Magisk):
Release Magisk v23.0 · topjohnwu/Magisk
This release is focused on fixing regressions and bugs. Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 only supports Android 5.0 and higher. Bug Fixes [App]...
github.com
Scroll down and under "Assets" select that Magisk 23.apk file, download and install it. Open Magisk if it doesn't open on install, and just let it sit, we're coming back to it shortly.
PATCHING THE BOOT.IMG FILE
On the PC, go back to the Factory Image you downloaded, and extract it to a temporary directory. You will see 6 files; a few "flash-all" files, a radio image, a bootloader image, and a ZIP file called "image-barbet-XXXXXXXXXXX.zip (the xxx's are whatever the version number is you've downloaded). Double click that ZIP file and you will see a dozen files. The one we need to root the device is "boot.img".
Copy (don't move!!) this file to c:\platform-tools. Now, go back to your command prompt (still pointing to c:\platform-tools) and type in:
adb push boot.img /sdcard/Download
Now back on the phone, within the Magisk app we left open, at the top where it says Magisk, choose to install. A dialog box will open, select Patch Boot File Image. Point the process to your /sdcard/Download, and select the boot.img file we just pushed there. Now allow it to patch the boot.img and Magisk will show you it's patching it, and in a moment tell you it was successful. Close the Magisk app, open "Files" and direct it to sdcard/Download. Note the name of the patched boot file, which is called "magisk_patched-XXXXX_xxxxx.img (the X's are the Magisk version, and the x's are 5 random chars). Feel free to leave it there as you go back to the PC...
Back on the PC, in the command prompt, now type:
adb pull /sdcard/Download/magisk_patched-XXXXX_xxxxx.img
make certain you get the name exact or it won't go, no worries, just get it correct. The file now resides in the "c:\platform-tools" directory along with the unpatched "boot.img" and your ADB+Fastboot tools.
Just about done rooting, here we go!
Now, in the command prompt type:
adb reboot bootloader
The phone reboots into bootloader. Now type:
fastboot flash boot magisk_patched-XXXXX_xxxxx.img (again, use the numbers and letters in YOUR patched file!)
Lastly, type:
fastboot reboot
Your phone reboots, and you should be rooted!! Unplug your phone from the PC, open up Magisk App and confirm, the Magisk entry at the top of the main Magisk App screen should now show you the version you installed, etc!
Time to get your banking apps (and any others that may detect unlocked bootloaders/root/etc) working!
In the Magisk App, on the bottom of the screen is a 4 item menu bar. Select the right-most icon, which is "Modules". At the top of the screen select "sorting order" and sort alphabetically. Scroll down to "riru" and select the module that is JUST "RIRU", (not any of the other "riru _______" modules). Choose to download it, then choose to install it. You'll be prompted to reboot the phone, so reboot the phone.
Next, we're going to install drag0n's Universal SafetyNet fix (at the time of this writing it's currently v 2.1.1) You will need to download this via a browser on your phone, so open a web browser and go to:
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
On the right-hand side, you'll find "Releases", and v2.1.1 is the latest. Select that, then scroll down to "Assets" and download "safetynet-fix-v2.1.1.zip" By default this will download to sdcard/Download.
Go back into the Magisk App, select the "Modules" menu as above, and at the very top select the "Install from Storage" bar. Point to the file we just downloaded and install it (don't extract it, etc, it requires the zip exactly as downloaded and will do it's thing). Again, it will install the module and prompt you to reboot. Reboot.
Almost there!
At this point, if you havent installed your banking apps, do so. DON'T RUN THEM, just install them. I also have a Nintendo Switch Online app which failed because of root, so if you also have or want this app, install it now, again, do NOT run it yet, just install. Same with any other apps you are aware which have root/bootloader unlocked issues, get them installed, but don't run 'em.
Now, we're going to use MagiskHide to hide these apps and complete the process for passing SafetyNet and running apps which may not run due to root.
in the Magisk App, at that 4 item menu bar at the bottom, select the 2nd from left, or "MagiskHide". Select the MagiskHide item and it will open to a scan of all the apps on your system. By default I believe Magisk sets up to hide Google Play Services. You will see it selected, and all the other apps on your system unselected. Select each of the banking apps, the Nintendo Switch Online (if you have it), and any other apps that YOU ARE SURE will complain about unlocked bootloaders and/or root. Any onilne gaming that's popular are good choices, but again, it's easiest to NOT RUN them PRIOR to hiding them via MagiskHide. Pokemon GO comes to mind as one I've seen that needs hiding, etc, so make it easy on yourself and do a little research on any suspect apps prior to running them, then hide them if needed.
Anyhow, select your banking apps to hide them.
Now, we're going to check SafetyNet to make sure youll now pass.
On the Home menu in the Magisk App, select "Check SafetyNet". You will be prompted to download some proprietary SafetyNet shhhhhhhtuff....so let it download. Once done, SafetyNet check will open, and you should show a blue screen which says SUCCESS, and "basicintegrity" and "ctsProfile" will be checkmarked, evalType will show BASIC.
You're good to go, rooted, SafetyNet works perfect, and you can now open your banking apps and should open right up!!
If you find any specific issues about specific apps not working, or detecting root, etc, the best place to get help is in the Magisk General Discussion forum:
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
I owe those folks eternally for showing me what I know, and always having the answers for any issues I've ever had. Some of the nicest, smartest people Ive had the pleasure of knowing, they're always helpful, and even maintain fantastic sites for FAQ and chock full of great info about every aspect of Magisk.
BONUS ITEM: As I indicated above, I'd share the method I know, trust, and have used many many times, trouble free, to apply a system update to the phone without overwriting anything, and not hitting any issues many encounter using the OTA method (though I understand that's been vastly improved, I haven't educated myself as to that process and will likely continue to use this method).
Security Update (monthlies) Process using Full System Image
As above, download the newest Full Factory Image from the site. Extract this full image to a directory inside C:\platform-tools
In this directory, if you're on Windows, open the "flash-all.bat" file (don't run it, open it with Notepad or something similar, I really like Notepad++ as it's free, has a LOT of great functionality and, like the native Notepad, doesn't do any goofy formatting/fonting/etc when modifying and saving a file.)
In flash-all.bat, look for the "-w" entry in the fastboot command near the end of the file and REMOVE ONLY THE "-w", leaving the line correctly formatted (don't leave an extra space or something goofy), then save the file over the top of the original with the same name. This will remove the overwriting of your data when pushing the image, the "-w" tells the process to overwrite, so we remove it.
Open up a Windows Explorer and go to your c:\platform-tools directory. Delete (or move to another location) any "boot.img" files along with any "magisk_patched-XXXXX_xxxxx.img" files from previous operations. Also note and confirm that you have correctly extracted the latest Full System Image to it's own directory, residing in c:\platform-tools.
Now, connect your phone to the PC. Open your command prompt and point to "C:\platform-tools" again. Type: cd <name of Full system Image directory>
In command prompt, type:
adb reboot bootloader
The phone is now in bootloader. In command prompt, confirm you're pointing to "C:\platform-tools\<Full System Image extract dir>" Type:
flash-all
This will do a full factory image push to your phone, you'll see a couple quick writes and phone reboots, then begins writing the rest of the image to your phone, but since we removed the "-w" from "flash-all.bat", it's NOT overwriting your data, just the necessary system files to update it to the latest version!
Reboot your phone, let it do any optimizing and updating it needs to do, and don't run anything yet, we're not quite done, just let the phone settle in and finish booting and doing it's thing.
Now, go back and perform the steps above listed under "PATCHING THE BOOT.IMG FILE" to patch the newest boot.img from the Full System Image we just updated the phone with (push the boot.img to sdcard/Download, patch with Magisk App, pull magisk_patched-XXXXX_xxxxx.img to your PC, blast it back using fastboot), and you've now rerooted the phone.
Lemme just say again that I know this was a friggin' book, and I tried to make it as clear and plain language as I could to help even a first timer, so my apologies if it seems like an onerous process. It's really not, and once you've done this once or twice, it's a cakewalk and takes about 10 minutes of your time from start to finish to do the whole system update and reroot. Again, the newer methods to take OTA without losing root may be something you'd like to look into, i definitely will, but I'm very confident in sharing this method as I know it works like a champ and is foolproof if you take your time the first few times and make sure you do what's required (remove the "-w" from the flash-all.bat, etc)
Lastly, I've been using this method since the Pixel 2, and just performed it on my new 5a, it worked exactly as it has for years for me on the P2, so you can be confident moving forward that, if you follow instructions and take your time until it's all familiar, you'll be successful in rooting, passing SafetyNet, and applying system updates without screwing up the A/B slots or overwriting your data in the process.
I hope this helps even one person, and since I rarely find myself able to give back to the community in any real meaningful way (many of these folks are WAAAY beyond my modest skills and know so much!!), I hope that this provides some folks with a useful and meaningful tutorial, providing confidence that anyone can root their P5a (or about any Pixel it seems) without being a Magisk/Android prodigy.
@Didgeridoohan, @pndwal, @zgfg, @jcmm11, and so many others over the years have been so helpful, I couldn't have done any of this without their selfless help, so give those folks a big thanks also if this is any help to you.
Best of luck,
hfam
Thanks for the write-up @hfam, it's good to know that some of the steps that i tried aren't really necessary, like using props config or hiding the actual magisk app.
Appreciate you!
nsoult said:
Thanks for the write-up @hfam, it's good to know that some of the steps that i tried aren't really necessary, like using props config or hiding the actual magisk app.
Appreciate you!
Click to expand...
Click to collapse
Awww, thanks! Glad to do it and really hope it helps some folks tackle rooting their phones and passing SN!
Rooted with magisk v.23 - flashed zip as a module
So has anyone installed the October update yet?
GrandAdmiral said:
So has anyone installed the October update yet?
Click to expand...
Click to collapse
Yep, good to go. I used the same method I shared above.
Is this working with Android 12? Which Magisk version to use?
This method did not work for Android 12. I updated my rooted phone to android 12 OTA. It returned to stock. I followed the method above to patch the factory boot.img file with magisk. After flashing my phone in bootloader with the patched boot.img, my phone will not reboot. says:
failed to load/verify boot images
Any advice? My Magisk is v23. Do I need to use a beta version?
Poking around in this thread, it seems that android 12 root is a much more involved process, requiring factory wipe and additional steps.
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
tintn00+xda said:
This method did not work for Android 12. I updated my rooted phone to android 12 OTA. It returned to stock. I followed the method above to patch the factory boot.img file with magisk. After flashing my phone in bootloader with the patched boot.img, my phone will not reboot. says:
failed to load/verify boot images
Any advice? My Magisk is v23. Do I need to use a beta version?
Click to expand...
Click to collapse
As you stated, you are correct. You need to perform a full wipe or flash the factory image with a wipe and then root works fine and phone boots. Tried myself and works fine.
heeeeey!
old magisk user, it was working like a charm on my galaxy s20, but lately something broke!
I have installed Magisk version 97b72a59 (20419)
and magisk manager version 8.0.7 (4834)
When I open an app that requires root access, nothing happens, and after a while, i get the toast message that denied superuser rights.
11-16 21:36:12.620 5867 27034 D Magisk : su: request from pid=[27031], client=[9]
11-16 21:36:12.620 5867 27034 D Magisk : su: request from uid=[10452]
11-16 21:36:12.620 5867 27034 D Magisk : magiskdb: query magiskhide=[0]
11-16 21:36:12.620 5867 27034 D Magisk : magiskdb: query su_fingerprint=[0]
11-16 21:36:20.462 5867 25942 W Magisk : su: request rejected (10452)
11-16 21:36:20.462 5867 25942 E Magisk : write failed with 32: Broken pipe
Click to expand...
Click to collapse
i have seen that it happens a lot, but there isn't any solution on these threads!
any suggestions?
thank you in advance for your help!
Go to magisk manager and manually grant root permission to that app in question
miravision said:
Go to magisk manager and manually grant root permission to that app in question
Click to expand...
Click to collapse
thank you for your reply!
on this page, on magisk manager app, I get the message "no app has asked for superuser permission yet"!
Install root checker app and check if it prompts you for root access, else magisk is configured to always reject root access in magisk settings
miravision said:
Install root checker app and check if it prompts you for root access, else magisk is configured to always reject root access in magisk settings
Click to expand...
Click to collapse
As expected, root checker app reports "Sorry! Root access is not properly installed on this device."
On magisk manager settings, i have set "automatic response" to "grant" instead of "prompt" but nothing changed.
any other options?
Unroot and reinstall latest magisk
miravision said:
Unroot and reinstall latest magisk
Click to expand...
Click to collapse
that's my last resort.
I am trying to repair it, rather than uninstalling and installing it again...
@sakis_the_fraud You see that broken pipe in your log? That suggests you're seeing an issue that was present in builds around v21 and fixed in v21.4.
I suggest you update to a more recent Magisk release instead of trying to troubleshoot further...
Didgeridoohan said:
@sakis_the_fraud You see that broken pipe in your log? That suggests you're seeing an issue that was present in builds around v21 and fixed in v21.4.
I suggest you update to a more recent Magisk release instead of trying to troubleshoot further...
Click to expand...
Click to collapse
thank you for your reply!
The reality is that I'm trying not to mess a lot with these just to be safe!
OK so If I got it correctly, i should do these steps:
select uninstall from magisk manager app,
reboot
and then "Patch the boot (Kernel) image via Magisk" as described in Stage 6 of the link?
any precautions and measures that i should take in order to avoid or minimize failure?
sakis_the_fraud said:
thank you for your reply!
The reality is that I'm trying not to mess a lot with these just to be safe!
OK so If I got it correctly, i should do these steps:
select uninstall from magisk manager app,
reboot
and then "Patch the boot (Kernel) image via Magisk" as described in Stage 6 of the link?
any precautions and measures that i should take in order to avoid or minimize failure?
Click to expand...
Click to collapse
No matter how you choose to update, there's always a risk of failure. Only way to minimise any damages is to make sure you have a backup of any important data before updating.
You should be able to do a direct update in the Magisk app (but since you're jumping a few versions it's a very good idea to have that backup ready). Only thing to mind is that the update to v22+ requires you to not have the Magisk app repackaged with a random name, so make sure you've restored that before updating. This should be the easiest way of doing things...
If you're on the Canary channel (since you have a Canary release installed now), keep in mind that the current Canary (23014) has some major changes from previous Magisk versions. The Hide list has been replaced with a Deny list and there's now a new feature: Zygisk (it's very similar to Riru, if you know that that is). If you're not ready for those kind of changes yet, make sure to be on the stable update channel...
If you don't want to do a direct update the linked guide should work.
Didgeridoohan said:
No matter how you choose to update, there's always a risk of failure. Only way to minimise any damages is to make sure you have a backup of any important data before updating.
You should be able to do a direct update in the Magisk app (but since you're jumping a few versions it's a very good idea to have that backup ready). Only thing to mind is that the update to v22+ requires you to not have the Magisk app repackaged with a random name, so make sure you've restored that before updating. This should be the easiest way of doing things...
If you're on the Canary channel (since you have a Canary release installed now), keep in mind that the current Canary (23014) has some major changes from previous Magisk versions. The Hide list has been replaced with a Deny list and there's now a new feature: Zygisk (it's very similar to Riru, if you know that that is). If you're not ready for those kind of changes yet, make sure to be on the stable update channel...
If you don't want to do a direct update the linked guide should work.
Click to expand...
Click to collapse
Ohhhh I see!
There are major changes listed on the changelog...
I found the "magisk_patched.tar" that I have used on my initial installation, do you believe that if i could flash it will solve this problem?
It's clear that I don't want the latest, i want the one working with minimal risk because I found out that i haven't installed TWRP at all
sakis_the_fraud said:
Ohhhh I see!
There are major changes listed on the changelog...
I found the "magisk_patched.tar" that I have used on my initial installation, do you believe that if i could flash it will solve this problem?
It's clear that I don't want the latest, i want the one working with minimal risk because I found out that i haven't installed TWRP at all
Click to expand...
Click to collapse
If that patched file is from an earlier release of Magisk, and you want to use that version, it's probably best to uninstall Magisk and flash that.
If you want a newer release you can either just choose the stable update channel and do a direct update to v22.1 (you'll be able to update to v23 after that), or you can download the v21.4 zip from GitHub and install that zip from the module section of the Magisk app.
You've got many options. Only you can decide what's best for you...
Didgeridoohan said:
If that patched file is from an earlier release of Magisk, and you want to use that version, it's probably best to uninstall Magisk and flash that.
If you want a newer release you can either just choose the stable update channel and do a direct update to v22.1 (you'll be able to update to v23 after that), or you can download the v21.4 zip from GitHub and install that zip from the module section of the Magisk app.
Click to expand...
Click to collapse
thank you for your help so far!
When i select uninstall i get two options "restore images" and "complete uninstall" what should i choose in order to keep my data?
If i go with the direct update to v22.1, then will i have to flash something? this is "safer"?
sakis_the_fraud said:
thank you for your help so far!
When i select uninstall i get two options "restore images" and "complete uninstall" what should i choose in order to keep my data?
If i go with the direct update to v22.1, then will i have to flash something? this is "safer"?
Click to expand...
Click to collapse
No worries.
To avoid incompatibilities between different Magisk versions you'd have to do a complete uninstall. If you do the direct update you don't have to do anything else then pick "Update" in the Magisk app and then "Direct install".
To say if one or the other is safer is hard to say since there quite a few variables that come into play. Doing an uninstall might cause issues if you've previously disabled encryption, as an example. On the other hand there might also be issues when doing a direct install.
Personally I would go for a direct install, but make sure that I have my firmware's/ROM's unpatched boot image at hand so I can install that and get my device up and running again without any further damage (hopefully). Magisk only alerts the boot image (or in some cases recovery image), which makes it very safe and easy to revert if there are problems. You rarely end up with an irreparable loss unless you start trying to fix stuff without actually knowing what you're doing.
Didgeridoohan said:
Personally I would go for a direct install, but make sure that I have my firmware's/ROM's unpatched boot image at hand so I can install that and get my device up and running again without any further damage (hopefully). Magisk only alerts the boot image (or in some cases recovery image), which makes it very safe and easy to revert if there are problems. You rarely end up with an irreparable loss unless you start trying to fix stuff without actually knowing what you're doing.
Click to expand...
Click to collapse
I made it!
I finally went with direct install as it appears to be less disruptive, first it updated the app, then I selected "direct install (recommended)". Afterwards it started to patch ramdisk, repacked and flashed the image. One reboot later and the root status is back! I really missed my adblock!!!
thank you for your help!