Database Develop

Viper4Android FX doesn't work

It calling me all time for the driver. I do that every time and I give him magisk root to do that. Any suggestion?

Did i get here some help or not? Then i looking maybe for a other Forum...

Install as system app and allow it to install through the not recommended settings.
U now have to delete it and reinstall it.. Watch the instructions in the thread pls before you become sow passive agressive mate. It is not our fault, ok?

Use this module. Flash in Magisk manager. Choose latest driver, material app, system app, lib workaround, and choose no for the last. (I don't remember what was it)

Hi, I've a Mi9 and tried to install Viper4AndroidFx.. Installation ok, driver installed, but no effect.. tried to set all to highest value to ear some difference but nothing..
Uninstalled it, i tried Viper4Android Legacy, installed as system app and by magisk and chosen all installation option with up volume button..
But still no difference with the stock speaker.. can you help me?
I would like to encrease the volume during a calling. thanks bye

take a look on mi8 or mi a1 forum in xda, there is described exactly which modules in Magisk must be installed to allow a proper function of the ViperFX. Still bootloader locked, so I cannot support by then.

catalindobre said:
take a look on mi8 or mi a1 forum in xda, there is described exactly which modules in Magisk must be installed to allow a proper function of the ViperFX. Still bootloader locked, so I cannot support by then.
Click to expand...
Click to collapse
my bootloader is unlocked to flash magisk, why it doesn't works with unlocked bootloader?

nikzodiac said:
my bootloader is unlocked to flash magisk, why it doesn't works with unlocked bootloader?
Click to expand...
Click to collapse
It only works with unlocked BL ofc. Did you tried installing "Audio Modification Library", and "Audio Compatibility Patch" from Magisk repo?

darek1995 said:
It only works with unlocked BL ofc. Did you tried installing "Audio Modification Library", and "Audio Compatibility Patch" from Magisk repo?
Click to expand...
Click to collapse
no, what I've to do exactly? I'm not an expert of modding.. thanks

make sure to have installed Magisk Manager, also latest Magisk root installed via TWRP. After this it should be pretty simple, look for the afore mentioned modules in Magisk install them one by one (each single one might require a reboot). After installing them you may install ViperFX, (version 2.3.4 as a system app).

catalindobre said:
make sure to have installed Magisk Manager, also latest Magisk root installed via TWRP. After this it should be pretty simple, look for the afore mentioned modules in Magisk install them one by one (each single one might require a reboot). After installing them you may install ViperFX, (version 2.3.4 as a system app).
Click to expand...
Click to collapse
hi, I tried to do everything you said, no one difference..

in a few days when the unlocking time will end will try it myself and in case will make it work, I will post here the process steps.

You have to install the legacy version with lib workaround. For me its working or you can try the rootless version from team_dewitt (look here in xda for it) you only need twrp and init.d injector.

Try this one.
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
Just to install the apk, nothing else.
Working here like a charm

Hi, I tried the version linked by pokko, it works, but I can't find the way to encrease volume, it works just to have a lower volume, If I set the master volume value higher it doesn't encrease, seems like the stock volume.. is there a way to have an higher volume for the speakers?
thanks

2.7.0/2.7.1 working great on MIUI but with GSI roms it's a different story

if someone can tell me how to get an higher volume please let me know soon.. I'm really thinking to remove root frome my phone.. I've found no one good reason to have it, I don't want to change rom, so I did it just to have 3 things: adaway, encrease volume and use ps3 controller with bluetooth...
adaway doesn't block anything in site that I tried it,
with viper4android my speaker volume is still the same..
miui seems not compatible with ps3 controller.. sixaxis compatibility checker can't works with bluetooth..
the only good thing I've found is the modded youtube version with no ads and background player.. but I've seen exist a versione for no rooted phones too..

found a way to completly disable apps like breeno

so i was just searching in xda and i found a thread for realme x2 pro that makes all the Chinese app go away for good and make coloros CN version tolerable.
I TRIED IT AND IT WORKS ON REALME X2.
and below is the link to that thread which is made by kkarnaout and im personalty thankful.
https://forum.xda-developers.com/realme-x2-pro/how-to/guide-removal-china-related-apps-making-t4010019

Is the fingerprint scanner still working after the process?

Can you remove com.oppo.market and com.nearme.themestore ?

nothing happen to fp. everything works just fine.
well i couldnt remove the market and didn't try it with theme store.

Hi
Hi. Does it work on realme UI or only colors version?

This seems interesting. Please confirm whether this works on realme UI.

maxs8007 said:
This seems interesting. Please confirm whether this works on realme UI.
Click to expand...
Click to collapse
Yes it works on m X2 CN

You can use debloater magisk module and remove all the Chinese apps including theme store, market, phone manager etc. Everything works fine without any issue.

maxs8007 said:
You can use debloater magisk module and remove all the Chinese apps including theme store, market, phone manager etc. Everything works fine without any issue.
Click to expand...
Click to collapse
If it's stock rom + magisk module, will the safetynet check break?
It's returned to stock rom now.
I plan to unlock again and flash the recovery, then delete the .apk files in recovery. Finally relock again.
I think the safetynet check would be okay after this. Hope I'm correct.

nickyip123 said:
If it's stock rom + magisk module, will the safetynet check break?
It's returned to stock rom now.
I plan to unlock again and flash the recovery, then delete the .apk files in recovery. Finally relock again.
I think the safetynet check would be okay after this. Hope I'm correct.
Click to expand...
Click to collapse
Please avoid unlocking relocking bootloader multiple times. It may get hardbricked anytime.
Stock rom with magisk modules will not break the safetynet unless you flash xposed.
Just make sure you hide the magisk manager from settings and hide all banking apps or all those apps that detect root and you'll be good to go.
I'm on stock with magisk +modules and debloated all Chinese apps.

com.coloros.assistantscreen - breeno feed
com.heytap.speechassist - breeno voice , long power click
com.heytap.quicksearchbox - global search cant be change to english[?]
any fix to this problem ?
130|RMX1991CN:/ $ pm uninstall --user 0 com.heytap.market
Failure [DELETE_FAILED_INTERNAL_ERROR]

The right A12 ROMs rooting procedure

After searching the forum thoroughly, trying multiple found solutions and trying to find the answer on my own I decided to ask here. What is the right procedure to clean flash A12 AOSP-based roms and getting root?
Some time ago, after updating to A11 rom, I noticed I can't use Magisk the way I used to to root my device - 'no ramdisk' status made me forget about rooting for a while. Now I want it back at any cost. This is why I want you to answer some of my questions, including the one above:
1. Is 'ramdisk: no' status caused by A11 and above versions?
2. Is there a way to have ramdisk status 'yes' on A12 ROM to root the device without having to patch boot.img?
3. Magisk installation doc has totally different way of rooting in my situation. According to it, for ramdisk status 'no' the only solution is 'Magisk in Recovery'. However, every time I saw someone talk about no ramdisk magisk patching, they were patching the boot image - it works fine and is even suggested by Magisk app. Who is wrong here and which solution is the right one?
4. Is there a way to get SafetyNet to pass on patched boot.img? Is there a way to get it to pass on a rooted A12 rom?
5. Some time ago, I have accidentally flashed european vendor instead of chinese one (I own chinese K20 Pro). I had no problems with it so I ran it for a few months and then flashed it back to chinese. Might this be the source of ramdisk issue?
Big thank you to anyone who replies. I have no important data on my device so there is no need for a data-safe solution. I feel like existing flashing/rooting guides seem outdated as they mention A10 at best. After more than 2 years of owning this device I still love it and am not going to replace it anytime soon and I hope there are still people like me! Cheers!

deadw0lf said:
After searching the forum thoroughly, trying multiple found solutions and trying to find the answer on my own I decided to ask here. What is the right procedure to clean flash A12 AOSP-based roms and getting root?
Some time ago, after updating to A11 rom, I noticed I can't use Magisk the way I used to to root my device - 'no ramdisk' status made me forget about rooting for a while. Now I want it back at any cost. This is why I want you to answer some of my questions, including the one above:
1. Is 'ramdisk: no' status caused by A11 and above versions?
2. Is there a way to have ramdisk status 'yes' on A12 ROM to root the device without having to patch boot.img?
3. Magisk installation doc has totally different way of rooting in my situation. According to it, for ramdisk status 'no' the only solution is 'Magisk in Recovery'. However, every time I saw someone talk about no ramdisk magisk patching, they were patching the boot image - it works fine and is even suggested by Magisk app. Who is wrong here and which solution is the right one?
4. Is there a way to get SafetyNet to pass on patched boot.img? Is there a way to get it to pass on a rooted A12 rom?
5. Some time ago, I have accidentally flashed european vendor instead of chinese one (I own chinese K20 Pro). I had no problems with it so I ran it for a few months and then flashed it back to chinese. Might this be the source of ramdisk issue?
Big thank you to anyone who replies. I have no important data on my device so there is no need for a data-safe solution. I feel like existing flashing/rooting guides seem outdated as they mention A10 at best. After more than 2 years of owning this device I still love it and am not going to replace it anytime soon and I hope there are still people like me! Cheers!
Click to expand...
Click to collapse
Although Magisk official guide on Github is not clear about, for MIUI you should patch boot.img, not recovery, and do not pay attention to Ramdisk no.
However, when patching boot.img, watch to the log window and you will see it reports there that it found Ramdisk
And that procedure works fine on A11 as well - I have it (MIUI 12.5.2 on my side)
I suppose you have the official A11 and you installed over custom A12 ROM).
Old Magisk v23 was released before A12, hence you should IMO go for the new Canary or Alpha 23016
Btw, you will be IMO better askung in the Magisk General XDA thread

zgfg said:
Although Magisk official guide on Github is not clear about, for MIUI you should patch boot.img, not recovery, and do not pay attention to Ramdisk no (when patching boot.img, watch to the log window and you will see it reports that it found Ramdisk)
And that procedure works fine on A11 as well - I have it (I suppose you have the official A11 and you installed over custom A12 ROM)
However, old Magisk v23 was released before A12, hence you should IMO go for the new Canary or Alpha 23016
Btw, you will be IMO better askung in the Magisk General XDA thread
Click to expand...
Click to collapse
Thank you for replying.
I am aware of Magisk Canary, I used it to root my current A12 rom. Yes, I flashed it over the latest chinese MIUI firmware. Is there any way to pass SafetyNet with it though?

deadw0lf said:
Thank you for replying.
I am aware of Magisk Canary, I used it to root my current A12 rom. Yes, I flashed it over the latest chinese MIUI firmware. Is there any way to pass SafetyNet with it though?
Click to expand...
Click to collapse
If you are on Canary 23016 (latest), you must enable Zygisk, and reboot
Then enable Enforce DenyList and go to Configure DenyList, enable Show System and OS apps, find Google Play Services and checkmark com.google.android.gms and
com.google.android.gms.unstable, and reboot again
If you were on the official, certified ROM, that would be enough to pass SafetyNet (since new Magisk app has no more the built-in SN checker, use one from PlayStore like YASNAC)
With your custom ROM you would probably need Universal Safety Net Fix= USNF 2.2.1 (latest).
Maybe even Magisk Hide Props Config (if USNF not enough) to spoof your unofficial/not Google certified ROM fingerprints - you will need to figure out (pain in the ass with custom ROMs)

zgfg said:
If you are on Canary 23016 (latest), you must enable Zygisk, and reboot
Then enable Enforce DenyList and go to Configure DenyList, enable Show System and OS apps, find Google Play Services and checkmark com.google.android.gms and
com.google.android.gms.unstable, and reboot again
If you were on the official, certified ROM, that would be enough to pass SafetyNet (since new Magisk app has no more the built-in SN checker, use one from PlayStore like YASNAC)
With your custom ROM you would probably need Universal Safety Net Fix= USNF 2.2.1 (latest).
Maybe even Magisk Hide Props Config (if USNF not enough) to spoof your unofficial/not Google certified ROM fingerprints - you will need to figure out (pain in the ass with custom ROMs)
Click to expand...
Click to collapse
This is exactly what I needed, thank you!

I dont have this model phone but i faced the same problem, i just flashed ArrowOS S along with magisk but i didnt realised it has now ramdisk no, before i was using AICP and it has ramdisk yes, so i installed latest version of magisk and the system updated but i dont have root anymore, what can i do?
I use OrangeBox for flashing
Edit: also it does replace the custom recovery?

Magisk Update from 2.30 to 2.4.1 Guide for dummies

The new Magisk is here and with it some major changes. One of the most important is the removal of support for "MagiskHide". There are many advanced users who have figured this all out already and few (maybe more) like me who are just kind of lost not knowing what should be exactly done to be able to update and be able to use Magisk as they were, before the update.
I was hoping that a kind soul would put up an easy step by step guide to help these users and at the same time it will avoid a lot of repetitive questions on the main thread. I personally spent a long time reading many pages and was not able to fully understand what should be done.
In my case all I want to achieve is to update and be able to hide Magisk like it was in the previous version. Should I start by un-hiding it first before doing the update?
(what and how and from where) should I add something that will replace the hiding function? Viola! these are the kind of simple questions that will help some of us get going
I hope that someone will bring his precious help

Yeah I unfortunately did my upgrade and fought with the whole process for 6 hours straight (lol) and I still don't know what I did exactly to even begin to write any instructions - other than 6 hours straight of reading and trying and hoping .....
Not sure if you have been able to refer to this which helped me.... But, I also have an very basic understanding of how my device (OnePlus 7T) works with Magisk... Hope this helps. May be see if your specific device has the instructions already posted in the device specific forum here?
Installation
The Magic Mask for Android
topjohnwu.github.io
I've not used the Magisk hide cause I haven't needed it - BUT, it's still available in the latest Magisk Manager (24.1) in the Magisk Manager settings. I'm only using the systemless hosts module (included in Magisk manager settings) for Adaway, and the universal safety net fix to get Google Play store to say my device is certified.
But I don't know what device you have nor do I know the specific ROM you are using.
Sounds like you have root already so I'm thinking that's the worst of this behind you if you've already done that much yourself. Sounds like it's a basic case of update the Magisk Manager app from itself then determine the method appropriate for root to update which could be through the Manager app or like I chose to use the boot IMG then patch that then install since my device has no working TWRP. That, and once I updated the manager app and panicked so I uninstalled it to try and downgrade to v23 .... Good luck and may be just don't update just yet if there is no specific need to at this time. Take your time and read and proceed when comfortable.
Please:
Start with your preferred method of backing up everything first.
Also, may be consider if it's necessary to update and why??? I'm on stock Andriod 11 and this Magisk update make me think it's intended to be more for those on Android 12 - but I could also assume wrongly.
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
That's the thread I'm reading now...

Thanks a lot for your reply wugga3. I also on my side found two very helpful posts. They explain the basics (just to get started) and to make the update . I hope with the information gathered I will be able to do the update without messing things up!
[Discussion] Google Pay Magisk Discussion Thread
This thread is inspired by the PoGo Magisk discussion thread. It's meant to keep the clutter of "Google Pay doesn't work" posts out of the main Magisk threads. Please use this to discuss issues with Google Pay and possible solutions. There's a...
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com

Good and good luck...
One problem and probably the only problem I really had was self inflicted for not following the instructions properly and that was to uninstall any Magisk modules first or at that the appropriate step.
Other than that... still don't know your device or rom etc. Your device specific or rom specific forums may be able to provide you with much better assistance from members that have the same rom/device as you.

wugga3 said:
Good and good luck...
One problem and probably the only problem I really had was self inflicted for not following the instructions properly and that was to uninstall any Magisk modules first or at that the appropriate step.
Other than that... still don't know your device or rom etc. Your device specific or rom specific forums may be able to provide you with much better assistance from members that have the same rom/device as youI
Click to expand...
Click to collapse
I am using LineageOS 18.1 Android 11 for Samsung Galaxy Note 3 and I have twrp as recovery. Magisk 2.30 is already installed and device is rooted. I have no modules installed and in Magisk settings I have only MagiskHide enabled. All other settings are set to default. On Samsung Note3 forum there is no talk about this (understandable as the device is very old).

Ok great and is there any discussion for lineage 18.1 and root/update?
Since it's lineage 18 and based on Andriod 11 - I have to wonder if there is even the need to update Magisk as my limited understanding is that the Magisk update is aimed at Andriod 12? Other than that... I should expect from my prior understandings of Samsung that nothing much has changed with respect to root and updates of Magisk. Not much help but hopefully enough. May be best to wait until for now and usually I do also wait until all the facts are in and the bugs are sorted out (if any...) before I update if unnecessary.

Thanks wugga3,
I disabled "Check for updates" in Magisk app and decided to keep the older 2.30 version for now. Everything is working fine and so there is no reason to fix something which is not broken. The only reason I thought That I should update was a real advantage over the older version or a security weakness being fixed in the new one.
I am even seeing some people asking for help on how to downgrade! Anyway as you said wisely, it;s not after all a bad idea to wait a little to see how things work out for those who have upgraded and have new issues fixed before taking the jump.

Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot (Magisk) to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want

mingkee said:
Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want
Click to expand...
Click to collapse
Thanks a lot for your post mingkee,
I am sure many like me will be happy and appreciate reading this instead of having to go through many pages and still not be totally sure what to do
Allow me to just ask one question as I did not understand the second option of your instruction:
I update Magisk from the application itself. Once updated what do you mean by update boot to 24.1? This is to be done in Magisk itself?

rezpower said:
Thanks a lot for your post mingkee,
I am sure many like me will be happy and appreciate reading this instead of having to go through many pages and still not be totally sure what to do
Allow me to just ask one question as I did not understand the second option of your instruction:
I update Magisk from the application itself. Once updated what do you mean by update boot to 24.1? This is to be done in Magisk itself?
Click to expand...
Click to collapse
After updated app to 24.1, you will see another update on top of the app (Magisk). Direct install would be the simplest method

mingkee said:
Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot (Magisk) to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want
Click to expand...
Click to collapse
this should be pinned somewhere, very simple and worked fine on my Poco F3 using miui.eu & android 11
thanks a lot

Magisk, Lsposed Google photos unlimited uploads?

I apologize if this is a noob question. I haven't rooted since Pixel 2, so it has been close to 6 years and I am not very aware anymore about Magisk. I can probably find videos regarding how to install Magisk and root, but my question was with its use of LSposed and Pixelfy Google photos.
The Pixel 5 and older have free photo storage, and I assume this module spoofs the type of phone and makes it think it is a Pixel and gives free photo storage.
I have a phone I am not using but it is not rooted yet and something I am considering.
I have been also checking various threads and there is mixed feedback on this particular module.
Does anyone use the Pixelfy free photo storage ? It looks like it needs to be used with Magisk and LSposed to get it to work ? Some threads it looks like it works, others have been commenting that it is bricking and causing problems. If it is unreliable or bricking, then I'll just see if I can buy and older pixel but thought I'd ask here first. Thanks.

mikeprius said:
I apologize if this is a noob question. I haven't rooted since Pixel 2, so it has been close to 6 years and I am not very aware anymore about Magisk. I can probably find videos regarding how to install Magisk and root, but my question was with its use of LSposed and Pixelfy Google photos.
The Pixel 5 and older have free photo storage, and I assume this module spoofs the type of phone and makes it think it is a Pixel and gives free photo storage.
I have a phone I am not using but it is not rooted yet and something I am considering.
I have been also checking various threads and there is mixed feedback on this particular module.
Does anyone use the Pixelfy free photo storage ? It looks like it needs to be used with Magisk and LSposed to get it to work ? Some threads it looks like it works, others have been commenting that it is bricking and causing problems. If it is unreliable or bricking, then I'll just see if I can buy and older pixel but thought I'd ask here first. Thanks.
Click to expand...
Click to collapse
If you mean this LSPosed module, then yes, I use it on 3 of my devices and it works perfectly.
And yes, it requires to be rooted with Magisk and to have LSPosed framework installed.

Lord Sithek said:
If you mean this LSPosed module, then yes, I use it on 3 of my devices and it works perfectly.
And yes, it requires to be rooted with Magisk and to have LSPosed framework installed.
Click to expand...
Click to collapse
Hi yes I believe this is it. So in order to have unlimited Google photo uploads, I need to first root, have magisk, download lsposed, then download this module separately?
I have a pixel 6a. Has there been any issues with Google halting or finding out about the spoof and blocking it?

mikeprius said:
Hi yes I believe this is it. So in order to have unlimited Google photo uploads, I need to first root, have magisk, download lsposed, then download this module separately?
I have a pixel 6a. Has there been any issues with Google halting or finding out about the spoof and blocking it?
Click to expand...
Click to collapse
Yes...there is actually two methods Pixelify goes about this; they either spoof the Pixel 5 (which is the latest Pixel Google will allow unlimited uploads but at "Storage Saver" lowered quality on the photos and videos) or the original Pixel(1) [which is the original and only Google Pixel left that Google allows unlimited uploads in original quality]. So you would need to decide which method you are willing to try and do...
But yes, you'd have to unlock the bootloader (which wipes the device), root with Magisk, install the LSPosed Magisk module, then run that Unlimited Google Photo app (or Baltiapps Pixelify GPhotos as it's officially named) which will then install the LSPosed module "separately".
I've already spoken a bit on this, so I will just quote what I said before (things to consider and risks involved) as well as you can click on the quote to go to the post/thread and see how the discussion developed there;
simplepinoi177 said:
I wouldn't make this claim with such certainty. Spoofing a Pixel phone is definitely against Google's Terms and Conditions. Doing this for years may have worked out since Google was offering it from Pixel 2-5 in Storage Saver capacity, but it's been 2 years since the Pixel 5 was released, and as time goes on, it's less realistic that Pixel's before 6 would still be in use, yet there would be all these accounts still backing up using the unlimited storage feature. ESPECIALLY if (like me, to be guilty of) there are many who are spoofing the Pixel 1 to get it unlimited WITH original quality -- being the first Pixel is 7 years old; highly unrealistic that so many people should still be using the phone to be taking photos and videos off of.
My point is that, no one using this "trick" should completely rely on it and expect Google to "play along" indefinitely about it. Like I've been saying, at best, Google will just plug in the loophole and close the feature down; at worst, they remove any photo or video that were taken under a particular Pixel model when your google account shows it being connected to another device altogether and/or they suspend a google account outright using the exploit -- this is highly unlikely, but is still in the realm of possibility and is as I said worst case.
I, myself, back my photos and videos from my Pixel 7 Pro using this spoofing trick, but I will also back all my media up (when my device is full) on a physical medium just in case.
Click to expand...
Click to collapse
P.S. Also, since you are out of practice in rooting, there is an excellent tool that streamlines most anything to do outside of stock experience on the Pixels (bootloader unlocking, rooting, flashing and/or updating Full Factory images or OTAs [to either both or inactive slots], flashing custom ROMs, other recovery checks and protocols, advanced apk install or apk/app disabling [system, stock], it might even be able to flash custom kernels but I can't be too sure) which would be able to accomplish what your aims are pretty much with a single click (outside of clicking where your factory images are and what not)....

simplepinoi177 said:
Yes...there is actually two methods Pixelify goes about this; they either spoof the Pixel 5 (which is the latest Pixel Google will allow unlimited uploads but at "Storage Saver" lowered quality on the photos and videos) or the original Pixel(1) [which is the original and only Google Pixel left that Google allows unlimited uploads in original quality]. So you would need to decide which method you are willing to try and do...
But yes, you'd have to unlock the bootloader (which wipes the device), root with Magisk, install the LSPosed Magisk module, then run that Unlimited Google Photo app (or Baltiapps Pixelify GPhotos as it's officially named) which will then install the LSPosed module "separately".
I've already spoken a bit on this, so I will just quote what I said before (things to consider and risks involved) as well as you can click on the quote to go to the post/thread and see how the discussion developed there;
P.S. Also, since you are out of practice in rooting, there is an excellent tool that streamlines most anything to do outside of stock experience on the Pixels (bootloader unlocking, rooting, flashing and/or updating Full Factory images or OTAs [to either both or inactive slots], flashing custom ROMs, other recovery checks and protocols, advanced apk install or apk/app disabling [system, stock], it might even be able to flash custom kernels but I can't be too sure) which would be able to accomplish what your aims are pretty much with a single click (outside of clicking where your factory images are and what not)....
Click to expand...
Click to collapse
Thank you for the information. So before the way I used to root was I would use adb then type fastboot img then the TWRP file.
Then reboot and now I have custom recovery TWRP. This is of course after I have unlocked the bootloader which wiped.
I assume this is still the case where oem unlock is checked in developer options then sdb fastboot flashing unlock?
I briefly used magisk by topjohnwu but it was new back then and I sort of didn't keep up with it.
If there is a program or different method is it possible to point me to it? I honestly can remember what to do after booting TWRP.
Regarding the spoofing, the standard upload of the pixel 5 is fine for me and you mentioned some good points regarding Google potentially catching on. At the time banking apps didn't care if you were rooted but I think they do not work anymore if you are.
Also I thought I read somewhere, lets say I just flash a custom rom instead and don't use the pixel OS, will this be automatically for this module without having to do anything extra? It reminds me of when all custom roms had free Hotspot tethering built in so you didn't need to do anything extra.
I also don't mind flashing a custom rom and using it as a dedicated backup device either. Just exploring options
Thanks for the starter info. I just realized how long it has been and I don't recognize anything anymore.

mikeprius said:
Thank you for the information. So before the way I used to root was I would use adb then type fastboot img then the TWRP file.
Then reboot and now I have custom recovery TWRP. This is of course after I have unlocked the bootloader which wiped.
I assume this is still the case where oem unlock is checked in developer options then sdb fastboot flashing unlock?
I briefly used magisk by topjohnwu but it was new back then and I sort of didn't keep up with it.
If there is a program or different method is it possible to point me to it? I honestly can remember what to do after booting TWRP.
Regarding the spoofing, the standard upload of the pixel 5 is fine for me and you mentioned some good points regarding Google potentially catching on. At the time banking apps didn't care if you were rooted but I think they do not work anymore if you are.
Also I thought I read somewhere, lets say I just flash a custom rom instead and don't use the pixel OS, will this be automatically for this module without having to do anything extra? It reminds me of when all custom roms had free Hotspot tethering built in so you didn't need to do anything extra.
I also don't mind flashing a custom rom and using it as a dedicated backup device either. Just exploring options
Thanks for the starter info. I just realized how long it has been and I don't recognize anything anymore.
Click to expand...
Click to collapse
I also had a Pixel 2 XL (taimen) for 3 years -- upgraded to the Pixel 5 -- so I am familiar with the method you are familiar with.
Unfortunately, that is no longer how it works. It sucks, but TWRP could never catch up after Android 10 -- it would take so long for them to develop that once they finally got TWRP to work with Android 10, Android 11 was released and became the new established version; then once they finally got it compatible with Android 11, Android 12 released and the same thing. So, as I understand it, TWRP does work in a limited capacity for Android 12, but it will not work for Android 13 (yet); and it seems if history repeats itself, it might not get there by the time Android 14 releases...
So still using magisk, but you can't "install" magisk from a .zip like you could with TWRP.
It's not that much more complicated than flashing Full Factory images or temp booting from a recovery image -- you simply extract the init_boot.img from the Full Factory image, "run it through" the Magisk app and get it patched that way, then flash the patched image the same way you flash the recovery partition (from the TWRP image) to permanently install/flash the custom recovery.
But, if you are still wary about going about all of this and/or if you are out of practice and unsure, please consider badabing2003's PixelFlasher. It basically does all of that stuff, but puts a GUI and automates it all for you -- as well as doing certain checks and protocols to make sure things aren't done wrong or buggy/incompatibly. It's as close to "one-click" as anyone's gonna get for the Pixels...
PixelFlasher will guide you to downloading the Full Factory image (or OTA if you wish that way), Magisk, the right platform-tools version (the least buggy version), i believe it can unlock the bootloader (but I could be wrong), and root or Full Factory update for you.
Hope this helps!

Lord Sithek said:
If you mean this LSPosed module, then yes, I use it on 3 of my devices and it works perfectly.
And yes, it requires to be rooted with Magisk and to have LSPosed framework installed.
Click to expand...
Click to collapse
Please, after installing how can be used?
Thanks!

amplatfus said:
Please, after installing how can be used?
Thanks!
Click to expand...
Click to collapse
after installing the module, the module actually installs an app (which can be found in the app drawer) under "Pixelify GPhotos". Running the app should give you all the settings and options you need to get it to work/"be used" -- it even has a button to force-close Google Photos to reset it to detect the spoofing. Just be sure you have all modules enabled (LSPosed[within Magisk], Pixelify GPhotos[within LSPosed]).
I've assisted a bunch of users/members where they had to play around with the configurations a bunch to finally get it to work for them; for whatever reason, one configuration works for one user but not the other -- my configuration did not work for some of them and they had to enable certain settings to get it to work for them (even though we are using the same device).

simplepinoi177 said:
after installing the module, the module actually installs an app (which can be found in the app drawer) under "Pixelify GPhotos". Running the app should give you all the settings and options you need to get it to work/"be used" -- it even has a button to force-close Google Photos to reset it to detect the spoofing. Just be sure you have all modules enabled (LSPosed[within Magisk], Pixelify GPhotos[within LSPosed]).
I've assisted a bunch of users/members where they had to play around with the configurations a bunch to finally get it to work for them; for whatever reason, one configuration works for one user but not the other -- my configuration did not work for some of them and they had to enable certain settings to get it to work for them (even though we are using the same device).
Click to expand...
Click to collapse
Hi thank you for all your help. I currently have the pixel 6a now and will get the 7a but probably keep the 6a as a dev device. Once I unlock the bootloader, I will try the pixel flasher and go from there. Good to know about TWRP but if there is a newer and better way I am all about experimenting with that as well. I may give it a run over the summer.
Once I download pixel flasher and install magisk, so I go to gitgub and download lsposed then install pixelfy as a module separately?
Unlock bootloader -> pixel flasher->magisk->Lsposed-> Pixelfy?
Thanks and salamat po

mikeprius said:
Hi thank you for all your help. I currently have the pixel 6a now and will get the 7a but probably keep the 6a as a dev device. Once I unlock the bootloader, I will try the pixel flasher and go from there. Good to know about TWRP but if there is a newer and better way I am all about experimenting with that as well. I may give it a run over the summer.
Once I download pixel flasher and install magisk, so I go to gitgub and download lsposed then install pixelfy as a module separately?
Unlock bootloader -> pixel flasher->magisk->Lsposed-> Pixelfy?
Thanks and salamat po
Click to expand...
Click to collapse
Once [you] download pixel flasher and install magisk,...go to [github] and download LSPosed (zygisk version), then install Pixelify GPhotos (Baltiapps version, not original kingsman44) LSPosed module as a module separately (in LSPosed).
It will then install a companion app which you can set the settings and options....
But yes, "Unlock bootloader -> pixel flasher->magisk->Lsposed-> Pixelfy?" looks right; just keep in mind that unlocking bootloader wipes device, and use Pixelify Baltiapps and not kingsman44's.
Glad to help!