Why is this phone some wonky with installing **** through recovery?
Installed magisk and don't pass the safetynet. F droid won't give me an option to install adaway.
How the heck do you root this thing.
I'm on crdroid 8.1
Are you using the latest version of Magisk? How did you install it? Do you have the Magisk Manager app installed?
You can install AdAway yourself. Get it here.
I'm on stock Pie and rooted no problem flashing magisk through twrp.
Maybe if you have a pixel it's easier to just stay up to date instead of playing the nerd who always knows better and then complaining that **** doesn't work.
Related
I have a google pixel recently rooted with Magisk and have TWRP. My system is informing me of a system update, and it says Couldn't install update. I've seen people suggesting using FlashFire to flash a factory image of the update, then install Magisk right after that. So how would i go about it? can i do just that? is it possible to update that way? can i flash both magisk and twrp after flashing the factory image? thanks in adv
https://forum.xda-developers.com/showpost.php?p=75480639&postcount=3
Try this
2x speed video of my using FlashFire to update the Pixel to the February Android 8.1 update, plus flashing ElementalX custom kernel v3.02 and Magisk v14.2. A little less than 3 minutes at this speed.
https://photos.app.goo.gl/Ck70tezbKVvbBCjs2
You have to be on Magisk 14.2 (not a higher version) to begin with, though, so if you're not, disregard this, or search for and read the appropriate posts for uninstalling Magisk and installing the correct version in order to use FlashFire under 8.1.
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok
airdi1 said:
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok
Click to expand...
Click to collapse
As I mentioned in the post, I do not have Xposed framework
quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.
run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk
tabletalker7 said:
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.
Click to expand...
Click to collapse
I have magisk 16.7
virtyx said:
run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk
Click to expand...
Click to collapse
How do I do that? Do you have a link to this zip?
quantumcity said:
I have magisk 16.7
Click to expand...
Click to collapse
Google "Magisk uninstaller". Flash that file in TWRP. Then reboot to recovery. Then flash Magisk 16.4
quantumcity said:
How do I do that? Do you have a link to this zip?
Click to expand...
Click to collapse
its in the magisk official thread.
virtyx said:
its in the magisk official thread.
Click to expand...
Click to collapse
Yes
So for me, the safety net check passes in the Magisk app but I am not able to access Google tez which tells me that my device is rooted or custom ROM has been changed. Using Magisk v 16.0
16.4... notice the 4
Just fyi I'm on 5.19 and using Magisk 16.0 and safety net passes just fine. Use Google pay daily and play store shows certified.
I hide everything Google related in magisk hide just to be sure
Eric214 said:
16.4... notice the 4
Click to expand...
Click to collapse
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!
I have attached the screenshots below. And I understand that I'm using Magisk 16.0
skr975 said:
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!
Click to expand...
Click to collapse
Do you have it hidden in Magisk? Google Pay works here if you hide it.
Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?
quantumcity said:
Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?
Click to expand...
Click to collapse
In playstore / settings are you uncertified? After unlocking bootloader I was and couldn't use Google pay. I flashed magisk and it was still uncertified so I cleared playstore app data. Now the phone says certified and Google pay works for me.
I suggest you flash 16.4 magisk and clear app data in playstore to see if you can get them working. Also you will need a different app than magisk manager to check safety net ATM as it will come back with "invalid response"
Sent from my OnePlus6 using XDA Labs
I was thinking of trying to fix a few minor things like won't boot with charger plugged in and Google Pay getting screwed up every once in a while...but figured I would ask first.
To be safe I was going to nandroid backup, TWRP Magisk Uninstaller, TWRP Magisk 18.1 installer and try it out later on....it seems people have reported bootloops on other phones upgrading from the Magisk Manager app...
MW
I am in 9.0.3 but under xxx no limits magisk rom.
It works well
0xPraeT0Rian said:
I am in 9.0.3 but under xxx no limits magisk rom.
It works well
Click to expand...
Click to collapse
Using the new magisk 18.1 or 18?
You asked about 18.1.
I am on 9.0.3 with 18.1 magisk and the new magisk manager
Hi to all,
I am on OB12, and I'm no longer able to root since I tried to upgrade from Magisk 18 to 18.1
I already tried the 2 last versions of Magisk uninstaller and also to reflash OB12, but still impossible to root.
What is very strange is that if I flash Smurfkernel it says that I'm rooted, but after booting, no Magisk APK and impossible to install it !
Any suggestions?
Thank in advance for any help.
I have already had Magisk 18.1 on stock 9.0.3 and it was fine. I upgraded from Magisk 18 through Magisk manager.
No problems here.
b.huss2 said:
I have already had Magisk 18.1 on stock 9.0.3 and it was fine. I upgraded from Magisk 18 through Magisk manager.
Click to expand...
Click to collapse
This is the first think I did, but unsuccessfully: Magisk Manager gave an error message installation unsuccessful like if not rooted.
It's why I flashed the Magisk uninstallers in order to clean all previous installations that could create problems, but whatever I do, rooting is missing after booting.
Really strange...(and annoying)
OP here -- I updated and am having no issues, but I did it all through TWRP by uninstalling Magisk 18.0 first and then re-installing 18.1 before rebooting. I had already updated Magisk Manager from the app.
Only thing I noticed was I had to reset up all my settings (Magisk hide for Direct TV Now, and re SU authorize all root apps). First reboot everything was slow with root apps waiting for SU access before the request came through, but then everything was fine once it was granted.
michelD said:
This is the first think I did, but unsuccessfully: Magisk Manager gave an error message installation unsuccessful like if not rooted.
It's why I flashed the Magisk uninstallers in order to clean all previous installations that could create problems, but whatever I do, rooting is missing after booting.
Really strange...(and annoying)
Click to expand...
Click to collapse
You might could try dirty flashing your ROM and then try Magisk again. You could have something jacked up.
(of course don't forget about TWRP if you go dirty flashing your ROM)
b.huss2 said:
You might could try dirty flashing your ROM and then try Magisk again. You could have something jacked up.
(of course don't forget about TWRP if you go dirty flashing your ROM)
Click to expand...
Click to collapse
Yes I tried this too, but unsuccessfully !
And I'm even not sure that a full wipe will help, because it concerns another partition.
Ive been using magisk for quite some time, rebooted my phone once to check that it worked. Went on for a while without rebooting, decide to reboot it after installing all my apps (no modules), have a couple root apps like adaway and J oneplus tools. Anybody else have this issue, any idea on how to fix it? Im running the latest OOS and the latest Magisk with the most recent Mauronofrio TWRP
I rooted my A7160 last year using Magisk only, no TWRP, since I couldn't find TWRP for the Exynos chipset. A couple days ago I dumbly let Magsik update to v22.1, which removed Magisk Hide, an essential for me. I want to downgrade Magisk, but haven't yet found a way to do so without TWRP.
First, does anyone know of a way to downgrade Magisk without TWRP? I've tried restoring my Titanium Backup of Manager, but that prompts me to download and install the full Magisk, which will leave me with the new Magisk. I also tried fresh install of the 7.5.1 Magisk Manager app, which only lets me install 22.1.
Second, is there any work on or anyone willing to work on TWRP or other custom recovery for the Exynos chipset (A7160)?
Third, is there any other way to hide root? A brief search did not yield anything promising yet.
Thanks in advance!
stgibson said:
I rooted my A7160 last year using Magisk only, no TWRP, since I couldn't find TWRP for the Exynos chipset. A couple days ago I dumbly let Magsik update to v22.1, which removed Magisk Hide, an essential for me. I want to downgrade Magisk, but haven't yet found a way to do so without TWRP.
First, does anyone know of a way to downgrade Magisk without TWRP? I've tried restoring my Titanium Backup of Manager, but that prompts me to download and install the full Magisk, which will leave me with the new Magisk. I also tried fresh install of the 7.5.1 Magisk Manager app, which only lets me install 22.1.
Second, is there any work on or anyone willing to work on TWRP or other custom recovery for the Exynos chipset (A7160)?
Third, is there any other way to hide root? A brief search did not yield anything promising yet.
Thanks in advance!
Click to expand...
Click to collapse
FYI Update for others' reference: I got what I needed with Zygisk and DenyList, so should be OK without downgrading. If I need to downgrade, I realized an option that may work: re-flashing the previously-used patched boot.img.