Hey all,
Yes, first post, and yes, I did search for a solution to my problem, but didn't see this one, and didn't like those.
Was having trouble with Google Wallet on CM 10.1. I went to stock (from backup) and pulled that build.prop file for comparison to the CM 10.1 build.prop. There were some discrepancies and I changed the values to what is below.
Code:
ro.product.brand=htc
ro.product.name=m7wls
ro.product.device=m7wls
ro.product.name=HTCONE
Removed this line as well.
Code:
ro.product.locale.region=US
Saved, then rebooted the phone. Installed Google Wallet. Ran it. Everything worked as expected (says "Unsupported Device" at the top, but I assume its due to being rooted).
I searched for this solution but could not find it. If I posted out of error, please forgive me, I usually only lurk on here.
Veranor said:
Hey all,
Yes, first post, and yes, I did search for a solution to my problem, but didn't see this one, and didn't like those.
Was having trouble with Google Wallet on CM 10.1. I went to stock (from backup) and pulled that build.prop file for comparison to the CM 10.1 build.prop. There were some discrepancies and I changed the values to what is below.
Code:
ro.product.brand=htc
ro.product.name=m7wls
ro.product.device=m7wls
ro.product.name=HTCONE
Removed this line as well.
Code:
ro.product.locale.region=US
Saved, then rebooted the phone. Installed Google Wallet. Ran it. Everything worked as expected (says "Unsupported Device" at the top, but I assume its due to being rooted).
I searched for this solution but could not find it. If I posted out of error, please forgive me, I usually only lurk on here.
Click to expand...
Click to collapse
I can confirm that this line alone works:
Code:
ro.product.device=m7wls
I myself recieve the error "Not Supported"
No dice on this end either.
For the record, is the Wallet you are using from the Play Store or is it some third party cracked one?
rougegoat said:
No dice on this end either.
For the record, is the Wallet you are using from the Play Store or is it some third party cracked one?
Click to expand...
Click to collapse
I'm fairly certain mine is from the Play store. I'm not 100% on that though.
rougegoat said:
No dice on this end either.
For the record, is the Wallet you are using from the Play Store or is it some third party cracked one?
Click to expand...
Click to collapse
Wallet from the play store. I went through this twice, then updated to the latest nightly and saw that it broke, so I force closed it, deleted cache, updated build.prop, rebooted, and i was able to initialize wallet again just fine.
Veranor said:
Wallet from the play store. I went through this twice, then updated to the latest nightly and saw that it broke, so I force closed it, deleted cache, updated build.prop, rebooted, and i was able to initialize wallet again just fine.
Click to expand...
Click to collapse
Followed to a T on the most recent nightly, still no dice.
rougegoat said:
Followed to a T on the most recent nightly, still no dice.
Click to expand...
Click to collapse
That's bizarre. I can even go back to the build.prop, change the settings back, reboot, and my wallet breaks. I'll double-check the settings to make sure there wasn't something I missed here.
If you want to kill the unsupported app banner, use MoDaCo Toolkit. I didn't see this issue at all though, so something seems up. You could try the aforementioned toolkit to download an installer and see if that works either.
I've redone this process, only doing one item at a time. Wallet functions when you change the following value.
I tested this by wiping and flushing cache thru recovery, then installing latest nightly.
After that finished, I installed Wallet, verified that it did not work.
Opened build.prop and changed the following property. Force closed Wallet, flushed data. Rebooted.
ro.product.model
from "One" to "HTCONE"
Opened Wallet - completed setup.
The m7spr is supposed to be m7wls though - not sure why I added those, thought maybe they were linked.
This works. Just got some mc Donald's.
Sent from my HTCONE using Tapatalk 4 Beta
As of the nightly today, this no longer works. :-/ Worked yesterday though.
Veranor said:
I've redone this process, only doing one item at a time. Wallet functions when you change the following value.
I tested this by wiping and flushing cache thru recovery, then installing latest nightly.
After that finished, I installed Wallet, verified that it did not work.
Opened build.prop and changed the following property. Force closed Wallet, flushed data. Rebooted.
ro.product.model
from "One" to "HTCONE"
Opened Wallet - completed setup.
The m7spr is supposed to be m7wls though - not sure why I added those, thought maybe they were linked.
Click to expand...
Click to collapse
Here is what I did:
Update to newest nightly
Use recovery to clear cache, dalvik cache, reboot
Confirm Wallet does not work
Force closed Wallet, cleared its cache, data
Edit build prop from "ro.product.model=One" to "ro.product.model=HTCONE"
clear cache, dalvik cache, reboot
Confirm that Wallet still does not work
If you flash another nightly you have to do the build prop edit AGAIN....OK. The flash overwrites it.
Sent from my One using Tapatalk 4 Beta
david279 said:
If you flash another nightly you have to do the build prop edit AGAIN....OK. The flash overwrites it.
Sent from my One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Assuming you are talking to me, I am quite well aware. Back to Xposed I go I guess.
david279 said:
If you flash another nightly you have to do the build prop edit AGAIN....OK. The flash overwrites it.
Sent from my One using Tapatalk 4 Beta
Click to expand...
Click to collapse
True, but if all that it takes to fix it is one line change in the build.prop, that can be reported to the CM guys and fixed in future builds.
Tell @kushdeck
Sent from my One using Tapatalk 4 Beta
david279 said:
Tell @kushdeck
Sent from my One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Brought it up in the CM10.1 thread already. It probably isn't being taken too seriously though since it apparently does not work every time or for every device.
Go on IRC beware though it's a hard place.
Sent from my One using Tapatalk 4 Beta
david279 said:
Go on IRC beware though it's a hard place.
Sent from my One using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm not one to report a fix there that I have confirmed does not work all the time. Feel free to report it yourself.
Related
Hi:
My N7 in San Francisco and my sister's N7 in New Mexico can no longer download from the PlayStore. We get the following error:
Update for xxx could not be downloaded due to an error. Error retrieving information from server. [RPC:S-5:AEC-0])
Any ideas?
Thanks,
Tom
Same problem in Germany with Galaxy Nexus and Android 4.1.2!
I think it's a global Google Play problem.
Found a lot of this posts in different forums today.
thenrik said:
Hi:
My N7 in San Francisco and my sister's N7 in New Mexico can no longer download from the PlayStore. We get the following error:
Update for xxx could not be downloaded due to an error. Error retrieving information from server. [RPC:S-5:AEC-0])
Any ideas?
Thanks,
Tom
Click to expand...
Click to collapse
Do you have the 3.9.17 version? Open settings/apps/downloaded and open Google play and check version. While there clear data, force stop and reboot. Did you both do ota update, or did you both flash the update? We have 2 N7's, mine rooted and both of ours got the Ota at the same time. Both play stores work perfectly. Heck I didn't even loose root on mine.
leroybrute said:
Do you have the 3.9.17 version? Open settings/apps/downloaded and open Google play and check version. While there clear data, force stop and reboot. Did you both do ota update, or did you both flash the update? We have 2 N7's, mine rooted and both of ours got the Ota at the same time. Both play stores work perfectly. Heck I didn't even loose root on mine.
Click to expand...
Click to collapse
Hi I cleared data and rebooted. But it didn't solve the problem.
Galaxy Nexus
Android 4.1.2
Play: 3.9.16
leroybrute said:
Do you have the 3.9.17 version? Open settings/apps/downloaded and open Google play and check version. While there clear data, force stop and reboot. Did you both do ota update, or did you both flash the update? We have 2 N7's, mine rooted and both of ours got the Ota at the same time. Both play stores work perfectly. Heck I didn't even loose root on mine.
Click to expand...
Click to collapse
I have version 3.9.16. Tried to clear data, stopped and rebooted the phone. After that Google Play asked for terms agreement but the error still exists.
I posted this in another similar thread...
That commonly happens for stopping and clearing data of Google Framework services. Also break Push Notifications in some cases.
Fixes:
1. Clear data and cache of Play Store or
2. Remove and re add Google account and worst scenario do a
3. Factory Reset (then you can restore backed up apps but without data to minimize further issues.)
Sent from my SPH-D710/Nexus7 using Tapatalk v2.4.1
Omar04 said:
I posted this in another similar thread...
That commonly happens for stopping and clearing data of Google Framework services. Also break Push Notifications in some cases.
Fixes:
1. Clear data and cache of Play Store or
2. Remove and re add Google account and worst scenario do a
3. Factory Reset (then you can restore backed up apps but without data to minimize further issues.)
Sent from my SPH-D710/Nexus7 using Tapatalk v2.4.1
Click to expand...
Click to collapse
Thanks! Worked without factory reset
Stinsonmaster said:
Thanks! Worked without factory reset
Click to expand...
Click to collapse
Yeah factory reset is for worst case scenario. Glad you resolve the issue. :beer:
Sent from my SPH-D710/Nexus7 using Tapatalk v2.4.1
How do I go about removing and adding my account again?
Sent from my Nexus 7 using Tapatalk 2
hic9582 said:
How do I go about removing and adding my account again?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Go into setting accounts.. click on google account. click on the ... for settings.. Click delete account...
Reboot device.. Set account back up. On boot it should ask you to set up google account. If not go to settings accounts add account...
hic9582 said:
How do I go about removing and adding my account again?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Go to Settings. Underneath account hit Google. Tap your email address. Go into the menu (three small squares in top right corner) and tap 'Remove account'.
*Sent from N7*
just Clearing the data of market place and force close it didnt do the trick
so i removed google account, rebooted and added google account again, it worked! :good: without factory reset
I am also having a similar issue, however, i have tried removing and re-adding my daughters gmail account, i have cleared the cache and force stopped the play store and i have also done a factory reset. While doing the factory reset does initially resolve the problem, shortly after the second or third download i get an error message advising that it could not verify my account details, it then comes back with the 'error retrieving information from server[RPC:S-5:AEC-0]'. What i have noticed is that the device is not registering itself against the gmail account as when i sign in from my laptop it does not show the device in the list when trying to download an app.
device - A13MID
Android - 4.0.4
baseband - 1.5
kernel - 3.0.8+
any other information you want i can get but id appreciate any help i can get as my daughter is getting kinda upset she cannot install any apps on her new tablet.
(last resort would be to return the device but that will cost me greatly as it was shipped from china (was ordered through amazon).
logansfolly said:
I am also having a similar issue, however, i have tried removing and re-adding my daughters gmail account, i have cleared the cache and force stopped the play store and i have also done a factory reset. While doing the factory reset does initially resolve the problem, shortly after the second or third download i get an error message advising that it could not verify my account details, it then comes back with the 'error retrieving information from server[RPC:S-5:AEC-0]'. What i have noticed is that the device is not registering itself against the gmail account as when i sign in from my laptop it does not show the device in the list when trying to download an app.
device - A13MID
Android - 4.0.4
baseband - 1.5
kernel - 3.0.8+
any other information you want i can get but id appreciate any help i can get as my daughter is getting kinda upset she cannot install any apps on her new tablet.
(last resort would be to return the device but that will cost me greatly as it was shipped from china (was ordered through amazon).
Click to expand...
Click to collapse
Since you were comfortable wiping the device I would recommend downloading the fastboot files and manually flashing them through the boot loader. Go to fresh 4.2.
Now there is a commonality between some of these stories I've heard. How old is your daughter listed on the account? You don't have to post it lol I'm not a creeper, but if she is underage I wonder if it causes issues... Just some random thoughts.
Is your N7 GSM? Because it shouldnt have a baseband
Sent from my Nexus 7 using Tapatalk HD
Great Solution
erica_renee said:
Go into setting accounts.. click on google account. click on the ... for settings.. Click delete account...
Reboot device.. Set account back up. On boot it should ask you to set up google account. If not go to settings accounts add account...
Click to expand...
Click to collapse
Thanks, this worked for me. Yet, do I have to look forward to continueing to have to do this?
http://d-h.st/tTn
Flash after the ROM giving you the error.
I'm assuming it only happens to Sprint users, so it also includes the fixed Sprint APN.
Enjoy.
Works great. Thanks.
I don't think a carrier would have anything to do with it at all since this is the Nexus 5, and carriers have absolutely nothing to do with any aspect of the device, both software and hardware.
It does have a lot to do with it actually.
Great fix, seriously a life saver I've been pulling my hair out trying to figure it out. The closest I got was to just delete the apk from the rom if possible before flash.
Thanks so much
Going to try this tonight. Been pulling out my hair trying to figure this out with some roms
Well, whatever it does it worked. I flashed this after installing the AICP 5.0 nightlies that were giving me update device crashes. They no longer occur... thanks
@Lethargy you make me lol in every thread, brighten my days. Hats off to you ??
At least for me, while this zip does make the error message go away, it's not actually installing a working replacement. If you use a file manager and go to /system/app/OmaDmClient and try to install the apk within, you will get the standard install confirmation, not the one for updating existing software (which it should do if the app was already correctly working). So while this is technically a "fix", it's the same as just deleting the buggy apk.
Sent from my Nexus 5 using XDA Free mobile app
bray424 said:
At least for me, while this zip does make the error message go away, it's not actually installing a working replacement. If you use a file manager and go to /system/app/OmaDmClient and try to install the apk within, you will get the standard install confirmation, not the one for updating existing software (which it should do if the app was already correctly working). So while this is technically a "fix", it's the same as just deleting the buggy apk.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thinking I skipped setting perms in a rush. Either way, it shouldn't be needed for too long. I flashed to 5.0.1 without needing anything besides the fixed APN. I do see an issue with prl/profile update however.
killersloth said:
Thinking I skipped setting perms in a rush. Either way, it shouldn't be needed for too long. I flashed to 5.0.1 without needing anything besides the fixed APN. I do see an issue with prl/profile update however.
Click to expand...
Click to collapse
You a sprint user by chance?
crazyeats said:
You a sprint user by chance?
Click to expand...
Click to collapse
Yep
really need this file, can anyone please upload valid zip at legit host.
update: got it, not sure whether dev-host was backup or using different pc did the trick!
I'm having this same problem on my L720...
I assume this file wont work...
Is there a way to fix on my CM12 install without reflashing?
gbean009 said:
I'm having this same problem on my L720...
I assume this file wont work...
Is there a way to fix on my CM12 install without reflashing?
Click to expand...
Click to collapse
It should work, all it does is replace an apk and insert apns to /etc
Tried on my LG G2 LS980 with FreedomPop, but it didn't fix the Update Device error. Any clue for the failure?
This "fix" is crap. Don't flash random stuff to your device. No documentation? No source for the included APK?
Hello XDA geniuses; If anyone can figure out and provide me some suggestions, its here!
So, I've been running Benzo ROM for the last few months, its perfect for me. I've tried others but have settled on it. In the last update, it required a clean flash, which I did. TWRP -> Advanced Wipe -> System, Data, Dalvik and Cache. Never had an issue before, but in this build I can't use Google Wallet or Tap and Pay.
When I go to start either of those 2 apps, they just sit at the initial screens. Thats all, they just sit there.
I've made sure I'm signed into my account, no ad blocking or security issues I can see. I've wiped and re-flashed 4 times. Made sure I have the right ROM and gapps. I've uninstalled and reinstalled Wallet a bunch of times.
The dev did say in this build he; "AOSP Webview to Google's Webview", hence the clean flash.
Nothing I've tried yet has made any difference. I did a logcat, but did not see anything notable.
And, yes of course I posted this in the ROM forum, unfortunately I've not received much response and figured I would ask in the Help section.
Thanks in advance and if you have any suggestions at all, please let me know. I use Wallet daily and I hate to move off this rom, but I have been trying others and I do rely on Wallet at this point.
jackpollard said:
Hello XDA geniuses; If anyone can figure out and provide me some suggestions, its here!
So, I've been running Benzo ROM for the last few months, its perfect for me. I've tried others but have settled on it. In the last update, it required a clean flash, which I did. TWRP -> Advanced Wipe -> System, Data, Dalvik and Cache. Never had an issue before, but in this build I can't use Google Wallet or Tap and Pay.
When I go to start either of those 2 apps, they just sit at the initial screens. Thats all, they just sit there.
I've made sure I'm signed into my account, no ad blocking or security issues I can see. I've wiped and re-flashed 4 times. Made sure I have the right ROM and gapps. I've uninstalled and reinstalled Wallet a bunch of times.
The dev did say in this build he; "AOSP Webview to Google's Webview", hence the clean flash.
Nothing I've tried yet has made any difference. I did a logcat, but did not see anything notable.
And, yes of course I posted this in the ROM forum, unfortunately I've not received much response and figured I would ask in the Help section.
Thanks in advance and if you have any suggestions at all, please let me know. I use Wallet daily and I hate to move off this rom, but I have been trying others and I do rely on Wallet at this point.
Click to expand...
Click to collapse
Have you tried going into settings>apps>all and force stopping and clearing data?
i just got my n6 yesterday and installed stock android m preview. so far evreything seems to work fine, but my venmo app just shows a blue screen. ive tried force closing and clearing cache/data.
strangeeeeeeeeeeeee
Evolution_Tech said:
Have you tried going into settings>apps>all and force stopping and clearing data?
Click to expand...
Click to collapse
Hey Evolution_Tech, super appreciate the feedback! Yes, I tried it again, just to make double sure. I force stopped Wallet, even went into Show Cached Process and killed it. Same thing for both T&P and Wallet; I bring up the app, it goes to the 1st screen and boom just sits. In T&P I cant even press the Display link. So freaking odd.
Again, Thanks!!
jackpollard said:
Hey Evolution_Tech, super appreciate the feedback! Yes, I tried it again, just to make double sure. I force stopped Wallet, even went into Show Cached Process and killed it. Same thing for both T&P and Wallet; I bring up the app, it goes to the 1st screen and boom just sits. In T&P I cant even press the Display link. So freaking odd.
Again, Thanks!!
Click to expand...
Click to collapse
You could try logging out of your Google account completely then logging back in.
Any update on this?
Sent from my Nexus 6 using Tapatalk
nlua said:
Any update on this?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hello; Here is what worked for me, but I have to preface it with make sure you do a good backup. When the Rom I use asked for a full refresh including wiping data, is when I had the issue. I eventually tried it with not wiping data and that's what worked. I think wallet keeps some persistent data there and when you wipe it out, it gets stuck. Good luck.
I will try and make this my last update; I finally got wallet to work with a complete wipe, including data.
I used dev options and found the package in data/data for wallet, its com.google.android.apps.walletnfcrel
I copied com.google.android.apps.walletnfcrel from data/data into a folder on my sd card. Then I did my clean wipe. I installed wallet and let it build the structure. Then when I tried it, it would hang. I stopped it, then I copied all the files back in from my backup and it worked. I overwrote the files and used es file explorer that had root.
Make sure, as always you have a good backup.
If you have any questions just give me a shout.
I installed SlimLP 0.14 recently with TWRP and used this version of Gapps - Slim_mini_gapps.BETA.5.1.build.0.x-20151228.zip
Throughout using the tablet I keep getting this message popup that Exchange Services has stopped working.
Anybody know how to fix this issue? I just started Rooting and ROMing, this is my first device.
Same issue
flatout42 said:
I installed SlimLP 0.14 recently with TWRP and used this version of Gapps - Slim_mini_gapps.BETA.5.1.build.0.x-20151228.zip
Throughout using the tablet I keep getting this message popup that Exchange Services has stopped working.
Anybody know how to fix this issue? I just started Rooting and ROMing, this is my first device.
Click to expand...
Click to collapse
Anyone know the cause of this, I get it pop up all the time and I don't use exchange and have disabled it and cleared all other email cache to no avail
Putridpauline said:
Anyone know the cause of this, I get it pop up all the time and I don't use exchange and have disabled it and cleared all other email cache to no avail
Click to expand...
Click to collapse
Bad/corrupt GAaps installation. Reflash package (suggest nano).
Davey126 said:
Bad/corrupt GAaps installation. Reflash package (suggest nano).
Click to expand...
Click to collapse
I'll try that now, thanks for the reply
Sent from my Fire Phone using Tapatalk
Putridpauline said:
Anyone know the cause of this, I get it pop up all the time and I don't use exchange and have disabled it and cleared all other email cache to no avail
Click to expand...
Click to collapse
Davey126 said:
Bad/corrupt GAaps installation. Reflash package (suggest nano).
Click to expand...
Click to collapse
Putridpauline said:
I'll try that now, thanks for the reply
Click to expand...
Click to collapse
More controversial is the source. I use Open GAaps builds w/o issue. Others claim only builds tweaked for SlimLP will function properly. Both should work and auto update to the latest versions once installed. As you (and others) have discovered it doesn't always work that way. Don't have a decisive answer; simply recapping past discussions.
If you are indeed on 0.14, 0.15 is out. Try flashing the latest version. Hopefully you've already had it fixed but I still recommend you update your rom
I was running SlimLP and I kinda liked it, but the CM build is updated very regularly so I feel a little better on a more up-to-date build. Performance may have been a tad better on Slim though, hard to say.
Mee too. I found that Exchange services stop working if Gmail app is installed. Just freeze Exchange services with Titanium backup.
The app "Get Assistant" wiped my build property file. I have not made a backup on this new Nexus 6 64GB yet. And there is no backup build prop file in System.
I know I can't reboot without getting stuck in a boot loop.
I am running a rooted stock 7.0.0 NBD91P.
Can someone post a build property or something? Need help. How can I rebuild it?
My bad. This phone has 7.0.0 Build NBD91P
Reboot. I've wiped mine before and it's been rebuilt by the system.
Sent from my Nexus 6 using Tapatalk
Larzzzz82 said:
Reboot. I've wiped mine before and it's been rebuilt by the system.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
So there is no chance of getting stuck in bootloop?
There is one line on it. The one that adds Google assistant.
Should I delete that line? Or delete the build.prop file?
The author of that apps says it will bootloop.
Dixon Butz said:
So there is no chance of getting stuck in bootloop?
There is one line on it. The one that adds Google assistant.
Should I delete that line? Or delete the build.prop file?
The author of that apps says it will bootloop.
Click to expand...
Click to collapse
Don't delete build.prop!
Sent from my A0001 using Tapatalk
This is what happened to me, YMMV... I edited my build prop one time with regards to making assistant work. I made the changes, then changed my mind, as it was the third time trying to get it to work. I attempted to back out and was asked if I wanted to save the changes. I said no. Stuff wasn't working after that. Went back to look at the build prop and it was empty. After a longer than normal reboot, everything was fine. I was using root explorer, fwiw.
Sent from my Nexus 6 using Tapatalk
Larzzzz82 said:
This is what happened to me, YMMV... I edited my build prop one time with regards to making assistant work. I made the changes, then changed my mind, as it was the third time trying to get it to work. I attempted to back out and was asked if I wanted to save the changes. I said no. Stuff wasn't working after that. Went back to look at the build prop and it was empty. After a longer than normal reboot, everything was fine. I was using root explorer, fwiw.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks!
But I found a backup that was made in :
/storage/emulated/0/
temp_build.prop.bac 03/04/17 01:42 PM 4.86 kB
Ho Lee Fuk!
Time for TWRP backup and a beer :victory: