Related
So I downloaded the 1.0.1 update. It is a zip file and appears to be valid (I can open it and see the files inside).
I plug my NC into the PC and two drives show up. One is the internal storage and the other the SD card I added to the NC.
I place the zip file for the update into the root of the internal storage as the instructions on the Nook support site say. Then I do a safe remove which causes the NC drives to disappear from the system. I unplug the NC.
It sits there. I wait. It mocks me. I wait some more. It finally goes to sleep. I wait some more. I turn it back on and it isn't updated. I plug it back into the PC and the update file is now gone.
I must be doing something really dumb but can't figure out what it is.
Phergus said:
So I downloaded the 1.0.1 update. It is a zip file and appears to be valid (I can open it and see the files inside).
I plug my NC into the PC and two drives show up. One is the internal storage and the other the SD card I added to the NC.
I place the zip file for the update into the root of the internal storage as the instructions on the Nook support site say. Then I do a safe remove which causes the NC drives to disappear from the system. I unplug the NC.
It sits there. I wait. It mocks me. I wait some more. It finally goes to sleep. I wait some more. I turn it back on and it isn't updated. I plug it back into the PC and the update file is now gone.
I must be doing something really dumb but can't figure out what it is.
Click to expand...
Click to collapse
You're are not doing anything wrong, it can take a while. Don't quote me on this but I became impatient and turned my device off after a while then turned it back on and bingo, that did the trick. I'm not sure if that is recommened however so you may want to ask this eithe rin the root thread or wait for a reply here from someone else.
Edit:
Also check out the nook colors irc channel for help, that worked for me when I needed help with my EVO.
irc.freenode.net #nookcolor
Thanks. I tried doing the power off cycle in one of the umpteen iterations I've tried but had the same effect.
Does it matter that I have the Android SDK installed? Can't imagine why as it is up to the Nook to see the update and then apply it.
Phergus said:
Thanks. I tried doing the power off cycle in one of the umpteen iterations I've tried but had the same effect.
Does it matter that I have the Android SDK installed? Can't imagine why as it is up to the Nook to see the update and then apply it.
Click to expand...
Click to collapse
I don't think it would matter, cause I had android sdk on my laptop when I did the update.
Phergus said:
I must be doing something really dumb but can't figure out what it is.
Click to expand...
Click to collapse
Is your Nook rooted? I don't think you can apply the update without unrooting...
Not rooted. But I finally figured out what it was. There is something funny about their update zips. Even though the zip file seemed to be fine if looked at in 7-Zip when I did a MD5Sum on it the number was different than what others reported.
So I re-downloaded and then immediately did a MD5 on it. Came out correctly.
So without further mucking with it I copied it to the Nook, ejected, unplugged, put it into Sleep mode, waited a couple minutes and my Nook finally did the update.
In case anyone else comes across this here is the MD5Sum on the 1.0.1 zip update.
2a25b1b63608887800fa97ab681d70f8 *Sideload_update.zip
MD5 is correct for me, file is in the root of my SD card, but it just... doesn't do anything.
Any other ideas?
Whoops. Now I know what it was. It has to be in the root of the eMMC partition ON BOARD THE NOOK, not the SD card.
Recently purchased a CN with a serial # starting with 2005 and running 1.0.0. Want to upgrade to 1.0.1 to be able to use Auto-Nooter however the new 1.1 is only showing on b&N.com , have been searching for hours with no luck. Thanks
Nevermind found it
If/when I learn to use that dropbox or w/e it is, I will be able to help more
The B&N link will take you to the 1.1.0 release. However if you copy the link and then paste it into your address bar you can change the link to point to the 1.0.1 release. You will need to change the "v1.1" directory to "v1.0.1" and you should be able to download the 1.0.1 Sideload file.
http://dl.dropbox.com/u/9943171/Sideload_update.zip
If theres a lot of interest Ill post it to megaupload
I am having a problem with the Nook app on CM7 (using the 4th nightly and the OC kernel.)
Doing some quick searching and extensive looking hasn't yielded any results directly related to the following issue.
When looking in my library, if I try to download a book it just says "No such file or directory" and my other books that are on my SD card don't show up/can't open them with the app (No Application Found).
So, just wondering if anyone else has got this working, I would really like to use this as an e-reader.
Thanks
Ran into the same problem last night
lycwolf said:
I am having a problem with the Nook app on CM7 (using the 4th nightly and the OC kernel.)
Doing some quick searching and extensive looking hasn't yielded any results directly related to the following issue.
When looking in my library, if I try to download a book it just says "No such file or directory" and my other books that are on my SD card don't show up/can't open them with the app (No Application Found).
So, just wondering if anyone else has got this working, I would really like to use this as an e-reader.
Thanks
Click to expand...
Click to collapse
I ran into the same problem last night when my wife was trying to buy a book. I am on v2 though!!!
lycwolf said:
I am having a problem with the Nook app on CM7 (using the 4th nightly and the OC kernel.)
Doing some quick searching and extensive looking hasn't yielded any results directly related to the following issue.
When looking in my library, if I try to download a book it just says "No such file or directory" and my other books that are on my SD card don't show up/can't open them with the app (No Application Found).
So, just wondering if anyone else has got this working, I would really like to use this as an e-reader.
Thanks
Click to expand...
Click to collapse
Nook app works okay on nightly #4. I am having wifi issues, so I am not sure about downloading anything.
try the solution from this thread, it worked for me
http://forum.xda-developers.com/showthread.php?t=966339
bigtourist said:
try the solution from this thread, it worked for me
http://forum.xda-developers.com/showthread.php?t=966339
Click to expand...
Click to collapse
Tried that solution and it doesnt work when trying to download books. I always get file type not supported. You?
yes, it does work when downloading books. make sure you follow it exactly.
you have to set the EXTERNAL_STORAGE value to /sdcard like it says and NOT /mnt/sdcard
Tibedabeeto said:
Tried that solution and it doesnt work when trying to download books. I always get file type not supported. You?
Click to expand...
Click to collapse
It does work.
bigtourist said:
yes, it does work when downloading books. make sure you follow it exactly.
you have to set the EXTERNAL_STORAGE value to /sdcard like it says and NOT /mnt/sdcard
Click to expand...
Click to collapse
Plus 1 for "Yes, it does work."
bigtourist said:
yes, it does work when downloading books. make sure you follow it exactly.
you have to set the EXTERNAL_STORAGE value to /sdcard like it says and NOT /mnt/sdcard
Click to expand...
Click to collapse
I did change that but I didnt notice that I had to type out adb shell before typing su for the apk. I get permission denied, does that mean I missed something while rooting my nook?
Edit:
NM adb shell works, just didnt work from terminal emulator. Anyways tried everything from adb and a computer and still no dice. I have no clue why this is not working. The books in my files dont have the cover and when I click on it it looks like it will load then just goes back to my files again.
NM, it seems that the books that were already in my library from when I had the regular nook OS was giving me issues. I went to shop for a new free book to see what happened and it downloaded and worked. So I did it right from the beginning but kept trying the same 2 stupid books. lol Thanks
I'm not sure what's going on here.
I tried following through with the directions posted in the link. But my adb shell seems to be repeating whatever I type after I press enter. It doesn't seem to be working.
Is there something I'm doing wrong?
I'm using phiremod.
Okay, so I found something... I think.
I did export EXTERNAL_STORAGE /sdcard
and I got
export: /sdcard: bad variable name
Any suggestions?
WORKING Nook ereader app on Nook Color running CM7 from sd card
I wanted to be able to have access to 2 barnes and noble libraries on the same device. I looked around and this is what I came up with. You don't need to do any really tricky or invasive mods and it works great. I'm mostly a moron so I wrote this for people who are like me, please don't be offended if you have to say "well duh" alot.
I would read the notes at the bottom of the post after you read this.
1. I prepared a CM7 sd card with google apps!!! using this method:
http://forum.xda-developers.com/showthread.php?t=1000957
***(I used the stable CM-7.1.0-RC-1-encore-signed version + current gapps, but it should work with any current CM7 nightly)
2. I powered down my nook completely, inserted the CM7 sd card, powered it back up, and let the CM7 installer routine run. The installer shuts the nook off when complete, then I rebooted into CM7. After registering to my google acct and getting to the home screen, I clicked on the icon in the bottom left corner (3 little horizontal lines) and selected Settings>Applications>Unknown sources...check that box.
3. Opened the Market app. Searched for "appinstaller" and installed AppInstaller by FunTrigger. Then I completely powered down my nook and removed the CM7 sd card.
4. Then I downloaded an older version of the Nook ereader app (ver 2.5) and put it somewhere in my filesystem that was easy to locate (you will be locating it from linux) from here:
http://www.freewarelovers.com/android/app/nook
5. Then on a PC running Linux (ubuntu 11), I plugged the sd card I put CM7 on into my computer. In linux you can see all the partitions...in windows all you can see is boot. I opened the "CM7 SD CARD" partition, and I put the nook.apk file I downloaded from freewarelovers right in there.
6. I reinserted the CM7 sd card into my nook and booted it back up. I went to applications, ran AppInstaller and clicked on the "nook.apk" icon and installed it. Registered my B&N account normally and populated my library.
Notes:
* DO NOT add the nook.apk into the native OS. This is only for CM7. If you try to add this app to an OS with the native nook reader working (unrooted/nootered) the device gets stuck in a boot loop which you will have to use CWM or 8 fail boots to recover from.
* I bear no responsibility for any damage you may do to your device by using this method. That said, it is almost impossible to brick a nook color, especially using a sideload OS. If you think you did just look around the forums, there is lots of information on how to unbrick a nook color.
* If you do not have Linux running on anything to read the CM7 partitions, you can google "reading ext4 filesystems in Windows" and figure out how to do that. Mac is Unix based, so maybe you could use a mac and just hope no one finds out. I highly suggest you just make a live CD by following the directions here:
https://help.ubuntu.com/community/LiveCD
* Incidentally, you can use this method for sideloading any apps into your sd-based CM7 environment.
Why would you need to sideload the Nook app? Is it hiding in the market these days??
No it's there but you can't download it. Either says invalid device or it won't give you the option to install at all.
EDIT: I updated to a current nightly and it allowed me to download the ver 2.6 Nook reader, but the sign in screen is garbled and it won't communicate with the B&N servers. Had a similar issue with Netflix, which I also sideloaded an older version of and works well.
@ mastigia.
Firstly, very appreciate your effort and post instructions for others.
Secondly, why would you want to go with that route?
At least, there are 2 options installing Nook App with ease.
a. Download and install directly from Market. (see note 1)
b. If for sideloading, just use usb cable to tranfer the .apk over, no need to remove the uSD then insert into Linux just to copy the file.
Note 1: If you can't see Nook App on the Market, then fix your Market first.
Note 2: another option (would be 3rd) is using ADB (either over USB or wireless to push file over)
why oh why
votinh said:
@ mastigia.
Firstly, very appreciate your effort and post instructions for others.
Secondly, why would you want to go with that route?
At least, there are 2 options installing Nook App with ease.
a. Download and install directly from Market. (see note 1)
b. If for sideloading, just use usb cable to tranfer the .apk over, no need to remove the uSD then insert into Linux just to copy the file.
Note 1: If you can't see Nook App on the Market, then fix your Market first.
Note 2: another option (would be 3rd) is using ADB (either over USB or wireless to push file over)
Click to expand...
Click to collapse
Ok...
a. I CAN see the app on the market. The app currently available is ver 2.7 which from the previous build of CM7 I was using had "Incompatible Device" where the "Install" button would normally be. So, I updated to CM7 nightly 209 thinking I was an idiot. And hey, whaddya know, that made it possible for me to install the 2.7 reader from the market. But it was garbled and would not communicate with the B&N servers and caused me some really crappy synching issues later which I won't go into here.
b. This is just for getting the nook.apk onto CM7 loaded on an sd card. The prob with just moving the file over usb is that windows (which I started off using) will only pick up my native emmc because the sd card partition I want to move the .apk to is in an ext4 partition. Using adb wireless I was unable to find the mount point, once again probably for the same reason.
So, to clean that up I would say just plug your nook into linux and move the file over usb and that would probably work and thanks for the suggestion, I just did not think of that.
Ya know this is kind of a silly and unique issue. I got my gf a nook color, she wants her own library and an unrooted nook (warranty). She also wants access to MY library (which has alot of books she would like to read) and apps like netflix (which also requires a legacy version). Books are the primary reason we got nooks. So for someone like ME, thats the post I would need.
Anybody having force close issues with the latest Nook app? I'm running 213 and I can download but anytime I try to open anything I get a force close.
Okay, if you have received the 1.3 update or you want to get it, this has worked for a few people now (thanks to billingdl for figuring our walking this path first!). This has only been tested for going from rooted 1.2 to 1.3. No idea on how it will fare with other changes.
You will need a bootable CWM card for this procedure. Look here for that. Then put these files on it:
manualnooter-4-5-18.zip
manualnooter-4-6-16a.zip
Note: Rom Manager is included as part of MN.
You'll notice that MN has an 'a' on it. I added two things there: the final fix for build.prop that was never updated and I also added a script to update the database to block OTA updates (this has worked for me) as found here.
Okay, so here we go...
1. Get the 1.3 update. YOU WILL LOSE ROOT! But don't fret - you shouldn't lose anything else.
2. Shut down your nook and boot with the bootable card.
3. Install manualnooter-4-5-18.zip and then reboot.
4. You have root now, so go launch the market and sign in.
5. Shut down your nook again and boot with the bootable card.
6. This time install manualnooter-4-6-16a.zip.
6a. If you want to, you can also install Dalingrin's OC kernel while you're here, which he recently updated with the 1.3 source. Your choice, but the file is here.
7. Reboot again.
8. Put your regular "data" SD card in for this step - Go into Rom Manager and run the 'Fix Permissions' option.
9. Go into Nook Color Tools and note the check box at the top. After 1.3 for most (if not all) people, the label is missing now. Uncheck and check the box anyway and close NCT.
10. Reboot
and Voila! All should be working!
root seems to be back after step four, but I wasn't unable to open the market until loading up 16a. Looks good so far though!
Your instructions didn't work for me
I purchased a Nook Color in July. It came with Froyo 1.2. I rooted it using Manual Nooter 4.6.16 shortly afterwards and was loving it!
Then last night, the Nook OTA auto-updated me to the Nook 1.3 firmware.
This morning when I picked up my Nook, I noticed that my Android Market, Google Email and Calendar apps icons had changed. When I tried to start them, I got a "App not found" error message. Then after some exploration, I discovered that I had I had lost Root access.
I followed your instructions. After installing Manual Nooter 4.5.18 and rebooting my Nook, I had root access again. However, when I tried to run the Android Market app I got a prompt saying "loading...", then the app closed.
I tried a couple of times with the same outcome. I then ran Rom Manager, was prompted for super user access and allowed it. I then selected the fix permissions option and rebooted the Nook, but the Android Market app still had the same issue as above.
I then figured I move ahead and install Manual Nooter 4.6.16a in hopes it would fix the problem. After applying it and rebooting my Nook, I again tried to start the Android Market app. This time, on the first attempt to run it, I was prompted to set up a Google account. I selected the existing account option and provided my account name and password. I received a confirmation that my android device was now associated with my Google account.
When I attempted to run the Google Market app again, I experienced the same issue as above. I got a prompt saying "loading...", then the app closed.
I again used Rom Manager and selected the Fix Permissions option and rebooted my Nook again. After rebooting I still have the same problem with Android Market app - starts to load then closes.
Now I'm stuck...
Anyone else experiencing the same behavior? Anyone have suggestions for how I might fix the issue?
For those of you who have been lucky enough to dodge the Nook OTA 1.3 firmware auto-update, I'd highly recommend you disable your wireless until you are able to turn off the auto-upgrade to avoid this unpleasant experience.
I'd be very happy to return to Nook 1.2 firmware with Manual Nooter 4.6.16. It was working perfectly for me and allowed me to access, load and run Android Market apps without any problem.
...Steve
ManualNooter was never about blocking updates, it's about keeping the device as fully functional as possible INCLUDING updates while adding more to the device such as a proper Android Market. Unrooting was always going to be a side effect of the update, which should of easily been fixed by by just reapplying 4.6.16. As for the build.prop "final fix", what exactly is that?
Also any indication on WHY this works would be more helpful than you repackaging 4.6.16 with stuff it wasn't designed to have.
GabrialDestruir said:
ManualNooter was never about blocking updates, it's about keeping the device as fully functional as possible INCLUDING updates while adding more to the device such as a proper Android Market. Unrooting was always going to be a side effect of the update, which should of easily been fixed by by just reapplying 4.6.16. As for the build.prop "final fix", what exactly is that?
Also any indication on WHY this works would be more helpful than you repackaging 4.6.16 with stuff it wasn't designed to have.
Click to expand...
Click to collapse
Wish I could say why it works. Like I said, the only thing I did with it was put the build.prop fix in and add the ota change. But others had it work using the last published MN of 4.6.16. I'd love to be able to say it was something I did, but it's not. I was just trying to pull everything together for folks...
sbrack01 said:
I purchased a Nook Color in July. It came with Froyo 1.2. I rooted it using Manual Nooter 4.6.16 shortly afterwards and was loving it!
Then last night, the Nook OTA auto-updated me to the Nook 1.3 firmware.
This morning when I picked up my Nook, I noticed that my Android Market, Google Email and Calendar apps icons had changed. When I tried to start them, I got a "App not found" error message. Then after some exploration, I discovered that I had I had lost Root access.
I followed your instructions. After installing Manual Nooter 4.5.18 and rebooting my Nook, I had root access again. However, when I tried to run the Android Market app I got a prompt saying "loading...", then the app closed.
I tried a couple of times with the same outcome. I then ran Rom Manager, was prompted for super user access and allowed it. I then selected the fix permissions option and rebooted the Nook, but the Android Market app still had the same issue as above.
I then figured I move ahead and install Manual Nooter 4.6.16a in hopes it would fix the problem. After applying it and rebooting my Nook, I again tried to start the Android Market app. This time, on the first attempt to run it, I was prompted to set up a Google account. I selected the existing account option and provided my account name and password. I received a confirmation that my android device was now associated with my Google account.
When I attempted to run the Google Market app again, I experienced the same issue as above. I got a prompt saying "loading...", then the app closed.
I again used Rom Manager and selected the Fix Permissions option and rebooted my Nook again. After rebooting I still have the same problem with Android Market app - starts to load then closes.
Now I'm stuck...
Anyone else experiencing the same behavior? Anyone have suggestions for how I might fix the issue?
For those of you who have been lucky enough to dodge the Nook OTA 1.3 firmware auto-update, I'd highly recommend you disable your wireless until you are able to turn off the auto-upgrade to avoid this unpleasant experience.
I'd be very happy to return to Nook 1.2 firmware with Manual Nooter 4.6.16. It was working perfectly for me and allowed me to access, load and run Android Market apps without any problem.
...Steve
Click to expand...
Click to collapse
I decided to go back and give it a try again from the top. (I had nothing to lose).
The second time I applied MN 4.5.18 and rebooted, the Android Market started working. I was able to connect and I tested installing an app just to make sure it was fully functional.
Great - Then I figured I try to move forward and re-apply MN 4.6.16a. After doing so and rebooting, the issue with Android Market app NOT working returned, ("loading..." message followed by a shutdown of the app). I then realized that wifi wasn't working properly after applying MN 4.6.16a. Checking the settings panel revealed that wifi was off. Every attempt to turning on wifi resulted in a wifi error. Tried applying ROM Manager 'Fix Permissions' again just in case - but wifi problem persisted.
So, I decided to go back and reapply MN 4.5.18 once more. Voila - the wifi and the Android Market started working again.
So I'm now running with MN 4.5.18 and Nook firmware 1.3
I should note that I did apply the optional over-clocking update that you included in your instructions above after applying MN 4.6.16a. Don't know if that is related to the wifi problems I experienced.
Anyway - I've got my Nook Rooted again and running Android Market so I'm happy.
Hope the above info is useful to others who might have the same experience I did.
...Steve
FYI... Did some more follow-up. Tried another version of MN 4.6.16...
Seems that MN 4.6.16 with Nook firmware 1.3 breaks wifi. After applying it, checking the settings panel shows "error" under wifi and wifi is off. Attempts to enable it result in a wifi error. Checking the Nook device info shows an empty MAC address.
So on my Nook there's definitely something incompatible between MN 4.6.16 and Nook firmware 1.3. On doing some googling, wifi improvements are mentioned as one of the optimizations included with firmware 1.3. So maybe that's where the issue lies.
Anyway it's easy to re-apply MN 4.5.18 and once that's done things seem to work fine with firmware 1.3.
...Steve
Try removing the Kernel from 6.16 and see if that works.
sbrack01 said:
FYI... Did some more follow-up. Tried another version of MN 4.6.16...
Seems that MN 4.6.16 with Nook firmware 1.3 breaks wifi. After applying it, checking the settings panel shows "error" under wifi and wifi is off. Attempts to enable it result in a wifi error. Checking the Nook device info shows an empty MAC address.
So on my Nook there's definitely something incompatible between MN 4.6.16 and Nook firmware 1.3. On doing some googling, wifi improvements are mentioned as one of the optimizations included with firmware 1.3. So maybe that's where the issue lies.
Anyway it's easy to re-apply MN 4.5.18 and once that's done things seem to work fine with firmware 1.3.
...Steve
Click to expand...
Click to collapse
There are many variables in getting BN1.3 to be rooted and functional:
1. the method to get to BN1.2: upgrading to BN1.2 via wifi or restoring to BN1.2 via Nemith's zip file.
2. whether CWM is installed on emmc or not.
3. green dot NC or not?
Thanks to OP, i have my NC 1.3 rooted and functional. By the, Flash 10.3 is part of NC 1.3. This is how I got there:
- restore to stock BN1.2 via Nemith's zip file with no CWM on emmc.
-apply MN4.5.18
- get NC working with gmail, apks', etc... still on BN1.2 but rooted
- side load BN1.3 update
- apply MN 4.5.18 - but be sure to wait until it's done 10-15 minutes
- apply MN 4.6.16a
- fix permissions
- install Dalingren's updated OC kernel
Everything works like a champ.
Thanks don caruana! I followed your instructions exactly and they worked perfectly! Like another poster, I didn't have the market back until after I uploaded MN 4-6-16a but everything is back to normal now. Yay!
If I am running cm7 off emmc, i should not even get prompted for this update, correct?
I am not dual booting, just straight cm7!
I'm having a problem.
I was on 1.2 w/MN 4.6.16 and get the OTA to 1.3.
I just flashed MN 4.5.18 and rebooted.
When I launch market, I get a message saying "you must add an account to the device to continue. Do you want to add one now"? If I select either yes or no, it takes me back to my home screen.
What do I do now?
lexluthor said:
I'm having a problem.
I was on 1.2 w/MN 4.6.16 and get the OTA to 1.3.
I just flashed MN 4.5.18 and rebooted.
When I launch market, I get a message saying "you must add an account to the device to continue. Do you want to add one now"? If I select either yes or no, it takes me back to my home screen.
What do I do now?
Click to expand...
Click to collapse
Try going in to gmail and setting up your account there, then go back to the market. You could also clear data for the market and see if that helps.
doncaruana said:
Try going in to gmail and setting up your account there, then go back to the market. You could also clear data for the market and see if that helps.
Click to expand...
Click to collapse
Gmail and Talk both automatically close immediately, clearing data for market doesn't change anything. I got into youtube, chose my channel and it took me to an add account option and when I click that it says "there was a problem authenticating."
Now what?
lexluthor said:
Gmail automatically closes immediately, clearing data for market doesn't change anything. I got into youtube, chose my channel and it took me to an add account option and when I click that it says "there was a problem authenticating."
Now what?
Click to expand...
Click to collapse
That kinda sounds like a network issue of some sort. Try logging into your account from your pc. Also, can you browse the internet with the nook?
doncaruana said:
That kinda sounds like a network issue of some sort. Try logging into your account from your pc. Also, can you browse the internet with the nook?
Click to expand...
Click to collapse
Account works fine on the PC. Nook can browse the internet.
Any other ideas? Argh.
lexluthor said:
Account works fine on the PC. Nook can browse the internet.
Any other ideas? Argh.
Click to expand...
Click to collapse
You know, I had the issue where the market closed immediately on me when I tried to put mn4.6.16 on first. You could try a few things here...
Try going ahead with 6.16 and see if that works
or
Reapply 5.18
or
Reapply the 1.3 update and start over with the process
Unfortunately this thing seems to be a bit of a mystery (no one even knows why 5.18 first works for some), so just keep plugging at it and report back in case anything inspires someone more knowledgeable than me.
I reapplied 5.18 and then rebooted, same thing.
I then applied 6.16a and rebooted. This time I got the same thing about needing to added an account, but when I said yes, it let me add the account.
I then ran fix permissions and rebooted one more time for good measure.
Things all look good now!
Thanks so much.
Hopefully this helps anyone else with the same issue.
I guess I don't have to worry about a future OTA forced upon me now since I used the "a" version. What exactly does the "final fix for build.prop" do though?
lexluthor said:
I reapplied 5.18 and then rebooted, same thing.
I then applied 6.16a and rebooted. This time I got the same thing about needing to added an account, but when I said yes, it let me add the account.
I then ran fix permissions and rebooted one more time for good measure.
Things all look good now!
Thanks so much.
Hopefully this helps anyone else with the same issue.
I guess I don't have to worry about a future OTA forced upon me now since I used the "a" version. What exactly does the "final fix for build.prop" do though?
Click to expand...
Click to collapse
Glad that worked for you!
The build.prop thing is an issue where the original intent of MN was to change the fingerprint of the device for improved market visibility. It was supposed to change to "samsung/GT-P1000/GT-P1000/GT-P1000", but the script had an error and it just got left at zoom2. I can't tell you what the difference in visibility is, but it was a fix that never got implemented, so I slapped it in there.
BTW, I'm sure you're skittish at this point, but you might want to look at Dalingrin's OC kernel, if you haven't already. Although the first thing I'd do is take a full backup with CWM!!
Happy "Nook"ing!
Thanks doncaruana!
This worked for me too, however, I had the same initial problem with Market as two other posters where it would FC when fired up as per your instructions. But after applying the MN 4.6.16a, it fired up fine. I'm wondering if it had to do with my SD card though. I did not have my "normal" SD card installed when I first fired up Market, but I did have it in once I had applied MN 4.6.16a, so no big deal. Just successfully downloaded/updated a dozen apps. from the Market with no problem and definitely have root again. System reports BN software version 1.3.0. Thanks again for all of your work on this, esp. regarding no OTA updates; obviously the otacerts.zip rename doesn't work since that's what I had in place and I still got 1.3 pushed!
One question for you though - does the DB OTA fix disable any BN features other than OTA updates (e.g. in store stuff, etc.)?
A few folks have asked for a step-by-step, so I thought it might be helpful to have a copy here on XDA. GMPOWER has recently created a thread on his ManualNooter for NC 1.4.1 which should be considered the authoritative source on the basic rooting process. I'm going to leave this post here to collect other tips & tricks that can be done post-root.
I want to emphasize that I did none of the original work required for this effort to succeed. I only seem to follow instructions carefully, and know just enough to figure out what instructions to ignore. I'm posting this here because I'm hoping other will benefit from skipping a few of the painful steps I went through to get this working. All credit goes to GMPOWER, Dalingrin, Roustabout and the wonderful crew at XDA that create these tools to let us get more out of our devices!
TARGET AUDIENCE
This guide is for anybody wanting to root the stock Barnes and Noble 1.4.1 firmware. Is it worth it? Probably not. With all the options available today, reverting to B&N makes sense if, and only if, if you want to use any of the following B&N capabilities:
Read to me (mostly children's book)
Enhanced content (e.g. Conde Nast magazines such as Wired, New Yorker, though some of these are becoming available via 3rd party sources.)
Newpaper or magazine subscriptions (auto-update)
B&N Free in-store reading
Support from friends with stock Nooks or B&N (conditional upon being rooted)
The B&N reader experience and shell. The B&N Android Nook app is not the same thing as their firmware experience, at least not yet. Someday, they may update the B&N Nook Android app, but it is pretty poor right now. If you want to read B&N stuff, then 1.4.1 is a big deal.
If these apply, consider keeping your NC at B&N 1.4.1. If you want 3rd party content (e.g. Kindle), then root it, but make sure you've got it configured NOT to auto-update, since B&N has killed sideloading with OTA updates.
If you will not be using B&N content, then go with Cyanogenmod or similar. The B&N firmware suffers a lot of shortcomings compared to the "full tablet" experience:
Lots of settings are missing.
Getting a 3rd party keyboard to work is possible, but very kludgy at present. I had luck with SwiftKey by copying the apk from /data/app to /system/app as directed in NookColor Tools.
If you're looking to install CyanogenMod or other firmware, check out Koopakid08's A Noobs Guide to Getting Started with a Custom Rom on the Nook Color.
BACKGROUND
I started out reading and trying the procedure described the XDA thread on rooting 1.2 and 1.3:
[NC][1.2][1.3] ManualNooter 4.6.16 - xda-developers
However, it is critical to realize that the directions early on in that thread do not work for 1.4.1. The magic starts at about page 160. Below is my distillation of this information in easy-to-digest form (hopefully).
PROCESS
You need to create a ClockworkMod (CWM) bootable SD card to reset your device back to standard B&N firmware, and to install the "manualnooter" root kit. Colchiro has posted a nice summary over at Androidforums. His guide includes the latest (3.2.0.1) CWM versions.
Restore to stock B&N ROM. I'd been running CM7.1 on emmc, so had to go through the process of restoring to a stock B&N 1.3 ROM. Depending on the age of the article you read on how to do this, you may have problems either formatting /data or get into a boot loop at the 'n' logo. You need a current CWM to be able to successfully format /data. If /data is not properly formatted, you will get a bootloop at the B&N splash screen when you restart. Not a big deal to fix, but you can waste a lot of time on this. As of this writing, CWM 3.2.0.1 is the latest, and should allow you to format partitions without problems.
After restoring to B&N 1.3, I re-registered my device to make sure B&N functionality would work. After all, the only reason to bother with 1.4.1 is if you intend to use B&N content. Otherwise, save yourself the trouble. NOTE: We are not root yet.
Update to 1.4.1. I got my copy of 1.4.1 directly from B&N [EDIT 01162012: I have verified that the latest as of this date still works as described here.] Your Nook Color will also update to the latest if you just let 1.3 unrooted go to sleep if you don't have ClockWorkMod installed to eMMC. I have confirmed that this procedure works with the following nookcolor_1_4_1_update.zip md5sum: 2a27f54b65431a096af4f07967bcd6b5 (post-Christmas 2011)
Once 1.4.1 was running unrooted, I then followed GMPOWER's efforts over at XDA. The key is to run an updated version of manualnooter that does not make the database updates. As of this writing, his latest 5.01.24 can be found in post 1745. So far as I know, the official manualnooter repositories have not been updated.
Copy manualnooter-5.01.24.zip (or whatever the latest is) to your bootable SD recovery card.
Boot the recovery SD card.
Install manualnooter-5.01.21.zip.
Remove the recovery SD card and reboot your NC. It boots any card present, so this is kinda important. Behold the pretty startup screens. You should have root at this point.
Be sure to select Zeam as your initial launcher. Note that if you press the 'n' key at this point, you'll be taken back to the B&N interface, and not have ready access to anything non-standard. This is not a big deal. Simply press 'n'->Search and enter zeam in the search box. It should locate zeam. Select it to launch.
To enable 3rd party apps to load, you must open the NookColor Tools program. There's a magic check box that enables 3rd party apps at the top. By default, the text is white on white, so impossible to see. Select that box twice - to uncheck then recheck (toggle) it. When you are done, it should be checked.
To get 3rd party apps to show up in the Nook interface, download Nook Color App Manager from the Market. HINT: Don't go overboard and select everything. Select only those things you really want to see in the B&N Walled Garden. You might also want to select the HomeCatcher app (included in ManualNooter) to allow using the 'n' button to go to your launcher of choice, but I do not. My philosophy is to keep the B&N interface as much as possible, or I wouldn't have gone to all this effort. When I need "power user" functions, I just launch zeam using the search procedure listed above.
Disable OTA updates. B&N auto over-the-air (OTA) updates apparently break root, and lately, sideloading. There seems to be some debate about what works best for this, but I've gone for modifying the devicemanager.db using SQLite Editor to open devicemanager.db and change registry->com.bn.device.fota.mode from "auto" to "manual". You can use an alternate method with a free sqlite3 binary from the command line. So far, no nasty OTA surprises.
COMMON PROBLEMS
Here are some common problems and what to do about them:
Can't overclock. GMPOWER has indicated that an overclocked kernel is not provided as of manualnooter-5.1.24. You need to install Dalingrin's overclocked kernel for B&N 1.3 (NOTE: Dalingrin's hosting site for these files seems to be offline. Doncarauana has posted a set of temporary links to the kernel files you can try. You will also need a copy of Dalingrin's Nook Color Tweaks installed.
Can't format /data when restoring to stock firmware. You probably followed an old guide on how to do this. Depending on the age of your NC, the version of CWM you're using may not handle partition changes. You need to update CWM. See Step 1, above.
Bootloop at the 'n' logo when trying to restore B&N firmware.You probably goofed. Hard as it is to believe, it's very easy to miss the fact that /data wasn't formatted. This is the same problem as the preceding problem. Just follow Step 1, above, and be sure /data actually gets formatted.
1.4.1 is rooted, but unable to install anything from Android Market or Amazon App Store. When this happens, everything appears to be working, but after downloading, apps will fail to install. They key is to use GMPOWER's latest manualnooter and do not ever, even once, install one of the older versions. Refer to Steps 4 and 10, above. I had to restart from scratch to make up for not paying attention and running the old manualnooter versions. Something to do with a database patch that causes problems.
Facebook and other apps are missing from Android Market. UPDATE: This is fixed with GMPOWER's manualnooter-5.01.24.zip. (For other apps: A simple workaround is to install the app onto another Android device, then use Android Assistant to make a backup .apk and copy that to the Nook Color. If you only have a Nook Color Android device, you can create a bootable SD with CyanogenMod (see above) and install to that, then use this procedure to copy the .apk over.)
UPDATES
2/14/2012: Updated to add link to manual procedure for blocking OTA updates using sqlite3.
2/13/2012: Updated to include link to GMPOWER's thread on his ManualNooter for NC 1.4.1.
2/6/2012: Updated links for Dalingrin's overclocked kernel to include Doncarauna's temporary links.
1/24/2012: Updated to reference GMPOWER's manualnooter-5.01.24, restored references to Dalingrin's OC'ed 1.3 kernel.
1/22/2012: Updated to reference GMPOWER's manualnooter-5.01.21, remove references to APPS2SD not working. It's working now! Removed overclock kernel as a concern. GMPOWER's latest MN includes it. Added link to Colchiro's SD HOWTO at Androidforums.
1/16/2012: Updated description of 1.4.1 update now that I've verified this procedure works with the latest, and added link to SQlite OTA blocking procedure.
1/11/2012: Updated link to GMPOWER's ManualNooter update to be more concise.
Thanks, This really helped me to get my nook rooted.
So running CM7.1 off a sd card is another way in a good way or is there a better way to root a NC. The reason I ask is because I am running of a SD and it stalls on me when i go to turn it off and back on. Is there something I need still to download.
ciscom25 said:
So running CM7.1 off a sd card is another way in a good way or is there a better way to root a NC. The reason I ask is because I am running of a SD and it stalls on me when i go to turn it off and back on. Is there something I need still to download.
Click to expand...
Click to collapse
Sounds like your CM install is screwed up. It should have no problems powering on and off. However, if you don't care about the B&N stuff, you'll be better off installing CM to internal (eMMC) storage so you're not dependent on the SD card and can use it freely.
This guide is only about rooting the stock firmware if you decide you do want the B&N stuff. Koopkakid08 has a great summary on alternate firmware strategies.
Your link for the MN 5.x.x post needs to point here: http://forum.xda-developers.com/showpost.php?p=20456719&postcount=1631
Taosaur said:
Your link for the MN 5.x.x post needs to point here: http://forum.xda-developers.com/showpost.php?p=20456719&postcount=1631
Click to expand...
Click to collapse
I'll update to include the single post you pointed to, and move the full-thread discussion to a separate APPS2SD issue at the bottom. I think that will make the step-by-step clearer, while still pointing to the ongoing efforts GMPOWER is working on.
I urge anybody rooting 1.4.1 to track the ongoing discussion and GMPOWER's updates.
Thanks!
Bumpity bump
Do these instructions assume you have CWM already installed? Sorry I got lost at "Copy manualnooter-5.12.XX.zip, or whatever the latest is, to your bootable SD recovery card." because I have no idea what you mean by "bootable SD recovery card". Do I need to create this?
Followed directions
Am rooted but none of the nook tools apps are present when launching zeam
Neither are Gapps.
Must they be flashed separately or were they supposed to bepart of the flashing procedure for manual nooter
Looking at manualnooter-5.12.20, you should have an older version of the Android Market app, gmail, calendar, contacts, maps, homecatcher, rom manager, superuser, talk, YouTube and SoftKeys. What are you missing?
wasnt said:
Do these instructions assume you have CWM already installed? Sorry I got lost at "Copy manualnooter-5.12.XX.zip, or whatever the latest is, to your bootable SD recovery card." because I have no idea what you mean by "bootable SD recovery card". Do I need to create this?
Click to expand...
Click to collapse
the bootable SD recovery card is where you install the CWM. creating this recovery card is the first step you to root the nookcolor. Not only you need it to install the manualnooter (MN), it also allows you to reset to stock setting and other good stuffs.
Good catch, guys. I've inserted a new step 1 which points to a guide for creating a bootable CWM card. Thanks for pointing out that omission.
"Updated to reference GMPOWER's manualnooter-5.01.21, remove references to APPS2SD not working. It's working now! Removed overclock kernel as a concern. GMPOWER's latest MN includes it."
Thanks for this thread.
Does this mean you are able to use Nook Color Tweaks to overclock? I upgraded to MN 5.0.1.21 but I still get an error message in Nook Color Tweaks
" Kernel is not compatible with Audio settings. A newer build of CM7 or Dalingrin's overclock kernel is required"
Also, any idea where I can obtain the kernel other than somehow pulling it from a CM7 build?
Thanks,
Ken
Help! I really messed up this time.
I followed the instructions to install 1.3.0 but did not update to 1.4.1 and then I completed the root. I see the Android Market and can actually buy an app. However, installation hangs at "authorizing" because, according to Android Market support, the Nook is not authorized to load apps from the Android Market. So, clearly something is wrong. Either nobody can run those apps, which I doubt, or I messed up.
To compound the problem, I default to Zeam Launcher and cannot boot into B & N. I have also tried to force a reset by 8 failed starts but that did not work. This Noob could really use some help to fix the problem.
chengka said:
"Updated to reference GMPOWER's manualnooter-5.01.21, remove references to APPS2SD not working. It's working now! Removed overclock kernel as a concern. GMPOWER's latest MN includes it."
Thanks for this thread.
Does this mean you are able to use Nook Color Tweaks to overclock? I upgraded to MN 5.0.1.21 but I still get an error message in Nook Color Tweaks
" Kernel is not compatible with Audio settings. A newer build of CM7 or Dalingrin's overclock kernel is required"
Also, any idea where I can obtain the kernel other than somehow pulling it from a CM7 build?
Thanks,
Ken
Click to expand...
Click to collapse
A kernel was not included in any of the MN releases for 1.4.1, you will need to download the Dalingrin kernel to use Nook Color Tweaks, LINK
rkulp said:
I followed the instructions to install 1.3.0 but did not update to 1.4.1 and then I completed the root. I see the Android Market and can actually buy an app. However, installation hangs at "authorizing" because, according to Android Market support, the Nook is not authorized to load apps from the Android Market. So, clearly something is wrong. Either nobody can run those apps, which I doubt, or I messed up.
To compound the problem, I default to Zeam Launcher and cannot boot into B & N. I have also tried to force a reset by 8 failed starts but that did not work. This Noob could really use some help to fix the problem.
Click to expand...
Click to collapse
The direction were for firmware 1.4.1, since you have firmware 1.3 you can update to 1.4.1, or follow these directions, LINK
Thanks! I have CM7 on way too many devices, tee hee, so I wanted to go back to stock on the reader to compare battery life.
Download Dalingrin's OC Kernel
Thanks for the guide! Working great but I can't seem to find a functioning download link for Dalingrin's kernel. Anyone have one?
I found Dalingrin's kernel here:
http://forum.xda-developers.com/showthread.php?t=925451
Some folks are having problems with some of the links, though.
Great guide, I tried CM7 on the SD Card, but I just found that I like the plain look of the B&N interface. Using your guide as a template I nootered my Nook, and will be doing my wife's later. I am also looking for Dalingrin's OC Kernel, I have had it from previous nooters, but my hard drive crashed, and I had erased all of my microsd cards, because I had all the files on my hard drive . So if anyone has a working link, or could send me the file I would greatly appreciate it.
Thanks, RDRANGER
Downloading binaries of any sort from an unknown source makes me queasy, but if you're feeling daring, there's a post in the Dalingrin 1.3 kernel thread to a copy. Use at your own risk, etc.