yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Sherip:
OK, I think its working fine. Once I successfully registered (took two attempts, don't know why since I verified my info) Nook store items listed and I noticed a notification that it was "Preparing SD card, checking for errors." Its been long enough that I don't think it plans to say when its finished.

Under My Files on the Library screen, there are two tabs: Device and SD Card. Device has a Notifications folder with an m4a media file in it. SD Card has 6 files (kernel, MLO, ramdisk, ramdisk.cwm, u-boot.bin and uImage) plus an empty folder called LOST.DIR.

I think this will be useful, I'll be able to collect the Friday free apps from the Nook Store if interesting.

Regards,

Sheri
[Nook HD, HD+ Android Development] Sherip:
How do I make it boot to recovery so I can install the new extras zip? Have tried holding in the n button while powering on, tapping the n button when I see Cyanoboot, holding the n and power buttons until booted (hard to do), etc., but it always restarts the Nook OS.
[Nook HD, HD+ Android Development] leapinlar:
You should be able to get there by holding the n and power keys together for 5 seconds or so after the cyanoboot logo comes on. Then release and it should boot to recovery.
[Nook HD, HD+ Android Development] Sherip:
Thanks, I got it to show the SD Clockwork menu, but I had the zip file in the root folder of the card, and apparently I need to get it onto the internal storage. Also tried renaming it update.zip on the card and still couldn't see it. I'm sure it will be fine once I get it onto internal storage.

Regards,

Sheri
[Nook HD, HD+ Android Development] Windsor1959:
Could this be done for HD as well? No biggie if it's not worth the trouble; I just have a spare sd card and it might be fun to play with.
[Nook HD, HD+ Android Development] RhinoNelson:
suggestion

I am coming from the Nook Tablet to the HD+. One of the 'feature' of Cyanoboot was the ability to choose what the tablet booted from - EMMC, SD Card, an Internal alternate boot image, Recovery, etc. Adding this feature to the current NookHD+ Cyanoboot would allow us to not have to remove/reinsert the SD Card depending on the operating system chosen. I have no idea of the amount of work this would require but if it were doable at some point in the future it would be an incredible plus. I believe it was conceived as a plus to the developing community to allow them to easily test different environments but it had major plusses for the end user as well.

And if these kinds of posts aren't appropriate I apologize in advance - I am extremely appreciative of the time and energy the developers invest on our behalf.
[Nook HD, HD+ Android Development] leapinlar:
Cyanoboot does work on the CM10.1 SD but for some reason does not work on the stock SD. So if you leave stock on emmc and make a verygreen SD for CM10.1, I have a cyanoboot that works. If you want it to have CM10.1 on emmc and stock on SD, it fails. Get it at my HD/HD+ CWM thread linked in my signature.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] Stevethegreat:
As per my previous experience with this the issue can be easily solved by installing quickboot from play store. Rebooting via quickboot gets you to SD-Stock, "Recovery" gets you to SD's recovery and "Bootloader" gets you to EMMC-CM10. Also if you want to boot to EMMC's recovery you can do that by rebooting to "bootloader" using CM10's reboot menu.

I think the greatest issue with trying to work both OSes like that is that there is no way to use both storage spaces from either OS. Stock is "blind" to EMMC and CM10 is "blind" to the SD Card which is rather annoying in my case because I lose half my storage that way. I tried the old leapinlar's fix and naturally it didn't work for EMMC-CM10
[Nook HD, HD+ Android Development] Sherip:
What about rebooting to emmc from the stock SD card? Do you install Quickboot on the SD card (stock) too?

Sent from my Nook HD+ Running CM 10.1 from emmc
[Nook HD, HD+ Android Development] Stevethegreat:
Yes the same is true if your reboot from SD-Stock via quickboot (the only option lacking is rebooting to EMMC's recovery which can only be reached via CM's "reboot to bootloader" option)...
[Nook HD, HD+ Android Development] Sherip:
Works, thanks! I think I may be able to live with this SD card kept in place rather than only inserted once in awhile. The only time it might be a pain is during a cold start.

Sent from my Nook HD+ Running CM 10.1 from emmc
[Nook HD, HD+ Android Development] ShapeShifter499:
I second this.... also can we turn off secure mode for a EMMC install of stock?
[Nook HD, HD+ Android Development] verygreen:
I'll try to look into it on the next weekend, it's been on backburner for some time.
[Nook HD, HD+ Android Development] Sherip:
Something odd happened today with my stock SD running. I had booted it to get the Free Friday app. It prompted (with notifications) to update some Google play apps, which I approved, then walked away for 5 or 10 minutes. When I came back, it was on the SD clockwork recovery screen where you are supposed to move the pointer down a bunch and enter to confirm a pending update. The pending update was something like "insecure update zip". Could rooted Nook stock on SD card have attempted an auto-update?

Sent from my Nook HD+ running CM 10.2 from SD card
[Nook HD, HD+ Android Development] verygreen:
I bet that's exactly what happened.
[Nook HD, HD+ Android Development] RageAgain:
Hey verygreen,

Have you looked at what might be involved in updating this to the 2.1.1 build yet? Thanks again for all the hard work...
[Nook HD, HD+ Android Development] Sherip:
I booted my stock SD card tonight and everything was working except the Nook shop. It said something like "Unable to load data." Is the Nook shop app still working for others who have stock on SD? I was also unable to download books in my library. But the browser was working so nothing was wrong with my connectivity.

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] Sherip:
I fixed it by wiping data (factory reset) in cwm and reregistering.

Sent from my HD+ Running CM 10.1 from emmc
[Nook HD, HD+ Android Development] RageAgain:
Nook HD+ Stock 2.1.1 on SD Card

I turned the Nook HD+ 2.1.1 update .npk into an SD Card update .zip by deconstructing verygreen's stock 2.1.0 for SD, and it seems smoother and faster - but maybe that is just me.
[Nook HD, HD+ Android Development] Sherip:
Please, I'd like to try that. Where did you get the npk file and how did you prepare the zip file?

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] Sherip:
Did you do anything more than substitute the contents of the new system directory into verygreen's 2.1.0 zip?
[Nook HD, HD+ Android Development] RageAgain:
I downloaded the .npk from B&N, it is the standard update file for 2.1.1.

Using verygreen's stock 2.1.0 for SD as a guide and for necessary SD boot files, I decompiled, edited, and recompiled the 2.1.1 update file. So I removed the recovery and boot files, and added the boot files from the 2.1.0 stock for SD. Then I edited the updater-script for SD card installation. It is almost the same setup as the 2.1.0 update, except for the inclusion of some files that install to /bootdata ( which I then had to find the correct SD Card mount parameters for ). I then simply installed it with the SD Card's CWM.

I had done this before on another tablet, so it wasn't hard to do it for the HD+ ( with verygreen's fine work to guide me ). :cyclops:
[Nook HD, HD+ Android Development] king200:
Is your creation available for download?
[Nook HD, HD+ Android Development] RageAgain:
I have 0% hosting skills, so if someone else wants to do that ( or alternatively clue my lazy self into how ) or has some other way to obtain the file...
[Nook HD, HD+ Android Development] leapinlar:
You can sign up for a free dev-host account and host it there. Go to:

http://d-h.st

It allows very large uploaded files.

Then post the link to this thread.
[Nook HD, HD+ Android Development] RageAgain:
B&N Stock 2.1.1 image for sdcard

Okay, so if I did this right then here it is:

stock-ovation-2.1.1-sdcard.zip

Let me know....
[Nook HD, HD+ Android Development] leapinlar:
I downloaded it ok and it looks right. Have not tried installing it yet.

The only suggestion I have is to put sdcard in the name so others do not get confused. You can rename both the link in the post and the actual file name on dev-host without having to reupload.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] RageAgain:
Done and done...

Thanks for the suggestion
[Nook HD, HD+ Android Development] Sherip:
I haven't really looked at it in detail, but I noticed the script updates or at least copies a few files to bootdata on emmc. Is there nowhere to put them on the sdcard? Is there a potential for conflict by updating bootdata if emmc is running a non stock ROM?

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] leapinlar:
No, those files are still used by the device even if running CM.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] Prof24:
Feeling a bit stupid

Don't really know why but it took me nearly 30 minutes to find this thread on how to dual boot Nook HD+. I like the CM 10.1 experience, but there are also aspects of the stock OS that I like too. If dual boot is no harder to achieve than initial root, I'll have a really cool tab in just a few hours. Just glad I didn't have to say "where are the direct instructions?". :)
[Nook HD, HD+ Android Development] Sherip:
I have installed it, seems fine. I have seen a couple of wifi error alerts that didn't make sense but it seems to working despite that.
[Nook HD, HD+ Android Development] RageAgain:
Although it says emmc ( in more than one place ), thanks to verygreen's work that actually refers to /bootdata on the sdcard. References to the actual internal memory look a bit different.
[Nook HD, HD+ Android Development] Sherip:
This is the part I was referring to --

mount("ext4", "EMMC", "/dev/block/mmcblk0p6", "/bootdata");

copy_file("/system/media/connect_charge.ppz", "/bootdata/connect_charge.ppz");

copy_file("/system/media/cooldown.ppz", "/bootdata/cooldown.ppz");
[Nook HD, HD+ Android Development] leapinlar:
Like I said earlier, CM on SD uses those files for charging, so it is ok to put them there (0p6).
[Nook HD, HD+ Android Development] RageAgain:
This is the original mount command:

mount("vfat", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/bootdata", "/bootdata");

As you can see, quite different. The work done by verygreen on the kernel makes it see part of the sdcard as emmc, otherwise it wouldn't work to run the os from sdcard. I did however, find an error in my code... Sigh...

---------- Post added at 09:53 AM ---------- Previous post was at 08:58 AM ----------

I updated my file/link for my stock on sd 2.1.1:

stock-ovation-2.1.1-sdcard.zip

I fixed a code/syntax error that apparently didn't make any difference...

Sigh...
[Nook HD, HD+ Android Development] leapinlar:
The mount command is different, but does exactly the same thing. It is just a different way of mounting the exact same partition on emmc. /bootdata is still on emmc with the new command. And the kernel is mostly the same, just in a different format. It is the ramdisk that makes most of the changes for partitions on sdcard.

Thanks for the new file.
[Nook HD, HD+ Android Development] RageAgain:
Sorry, ramdisk not kernel, gotcha. I never bothered to read enough about that.

Also, are you saying that the /bootdata you see from within the stock on sd when it is running is the one in internal memory? I didn't know that either....

Sigh..

However, for example, isn't it true that if you use:

mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "/system");

in cwm running on the sdcard instead of:

mount("ext4", "EMMC", "/dev/block/mmcblk1p2", "/system");

that it will write to internal memory instead of the sdcard? Because that is what happened to me a while back when I accidentally installed the emmc version of extras instead of the modified sdcard version ( shouldn't do installs or updates on lack of sleep ).

So, all I meant is that the two commands are interpreted differently by the cwm on the sd as opposed to the cwm on emmc. I just need to understand if that is not true...

So, for my own edification, what would be a good resource to read up on the file structure of the sdcard in stock on sd....
[Nook HD, HD+ Android Development] Sherip:
I'm struggling with the idea that vfat and ext4 types could be interchangeable, do you understand it?

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] leapinlar:
Yes /system is mounted on p2 on the SD. So if you accidently flash an SD version of a ROM, it will try to put it there and vice versa.

There are two conventions for the mount command, the /dev/block/platform method and the /dev/block/mmcblk method. They are equivalent.

Notice that the /bootdata mount says 0p6, not 1p6, which means emmc instead of sdcard.

The structure for the SD is 1p1=/boot, 1p2=/system and 1p3=/data. Then /sdcard is emulated by mounting a folder in /data (/data/media) just like it is in stock on emmc.

There are only three partitions on the SD. All the rest of the partitions used by the sdcard installation are on emmc (0p5=/rom, 0p6=/bootdata, 0p9=/cache).

Other emmc partitions (0p1=/xloader, 0p2=bootloader, 0p3=/recovery, 0p4=/boot, 0p7=/factory, 0p8=/system and 0p10=/data) are not used by the sdcard installation.

This structure is used for CM on SD also.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] RageAgain:
Thank you for clarifying all this for me.
[Nook HD, HD+ Android Development] verygreen:
I finally got to this myself.

ovation 2.1.1 rom installable to sdcard: stock-ovation-2.1.1.zip

hummingbird 2.1.1 rom installable to sdcard: stock-hummingbird-2.1.1.zip

I'll also have a nice script that generates such installs from stock update zips (and unlocked boot.imgs for emmc installs, though I am still verifying that they actually work). Will upload instructions a bit later after some verification ,so that you do't wait for me with these updates anymore.

Note that the install image for sdcard install has changed (you are fine if you are upgrading from 2.1.0 stock, but new installs must use new image).

Edit: I just noticed that I accidentally uploaded a version that does not like when you root it, so I reuploaded a fixed one, if you downloaded your image before this note appeared, please get the updated version if rooting is important to you.
[Nook HD, HD+ Android Development] Sherip:
Some info here http://source.android.com/devices/tech/storage/

Sent from HD+ MAG2GA CM 10.2 from SD
[Nook HD, HD+ Android Development] leapinlar:
I'm sorry, I somehow missed your original question. I see that reference, but I thought your question was about /bootdata.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] Sherip:
Yes, I am still wondering about /bootdata. I applied the first 2.11 update zip which treated /bootdata on EMMC as vfat type and am uncertain if anything there might need to be fixed. Certainly still boots. The only image I previously made was factory.

Sent from HD+ MAG2GA CM 10.2 from SD
[Nook HD, HD+ Android Development] leapinlar:
/bootdata is always vfat. And the only time it needs to be repaired is when users intentionally format it in CWM. And that is not for the two files that the ROM flash installs, it is for the missing boot control files. When you flash a new stock ROM it does put two files on /bootdata. Those two files are used to control charging.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] ST Dog:
The link is broken, no server given

Think it should be

http://nook.rootshell.ru/hd/hummingbird-sdcard-stock.img.gz

No older version? I haven't booted B&N in months so I'm pretty sure I still have the older version.

I just want to keep the versions the same so that moving /data doesn't risk any glitches.

Any comments on what you changed v/s the CM versions of CWM to get it to boot stock on the SD card?
[Nook HD, HD+ Android Development] verygreen:
Yes, indeed. Thanks.

Use the script I provided to convert any version into sdcard bootable zip installable, I guess?

dropped androidboot.hardware= from the kernel init string passed from bootloader.
[Nook HD, HD+ Android Development] ST Dog:
Any ideas as to why Cyanoboot won't boot stock on SD?

What did verygreen use for a bootloader then?

So, install quickboot in stock on the SD card.

Normal reboot gets stock

Using quickboot "recovery" from stock on SD gets what?

quickboot's bootloader gets direct CM EMMC boot, but no chance to enter recovery until you reboot a second time using quoickboot installed in CM on EMMC?

---------- Post added at 11:45 AM ---------- Previous post was at 11:23 AM ----------

I looked and didn't see any older .npk files on B&N which you script uses.

Would a CWM backup, that is then unpacked work?

I really don' understand the formats and such yet (long time *nix user, but new to android)

So, it should be possible to get it to leapinlar's version to work.

That's all in the ramdisk? (again, new to android. I know how to set lilo and grub parameters, even edit them on the fly)
[Nook HD, HD+ Android Development] verygreen:
the androidboot override from bootloader prevents the standard bootloader to load this.

you might want to play with internet wayback machine to find older npk links, I suspect.

No, this is in a bootloader, so you'll need to change the bootloader to understand if it wants to boot a stock image or not and modify the kernel command line accordingly.
[Nook HD, HD+ Android Development] ST Dog:
OK, I guess I need to figure out how this is all working.

I know LILO and grub pass specified parameters to the selected kernel.

I assumed this was similar to LILO, selecting the kernel on EMMC or SD as appropriate.

It appears that Cyanoboot isn't (though somehow the root device is being selected)
[Nook HD, HD+ Android Development] verygreen:
the root device is always ramdisk, and it's the ramdisk that has things hardcoded as to what's to mount from where.
[Nook HD, HD+ Android Development] ST Dog:
Different ram disk and kernel for each boot option, SD, EMMC, recovery.

Possibly multiple "installs" on SD or EMMC (set by which partitions are used)

I need to go find documentation on it. 20+ years of linux may have me thinking in the wrong paradigm.
[Nook HD, HD+ Android Development] verygreen:
It's actually very similar to how modern distros work, only modern distros usually get their "real root" passed as a kernel param that's queried and mounted from iitial ramdisk script and then check /etc/fstab for the rest, where as android has / on ramdisk at all times and has fstab (in newer releases) there as well (or in older releases the init script has montpoints hardcoded).
[Nook HD, HD+ Android Development] scuzzo:
hello im trying to Install the stock 2.1 rom on and SD card... and i went through all the steps.. but every time i boot with the SD card in the Nook HD+ it will always boot into CWM... im starting to think... perhaps i need 2 sd cards... one for the CWM image and one to store the Stock Rom?

but im not at all sure... i was using the same SD card to hold the store the CWM image and the Stock 2.1 rom... do i need 2 different DS cards? i never get to the point where CWM sees that the rom is unrooted and askes if you want to root it..

i ran into this same issue before.... not sure what i did to fix it...
[Nook HD, HD+ Android Development] max_frustration:
late 2013 HD+/2.1.1 successful rootings?

Has anyone successfully rooted and booted an HD+ with 2.1.1 from B&N of very recent (~nov 2013) manufacture?

I have been trying more than a week without result.
[Nook HD, HD+ Android Development] leapinlar:
I know you have been trying hard. Do you know that is really the date of manufacture? I doubt it since I don't think they have made any lately. The date of manufacture is available on the unit, I just am not sure how to get it in stock. I know if you erase and deregister, you can get to the factory screen that has that info. Go to my HD/HD+ Tips thread and look at the item for skipping OOBE.
[Nook HD, HD+ Android Development] max_frustration:
some progress

Well, I hit this thing hard enough to get it into a boot loop and subsequent system restore from eeprom.

I used Kingo Android Root, wow that is one weird piece of software, it operates totally blind, I know not

what it doeth. I believe it escalated successfully, and no doubt copied an su binary to the /system/bin

directory, prompting the watchdog to nuke the whole shebang. Ha. Kind of funny actually. I was hoping

in the mayhem the booter would load from my sd card. It paused a long time at nook 99% so I was

hopeful, but alas it was not to be. Rats. Close though.
[Nook HD, HD+ Android Development] max_frustration:
endlich

Ha. Rooted the swine. Sheesh.
[Nook HD, HD+ Android Development] leapinlar:
How?
[Nook HD, HD+ Android Development] max_frustration:
RE endlich

Using the util I mentioned above, I yanked the usb wire at precisely

the right instant. It took several tries. As expected, it deposits "su"

into /system/xbin along with a couple other no-no's. Now if I can just

get a decent recovery image installed I should own the computer I paid

for. Ridiculous.
[Nook HD, HD+ Android Development] leapinlar:
Just don't let it reboot and ADB that recovery image like I told you earlier and then when it reboots and tries to reset you can let it boot to the new recovery and flash verygreen's new boot.img which turns off system protection.
[Nook HD, HD+ Android Development] max_frustration:
I dd'd your recovery.img (sha1 cc078...) into partition 3 and rebooted. Boot loop and system nuke followed.
[Nook HD, HD+ Android Development] leapinlar:
Well try dding verygreen's boot.img to p4 before rebooting instead. Get it from his ultimate root dev thread.
[Nook HD, HD+ Android Development] max_frustration:
learning slowly

Hmm. I seem to be good at getting it to blast the system dirs but not much else.

I am also getting skilled at yanking the usb cable at jess' the right time.

So, uh, I tried to follow instructions as best I understood them to cause the device

to boot from the recovery partition after dd-ing recovery.img to partition 3. I get the idea

I may not be pushing the right buttons in the right order, waiting the right number of

seconds, etc. I have no zero experience with cwm. I have never seen it, but I think

it does not say "nook". I wonder if the device refuses to load cwm because it does not

find on partition 3 what it expected to find there. Nah. It's something else.

I tried hacking sha1 checksums for the new files into /manifest but ran into a file system

problem. Also tried moving the su binary etc. elsewhere and symlinking, but not successful

with that yet, not sure why.

I have tried operating on Kingo, I think it calls init 0 when it thinks it's done, rather than, say

reboot, which makes it harder to work on, but I may yet be able to patch the binary.

I have not yet tried dd-ing verygreen's modified stock system boot image to the standard

boot partition, 4 ... yet. I would like to see if under cwm the thing will boot from an SD

card. I am assuming cwm can boot from anywhere. I mean, I think it's a boot manager.

Max
[Nook HD, HD+ Android Development] leapinlar:
If it reset itself after dding the recovery, that means the DD did not take. The only way it can reset is with the stock recovery. If it was going to boot to cwm, it would show the nook logo followed immediately by the cyanoboot logo.

So try the boot.img.

This is really the wrong thread to be discussing all this. This thread is for stock installed to SD.
[Nook HD, HD+ Android Development] max_frustration:
moving to User tips...
[Nook HD, HD+ Android Development] Kubombelar:
please help....am unable to mount sd card nor emmc
[Nook HD, HD+ Android Development] leapinlar:
Please explain what you mean. Are you trying to install this stock 2.1.1 on SD and cannot make it work?