yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ General] GMTN:
Newbie alert ! Can apps be side loaded via the tablet ?

Hello , newbie here to the new Nook HD plus as I just got it for my other half.

My regular tablet is the Asus Transformer original with a Jellybean rom installed.

I've done a bit of reading and will eventually install a jellybean rom to this as well .

Am I reading the info correct in that the only way to install / sideload apps is via the PC, using the command line ? That you cannot install apk(s) via the tablet with a file manager like Astro or File explorer like I do with my other tablets ?

The screen is clearly sharper on this then my trusty Transformer. I'm a bit envious.

Thanks.
[Nook HD, HD+ General] leapinlar:
That used to be the case when the device first came out, but not so any more.

If you go to my HD/HD+ CWM thread linked in my signature and make a bootable CWM SD, you can flash my Enable Unknown Sources zip and you can install apps with a file manager app just like other tablets.
[Nook HD, HD+ General] GMTN:
Thanks for the update to that thread for late comer newbies like me ! More reading to do.
[Nook HD, HD+ General] molivarez3:
Trying to Unroot

If I place one of these on the root of the device ((i do not have an sd card and the nook hd + is already rooted)) and I flash the zip file. will that put me back to stock like if I just bought it from the store?

NookHD-bootable-CWM-6027-for-emmc-stock-small-rev3-(02.03.13).zip - [Click for QR Code] (5.51 MB, 272 views)

File Type: zip	NookHDplus-bootable-CWM-6028-for-stock-small-rev4-(05.15.13).zip - [Click for QR Code] (5.81 MB, 352 views)
[Nook HD, HD+ General] leapinlar:
No, see my response to your other post
[Nook HD, HD+ General] max_frustration:
serious progress

Having learned USER Tips is where the goodies are, I found someone0's post from 3 Dec 2012

detailing usb driver installation on Windows 7-64. The procedure worked immediately, adb (via

Minimal ADB and Fastboot) now provides shell access to the HD+ device. Whew. Thanks

someone0.

Max
[Nook HD, HD+ General] max_frustration:
sidestep sdcard boot?

As my HD+ unit refuses to boot from an external card I consider another approach.

Has anyone installed cwm or twrp to an HD+ using adb and dd?

Max
[Nook HD, HD+ General] leapinlar:
I don't think anyone has. But it might work. Take the recovery.img out of the recovery zip for CWM emmc ovation and DD it to /dev/block/mmcblk0p3 per my instructions in item 16. But do this at your own risk.

I would like to know if this works. It might not because stock ADB is not rooted, so I don't know.
[Nook HD, HD+ General] max_frustration:
I was assuming I would get root first.

It seems adb root exploits are now passé on the HD+; apparently

rev 2.0.5 plugged some holes, but if there is one known to work on

2.1.1, do tell. I expect there is still a way to shove an suid

binary on there or something.

The other thought I had was, the boot rom probably still has the code

in it to boot directly from an image it finds in the external sd slot, and

may be less finicky than the newer OLMA4-compliant version.

M.
[Nook HD, HD+ General] leapinlar:
Not that I know of.

The actual code to boot from SD is in the OMAP4 firmware, not the boot ROM code.
[Nook HD, HD+ General] max_frustration:
HD+, seeking particulars of a successful boot from external sd

Subj: HD+ attempt to boot from an external micro sd card

I would like to know as many details as possible about an

external sd card used for a successful CWM or twrp boot.

Manufacturer

capacity

speed class

when bought

was a file system formatted on it or was is used raw?

If f/s, which one?

Was it sub-partitioned?

Partition attributes set?

Here is a directory listing from one my cards formatted FAT32

max@wilk /cygdrive/h

$ ls -l

total 27184

drwxr-xr-x 1 max max 0 2013-11-29 21:09 LOST.DIR

-rw-r--r-- 1 max max 131072 2013-11-29 20:58 MLO

-rw-r--r-- 1 max max 10338059 2013-11-29 20:39 NookHD-HDplus-Universal-Root-rev3-(09.10.13).zip

-rw-r--r-- 1 max max 745332 2013-11-29 20:38 NookHD-HDplus-stock-enable-Unknown-Sources-rev0-(09.08.13).zip

-rw-r--r-- 1 max max 9813968 2013-11-29 20:37 NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13).zip

-rw-r--r-- 1 max max 574525 2013-11-29 20:38 NookHDplus-verygreen-New-SD-fix-stock-to-use-New-SD-Media-rev0-(06.01.13).zip

-rw-r--r-- 1 max max 3899456 2013-11-29 20:59 kernel

-rw-r--r-- 1 max max 1822850 2013-11-29 20:59 ramdisk

-rw-r--r-- 1 max max 262144 2013-11-29 20:59 u-boot.bin

-rw-r--r-- 1 max max 237380 2013-11-29 20:59 uImage

Can anyone tell me if this the right payload?

Other times I have tried using a raw image burned with win32diskimage

The image burned to it was this:

$ ls -l

total 3855600

-rw-r--r--+ 1 max max 3948134400 2013-05-15 14:26 NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13).img

Can anyone comment on this one?

As for the filesystem approach,

I have also tried exFAT. Is exFAT better? Worse?

Anyone tried ext3 or ext4?

As the loader boots to CWM, what does the screen show?

Any assistance is appreciated.

Max
[Nook HD, HD+ General] leapinlar:
The dates on the files look wrong for being my 5/15/13 version. Did you do some file copying?

Put the SD in your windows PC (not Mac or Linux) and remove the lost.dir folder. Make sure the first partition is set as active. Immediately try booting in nook. If it boots, it shows the cyanoboot briefly followed by the CWM screen.
[Nook HD, HD+ General] larrycl:
I'm running 2.1.1, and I am having the grey-on-grey (or white-on-white) menu problem with both Nova launcher & Apex Launcher. I can barely read the settings menus in either of these apps. Any suggestions? Are other people using these launchers ok? Should I even try modding framework-res.apk?
[Nook HD, HD+ General] max_frustration:
patience, grasshopper

Thanks for looking at my listing.

Did I copy the files? Of course. The timestamp shows when.

The lost.dir is something nook puts in there when it goes into "preparing external storage" mode.

Everything in on Win-7. I used the cygwin shell to list the files as the output is cutandpaste-able.

All write operations were done with standard BillGatesian methods however.

Do you have md5sums for these files? It would be mighty useful.

My reading of the OMAP bootloader so far is that it is impressively sophisticated.

I wonder if by exposing the mobo, a pin might be grounded to alter the boot sequence.

Thx.

Max
[Nook HD, HD+ General] leapinlar:
Well, you have listed my img file as the source for burning and that does not require copying files. They are placed on the SD with their original dates when win32diskimager burns the image. The reason I was asking is the boot process is very finicky and messing with the files sometimes makes it not boot.

Of course if you are using my new procedure, then you do copy files. But there are other steps too. See my HD/HD+ CWM thread linked in my signature and look at item 1a.

And I know how that lost.dir got their. I was suggesting you remove it if it is there. Some have reported that that folder prevents booting. So if it does not boot and stock puts it there again, remove it before trying to boot again.

I don't have md5 sums.

And I don't think messing with pins will help.
[Nook HD, HD+ General] leapinlar:
Nope. That is very difficult to do to get the colors right. I suggest you change launchers.
[Nook HD, HD+ General] max_frustration:
A couple more evenings were spent futzing. Still no joy.

Software version 2.1.1

Model number BNTV600

Serial number 3024950246604319
[Nook HD, HD+ General] larrycl:
Ugh. (That's directed at my Nook, not at you leapinlar; you've been incredibly helpful to all!)

I was hoping to get by with simply rooting my nook and not having to use a custom rom; however, even with all your patches there are too many things that are still annoying me. I may just have to install CyanogenMod and be done with it.
[Nook HD, HD+ General] leapinlar:
You've got a really tough nut to crack. I just went back and re-read all your posts on this subject. Nowhere did you say you used a different SD. Have you? Many found that made a big difference. And the preferred brand and class is SanDisk class 4.

And if using the burning procedure, using a external card reader instead of one built into your PC sometimes helps too.

I personally find using the new procedure the best. Format fat32 with SDFormatter (full), set first partition active, copy the five boot files (MLO first), insert in powered off nook and power on.
[Nook HD, HD+ General] max_frustration:
5 card draw, losing hand

My flash memory i/o device is an IOgear GFR381, recent manufacture, I have never observed any problems with it.

I have a couple others, I'll report if either helps.

I have five SD cards. Tried em all. On the strength of your Sandisk class 4 recommendation, I went and bought

a couple more. Still negative.

I have tried erase and overwrite formatting modes with SDFormatter and it always emits a diagnostic that the utility is reverting to

quick format because the other mode is not supported. All my cards do this. I wonder if that is significant.

I wish I could verify the 5 unrar'd files from

NookHDplus-bootable-CWM-6028-for-stock-BOOTFILES-r4-(05.15.13).rar

$ md5sum *

c42fe1103ff94365c1270445772736ff *MLO

6bcdd49057860c9570714b9b20737f8c *kernel

dc12ad5d61ae2910617fdb2cb2e4f530 *ramdisk

71ab85f33eab4a386a95615911744439 *u-boot.bin

6b41eb836c11ea9b562860eee965bb98 *uImage

Maybe someone out there can verify these checksums for me.

I power down my Nook HD+ thus: press power about 5 seconds, dialog box says Would you like to shut down?

touch OK.

I power up this way: press power about 5 seconds, screen says nook followed by the big N.

I assume the N stands for nowledge.

Max
[Nook HD, HD+ General] leapinlar:
On the md5sums, check them against the image version. They are supposed to be identical.

That inability to overwrite format sounds significant. The structure of the card is very important to the boot process. It could be your card reader. Try your others.
[Nook HD, HD+ General] max_frustration:
Another late night of experimenting...

Different computers, different flash i/o units, new cards.

On all cards on all computers everywhere I always see the same message from SDformatter that erase mode is not supported

by the card. It reverts to quick format issuing a benign sounding diagnostic as if it's no big deal.

Mr Gates's Windows-7 inbuilt utility has no such difficulty, and judging by the time a non-quick format takes, I believe it

really is writing all over flash memory reconstructing a file system. The time it takes varies directly with the size of the

card; I think it works. I think SDformatter doesn't work.

But none of it helps.

I also think I am following your procedure as you intended and that either something is wrong with the tablet I have, or my new

and good friend B&N has tweaked their software just a bit. I have 2.1.1 but there could be slipstream changes. It does seem

the trajectory of their releases is to tighten down the screws. My guess is the card unit on my machine works, the OS has no

trouble polluting my cards with LOST.DIR's. I havent really tried read ops but I expect it works, but that their nifty OS contains some

"enhancements", and possibly the hardware too. The device is squeaky new.

So, looks to me like card based attack is spun out. I think I have to move my attack back to the wire and possibly to physical

disassembly. My reading of the OMAP docs says there's a serial boot interface available too. I expect there is still a privilege

escalation exploit or two still left, though I have not seen any discussed for 2.1.1. At a certain point though, it just becomes

easier to pry the thing apart.

Good night.
[Nook HD, HD+ General] max_frustration:
reasonable progress

Subthread moved here from thread for stock on SD cards...

I unzipped verygreen's nookhd-unlocked-stock-emmc-ovation-2.1.1.zip boot.img adb push'd

and dd'd using the arguments in its updater-script.

I then unzipped leapinlar's nookHDplus-emmc-stock-recovery-rev0-(05.16.13).zip recovery.img adb push'd

and dd'd using the arguments in it's updater-script.

Boot cycling is now stopped, root access is now nonvolatile, natch.

On bootup, "nook" appears for half a second, then 2 cm of video buffer garbage on the extreme right hand side of the

screen, then "cyanoboot universal bootloader"

From http://xdaforums.com/showthread.php?t=1522226, the photo shows a menu, but all I see

is cyanoboot universal bootloader. The device displays the cyanoboot logo on a dark background for several

seconds, and does not seem to respond to any button presses, then nook stock boots.

Max
[Nook HD, HD+ General] leapinlar:
It is operating as it should. This version of cyanoboot has no menu. Those logos come up even on the normal boot to verygreen's unlocked stock. So you are making good progress.

To get to CWM recovery, you need to power off, press power and the n key together for like 5 seconds, releasing the power key followed by releasing the n key a few seconds later. It will then boot with the same logos but eventually end up in CWM (assuming it took). If it did not, then just the n logo shows and a message asking if you want to wipe your device. That is stock recovery. Say no.

If you don't get to CWM, let me know and maybe we can do something else.

EDIT: I just reread your post and you used my stock recovery zip to DD with ADB, you need to use my CWM recovery to DD.

No wonder the other attempt did not work. You just put stock recovery back, not CWM.
[Nook HD, HD+ General] max_frustration:
OK. There are two HDplus CWM 6028 zip's. 4GB and small. I've been hunting and googling and bing-ing. What is the difference?

Why would I want one or the other?
[Nook HD, HD+ General] leapinlar:
It is obvious, one is small and one is 4GB. LOL. Look at my item 14 in this thread, it explains it (in the hidden text). The small version is only 120MB in size and therefore it burns very quickly. But there is no room to store much of anything. You can use partitioning software to expand it larger if you wish. The 4GB version requires at least a 4GB SD to burn it to, and that takes many minutes to do. But there is plenty of room there for storing things. But if you go to my HD/HD+ CWM thread linked in my signature and read item 1a, you will see there is a new procedure where you can install CWM to any size SD without burning.
[Nook HD, HD+ General] max_frustration:
Good evening Leap. Thanks for the timely reply.

I am a little hesitant to dd in the big one.

It is not even clear to me how large partition 3 is on

the device. But I see no chatter about resizing partitions on these

threads. How can this be? Mysteries mysteries. It must be

new-age data storage. I'm about to try the small one. We'll

see if I turn this thing to a flat brick or not. ;>)
[Nook HD, HD+ General] leapinlar:
The partition is 15MB in size. I don't know what you are talking about 'big one vs small one'.

If you want to know more about partitions, go to my HD/HD+ Tips thread and look at item 16. And one the reasons you do not see repartitioning discussions is the HD/HD+ uses GPT instead of DOS partitions.
[Nook HD, HD+ General] max_frustration:
What?

NookHDplus-bootable-CWM-6028-for-stock-small-rev4-(05.15.13).zip

NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13).zip

one big one little.
[Nook HD, HD+ General] leapinlar:
Those are not the right ones. Those are CWM for bootable SDs. Look at item 5 in my CWM thread. There are off site links there for the internal CWM that you should be using. Just take the recovery.img file out of the zip and DD it to p3 like you did the boot.img to p4.

Edit: I am sorry, I did not realize that was you asking about the 4GB vs small a couple of posts ago. I have to pay more attention. I see how you got confused. You were just looking at the attachments, not reading the post.
[Nook HD, HD+ General] max_frustration:
Thank you! That makes much more sense.

---------- Post added at 05:41 AM ---------- Previous post was at 05:26 AM ----------

Hmm. dd'd recovery.img (sha1 ec564...) to partition 3 bs=4096 per the upgrade-script.

The behavior of cyanoboot has not changed so far as I can tell. I hold the nowledge button

but it just boots to stock in a few more seconds. Maybe I am not playing the keys right.

I figured it would boot to a little utility with a few menu items.

I'm suffering from serious raster burn. I'll pick this up another day. Thanks for the help

so far.
[Nook HD, HD+ General] leapinlar:
First hold POWER and n simultaneously (together) for 5-8 seconds. Then release POWER, followed by releasing n. That should take you to recovery (either CWM or stock). If it does not, you are still not doing it right.

But there is another option. Since you are rooted, you can install 'reboot to recovery' by wikilab.de from Play Store. Once installed and working it will boot you to recovery. I have found no other apps that actually work for rebooting to recovery from stock.

And lastly, once you get internal recovery working, you can flash anything (mods to stock, new ROMs, etc). But be careful with flashing my plain stock zips from item 6 in the CWM thread. They will undo everything you have accomplished. You will lose your root and especially your internal CWM. Even if you flash my rooted stock zip from item 6, you lose CWM.
[Nook HD, HD+ General] max_frustration:
Well, I finally saw CWM. It was about what I expected.

So now I get to the meat of the matter, the objective of this exercise, to install Cyanogen.

I downloaded cm-10.2-20131210-NIGHTLY-ovation.zip and put it on an SD card, booted to

CWM, -> install zip -> choose zip from external sd card

it shows the name of the file

toggle to that, press n,

Confirm install, toggle to Yes, press n

--- Installing /external_sd/cm-.......ovation.zip

Finding update package...

Opening update package...

E: Can't open /external_sd/cm-......ovation.zip

(bad)

Installation aborted

I checked the .zip as written to the sd card.

The perms are 644, i.e. rw, r r which I would think should do it.

Could it be that there is a hardware problem with this sd card reader?

If so it does not prevent CWM from seeing the .zip file.

I'll try adb push to internal storage and upgrade from there.

Max

---------- Post added at 05:40 AM ---------- Previous post was at 05:22 AM ----------

install zip from internal storage is no better, same result.

Note this sequence is from this http://wiki.cyanogenmod.org/w/Install_CM_for_ovation

which contains the odd "wipe data factory reset" line, which I nevertheless did.

Sigh. I wonder if the file is bad, it is after all a nightly. I just figured the 10.2 was

probably converging at this point and might well be better than a months old "stable"

release.

Max

---------- Post added at 05:55 AM ---------- Previous post was at 05:40 AM ----------

I figured maybe the long name of the .zip file was screwing it up. No. It doesnt seem to make

any difference. I know people have gotten cyanogen on these devices. I wonder how they did it.
[Nook HD, HD+ General] leapinlar:
I would recommend CM10.1.3 stable. That is what I use. There are still a lot of problems with CM10.2.

The bad message usually means a bad download. And CWM cannot read exfat formatted SDs if that is what you have.
[Nook HD, HD+ General] max_frustration:
It seems to have something to do with signature verification, hash sums.

toggling signature verification seems to make it go a little farther. The web is

full of fellow sufferers, at least I have company. No cures, but plenty of misery.

---------- Post added at 07:06 AM ---------- Previous post was at 06:22 AM ----------

I tried cm-10.1.3-ovation.zip

It has the same problem.
[Nook HD, HD+ General] leapinlar:
Try flashing this recovery.

http://d-h.st/2vd

It is a little older but very reliable. It will replace the existing one. Just flash it with that 6036 CWM. If it does not flash, strip the recovery.img out and dd it with adb just like before. It is version 6028.

BTW, that download page has an md5 sum so you can verify if it download properly.
[Nook HD, HD+ General] midimench:
All my nightlies starting with cm-10.2-20131209-NIGHTLY-tf700t keep aborting

All my nightlies starting with cm-10.2-20131209-NIGHTLY-tf700t keep aborting. I keep reverting back to the cm-10.2.0 stable version and newest pa_gapps-full-4.3-20131102-signed.zip to get my tablet working again.

Is anybody else having problem with the newer nightlies? I got cm-10.2-20131207-nightlie to work, but it was buggy, so I went back to the stable version.

Would appreciate anybody's input

Gregory
[Nook HD, HD+ General] max_frustration:
I tried cwm 6028 also with 10.1.3-stable. The result is the same.

Thanks for the pointer anyway.

What could it be? It doesnt matter whether the .zip is on internal storage or external.

It doesnt matter what .zip it is, and it doesnt matter what recovery partition is there.

A setting somewhere? A fundamental read problem from all storage? If so, it didnt

keep the kernel from booting.
[Nook HD, HD+ General] leapinlar:
I suspect your PC (antivirus) is corrupting these files on download. I suggest you download directly to your device using stock, that way it bypasses your PC.
[Nook HD, HD+ General] max_frustration:
ha! Well Mr. checksum himself got bitten in the a**. It looks like something added a couple bytes onto the end of those two

files. Since they unzipped, I didn't check the md5sums on the CM home page. Poetic justice, the gods are laughing. Hard.

Wget from a linux box and the md5sums are fine. Moral: stay away from Windows as much as possible.

Soo.. I got your 6.0.2.8 cwm to load the checksum-compliant cm-10.1.3 zip file from my external sd card. This time cwm

was able to load the zip.

I booted to a merry-go-round that never stopped. I Googled a bit, several posters suggested various remedies, all based on cache wiping.

Okay. Eye of newt, thumb of babe, data cache wiped. Poof. Tried boot again. This time it did not boot CM at all. Recovery was

still fine though, so I re-installed. Still no boot. I downloaded a newer CM release, and installed that. Still no boot.

Other than cwm 6028, I pretty much have a brick at this point. At least maybe I'll get my life back.

I don't have a shotgun but I have a buddy who does.

I can hurl this thing, discus-like, high into the air --boom-- the roar of a 12ga magnum!

Thousands of little RoHs-compliant bits raining down. Ah, the feeling. Satisfaction.

Min
[Nook HD, HD+ General] leapinlar:
Did you factory reset with CWM after flashing the CM zip and before re-booting?
[Nook HD, HD+ General] max_frustration:
I tried this a lot of times, trying to follow the sequence at the CM site. I'll try again

with special emphasis on the wiping order.

---------- Post added at 05:44 AM ---------- Previous post was at 05:31 AM ----------

I tried a bunch more times in all possible orders. No good.

---------- Post added at 06:04 AM ---------- Previous post was at 05:44 AM ----------

log says

net.tt.name=Android

net.change=net.bt.name

dalvik.vm.stack-trace-file=/data/anr/traces.txt

init.svc.ueventd=running

init.svc.recovery=running

service.adb.root=1

init.svc.adbd=running

I:Checking for extendedcommand...

I:Skipping execution of extendedcommand. file not found...

I:Can't format unknown volume: /extended_sd

I:Can't partition non-vfat: datamedia
[Nook HD, HD+ General] leapinlar:
Forget what the CM site says. You are doing too much surfing and looking at things that do not apply to the nook HD/HD+. Just follow the dummies guide here in the HD/HD+ forum. Doing a factory reset wipes /data and /cache which automatically wipes the dalvik cache. That should be all that you have to do.