Related
Hi,
I'm trying to find an exchange security bypass mod for Samsung Galaxy Note 8.0 (3G)
Have tried the following and they all don't seem to be compatible with the stock ROM
XPosed Module - http://forum.xda-developers.com/nex.../xposed-mod-bypass-exchange-security-t2483361
Xposed module - Exchange Security Bypass (No PIN/No Admin) - Android 4.1+ [v6.0] http://forum.xda-developers.com/showthread.php?t=1749921
Any thoughts?
My Device and Software details are
Android version: 4.1.2
Model No: GT-N5100
Kernel version:3.0.31 (KST 2013)
Build number: JZ054K.N5110XXBMD1
consultguru said:
Hi,
I'm trying to find an exchange security bypass mod for Samsung Galaxy Note 8.0 (3G)
Have tried the following and they all don't seem to be compatible with the stock ROM
XPosed Module - http://forum.xda-developers.com/nex.../xposed-mod-bypass-exchange-security-t2483361
Xposed module - Exchange Security Bypass (No PIN/No Admin) - Android 4.1+ [v6.0] http://forum.xda-developers.com/showthread.php?t=1749921
Any thoughts?
My Device and Software details are
Android version: 4.1.2
Model No: GT-N5100
Kernel version:3.0.31 (KST 2013)
Build number: JZ054K.N5110XXBMD1
Click to expand...
Click to collapse
OK, what is doing the hack to accomplish??? Exchange uses security features, so wouldn't that break functionality???
gooberdude said:
OK, what is doing the hack to accomplish??? Exchange uses security features, so wouldn't that break functionality???
Click to expand...
Click to collapse
Trying to check my corporate exchange email w/i being forced to 'always key-in a PIN', encrypted drive etc. I'm OK for all other enforcements that come with the exchange sync (e.g. force data wipe etc). Looking for a convenience factor.
Makes sense?
consultguru said:
Trying to check my corporate exchange email w/i being forced to 'always key-in a PIN', encrypted drive etc. I'm OK for all other enforcements that come with the exchange sync (e.g. force data wipe etc). Looking for a convenience factor.
Makes sense?
Click to expand...
Click to collapse
Ah, OK, I see... Have seen some thing about bypassing PIN for corporate email a few months back. Will look for it again, when I have time Monday. I thought you were disabling it completely or something.
OK, I don't have a corporate setup with exchange so I cannot test.
My xposed module has a security option though it is not enabled and I have no way to test.
Here is a thread on another site... http://mobility.forumsee.com/a/m/s/p12-9290-072026--exchange-security-bypass-no-pin-android.html
I would just unzip the two files and side load them from SD, after doing a complete backup in TI Backup, and removing the two installs associated with the replacement apps.
This way no old settings or double apps will be created.
Hi,
First of all I'm new here. I have recently rooted and installed Lineage OS on my HTC One m8. I have noticed that one of my apps (Adidas Confirmed) does not support rooted devices. Therefore I just tried (15 min ago) to flash SUhide on my phone. This resulted in a boot-loop and I therefore had to restore my device. Is there any other way to hide the fact that my device is rooted? As far as I know Xposed framework isn't out yet for Android 7.0 and I can't get Cydia substrate to work with root cloak. Btw I have S-off (not sure if this makes a difference to why the methods I have tried didn't work or not. Just wanted to mention)
Thanks in advance!
Use Rootcloak
http://repo.xposed.info/module/com.devadvance.rootcloak2
Sent from my ONE A2003 using Tapatalk
---------- Post added at 12:18 AM ---------- Previous post was at 12:16 AM ----------
princepavs said:
Use Rootcloak
There is version for nougat too google it too
http://repo.xposed.info/module/com.devadvance.rootcloak2
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Sent from my ONE A2003 using Tapatalk
There's no Xposed Framework for Nougat. Maybe he can try to use Magisk. Magisk has option to hide the root.
mefistoreyon said:
There's no Xposed Framework for Nougat. Maybe he can try to use Magisk. Magisk has option to hide the root.
Click to expand...
Click to collapse
Thanks! I'll try it out. Btw I can see you have S-off. Should I do that too for my m8?
BeastyUmbrella said:
Thanks! I'll try it out. Btw I can see you have S-off. Should I do that too for my m8?
Click to expand...
Click to collapse
No, you don't need to. S-OFF is giving you more permissions, like to flash h/k mod on sense rom or to flash firmware easily.
mefistoreyon said:
No, you don't need to. S-OFF is giving you more permissions, like to flash h/k mod on sense rom or to flash firmware easily.
Click to expand...
Click to collapse
Thanks! The Magisk manager worked
BeastyUmbrella said:
Hi,
First of all I'm new here. I have recently rooted and installed Lineage OS on my HTC One m8. I have noticed that one of my apps (Adidas Confirmed) does not support rooted devices. Therefore I just tried (15 min ago) to flash SUhide on my phone. This resulted in a boot-loop and I therefore had to restore my device. Is there any other way to hide the fact that my device is rooted? As far as I know Xposed framework isn't out yet for Android 7.0 and I can't get Cydia substrate to work with root cloak. Btw I have S-off (not sure if this makes a difference to why the methods I have tried didn't work or not. Just wanted to mention)
Thanks in advance!
Click to expand...
Click to collapse
I cannot give you a definative answer concerning your ROM mut I too have a rooted HTC One (M8). Post rooting I tried various ROMs from Cyanogen mod but none of these were very up-to-date for long and Android has been quite vulnerable since most manufacturers take an expediant and cynical view when it comes to supporting non-cutting edge hardware (HTC was one of the worst) and supplying security patches. I should add I try to avoid Google and the big social media platforms because I am not prepared to trade privacy (hand over personal data) for the sake of functionality. So, I have been using Moke ROM - MK60.1 Android security patch 1 April 2017. I tried usin MK71 Nightly OTA release but found them unstable - they lost dialer and network functionality after 24 hours. This is where my comments become more relevant. I have several proprietry UK banking apps installed including FinTek ones. None of them is supposed to instal on a rooted device, not at least without saying 'rooted - no go'. Under settings, developer options root access is controlled. The options are: Disabled Apps only ADB only Apps and ADB. None of the Fintek apps function but the main legacy bank app does even though it is not supposed to. In conclusion it seems to be that the app has code capable of interrogating the phone OS and detecting rooted status. Depending on the quality of the program it may correctly determin rooted status, or not. It is highly unlikely there is any intervention available to the rooter to combat this.
nickbw said:
I cannot give you a definative answer concerning your ROM mut I too have a rooted HTC One (M8). Post rooting I tried various ROMs from Cyanogen mod but none of these were very up-to-date for long and Android has been quite vulnerable since most manufacturers take an expediant and cynical view when it comes to supporting non-cutting edge hardware (HTC was one of the worst) and supplying security patches. I should add I try to avoid Google and the big social media platforms because I am not prepared to trade privacy (hand over personal data) for the sake of functionality. So, I have been using Moke ROM - MK60.1 Android security patch 1 April 2017. I tried usin MK71 Nightly OTA release but found them unstable - they lost dialer and network functionality after 24 hours. This is where my comments become more relevant. I have several proprietry UK banking apps installed including FinTek ones. None of them is supposed to instal on a rooted device, not at least without saying 'rooted - no go'. Under settings, developer options root access is controlled. The options are: Disabled Apps only ADB only Apps and ADB. None of the Fintek apps function but the main legacy bank app does even though it is not supposed to. In conclusion it seems to be that the app has code capable of interrogating the phone OS and detecting rooted status. Depending on the quality of the program it may correctly determin rooted status, or not. It is highly unlikely there is any intervention available to the rooter to combat this.
Click to expand...
Click to collapse
Thanks for the reply! In the meantime, I have bought a Samsung galaxy s8 and put my HTC One m8 on a shelf. However, I remember that I managed to solve the issue somehow through Magisk and their "hide root function". It may have been because of an update to the Adidas app or a Magisk update, I am not sure. Hope this was somewhat helpful
BeastyUmbrella said:
However, I remember that I managed to solve the issue somehow through Magisk and their "hide root function". It may have been because of an update to the Adidas app or a Magisk update, I am not sure. Hope this was somewhat helpful
Click to expand...
Click to collapse
Magisk is indeed a solution. It's been updated to (currently) hide root successfully from Safety Net. Although Google may update it again, and break the hide function. So the cat and mouse game goes on. But so far topjohnwu is aggressively keeping Magisk updated to bypass Safety Net.
Apps may use other methods to detect root besides Safety Net. But Safety Net is probably the most common method. Magisk works for me, in hiding root from Netflix and banking apps on my current device (OnePlus 3T).
More recent versions of SuperSU also have a function to hide root (current version is 2.82). I personally haven't tried it. But reports I've read are positive.
Xposed is a no-go, as far as I know. It inherently breaks SafetyNet. So whatever means the Xposed module used before to hide root, won't work now. Again, AFAIK (haven't personally tried, and not really an xposed user).
Also note that some custom ROMs may also trip Safety Net. And if so, there is nothing the Magisk Hide and SuperSU hide function can do about that. But I think this does not apply to Lineage (hide still works).
Hi,
ive got a question. How effective is the miui permission managment in a side by side comparison with xprivacy? I read in the android 7 and 8 documentation that for exampel if you ask for any permissions while running your code on the device they become automatic granted from the android syntax. Im not sure if it was also in oreo but for sure in 7. I also read from ways to bypass not granted permissions from the user with the IPC. So you can read every kind of data also open network sockets for communications with your on servers for sendig the users privat data. Im using miui 8 on mi mi5s with xprivacy and i registrate all kind of trying to bypass the permissions from several apps on my device. Allthough xprivacy working fine but for me the only way i can see to protect my private data is using xprivacy. Can someone tell me more about how effective miui works at this point and which permissions are necesarry for apps to run?( not the obvious necesarry permissions like for a music app to get permissions for using a external drive)
Thanks
[Back 2 Basics]
Simple privacy oriented rom based on stock, just like in old days.
[The way you like it]
Keep it simple or modify
Your Phone
Your Rom
[Simplicity]
So simple, your grandparents could use it
[Security]
Privacy is our right
Stop feeding corporations with your data
[Speed]
Do you need to buy visually faster phone every year, so the manufactures would produce more electronic waste?
Use your phone at full potential instead!
XDA:DevDB Information
[TomaHawk]Back2Basics, ROM for the Sony Xperia XZ Premium
Contributors
Doom Slayer
ROM OS Version: 9.x Pie
Based On: Sony Stock
Version Information
Status: Testing
Current Beta Version: 0.2
Beta Release Date: 2020-07-28
Created 2020-07-28
Last Updated 2020-07-28
How To
[Installation]
Assuming you unlocked your bootloader and have TWRP
IF WIPED SYSTEM/USING AOSP/WANT TO ENABLE SECOND SIM ON G8141
Flash This with a newflasher
CONTINUE:
P.S. Keep a TWRP backup of stock rom on your phone, so you won't need to use newflasher again.
Install this on top of the stock/stock based rom (like Tomahawk Project)
Don't forget factory reset!
Links:
AFH
GDRIVE
CONTINUE:
[Freedom of choice]
FOR MAXIMUM SECURITY:
Keep it simple, without ROOT
Install F-Droid and explore open source world. Download APK and send it to your device. I removed browser, pick your own
At your own risk:
If you want download apps from playstore anonymously, try Aurora Store
Want to get accurate Network location and some of the Google apps working properly, then install this Magisk Module
To get Network Location working, signature spoofing is needed. You'll need this or this edXposed module
If you think my work was for nothing:
Install Gapps and never visit this thread again
Changelog
0.1
Initial release
0.2
Fixed broken GSM + Data
Privacy made Easier
Let's find a balance between security and ability to use apps which we have to.
Most of us have people who use messengers we don't trust, but we still need to communicate with those people.
Another CONCERN is a fact that most of the apps rely on google for push notifications. Google get all the content, no matter how secure your messenger is.
If you don't have Google Services, then you have problems with notifications. Here MicroG will help us.
So, let's make a secure environment for apps we use, but don't trust.
You gonna need:
This rom installed
Magisk + "microG installer Revived"
Shelter
Let's do it!
Open Shelter app and let it create work profile.
Then you need to make sure install some apps in there:
If you install Aurora Store inside Shelter it will allow to easily manage apps from Play Store.
You can clone magisk to shelter( enable multi user in the main app first, then clone) and install firewall inside the shelter.
Update:
Another way is to install vpn inside shelter and enable kill switch. So apps inside shelter only won't have internet access unless you enable VPN.
I use protonvpn, it give 3 countries for free and it's more than enough for average user.
Beware that when VPN is outside of the shelter, on the mainland, apps on shelter will bypass it, so you need to have clients on both. You may have 2 different VPN clients enabled if you need to.
What do we get?
See "Contacts" and "Files"?
Those are seperate from the mainland, so you can just add your relatives' phone numbers and WhatsApp will only see those.
We are LIMITING ACCESS TO FILES AND CONTACTS.
Plus we can easily freeze those apps, or limit connectivity with a firewall, or vpn.
Result:
You can use apps, that brings vulnerabilities or privacy concerns in a locked,controlled environment.
Still receive notifications without sending them to Google.
Or you can try VMOS, at your own risk of course
Short message for each of you.
This rom is a result of a project which aim to strip android back to it's core, so WE CAN BUILD IT THE WAY WE WANT IT. Not the way market researchers say we want it.
In short, this ROM is a prototype of community communication device.
Everyone can join the digital freedom project. I am sure each of us can help a cause.
Is ther any way to get real all the 4k working all time
mahmoodsaud said:
Is ther any way to get real all the 4k working all time
Click to expand...
Click to collapse
Not real,but VM
If you set "apply on boot", you will notice that boot animation will become smaller ,but it's the same trickery as adb commands.
g8141 does not work, reboots right after sony logo no bootanimation.
p.s. flashed over .107 stock rom with twrp 3.2.3-0
edit: installation guide is a bit vague, do we MUST flash this? https://androidfilehost.com/?fid=4349826312261694774
It says
IF WIPED SYSTEM/USING AOSP/WANT TO ENABLE SECOND SIM ON G8141
but I didn't wiped system nor using aosp nor want to enable second sim
second edit: Needs few reboots before booting to system, seems to work like intended.
Some suggestions:
Please find a solution to Automatic reboot when sim tray is removed, since I don't use dual sim and switch SD cards frequently it gets frustrating so fast. Thanks in advance.
Qualcomm Device Security still persists on this rom, it has an apk under vendor\app\QualcommTelemetry(?)
Video Enhancement is not working, at least on settings preview.
VERY USEFUL: Show charging current on lock screen, existenz rom had it.
Dark/Full Black System theme
Boot time is unacceptable, it takes around 2 minutes for normal boot, whereas even in a bloated stock it took around 30~ seconds. It is due to your framework changes and deodexing. However, I've been able to restore optimal boot time by changing all frameworks.
@undefine,
Yeah, boot time is longer because because of deodexing. Frameworks are untouched though in this rom.
If you want Video Enhancements, then you need to go back to android 8 and istall drm patch.... Since they fixed the camera on Pie nobody really bothers with other drm related things...
Agree on the dual sim reboot thing, it's annoying, but I have no idea how to disable it for now. If you really don't need to dual sim functionality then you can try flashing this rom on top of G8141 version and make sure you got kernel as well.
Theme is overlay, adding functionality to the lock-screen require modifying services.jar to disable signature (super user mod), both are security risks... You may flash existenz on top and remove what you don't need. At your own risk of course
Doom Slayer said:
@undefine,
Yeah, boot time is longer because because of deodexing. Frameworks are untouched though in this rom.
If you want Video Enhancements, then you need to go back to android 8 and istall drm patch.... Since they fixed the camera on Pie nobody really bothers with other drm related things...
Agree on the dual sim reboot thing, it's annoying, but I have no idea how to disable it for now. If you really don't need to dual sim functionality then you can try flashing this rom on top of G8141 version and make sure you got kernel as well.
Theme is overlay, adding functionality to the lock-screen require modifying services.jar to disable signature (super user mod), both are security risks... You may flash existenz on top and remove what you don't need. At your own risk of course
Click to expand...
Click to collapse
I think boot time is not because frameworks are changed but some are missing, I just reflashed with everything in stock framework folder, it seems to be blazing fast as normal. I'm actually surprised it booted that fast even with Deodex.
As far as I remember Video Enhancements worked on stock 9 at least on my device, I have my drm keys though since I waited for a proper ta backup. However it is not a must feature either.
I'd rather flash opengapps full package than flashing existenz over this rom . I will look into some other tricks for showing charge current, maybe some xposed module exists?
Anyway, thanks for your contribution to this device. Cleanest stock rom I've ever used (besides one bloat called Qualcomm Device Security which I immediately removed).
Hello everyone,
Recently I have been experimenting with custom ROMs on my Samsung phone and was very unpleasantly surprised to find that Samsung does not allow my Galaxy Watch to be used with modded Samsung phone... Yeah, I know there's the option to replace manufacturer and brand in build.prop, however I don't like the idea of unnecessarily modifying the system just for a couple of proprietary apps, so instead I took the approach of patching the apps to make them work with the phone again.
All that needed to be done was patch manufacturer and brand to static string(s). Here's a command to do just that:
Bash:
find . -type f -name "*.smali" -exec sed -i 's/sget-object \(v\|p\)\(.\+\), Landroid\/os\/Build;->\(MANUFACTURER\|BRAND\):Ljava\/lang\/String;/const-string \1\2, \"letitbeheardthisphoneistobetreatedasifitwereofabranddifferentfromtheonestartingwiths\"/g' "{}" \;
Patching the apps, however made the shealth app refuse communication with the wearable app due to mismatching signing certificates and it needed to be patched too. It is possible to either completely bypass signature checking or insert custom certificate - I have attached a patch that does just that.
You can (and probably should) do this yourself if you want to use the modified applications. Just decompile apks with apktool, apply the command in the directory with the apps content (it is necessary for Galaxy Wearable, Samsung Accessory and Galaxy Watch Plugin apps), and insert you own custom certificate into Galaxy Watch Plugin (attached patch - just replace the cert with your custom one). If you use Samsung Health, just replace the certificate string with hex-encoded certificate you used to sign the apps in the attached patch and apply it to the app. Then rebuild the apps and sign using the key whose certificate you just inserted into the apps.
Although you should never trust a random stranger on the internet with apps you install, I understand not everyone wants to go through this process themselves, so hereby I solemnly promise there is no malicious code inserted into the provided apks. And here's the link
App Versions:
Samsung Accessory (com.samsung.accessory): 3.1.94.11128
Galaxy Wearable (com.samsung.android.app.watchmanager): 2.2.42.21083061
Galaxy Watch PlugIn (com.samsung.android.geargplugin): 2.2.05.21042051
Samsung Health (com.sec.android.app.shealth): 6.18.7.005
No idea what you're talking about. My watch works fine with my note 10+ using Dr ketan rom.
Same with Alexis. I just hide it with magisk but it was working just fine before that.
dchd310870 said:
No idea what you're talking about. My watch works fine with my note 10+ using Dr ketan rom.
Click to expand...
Click to collapse
Leon said:
Same with Alexis. I just hide it with magisk but it was working just fine before that.
Click to expand...
Click to collapse
I was talking about AOSP-based ROMs. Generally, I build and sign the ROM whenever possible and so I don't find it necessary to root my devices. Also I don't like the idea of making changes to mask the actual device and when the app is used with Samsung phone, it relies on proprietary interfaces implemented only in Touchwiz, which are not available in AOSP. Since it is an app issue, it makes sense to make changes on the app level instead of the system level.
dansimko said:
I was talking about AOSP-based ROMs. Generally, I build and sign the ROM whenever possible and so I don't find it necessary to root my devices. Also I don't like the idea of making changes to mask the actual device and when the app is used with Samsung phone, it relies on proprietary interfaces implemented only in Touchwiz, which are not available in AOSP. Since it is an app issue, it makes sense to make changes on the app level instead of the system level.
Click to expand...
Click to collapse
Hi,
I 've got the same problem with the rom Beyond V2.0.
Can you explain more precisely what i must do with yours files ? I'm a novice and my english not very good.
Thank a lot
Hello,
I'm using a unrooted (root not available yet) but knox tripped Samsung Galaxy S21 Ultra. Because of no root i'm not be able to edit build.prop to change the tima line. Now I'm searching a way to get Samsung shealth 6.15.1.003 get working with data sync. To be honost i dont really understand how to patch this way. Could somehone explain me what to do? Samsung health is already decompiled with APK Easy Tool. Thanks in Advance
Hallo sir can you update the files or explain a bit further how to do it by ourselves
Could you be more specific. I want to try it but I dont understand how to doit. some one knows how to patch these apks. ? you tube video? thanks.
hi sir, thank you for your hard work. looks good and might be what i wanted. just rooted my phone and i cant seem to pair my gear sport with my rooted S20+.
Do i just install the apk like normal, running it in file manager? or do i need to flash it in through custom recovery?
fwiw i use an Active 2 with a rooted Pixel 2 XL, and dont need any of that and have ECG/BP and Samsung Pay working. Only modified thing is the Samsung Health monitor app on the phone, modded to not detect root or require a Samsung Phone, thats it....
I own a s5neo with lineage 17.1 and I had the same problem as reported, galaxy wearable identified my phone as modified/rooted and exited. Using your apk I was able to launch the app but it fails to install the galaxy buds live plugin, only shows a message that failed to install.
I don't know how to do the patch and I would like to know if you can generate a patched apk for buds live plugin (https://play.google.com/store/apps/details?id=com.samsung.accessory.neobeanmgr&hl=en_GB)
thanks in advance
Can I use it for Spay?
nevermindrs said:
I own a s5neo with lineage 17.1 and I had the same problem as reported, galaxy wearable identified my phone as modified/rooted and exited. Using your apk I was able to launch the app but it fails to install the galaxy buds live plugin, only shows a message that failed to install.
I don't know how to do the patch and I would like to know if you can generate a patched apk for buds live plugin (https://play.google.com/store/apps/details?id=com.samsung.accessory.neobeanmgr&hl=en_GB)
thanks in advance
Click to expand...
Click to collapse
I have Galaxy Buds+ on a Pixel 2 XL
Heres how to do it the easy way...
Install Magisk
Enable MagiskHide in Magisk Manager settings
Tick all Samsung related apps in MagiskHide in Magisk Manager
Hide Magisk Manager
Reboot
Thats how i also have my Active 2 and Samsung Pay working
^yep, magisk is magic!
dansimko said:
I was talking about AOSP-based ROMs. Generally, I build and sign the ROM whenever possible and so I don't find it necessary to root my devices. Also I don't like the idea of making changes to mask the actual device and when the app is used with Samsung phone, it relies on proprietary interfaces implemented only in Touchwiz, which are not available in AOSP. Since it is an app issue, it makes sense to make changes on the app level instead of the system level.
Click to expand...
Click to collapse
Hi,
I am unable to install any of the apk. App not installed.
Please help me.
dansimko said:
Hello everyone,
Recently I have been experimenting with custom ROMs on my Samsung phone and was very unpleasantly surprised to find that Samsung does not allow my Galaxy Watch to be used with modded Samsung phone... Yeah, I know there's the option to replace manufacturer and brand in build.prop, however I don't like the idea of unnecessarily modifying the system just for a couple of proprietary apps, so instead I took the approach of patching the apps to make them work with the phone again.
All that needed to be done was patch manufacturer and brand to static string(s). Here's a command to do just that:
Bash:
find . -type f -name "*.smali" -exec sed -i 's/sget-object \(v\|p\)\(.\+\), Landroid\/os\/Build;->\(MANUFACTURER\|BRAND\):Ljava\/lang\/String;/const-string \1\2, \"letitbeheardthisphoneistobetreatedasifitwereofabranddifferentfromtheonestartingwiths\"/g' "{}" \;
Patching the apps, however made the shealth app refuse communication with the wearable app due to mismatching signing certificates and it needed to be patched too. It is possible to either completely bypass signature checking or insert custom certificate - I have attached a patch that does just that.
You can (and probably should) do this yourself if you want to use the modified applications. Just decompile apks with apktool, apply the command in the directory with the apps content (it is necessary for Galaxy Wearable, Samsung Accessory and Galaxy Watch Plugin apps), and insert you own custom certificate into Galaxy Watch Plugin (attached patch - just replace the cert with your custom one). If you use Samsung Health, just replace the certificate string with hex-encoded certificate you used to sign the apps in the attached patch and apply it to the app. Then rebuild the apps and sign using the key whose certificate you just inserted into the apps.
Although you should never trust a random stranger on the internet with apps you install, I understand not everyone wants to go through this process themselves, so hereby I solemnly promise there is no malicious code inserted into the provided apks. And here's the link
App Versions:
Samsung Accessory (com.samsung.accessory): 3.1.94.11128
Galaxy Wearable (com.samsung.android.app.watchmanager): 2.2.36.20113061
Galaxy Watch PlugIn (com.samsung.android.geargplugin): 2.2.05.20110441N
Samsung Health (com.sec.android.app.shealth): 6.12.3.001
Click to expand...
Click to collapse
how to generate hash from keystore. can anyone help? @dansimko
mohsin1122 said:
how to generate hash from keystore. can anyone help? @dansimko
Click to expand...
Click to collapse
Generate Hex from keystore
keytool -alias mykey -exportcert -keystore my-release-key.keystore -storepass 123456 | xxd -p
To anyone coming across this post who wants to do this themselves, I've made a little guide and some tools here: https://github.com/adil192/SamsungAppsPatcher.
I've also attached the apks I've patched if you don't want to do it yourself (since the ones in OP didn't work for me) here: https://mega.nz/folder/sUFj2C5b#M4zEP-c9ylY-ENxPw7qCUQ. Like OP, I promise I haven't added malware in this.
Edit: I've somewhat automated the process now so if anyone wants me to patch another plugin, just @ me and I'll get it added as soon as possible.
Adil192 said:
To anyone coming across this post who wants to do this themselves, I've made a little guide here: https://gist.github.com/adil192/ab95808fb66b6cde3d63ded6c19b0f1d. I've also attached the latest apps I've patched if you don't want to do that (since the ones in OP didn't work for me) here: https://mega.nz/folder/sUFj2C5b#M4zEP-c9ylY-ENxPw7qCUQ. This is tied to my name so I have no reason to add malicious code.
Click to expand...
Click to collapse
I need assistance with the gear s3plugin apk please.
Got it working..thanks
Would this process work to enable the Galaxy Wearable App to connect if using non-uk galaxy buds live? My app sets up the buds live but then fails to connect, even though Bluetooth connects and buds function.
Samsung have advised I have a Vietnamese version of the buds live which are not compatible with the Galaxy Wearable App in the UK.