Play Store Protect Certification - Google Pixel 5 Questions & Answers

After unlocking bootloader and flashing Magisk-patched boot.img, says "device is not certified". Would this cause any trouble in the future or even now? I can download apps so seems like it's nothing to worry about, just wanna make sure.

That's a standard message that comes up on any Android phone starting since Marshmellow I think? But no that screen is nothing to be concerned about, just showing that your bootloader has been unlocked.

ColdFyre33 said:
After unlocking bootloader and flashing Magisk-patched boot.img, says "device is not certified". Would this cause any trouble in the future or even now? I can download apps so seems like it's nothing to worry about, just wanna make sure.
Click to expand...
Click to collapse
Not much to worry about but if you wipe data and cache on pstore then reboot, it will usually certify

As previously already stated, just force close and delete app data + cache from the play store app, reboot, and it should show as certified (only if safetyNet previously already passes of course!). Keep in mind that after rooting, you need to enable the HideProps module in Magisk to force basic attestation by emulating an older device (e. g. a Pixel 3a). Otherwise safetyNet will fail and your device won't certify.

Related

Getting Safety Net to Pass Again After Uninstalling Xposed?

After installing Xposed I realized its current functionality isn't what it used to be so I uninstalled it to restore the ability to pass Safety Net, and it fails both the ctsProfile and basicIntegrity checks. What do I need to do to fix that?
I have Magisk 14.3 installed on a ZTE Axon 2017U, Android 7.1.1, if any of that is relevant.
Cyrus D. said:
After installing Xposed I realized its current functionality isn't what it used to be so I uninstalled it to restore the ability to pass Safety Net, and it fails both the ctsProfile and basicIntegrity checks. What do I need to do to fix that?
I have Magisk 14.3 installed on a ZTE Axon 2017U, Android 7.1.1, if any of that is relevant.
Click to expand...
Click to collapse
You shouldn't have to do anything else - I just tested, and just unchecking Xposed in my Magisk modules list and rebooting was all it took to get SafetyNet completely passing again. No other mods or alterations to /system that might have made it angry?
Xposed triggers SafetyNet, period. There's a Xposed module to pass the CTS profile check but you can't fully pass SafetyNet with Xposed active.
Jaitsu said:
You shouldn't have to do anything else - I just tested, and just unchecking Xposed in my Magisk modules list and rebooting was all it took to get SafetyNet completely passing again. No other mods or alterations to /system that might have made it angry?
Click to expand...
Click to collapse
I didn't have it installed as a module, I had it installed separately. I have it uninstalled now. I don't know what else I could have done to cause Safety Net's check to fail.
Didgeridoohan said:
Xposed triggers SafetyNet, period. There's a Xposed module to pass the CTS profile check but you can't fully pass SafetyNet with Xposed active.
Click to expand...
Click to collapse
I have it uninstalled completely. Any ideas what residual changes could cause this issue?
Cyrus D. said:
I didn't have it installed as a module, I had it installed separately. I have it uninstalled now. I don't know what else I could have done to cause Safety Net's check to fail.
I have it uninstalled completely. Any ideas what residual changes could cause this issue?
Click to expand...
Click to collapse
Ah... I didn't first understand you had uninstalled it in an attempt to pass SN.
Try a dirty flash of your ROM/factory image/firmware package.
Don't forget to uninstall the Xposed installer.
Just want to update that I got it working by running the uninstaller again from TWRP. Apparently the in-app "recovery" uninstallation didn't work properly despite reporting it did.
Edit: I just realized that Netflix was not updating because of it detecting Safety Net checks failed. That company is disgusting. It's locked to 720p outside of systems that have newer DRM, meaning on a PC you have to use Microsoft Edge, nothing else will work. And even then you can't get over 1080p unless it's attached to a certified DRM machine/qualified TV, and has a latest generation Intel chip for more built-in hardware DRM. I wish I was making this up, and I wish I knew that before I was paying for a "4K" account.
Cyrus D. said:
Just want to update that I got it working by running the uninstaller again from TWRP. Apparently the in-app "recovery" uninstallation didn't work properly despite reporting it did.
Edit: I just realized that Netflix was not updating because of it detecting Safety Net checks failed. That company is disgusting. It's locked to 720p outside of systems that have newer DRM, meaning on a PC you have to use Microsoft Edge, nothing else will work. And even then you can't get over 1080p unless it's attached to a certified DRM machine/qualified TV, and has a latest generation Intel chip for more built-in hardware DRM. I wish I was making this up, and I wish I knew that before I was paying for a "4K" account.
Click to expand...
Click to collapse
So actually you mean there was no SafetyNet pass after installing with Xposed uninstaller? Did you eventually fixed it? I guess it's a matter of deleting a few leftover files. Can you point out which files you've deleted (if any) and their storage path1? However, I think you can check these out by looking into the actual Xposed framework zip...
Sent from my Z2 Play using XDA Labs
The Analog Kid said:
So actually you mean there was no SafetyNet pass after installing with Xposed uninstaller? Did you eventually fixed it? I guess it's a matter of deleting a few leftover files. Can you point out which files you've deleted (if any) and their storage path1? However, I think you can check these out by looking into the actual Xposed framework zip...
Sent from my Z2 Play using XDA Labs
Click to expand...
Click to collapse
I actually don't remember much of anything, I switched to a Galaxy S9+ a long time ago and haven't looked back. I thought it'd be intolerable being on a locked device, but so far most functionality seems to work. With ADB commands most things more or less work, such as Greenify. Too bad I can't uninstall all the bloatware (using ADB commands to uninstall them just result in them being reinstalled on reboot).
This is kind of unfortunate for me because now I plan on sticking with Samsung devices, which are usually insanely priced and I have a real beef with Samsung. I got mine on a special promotion for getting $50 contract instead of a $40 one, + $25/m for 24 months for the phone. So $600 for the phone and an extra $120 which I wouldn't have paid otherwise (in Canadian dollars) but I do get some useful functionality out of it so whatever.

Apps refuse to start because phone being rooted but it isn't!

At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.
Use Magisk I guess? Use it to hide root from that app.
Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.
ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs
Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?
I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).
ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...
Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid
Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?
After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...
probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.
Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.

Lost root after Cache wipe, and forever lost device certification

I have a Nexus 6 stock and would like to share my recent experience with the community about what happened to me yesterday.
I installed Magisk 16.7 at the beginning of August and finally I was able to hide all apps from root, including Android Pay which said I was allowed to pay contactless. Hooray!!!
Yesterday something odd happened. I had troubles with my battery stats so -long story short- I chose to wipe the cache from stock recovery.
Upon reboot, Magisk lost root. I had a copy of the Magisk zip file handy so I booted TWRP and flashed the zip. Did not work.
So I spent my entire evening applying OTA N8I11F then flashing either Magisk zip or the patched boot image, but without success. Magisk was never enabled.
Only after wiping cache, reflashing OTA, deleting /data/su.img via TWRP, deleting the entire Magisk app with its settings and reflashing the patched boot image I was able to get Magisk to work again.
I am sure I didn't "dirt" the OS by running the steps above in their order in Flight Safe mode.
But now it looks like my phone is like doomed forever. Despite I applied MagiskHide to all apps except the ones I want to be root-enabled, Play Store reports my device as "not certified".
Android Pay does not start, demanding an update to Google Pay. But Pay is now incompatible with my device and won't download. (I think Google Pay is an upgrade to the Android Pay app)
At the moment I can still find Netflix, since Netflix won't appear on rooted devices for listing.
Today I was looking into SafetyNet and my attention was caught by:
Device Status Value of "ctsProfileMatch" Value of "basicIntegrity" Certified, genuine device that passes CTS true true Certified device with unlocked bootloader false true Genuine but uncertified device, such as when the manufacturer doesn't apply for certification false true Device with custom ROM (not rooted) false true Emulator false false No device (protocol emulator script) false false Signs of system integrity compromise, such as rooting false false Signs of other active attacks, such as API hooking false false
Click to expand...
Click to collapse
I don't know if this existed before and if Magisk Hide can hide the bootloader status to Play apps.
I am confused. Has something changed very recently? SafetyNet test reports failure despite it reported success in the past.
Anyone found this happening too? Any ideas on how to restore Pay?
Have you tried wiping data of pay, play store and play services?
Also, I think there's a magisk module for editing build props so eventually that could be used or modified for unlock status - yet that's just a speculation by me...
Gesendet von meinem Moto G (5) Plus mit Tapatalk
For Certifying The Device & Pass The SafetyNet, Check This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435.
gothicVI said:
Have you tried wiping data of pay, play store and play services?
Click to expand...
Click to collapse
Luck that worked. I didn't delete play services' data as I was afraid it would have deleted my accounts and SMSes.
Device is now certified. Android Pay does not demand me any update, asks me for adding cards.
Google Pay still unsupported. Not a problem.
Okay, problem solved.
Fiuuuuuuuuuuuuuuuuu
I have a similar problem too when I root from magisk The phone said me "Data partition corrupted" and I choose reset button but I was aiming root without data loss but my root hadn't gone to anywhere but my phone was unable to pass safetynet after a long time I tried to delete cache to accelerate my phone but when I opened my phone I got error messages from my root apps and when I tried to open magisk it stucks in magisk logo.I still can't pass safetynet too :crying:
igalhan said:
I have a similar problem too when I root from magisk The phone said me "Data partition corrupted" and I choose reset button
Click to expand...
Click to collapse
From what you are saying your problem seems to be with dm-verity/dm-verify, which MUST be disabled on devices that enforce it. In my experience with a Samsung phone I always got my system reset until I explicitly disabled dm-verify in the boot image. I didn't have to disable mandatory encryption, which is one of the security features I like the most in Android OS.
Regards.
djechelon said:
From what you are saying your problem seems to be with dm-verity/dm-verify, which MUST be disabled on devices that enforce it. In my experience with a Samsung phone I always got my system reset until I explicitly disabled dm-verify in the boot image. I didn't have to disable mandatory encryption, which is one of the security features I like the most in Android OS.
Regards.
Click to expand...
Click to collapse
Ok but I reseted my phone and it fixed could it be about forced encryption
---------- Post added at 05:16 PM ---------- Previous post was at 05:15 PM ----------
djechelon said:
From what you are saying your problem seems to be with dm-verity/dm-verify, which MUST be disabled on devices that enforce it. In my experience with a Samsung phone I always got my system reset until I explicitly disabled dm-verify in the boot image. I didn't have to disable mandatory encryption, which is one of the security features I like the most in Android OS.
Regards.
Click to expand...
Click to collapse
I didn't installed twrp it's from odin

Im rusty, mr 0 , 2 ,3 ?

No rom dev.
Can't get magisk in.
Dk magisk anyways
Xposed is doa? Or past it's prime.
Ok, how to gain root? Flash kernel which won't flash? Ow.
ǀcey said:
No rom dev.
Click to expand...
Click to collapse
Uh... you can try GSIs on this phone after unlocking bootloader. Most of the phone's functionality work with GSIs at the moment.
ǀcey said:
Can't get magisk in.
Click to expand...
Click to collapse
Recently Magisk has changed its way of distribution so there's only an apk now. But if you rename the Magisk apk into a zip, you can then flash it from TWRP (which you can access by flashing arter97's kernel).
ǀcey said:
Dk magisk anyways
Click to expand...
Click to collapse
Nowadays if you're to root the most ideal approach would be Magisk, which allows you to modify the system without directly touching the system partition, as well as hiding its presence from certain sensitive apps so Safety Net can still pass.
ǀcey said:
Xposed is doa? Or past it's prime.
Click to expand...
Click to collapse
If you're saying it's past prime... in some aspects, yes, thanks to the fact that you can't have both Xposed and Safety Net passing at the same time.
Still, if you're interested, you may consider looking for EdXposed or LSposed. I haven't tested it myself as I don't really have a use case at the moment, but these might be useful.
ǀcey said:
Ok, how to gain root? Flash kernel which won't flash? Ow.
Click to expand...
Click to collapse
You mostly need to just unlock bootloader following official instructions. After that you can proceed to flash kernels and GSIs through fastboot.
PS: I think this thread should best be posted in the Q&A forum...
EDIT: Just noticed your other post. If that was your real question... well, you were in the stock recovery and not the bootloader so fastboot commands obviously won't work there.
To enter bootloader, power it off, hold VOL- and POWER buttons until you see something like "Restart Bootloader", then you should be able to use fastboot.
Thank you, for all of your information!
It helped me by heaps!
The biggest problem I was having, was thinking the phone was in fastboot when it wasn't.
When I figured that out, the phone was quickly up n running on Phh-Treble with GApps Gsi.
Magisk Manager vs apk uses were confusing. It's Modules I can more easily blindly understand due to knowing XPosed.
Magisk went in smoothly & successfully via the change extension fastboot method which you explained.
But it appears the same as before inside the OS It's there but not really in type of thing.
Everything but the f2fs file and Magisk did complain.
I have no idea what kernel actually made it in now.
Safetynet! Hahaha! Is a new thing for me.
My phone is PlayStore bonafide uncertified also now.
PlayStore, I tried some other gapps nothing really changes, it just reupdates back to where it was, if it does, anyways(I think).
I tried registering device too. Failed that!
Being Uncertified = no netflix, no bank apps(deal breakers to me). GPhotos 1/2-ish working. Gvoice, Gmail working great! Razer Themes.apk + Pandora disappeared. I miss Razer Themes Lockscreens alot! Razer gives only a play link.
I installed older Netflix & Bank app. Both working.
Play ignores netflix but updated Bank. The same Bank app did stop working on a deemed outdated device in the past. It's not Chase but close.
I did try hiding things from the launcher via an other installed launcher.
An old Selinux(sp?) showed set to permissive. I changed to enforced, rebooted and it appeared to stick.
I installed Greenify(old) and stopped everything then did my monthly banking business, paid, xferred, etc. All transactions were confirmed. Boot still unlocked.
Soon afterwards, I installed Aptoide which informed me of root.
The Gsi's package Installer, won't install anything from within Es(I'm a diehard Es file manager user). The built-in file manager must be used to call the installer. The built-in file manager also crashes when searching.
A buggy installer I can deal with. Banking without it's app, I can not.
A halfbaked PlayStore is doable but not ideal.
The gsi itself on a RP2 is beautiful. The darks darker. The flashlight toggle works now! The fingerprint sensor never worked, still doesn't. 120fps, few games bake that capablity in. I haven't tested yet. No sound in Wyze app.
I recommend having your fav most used .apks dled before leaping onto it.
First boot was loud! Be prepared!
Then nothing.
2 days later, I noticed all alarms & notifications were set to silent sound.wav.
Idk, where to go from here. Stick to where it is now & wait for fixes. Go back. Or to go patch crazy if I can manage to get Magisk in.
I'm happy enough where it is now and it feels pretty secure. Will relocking the bootloader wipe it? The adult in me thinks.
But! I love tweaking...zzz
Relocking undoes it
LSS4181 said:
Uh... you can try GSIs on this phone after unlocking bootloader. Most of the phone's functionality work with GSIs at the moment.
Recently Magisk has changed its way of distribution so there's only an apk now. But if you rename the Magisk apk into a zip, you can then flash it from TWRP (which you can access by flashing arter97's kernel).
Nowadays if you're to root the most ideal approach would be Magisk, which allows you to modify the system without directly touching the system partition, as well as hiding its presence from certain sensitive apps so Safety Net can still pass.
If you're saying it's past prime... in some aspects, yes, thanks to the fact that you can't have both Xposed and Safety Net passing at the same time.
Still, if you're interested, you may consider looking for EdXposed or LSposed. I haven't tested it myself as I don't really have a use case at the moment, but these might be useful.
You mostly need to just unlock bootloader following official instructions. After that you can proceed to flash kernels and GSIs through fastboot.
PS: I think this thread should best be posted in the Q&A forum...
EDIT: Just noticed your other post. If that was your real question... well, you were in the stock recovery and not the bootloader so fastboot commands obviously won't work there.
To enter bootloader, power it off, hold VOL- and POWER buttons until you see something like "Restart Bootloader", then you should be able to use fastboot.
Click to expand...
Click to collapse
I have one of the faulty charging ports so cannot do anything with USB. I do have my bootloader unlocked so is there any way to get the gsi's, twrp and root onto the phone via SD card? Any help is appreciated.

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!

Categories

Resources