Database Users

Market problem with Roto JME v3

Dear all.
First off Roto's JME v3 is great. I give it a 9/10. The one missing point is because of the following problem I immediately faced after flashing from my German stock firmware (I don't have this verison # here atm, but can get it later, if needed).
Android Market:
Problem 1:
NHL Gamecenter app not found in Android Market. The app was available to me on the stock firmware but now I can't find it in the market. Not current under paid apps NOR under app search. It simply is not there. It is on my Desire Z and also can be found of my friend's Galaxy S.
Solution:
??
Problem 2:
Not able to download NitroDesk's TouchDown License Key. Program is found but not the key. Was found on my stock fw and also on my Desire Z.
Solution:
Got a license number from NitroDesk. Still unable to find the program in market tho!
I would really appreciate any help as the NHL Gamecenter is THE app I used to use on my gal tab!

Leaked firmware versions aren't know by the android market. To fix this you need to edit the build.prop file. There are several apps who can do that for you.
I myself use Eris Market Fix. Be aware though that the roto packages contains a buggy busybox. If you use that with Eris Market Fix your tab won't start up.
First update your busybox with the BusyBox app on the market place (17.1 is the most stable version) than run Eris Market Fix, reboot your Tab and you're done. All apps will be visible again.

Eris fix is also not showing in market..

Sorry if this is trivial but have you set your csc to XEU. Default is KOR and *could* lead to something like that.
*#272*<IMEI># afair
This will wipe your internal sdcard so do a TB backup first.
I would try that first. No roto-jme has been seen to cause that before...
Cheers,
Hal.
Sent from my GT-P1000 using XDA App

Have you checked your CSC Code?
# cat /sytem/csc/sales_code.dat
Should be DBT for germany.
to change the sales code, you can simply remount the system filesystem read/write ,
echo "DBT" >/system/csc/sales_code.dat
and reboot.

julianLo said:
Have you checked your CSC Code?
# cat /sytem/csc/sales_code.dat
Should be DBT for germany.
to change the sales code, you can simply remount the system filesystem read/write ,
echo "DBT" >/system/csc/sales_code.dat
and reboot.
Click to expand...
Click to collapse
Damit.. and there was I vi'ing the file..

kånda said:
Dear all.
Android Market:
Problem 1:
NHL Gamecenter app not found in Android Market. The app was available to me on the stock firmware but now I can't find it in the market. Not current under paid apps NOR under app search. It simply is not there. It is on my Desire Z and also can be found of my friend's Galaxy S.
Solution:
??
I would really appreciate any help as the NHL Gamecenter is THE app I used to use on my gal tab!
Click to expand...
Click to collapse
Open /system/build.prop in Root Explorer's text editor on the Tab, change XXJME to XXJK5, or whatever your stock version was (XXJK5 should work fine though), in ro.build.fingerprint. This will allow you to see your missing and protected apps in the market.
You can also edit build.prop by pulling it to your computer with ADB, editing it and pushing it back, but Root Explorer is much faster and easier to work with.
Edit: this issue has nothing to do with the CSE or what it is set to.

Thanks
rgbc said:
Open /system/build.prop in Root Explorer's text editor on the Tab, change XXJME to XXJK5, or whatever your stock version was (XXJK5 should work fine though), in ro.build.fingerprint. This will allow you to see your missing and protected apps in the market.
You can also edit build.prop by pulling it to your computer with ADB, editing it and pushing it back, but Root Explorer is much faster and easier to work with.
Edit: this issue has nothing to do with the CSE or what it is set to.
Click to expand...
Click to collapse
Thanks, that solved my problem!!!

rgbc said:
Open /system/build.prop in Root Explorer's text editor on the Tab, change XXJME to XXJK5, or whatever your stock version was (XXJK5 should work fine though), in ro.build.fingerprint. This will allow you to see your missing and protected apps in the market.
You can also edit build.prop by pulling it to your computer with ADB, editing it and pushing it back, but Root Explorer is much faster and easier to work with.
Edit: this issue has nothing to do with the CSE or what it is set to.
Click to expand...
Click to collapse
Problem solved! Thank you so much! I think I'm fast becoming a fan of these forums

biopsin said:
Eris fix is also not showing in market..
Click to expand...
Click to collapse
Lol, how funny !! It does on mine though when I've flashed new firmware.

let me get this straight. so i edit out anything that says xxjme with xxjjb in build.prop. ?
ever since ive been using roto's jme i can never find atomic bomber
i have market enabler. but i fake us tmobile and verizon and i can never see atomic bomber. going through withdrawals

b0ricuaguerrero said:
let me get this straight. so i edit out anything that says xxjme with xxjjb in build.prop. ?
ever since ive been using roto's jme i can never find atomic bomber
i have market enabler. but i fake us tmobile and verizon and i can never see atomic bomber. going through withdrawals
Click to expand...
Click to collapse
No just edit the ro.build.fingerprint. That did it for me. I just replaced JME with JK5.

kånda said:
No just edit the ro.build.fingerprint. That did it for me. I just replaced JME with JK5.
Click to expand...
Click to collapse
I am having the same issue as op. Where do I find the ro.build.fingerprint file to edit?
Sent from my GT-P1000 using Tapatalk

balto said:
I am having the same issue as op. Where do I find the ro.build.fingerprint file to edit?
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Wow, I am slow today, re read the post and figured it out.

julianLo said:
Have you checked your CSC Code?
# cat /sytem/csc/sales_code.dat
Should be DBT for germany.
to change the sales code, you can simply remount the system filesystem read/write ,
echo "DBT" >/system/csc/sales_code.dat
and reboot.
Click to expand...
Click to collapse
Does it mean that you can change CSC without doing *#272*IMEI# and a full wipe ? Is it working for samsung app as well ?

Interestingly I changed my code from JME to JJ4 which is the original firmware my GT came with, but still wouldn't find b0ricuaguerrero's game. Changed it to JK5 and it popped up.
The idea obviously works well though, cheers!

rgbc said:
Open /system/build.prop in Root Explorer's text editor on the Tab, change XXJME to XXJK5, or whatever your stock version was (XXJK5 should work fine though), in ro.build.fingerprint. This will allow you to see your missing and protected apps in the market.
You can also edit build.prop by pulling it to your computer with ADB, editing it and pushing it back, but Root Explorer is much faster and easier to work with.
Edit: this issue has nothing to do with the CSE or what it is set to.
Click to expand...
Click to collapse
I can't open then file using the text editor as it tells me it is a read-only file, and i am not comfortable using ADB, any other suggestions?
EDIT: ok never mind i was able to do it, but when i launch the market i only see 2 apps that installed and nothing else....
EDIT: ok i think either market is started to work properly on its own or i may have fixed it but all i did was re-flash JME v4 and so far it seems to work, but sure was a pain in the you know what.......

Anyone have a Froyo Archos with full Market Protected App access

After the market fix has been applied I see most apps (including some that I know are protected) but not all. From my experience on the DroidX, this is usually an issue with the build.prop not reporingt a valid ROM to google.
For example, I can search on my DX for "wii controller ime" and find the app. My Archos 101 does not. (I side loaded it.)
If someone has a build.prop for an Archos Gen 8, that will see that send it my way please.

Can you tell me what you've changed in the build.prop of your DX?

ok, done:
I just took the fingerprint from a galaxy tab:
paulshields said:
Code:
ro.build.fingerprint=samsung/GT-P1000/GT-P1000/GT-P1000:2.2/FROYO/XXJJ3:user/release-keys
Click to expand...
Click to collapse
- edited my build.prop using the root+rw package
- cleared the market cache and such
it's working
I can install apps like "Gun Bros" which I couldn't previously

This sounds cool! Is there a way a non rooted device can get this? Perhaps by some installation.apk
Thanks

Definitly not possible without root. I don't know if it's even possible with temproot
Sent from my A101IT using Tapatalk

Yeah, basically you need to fool the market into thinking you have a certified device. Not an easy task from what I understand. If you have a rooted Android phone you can download te app there, then use Titainium Backup to get the apk off the phone and side load it on you Archos. At least tha is what I do.

chulri said:
ok, done:
I just took the fingerprint from a galaxy tab: http://forum.xda-developers.com/showpost.php?p=9787172&postcount=2
- edited my build.prop using the root+rw package
- cleared the market cache and such
it's working
I can install apps like "Gun Bros" which I couldn't previously
Click to expand...
Click to collapse
Hi chulri,
I follow your instruction above by modifying the fingerprint in /system/build.prop, then did the same market fix as instructed by the gappsinstall thread, reboot. I still can't find the gun bros app.
What else I have to do? (I had 2.1.4 rw root installed before doing this)
Now "My Apps" list is gone in the Google Market, can I get the list back?
Update: ok, it works now. I have to clear cache, clear data, force stop and then run the Market again. Now Gun Bros also shows up, and My Apps list also populate.
I still can't find Heywire app, anyone can see this app after this mod?

I have used archangel to root, then used marketenabler app from the market,
no other steps involved.
I seem to see all apps now (not 100% sure on that) but, definately see some protected apps that I couldnt see before and havent come across any on my HTC Desire that the Archos isnt seeing now.

CarsnGadgets said:
I have used archangel to root, then used marketenabler app from the market,
no other steps involved.
I seem to see all apps now (not 100% sure on that) but, definately see some protected apps that I couldnt see before and havent come across any on my HTC Desire that the Archos isnt seeing now.
Click to expand...
Click to collapse
I also use MarketEnabler, but I can't see, at least, Gun Bros. Once applied this build.prop mod, I can see Gun Bros.

Gun Bros is available on Archos Apps Lib anyway

bthoven said:
I still can't find Heywire app, anyone can see this app after this mod?
Click to expand...
Click to collapse
I have attached the latest version.

bthoven said:
Hi chulri,
Update: ok, it works now. I have to clear cache, clear data, force stop and then run the Market again. Now Gun Bros also shows up, and My Apps list also populate.
I still can't find Heywire app, anyone can see this app after this mod?
Click to expand...
Click to collapse
Yes, me too

Tesla74 said:
I have attached the latest version.
Click to expand...
Click to collapse
Thank you very much for .apk, It work fine on my Archos 101.

chulri said:
ok, done:
I just took the fingerprint from a galaxy tab:
- edited my build.prop using the root+rw package
- cleared the market cache and such
it's working
I can install apps like "Gun Bros" which I couldn't previously
Click to expand...
Click to collapse
Hi chulri,
Can you provide a Guide of modify it?
Because I put my build.prop into /system to replace it, then force stop the Market and clean cache, then Reboot
the fingerprint will restore by itself????
I have no idea where I goes wrong...><

LeoNg628 said:
Hi chulri,
Can you provide a Guide of modify it?
Because I put my build.prop into /system to replace it, then force stop the Market and clean cache, then Reboot
the fingerprint will restore by itself????
I have no idea where I goes wrong...><
Click to expand...
Click to collapse
[Solved]I think the Market Fix trick only work in old Market, it means you need to "Uninstall updates" after clean cache and force stop the Market.

Can someone please post up step by step how to edit the build.prop file ??
I've never done such a thing and I'm desperately trying to figure this out for a guide that I'm working on putting together..
I'm rooted (perma root) FWIW
Thanks a TON.

I use a file manager to copy the file to the sd and then connect to the computer via usb and edit with notepad++.. don't use windows notepad or wordpad as I've had problems with them. After the file is edited.. safely disconnect from the computer. Then I add .bak to the end of the original file and then copy the new edited file over to replace it.
I hope that helps. I believe there are also text editors in the market, but I like editing with a real keyboard.
Tesla

daddymikey1975 said:
Can someone please post up step by step how to edit the build.prop file ??
I've never done such a thing and I'm desperately trying to figure this out for a guide that I'm working on putting together..
I'm rooted (perma root) FWIW
Thanks a TON.
Click to expand...
Click to collapse
Here: I"ve used the RootExplorer method detailed in this forum:
http://androidforums.com/droid-x-all-things-root/154976-2-2-market-issues-use-mod.html
Also to all: There are two states possible with the Market. Fixed if you the clear cache hack, unfixed if you do not do it or if you undo it...(to undo just do the clear Cache path but add clear data....no need to stop googleservicesframework and no need to reboot...just restart Market app and accept legal terms). The difference fixed state gives more apps but will hide some others from you: you get google maps, zeam, ADW, ...but you loose Google Earth, Flash Player 10, TVU, .... Jus to name a few. So the key thing is to know how to quicly switch from one state to the other. use the clear cache hack to get into fixed state and use my undo rootine (clear data) to revert the fix.
Once you add the fix to build prop you pretty much have now 4 possible states:
Please see my post below for my tests on the 4 different states and some conclusions
http://forum.archosfans.com/viewtopic.php?f=63&t=48312
Here's how to very easily undo the fix if you need to...
..Once you've done the Market fix you do not need to reinstall Market to go back to state before applying the fix. Once you do the Market fix you will gain access to few more apps but many apps requiring froyo will no longer show up anymore: that's the case of apps like TVU, Flash 10, .... (there must be many more). I suspect the market fix makes the device and generic device but not a froyo one.
To go back an forth between the fix and the original state all you need is to do this;
go to Settings --- Applications --Manage Applications ---Running -- Market ---Clear Cache ----Clear Data --Force Stop--Relaunch Market ---Accept Terms and Conditions ---
Voila. and you're back to the original State where you can find flash 10 & other froyo only apps.
If you do the the fix...you loose flash ..but gaine other apps...the fix skip the Clear Data steps ...and the Clear Data step will undo the fix. THe fix requires reboot..To undo it you do not need to reboot and do not need to stop googleframework.

I do this fix and after seach keyword "adnroid" i get about 143000 apps.
Is it ok?

ncuxxx said:
I do this fix and after seach keyword "adnroid" i get about 143000 apps.
Is it ok?
Click to expand...
Click to collapse
Yes, that's fine...you good...fixed state, fixed buld.prop
but note you may still not see some apps with are available in unfixed state, fixed build.prop (like TVU, Google Earth, Adobe Connect, flash 10.01,..)
That's the con of fixed state...you gain some you loose some....

Archos 101 one-click-root for firmware 2.0.71 using Archangel

Download rar file with apk:
dump.ru/file/5037798
or
depositfiles.com/files/7sh8g638s
rar password: cea69e0419
sha1sum of apk: 80ff2925e12b8d3f2e9c0cabd5b294e6556b2e3f
Archangel one-click-root from the Archaism Team
This will give you temporary or permanent root on your Archos 101 - firmware 2.0.71
Archos are kind enough to provide a SDE firmware which can allow root access,
but involves some significant changes to the system and they say that they will
invalidate your warranty if you install it. This is a bit frightening for new owners.
Archangel solves this with a painless one-click-root which you can uninstall at any time.
It does not use the SDE developer firmware.
This was specifically designed for the Archos 101 with firmware 2.0.71 - it may work on
other Archos devices or firmwares, but has not been tested and is not recommended for them.
If you find this application useful, please donate to those great forums who have given
the android root community so much. Encourage them to keep up their great work. We are
fans of C-Skills Blog, XDA Developers and Modaco Forum.
When installed, this app will use approx 10mb of storage space. Don't run it if you don't
have that much spare.
Usage Instructions:
1) Make sure you have 10mb of space available on the internal storage
2) Make sure you are connected on Wifi
3) Run the Archangel app
4) Click to install SuperUser application
5) Click to get root!
6) Check everything is working correctly, try an app which needs root
7) Once you have root you can tick the "Permanent" root option to always have root.
8) Party Hard!
To turn off root, either just reboot, or turn off permanent root and reboot if you had
enabled it.
To uninstall, just uninstall like any other app. You may also want to use the menu item
to clean up before you uninstall.
You can create a script in /sdcard/sdcard/extraroot.sh and this will be executed as root
whenver you reboot, so you can use this to do any additional root functions you want.
Enjoy!

does this work?
anyone try yet?
I have A70 so i'm not sure if this will work for me
ohh a video demo would be nice

I think this is a scam "Permanent" root is not possible because the filesystem is a read-only filesystem. But I can be wrong.
I'll download this and try to inspect it.

I hope this works, I really want to get Titanium Backup working.

Well I haven't tried yet, but did a quick analysis on the APK:
Permissions on the APK does not seem to be too fishy:
Storage: modify/delete SD card contents
System tools: view and change WIFI state
and automatically start at boot
APK contains superuser, su and ls binaries.

It Works
jsperri: I saw the same as you when I looked at it.
I did install it and it seems to be working. I was able to go su from the terminal and backup an app with Titanium Backup.
I can also confirm that if permanent root is checked this will still work after reboot. When I was looking at the app it looked like it plugged into the launcher process. So perhaps it is just starting just after android is loaded.
Although I have not verified, I suspect that /system is still read only because of squashfs.

What bothers me is first the dates within the apk are 29/2/2008 for all files.
Then the binaries su is a gzipped binary superuser is a gzipped superuser.apk BUT ls is not compressed.
Why do they need ls the ls of the ROM should work fine. I suspect a trojan but i'm not sure. I could be paranoid but a rar with passwords come on......

xdaAlan said:
jsperri: I saw the same as you when I looked at it.
I did install it and it seems to be working. I was able to go su from the terminal and backup an app with Titanium Backup.
I can also confirm that if permanent root is checked this will still work after reboot. When I was looking at the app it looked like it plugged into the launcher process. So perhaps it is just starting just after android is loaded.
Although I have not verified, I suspect that /system is still read only because of squashfs.
Click to expand...
Click to collapse
So xdaAlan your first post and you claim it works and what proof you can give us? screenshots maybe.....

I agree with extreme caution on files coming from the "wild" (my apologies to archaism1).
Permissions on the APK seems to be reasonably OK.
Like wdl1908 I was also puzzled about the files dates and the presence of ls binary.
Well, I'll run this Archangel beast on a resetted tablet and report here the results with proofs

The ls binary is definitely fishy I reexamined the rar file and the file dates for the readme.txt and the apk are 18/8/2009 whats up with that.......

jsperri said:
I agree with extreme caution on files coming from the "wild" (my apologies to archaism1).
Permissions on the APK seems to be reasonably OK.
Like wdl1908 I was also puzzled about the files dates and the presence of ls binary.
Well, I'll run this Archangel beast on a resetted tablet and report here the results with proofs
Click to expand...
Click to collapse
Thxs jsperri I don't have a spare unit and don't really want to reset my unit.

Does not seem to be doing much on my A32 test machine.
Just tested on my 70H, no root either ;(
What the application does is:
- install superuser apk
- does something while it says "please wait"
(ps on adb shell shows a
Code:
/tmp/ls 0x62c7a315 0x260de680
so ls may well be part of the exploit)
There is a checkbox "Permanent root" that probably just starts Archangel program on boot
(this is just my guess, based on the APK permission, and the fact there is little chance that the squashfs gets written)
Well, I'm pausing my investigation here, waiting for others feedback, hopefully positive.
There is a screenshot of the application here along with a comment from a user saying it worked on an Archos 70 IT.

hi,
i haven't been very careful about trojan risks, but i installed it on my 70it and it works!
how can i know if a trojan is instaled?

toutiwai said:
hi,
i haven't been very careful about trojan risks, but i installed it on my 70it and it works!
how can i know if a trojan is instaled?
Click to expand...
Click to collapse
Was WIFI enabled ?
How long does it take after the button says "Please wait" ?
What's next step on screen ?
Regarding the trojan risk, it's hard to say, you'd eventually want to run tcpdump to log for internet traffic on the tablet when the program is running. Also check if there are programs left (appart from Superuser) after uninstalling Archangel.

note: after install, i didn't asked to be "permanent root", but it launches "archangel" at startup anyway (but no root if i don't ask for)
wifi enabled: yes, enabled AND connected, if not it can't get "root"
how long? if wifi connected, say... 15-25 sec...
next step: nothing, the button "install root" changes in "i'm root" or something like this...
note: i had "superuser" already installed (but not rooted) before installing archangel, so it didn't asked me to install superuser
i'll try to be more precise next time if important...

archaism1,
Can you please give us some details on Archangel program, how the exploit works, why is Wifi necessary ? It would be great to trust this new tool, but it's difficult without having more details on a program coming from a dump archive and not a very well know author...
archaism1 said:
....
Archangel one-click-root from the Archaism Team
This will give you temporary or permanent root on your Archos 101 - firmware 2.0.71
Archos are kind enough to provide a SDE firmware which can allow root access,
but involves some significant changes to the system and they say that they will
invalidate your warranty if you install it. This is a bit frightening for new owners.
Archangel solves this with a painless one-click-root which you can uninstall at any time. It does not use the SDE developer firmware.
...
Click to expand...
Click to collapse

Will this work on my archos 43 Internet tablet ? Anyone brave to test and report.

http://www.appbrain.com/app/root-checker/com.joeykrim.rootcheck
anyone tried root-checker after trying this "1-click-root"? to check that it does what it claims?
I'd love to believe this, but i'm naturally sceptical.

i just tried (archos 70IT), and "rootchek" says it's ok

well at least that is promising , thanks

[Guide/Mod] -Kindle Fire MAWR Market! *now with better build.prop*

Intro: This is my first guide, so be nice.. This will give you access to every app on the Android Market. I have downloaded apps that were previously “incompatible” and almost ALL of the gameloft, popcap, EA, etc.. games run without FC, validate, and download their additional data without failure for MY device thus far. It will revert after a restart, but its great to get what you want without having to do TB backup/restores over and over again for stuff you forget/buy later/etc...
If you have changes you would like to see to this guide, please comment!
------------------------------------------------------------------------
UPDATE: Feb 5th
I have been tweaking the build.prop for the last month or so, and have found some modifications that will boost performance and increase your battery life. It isn't an ungodly amount, but it is noticeable to me.
The build.prop is attached to the post now, instead of uploaded to an external site.
The old 2.2.6 market is attached for apps that show as "incompatible for your device".
------------------------------------------------------------------------
Disclaimer:
I take no responsibility for anything that happens to your device. Do this at your own risk.
YOU MUST BE RUNNING CM7!
YOU MUST HAVE ROOT!
I WILL NOT SUPPORT STOCK!
IF THIS WORKED, CLICK THANKS!!
Prerequisites:
CM7
Root
Root Explorer
Titanium Backup
Attached Files
Terminal Emulator
Lets do this thing:
First, the build.prop
We are going to replace the build.prop, so make a backup of the one you have.
open RE, and head over to /system/
copy that file and put it in a safe spot
Now we are going to put this modified build.prop in the location of the old one.
download this modified build.prop to your phone’s sd card:
open RE and copy the build.prop you just downloaded
navigate to /system/ again
click Mount R/W to give RE permissions to modify these files
paste the build.prop in the /system/ directory
if it asks to overwrite, go ahead and it will make a backup of the original called build.prop.bak
restart your device
Next, the Market
Now, we’re gonna get rid of, and replace some of the market data.
Open TB and delete “or freeze if you prefer” the following from the app list:
Market
This is optional! Do this if you are installing the old market and want it to not update until you restart.
Open up TE and run the following:
pm disable com.android.vending.updater
Now, we replace the Market that we had with the downloaded ones:
install and overwrite data “if it asks” for com.android.vending_2.2.6.apk
open your app drawer
open market “you should see the old version of the market”
HAVE FUN DOWNLOADING!!!
About the build.prop:
I had been screwing around with the build.prop for a while trying to find the best combination of fingerprints and such to put as to get the most out of the market. I discovered that the GT-P1000 “GTab” had the best results, so I changed the following:
Code:
ro.product.model=GT-P1000
ro.product.brand=Samsung
ro.build.description=GT-P1000-user 2.3.3 GINGERBREAD DXJPI release-keys
ro.build.fingerprint=samsung/GT-P1000/GT-P1000:2.3.3/GINGERBREAD/DXJPI:user/release-keys
I recently threw in the following performance modifications from various threads all over the interwebs. This combination works well for me. It is already in the new build.prop, so if you find a different setting to work better for you, post it and I will give it a try.
Code:
ro.kernel.android.checkjni=0
ro.ril.disable.power.collapse=1
video.accelerate.hw=1
debug.performance.tuning=1
windowsmgr.max_events_per_sec=150
ro.media.enc.jpeg.quality=100
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true

Thank you so much I have been looking for a successful attempt at changing the build.prop file before I attempted it. I am very glad you shared your knowledge.

Good deal! Glad it worked out for you.

Yeah it worked perfectly..I did skip wiping my system cache and everything worked perfectly still..once again thank you so much. Just in time for the end of the gameloft sale..lol. I really love it!

Dude I love you..lol not only did I gain access with the old market, after I rebooted and killed the terminal, I now how access to all of the apps with the updated market..it appears to be to the perfect fix for the market, at least for me anyway. I will keep you posted if anything changes. I know I still have access to all Gameloft and EA games. Bravo sir. The only thing I did differently from you walk through is I didn't system wipe before install the old android market.
Sent from my GT-P1000 using xda premium

So your MUST have cm7 installed? I am rooted but didn't install that.

ASMAteMe said:
So your MUST have cm7 installed? I am rooted but didn't install that.
Click to expand...
Click to collapse
This may work on the stock rom, but I haven't tried it. If it works out for you then I will update the OP.

Thanks a ton!
This method worked perfectly. I figured that it might have something to do with the build.prop's device fingerprints but I just never had the patience to try it.
I actually just skipped the market part and followed the replacement of the build.prop with a reboot. I still got access to apps I previously weren't able to see before while using the new market app, however Im not sure if its the entire market. I also skipped the wipe of the /system and everything is working fine.

download?
where can i download the build.prop??

Poler166 said:
where can i download the build.prop??
Click to expand...
Click to collapse
it's in the .zip file in the OP
also, due to the responses of skipping clearing the cache through twrp, i have removed it from the OP. and added another little courtesy note below the "not supporting stock" note.

nfl46 said:
I am going to try this on the ICS rom tonight.
Click to expand...
Click to collapse
Awesome, let me know if it works!

Crash
whenever i try to get to the market it just crashes ... any suggestion ?
EDIT: never mind it works now Your epic

Poler166 said:
whenever i try to get to the market it just crashes ... any suggestion ?
Click to expand...
Click to collapse
Try clearing your market data and install the attached market again and let me know if it works.

enkode said:
Try clearing your market data and install the attached market again and let me know if it works.
Click to expand...
Click to collapse
Spoke to soon when ever i try to download an app from the market it force closes and said The application Market (process com.android.vending) has stopped unexpectedly.

lordsofletterbox said:
Dude I love you..lol not only did I gain access with the old market, after I rebooted and killed the terminal, I now how access to all of the apps with the updated market..it appears to be to the perfect fix for the market, at least for me anyway. I will keep you posted if anything changes. I know I still have access to all Gameloft and EA games. Bravo sir. The only thing I did differently from you walk through is I didn't system wipe before install the old android market.
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
Could you elaborate how you got access to the full updated market? I tried that, and I can't download anything from it.

Awesome. Gameloft's TinTin game now recognizes my Kindle as a 3D supported device.
Sent from my CM7 Kindle Fire

I just tried this and the only thing that i had to do is copy the build.prop to /system, rename old one to build.prop.bak, set permissions for new one, force stop and clear market data from manage applications, then reboot. Everything shows up and downloads with the new market.

Poler166 said:
Spoke to soon when ever i try to download an app from the market it force closes and said The application Market (process com.android.vending) has stopped unexpectedly.
Click to expand...
Click to collapse
This may seem a little out there, but go to titanium backup and longpress the market app and move it to a user app. Attempt to open it up then close it, clear your data from the application details and reinstall the app from the zip on the OP. Install the marketupdater.apk as well.

theholyfork said:
Could you elaborate how you got access to the full updated market? I tried that, and I can't download anything from it.
Click to expand...
Click to collapse
Don't let the other users methods confuse you. If you did everything in the OP, you shouldn't have any problems. If you did, be more specific and I will try to help. No offense.

enkode said:
Don't let the other users methods confuse you. If you did everything in the OP, you shouldn't have any problems. If you did, be more specific and I will try to help. No offense.
Click to expand...
Click to collapse
Don't worry, I'm pretty good with this stuff, but when he said he had full market access I wanted to know how he did it. I can confirm that it works though, I just had to replace the build.prop you provided, force stop the market, and clear the market data, then reboot, and I can see more apps in the new updated market!

[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.