I want to download Half Life 2 on my razer phone but it's locked to Nvidia shield devices. I heard that if you edit multiple things in prop.build, you should be able to download it. Well, I looked up what to edit and I edited all the common ones such as:
ro.product.model
ro.product.manufacturer
ro.product.name=
ro.product.device=
ro.product.manufacturer=
ro.build.fingerprint=
But even after changing all of those, it still says that it's incompatible. So I'm curious, have any of you done this successfully? And if you did what device did you use the prop.build information from and what things did you change? Thanks in advance.
Related
I have been struggling for some time trying to figure out how to get the *specific* model number of an Android device. Looking under the battery doesn't count because I'm trying to find it with software.
From an app, you can use Build.MODEL which seems to read from ro.product.model in /system/build.prop, but these values usually contain the marketing name for the device such as "T-Mobile MyTouch 3G" which is really a SAPP300 or SAPP310. My problem is that I need to actually know if it is the 300 or the 310.
It must be possible somehow because the bootloader shows this information as well as my PC when I plug the phone in via USB.
If anyone can help me it would be much appreciated.
$$$$$$ or a phone of your choice could be a reward for a solution!!!
Please help!
Another interesting thing regarding the model is that 9 times out of 10 the model string in the Settings -> About menu shows the same string that is in ro.product.model in build.prop. But once in a while, the about menu has a different string. For instance, the Inspire 4G (PD9812000) indeed says Inspire 4G in the about menu, but in build.prop and in Build.MODEL (app environment) it says Desire HD. These two models are very similar but for our purposes we need to be more precise. Any thoughts would be appreciated.
EDIT:
I looked through the android source and indeed the Model string in the About menu uses Build.MODEL, which I'm pretty sure uses the value in /system/build.prop. Since OEMs create their own builds, maybe they just hard coded "Inspire 4G" for the About menu string and just left build.prop alone (which is why it and Build.MODEL contain "Desire HD").
This still doesn't explain why the correct string is sent over USB for instance, but for now I'm just using a work around.
techsign said:
Another interesting thing regarding the model is that 9 times out of 10 the model string in the Settings -> About menu shows the same string that is in ro.product.model in build.prop. But once in a while, the about menu has a different string. For instance, the Inspire 4G (PD9812000) indeed says Inspire 4G in the about menu, but in build.prop and in Build.MODEL (app environment) it says Desire HD. These two models are very similar but for our purposes we need to be more precise. Any thoughts would be appreciated.
Click to expand...
Click to collapse
I think that the best you're going to get comes from the build.prop. If the firmware is hacked to make it look like another phone, there's not much you can do about it.
The Inspire 4G is the same phone as what Telus released in Canada as the Desire HD. Same FCC ID even, I believe. So there really is little by which you can distinguish them.
If your app has network access, it could read the IMEI and look it up in a publicly available database to confirm for sure which device it is.
Sent from my Nook Color!
hello XDA'ers,
I was on AppBrain looking at a variety of apps and games. I came across the game "Contract Zombie Killer" by GLU. I hit install on AppBrain and then went into my phone to install it. Market stats that this game is not compatible with your device. What the Hell, I have a flippin Photon. What device is it compatible with. Can anyone offer any explanation
***edit - normally I would not care, however this game looks like a COD Zombies ***
Worked on my Xoom...Not sure about the photon
I found this fix for most of these "device not compatible" games like contract killer zombies and gameloft games Like Nova 2.
TO FIX THIS ISSUE YOU NEED ROOT!!
Using Root Explorer you will need to modify your build.prop file.
Location: /system/build.prop
make sure /system is mounted R/W
and edit the build.prop file,
The best way to do this is to add these 5 new lines and just comment out the original 5 lines so you can easily go back to normal.
Lines to be added:
ro.product.model=Optimus 2X
ro.product.brand=lge
ro.product.name=lge_star
ro.droduct.device=p990
ro.product.board=p990
To comment out a line just add # in front of the line.
So should look like this: ( Yours might be different do to I have the USCC Electrify not Sprint Photon 4g )
ro.product.model=Optimus 2X
ro.product.brand=lge
ro.product.name=lge_star
ro.droduct.device=p990
ro.product.board=p990
# ro.product.model=Motorola Electrify
# ro.product.model.number=MB853
# ro.product.brand=MOTO
# ro.product.name=uscc_us
# ro.product.device=sunfire
# ro.product.board=sunfire
Then save and exit, reboot phone.
Then run the game again and it will download the files like normal (likely need wifi do to file size).
After you download the files you can change the build.prop so that your normal lines are no longer commented out and just comment out the five added lines so you can do it again easily for more games you get that are "not compatible".
Hope this helps.
seesser said:
I found this fix for most of these "device not compatible" games like contract killer zombies and gameloft games Like Nova 2.
TO FIX THIS ISSUE YOU NEED ROOT!!
Using Root Explorer you will need to modify your build.prop file.
Location: /system/build.prop
make sure /system is mounted R/W
and edit the build.prop file,
The best way to do this is to add these 5 new lines and just comment out the original 5 lines so you can easily go back to normal.
Lines to be added:
ro.product.model=Optimus 2X
ro.product.brand=lge
ro.product.name=lge_star
ro.droduct.device=p990
ro.product.board=p990
To comment out a line just add # in front of the line.
So should look like this: ( Yours might be different do to I have the USCC Electrify not Sprint Photon 4g )
ro.product.model=Optimus 2X
ro.product.brand=lge
ro.product.name=lge_star
ro.droduct.device=p990
ro.product.board=p990
# ro.product.model=Motorola Electrify
# ro.product.model.number=MB853
# ro.product.brand=MOTO
# ro.product.name=uscc_us
# ro.product.device=sunfire
# ro.product.board=sunfire
Then save and exit, reboot phone.
Then run the game again and it will download the files like normal (likely need wifi do to file size).
After you download the files you can change the build.prop so that your normal lines are no longer commented out and just comment out the five added lines so you can do it again easily for more games you get that are "not compatible".
Hope this helps.
Click to expand...
Click to collapse
this is great information - I just went into Root Explorer (mount as R/W) - went into systemt - selected the build.prob (has a notepad icon next to it) - when I opened it, it shows alot of text. I see the area to edit, my question is "how to edit it". I have selected view as text = nothing. Any advice??
Long press and select open in text editor
THANKS TO YOU BOTH - worked like a frickin charm - wow - that was awesomely impressive!!! - Thanks again!!
Glad to help. I ran into this problem mainly on my G-Tab running CyanogenMod, I could buy all the new Gameloft games at there sale $0.99 but was unable to download the game data for that reason and found this trick. what this does is changes the name and info about your phone, this mods tells the game/app checks for phone type that you are the LG Optimus 2X instead of the Photon 4g.
Just remember to change the commented area back so that the Photon is being read not the Optimus. So that when you get other items that are designed differently that you get the one for the Photon.
Hello. I tried using this to make 9mm work but its not working. I keep getting its not compatible. Do you know a way around this? Thanks
hello guys i have one problem with compatibility we all know that gameloft couldn't care less about supporting more devices and simply say "ask a refund" - which is not the way i'm gonna stop trying i have bought the game back when i had LG O2X, but now i have Xperia S which is not supported by default (odd, as cracked versions did - unfortunately i'm unable to play with cracked version anymore cause of update), so i decided to solve this by myself, i've managed to get Arc S data files pack from gameloft and decompiled it with third party tool to sd files and data files, moving them to according positions, but the game acts like there are no data files found, trying to download data files for LT26i, which, of course, fails, as there are no such data on gameloft server. is there any way to either trick the game to think it's running on Arc S or to properly setup the game manually including game data setup. thanks in advance.
2 mods: this is not "howto play stolen game" thread but "howto play legally owned copy on unsupported device" thread, but if it still break the rules, feel free to delete this thread and accept my apologizes. thank you.
problem solved... in case anyone wondering: open build.prop file in /system/ root...
then, find and modify following values:
Code:
ro.product.model=LT26i
ro.product.device=LT26i
They are ALLWAYS there, so do NOT create them in case you think they aren't, that might cause unforseen consequences including bootloop...
change them accordingly:
Code:
ro.product.model=LT18i
ro.product.device=LT18i
Reboot phone...
any application that checks those variables will think they are runnng on Arc S instead of S, allowing you to "forcibly download" data for Arc S in gameloft games, which, in most cases, will work on Sony Xperia S...
After the download it is safe and advised to revert values in build.prop to their original values, as it might break compatibility with other apps, relying on those values.
PS: you can buy the game by accessing gameloft mobile website (m.gameloft.com) and setting your device to Arc S, then you will see and be able to buy the game, it is even cheaper than via google play...
Hello, I know there’s a lots off topics about this subject but can’t find any answer on this subject.
I have a phone that I need to change resolution. Since I’m developing an app that needs fixed resolution. The problem is that if I try to use an app to change resolution, the apk won’t work. Since that kind of resolution change is not at hardware level. So in order to my app work on the device, need to set resolution as native.
Things I tried so far:
Nomode resolution app and wm size xxxx ( resolution that I want. No luck
After that started to dig into build.prop in order to find a solution, tried the lines:
debug.drm.mode.force=720x1280
ro.sf.lcd_width=720
ro.sf.lcd_height=1280
No luck with this lines in build.prop
I believe theres a way to change device resolution via build.prop but I’m not getting it. Maybe I need more lines in build.prop or edit something related. Maybe frame buffer. Anyway need help. In raspberry it could be done, also could be done on android x86, now need to do it on real phone.
At the moment I’m trying this on an huawei phone, if anyone can help I really appreciate it. Thanks
hello. i thought to be smart and download the APK through a downloader in browser on PC, but is still not able to install. it just says "App not installed".
ANYHOW... i feel this app should work just fine on the phone. problem is is that the company don't want it on other phones. so, there are some HTC and Sony apps from my past that won't install to a Coolpad phone i have.
is there any way to modify the APK so it will properly install? i don't believe the app to actually be incompatible, it is just proprietary to a different brand of phone.
the app i most want right now is > https://play.google.com/store/apps/details?id=com.sonymobile.xperiaweather
i used this to download it > https://apps.evozi.com/apk-downloader/
thanks for reading! i await any responses
@sk74261700027
If your phone's Android is rooted, you can try to edit Android's build.prop file housed in /system, will say change there brand / model settings according to your needs. Use a "BuildProp Editor" app to manage this,
jwoegerbauer said:
@sk74261700027
If your phone's Android is rooted, you can try to edit Android's build.prop file housed in /system, will say change there brand / model settings according to your needs. Use a "BuildProp Editor" app to manage this,
Click to expand...
Click to collapse
shoot. i have yet to figure out how to root this phone. it doesn't seem like there is any public root method for this phone yet. drat.
but if i could do that on the phone... shouldn't it also be possible to do this in the APK? i also don't know exactly what info that would be put there even if the phone was rooted. meh.
i figured worst case, i could use the regular Android software on PC to make changes to the APK. other then that, i think it could be possible to make changes to the APK with luckypatcher, but am not certain about that.
@sk74261700027
I never made use of LP.
You of course can try to decomplie an APK, rewrite app's source code and afterwards recompile it and then correctly sign the APK. Personally never have done so.
jwoegerbauer said:
@sk74261700027
I never made use of LP.
You of course can try to decomplie an APK, rewrite app's source code and afterwards recompile it and then correctly sign the APK. Personally never have done so.
Click to expand...
Click to collapse
oof. that sounds complicated. lol :/
i know there is Android Studio and SDK tools, but there is a lot there and i don't know exactly what is needed. i was just hoping that changing an APK for proprietary apps to install on non-proprietary devices was a normal thing, and that there would be a straight forward way to do this. sadly, i don't see any guides on this.
might just have to look around for something more generalized, like what you were talking about. i am surprised that there isn't a normal process for this type of thing. meh
well, thanks anyhow. thank you for replying here. at least that might give me an idea on where to go from here. in the meantime, imma just give this thread some more time. see if anyone knows anything more specific about this.
P.S. oh yeah! i do recall some kind of google market app that would allow you to change, or emulate, a device to download apps from the Play Store that are stated as not being compatible. will have to look for that and see if it still works. if someone knows where to find this, that would be really great.