Related
Anyone have any ideas as to how we could get Wallet working? I installed a few different versions and none of them seemed to work. I tried the modded version that was released for the GNEX and got an insecure element error (but not as an fc) and also tried the latest version I have on my GNEX but got another error (sshot) I would be happy to try out other ideas if anyone has any...
(Rooted) Modify the build props to a Sprint GS3?
This disappoints me, Google Wallet was something I was really looking forward to using. There's a Walgreens with NFC payment machines that I usually ride my bike to for quick things like milk, bread, etc. I was looking forward to leaving my wallet at home and just biking with the phone...I hope that we get that functionality sometime soon.
tlogank said:
This disappoints me, Google Wallet was something I was really looking forward to using. There's a Walgreens with NFC payment machines that I usually ride my bike to for quick things like milk, bread, etc. I was looking forward to leaving my wallet at home and just biking with the phone...I hope that we get that functionality sometime soon.
Click to expand...
Click to collapse
It's unlikely. Verizon Wireless has a competing product. They would much rather you use that than Google Wallet. There are a lot of NFC payment apps out there, whether they're Google/Apple side, carrier side, or bank side. They all want to become banks. I doubt Google Wallet will work on this device without some serious trickery.
When is ISIS coming anyway? These carriers are surely being assholes not even giving people a way to use NFC payments while ISIS jerks off. With all of them backing ISIS, I'm surprised it hasn't launched outside their test zone yet.
Google Wallet isn't competing if they don't even have their product commercially available yet.
Hilbe said:
(Rooted) Modify the build props to a Sprint GS3?
Click to expand...
Click to collapse
How do you that? Is it as simple as replacing the model to the Sprint's one?
Check here for all the research I've already done.
HTML:
http://forum.xda-developers.com/showthread.php?p=28432068
Are there any working alternative services to Google Wallet on Verizon at the moment?
I am pretty sure there is nothing else, the fact that verizon is blocking the only option really pi$$es me off, I will NEVER use isis
grhomes said:
Anyone have any ideas as to how we could get Wallet working? I installed a few different versions and none of them seemed to work. I tried the modded version that was released for the GNEX and got an insecure element error (but not as an fc) and also tried the latest version I have on my GNEX but got another error (sshot) I would be happy to try out other ideas if anyone has any...
Click to expand...
Click to collapse
Hate to break it to ya, but if you are getting the secure element error then you have (as of right now) permanently bricked your ability to use wallet and possibly other nfc payment options in the future. Ask me how I know
ISIS is not out yet, right? So there is no payment option for this yet?
Sent from my SCH-I535 using xda premium
cttwarnock said:
Hate to break it to ya, but if you are getting the secure element error then you have (as of right now) permanently bricked your ability to use wallet and possibly other nfc payment options in the future. Ask me how I know
Click to expand...
Click to collapse
I thought somebody just came up with an ADB shell call something along the line of reset broadcast something that could potentially fix the issue of bricked SE's?
Anybody know if anyone is planning on developing a Wallet app to work on Verizon GSIII. Isis is going to be terrible, because it won't work wherever a PayPass terminal is, only at select retailers, but thousands of retailers already use PayPass terminals, so I was hoping for Wallet.
Sent from my SCH-I535 using xda app-developers app
I want this bad. I will stalking this thread for updates
Well that was the first apk I tried, uninstalled and then got the sshot that was posted....I hope thats not the case but seeing as how I got a different error I sincerely doubt it...working on a few evo 4g wallet workarounds atm...
jackdubl said:
ISIS is not out yet, right? So there is no payment option for this yet?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Isis is supposed to hit the SLC area any day now, and some other select areas for testing. Isis is close, and looks like it's going to be awefully similar to Google Wallet. You can link it with supported brands of credit card or use their rechargeable card just like your google wallet account. Way to not innovate. I wonder if Google could pull and Apple and sue...?
http://www.paywithisis.com/get-isis.xhtml
konman2k4 said:
I thought somebody just came up with an ADB shell call something along the line of reset broadcast something that could potentially fix the issue of bricked SE's?
Click to expand...
Click to collapse
Can you link that? I cant find it anywhere. That would be so helpful!
I'm not an expert on how Android does credential storage, but I poked around a bit with this version of 1.1-R67-v12, which is patched to avoid region, device, and carrier restrictions. When pushed to /system/app this version launches fine, but when I attempt to link my account I get this:
I checked out the device logs, and I believe this is because our /etc/nfcee_access.xml does not contain the requisite keys to run Wallet:
Code:
NfcServiceSecurityException: java.lang.SecurityException: /etc/nfcee_access.xml denies NFCEE access to com.google.android.apps.walletnfcrel
07-11 20:29:25.678 E/InitializerTaskManagerImpl(1853): java.util.concurrent.ExecutionException: com.google.android.apps.wallet.secureelement.NfcServiceSecurityException: java.lang.SecurityException: /etc/nfcee_access.xml denies NFCEE access to com.google.android.apps.walletnfcrel
As I understand it, this is something that has to be built into the system at compile-time, but I could be wrong. With the correct keys I believe the app will run fine - but as others have pointed out, most of the development effort is (rightly) going into bootloader circumvention at the moment. I have no doubt we'll get access to Wallet in the near future - probably coinciding with the release of CM9 or some other custom ROM.
Expanded logcat here for the curious.
This isn't going to help you verizon folks, but I just got this working on tmobile (havent tested it, but it is installed, no errors, card added)
I'm betting it'll work on att or any other carrier that has a cm9 build.
First thing i did was a backup, then i wiped and installed cm9
then i used the apk and followed the instructions found here and performed the build.prop tweaks found here
Now I'm good to go :good:
dcmtnbkr said:
This isn't going to help you verizon folks, but I just got this working on tmobile (havent tested it, but it is installed, no errors, card added)
I'm betting it'll work on att or any other carrier that has a cm9 build.
First thing i did was a backup, then i wiped and installed cm9
then i used the apk and followed the instructions found here and performed the build.prop tweaks found here
Now I'm good to go :good:
Click to expand...
Click to collapse
Did you have all 3 lines in the build.prop? I can only see 2 of them. AT&T GS3.
Google Wallet - Everything you need to know before you flash or root!
DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR ANY DAMAGE THAT OCCURS TO YOUR PHONE. THIS IS A COLLECTION OF INFORMATION I FOUND WHILE ROOTING AND FLASHING ROMS. I ONLY ORGANIZED IT HERE TO MAKE IT EASIER FOR PEOPLE TO FIND.
Don't forget to thank people who made the ROMs, Root Methods, etc. They put in a lot of work and take a lot of time helping people. All it takes is a click of a button. One for me too! It's a lot of work trying to keep everything updated. =P
This will and always will be a work in progress. If you feel something should be added, clarified, or corrected feel free to PM me. I'm not perfect and I can't read everything so any and all help is appreciated. (Yes of course I will credit you. Just no plagiarism!)
-----------------------------------------------------------------------------
What is Google Wallet?
http://www.google.com/wallet/what-is-google-wallet.html
The new update has simplified the process greatly. Now all cards can be added and all transactions are saved to the cloud. Very minimal information is saved on the device. There is also a very very very slim chance at breaking your secure element.
What do I need to know before I start rooting or flashing ROMs?
While there is much debate over whether or not to Reset Google Wallet before wiping the device, you should do it just in case. There needs to be more testing done to see if the Secure Element will be broken if you don't.
To Reset Google Wallet do the following:
1) Open Google Wallet
2) Enter your pin
3) Tap your Menu Button
4) Tap Settings
5) Tap "Reset Google Wallet"
You should also write down your Google Prepaid Card User ID as well prior to resetting just incase. This will help Google find your money incase your ID changes. You only have to do this once. So far the USER ID has not changed for me ever. This change happens when you physically change phones. Also make sure you know the balance on the card.
Write down your Google Prepaid Card User ID.
1) Open Google Wallet
2) Enter your pin
3) Tap "Payment cards"
4) Tap "Google Prepaid Card"
5) Wait for your User ID to load and then tap "Show ID" to see your entire ID number. Write this down BEFORE FLASHING OR CLEARING DATA.
Once you do this you are good to go and flash a custom ROM. You can wipe data, cache, dalvik without an issue.
After you have set up your new ROM, download and install the latest Google Wallet in the Play Store.
Once you login, Google Wallet will now automatically pull from the cloud any credit cards on file. All you have to do is set them up by tapping them. Some will automatically setup, others will require you to enter in all the card and billing details.
Google Prepaid Cards you have to tap to add. It should pull all the funds and the same user ID as before. If the funds do not pull up, make sure you have your User ID from above, and call Money Network. Their number is (855) 896-0693.
As I don't have every single credit card type, please post in this thread if you run into any issues. I'll update the OP
-----------------------------------------------------------------------
ROOTED USERS:
If you are rooted but stock and you have never used the Google Wallet application, there are a few things you need to know:
#1 - You will always get an unsupported error at the top of your Google Wallet application. Do not worry. Google Wallet will still work as long as you didn't break your secure element. If you can add a Google Prepaid Card and add funds, then you can use it.
#2 - If you try to call in for support, Citi Mastercard will not help you since you are rooted. Google Wallet and Money Network will give you very limited support if you are rooted.
#3- Some users are finding success restoring their backups of Google Wallet to fix broken secure elements. I will need more confirmation but if it is broken, what do you have to lose.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Common Questions + Issues
How to get it up and running on actual unsupported devices:
You will have to edit your build.prop to make Google Wallet think your phone is one of the ones supported.
Here are instructions. This is not for everyone. Sprint users won't have to do all this.
http://forum.xda-developers.com/showthread.php?t=1769083
How do I use Google Wallet to purchase items?
1) You do not need to have the app open but the phone must be turned on. (There are some ROMs that turn NFC on without the screen being on, but you will still need to put in your PIN so just turn the screen on)
2) Let the cashier know you are paying credit or press credit on the credit card terminal.
3) Place the BACK of the phone on the sensor of the card terminal. You can put it on the terminal or place it near but it has to be within an inch or two.
4) Remove the device and enter your pin.
5) Follow directions on the screen till your transaction is complete.
6) When in doubt, ask the cashier if it went through. Most will be amazed and think its cool and spend time with you to get it to work. lol
I think my secure element is broke. How do I tell? How do I fix it?
Check out this explanation w/screenshots. Great work Hobadee!
http://forum.xda-developers.com/showpost.php?p=35156196&postcount=93
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope this helped you. If it has, please click thanks!
Thanks to Racer of All and Rev3ge07 for their contributions on the Secure Element. Thanks to ogdobber for the build.prop tutorial. Thanks to Hobadee for the secure element soft brick fix explanation.
[/strike]
Cool write-up.
and can you clarify in the OP, that if someone HASN'T used google wallet, or "enabled" any cards on a phone, they don't have to mess with any of this, right? can they flash a new rom normally?
okay... and another hypothetical situation: what if someone originally HAD google wallet, did everything as stated in the OP, but after they flashed a new rom, they didn't bother with google wallet, so the app was never installed. does that person have to do anything before installing a FUTURE rom? or what?
Lieu10ant said:
Cool write-up.
and can you clarify in the OP, that if someone HASN'T used google wallet, or "enabled" any cards on a phone, they don't have to mess with any of this, right? can they flash a new rom normally?
okay... and another hypothetical situation: what if someone originally HAD google wallet, did everything as stated in the OP, but after they flashed a new rom, they didn't bother with google wallet, so the app was never installed. does that person have to do anything before installing a FUTURE rom? or what?
Click to expand...
Click to collapse
I'll update the OP for that once I get to work.
Sent from my SPH-L710 using Tapatalk 2
the first post makes it sound like this only applies to citibank master cards, but I'm assuming this affects all credit cards you load into google wallet?
First, if someone (ie me) only has the free $10 dollars from google wallet, then you only need to do the part for the google prepaid card?
And, do you know if anything needs to be done about any of the gift cards that you can add in. I have not done any yet but I do plan to at some point.
Thanks and great job. The instructions are pretty straightforward which is always important when you're dealing with money related things.
sweetness. works perfect on my verizon s3. just added my google card about 15 minutes ago, 10 bucks showed up and just tried it at 7-11. worked perfect. thanks a million OP
wow thanx
wow thanx for the tutorial
inline6power said:
sweetness. works perfect on my verizon s3. just added my google card about 15 minutes ago, 10 bucks showed up and just tried it at 7-11. worked perfect. thanks a million OP
Click to expand...
Click to collapse
I still get the "unsupported device" error on my Verizon S3. Can you tell me which Wallet app you are using? Is it the one from the Play store or a modded one? I'm on the stock rooted rom btw.
Thanks.
skiddingus said:
I still get the "unsupported device" error on my Verizon S3. Can you tell me which Wallet app you are using? Is it the one from the Play store or a modded one? I'm on the stock rooted rom btw.
Thanks.
Click to expand...
Click to collapse
Go Here
http://forum.xda-developers.com/showthread.php?t=1769083
inline6power said:
sweetness. works perfect on my verizon s3. just added my google card about 15 minutes ago, 10 bucks showed up and just tried it at 7-11. worked perfect. thanks a million OP
Click to expand...
Click to collapse
How did you get wallet to work on verizon galaxy s3 at the store? I got it setup but it won't work in store when I try to use it.
Sent from my SCH-I535 using Tapatalk 2
I get the unsupported device message on my sprint gs3 and I didn't open or do anything to google wallet before flashing blazers rom
Did I void Google Wallet on my phone indefinitely if it added my Gmail account, but I never added a prepaid card yet. Then flashed a new from...??? I set up a pin but never added a card...
Sent from my htc_SIII using xda premium
antispiral said:
How did you get wallet to work on verizon galaxy s3 at the store? I got it setup but it won't work in store when I try to use it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Have no clue I just follow ed the op instructions and our worked for me
sent from my galaxy s3
Can you wallet uninstall using rom toolbox / titantium backup before flashing rom and after flashing new rom re-install using rom toolbox/titantium backup
So no one has found out what files on the rom need to be backed up to keep google wallet from breaking? That seems like a lot to go through everytime the rom gets upgraded.
Thank you to share!
Thank you to share!：好：
many thanks:good:
Great guide! Thank you so much!
Thank you:thumbup:
Gesendet von meinem GT-N7000 mit Tapatalk 2
Thanks
sekigah84 said:
I'll update the OP for that once I get to work.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much:good:
{
"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"
}
Thought I'd spread the word. All credit goes to Paul on this! Amazing work!
Google Wallet is super cool. It allows purchasing of things using the NFC chip in your device at Mastercard PayPass terminals, using either an inbuilt pre-paid card (which is loaded up with $10 free credit initially) or a CitiBank Citi Mastercard. But, there is a problem - and that's that Wallet is only available for a very limited subset of devices on a limited number of operators in the US.
Hence the need to patch the APK.
Now, i'll start by saying that there may well be a patched APK out there already (I didn't check), I chose to patch the APK myself because, when i'm putting in my credit card numbers etc. I like to know what i'm working with. I started with the latest version I downloaded personally from the Google Play Store (by spoofing my operator with 'Market Access') which I then patched as required.
The patched APK
The APK has 3 features that I patched out. The first was a device check - the app will now work on any device. Of course you need to have NFC for it to be useful! I tested on a HTC One X successfully (as you can see in the screenshots above) but of course YMMV. The second patch was an operator check - the app should now not care which operator you are on. The third patch was removing the root warning. Google Wallet doesn't actually stop you using the app if you're rooted, it just gives you a warning on screen (which is a little annoying), so I removed it. BUT... rather than having the warning in app, let me post it here instead. If you are using Google Wallet on a rooted device, really think about which apps you are giving root access... because there is the possibility that a malicious app could do bad things. There's no evidence of this happening, but it's possible. As always, be wary of what you're installing and where it came from.
Installation
The APK cannot be installed in the regular way (because it is not re-signed and therefore has broken signatures), instead you should push the apk to /system/app (or copy there using a file explorer and set appropriate permissions) and then you'll be good to go. This means you'll need to be rooted or at least have a custom recovery installed mind. To uninstall, use the 'reset wallet' option in the settings menu then delete the APK.
Important note re: upgrading
If you are using a previous version of Wallet, please ensure you the 'reset wallet' option in the Wallet app settings.
Download
Download the patched APK here - DOWNLOAD (ROMraid) - MD5: 775946c9b164d2dd1edc1a36e59e41a3
Topping Up
So you've installed the APK and spent your initial $10 at Greggs or maybe Mcdonalds. Healthy. Now you need to top up... there's a problem!
Google Wallet only allows you to load the prepaid card using a US card, which most of us accessing Wallet this way don't have! The card that you use needs to support AVS (address verification) with a US address, something that also excludes a number of US cards. I'm hoping that we as a community can collaborate to work out the best way to do this, but i've tried a few methods and i've chronicled them below. I'll update this post as more methods / information surfaces. I'm hoping we can find a low cost disposable Visa solution or similar that makes the process easy. Getting a US address is easy enough to associate with a card, just sign up (free) for US Unlocked.
BFPS - Virtual credit card in various denominations, configurable AVS address, use coupon 'modaco' for 5% discount - WORKING
EntroPay - Virtual credit card, turns out to be Malta registered and doesn't support AVS - FAILED
US Unlocked card - Virtual credit card, currently untested - UNKNOWN
The 1.5 release
The 1.5 release added support for third party Visa / Mastercard / Discover / Amex cards. This is officially US only at the moment and although you CAN get non-US cards appearing correctly, in my experience so far, payments are always declined.
Disclaimer
If you use any of the above modified APKs or top up methods, you do so at your own risk! Please let us know how you get on in the comments below, so we can refine / improve the process based on our experiences.
WARNING
If you plan to wipe your device, switch ROM on your device or otherwise do anything unusual (including 'clearing data' on wallet), it is highly recommended that you use the 'reset wallet' option in the Wallet app settings. Failure to do this could render Wallet inoperable on your device!
Another note of caution, we're using a 'hack' here, so it's probably not the best idea to load up your Prepaid card with a ton of money in case Google blocks hacked wallets, something changes, etc. etc. and you could lose your money. Again, use at your own risk.
And finally...
If you find the above useful and you want to support my work on this and all the other MoDaCo projects, please consider signing up for a premium MoDaCo account. Thanks!
Paul
The link is just text Mike
Sent from my HTC One S using xda premium
doktortaru said:
The link is just text Mike
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Just fixed it bro
Good to see you here!
Says cant install ?? .
Stock rooted rom !
Sent from my SGH-T999 using xda premium
bikrame said:
Says cant install ?? .
Stock rooted rom !
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Read the install directions....
Wait. So I can install this on all my android phones and receive 10$ on each? And could I spend the money like a cc without NFC?
Sent from my SGH-T999 using xda app-developers app
ayeitschris said:
Wait. So I can install this on all my android phones and receive 10$ on each? And could I spend the money like a cc without NFC?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
No you'll need the NFC....it'll check for that.....but anything else it won't check for....
won't connect to account/
Thanks for posting this. Unfortunately, connecting my account is not working for me. The install works fine and I can open the app but then it gets stuck when I try to link my google account. On the "Select an Account" screen I select my account and press "continue" which triggers the "adding account" waiting pop-up but nothing happens. It'll just stay like that until the screen turns off then I'm back to the "Selecting an Account" screen. Tried over cell signal and wifi. Anybody else out there with more luck?
This is the message i get when trying to sign in...
Sent from my SGH-T999 using Tapatalk 2
ayeitschris said:
Wait. So I can install this on all my android phones and receive 10$ on each? And could I spend the money like a cc without NFC?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It's most likely $10 per account not per device so you would probably have to link the app on each phone to a separate account in order to do that.
Sent from my SGH-T999 using xda premium
youngchris29 said:
This is the message i get when trying to sign in...
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I get the same thing. I wonder if it's the NFC configuration that's missing for us.
Sent from my SGS3...
youngchris29 said:
This is the message i get when trying to sign in...
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Sent from my SGH-T999 using xda app-developers app
I get the same error.
youngchris29 said:
This is the message i get when trying to sign in...
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
That sounds like the secure element was messed up due to clearing data or falshing a rom without reseting wallet. I beleive there is a fix floating around for that.
pytyper483 said:
That sounds like the secure element was messed up due to clearing data or falshing a rom without reseting wallet. I beleive there is a fix floating around for that.
Click to expand...
Click to collapse
This is my first time ever trying to use google wallet on my s3. So i never had to reset it or anything
Sent from my SGH-T999 using Tapatalk 2
pytyper483 said:
That sounds like the secure element was messed up due to clearing data or falshing a rom without reseting wallet. I beleive there is a fix floating around for that.
Click to expand...
Click to collapse
Same here, I've never had wallet installed on this phone.
But, this apk did work great on my verizon nexus (which stopped working after it requested an update) lol. thanks!
I just installed Google wallet today from another thread. There were some library file to flash then the .apk. I'll find the thread and link you guys. Maybe it will shed some light.http://forum.xda-developers.com/showthread.php?t=1794733
EDIT: This site has a solution for Touchwiz and AOSP ROMs. Maybe that's the problem? It links to yet another thread for more complete instructions and discussion.
RaymondPJR said:
I just installed Google wallet today from another thread. There were some library file to flash then the .apk. I'll find the thread and link you guys. Maybe it will shed some light.http://forum.xda-developers.com/showthread.php?t=1794733
EDIT: This site has a solution for Touchwiz and AOSP ROMs. Maybe that's the problem? It links to yet another thread for more complete instructions and discussion.
Click to expand...
Click to collapse
When i tried it....it removed the NFC function from the phone....I think it's for ICS based ROMs....I'm running Jelly Bean which may be why it's not working for me....I posted to see if it was me maybe getting the error, but seems we all are....
itsmikeramsay said:
When i tried it....it removed the NFC function from the phone....I think it's for ICS based ROMs....I'm running Jelly Bean which may be why it's not working for me....I posted to see if it was me maybe getting the error, but seems we all are....
Click to expand...
Click to collapse
Yea i think you're right. The same thing happened to me (losing nfc options in settings) when i tried that method. I was also running jb so i think that it only works on ics for now
Sent from my SGH-T999 using Tapatalk 2
I can't get the apk to install using UVDLI8. I changed permissions and put it into /system/app but the install fails.
Sent from my SGH-T999 using xda premium
itsmikeramsay said:
When i tried it....it removed the NFC function from the phone....I think it's for ICS based ROMs....I'm running Jelly Bean which may be why it's not working for me....I posted to see if it was me maybe getting the error, but seems we all are....
Click to expand...
Click to collapse
Oh, sorry then. I'm wondering if anyone can answer this: I tried to give GW it's first test today and it failed. I have NFC enabled in settings and I've set up my account. I have a FlyGrip attached to the rear of my phone, an accessory that allows me to hold this big phone with one hand and reach all areas of the screen with my thumb. I'm wondering if it failed because I cant touch my phone flush with the PayPass reader? For this same reason I cannot do the wireless charging hack the rear of the phone needs to be flush with the charging pad. So, can it be less than an inch away or does it need to touch? Maybe that FlyGrip has got to go.
Okay. I have a brand-spanking-new Galaxy Note 7, exchanged at Verizon for my prior IED version. Good news is that I don't have to worry about my battery self-immolating. The bad news is that I'm getting these "Your request has been declined for security reasons" toast messages when I attempt to carry out various and sundry simple tasks, such as clicking on a legitimate link in an email in my Gmail app or tapping on "About Google Play Store" in the Play Store app. Are there some sort of Gestapo security measures added to the 2nd Gen Note 7 that weren't on the 1st? Is there a way to knock these down a peg? This is insane...to the point where I have to find creative ways around the block to get things done (such as copying the address from the link or button in an email and pasting it in a browser). It makes the phone considerably less user-friendly. What a shame. Any feedback or input here? I'd really appreciate it.
Note: I have seen things online for "FRP" when I search for that very quote, but I don't think this has anything to do with a "reset phone."
Thanks so much!
Never heard of something like this before. Solution? Root that *****, slap twrp on top and flash Ketan Rom M2, and unleash your Note 7 to its full potential instead of that stock crap
discgolfdc said:
Okay. I have a brand-spanking-new Galaxy Note 7, exchanged at Verizon for my prior IED version. Good news is that I don't have to worry about my battery self-immolating. The bad news is that I'm getting these "Your request has been declined for security reasons" toast messages when I attempt to carry out various and sundry simple tasks, such as clicking on a legitimate link in an email in my Gmail app or tapping on "About Google Play Store" in the Play Store app. Are there some sort of Gestapo security measures added to the 2nd Gen Note 7 that weren't on the 1st? Is there a way to knock these down a peg? This is insane...to the point where I have to find creative ways around the block to get things done (such as copying the address from the link or button in an email and pasting it in a browser). It makes the phone considerably less user-friendly. What a shame. Any feedback or input here? I'd really appreciate it.
Note: I have seen things online for "FRP" when I search for that very quote, but I don't think this has anything to do with a "reset phone."
Thanks so much!
Click to expand...
Click to collapse
Do you have an anti-virus app installed? If so try removing it.
Sent from my SM-N930T using Tapatalk
dig into the default browser's settings, and see if there are any silly security features enabled.
you could also try a 3rd party browser.
rcobourn said:
Do you have an anti-virus app installed? If so try removing it.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
No, I have no anti-virus installed. This didn't happen with my first, shall I say "more volatile," Note 7, and I simply allowed Android and Google to simply restore the exchange device to precisely the same state (in terms of apps installed, etc.) as the original.
Sent from my SM-N930V using Tapatalk
thedicemaster said:
dig into the default browser's settings, and see if there are any silly security features enabled.
you could also try a 3rd party browser.
Click to expand...
Click to collapse
I don't know that it's a browser issue, as I'd also mentioned that it also happened when I tapped "About Google Play." It doesn't even attempt to access a browser. For good measure, though, I did poke around Chrome and didn't find anything that would be helpful there. [emoji20]
Sent from my SM-N930V using Tapatalk
discgolfdc said:
I don't know that it's a browser issue, as I'd also mentioned that it also happened when I tapped "About Google Play." It doesn't even attempt to access a browser. For good measure, though, I did poke around Chrome and didn't find anything that would be helpful there. [emoji20]
Sent from my SM-N930V using Tapatalk
Click to expand...
Click to collapse
I have a brand new green battery N7. Never had any problems.
Just do a factory reset to your phone. Be aware of restoring backups. Maybe that's the source of your problem...
Sent from my SM-N920C using XDA-Developers mobile app
I mentioned the browser because every action you mentioned that results in that error is supposed to open a page in the web browser.
have you tried resetting the default browser?(I have no access to the new settings app, so I can't explain where to find that option)
update to latest firmware or do a hard reset on your device..
Sent from my SM-N930F using Tapatalk
calinormy said:
I have a brand new green battery N7. Never had any problems.
Just do a factory reset to your phone. Be aware of restoring backups. Maybe that's the source of your problem...
Sent from my SM-N920C using XDA-Developers mobile app
Click to expand...
Click to collapse
I did. There are only 4 "backups," per se, that I restored: Aqua Mail (configuration), Business Calendar (configuration), Nova Launcher (configuration) and Authenticator Plus (accounts). Aside from that, Android and Google's native "restore apps" function handled the job 100%. It should also be said that performing the exact same procedure and restoring the very same backed-up configurations resulted in a perfectly functional white-battery Note 7 when going to it from my previous Note 4. That's why all of this is so confusing. I didn't do any tinkering. I know some here will probably say "that, right tbereis your first mistake," but I prefer to know I have a functioning device before I decide (or don't) to do any modifications. It might just be that I take it back to Verizon while I can and see if they'll let me swap it for another. Who knows? Ghost in the machine?
Sent from my SM-N930V using Tapatalk
discgolfdc said:
I did. There are only 4 "backups," per se, that I restored: Aqua Mail (configuration), Business Calendar (configuration), Nova Launcher (configuration) and Authenticator Plus (accounts). Aside from that, Android and Google's native "restore apps" function handled the job 100%. It should also be said that performing the exact same procedure and restoring the very same backed-up configurations resulted in a perfectly functional white-battery Note 7 when going to it from my previous Note 4. That's why all of this is so confusing. I didn't do any tinkering. I know some here will probably say "that, right tbereis your first mistake," but I prefer to know I have a functioning device before I decide (or don't) to do any modifications. It might just be that I take it back to Verizon while I can and see if they'll let me swap it for another. Who knows? Ghost in the machine?
Sent from my SM-N930V using Tapatalk
Click to expand...
Click to collapse
I have the AT&T version, no such issues (I know that doesn't help) what I would do as suggested above is wipe the phone and start over as new without installing anything from a restore. It's a pain but this will remove any possibility of carrying something over from your previous Note. I would think it has to be something in the permissions portion of an app, Knox or the O/S that is not registered correctly??
I think I'm going to see if Verizon will swap the unit before I do that, seeing as though I believe I recall seeing the message after a previous factory reset and before any significant restoration had taken place. What I can do on one phone, I can do on another, I guess. I may see if, after powering up straight out of the box, it gives me the same problem, I'll wipe it and restore everything manually, much as that blows. If it still operates the same way, well, I guess that will teach me that not every upgrade is an upgrade.
Sent from my SM-N930V using Tapatalk
Birdsfan said:
I have the AT&T version, no such issues (I know that doesn't help) what I would do as suggested above is wipe the phone and start over as new without installing anything from a restore. It's a pain but this will remove any possibility of carrying something over from your previous Note. I would think it has to be something in the permissions portion of an app, Knox or the O/S that is not registered correctly??
Click to expand...
Click to collapse
In my previous response, I meant to say 'straight out of the box and letting it restore everything fresh and uninterrupted by me.
discgolfdc said:
I think I'm going to see if Verizon will swap the unit before I do that, seeing as though I believe I recall seeing the message after a previous factory reset and before any significant restoration had taken place. What I can do on one phone, I can do on another, I guess. I may see if, after powering up straight out of the box, it gives me the same problem, I'll wipe it and restore everything manually, much as that blows. If it still operates the same way, well, I guess that will teach me that not every upgrade is an upgrade.
Sent from my SM-N930V using Tapatalk
Click to expand...
Click to collapse
Sent from my SM-N930V using Tapatalk
Did you ever find a fix for the problem? I have the same thing going on. Just got mine Oct 1st (replaced a Note 3) and love everything about it (except for the "potential" lethal aspect and the annoying situation with the "your request has been declined due to security reasons" deal...) Everyone's saying I need to turn it in now and replace it... but there's no other phone available now that I would prefer (once I fix the glitch)
discgolfdc said:
Okay. I have a brand-spanking-new Galaxy Note 7, exchanged at Verizon for my prior IED version. Good news is that I don't have to worry about my battery self-immolating. The bad news is that I'm getting these "Your request has been declined for security reasons" toast messages when I attempt to carry out various and sundry simple tasks, such as clicking on a legitimate link in an email in my Gmail app or tapping on "About Google Play Store" in the Play Store app. Are there some sort of Gestapo security measures added to the 2nd Gen Note 7 that weren't on the 1st? Is there a way to knock these down a peg? This is insane...to the point where I have to find creative ways around the block to get things done (such as copying the address from the link or button in an email and pasting it in a browser). It makes the phone considerably less user-friendly. What a shame. Any feedback or input here? I'd really appreciate it.
Note: I have seen things online for "FRP" when I search for that very quote, but I don't think this has anything to do with a "reset phone."
Thanks so much!
Click to expand...
Click to collapse
Did you ever find a solution to this problem?
chrisherts said:
Did you ever find a fix for the problem? I have the same thing going on. Just got mine Oct 1st (replaced a Note 3) and love everything about it (except for the "potential" lethal aspect and the annoying situation with the "your request has been declined due to security reasons" deal...) Everyone's saying I need to turn it in now and replace it... but there's no other phone available now that I would prefer (once I fix the glitch)
Click to expand...
Click to collapse
For now I'm still okay with mine, nothing is popping up.
Yeah I found a solution. I now have the LG V20.
Sent from my VS995 using Tapatalk
Ironacally while you would have normally gotten help how to solve your problem, this forum is now only focused on keeping/not keeping the phone. Compare it to other forums here and think. People can't even extract asked for apks.
Has anyone run across issues with the MobileIron SecureApps module not being found after previously working just fine on the most recent OxygenOS Beta 13?
Yes, Mine is constantly losing configs, saying its not registered but works again when a force check in is done.
You know how your work has the config set up? I just finished deploying for our work environment using android enterprise and it is working flawlessly with exception of a few add-on launchers. I run several different ROMs and it works on all of them.
Sent from my ONEPLUS 3 using Tapatalk
noobtoob said:
You know how your work has the config set up? I just finished deploying for our work environment using android enterprise and it is working flawlessly with exception of a few add-on launchers. I run several different ROMs and it works on all of them.
Click to expand...
Click to collapse
I am not sure. Now that I am on OOS Beta 19 it only seems to happen much less frequently. I have found you can just go to the Secure Apps app, it will prompt you for your password, and that this is enough to get the other apps (Mail, Calendar, etc) to see the Secure Apps and allow login. My Help desk raised a ticket with MobileIron, who acknowledge that they are aware of the issue. Now that I know I can get access restored by logging into Secure Apps module, it is not a headache anymore.
Why do you use such piece of software on rooted devices?
romskii said:
Why do you use such piece of software on rooted devices?
Click to expand...
Click to collapse
I am not rooted. That is what the Secure App module checks.
ariesgodofwar said:
I am not sure. Now that I am on OOS Beta 19 it only seems to happen much less frequently. I have found you can just go to the Secure Apps app, it will prompt you for your password, and that this is enough to get the other apps (Mail, Calendar, etc) to see the Secure Apps and allow login. My Help desk raised a ticket with MobileIron, who acknowledge that they are aware of the issue. Now that I know I can get access restored by logging into Secure Apps module, it is not a headache anymore.
Click to expand...
Click to collapse
So, mobile iron fixed this issue, I was reading through their android corner the other day. Should've posted the content here for you. When I get back to work tomorrow on Monday, I'll try and remember to post the fix.
It's pretty simple, just have to enable secureapps at startup, but can't remember where to do this.
Sent from my ONEPLUS 3 using Tapatalk
noobtoob said:
So, mobile iron fixed this issue, I was reading through their android corner the other day. Should've posted the content here for you. When I get back to work tomorrow on Monday, I'll try and remember to post the fix.
It's pretty simple, just have to enable secureapps at startup, but can't remember where to do this.
Sent from my ONEPLUS 3 using Tapatalk
Click to expand...
Click to collapse
Yes, please do. Thanks!
Fix?
ariesgodofwar said:
Yes, please do. Thanks!
Click to expand...
Click to collapse
From the Mobile Iron Support site:
Work Around
Enable Secure App Manager in App Auto-Launch.
On the One Plus device go to Settings > Apps
Click on Settings
Settings > Apps
Scroll down and click on App auto-launch
App auto-launch
Enable Secure App Manager
Enable Secure App Manager
Since I'm running AOSP, I'm not really running into any issues. I'm also using my device as a BYOD, but hopefully this helps.
I'm trying to install the [email protected] app on my device OnePlus 3 which is running on Oxygen OS 5 (Android 8.0.0), I'm getting similar error message. With Oxygen OS 5 there is no option to Enable Secure App Manager or modify App Auto Launch settings. What is the work around? Please help.
Suri
suri091 said:
I'm trying to install the [email protected] app on my device OnePlus 3 which is running on Oxygen OS 5 (Android 8.0.0), I'm getting similar error message. With Oxygen OS 5 there is no option to Enable Secure App Manager or modify App Auto Launch settings. What is the work around? Please help.
Suri
Click to expand...
Click to collapse
I checked the mobile iron forums and have not seen a work around for Oreo. Strange however, I have it installed and everything is running fine. Are you using the device in a BYOD environment or in a corporate owned state?
A lot of [email protected] has to do with the way it is set up (phone to server), so without knowing all of this information, I can't necessarily recommend any fixes.
Can you throw up some app settings and screen shots by chance? Please blur out any information before hand that is no one else should know.
Sent from my ONEPLUS A3000 using Tapatalk