Hi all,
Is it possible to have a stock rom/locked BL/stock recovery and ADB push framework-res.apk, android.policy.odex, android.policy.jar?
What I really want is to be fully stock for the moment but use Expanded Desktop Mode to hide softkeys, so when I play a games/browse net it is in full screen.
Assuming I was able to get the modded files.
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
any ideas?
Just like the other threads where op wants features from a custom rom. Just save yourself the time and flash a custom rom.
If you do get it to work, you won't be able to accept further otas because you modified your phone.
Also you will most likely need a rom that's deodexed which the stock rom is not.
Sent from my Nexus 4 using xda premium
zephiK said:
Just like the other threads where op wants features from a custom rom. Just save yourself the time and flash a custom rom.
If you do get it to work, you won't be able to accept further otas because you modified your phone.
Also you will most likely need a rom that's deodexed which the stock rom is not.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
He's right. Why do you want this setup, OP? Surely there is a reason.
Unless I'm mistaken, advanced power menu requires modifying framework-res.apk. Not sure how familiar you are with modifying framework, but it's not fun.
estallings15 said:
He's right. Why do you want this setup, OP? Surely there is a reason.
Unless I'm mistaken, advanced power menu requires modifying framework-res.apk. Not sure how familiar you are with modifying framework, but it's not fun.
Click to expand...
Click to collapse
2 reasons really, 1st is stock rom is stable
2nd is barclays bank app will not work on rooted rom.
zephiK said:
Just like the other threads where op wants features from a custom rom. Just save yourself the time and flash a custom rom.
If you do get it to work, you won't be able to accept further otas because you modified your phone.
Also you will most likely need a rom that's deodexed which the stock rom is not.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Worth a shot.
Ronaldo_9 said:
2 reasons really, 1st is stock rom is stable
2nd is barclays bank app will not work on rooted rom.
Worth a shot.
Click to expand...
Click to collapse
Have you tried a custom rom? All of them are stable, Nexus devices are aosp supported and will work off the bat with no problems.
Stability is a definition of all drivers working (wifi, blue tooth, cellular data, etc) as well as features.
I don't get why you're bringing root into question here. In order to do the tweak you want, it requires root? So either way you'd be rooted in both cases. You may also choose to temporarily un root using the superuser app.
So......
Sent from my Nexus 4 using xda premium
simple answer is, a custom roms with these tweaks have root. The barclays app does not work even if you remove SU and SuperUser.apk
Ronaldo_9 said:
simple answer is, a custom roms with these tweaks have root. The barclays app does not work even if you remove SU and SuperUser.apk
Click to expand...
Click to collapse
You don't need to remove SU and SuperUser to disable root. There is a option implemented within the app in which you can disable root access temporarily until you uncheck the box again.
Your stock ROM with this "enhanced power menu" requires root as well. So your point invalidates yourself? because stock ROM + this tweak you want needs root.
Custom rom = root.
??????????? both requires root. I don't get where you're going at.
incorrect. You are either trying to be helpful and want to understand my point or you are just trying to be smart.
enhanced power menu does not need root access and therefore you can delete SU and Superuser.apk.
You have not used the barclays app so do not comment on how you can disable root access to use it.
I had this issue on Galaxy Nexus but had it working on a custom rom by manually removing all root files from the zip beofre flashing but all other roms Barclays app always detected root even if i removed all root files maybe because the rom had insureboot image.
Anyway I think for me to use a modded framework I would need a deodex, which =custom rom
Ronaldo_9 said:
incorrect. You are either trying to be helpful and want to understand my point or you are just trying to be smart.
enhanced power menu does not need root access and therefore you can delete SU and Superuser.apk.
You have not used the barclays app so do not comment on how you can disable root access to use it.
I had this issue on Galaxy Nexus but had it working on a custom rom by manually removing all root files from the zip beofre flashing but all other roms Barclays app always detected root even if i removed all root files maybe because the rom had insureboot image.
Anyway I think for me to use a modded framework I would need a deodex, which =custom rom
Click to expand...
Click to collapse
Trying to be smart? I am smart. Look at my amount of posts and thanks, I don't get all those points by saying nonsense. I am being helpful but YOU aren't understanding me. I'm saying Superuser can temporarily DISABLE ROOT on the WHOLE PHONE regardless of WHAT APP you use. It's a GLOBAL functionality.
Enhanced Power Menu requires changes in the /system/ so it requires root access. Root access is what allows you to do changes outside of /sdcard/.
That's what I said about barclays app. You can disable root access on the whole phone via SuperUser app. I mentioned this many times. It doesn't matter what app I'm referring to. The superuser app disables root on the WHOLE PHONE regardless of what app it is. So don't comment to me saying I don't know what I'm talking about. Chainfire implemented superuser this way because when you rent/buy movies from Google Videos/Movies it doesn't let you watch them if you are rooted; so a workaround is to temporarily disable root so you can watch them. Then when you are done, you can reactivate root access.
Obviously no one else is here helping you so...... if you're so smart figure it out then. But flashing a custom ROM is the easiest way.
https://play.google.com/store/apps/...51bGwsMSwxLDEsImV1LmNoYWluZmlyZS5zdXBlcnN1Il0.
Features include:
- Superuser access prompt
- Superuser access logging
- Superuser access notifications
- Per-app notification configuration
- Temporary unroot
- Deep process detection (no more unknowns)
- Works in recovery (no more segfaulting)
- Works when Android isn't properly booted
- Works with non-standard shell locations
- Always runs in ghost mode
- Wake on prompt
Click to expand...
Click to collapse
So I unlocked BL and flashed custom rom, done the hide SuperSU but barclays app still said phone is rooted, cleared cache and davik still the same. Uninstalled SU same. Deleted files in xbin that relates to busybox and su damn app still says phone is rooted (i did clear it's cache/uninstall/reinstall.
this app has good root protection/detection
Related
Gmail 2.3 is in the market now but when I try to install it I get "Package file was not signed correctly."
I'm currently using Gmail 2.2.1. I even found the apk online and tried to install it manually but it just says installation unsuccessful. Anybody else seeing the same problem? Any fix?
FIX:
Here is the easiest fix I could find from within this thread...
Uninstall 2.2.1 with titanium or root explorer, reboot, then install from the market.
Mine installed fine and runs fine... I'm rooted/s-off and installed the deoxed 2.2 leak and running kings #4... (just for reference)
Same here. Installed fine.
Dmtalon said:
Mine installed fine and runs fine... I'm rooted/s-off and installed the deoxed 2.2 leak and running kings #4... (just for reference)
Click to expand...
Click to collapse
Interesting... I have the exact same setup as you right down to the kernel.
I tried rebooting the phone but that didn't help. I guess I could try to do it via adb, but I was just curious if others saw the same problem.
I am running Vitrous 2.7 (gmail 2.2.1) and it will not install from the market.
TD7424 said:
I am running Vitrous 2.7 (gmail 2.2.1) and it will not install from the market.
Click to expand...
Click to collapse
im running the same setup, and mine wont install either. I get "unsuccessful installation".
I'm running uncommon sense bats .8 install fails for me as well
Sent from my ADR6300 using XDA App
big.daddy said:
im running the same setup, and mine wont install either. I get "unsuccessful installation".
Click to expand...
Click to collapse
Same.
Unsure why.
Do we need a zip of the APK to apply or what?
Virtuous 2.7, won't install from the market.
CM6 - won't install from Market .
Package not signed correctly.
virtuous 2.7 - won't install.
"Installation unsuccessful"
EDIT: just saw this from rmk
"I know about it and expected it. The reason this is occurring is because our Gmail version had to be patched to work with Voice Search. I had been considering a new release the past few days anyway so this will act is a nice catalyst.
Since I am here posting, here's what I was thinking (please provide comments/feedback on it):
I want to move more apps back to /system/app. Prior to Virtuous Buddy and/or EZ-Customizer it was compelling to move as many apps as possible to /data/app. At this point, it just adds another place to have to go to remove stock apps. My thought is, it would be easier for you guys to either use Buddy or Customizer for EVERY stock app.
The trigger for this is two-fold. First, I discovered a bug in the /data/app logic which is just becoming increasingly complicated to deal with. And second, if everything is in one place, I can modify the scripts to move disabled apps rather than delete them, so you can easily toggle them off and on via buddy.
Our end result is the same, you can still easily remove everything, it just becomes simplified. I was thinking this next release would be 3.0 (given the magnitude of the change). Following 3.0, every upgrade would be made available as a small patch, like we had from 2.5 to 2.6.
What do you guys think?"
If you are rooted with a custom ROM, use Root Explorer to rename "Gmail.apk" to "Gmail.apb" then REBOOT. You should now be able to install Gmail update from Market.
-copied from a fb post, worked for me
I am also getting Installation Unsuccessful -- package not signed correctly...
---
C_01.3E.03P
Droid kernal 2.6.32.9-P3Droids ([email protected] #17)
voles-userdebug 2.2 FRFxx 49593 test-keys
I was using 2.2.1 and mine installed fine. I'm rooted also.
enigma429ad said:
If you are rooted with a custom ROM, use Root Explorer to rename "Gmail.apk" to "Gmail.apb" then REBOOT. You should now be able to install Gmail update from Market.
-copied from a fb post, worked for me
Click to expand...
Click to collapse
I couldnt get mine to update (sr 3.1 sense, kk bfs4, s off) until I did this. Now I'm updated.
Sent from my ADR6300 using XDA App
enigma429ad said:
If you are rooted with a custom ROM, use Root Explorer to rename "Gmail.apk" to "Gmail.apb" then REBOOT. You should now be able to install Gmail update from Market.
-copied from a fb post, worked for me
Click to expand...
Click to collapse
Did not work for me.
Edit: it is not allowing me to rename by simply long pressing and then clicking rename. Any ideas?
I searched "gmail" in Root Explorer and found /system/app/gmail.apk and tried to rename that but it would not work. Just keeps reverting to .apk even though it says rename successful.
Could I try moving the gmail.apk to another folder and then downloading?
enigma429ad said:
If you are rooted with a custom ROM, use Root Explorer to rename "Gmail.apk" to "Gmail.apb" then REBOOT. You should now be able to install Gmail update from Market.
-copied from a fb post, worked for me
Click to expand...
Click to collapse
Worked for me.
Running Virtuous 2.7.
angryspoon said:
Did not work for me.
Edit: it is not allowing me to rename by simply long pressing and then clicking rename. Any ideas?
I searched "gmail" in Root Explorer and found /system/app/gmail.apk and tried to rename that but it would not work. Just keeps reverting to .apk even though it says rename successful.
Could I try moving the gmail.apk to another folder and then downloading?
Click to expand...
Click to collapse
I had to change it from R/O to R/W to get it to be able to be renamed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mzmartipants said:
I had to change it from R/O to R/W to get it to be able to be renamed.
Click to expand...
Click to collapse
First thing I do every time is change to RW. Would not change it.
Didn't want to pay for root explorer, but this works:reboot into recovery, mount /system, then use the command prompt to move the Gmail.apk. Reboot and download and install from the market.
Setup: DInc running Skyraider 3.0 RC3
WARNING: THIS WILL WIPE /DATA! All of your data will be erased!
So the first thing I did when I got home from work is root my Thunderbolt and create a backup of a fresh wipe of Thunderbolt stock.
First off:
Android OS: 2.2.1
Device: mecha
ROM Name: 1.12.605.6
Rooted (Unsecured boot.img): Yes
Rooted (Superuser.apk + su): Yes
Busybox Installed: Yes
Nano text editor installed: Yes
/system/framework deodexed: Yes
/system/app deodexed: Yes
ROM will wipe data: Yes
Second:
I have tested it does work in its entirety. I had to remove the lines where it flashed boot.img but that is still in the .zip it just doesn't do anything with it since that code in the script it throws errors but without it flashes fine.
Third:
This is completely stock so it does contain the bloat. You can remove it as you see fit using Root explorer or freeze them with titanium backup.
Link:
Debloat: http://www.megaupload.com/?d=F60KZRU0
Bloated: http://www.megaupload.com/?d=RNUVRAM0
Credits:
dsixda for the kitchen to de odex this sweet device
ROOT TEAM:
"Scotty2, jamezelle, jcase, and all of Team AndIRC
Testers, especially ProTekk and Trident
Thanks to scotty2 for WPThis
Busybox was pulled from a CyanogenMod ROM, source should be available here
psneuter was pulled from somewhere, credit to scotty2, source here
All firmware credit goes to 911sniper
Jaroslav from Android Police for editorial help"
Thank you ALL for making this possible.
How do we install this Rom? I tried with CW recovery and no luck.
Thanks
I can flash it via CWR but it just hangs at the boot screen and won't go any further... I wish this would work, I just want a factory rooted/deodexed rom without anything removed so I can choose what stays and what goes.
JAYNO20 said:
I can flash it via CWR but it just hangs at the boot screen and won't go any further... I wish this would work, I just want a factory rooted/deodexed rom without anything removed so I can choose what stays and what goes.
Click to expand...
Click to collapse
Might wanna try Fastboot for flashing. IE replace the file in the permaroot tutorial with this one. Then skip the root steps as this is already rooted.
Str0ntium said:
Might wanna try Fastboot for flashing. IE replace the file in the permaroot tutorial with this one. Then skip the root steps as this is already rooted.
Click to expand...
Click to collapse
so we need to rename it to PG05IMG.zip?
or is there a better way?
Sorry guys for leaving you all hanging. I do have a newer .zip to flash but it doesn't have any of the bloatware (CityID etc) and has some google apps that are on market (Except for quicksearch because it stops the search button from working) to /data/app.
I will upload that later if you like .
Please do. This file is very much appreciated.
Sent from my Thunderbolt using Tapatalk
I would really like to have the file that is deodexed but still contains everything else... can you reupload that one too?
Both are up now. Enjoy.
gonna try something so nvm
Can someone explain exactly what Deodexed means.
Thanks
Jrocker23 said:
Can someone explain exactly what Deodexed means.
Thanks
Click to expand...
Click to collapse
Deodexed in a sense means you can edit and change the files as you like allowing custom figures,images, and animations in place of the stock. It basically allows for people to completely customize rooms to make the run and look as they like. Odexed is completely opposite and you would know a rom is odex because there are .odex files next of ever .apk in the system/app/ folder. You cannot change anything in a odex rom. The completely stock rom is odexed.
mjhuffer said:
Deodexed in a sense means you can edit and change the files as you like allowing custom figures,images, and animations in place of the stock. It basically allows for people to completely customize rooms to make the run and look as they like. Odexed is completely opposite and you would know a rom is odex because there are .odex files next of ever .apk in the system/app/ folder. You cannot change anything in a odex rom. The completely stock rom is odexed.
Click to expand...
Click to collapse
Understood, thank you vm... appreciate the info..
Thank searched high and low for a rom like this. Very much appreciated.
I installed the debloated version and now I have no 3G or WIFI. I'm stuck in 1X and when I try to enable WIFI I get a message that simply states "Error".
http://gititbit.ch/tHu3 - signed_032111_214510.zip
100mbit mirror of the debloated.
Thank you very much for this!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Axiom119 said:
I installed the debloated version and now I have no 3G or WIFI. I'm stuck in 1X and when I try to enable WIFI I get a message that simply states "Error".
Click to expand...
Click to collapse
Put the back cover on, give it about 10 minutes. The back cover is required for 3G/4G.
foszz said:
Put the back cover on, give it about 10 minutes. The back cover is required for 3G/4G.
Click to expand...
Click to collapse
I think ur 7 months or so late.
Sent from my ADR6400L using XDA App
I m on cataclysm Rom and Semaphore kernel. I was not sure whether tbis issue was kernel or rom related, so thought to put this question in this thread.
On opening trickstermod app, i m getting the following warning (plz see screenshot):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this some generic warning? Coz i never got this b4 (or may b didnt notice it). I dint modify any app.
Thanks in advance.
Sent from my Nexus 4 using Tapatalk
Seems only a trickstermod App issue, got my answer here:
http://forum.xda-developers.com/showthread.php?t=1768315&page=89
omer7 said:
Seems only a trickstermod App issue, got my answer here:
http://forum.xda-developers.com/showthread.php?t=1768315&page=89
Click to expand...
Click to collapse
I'm unsure... even though they say that there, I do not get this warning. Do you have a virus scanner? (I know, horrible bloated things for phones) might be worth getting one and having a poke around just to make sure?
Monotoko said:
I'm unsure... even though they say that there, I do not get this warning. Do you have a virus scanner? (I know, horrible bloated things for phones) might be worth getting one and having a poke around just to make sure?
Click to expand...
Click to collapse
No, don't have any anti virus in my phone.
But after restarting my phone and removing Super SU access from SuperSU (app), I'm not getting this warning again.
I also read in some other thread, that this is false positive (but that post was about a year old), so not sure why did i get that error, but now not getting it.
Lets see how it goes now :cyclops:
omer7 said:
No, don't have any anti virus in my phone.
But after restarting my phone and removing Super SU access from SuperSU (app), I'm not getting this warning again.
I also read in some other thread, that this is false positive (but that post was about a year old), so not sure why did i get that error, but now not getting it.
Lets see how it goes now :cyclops:
Click to expand...
Click to collapse
You removed SuperSU access from the SuperSU app? It's the SuperSU app that was generating the warning, warning you of another app that may have been modified. I don't think root access will work without SuperSU having root...
Monotoko said:
You removed SuperSU access from the SuperSU app? It's the SuperSU app that was generating the warning, warning you of another app that may have been modified. I don't think root access will work without SuperSU having root...
Click to expand...
Click to collapse
I didn't know which app (whether ROM/Kernel) was causing this issue, I read in some other thread where someone said, clear data (and cache) of trickstermod app and restart your phone (in addition, I removed trickstermod root access in SuperSU app as well). Restarted my phone, got that warning once or twice again I think, but checked it again, and this warning was no more there. I am still not sure what this warning is. Coz I didn't modify any app.
In that thread (link posted above) someone said, it is just a warning. Hope it is not an issue. . And I'm checking it, not getting this warning again, so could be it was a false positive.
And tell me is this warning given by SuperSU app? I've SuperSU (by ChainFire) app installed in my phone.
omer7 said:
I didn't know which app (whether ROM/Kernel) was causing this issue, I read in some other thread where someone said, clear data (and cache) of trickstermod app and restart your phone (in addition, I removed trickstermod root access in SuperSU app as well). Restarted my phone, got that warning once or twice again I think, but checked it again, and this warning was no more there. I am still not sure what this warning is. Coz I didn't modify any app.
In that thread (link posted above) someone said, it is just a warning. Hope it is not an issue. . And I'm checking it, not getting this warning again, so could be it was a false positive.
And tell me is this warning given by SuperSU app? I've SuperSU (by ChainFire) app installed in my phone.
Click to expand...
Click to collapse
Ah, yes it certainly looked like a regular SuperSU informational (like "root access was granted") and if I was to hazard a guess I would say that SuperSU noticed something had changed and thus gave you the warning. There will be something that triggers the warning, so your next course of action would be to find out what triggered it. It isn't something that will come up randomly or "for everyone"
You can maybe check the SuperSU logs?
Monotoko said:
Ah, yes it certainly looked like a regular SuperSU informational (like "root access was granted") and if I was to hazard a guess I would say that SuperSU noticed something had changed and thus gave you the warning. There will be something that triggers the warning, so your next course of action would be to find out what triggered it.
You can maybe check the SuperSU logs?
Click to expand...
Click to collapse
Yeah checked the Logs, just found info of app(s) which were granted SuperSU app.
ANyway hope it was just a false positive, but searching some other threads as well to find some more info...
If the rom comes rooted with any build in superuser, you don't have to flash SuperSU anymore. It will only create conflicts.
arffrhn said:
If the rom comes rooted with any build in superuser, you don't have to flash SuperSU anymore. It will only create conflicts.
Click to expand...
Click to collapse
Sorry, can't press thanks button, reached limit :fingers-crossed:
ANd I'm on Cataclysm ROM, and it came with SuperSU (app by ChainFire).
omer7 said:
Sorry, can't press thanks button, reached limit :fingers-crossed:
ANd I'm on Cataclysm ROM, and it came with SuperSU (app by ChainFire).
Click to expand...
Click to collapse
Lol, pro-tip here. XDA app has no thanks limit. Btw, it's good if you have solved your problems.
arffrhn said:
Lol, pro-tip here. XDA app has no thanks limit. Btw, it's good if you have solved your problems.
Click to expand...
Click to collapse
Thanks for the tip, and yeah it works. :fingers-crossed:
ANd problem not really solved, just I'm not getting that warning anymore, and I'm assuming it was a false positive or may be something else. I've done some search on google and XDA, i could only found 2 ppl who got the same warning.
I'm glad I'm the 3rd one. Lol ... (I know there wud b many other, didn't search too many pages)
SOLVED - Flashed suhide (linked in post 2) leaving this here for anyone else that struggles
Hi all, I'm trying to get Systemless root working with Android 7.0.
In the developer previews it was still passing CTS, as Android Pay was fully working; however now that "full" android 7.0 has been released my device is failing CTS profile match as soon as I flash SuperSU (2.77 or 2.78).
I've even tried the old ways of using the old commands in TWRP terminal
Code:
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
I'd like to be able to use Android Pay on 7.0, but still have root functionality for things like Tasker.
Is there any way to get it working currently?
(other than Magisk, I don't want to have to open an app, disable root, use android pay, go back to Magisk, enable root every single time.. Kinda defeats the point of android pay being easy to use)
Have you checked out suhide by Chainfire? I'm still on 6.0.1 but it passes safetynet now. Google has changed the detection so even systemless root fails now. I haven't had s chance to use AP for a purchase though. Others state in this thread that it works.
http://forum.xda-developers.com/apps/supersu/suhide-t3450396
Sent from my Nexus 6P using XDA Labs
swallowingled said:
Have you checked out suhide by Chainfire? I'm still on 6.0.1 but it passes safetynet now. Google has changed the detection so even systemless root fails now. I haven't had s chance to use AP for a purchase though. Others state in this thread that it works.
http://forum.xda-developers.com/apps/supersu/suhide-t3450396
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
Success! Thank you, I'll give AndroidPay a try and edit this to let you know
pk92 said:
Success! Thank you, I'll give AndroidPay a try and edit this to let you know
Click to expand...
Click to collapse
I'm very curious as well, let us know either way!
It was all working well for a couple of days by now SafetyNet has a "Response payload validation failed"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've been unsuccessful in googling, and AndroidPay is no longer functioning.
pk92 said:
It was all working well for a couple of days by now SafetyNet has a "Response payload validation failed"
I've been unsuccessful in googling, and AndroidPay is no longer functioning.
Click to expand...
Click to collapse
Yeah sadly everyone is getting that now with suhide. Like chainfire said, it'll be a never ending cat and mouse game. Have you tried Magisk by any chance yet? http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
I have not but it looks like people have been able to get it to work using that. With it you can unmount root temporarily and supposedly Android Pay works at that point.
DanRyb said:
Yeah sadly everyone is getting that now with suhide. Like chainfire said, it'll be a never ending cat and mouse game. Have you tried Magisk by any chance yet? http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
I have not but it looks like people have been able to get it to work using that. With it you can unmount root temporarily and supposedly Android Pay works at that point.
Click to expand...
Click to collapse
Magisk is really a last resort, I'd rather not have to open the app, unroot, use AP, open magisk, and reroot every time I need to make a payment. It kind of defeats the point of the convenience of Android Pay
pk92 said:
Magisk is really a last resort, I'd rather not have to open the app, unroot, use AP, open magisk, and reroot every time I need to make a payment. It kind of defeats the point of the convenience of Android Pay
Click to expand...
Click to collapse
I hear ya but I think this is going to be the norm. It won't be easy to have root AND Android Pay play nicely side by side. Not when big banks are involved. Google has to do all they can to stop it.
May I ask what you use root for? Only reason is because I too like to use Android Pay but like making a few modifications to my system, namely the Emoji font file, system font file, custom ad-blocking hosts file and an overlay file. I manually make all my changes to /system in TWRP and none of them trip up SafetyNet/Android Pay.
Of course if you're using actual apps that require root, my solution won't work for you.
DanRyb said:
I hear ya but I think this is going to be the norm. It won't be easy to have root AND Android Pay play nicely side by side. Not when big banks are involved. Google has to do all they can to stop it.
May I ask what you use root for? Only reason is because I too like to use Android Pay but like making a few modifications to my system, namely the Emoji font file, system font file, custom ad-blocking hosts file and an overlay file. I manually make all my changes to /system in TWRP and none of them trip up SafetyNet/Android Pay.
Of course if you're using actual apps that require root, my solution won't work for you.
Click to expand...
Click to collapse
+DanRyb would mind telling me how you use TWRP to install say system fonts, etc? While I generally root, I'm enjoying Pay on stock for now, but would like to make a few mods also. Thanks.
jackpollard said:
+DanRyb would mind telling me how you use TWRP to install say system fonts, etc? While I generally root, I'm enjoying Pay on stock for now, but would like to make a few mods also. Thanks.
Click to expand...
Click to collapse
I do it manually through adb command line but you could use a flashable zip too if you find one with the font you like. If making manual changes through adb, just boot into TWRP, go to Mount and make sure you check off /system. Fonts are all in /system/fonts. I replace a bunch of the Roboto*.ttf ones with a font I found like over a year ago. I also replace the emoji font with a custom one of my own which is NotoColorEmoji.ttf.
I'm not sure exactly WHY yet but it seems a custom kernel is needed to respect the changes I made. I attempted last night with just a simple modified boot image that removed the force encryption but all the changes I made in /system I couldn't see once booted. After I installed a custom kernel (I use ElementalX), I was able to make my changes and actually see them. I'm not sure if it has to do with dm-verity or not but I'm still learning as I go. Obviously I can't tweak any of the custom kernel settings using an app (since I don't have root installed) but for me that's OK.
DanRyb said:
I do it manually through adb command ....
Click to expand...
Click to collapse
Thanks for the details, I think I will make a nandriod and play a bit. Again, thanks!
I use root for Tasker, TiBu, AdAway, SDMaid, Nova Launcher (for quicker pull down)
As of right this second 9/13/2017 i have gotten SuperSU ElementalX kernel, SUHide and Busybox working, and YES it survives reboot
Instructions that i used
Flash new September Factory image
Boot phone setup password.ect
reboot using the modified TWRP.img in the other thread here"
Flash Boot.img to both slots from September Factory update
Flash ElementalX, SuperSu.zip and SUHide.zip reboot
when phone loads up installed meefik's Busybox
changed install path to /system/bin
and unselected replace existing applets
and BOOM BABY
ENJOY
let me know if it works for you guys
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ne0ns4l4m4nder said:
As of right this second 9/13/2017 i have gotten SuperSU ElementalX kernel, SUHide and Busybox working, and YES it survives reboot
Instructions that i used
Flash new September Factory image
Boot phone setup password.ect
reboot using the modified TWRP.img in the other thread here"
Flash Boot.img to both slots from September Factory update
Flash ElementalX, SuperSu.zip and SUHide.zip reboot
when phone loads up installed meefik's Busybox
changed install path to /system/bin
and unselected replace existing applets
and BOOM BABY
ENJOY
let me know if it works for you guys
Click to expand...
Click to collapse
Glad to hear this is working for you, it's not really anything that hasn't been covered in more depth in other threads / guides...
As a note; You would only lose root, if you flashed a kernel, but didn't flash SuperSU after && or by installing busybox into the wrong location or by replacing the system applets...
Personally, I install busybox into /sbin/supersu/bin because it has the advantage of not touching the /system partition at all - so for example; I can flash a a full factory image (rather than OTA), using flash-all script (removing the -w argument to not wipe data) and retain busybox.
Cheerz
Have you got any advice about viper/arise? I just need it and than I'm good to go :good:
TENN3R said:
Have you got any advice about viper/arise? I just need it and than I'm good to go :good:
Click to expand...
Click to collapse
Not really, no. I don't use viper or arise. I would say read through the related threads on them. There is bound to be good instructions.... sometimes I read through the comments, in particular; the last couple of pages on a given thread, as sometimes there is useful information.
I pretty much have a similar setup to your device, plus substratum and a few other root apps and tweaks. (Fdroid, adaway, afwall, etc).
Good luck.
Is there a difference in flashing the boot.img versus flashing the image minus the -W? I've been trying and trying but I always end up with boot loops and it going back to stock recovery. Usually the boot Loops start right away when I'm first rebooting the system. Last night I got Elemental and root installed it worked fine for about 30 minutes then started bootlooping and ended up at stock recovery again.
I used Busybox v1.27.2 from osm0sis
What I do:
- Flash the September update (I do a full wipe)
- Boot up, finesh the setup and set a pin
- boot modded twrp
- Enable MTP and copy the Files (BusyBox v1.27.2, EX Kernel 2.0.1, SuperSU v2.82 SR3 & Suhode v1.0.8)
- Flash EX Kernel, SuperSU, Suhide and BusyBox
- reboot and enjoy
PS: passing with Substratum is also no problem
Flash sr4 to prevent bootloop: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Sent from my Pixel using Tapatalk
trying to apply adaway seems to remove root and break twrps ability to mount /data
KittyRgnarok said:
trying to apply adaway seems to remove root and break twrps ability to mount /data
Click to expand...
Click to collapse
Adaway was giving me problems too. Started using Brave browser and haven't looked back. https://www.brave.com/
Installing busybox in /system/bin didn't work for me. Flashing Busybox from osm0sis did.
brownkid said:
Installing busybox in /system/bin didn't work for me. Flashing Busybox from osm0sis did.
Click to expand...
Click to collapse
Use meefix busybox not stericson
Droid1019 said:
Adaway was giving me problems too. Started using Brave browser and haven't looked back. https://www.brave.com/
Click to expand...
Click to collapse
This is the best adblocker for android, it uses dns block lists like pi-hole and root isn't needed since it uses the vpn interface:
https://f-droid.org/packages/org.jak_linux.dns66/
Sent from my Pixel using Tapatalk
Stericson Busybox has been updated for Android O.
https://forum.xda-developers.com/pixel-xl/how-to/busybox-oreo-t3672140/page2
Droid1019 said:
Adaway was giving me problems too. Started using Brave browser and haven't looked back. https://www.brave.com/
Click to expand...
Click to collapse
Adaway works great if you change the "Target hosts file" to "/data/data/hosts"
I installed the updated Stericson Busybox to /sbin/supersu/xbin and all working great.
KittyRgnarok said:
trying to apply adaway seems to remove root and break twrps ability to mount /data
Click to expand...
Click to collapse
I disagree, I dont have a problem with adaway.
TENN3R said:
Have you got any advice about viper/arise? I just need it and than I'm good to go :good:
Click to expand...
Click to collapse
Viper4arise does work but only with the older release...for me at least. I tried many times and ways with magnumopus and it wouldn't work. Using the 2.94 deurotomy aroma installer it's installed and processing.
devilsadidas said:
Viper4arise does work but only with the older release...for me at least. I tried many times and ways with magnumopus and it wouldn't work. Using the 2.94 deurotomy aroma installer it's installed and processing.
Click to expand...
Click to collapse
Same here. At least we have something
devilsadidas said:
Viper4arise does work but only with the older release...for me at least. I tried many times and ways with magnumopus and it wouldn't work. Using the 2.94 deurotomy aroma installer it's installed and processing.
Click to expand...
Click to collapse
To which older release of viper4arise are you referring to?