by pass untrusted App install actions - App Stores

Does any one know if it is possible to install a certificate on a Android device as type "VPN and App" certificate, and sign your app with this certificate via de keytool/jarsigner process. And then let it by pass the untrusted app restriction when deploying the app via a website?

Related

[Q] Help with ADB uninstall

After returning 4 HDs that developed charging and other problems following the setting of the "allow unknown sources" flag, we decided not to tempt fate with the 5th Nook HD and then I discovered that apks can be installed via ADB, bypassing the Android setting. There is a drawback, of course--the apps cannot self-update.
I did this with a copy of an apk that's no longer available in the PlayStore and which I had already installed on my NT/CM10. What I forgot was that this package came with an Aptoide Store app attached. The desired app installed on the Nook HD and runs fine, but we now get periodic random messages like "this app cannot be installed" blah, blah, blah. I'm assuming this is because the Aptoide store is trying to install itself, but of course is blocked by the Android setting that won't allow unknown sources.
My question: where do you suppose this uninstalled package is hiding? If I try to use the ADB uninstall command as if it were already installed, will that expunge it?

[How To] Bypass Lloyds and Santander Root Detection

Hi All,
I've seen mention of Santander but not of Lloyds bypassing the root detection. After much trial and error it's quite simple and my method will bypass both Santander and Lloyds. If bypassing Santander just do the same for the Santander app as ive said to do with Lloyds.
<--Update 08/06/19-->
Having flashed a new rom and following my steps again I received the detection message again but was resolved by using the Canary build of Magisk Manager.
To get Magisk Manager Canary click the link below:
https://github.com/topjohnwu/magisk_...pp-release.apk
Once installed, open Magisk Manager and go to
settings > Update Channel > Canary
Go back to Magisk home screen and swipe down to check for updates, you'll receive an update for the canary build. Once you update follow the guides original steps below.
<--End of update-->
In Magisk Manager Settings:
Enable Magisk Hide
Enable Sytemless Host
And if the option is available select "Hide Magisk"
In Adaway:
Download my exported blacklist from:
https://drive.google.com/file/d/1xCBB4iVA65gJTTYqbhU1qTlghVYyAL1S/view?usp=drivesdk
Then in adaway click the 3 dots in the top right to open the menu, select "Your Lists" then press the menu button again in the top right and press "Import all lists" and select the file you downloaded.
With the urls added go back to the adaway main screen and press "Download Files and Apply ad blocking" and Reboot device. If "Download Files and Apply Ad Blocking" doesn't appear, click "check for updates" and then download them which will do the same thing.
Once your phone has restarted install the Lloyds Banking app but don't open it. Go into Magisk Manager and select Magisk Hide from the menu and tick the Lloyds Banking app. Reboot phone and Lloyds should work perfectly!
I managed to do this from researching other threads and adding my own bits in so credit due elsewhere as well, as usual you can follow this guide but do so at your own risk, i take no responsibility
This should also work for Halifax and TSB but with a different URL nice work but what happens if they fix this? No banking app again....
Also do you know how to get past Natwest?
Doesn't work for me.
Hi Steve,
This is the first time ive noticed an application that has gone to greater lengths and was relatively easy to bypass. Given how long it took to come up with this technique of connecting to a url to blacklist your device i cant see them coming up with something new anytime soon.
All that is required to bypass this new technique is to log dns requests in Adaway and with the listed urls the app connected to for the login you simply block the urls and leave 1 out. Take for example Lloyds used 3 urls, i blocked two leaving only one allowed but Lloyds couldnt connect so that url was genuinely used to login, i then knew to allow that url and focus on the other two finally figuring out it was that url i listed that was being used to connect and block my device. With the app unalee to connect to that url it cannot verify if my device is blacklisted. Its time consuming as you need to restart after each new url you blacklist but its simple to do.
Muresan01 said:
Doesn't work for me.
Click to expand...
Click to collapse
Are you on the new Magisk 17.1? And after inserting the url to adaway you rebooted the device then installed lloyds then hidden it in magisk and rebooted again?
Muresan01 said:
Doesn't work for me.
Click to expand...
Click to collapse
Thread will be updated in a minute with a link to an Adaway blacklist export i made, i tried on a rooted S7 after seeing your post and it didnt work but i did it after a few tries, it seems i missed out a few urls.
Muresan01 said:
Doesn't work for me.
Click to expand...
Click to collapse
Thread updated
thanks @steve51184. Lloyds bank app works for me. Wondering how to go about for the Halifax bank app.
Elvisnazareth said:
thanks @steve51184. Lloyds bank app works for me. Wondering how to go about for the Halifax bank app.
Click to expand...
Click to collapse
Ill have a look into Halifax later and see if i can update the adaway list to work with all 3. If i do ill let you know and update the link
mrsweet1991 said:
Hi All,
I've seen mention of Santander but not of Lloyds bypassing the root detection. After much trial and error it's quite simple and my method will bypass both Santander and Lloyds. If bypassing Santander just do the same for the Santander app as ive said to do with Lloyds.
First go into the Lloyds app info (hold on Lloyds App icon and select "App Info") or you can do the same by going to "Settings > Apps > Lloyds Bank" and then select "Storage" and press "Clear Data". With all the stored information removed uninstall the Lloyds Banking app completely and reboot your device.
In Magisk Manager Settings:
Enable Magisk Hide
Enable Sytemless Host
And if the option is available select "Hide Magisk"
In Adaway:
Download my exported blacklist from:
https://drive.google.com/file/d/1xCBB4iVA65gJTTYqbhU1qTlghVYyAL1S/view?usp=drivesdk
Then in adaway click the 3 dots in the top right to open the menu, select "Your Lists" then press the menu button again in the top right and press "Import all lists" and select the file you downloaded.
With the urls added go back to the adaway main screen and press "Download Files and Apply ad blocking" and Reboot device.
Once your phone has restarted install the Lloyds Banking app but don't open it. Go into Magisk Manager and select Magisk Hide from the menu and tick the Lloyds Banking app. Reboot phone and Lloyds should work perfectly!
I managed to do this from researching other threads and adding my own bits in so credit due elsewhere as well, as usual you can follow this guide but do so at your own risk, i take no responsibility
Click to expand...
Click to collapse
Works perfectly
Thank you !
Muresan01 said:
Works perfectly
Thank you !
Click to expand...
Click to collapse
Great to hear
Awesome, works for Halifax app as well!
This also allows the Metro Bank app to run. Thanks
Could you make this to work with Digibank DBS Indonesia? I'm stuck to stock rom because of this
steve51184 said:
This should also work for Halifax and TSB but with a different URL nice work but what happens if they fix this? No banking app again....
Also do you know how to get past Natwest?
Click to expand...
Click to collapse
Natwest in UK does not prohibit rooted phones.
Deleted
haybill said:
Sent from my SM-N910F using Tapatalk
Sorry, removed my post-- found both XDA source and FDroid source for Adaway, doh!!
Click to expand...
Click to collapse
Just want to say Thanks for putting this together, there are several Threads giving info but this one has got it all in an easy to use format.
Sent from my SM-N910F using Tapatalk
And, finally, after about a month of failing to access my Bank account--- success, after following all the necessary actions, I can now once again use Online Banking via the App.
Let's hope they don't make further changes that mean we can't, in the future.
Sadly it doesn't work for me.
Santander app on Oneplus 5T.
Get the solid red screen for a second or so then "Santander UK has stopped"
Is this what usually happens if the app detects root?
Cheers!
spwyatt said:
Sadly it doesn't work for me.
Santander app on Oneplus 5T.
Get the solid red screen for a second or so then "Santander UK has stopped"
Is this what usually happens if the app detects root?
Cheers!
Click to expand...
Click to collapse
I'd expect the app to tell you that you have a rooted phone instead of crashing. I'd try clearing data again, then removing the app completely and making your you followed the instructions fully.
If you haven't Magisk 17.1 then getting this together with the latest stable manager is also recommended. For a weird reason 16.4 has issues for me after some ROM update and wouldn't pass the Safetynet check any longer (even after complete removal and magisk reinstall). However, 17.1 somehow fixed it for me.
While I'm no fully sure about Santander, uninstalling and reinstalling the app also was essential for Lloyds on my phone (just clearing data and adding + applying the blacklist still showed the rooted message).
Good luck,
This thread is amazing, good work OP!
I am having an issue unfortunately when it comes to selecting the downloaded item. I'm unable to select the file from my Downloads, slight grey hue and long holding tap does nothing. (I'm trying to import)
I've checked and in the Downloads manager the file definitely exists, I just can't seem to apply it.
Any ideas?
EDIT: I solved the issue by granting Adaway storage permissions and importing the file from my Google Drive.

Google device policy and magisk.

Is it possible to get magisk and Google device policy on a work profile Google account working at the same time. Using magisk hide doesn't work and after a reboot resulted in "device compromised"
fma965 said:
Is it possible to get magisk and Google device policy on a work profile Google account working at the same time. Using magisk hide doesn't work and after a reboot resulted in "device compromised"
Click to expand...
Click to collapse
Same problem; also magisk hid Google Play Services and that didn't help either.

Enable ECG(BP Featur) On Non-Samsung Phones for Galaxy Watch 3, Active 2 Step-By-Step

Update 09/29/20:
1. The latest Samsung Health Monitor Version 1..1.0.175.Caravana (Thanks Caravana for the Mod) Download
This tutorial should work on all Android Phones to enable ECG for your Galaxy Watch 3 and Active 2. BP might also work the same way when it is released in the US.
Basic idea is to create your own certificate to sign ECG.tpk application and install it on your watch, then install the Samsung Health Monitor Mod app on your phone.
I have read lots of threads on XDA and can't find a complete tutorial about how to do it for Galaxy Watch 3 or Active 2. Hope this step-by-step tutorial will help. The whole process took me around 30 mins, it shouldn't be very hard. Make sure you back-up your watch first, just in case anything goes wrong and you need to restore data.
You will need an Android Phone, a Windows PC and Galaxy Watch 3/Active 2 watch for this tutorial. And a wireless network.
Downloads:
1. Download Java for Windows offline (64 bit) https://www.java.com/en/download/manual.jsp and install it.
2. Download JavaSE/Oracle JDK https://www.oracle.com/technetwork/java/javase/downloads/index.html Click "JDK Download" from the top the latest version, then it will direct you to a new page, find "Windows x64 Installer" click the download page from the page and install it.
3. Download Tizen SDK https://developer.tizen.org/development/tizen-studio/download Download Latest Tizen Studio with IDE installer, click "64 Bit" to download and install it.
4. Download ecg.tpk, BP.tpk, Fit2Installer from here(ecg_downloads)
5. Download Samsung Health Monitor Version 1..1.0.167.Caravana (Thanks Caravana for the Mod) from here (See update 09/29/20 from the top of the thread to download the latest version)
On Your Phone:
1. Install Samsung Health Monitor Version 1..1.0.167.Caravana on your phone. Open the app enter your name, BOD and etc to finish the setup.
On Your Watch:
1. From your watch, Go to "Settings"->"About Watch"->"Software"->Click On "Software Versio" 5 times until it shows "Developer mode turned on"
2. Go back to "About Watch", make sure it shows "Debugging is turned on", it not click "Debugging" and turn it on.
3. Go to Wifi settings on the watch, change wifi setting to always On, and connect it to the same wireless network with your PC.
4. Reboot the watch. Make sure wifi is connected after the reboot.
From Your PC:
1. Launch Tizen Package Manager and Navigate to 5.5 wearable(It depends on your watch's software version, eg mine shows Tizen Version 5.5.0.1, so I navigate to 5.5 wearable), then click Install icon
2. Scroll down to the Tizen SDK tool and click the install icon
3. Click on the Extension SDK tab
3.1 Click the arrow on Extras
3.2 Install Samsung Certificate Extension and Samsung Wearable Extension
4. Check the Progress tab, once it shows 100%, you can close Tizen Package Manger and do not launch Tizen Studio(we don't need to use Tizen Studio)
5. Open up "Certificate Manager"
6. Click on the "+" icon and from the pop-up window click Samsung Logo.
6.1 Device Type -> Mobile/Wearable, Click Next
6.2 Certificate Profile(Give it whatever name you like), Click Next
6.3 Author Certificate -> Create a new author certificate, Click Next
6.4 Author Certificate -> Enter Author name, Password, Confirm Password as required(Remember the password,. you will need it when you sign the TPK file) and click next
6.5 A pop up will ask you to sign in to your Samsung account, enter your account information and sign in
6.6 Now it will show your certificate has been saved at C:/Users/USERNAME/SamsungCertificate/cert_name and click next.
6.7 Create a new distributor certificate and click next
6.8 Do not change Privilege and password information, do not close these windows, just leave it there, we need to enable debug mode from the watch and connect it to PC now.
7. Open Tizen "Device Manager" from the PC.
8. Click the "Remote Device Manager" icon from top right corner.
9. From pop-up windows, click the "Scan Devices" icon from the top right corner.
10. Once it find your watch turn the connection switch to on. and close pop-up windows. At this time, you should able to see lots of debugging information from Device Manager. (If you don't see debug information, try these steps: 1. Turn off your windows firewall 2. turn off bluetooth&GPS on your watch 3. reboot your watch )
11. Go back to Tizen Certificate Manager, step 9.8, we can see one DUID has been added automatically. Click next.
12. It will show your certificate has been saved at C:/Users/USERNAME/SamsungCertificate/cert_name, Click Finish.
13. Download Fit2installer.zip unzip the whole folder to your desktop.
14. Go to the certificate(C:/Users/USERNAME/SamsungCertificate/cert_name) you just created and copy all files. inside the folder
15. Go to C:\Users\USERNAME\Desktop\Fit2Installer\cert Paste all the certificate file you just copied.
16. Copy ecg.tpk file and paste it at C:\Users\USERNAME\Desktop\Fit2Installer\sign_me
17. Click sign.bat from the Fit2Installer folder. Enter your certificate password.
18. It will show "Package( C:\Users\USERNAME\Desktop\Fit2Installer\install_me\ecg.tpk ) is created successfully." and enter any key to close the window.
19. Now go to "Device Manager", right-click your device, choose "install app", Select ecg.tpk file from C:\Users\USERNAME\Desktop\Fit2Installer\install_me.
20. Wait a few seconds, you should see ECG app has been installed on your watch. Open it.
21. Open the "Samsung Health Monitor" app from your phone, you should be able to read the ECG data from your watch now.
As Blood Pressure has not been released in the U.S, once it released, you should be able to activate for Non-Samsung phone the same way. You can disable debug mode if you want now.
Enjoy!
Reference:
1. https://forum.xda-developers.com/showpost.php?p=83574519&postcount=6
2. https://www.reddit.com/r/GearS3/comments/aljplu/tutorial_how_to_install_tpks_and_wgts_onto_your/
3. https://forum.xda-developers.com/smartwatch/gear-fit/howto-sign-sideload-tizen-applications-t3639793
Nice! I'm in the process of following this guide at the moment. Tizen Studio's package installers are so slow!
Nice to have well documented details! kudos
Step 6. I don't have a Samsung logo. When I click the + in certificate manager it just asks me for a certificate profile name
Is there a risk of voiding the warranty or bricking the watch doing this?
Is there an IPA file for this that can be sideloaded onto an iphone? I'm no expert at this stuff and have only followed the great instructions here before so not sure. Or is there any way to connect my GW3 to my Samsu g Tab S6 on Verizon that shares my iPhone number? I'd like to get the Health Monitor app features as I really don't want to go back to an apple watch.
Supposedly on tizen 5 there is no bp.tpk - ecg and bp are now both in ecg.tpk. installing old ecg.tpk may be main reason for bp not to work. Did anyone try to follow the tutorial but use new ecg.tpk? Does ecg.tpk need to be specialy prepared to by signed with certificate or can we do it with new ecg.tpk that has been posted by caravana?
Can there be a mess if in the future I change my phone and take a samsung?
Does the smartwatch remain unaffected? Will I always have to update it manually?
Works great!
Anyone else having issues w the carvana health monitor app? I keep getting an error saying it cant be run on a rooted phone...
g33gz said:
Anyone else having issues w the carvana health monitor app? I keep getting an error saying it cant be run on a rooted phone...
Click to expand...
Click to collapse
hide it in magisk hide section of Magisk manager app.
Also, make sure you're passing safetynet on magisk manager & from manager's settings, enable magisk hide, also hide magisk manager & give it another name.
Sent from my HD1901 using Tapatalk
rohit83 said:
hide it in magisk hide section of Magisk manager app.
Also, make sure you're passing safetynet on magisk manager & from manager's settings, enable magisk hide, also hide magisk manager & give it another name.
Sent from my HD1901 using Tapatalk
Click to expand...
Click to collapse
I can confirm I pass safetynet, I have all samsung related items enabled in the hide section and I've renamed the magisk manager app and renamed it. Still nothing
g33gz said:
I can confirm I pass safetynet, I have all samsung related items enabled in the hide section and I've renamed the magisk manager app and renamed it. Still nothing
Click to expand...
Click to collapse
strange, it worked for me though after hiding it in magisk.
Sent from my HD1901 using Tapatalk
rohit83 said:
hide it in magisk hide section of Magisk manager app.
Also, make sure you're passing safetynet on magisk manager & from manager's settings, enable magisk hide, also hide magisk manager & give it another name.
Sent from my HD1901 using Tapatalk
Click to expand...
Click to collapse
rohit83 said:
strange, it worked for me though after hiding it in magisk.
Sent from my HD1901 using Tapatalk
Click to expand...
Click to collapse
Maybe its because I'm on LineageOS? I have an S9
g33gz said:
Maybe its because I'm on LineageOS? I have an S9
Click to expand...
Click to collapse
Not sure man, I'm on Oxygen OS Open beta, rooted on my Oneplus 7t.
Sent from my HD1901 using Tapatalk
Thank you very much!! @xxstd
I had some problems running "sign.bat" due to relative path command routes, but after "customizing" the script changing to absolute path, all went ok.
I've signed BP.tpk and ECG.tpk and both are running OK in my GW3. I live in Spain, and here in Europe neither ECG nor BP are approved, so it is not the reason your BP tpk is not working IMHO.
plouprou said:
Thank you very much!! @xxstd
I had some problems running "sign.bat" due to relative path command routes, but after "customizing" the script changing to absolute path, all went ok.
I've signed BP.tpk and ECG.tpk and both are running OK in my GW3. I live in Spain, and here in Europe neither ECG nor BP are approved, so it is not the reason your BP tpk is not working IMHO.
Click to expand...
Click to collapse
I tried installing bp and it failed to install. But ecg worked.
plouprou said:
Thank you very much!! @xxstd
I had some problems running "sign.bat" due to relative path command routes, but after "customizing" the script changing to absolute path, all went ok.
I've signed BP.tpk and ECG.tpk and both are running OK in my GW3. I live in Spain, and here in Europe neither ECG nor BP are approved, so it is not the reason your BP tpk is not working IMHO.
Click to expand...
Click to collapse
Can you confirm the Tizen version from your watch? I know if you are runing Tizen 4.0.0.8 you could get BP works as well. Only ECG for Tizen 5.
S-C said:
Step 6. I don't have a Samsung logo. When I click the + in certificate manager it just asks me for a certificate profile name
Click to expand...
Click to collapse
Hmm, are you using the latest version Tizen SDK? Mine is Tizen Studio 3.7, they might change the UI a little bit for different versions.
Lazyboy8134 said:
Is there a risk of voiding the warranty or bricking the watch doing this?
Click to expand...
Click to collapse
Well, as the debugging mode has been enabled, if you tell Samsung they will possibly decline the warranty since they don't know what you have done to the watch...... But you can always turn it off, and reset the watch anytime you want.

Pixel 4 XL CA Certificate Not Trusted

Hello, I have installed a Burp Suite CA certificate in /system/etc/security/cacerts and gave it the correct permissions (chmod 644 and chown root:root). I see the certificate listed in trusted system certificates (not user), and it is enabled. Despite this, all HTTPS connections in all apps throw a certificate warning. I have never encountered this before. I'm using a Pixel 4 XL with LineageOS 19.1. Any advice would be much appreciated.
rhamnetin said:
Hello, I have installed a Burp Suite CA certificate in /system/etc/security/cacerts and gave it the correct permissions (chmod 644 and chown root:root). I see the certificate listed in trusted system certificates (not user), and it is enabled. Despite this, all HTTPS connections in all apps throw a certificate warning. I have never encountered this before. I'm using a Pixel 4 XL with LineageOS 19.1. Any advice would be much appreciated.
Click to expand...
Click to collapse
How about using Move Certificate Module from magisk, it will automatically trust the certificate, save the hassle from above
xracerx123 said:
How about using Move Certificate Module from magisk, it will automatically trust the certificate, save the hassle from above
Click to expand...
Click to collapse
I did use this module, and while it did what it was supposed to do, all apps still threw certificate warnings.

Categories

Resources