Stock build prop - Sprint HTC EVO 4G LTE

So I am trying to change my stock build prop so I can use Google wallet... I am supposed to change it to htc_jewel. But my stock build prop already says htc_jewel... Not evo? What's going on? I never changed anything... My Google wallet does not work even with it saying htc_jewel stock... Should I change it to evo? I'm really confused why my stock evo lte says htc_jewel.
Sent from my EVO using xda premium

NissanNick said:
So I am trying to change my stock build prop so I can use Google wallet... I am supposed to change it to htc_jewel. But my stock build prop already says htc_jewel... Not evo? What's going on? I never changed anything... My Google wallet does not work even with it saying htc_jewel stock... Should I change it to evo? I'm really confused why my stock evo lte says htc_jewel.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Wallet is broke for everyone. Google is aware and working on a fix.
Sent from my released from customs Evo Lte!

NissanNick said:
So I am trying to change my stock build prop so I can use Google wallet... I am supposed to change it to htc_jewel. But my stock build prop already says htc_jewel... Not evo? What's going on? I never changed anything... My Google wallet does not work even with it saying htc_jewel stock... Should I change it to evo? I'm really confused why my stock evo lte says htc_jewel.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Most people edit the second model line look around line 10 and change that one

NissanNick said:
... I'm really confused why my stock evo lte says htc_jewel.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Because that is the base internal model HTC assigned to our phone. That way no matter what carrier calls it (One X or Evo or anything else) internally it is the Jewel model. It is common practice for manufacturers to develop a product under a name internally, before the public name has been decided ... hope that makes sense
Sent from my Kindle Fire using xda premium

Ok so I edit my build prop file and it keeps telling me it can't save it? I have root and im using es file exsplorer...
Sent from my EVO using xda premium

Mount system as rewritable in order to save
sent from my EVO LTE

Ok got it edited and saved... Site tell my me the "not in your country" error... What am I doing wrong.
Sent from my htc_jewel using xda premium

You need to reboot after making changes to the build.prop. Also clear Wallet's app data.

grayn0de said:
You need to reboot after making changes to the build.prop. Also clear Wallet's app data.
Click to expand...
Click to collapse
NissanNick said:
Ok got it edited and saved... Site tell my me the "not in your country" error... What am I doing wrong.
Sent from my htc_jewel using xda premium
Click to expand...
Click to collapse
This plus make sure you update wallet AFTER changing your build.prop
Sent from my Transformer Prime TF201 using Tapatalk 2

I edited it... With the wallet app deleted... Then I reboot the phone... Redownload the app.... And still nothing?
Sent from my htc_jewel using xda premium

Related

Package file invalid?

I sometime get package file invalid when software installes. I run it again and all is cool? Any ideas or clues?
Sent from Photon 4G code name "Neo"
Anyone? Its not a deal killer, like I said, if I go and reinstall it, it works. I have just never seen it.
I get it sometimes too. Couldn't tell you why tho.
Sent from my MB855 using xda premium
magui43212 said:
I get it sometimes too. Couldn't tell you why tho.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Same here!
My bad, I only looked into Photon 4G and not the entire XDA. Android Market is jacked up and/or did not install correctly. From my read, guy/girl installed version 3.1.1 and that cured it? I will go see.

Google wallet

Mine just started working. My build.prop file is in its original state. Anyone else?
Sent from my htc_jewel using xda premium
Not me
Sent from my EVO using XDA
Not mine as well
Sent from my EVO using Xparent ICS Tapatalk 2
Still getting the not supported error.
Same here with the error...
DrZune said:
Still getting the not supported error.
Click to expand...
Click to collapse
Mine is getting the same. Went from stock ROM to Team Nocturnal ROM. No change even after uninstalling and reinstalling. Lucky you to get yours working. After all this, just give me a $10 Amazon Gift Card and end this.
Can I root
OK I have a question. I just got the EVO LTE and want to root it. But I keep seeing that I need to clear the data from my Google Wallet or it will be forever bricked. But of course I am getting an error saying its not supported buy my country (WTF). I cleared the data in the app settings but wonder is it safe to root if I dont do it thru the app. I want to root but dont too loose wallet if I do. Any suggestions or should I just wait till Google figures out what to do with wallet.
Thanks for any advice
Adam1422 said:
Mine just started working. My build.prop file is in its original state. Anyone else?
Sent from my htc_jewel using xda premium
Click to expand...
Click to collapse
But your Sig shows htc_jewel so doesnt that mean you changed your build prop?
Sent from my EVO using xda premium
Adam1422 said:
Mine just started working. My build.prop file is in its original state. Anyone else?
Sent from my htc_jewel using xda premium
Click to expand...
Click to collapse
Nope, not mine either
butterbuns said:
But your Sig shows htc_jewel so doesnt that mean you changed your build prop?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
No
sent from my Jewel via xda premium.
Still getting error
Still getting error...
No go...
Check Me Out On The Google Play Store!!!
​
Sent From My HTC Evo 4G LTE, On The Now Network From Sprint!
smells of a troll post. maybe google only wanted it to work for you?
Mine still broke, at least google finally said something about the situation. Was pissing me off that no one was talking Sprint, HTC or google for a while. Just setup a friend with a GSIII on Friday and Google Wallet seemed to be ok no errors. Wonder how long it will take for fix.
http://www.androidauthority.com/htc-evo-4g-lte-google-wallet-software-fix-96935/
not safe to root
killwrath, from what I read you should not root, you MUST clear your data from within the app itself (restore to factory). clearing you data will not help and you'll brick your secure element..
kaos420 said:
smells of a troll post. maybe google only wanted it to work for you?
Click to expand...
Click to collapse
Agreed
Sent from my EVO using xda premium
scottspa74 said:
No
sent from my Jewel via xda premium.
Click to expand...
Click to collapse
Get out of here you worthless troll
Sent from my htc_jewel using xda premium
killwrath said:
OK I have a question. I just got the EVO LTE and want to root it. But I keep seeing that I need to clear the data from my Google Wallet or it will be forever bricked. But of course I am getting an error saying its not supported buy my country (WTF). I cleared the data in the app settings but wonder is it safe to root if I dont do it thru the app. I want to root but dont too loose wallet if I do. Any suggestions or should I just wait till Google figures out what to do with wallet.
Thanks for any advice
Click to expand...
Click to collapse
It's safe to root using Zedomax(?)'s method only. I've done it, been in your same spot.
Sent from my htc_jewel using xda premium
Closed...Even if not a troll post, there are countless Wallet threads that this kind of information could be posted in, instead of creating a new thread.

Google Wallet is not available on your device or your carrier

After the latest update of Google Wallet, I get that error on both my EVO LTE and my Nexus 7.
Both are rooted, but Wallet ran, at least on my EVO LTE, before the update.
I have tried uninstalling, but I get the same error. I've tried temporarily un-rooting, but I get the same error. I've tried re-installing the update. I've cleared both cache and data.
I've even tried using search in this xda app, but it doesn't even find the word Wallet.
Two days ago Wallet decided to run on my Nexus, but today it says "no".
As I am having this same error on both devices, I can infer it has nothing to do with Sprint. Since Wallet ran previously on my rooted device, I can assume it has nothing to do with that either.
Also, since my Nexus and EVO LTE are not related, there must be others having this issue.
Has anyone heard about this?
Sent from my Nexus 7 using xda app-developers app
In Root Explorer, what are the permissions on the wallet APK in the system directory?
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
michael.stollaire said:
In Root Explorer, what are the permissions on the wallet APK in the system directory?
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
Click to expand...
Click to collapse
On Nexus 7
Owner: read write checked.
Group: read checked
Other: read checked.
Everything else un-checked.
On the EVO LTE:
The apk is called "walletnfcrel-1.1-R57-v5-prod-20120405-relkeys.apk.
Permissions show rw-r-r-
Owner is listed as root.
Btw, back at home, Wallet opens on the Nexus again. Wtf? When I started this thread, I was at Starbucks, someplace where I could have actually had a use for Wallet.
Still no go on the EVO though.
Sent from my Nexus 7 using xda app-developers app
I finally got tired of it. I really wanted wallet to work, and since switching to MeanROM ICS it's worked perfectly. Did you try editing the build prop file to the model number of another device?
Sent from my EVO using xda premium
With the newest software from the OTA wallet is fixed guys.
If your rooted, don't take the OTA, flash a rom with it baked in
Sent from my EVO using Tapatalk 2
So no way to get it working on the EVO LTE other than flashing a different Rom? Great.
I'm sure this Wallet thing will really take off if the typical consumer has to do that. I hate Apple, but I can't see this ever happening on that platform.
I tried editing my build.prop to:
I edited my build.prop file to:
I changed my ro.product.model=GT-I9300
ro.product.device=GT-I9300
Still won't even run, much less log into my account.
Sent from my Nexus 7 using xda app-developers app
leebo said:
I'm sure this Wallet thing will really take off if the typical consumer has to do that. I hate Apple, but I can't see this ever happening on that platform.
Click to expand...
Click to collapse
Well.. The latest update that the "typical consumer" would be using has a Wallet fix, so they wouldn't even have to think of rooting their phone.
I see.
So even though Wallet ran on my rooted EVO LTE with stock room before, I now have to either un root and update, change to a different Rom, or simply forget about Wallet.
So weird. Thanks though.
Sent from my Nexus 7 using xda app-developers app
leebo said:
I see.
So even though Wallet ran on my rooted EVO LTE with stock room before, I now have to either un root and update, change to a different Rom, or simply forget about Wallet.
So weird. Thanks though.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You need to fix your build.prop. You obviously did a gameloft mod or something similar. You need to restore your build.prop backup or get the proper settings installed. The problem you are describing is caused by the wrong phone in the build.prop.
Sent from my A500 using Tapatalk
---------- Post added at 06:56 PM ---------- Previous post was at 06:54 PM ----------
leebo said:
So no way to get it working on the EVO LTE other than flashing a different Rom? Great.
I'm sure this Wallet thing will really take off if the typical consumer has to do that. I hate Apple, but I can't see this ever happening on that platform.
I tried editing my build.prop to:
I edited my build.prop file to:
I changed my ro.product.model=GT-I9300
ro.product.device=GT-I9300
Still won't even run, much less log into my account.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Those aren't the correct settings.
Sent from my A500 using Tapatalk
I'm a little dense.
Obviously those aren't the correct settings.
The correct settings didn't work in the first place (ro.product.model=EVO, ro.product.device=htc_jewel). That's why I edited it.
I got that from another long thread thread.
I thought the point was to trick Wallet into thinking it was a different device?
I did not do any other mods besides root the phone. It's not even unlocked.
I'm so lost!
Sent from my Nexus 7 using xda app-developers app

CM 10.1 asking me to activate?

Just flashed CM 10.1 and Gapps and upon first bootup it's asking me to activate. Do I need to activate or can I skip it?
I installed Meanbean before this and it didn't ask me to activate so I'm a little confused.
Thanks!
SKip
Did you just s-off your phone, regardless when you try to make a call, sprint will pick up and fix it for you if you are not able to make calls.
Sent from my Evo 4G LTE using xda premium
? Have never seen CM ask to be activated. Never. You able to get a picture of this?
Sent from my EVO using xda premium
tonyevo52 said:
Did you just s-off your phone, regardless when you try to make a call, sprint will pick up and fix it for you if you are not able to make calls.
Sent from my Evo 4G LTE using xda premium
Click to expand...
Click to collapse
jkrlvgn said:
? Have never seen CM ask to be activated. Never. You able to get a picture of this?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yeah, I S-off'd via DirtyRacun right before flashing the rom.
Just skipped it and I can still make calls so no worries.
jkrlvgn said:
? Have never seen CM ask to be activated. Never. You able to get a picture of this?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
If I recall right, when deck very first built CM10, people got the activate message and it actually really borked a couple phones. There's even big red bold type in the OP referring to it. But that was long ago, and not on 10.1
From my Evo LTE, yup.

Weird text message.

Anyone know what this is? I started getting these on the sense 5 rom and now I'm stock and got it again. Happened when a friend tried to send a pic. They had to send it twice for it to work.
Tried Google and got nothing.
Sent from my HTC6435LVW using xda app-developers app
Did you download a new app recently? One from a random developer?
mwl1119 said:
Did you download a new app recently? One from a random developer?
Click to expand...
Click to collapse
Not that I can think of. I could have though. I've installed and uninstalled so many apps it's hard to keep track. You mean just grabbing the apk online?
Sent from my HTC6435LVW using xda app-developers app
croppz said:
Not that I can think of. I could have though. I've installed and uninstalled so many apps it's hard to keep track. You mean just grabbing the apk online?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I have had apps from the play store do weird things to my phone as well.
mwl1119 said:
I have had apps from the play store do weird things to my phone as well.
Click to expand...
Click to collapse
Well. Spam tastes like crap haha
Sent from my HTC6435LVW using xda app-developers app
Did you by chance use to have a fascinate or other galaxy s variant?
Sent from my HTC6435LVW using Tapatalk 4
ibsk8 said:
Did you by chance use to have a fascinate or other galaxy s variant?
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
Nope. Went from droid 2 to iphone 4 to the DNA.
Sent from my HTC6435LVW using xda app-developers app
It's a WAP push. Something to do with the MMSc.
I got those when I went from a feature phone to smartphone.
I blocked the number but a call to CS should fix it. I'm blaming the iPhone.
fr4nk1yn said:
It's a WAP push. Something to do with the MMSc.
I got those when I went from a feature phone to smartphone.
I blocked the number but a call to CS should fix it. I'm blaming the iPhone.
Click to expand...
Click to collapse
It only started happening after I ran AOSP and Sense 5 based roms recently. Got it on sense 5 and restored and started getting it on stock as well. I tried googling the issue and got nothing. Not sure verizons goons are gonna be able to do anything.
Verizon support is not the best. Most don't even know what they are talking about. When I called once to get my data working again on my continuum the guy who I got had the same phone and he said he had the same problem but his data was just turned off and he didn't even know...
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Could it have something to do with the MMS proxy being set wrong in the APN settings? Are you running one of the Sense 5 ROMs designed for GSM use?
Dave12308 said:
Could it have something to do with the MMS proxy being set wrong in the APN settings? Are you running one of the Sense 5 ROMs designed for GSM use?
Click to expand...
Click to collapse
Nope. Was running NOS vzw sense 5 and never messed with my APN. Seems like thats all normal though. Only happens when my friend with her iphone tries to send me a pic. The message in thr screenshot will show up and she'll have to send again for it to work. Android to android seems to work fine.
Sent from my HTC6435LVW using xda app-developers app
croppz said:
Nope. Was running NOS vzw sense 5 and never messed with my APN. Seems like thats all normal though. Only happens when my friend with her iphone tries to send me a pic. The message in thr screenshot will show up and she'll have to send again for it to work. Android to android seems to work fine.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Google search for vnd.wap.mms and you'll find info. It should've cleared itself by now though.

Categories

Resources