Chase Bank App - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

So after updating to NC2 Kitkat all apps are functioning as one would expect, save for one: the Chase Bank app. I repeatedly try to log in and it accepts my credentials, forwards me to a confirm identification by using an authorization code screen. From there I click email/text/call to get an authorization code which comes promptly.
The problem is when I enter it in, it accepts it then spits an error station that my accepted login credentials are incorrect (they're not) and I'm rerouted back to the login screen to repeat the cycle in futility.
Now what's odd is if I go to the mobile site using ANY browser on my phone (stock browser, chrome, Firefox, opera, tried em all) it will do the SAME thing. However, the moment I click "use desktop mode" and try to log in using the full site, it works perfectly, no hiccups whatsoever.
So, this means something on my phone is blocking the use of the mobilized versions of Chase's site. My first thought was my ad blocker. I disabled that completely and uninstalled it, rebooted, and still no dice.
Any ideas? Had anyone else had this same experience? I'm running stock, rooted, de-odexed Kitkat NC2 for reference. No tweaks aside from Wanam via Xposed framework.

Another thought was maybe it's checking my root status as ISIS Mobile Wallet does. Thus I downloaded a root cloak (aptly called rootcloak in Xposed download section) for just such apps. Alas, this too is not the problem.
Sent from my SM-N900V using Tapatalk

Im on nc4 non rooted device and the app works flawlessly. Not sure if this helps you just adding my .02 A lot of the lil bugs I encountered were gone after a full reset. maybe u should try it.
Sent from my SM-N900V using XDA Free mobile app

I'm using NC4 rooted and Chase is working fine for me. I never had to verify though because I restored the app from titanium backup. It may be obvious but did you try clearing the app data? Maybe you have a backup to restore from when it was working?
Edit: Rereading your post, I also successfully used Chase on NC2. Also, you can use Titanium Backup to restore an app and data from a nandroid backup if you didn't backup through titanium.

Related

[Q] Huge bug with ATT 4.5.91, or just me?

So I updated from stock 1.83, unlocked and rooted. It is now impossible to add a new contact. I get "The application Contacts Storage (process com.motorola.contacts) has stopped unexpectedly. Please try again."
Is anyone else having this issue? Are there any fixes out there that I'm unaware of?
Nope
GuyIncognito721 said:
So I updated from stock 1.83, unlocked and rooted. It is now impossible to add a new contact. I get "The application Contacts Storage (process com.motorola.contacts) has stopped unexpectedly. Please try again."
Is anyone else having this issue? Are there any fixes out there that I'm unaware of?
Click to expand...
Click to collapse
I just tried and it worked perfectly for me. Although when asked I selected Google contacts as my default storage... I don't use blur. Oh, and my phone was brought up the same as yours 1.83 Unlocked and Rooted -> 4.1.91 Unlocked and Rooted.
Did you wipe everything when you installed via CWM? I always manually wipe everything.
Same here. No issues adding. 4591 stock (no going back!), rooted, unlocked bl.
Sent from my MB860 using XDA App
matthebe said:
I just tried and it worked perfectly for me. Although when asked I selected Google contacts as my default storage... I don't use blur. Oh, and my phone was brought up the same as yours 1.83 Unlocked and Rooted -> 4.1.91 Unlocked and Rooted.
Did you wipe everything when you installed via CWM? I always manually wipe everything.
Click to expand...
Click to collapse
I updated to 1.91 via update.zip and did not wipe anything since it wasn't rooted/unlocked. When I try to go into the settings in contacts and change where my contacts are stored, I get force closed again.
Not sure what the problem is , and with all the issues reflashing sbf's and bricking, I don't feel like trying any of that out.
GuyIncognito721 said:
I updated to 1.91 via update.zip and did not wipe anything since it wasn't rooted/unlocked. When I try to go into the settings in contacts and change where my contacts are stored, I get force closed again.
Not sure what the problem is , and with all the issues reflashing sbf's and bricking, I don't feel like trying any of that out.
Click to expand...
Click to collapse
Hate to say this but you may need to do a factory reset. Most likely it will be the only way to fix it.
Back up your standard apps (no system settings or apps ) and then do the wipe.
Sent from my MB860 using XDA App
DarrellRaines said:
Hate to say this but you may need to do a factory reset. Most likely it will be the only way to fix it.
Back up your standard apps (no system settings or apps ) and then do the wipe.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I would have to agree with this assessment. I flashed to beta 4.5 and did a TB restore and the phone was very unresponsive and took 2-4 minutes to boot. Many apps were not even working. I performed a Data wipe/factory reset and cache wipe to fix it.
Ok, fixed it. I'm an idiot. Froze some stuff with TBU. Of all things, it was Yahoo! Mail Authenticator 2.3.4 that was screwing it up.
Thanks for the suggestions, mods feel free to close this thread.
Pieces of the motoblur social apps I had frozen caused this for me too .. I'm just letting everything run without freezing anything until the final release and towing a generator behind me to keep the battery going
My phone work perfect. I install it by using fastboot. I think some phone have issue with clockwork recovery.
I restored "Contact Storage 2.3.4" with TiB and it stopped the FC and its working fine now.
Anyone got any suggestions about the radio not locking to HSPA+ signal and the GPS shows 0 feet error in GPS Status?
fastbikedroid said:
Pieces of the motoblur social apps I had frozen caused this for me too .. I'm just letting everything run without freezing anything until the final release and towing a generator behind me to keep the battery going
Click to expand...
Click to collapse
Yahoo authentication service was the culprit in my case of force close on selecting contacts. Make sure that it isn't frozen
Sent from my MB860 using XDA Premium App
SolidHelix said:
Yahoo authentication service was the culprit in my case of force close on selecting contacts. Make sure that it isn't frozen
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Thanks a lot. I suffer this problem after I tried to delete some apps from system/app/. now at lease I don't need to re-flash the rom again.
Thanks again.
thank you this saved me a reinstall..dont know y i need the yahoo service running, i dont even have a yahoo account set up on my phone

Official Marketplace Myapps isn't showing anything.

I'm not sure how it happened, but the official Google marketplace just doesn't work anymore.
On Bell Atrix, 2.3.6, Stock.
The Marketplace loads up fine, by when I go into my apps it just doesn't list anything. Not my installed apps, not my purchases, nothing. I can download apps just fine, but nothing then gets linked to my apps.
I have tried my account on 2 other devices(galaxy nexus and asus transformer), and it works fine. I have also tried someone else's account on my phone and that works.
I have tried a factory reset, and it the marketplace v2.3.6 works for the first login. But after it just gives the following error.
"A server error has occurred. retry, or cancel and return to the previous screen"
Retry just loops the error, with no success, and cancel just returns me to the marketplace's main page
After the marketplace updates, when I go to my apps I just get a generic white page w/my google account and 2 buttons to go to either the game or apps section.
This site lists the exact same issue I'm having. No fixes though =/
http://davesdroid.blogspot.com/2011/11/android-market-not-showing-my-apps.html
Try erasing market's cache, or using a different market version.
Sent from my MB860 using xda premium
I have the same issue. Nothing worked for me soo far... The only think you can do is to install cm7, cm9 or miui. It works on these roms just fine.
Sent from my MB860 using Tapatalk
install neutrino rom
JaronBang said:
Try erasing market's cache, or using a different market version.
Click to expand...
Click to collapse
Did all that, even did a few factory resets.
Foka002 said:
I have the same issue. Nothing worked for me soo far... The only think you can do is to install cm7, cm9 or miui. It works on these roms just fine.
Click to expand...
Click to collapse
I was hoping to avoid that. Blasphemy, I know, but I like being on stock.
Have you tried returning to stock, and seeing if it works?
Cryingmoose said:
Did all that, even did a few factory resets.
I was hoping to avoid that. Blasphemy, I know, but I like being on stock.
Have you tried returning to stock, and seeing if it works?
Click to expand...
Click to collapse
Yeah went back to stoc using sbf and that did not work. My 1st though was that titanium backup messed up my links or something then I saw that other people has the same problem... Wierd
Sent from my MB860 using Tapatalk
I emailed Android Market Support on friday when it started. They emailed back asking for more information pretty quickly.
However, I haven't heard anything, since responding to the initial email.
https://support.google.com/androidmarket/bin/request.py?contact_type=market_phone_tablet_web
Try submitting a request. It might not account to anything, but it may make them realize others are having the issue also
Try erasing market cache and then deleting /data/data/com.android.vending/databases/market_assets.db with some file manager. After rebooting market should work properly(but you may need instal something or restore links using TiBu) at least for while
EDIT: I have this error from ca. 1,5-2 months, reported it and google did exactly nothing about this issue
Ok, this has worked for me so far. My fingers are crossed that it'll be a permanent fix.
http://forum.xda-developers.com/showthread.php?t=1458670
1) Go to Market Tools -> Market Doctor and Unlink all User & System apps.
2) Reboot device.
3) Open any Root Explorer or Browser and locate and delete the file "market_assets.db" in "/data/data/com.android.vending/databases".
4) Reboot device.
5) Go to TB Pro and to Market Tools -> Market Doctor -> User Apps and link all the User Apps that you installed on your device from the Android Market. Make sure that no System App is linked.
6) Reboot device.
7) Install a free app
Looks like that was only a temp fix, because the issue came right back this morning....

[Q] Anyone have FoxFi working in 4.4.2 NC4?

I'm stumped here. I can't for the life of me get it to work.
1. Click activate hotspot
2. Get prompted to install certificate, asked for cert name
X. Then I get stuck at Enter password for credential storage.
I have no idea what this password might be, it's certainly not any password I've ever used.
I've tried various work-arounds found on teh google but none work so far.
Anyone have any magic to get this working?
Info: Stock rooted NC4, wanam xposed, couple of other modules, some bloat frozen with tibu etc.
Install the x tether module and use the stock hotspot app
Thanks, that works just as well as a workaround.
Sent from my SM-N900V using XDA Free mobile app
frieked said:
I'm stumped here. I can't for the life of me get it to work.
1. Click activate hotspot
2. Get prompted to install certificate, asked for cert name
X. Then I get stuck at Enter password for credential storage.
I have no idea what this password might be, it's certainly not any password I've ever used.
I've tried various work-arounds found on teh google but none work so far.
Anyone have any magic to get this working?
Info: Stock rooted NC4, wanam xposed, couple of other modules, some bloat frozen with tibu etc.
Click to expand...
Click to collapse
I am stock, not rooted and it works fine after the latest OTA. It is a bit annoying because sometimes the popup certificate warning comes up, other times it doesn't...but then you have to click the hotspot on within 30 seconds before it works.
I'll be glad to get home and get them to replace this thing. FoxFi is the only thing that works reliably after the OTA.

Rooted, can no longer receive MMS

I installed root with towelroot and installed safe strap recovery 3.72. I have frozen a lot of bloatware with titanium backup as well. I'm not using any custom roms either. I've messed around with my APN settings yet none of the ones I try work. I only receive MMS as soon as I restart, all at once. Everything after that shows up as downloadable but always fails to download. Any ideas?
something you froze. Root by itself won't cause that problem
Sent from my Nexus 9 using XDA Free mobile app

Snapchat on rooted LG V20

I am trying to login to Snapchat but it keeps saying there's an error with the login and I found out it is because I am rooted. A fix I found involves full unroot and I don't want to do that. Can anyone help me?
Snapchat
Ive used snapchat rooted. On mutiple roms.
Snapchat for some devices (like the v20 now) is checking for root. It's hit or miss really. On my VS995 Snapchat wouldn't work till I did suhide. So you'll have to most likely use Magisk or SU-Hide or some kind of root hiding thing to get past it.
Just install Snapchat on a other device, log in, make a backup with Titanium Backup and load it on your main device.
This worked for my rooted S5 KLTE
D.Va said:
I am trying to login to Snapchat but it keeps saying there's an error with the login and I found out it is because I am rooted. A fix I found involves full unroot and I don't want to do that. Can anyone help me?
Click to expand...
Click to collapse
magisk hide is option 1
rootswitch is option 2
full unroot, sign in, then re-flash the supersu zip to re root is option 3
restore a app+data backup from a logged in device using backup app like titanium is option 4..
Team DevDigitel said:
magisk hide is option 1
rootswitch is option 2
full unroot, sign in, then re-flash the supersu zip to re root is option 3
restore a app+data backup from a logged in device using backup app like titanium is option 4..
Click to expand...
Click to collapse
Personally i feel option 2 is easiest but not all kernels like it.
I wish these things could be put in to roms so when we flash them, there's no alternate flashing needed that could cause issues.. I had nothing but issues tryna get both of those options to work, but again it was probably kernel related so I just gave up on it..
jdmsohc22 said:
I wish these things could be put in to roms so when we flash them, there's no alternate flashing needed that could cause issues.. I had nothing but issues tryna get both of those options to work, but again it was probably kernel related so I just gave up on it..
Click to expand...
Click to collapse
Actually, the Stock deOdexed US996 ROM has them built into it, also allows for hotspot provisioning without having to edit anything. I've been running it for a few months now, and been flawless on every aspect, other than it disables the ability to use MyVerizon apps, and Verizon's visual voicemail.

Categories

Resources