J320A with custom ROM and android pay? - Samsung Galaxy J3 (2016) Questions & Answers

I am running the pixel experience ROM since the beginning when it was literally the only option out there but maybe it is time to switch roms? I saw someone mentioning something about this phone can finally do twrp now?
I am just trying to bypass whatever checks Google is doing for android pay. Get error saying they detected custom rom. Maybe there is a way to use android emulator on desktop or something? Once my android pay account is set up I should be able to add it as payment option for this app that doesn't like my CC then there is no reason to run Android pay app any more I hope?
I found this https://amp.reddit.com/r/oneplus/comments/5u2t4e/you_can_use_android_pay_with_root_and_a_custom/ but it assumes I have twrp which I don't.. Required?

Related

AT&T Now Bricks Modded Galaxy Tabs

What used to be a simple patch to permit AT&T Galaxy Tabs to download apps from sites other than the Google Market is no more. We recently got our Tab back from the Samsung repair facility and it was wiped clean and loaded with a new Android version that now puts your Tab in an endless boot loop if you attempt to patch the config setup to permit downloads from outside Google Market.
Simple solution: DON'T BUY AT&T-BRANDED GALAXY TABS.
If there were some sort of unlimited data plan, this kind of behavior might be warranted but since AT&T charges by the amount of data you consume, there's really no excuse for crippling these devices... other than just being assholes!
Not entirely sure what you're referring to here. I have an AT&T SGT and it works just fine with sideloaded apps.
Did you run SuperOneClick root and then enable non-market apps?
Either way, nuke that horrid stock ROM with one of the Euro roms and you'll never have to worry about AT&T's crippled version again.
Yeah, but...
There still are a number of ways to root the phone, but the new checksummed firmware will make it extremely difficult to load custom roms with any hope of restoring an earlier firmware version. And, once you update your current version of Android, using the standard method of allowing non-market apps by changing the non-market apps entry in /dbdata/databases/com.android.providers.settings/settings.db will put the device into an endless boot loop when you restart it.
So, while it used to be simple, those days are over. No need to shoot the messenger.
What version of firmware did your Tab come back with?
What method did you attempt to enable side loading?
I find this very hard to believe because every single ATT Android device to date has been able to side load after a simple 1 bit edit of the device settings db.
I believe that you had problems with the SuperOneClick app but there is a much cleaner / safer way to do it.
Sent from my SGH-I987 using Tapatalk
NerdUno said:
There still are a number of ways to root the phone, but the new checksummed firmware will make it extremely difficult to load custom roms with any hope of restoring an earlier firmware version. And, once you update your current version of Android, using the standard method of allowing non-market apps by changing the non-market apps entry in /dbdata/databases/com.android.providers.settings/settings.db will put the device into an endless boot loop when you restart it.
So, while it used to be simple, those days are over. No need to shoot the messenger.
Click to expand...
Click to collapse
I don't believe my ATT SGT came with a protected bootloader, and if I'm not mistaken, AT&T hasn't released any firmware updates via KIES or OTA. So while there's always the possibility of Samsung "screwing" us all with that mess, it's only been seen on the leaked firmwares. Not that I don't put it past the big blue DeathStar to opt to use something like that to prevent people from avoiding their preloaded garbage....
I'm happy I liberated my device from the clutches of the Evil Empire, and will gladly look to XDA for my future upgrade paths.
Could just be a bad software flash from factory. A number of t-mobile vibrants couldn't get to restore via volume up/down power because of a buggy flash file they put on a certain build date
Sent from my Galaxy Tab

[Q] Beating MobileIron on a Rooted S4 [MDL]

First my phone's details:
Rooted
Model: Samsung-SGH-I337 (AT&T)
Android Version: 4.2.2
Build: JDQ39.I337UCUAAMDL
Here's the situation...
I'm an IT guy (low on totem) and we're in the Pilot phase for Android using MobileIron. I have a rooted AT&T 32GB S4 and I'm trying to fool MobileIron into believing my phone is compliant. I have done lots of reading on this subject, and nothing has helped, to this point. I have access to the MobileIron server, so I can register, and de-register, my device as often as I want. I plan on reporting this back to the people who get paid more than I do to let them know how secure this is.
Here's what I've tried:
1. I have installed Xposed Framework, and installed RootCloak, but it has zero effect on MobileIron. I couldn't even get to the point in MobileIron setup where I could download our 'secure apps'. (I am aware that RootCloak moved to Cydia, but I read it wasn't as good)
2. I tried using 'Hide My Root' from Play, and that also had zero effect on MobileIron; I got no further than I did with RootCloak.
3. I tried using 'Hide Rooting Lite' from Play, and I was able to download our 'secure apps', and MI required that I create a password/pattern to unlock my phone. In my opinion, this got past the first level of authentication that MI requires, which is a step in the right direction. I have recently learned that MI also scans your list of installed APPs for any APP that requires root.
Do any of you think that changing the names of some of my apps (Titanium Backup, Root Explorer, etc.) would help fool MobileIron? What about trying to DualBoot ROMS? If the secondary ROM that I setup is not rooted, and I have MI installed on it, would it be able to detect root from my primary ROM?
Any help, or ideas that I have not thought of yet, that you geniuses can provide would be greatly appreciated!!
GatorRuss said:
First my phone's details:
Rooted
Model: Samsung-SGH-I337 (AT&T)
Android Version: 4.2.2
Build: JDQ39.I337UCUAAMDL
Here's the situation...
I'm an IT guy (low on totem) and we're in the Pilot phase for Android using MobileIron. I have a rooted AT&T 32GB S4 and I'm trying to fool MobileIron into believing my phone is compliant. I have done lots of reading on this subject, and nothing has helped, to this point. I have access to the MobileIron server, so I can register, and de-register, my device as often as I want. I plan on reporting this back to the people who get paid more than I do to let them know how secure this is.
Here's what I've tried:
1. I have installed Xposed Framework, and installed RootCloak, but it has zero effect on MobileIron. I couldn't even get to the point in MobileIron setup where I could download our 'secure apps'. (I am aware that RootCloak moved to Cydia, but I read it wasn't as good)
2. I tried using 'Hide My Root' from Play, and that also had zero effect on MobileIron; I got no further than I did with RootCloak.
3. I tried using 'Hide Rooting Lite' from Play, and I was able to download our 'secure apps', and MI required that I create a password/pattern to unlock my phone. In my opinion, this got past the first level of authentication that MI requires, which is a step in the right direction. I have recently learned that MI also scans your list of installed APPs for any APP that requires root.
Do any of you think that changing the names of some of my apps (Titanium Backup, Root Explorer, etc.) would help fool MobileIron? What about trying to DualBoot ROMS? If the secondary ROM that I setup is not rooted, and I have MI installed on it, would it be able to detect root from my primary ROM?
Any help, or ideas that I have not thought of yet, that you geniuses can provide would be greatly appreciated!!
Click to expand...
Click to collapse
Hi! Any luck with beating mobile iron?
MobileIron is kicking my ass. I have a Nexus 5 that's never been rooted and I can't get MI to install on this device. Is it because the bootloader is unlocked? I'm in IT as well, and our MobileIron administrators have NO IDEA what to do.
Broadscope said:
MobileIron is kicking my ass. I have a Nexus 5 that's never been rooted and I can't get MI to install on this device. Is it because the bootloader is unlocked? I'm in IT as well, and our MobileIron administrators have NO IDEA what to do.
Click to expand...
Click to collapse
I had a similar issue in my non-rooted M8. MI started working after I did a factory reset .

can you root your phone but still pass the device policy check for gaps for work?

Hi all,
I use my personal phone (specifically a phone that I own) for both home use and work use and I am considering rooting my phone so I can make some changes to the system UI file. I know that one of the checks that the "Device Policy" app checks for is to see if the phone is rooted so I was wondering if anyone has rooted their phone and successfully been able to pass the device policy check? Specifically I am looking to find out if:
1. would something like root cloak work?
2. if root cloak will not work, has anyone rooted the phone, made the changes, and then disable root leaving the phone running un-rooted so that the device policy check still succeeds? (I ask as I do not need permanent root, just access to fix some of the annoyances that come with stock android).
Thanks,
dave

Samsung Pay on Rooted (0x1 Status) Phone

OK guys, sorry I know this has been brought up a bit, but I've been determined to find a solution. I've been trying to get Samsung Pay to work. More specifically because I use it a lot and have a Gear S3 that I want it to work with.
Yes I did research before I rooted, and it appeared there were many solutions to this problem, but I've tried them all and none have worked. I just want to see if anyone at all has got this working. Maybe I can update with different things everyones tried as we go. I feel like there HAS to be a way to make this work. If anyone has gotten this to work in any way, please post!
My Phone: SM-G950F
Knox Status: 0x1 (Faked 0x0 by Magisk)
ROM: Renovate Ice 5.1
CSC Version: SPE (Spain)
From my research, the SPE seems to be open to Samsung pay along with some others. I have encountered different error messages with different combinations of software, hiding Samsung Pay in Magisk, etc. It might just be due to newer and older version of Samsung Pay
Things I've tried:
Fake 0x0 with Magisk, v13.6, 13.7, 14.0
Hide root status with Magisk
1.3.7 Samsung Pay Gear Plug-In (I found somewhere that said this version works, although it just keeps updating for me)
Moved /system/xbin/busybox to SD card
Error message I'm receiving on latest software: Access Denied: Samsung Pay has been locked due to an unauthorized modification. Tap the link below to call customer service and unlock Samsung Pay (RD-SXA).
Note, I have not tried calling customer service yet, that will likely be my next step. I will just tell them I bought the phone on eBay and I'm getting this message. I doubt there is anything they can do, but it's worth a try.
Please don't grill me, I know basically everyone claims this is NOT possible with 0x1 due to hardware fuse, etc. I know this community is strong and I've seen people pull off the impossible before, just hoping to get this to work so my S3 Gear doesn't become a paper weight.
The actual functionalities of Samsung Pay (MST for example) are handled by trusted apps running in secure world. Root in normal world does not affect anything there. Saying that we can fool normal world apps, we still can't fool the TA running in secure world. So even though Samsung Pay app can launch, it won't be able to function in the end.
OK, I have an update. I was able to get Samsung Pay (mobile version) to work! The regular version still gives me an error, but if I launch from my watch, it pulls the mobile version instead.
Here's what I did:
**NOTE: This only works if you have a Gear S3, I have not been able to get the full version of Samsung Pay to work on the phone yet.
1. Boot into recovery
2. Wipe all partitions except the SD Card and OTG
3. Installed Renovate Ice 5.1
4. Select Custom CSC during install and chose "214 Spain"
5. At the end of setup, don't reboot, flash magisk again manually (It's installed in the ROM, however this is the only way I found to get the icon to show up)
6. Open Magisk Manager
7. Click Menu and go to "Magisk Hide"
8. Search for "Pay" and check all apps that show up
9. Update all apps and connect S3 as a new device (you can restore apps/settings)
10. Use root explorer to /system/xbin and move busybox to your SD card (Make sure it doesn't exist on internal storage, if it's present, app will fail)
11. Launch Magisk Manager again and search for "Pay", again make sure all are checked, for me there was another new Gear version that I had to check to hide
12. Reboot the phone
13. Hold down top button on S3 to launch Samsung Pay
14. Proceed through wizard and add a card or "Launch" Samsung Pay on the phone from the S3
15. The Samsung Mobile app should open correctly on the phone and let you add cards etc.
If you try to add busybox back and reboot, it will not work. And again, the actual "Samsung Pay" app on the phone does NOT work, I still get an error. Maybe it's not possible.
schwags said:
OK, I have an update. I was able to get Samsung Pay (mobile version) to work! The regular version still gives me an error, but if I launch from my watch, it pulls the mobile version instead.
...
If you try to add busybox back and reboot, it will not work. And again, the actual "Samsung Pay" app on the phone does NOT work, I still get an error. Maybe it's not possible.
Click to expand...
Click to collapse
Nice findings! So Gear S3 has stand alone pay capability even with non-Samsung devices?
idler1984 said:
Nice findings! So Gear S3 has stand alone pay capability even with non-Samsung devices?
Click to expand...
Click to collapse
I'm not sure about non Samsung devices. All I'm saying is there are 2 versions of Samsung Pay on the S8, one standard version that you would use if you didn't have a Gear S3 and another version that s triggered from the S3 but then runs on phone. That's the one I can get to work.
Sent from my SM-G950F using XDA-Developers Legacy app
Does this method work with renovate 7.2? I have followed the steps and appears denied access
Same problem here, and I live in Spain too!
Does it work with other rom?
I have an sm 930f with 0x1 status, also. since the error message has changed and suggests "call customer service to unlock samsung pay at 0330 726 7729" I just got off the phone with UK customer service.
1. agent didn't know anything about unlocking samsung pay
2. since I reside in the U..S he suggested I had to call U.S customer service which I have already done and they know nothing about unlocking samsung pay. Perhaps there's a change in the works but not yet.
I wonder what happens if the flash counter hits 0x9. One more flash and it hits 0x10 or does it go back to 0x0??

help with either downgrading or changing rom to keep call record

Hi i have samsung s8 and have lost call record function and needed it several times.
I have tried loud speaker and changing settings but want to get it working again.
What is the best solution for this as i want to keep my banking apps working aswell so i cant root the phone
I have downloaded the firmware from sammobile for android 8 but before downgrading i have alot of photos and videos i am currently backing up.
I need to know if there are other solutions as i want to get all security patches and keep banking apps working but also keep call record. and android 8 will have vulnerability.
I have heard changing phone rom to another country may keep it updated but need help to which country can i change to that will allow call records.
from what i know - All Android 9 roms require Root.
So you have to downgrade to Android 8 if you dont want to root.
I have Android 9 and all my banking apps work, except for Samsung Pay.
Install Magisk and you can hide root detection for your banking apps. That way you can have Android 9 with Root and enable Call record - but still have your banking apps working.
loni90 said:
from what i know - All Android 9 roms require Root.
So you have to downgrade to Android 8 if you dont want to root.
I have Android 9 and all my banking apps work, except for Samsung Pay.
Install Magisk and you can hide root detection for your banking apps. That way you can have Android 9 with Root and enable Call record - but still have your banking apps working.
Click to expand...
Click to collapse
I tried downgrading but it failed and i tried rooting my phone and successfully got to welcome screen after installing magisk but when i did a reboot it went into bootloop with "Only official released binaries are allowed to be flashed"
I tried twice and get that message and can only install latest android 9.
I was on latest update prior to rooting so not sure if they stop flashing somehow.
I got unlock bootloader but cant flash anything as i get soft bricked.

Categories

Resources