As I've already pointed out in my comments on the question, modifying your device's build.prop
to appear as a different architecture is a very bad idea. It won't "hard-brick" your device, but certainly will have side-effects you won't like (e.g. the device might refuse to boot up at all – not sure what exactly will happen, as I was not yet bold enough to try; if you really want to know that, either try (not recommended if you don't know a way out then) or ask that as a separate question).
Concerning your real goal: As pointed out in my answer here, you can use Raccoon on your computer for that.
While the other question focuses on apps you've bought, Raccoon of course also works for free apps. For different device architectures, you will need to create different profiles: DummyDroid can create the required "GSF IDs for mock up devices" if you don't know the one of yours, based on the given device's build.prop
. If that doesn't work out, or you want to use the "real ID", please see my answer here on how to obtain it from your device (or from that of your cousin).
.apk
for some Intel device that has no Playstore access? It's no good idea to manipulate your device for that, as for the side-effects to be expected. – Izzy Aug 30 '16 at 10:01build.prop
via recovery or reflash the ROM. But again, please [edit] your question and add the background: What do you need that for? This is not a forum to discuss things – and I have good reason to believe this is a XY problem. What is your final goal? What do you need the Intel.apk
for? there might be other (and less dangerous) ways to achieve that. – Izzy Aug 30 '16 at 10:12build.prop
part: Please ask that as separate question. Q&A sites work best if you put each question in a separate question post. – Izzy Aug 30 '16 at 11:18