I want to fool the market into thinking I have a D3 instead of an xt860, I've found a few possible lines in the build.prop to change the model but aren't sure which to change and what they should read. Any help?
Also what are the file(s) that need to be changed to force hardware acceleration
Sent from my XT860 using xda premium
Related
Just discovered the market won't let me download my gameloft games. Googled it and it seems I need to change my build. Prop. I really suck with terminal commands, anyone got a cwm flashable idiot proof fix?
Sent from my SGH-I897 using XDA App
Looking for a fix as well. Surprised a definitive answer hasn't been posted yet unless I missed it. One Guy posted his build.prop but I don't know exactly what to change
Well I imagine someone eventually well help us out. I'm going to keep googling in the meantime. I found someone who had the issue on the vibrant and someone had a new build.prop to give him and it worked, but he didn't say how to install the build.prop. Just said "Swap this one out with your old one"...and? How exactly do I go about doing that?
It can be done with root explorer
Cor-master said:
Just discovered the market won't let me download my gameloft games. Googled it and it seems I need to change my build. Prop. I really suck with terminal commands, anyone got a cwm flashable idiot proof fix?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
No terminal commands needed.
Get a root file explorer
Navigate to /system
There you will find the build.prop
Open that with any text editor, or copy it to your sdcard and use NotePad on your pc. It's just a plain text file.
Once all edited. Save and reboot.
Make sure your system is mounted r/w or it won't let you change anything in that partition.
Cool, so I have another stupid question : what do you change the build.prop too?
Sent from my SAMSUNG-SGH-I897 using XDA App
Kind of depends on what ROM you are running and what in the build prop is incorrect. Sometimes when running i9000 roms your build will be written to reflect your phone as no longer being an I897. It happened to me many moons ago. Luckily the rom thread had an updated build prop posted. Search for the Market Fix apk in the market. That allows you to change your signature that the market views your phone by. You may also try Market Enabler there's a few different versions to choose from, just a temporary ID changer.
Sent from my SAMSUNG-SGH-I897 using XDA App
Ok but what do I change EXACTLY to have it recognized by the market as a Samsung Captivate? And why don't these cyanogenmod developers fix this? It's a common issue why ignore it? Arghhhhhhh I'm getting irritated. A guy on the cyanogenmod forums said to use root explorer and change manufacturer to samsung and model to nexus s. I did that and only freaking difference is my XDA app says I'm using a nexus s. The market is still the freaking same and i even freaking cleared the cache and rebooted. Yeah I'm irritated. Just bought Modern Combat 2 and can't play it because of this stupid problem!
Sent from my Nexus S using XDA App
Finally figured it out, the stuff I was told to change has nothing to do with market access, changed 4 other entries to "GT-I9000" and that fixed the problem. Wasn't mad at anyone just frustrated
Sent from my Nexus S using XDA App
Cor-master said:
Finally figured it out, the stuff I was told to change has nothing to do with market access, changed 4 other entries to "GT-I9000" and that fixed the problem. Wasn't mad at anyone just frustrated
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
To get everything to recognize it as a Captivate you need to chang eANYTHING that says Gt-i9000 to SGH-i897 and anything that says galaxysmtd or something like that to captivatemtd or whatever stock shows it as( I cannot remember what stock shows at this moment). But if you make these changes then xda app and the market and anything else will recognize it as a Captivate
Sent From My KickAss ATT SGS2 SPORTING CM7
Hey there,
I was wondering if there's a way to change the device ID for a specific application on my phone? Rogers launched Android Visual Voicemail today, but the application is only compatible for the Xperia X10 and Samsung Galaxy Q. Change the whole device ID could, I believe, create problems with my other apps.
What I'm looking to do is basically make the VVM application believe I'm using an X10/Galaxy Q, but leave my Raider ID for the other apps.
Is that even possible?
I did search around, but found nothing exactly related to what I'm looking for.
Thanks!
Yes, it is, you have to change a few things in the build.prop
ro.product.model=PH39100
ro.aa.modelid=PH3910000
ro.product.brand=cingular_us
ro.product.name=htc_holiday
ro.product.device=holiday
ro.product.board=holiday
ro.build.fingerprint=cingular_us/htc_holiday/holiday:2.3.4/GRJ22/172546.4:user/release-keys
and change it into the device you want
Maybe something in system/customize/CID but most like not
cruzin_cruzing said:
Yes, it is, you have to change a few things in the build.prop
ro.product.model=PH39100
ro.aa.modelid=PH3910000
ro.product.brand=cingular_us
ro.product.name=htc_holiday
ro.product.device=holiday
ro.product.board=holiday
ro.build.fingerprint=cingular_us/htc_holiday/holiday:2.3.4/GRJ22/172546.4:user/release-keys
and change it into the device you want
Maybe something in system/customize/CID but most like not
Click to expand...
Click to collapse
Would that affect ALL my apps?
I just want the Rogers Visual Voicemail Plus app. to think I'm using a Galaxy Q or a Xperia X10, not ALL of my apps.
Thanks!
It will basically make all apps see your phone as what you change it too. I'd think for the most part with those models you'd pretty much have access to the same apps on the market. What you have installed already shouldn't be affected I think. The visual voicemail from rogers needs to be signed up through them though so this method might not work properly. Just save a copy of your original build.prop so you can go back to normal if it doesn't work out.
Sadly it will. You could decompile the apk with apktool and edit the manifest but even that is not guaranteed.
That method is down here:
http://forum.xda-developers.com/showthread.php?t=1258335
Just scroll down a bit more.
Sent from my HTC PH39100 using xda premium
I am trying to do the same thing for an APP called Modern combat 3, i have heard that some were able to play it after changing to an samsung ID.
is there a link on how to change that build.prop?
change it in DOS/ terminal?
ikkuy said:
I am trying to do the same thing for an APP called Modern combat 3, i have heard that some were able to play it after changing to an samsung ID.
is there a link on how to change that build.prop?
change it in DOS/ terminal?
Click to expand...
Click to collapse
There is many ways. here https://market.android.com/details?id=org.nathan.jf.build.prop.editor its free realy easy to use. You got be carefull if you change wrong value in thete you can have all kings of problems.
If i helped please thank me by hiting thanks
Send from my SG2-i777 using XDA Premium App
ikkuy said:
I am trying to do the same thing for an APP called Modern combat 3, i have heard that some were able to play it after changing to an samsung ID.
is there a link on how to change that build.prop?
change it in DOS/ terminal?
Click to expand...
Click to collapse
**** I accidently thanked you while trying to hit the more button.
Sent from my GT-I9100 using Tapatalk
Waddle said:
**** I accidently thanked you while trying to hit the more button.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
uh...thanks. i guess i d hit thank you for ur post then
---------- Post added at 01:33 PM ---------- Previous post was at 01:32 PM ----------
Waddle said:
**** I accidently thanked you while trying to hit the more button.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
found my way there
I changed it with root explorer thx tho
cruzin_cruzing said:
Sadly it will. You could decompile the apk with apktool and edit the manifest but even that is not guaranteed.
That method is down here:
http://forum.xda-developers.com/showthread.php?t=1258335
Just scroll down a bit more.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Can this make the switch in android id for a specific app easier?
Would anyone know why a d3 would have issues d/l stuff from market? It says that my device is not compatible but some of these apps I already have on my phone and some of them my girlfriend can d/l on her d3 but I can't? Any ideas?
Sent from my DROID3 using XDA
Jason Roach said:
Would anyone know why a d3 would have issues d/l stuff from market? It says that my device is not compatible but some of these apps I already have on my phone and some of them my girlfriend can d/l on her d3 but I can't? Any ideas?
Sent from my DROID3 using XDA
Click to expand...
Click to collapse
Market version I'd assume? Are you using Google Play yet?
Yep on play
Sent from my DROID3 using XDA
Jason Roach said:
Would anyone know why a d3 would have issues d/l stuff from market? It says that my device is not compatible but some of these apps I already have on my phone and some of them my girlfriend can d/l on her d3 but I can't? Any ideas?
Sent from my DROID3 using XDA
Click to expand...
Click to collapse
because it's not classifying your phone as a "droid 3" its classifying it as something different, i believe if you modify the build.prop file, theres a line in there that says "device ID" and you can change it to the correct device ID and it should recognize it as a D3, but then this is all for custom roms, if you're using a stock rom, then i'm completely in the dark lol
digitalsynner85 said:
because it's not classifying your phone as a "droid 3" its classifying it as something different, i believe if you modify the build.prop file, theres a line in there that says "device ID" and you can change it to the correct device ID and it should recognize it as a D3, but then this is all for custom roms, if you're using a stock rom, then i'm completely in the dark lol
Click to expand...
Click to collapse
It definitely can be seen as many phones. The XT862 is the American model of the Droid 3, but the Droid 3 is a Verizon specific branding. If I go to the Play Store on my computer and DL an app to my phone, I have multiple models to pick from, all are my D3, but some are labeled D3 and some are XT862, and I attribute this to running custom ROMs, both modified Blur and AOSP (I believe AOSP broke the Droid 3 branding).
Check my screen capture.
I saw that iPhone users on AT&T got a hacked carrier update today that enables HD Voice in markets where it's being tested in the USA, and I can't find anything on how to enable it for our HTC One devices. I know that for the One X it was a simple build.prop tweak, but I don't see any such entry in the build.prop for the HTC One. Any ideas?
mine has the following in build.prop, i'm pretty sure it enables it...
ro.ril.enable.amr.wideband=1
In addition the carrier has to white list the handset model as a whole.
Sent from my SPH-D710 using xda premium
daclaw said:
mine has the following in build.prop, i'm pretty sure it enables it...
ro.ril.enable.amr.wideband=1
Click to expand...
Click to collapse
AOSP or Sense?
Does anyone know if you could allow certain commands using the build.Prop to desable security on the att version of the note 3? I know that in the sprint version I got rid of the annoying sim icon on top of the screen. Maybe there's a command or change of value to make the phone think it's a T-Mobile instead? Lol...
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app