Hi, I have a problem changing my device model from "ONE E1003" to "X" on Nougat.
Some ROMs like AOSIP,Tesla,Citrus can just simply add/edit "ro.product.model=X" on build.prop and the device name will change just like that.
But on another ROMs like RR,AICP,AEX(my current rom), editing like that won't change the device model. I also tried to use adb command, (adb shell settings put global device_name "X") but it still won't change anything.
Actually it is not really important but seeing my device name on certain apps and in the google play as "OnePlus ONE E1003" sometime really annoy me
If anyone have a better solution, feel free to share with me. Thank you.
Related
Many programs refuse to download on Google play, giving me the message: This program is not compatible with your device.
I have hunted down the APK files for most of those, and they have all worked flawlessly.
This means that Google play essentially doesn't really work for the Folio 100 IMO.
But maybe if it is possible to change the ID to that of some compatible device like the Motorola Zoom or Asus Transformer things would be better?
Do any of you know how to do that? And which device name or ID is best for getting full market access?
I have installed CyanogenMod 9 Alpha 4, after much tampering, but I can't find the answer to this problem anywhere?
I think you have to edit /system/build.prop file. I'm trying to also do it myself, but there must be a tricky way of doing it, because even with root permissions, I get "read only filesystem" errors and can't modify the file.
Don't know if it applies for this tablet but /system requires a app that can mount it as R/W. On my phone I've used Es File Explorer(free), Solid Explorer(free). There is also root explorer and a few other apps that do the same, all of them require SU. hope it helps
Cheers
anyone knows the lines that need to be edited to make it look like a galaxy tab 10.1??
Anyone have an idea as to an app that will change the device seen by the market, on the fly (no editing and not permanent)?
Why I need this (example):
I flash a ROM and the device is seen as an HTC HD2 – some apps will be marked as incompatible and cannot be downloaded
I flash a ROM and the device is seen as a NexusHD2 – those same apps are not blocked and can be downloaded
It is a limitation of the information provided by the developer when he/she submits his/her app to the market, which restricts the access.
While I am affected by a number of apps, here is one that comes to mind... HBO GO is marked as incompatible. I pay FiOS & HBO and would like to make use of that free app (among others) to access what I am already paying for.
I have contacted HBO and was unable to talk with anyone having the slightest clue as to what I was talking about, subsequently sending me to a page that listed "currently" supported Android devices and suggested that I check that regularly for updates…
My suggested resolution:
Freeze Google Play
Run Device_Change_App (whatever it might be called) to change the device information, reported by my device, to a device that will work for the app I want
Defrost Google Play, login, and download (pay if needed) the app.
Exit Google Play
Freeze Google Play
Re-run the Device_Change_App app and return to the ROM defaults.
Defrost Google Play
Ideas?
Look at the build.prop of the rom that show device like NexusHD2
Open the build.prop of rom that show device as HTC HD2
Change those lines :
ro.product.model=
ro.product.brand=
ro.product.name=
ro.product.device=
ro.product.board=
You can do this on your PC then copy build.prop on your SDCard and after you have to replace the build.prop set in system folder or you can follow this tuto :
How-to-edit-build-prop
ghenarys said:
Look at the build.prop of the rom that show device like NexusHD2
Open the build.prop of rom that show device as HTC HD2
Change those lines :
ro.product.model=
ro.product.brand=
ro.product.name=
ro.product.device=
ro.product.board=
You can do this on your PC then copy build.prop on your SDCard and after you have to replace the build.prop set in system folder or you can follow this tuto :
How-to-edit-build-prop
Click to expand...
Click to collapse
Thank you, ghenarys. I know how to edit it. The first line of my OP was "Anyone have an idea as to an app that will change the device seen by the market, on the fly (no editing and not permanent)?"
There was some app called build.prop editor
Sent from my GT-S5660
Yes but he's not looking to edit the build prop, reboot, blablabla. Instead an app with su permossions to freeze, change, and unfreeze. Like what Market Enabler does but for device Id. Is marketenabler open scource I wonder, maybe get in contact with them and see how they do it?
Dubhaltach said:
Yes but he's not looking to edit the build prop, reboot, blablabla. Instead an app with su permossions to freeze, change, and unfreeze. Like what Market Enabler does but for device Id.
Click to expand...
Click to collapse
Thank you, Dubhaltach. One app, would be ideal, but I was not pushing that far.
The problem would be for the app to contain, or look-up in real-time, info (ro.product.model=, ro.product.brand=, ro.product.name=, ro.product.device=, ro.product.board=) for the various ROMs that could be selected from.
Coding the app would definitely be easy enough as you wouldn't have to code in java, I'm sure a script would do. Maybe have a look over in Rom Toolbox, they let you run and write script codes. Let's see something like this
Code:
echo Changing Build prop...
pm disable vending.apk
Pull /system/build.prop /sdcard/buildpropbackup/build.prop
Move /sdcard/buildpropnew/build.prop /system/app
Echo rebooting...
Reboot
Pm enable vending.apk
you'd have premade custom build.props in your sd card. Can't think of a way of doping or without atleast 1 reboot. Making it a hot reboot would work I just don't know the busybox command for it. By the way what I wrote might have no effect at all its just my rough idea, needs refining!
Sent from my HTC One X using XDA
Post Deleted
I will move this back to development
But for future ref asking for or suggestions are not development as nothing has been developed so should go into the General or Q&A
When something has been developed then it goes into development
Thanks and good luck with this
Mods, if you could possibly move this back to development now that we have something to work on...
Eitherway, I present you................... device id changer!
Take it at your own risks, I'm not responsible for anything and havent fully had a chance to fully test anything. MAKE. A. NANDROID. BACKUP. And maybe try testing it from recovery if it doesn't work from Android.
If anyone would know how to throuw this into an android shell script (I don't know the syntax what with Echo and list's ect) give us a shout, or better yet a nice GUI app for this thing!
Good Luck!
Dubhaltach said:
Mods, if you could possibly move this back to development now that we have something to work on...
Eitherway, I present you................... device id changer!
Take it at your own risks, I'm not responsible for anything and havent fully had a chance to fully test anything. MAKE. A. NANDROID. BACKUP. And maybe try testing it from recovery if it doesn't work from Android.
If anyone would know how to throuw this into an android shell script (I don't know the syntax what with Echo and list's ect) give us a shout, or better yet a nice GUI app for this thing!
Good Luck!
Click to expand...
Click to collapse
Thank you, Dubhatach! Will give it a try after I do a triple backup...
Not at all, was a lovely simple yet doable project! Yeah I didn't want any mobs with pitchforks after me and my HD2 temporarily went kaput.
Sent from my HTC One X using XDA
DizzyDen's IMEI generator and ROM updater
This thing has been slowly packed with features, I bet you could do a lot of what you want here.
Pdroid lets you pick a random or static imei number as well, but the generator may be closer to what you want.
Hi everyone,
I'm new on xda and I come here because I struggle to install this app on my rooted Galaxy S4 with CyanogenMod 11: "Paiement mobile (pour Orange)" (sorry, I'm new, so I cannot post urls).
In fact, this app has not been declared by the devs (on the Google Play) to be compatible with my phone, despite the fact that I have the specs to run it (NFC payment).
I asked a friend who was able to download the app to upload it on Aptoide, giving me the opportunity to download the apk on my phone (this apk is available in this thread). I tried to install it, but I get the following the error: "app not installed".
I would like to force the installation of the app. I tried many ways, like using apps that use root access on the phone, without success (for example, I tried with "System Apps Installer" on the Google Play, but I get a problem with mounting /system). I also tried to install it with the command line tool, but I get the error "[install_failed_invalid_uri]". I tried to change the permission of the /data/local directory and /data/local/tmp with ES file explorer, but it did not change anything.
In addition to this, I'm not able to enable usb debugging in the developper options (to install the apk with adb), because every time I activate the option, it becomes disabled in the following seconds.
It seems to be a little bit complicated, because I seem to have different problems, but I hope that someone here will be able to help me !
Thanks for your help,
Aquignis.
The issue is most likely Cm. They alter things so some that normally work no longer work
I suceeded to solve the "[install_failed_invalid_uri]" error in the command line tool by also changing the permissions of /data.
After that, I got another error (yes, one more, but the last) that made me discovering what's the real problem in this situation: "install_failed_missing_shared_library". By doing some researches on the web and exploring the apk, I understood that the app use a library called "org.simalliance.openmobileapi" that corresponds to the work of SIMalliance, who developped an API called "Open Mobile API", which notably enables communication with NFC sim cards and must be integrated to the build of the ROM. This system is used by many banks in Europe and has been integrated in the stock ROM of many NFC devices by the important manufacturers, but not by Cyanogenmod devs in the last stable release of CM 11 for the Galaxy S4.
Like you said it, the problem was CM
I asked them if it has been integrated in CM 12, because that is why the app is said to be incompatible with my device by Google Play which automatically checks which libraries are installed on your device (I'm waiting for their answer). The other solution would be to add the library to the CM build by myself, because it seems not to be very complicated, but I'm not qualified enough to do this !
If it is not part of aosp I wouldn't count on it being added to be honest. Not to mention most banking apps refuse to work if the Rom has root as it can cause security issues.
Yes, the root seems to be a problem with some apps according to the work of this man.
On the other hand, I think that this API is important enough to make CM devs pay attention to it, because it is used in many countries (except the USA which use only HCE, I believe). If only I was able to build it myself !
I've been trying to find information on how to make some sort of restorable image of my stock phone (nexus 5x) before I do anything to it. I don't want to root it so that seems to really limit my options as most of the imaging options seem to involve rooting.
I was hoping to be able to use something like dd, someone suggested over on android forums which seems logical to me but I have run into another problem that everytime I boot into recovery adb on my computer (Lubuntu v17 if that helps) stops seeing my phone (ie adb devices yeilds nada) and even when it does see my phone there is nothing in the /dev/blocks/ dir that resembles what I think my phone should look like, its all symb links named like 7:0-8:82 pointing to things like loop and sda.
I am guessing that my phone is one of the sd?s (there is sda-sdf) but as adb is not seeing any devices I get "no such file or dir" when I try something like
dd if=/dev/block/sdf of=nexus5x.pit bs=4096
I would really like to make a clean image of this phone before I try anything so any thoughts would be appreciated!
I came across this issue 3 or 4 years ago. I searched internet and there were some discussions saying that there is a file (or profile) in Android that contains info on the type of device it is running on. The reason for the Apps not running was because the software (OS or Apps) detected that it is not on the right device. One circumvention is to modify the file (or profile) on the Android box to fool the software that it is running on the right device (e.g. a phone). This kind of modification require root access. At that time, I did not have any spare device to risk with. I did not write down the details. Now I have a spare android box and like to revisit the problem. But I am not able to find the info anymore. I hope my memory is correct. I am not sure if this is still true with the current Android version. If anyone has seen this before, can you kindly point me to the right direction.
There are some protections in app like RootBeer or PiracyChecker that check few things that crash certain apps on rooted phones and android emulators.
Check examples: is there superuser.apk, is there /system/bin access, is there SU binary or magisksu, is there Android_x86/Android_x64/MoboGenie/Droid4X in signature in build.prop, or hacking apps like AC Market, Black market, Lucky patcher etc.