Related
Root is required for this application. Thanks to DesignGears & Chainfire for putting in the work for root to be on our phones.
Please try method 1 and 2 before posting that it doesn't work. Let me know which one worked for you in the comments.
_________________________________
Method 1 :
Download FDroid from this link - https://f-droid.org/FDroid.apk
Open FDroid and download AdAway.
Some have reported that this AdAway will install the host file without any issues.
_________________________________
Method 2 :
Download AdAway here - http://www.androidfilehost.com/?fid=23060877490004670
(All credit for the link goes to mrRobinson)
After you have installed and opened the app -
Click "Download files and apply ad blocking"
The app is going to crash, don't worry!
Re-open the application and click "Download files and apply ad blocking" again
This time it will give you a pop up saying "Copying of host file failed", once again don't worry!
Now click the refresh button in the top right, and now for the last time click "Download files and apply ad blocking"
You will now be told that it was successful and to restart.
This is how I got it to work, I apologize if it does not work on your device.
Please click the thanks button if this worked for you.
Screenshots
Don't you need root for this?
slidesear said:
Don't you need root for this?
Click to expand...
Click to collapse
Yes
147aaron said:
Yes
Click to expand...
Click to collapse
why wouldnt the official app work without crashing if you have root?
try the official one:
http://sufficientlysecure.org/index.php/adaway/
Guitarboarder28 said:
why wouldnt the official app work without crashing if you have root?
try the official one:
http://sufficientlysecure.org/index.php/adaway/
Click to expand...
Click to collapse
I tried to get the the app from that website but they want you to download it through a store. And I don't know about others but it hangs on downloading icons or something. So the only way I got the app was from mrRobinson post. According to him its the same app, but he just compiled it from the source from the Devs website.
does this nix the youtube apps? (pre-rolls)
wdkingery said:
does this nix the youtube apps? (pre-rolls)
Click to expand...
Click to collapse
I just tested it for you and no. I don't know of a way to that ether. I tried the youtube app and the mobile, they both had a ad on the same video that I tested.
Well yea but the stores legit no worries there
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I just installed it normally with no problems. Never even had a crash the first time.
I'm not rooted (yet), but all of my rooted device AdAway just works. So I really don't see any reason for the AdAway NOT to work if your phone is rooted. Unless I'm missing something here...
Pikezer1337 said:
I just installed it normally with no problems. Never even had a crash the first time.
Click to expand...
Click to collapse
Visual360 said:
I'm not rooted (yet), but all of my rooted device AdAway just works. So I really don't see any reason for the AdAway NOT to work if your phone is rooted. Unless I'm missing something here...
Click to expand...
Click to collapse
This was just my experience with it. I have used adaway on other devices and it just installed with no problem. I posted this because I had seen some other people were having issues with it, so I was just letting people know how I got it to work.
147aaron said:
Please follow tutorial before posting that it doesn't work.
Root is required for this application. Thanks to DesignGears & Chainfire for putting in the work for root to be on our phones.
Download AdAway here - http://www.androidfilehost.com/?fid=23060877490004670
(All credit for the link goes to mrRobinson)
After you have installed and opened the app -
Click "Download files and apply ad blocking"
The app is going to crash, don't worry!
Re-open the application and click "Download files and apply ad blocking" again
This time it will give you a pop up saying "Copying of host file failed", once again don't worry!
Now click the refresh button in the top right, and now for the last time click "Download files and apply ad blocking"
You will now be told that it was successful and to restart.
This is how I got it to work, I apologize if it does not work on your device.
Please click the thanks button if this worked for you.
Screenshots
Click to expand...
Click to collapse
I downloaded my AdAway from f-Droid, but I've seen the same crash behavior.
After the crash, the download and apply worked on the first try.
(The first time, I had to flash back to stock and re-root. The second time applying AdAway blocking took a couple of tries before it went through (6 more specifically))
you can try adaway 2.3 official
or
AdAway-release_Build-10.09.13
the new release is working like a charm
147aaron said:
I tried to get the the app from that website but they want you to download it through a store. And I don't know about others but it hangs on downloading icons or something. So the only way I got the app was from mrRobinson post. According to him its the same app, but he just compiled it from the source from the Devs website.
Click to expand...
Click to collapse
Mine also hung on downloading icons....so i went to playstore and seached for busybox...downloaded and installed newest version by jrummy....installed box and then tried the app again and install flawlessly....doesnt mean it will work for everyone but it worked for me...:good::laugh:
I just install it from fdroid. I don't really use a lot of stuff from there as it's mostly in the market, but I do for this one so I don't have to look for updates on a website etc.
i dled it from fdroid also, it didnt work at first, would just hang up on applying the files but i rebooted and it was successful the first try
rockinandroid said:
Mine also hung on downloading icons....so i went to playstore and seached for busybox...downloaded and installed newest version by jrummy....installed box and then tried the app again and install flawlessly....doesnt mean it will work for everyone but it worked for me...:good::laugh:
Click to expand...
Click to collapse
khaytsus said:
I just install it from fdroid. I don't really use a lot of stuff from there as it's mostly in the market, but I do for this one so I don't have to look for updates on a website etc.
Click to expand...
Click to collapse
xaniq said:
i dled it from fdroid also, it didnt work at first, would just hang up on applying the files but i rebooted and it was successful the first try
Click to expand...
Click to collapse
Thanks for the feedback. I will update the thread to have both methods shortly
I've found supersu leaving dozens of sudaemon's around which sometimes breaks root entirely (until you reboot) or sometimes you can manage to get su to work and then kill apps.
Adaway seems to potentially be a leading cause of this, or maybe it's just the obvious victim, I'm not sure. But I often find it's complaining it could not apply the hosts file, so I get into a shell, find a bunch of stray sudaemon's, kill them, then it's happy again.
I think there's still some tweaking that can be done for su on 4.3.
All I did was install Fdroid, then
Go into to terminal and type this
su
restorecon -R -v /data/data
Then install adaway and run as normal
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Use FDroid
Just a quick heads-up. I used FDroid to install AdAway yesterday...no problems, loaded first time and enabled without a hitch. A word to the less experienced Android (Note 3) flashers like myself.
OFF TOPIC Question: What's the best Terminal Emulator to use for someone like me, who wants to learn to use a TE?? Your assistance would be most appreciated.
Thanx...Chief
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
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.
Hi,
I ordered an expensive toothbrush by Philips, it has an app that keeps track of your brushing habits.
Even tracks of certain areas you don't cover too well.
If it works that would be great.
But I haven't even received my package yet, and I just try to install the app on my phone, I get a message that It won't work because I have a rooted phone.... Well it does not really say this, it said I have a jailbroken phone. See attachment.
Now before ordering I did try to see if it would work on a rooted phone, (on my wife's oukitell) no, but with magisk hide, it worked fine...
On my Xperia xz1, with Android 9 rooted also with magisk, magisk hide does not seem to work for this app.. Not even magisk repackaging.
I looked in the play store and see that there are a few others that bump into this problem.
I found on apkmirror that version 4.2.2 does work though if anyone needs this info.
At least on a repackaged magisk, and magisk hide.. I did not yet try it if it works without those.
I wish app makers would not do this... Many banking apps and other important apps I never have a problem with.
For anyone that is interested, with magisk version 18 and magiskhide activated for the sonicare app you can use it, even after the app detected root 'jailbreak' (as Philips puts it), and you turn on magiskhide in magisk 18 for sonicare the app will work again.
Using Sonicare apk 4.8.0 & Magisk 18.1 and turn on magiskhide on almost every app (incl system apps)
but still get the detect 'jailbreak' message.
Any idea how to fix this?
Ancientsthe said:
Using Sonicare apk 4.8.0 & Magisk 18.1 and turn on magiskhide on almost every app (incl system apps)
but still get the detect 'jailbreak' message.
Any idea how to fix this?
Click to expand...
Click to collapse
The app checks following things:
Code:
String str = Build.TAGS;
if (str != null && str.contains("test-keys")) {
return "true";
}
for (String file : new String[]{"/system/app/Superuser.apk", "/sbin/su", "/system/bin/su", "/system/xbin/su", "/data/local/xbin/su", "/data/local/bin/su", "/system/sd/xbin/su", "/system/bin/failsafe/su", "/data/local/su", "/su/bin/su"}) {
if (new File(file).exists()) {
return "true";
}
}
also tests output for /system/xbin/which su and /system/bin/which su
and check for emulator
public static boolean isEmulator() {
return Build.FINGERPRINT.startsWith("generic") || Build.FINGERPRINT.startsWith(EnvironmentCompat.MEDIA_UNKNOWN) || Build.MODEL.contains("google_sdk") || Build.MODEL.contains("Emulator") || Build.MODEL.contains("Android SDK built for x86") || Build.MANUFACTURER.contains("Genymotion") || (Build.BRAND.startsWith("generic") && Build.DEVICE.startsWith("generic")) || "google_sdk".equals(Build.PRODUCT);
}
You can find application without the check here https://drive.google.com/open?id=1VRqHwyN9OoHioX2-nppkJRwyQOUPAqSh .
Sadly due to paranoid developers you have to modify the app.
elektro255 said:
The app checks following things:
You can find application without the check here https://drive.google.com/open?id=1VRqHwyN9OoHioX2-nppkJRwyQOUPAqSh .
Sadly due to paranoid developers you have to modify the app.
Click to expand...
Click to collapse
Thanks a ton! I've been using the app for a while, but now it came up with that blocked message. Nothing I do seems to get rid of it anymore, even Magisk Hide. I didn't update the app, either. It's really weird.
Can you tell me which class the checks are in so I can do this myself? I'd really appreciate it.
Also, can this be removed through just .smali modifications? Or does it require a full .java decompile and recompile?
(Edit: I was able to find all of the code you pointed out and change these myself - I successfully modded version 6.4.1 of the app)
And since you seem knowledgeable, another thing I'd like to do is completely disable the need to log in before using the app. I've been able to use the app for a while, and it works fine if you totally block it from the internet. If I could just disable the account check and skip straight to the main activity and make the app think I'm logged in, that would be awesome.
I'm not super skilled with modifying decompiled apps, but I'm going to try and rip out the need to log in with an account just to use the app. I'm hoping I can attach this to a debugger and see which functions I will need to change. If anyone could point me in the right direction with this, that would be awesome!
ubergeek77 said:
Thanks a ton! I've been using the app for a while, but now it came up with that blocked message. Nothing I do seems to get rid of it anymore, even Magisk Hide. I didn't update the app, either. It's really weird.
Can you tell me which class the checks are in so I can do this myself? I'd really appreciate it.
Also, can this be removed through just .smali modifications? Or does it require a full .java decompile and recompile?
(Edit: I was able to find all of the code you pointed out and change these myself - I successfully modded version 6.4.1 of the app)
And since you seem knowledgeable, another thing I'd like to do is completely disable the need to log in before using the app. I've been able to use the app for a while, and it works fine if you totally block it from the internet. If I could just disable the account check and skip straight to the main activity and make the app think I'm logged in, that would be awesome.
I'm not super skilled with modifying decompiled apps, but I'm going to try and rip out the need to log in with an account just to use the app. I'm hoping I can attach this to a debugger and see which functions I will need to change. If anyone could point me in the right direction with this, that would be awesome!
Click to expand...
Click to collapse
Hi!
I have the same problem with Sonicare for Kids 1.8.6 even when I uninstalled Magisk.
Can you tell me where did you find the checks please? I'm searching for it with APK Multi Tool but find nothing after a long time and multi files opening.
Thanks for your help.
Hi
try to install the sonicare kids app on my samsung tab 3 with lieneago OS 14.1.
same problem, i try magisk hide, hide the app, hide magis, all no solution Can any help or modify the app for me? After modify i can update the app? Big Thanks
I ran into same problem.
I downloaded APK, modified methods for verifying root a tampered package, recompile, resign and it's working.
If anyone interested I can upload it somewhere, not sure if it can be uploaded on XDA directly.
DasioX said:
I ran into same problem.
I downloaded APK, modified methods for verifying root a tampered package, recompile, resign and it's working.
If anyone interested I can upload it somewhere, not sure if it can be uploaded on XDA directly.
Click to expand...
Click to collapse
If you are talking about the sonicare kids app, then yes, please My daughter has been needling me mercilessly to get it working again on her tablet.
uberhund said:
If you are talking about the sonicare kids app, then yes, please My daughter has been needling me mercilessly to get it working again on her tablet.
Click to expand...
Click to collapse
No i'm not talking about kids app
I know, it is an old thread, but it is the closest thing I found to get the sonicare apps running.
A good source on how and what to patch is here: https://resources.infosecinstitute.com/topic/android-root-detection-bypass-reverse-engineering-apk/
The patched apps can be found here:
patched sonicare app (10.6.0): https://gofile.io/d/6riPuK
patched kids app (4.0.1): https://gofile.io/d/2OcFKB
moto-assa said:
I know, it is an old thread, but it is the closest thing I found to get the sonicare apps running.
A good source on how and what to patch is here: https://resources.infosecinstitute.com/topic/android-root-detection-bypass-reverse-engineering-apk/
The patched apps can be found here:
patched sonicare app (10.6.0): https://gofile.io/d/6riPuK
patched kids app (4.0.1): https://gofile.io/d/2OcFKB
Click to expand...
Click to collapse
Could you re-upload patch kids app? Unfortunately "This file does not exist."
Would love this patched app as well, but link no longer works.
Me too
No patched app is needed.
1. Open Magisk app*.
2. Go to "Settings".
3. Enable "Enforce DenyList".
4. Tab on "Configure DenyList".
5. Search for Sonicare app and tab on it.
6. Enable all displayed sliders. (two for me)
7. That's it.
Have fun to use Sonicare app with your rooted device.
* latest Magisk app 25.2 (25200)(33)
resi83 said:
No patched app is needed.
1. Open Magisk app*.
2. Go to "Settings".
3. Enable "Enforce DenyList".
4. Tab on "Configure DenyList".
5. Search for Sonicare app and tab on it.
6. Enable all displayed sliders. (two for me)
7. That's it.
Have fun to use Sonicare app with your rooted device.
* latest Magisk app 25.2 (25200)(33)
Click to expand...
Click to collapse
Thanks resi83.
I did that.
Unfortunately on my device (Galaxy Tab S2, LineageOS 17.1) I still get the jailbreak message.
joehensley said:
Thanks resi83.
I did that.
Unfortunately on my device (Galaxy Tab S2, LineageOS 17.1) I still get the jailbreak message.
Click to expand...
Click to collapse
Sorry to hear that, joehensley!
Described way works fine for me on two different systems without the jailbreak message or other issues:
- Galaxy S10+ (G975F) with stock firmware (one ui 4.1 aka Android 12) + rooted via Magisk
- Galaxy A5 (A520F) with LineageOS 18.1 + rooted via Magisk
I'm sorry! :-/
Maybe someone else has also tested it and can give us feedback!? (@All)
DasioX said:
I ran into same problem.
I downloaded APK, modified methods for verifying root a tampered package, recompile, resign and it's working.
If anyone interested I can upload it somewhere, not sure if it can be uploaded on XDA directly.
Click to expand...
Click to collapse
Can you give me a download link ? Which version did you patch?
Nope.
^Preemptively answering all PMs.
This sounds amazing, May i ask for a very wanted feature? Android 10(Q) battery! If you make this possible ill love you to the ends of the world and donate a bottle of something good lol ?
Thanks for this. Can you tell me if the transcripts for screened calls are available with this?
mikkis2k said:
This sounds amazing, May i ask for a very wanted feature? Android 10(Q) battery! If you make this possible ill love you to the ends of the world and donate a bottle of something good lol
Click to expand...
Click to collapse
What are you asking for?
lollyjay said:
Thanks for this. Can you tell me if the transcripts for screened calls are available with this?
Click to expand...
Click to collapse
I'm not sure if call screen saves the transcript, but I've interacted with live transcriptions with multiple responses. You can see my screenshots in the other call screen thread.
TotallyAnxious said:
What are you asking for?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
"v1.7 (23/04/2019)
- Add Android Q battery icon style"
This, if its possible tho, its weird that the oneplus 6 thats on pie can and we cant, you think its possible? ?
mikkis2k said:
https://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
"v1.7 (23/04/2019)
- Add Android Q battery icon style"
This, if its possible tho, its weird that the oneplus 6 thats on pie can and we cant, you think its possible? ?
Click to expand...
Click to collapse
No idea. I'll maybe look into it. But it's not something that immediately hits me as "hey I can do that". I'm incredibly lazy and stoned a lot (stage 3 colon cancer survivor). So keep that in mind lol
Well dang, I still can't get call screening even with this. That's the only feature I truly missed when I left pixel 2 xl for a op7pro. I just have the worst luck trying to get it back.
Also I had a super nice stable device on 9.5.13 with root and a lot of nice things and the only reason I even went to 10 was the other thread said it was working on 10 and xxx said it worked on 10 and now I've been on 10.0.1 for 3 days and it's the buggiest thing I've used ever
Sent from my OnePlus7Pro using XDA Labs
spart0n said:
Well dang, I still can't get call screening even with this. That's the only feature I truly missed when I left pixel 2 xl for a op7pro. I just have the worst luck trying to get it back.
Also I had a super nice stable device on 9.5.13 with root and a lot of nice things and the only reason I even went to 10 was the other thread said it was working on 10 and xxx said it worked on 10 and now I've been on 10.0.1 for 3 days and it's the buggiest thing I've used ever
Click to expand...
Click to collapse
It's incompatible with your set up or you didn't follow the directions. (I'm not angry). But I've posted screenshots proving it works
So try eliminating variables till it works.
https://forum.xda-developers.com/on...bling-google-pixel-call-t3946535/post80596215
TotallyAnxious said:
It's incompatible with your set up or you didn't follow the directions. (I'm not angry). But I've posted screenshots proving it works
So try eliminating variables till it works.
https://forum.xda-developers.com/on...bling-google-pixel-call-t3946535/post80596215
Click to expand...
Click to collapse
Well I am on the T-Mobile version converted to international so mine is the gm1915 which you already said might not work. I completely clearer out every magisk module I had, rebooted to a stock rooted phone and things were fine, installed your first module, rebooted things were fine, installed the companion module and get a bootloop. Thankfully I have twrp and uninstalled the companion module and now it boots. I just have a gut feeling it's not going to work on here and I REALLY hate wiping my data so I'm just going to wait and see if someone else makes a breakthrough on the gm1915 model
Sent from my OnePlus7Pro using XDA Labs
spart0n said:
Well I am on the T-Mobile version converted to international so mine is the gm1915 which you already said might not work. I completely clearer out every magisk module I had, rebooted to a stock rooted phone and things were fine, installed your first module, rebooted things were fine, installed the companion module and get a bootloop. Thankfully I have twrp and uninstalled the companion module and now it boots. I just have a gut feeling it's not going to work on here and I REALLY hate wiping my data so I'm just going to wait and see if someone else makes a breakthrough on the gm1915 model
Click to expand...
Click to collapse
Well you didn't follow the instructions. You didn't install Google phone. Please reread.
If you don't install Google phone before flashing the companion. It won't boot.
I provided clear instructions. Follow them and you'll get call screen.
How to install (Magisk Manager or TWRP):
0. Uninstall kirisakura kernel companion, it's included.
1. Install "Anxious7Pro_v*.zip".
2. Reboot.
3. Install google phone apk from apkmirror or just use the apk in the companion module.
4. Set up google phone, i.e. grant all permissions (including "Draw over other apps" and "Modify system settings"), set as default phone app, open app and set up available features.
5. Install "Anxious7ProCompanion_v*.zip".
6. Reboot.
7. Profit.
Also you should pretty much always have BusyBox installed if you're rooted.
TotallyAnxious said:
Well you didn't follow the instructions. You didn't install Google phone. Please reread.
If you don't install Google phone before flashing the companion. It won't boot.
I provided clear instructions. Follow them and you'll get call screen.
How to install (Magisk Manager or TWRP):
0. Uninstall kirisakura kernel companion, it's included.
1. Install "Anxious7Pro_v*.zip".
2. Reboot.
3. Install google phone apk from apkmirror or just use the apk in the companion module.
4. Set up google phone, i.e. grant all permissions (including "Draw over other apps" and "Modify system settings"), set as default phone app, open app and set up available features.
5. Install "Anxious7ProCompanion_v*.zip".
6. Reboot.
7. Profit.
Also you should pretty much always have BusyBox installed if you're rooted.
Click to expand...
Click to collapse
I have no idea what kirisakura kernel companion is, but is compatible with Smurf kernel? Could that be my problem?
I also had Google phone installed before I did this, I preferred it over oos dialer from the start
Sent from my OnePlus7Pro using XDA Labs
spart0n said:
I have no idea what kirisakura kernel companion is, but is compatible with Smurf kernel? Could that be my problem?
I also had Google phone installed before I did this, I preferred it over oos dialer from the start
Click to expand...
Click to collapse
You should follow the instructions. If it says install Google phone, you should do that. If it's already installed that means you should uninstall to install. And it's just a handful of shell script commands. It is NOT the issue.
I'm not trying to be difficult. But you've twice not followed the instructions. If you don't follow them. It won't work.
The instructions were set up specifically for this. The non-boot that is caused by Google phone being installed as a system app prior to being a user app. I have no idea why in hell that would cause a non-boot. But it does. As I said I am very lazy. I did everything I could to make this a one and done module. So I wouldn't have to provide much support.
Kirisakira companion is listed as feature but I actually rewrote it and that will probably be put into the original mod from freak07. It's just to emphasize not needing to install both.
I think it's ridiculous it requires instructions but it's the only consistent way I've found to get all the listed features working. Please please please ? ?? read them carefully and follow them. Meaning the below paragraph is the ridiculous part btw.
It makes no sense Google phone causes a non-boot when installed as system app first. Even in a module by itself. It causes that.
I spent a week figuring out the easiest way to do this. And I got it down to under 10 steps. Please follow them.
I even spent time leanring how the unity module template works ecause the companion module is unity. And I'm really lazy.
Simplified instructions
How to install (Magisk Manager or TWRP):
0. Uninstall Kirisakura kernel companion and Google Phone, if both/either are installed. Reboot if you uninstalled.
1. Install "Anxious7Pro_v*.zip".
2. Reboot.
3. Install google phone apk from apkmirror or just use the apk inside the companion module.
4. Set up google phone, i.e. grant all permissions (including "Draw over other apps" and "Modify system settings"), set as default phone app, open app and set up available features.
5. Install "Anxious7ProCompanion_v*.zip".
6. Reboot.
7. Profit.
If you don't follow the instructions, you'll probably end up in a non-boot/bootloop.
@TotallyAnxious I will post here. I will be doing clean install of Beta 4 in a couple of hours, and post feedback here. One question though... I am a beta tester for Google Phone. Should I not use it, and instead install the nodpi version of latest .APK that you linked?
Sent from my JiaYu S3 using XDA Labs
lollyjay said:
@TotallyAnxious I will post here. I will be doing clean install of Beta 4 in a couple of hours, and post feedback here. One question though... I am a beta tester for Google Phone. Should I not use it, and instead install the nodpi version of latest .APK that you linked?
Click to expand...
Click to collapse
Didn't you just confirm it works with that screenshot? And I use beta too. But I have stable in the companion module and you can use any verison. I just don't want to provide a non stable starting point. I get less issues reported that way haha you'll learn overtime I consider how to minimize the effort I need to put into support beyond the OP. I'm incredibly lazy.
TotallyAnxious said:
Didn't you just confirm it works with that screenshot? And I use beta too. But I have stable in the companion module and you can use any verison. I just don't want to provide a non stable starting point. I get less issues reported that way haha you'll learn overtime I consider how to minimize the effort I need to put into support beyond the OP. I'm incredibly lazy.
Click to expand...
Click to collapse
lol same here (lazy). But I think that testing your modules with clean beta 4 install is worth the time and effort.
Sent from my JiaYu S3 using XDA Labs
lollyjay said:
lol same here (lazy). But I think that testing your modules with clean beta 4 install is worth the time and effort.
Click to expand...
Click to collapse
I don't think it is but I haven't tried beta OnePlus software yet. But I doubt it's gonna be that different with a clean install. Can you post the screenshot here so people see it works? Until it's posted here, people can click the link to see it.
https://forum.xda-developers.com/on...-nolimits-7-0-speed-ram-t3933927/post80645203
TotallyAnxious said:
I don't think it is but I haven't tried beta OnePlus software yet. But I doubt it's gonna be that different with a clean install. Can you post the screenshot here so people see it works?
Click to expand...
Click to collapse
Sure, np
Sent from my JiaYu S3 using XDA Labs
Hi, Ive just followed the instructions and got this working.. but i previously had the google phone installed as system app so went to my uninstaller and uninstalled 3 things, phone, phone .com and android.phone i think it was and now i have no mobile data.
Any idea what i install again to get this back? Thanks!