• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Does anyone have a link that meets the following recipe...

saintdanbert

Well-Known Member
The op here needs to be updated, there is an image on xda that will load any nc rom zip onto the sdcard. I'm posting from my phone or I'd paste links. I'll probably get on the pc later and post some links.

Does anyone have a link that meets the following recipe:

  1. download these URL(s): A, B, ..., Y, Z
  2. {optional}unpack this archive or zip file or tar-ball with
    Honeycomb(preferred) or Gingerbread(minimum) or Froyo(last resort) edition of SD-bootable Android and friends
  3. make your micro-SD (uSD) media writeable on your workstation
  4. write file(s) from the archive onto the uSD media using
    • 'dd... command' -- for linux
    • 'windows imager command -- for Win-doze
    • 'whatever' -- for Mac
  5. do XXX to confirm that your uSD card is written correctly
  6. remove the uSD card from your workstation
  7. power off your Nook Color; insert your newly written SD card
  8. power-on your Nook Color
  9. do A, B, C, ... , X, Y, Z as post-install, post-boot configuration
  10. do A, B, C, ... , X, Y, Z to fetch and install valuable 'droid apps (like Market and various google apps)


If someone can make an ISO and install an entire linux workstation or server distro, surely someone can make a tar ball that has all of the parts
required to write an uSD card that is bootable on a Nook Color and that
has enough apps to make it useful.

Puzzled by why this is so very difficult to accomplish,
~~~ 8d;-/ Dan
 
... you seriously need to consider putting on Gingerbread. CM7 is stable, and Phiremod 6.1 is the preferred ROM and works beautifully. You do lose B&N instore reading and Read-to-me books, but can still access all your B&N books through the Nook App. But what you are left with is pure Gingerbread goodness. You can also dual boot OS, if you want to keep stock.

When I search around I find dozens of posts in various places that talk about Gingerbread and CM7 on a Nook Color uSD card. Can someone post a link to something that does not require a PhD in Tinker-ology to accomplish?

If someone can make an ISO that is an entire workstation distro, surely someone can make an archive that one can 'dd' onto uSD media.

Frustrated,
~~~ 8d;-/ Dan
 
http://androidforums.com/nookcolor-...ok-color-rooting-rom-guide-read-me-first.html

It has instructions for many options, including http://androidforums.com/nookcolor-...how-download-install-cm7-run-off-sd-card.html .

Here is my attempt at a simplified recipe:

Ingredients:

(1) Win32 Disk Imager
(2) Size-agnostic SD Card image
(3) CM7 build of your choice (zip file)
(4) latest gapps (zip file)
(5) Nook Color
(6) Micro SD card (everyone says to use Class 4. There are widespread reports of problems with Class 10 cards.)

Preparation:

1. Use Win32 Disk Imager (1) to write SD card image (2) to card
2. Copy CM7 zip file (3) to SD card
3. Put SD card in NC, boot. CM7 will unpack and install itself.
4. reboot NC, set up network connection.
5. Turn off NC, remove SD card
6. Copy gapps file (4) to SD card,
7. Place SD card in NC, boot into recovery mode, GAPPS will unpack and install
8. Enjoy!

I've intentionally left links out, except for the link to instructions and the imager software. This is to encourage/force you to read the instructions on the pages above.

If you're unsure what you're doing, I recommend going with a stable build, not a nightly. Finally, remember that in CM7 world, The NC is Encore. Make *SURE* you get a build (nightly or stable) for Encore, not any other CM7 project!
 
I moved this to it's own post since it's slightly off-topic and could get lengthy.

DanBert, you don't make sense. First you want a highly technical list of features, then you ask for a newbie guide. :D

I suspect you want a bootable disk or exe that'll do all the work for you, but when you rattle off a long list of technical terms like you did, that tells me you're capable of following any of the guides we have posted here and be a better person when it's all done. It's like building your own car versus Dad giving you one. Which one are you going to appreciate more?

Trust me when I say, that flashing a bootable sdcard, booting off of it and running a few commands in recovery gives you the start of skills that you can use if your Nook becomes unbootable and you need to repair it.
 
I moved this to it's own post since it's slightly off-topic and could get lengthy.
I think that this is a good thing, but I don't understand the whole "move" part. What changed? Are there not two separate threads? Do they each have links to the other part?

DanBert, you don't make sense. First you want a highly technical list of features, then you ask for a newbie guide. :D

I'm not asking for a "newbie guide". Rather, I'm asking for help sorting through what I see a dozens of posts with multiple links all saying variations of the same thing.

While I consider myself a technical guy, what I'm reading does not make sense to me. In my experience, that means one of two things:

  1. The available information is valuable as is, but there are some details that I don't know or don't understand well enough to make use of that value. In other words, "I don't know what I don't know or understand."
  2. The available information would be valuable to someone who is thoroughly competent on the subject and all of the supporting details and concepts. Someone less competent (myself) therefore trips over the missing details that the more competent person implements without thinking about them. As a result, the instructions, as written, are not complete.
I suspect you want a bootable disk or exe that'll do all the work for you, but when you rattle off a long list of technical terms like you did, that tells me you're capable of following any of the guides we have posted here and be a better person when it's all done.

If I could build industrial instruments with 1995 Yggdrasil linux (Yggdrasil Linux/GNU/X - Wikipedia, the free encyclopedia) I believe that I can follow instructions. I even know how to use dd instead of WindowsImager or similar, so lets get specific as an example.

The instructions say, "insert the uSD card into your workstation." Depending on one's distribution and configuration all sort of things might happen automatically when a workstation sees a new media card. Notice that I said, "might happen." The instructions that everyone seems so proud of fail to mention what they expect to happen based on their use of the simple word, "insert."

A reasonable expectation might include having the existing fat32 file system mounted and read-write to the current workstation session. Oh, wait:

  • is the file systems supposed to be fat32?
  • if not fat32 then which file system?
  • before there are file systems there must be partitions
  • before partitions there must be a partition table
  • which partition table -- "msdos" is a reasonable expectation, but ...
  • is it supposed to be mounted at all?

I say all of this to illustrate that there are "instructions" and there is a "recipe" in my opinion. A "recipe" provides a general list of ingredients and a general list of things to do. (I recently used one that called for a knob of butter, where "knob" was defined as "a couple of tablespoons more or less." (Hardly a precise ingredient.). In contrast, "instructions" are detailed and precise. If prerequisite knowledge is important, "instructions" will identify precise requirements.

I have read dozens of "recipes" for making the desired uSD card.
I have tried several that looked promising.
I have yet to find success among my readings and efforts.
I came here to ask for guidance and maybe find assistance.
It's like building your own car versus Dad giving you one. Which one are you going to appreciate more?
What I said, and what I seek are a very far cry from this simplistic admonishment.
Trust me when I say, that flashing a bootable sdcard, booting off of it and running a few commands in recovery gives you the start of skills that you can use if your Nook becomes unbootable and you need to repair it.
I found several uSD card sellers and could have placed my order online. Instead, I chose to roll-my-own for the precise reason you mention here.

I will continue to tinker and hope to find success.

I will continue to read Android Forums and hope to find guidance and maybe help for this and future situations.

Cheers,
~~~ 8d;-/ Dan
 
I think that this is a good thing, but I don't understand the whole "move" part. What changed? Are there not two separate threads? Do they each have links to the other part?

I moved your posts to the root section. (I was thinking I split it off from another topic.) :D

The instructions say, "insert the uSD card into your workstation." Depending on one's distribution and configuration all sort of things might happen automatically when a workstation sees a new media card. Notice that I said, "might happen." The instructions that everyone seems so proud of fail to mention what they expect to happen based on their use of the simple word, "insert."

A reasonable expectation might include having the existing fat32 file system mounted and read-write to the current workstation session. Oh, wait:

  • is the file systems supposed to be fat32?
  • if not fat32 then which file system?
  • before there are file systems there must be partitions
  • before partitions there must be a partition table
  • which partition table -- "msdos" is a reasonable expectation, but ...
  • is it supposed to be mounted at all?


When you write an image to a disk (of any type), the file system of the image is written to the disk. Makes no difference what was on it.

I will continue to tinker and hope to find success.

I will continue to read Android Forums and hope to find guidance and maybe help for this and future situations.

Cheers,
~~~ 8d;-/ Dan

I agree that some forum will simply say to download this image and write it to your sdcard. The guides here do not do that. When we link to one, we try to find a good one.

I think it's best to just try one and see what happens. It's pretty hard to brick a Nook. :D
 
...When you write an image to a disk (of any type), the file system of the image is written to the disk. Makes no difference what was on it.
This is why one names the device and not a partition for the output file option to the 'dd' command.
Code:
prompt$  dd  if={image file name}  of={device name} bs=NN {other options}
QUESTION: For SD-media aimed at the Nook Color, what is an appropriate value for block-size (bs) option?
I agree that some forum will simply say to download this image and write it to your sdcard. The guides here do not do that. When we link to one, we try to find a good one.
Agreed ... when it happens. Either way, a post might be better if it says just that: "I looked at A, ..., Z posts and decided Q was the best." Couple that with a link to Q and explanation of whatever wrinkles you needed to iron out.
I think it's best to just try one and see what happens. It's pretty hard to brick a Nook. :D
I've tried several with the same result: NOOK CONTINUED TO BOOT NOOK. Let me see if I understand things:

  1. I need one mumble.img as the bootable part of uSD contents. {note 1}
  2. I use dd to write that image to the media device
  3. There are several ZIP files {note 2} to add to the uSD root folder.
    • the CyanogenMod "froyo", "gingerbread" or "honeycomb" archive
    • the 'gaaps' archive -- google applications, including the Market
    • optional archive(s) -- overclocking and other "patches"
  4. with the uSD mounted at the workstation, use cp to move these archvies to the uSD root folder
  5. insert the uSD to the Nook with the power off.
  6. at power on, the Nook is expected to load the image &c from the uSD and present a pure Android desktop (home screen).
CLARIFICATION -- One must unmount the uSD from the workstation after step #4 before on can remove it from the workstation read-write adapter.

CLARIFICATION -- While the Nook Color allows hot-swap of the uSD media when running in Nook Color mode, it is the power-on restart at step #5 that provokes the boot-from-uSD process.

Note 1 -- I think the image is "ClockWork" something or is it some file inside the CyanogenMod download or something else?

Note 2 -- I expect that the image file runs code that unpacks these archives and loads them at boot time in much the same way that workstation bootstrap uses a compressed ramdisk image.
QUESTION -- Is it possible to use "tar.gz" or "tar.bz2" instead of ".zip"?

Have I missed anything?

If I've got this much right, only one (sic) question remains?
Where do I download a complete set of files to use above?
 
Have I missed anything?

Yes, what exactly are you trying to do? I assume flash a rom to a sdcard and dual boot with the stock rom.

When they say to flash an img to your sdcard, you just pick the image, load it into WinImage or W32 imager and flash it. If it doesn't boot, then it's usually operator error due to a naive user and/or bad instructions (or a corrupt file or use of a usb hub/unreliable adapter).

Many guides are tailored to an experienced user. If you have to use adb scripts to flash a rom, you're using the wrong guide since most of that stuff can be done a friendlier way. (I've only used adb a couple times in the last 2 years and one was to root my phone and the only way available at the time.)

Are you aware that sdcard installs are slower, more fragile (they eventually fail, some after a few months), more difficult to update and most guides/software don't take them into account, so they're easier to trash. I've never needed, wanted or flashed a rom-on-a-bootable-sdcard. </endrant>

The ONLY rom you should be considering would be the stock B&N rom (if you HAVE to have the stock reader and the Android readers don't cut it for you) or CM7. Gingerbread is a Frankenstein hack with files from different phones & tablets. It's slow and buggy. I believe the last latest and greatest version I saw was from April. Froyo is so old it's a joke. Gingerbread is faster, more stable, has better battery life and even has daily builds.

That said, Chocophile gave you good advice yesterday with a link to a guide one of our users created here. None of our rom guides use adb for something that can be done easier without.
 
I'm running Ubuntu Lucid (v10.04 LTS) and use DD to write the image.
I've done that for years writing other bootable images without any grief.
By the way, some of the online "instructions" provide details for using DD
to write the bootable part of the Nook Android uSD.

Cheers,
~~~ 0;-Dan
 
Yes, what exactly are you trying to do? I assume flash a rom to a sdcard and dual boot with the stock rom.
Yes, this is exactly what I am trying to accomplish.
When they say to flash an img to your sdcard, you just pick the image, load it into WinImage or W32 imager and flash it. If it doesn't boot, then it's usually operator error due to a naive user and/or bad instructions (or a corrupt file or use of a usb hub/unreliable adapter).

Many guides are tailored to an experienced user. If you have to use adb scripts to flash a rom, you're using the wrong guide since most of that stuff can be done a friendlier way. (I've only used adb a couple times in the last 2 years and one was to root my phone and the only way available at the time.)
I've used ADB to update or patch my smartphone, but I've avoided those "instructions" for the Nook uSD card effort.

Many of the "instructions" include links for the various parts they want you to use. Few "instructions" mention available md5sums. It is the rare download target that offers md5sums. This makes it difficult to discover if one has a viable download, but at least I know to look.
Are you aware that sdcard installs are slower, more fragile (they eventually fail, some after a few months), more difficult to update and most guides/software don't take them into account, so they're easier to trash. I've never needed, wanted or flashed a rom-on-a-bootable-sdcard.
</endrant>
I never saw where you started ranting so this is not necessary.
If you have never tried any of the available dual-boot "instructions" perhaps a trip down that road might help you better understand what is causing this poster so much grief.
The ONLY rom you should be considering would be the stock B&N rom (if you HAVE to have the stock reader and the Android readers don't cut it for you) or CM7. Gingerbread is a Frankenstein hack with files from different phones & tablets. It's slow and buggy. I believe the last latest and greatest version I saw was from April. Froyo is so old it's a joke. Gingerbread is faster, more stable, has better battery life and even has daily builds.

That said, Chocophile gave you good advice yesterday with a link to a guide one of our users created here. None of our rom guides use adb for something that can be done easier without.
Thanks for the reminder (and thanks, again, to Chocophile). I will take another look at the "instructions" suggested. I will also take good and detailed notes and bring back my results.
Was this http://androidforums.com/b-n-nookco...-link-meets-following-recipe.html#post3400491 the post you had in mind?

Cheers,
~~~ *<;-}( )( )// Dan
finally some cool weather in Texas
 
Sorry, I've briefly tried Linux, but not a fan of that so not going to be much help. Most of the guides here assume Windows since I'd hate to guess how a Linux install might work like.

Unless you're able to borrow a Windows computer, I would think you're either going to have to wing it or find a Linux-based guide if our sdcard guide doesn't work.

Yes, that's the correct link and it even references Linux equivalents.
 
To all who have made comments here, THANK YOU, Thank you ver-uh much. (sorry Elvis)

I'm now hot on the trail of a solution. I'll be back (sorry Arnold) once I have
something that works.

I can tell you a couple of things that I have learned:

1. The partition table is, in fact, an "msdos" partition table
Master boot record - Wikipedia, the free encyclopedia

2. Using an "msdos" table means that there is a "boot record" and not more than four(4) primary partitions.

3. The dual-boot Android seems to want fat32 for the boot partition and the end-user data space.

4. Programs such as WindowImage and dd (linux) treat a disk device as a string of bytes: byte(0) ... byte(last). This includes any bytes used for a "boot record" or "partition table".

5. The correct "image file" -- obtained by download or extracted from a downloaded archive -- will include any required "boot record" and "partition table" as well as some other software. Writing this image file directly to the disk device (your uSD card) fills in all of the bits (sic) needed to boot software using that uSD card.

In Summary, you write an image to the uSD card getting a bootable device with some software including partitions. You might need to use this freshly booted Android to "format" those partitions. Next, you need to add more software, reboot and enjoy your Nook.

ASIDE -- I put this into a category called "Confirming that I know
what I think I know."

Thanks,
~~~ 0;-Dan
 
I never found a solution to this item and want it to "drop dead".
I don't want to mark it "solved" because it is not.

How do I mark a thread as a "dead end"?
~~~ 0;-Dan
 
We don't delete posts and don't usually lock them unless it turns nasty with fighting.

There is no "solved" option.

You could edit your first post if you feel the need to change the wording.

Until you revived it, it was working it way toward the bottom of the heap as new posts are added... :D
 
Back
Top Bottom