yashsingh1/xdaforums huggingface dataset:
[Nook Color General] nikto34:
Yes- I have tried changing the build.prop (fingerprint line as well as other lines) on my autonootered NC to match that of stock build.prop with no success. You can review earlier posts in this thread that show what lines have been changed to try and get instore features to work. Maybe there is something else in the build.prop that we need to change but I am leaning towards this not being the answer.
[Nook Color General] pulser_g2:
Has anyone tried to root the nook by themselves (ie, not using any pre-made tools).

I'm talking about using an exploit like RageAgainstTheCage, or similar, or one of the z4root type things, just to get a root shell. Once there, installing su binary, under a random name, etc...

I'm thinking that we need someone to gain root on its own, without adding or changing anything, and make sure they still have in-store wifi. No idea if this has been done or not, but it seems best place to start. Once you verify a rooted device can get on to the network fine, then we can start to look into logcats of failing ones, and see what is checking...

I know how I would verify devices if I was B&N, and it would be bad news for you guys, as I would fingerprint the filesystem on /system, and make sure it matched that of a valid shipping rom. It could just be a simple recursive "find . -type f > file.txt", and then the SHA sum of that file. But it would give the same result on any untouched phone. The moment someone started to tweak with the filesystem, and added a new file, the content of "file.txt" (this would be done in memory, just doing it like this as an example) would be changed, so the SHA sum wouldn't work.

There's obviously other methods they could use, like MD5ing files, or having a "tamper" flag somewhere on the filesystem. Has anyone ever "unrooted" and gone into a store and had it work? Perhaps mounting as RW "flags" something that you need to do the 8 boot interruptions to clear?

There's loads of mean ways I could protect against something like this. Best hope it's not something as mean as that... Though what would be worst would be SHA summing up framework.jar and build.prop etc, along with a few "targeted" checks for presence of Superuser.apk and su binary... Just remember that the people who protect systems know everything you guys know here :( That includes all the things people install... Even checking for the number of APKs in /system/app would be a good way to quickly spot a rooted and thus modified device...

I could go on, but won't... Would love to hear if anyone has put a stock rooted one onto the network successfully or not... Heck, they could check default.prop hasn't been jiggered to allow ADB with ro.secure=0...
[Nook Color General] pulser_g2:
As in my long post there, I reckon it will be a combination of this and something else, or not this... Doesn't seem to be the issue.

Just diff the two build.prop files and you can see all the changes.

I wonder if B&N used a "mean" method like those I came up with in the previous post... :(
[Nook Color General] Musicman247:
As you can see from the quotes above (on page 12 of this thread, btw), there have been a few reports for In Store options working using Nooter 0.2.

We have a guy (likearaptor) that will be checking tonight to see if this is the same every time or if these instances are flukes.
[Nook Color General] nikto34:
SO, I am working on my new approach...

I returned my nooter NC back to stock 1.0.0. Then checked and I obviously have instore features working.

I then decided to try and see what nootering process causes instore features to stop working. In seeing a response that devis has used nooter 0.2 and still has instore feature access, I decided to try Supernooter 0.1 ("In addition to enabling ADB, SuperNooter will also mount the NC /system partition and copy over Superuser.apk and the su binary").

I rooted my NC with this process and then updated the rooted NC with the ability to install apps without adb. Finally, I adb installed rootexplorer and went to B&N...

I rebooted the NC in store and did not have access to instore features. So, it would appear that the Supernooter 0.1 process disables instore features somehow. Maybe through the install of superuser access??? I do not think the adb process of enabling on device app install would cause this issue.

Therefore, my next plan is to return NC to stock, use nooter 0.2 to root, and then return to B&N to see if I have access to instore features...

I did the boot count to 8 method to return the NC to stock and then decided to see if I had access to instore features. No luck. This could mean that the answer to the changes occurring during rooting do not lie within the /system partition as this is re-imaged during this process. Potentially then the answer lies in the /data of the NC. Does anyone know what changes the rooting processes do to the /data of the stock NC?
[Nook Color General] pulser_g2:
Thanks for the quotes. I took a look through, but it was a quick skim of the thread mainly, so it certainly sounds like you have a good plan going on here (you being collective for everyone trying to find this out).

Good teamwork here :)

I'm interested to see where this goes, just out of curiosity...
[Nook Color General] pulser_g2:
Now we're making progress here... :)

packages.xml is edited to allow market access iirc. That of any help? Failing that, might be time to make a tarball before rooting, and after rooting, then extract on a linux PC or virtual machine, and diff -r or diff -uNr and see...
[Nook Color General] likearaptor:
I just got out of the store with bad results. So I went in

with 1.0.1 stock and I had in store access. I was able to download some books so it was working. I then did the nooter 0.2 rebooted and verified I had adb then I checked for in store features and I got nothing I rebooted it twice connected to my PC and twicce disconnected from my PC and still nothing. What if they check to see if adobe is enabled? I don't think nooter 0.2 does anything else.
[Nook Color General] pulser_g2:
What do you mean by "check to see if Adobe is enabled"?

You mean an app being installed or something?
[Nook Color General] nikto34:
This is of help! Thanks... IF we can figure out what specific files are being changed during the rooting process then maybe we can find the culprit. I am really thinking the answer lies on the changes done to the /data.

Does anyone have a stock packages.xml that we can compare to the rooted version?
[Nook Color General] devis:
per the request of nicto34 i am uploading my version of build.prop

P.S. This was done using a WM6 phone...
[Nook Color General] nikto34:
This is helpful! In comparing this build.prop file to the build.prop of a stock 1.0.0 NC, it appears that the files are almost identical except for a few lines that are ones that are generated based on build of the NC. The only real difference is with the fingerprint which we have tried changing multiple times previously.

Therefore, I think the build.prop is not the issue and we need to look at another option which I think lies in the /data portion of the rooting. As mentioned and suggested previously possibly the packages.xml file.

My next steps are to root my stock NC with nooter 0.2 and do nothing else. I will then take to B&N to try. IF I still have instore features, I will begin changing one variable at a time and see what happens. A slow process but needed to confirm what may be the issue.

If someone has a stock packages.xml file and a rooted packages.xml that we can compare this would be extremely helpful as we move forward.
[Nook Color General] pulser_g2:
One of my posts explains the manual process to root, and tells the line that is changed. I'd suggest editing the packages file rather than swapping it, given the database is used by the system to record apps installed.

I think it's a tiny change
[Nook Color General] nikto34:
Any tips on how to get the packages.xml file off a unrooted NC? I have adb setup on my system (Windows 7 x64) but can not seem to access my NC unless I root the device.
[Nook Color General] nikto34:
I can confirm that using any process to root the NC results in no access to instore features.

My latest attempt, I took my stock 1.0.0 NC and rooted with nooter 0.2. I did nothing else and then went to B&N. Rebooted and had no access to instore features.

So I am confident in saying the issue lies in the /data portion of the root.
[Nook Color General] Homer_S_xda:
OK, so I think we need to do one of two things, or maybe both. 1) Do the manual root and see if In-Store is available. 2) Go the other way and dump the untouched partitions to an SDCard, boot from that "unrooted" and see if that works. The 2nd way might have advantages in that you could run around rooted like we want and when you happen to be at a BarN, pop in the other card and enjoy the In-Store features.

Homer
[Nook Color General] thisisjjd:
I don't have a Nook Color, so I may be talking out of my hat.

Since it didn't seem as if the fingerprint in the build.prop file had any effect on in-store features, perhaps another approach would be the browser User-agent presented on http requests.

Can someone use an unrooted nook color and a rooted nook color to check what User-agent the browser presents? You can use this website to check the user-agent: whatsmyuseragent.com

My T-Mobile G2 presents:

Mozilla/5.0 (Linux; U; Android 2.2; en-us; T-Mobile G2 Build/FR91) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1

My wife's Droid (1) presents:

Mozilla/5.0 (Linux; U; Android 2.2.1; en-us; Droid Build/FRG83D) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1

Perhaps it is as simple as the BN server checking the user agent presented by a web request?

Just a guess.
[Nook Color General] fatfingered:
This is from my virgin NC, still on 1.0.0 from the factory, using the stock browser.

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_7; en-us) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Safari/530.17

:confused:
[Nook Color General] CygnusTM:
I just got back from B&N. My daughter's stock regular nook was able to access the in-store features, but my rooted NC was not. It was able to before I rooted it. Just another data point...

My rooted NC with 1.0.1 reports the same with both the stock browser and Dolphin HD.
[Nook Color General] thisisjjd:
Hmm. Well I guess if rooted and unrooted have the same user-agent, that can't be it. Oh well! Thanks for testing.
[Nook Color General] rlkelley:
I hope this topic has not died....
[Nook Color General] likearaptor:
I am not sure if we will ever get this working since B&N is giving us free epubs for an hour and the promotional material. One way we might get around this is getting the stock nook software to boot from an sdcard. Then when we want store features we boot from that sd card use it and then take it out when we are done. Here are some posts I have found:

http://xdaforums.com/showthread.php?p=10510859

http://xdaforums.com/showthread.php?t=873243

But it looks like we have to root the nook in order to get a copy of the system, so the copy we will make will be disabled. Oh well back to the drawing board :) Has the developer of the Nooter 0.2 said what happens when the image is ran on the Nook? It would be good to figure out what he/she changes to get adb working that is disabling in store features
[Nook Color General] brgavino:
Anyone think we can do a packet trace?

If anyone has experience with wireshark, there's a sniffer available on the market:

"Shark for Root"

I'd run it myself, but I don't regularly go to B&N stores. If we can get a dump of a stock NC connecting to instore wifi, then a dump of a rooted NC, that might help a bit.
[Nook Color General] fatfingered:
How would one run wireshark on an unrooted NC?

One would need to have a laptop to sniff wifi traffic, if that's possible.
[Nook Color General] nikto34:
I am working on creating a bootable uSD card that can be used when one wants to go to a B&N store to use the instore features.

Currently, I am having a little difficulty getting the mmcblk0 pulled. I am working on pulling the stock boot files as these are backed up in the /dev section of the NC which allows for the fail-safe boot of the NC.
[Nook Color General] likearaptor:
I would be able to do this next week on the 21st with my rooted nook, but hopefully someone can get to it sooner so we can make some more progress. I downloaded the app and did some sniffing on my device, works great
[Nook Color General] Musicman247:
I can go tomorrow to a store, start sniffing, then turn the wifi off then back on on one of the display NookColors. I should be able to post the resulting file by tomorrow afternoon (as long as I can get it off my Nook).

Edit: Figured out I could email myself the file. I'll post it tomorrow afternoon.
[Nook Color General] shadow349:
You may not need it. If you can see the conversation that is taking place, you might be able to deduce what values the B&N servers are expecting.

The problem is that if the connection is secure, then Wireshark probably won't be of much help since the conversation will be encrypted at a layer above where Wireshark sees it.
[Nook Color General] brgavino:
Very true

I'm almost tempted to spoof the B&N SSID and see if I can get it to trigger any client (NC) initiated traffic just to see what we're dealing with, before someone wastes any time.

If before then someone posts a log, I'll be happy to look it over.
[Nook Color General] fatfingered:
I have an extra router that I need to update dd-wrt on, to play around with this idea. :D

I'm sure there is some additional server side authentication going on in the background then something this simple.
[Nook Color General] KDHaro:
Yes, see this post: http://xdaforums.com/showthread.php?p=9688146#post9688146
[Nook Color General] Homer_S_xda:
I think until B&N releases an update with Froyo, I'm taking my Nook Color back to stock on the internal. Nookie Froyo will run off an SDCard and I have one that is Class 10. So, Like I said, I'm taking the NC back to stock on the internal and then run NFroyo off the card. That way, I'll run off the card when I'm out and about and then when I find myself in a B&N, unmount the card, eject and reboot. Voila, the NC looks like it should to B&N.

Homer
[Nook Color General] Musicman247:
Here is the B&N packet dump from shark.

I went into the store with shark running. Went to Nook display stand. Turned on a NookColor. It connected to the store's network. I went to the shop home, then read a book In-Store. Then opened the browser and went to engadget.com, then went to xdaforums.com. I then turned off the wifi, turned it back on and repeated these steps except going to xda first, then engadget.

Haven't looked at the file yet, but hope it helps in our quest!
[Nook Color General] jgriesel:
I do not think we captured any B&N communication with this particular sniff.

What I see in it is a quick check to 65.172.31.185 from the IP Address of 10.131.90.40 and then a bunch of communication between the 10.131.90.40 with a remote server at 74.125.45.188.

The 65.172.31.185 is probably an Akami appliance based upon the Whois look up below.

NetRange	65.172.31.128 - 65.172.31.255

CIDR	65.172.31.128/25

Name	SPRINTLINK

Handle	NET-65-172-31-128-1

Parent	SPRINTLINK-2-BLKS (NET-65-160-0-0-1)

Net Type	Reassigned

Origin AS

Nameservers

Organization	AKAMAI TECHNOLOGIES, INC (AKAMA-31)

Registration Date	2010-05-18

Last Updated	2010-05-18

And the 74.125.45.188 is probably some Google server based upon the Whois info below.

NetRange	74.125.0.0 - 74.125.255.255

CIDR	74.125.0.0/16

Name	GOOGLE

Handle	NET-74-125-0-0-1

Parent	NET74 (NET-74-0-0-0-0)

Net Type	Direct Allocation

Origin AS

Nameservers	NS2.GOOGLE.COM

NS3.GOOGLE.COM

NS4.GOOGLE.COM

NS1.GOOGLE.COM

Organization	Google Inc. (GOGL)

Registration Date	2007-03-13

Last Updated	2007-05-22

I would bet that all this particular sniff captured is the communication between Musicman247 sniffer and the systems his device was communicating with. The Wireless APs that B&N uses I am sure function similar to an Ethernet switch, which means that all we can capture is the traffic from the specific device running the sniffing software and the broadcast traffic that is sent to all nodes attached to the Wireless AP network.

The best we can do with the Wireshark running on a Rooted Nook is the communication between that Nook and the B&N services. The only way to capture the traffic from a non-rooted Nook is to setup a Man in the Middle attack and get a non-rooted Nook to connect to this fake AP which in turn captures the packets between the Nook and the B&N servers.

But before we do this, a complete sniff of a Rooted Nook communicating with the B&N services is probably in order. Best to take a Nook to B&N with wireless off, start the capture, turn wireless on and check out the B&N store.

P.S. I did not see any user info in the Google communication, but you might want to change your account password.
[Nook Color General] scuffe82:
boot and rom images pushed back

So i attempted to push the stock 1.0.1 /boot ramdisk and stock /rom max image back to my rooted device, the device functions fine and strangely enough i still have ADB access to it after a reboot but i did not gain in-store features back. This had been mentioned in the nooter thread from the devs that it might make a difference from what i could tell nothing changed :-(
[Nook Color General] leo662:
I was doing a search for "magazine subscriptions" & I think this might have answered my question but want to clarify. I'm not new to rooting, jailbreaking, custom ROM's, etc...having completed this on previous iPhones & my current Sprint Hero.

I'm interested in getting a Nook Color with rooting in mind. B&N offers some magazines (& possibly books?) for "Nook only"...that is to say they are only available on a physical Nook device, not Nook for Android/PC/etc. If I were to get a NC, can I buy/access these magazine subscriptions if (a) the NC is rooted with the stock ROM and/or (b) the NC is rooted with a custom ROM (either hard installed or installed to SD only)?
[Nook Color General] Homer_S_xda:
I had this issue also. I have not followed up on it.

Homer
[Nook Color General] dct3416:
I can't speak for the custom ROMs but the stock rooted device definitely allows these items to be purchased and viewed from the Nook.
[Nook Color General] rlkelley:
Something that may have been overlooked

So in the discussions about trying to block the 1.1 upgrade someone mentioned a list of urls in their devicemanager.db

The thread: http://xdaforums.com/showthread.php?t=930477

this is the line they found:

PREF,BNCLOUD_INSTORE_URL,https://bncsis.barnesandnoble.com/bncloud/serviceDI

Any chance that this helps?
[Nook Color General] JamesEcht:
Full in-store access restored. I'm sitting in B&N right now with full in-store access on my Rom 1.1-updated rootedNC. Updating via the ROM CWRmod method seems to restore full access.
[Nook Color General] autumnmist:
I wish we knew why so we know if this is something on B&N's side or something special about the config of this ROM.
[Nook Color General] SCIONTX:
"Read in Store" works for me as well now. I was on 1.0.0 when I originally rooted (nooter0.2). I reset, updated to 1.0.1 and 1.1.0 and re-rooted using nooter0.2. I enabled Market manually by generating an AndroidID. I did not replace the stock framework.jar file with the one that's included in the Google Apps package (nc_gapps.zip).
[Nook Color General] Musicman247:
Just to clarify: You have full In-Store access after flashing to the 1.1 pre-rooted image? Or did you update to 1.1 and root the device some other way?
[Nook Color General] cal3thousand:
I'm going tonight with my 1.1 R1 prerooted to check it out.

I suspect that 1.1 has code that will allow a rooted device, 1.0.x will work if NOT rooted, and all unrooted will work.
[Nook Color General] Musicman247:
Let us know what happens! :D
[Nook Color General] :
It's true for me too. After flashing the 1.1 rooted update in the Dev forum I am able to enjoy both the benefits of rootin and all the in-store features as well! I don't us thos features that often, but it is nice to have them once in a while. I just wish we would have gotten them back before the free smoothies coupon was gone!
[Nook Color General] sbddude:
Can confirm that it works for me also on 1.1.0.

I was able to start reading a free instore book. As an experiment i turned off wi fi. My free book immediatey dissapeared. When i tuned wifi back on, it sait my hour had expired, evven though i've ony been st the store for a few minutes.
[Nook Color General] khaytsus:
I really think what you all are seeing is that B&N has finally fixed in-store reading. I suspect if I went in today I could read at B&N.

My unrooted NC nor my wifes could read at B&N when we got ours in late December and Early January respectively.

Perhaps I'll try it this weekend for S&G...
[Nook Color General] Homer_S_xda:
Is there some definitive way to know that In Store is working? A screenshot would help. I tried again yesterday at the B&N in Vernon Hills. I don't see any difference in the Shop than it behaves when I am at home.

Thanks,

Homer
[Nook Color General] mjc8870:
I have flashed 1.1.0 v2 from development forum over rooted 1.0. Everything is working perfectly except BN in-store services.

Do you think this is because I nootered with version for 1.0 . (.15). Any suggestions to get in store services working?
[Nook Color General] jwortiz:
JamesEcht,

Can you clarify further on the steps you took? I think it will help those interested (like me) on accessing in-store features, such as free eBook reading, etc..

Thanks
[Nook Color General] jwortiz:
Homer,

When you're connected in-store, the shop button will have an "in-store" ribbon across the upper-right corner of the shop icon. It is similar to the "New" ribbon you get when you download a book. You will get free access to available eBooks for reading in-store. You'll sometimes see some specials popping up on the screen, if any.

Hope this helps...
[HD2 Android Q&A, Help & Troubleshooting and Genera] Mafioso:
Hi Guys,

So there are many Desire HD Sense build around now for the HD2. I've tried them few though most of the issues have been sorted out and are smooth also. They still don't feel as snappy as the regular sense and I don't see much advantages over regular sense...the flying animations are also there in MDJ Revolution build....Is it about the extra eyecandy only for which all this hype is...or am I missing something :confused:

Regards
[HD2 Android Q&A, Help & Troubleshooting and Genera] akbisw:
Im on froyo hd 4.3 by mdeejay. AND IT ROCKS. Desire HD builds have latest gen sense which is highter resolution(Several elements are smaller so that they fit in the screeen) that Evo and everything just looks better.
[HD2 Android Q&A, Help & Troubleshooting and Genera] pack21:
For me the bigest advanced of HD builds, is the extended goodies in Browser, and for me is faster than other froyo's.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Mafioso:
Well I don't use the inbuilt Android Browser Much...its mosty opera mini for me..becoz its faster and saves bandwidth...

One thing i liked though is inbuilt task list in notification bar...its definitely a cool feature..
[HD2 Android Q&A, Help & Troubleshooting and Genera] dj_ghosie:
The percentage battery bar, keyboard with arrows and revised font size are worth the using of the Desire HD Rom.
[HD2 Android Q&A, Help & Troubleshooting and Genera] -deuces-:
for me: 1)lcd density (displays more on the 4.3 inch screen, unlike before...it showed the same as a 3.2" device)

2)htc sense . com

3)customizable (skins, skins, skins!!!!)

3) improved camera
[HD2 Android Q&A, Help & Troubleshooting and Genera] FrAsErTaG:
I agree with op, the desire hd builds lag.. This is no fault of the developers as it lags on a DHD...

Personally vanilla android wins my vote.
[HD2 Android Q&A, Help & Troubleshooting and Genera] victorbd:
i liked the desire HD build until the superfast rom i got with quadrant score 2775 :S itz the fastest smoothest i had till now... no lags at all..using 2 memory cards now... :P one for desire HD one for JDMS ultimate

http://xdaforums.com/showthread.php?t=782301&highlight=arabic