So, my banking app was working for months. Then it went and updated without my permission (had auto update enabled without realizing). Now it's discovering root. I updated Magisk, and followed a number of updated guides (zygisk, safetynet, shamiko... etc.) None worked.
Then I gave up and decided to downgrade my banking app. I don't believe an older version of the app is available for download, but I have a backup of my entire phone.
So, if any geniuses out there are reading this, I have two questions:
1. In your opinion, will copying app files from a back up to an android phone work? Or do other things have to be modified, such as registry and such?
2. I looked through the back up AND my phone, but I can't find the files of any application, even the installed ones. Does anyone know where they are located?
Thanks
Related
//EDIT: Please delete this thread. Titanium Backup installed BusyBox for me after I clicked the "Problem?" button. Sorry!
**Skip to the other asterisked line to skip the long story**
Last night I decided "(vulgarity here) AT&T!" and decided to load FroYo myself.
After reading for hours (on top of reading I've been doing for a few weeks) it seemed it was easier to root on 2.1, then update to 2.2.
I rooted, then installed 2.2 only to find out I was no longer rooted when I tried restoring my apps with MyBackup Pro. After tons of searching and trying 3 "one click" style rooting programs, many times over, the SuperOneClick method worked, only after I did the shell root, and then root button.
Awesome! I had a rooted 2.2 captivate! Restoring my apps with MyBackup Pro let me knew it worked, and then I was also able to install a non-market foreign language pack for the AnySoftKeyboard app. I also installed the MarketAccess app and I'm running the T-Mobile US code, so I'm pretty sure I've got root.
Tonight I wanted to get rid of all the AT&T garbage still on the phone, and a guide I found told me that Titanium Backup would allow me to do so (still not sure if it can all be done from the phone though). I downloaded and installed Titanium Backup, opened it up, clicked the button to allow SuperUser, but I get an error message:
Sorry, I could not acquire root privileges. This application will *not* work ! Please verify that your ROM is rooted and includes BusyBox, and try again.
Pretty sure I'm rooted, I am assuming I only require BusyBox be on the phone?
**I was under the impression that rooting and BusyBox was the same thing, or went hand-in-hand, one needing the other.
After now 4 more hours of searching, I can't seem to find a guide that only installs BusyBox, and I'm hesitant to try any of the Root and BusyBox in one methods for fear of the root not working and potentially messing something up.
I found one posting that requires a bunch of commands, but I have no idea where to do them from/in or what to do with the phone.
If anybody could link me to or tell me how to install BusyBox that would be awesome! I am rooted on FroYo. I have the drivers installed. I have DroidExplorer installed. Not sure of anything else that may have come in the .zip files I downloaded that might be installed, so assume only the drivers and DroidExplorer and installed.
Thanks in advanced!!
Busybox is an app on the market, download, open app, install, profit
Sent from my GT-I9000 using XDA App
Hi, it wouldn't surprise me if this has already been answered elsewhere, but I can't seem to find it.
I want to upgrade my P7 because all my music apps just stop at random. I assume it's a firmware problem. It happens with internet radios, Spotify both online and offline etc. I also need to root my phone to get rid of unneeded system apps and prevent apps like Swype from reading my location all the time (google "Swype location requests").
Rooting seems to be straightforward, but will OTA upgrades work afterwards?
EMUI 2.3
Build number P7-L10V100R001C00B133SP01
Custom Version CUSTC432D133SP01
I'm in Norway, if that matters
From someone that had the root before, OTA won't work. You would have to force the update. I'm on 609 and it works perfectly well (well ... I don't use the basic music app as it has some weird characters recognition and it doesn't have a "genre" tab, but Rocket Player doesn't stop randomly and it did when I was on 133, so I guess the update solved the problem). You can still upgrade and root again.
A question which might be out of subject but, what do you use to get rid of the apps and what are the apps that are not dangerous to get rid of?
thanks a lot!
Thanks! I'll look for the procedure on flashing new firmware and rooting it again, I am a little worried about flashing the wrong files and getting a chinese phone
I'll probably use Root Uninstaller to get rid of the weather and music apps, the bundled web browser, Hangouts and stuff like that. If I remember correctly, Root Uninstaller warns you against uninstalling essential system apps. But most importantly I need to be able to keep apps from leaking private data.
So the plan is to first force an upgrade, assuming there is one for my region, then root.
Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Googling has led me t believe that this is an error related to the app detecting root. I tried both of these methods, but neither has worked. http://bit.ly/1LnwzAZ http://bit.ly/1LnwEog . I've tried each separately with rebooting in between as well as trying them together all to no avail.
Other than following the guide above the only root-related things I have modified on the phone are the removal of some verizon apps via titanium backup and adding the following xposed module: "NoSafeVolumeWarning".
One thing that I noted was when I uncheck "Enable Superuser" inside of SuperSu 2.46 it displays a message saying "Uninstall Failed !" It still displays the "Superuser is disabled and hidden" underneath the box and if i enable it again and disable it it does not pop up with the uninstall failed message. Does this have something to do with write protection?
Any help would be greatly appreciated!
Thanks,
Adam
johnnyboy239 said:
Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Click to expand...
Click to collapse
Having the exact same issue. Just upgraded to 5.1 today, xposed Rootcloak as well as No Device Check installed. Also tried Disable SU. Still get the same issue.
Same. I tried uninstalling SU, Hide My Root, and Rootcloak...nothing has worked. Found out today that the app updated when I went to buy something at Walgreen's. How ****ing embarrassing is that?
So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.
Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.
Same problem, few apps frozen with TiBu and xposed installed. Any other work around? s
johnnyboy239 said:
So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.
Click to expand...
Click to collapse
check to see if your phone allows pin codes to be deactivated at times. I have mine set to not be used at home work and if I am carrying the phone. It is quite useful feature in settings Lockscreen but I am on COS 12.1 OnePlus basically CM
I haven't tried it yet, but I think they only way we'll get this working on root is to install it on stock unrooted, back it up with TiB or Helium, root and then reinstall/restore.
Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.
Ezekial said:
Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.
Click to expand...
Click to collapse
I'm in the same boat. Couldn't get AP to work. Just loaded up the previous version of Wallet. Now have two wallet apps, but whatever. Both appear to be working.
Has anyone tried to get Android Pay working by re-locking the bootloader and temp unrooting on a Nexus device (say, a tablet), then getting AP up and running, and then checking to see if it was usable on your other device(s)??....I was curious if Android Pay would work on ALL of your devices once it was set up properly. Working with lock, unlocking, rooting, etc. is much easier on a Nexus than it would be to work on a Moto, or similar.
Does this make any sense?
KenNashua said:
Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.
Click to expand...
Click to collapse
Tried AP for the first time at Panera today and failed...seems even with Root Cloak on AP and Google Play Service as well as No Device Check, it still fails.
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
same thing happened to me just now.
not sure what to do, not sure if i have to reinstall everything again
fmkilo said:
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
Click to expand...
Click to collapse
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
JokersWild0075 said:
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
Click to expand...
Click to collapse
Listen up folks. Do not and i repeat do not update any of samsungs apks. Until we can find out whats going on. It seems that samsung is now pushing updates thru their apks to check and get rid of SU. They are getting sneaky. So for now do not update any samsungs apk, not even thru google. Also do not update SU, this is another way to lose root. We are working on it. Please do not ask if we found anything, if a fix is found we will post our findings.
If you need shealth, iris scanner, samsung pay, android pay, or any other samsung apk, then you need to stay on stock firmware and not use root.
Also if anyone is having issue with files or odin not flashing, make sure you are not on the new PI4 stock ROM, if you are then odin will fail everytime and at this moment there is no way to root or down grade to the older firmware.
Otherwise Try to redownload all files as it seem that afh is/was having alot of issues with uploads and downloads. This not something that we can fix as we dont host or own that site.
Can you guys break down the steps to regain root without reinstalling the OS? Mine also lost root on v2.
It looks like my S-Health was automatically updated to the latest version, which has been reported to be a root of the cause.
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
elite-fusion said:
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
Click to expand...
Click to collapse
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
galaxyuser88 said:
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
Click to expand...
Click to collapse
I am currently logged into the Samsung account and have been for about 2 days now with no ill affects so far, downloaded a couple themes is all...that is with all the Sammy stuff froze and functional root.
I got a custom ROM and it tripped KNOX, I got bored of the custom ROM and went back to stock android, not realising I had tripped my KNOX somehow. After finding this out due to secure folder not working and my banking app (barclays) sh**** itself on me I decided to root it since I had nothing to lose. I use Magisk and for a while the barclays app worked, until it didn't, and I haven't been able to get it to work anymore.
I've tried:
- Hiding the app
- Changing my android ID with both apps and the adb shell
- Reinstalling and trying all of the above
I need help as it's crucial for me to get this app to work again, I haven't had it for a couple of months but now that I have an actual income i need it.
And if I can't get it to work, are there any banking apps that support barclays?
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps