Safteynet custom roms - Google Pixel 4a Guides, News, & Discussion

1. Install latest canary magisk APK
https://github.com/topjohnwu/Magisk
2. Use magisk to patch boot img
3. Flash root img
4.install magisk module : magisk hide prop config
5. Install magisk module : universal safteynet pass latest version
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
6.Reboot phone go into terminal put command : su -c props
Grant superuser permission
7.choose 1 then F then 7 for Google then choose 25 for pixel 4a 5g
Reboot
8.goto magisk and enable magisk hide ,and hide magisk (rename to something else besides manager or settings )
Reboot
9.go into magisk hide and hide Google like in picture and reboot and you should be able to pass on latest may and lower builds
Do not update magisk from manager reinstall latest canary from magisk has to be canary
Also I do downgrade magisk to v21 as it is so far the best for pixel 4a allows magisk modules such a viper4android flawlessly
{
"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"
}

With magiskhide props config you can now set it to pixel 4a and pass

Related

Pixel 3 - Magisk keeps failing to detect it's self

Let me clarify -
Sometimes, seemingly randomly the Magisk manager app reports that Magisk is not installed, While all of my root apps still function fine. But, annoyingly, any apps that detect root.. can now detect root, because magisk hide is not working either. but then if i kill the app and relaunch it sometimes it will report that magisk is installed, sometimes it takes a reboot to get it to detect, sometimes i just plum can't get it to detect no matter what i do. It's like my system and magisk are fighting each other for control of root. I've tried searching for someone else who's experienced this, but to no avail. is there anything anyone can recommend to try?
very big image said:
{
"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"
}
Click to expand...
Click to collapse
Have you tried reflashing factory boot image and doing twrp and magisk from scratch?
Indeed I have.
When did this start happening? After a recent update? Is this your first time rooting the device? More info on your setup would be helpful.
Some steps to try:
Temp boot to TWRP image
Flash latest Canary Magisk Uninstaller
Reboot to System
Temp boot back to TWRP img
Flash latest Canary Magisk Installer
Reboot to System
Install latest Canary Magisk Manager (if not there after Installer flash)?
See if that solves the issue?
I have used this process during my factory updates and it's worked fairly well thus far. I have no kernels installed nor do i have TWRP installed.

[HOW TO] [ROM] LINEAGEOS FOR AMAZON FIRE 7 (9TH GENERATION)

I AM NOT RESPONSIBLE FOR ANY DAMAGE YOU MAKE TO YOUR DEVICE.
IF YOU ENCONTER A BOOTLOOP BOOT BACK INTO TWRP AND RESTORE YOUR BACKUP OR TRY INSTALLING LINEAGEOS AGAIN.
{
"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"
}
​
This will work on Amazon Fire 7 2019 (Don’t Try this in Any other device):​
Charge your phone up to 80% or 70%.​
Download and Install Latest Amazon USB Drivers.​
You will loose the original ROM or any CUSTOM ROM if you already installed on your phone. So make sure to Backup your phone before doing this step using TWRP or CWM or any Custom Recovery.​
You can also backup all your apps using Titanium Backup or you can Backup without any Root​
You must install TWRP or any Custom Recovery on your phone.​
install TWRP Recovery using this full guide​
Download all the Zip files from below and Place it in your phone’s root of internal memory​
​ DOWNLOAD FILES​ LineageOS
Flash Files​
Flash LineageOS Latest Zip​
Follow Below Instructions Carefully​
Download NanoDroid with MicroG (.zip)​
Root With Magisk (DONT USE APP) ​
Get Xposed framework From NanoDroid And configure it​
Go into NanoDroid and search FakeGapps​
install FakeGapps and configure it through Xposed​
flash MicroG And allow all permissions​
Go into NanoDroid and search play store​
use LINK2SD to turn google play into system app​
https://apkpure.com/link2sd/com.buak.Link2SD​
update to LineageOS latest version​
CREDITS​
GGOW For Making The ROM​
Me For The ROM And MicroG Installation Process ​

Question Rooting attempt ended up with no playstore

I recently attempted to root my op9 following the guide in the pro forum after booting a rooted bootloader and installing via magisk everything seemed fine, I actually use my phone a lot for contactless payments so I needed to pass safetynet and this is where everything went wrong, I followed the magiskhide guide and hid from gms and proceeded to reboot.
When my phone booted up I had lost the playstore and my phone was no longer rooted to make things worse safteynet failure.
In the end I had to flash a standard bootloader into both slots and relock my bootloader just to get stock working correctly.
What could I have possibly done wrong to lose playstore?
Fixed the issue partially following the rooting guide on the pro forum
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
I restarted the process after I factory reset and updated to LE2113_11_F.72
extracted the boot.img and patched it and finally got everything working...
it's been a while since I've rooted anything and the whole ecosystem has changed but I still managed the basics My only thought is I used the wrong bootloader.
{
"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"
}

TNG wallet can't be used after I ROOT ?

After opening the app, it is displayed on the first screen (blue), I have hidden it, but it doesn't work, Magisk 25.2 with Shamiko 0.6v, does anyone know what's going on?
{
"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"
}
Most banking / payment apps refuse their service when Android is rooted.
Use previous version. for me v1.7.82 work. after install just hide as usual and don't update from playstore.
jwoegerbauer said:
Most banking / payment apps refuse their service when Android is rooted.
Click to expand...
Click to collapse
Most apps can be used with Magisk Hide. Hide My Applist doesn't seem to work for TNG. Did a clean install of LOS to see if TNG was detecting root apps but it's still the same.
Edit: Installed PixelOS 12 on my Poco F1 and it works, but I did not install root. It's still something.
klchin0705 said:
After opening the app, it is displayed on the first screen (blue), I have hidden it, but it doesn't work, Magisk 25.2 with Shamiko 0.6v, does anyone know what's going on?
View attachment 5810735View attachment 5810737
Click to expand...
Click to collapse
Use Magisk Delta. Add root apps in SU List for root access. Works on all my devices.
wipeyourbuttocks said:
Use Magisk Delta. Add root apps in SU List for root access. Works on all my devices.
Click to expand...
Click to collapse
Yep, magisk delta is the only working solution here. both sulist and magiskhide work.
Additionally, use Momo to troubleshoot your magisk detection.

Question [Root] AdAway won't recognise my rooted device

Hi everyone,
For some reason I cannot turn on the root based method for AdAway (see screenshot).
I reinstalled AdAway several times, checked for root with RootChecker and I am running the latest version of Magisk.
Any ideas?
Cheers,
{
"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 give it root permission in Magisk?
You have to go in magisk settings and click "allow systemless hosts" for adblockers and then check in your modules section off magisk's main screen, if it's there reboot and then adaway will work(must reboot after adding systemless host). If latest magisk won't allow u to do what i mentioned above, you may have to switch to another devs version of magisk. Previous versions of magisk wldnt allow it so I had to switch and never switched back. Dm me if still have problems and I'll direct you
Install systemless Hosts Module from magisk settings
Installed and rebooted (see screenshot), yet I still get the same screen with AdAway..
I've added my latest Magisk profile below
If u got systemless host added in magisk and adaway still won't work after reboot, u need to uninstall adaway and then reinstall, all while keeping systemless host. Then it shld work. I've had same issues b4.
Tried reinstalling AdAway from F-Droid and it didn't work...
Weird. Since u have systemless host running in magisk u shld be able to reboot, then download adaway and do initial setup(for it).
Llywelyn said:
Tried reinstalling AdAway from F-Droid and it didn't work...
Click to expand...
Click to collapse
Have you tried installing an older version of AdAway first and then if it works upgrading after that?

Categories

Resources