Related
Hi,
It's a long time that I don't use root on my Oneplus 3T.
What I want to know is that if with the latest Oxygen Os, unlocked bootloader and latest magisk root / magisk hide I will be able to use Google Pay.
I know that Google can update SafetyNet detection algorithm, so usually if that happens after how long Magisk is updated to hide root again?
Thanks!
I had a message last time that tells me that if I have my bootloader unlocked, no matter if I have Magisk or not, Google Pay won't let me pay with NFC
tetra96 said:
I had a message last time that tells me that if I have my bootloader unlocked, no matter if I have Magisk or not, Google Pay won't let me pay with NFC
Click to expand...
Click to collapse
Without hiding the status of the bootloader, for sure Google Pay won't work. But Magisk Hide, can hide root status and bootloader status.
That's what I want to know, if Magisk Hide working or not
Waiting more responses from other users
andQlimax said:
Without hiding the status of the bootloader, for sure Google Pay won't work. But Magisk Hide, can hide root status and bootloader status.
That's what I want to know, if Magisk Hide working or not
Waiting more responses from other users
Click to expand...
Click to collapse
Google Pay works fine with Magisk. You don't need to hide it or hide Magisk Manager.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Google Pay works fine with Magisk. You don't need to hide it or hide Magisk Manager.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Can you explain how you were able to make it work? Because whether I hide Google Pay in Magisk or not, when I try to setup my credit card in Google Pay it says "Couldn't finish setup to pay in shops. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
I have a OnePlus 3 Oxygen 5.0.6 and Android 8.0.0 with Magisk 17.1.
axelryder said:
Can you explain how you were able to make it work? Because whether I hide Google Pay in Magisk or not, when I try to setup my credit card in Google Pay it says "Couldn't finish setup to pay in shops. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
I have a OnePlus 3 Oxygen 5.0.6 and Android 8.0.0 with Magisk 17.1.
Click to expand...
Click to collapse
That's odd. I didn't have to do anything to get it working. I'm on OOS 5.0.5 and Magisk 17.1.
Two question: is your phone encrypted and do you have a pin/password set?
My phone is encrypted and I use a password.
You could also try hiding Magisk Manager (I haven't needed to do this) and delete any Magisk folder on you internal storage.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
That's odd. I didn't have to do anything to get it working. I'm on OOS 5.0.5 and Magisk 17.1.
Two question: is your phone encrypted and do you have a pin/password set?
My phone is encrypted and I use a password.
You could also try hiding Magisk Manager (I haven't needed to do this) and delete any Magisk folder on you internal storage.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I have a pin set, I don't think my phone is encrypted; although when I go to the Security menu, under "Encryption" it does say "Encrypted", but I don't remember setting it up. So I guess it is!
I did try to hide Magisk Manager from their option in the settings menu, but I still got the same error in Google Pay after;
As a side note, in Magisk SafetyNet Check does "Success", but ctsProfile is false, and basicIntegrity is false too; does that matter?
axelryder said:
As a side note, in Magisk SafetyNet Check does "Success", but ctsProfile is false, and basicIntegrity is false too; does that matter?
Click to expand...
Click to collapse
Yes; SafetyNet check means that app contacted with Google server with success, but the result of your device check is false, which means that your device is not certified "secure" in its current state.
Perhaps you tampered system partition?
tetra96 said:
I had a message last time that tells me that if I have my bootloader unlocked, no matter if I have Magisk or not, Google Pay won't let me pay with NFC
Click to expand...
Click to collapse
Did you try with a custom kernel? Your kernel needs SultanXDA's patch to pass safetynet with a unlocked bootloader. There is a magisk module here, that might work if you don't want a custom kernel. There's also some commands you can run on your devices terminal here, that might work too. I only have experience with using a custom kernel but the changelog for the module does say it was patched for OP3 support.
axelryder said:
...
As a side note, in Magisk SafetyNet Check does "Success", but ctsProfile is false, and basicIntegrity is false too; does that matter?
Click to expand...
Click to collapse
You've definitely installed something that breaks SafetyNet. Xposed used to do this, though I think it's been fixed to work with Magisk.
namanjr said:
Did you try with a custom kernel? Your kernel needs SultanXDA's patch to pass safetynet with a unlocked bootloader. There is a magisk module here, that might work if you don't want a custom kernel. There's also some commands you can run on your devices terminal here, that might work too. I only have experience with using a custom kernel but the changelog for the module does say it was patched for OP3 support.
Click to expand...
Click to collapse
Both Magisk and custom kernels patch the boot image so that it doesn't trigger dm-verity and pass SafetyNet. You don't need to use a custom kernel if you're using Magisk.
Sent from my OnePlus3T using XDA Labs
My Safetynet check is successful. Yet it doesnt work with Google Pay. I am told that PAY is not supported on my device as it is rooted.
przemcio510 said:
Yes; SafetyNet check means that app contacted with Google server with success, but the result of your device check is false, which means that your device is not certified "secure" in its current state.
Perhaps you tampered system partition?
Click to expand...
Click to collapse
BillGoss said:
You've definitely installed something that breaks SafetyNet. Xposed used to do this, though I think it's been fixed to work with Magisk.
Both Magisk and custom kernels patch the boot image so that it doesn't trigger dm-verity and pass SafetyNet. You don't need to use a custom kernel if you're using Magisk.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I do indeed have Xposed installed, V90 beta 3. I guess maybe it's not fixed for Magisk after all :/
@przemcio510 do you use Xposed ?
axelryder said:
I do indeed have Xposed installed, V90 beta 3. I guess maybe it's not fixed for Magisk after all :/
@przemcio510 do you use Xposed ?
Click to expand...
Click to collapse
Yes, I do, Xposed breaks SafetyNet and there's nothing you can do to keep it installed and have SN passing
przemcio510 said:
Yes, I do, Xposed breaks SafetyNet and there's nothing you can do to keep it installed and have SN passing
Click to expand...
Click to collapse
Oh I see... well here's my problem I guess lol
On my Redmi note 4 From recent update of miui 10 and magisk 17.1 update google pay stopped working even though safety net check is passed. Earlier google pay was working fine.
Is there any work around?
Sahil Shaikh said:
On my Redmi note 4 From recent update of miui 10 and magisk 17.1 update google pay stopped working even though safety net check is passed. Earlier google pay was working fine.
Is there any work around?
Click to expand...
Click to collapse
This is a OnePlus 3T forum. Ask the question in the Redmi forum.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
This is a OnePlus 3T forum. Ask the question in the Redmi forum.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Okay, don't consider redmi note 4. Still do you got any way out for one plus 3?
Sahil Shaikh said:
Okay, don't consider redmi note 4. Still do you got any way out for one plus 3?
Click to expand...
Click to collapse
I think that your problem is specific to MiUI, because on our phones it works fine
Sahil Shaikh said:
Okay, don't consider redmi note 4. Still do you got any way out for one plus 3?
Click to expand...
Click to collapse
As per the previous post, Google Pay works just fine with Magisk installed. There's no need to hide it.
Sent from my OnePlus3T using XDA Labs
andQlimax said:
Hi,
It's a long time that I don't use root on my Oneplus 3T.
What I want to know is that if with the latest Oxygen Os, unlocked bootloader and latest magisk root / magisk hide I will be able to use Google Pay.
I know that Google can update SafetyNet detection algorithm, so usually if that happens after how long Magisk is updated to hide root again?
Thanks!
Click to expand...
Click to collapse
It is reliant on safetynet AFAIK, and that passes on my device when using Magisk - havent tried Android Pay as of yet, but am aware that Safetynet passes.
I know other folks had issues with earlier updates, but this is the first time I've seen this. I skipped the last few updates. Does the Magisk patch method no longer work for rooting the Pixel 4 XL? Or is there some way to fix this?
The "hardware off" module from Displax might help you.
Sent from my Google Pixel 4 XL using XDA Labs
It's hardware based so nothing you can do about it
Patching your boot image with Magisk still works. With the recent implementation of hardware attestation, apps can now recognize if your bootloader is unlocked and safetynet checks result in ctsProfile failing. Magisk Hide still works and you can still hide root from most apps but cannot hide that your bootloader is unlocked unless you use either the hardwareoff mod or the Magisk Props mod.
Lughnasadh said:
Patching your boot image with Magisk still works. With the recent implementation of hardware attestation, apps can now recognize if your bootloader is unlocked and safetynet checks result in ctsProfile failing. Magisk Hide still works and you can still hide root from most apps but cannot hide that your bootloader is unlocked unless you use either the hardwareoff mod or the Magisk Props mod.
Click to expand...
Click to collapse
I tried MagiskHide Props Config but that didn't work - unless I need to do more than just replace the fingerprint. Replacing the fingerprint did not fix the problem. It's likely the Pixel 4 XL uses hardware backed key attestation to check the bootloader state, which I think means MagiskHide Props Config won't solve the problem.
I did find and install the hardwareoff mod and that fixed the problem. Thanks everyone who mentioned that. It was not available for download in Magisk but I found it buried deep in a 4000+ post thread on XDA.
https://forum.xda-developers.com/ap...systemless-t3432382/post83028387#post83028387
fuarkgl3 said:
It's hardware based so nothing you can do about it
Click to expand...
Click to collapse
Eventually you will be right, once Google makes hardware backed key attestation permanent. But for now the hardwareoff mod works.
No work for me
Basic integrity and CTS profile remains false.
madmartian said:
I tried MagiskHide Props Config but that didn't work - unless I need to do more than just replace the fingerprint.
Click to expand...
Click to collapse
Just for clarification: you would also have had to use the "Force BASIC attestation" option. It basically does the same thing as the hardware off mod, so you're good to go already...
So I have the same problem basic integrity but the cts profile fails. Iam in the January update.
I've done anything to fix it but 0 for me. And the problem is that it just happened from nowhere it was everything ok I was passing the safety net and in a moment the gpay made me a warning about contactless payments and the problem started.
Escribis said:
So I have the same problem basic integrity but the cts profile fails. Iam in the January update.
I've done anything to fix it but 0 for me. And the problem is that it just happened from nowhere it was everything ok I was passing the safety net and in a moment the gpay made me a warning about contactless payments and the problem started.
Click to expand...
Click to collapse
Go over to the Magisk thread. It's discussed there in detail and there has been a Magisk Mod released to fix it..
Lughnasadh said:
Go over to the Magisk thread. It's discussed there in detail and there has been a Magisk Mod released to fix it..
Click to expand...
Click to collapse
Can you give me the link my friend?
Lughnasadh said:
Go over to the Magisk thread. It's discussed there in detail and there has been a Magisk Mod released to fix it..
Click to expand...
Click to collapse
Found it, thank you very much sir.
Can you share the link please?
I also woke up to Google Pay warning, an update, than lost Magisk. I've re-installed it but now failing safetynet. Been attempting to fix it for 2 hours now
mushtafa said:
Can you share the link please?
I also woke up to Google Pay warning, an update, than lost Magisk. I've re-installed it but now failing safetynet. Been attempting to fix it for 2 hours now
Click to expand...
Click to collapse
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
Found the link. It works, just need to setup Google Pay again https://github.com/kdrag0n/safetynet-fix
Has anyone had any issues with GPay not working on the Pixel 5? I've been getting a lot of issues with it recently. I keep getting errors when I try to pay for stuff using GPay. I'm using Magisk on my phone, but it isn't actually rooted. My version of Magisk and the OS are both a little out of date.
I had issues with it too. I just uninstalled then installed again and it worked just fine
Ewto16 said:
Has anyone had any issues with GPay not working on the Pixel 5? I've been getting a lot of issues with it recently. I keep getting errors when I try to pay for stuff using GPay. I'm using Magisk on my phone, but it isn't actually rooted. My version of Magisk and the OS are both a little out of date.
Click to expand...
Click to collapse
Can you explain a little more about what you mean about not being rooted but using Magisk? Magisk doesn't have much use without root, and if you're running a Magisk patched kernel, you -are- rooted.
I would suggest using Magisk Hide, but I believe that option is only available under root.
did you install the latest safetynetfix by kdragon?
Releases ยท kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Updated to Android 12 and now the GPay doesn't work.
Stock ROM, Cleanslate kernel, no root. Is there a fix? Or do I need to relock the bootloader?
Hi! You will need to root with Magisk and use safetynet fix module. I am affraid that other way doesn't exist with unlocked bootloader...
This doesn't work with the new google pay. For the official android 12 you have to use magisk canary and there is no more magisk hide. They've gone to whats called the deny list. There isn't even a section to view safety net status on the new magisk canary build. I'm on a rooted pixel 4 with official android 12 and I can get every other banking and money app i use to work fine but just not google pay. Google is looking for disabled verity and verification and for unlocked bootloader status. Even if you don't have root, just the fact your bootloader is unlocked will not let google pay to work.
Magisk alpha on T
It works with Pixel 3XL on Android 12. Root / install Magisk, enable SafetyNet (https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/), add Google Pay to deny list and that's it. No SQL hack required...
Search 'google pay' within thread in the link if you're unsure how to set everything up.
This fixed my 4 XL which is running Android 12 November 2021. Been racking my brain the past two days trying to figure out how to get GPay working since upgrading two A12. I NEVER carry my cards, I'd die without GPay.
All I needed was Canary, the newest SafetyNet and to hide GPay.
No SQL hack BS required here either.
Side note, A12 sucks. The layout looks like it was designed for a 70-year-old that has bad vision. I see I'm not the only one that shares these thoughts though, Google's forums and Reddit are littered with people complaining about the same thing.
This may be the first time in history and I'd been a Nexus and Pixel owner for years, I may downgrade back to a previous version of Android, it's THAT bad.
.
updated Android 12 on motorola edge 20 .. rocks .. all smooth good experiance
google pay DOWN
unlocked bootloader .. my OEM UNLOCKINg is greyed out so i didnt root
researched SHIZUKU but doesnt allow me to (use google pay)
strange thing . BANK MILLENIUM has activated my NFC functionality so i can pay in store
WE DONT NEED GOOOGLE PAY ... i just need to get REVOLUT WORKING SAME WAY
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!