It's there some trick to installing Asphalt 6 on the fire? It says this game is not compatible to my device.
Sent from my Amazon Kindle Fire using xda premium
Edit your build.prop
go to root exploror (or any explorer you use) and then go to /system then build.prop
on the lines were it says "ro.product.model" put Galaxy Nexus and on ro.product.brand put google, then save it.
Daevionne said:
Edit your build.prop
go to root exploror (or any explorer you use) and then go to /system then build.prop
on the lines were it says "ro.product.model" put Galaxy Nexus and on ro.product.brand put google, then save it.
Click to expand...
Click to collapse
I have a similar issue except I don't receive a message. The game just closes as soon as I open it. I have all of those edits in the build.prop file.
Related
Ok, there are several threads alluding to installing the Android Market on your Kindle Fire, and this Guide will bring them all together for the EASIEST and MOST Successful process. Credit given to authors or other guides.
Android Market on Kindle Fire
Itching for a broader expanse of app selection on your rooted Kindle Fire? It is possible to install the Android Market, furthering your journey on the path of turning the Fire into a full fledged Android Tablet. Follow the tutorial.
Warning: NOT for the faint of heart.
As with any modification to system files, there is a chance you could cause damage to your device. Use at your own risk.
Prerequisites
Root your Kindle Fire
Download the following apks
GoogleServicesFramework.apk
Vending.apk (Latest Version 3.3.11)
See HERE for .apk downloads (complete GApps zip file)
Root Explorer App (or similar that lets you change ro/rw permissions)
Side Loading Apps activated on Kindle Fire
On the Kindle Fire Settings screen, go to “Device” and turn On “Allow Installation of Application From Unknown Sources”
Instructions
1. Transfer the .apk files to your Kindle Fire via PC / Mac (remember where you put them)
2. Open Root Explorer App, and navigate to the transferred .apk files
3. Select the GoogleServiceFramework.apk and install
4. When complete, click "Done" and return to the file location for Vending.apk
5. Long-press Vending.apk and select the "Move" option on pop-up menu
Navigate to /system/app folder
6. Change mount option from RO to RW (read-only to read-write)
Paste Vending.apk into the /system/app folder
7. Long-press Vending.apk and select "Permissions" from pop-up menu
Change permissions to match all other apps in this folder (rw-r--r--)
8. Install Vending.apk
9. Reboot your Kindle Fire
Once reboot is complete, select Market App and log-in as usual.
Enjoy!
You will most likely notice some familiar apps missing from the market, as this device is lacking certain hardware specifications. However, once custom ROMs start appearing for the Kindle Fire, it is a safe bet it will no longer be the case.
Also, the Market App will not show up in the default Amazon Launcher.
You will need to install an alternate launcher (ie Go Launcher EX, ADW).
Find instructions HERE.
For another option than installing an alternate option, check out this work around also!
Credits
JolleyBoy
mashi
And myself of course.
**Keep in mind, I'm NOT trying to step on toes in posting this guide...just creating a place for users to go and not have to sift through endless posts.**
Thank you! This works!
One thing I would add to your instructions before 8. Reboot is to install Market.
After installing the Android Market, will it still work if I unroot the Kindle Fire?
Jackalx said:
After installing the Android Market, will it still work if I unroot the Kindle Fire?
Click to expand...
Click to collapse
I imagine so, however I haven't tested it. Worst case scenario, you un-root...it doesn't work, then root again.
Let me know how it works out!
I hate to seem dumb, but where is Vending.apk? It's not in the gapps RAR file.
Every time I try to install the googleservicesframework.apk I get "Application Not Installed" any ideas?
Jackalx said:
After installing the Android Market, will it still work if I unroot the Kindle Fire?
Click to expand...
Click to collapse
Yes.
I rooted, installed Market and Calendar, then unrooted so I could use the video streaming. Market still works.
New market apk from tonight that includes google music store attached - can confirm it working following the same directions, at least for me.
ok having a problem, root explorer wont mount /system/app as R/W so I cant copy the vending.apk. any suggestions?
I don't think vending.apk is necessary. I didn't copy that over, and everything worked fine.
When I did copy it over, stuff started bugging out (instant video lagging (after unrooting), access to Amazon app store denied), so went back to deleting that file.
Are we not able to purchase apps through the google market once it installed?
I can download free stuff, but when I try to get a commercial app, it shows an error about not being able to purchase
I ran into this with movies in the market - but i can buy apps just fine - just tested.
DoubleByte said:
I hate to seem dumb, but where is Vending.apk? It's not in the gapps RAR file.
Click to expand...
Click to collapse
I got it out of the cyanogenmod 7 google apps zip. From this page :
http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
Sent from my Kindle Fire using Tapatalk
I'm having the issue moving the vender.apk - root explorer won't let me mount as r/w. Anyone have a quickfix for this?
nerdgirl said:
I'm having the issue moving the vender.apk - root explorer won't let me mount as r/w. Anyone have a quickfix for this?
Click to expand...
Click to collapse
One question, have you followed the steps?
"Prerequisites
Root your Kindle Fire"
before using Root Explorer?
Because if you've rooted it, then in root explorer, at the top should be a Mount R/w button you just press.
I AM rooted. I get the rw option and can actually change *some* directories to rw, but it won't allow me to change /system/apps. I have tried with terminal emulator as well, but get denied. WTF is going on?!?
I have superuser permissions set on root explorer and can write to most directories...
Help!
nerdgirl said:
I AM rooted. I get the rw option and can actually change *some* directories to rw, but it won't allow me to change /system/apps. I have tried with terminal emulator as well, but get denied. WTF is going on?!?
Click to expand...
Click to collapse
Feeling the pain here as well...
---------- Post added at 10:11 PM ---------- Previous post was at 09:40 PM ----------
Aha... finally got it to work using the Jackpal terminal emulator and the instructions in this post:
http://forum.xda-developers.com/showpost.php?p=19446504&postcount=66
Problems with kindle fire
Can you please help with kindle fire?
I did root it,then after that i did follow the step 1. Transfer the .apk files to your Kindle Fire via PC / Mac (remember where you put them)
2. Open Root Explorer App, and navigate to the transferred .apk files
3. Select the GoogleServiceFramework.apk and install
and then really it doesnt make sense all is written after that???
4. When complete, click "Done" and return to the file location for Vending.apk
5. Long-press Vending.apk and select the "Move" option on pop-up menu
Navigate to /system/app folder ( where is the move option on kindle fire? i triple check and doesnt exist)
6. Change mount option from RO to RW (read-only to read-write)
Paste Vending.apk into the /system/app folder
7. Long-press Vending.apk and select "Permissions" from pop-up menu
Change permissions to match all other apps in this folder (rw-r--r--)
8. Install Vending.apk
9. Reboot your Kindle Fire
I am stuck with the instructions please help.
Plus when i install the market after the framework i cant sign in on the market,no conection it says
To the above and anyone else having problems changing permissions with Root Explorer (I did, the button change to R/W did nothing at times) then try Super Manager, did the trick for me. Strangely once SM has changed permissions once in a session you can generally go back with Root Explorer and change any R/O -R/W you like.
Also "Move" comes up after a press of the file you wish to move.
Finally, I have a problem - I have installed vending.apk, permissions all ok etc. I can load and search the marketplace but when I try and download a file it hangs o waiting for download. This has happened on multiple apps and I've tried a couple of different vending files and a couple of installs. Any suggestions?
My only thought now is that since this is my first Android I don't currently have a device associated with my account. Any other thoughts?
I know I was half asleep the second time I installed market (after a system reinitialize) and ran the market installer but forgot to move it to /system/app and then compounded the mistake by leading the name be vending-1 instead of just vending. Only once I caught both mistakes and corrected them did market work properly. But it half worked until I fixed my mistakes. Perhaps you didn't copy to system like me or got permissions wrong?
Sent from my Kindle Fire using Tapatalk
So, now all of the US Galaxy Note II variants have a mod to enable fully working Google Wallet. What about us? Can we get Google Wallet working on the GT-N7100/GT-N7105? Our devices are so very similar to the US variants that if you changed the battery cover and the build.prop, you couldn't tell the two apart (Except for the VZW variant... Can anybody say FUGLY!). Anyway, we need to get on this. If someone with a working knowledge of Google Wallet is willing to take up the cause, I will help in any way I can. So come one people!! Let's get this working!!!
Sent from my GT-N7100 using XDA Premium HD app
Come on.... anyone!?!?!?
Sent from my GT-N7100 using XDA Premium HD app
google wallet is working fine on my n7100. just follow the instruction for tmobile note 2, and remember our model, name and device are different when you change them back in build.prop (in system instead of system/app)
Mister_Mxyzptlk said:
Come on.... anyone!?!?!?
Sent from my GT-N7100 using XDA Premium HD app
Click to expand...
Click to collapse
Are u able to add credit card that is registered outside of us?
Handwritten from my Note 2
These are the steps that worked for me following steps from the Verizon Note II thread.
How to Install Google Wallet on Samsung Galaxy Note II
http://forum.xda-developers.com/showthread.php?t=2031127&page=5
See post #237
================================================
I guess the 3rd times a charm, as I was finally able to get Wallet to successfully install and set-up on the Verizon Note 2 (yet I've haven't tested any purchases yet).
Here's what I did:
A) Downloaded the NoteII-lib_nfc-fix-r87.zip from the first post, unziped it, and placed it in the /sdcard.
B) Made backups of these files using Root Explorer (copy & paste them to your sdcard or extsdcard):
Nfc.apk, Nfc.odex NfcTest.apk and NfcTest.odex files from /system/app
libnfc.so, libnfc_jni.so, libnfc_ndef.so from /system/lib
nfc.smdk4x12.so from /system/lib/hw
nfcee_access.xml from /system/etc
C) After those 9 files are backed up, use root explorer to delete them.
Use as reference for step D:
http://forum.xda-developers.com/show...8&postcount=76
D) Then copy the NEW files from the NoteII-lib_nfc-fix-r87 folder on the sdcard to the appropriate folders /system/app, /system/lib, /system/lib/hw, /system/etc.
Be sure to long-press on each file after they are copied and change their Permission to Owner Read Write, Group Read, Others Read.
E) Use Root Explorer to backup (copy/paste) your build.prop file from /system
F) Then edit the build.prop in /system to have the lines below (and then save it):
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
Make sure the build.prop has the Permission set to Owner Read Write, Group Read, Others Read or the phone will boot-loop.
G) Restart phone.
Now run the Wallet app. If it says "This may take 5 minutes" and then force-closes (this happened to me), do the steps from:
http://forum.xda-developers.com/show...&postcount=160
After I removed the Wallet app, restarted phone, downloaded the Wallet from the app store, set it up, then removed the wallet app and coped the R87 Wallet back.
Once you have Wallet installed and fully functional, go back to the /system build.prop file and edit the three lines back to their original values:
ro.product.model=SCH-I650
ro.product.name=t0ltevzw
ro.product.device=t0ltevzw
======================================================
Next see post #160
http://forum.xda-developers.com/showpost.php?p=35092232&postcount=160
To anyone getting the app crashing at "This may take 5 minutes" here is how I fixed it:
1) Delete the Walltet apk from system/app
2) Edit your build.prob to be a Galaxy Nexus
3) Reboot
4) Grab legit Wallet from the app store
5) Set up the legit Wallet (it will work) then register a card. After it successfully registers the card wait a minute and it will say it has to reset the app. This will take forever, wait for it to finish.
6) Once you are prompted with a list of accounts to re-setup Wallet close the app
7) Delete the Wallet apk from data/app (DO NOT uninstall Wallet, JUST delete the apk) and put the modaco patched r87 into system/app and set permissions (notice the legit was in data but the new one goes in system)
8) Reboot device
9) Run Wallet and this time it should let you set everything up, even though you are now using r87 which previously crashed
10) Once Wallet is working and your cards are registered reboot and make sure it still works
11) If Wallet is now r87 and it still works after the reboot put your build.prop back the way you found it and enjoy!
easiest way is to follow this direction posted by paul over on modaco, all you have to do is install and go (no need to do anything else)
http://www.modaco.com/topic/354635-region-device-root-patched-google-wallet-apk-15-r87-v15/
I posted this because surprisingly I have not seen this post for our nexus 4. Thank this awesome guy from xda for creating this for all devices!!! Here's the link to his post and also here's some snapshots
http://forum.xda-developers.com/showthread.php?t=2143860
Oh if you didn't know you can pinch to zoom to do this awesome zoom effect. Try it out!! You have to flash through twrp or cwm. It will install the xperia launcher as well so if you want that aligned perfectly you have to edit your build prop. How to do that?
Easy!!
1st download es file explorer (its free)
2nd when you open es file explorer hit the menu key and tap settings
3rd scroll all the way down and click root settings and check all the boxes.
Now that you've done that, hit back until you get to a sign that pops up and says "press again to exit" then don't exit obviously.. You've just got full access to your files!! Meaning be careful which system files you touch! You only need to modify one. Trust me. It sounds hard but is a lot less complicated. Simply navigate to system/ then go all the way down to build.prop. simply tap on it and click es note editor. Then locate " ro.sf.lcd_density=320" then simply change the 320 to 340 and save. It will automatically create a back up build prop for you. Here's where you really need to watch out. Make sure after your done editing and saving your build.prop you TAP AND HOLD build.prop and scroll all the way down to properties and tap it. Then tap change and check all the boxes on the left and below write tap the top middle box. If your confused I posted a pic below... What your are doing here is setting permission to the file you just modified. Then now that you just set permission your good to reboot!!! After you reboot you just flash jb gapps and clear cache and dalvik cache. And your launcher is perfectly set. If you did not fix permissions the way the pic looks you won't boot up at all you'll only be able to fastboot. That's why I say its important to follow step by step. Also the reason I say flash gapps is because if you don't you won't be able to install certain apps in the play store (it'll say device not compatible). No more misaligned launcher!! If your don't like the launcher simply use titanium backup to remove it or search through file explorer. Bye all!!
Sent from my Nexus 4 using xda app-developers app
Cool.
[NEXUS⁴] [CARBON1.6] [MATR1X8] [TWRP]
If I remember from the Nexus 7 forums correctly, changing your build prop will cause future Android update to fail during installation. This looks awesome though.
It may cause problems with installation with modified changes
But that would just require you to go back to stock with our recovery tool. I never update my ROM straight through a custom rom. Or simply use your "back up build.prop" that I mentioned es explorer does automatically for you and rename that back up back to build.prop then delete modified build.prop. Of course always make sure you set your permissions even on the back up !
Sent from my Nexus 4 using xda app-developers app
dEris said:
Cool.
[NEXUS⁴] [CARBON1.6] [MATR1X8] [TWRP]
Click to expand...
Click to collapse
Thanks
Sent from my Nexus 4 using xda app-developers app
So this is a problem I've had basically since day one with my Nexus 7. No matter what file explorer I use, I can not edit anything in the root directories. Unable to save build.prop edits for example. I am assuming it is a permission thing but I have no idea exactly what I am doing wrong or how to fix it. Any help is appreciated.
Sent from my Nexus 7 using Tapatalk
Are you rooted? If you are - check to see if you are in read only mode in your file manager(s)
Besides requiring root, apps like ES File Explorer need to have root access turned on. Root Explorer needs a directory mounted as R/W.
Best practice, anyway, is to copy a file (especially build.prop) to a regular directory under /sdcard, edit it there, rename the original, then copy back the modified file.
I managed to figure it out. Was using cm file explorer and root browser. Got root browser working by changing permissions on the system folder.
I always copy files into the internal storage before editing. Thanks for the replies.
Sent from my Nexus 7 using Tapatalk
So I have successfully rooted my wife's TMobile D851, which was verified using joeyk root checker app from the playstore, but I am unable to edit the build.prop so I can hide the nav bar and install lmt launcher for pie control. Am I missing something? I have no issue with my Nexus 5 or any other phone I've tinkered with and I am drawing a blank on what the issue is.
I'm hoping it's something super obvious that I missed and I'll feel stupid after I'm told what I am doing wrong.
JeauxAdam said:
So I have successfully rooted my wife's TMobile D851, which was verified using joeyk root checker app from the playstore, but I am unable to edit the build.prop so I can hide the nav bar and install lmt launcher for pie control. Am I missing something? I have no issue with my Nexus 5 or any other phone I've tinkered with and I am drawing a blank on what the issue is.
I'm hoping it's something super obvious that I missed and I'll feel stupid after I'm told what I am doing wrong.
Click to expand...
Click to collapse
the build.prop is huge for the lg g3(to big for some apps) try copying it to your pc and editing it there with notepad++ end then placing it back and set permissions(important or you will brick)
suljo94 said:
the build.prop is huge for the lg g3(to big for some apps) try copying it to your pc and editing it there with notepad++ end then placing it back and set permissions(important or you will brick)
Click to expand...
Click to collapse
I had thought about that so before I made this post I did a adb pull /system/build.prop and edited it with notepad++, as you suggested, but then I am unable to actually push it back. Can I just put it into a folder on my phone and then use some root file browser like ES or whatever and set permissions that way?
JeauxAdam said:
I had thought about that so before I made this post I did a adb pull /system/build.prop and edited it with notepad++, as you suggested, but then I am unable to actually push it back. Can I just put it into a folder on my phone and then use some root file browser like ES or whatever and set permissions that way?
Click to expand...
Click to collapse
place it in /system then in es enable root explorer then click your newly added build.prop long click it then select properties then change permissions to
Code:
yes yes /
yes / /
yes / /
suljo94 said:
place it in /system then in es enable root explorer then click your newly added build.prop long click it then select properties then change permissions to
Code:
yes yes
yes / /
yes / /
Click to expand...
Click to collapse
Your description of the permissions is a little weird but I think I can figure it out. I imagine it's the same permissions the current build.prop has? My wife has now taken her phone and gone to bed so I will have to try this tomorrow. Thank you very much for your assistance!