yashsingh1/xdaforums huggingface dataset:
[Nook Color General] Musicman247:
I've got a non-rooted 1.01 Nook Color. What do I need to do to get the build.prop file?
[Nook Color General] .mak:
You may need to change to.product.model too.. compare the build.prop from the stock NC to the nootered NC and give it a shot.
[Nook Color General] nikto34:
In checking my nootered NC build.prop file I do not see "to.product.model"

Would this line be located somewhere else? Does anyone know if this line is present in the stock NC build.prop?
[Nook Color General] whit32:
I'm also in a bn now, same result. No problems getting on wifi, but no in-store features on the store tab. I tried a couple of demo nooks so I am sure it's working.

Also tried rebooting into the default home thinking that the default launcher may do some store check, but no dice. Must be using something other than the fingerprint line to auhenticate.
[Nook Color General] ripleys:
I believe this should be "ro.product.model"

On my nootered nook, it is set to "LogicPD Zoom2"
[Nook Color General] nikto34:
Good catch! I checked my nootered NC build.prop and it also says "LogicPD Zoom2" If someone can tell me how to get to the build.prop on the stock NC, I can try and see what the build.prop says as I have a stock NC as well. However, maybe someone already knows this information or can post the stock build.prop file.

Looks like we are making progress here...
[Nook Color General] Musicman247:
Been trying to get my non-nootered Nook Color to work with adb with no success so far. Any tips? I'm using Windows 7. ADB is working, but the Nook color is not showing up as a connected device.
[Nook Color General] nikto34:
I may be incorrect, but to get adb access to the NC, it needs to be nootered... There most likely is someone else that is more knowledgeable on this subject than me so maybe they can clarify.
[Nook Color General] eyecrispy:
i assume this applies to the NC. i just used adb on an unrooted samsung galaxy tab and it showed up in my list of devices. but i was not able to do a whole heck of a lot after that. couldn't adb shell over to browser the file system. no surprise, i guess.
[Nook Color General] Musicman247:
Followed the directions Here, USB drivers installed and everything, just cannot connect to the Nook via adb. My device list shows up empty.

Edit: Have just been told in the Nookdev IRC channel that adb only works on rooted Nook Colors.
[Nook Color General] whit32:
Unnootered build.prop can be found in the mmcblk0p3 partition factory.zip file. I have compared to the nootered build file and it appears the only difference in the build info is the fingerprint.

Here's the first part of my 1.0.0 unnootered file:

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=ERD79

ro.build.display.id=ERD79

ro.build.version.incremental=273

ro.build.version.sdk=7

ro.build.version.codename=REL

ro.build.version.release=2.1

ro.build.date=Tue Nov 23 15:54:59 PST 2010

ro.build.date.utc=1290556499

ro.build.type=user

ro.build.user=build

ro.build.host=dhabuildimage10

ro.build.tags=test-keys

ro.product.model=LogicPD Zoom2

ro.product.brand=generic

ro.product.name=zoom2

ro.product.device=zoom2

ro.product.board=zoom2

ro.product.cpu.abi=armeabi

ro.product.manufacturer=LogicPD

ro.product.locale.language=en

ro.product.locale.region=US

ro.wifi.channels=

ro.board.platform=omap3

# ro.build.product is obsolete; use ro.product.device

ro.build.product=zoom2

ro.build.sourceversion=full

ro.build.description=1.0.0.273.int.enc.rrdp.s30428

ro.build.fingerprint=generic/zoom2/zoom2/zoom2:2.1/ERD79/273:user/test-keys

# end build properties
[Nook Color General] nikto34:
Thanks! This is what we needed.

I compared my build.prop to the one supplied as the stock 1.0.0 version. Remember, I have the 1.0.1 nootered. Here is what mine says:

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=ERD79

ro.build.display.id=ERD79

ro.build.version.incremental=278

ro.build.version.sdk=7

ro.build.version.codename=REL

ro.build.version.release=2.1

ro.build.date=Thu Dec 16 14:27:20 PST 2010

ro.build.date.utc=1292538440

ro.build.type=user

ro.build.user=build

ro.build.host=dhabuildimage10

ro.build.tags=test-keys

ro.product.model=LogicPD Zoom2

ro.product.brand=generic

ro.product.name=zoom2

ro.product.device=zoom2

ro.product.board=zoom2

ro.product.cpu.abi=armeabi-v7a

ro.product.manufacturer=LogicPD

ro.product.locale.language=en

ro.product.locale.region=US

ro.wifi.channels=

ro.board.platform=omap3

# ro.build.product is obsolete; use ro.product.device

ro.build.product=zoom2

ro.build.sourceversion=full

ro.build.description=1.0.1.278.int.enc.rrdp.s30428

ro.build.fingerprint=generic/zoom2/zoom2/zoom2:2.1/ERD79/273:user/test-keys

# end build properties

As you can see the differences are:

ro.build.version.incremental=278

ro.build.date=Thu Dec 16 14:27:20 PST 2010

ro.build.date.utc=1292538440

ro.product.cpu.abi=armeabi-v7a

ro.build.description=1.0.1.278.int.enc.rrdp.s30428

ro.build.fingerprint=generic/zoom2/zoom2/zoom2:2.1/ERD79/273:user/test-keys

I have changed my build.prop to match the stock NC build.prop (leaving the build.description as 1.0.1.278).

I am going to B&N tonight to test...
[Nook Color General] whit32:
Be aware some of those differences are just due to the different un-nooted Nook builds. Here's the source code of the nooter changes to the file, which should be the only reversions needed to test the current theory that the build.prop file is actually used for in-store authentication (which I am beginning to doubt):

From h t t p : / / code.google.com/p/nooter/source/browse/trunk/auto-nooter-2.12.25/NooterFiles/tmp/scripts/Nooter?r=14

cd /mntsys

sed -i '/nocheckin/d' build.prop

echo "ro.config.nocheckin=no" >> build.prop

sed -i 's/abi=armeabi$/abi=armeabi-v7a/' build.prop

sed -i '/cpu.abi2/d' build.prop

echo "ro.product.cpu.abi2=armeabi" >> build.prop

sed -i 's/^.*ro.build.fingerprint.*$/ro\.build\.fingerprint=verizon\/voles\/sholes\/sholes:2\.1-update1\/ESE81\/29593:user\/release-keys/' build.prop

EDIT to clarify -- to completely reverse the changes to build.prop that the nooter did I think you would need to do 4 things:

1. revert the fingerprint line

2. revert the abi line

3. remove the nocheckin line (appended at end)

4. remove the abi2 line

I want to look a bit more into this code which modifies some "uid.system" parameter:

cd /mnt/system

sed -i '/uid.system/,/perms/{/uid.system/b;/perms/b;d}' packages.xml
[Nook Color General] nikto34:
Well, just changing the build.prop file to match the stock NC build.prop did not help enable instore features. I did not make any changes other than the ones I listed as different in my previous post.

Whit32- I did not try your changes you suggested but will look into editing my build.prop with your suggestions and try again tomorrow. In looking at my build.prop I can not find the "abi2" line in the main section of the code. I see this line at the very end of the code, would this be the line to remove?
[Nook Color General] whit32:
Yep, the abi2 and nocheckin lines are both appended to the bottom. The stock nook build.prop does not have those lines.

But I think we're chasing ghosts here .... I'm no expert but I'm beginning to think it unlikely that the in-store auth relies on the build.prop file. If it did, it should have looked at the fingerprint only. But I bet it's more sophisticated.

I'd like to monitor wifi traffic when booting a stock and nooted device in-store to figure out what data is actually being passed. Does the nook ID itself and ask for permission to display? Or is it challenged by the BN http server? Anyone have pointers about how to go about wifi sniffing to a particular mac address?
[Nook Color General] nikto34:
Do we know how the market identifies devices? Is it using the fingerprint in build.prop? Maybe there is a link and the NC uses the same process? However, if the build.prop is what the market uses then there may be something else.

To confirm that build.prop may not be the answer, I will try my edited build.prop later today...
[Nook Color General] whit32:
Here's a decent intro to how the market uses fingerprints, it's a bit light on tech.

http://chall32.blogspot.com/2010/06/android-market-fingerprints-demystified.html
[Nook Color General] nikto34:
What if we used the descriptors from a phone build.prop, such as an incredible and put these in the build.prop of the NC. Based on the above article this would be a registered build.prop so we should be able to have access to the apps the incredible has access to. Correct, or am I oversimplifying things?

I know this would not solve the NC instore features but it may confirm that the build.prop file is not the solution???
[Nook Color General] Musicman247:
AutoNooter 2.12.25 already sets the fingerprint to that of the Nexus1, or Droid X (as posted earlier in this thread), which are both Google flagship devices.
[Nook Color General] nikto34:
Right! Thanks for bringing me back around...

Well based on this information it looks as though the build.prop file is probably not the culprit as whit32 sensed last night... However, the one thing that continues to stick in my mind is that if auto-nooter 2.12.25 gives us the build.prop of a Nexus1/DroidX, why then are there some apps not accessible for download from the market? Is there another file that needs to be changed that we are missing? Am I beating a dead horse in still thinking these issues are linked???
[Nook Color General] cutterjohn:
...and there is something that I recall from my Augen GT days and getting the market mostly working... we had to use an emulator, pull androidID from a sqlite3 db under the emulator(IIRC) and then pull the db from the GT and add the androidID from the emulator to it, then push it back to the GT as one of the steps...

on the gTab OTOH it was pretty much just installing market(and support apps/libs) adding a Google acct, then clearing market & google framework services cache/data...
[Nook Color General] jasoraso:
I'm not very much of a hacker - but I thought I would point out that In-Store features have been disrupted since the very first rooting ... on 1.0.0. Before the market/gmail/youtube and build.prop. The v.1 of the rooting seemed to break the in-store features.

I didn't understand all of the steps, but if you find the original threads regarding rooting, perhaps you can understand the steps that were taken to obtain root. It seems that one of those steps is key to breaking the In-store features.

Hope this helps.
[Nook Color General] WillCameron:
do people using the Nook App on android phones get special deals too?

I think we need a full image of the NC and all its configuration files pre and post nootering. Perhaps theres a special ID file thats getting deleted in the conversion?

- Will.
[Nook Color General] :
Nope. . . people using the Nook App on android phones do not get the special deals. They are available only to the NookColor and Nook hardware users.

I have noted that in-store features were broken on my device from 1.0.0 rooting on. I rooted within a day of the first rooting image being available and lost my features long before market was enabled. The interesting thing was that a few people who rooted early on did not lose their in-store features. . . So it seems it is possible to be rooted AND have access to the features.
[Nook Color General] nikto34:
Well, to confirm. My rooted NC build.prop file with the edits that have been suggested and tried the last few times still does not give me instore feature access.

I have put out some messages to some other users in the threads that seem to indicate that they have a rooted NC and still have instore access. I am attempting to get a copy of their build.prop file to compare as well as get more details about the way they rooted.
[Nook Color General] gmanvbva:
To confirm though. You can do a factory reset and this will remove root and restore full (stock) functionality?
[Nook Color General] :
Though I have not tried this myself, that is what I have heard others report. I am sure someone will chime in soon to confirm!
[Nook Color General] nikto34:
Yes, performing a factory reset allows access. So we know it is linked to the rooting process.

In addition, I have access to a stock NC 1.0.1 and it has instore features in B&N at the same time my rooted one does not even with all the different build.prop edits attempted. I have been to two different B&Ns and tried with no success on the nootered NC with stock NC comparisons.
[Nook Color General] WillCameron:
dunno if this means anything, but three things: 1) while poking around in the nook last night, i noticed there were two BN services running, one appeared to be an Identifier service, and the other i think was a security service (Sorry didnt take notes and I'm late for work ATM! will try and update when I get home later). So possibly those services arent sending the correct paroles? 2) I went into the settings and noticed that both Serial Number and Who the nook is registered to both said "Unknown". Is that a known part of rooting or is something amiss on my nook? and 3) My Borders Books android app appears to be working. I dont get any errors connecting to the store, I can select and download samples. the only two things I haven't tried (because I discovered it last night) are Sideloading books and actually buying a book through them...

People probably already know the first thing, and the second is probably

something i missed in the rooting threads...

- Will.
[Nook Color General] nikto34:
Thanks for the info. A couple questions...

1. Were the BN services that were running on a rooted NC or stock?

2. How did you find these services that were running?

3. If rooted, how did you root your NC? (autonooter, other)?
[Nook Color General] WillCameron:
I dunno if this matters either, but I'll throw it in there for the sake of completeness.

I started with the stock 1.0.0 nookcolor back in december. Nootered it originally with nooter 0.2, and stayed with that until the final autonooter came out then used that (Without reverting back to the stock NC.

Then on January 2nd i think it was, I reverted to the stock NC. Updated to 1.0.1, then used Autonooter 2.12.25 on it but apparently something went wrong because after the reboot it stayed on the N screen for an hour or so. so I reverted again to the stock (like the first time I wiped out both Data and System folders) and redid it and it worked fine the second time.

Installed Launcher pro, Kindel, borders, comic reader mobi, Android comic reader,

Aldeko and Adobe Readers, titanium backup, astro file reader, task killer, Spare Parts, Absolute system root, and overdrive media console. I pretty much did that through ADB (off a windows 7 x64 system).

that pretty much brings me to right now.

--- 1. Were the BN services that were running on a rooted NC or stock?

--- 2. How did you find these services that were running?

--- 3. If rooted, how did you root your NC? (autonooter, other)?

Rooted, using autonooter 2.12.25 off the 1.0.1 nookcoolor update.

The services are:

InStoreService

And the other one I remember is not running now after a reboot ( Dunno if it also matters but when I'm not using the NC I Turn It Off by holding the power button until it asks to shut down entirely. I dont 'rest' it)

The way I got to this is thorugh NookColor Tools all settings // development // running services. InStoreService and WsprService are both running now, from com.android.settings

Oh and to clarify (because I was rushed. not that that matters, heh). through NookColorTools // about your nookcolor under OWNER and ACCOUNT both say Unknown, not the serial number, thats correct.

Sorry it says Unavailable, not Unknown....

- Will.
[Nook Color General] :
For what it is worth, I followed a nearly identical path to Will's (not all the same apps installed) and under settings/About Your NOOKcolor my Owner and Account information (Actually all the info on that page) is known and looks correct.

Using NookColor Tools/All Settings/Running Services I see to services running under Settings:

InstoreService

WsprService

There is also another BN Service:

BnCloudRequestNdsvc

Don't know if that helps you more intelligent folks or not. . . but there you go!
[Nook Color General] nikto34:
Great! Thanks for this info. I checked my rooted NC and found the following services running:

BNCloudRequestNdSvc

CloudService

These two services are coming from com.bn.cloud.svc

I have not been able to find much on these services but since they have been running all the times I went to B&N to try edits to the build.prop, I have a feeling that these services are not the reason we do not have Instore features with nootered NC.

As I have yet to hear from any of the members stating they had access to Instore features, I am beginning to wonder if those few members that stated that they had Instore features working on their nootered NC had full access to all the features.

I am also trying to look at the framework.jar file as a potential culprit. Does anyone have access to a stock framework.jar that they can post or send? I would like to put this file on my nootered NC and see if this has any impact.
[Nook Color General] WillCameron:
Also if you have Absolute System Root installed, go into Application Management, and theres a few interesting things in there (well, maybe...) such as:

AFileDownloadService

/system/app/affiledownloadservice.apk

/data/data/com.bn.nook.affiledownloadservice

com.bn.app.crypto.server

/system/app/cryptoserver.apk

/data/data/com.bn.app.crypto.server

DownloadAdmin

/system/app/downloadadmin.apk

/data/data/com.bn.nook.dadmin

dunno if thats any use.... there may be others.

And I also just noticed, if I go through the default nook launcher and launch the Shop, it just hangs...

- Will.

Sitting hear eating a big mac, futzing on the nookcolor and computer :-)
[Nook Color General] whit32:
Can someone tell me what log file is being shown in the following pastebin link?

http://nookcolor.pastebin.com/mazVLN7J

There are some log entries being shown for InstoreService, for example (this is not my nook, just something I found by googling InstoreService):

D/InstoreService( 882): ACTION received = com.nook.intent.action.ACTION_BN_INSTORE_SERVICE_STOP

D/InstoreService( 882): Message: (102)

D/InstoreService( 882): setState: From SESSION_TERMINATED to SESSION_STOP

Might be worth looking for log entries indicating successful and failed instore sessions...
[Nook Color General] nikto34:
SO an interesting thing just happened...

I went to B&N to play with some more settings and edits to see about getting Instore features to work.

After seeing your post, I wanted to run logcat on my NC to see if I could figure out the log entry. I downloaded Terminal Emulator from the market on my rooted NC, installed, and rebooted.

Upon reboot, my NC started to installing "new software." I waited thinking my device had been factory reset somehow but upon booting, it said I had version 1.0.0 on my device now when I have 1.0.1. Assured that I had been reset, I checked and some of my apps were still intact however, I lost the market and a couple other apps. Terminal Emulator was installed

I thought that I might have instore access but no luck. I do however now have 6 screens when I go to the shop when previously I only had 5.

Not sure what is happening here but some very weird events...

I have also lost superuser access...
[Nook Color General] devis:
I'm on 1.0 and have full access to all the in store features. Rooted NC of course.

Sent from my NookColor
[Nook Color General] mtl171:
Yes if auto-update is NOT disabled.
[Nook Color General] Musicman247:
Which method did you use to root?
[Nook Color General] nikto34:
Yes, it is important that we determine how those that have rooted NCs with Instore features have rooted their devices. Then if possible, if devis or another member could post a copy of their build.prop for comparison, that would also be helpful.

I currently have reverted my NC back to stock 1.0.0 and am looking to take a new approach...

As for the comment about autoupdate. I did not have this disabled but have been in two different B&N, multiples times, with multiple reboots and this was the first time this happened. Could be that I got lucky all the other times but not sure this is the case. Also, only the /system was reset and not a full factory reset.
[Nook Color General] JamesEcht:
I had in-store access via nooter 0.2, but no in- store access via autonooter.

JE

Sent from my Nook Color using the XDA app.
[Nook Color General] nikto34:
OK, this is the first report (that I know of) of a difference in access via the rooting method. Thanks!

Are you still using autonooter version?

Did you have any apps installed under the nooter 0.2, did you have market access?
[Nook Color General] JamesEcht:
Under nooter 0.2, I didn't have market access butI did have apps both sideloaded and directly downloaded/installed.

JE

Sent from my Nook Color using the XDA app.
[Nook Color General] devis:
Not the autonooter, the other one. The first method.

Sent from my NookColor
[Nook Color General] devis:
Same here.

Sent from my NookColor
[Nook Color General] WillCameron:
Is there a way to use something like ADB to mirror the entire internal folder and file structure onto my PC? theres tons of interesting stuff in tons of interesting folders but navigating and reading it through the nook itself is somewhat tiersome.

- Will.
[Nook Color General] likearaptor:
I would say something like adb pull /system .

I am going to B&N today with a freshly updated Nook 1.0.1 without rooting/adb, I will then apply the Nooter 0.2 patch in the store and see after rebooting if I still have access. Then I will try to figure out what changes with the auto-rooter so I can try to figure it out, but I wouldn't count on me figuring it out soon. The B&N store is 40 minutes from where I live so I can't go each day and test. But I do want to help confirm the Nooter 0.2 does allow in store access today.
[Nook Color General] eyecrispy:
What's the difference between Nooter 0.2 and Autonooter? Just what Autonooter installs after the root?
[Nook Color General] pulser_g2:
OK. I have an idea (and I don't have any device or anything like that)

Can someone get me the build.prop from a nook before rooting, and after.

I reckon we can fix this with a small script, run via gscript or shell.

Once we compare them, we'll find there's a line like

ro.build.fingerprint=chunghwa/htc_hero/hero/hero:2.1-update1/ERE27/183682:user/release-keys

that doesn't match that in the original file. If someone posts this, please PM me. If there's an OTA zip with a new build.prop, it would do. But we also need the build.prop after the rooting process.

What I intend to do is script a change of the value(s) which are changed after rooting. So by default you would be set for market. If you wanted to use in-store, then you would simply tap an AnyCut icon on your homescreen, launching a Gscript script (just a plain linux shell script) which will change the values in memory. You connect to instore wifi after this, and hopefully it lets you on.

That sound worth a shot?
[Nook Color General] pulser_g2:
Right, I've found the technical info of the root process:

Old build.prop fingerprint:

ro.build.fingerprint=generic/zoom2/zoom2/zoom2:2.1/ERD79/269:user/test-keys

Eris one:

ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys

See http://nookdevs.com/NookColor:Manual_market_enable for the full guide.

I reckon the secret lies in nc_gapps.zip from that page. That file will enable market and google apps, which I gather breaks the B&N stuff. Is that correct, or is it broken merely by rooting?

I found 1.4.1 image (unsigned) from restore partition from http://nookdevs.com/Rooting_New_Hardware, which appears to be an unedited rom image... Once I get this nooter thing in, I can compare the two sets of ROMs, and see what's different
[Nook Color General] Musicman247:
That's what we've been trying to figure out for the past few days. We've already had people change the build.prop file fingerprint back to the original with no success in getting the In Store features to work.