We have a nice little discussion going in the Development section. The 1.2 root / APK enabler is now available and ready for testing. Let me know what you think, and what you'd like to see done in the future. It's all down-hill from here.
http://forum.xda-developers.com/showthread.php?p=13212931#post13212931
I’m having problems
I am unable to get the apk files to run on my nook color.
I was at some point able to install apk files from the browser.
I had so other issues and had to start over from scratch. After doing so and running the new version now when I download the apk files from the browser it tells me it is an unrecognized file and does nothing with it. Everything else seemed to work with the patch but the key feature.
Im running truepure Rom. Would love to have android pay working, but just cant get it going. Assuming will have to live without for a while...
I have it installed on the stock rooted MM (soak test) and my card is loaded. I have not had a chance to actually use it yet. There aren't many retailers that accept it yet. If I get a chance to use it I'll report back.
rsmiff said:
I have it installed on the stock rooted MM (soak test) and my card is loaded. I have not had a chance to actually use it yet. There aren't many retailers that accept it yet. If I get a chance to use it I'll report back.
Click to expand...
Click to collapse
As I understand, Android pay pretty much only works works with stock ROM due to system system Partition Modifications made on custom Rom's. I understand some devices have had limited luck with Custom Roms but for the most part, Stock only. All that said, I just upgraded to MM 6.0 on Friday and then Rooted using the Beta System less Root method from the forum and Android Pay works like a charm, added cards no problem and works perfect at the retailers that accept it. Most recently, RiteAid in my area. This root is not a full root as I understand but the apps I use get permissions without an issue , Quick Boot is my must have and it works just fine. (Did notice ES File Explorer wont' allow full access to my device but Root Browser did. Adding XPOSED would still disable Android Pay since it modifies the partititons , I really wish that was not the case but I really love Android pay so for now, I might just have to do without it. I am sure you saw the Root Method but just in case, the link is below. Follow the instructions carefully and don't forgot to hit the Do Not Install button in TWRP (Your device does not appear to be rooted) every time you reboot from there . You'll know what I am talking about as soon as you get to that point.
Anyway, good luck!
Mike
http://forum.xda-developers.com/moto-x-style/development/wip-systemless-root-t3263405
EDIT: And I broke pay somehow... So I guess this is not a great guide...
I am having Android pay working on a slightly modded stock rooted MM.
- I did the OTA process (back to stock and side loaded the OTA)
- Installed and setup Android Pay (including cards)
- Installed TWRP 2.8.7.1 in fastboot (link)
- Rooted with Chainfire's systemless autopatcher (link)
- Renamed system\recovery-from-boot.p to .bak in TWRP
- Installed No increased ringtone in TWRP (link)
- Installed and setup AdAway
- Android Pay is still working, I tested it at the vending machine at work.
I have not tried to add the new Google dialer (link), someone in the thread say it doesn't break Android pay.
timeToy said:
I am having Android pay working on a slightly modded stock rooted MM.
- I did the OTA process (back to stock and side loaded the OTA)
- Installed and setup Android Pay (including cards)
- Installed TWRP 2.8.7.1 in fastboot (link)
- Rooted with Chainfire's systemless autopatcher (link)
- Renamed system\recovery-from-boot.p to .bak in TWRP
- Installed No increased ringtone in TWRP (link)
- Installed and setup AdAway
- Android Pay is still working, I tested it at the vending machine at work.
I have not tried to add the new Google dialer (link), someone in the thread say it doesn't break Android pay.
Click to expand...
Click to collapse
I have Android pay working here. stock MM and systemless root. I did try flashing the dialer zip and it did break Android pay. However I moved the required files into place using root explorer and set the correct permissions, and Android pay works no problem.
So it seems that flashing zips that modify the system partition in any way will break Android pay, but not if you modify it while in the OS itself. I've been using the cigital safteynet playground app to check each time I make a modification. Definitely make a backup of /system so you can always restore Android pay functionality if a mod breaks it.
Also using Xposed WILL break Android pay. I try not to miss it much, but honestly I've got my MXPE pretty much perfect for me, and what apps I use that require root are all working well with systemless root.
Sent from my XT1575 using Tapatalk
timeToy said:
- Renamed system\recovery-from-boot.p to .bak in TWRP
Click to expand...
Click to collapse
What does this do?
EVR_PR said:
What does this do?
Click to expand...
Click to collapse
This prevent the stock recovery from overwriting TWRP
I actually have TWRP in read only mode, which allows stock to overwrite it, and the file ends in .p.
Will changing it to .bak allow me to remove the read-only status?
bb12489 said:
However I moved the required files into place using root explorer and set the correct permissions, and Android pay works no problem.
Click to expand...
Click to collapse
Any chance you'd be willing to elaborate on this a little? (i.e. which files, where and the correct permissions)
Thanks!
innoman said:
Any chance you'd be willing to elaborate on this a little? (i.e. which files, where and the correct permissions)
Thanks!
Click to expand...
Click to collapse
Well the flashable zip as the folder structure laid out inside it, so just use that to know where to move the files. Usually the permissions are rw-r-r in most folders, but just check other files in the directories to make sure what permissions to set. That's all I've done to get the dialer working at least. I imagine it works for other things as well.
bb12489 said:
I have Android pay working here. stock MM and systemless root. I did try flashing the dialer zip and it did break Android pay. However I moved the required files into place using root explorer and set the correct permissions, and Android pay works no problem.
Click to expand...
Click to collapse
That didn't work for me, I was able to install the 3.2 dialer just fine using root explorer, but it break Android Pay (Fail Cigital Safteynet Playground)
I try step by step install, testing with Cigital after every step, it fail when I copy the Google Dialer folder to pri-app. How did you do?
timeToy said:
That didn't work for me, I was able to install the 3.2 dialer just fine using root explorer, but it break Android Pay (Fail Cigital Safteynet Playground)
I try step by step install, testing with Cigital after every step, it fail when I copy the Google Dialer folder to pri-app. How did you do?
Click to expand...
Click to collapse
I followed the same steps that bb did and am getting the same results you are. Android Pay was working just fine with systemless root and Adaway, but so far, DPI changes and the Google Dialer have both broken Android Pay for me.
I lost it manually installing the new emoji font pack and google keyboard. I manually copied the files over and fixed the permissions.
I'm stock UK, but I keep getting a popup saying Android Pay isn't available in the UK
Jay794 said:
I'm stock UK, but I keep getting a popup saying Android Pay isn't available in the UK
Click to expand...
Click to collapse
That's because it isn't but it should be coming to the UK in the next few weeks according to rumours.
Sent from my LG-D855 using Tapatalk
Pardon me if I sound like an idiot here, but can I flash a magisk zip through Flashfire so I can finally get Netflix to work? I have tried deleting liboemcrypto.so and have also done other **** without any results. Is it possible to have magisk on Snapdragon variants?
Unfortunately not yet.... We US Snapdragon S8/S8+ owners can't mess with our bootloaders, recovery or boot image without running afoul of secure boot. Recovery is not as bad to mess up, because you can still reboot and re-flash a backup of your recovery (if you made one). If you mess with your boot image (e.g., Magisk, custom kernel, etc.), you will have to Odin flash, again.
no, I tried and it broke root. It modifies the boot image which cant be modified for us.
This is what I thought too. How then are people installing Viper properly now that we can't install Magisk on S8 snapdragon? Viper or Arise "installs" and "runs" but a) processing doesn't work for USB output and b) sound quality is bad. Exynos guides talk about using Magisk with Viper but that doesn't apply to us.
I just renamed that file using Aptoid's ES File Explorer/Manager PRO with the black icon.
I ran netflix and gave me error -9, relaunched it and it's working now for me.
RypeDub said:
I just renamed that file using Aptoid's ES File Explorer/Manager PRO with the black icon.
I ran netflix and gave me error -9, relaunched it and it's working now for me.
Click to expand...
Click to collapse
Which file did you rename? I'm having quite the same issue with Netflix.
Danhack000 said:
Which file did you rename? I'm having quite the same issue with Netflix.
Click to expand...
Click to collapse
liboemcrypto.so
RypeDub said:
liboemcrypto.so
Click to expand...
Click to collapse
What'd you do?
Edit: update.
I deleted that file and Netflix works now.
Hi all; pardon my lack of knowledge in this subject.
I tried to make a magisk module out of the blackberry productivity edge port found here: https://forum.xda-developers.com/android/apps-games/blackberry-productivity-tab-devices-t3606967
So I tried using the magisk 1500 template and followed the instructions that I found; and the module installs and works fine via TWRP (and magisk recognizes it), but causes the device to lag. And when I try to install it via magisk, I get "installation failed" with no other logs whatsoever. All the module is supposed to do is to mount a few files to the app and priv-app directory in the system. I edited the module.prop and the config.sh. Could anyone check if I had missed something or did a mistake? Thanks in advance.
The module is located here in case anyone wanted to assist:
https://1drv.ms/u/s!AvW_5k8Bkea9sU0SVteHqOoII5N_
Hadi99 said:
Hi all; pardon my lack of knowledge in this subject.
I tried to make a magisk module out of the blackberry productivity edge port found here: https://forum.xda-developers.com/android/apps-games/blackberry-productivity-tab-devices-t3606967
So I tried using the magisk 1500 template and followed the instructions that I found; and the module installs and works fine via TWRP (and magisk recognizes it), but causes the device to lag. And when I try to install it via magisk, I get "installation failed" with no other logs whatsoever. All the module is supposed to do is to mount a few files to the app and priv-app directory in the system. I edited the module.prop and the config.sh. Could anyone check if I had missed something or did a mistake? Thanks in advance.
The module is located here in case anyone wanted to assist:
https://1drv.ms/u/s!AvW_5k8Bkea9sU0SVteHqOoII5N_
Click to expand...
Click to collapse
Nothing looks wrong with the module itself, but you may be missing some libraries or odex/vdex files for the apps you're trying to install. Make sure the entire tree under system/app or system/priv-app is included in the module. The first link you sent tasks about oat subdirectories that are not included in your module.
Howdy all,
I recently rooted my note 5 and ran this debloating script which worked fantastically. However, it did remove the Samsung live wallpaper app which has left me unable to use live wallpapers.
So "no problem" I thought, went and found the .APK for Android 7 online and tried to install it. Unfortunately I get the error "The package conflicts with an existing package by the same name." error.
I've been attempting various fixes I found after googling the problem however I've yet to find anything that'll work (and is within my realm of understanding) in this instance. So what I'm hoping is one of you folks can help me fix this little annoyance without having to completely blow out my phone and edit the debloat script to not uninstall that app.
Cheers!
InfiniteWeird said:
Howdy all,
I recently rooted my note 5 and ran this debloating script which worked fantastically. However, it did remove the Samsung live wallpaper app which has left me unable to use live wallpapers.
So "no problem" I thought, went and found the .APK for Android 7 online and tried to install it. Unfortunately I get the error "The package conflicts with an existing package by the same name." error.
I've been attempting various fixes I found after googling the problem however I've yet to find anything that'll work (and is within my realm of understanding) in this instance. So what I'm hoping is one of you folks can help me fix this little annoyance without having to completely blow out my phone and edit the debloat script to not uninstall that app.
Cheers!
Click to expand...
Click to collapse
First off you are supposed to learn about editing the script & then flashing it after making necessary changes to the script by deleting the lines of needed apks.
Secondly for the apk package conflict, you need to manually replace the apk to its actual location with an file explorer capable to access root & restart the phone.