[MOD] Patched Google Wallet for Galaxy S4 (Version 2.x+ - New Version) - Verizon Samsung Galaxy S 4

Patched Google Wallet for Galaxy S4
(Version 2.x+ - New Version)
{
"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"
}
Description: This method will help you get Google Wallet (version 2.0+) working on your Verizon Galaxy S4. This should also work on AT&T/Sprint/T-Mobile Galaxy S4 as well.
Please Note
This method has been tested and guaranteed to work on stock odexed VRUAME7 build on the Verizon Galaxy S4. Other custom ROMs on the same device and other Galaxy S4s are welcome for testing but not guaranteed as working.
If you happen to have issues with this version of Google Wallet no matter what you test, please consider using the older version which seems to be working for more ROMs: Link Here
In order to use this method you need to be rooted and have a custom recovery or SafeStrap recovery on your device.
Downloads (Version 2.0-R133-v14)
TouchWiz Only - Download Link
AOSP Only - Download Link
Click to expand...
Click to collapse
How to Apply Mod
If you have Xposed app installed you don't need to remove it
Just be sure to disable/uncheck the Google Wallet Root and Region Check Remover in the Modules section of the app if you have it installed
You DON'T need to "Reset" your current Google Wallet in the app if you have any installed
Just "Force Stop" the Wallet app (in the Application manager section on your device)
Then "Clear Cache" and "Clear Data" on Wallet app (in the Application manager section on your device)
Using Root Explorer, delete all traces of the Wallet app from both locations /system/app/ and /data/app/
It could be called com.google.android.apps.wallet.apk or similar or could be called Wallet.apk as well so check for both
Then reboot your device right after this is done
Flash the one of the attached zip files I have in this post using your custom recovery
Once you boot back into Android, just open the Wallet app and set everything up, and setup Tap and Pay but wait till it finishes and says it is ready
Check what "Tap and Pay" says in "About" section of the app and then you can close Google Wallet and should be all set
Click to expand...
Click to collapse
Transaction Process
When you're ready to pay with Google Wallet DON'T open the app at all
Just unlock your device to the home screen and tap it on the POS system in the store and the app will launch on its own
This should ask you for a PIN now, just enter your PIN and it should authorize the transaction
Confirm the transaction went through by a receipt getting printed
It might ask you to tap the device or enter the PIN one more time just in case so don't worry if it does as long as you have the receipt
Click to expand...
Click to collapse
Credits
Credit goes to loserskater for patching the new Google Wallet apk to work for most devices (Original Post)

Thanks will try...I'm rooted and ss installed but no ROMs stock me7...no exposed so just flash this to stock ROM ams reboot no other files right? Just this one?
Sent from my SCH-I545 using XDA Premium 4 mobile app

Poofster said:
Thanks will try...I'm rooted and ss installed but no ROMs stock me7...no exposed so just flash this to stock ROM ams reboot no other files right? Just this one?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Correct sir! Let us know how it goes. :good:

working for me like i said in last thread, but i dont get why i cant open the app first as i do the wallet thing?

jerrah said:
working for me like i said in last thread, but i dont get why i cant open the app first as i do the wallet thing?
Click to expand...
Click to collapse
You can (that's the way I've been doing it on the old version) but I'm just mentioning this proper way because that's the same way Google mentions how to do in the Wallet app itself if you look up the "help" on how to tap and pay in the app. It could work either way though but I recommend trying my/official way first for testing before trying opening the app first and then paying.

Deleted the test zip and downloaded the new TW zip posted in the OP. Initial set up went smooth. Going to try to make a purchase tomorrow and report back on my findings. Running Hyperdrive RLS9.1 with KToonz kernel.

RJV3 said:
Deleted the test zip and downloaded the new TW zip posted in the OP. Initial set up went smooth. Going to try to make a purchase tomorrow and report back on my findings. Running Hyperdrive RLS9.1 with KToonz kernel.
Click to expand...
Click to collapse
Please also note that the TW zip I have now is the same as Test-2 zip was before in case anyone is already running this version there's no need to rerun this method again.

I installed eclipse 2.0 today. I installed the test 2 zip from prior thread. I heard it works on this ROM. I did only have a battery for percentage of 8 when I tried this but it didn't do a damn thing at the terminal. Didn't vibrate or anything. Does it not work past a percentage? What's the minimal battery it needs.
Sent from my SCH-I545 using Tapatalk 4

dseda86 said:
I installed eclipse 2.0 today. I installed the test 2 zip from prior thread. I heard it works on this ROM. I did only have a battery for percentage of 8 when I tried this but it didn't do a damn thing at the terminal. Didn't vibrate or anything. Does it not work past a percentage? What's the minimal battery it needs.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
I couldn't even setup tap to pay when i was at 9% FYI (it straight up told me I have to charge the device). So that could very well be why. My guess is minimum either 10% or 15%. I would just do it on 25%+ just to be sure though.

open1your1eyes0 said:
I couldn't even setup tap to pay when i was at 9% FYI (it straight up told me I have to charge the device). So that could very well be why. My guess is minimum either 10% or 15%. I would just do it on 25%+ just to be sure though.
Click to expand...
Click to collapse
Will try again. I am currently speaking with a user of eclipse who found this new wallet to work perfectly fine. It didn't even vibrate for me which was odd but then I looked at my phone and it said that I had 8 percent left. So I'll try tomorrow with a little more juice. All this flashing and modding has my baby tired!
Sent from my SCH-I545 using Tapatalk 4

Has anyone attempted and/or successfully installed via this method with slimbean 4.3? I think I'm going to try it.
May be slightly off topic but has anyone actually called customer service to verify their identity? If so, what was the process like? Types of questions, how long did it take approximately, what do they need/require from you as far as documentation? I'm assuming you're just dictating to them the personal info that they give you the option of scanning (ss#, a bill of some sort and a DL # or something?)
Thanks and sorry for the off topic question.
Kevin

open1your1eyes0 said:
Please also note that the TW zip I have now is the same as Test-2 zip was before in case anyone is already running this version there's no need to rerun this method again.
Click to expand...
Click to collapse
All noted no need to delete the test zip. Nevertheless...... Epic fail. Tried it at McDonald's today. No go. Any suggestions? Running Hyperdrive 9.1
Rooted S4

No go for me..... Running Hyperdrive 9.1
Rooted S4

RJV3 said:
All noted no need to delete the test zip. Nevertheless...... Epic fail. Tried it at McDonald's today. No go. Any suggestions? Running Hyperdrive 9.1
Rooted S4
Click to expand...
Click to collapse
I get that too before i did the v2 one. But now i get that the tap to pay is being set up and should be done in a few minutes. Been like that for hours. Any fix/

I wanted to share my experience with wallet mod on Beans build6 Me7. I finally found a store with a pay pass that does work. The cashier scanned my stuff and when I went to pay wallet beeped and then came up and said processing transactions. It proceeded to say waiting on cashier to approve. I ask the cashier if it processed and she said no. I asked her to try it again and this time try credit. I tapped the phone and nothing happened this time.
I just wanted to share this and hopefully this gets usone step closer to figuring this thing out.
Sent from my SCH-I545 using Tapatalk 4

No luck on eclipse 2.0 ROM either.
Sent from my SCH-I545 using Tapatalk 4

I'll try it out tomorrow!
You guys ROCK for making these processes so easy on us.!
I will try my best to use it tomorrow and report back on how it works. The upgrade process went smoothly, and Tap and Pay only took about 45 seconds to setup.
Fingers crossed!

JPMontana said:
You guys ROCK for making these processes so easy on us.!
I will try my best to use it tomorrow and report back on how it works. The upgrade process went smoothly, and Tap and Pay only took about 45 seconds to setup.
Fingers crossed!
Click to expand...
Click to collapse
Cross them tight. So many of us are having issues with it and some aren't. I wish there was a fool proof method of having this work. Believe me I've flashed 3 roms in the past few days and reflashed eclipse four times already clean to try and get it to work.
I even went as far as going to wallet.google.com and disabling all of my devices and setting up from scratch. Don't know why my info won't go to the reader. I certainly see that the phone detects a reader because that's what it says, but after that it says that my transaction may not have gone through. Best of luck, hopefully we can all have a concrete version that'll work on every phone and every rom, but for now I'll stick with the old mod.
Seriously Verizon needs to quit it with that Isis bull**** and let us use wallet.

blacklabel2020 said:
I get that too before i did the v2 one. But now i get that the tap to pay is being set up and should be done in a few minutes. Been like that for hours. Any fix/
Click to expand...
Click to collapse
What kernel are you using? I'm running ktoonz kernel and I get all the way to the transaction summation screen.
When I was on darkslide rom and using elite kernel, old wallet apk worked. I'm wondering if this is kernel related. Anyone have Hyperdrive 9.1 installed and runnite elite kernel and is willing to give the new wallet apk a try?
Sent from my SCH-I545 using Tapatalk 4

RJV3 said:
All noted no need to delete the test zip. Nevertheless...... Epic fail. Tried it at McDonald's today. No go. Any suggestions? Running Hyperdrive 9.1
Rooted S4
Click to expand...
Click to collapse
yea i keep getting the same message to when i try to use the NFC, i can install no problem but when i try to use the NFC for payment it says "reader detected. your last tap may not have been successful" . ive even held it there for like 15 secs and still not working. Anyone else getting this when trying to use the NFC for payment using google wallet v2 ?

Related

Jelly Bean Optimus One Discussion

OK This thread is for THIS ROM. Please don't come here posting questions for other ROMs
OK This is for general discussion of the ROM. General discussion about the ROM, Google Apps, etc...
please keep the other thread for DEVELOPMENT ONLY!!!!
Thanks! Now chat away!
Good, thank you
Just FYI, lupohirps latest build is much smoother and has semi-project butter working, i wont call it full since it still is slightly laggy...
Sent from my LG-P500 using Tapatalk 2
RockR172 said:
Just FYI, lupohirps latest build is much smoother and has semi-project butter working, i wont call it full since it still is slightly laggy...
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
Where can we find that build?
Thanks!
Sent from my LG-P500 using xda app-developers app
Thanks Rashed,
testing on my O1.
when phone es turned off, turns ON when you connect it to AC for charging.
also when charging, and you turn it OFF, it doesn't, reboots instead.
I'll post more things I notice, and expectin next build soon.
Thanks again.
andreuspvr said:
Thanks Rashed,
testing on my O1.
when phone es turned off, turns ON when you connect it to AC for charging.
also when charging, and you turn it OFF, it doesn't, reboots instead.
I'll post more things I notice, and expectin next build soon.
Thanks again.
Click to expand...
Click to collapse
Yeah, I know about that one. Something is wrong with the boot.img...
It existed in CM9 too
As for the next build, expect one sometime in the next 7 hours
That's because Offline Charging is disabled.
It is still buggy.
{
"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"
}
gekko69 said:
Where can we find that build?
Thanks!
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
https://github.com/downloads/lupohirp/cm_device_lge_p500/cm_p500-ota-eng-02082010.lupohirp.zip
I think the date stamp should be 02082012?
deleted
when can we download your rom without use of rom manager premium.
Rashed97's ROM download without ROM Manager Premium: http://www.clockworkmod.com/rommana...name=Rashed's ROMs&deviceName=LGE Optimus One
Google Now
Anyone noticed that Google Now doesn't seem to work? It doesn't FC anymore but it won't let you scroll through the different cards...
EDIT: Oh, and also... Link2SD is still un-usable. After installing it, downloading apps from Play Store makes the process "system" crash and there's nothing you can do from that point, you have to reboot your phone.
juandpineiro said:
Anyone noticed that Google Now doesn't seem to work? It doesn't FC anymore but it won't let you scroll through the different cards...
EDIT: Oh, and also... Link2SD is still un-usable. After installing it, downloading apps from Play Store makes the process "system" crash and there's nothing you can do from that point, you have to reboot your phone.
Click to expand...
Click to collapse
What Google Apps package are you using?
Link2SD works fine for me
I'm using latest "light" gapps. The problem with Google Now is not only with the cards but when I search something I can't scroll through the results, only the top part of the screen "moves" when scrolling.
Link2SD does work but I'm not sure why but it makes it a pain to install new apps. Having to reboot phone each time because system process crashed. And must be done each time you install a single app... :silly:
Rashed97 said:
What Google Apps package are you using?
Link2SD works fine for me
Click to expand...
Click to collapse
juandpineiro said:
I'm using latest "light" gapps. The problem with Google Now is not only with the cards but when I search something I can't scroll through the results, only the top part of the screen "moves" when scrolling.
Link2SD does work but I'm not sure why but it makes it a pain to install new apps. Having to reboot phone each time because system process crashed. And must be done each time you install a single app... :silly:
Click to expand...
Click to collapse
Weird, I've installed quiet a few apps...
And is that my Google Apps Lightweight? If it is, I used the modifies Velvet.apk for CM9. That's why it actually opens.
Hey, Google Now doesn't work for me, I am getting FC Do you know what the problem is? I reflashed the ROM and I am using the 'Micro GApps', anyway same problem
juandpineiro said:
Anyone noticed that Google Now doesn't seem to work? It doesn't FC anymore but it won't let you scroll through the different cards...
EDIT: Oh, and also... Link2SD is still un-usable. After installing it, downloading apps from Play Store makes the process "system" crash and there's nothing you can do from that point, you have to reboot your phone.
Click to expand...
Click to collapse
Use davidnt mod, first delete some systen apps so it have space for the mod to work it works here just fine, not a single issue
Sent from my LG-P500 using xda app-developers app
@Rashed
Still the p500 with ROM build1 can't be detected as USB modem (I meant no USB tethering) by Slackware machine. Could you please to fix it? I encountered that bug (?) in all ROM (ICS and JB) I ever have flashed it, but GB (OpenOptimus ROM build 2.202.1)!.
Anyway, your ROM even it's the first built is one of the great JB ROM for obsolete phone hardware. It's almost stable imho. If you can fix mentioned above problem and the camera, it'll be perfect for my daily use!
Hey, as I posted, take a break from your hard hacking! Enjoy your real live. Have fun!
xu3sno said:
@Rashed
Still the p500 with ROM build1 can't be detected as USB modem (I meant no USB tethering) by Slackware machine. Could you please to fix it? I encountered that bug (?) in all ROM (ICS and JB) I ever have flashed it, but GB (OpenOptimus ROM build 2.202.1)!.
Anyway, your ROM even it's the first built is one of the great JB ROM for obsolete phone hardware. It's almost stable imho. If you can fix mentioned above problem and the camera, it'll be perfect for my daily use!
Hey, as I posted, take a break from your hard hacking! Enjoy your real live. Have fun!
Click to expand...
Click to collapse
Thanks!
See the reply at the other thread
juandpineiro said:
Anyone noticed that Google Now doesn't seem to work? It doesn't FC anymore but it won't let you scroll through the different cards...
Click to expand...
Click to collapse
To make Google Now work, you have to use the version for ARMv6 from this link(from 'Instructions for ARMv6 devices')>> http://forum.xda-developers.com/showthread.php?t=1816622 !!! To get the voice work (it will listen to you, but will repeat what you said, but at least you don't have to write what you are looking for) use the workaround: The Voice Search for Google Now app. More details in the link!!! And yes, this method should work on Jelly Bean, not only on ICS. Good Luck!!! :good:

[Google Wallet] Device set-up failed

Hello all,
I recently flashed CyanogenMod 10.1 on my Verizon Galaxy Note II. I previously came from a stock, deodexed ROM where Google Wallet worked. Apparently, sometime in the past week, Google Wallet no longer works on many devices (including the Galaxy Note II) and gives the following error:
Device set-up failed
Unable to set up Wallet for purchases
First, make sure you have a reliable Internet connection.
If the problem persists, restart your device and try again.​
The main reason I am putting this here is that it seems to have gotten buried within all the other Google Wallet threads with no replies. If a solution is found, I will update this post so it is easily found again.
Has anyone else had this issue? Has anyone gotten around this issue? Is my NFC secure element borked and Google Wallet will never work on my device again?
Thanks!
NOTES: My build.prop is set to a Galaxy Nexus. I have the Xposed module installed. I have tried an older version of the Wallet app which gives the same error. I've read somewhere that this might actually be a server-side constraint which would rule out anything we can do on the device.
I loaded it fine today for the for the first time with no problems..I also changed my build.prop to galaxy nexus.. I'm currently on PA 3+ and matrix kernel..
Sent from my SCH-I605 using xda app-developers app
lacoursiere18 said:
I loaded it fine today for the for the first time with no problems..I also changed my build.prop to galaxy nexus.. I'm currently on PA 3+ and matrix kernel..
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the input. Hopefully my NFC secure element hasn't been borked. That would be upsetting.
Anyone else?
lacoursiere18 said:
I loaded it fine today for the for the first time with no problems..I also changed my build.prop to galaxy nexus.. I'm currently on PA 3+ and matrix kernel..
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
If you successfully set up, you're the first person that's been able to set up in a few weeks. Note 2's haven't been able to successfully provision in a while.
Even with a different ROM and build.prop adjustments? From my understanding people are having issues on TW bases and running build.prop as is and not modify it to reflect a different device..
Sent from my SCH-I605 using xda app-developers app
lacoursiere18 said:
Even with a different ROM and build.prop adjustments? From my understanding people are having issues on TW bases and running build.prop as is and not modify it to reflect a different device..
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Not sure about AOSP, but TW isn't working at all. You have to adjust the build.prop to get it to work at all. It used to work after that, but now, adjust the build.prop, and you can get it to get almost done, but it will never provision the payment info. It's not just on the Verizon version...it's across all unsupported carriers.
Not sure why this is a sporadic issue. My Wallet has never stopped working.
EVOme said:
Not sure why this is a sporadic issue. My Wallet has never stopped working.
Click to expand...
Click to collapse
Mine stopped only because I switched ROMs. They might have added some server side security to bow down to Verizon, AT&T and T-Mobile due to the competing ISIS system. <-- Just a guess.
EVOme said:
Not sure why this is a sporadic issue. My Wallet has never stopped working.
Click to expand...
Click to collapse
For people that are already provisioned, it hasn't stopped working, but if you try to set it up new, it will fail. That's been the common story.
Well good thing my Note is running cherry because I'll never change the rom until an official 4.2.2 is released...hopefully with S4 features.
tithefug said:
Hello all,
I recently flashed CyanogenMod 10.1 on my Verizon Galaxy Note II. I previously came from a stock, deodexed ROM where Google Wallet worked. Apparently, sometime in the past week, Google Wallet no longer works on many devices (including the Galaxy Note II) and gives the following error:
Device set-up failed
Unable to set up Wallet for purchases
First, make sure you have a reliable Internet connection.
If the problem persists, restart your device and try again.​
The main reason I am putting this here is that it seems to have gotten buried within all the other Google Wallet threads with no replies. If a solution is found, I will update this post so it is easily found again.
Has anyone else had this issue? Has anyone gotten around this issue? Is my NFC secure element borked and Google Wallet will never work on my device again?
Thanks!
NOTES: My build.prop is set to a Galaxy Nexus. I have the Xposed module installed. I have tried an older version of the Wallet app which gives the same error. I've read somewhere that this might actually be a server-side constraint which would rule out anything we can do on the device.
Click to expand...
Click to collapse
I have been having the same problem recently on my Nexus 4. I don't know what could be the issue, as it worked fine previously.
4.1.2
Did you upgrade to a ROM based on 4.1.2? If you look at the following file from 4.1.2 ROMs they have changed to allow ISIS only and not Google.
From a 4.1.1 ROM /system/etc/nfcee_access.xml
<?xml version="1.0" encoding="utf-8"?>
<resources xmlns:xliff="urnasis:names:tc:xliff:document:1.2">
<!-- Applications granted NFCEE access on user builds
See packages/apps/Nfc/etc/sample_nfcee_access.xml for full documentation.
-->
<!-- Google wallet release signature -->
<signer android:signature="3082044c30820334a003020102020900a8cd17c93da5d990300d06092a864886f70d01010505003077310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e205669657731143012060355040a130b476f6f676c6520496e632e3110300e060355040b1307416e64726f6964311330110603550403130a476f6f676c65204e4643301e170d3131303332343031303635335a170d3338303830393031303635335a3077310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e205669657731143012060355040a130b476f6f676c6520496e632e3110300e060355040b1307416e64726f6964311330110603550403130a476f6f676c65204e464330820120300d06092a864886f70d01010105000382010d00308201080282010100c30f88add9b492096a2c586a5a9a80356bfa026958f8ff0c5dfaf59f49268ad870dee821a53e1f5b170fc96245a3c982a7cb4527053be35e34f396d24b2291ec0c528d6e26927465e06875ea621f7ff98c40e3345b204907cc9354743acdaace65565f48ba74cd4121cdc876df3522badb095c20d934c56a3e5c393ee5f0e02f8fe0621f918d1f35a82489252c6fa6b63392a7686b3e48612d06a9cf6f49bff11d5d96289c9dfe14ac5762439697dd29eafdb9810de3263513a905ac8e8eaf20907e46750a5ab7bf9a77262f47b03f5a3c6e6d7b51343f69c7f725f70bcc1b4ad592250b705a86e6e83ee2ae37fe5701bcbdb26feefdfff60f6a5bdfb5b64793020103a381dc3081d9301d0603551d0e041604141ccece0eea4dc1121fc7515f0d0a0c72e08cc96d3081a90603551d230481a130819e80141ccece0eea4dc1121fc7515f0d0a0c72e08cc96da17ba4793077310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e205669657731143012060355040a130b476f6f676c6520496e632e3110300e060355040b1307416e64726f6964311330110603550403130a476f6f676c65204e4643820900a8cd17c93da5d990300c0603551d13040530030101ff300d06092a864886f70d01010505000382010100a470c728e1d31b06d9af6ae768b565046c57806b9843724931d75d4ca10c321520d33ccfed2aa65462234c9ef9b6f910cc676b99cb7f9895d6c06763574fbb78331275dc5cf38fbaa918d7938c051ffba2ade8f303cde8d9e68a048d1fdb9e7c9f2a49b222c68fff422bf15569b85eeeedb04aa30873dbe64b9c9e74f8f2c2f6c40124aaa8d1780d18512b540add28b3e9581971a4170dd868cf5f31e44712b2c23bb51037d7ef9f87a6e5bdb35e2ceb6bb022636c17a56a96bc7a50258c0bd2ed7b31555a18452e17321a0d52838c82f63f742d74ff79586a5cbb7faf7198a84bcf744310e9e927597f00a23dd00660800c2238d90b2fb372dfdbba75bd852e" />
<!-- Samsung wallet signature -->
<signer android:signature="3082037830820260a00302010202044fd98476300d06092a864886f70d0101050500307e310b3009060355040613024b52311430120603550408130b536f757468204b6f726561311330110603550407130a5375776f6e2043697479311c301a060355040a131353616d73756e6720436f72706f726174696f6e310b3009060355040b13024547311930170603550403131053616d73756e67204e46432043657274301e170d3132303631343036323830365a170d3339313033313036323830365a307e310b3009060355040613024b52311430120603550408130b536f757468204b6f726561311330110603550407130a5375776f6e2043697479311c301a060355040a131353616d73756e6720436f72706f726174696f6e310b3009060355040b13024547311930170603550403131053616d73756e67204e4643204365727430820122300d06092a864886f70d01010105000382010f003082010a0282010100a376fd8e06bcd2f000d646233c415a99253e880612becafc22c3a8c402670f7777a776f367da3756e31c8ac72a9801439236db9cc5cdf11509531648d9f82ed00e3145b42cbc3a5820ba9a8543c582444f79e045e170d59c238869c5159968fd8c2d20347e9edb65596c4404579b25b160d022ed24aa3debeff6c436236e76bfebd288ed0f30f97b1d9a5a509c3d8e3fa402ecf74b2d4be0cb70d5041310e18a3a29ec413badf7a538732dc67d687d01f9f3bb34e09a11590c84b818c04e1f2d0f81d9a1182af744f6094685e875b79b807f2a3b9364211b1f3c0b20c27a555f3b8818404a50eb055eb61552d711f6a7bb551cae4d2b6436f69d63ffdb2b64ad0203010001300d06092a864886f70d010105050003820101009933f9a7f1abe9bf1fd91207ecaabb603a405fbe9a7f68a59a0e3a0f07c901961613813745e05fa086d9fd784b8735145670910ffa36f2617bd4be1d24a9ea25c6c8705cdd27c1303b8ac13a3426a9208bfa8e4e703ceef85075214943959b2ca2ebb4a30ac39e4862512744976828d989e322afa27081e14ac6cf281f9e50a09f0d1b095c40b6dff9c54b22afce0ddc3680f05c70183f70876d5cb25c7845fe5970cc90aa71708870915a8acfcda87a2778847c9e384bea2f1739d5dd062d2c325a47b7a95680d4369d5b886345432cca9e891a19733cffd722fa88fafd21d1867cc5567865fff4ebea47fdb3d24fc31c4cc1f8cfd0c1fddb7998af2bc697bf" />
</resources>
Click to expand...
Click to collapse
Unfortunately it looks like the other files for NFC have also been updated and will not work by just replacing this file.
I do not have a fix for this either.
---------- Post added at 12:26 PM ---------- Previous post was at 12:15 PM ----------
And I just extracted the 4.1.2 file contents if you're interested. Maybe a smart guy will be able to figure out how to get it to work based on this info? I really miss my Google Wallet!
<?xml version="1.0" encoding="utf-8"?>
<resources xmlns:xliff="urnasis:names:tc:xliff:document:1.2">
<!-- Applications granted NFCEE access on user builds
See packages/apps/Nfc/etc/sample_nfcee_access.xml for full documentation.
-->
<!-- VZW CERT PROD Signature -->
<signer android:signature="3082035930820317A00302010202044F6C89C2300B06072A8648CE380403050030818F310B3009060355040613025553311330110603550408130A4E6577204A6572736579311630140603550407130D4261736B696E6720526964676531193017060355040A1310566572697A6F6E20576972656C65737331193017060355040B1310566572697A6F6E20576972656C657373311D301B06035504031314566572697A6F6E20576972656C657373204E4643301E170D3132303332333134333333385A170D3337303331373134333333385A30818F310B3009060355040613025553311330110603550408130A4E6577204A6572736579311630140603550407130D4261736B696E6720526964676531193017060355040A1310566572697A6F6E20576972656C65737331193017060355040B1310566572697A6F6E20576972656C657373311D301B06035504031314566572697A6F6E20576972656C657373204E4643308201B73082012C06072A8648CE3804013082011F02818100FD7F53811D75122952DF4A9C2EECE4E7F611B7523CEF4400C31E3F80B6512669455D402251FB593D8D58FABFC5F5BA30F6CB9B556CD7813B801D346FF26660B76B9950A5A49F9FE8047B1022C24FBBA9D7FEB7C61BF83B57E7C6A8A6150F04FB83F6D3C51EC3023554135A169132F675F3AE2B61D72AEFF22203199DD14801C70215009760508F15230BCCB292B982A2EB840BF0581CF502818100F7E1A085D69B3DDECBBCAB5C36B857B97994AFBBFA3AEA82F9574C0B3D0782675159578EBAD4594FE67107108180B449167123E84C281613B7CF09328CC8A6E13C167A8B547C8D28E0A3AE1E2BB3A675916EA37F0BFA213562F1FB627A01243BCCA4F1BEA8519089A883DFE15AE59F06928B665E807B552564014C3BFECF492A038184000281805C194C2A5092C4BF6BB1329B751B96AA4DA1CAC0232C0860C8D24B69A2A24822FD418010D3EB1F3D1EA15915499BF100976AB413DF95399D21ABB0F9022683415F44654A1F46226D23FF3C98417897F021A13E0875F786FEA5EAD61730C8A2286CE12F5701543C83D6179C440999C8527DA7C20D967D3CAE32933BA39A5AD395300B06072A8648CE3804030500032F00302C021428EE87B4B6B4BAB52E5460E8544D73540E862E06021464EB747DB43A8C3C53CFB0ED6B20DF7AF236149E" />
<!-- VZW ISIS PROD Signature -->
<signer android:signature="308203C2308202AAA00302010202044F6B9529300D06092A864886F70D01010505003081A2310B3009060355040613025553310B3009060355040813024E4A311630140603550407130D4261736B696E6720526964676531243022060355040A131B566572697A6F6E20436F6D6D756E69636174696F6E7320496E632E31193017060355040B1310566572697A6F6E20576972656C657373312D302B06035504031324566572697A6F6E20576972656C657373205369676E696E67204365727469666963617465301E170D3132303332323231313030315A170D3339303830383231313030315A3081A2310B3009060355040613025553310B3009060355040813024E4A311630140603550407130D4261736B696E6720526964676531243022060355040A131B566572697A6F6E20436F6D6D756E69636174696F6E7320496E632E31193017060355040B1310566572697A6F6E20576972656C657373312D302B06035504031324566572697A6F6E20576972656C657373205369676E696E6720436572746966696361746530820122300D06092A864886F70D01010105000382010F003082010A02820101009452BDCE78F36373D547CA2F6FE0939C239E423311F96A9A2CA253A7B21CBE6F82AF19A97E4B183270395D222423B3A3B9C1809D213E048EF4C63C3C8033C8AC7EB7943E95EF209D819EDEAA9AA41A4F8838054CEA83A19AFD49BE794DA3AFAAA4216320754D6161E691C64E2396DCA7DF0AFB030FFAAEBA96F1575385CB2EF967A09652D14CA2B6A9ECD58A8DFDDB16792A00E5427C7435CAC1714A3C4014B1ACEE14D6E2B220888DF392ACA253D731884E9D5D40214D36033206F07B8F48BD94FFB649F8CD84417AF9A7E4A344FBB3BEA0DA18DD55E2BBFE3A953A3D484CBB02E650FEE8CD2A74C6CCF506F382592BD64F03A10BC64BDAB4577C47E55C96850203010001300D06092A864886F70D01010505000382010100902BBEE97568A427EE75054C731BDADB5D045EB6557B771C06A4BE4D2253650D9E7CE04CBBF10516B23B6E7E03154CB181B421FC91527A9BDBBD7CF4025F4F808888A8A06C1C34C7637F423B56017FD7C002FD651C7C9BD1B73BCEBB31A0DD0870CDFD117BA119BC32324835E7A4E43FD2267B2FB6A326F7E978B7A856FB0E07C663750BC4ED0A11FB48A05AC0B01CA9B14E65496D5F3866617E6C4A63428ED68F56E87A8544CEE4FC1BBD07ED91D888089B2950397AA332883E3DB5C51D41EA31C76CE03B62AB61ABF17CF5E5145A85CE2DDE698D0E8038346DEE9BC59DCBED7CDF41D3CAD10A61B3357A380FC403F2FD1DCD955B2D5DD9D9DFABEFF8284103" />
</resources>
Click to expand...
Click to collapse
Ok i'm an idiot
So I'm an idiot. Looks like WarlockLord updated his thread about 4.1.2 ROMS...I haven't gotten mine working yet but will be sometime today. Here's a link to the thread.
http://forum.xda-developers.com/showthread.php?t=2031127
Hope that helps.
dprk said:
So I'm an idiot. Looks like WarlockLord updated his thread about 4.1.2 ROMS...I haven't gotten mine working yet but will be sometime today. Here's a link to the thread.
http://forum.xda-developers.com/showthread.php?t=2031127
Hope that helps.
Click to expand...
Click to collapse
Yep doesn't work still....
I made at least a small step towards figuring this out, as I ran into the same problem. I had the hacked version .13 running on my phone and updated to G Wallet .16 (real version). Once I found that wasn't working I reverted back to .13 but then ended up with Device Setup Failed (like you did). I tried everything and couldn't get it working again. I assume if you look in settings and "About" you'll see applet controller version is unknown.
I got G Wallet working again by creating a new Google account and associating wallet with that account. Then I added a card which added without issue. I'm wondering if for some reason Google locked out my primary account from Wallet once I updated to .16. I'm going to give them a call and see if it somehow got locked at the account level.
tithefug said:
Hello all,
I recently flashed CyanogenMod 10.1 on my Verizon Galaxy Note II. I previously came from a stock, deodexed ROM where Google Wallet worked. Apparently, sometime in the past week, Google Wallet no longer works on many devices (including the Galaxy Note II) and gives the following error:
Device set-up failed
Unable to set up Wallet for purchases
First, make sure you have a reliable Internet connection.
If the problem persists, restart your device and try again.​
The main reason I am putting this here is that it seems to have gotten buried within all the other Google Wallet threads with no replies. If a solution is found, I will update this post so it is easily found again.
Has anyone else had this issue? Has anyone gotten around this issue? Is my NFC secure element borked and Google Wallet will never work on my device again?
Thanks!
NOTES: My build.prop is set to a Galaxy Nexus. I have the Xposed module installed. I have tried an older version of the Wallet app which gives the same error. I've read somewhere that this might actually be a server-side constraint which would rule out anything we can do on the device.
Click to expand...
Click to collapse
johnhazelwood said:
I made at least a small step towards figuring this out, as I ran into the same problem. I had the hacked version .13 running on my phone and updated to G Wallet .16 (real version). Once I found that wasn't working I reverted back to .13 but then ended up with Device Setup Failed (like you did). I tried everything and couldn't get it working again. I assume if you look in settings and "About" you'll see applet controller version is unknown.
I got G Wallet working again by creating a new Google account and associating wallet with that account. Then I added a card which added without issue. I'm wondering if for some reason Google locked out my primary account from Wallet once I updated to .16. I'm going to give them a call and see if it somehow got locked at the account level.
Click to expand...
Click to collapse
Excellent. Keep us posted!
johnhazelwood said:
I made at least a small step towards figuring this out, as I ran into the same problem. I had the hacked version .13 running on my phone and updated to G Wallet .16 (real version). Once I found that wasn't working I reverted back to .13 but then ended up with Device Setup Failed (like you did). I tried everything and couldn't get it working again. I assume if you look in settings and "About" you'll see applet controller version is unknown.
I got G Wallet working again by creating a new Google account and associating wallet with that account. Then I added a card which added without issue. I'm wondering if for some reason Google locked out my primary account from Wallet once I updated to .16. I'm going to give them a call and see if it somehow got locked at the account level.
Click to expand...
Click to collapse
So I just tried this. I went to Google.com/wallet and deleted my devices that were associated. Changed my build.prop to the nexus then flashed the zip file with the libs and deleted old wallet and installed from market and I still get the same no Internet connection error. I've heard that people who have swapped their phones out who were having this problem were able to get it working no problem with a new device :/. I believe I'll have to get a new device as it looks like my secure element is broken.
{
"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"
}
Doin' big thangs from my Note Deuce

Google Wallet works on MJ7

I downloaded Google wallet on the play store just to see if it would work. To my surprise I found that it does work! I'm on stock 4.3 or MJ7
somedude011 said:
I downloaded Google wallet on the play store just to see if it would work. To my surprise I found that it does work! I'm on stock 4.3 or MJ7
Click to expand...
Click to collapse
can't use the pay function can you?
Josebori said:
can't use the pay function can you?
Click to expand...
Click to collapse
I don't know as I haven't tried this yet
Should look like this if it's working!
Sent from my SCH-I545 using XDA Premium 4 mobile app
Tap to pay doesn't work for me, just tested it on mine running MJ7 rooted with SuperSU preserve from MI1.
I wish junior members would spend more time searching before they post.
Verizon does not allow "Tap to Pay" to work. The function is blocked.
You need to root and go through one of the methods to get it to work.
I have Version 2.0-R1333-v14... running on MI1.
To get it to work, I used a combination of methods from two different threads.
I used the wallet installer with the exposed framework to remove the region and root check.
I used the instruction from this thread -> http://forum.xda-developers.com/showthread.php?t=2303325&highlight=wallet
And got the exposed wallet hack installed. At step 12.
I took the zip from this thread -> http://forum.xda-developers.com/showthread.php?t=2454971&highlight=wallet
I manually installed all the files by following the script in the zip file.
Then I followed #13 on.
I will post more detailed instructions when I get a chance.
You can get 2.x to work it's just a pain.
Almost there
I am on stock MJ7 with the root that the member "open1your1eyes0" posted. I thought I would play with Google Wallet because it updated today for me. I have done the build.prop name change game several time with the "unsecured element" message every time since rooting, even with frameworks. I edited the build.prop again, restarted w/framework mod checked, installed Google Wallet off the play store. It worked for the most part without any issue and the tap-n-pay let me set it up. I ran into issues after it let me turn on tap-n-pay. I get the message, "Tap and pay setup failed- Unable to set-up Wallet for purchases. Wallet is having trouble setting up tap and pay. Please try again. This may take a few minutes". Under that message it shows my debit card and a "change tap and pay settings". and it as "Tap and pay Unavailable (NfcPaymentSetupFailure: 1) in the "About" menu. Not sure how to fix this but it is way further than I have ever gotten with Wallet.
sparkk said:
I am on stock MJ7 with the root that the member "open1your1eyes0" posted. I thought I would play with Google Wallet because it updated today for me. I have done the build.prop name change game several time with the "unsecured element" message every time since rooting, even with frameworks. I edited the build.prop again, restarted w/framework mod checked, installed Google Wallet off the play store. It worked for the most part without any issue and the tap-n-pay let me set it up. I ran into issues after it let me turn on tap-n-pay. I get the message, "Tap and pay setup failed- Unable to set-up Wallet for purchases. Wallet is having trouble setting up tap and pay. Please try again. This may take a few minutes". Under that message it shows my debit card and a "change tap and pay settings". and it as "Tap and pay Unavailable (NfcPaymentSetupFailure: 1) in the "About" menu. Not sure how to fix this but it is way further than I have ever gotten with Wallet.
Click to expand...
Click to collapse
I have searched high and low and tried everything and still found no work around
somedude011 said:
I downloaded Google wallet on the play store just to see if it would work. To my surprise I found that it does work! I'm on stock 4.3 or MJ7
Click to expand...
Click to collapse
DOES NOT WORK for tap & pay, which is what we care about. Please update your post so others don't get their hopes up.
I got Wallet to work, including tap and pay, on 4.3 using this:
http://forum.xda-developers.com/showthread.php?t=2540196
timeToy said:
I got Wallet to work, including tap and pay, on 4.3 using this:
http://forum.xda-developers.com/showthread.php?t=2540196
Click to expand...
Click to collapse
Wish i still had recovery
webmastir said:
Wish i still had recovery
Click to expand...
Click to collapse
You don't need recovery!
Follow the same principle as described in this post, but with the 4.3 files
http://forum.xda-developers.com/showpost.php?p=47457381&postcount=251
timeToy said:
I got Wallet to work, including tap and pay, on 4.3 using this:
http://forum.xda-developers.com/showthread.php?t=2540196
Click to expand...
Click to collapse
That's not wallet for MJ7. It's wallet for deodexed 4.3.
If you know how to make Wallet work with tap-and-pay on MJ7 (which is what this thread is about) then several people would be happy to hear about it.
Why would I want deodexed 4.3? I don't mind losing a little space on my phone that I can easily get back with an sd card.
Sent from my SCH-I545 using Tapatalk
That screwed my phone up and had to restore to factory and re root my phone. It kept lagging up and would force close apps
Sent from my SCH-I545 using xda app-developers app
Chris-M. said:
That screwed my phone up and had to restore to factory and re root my phone. It kept lagging up and would force close apps
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Happened to me multiple times
Sent from my SCH-I545 using Tapatalk
What's wrong with isis?
gaer01 said:
What's wrong with isis?
Click to expand...
Click to collapse
It only works with AmEx.
k1mu said:
That's not wallet for MJ7. It's wallet for deodexed 4.3.
If you know how to make Wallet work with tap-and-pay on MJ7 (which is what this thread is about) then several people would be happy to hear about it.
Click to expand...
Click to collapse
It's working just fine on Odexed MJ7
Working fine on deodexed 4.3
Sent from my SCH-I545 using XDA Premium 4 mobile app

[ROM][5.1/6.0][CM12.1/13][UBERTC][OPTIMIZED] Unofficial Build for i605

Welcome to my unofficial build for cm-12.1/13.0
Disclaimer: I take no responsibility for bad things that happen as a result of flashing this.
My kernel source is HERE.
Uber tool chain source is HERE.
[ROM]
Download Latest (credits to @c0urier)
[GAPPS]
Download
[PATCHES]
fast charge + boeffla sound
Sample faster GPS fix (replace country SG to your own)
Clean installation is encouraged if come from different roms or android versions...
Thanks cm team for the amazing ROM.
Special thanks to: @DerTeufel1980 , @sbrissen , @rogersb11 , @TheBr0ken , @DreamFX , @frankie ...
Thanks Wilson Downloading Now.
thank you sir.
Wanted to confirm SMS is fixed. Noticed mute button is greyed out when calling so I can't use mute.
Still testing other functions.
Going to go for it. Thank you so much.
"Chance Favors the Prepared"
nm
Really nice so far. Theme engine is flawless so far and opened browser up for first time and it logged me right in almost instantly. Have had issues with that since first lollipop build went out.
I can't use any third party browser all the ones I try won't open they fail with weird errors.
Testing update
Everything seems pretty solid for a first build. I went from the 3-25 build of 5.0.2. To Pac roms the last couple days. To clean slate and fresh install this morning. Only thing i have is still no Netflix. Have tried uninstalling and a reboot. Install and a couple reboots. And there is no mute on calls. Which by no means are deal breakers for me. Also GPS is a little off however finds location pretty quickly. I use my LTE connection for all my net use. I average around 250-350gb per month so a daily driver is a must for me. Thanks for your hard work on this Wilson.
On a side note. I don't see the thanks button anymore. Am i missing something.
momule said:
Everything seems pretty solid for a first build. I went from the 3-25 build of 5.0.2. To Pac roms the last couple days. To clean slate and fresh install this morning. Only thing i have is still no Netflix. Have tried uninstalling and a reboot. Install and a couple reboots. And there is no mute on calls. Which by no means are deal breakers for me. Also GPS is a little off however finds location pretty quickly. I use my LTE connection for all my net use. I average around 250-350gb per month so a daily driver is a must for me. Thanks for your hard work on this Wilson.
On a side note. I don't see the thanks button anymore. Am i missing something.
Click to expand...
Click to collapse
Did you try another reboot after installing Netflix?
Check this file /data/data/com.netflix.mediaclient/shared_prefs/nfxpref.xml:
Did you see this line before "</map>"?
<int name="nflx_player_type" value="10" />
If not, manually add this line...
Sent from my GT-N7105 using XDA Free mobile app
Chrome FCs. Other than that, awesome ROM!
Sent from my SCH-I605 using Tapatalk
DreamFX said:
I can't use any third party browser all the ones I try won't open they fail with weird errors.
Click to expand...
Click to collapse
Fixed...
Wait for next build.
{
"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"
}
CHANGiism said:
Chrome FCs. Other than that, awesome ROM!
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
I think it is all related...
I just fixed a libc issue...causes chrome could not start up...
Will be loaded in next build.
Tried multiple reboots after both uninstall and re install. I get the spinning wheel when opened and after selecting sign out the same effect. it says check time and date
Im am a rookie. How do i check for the script. a file explorer ?
wilson3q said:
Did you try another reboot after installing Netflix?
Check this file /data/data/com.netflix.mediaclient/shared_prefs/nfxpref.xml:
Did you see this line before "</map>"?
<int name="nflx_player_type" value="10" />
If not, manually add this line...
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
momule said:
Tried multiple reboots after both uninstall and re install. I get the spinning wheel when opened and after selecting sign out the same effect. it says check time and date
Im am a rookie. How do i check for the script. a file explorer ?
Click to expand...
Click to collapse
Default CM file manager will do...change access mode to root in settings...
You can get a logcat for me to trace...It could be due to the same libc issue. Sorry no netflix in my country.
Other than Chrome force-closing, this seems to running well for me. My last week or two of 5.0 nightlies gave me a lot of trouble connecting to my home wifi, but this is not an issue here. I did wipe clean for this, whereas I was dirty flashing 5.0, so maybe that has something to do with it.
EDIT: Not sure if this would be ROM related, but I do not have an option within either of my Google accounts to synchronize my calendar. I can synchronize Gmail, App Data, Contacts, People, and Fit data, but that's all. I do not even have a greyed out option for calendar; it's simply not there.
savaytse66 said:
Other than Chrome force-closing, this seems to running well for me. My last week or two of 5.0 nightlies gave me a lot of trouble connecting to my home wifi, but this is not an issue here. I did wipe clean for this, whereas I was dirty flashing 5.0, so maybe that has something to do with it.
EDIT: Not sure if this would be ROM related, but I do not have an option within either of my Google accounts to synchronize my calendar. I can synchronize Gmail, App Data, Contacts, People, and Fit data, but that's all. I do not even have a greyed out option for calendar; it's simply not there.
Click to expand...
Click to collapse
Had same issue but I flashed a different gapp package and it magically came back.
New build up:
Fixed some app crashed issue...
Latest cm changes...
Sent from my GT-N7105 using XDA Free mobile app
wilson3q said:
New build up:
Fixed some app crashed issue...
Latest cm changes...
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Confirmed. 4/2 build is flawless. Everything works. FCS are gone. Other than missing MUTE in call everything is pristine.
Thank you!
I'm Going to have to give this another go. I reverted back to Alliance build 30 because of not receiving calls all of the time on a lot of the lollipop builds. And it is hit or miss as to weather I would receive a call and not rom specific.
"Chance Favors the Prepared"

XDA app will not open

I have a Verizon LG v30 and just the other day, I installed the just updated us99830b rom coming from the vs996 30b rom (I think). It has been a little while since I've tried a different rom.
I did a clean install when I flashed it. After flashing, I installed my apps by using the Titanium Backup app. I installed XDA using tibu, restoring both the app and data. When I tried to open the app, it would not open. I get the warning that the app won't open.
{
"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"
}
I have searched on here and Google, but, can not get the app to open.
I've deleted and installed the xda app multiple times from the play store. I've deleted cache, deleted its data, checked all permissions for it. I've since done a dirty flash of the rom, but, still cannot get XDA to open.
I haven't tried too many other apps, but did have one other one that did the same thing. I can't fermenter which one it was, if I still have it, or not ().
The only way I can get into this app is to open a link to it from an email notification on a watched thread or an already open window on my browser.
So, I don't know if it is rom related or some unknown setting I've inadvertently set.
Any one have any ideas on how to get this app to open correctly?
Thx
Sometimes it helps to install either:
A) An older version of the app which you can find online somewhere
or
B) The same app from a different source, like an alternative store
ldeveraux said:
Sometimes it helps to install either:
A) An older version of the app which you can find online somewhere
or
B) The same app from a different source, like an alternative store
Click to expand...
Click to collapse
Well, I did find an older source, Sept, 2020, I think.
ldeveraux said:
Sometimes it helps to install either:
A) An older version of the app which you can find online somewhere
or
B) The same app from a different source, like an alternative store
Click to expand...
Click to collapse
Well, I did download and try an older version, Sept, 2020, I think. Same problem with just a little different warning (fail to connect to the forum, check with an administrator). This added an icon to my home page, just like the new xda app does, and, just like it, it failed to open. I'm still trying to figure it out, but...
Thx, for the help.
gimpy1 said:
Well, I did find an older source, Sept, 2020, I think.
Well, I did download and try an older version, Sept, 2020, I think. Same problem with just a little different warning (fail to connect to the forum, check with an administrator). This added an icon to my home page, just like the new xda app does, and, just like it, it failed to open. I'm still trying to figure it out, but...
Thx, for the help.
Click to expand...
Click to collapse
In addition to the xda app, I went to my home screens and tried opening the other apps (25 or 30 or so). All opened fine, except for 1: Allstate Insurance, 2: American Airlines, and 3: YouTube Vanced. They all closed on me like the xda app does. Their icons are on the screen, but the app won't open.
Sorry wish I could help. That happens with different apps on literally every phone I've owned. I know a wipe will fix it, but that's a crazy solution. Maybe there are remnant folders for reasons? You could try looking for a really deep app uninstaller. Not sure how effective it would be haven't used one in years.
XDA App is totally different since Dec 2020, older versions will not work because the forum software changed. If you try the latest from the Play store it should work. Are you saying you are getting a crash from there? Again, do a fresh play store install and not from a backup.
gimpy1 said:
In addition to the xda app, I went to my home screens and tried opening the other apps (25 or 30 or so). All opened fine, except for 1: Allstate Insurance, 2: American Airlines, and 3: YouTube Vanced. They all closed on me like the xda app does. Their icons are on the screen, but the app won't open.
Click to expand...
Click to collapse
bitpushr said:
XDA App is totally different since Dec 2020, older versions will not work because the forum software changed. If you try the latest from the Play store it should work. Are you saying you are getting a crash from there? Again, do a fresh play store install and not from a backup.
Click to expand...
Click to collapse
I have just uninstalled all four apps, and reinstalled them. The other three opened up and appears to be working fine, although my All-State app did open and close a couple of minutes later. I reinstalled it, but it seems to be working fine now.
The xda app still will not open, even after a clean install from the Play store. I hand probably tried that a dozen or so times the last 3 days. It just will not open.
I install it and click open from the Playstore sight. It goes to the xda icon on my home screen. I click on it, and get the error message every time.
I changed launchers to my old reliable Nova, and it still does not work .
gimpy1 said:
I have just uninstalled all four apps, and reinstalled them. The other three opened up and appears to be working fine, although my All-State app did open and close a couple of minutes later. I reinstalled it, but it seems to be working fine now.
The xda app still will not open, even after a clean install from the Play store. I hand probably tried that a dozen or so times the last 3 days. It just will not open.
I install it and click open from the Playstore sight. It goes to the xda icon on my home screen. I click on it, and get the error message every time.
I changed launchers to my old reliable Nova, and it still does not work .
Click to expand...
Click to collapse
Can you post your logcat so we can see/fix the error?
I have not done cat logs before. I have been trying all afternoon and evening to get you one and have attached a zip of a cat log (I think) from a downloaded app called "matlog".
Please let me know if this was done correctly in the accompanying attachment. I'm not sure.
Thx
Update
I was not able to ever get the xda app to open tapping on its icon. I even did another clean install. The second install would not even let me download the app from the play store. This was installing the new updated version of the US99830b Rom just posted a few days ago. I used that Rom for about 4 days with no problems (still don't know if the problem with xda is associated with that Rom).
What I have done just a few minutes ago was to delete/uninstall that Rom. I have now installed, and am currently using the Verizon vs99630c/debloated rom. I have not reset up my phone, yet, but did download the xda app from the play store. The xda app is now working properly. I click on the icon and it opens right up.
They only thing now (not related to the xda app, I don't think), is that when I check in the phone settings under about phone and hardware, it shows it to be US998, not VS996 (which is what I'm think I'm on--vs99630c/debloated Rom.
I will finish setting my phone up and see if any problems develop. Hopefully not.
Tnx, for your help.
gimpy1 said:
They only thing now (not related to the xda app, I don't think), is that when I check in the phone settings under about phone and hardware, it shows it to be US998, not VS996 (which is what I'm think I'm on--vs99630c/debloated Rom.
I will finish setting my phone up and see if any problems develop. Hopefully not.
Tnx, for your help.
Click to expand...
Click to collapse
I believe that debloated VS996 ROMs was not made by JohnFawkes, but someone else and they combined US998/VS996 stuff together. JohnFawkes and him got into it because as you pointed out it would show it's a US998. It was an easy workaround vs the specific tools/procedures JohnFawkes and Seadersn used for their TWRP-flashable zips.
I am currently on the vs99639c debloated rom now. It runs very nice.
The US99830b rom (updated one) also ran very nice. Really the only problem I had with it was not being able to open up xda from the Home page icon.
It also contained a lot of bloat on it. But, I got around most of that, otherwise, no problem with it.
On a personal note, I hope you are doing well with your new family.
Where did you visit in S. A.? I plan on taking a trip later this year to Paraguay.
gimpy1 said:
I am currently on the vs99639c debloated rom now. It runs very nice.
The US99830b rom (updated one) also ran very nice. Really the only problem I had with it was not being able to open up xda from the Home page icon.
It also contained a lot of bloat on it. But, I got around most of that, otherwise, no problem with it.
On a personal note, I hope you are doing well with your new family.
Where did you visit in S. A.? I plan on taking a trip later this year to Paraguay.
Click to expand...
Click to collapse
Brazil.

Categories

Resources