Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:
Just so you're aware the link you included is broken and depending on which version of SU is installed Step 2 might not be necessary as version 2.62-3 automatically installs systemless.
Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.
Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk
Fixed the broken link, and clarified that this is only tested on the latest supersu.
SR3TLAW said:
Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.
Click to expand...
Click to collapse
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.
drewksparks said:
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.
Click to expand...
Click to collapse
Spasticdroid said:
Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Sounds like regardless there is no still no way with Exposed or Google Dialer
SR3TLAW said:
Sounds like regardless there is no still no way with Exposed or Google Dialer
Click to expand...
Click to collapse
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
Whats all the fuss about Google Dialer, does it make dreams come true?
drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk
Spasticdroid said:
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
My mistake. I thought I remembered something about it working. So, at the moment, there seems to be no way to make Android Pay work with Xposed or Google Dialer. I personally get by very well without both.
Has anyone tried it with multirom and have the second rom without any root or xposed? I'm gonna give it a go and see how it pans out.
Sent from my XT1575 using Tapatalk
Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...
bsilver2988 said:
Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...
Click to expand...
Click to collapse
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
/system/app
Android System WebView (WebViewGoogle)
Chrome Browser - Google (Chrome)
Clock (DeskClockGoogle)
Cloud Print (CloudPrint2)
Exchange Services (Exchange3Google)
Gmail (Gmail2)
Google Calendar (CalendarGoogle)
Google Docs (EditorsDocs)
Google Drive (Drive)
Google Keyboard (LatinImeGoogle)
Google Now Launcher (GoogleHome)
Google Photos (Photos)
Google Play Movies & TV (Videos)
Google Play Music (Music2)
Google Sheets (EditorsSheets)
Google Slides (EditorsSlides)
Google Talkback (talkback)
Google Text-to-Speech (GoogleTTS)
Google Translate (Translate)
Hangouts (Hangouts)
Maps (Maps)
YouTube (YouTube)
/system/priv-app
Google Play Services (GmsCore)
Google Play Store (Phonesky)
Google App (Velvet)
Click to expand...
Click to collapse
Spasticdroid said:
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
Click to expand...
Click to collapse
Thanks for this! It makes perfect sense. Unfortunately I'm still getting a Fail when I run the test. Any other thoughts?
EDIT: Figured it out! I guess OpenGapps itself was incompatible with this setup. Installing TruPure without it solved the problem. Thanks for the help!
Thanks @drewksparks, followed your detailed instructions and confirmed by buying me a beer with my phone running True Pure 2.6.2. Now to decide if it's worth giving up Xposed, Gravity Box, Amplify, etc. Hmmm I want it all.
drewksparks said:
Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:
Click to expand...
Click to collapse
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.
cerobles1 said:
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.
Click to expand...
Click to collapse
Won't work unfortunately. Too many files and apps and such are needed in CM and CM-based ROMs (example: Bliss) for them to work properly, and in turn breaks Android Pay.
If we can ever get an AOSP-based ROM, which is bare (meaning not built with AOSP apps included) working on this device, we may have a chance, just like how some ROMs on Nexus devices, such as Chroma and PureNexus, works with Android Pay.
The last thing needed would be a proper GApps package containing only the default GApps found in a stock Pure/Style ROM to install (can be updated versions of those apps too.)
Sent from my XT1575 using Tapatalk
Related
Has anyone had success installing xposed framework on the m8 running a stock rooted lollipop rom? I have tried multiple times following the guide in the xposed thread here http://forum.xda-developers.com/showthread.php?t=3034811 with no success.
It worked for me on adrenaline 2.1 but not on a couple of other roms I tried.
jas88 said:
It worked for me on adrenaline 2.1 but not on a couple of other roms I tried.
Click to expand...
Click to collapse
What were the steps you took to install it?
I opened xsposed installer >framework > reboot. I only downloaded a couple of modules but they work.
nmarietta said:
What were the steps you took to install it?
Click to expand...
Click to collapse
what steps are you using to install xposed? I have it working on Fluent 7.1 just fine.
BladeRunner said:
what steps are you using to install xposed? I have it working on Fluent 7.1 just fine.
Click to expand...
Click to collapse
I downloaded the files from the link I posted above..
Install the xposed installer .apk
Reboot from within the installer and grant root privileges.
Flash the framework via TWRP
I have also tried to flash the framework first, install the .apk, and reboot from within the installer to grant root.
Neither way has worked for me.
nmarietta said:
I downloaded the files from the link I posted above..
Install the xposed installer .apk
Reboot from within the installer and grant root privileges.
Flash the framework via TWRP
I have also tried to flash the framework first, install the .apk, and reboot from within the installer to grant root.
Neither way has worked for me.
Click to expand...
Click to collapse
I have it running on stock rooted, here are the steps I took.
Flashed the xposed arm zip file in TWRP
Installed the 3.0 alpha2 apk
Once installed I went into "framework" and hit soft reboot.
Once the phone was done I installed a module/made it active and soft reboot again.
I don't think you have to take these exact same steps but this is just what I did following a YT video. In "framework" it always says "Installation is only possible maunally via recovery for now." in red letters. That confused me into thinking it was not installed properly but all the modules I'm using are working fine.
The Stig 04 said:
I have it running on stock rooted, here are the steps I took.
Flashed the xposed arm zip file in TWRP
Installed the 3.0 alpha2 apk
Once installed I went into "framework" and hit soft reboot.
Once the phone was done I installed a module/made it active and soft reboot again.
I don't think you have to take these exact same steps but this is just what I did following a YT video. In "framework" it always says "Installation is only possible maunally via recovery for now." in red letters. That confused me into thinking it was not installed properly but all the modules I'm using are working fine.
Click to expand...
Click to collapse
I have tried to install this exact same way. After flashing the framework and installing the alpha .apk, I activated greenify and rebooted.
Upon launching greenify, I saw a yellow dialogue box that said auto hibernation service has stopped (auto hibernation worked fine before trying to use xposed) I attempted to enable the xposed features and a screen popped up telling me to install the xposed framework.
I have since restored my nand backup I made before flashing xposed, and greenify is back to auto hibernating, just cant use the xposed features.
nmarietta said:
I have tried to install this exact same way. After flashing the framework and installing the alpha .apk, I activated greenify and rebooted.
Upon launching greenify, I saw a yellow dialogue box that said auto hibernation service has stopped (auto hibernation worked fine before trying to use xposed) I attempted to enable the xposed features and a screen popped up telling me to install the xposed framework.
I have since restored my nand backup I made before flashing xposed, and greenify is back to auto hibernating, just cant use the xposed features.
Click to expand...
Click to collapse
Have you tried installing other modules? Looking around the greenify sections here on XDA seems it wasn't ready for 5.0, but there is a beta thread that you may want to take a look at.
http://forum.xda-developers.com/apps/greenify
The Stig 04 said:
Have you tried installing other modules? Looking around the greenify sections here on XDA seems it wasn't ready for 5.0, but there is a beta thread that you may want to take a look at.
http://forum.xda-developers.com/apps/greenify
Click to expand...
Click to collapse
I just found that beta thread, and I am now trying to install xposed again.
I also tried Xsense, and did not have any luck.
What modules are you using? I will activate them and test.
nmarietta said:
I just found that beta thread, and I am now trying to install xposed again.
I also tried Xsense, and did not have any luck.
What modules are you using? I will activate them and test.
Click to expand...
Click to collapse
Currently I'm using
Sense 6 lockscreen mods (LP)
Sense 6 Toolbox beta (to find the beta you have to change your settings, open the module in xposed/scroll all the way right to settings/change to "beta")
YouTube AdAway
YouTube Background Playback
The Stig 04 said:
Currently I'm using
Sense 6 lockscreen mods (LP)
Sense 6 Toolbox beta (to find the beta you have to change your settings, open the module in xposed/scroll all the way right to settings/change to "beta")
YouTube AdAway
YouTube Background Playback
Click to expand...
Click to collapse
I reinstalled xposed, and updated greenify to beta 11. I also installed Sense 6 Toolbox beta. Everything seems to be working just fine.
My problem was using modules that were not updated to work with lollipop. Thanks for all your help!
This is a modified version of @jrkruse stock BPB1 deodexed ROM with all(or most) of the stock BS removed.
INSTRUCTIONS:
I've included the links needed if you want to use xposed. If you chose not to use Xposed, then skip that step in the flashing process.
I have only used Safestrap to install this ROM, but FlashFire should work as well.
1) Flash NO_BS_BPB1_ROM_DEODEXED.zip
2) Flash Extra_toggles.zip
3) Flash xposed-v75-sdk21-arm-arter97-snapdragon.zip
4) Flash Lollipop_Safestrap_Reboot_Extended_PM_PB1.zip
5) Flash BPB1_Firmware_No_Bootloaders.zip
6) After first boot, open Lollipop Recovery Control and install the latest Safestrap.
7) Open up Viper4Android and install the driver. Then install Viper Fix 1.1.apk and run the Viper fix in the app.
There is no need to flash any Viper zips with this ROM. This ROM has all the same apps as BOK3 V5, but obviously updated to the BPB1 apps. The only app added is multiwindow. I don't use multiwindow, so I can be certain that all aspects of it work, but everything seemed to work normally when I played with it.
Note: Don't pay attention to the 1- prefix in front of some of the ROM versions. I prefix all my flashables in my ROM folder with a 1-, 2-, 3-, ect, so that I have them all in order when I flash them instead of having to remember the order every time lol. I forgot to remove those prefixes when I uploaded the ROMs.
reserved
reserved1
Can this be dirty flashed over your bs free bok3?
Sent from my SM-G900V using Tapatalk
---------- Post added at 05:14 PM ---------- Previous post was at 04:53 PM ----------
Just dirty flashed. All is good so far. Thank you
Sent from my SM-G900V using Tapatalk
I've downloaded it multiple times from multiple mirrors, I keep getting 6619258FCFF93587050F9E15B2FFBAA9 as the md5 not
a1d8316898d604314b884dafb09298b0 that is listed for 1-NO_BS_BPB1_ROM_DEODEXED.zip on the download page. I'll give it a try anyway since I can always reflash my NCG stock.
Edit:
It works! But now I have 492 errors anytime I want to download something from google play? Anyone else with this issue?
renthispace said:
I've downloaded it multiple times from multiple mirrors, I keep getting 6619258FCFF93587050F9E15B2FFBAA9 as the md5 not
a1d8316898d604314b884dafb09298b0 that is listed for 1-NO_BS_BPB1_ROM_DEODEXED.zip on the download page. I'll give it a try anyway since I can always reflash my NCG stock.
Click to expand...
Click to collapse
Does anyone know what exactly is new/improved in this BPB1? I feel like these versions keep getting released, but I have no idea what is actually improved LOL.
Thanks! Seems to be working well. Google Calendar kept force closing, so I removed it and installed the Play Store version.
Some apps seen to have a touch recognition problem, like titanium backup. Haven't had any FC errors.
renthispace said:
Edit:
It works! But now I have 492 errors anytime I want to download something from google play? Anyone else with this issue?
Click to expand...
Click to collapse
twelvevyan said:
Some apps seen to have a touch recognition problem, like titanium backup. Haven't had any FC errors.
Click to expand...
Click to collapse
I don't have any of these problems on mine. Does anybody else? It sounds like you guys might have some bad data from a previous ROM. The Play Store was updated in this ROM, so clear data for the Play Store, and that might fix the problem.
Stupifier said:
Does anyone know what exactly is new/improved in this BPB1? I feel like these versions keep getting released, but I have no idea what is actually improved LOL.
Click to expand...
Click to collapse
It is just security patches in this ROM. I haven't found anything really new.
btonetbone said:
Thanks! Seems to be working well. Google Calendar kept force closing, so I removed it and installed the Play Store version.
Click to expand...
Click to collapse
I wouldn't expect Google Calendar to work, because it's not in the ROM lol.
Few Questions
First, since I'm pretty new to flashing ROMs with SafeStrap...
At each step of your process when you say "Flash" does that mean Safestrap-> Boot to Recovery ->Install Zip ???
I'm looking at needing Xposed in order to bypass my company's Exchange security requirement of encrypting my device in order to allow email access.
I got a little confused with all the Xposed documentation out there.
Does this set of instructions get me to where I can load the Xposed module to bypass that security and then continue from there?
Big Thanks for your help.
I'm going to start a backup of current ROM so I'll be ready to install this soon.
Regards,
NerdyKowboy
NerdyKowboy said:
First, since I'm pretty new to flashing ROMs with SafeStrap...
At each step of your process when you say "Flash" does that mean Safestrap-> Boot to Recovery ->Install Zip ???
I'm looking at needing Xposed in order to bypass my company's Exchange security requirement of encrypting my device in order to allow email access.
I got a little confused with all the Xposed documentation out there.
Does this set of instructions get me to where I can load the Xposed module to bypass that security and then continue from there?
Click to expand...
Click to collapse
Yes, flash means install in Safestrap.
If you flash the Xposed zip I linked in the original post, then you can use modules in the Xposed installer app included in the ROM.
CVertigo1 said:
This is a modified version of @jrkruse stock BPB1 deodexed ROM with all(or most) of the stock BS removed.
INSTRUCTIONS:
I've included the links needed if you want to use xposed. If you chose not to use Xposed, then skip that step in the flashing process.
I have only used Safestrap to install this ROM, but FlashFire should work as well.
1) Flash NO_BS_BPB1_ROM_DEODEXED.zip
2) Flash Extra_toggles.zip
3) Flash xposed-v75-sdk21-arm-arter97-snapdragon.zip
4) Flash Lollipop_Safestrap_Reboot_Extended_PM_PB1.zip
5) Flash BPB1_Firmware_No_Bootloaders.zip
6) After first boot, open Lollipop Recovery Control and install the latest Safestrap.
7) Open up Viper4Android and install the driver. Then install Viper Fix 1.1.apk and run the Viper fix in the app.
There is no need to flash any Viper zips with this ROM. This ROM has all the same apps as BOK3 V5, but obviously updated to the BPB1 apps. The only app added is multiwindow. I don't use multiwindow, so I can be certain that all aspects of it work, but everything seemed to work normally when I played with it.
Note: Don't pay attention to the 1- prefix in front of some of the ROM versions. I prefix all my flashables in my ROM folder with a 1-, 2-, 3-, ect, so that I have them all in order when I flash them instead of having to remember the order every time lol. I forgot to remove those prefixes when I uploaded the ROMs.
Click to expand...
Click to collapse
1.) In safestrap, just do wipe->factory reset or is more of a wipe required?
2.) Can I flash them all using the Zip Queue in Safestrap (TWRP 2.7.1.0) or should I do them one at a time?
Factory reset in factory recovery. You can install all of them on one queue.
CVertigo1 said:
Factory reset in factory recovery. You can install all of them on one queue.
Click to expand...
Click to collapse
I did that, and this is AWESOME. Love the ROM. Tough to decide between the two launchers. Haven't had this level of control in a while.
Only snag was that Android Pay doesn't recognize the device as Android authentic, so can't use Android Pay (which I almost never used anyway).
Thanks for all the work @CVertigo1
NerdyKowboy said:
Only snag was that Android Pay doesn't recognize the device as Android authentic, so can't use Android Pay (which I almost never used anyway).
Thanks for all the work @CVertigo1
Click to expand...
Click to collapse
I believe Android Pay doesn't work sheerly because the device is rooted, not because of the ROM itself.
Can't get snapchat to login with Xposed. I've read the solution is to do an Xposed framework uninstall, login to Snap, then reinstall Xposed, but have found a lot of people get hung in a bootloop when uninstalling.
Is this from using the wrong uninstaller or something else?
Which uninstaller is correct?
Do you have another solution?
I have tried removing the modules and doing a reboot to see if that'd be adequate.
EDIT:
The issue was the xposed framework.
To anyone else doing this on Galaxy S5 with this ROM (or same version of Xposed)
1.) uninstall Snapchat
2.) Deactivate modules from Xposed
3.) Download and Flash "xposed-uninstaller-arter97.zip" from this post: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
4.) Reboot and wait for all the apps to Optimize
5.) Reinstall snapchat and login
6.) Flash the same Xposed framework in original post of this thread (apps will re-optimize)
Is there a way to disable the high volume warning? I can't believe they now also have it on Bluetooth...
renthispace said:
Is there a way to disable the high volume warning? I can't believe they now also have it on Bluetooth...
Click to expand...
Click to collapse
Since Xposed is already in the ROM, inside of Xposed, go to Downloads & download the module "NoSafeVolumeWarning". Enable it and reboot.
Boom. No more volume warning.
NerdyKowboy said:
Can't get snapchat to login with Xposed. I've read the solution is to do an Xposed framework uninstall, login to Snap, then reinstall Xposed, but have found a lot of people get hung in a bootloop when uninstalling.
Is this from using the wrong uninstaller or something else?
Which uninstaller is correct?
Do you have another solution?
I have tried removing the modules and doing a reboot to see if that'd be adequate.
EDIT:
The issue was the xposed framework.
To anyone else doing this on Galaxy S5 with this ROM (or same version of Xposed)
1.) uninstall Snapchat
2.) Deactivate modules from Xposed
3.) Download and Flash "xposed-uninstaller-arter97.zip" from this post: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
4.) Reboot and wait for all the apps to Optimize
5.) Reinstall snapchat and login
6.) Flash the same Xposed framework in original post of this thread (apps will re-optimize)
Click to expand...
Click to collapse
So were you able to uninstall Xposed? I see your edit of "fixed issue" but in case you didn't or having issues I posted this in another thread.
http://forum.xda-developers.com/showpost.php?p=65635081&postcount=18
al50 said:
So were you able to uninstall Xposed? I see your edit of "fixed issue" but in case you didn't or having issues I posted this in another thread.
http://forum.xda-developers.com/showpost.php?p=65635081&postcount=18
Click to expand...
Click to collapse
Yes, that fixed the issue.
Successfully uninstalled Xposed, Reinstalled SnapChat and logged in without issue. Then, reflashed the Xposed framework.
So easy, but I was so nervous doing it after seeing many, many people talking about getting hung in a bootloop.
I don't know how much you are concerned about the fact Chainfire is no longer maintaining SuperSU (apparently 2.76 version was the last one developed by him) and the fact it was taken over by some mysterious chinese company, but if you are - there's an alternative. If you want to read more about this issue - here's the link to reddit thread:
https://www.reddit.com/r/Android/comments/54xdmp/ccmt_who_exactly_are_the_owners_of_supersu/
The new owner of SuperSU may or may not be a bad guy, but closed source root manager in hands of some chinese company that we don't really know anything about is kind of a gamble. Fortunately there's an open source alternative - Phh's Superuser. Rooting a phone with it is even easier than using SuperSU, as you avoid all that system/systemless hassle and just root. The only disadvantage is that you need to install the manager separately.
In order to replace SuperSU with Phh's Superuser you need to:
1. Go to SuperSU and fully unroot your device
2. Download Phh's binary from this thread - http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 (TWRP flashable zip direct download link)
3. Flash the zip in TWRP
4. Download Phh's Superuser - https://f-droid.org/repository/browse/?fdid=me.phh.superuser
5. Install Superuser and enjoy
I tried this on 6.01 stock and can confirm everything is working (so far). Let me know what are your thoughts about this. Thanks
Seriously ? If 2.76 was the last by chainfire, it means my 2.78 currently installed with nougat rom, with full power on my phone of course, is made by some mysterious chinese company, chills
On spetrum working nice ant thank you so mucho for the info:good:
I think I ll give a try with nougat, is the app on f-droid the same as on the play store ? https://play.google.com/store/apps/details?id=me.phh.superuser
fablebreton said:
I think I ll give a try with nougat, is the app on f-droid the same as on the play store ? https://play.google.com/store/apps/details?id=me.phh.superuser
Click to expand...
Click to collapse
It seems so (both have the same version number). They probably have different signature, so you won't be able to update PlayStore version in F-Droid and vice versa.
I can confirm it work on nougat perfectly.
Thank you
Thanks for the info.
dudes will this work on stock rom with squid kernel?also on step 1 do we uninstall also supersu after reboot?
Peace to all
kos25k said:
dudes will this work on stock rom with squid kernel?also on step 1 do we uninstall also supersu after reboot?
Peace to all
Click to expand...
Click to collapse
Hello, yes, tried on stock 6.1 with squid kernel too, works fine.
The full unroot will uninstall the app automatically
In step 4, i have installed pph from play store
thanks dude!we hope that will be stable and supported!
can I do it right now?or must I f.reset first?also do I have to give permissions to root apps one to one?
Στάλθηκε από το SGP611 μου χρησιμοποιώντας Tapatalk
no need to factory reset.
May be before full unroot freeze or uninstall any app who will try to get root permissions, and be sure to not have any malware who will try to get root, just by security, we never know...
One pph apk installed from play store or fdroid : when you will unfreez or reinstall those apps, pph will pop up to ask if you want to allow root permission, like supersu
For anyone concerned about this issue, I highly suggest you read this:
http://dirtyunicorns.com/2016/09/06/supersu-the-fear-and-the-plan/
There's most likely nothing to be worried about.
Sent from my Moto X Play using XDA Labs
OK, I’ve ordered and am awaiting arrival of my unlocked Pixel 2 from Google. I am on Verizon GFUDP and I plan on unlocking, rooting with Magisk and installing the tethering module. Then I plan on enjoying the phone and pretty much don’t plan on fussing around much with it.
I plan on unlocking before I do anything, including installing my Verizon sim. But do I have to allow the phone to do any upgrading prior to the rooting process? Also, can I (should I)hold off installing my sim until everything is rooted and up and running?
I was also thinking of using the Skipsoft toolset, but not sure if it is necessary. What are your thoughts on that?
Also, regarding lockscreen security on the phone, is fingerprint or password required? Can you use one or the other? I never use a passcode in general so wondering how it works.
Any "must have" apps to take advantage of Pixel 2?
Any help or advice is much appreciated!
Thanks in advance!
I purchased two Pixel 2 phones, and did the same thing you're planning on doing. I also have Verizon.
1) Unlocking the bootloader will wipe the device; Do this first. If you set up the phone prior to OEM unlocking, you will lose everything you set up.
2) Installing the SIM at anytime won't affect anything. When you install the Verizon SIM, some verizon apps will download. You can delete them if you want.
3) I did not use skipsoft. If you have a basic knowledge of ADB/Fastboot you will be fine without it.
4) The finger print reader is crazy fast. Also, setting up the phone it asks for a pin. Try it with the security of both to start. If you dislike it you can disable it in the future.
5) Apps I like/use: Tasker, Magisk, Titanium Backup, Custom Navigation Bar, Hide "using battery" notification, AdAway, Nova Launcher, Swipepad (where I put the "reboot" shortcuts), Reboot (Material Design) [ I made shortcuts to enter recovery, bootloader, etc], 1weather, Digilux (screen brightness control from the fingerprint reader), and Naptime (Have seen some battery length increase, though slows down notifications)
6) Not really apps, though @Tulsadiver made mods via Aroma from here: Various Mods for 8.1 December Update (Added Screen shots to show black notifications, battery icon removal, and clock w/day & ampm)
7) I like the Snoke kernel found here: [KERNEL]Snoke Kernel by @DespairFactor
There is a guide here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) by @nathanchance
I laid out steps in this post here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Here are links because sometimes they can be tiresome to find:
SDK Platform Tools
(Follow the steps in the linked Post 127 to make cmd and SDK tools easier)
Factory Images for Nexus and Pixel Devices
Full OTA Images for Nexus and Pixel Devices
amajamar said:
Do I have to allow the phone to do any upgrading prior to the rooting process?
Click to expand...
Click to collapse
You should.
amajamar said:
Also, can I (should I)hold off installing my sim until everything is rooted and up and running?
Click to expand...
Click to collapse
Doesn't make a difference.
amajamar said:
I was also thinking of using the Skipsoft toolset, but not sure if it is necessary. What are your thoughts on that?
Click to expand...
Click to collapse
I'd do it manually via the command line with fastboot and adb - knowing how to use these tools is very important in case something ever goes wrong.
amajamar said:
Also, regarding lockscreen security on the phone, is fingerprint or password required? Can you use one or the other? I never use a passcode in general so wondering how it works.
Click to expand...
Click to collapse
You can use both.
Diesel_Jeremiah said:
I purchased two Pixel 2 phones, and did the same thing you're planning on doing. I also have Verizon.
1) Unlocking the bootloader will wipe the device; Do this first. If you set up the phone prior to OEM unlocking, you will lose everything you set up.
2) Installing the SIM at anytime won't affect anything. When you install the Verizon SIM, some verizon apps will download. You can delete them if you want.
3) I did not use skipsoft. If you have a basic knowledge of ADB/Fastboot you will be fine without it.
4) The finger print reader is crazy fast. Also, setting up the phone it asks for a pin. Try it with the security of both to start. If you dislike it you can disable it in the future.
5) Apps I like/use: Tasker, Magisk, Titanium Backup, Custom Navigation Bar, Hide "using battery" notification, AdAway, Nova Launcher, Swipepad (where I put the "reboot" shortcuts), Reboot (Material Design) [ I made shortcuts to enter recovery, bootloader, etc], 1weather, Digilux (screen brightness control from the fingerprint reader), and Naptime (Have seen some battery length increase, though slows down notifications)
6) Not really apps, though @Tulsadiver made mods via Aroma from here: Various Mods for 8.1 December Update (Added Screen shots to show black notifications, battery icon removal, and clock w/day & ampm)
7) I like the Snoke kernel found here: [KERNEL]Snoke Kernel by @DespairFactor
There is a guide here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) by @nathanchance
I laid out steps in this post here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Here are links because sometimes they can be tiresome to find:
SDK Platform Tools
(Follow the steps in the linked Post 127 to make cmd and SDK tools easier)
Factory Images for Nexus and Pixel Devices
Full OTA Images for Nexus and Pixel Devices
Click to expand...
Click to collapse
Nice! Thanks! No need for TWRP? I was going to install it.
Was there a "thing" regarding which version of Magisk to install? I thought I read something somewhere about issues with the newest version.
amajamar said:
Nice! Thanks! No need for TWRP? I was going to install it.
Was there a "thing" regarding which version of Magisk to install? I thought I read something somewhere about issues with the newest version.
Click to expand...
Click to collapse
I have TWRP installed as well. I didn't comment on it since you didn't ask about it.
NOTE: You have to boot TWRP img, then install TWRP ZIP. Search threads, you'll find the info.
NOTE 2: You cannot install TWRP, Magisk and Kernel at the same time. Best way is to install everything is: TWRP ZIP, reboot. Flash Kernel, reboot. Flash Magisk, reboot.
As for Magisk, I'm on v5.5.3 and V15.2 without issues.
I've been upgrading through Magisk direct install without issues.
NOTE: You will get a pop up that your system has an issue and contact the manufacturer after Magisk. Do not panic, it'd because Magisk is modifying the DTBO img. It does not harm anything.
I also installed Viper4Android from Magisk.
Version 2.5.0.4 = works normal and processes correctly.
Diesel_Jeremiah said:
I have TWRP installed as well. I didn't comment on it since you didn't ask about it.
NOTE: You have to boot TWRP img, then install TWRP ZIP. Search threads, you'll find the info.
NOTE 2: You cannot install TWRP, Magisk and Kernel at the same time. Best way is to install everything is: TWRP ZIP, reboot. Flash Kernel, reboot. Flash Magisk, reboot.
As for Magisk, I'm on v5.5.3 and V15.2 without issues.
I've been upgrading through Magisk direct install without issues.
NOTE: You will get a pop up that your system has an issue and contact the manufacturer after Magisk. Do not panic, it'd because Magisk is modifying the DTBO img. It does not harm anything.
I also installed Viper4Android from Magisk.
Version 2.5.0.4 = works normal and processes correctly.
Click to expand...
Click to collapse
Awesome! What features does the Snoke kernel give? Any issues with it? Do you need to flash the factory kernel to take an OTA?
I never used Viper4Android before. What does it do?
Thanks.
amajamar said:
Awesome! What features does the Snoke kernel give? Any issues with it? Do you need to flash the factory kernel to take an OTA?
I never used Viper4Android before. What does it do?
Thanks.
Click to expand...
Click to collapse
Custom Kernel: Android Basics 101: Understanding Kernels – XDA Developer TV
I feel a bit snappier response and better battery life. There is Snoke, Flash, and ElementalX to name a few.
If you've loaded TWRP at all or mounted system rw; OTAs will not work. You'll have to use the factory images.
I've had no issues with the Snoke kernel. Just ensure you use the proper one for 8.0 or 8.1.
Viper4Android: Get the Sound you Deserve with ViPER4Android -- Android App Review
Viper4Android and Pizel 2 front facing speakers work very well together.
Diesel_Jeremiah said:
Custom Kernel: Android Basics 101: Understanding Kernels – XDA Developer TV
I feel a bit snappier response and better battery life. There is Snoke, Flash, and ElementalX to name a few.
If you've loaded TWRP at all or mounted system rw; OTAs will not work. You'll have to use the factory images.
I've had no issues with the Snoke kernel. Just ensure you use the proper one for 8.0 or 8.1.
Viper4Android: Get the Sound you Deserve with ViPER4Android -- Android App Review
Viper4Android and Pizel 2 front facing speakers work very well together.
Click to expand...
Click to collapse
Excellent information! Thanks!
This is just to inform the community that there is a way to get snapchat, and maybe other apps, working with root/Xposed and a locked bootloader
Step 1) install safestrap
Step 2) turn off/uninstall Xposed, uninstall all system mods (such as liveboot), unstall super su via unsu.zip (can be found by simple search on xda and flashed via safestrap.
Step 3) (not sure if required just what I did) uninstall snapchat if you have it installed, clear data on Google play store, play services and play services for instant apps.
Step 4) reinstall snapchat though Google play, login.
Step 5) without logging out boot back into safestrap and reinstall super su (I use the 2.79 zip from chainfire as the 2.82 is made by a Chinese company and freezes on partycyborg for s8.
Step 6) reboot and enable/ reinstall Xposed and your system mods if you wish. You will stay signed into Snapchat until you sign out.
Step 7) Enjoy
Tested on SM-G950U AT&T running partycyborg samfail.
IHAX 420 said:
(I use the 2.79 zip from chainfire as the 2.82 is made by a Chinese company and freezes on partycyborg for s8.
Click to expand...
Click to collapse
ffffffFUUUUUUUUUUUUUUUUUU
No wonder it took ages for the SU dialogs to pop up. I went back to stock just because of that, and I accidentally upgraded to bootloader v3 and now I'm going to wait a very long time to get root again.