Database Info

How to disable System Update notifications

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.

Remove apps from Playstore update list?

Got a rooted op7p & various versions of my favourite apps installed that I don't want to update. Because there not the latest versions they stay stuck in my update list in the play store!
Is there a magisk module or app I can run to remove them from the list so I'm not constantly told to update or accidentally update it?
Think I might have solved it!
Went into Titanium backup pro, found the app, scrolled across to 'special features', then 'detach from the market'! There no longer in the update list now anyway ?

Detach is one that is for this
Titanium Backup like you found is another option
However, in my experience, both apps don't keep apps removed. After some time, they will show up again

Yeah your right, already popped back up!
Any idea how to permanently get rid of them?

You can turn off updates from the google play store itself, and it never notifies you.
Go into google play > Settings > Auto-update apps | Set to Don't auto-update apps. If I want to update something, I go in manually and choose what I want to update.
As for Magisk modules, also under settings, turn off Check Updates.
Titanium Backup was my first play store purchase for those features as well

Hi there, I have found a work around for this.
Go to (https://github.com/yuk7/playstore-excl-upd)
{
"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"
}
then follow the instructions on the page.
Make sure you create a txt file named as peulist.txt under root directory /data/cache/peulist.txt... once done reboot after flashing the file and include the apps with there package name that you want to exclude from the update list.

Bengemin14 said:
Hi there, I have found a work around for this.
Go to (https://github.com/yuk7/playstore-excl-upd)View attachment 5666533 then follow the instructions on the page.
Make sure you create a txt file named as peulist.txt under root directory /data/cache/peulist.txt... once done reboot after flashing the file and include the apps with there package name that you want to exclude from the update list. View attachment 5666537View attachment 5666539
Click to expand...
Click to collapse
Thank you a lotttt, worked perfectly! :3 <3
Also hiding YouTube, so it won't override YouTube vanced, hihi

Bengemin14 said:
Hi there, I have found a work around for this.
Go to (https://github.com/yuk7/playstore-excl-upd)
then follow the instructions on the page.
Click to expand...
Click to collapse
Um... any idea how you can UNDO this, so all available updates will show up again? I've tried disabling the module and rebooted, but the changes seem to stay...
Does anyone know what exactly this module does/changes? It does not seem to be really well documented...

Pixel 4a w/ May 2021 Security Update - Passing SafetyNet check

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.

Magisk hide "Settings" app force closing

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

Question Stuck in Download Mode: Error verifying vbmeta image

Hey there,
I have a problem with my A52 (SM-A525F/DS): It doesn't boot anymore, as it is stuck in the Download mode, showing the error message: "Reason recovery: Error verifying vbmeta image: invalid vbmeta header (6)"
Steps that lead to this:
LineageOS is installed. After installation of a software update, Magisk lost its root. So I tried to install an alternative recovery (TWRP) with Odin. Odin said "Pass", but now this error message occurs.
What can I do now to make the phone work again? Install the Stock ROM?
Would you please help me with this issue? Thank you so much.
{
"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"
}

Once again, you need to properly follow all the instructions listed on the thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-for-galaxy-a52-4g-and-a72-4g.4405751/

Thank you and please excuse my stupidity.

@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?

fheba said:
@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?
Click to expand...
Click to collapse
Not automatically. You would have to reflash magisk every time you install an OTA.

deleted

Simon1511 said:
Not automatically. You would have to reflash magisk every time you install an OTA.
Click to expand...
Click to collapse
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.

fheba said:
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.
Click to expand...
Click to collapse
The problem is encryption. On the A5 2017 the Magisk re-install script would run after installing an OTA and would install itself again. But since encryption is enabled by default on newer phones (such as the A52) it doesn't work/behave correctly.
I'm fairly sure though it's an issue with Magisk and not with the ROM.