Database Users

[Q] How to make NC appear as something else? (Eg:- Xoom, Nexus)

Guys,
I following the Verygreen C7 SD Card install method to install CM7 on an 8GB SD Card and I'm using it with my Nook Color 1.4.2. Using the SD Card I'm able to run Gingerbread without any problems.
The one problem I've noticed is that some of the Apps in Google Play Store don't appear compatible. The Google Play Store reads the device as "BN Nook Color" and for some apps it says "This device is not compatible with this app" -- something like that.
I've seen threads where people have changed some property in their NC (I think bild.prop or something) that allows them to show their NC as something other then BN Nook Color, like Samsung Galaxy Tab or Nexus S or Motorola Xoom or something. I cannot find instructions to do this.
How exactly do you this? Will this allow me to pick up more Apps from the Google Play Store?
Thanks!!

Use the IMEI Generator in my sig... it will allow you to change device in build.prop for some of the most common.

DizzyDen said:
Use the IMEI Generator in my sig... it will allow you to change device in build.prop for some of the most common.
Click to expand...
Click to collapse
Excellent! I will definitely give this a shot. Thank you so much for replying.

DizzyDen said:
Use the IMEI Generator in my sig... it will allow you to change device in build.prop for some of the most common.
Click to expand...
Click to collapse
I downloaded your software, but I'm not quite sure I'm understanding exactly what I need to do and how to use it.
I do have a working USB ADB connection; and I really just want to make my NC appear as a Galaxy Tab (Which I see is in the list of devices) ... do you have instructions for a n00b on how to go about doing this?
Sorry for the lack of know-how. Thanks again.

Sorry if its too late, but try this app:
I used this on my Kindle Fire and it changed the build.prop to another device. Sadly, I can't seem to get Google Play to see it as a Nexus S...

Just today I noticed a bug in the IMEI Generator that causes it to not update build.prop when using in-place updates... that will be fixed shortly...
In the meantime if you want to make the change to build.prop it is really easy to do...
adb pull /system/build.prop
edit build.prop with notepad+ or something that will not convert it to dos/windows type of text... carriage return/line feeds get hosed if you use normal notepad
the lines you want to chage are:
for Samsung GalaxyS
ro.product.model=NC_CM7 (or SCH-I500 per manufacturer)
ro.product.device=GalaxyS
ro.product.manufacturer=Samsung
ro.build.description=passion-user 2.3.6 GRK39F 189904 release-keys
for Samsung Galaxy Tab
ro.product.model=NC_CM7 (or SPH-P100 per manufacturer)
ro.product.device=SPH-P100
ro.product.manufacturer=Samsung
ro.build.description=passion-user 2.3.6 GRK39F 189904 release-keys
After above edits...
adb shell busybox remount
adb push build.prop /system
reboot Nook and wait... initial boot takes a while.
The entries for the GalaxyS are what use with CM7 on my Nook... it registers as a Samsung GalaxyS model NC_CM7 in Google Play Store... the Galaxy Tab entries are compiled from user suggestions and information from my GalaxyS phone modified to what I think the Galaxy Tab would use.
Hopefully this information is helpful.
If anyone will provide me information regarding Nexus S in the thread in my signature to have devices add to IME Generator... I will GLADLY include it in the devices.dat file... a new one is going to be uploaded very soon.

DizzyDen said:
for Samsung Galaxy Tab
ro.product.model=NC_CM7 (or SPH-P100 per manufacturer)
ro.product.device=SPH-P100
ro.product.manufacturer=Samsung
ro.build.description=passion-user 2.3.6 GRK39F 189904 release-keys
Click to expand...
Click to collapse
Dizzy,
Thanks for the update; I had used your Generator to make my NC appear as Samsung Galaxy Tab ... which it does in the market. I did use the "in-place" update.
I went ahead & used adb pull to get my build.prop, but I noticed that in my build.prop I already have the EXACT same information as above (Samsung Galaxy Tab). That tells me that your Generator did indeed insert the correct information in build.prop ... since I didn't put it there manually. I didn't need to change or modify anything.
Unfortunately, my problem persists. There are many apps, especially Tablet apps, that still come up as "This app is incompatible with your SPH-P100 device". I'm not sure why!!
Thanks.

Is this to fool Market/Play Store, the app, or both?
Is this deception needed just to get Google to allow one to install the apps in question, or do the apps themselves need to be fooled when they are installed from their .apk files and/or when they run?

aarons510 said:
Is this deception needed just to get Google to allow one to install the apps in question, or do the apps themselves need to be fooled when they are installed from their .apk files and/or when they run?
Click to expand...
Click to collapse
I think the apk files will use build.prop to figure out what device they are running on. I remember using this method to get netflix working back in the day.

[Q] How to install standalone Play store?

Hi everyone,
After flashing a new ROM for my Nexus7 (CM, PA, etc) I want to avoid installing the standard gapps zip with all the Google software, but instead I only want the Play store.
I have searched the XDA forums and I struggle to find anything that precisely solve this issue. It seems that the general consensus when it comes to minimal systems is to install everything first and only then remove the bloat either directly from the shell or via TB, sometimes proceeding with trial and error.
Is there any way, or anyone willing to detail the exact dependencies needed for the Play store apk to work when installed on its own?
Thanks!

What's the problem in manually deleting the unneeded Google apps that you are not going to use and live happily ever after?
Of vourse if you change ROMs often - that might be a trouble, but if you intend to stay with one and only ROM - then I guess it shouldn't be that hard, right?

Fatal1ty_18_RUS said:
What's the problem in manually deleting the unneeded Google apps that you are not going to use and live happily ever after?
Of vourse if you change ROMs often - that might be a trouble, but if you intend to stay with one and only ROM - then I guess it shouldn't be that hard, right?
Click to expand...
Click to collapse
Not so much of a problem in the sense that it is blocking me, there are however some points that motivate me in knowing how to do it properly, namely:
I have a general Interest in how the interdependencies between the OS and Google apps is actually working. I've been using GNU/Linux for more than 15 years and I grew the habit to like to know what I am installing on my machines.
Frequent ROM updates make manual removal of items quite inefficient. Maybe a backup app could help here but that feels clunky and has the risk to introduce quite some mess when the system receives major updates that would break the backup.
The time to go through manual removal though trial and error is possibly the same that it takes to start this thread, bump it and hopefully gather enough interests so that more people will benefit from it.

I also reacted in other topic. Somehowe i could not react here but now it does.
Not my own idea, but it did work for me on my desire s. Open up the zip and read the next:
I have made a minimal install sufficient to get Contacts and Calendar sync + Google Play.
Then copy with a root explorer and set permissions to 644 of:
GoogleCalendarSyncAdapter
GoogleContactsSyncAdapter
GoogleLoginService
GoogleServicesFramework
Phonesky
Later installed as a regular apk Gmail2 and GenieWidget
Sent from my Nexus 7 using xda app-developers app

Auke11 said:
I also reacted in other topic. Somehowe i could not react here but now it does.
Not my own idea, but it did work for me on my desire s. Open up the zip and read the next:
I have made a minimal install sufficient to get Contacts and Calendar sync + Google Play.
Then copy with a root explorer and set permissions to 644 of:
GoogleCalendarSyncAdapter
GoogleContactsSyncAdapter
GoogleLoginService
GoogleServicesFramework
Phonesky
Click to expand...
Click to collapse
Thanks for the hint!
To get the Play store working I only had to install Phonesky, GoogleServicesFramework and GoogleLoginService.
Now I am trying to figure out what is needed to get the quick settings menu. The latter only appears when the gapps are installed.

ugrnm said:
Thanks for the hint!
To get the Play store working I only had to install Phonesky, GoogleServicesFramework and GoogleLoginService.
Now I am trying to figure out what is needed to get the quick settings menu. The latter only appears when the gapps are installed.
Click to expand...
Click to collapse
Hi OP
Could you mention the details of how you got the store working? Eg, where did you download the service files from and where did you copy them in your phone.
Thanks
Anupam

lovethenexus said:
Hi OP
Could you mention the details of how you got the store working? Eg, where did you download the service files from and where did you copy them in your phone.
Thanks
Anupam
Click to expand...
Click to collapse
As instructed, you download the gapps zip, remove the unwanted apks, and then flash in recovery.
Sent from my Nexus 7 using Tapatalk HD

I have a PA 3.1 ROM that shows the quick settings without GApps. However, the settings don't appear using a swipe down or through the button in the navigation area. They appear specifically in the expanded desktop mode only. Not sure why, but it doesn't look like an issue related to GApps. Let me know if you were able to validate the link between GApps and quick settings though.
ugrnm said:
Thanks for the hint!
To get the Play store working I only had to install Phonesky, GoogleServicesFramework and GoogleLoginService.
Now I am trying to figure out what is needed to get the quick settings menu. The latter only appears when the gapps are installed.
Click to expand...
Click to collapse

ugrnm said:
Thanks for the hint!
To get the Play store working I only had to install Phonesky, GoogleServicesFramework and GoogleLoginService.
Now I am trying to figure out what is needed to get the quick settings menu. The latter only appears when the gapps are installed.
Click to expand...
Click to collapse
Hi OP
I had been wondering why I had not been able to get the quick settings (the tiles in the status bar) to appear.
Btw, I'm using Rootbox on my Galaxy S3 (GT-i9300).
Your comment above told me that something from was gapps missing, so I installed the full gapps package and the quick settings work.
I reset/wiped my phone for further testing...
Long story short, I discovered Google's Setup Wizard was the culprit. Once I had rebooted and completed Google's setup wizard my quick settings tiles started working. I have no idea why this affects the tiles
GoogleLoginService was required for SetupWizard. I removed both afterwards with no problems.
Sorry for bumping an old thread, I was searching for info on the play store when I found this thread. Doubt I would have found this info otherwise.

Thanks for the bump, I gave up eventually, but what you found out is great. I'll give it a try!
These days I'm also trying to figure out how painful/feasible it would be to simply not use any of the gapps and just rely on alternative repos such as F-droid.

ugrnm said:
Thanks for the bump, I gave up eventually, but what you found out is great. I'll give it a try!
These days I'm also trying to figure out how painful/feasible it would be to simply not use any of the gapps and just rely on alternative repos such as F-droid.
Click to expand...
Click to collapse
Sorry to dig up old threads, hopefully one of you is still around,
I've put Cynogenmod on my xperia, but forgot to install google play, I installed it from an apk using the terminal but it crashes, obviously needs some other google services to work. I have a the google apps zip file but the app names are very different...
ChromeBookmarksSyncAdapter.apk
GalleryGoogle.apk
GenieWidget.apk
Gmail.apk
GoogleBackupTransport.apk
GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk
GoogleFeedback.apk
GoogleLoginService.apk
GooglePartnerSetup.apk
GoogleQuickSearchBox.apk
GoogleServicesFramework.apk
GoogleTTS.apk
MarketUpdater.apk
MarketUploader.apk
NetworkLocation.apk
OneTimeInitializer.apk
SetupWizzard.apk
Talk.apk
Vending.apk
VoiceSearch.apk
I only want google Play and gmail, I have flashed Cyanogenmod mainly to "ungoogle" my phone but I do want an easy way to install new apps.
Any ideas on what the equivolent to Phonesky will be in the list above?

Phonesky, GoogleServicesFramework and GoogleLoginService were enough for < cm 10.2
But with android 4.4 cm11 , it doesn't work anymore.
'there was a problem communicating with google servers'
any tried a standalone market install on kitkat?
---------- Post added at 04:07 PM ---------- Previous post was at 03:50 PM ----------
whitenight639 said:
Sorry to dig up old threads, hopefully one of you is still around,
I've put Cynogenmod on my xperia, but forgot to install google play, I installed it from an apk using the terminal but it crashes, obviously needs some other google services to work. I have a the google apps zip file but the app names are very different...
ChromeBookmarksSyncAdapter.apk
GalleryGoogle.apk
GenieWidget.apk
Gmail.apk
GoogleBackupTransport.apk
GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk
GoogleFeedback.apk
GoogleLoginService.apk
GooglePartnerSetup.apk
GoogleQuickSearchBox.apk
GoogleServicesFramework.apk
GoogleTTS.apk
MarketUpdater.apk
MarketUploader.apk
NetworkLocation.apk
OneTimeInitializer.apk
SetupWizzard.apk
Talk.apk
Vending.apk
VoiceSearch.apk
I only want google Play and gmail, I have flashed Cyanogenmod mainly to "ungoogle" my phone but I do want an easy way to install new apps.
Any ideas on what the equivolent to Phonesky will be in the list above?
Click to expand...
Click to collapse
Vending = market = phonesky

Stand Alone Play Store Installation
ugrnm said:
Hi everyone,
After flashing a new ROM for my Nexus7 (CM, PA, etc) I want to avoid installing the standard gapps zip with all the Google software, but instead I only want the Play store.
I have searched the XDA forums and I struggle to find anything that precisely solve this issue. It seems that the general consensus when it comes to minimal systems is to install everything first and only then remove the bloat either directly from the shell or via TB, sometimes proceeding with trial and error.
Is there any way, or anyone willing to detail the exact dependencies needed for the Play store apk to work when installed on its own?
Thanks!
Click to expand...
Click to collapse
-----------------------------------------------------------------
Hi, im just a newbie here but i just want to share my experience in installing playstore.apk and you're right. Its trial and error.
At 1st, i zip signed the playstore.apk and tried to install it in cwm recovery. Yes it was installed but when i reboot my system, it pops up a toast that playstore stopped. i pressed ok and it pops again everytime. 1st failure
2nd, i tried to put the playstore.apk directly in the device/system/priv-app folder then install it normally. it was installed again but when i reboot my system, it crashes again. 2nd failure.
then here is the 3rd and final one and i said to myself that if this will not work again, maybe playstore.apk isnt a stand alone app. so here is what i did. i put the playstore.apk file again in the device/system/priv-app folder and this time i renamed it as "Phonesky" just like in stock roms. i just leave it there exit the file explorer then reboot system. And suddenly, it works and till now, it still works. Maybe it was luck but i'm just sharing my experiences. Im not saying that it will work 100% but maybe give it a try then. But make sure that you already back up everything. Thanks and God bless.

Hi guys,
I have installed Cyanogen 12 on my Wiko Darkmoon do set myself free from Google and I am happy with that... But unfortunately I still need to used Google Calendar (because my wife does not want to change so far and we are using shared calendar big time).
I don't want to install gapps but I am ok to install the minimum apk to have Google calendar sync working on my phone. Based on what I red on that topic, I came to install (may be not in this order) :
GoogleServicesFramework.apk
GoogleLoginService.apk
GoogleCalendarSyncAdapter.apk
Unfortunately, when trying to register a Google account, I get the following message (translated from French, maybe inaccurate sorry) : " Impossible to connect. A communication problem with Google servers occurred. Please try later." with a next button leading always to the same message.
I cannot figured out if something is missing neither if it is possible to do so. I used adb logcat to get some log but I am not familiar at all with it but maybe the answer is in this part :
Code:
I/Timeline( 9816): Timeline: Activity_idle id: [email protected] time:46061804
I/ActivityManager( 535): Displayed com.google.android.gsf.login/.LoginActivityTask: +244ms
I/Timeline( 535): Timeline: Activity_windows_visible id: ActivityRecord{44c1813 u0 com.google.android.gsf.login/.LoginActivity t218} time:4
V/GLSActivity( 9816): Error in
V/GLSActivity( 9816): java.lang.NullPointerException: Attempt to invoke interface method 'java.util.Iterator java.util.List.iterator()' on a
V/GLSActivity( 9816): at com.google.android.gms.auth.firstparty.dataservice.GoogleAccountDataServiceClient.c(Unknown Source)
V/GLSActivity( 9816): at com.google.android.gms.auth.firstparty.dataservice.GoogleAccountDataServiceClient.a(Unknown Source)
V/GLSActivity( 9816): at com.google.android.gms.auth.firstparty.dataservice.GoogleAccountDataServiceClient.signIn(Unknown Source)
V/GLSActivity( 9816): at com.google.android.gsf.loginservice.GLSHelper.blockingAddWithPassword(GLSHelper.java:281)
V/GLSActivity( 9816): at com.google.android.gsf.login.LoginActivityTask$1.runInBackground(LoginActivityTask.java:147)
V/GLSActivity( 9816): at com.google.android.gsf.login.CancelableCallbackThread.run(CancelableCallbackThread.java:37)
I/Timeline( 9816): Timeline: Activity_launch_request id:com.google.android.gsf.login time:46061909
I/ActivityManager( 535): START u0 {cmp=com.google.android.gsf.login/.ShowErrorActivity (has extras)} from uid 10079 on display 0
V/WindowManager( 535): addAppToken: AppWindowToken{1d261f3f token=Token{21b7cf5e ActivityRecord{445c099 u0 com.google.android.gsf.login/.Sh
I/art ( 9816): Background sticky concurrent mark sweep GC freed 14973(933KB) AllocSpace objects, 2(32KB) LOS objects, 18% free, 3MB/4MB,
I/MaliEGL ( 886): [Mali]window_type=1, is_framebuffer=0, errnum = 0
I/MaliEGL ( 886): [Mali]surface->num_buffers=4, surface->num_frames=3, win_min_undequeued=1
I/MaliEGL ( 886): [Mali]max_allowed_dequeued_buffers=3
May be this is not the right topic to post that but this is the closer I have find.

[Guide] Google Wallet [100% Working]

This is a guide on how I got Google Wallet working on my SGN2 (N7105) in New Zealand (which is not supported by Google Wallet at the moment).
Should work for all variants.
REQUIREMENTS:
1: Samsung Galaxy Note 2 (Should work with all variants) TESTED ON N7105
2: Root Access
3: MarketEnabler from here
4: Newest modded Wallet.apk from here
5: Root Explorer from PlayStore/Market
Guide
Step 01: Clear data for Google PlayStore/Market (and any updates)
Step 02: Change build.prop details to this - (use root explorer)
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
Make sure it has correct permissions still!!
Step 03: Reboot
Step 04: Use MarketEnabler and set your market to US T-Mobile
Step 05: Push the modified Wallet.apk to \system\app and make sure to give it correct permission!!
Step 06: Open wallet
Step 07: Set up wallet
Step 08: Reboot
Step 09: Check wallet is still working
Step 10: Change build.prop values back to what they were before you changed them
Step 11: Reboot
Step 12: Check wallet is still working
ENJOY!!
All this information was taken from different threads and I just pulled the info together for what worked for me - none of it is my work.
Thanks to everyone involved in getting this working on the SGN2.
I may upload a video on how to do it...so more to come!!!

Thanks dude...i appreciate it.
Well done.
Keep up the good work..and keep us always up 2 date....nice share.
Sent from my GT-N7100 using xda premium

Hi thanks for the info as anyone tried this and confirm it works
Sent from my GT-N7100 using xda premium

Setup completed
Managed to setup Google wallet as said. Important! Rem to set permission before reboot. I got bootloop but luckily restored via backup. Not tried paying with it yet. But Good work! Will update if payment successful

kelvinator said:
Managed to setup Google wallet as said. Important! Rem to set permission before reboot. I got bootloop but luckily restored via backup. Not tried paying with it yet. But Good work! Will update if payment successful
Click to expand...
Click to collapse
Thanks, made that part red in the OP now
Cheers,
Evil.

Does sbi maestro debit card work with wallet??
Edit sry wrg thread
Sent from my GT-N7100 using Tapatalk 2

hi, wallet is working fine when i change the prop value to the one you stated before. but when i change it back to galaxy note 2 prop before, the wallet seems to be not working saying not yet available for your device or mobile network. is it okay to just leave it at galaxy nexus?

Working in the uk? Can we add cards
Sent from my GT-N7105 using Tapatalk 2

I have tried this about 30 timed now and it gets stuck at the same point every single time:
"Setting up Wallet for purchases"
Anyone have any ideas?
Rooted stock 4.1.2 n7100 uk model unlocked.
Thanks.

Managed to sort it.
Heres how I fixed it... hopefully it will help anyone else with the same problem.
1. Follow the instructions in the op.
2. Download google wallet 1.5-r87-v15 NOT the newer version or any modded version
3. Continue with the instuctions in the op.
If you installed the newer version ending in v13, then 1st clear the cache and data file and stop the program. Then using titanium backup, uninstall it.
Restart your phone and then start the process again using the older version.
Once installed, search google for google wallet, click the play store link and open with play store.
Scroll down until you see a tick box saying allow automatic updates and untick it.
Restart your phone and set it up.
Sent from my Galaxy Nexus using xda app-developers app.
It's not a galaxy nexus, it's just a modded n7100.

There is not a modded wallet in link at prereq step 4 any more. Paul has redone it using an exposed framework hack to patch out the region and device checks now.
I did manage to get wallet working using an older version like previous poster said but I cant setup any cards, I am in the UK.
Is anyone actually able to add cards in a region that google does not support and able to purchase anything using NFC because thats the goal for me, not just to see what I have bought at the play store?
Does anyone have links for modded wallet apks that work, or is it best to get the latest from the market, use the framework to patch out the checks and then convert to a system app?
The latest from the playstore/market not seem to work, it get disabled/frozen when you reboot and hangs at "Setting up Wallet for Purchases" stage after you enable/defrost it.
This is anoying, visa were supposed to be rolling out NFC for purchases, they trialled it at the olympics last year by giving all the competitors smart phones with NFC for payments, so far nothing has happened.
Google are dragging their feet about releasing it officially here in the UK.
AFAIK google still checks the region the card is registered in, so unless you have a card from a region that is supported it wont work.
For now I've given up, I dont want to screw up my secure element on my phone, reset wallet from settings before uninstalling it is supposed to protect against this.

scote said:
There is not a modded wallet in link at prereq step 4 any more. Paul has redone it using an exposed framework hack to patch out the region and device checks now.
I did manage to get wallet working using an older version like previous poster said but I cant setup any cards, I am in the UK.
Is anyone actually able to add cards in a region that google does not support and able to purchase anything using NFC because thats the goal for me, not just to see what I have bought at the play store?
Does anyone have links for modded wallet apks that work, or is it best to get the latest from the market, use the framework to patch out the checks and then convert to a system app?
The latest from the playstore/market not seem to work, it get disabled/frozen when you reboot and hangs at "Setting up Wallet for Purchases" stage after you enable/defrost it.
This is anoying, visa were supposed to be rolling out NFC for purchases, they trialled it at the olympics last year by giving all the competitors smart phones with NFC for payments, so far nothing has happened.
Google are dragging their feet about releasing it officially here in the UK.
AFAIK google still checks the region the card is registered in, so unless you have a card from a region that is supported it wont work.
For now I've given up, I dont want to screw up my secure element on my phone, reset wallet from settings before uninstalling it is supposed to protect against this.
Click to expand...
Click to collapse
I agree!
I am from Australia and none of these methods work. I have tried flash and unflashing, clearing system, cache everything.
Newer version doesn't get past the setting up wallet for purchases and using the old apps gets stuck at adding my Mastercard.
Using the Omega ROM

If they simply accepted paypal we wouldn't hace this problem but google don't want it to be easy do they?
Sent from my Galaxy Nexus using xda app-developers app

[Guide] Google Wallet working on Xperia S running DooMLoRD pre-rooted 6.2.B.0.211 (JB
[Guide] to get Google Wallet working on Xperia S running DooMLoRD pre-rooted 6.2.B.0.211 (Jelly Bean Rom) Android 4.1.2 in New Zealand
I want to start by saying thanks to evilbarcode best post out there However i had to do a few different things to get google wallet 100% work on DooMLoRD pre-rooted 6.2.B.0.211 (Jelly Bean Rom) Android 4.1.2
REQUIREMENTS:
1: Xperia S running DooMLoRD pre-rooted 6.2.B.0.211 (Jelly Bean Rom). A similar method would probably work for others.
2: Root Access
3: MarketEnabler from here
4: Root Explorer from PlayStore/Market
5. BACK UP! use Titanium Backup ★ root from the play store if you have no idea how to back up you phone. this will save you a lot of time if something goes wrong.
Guide
1) download the latest google wallet app from the xda post "Google wallet fix for SGS3 US variants AT&T, T-MOBILE, US Cellular, VERIZON, etc". usecom.google.android.apps.walletnfcrel.modaco.1.6-R96-v13.zip - [Click for QR Code] (4.60 MB, 1781 views) which is/was the latest and put the
2) Use root explorer and mount as r/w. you must mount as r/w (it is an option in root explorer. look and you will find it)
3) go to /system/ and look for build.prop
4) open with text editor in Root explorer
5) within the file, search look for ro.xxxx, not ro.sem.xxx. look for exactly below.
so Only change the ro.product. fields here. so it should look like
ro.product.brand=SEMC
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
ro.build.tags=release-keys
you will also notice that ro.product.model= doesnt exist. ADD IT!
Note: If you stuff this part up you will probably get a boot loop (i did first time) and then you would have been wishing you backed up
6) Use MarketEnabler and set your market to US T-Mobile
7)put the google wallet application from the zip file from prereq step 1 to /system/apps and set permission to 644. if you dont under stand what the numbers mean google it.
8) go to setting,more and check nfc and under wallet select google
9) reboot
10)make sure you clear all goolge wallet ap data and uninstall any previous versions of google wallet
11) install the app you have just put in /system/apps
12) open the app
14) after you get google wallet to work then launch root explorer
15) go to /system and rename the build.prop to build.prop.ori
16) rename build.prop.bak to build.prop
17) the last 3 steps will stop your phone from thinking its a Galaxy Nexus
18) reboot
Done!
Notes This is not required for the app but usefull. Boot to recovery enabled. use X-Parts from the play store and also install doomrecovery based on clockworkmod recovery on sony xperia s. I wouldnt find the [Xperia S] DooMKernel (v01) on that site and ended up getting version 4 from another page. also if you run version 4 dont install the modules. you don't need to and when i did it messed up my wifi.
Note: for DooMLoRD pre-rooted 6.2.B.0.211 (Jelly Bean Rom) i couldn't boot into recovery for some reason which is a pain in the ass but the above works.
I would add links if i could but i am new to xda
My problem
The app works fine and I have my kiwibank visa debit card loaded onto it (which is a new zealand visa debit card). I went into countdown (a supermarket if your not in new zealand which supports contactless payments) . I put my phone up the the terminal and my phone vibrates and says processing the eftpos machine says processing then my phone and the machine say declined. Not because i am poor . Then the eftpos machine says please contact your bank.
Can anyone shed some light on this?
does the card loaded onto my google wallet account have to support contactless payment?
my speculation is that kiwibank dont support visa paywave only mastercard paypass and i dont have a mastercard paypass card, so i am thinking that i might need to enable contactless payment with my bank account.

Chillerhippie said:
I have tried this about 30 timed now and it gets stuck at the same point every single time:
"Setting up Wallet for purchases"
Anyone have any ideas?
Rooted stock 4.1.2 n7100 uk model unlocked.
Thanks.
Click to expand...
Click to collapse
This took AGES! to work for me. it was sitting on "Setting up Wallet for purchases" for maybe 5 to 10 minutes but it eventually worked !
just wait, then wait some more. I have got it fully working twice just to give you some confidence and i live in new zealand.

Google check what country the card is registered in, or so I am lead to believe by other posts. If the card is from an unsupported country it wont work. If NZ is an unsupported country this would tend to seem like that the country check is not an issue now, as you got as far as attempting payment.
Sent from my Transformer Prime TF201 using Tapatalk 4 Beta

Build.prop

Anyone have any luck modifying the build.prop to install (supposedly) incompatible apps from the market?
If so, what lines did you edit? And to what?
Thanks

philhachey said:
Anyone have any luck modifying the build.prop to install (supposedly) incompatible apps from the market?
If so, what lines did you edit? And to what?
Thanks
Click to expand...
Click to collapse
I had luck in the previous build in modifying the build.prop. After modifying it to a nexus 9, I was able to install non-TV apps. However, when I modified it, the leanback play store disappeared.... I was stuck with the traditional play store you see when you use a tablet or phone. It was really clunky to navigate & I had to use my keyboard/mouse.
I modified:
ro.product.device=
ro.product.manufacturer=
ro.product.model
ro.build.fingerprint=

I had been using the Market Helper app on my Nexus Player to simulate other devices and providers to bypass the Play Store restrictions. It worked fine on the NP running 5.0, but it crashes on 5.1. I hope someone finds a way to bypass this market restriction and a way to re-arrange the icons on the Leanback Launcher.

[Guide] Convert Shield Tablet into a dedicated Android TV

What works
Leanback Launcher
Leanback App Buttons (you may still want Sideload Launcher for some things)
Leanback Recommendations
HDMI-CEC (insofar as my TV supports it YMMV)
Shield Controller, including right thumbstick as mouse
Ten Foot experiences for applications that check for it
What doesn't work
Cast Receiver
Probably other things, this is a work in progress
What's needed
ADB access - If you don't have the Android SDK you can just use Minimal ADB and Fastboot
Stock 5.0 OTA (Android 7.0 Nougat) - I don't know how necessary this is but it's what I used.
Root
TWRP or some means of flashing a zip
Open GApps arm tvstock
Step 1 - Debloat
First we need to get rid of a number of things that we won't need, or will get in the way. Use debloat.zip for this. I actually like to run this initially, as well as after Gapps are installed. The script file inside is copied in the spoiler below.
Code:
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
ui_print("System app removals");
delete_recursive("/system/priv-app/BackupRestoreConfirmation");
delete_recursive("/system/priv-app/BlockedNumberProvider");
delete_recursive("/system/priv-app/ConfigUpdater");
delete_recursive("/system/priv-app/CalendarProvider");
delete_recursive("/system/priv-app/Contacts");
delete_recursive("/system/priv-app/ContactsProvider");
delete_recursive("/system/priv-app/DocumentsUI");
delete_recursive("/system/priv-app/GmsCore");
delete_recursive("/system/priv-app/GoogleBackupTransport");
delete_recursive("/system/priv-app/GoogleFeedback");
delete_recursive("/system/priv-app/GoogleLoginService");
delete_recursive("/system/priv-app/GoogleOneTimeInitializer");
delete_recursive("/system/priv-app/GooglePartnerSetup");
delete_recursive("/system/priv-app/GoogleServicesFramework");
delete_recursive("/system/priv-app/MmsService");
delete_recursive("/system/priv-app/Phonesky");
delete_recursive("/system/priv-app/SetupWizard");
delete_recursive("/system/priv-app/TegraOTA");
delete_recursive("/system/priv-app/TeleService");
delete_recursive("/system/priv-app/Telecom");
delete_recursive("/system/priv-app/Velvet");
delete_recursive("/system/priv-app/NvLauncher");
delete_recursive("/system/priv-app/NvCustomize");
#delete_recursive("/system/priv-app/NvRpxService"); needed for controller pairing
delete_recursive("/system/priv-app/nvlasso");
delete_recursive("/system/priv-app/shield_platform_analyzer");
delete_recursive("/system/priv-app/shieldcustomize");
delete_recursive("/system/priv-app/Katniss");
delete_recursive("/system/app/CalendarGoogle");
delete_recursive("/system/app/Chrome");
delete_recursive("/system/app/CloudPrint");
delete_recursive("/system/app/DeskClockGoogle");
delete_recursive("/system/app/Drive");
delete_recursive("/system/app/ExactCalculator");
delete_recursive("/system/app/FaceLock");
delete_recursive("/system/app/Gmail2");
delete_recursive("/system/app/GoogleContactsSyncAdapter");
delete_recursive("/system/app/GooglePrintRecommendationService");
delete_recursive("/system/app/GoogleTTS");
delete_recursive("/system/app/Hangouts");
delete_recursive("/system/app/JusWrite");
delete_recursive("/system/app/Maps");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/PrintSpooler");
delete_recursive("/system/app/SoundRecorder");
delete_recursive("/system/app/Tn8Tdc");
delete_recursive("/system/app/Videos");
delete_recursive("/system/app/Write");
delete_recursive("/system/app/idsmonitor");
delete_recursive("/system/app/stylusmobile-oem");
delete_recursive("/system/app/talkback");
delete_recursive("/system/app/trine2");
delete_recursive("/system/app/Twitch");
delete_recursive("/system/app/YouTube");
delete_recursive("/system/app/Music2Pano");
delete_recursive("/system/app/VideosPano");
delete_recursive("/system/vendor/app/CalibNotifier");
delete_recursive("/system/vendor/app/ConsoleSplash");
#delete_recursive("/system/vendor/app/ConsoleUI");
delete_recursive("/system/vendor/app/NvAndroidOSC");
delete_recursive("/system/vendor/app/NvBenchmarkBlocker");
delete_recursive("/system/vendor/app/NvCPLUpdater");
delete_recursive("/system/vendor/app/NvCamera");
delete_recursive("/system/vendor/app/NvEsrd");
delete_recursive("/system/vendor/app/NvGamecast");
delete_recursive("/system/vendor/app/NvRegistration");
delete_recursive("/system/vendor/app/Stats");
delete_recursive("/system/vendor/app/TegraZone");
delete_recursive("/system/vendor/app/Welcome");
delete_recursive("/system/vendor/app/nvbatterymonitorservice");
delete_recursive("/system/vendor/app/nvidiafeedback");
delete_recursive("/system/vendor/app/nvpowerstats");
delete_recursive("/system/vendor/app/watercolor");
ui_print("Finish");
Step 2 - TV Permissions
Some apps with ten foot experiences are packaged and distributed separately from their mobile/tablet counterparts (like Twitch and ESPN). Others, package all experiences together and ask for permissions at runtime (like PBS Video and PBS Kids). The attached tv_permissions.zip file adds these, as well as android.software.picture_in_picture in order to prevent an exception when the home button is double tapped.
Step 3 - Settings activity is now broken
This is because our conflicted device is looking for the ribbon at the top of the settings activity, but it doesn't exist in the tv layout. fixes.zip patches Settings.apk to include the ribbon in the tv layout.
If you have issues with this, try running debloat and tv_permissions, boot the device, then go back to recovery and flash fixes.zip.
Step 4 - Open GApps tvstock
Big thanks to the Open GApps guys for this one. I cheated a bit here and instead of adding the packages one-by-one to be removed in the debloat script, I manually removed a number of tars from the zip file. I'll fix this, I promise but in the meantime open up the zip file and remove the following:
GApps/castreceiver-arm.tar.lz
GApps/gamepadpairing-arm.tar.lz
GApps/livechannels-arm.tar.lz
GApps/talkback-arm.tar.lz
GApps/tvmovies-arm.tar.lz
GApps/tvmusic-arm.tar.lz
GApps/tvplaygames-arm.tar.lz
Core/bugreport-all.tar.lz
Core/googlebackuptransport-all.tar.lz
Core/googlecontactssync-all.tar.lz
Core/gsfcore-all.tar.lz
Core/notouch-all.tar.lz
Core/setupwraith-all.tar.lz
...or don't if you want to experiment with Google Play Services, but that's not my cup of tea on a TV device. Early builds saw hangouts messages popping up while my wife and I were watching tv (ugh). By the way anything you do with any of this knowledge your sole responsibility.
Other Minutiae
Use the SPMC fork if you use Kodi. You will get recommendations/now playing, among other things.
Some apps may look for Play Services at runtime (I had this with Twitch, for example). If you don't want GPS/GSF I can verify that microG works for this. I used Lanchon's Haystack for signature spoofing. This required Linux and the Android SDK, but there are other ways to accomplish signature spoofing, I just didn't try them.
You'll need some means of downloading app packages without Play Store on your device. I used Raccoon and DummyDroid with the build.prop from Shield Android TV and this user agent string:
Code:
'Android-Finsky/6.5.08.D-all (versionCode=80650800,sdk=23,device=foster,hardware=foster_e,product=foster,build=NRD90M:user)'
Originally, I wanted to do this as a custom AOSP or Lineage-based rom. Some of the issues I ran into were beyond my reckoning and I decided to cut bait and use stock. Lineage does work though, you'll just be sacrificing HDMI-CEC and Granular HDMI audio volume (Steel01 got HDMI audio working though, so big props there).
One thing that was bugging me was that the Shield Controller won't wake the tablet when the tablet is on batter power, even if you have it set to leave wifi on when sleeping. The following setting will fix this:
Code:
adb shell settings put system com.nvidia.blakepairing.agoAlwaysOn 1
Edit 3/6
Guide skeleton, can't attach zips, screens, or post links
Setting to wake device on battery power
Edit 3/9
Screens and flashable zips added

tenFootPedal said:
Title seems sudden, but actually it's been a bit of a task. If anyone's interested I'll put some details and flashables up in here.
Click to expand...
Click to collapse
Put em up, I was just thinking about converting mine with my Chromecast for mobdro, TV portal, and terrarium app. I already have a roku box and a Chromecast, but I'm curious how you converted yours. Thanks!

tenFootPedal said:
Title seems sudden, but actually it's been a bit of a task. If anyone's interested I'll put some details and flashables up in here.
Click to expand...
Click to collapse
It's a GOOD IDEA to add the method rather than just a passing comment...
Thanks

set my spare shield up with kodi and its fine, i even still game on it occasionally. it's always hooked up so, why not?

LenAsh said:
It's a GOOD IDEA to add the method rather than just a passing comment...
Thanks
Click to expand...
Click to collapse
Yeah I'm planning on sharing but I wanted to gauge interest. Also I've never posted here and either I don't have permissions or I'm having PEBKAC issues with posting attachments.

Edit 3/6
Guide skeleton, can't attach zips, screens, or post links
Setting to wake device on battery power

Edit 3/9
Screens and flashable zips added
I'll be trying this with 5.1 OTA next

i have gotton the sheild game hub from the stock nvidia sheild tv firmware to install and work with this mod. i also use the ps4 controller via bluetooth for my remote in console mode. i cant figure out how to install the Google play store on this mod. can someone help me get it to install and work.

i have gotton the sheild game hub from the stock nvidia sheild tv firmware to install and work with this mod. i also use the ps4 controller via bluetooth for my remote in console mode.
Click to expand...
Click to collapse
nice. Thanks for the feedback.
I haven't been down the play store road, but I would start by installing the tvstock gapps package without removing gsfcore (maybe others?) and don't run the debloat zip after you do so.

tenFootPedal said:
nice. Thanks for the feedback.
I haven't been down the play store road, but I would start by installing the tvstock gapps package without removing gsfcore (maybe others?) and don't run the debloat zip after you do so.
Click to expand...
Click to collapse
the tv gapps dont even have google play within the zip so we have too figure out how to install the android tv google play store on this mod we will be all set to go. i have all the system files from the stock nvidia shield tv on my pc trying to swap files to see what i can mimic. but the shield games for the nvidia shield tv works perfectly on this mod.im also trying to see if i can install the stock shield tv firmware on the shield k1. i can get the boot,recovery,system img's to flash successfully but it taking forever to boot. so it seems it dont work but i will keep trying.

So u can install stock Android shield TV games on this mod aye
Sent from my ONEPLUS A3003 using Tapatalk

also this mod works with the 5.1.1 OTA and the 6.0.1 OTA. and the lastest firmware but its a little buggy for me. aslo is there any way to make a uninstaller.zip for this mod. im also still having a hard time to get google play store installed

It would be so great if someone could pack this all up into a flashable ROM. That's something out of my abilities, could someone pretty please make it happen?

phuzznut said:
It would be so great if someone could pack this all up into a flashable ROM. That's something out of my abilities, could someone pretty please make it happen?
Click to expand...
Click to collapse
If this were an aosp-based build, I would do it. But since its stock, I didn't feel comfortable doing it. There are some things I should probably do to take some of the steps out and make it easier though.
@brandonlee96, since this deletes a number of stock apks, I'd need to pack them up to put them back to make an uninstaller, which I don't want to do for the same reasons as above. You can do what I do and just make a twrp backup of stock to go back to.

@brandonlee96 Here's your play store problem. TubeSky is missing when tvstock runs on a tablet device. So you need to change this line in your build.prop
Code:
ro.build.characteristics=tablet
to this
Code:
ro.build.characteristics=tv
before flashing tvstock.
After that, make sure you delete SetupWraith, because it will perpetually crash and restart on boot. I haven't tested it any further than that.

tenFootPedal said:
@brandonlee96 Here's your play store problem. TubeSky is missing when tvstock runs on a tablet device. So you need to change this line in your build.prop
Code:
ro.build.characteristics=tablet
to this
Code:
ro.build.characteristics=tv
before flashing tvstock.
After that, make sure you delete SetupWraith, because it will perpetually crash and restart on boot. I haven't tested it any further than that.
Click to expand...
Click to collapse
im doing that right now! i will let you know the results.

Apparently play store will auto update itself to the intended device's version. Getting the leanback (TubeSky) version to stay likely involves spoofing your device as an android tv to the play store (via build.prop and/or other means). I don't think I want to devote any more time to play store for now, when apks can be pulled from another device or via Raccoon.

tenFootPedal said:
Apparently play store will auto update itself to the intended device's version. Getting the leanback (TubeSky) version to stay likely involves spoofing your device as an android tv to the play store (via build.prop and/or other means). I don't think I want to devote any more time to play store for now, when apks can be pulled from another device or via Raccoon.
Click to expand...
Click to collapse
i have the google play working thank you. i just wondering is there anyway we can beef up this mod? btw the recommendations does work it just didn't load up at this time!

brandonlee96 said:
i have the google play working thank you.
Click to expand...
Click to collapse
How did you make it stop auto-updating/replacing the vending package?
brandonlee96 said:
is there anyway we can beef up this mod?
Click to expand...
Click to collapse
What did you have in mind?

Hi, great thread! Will defenitly be trying this out in the next couple days... but i have a few questions. .
Does GFN work?
Does the system UI mimic ATV? Like the settings menu etc..?
Can we tell the battery level when unplugged?
Also, regarding build.prop edits to mimic the ShieldTV, i haven't changed build.prop to mimic anything in like 4 years haha! so I'm a little rusty, can you kindly show me what lines need changing to successfully spoof the STV?
Also, may be worth adding the Playstore is now working to the OP and credit @brandonlee96 haha
Great work guys! This looks amazing.