Hey everyone, I just got back into rooting and well I would like to share some useful information that helped me pass the saftynet check within Magisk in 2021 with the latest security update (May 2021).
First off, I followed this guide to unlock my bootloader and gain root: google-pixel-4a-how-to-unlock-bootloader-root-pass-safetynet
I did run into some issues were I was not able to run fastboot in the cmd terminal.
To fix that, I downloaded
Google Pixel 4A Driver for Flashing Firmware
Google Pixel 4A USB Driver for normal connecting to PC
from here: google-pixel-4a-usb-drivers and it fixed my issues with not being able to run fastboot cmds.
After that, I was able to unlock my bootloader and root my Pixel 4a.
I followed the last step in the thread google-pixel-4a-how-to-unlock-bootloader-root-pass-safetynet on how to pass the safetynet check but it did not work for me. Installing MagiskHide Props Config and enabling MagiskHide did nothing.
So I downloaded an app from the PlayStore called Turmux where I half followed these steps: MagiskHide Props Config. I say half because the option "force BASIC key attestation" is no longer an available option. I went a different route. I selected the option Edit device fingerprint -> Pick a certified fingerprint and it is pretty self explanatory after that. Just make sure you pick your device model ad double check that the file and path are correct. (more info here)
This helped me pass the basic integrity check but this isn't enough!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did about 10 mins of googling and found this thread which lead me to the final fix. Instructions are in the screenshot below.
And that is all. check it out!
Happy modding xda fam!
P.S I am not in any way responsible for what happens to your device, your laptop, or the mods you decide to install afterwards.
Please let me know if there is any confusion that I can clear up.
Related
Hey guys,
Big thanks to @autoprime for mentioning this info on this in the general G4 forum. Figured I'd sum up the steps and repost in our sub-forum for anybody who may be struggling.
If you're like me, you're waiting on root and don't want to accidentally take that new OTA update that was pushed out about a week ago. This OTA has been found to prevent rolling back to previous versions of android, and may also block some/many of the root methods that the developers are preparing to release to us.
If System Update is constantly bugging you to update, follow the directions below:
1) Enable USB Debugging
-Go to About phone and tap on Build number 10 times to enable Dev Options
-Enter Developer Options and enable USB Debugging
2) Download and Install the Debloater tool (this happens on your computer)
-Windows http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater-setup-v3.85.exe
-OSX http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater.v.3.85.dmg
3) Connect your phone via USB. Make sure to install any drivers needed
4) Watch for pop up requesting ADB Access on your phone
5) Launch the Debloater tool
6) Select OK on the popup
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7) Click the top left button
8) Find LGDMSClient.apk and put a checkmark next to it. Then select Apply at the top
Congratulations! You no longer have to worry about pocket-updating your G4 and not being able to root down the road!
I just got the G4 yesterday. I didn't do my homework first and did the updates. Am I screwed when it comes time to root? (If ever)
Delete
I just went into Settings/Apps/Google Services Framework and unselected Show Notifications. This took the warning out of the Notification Bar.
Not certain yet in the event that it will keep the popup for the framework OTA overhaul.
Deleted
I saw on a website that there were other things listed in addition to what you blocked to avoid OTA updates. Should these be taken into consideration?
LGUpdateCenter.apk
LGFOTA.apk
LGLDB.apk
EDIT: I used that debloater tool and disabled that stuff. I've had no problems with the phone after that except for the AT&T bloatware.
Make ViPER4Android work on any marshmallow device : SELinux Permissive Fix
This is the easiest method I found so far, to make Viper4Android work on my V10 H960A running MM
Thanks to Sidharth Pk Here’s how you can install ViPER4Android on your Android phone running on Marshmallow or above. Change the SELinux policy from Enforcing to Permissive and enable ViPER4Android on your device. Also, fix the common errors while installing V4A like abnormal driver status, no processing etc.
I will copy/paste here his short instructions and for further details I will post a link to his page at the end of this post
Change SELinux to Permissive & Make ViPER4Android Work on any Marshmallow Device (By Sidharth Pk) :
ViPER4Android itself needs root access. So there’s no point of saying that your device must have root privileges.
.
Get ViPER4Android’s latest APK from here and install it on your Marshmallow device.
.
Now open it and let it install the driver for your device.
.
Once you get the install complete message, simply reboot the phone.
.
After bootup, Install Terminal Emulator App from here and install it on your phone.
.
Open it and perform the following commands one after one
Click to expand...
Click to collapse
Code:
[COLOR="Navy"][SIZE="4"][SIZE="5"]su
setenforce[/SIZE][/SIZE][/COLOR]
Close the terminal and check the driver status on ViPER4Android app, it should display like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Enable & Processing status will automatically change to Yes once you activate the master power option and start playing music on your headphone/speaker. If this method doesn’t work for you, you can flash the ViPER4Android Marshmallow ZIP file. It changes the SELinux from Enforcing to Permissive.
For more info have a look at the original thread/page:
http://www.techbii.com/install-viper4android-marshmallow/
Enjoy !
We can discuss here afterwards, why install Viper4Android in a phone with already such a great sound out of the box, such as the LG V10...
Cheers
.
.
Reserved
For some unknown reason I am unable to unroot my S6 (SM-G920F)
three is no uninstall option in the APP its self and using TWRP it says
*******************************************
the Magisk app will not be uninstalled
please uninstall it manually after reboot
*******************************************
Need to run banking apps so want to unroot my device
marcwsa said:
For some unknown reason I am unable to unroot my S6 (SM-G920F)
three is no uninstall option in the APP its self and using TWRP it says
*******************************************
the Magisk app will not be uninstalled
please uninstall it manually after reboot
*******************************************
Need to run banking apps so want to unroot my device
Click to expand...
Click to collapse
So, I understood that for whatever reason you don't have the red-framed button in your Magisk app as shown in my screenshot.
Spoiler: Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you try the uninstallation instruction that topjohnwu provides in his Github here (I mean the second sentence of the paragraph):
Installation
The Magic Mask for Android
topjohnwu.github.io
Last but not least, the following thread is monitored by highly knowledgable members who are certainly better suited to support you than me, although a search there could probably already provide a solution:
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
@marcwsa
You uninstall Magisk from within Magisk Manager app.
Apologies - but I am new to this and I think I may have bricked my phone now.
I did a complete wipe and now when it asks to reboot it says "No OS installed"
I fortunately still have access to the phone using USB to my PC so can transfer an image to the phone still. It ends up in /sdcard
BUT when I say install and point to the Pixel image file it goes all the way to the end and then on reboot says
No OS Installed Are you
sure you wish to reboot?
Damn --
jwoegerbauer said:
@marcwsa
You uninstall Magisk from within Magisk Manager app.
Click to expand...
Click to collapse
No uninstall option on my APP - that's the problem - but no worries anymore, I think I bricked my phone in any case :-(
So I got the first step, flashing TWRP. But, there's only a version of TWRP for the a10, would this work?
you don't really need twrp for root, just follow this guide
Installation
The Magic Mask for Android
topjohnwu.github.io
imalreadycrying said:
you don't really need twrp for root, just follow this guide
Installation
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
my phone doesn't show an oem bootloader unlock option
is it grayed out or do you just not see it
imalreadycrying said:
is it grayed out or do you just not see it
Click to expand...
Click to collapse
doesn't exist.
do you have dev options?
imalreadycrying said:
do you have dev options?
Click to expand...
Click to collapse
yes
send me a screen recording if you can, dev options should look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have previously tried Kingo/King Root which worked on my KitKat Nabi tablet, I tried that on my a10e it failed. Root checker says there is no root for andr 11 on the a10e
whatever you do, do NOT use kingoroot, it basically installs a outdated version of SuperSU (which isn't liked by the community anymore because the original developer sold it to some random company) and bloats ur system up.
Yep, no OEM bootloader unlock option in dev settings
it may be possibly locked to your carrier. again, you can send me a screen recording or get an unlocked phone
My phone appears to be unlocked already, there is no sign of Verizon still being on here. I have since upgraded phones and the SIM card isn't in anymore.
Do I have to factory reset to fully get rid of the OEM?
i found this youtube video with some quick searching. it's in hindi but you can get the gist of it.
I most certainly dont have to disable automatic time right?
i don't know, after you get the option maybe you can set it back
i followed and nothing happened
did you reboot your phone after the fact?
yep, nothing works
A few weeks ago, my hidden Magisk Manager (hidden as "Settings") stopped working. When I try and launch the generic Settings app it sets up, I get the normal FC menu ("Settings keeps stopping") error. I also get it when I open up any app that I previously allowed root access to, but obviously I cannot add new apps superuser access. I also get the FC every time I reboot the phone.
I haven't updated my OnePlus 9 Pro since the ColorOS 12 update came out, as 1) was not a fan, and 2) everything I read said I'd need to wipe the phone to get root back. Needless to say, it's been a while. My phone is currently on the 11.2.10.10.LE15AA version.
This just started happening one day, but I have no idea why. I am not sure what version of Magisk I am on, because I can't open the app. I also tried downloading the latest and installing the APK, but when I launch it, it's says things need to be "fixed" and to reboot. I then get the choice the normal Magisk installer brings up. I tried doing a direct install, but it failed. I also tried to restore the boot image, but it said the backup wasn't found (never seen that either, as I restore images every time I do an OTA).
Not sure what to do at this point. I'm at a complete loss. I would appreciate any help you guys can provide!
Do a LOGCAT to get the very reason why Magisk is not working.
I tried to get it as quickly as possible to minimize clutter, but it's still pretty long. I believe I've found where in the log the FC I captured (by looking for "zygote", but not sure what to make of it. It sounds like a file or something is missing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Doesn't seem like the logcat file got attached.
Oh well, here's a link:
FilePost
filepost.io