Yeah, asshats suck.
Are you talking about the "verizon single sign on engine?" Cause it doesn't work with that either."Jaxidian said:I forget what the name was but would that security app that was released a while ago that identifies and modifies apks that perform sensitive things, like imei, network, etc., but could this app quickly help us by hard-coding verizon in as our carrier? Sounds easier than hand-editing the apk.
Privacy Blocker is what I was thinking of and I wasn't able to get any different result by using it.
Sent from my Thunderbolt using Tapatalk
Well, I was doing it on the NFL app but you're right, should prolly do it on the SSO engine as well/instead. Thanks for trying that too, and thanks for correcting my errant thinking.luniz7 said:Are you talking about the "verizon single sign on engine?" Cause it doesn't work with that either.
Well the sso engine installs and everything but it doesn't solve the problem with the nfl app or the my verizon app"Jaxidian said:Well, I was doing it on the NFL app but you're right, should prolly do it on the SSO engine as well/instead. Thanks for trying that too, and thanks for correcting my errant thinking.
The Verizon SSO engine could still certainly be the thing to focus on here. Here's how SSO setups usually work:Balber said:I've also tried multiple AOSP builds over the last 1 1/2 months and had the exact same issue. If you don't install the Verizon SSO engine you get this error, "ERROR - This application requires the Verizon Login Client. Please download the login client and start the application again. Error code -305" Once you install the Verizon SSO engine, you get the other error that others are referring too. So we can rule out the Verizon SSO engine, because you need that to start the NFL app, but then NFL mobile still checks home somewhere which is flagging the requirement to be a Verizon customer. I've also checked around on the net prior and other people are having similar issues with no resolution. Everyone's "fix" was to use a Sense-based ROM. @Jaxidian, I will look into the privacy blocker application, haven't played around with that at all. I've also noticed that My Verizon doesn't work either. Could this also be a similar issue?