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.
Trying to restore a backup made with MyBackup again. And again, it isn't working. This happens every time I need to do a restore, and every time it's a different problem. At some point, it oughta work flawlessly
So I've got MyBackup Pro, latest version. I've got root access (enabled, activated, allowed, etc) and BusyBox. My phone is a Galaxy S7 with LineageOS 14.1 (see further for details).
When I restore any app, any app at all, I get in the "restore summary" screen, a message for each restored app, for example for the app "9292":
Code:
9292: Failed: cp: can't create '/data/app/nl.negentwee-2/nl.negentwee.apk': Path does not exist
(I mean, isn't it MyBackup's job to create it when it doesn't exist?...)
Details:
Device model: SM-G930F
Android 7.1.2
LineageOS version 14.1-20171213-NIGHTLY-herolte
LineageOS API level: Guava (7)
Security patch level: 5 december 2017
Kernel: 3.18.14-gadb2bc5
SELinux status: enforcing
Root access is enabled, allowed for MyBackup, and definitely working. BusyBox is installed (both the app, and the binaries of course), and probably working (don't quite know how to test).
I'm not sure what else could be wrong, so I'm guessing some sort of bug, maybe.
I can try rootless restore, and it'll probably work, but more important than restoring the apps, is restoring the data, which requires root, afaik. So, rootless isn't a viable workaround, just in case you were going to suggest it
Also note that this is a totally fresh installation. I've only installed 3 other apps, but haven't done any level of tweaking at all yet.
One thing I've tried is this:
I've created the `/data/app/nl.negentwee-2` (as in the example above) directory manually in Root Explorer. And then tried the restore again. Then what happens, is it says "Data not restored: App not installed".
This is true, the app isn't installed. But it's MyBackup's job to do that, isn't it?... Also when I go have a look in that directory, I do see an apk file there. So it was installed but not quite? Or what?
Okay, I removed the default LineageOS root (that one) and installed the latest SuperSU. That one app at least, now restores perfectly fine.
So I wonder, where's the bug? Is it in MyBackup, in addonsu from LineageOS, or in LineageOS itself?
Okay, I removed the default LineageOS root (that one) and installed the latest SuperSU. That one app at least, now restores perfectly fine.
So I wonder, where's the bug? Is it in MyBackup, in addonsu from LineageOS, or in LineageOS itself?
I have this issue on a Pixel 3 rooted with Magisk. MyBackup Pro was granted superuser rights. Did you ever discover any more about the root cause?
My post in Pixel 3
thany2 said:
Trying to restore a backup made with MyBackup again. And again, it isn't working....
When I restore any app, ...I get in the "restore summary" screen, a message ...:
Code:
9292: Failed: cp: can't create '/data/app/nl.negentwee-2/nl.negentwee.apk': Path does not exist
....SELinux status: enforcing....
Click to expand...
Click to collapse
posting here on seeing @timg11's post quoting your post; fwiiw: when i flashed a new rom (06-apr build) on x00td device, there were issues like the ones you faced. even in twrp, @osm0sis's busybox (latest module) wouldn't get flashed. i gathered it was due to selinux being set to enforcing by default. so, i flashed 'magisk-permissive-script_v1.2.zip' got from elsewhere and the issue got resolved.
Hello all, long time member but never really had a reason to post.
I just received my oneplus6, I wanted IOS style emojis (ridiculous I know... lol) So I unlocked bootloader, flashed the temporary TWRP release and flashed MAGISK.
When I booted my phone the error "There's an internal problem with your device contact your device manufacturer" comes up. Unfortunately I took my nandroid backup AFTER installing MAGISK.
I have no wifi at all, I can't use wifi hotspot either, but cellular works. I wanted to flash back to stock recovery but it seems oneplus hasn't released it. I have tried removing magisk and rebooting (via the magisk app) but then the device wont boot.
I canno't flash a stock copy of OxygenOS as it seems it can only be flashed with stock oxygen oneplus6 recovery (which I cannot get access to.) TWRP simply fails to flash it.
Recently in an attempt to solve my issue I formatted the memory, magisk has gone from my app drawer, but the effects it had are still there (I still have IOS emojis) Now apps wont login (snapchat for example says there is a temporary error) Facebook managed to login after a few reboots, I cannot stream video at all. And as I have formatted memory the original nandroid backup (after magisk flash where apps would login but still gives the internal error message and no wifi) is gone.
I really just want to get the device back to a stable operation, if anyone knows what I should do next or somehow has access to stock oneplus6 recovery, please let me know! Thankyou in advance for all help.
Find post with stock fastboot ROMs, download it and extract, then run flash-all.bat while phone is in fastboot
But data will be gone
DalekExt said:
Find post with stock fastboot ROMs, download it and extract, then run flash-all.bat while phone is in fastboot
But data will be gone
Click to expand...
Click to collapse
you mean this?: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I just did this and it has bricked the phone lol, it fails when I try to complete it
Bricked
19kylegreer96 said:
you mean this?: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I just did this and it has bricked the phone lol, it fails when I try to complete it
Click to expand...
Click to collapse
Hi,there is un-brick tool available
I would just like to guide anyone who might be having the same issue as me, to this post:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
And take note of what I said here about Large address aware ( to make this fix work on 64bit PC):
https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
Using the BAT file in that post that I have linked and the large address aware fix, my problem is fixed and I have now booted the phone and have working wifi!
If you run into that issue next time, just remember to install the provided boot image within TWRP, along with the other zip files to get TWRP to not lag. I had the exact same issues as you and I realized I missed the step of flashing the boot.img within TWRP.
Once I did that, I had working TWRP and WiFi!
I received the same message after rooting. However, everything is working well (wifi, 4G/LTE/camera, etc) except this message [There's an internal problem with your device. Please contact your adminstrator] during start-up.
Whenever I have seen this I just flash the same version of the original rom over my install and it fixes it.
I also notice that for me, Magisk 6.6 causes this, whereas 6.4 does not.
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
MickyFoley said:
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
Click to expand...
Click to collapse
Going from memory so I might not have it straight but I want to say this was from installing either twrp on just 1 partition or Magisk on the inactive partition. Making 16.4 and 16.6 works perfectly with stock kernel since already 5.1.6 for me as I've had this phone since launch.
It was all working without a problem - just the message popped up. Altering something in the kernel triggered this to happen. @eng.stk got this issue explained by another user, pointing to the Git from sultanxda. Since then, it was solved. Dunno. Had this in the very beginnings and since then never again. Well... Yeah
Thanks
MickyFoley said:
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
Click to expand...
Click to collapse
Thank you. That worked fine. I flashed [KERNEL] [blu_spark r31 OP6] [OOS 5.1.*] and the Error-Message is gone.
Installing a custom kernel fixed the issue for me as well.
Magisk fully working now as well as safetynet.
Might want to to edit the title to *fixed* so people know you resolves your issue.
Q: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"
A: This is caused by dtbo image patched to remove AVB 2.0 of the vendor partition. This is required for allowing you to mount vendor to rw and make modifications
If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app.
JerryGoyal said:
Q: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"
A: This is caused by dtbo image patched to remove AVB 2.0 of the vendor partition. This is required for allowing you to mount vendor to rw and make modifications
If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app.
Click to expand...
Click to collapse
Great, it worked!!!! It solved the scary message pop-up and kept the root. Thanks!!!
Hi!
This morning I ran into some trouble while running the Android Q Open Beta rom that I've been using since release. I have downloaded and flashed the zip of the open beta with TWRP recovery and flashed Magisk afterwards. After the install was complete I booted in to Android Q and checked Magisk Manager to see if it installed correctly, which it did. I have some apps like Pokémon Go that require Magisk hide and they also worked fine for days. Until today, out of the blue Magisk Hide didn't seem to work anymore and those apps knew the devices was rooted.
I have then tried to:
1. reflash Magisk (although it was still installed)
2. reinstalled Magisk Manager
3. Reapplied Magisk Hide for those apps and rebooted
Between every step I also removed cache and data from the applications (even reinstalled), however I couldn't get the hide the root for the apps.
Anyone else encountered this? It's strange that it only failed after a few days of working on Android Q. Anyway I'm back on Android P at the moment.
Did you try updating magisk in magisk manager? I wasn't passing safety net until I did so
ConsoleHax said:
Hi!
This morning I ran into some trouble while running the Android Q Open Beta rom that I've been using since release. I have downloaded and flashed the zip of the open beta with TWRP recovery and flashed Magisk afterwards. After the install was complete I booted in to Android Q and checked Magisk Manager to see if it installed correctly, which it did. I have some apps like Pokémon Go that require Magisk hide and they also worked fine for days. Until today, out of the blue Magisk Hide didn't seem to work anymore and those apps knew the devices was rooted.
I have then tried to:
1. reflash Magisk (although it was still installed)
2. reinstalled Magisk Manager
3. Reapplied Magisk Hide for those apps and rebooted
Between every step I also removed cache and data from the applications (even reinstalled), however I couldn't get the hide the root for the apps.
Anyone else encountered this? It's strange that it only failed after a few days of working on Android Q. Anyway I'm back on Android P at the moment.
Click to expand...
Click to collapse
What version of magisk did you install? Try the magisk canary (debug) build. Works like a charm.
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
bitblocksplicer said:
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
Click to expand...
Click to collapse
Which ROM are you actually running?