Question Samsung pay with a root Samsung - Samsung Galaxy Watch 4

Hi,
I have one root Z flip 3 and I can pair it without problems with my galaxy watch 4, the problem is when I try to add one card to samsung pay through the Watch plug in, whenever i try to do all works fine until the last moment when the watch disconnect from the phone. I have tried this with other phones and with my own Z flip without root and It works.
Maybe, someone in the forum have found a way to make it work.
Thank you.

Samsung Pay is secured by Knox.
[Guide]Use Samsung Pay and Knox on your Rooted device
WARNING THIS IS A WIP AND SO FAR NO ONE HAS CONFIRMED THIS WORKING Samsung pay and Knox is working after Rooting. How is this possible?:confused: well, The loophole here is both Samsung pay and Knox apps check the kernel for knox status...
forum.xda-developers.com

blackhawk said:
Samsung Pay is secured by Knox.
[Guide]Use Samsung Pay and Knox on your Rooted device
WARNING THIS IS A WIP AND SO FAR NO ONE HAS CONFIRMED THIS WORKING Samsung pay and Knox is working after Rooting. How is this possible?:confused: well, The loophole here is both Samsung pay and Knox apps check the kernel for knox status...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes I know but i want to use samsung pay on the watch not in the phone, i was able to use it with knox tripped but not when magisk is installed.

Zoidben said:
Yes I know but i want to use samsung pay on the watch not in the phone, i was able to use it with knox tripped but not when magisk is installed.
Click to expand...
Click to collapse
Try to hide the watch app with magisk hide, and Spay too

Rick_BR said:
Try to hide the watch app with magisk hide, and Spay too
Click to expand...
Click to collapse
I have already done that if not I couldnt even open the app of the Spay watch plugin, i dont know what can be the problem

Ive used Samsung Pay on my Pixel 2XL for over 6 months now using my Active 2, until i just swapped to the Watch 4 and can use Google Pay easily, yay
How i setup Samsung Pay (using Active 2) :
* Magisk (i still prefer older Magisk - Alpha 31 to be exact - last build before John started removing MagiskHide etc - and yes it stillworks on Android 12)
* MagiskHide Enabled - checked to pass SafetyNet
* Rename Magisk app (from settings)
* Tick apps in MagiskHide: All Samsung related apps, including watch plugins
Added modules after the above:
* Riru
* Riru-MomoHider (my mod to add all 4config options - note later Magisk builds may or not allow Riru, and if they do, some may not allow all Riru-MomoHider config options - best to check in main Magisk thread if you use the latest/bleeding edge)
The Riru/Riru-MomoHide setup will give you greater process isolation than MagiskHide itself....
Attached:
*Magisk - Alpha 31 (apk, you can sideload this apk from TWRP, TWRP doesnt care its not named as a zip, only its content- sideload apk, reboot then install the apk, as the flashed apk only installs the stub Magisk Manager, and you dont want it grabbing the latest Magisk Manager from the interwebs at the moment...)
*Riru (Riru must be installed first, and a reboot performed before adding Riru-Momohider)
*Riru-MomoHider (my mod with 4 config options set at module install, instead of having to manually do it)
Bonus info:
If youre a regular ROM flasher, you'll want to keep your watch connection and Samsung Pay working across flashes, i have a guide for that in my signature, basically involves keeping the same Android ID across flashes. I need to update it for Android 12, which ill do over the weekend...the Android ID changer app i use on Android 11 doesnt work on 12...
Note: Magisk Alpha 31 referenced in above post removed from post as its quite old now.....use either Official Magisk (details in my following post down the page) or Magisk Delta (and the modules from this post)

73sydney said:
Ive used Samsung Pay on my Pixel 2XL for over 6 months now using my Active 2, until i just swapped to the Watch 4 and can use Google Pay easily, yay
How i setup Samsung Pay (using Active 2) :
* Magisk (i still prefer older Magisk - Alpha 31 to be exact - last build before John started removing MagiskHide etc - and yes it stillworks on Android 12)
* MagiskHide Enabled - checked to pass SafetyNet
* Rename Magisk app (from settings)
* Tick apps in MagiskHide: All Samsung related apps, including watch plugins
Added modules after the above:
* Riru
* Riru-MomoHider (my mod to add all 4config options - note later Magisk builds may or not allow Riru, and if they do, some may not allow all Riru-MomoHider config options - best to check in main Magisk thread if you use the latest/bleeding edge)
The Riru/Riru-MomoHide setup will give you greater process isolation than MagiskHide itself....
Attached:
*Magisk - Alpha 31 (apk, you can sideload this apk from TWRP, TWRP doesnt care its not named as a zip, only its content- sideload apk, reboot then install the apk, as the flashed apk only installs the stub Magisk Manager, and you dont want it grabbing the latest Magisk Manager from the interwebs at the moment...)
*Riru (Riru must be installed first, and a reboot performed before adding Riru-Momohider)
*Riru-MomoHider (my mod with 4 config options set at module install, instead of having to manually do it)
Bonus info:
If youre a regular ROM flasher, you'll want to keep your watch connection and Samsung Pay working across flashes, i have a guide for that in my signature, basically involves keeping the same Android ID across flashes. I need to update it for Android 12, which ill do over the weekend...the Android ID changer app i use on Android 11 doesnt work on 12...
Click to expand...
Click to collapse
Anyone tried this on S22 Sandragon Variant, Android 12?

Gymcode said:
Anyone tried this on S22 Sandragon Variant, Android 12?
Click to expand...
Click to collapse
My post is not current except if you are using the (recent) unofficial Magisk Delta, which still has MagiskHide as an option, Delta can be found here:
[Discussion] Magisk Delta - Another unofficial third-party Magisk fork
This is not an officially supported topjohnwu project. If you are looking for official Magisk source, please go to this page Introduction Custom Magisk fork by HuskyDG. Sync with official Magisk adding back MagiskHide...
forum.xda-developers.com
For mainstream/official Magisk, you should use Zygisk:
* Magisk 25.x
* Zygisk Enabled
* Rename Magisk app (from settings)
* Tick apps in Deny List: All Samsung related apps, including watch plugins
* DenyList Not Enforced (shamiko will handle this)
Added modules after the above:
* shamiko
all required files can be found in page 1 of this thread:
[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
As an alternate to shamiko, you can also try DenyList Unmount
GitHub - mywalkb/DenylistUnmount
Contribute to mywalkb/DenylistUnmount development by creating an account on GitHub.
github.com
As for "has anyone tried it?", if you have already rooted with Magisk, then simply try it....waiting for some other random person to do something isnt my 1st thought process....magisk is systemless and you cant really hurt anything...

Related

Snapchat and root

Hi title says all,
If you root your device is it possible to use snapchat?
On my rooted samsung device i was gettting after a few days a temporary ban.
Thanks, ?
Snapchat should work fine. I had one time over this weekend i got banned for 12 hours but at the time my Magisk was crashing from updating without removing substratum theme.
As long as you enable magisk hide and pay attention to updates, you should be fine.
You can use Snapchat if you don't install Xposed, I do know that much. Xposed gives you a temp. ban. There might be a work-around, but if you don't need that, you're good to go anyways
Don't have OP yet , but with other devices I've found that enabling Hide on Magisk for Snapchat actually makes things worse
Do others using Magisk have to enable Hide to use Snapchat?
jcrompton said:
Don't have OP yet , but with other devices I've found that enabling Hide on Magisk for Snapchat actually makes things worse
Do others using Magisk have to enable Hide to use Snapchat?
Click to expand...
Click to collapse
I have always hid Snapchat and Google Pay, along with other Google apps and never had an issue.
I have snapchat and I don't hide it from Magisk.
Sent from my GM1915 using Tapatalk
had issues on my Pixel 3XL
everything works perfectly fine on the OP7Pro
Well after a week rooting my device i was getting issues. But now i dont wanna risk a permanent ban for the sake of rooting ?
How to use Snapchat with magisk (After Ban)
bartjeh1991 said:
Well after a week rooting my device i was getting issues. But now i dont wanna risk a permanent ban for the sake of rooting
Click to expand...
Click to collapse
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ultimate Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX
ricketrash said:
You can use Snapchat if you don't install Xposed, I do know that much. Xposed gives you a temp. ban. There might be a work-around, but if you don't need that, you're good to go anyways
Click to expand...
Click to collapse
You won't get a temp ban with xposed. I'm even using SnapTools (Snapchat modifications) along with xposed and I've been fine for about 3 months now.

[Tips] Google Pay on Rooted Android Phone

If you want to make your Google Pay work, make sure you followed those steps below
Use AOSP/LOS or OEM Based rom. MIUI 7 and 8 have problems with SafetyNet [Even if you have Magisk installed]
***MOST IMPORTANT***
[###ROOT###]
Check your Selinux Mode in the About Phone section in Settings.
Selinux is another Google Protection featured with Kitkat in 2014
If you have Permissive, change it to Enforcing using this app [Download Attached Files]
Reboot after applying Enforcing. Don't Delete Selinux Mode Changer, You will lose your Enforcing and will be switched back to Permissive
Use Magisk only - Don't use SuperSu, it doesn't have Hiding features and it is not supported anymore
If magisk triggers your SafetyNet (Main reason why Google pay stops working) install the SafetyPatch module or Magisk Hide Props or check your SafetyNet. That will fix your safety net.
Don't use XPOSED, it will trigger safety net even if magisk hide working. Xposed modify Boot.IMG, the reason for the safety net to trigger. If you cant live without Xposed, use EDXPOSED magisk module, install Riru core, riru edxposed and Xposed installer that will not trigger your safety net (Please note: Android 5.1 Android 6.0 get bootloop because of EdXposed, sorry guys no luck)
Don't Update you GOOGLE PAY - google updates security patch, magisk too Update your Google pay rarely
Always update your magisk and try to download magisk from Github.
Check your Safety net and make sure your Selinux is in Enforcing Mode
???
If that helped you, you are welcome
thanks for this solution.
Regards
Ginifa
dviree said:
???
Click to expand...
Click to collapse
Not sure what is so funny?....
Not able to install
amelbeabk said:
That Google Pay image says your phone is rooted, but it says that as an example as what could have tripped off Safety Net.
Safety Net failing doesn't mean you a rooted. Safety Net is designed to fail if you have an Unlocked bootloader.
Click to expand...
Click to collapse
It sucks, but for things like Google Pay, I'd strongly suggest that you just give up. Google is contractually obligated to play this game with you and try to prevent you from using it on a rooted "insecure" device so they can process card payments.
I have moto G5+ with unlocked bootloader and magisk. Google pay works fine and saftey net does not fail if bootloader is unlocked
I have a custom rom. Only way to get Magist working was to install EdXposed and hide module. SafetyNet Test also says safetynet passes but my gpay doesnt want to work. Assuming its seeing edxposed perhaps. Anything else i can do
dk0dave said:
I have moto G5+ with unlocked bootloader and magisk. Google pay works fine and saftey net does not fail if bootloader is unlocked
Click to expand...
Click to collapse
I also have moto G5+, But still not unlock boothloader. I need study more for unlocked it, however this comment is helpful to get a decision for me, Thanks.
Tutuapp Movie HD Cokernutx
Google Play warns me to uninstall SELinux Changer, then shuts my phone down. I tried uninstalling it then rebooting, but the phone is behaving extremely oddly and shutting down by itself.
Now I have to format it, just to be sure.
murick_show said:
If you want to make your Google Pay work, make sure you followed those steps below
Use AOSP/LOS or OEM Based rom. MIUI 7 and 8 have problems with SafetyNet [Even if you have Magisk installed]
***MOST IMPORTANT***
[###ROOT###]
Check your Selinux Mode in the About Phone section in Settings.
Selinux is another Google Protection featured with Kitkat in 2014
If you have Permissive, change it to Enforcing using this app [Download Attached Files]
Reboot after applying Enforcing. Don't Delete Selinux Mode Changer, You will lose your Enforcing and will be switched back to Permissive
Use Magisk only - Don't use SuperSu, it doesn't have Hiding features and it is not supported anymore
If magisk triggers your SafetyNet (Main reason why Google pay stops working) install the SafetyPatch module or Magisk Hide Props or check your SafetyNet. That will fix your safety net.
Don't use XPOSED, it will trigger safety net even if magisk hide working. Xposed modify Boot.IMG, the reason for the safety net to trigger. If you cant live without Xposed, use EDXPOSED magisk module, install Riru core, riru edxposed and Xposed installer that will not trigger your safety net (Please note: Android 5.1 Android 6.0 get bootloop because of EdXposed, sorry guys no luck)
Don't Update you GOOGLE PAY - google updates security patch, magisk too Update your Google pay rarely
Always update your magisk and try to download magisk from Github.
Check your Safety net and make sure your Selinux is in Enforcing Mode
Click to expand...
Click to collapse
Hello, hope you can help, installed Beyond ROM and Thunderstorm kernel. Google pay not working, SE for Android status shows 'enforcing' when the apk is installed the 'permissions' and ''enforcing' tabs are greyed out. Thank you

Question Magisk & root hide for Google Pay for recent firmware update

What version of Magisk and what root hide (module name and version please) people have it fully working for Feb 2022 firmware update (840.2201.226), especially for Google Pay? Thanks
(I'd it all working on the previous firmware release just fine. Then right after applying the above mentioned Feb update, when I tried to execute Magisk (possibly 23.1) to patch the inactive slot, it just wouldn't execute let alone patch; nor would Termux "su" command would execute. So there was no way to patch Magisk over that update. Problem was made worse, when I executed LSPosed, which proceeded to update and auto rebooted the phone! Jumped from the frying pan into the fire.)
nexusnerdgeek said:
What version of Magisk and what root hide (module name and version please) people have it fully working for Feb 2022 firmware update (840.2201.226), especially for Google Pay? Thanks
(I'd it all working on the previous firmware release just fine. Then right after applying the above mentioned Feb update, when I tried to execute Magisk (possibly 23.1) to patch the inactive slot, it just wouldn't execute let alone patch; nor would Termux "su" command would execute. So there was no way to patch Magisk over that update. Problem was made worse, when I executed LSPosed, which proceeded to update and auto rebooted the phone! Jumped from the frying pan into the fire.)
Click to expand...
Click to collapse
Using Latest Magisk and Zygisk-Shamiko.
MagiskHide is no longer available - and Denylist is not effective.
For the patch - First Patch the Boot Image, then Install Magisk again over TWRP as well.
Thanks, I got Magisk 24.2 installed & working fine now.
(Things are super difficult as it is, so I've skipped trying to install/activate TWRP.)
However, Universal SafetyNet Fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases), though installs fine, gets disabled due to "Module suspended because Zygisk is not enabled".
I've confirmed that Zygisk (Beta) is activated in Magisk's settings. What am I missing?
Q: How to "unsuspend" Universal SafetyNet Fix module?
Thanks
(It's so difficult to keep up with all this work that I'm leaning towards relocking the boot-loader. I really don't use any app or feature to benefit from unlocked boot loader or root. I did it only to be ready for injecting mbn, which isn't needed or possible anyway. It was a bad decision then & remains so now. Though I don't know if while relocking the bootloader the phone will get bricked. Decision.. decision... With all the difficulty of keeping up with root, it sounds like a risk worth taking.)
Actually removing the Magisk APK and reinstalling it seemed to have helped. Termux works reliably for su. Gpay is good as well. Magisk log shows no funky messages.
In the end, I had to use this to overcome root detection on two banking apps: https://github.com/vvb2060/magisk_files/blob/alpha/app-release.apk
nexusnerdgeek said:
In the end, I had to use this to overcome root detection on two banking apps: https://github.com/vvb2060/magisk_files/blob/alpha/app-release.apk
Click to expand...
Click to collapse
What's that ?
Leads to a empty GitHub Page ...
Actually official Magisk 24.3 works well for all of the banking apps I need root hide for. So, there's no need for that unofficial alpha build anymore for me; in fact, I got rid of it. Please disregard that link.

Question Company Portal (InTune) detects root - anyone else?

I have zero interest in rooting my phone, but because 5G/VoLTE/VoWiFi are not supported in my country (Slovakia) I had to root it. After successful root, passing SafetyNet and pretty much make everything to work as expected, my Company Portal is detecting root when running Teams and Outlook provisioned by my Company Portal despite having them in DenyList. Is there anyone who managed to pass this?
Thank you.
Happened to me as well. I used Shamiko magisk module and it's all good now.
@chaos193, did you use Riru along?
Or maybe even better question if you don't mind - what modules are you using to successfully pass SafetyNet and hide root?
Can you list them one by one, please?
Either use Shamiko or MagiskHidePropsConf to mask additional properties. I can confirm that InTune Company Portal works fine with SafetyNetFix + Shamiko
p4ra said:
@chaos193, did you use Riru along?
Or maybe even better question if you don't mind - what modules are you using to successfully pass SafetyNet and hide root?
Can you list them one by one, please?
Click to expand...
Click to collapse
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
chaos193 said:
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
Click to expand...
Click to collapse
Quick question @chaos193 - I haven't updated Shamiko to 0.6 as the update states that it requires Magisk 25205+. Reckon that would be magisk canary? Or as you using 0.6 with Magisk stable?
WhoIsJohnGalt1979 said:
Quick question @chaos193 - I haven't updated Shamiko to 0.6 as the update states that it requires Magisk 25205+. Reckon that would be magisk canary? Or as you using 0.6 with Magisk stable?
Click to expand...
Click to collapse
I used it with magisk stable 25.2. I think we are all using magisk stable to root our phone right?
I have tried your suggestions, but still does not seem to work. Adding screenshots.
Can you help me, please? What is wrong with my setup?
Following steps work 100% - I had the same issue.
1. Use magisk canary.
2. Install universal safetynet fix MOD 2.0 from displax (Google for "displax github")
3. Use latest shamiko module
4. Activate zygisk
5. Don't enforce denylist
6. Go to denylist and chose all Microsoft apps and tick ALL options for each app.
7. Hide magisk app
I had issue with a specific banking app which detects root by most of the methods. I made it working by using shamiko + airfrozen which i was not really liking.
Now i wnded up with a forked project of magisk bu Husky called magisk delta which brought back magisk hide along with zygisk. With this i don't need shamiko, magiskpropshide, airfrozen or any modules for hiding the root from apps. Yes for safetynet you can use the modded veraion by D. Below is the link. If you are interested have a look at Magisk Delta by HuskyDG... I use the magisk delta canary builds...
I have made it work with first approach. I did a restart of the phone and it worked.
What I am wondering though is the following - I have used the VoLTE/VoWiFi/5G Magisk module, but I don't see the "HD" icon during the call, even though I can browse the internet (when I am not on WiFi). And despite 5G coverage of my current carrier in my area, I don't see 5G icon.
Is there any other module I am missing for this last piece of puzzle?
And last but not least. What scares me the most is that next OTA will completely screw me over after setting everything up. I wish there was a clear tutorial on how to OTA and keep the root without wiping everything out.
p4ra said:
I have made it work with first approach. I did a restart of the phone and it worked.
What I am wondering though is the following - I have used the VoLTE/VoWiFi/5G Magisk module, but I don't see the "HD" icon during the call, even though I can browse the internet (when I am not on WiFi). And despite 5G coverage of my current carrier in my area, I don't see 5G icon.
Is there any other module I am missing for this last piece of puzzle?
And last but not least. What scares me the most is that next OTA will completely screw me over after setting everything up. I wish there was a clear tutorial on how to OTA and keep the root without wiping everything out.
Click to expand...
Click to collapse
I'm not quite sure which VoLTE/VoWiFi/5G Magisk module you are referring to, but I believe enabling 5G requires modified mbn files specific to your country/region.
Regarding OTAs, there are two "How To" guides here with all the details you need.
Blaze1001 said:
Following steps work 100% - I had the same issue.
1. Use magisk canary.
2. Install universal safetynet fix MOD 2.0 from displax (Google for "displax github")
3. Use latest shamiko module
4. Activate zygisk
5. Don't enforce denylist
6. Go to denylist and chose all Microsoft apps and tick ALL options for each app.
7. Hide magisk app
Click to expand...
Click to collapse
I have done exactly this but it still detects
Oneplus 7 pro
LineageOS 19.1 Nov 27th nightly build
This should be all that's needed to pass the compliance checks for Intune
1. Magisk (Zygisk mode)
2. SafetyNet v2.3.1-MOD_2.0
3. Shamiko v0.5.1 (or higher)
4. Magisk deny-list for the following apps (without Enforce deny-list)
a. Company Portal (Intune)​b. Microsoft Authenticator (if you use it)​c. Microsoft Defender (if you use it)​5. Make sure you clear app data for the apps in the deny list after adding them to the deny list
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
craigacgomez said:
This should be all that's needed to pass the compliance checks for Intune
1. Magisk (Zygisk mode)
2. SafetyNet v2.3.1-MOD_2.0
3. Shamiko v0.5.1 (or higher)
4. Magisk deny-list for the following apps (without Enforce deny-list)
a. Company Portal (Intune)​b. Microsoft Authenticator (if you use it)​c. Microsoft Defender (if you use it)​5. Make sure you clear app data for the apps in the deny list after adding them to the deny list
Click to expand...
Click to collapse
s3axel said:
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
Click to expand...
Click to collapse
Still doesn't work. Its weird because it worked for one night and the next morning it stopped.
UPDATE: its LSPosed I think. But this is the only way to force dark mode on some apps....
UPDATE 2: I disabled forced dark mode on all Microsoft apps in LSPosed plugin and its looking good so far...
UPDATE 3: Had a full day with not a single root detection notification. Looks solid!
s3axel said:
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
Click to expand...
Click to collapse
one of the worse parts of it, if not the worst, is that nobody knows what it detects and there's no guide that applies to each and every device,
I tried in 3 devices, the exact same steps and files, etc, it worked on the 1st one, but on the other two.. no!
For all those who still got issues as another idea: Does Google Wallet work ? Is the device play protect certified ?
I ask because to get Wallet to work (and presumably other apps that rely on Safetynet and/or Play Protect certification) the additional step after #5 in the list above is: clear data for Google Play Services and Google Play Store, then reboot (your device will ask for Google backup configuration again).....
I got the same issue with an App called "SwissID". It recognizes magisk for some reason. All other Apps work (like banking, google wallet etc.)
chaos193 said:
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
Click to expand...
Click to collapse
Its work to me!!! Thanks

Question How to enable unlimited Google Photos storage on Stock ROM without destroying my system?

Well, It has happened twice already, and I had to reinstall the entire OS 3 times, let's not forget about having to update the phone and reconfigure it every time.
Anyway, I downloaded some Pix3lify magisk module or something like that, basically, after installing it and rebooting, my system is destroyed.
So the question is: How can I get unlimited Google Photos storage on Stock ROM without destroying my system?
rtkpX said:
Well, It has happened twice already, and I had to reinstall the entire OS 3 times, let's not forget about having to update the phone and reconfigure it every time.
Anyway, I downloaded some Pix3lify magisk module or something like that, basically, after installing it and rebooting, my system is destroyed.
So the question is: How can I get unlimited Google Photos storage on Stock ROM without destroying my system?
Click to expand...
Click to collapse
Try this: https://github.com/Xposed-Modules-Repo/balti.xposed.pixelifygooglephotos/releases/tag/5-4.1
This is called Pixelify too but it's different from what you've tried already. It's LSPosed module so you have to flash LSPosed first: https://github.com/LSPosed/LSPosed
And then spoof your device for GPhotos only as Pixel XL
By the way, many custom ROMs for bitra has that spoof included
Lord Sithek said:
Try this: https://github.com/Xposed-Modules-Repo/balti.xposed.pixelifygooglephotos/releases/tag/5-4.1
This is called Pixelify too but it's different from what you've tried already. It's LSPosed module so you have to flash LSPosed first: https://github.com/LSPosed/LSPosed
And then spoof your device for GPhotos only as Pixel XL
By the way, many custom ROMs for bitra has that spoof included
Click to expand...
Click to collapse
Yes, I know about the custom ROMs with that spoof included, but I'm using the Stock ROM and I don't want to switch to a custom one now, since a lot of features like the camera, google assistant, etc... don't work properly on other ROMs.
rtkpX said:
Yes, I know about the custom ROMs with that spoof included, but I'm using the Stock ROM and I don't want to switch to a custom one now, since a lot of features like the camera, google assistant, etc... don't work properly on other ROMs.
Click to expand...
Click to collapse
please share Custom Rom name and link
Instructions to get Unlimited Google photos backup on any rom without spoofing whole Device :
⭕️ Advantage of this method :
No other apps like miui cam etc will not be effected. And safety net also will not influenced.
Steps :
1) Install Latest Magisk and use magisk hide properly to make sure you passed safety net.
2) Install latest Riru magisk module. (https://github.com/RikkaApps/Riru/releases)
3) Install latest Lsposed magisk module.
Lsposed for Magisk Stable & Zygisk (https://t.me/LSPosedArchives)
Note if you are using Magisk with ZYGISK, you should use only Lsposed zygisk build (https://t.me/LSPosedArchives)
4) Reboot and make sure Lsposed status is active.
5) Install latest Pixelify Google Photos Module
(https://github.com/BaltiApps/Pixelify-Google-Photos/releases)6) Open Lsposed and enable Pixelify module, and select Google photos app in apps list.
Note: If you need pixel props to enable for any other app you can also select those apps, but make sure you disable "spoof only Google photos" toggle on pixelify module.
7) Reboot the device and open pixelify module.
• Set Device spoof to Pixel XL for Original Quality unlimited .
• Set Device spoof to Pixel 5 for Storage saver Unlimited.
8) Reboot the device and open Google photos app. that's it enjoy.
Pixelify GPhotos
Group rules: 1. Mild OT allowed as long as you are civil. 2. Hurt speech / flame speech = BAN. 3. English only 4. Any topic not related to "Pixelify GPhotos" will be warned, including how to install Magisk
t.me
SanOne+1 said:
please share Custom Rom name and link
Click to expand...
Click to collapse
Bananadroid
Project Elixir
Are some examples.
eliteforce said:
Instructions to get Unlimited Google photos backup on any rom without spoofing whole Device :
⭕️ Advantage of this method :
No other apps like miui cam etc will not be effected. And safety net also will not influenced.
Steps :
1) Install Latest Magisk and use magisk hide properly to make sure you passed safety net.
2) Install latest Riru magisk module. (https://github.com/RikkaApps/Riru/releases)
3) Install latest Lsposed magisk module.
Lsposed for Magisk Stable & Zygisk (https://t.me/LSPosedArchives)
Note if you are using Magisk with ZYGISK, you should use only Lsposed zygisk build (https://t.me/LSPosedArchives)
4) Reboot and make sure Lsposed status is active.
5) Install latest Pixelify Google Photos Module
(https://github.com/BaltiApps/Pixelify-Google-Photos/releases)6) Open Lsposed and enable Pixelify module, and select Google photos app in apps list.
Note: If you need pixel props to enable for any other app you can also select those apps, but make sure you disable "spoof only Google photos" toggle on pixelify module.
7) Reboot the device and open pixelify module.
• Set Device spoof to Pixel XL for Original Quality unlimited .
• Set Device spoof to Pixel 5 for Storage saver Unlimited.
8) Reboot the device and open Google photos app. that's it enjoy.
Pixelify GPhotos
Group rules: 1. Mild OT allowed as long as you are civil. 2. Hurt speech / flame speech = BAN. 3. English only 4. Any topic not related to "Pixelify GPhotos" will be warned, including how to install Magisk
t.me
Click to expand...
Click to collapse
it works. and there is a typo in the Pixelify Github link above, delete ")6" after release.
Thank You!

Categories

Resources