Related
It seems Android pay is blocking custom ROMS and root. Hiding the SU binary and pushing a stock build.prop dont seem to alleviate the situation. Does anyone know of a workaround that allows one to keep his root and/or ROM?
I saw this pic on reddit when a user asked google http://imgur.com/FVhQPTz
It uses the SafetyNet API.
Tried setting it up on a stock / signed ROM, went through fine. Tried to backup the app+data and restore it on a custom ROM. Saw my complete account screen for a split second before the 'add new card' window came back and wouldn't go away.
This would not surprise me. Don't be surprised if you can't get around it. Root is too much of a security risk for something like that
I'm not very good with hacks and workarounds but I tried this and it didn't work.
http://androiding.how/android-pay-with-root/#comment-779
Note 2/i317 AT&T/unlocked sim/CyanideL ROM v19/Shift Kernel 5.7
SafetyNet API - fix Android Pay issue with Root / Custom ROMS / xposed
New Last Night...
http://repo.xposed.info/module/com.pyler.nodevicecheck
No luck on a Moto X (2014)...anyone else having any luck?
Nope
No luck on Safteynet API, root cloak, disabling root aps, etc. LG G3 modified stock rom and kernel.
in SuperSU i just disabled SU, NOT unroot, and then it allowed me to add card. im stock rooted s5
Same here
I'm reading that "custom ROMs are missing some proprietary files that Android Pay relies upon"
http://android.wonderhowto.com/how-to/get-android-pay-working-rooted-device-0164604/
It may allow you to add the card, but when you re-enable SU, Pay will not go through when trying to use it.
Downgrade to an 8.x version of Google Wallet. All versions in the 9.x range were preprogrammed to disable themselves when Android Pay came out. I switched back to 8.0-R190-v25 that's preinstalled on my Nexus 5 and disabled automatic updates for Android Pay on the play store.
If you have something like Titanium Backup (which most would if they're rooted), you can also detach Wallet form the Market, meaning it shouldn't know to update it.
Okay, let me start off by saying I thought I could not give up root for Android Pay. I tried workarounds, e.g., temporarily disabling supersu, which let me add cards but wouldn't actually process payment at store.
I have a Nexus 5 on Sprint, with official 6.0 factory imgs installed. I have TWRP recovery and an (obviously) unlocked bootloader. While rooted, I flashed ElementalX kernel (allowing for double-tap to wake, swipe to sleep, and under-volting--3 features I can't live without), modified build.prop to allow multi-window mode, and ran ADB commands to enable tethering (courtesy of Reddit instructions).
I then completely uninstalled SuperSU and BusyBox (no easy task--had to delete system apks and reboot numerous times). I also had to delete su and busybox entries from system/xbin for unrooting. After a reboot, I successfully installed Android Pay, added credit card, and have successfully used it at several retail outlets. More importantly, my kernel DT2W/swipe to sleep/undervolting options still work, as does tethering and multi-window. Apparently AP doesn't check for build.prop or boot mods, nor does it check for bootloader state or stock recovery. I do miss quickboot options I had with root however.
If I absolutely need something that requires root, e.g., Titanium Backup restore, etc, I can just boot into TWRP recovery through old-school holding down power/ volume button technique (hence why I miss quickboot features), flash SU and BusyBox zips I have on internal SD, reboot, do my business, and then unroot like I did above. FWIW unrooting is MUCH more difficult than rooting, but still very doable once you figure out all the steps.
Can you post the steps for cleanup? I have been trying it myself and have had no luck with getting A-Pay to actually work correctly.
How do you stop updates from automatically applying?
Dankees said:
How do you stop updates from automatically applying?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74672462&postcount=5
This worked for me, but that was in the way back of 5.6.0, good luck!
Use a firewall, and block internet access to the two OTA apps. After go to Settings 》 Apps and look for the two OTA apps. Clear cache and data.
@Dankees
TechNash said:
Use a firewall, and block internet access to the two OTA apps. After go to Settings 》 Apps and look for the two OTA apps. Clear cache and data.
@Dankees
Click to expand...
Click to collapse
Huh? How do I use a firewall?
And, which two OTA apps?
Dankees said:
Huh? How do I use a firewall?
And, which two OTA apps?
Click to expand...
Click to collapse
Try NoRoot Data Firewall from the Play Store.
There are two apps that have "OTA" in the name. I forget the full name right now.
Dankees said:
....
And, which two OTA apps?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74672462&postcount=5
Hi all. I've successfully rooted my Fire 10 (2017) using retyre's excellent offline rooting guide. I never (and still have not) connected to wifi and sideloaded 5.6.2.0 from what was previously at 5.5.0.0
After root, I've installed Google Play Store with forum.xda-developers.com/showpost.php?p=77125897&postcount=80
Installed Xposed Framework Installer APK, but have yet to install the actual Xposed SDK because that requires an internet connection to retrieve the SDK. And I haven't downloaded a root file explorer yet, either.
Anyways, I've read and read before doing all these things, but there's one more thing to figure out before I finally connect to wifi.
What's the correct way to prevent Amazon from pushing a ROM OTA? I've seen 2 different implementations posted around the forums.
THIS:
TechNash said:
Use a firewall, and block internet access to the two OTA apps. After go to Settings 》 Apps and look for the two OTA apps. Clear cache and data.
Click to expand...
Click to collapse
OR
THIS:
bibikalka said:
Code:
adb shell
su
mount -w -o remount /system
mv /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk_
ls -l /system/priv-app/DeviceSoftwareOTA/
ignore any errors you may get while doing this; after 'su', you should see root (#) prompt here
Click to expand...
Click to collapse
bibikalka follows this up by saying this
bibikalka said:
How to install Xposed & Flashfire for easy backups and ROM updates
How to enable Amazon packages (apk) updates but prevent the ROM updates (keeping root & rootable rom).
1) Edit /system/build.prop and change ro.build.version.number to have "9" as the first value instead of "5", as recommended in this link
2) Reboot
3) Enable OTA by ensuring that /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk is renamed back to apk from apk_
4) Reboot
At this point the Fire will download a lot of apk packages, and will update Amazon system components (keeping FireOS version the same).
Click to expand...
Click to collapse
-Someone help explain why one is better than the other?
-Will setting up a firewall prevent Amazon's apps as well as system firmware from being updated?
-Is the firewall implementation equally as effective as changing the DeviceSoftwareOTA.apk to DeviceSoftwareOTA.apk_?
-Is changing the build number in /system/build.prop to 987654321 all we actually need to do to protect us from firmware updates?
I did my best to compile all my relevant questions in one lengthy post hoping that it will help someone else in the same position as I am somewhere down the line.
Jned said:
https://forum.xda-developers.com/showpost.php?p=74672462&postcount=5
This worked for me, but that was in the way back of 5.6.0, good luck!
Click to expand...
Click to collapse
This method worked for me after rooting using the offline root guide. When I go into System Updates and click check, it just says "Check for updates failed." It does require root, so make sure to use the "su" command before the others or it will give you an error. I am on 5.6.0.1 by the way.
Hylex said:
Hi all. I've successfully rooted my Fire 10 (2017) using retyre's excellent offline rooting guide. I never (and still have not) connected to wifi and sideloaded 5.6.2.0 from what was previously at 5.5.0.0
After root, I've installed Google Play Store with forum.xda-developers.com/showpost.php?p=77125897&postcount=80
Installed Xposed Framework Installer APK, but have yet to install the actual Xposed SDK because that requires an internet connection to retrieve the SDK. And I haven't downloaded a root file explorer yet, either.
Anyways, I've read and read before doing all these things, but there's one more thing to figure out before I finally connect to wifi.
What's the correct way to prevent Amazon from pushing a ROM OTA? I've seen 2 different implementations posted around the forums.
THIS:
OR
THIS:
bibikalka follows this up by saying this
-Someone help explain why one is better than the other?
-Will setting up a firewall prevent Amazon's apps as well as system firmware from being updated?
-Is the firewall implementation equally as effective as changing the DeviceSoftwareOTA.apk to DeviceSoftwareOTA.apk_?
-Is changing the build number in /system/build.prop to 987654321 all we actually need to do to protect us from firmware updates?
I did my best to compile all my relevant questions in one lengthy post hoping that it will help someone else in the same position as I am somewhere down the line.
Click to expand...
Click to collapse
The methods can be ranked in terms of update prevention:
1) DeviceSoftwareOTA.apk_ blocks anything an everything, forever and ever
2) build.prop version blocks FireOS ROM updates (no threat to root), but does not block individual Amazon apk updates for various packages, so something like Amazon store may still update
3) firewall method is intermittent, and often people complain that it would still update even with the firewall blocking - this one is absolutely not recommended
I will do the build.prop edit then. Thank you!
Hylex said:
Hi all. I've successfully rooted my Fire 10 (2017) using retyre's excellent offline rooting guide. I never (and still have not) connected to wifi and sideloaded 5.6.2.0 from what was previously at 5.5.0.0
After root, I've installed Google Play Store with forum.xda-developers.com/showpost.php?p=77125897&postcount=80
Installed Xposed Framework Installer APK, but have yet to install the actual Xposed SDK because that requires an internet connection to retrieve the SDK. And I haven't downloaded a root file explorer yet, either.
Anyways, I've read and read before doing all these things, but there's one more thing to figure out before I finally connect to wifi.
What's the correct way to prevent Amazon from pushing a ROM OTA? I've seen 2 different implementations posted around the forums.
THIS:
OR
THIS:
bibikalka follows this up by saying this
-Someone help explain why one is better than the other?
-Will setting up a firewall prevent Amazon's apps as well as system firmware from being updated?
-Is the firewall implementation equally as effective as changing the DeviceSoftwareOTA.apk to DeviceSoftwareOTA.apk_?
-Is changing the build number in /system/build.prop to 987654321 all we actually need to do to protect us from firmware updates?
I did my best to compile all my relevant questions in one lengthy post hoping that it will help someone else in the same position as I am somewhere down the line.
Click to expand...
Click to collapse
I said Firewall because he didn't have root. A non-root firewall works, but isn't the most reliable.
Since you have root, go ahead and delete those two apps altogether. Use something like Titanium Backup, and then uninstall the OTA Apps. Make a backup in case you ever want automatic updates again.
I'm working on porting "CIT test" application from MIUI to custom Android 11 ROMs (for calibrating proximity and fingerprint sensors), with end goal of creating a Magisk module. I'm stuck now with the application calling android.os.ServiceManager/addService, which fails with SecurityException -- I presume because I removed android:sharedUserId="android.uid.system" from its manifest, so it doesn't run with system app permissions. Currently I place it in /system/priv-app instead, which allows me to give it at least all the manifest permissions that it requires.
AFAIU, there is no way for me to simply use android.uid.system, as it requires one to sign the package with the same keys that were used for the ROM itself. As my idea is to have a general Magisk module, this is out of the question. However, because obviously I expect devices to be rooted (and can require Xposed), I want to find some way of circumventing signature check for this one package. Say, using Xposed to patch signature check, and to allow my public key to be used for android.uid.system apps. I don't want to completely disable signature checks, as this greatly compromises security.
I also thought of somehow using su to run this application as root, but apparently this is also not possible.
Is there a way to do this or something similar? Maybe I miss another way of implementing what I want? Any help or links are greatly appreciated.
I am curious about this too. It would help install the nReal nebula service on non-carrier devices and use nRreal Light AR glasses with the Nebula app.
Re-add the android.uid.system line
disable your Android Signature Verification
install with magisk to /system/app or priv-app
As the title suggest, I'm trying to bypass a root check for an app, more specifically MyMazda App. I have tried several different methods ( repacking Magisk, Root Cloak, LSposed/Xpirvacy, Unviersal SafteyFix Patch ). None seem to work, my bank, credit and stock exchange apps work completely fine along with every other app except this one. I'm running on a complete stock ROM.
I am running:
Oneplus 8 Pro
Android 11
OxygenOS 11.0.10.10.IN11AA
Magisk v24.1
This raised a few questions:
1. Is it even possible to bypass this apps root check?
2. If it is and when I do bypass it, will all the features work (ie. Remote Start/Stop, Remote Lock/Unlock, etc.)?
3. If there is no way, will downgrading Magisk to when MagiskHide was in the app?
4. And if I do need to downgrade, is there aspecific procedure for the Op8 Pro or is just like any other phone?
Sidenote: I am very new to this, I only just rooted my phone 2 days ago, without any issues thankfully, so I may have missed something important to one of the modules for it to work. Thank you in advanced!
Checking whether Android is rooted or not basically requires only 1 line of program code.
xXx yYy said:
Checking whether Android is rooted or not basically requires only 1 line of program code.
Click to expand...
Click to collapse
Interesting, then how come this app is causing so much issues compared to my banking apps and such?
Hi, I use root in all my devices from a lot of time but now I'm 41yo and no more interested in this.
I use root "now only" for
1) call recording (BCR);
2) SwifthBackup;
3) Revanced.
So, call recorder seems to be installed also without root: just put apk in system app directory!
... but, how I can move an apk in system directory without root or twrp, and with locked bootloader?
SwifthBackup can work without root? I don't remember but I can search.
Revanced isn't a problem, I can use with microG.
----
Any help about my doubts?
I want try also because VPN not work, and after a months of email with support "seems" can be related to unlocked/rooted device.
I want just try.
Ty.
Without root, Swift Backup can backup app APK files, but not the app data. It does allow you to grant adb permissions through Shizuku, but I never figured out what [if anything] that allows it to do. I wasn't able to backup app data with ADB privelages.
I don't know the answer to the Call Recording issue.
lupastro82 said:
Hi, I use root in all my devices from a lot of time but now I'm 41yo and no more interested in this.
I use root "now only" for
1) call recording (BCR);
2) SwifthBackup;
3) Revanced.
So, call recorder seems to be installed also without root: just put apk in system app directory!
... but, how I can move an apk in system directory without root or twrp, and with locked bootloader?
SwifthBackup can work without root? I don't remember but I can search.
Revanced isn't a problem, I can use with microG.
----
Any help about my doubts?
I want try also because VPN not work, and after a months of email with support "seems" can be related to unlocked/rooted device.
I want just try.
Ty.
Click to expand...
Click to collapse
I imagine that, once you move that .apk to the system app directory (while rooted), once you unroot, it should still stay there and probably be accessible; but I'm unsure whether successfully running it will be possible -- it depends on the call recording app and if the app requires root to run. If it doesn't and it simply needs root just to be inserted, then I imagine it would probably work if you unroot.
But I have never heard of this method of getting a mod or add-on to work by inserting it in the system app directory...it's fascinating...
Like you said, ReVanced doesn't necessarily need root to work; it just works better with it. Swift Backup will only in a basic way be able to back your device up without root access.
But if you are simply just trying to get a certain VPN to work -- and in the end you don't want to lose root -- you could try doing the numerous root-hiding methods. There are many games, banking apps, and streaming apps that won't work with root (without even giving you a warning that it's because of root detection sometimes) that, once you hide root successfully, are able to run it. It sounds like that could possibly be the case for your VPN.
There are these you can try (if you haven't yet); Zygisk Deny List, UniversalSafetyNetFix (Displax mod works best with P7P), Shamiko, HideMyApp, Magisk Delta, etc.
Also, please be aware (or reminded if you know already) that while unrooting will not wipe and reset your device, locking your bootloader requires wiping the device and you losing everything! You'll be able to get some stuff restored through Google One Backup/Sync, but most everything will need to be set back up and/or lost. And if all you are seeking is to get a VPN to work, I really highly doubt that the app/service goes so far as to detect if you have an unlocked bootloader; it seems there are some banking apps that go that far, but most apps out there don't go that far, and hearing a VPN does would be a first...
Good luck!
Just Google VPN. Do not work anymore from about two months and seems can be a root/unlocked issue.
Anyway, u're right. Ty so much.