yashsingh1/xdaforums huggingface dataset:
[Nook Touch Android Development] mali100:
Please do not use the restore backup function, there seems to be a problem during restore!

I m currently trying to fix that.
[Nook Touch Android Development] GabrialDestruir:
I'd use CWM on SDCard alone, replace the uRamdisk with a CWM uRamdisk. This will allow you to boot into CWM immediately every single time when booting from sdcard. I also wouldn't replace the stock recovery because if anything happens you may lose the ability to do a quick restore/reset instead having to rely on "restore.zips" provided by other users.

That's just my opinion anyways. Will put a new TouchNooter in a week or two after my classes are over that will work on CWM.
[Nook Touch Android Development] jhedfors:
Frozen at CM Recovery

Well, I screwed up...

I was stuck, and attempted to restore from CM Recovery installed on the device. It all appeared to be working until tbe reboot after it was finished, and then....frozen.

I have tried to reset by holding down the power for a few seconds ,repeating 20 times, then doing the same holding the power longer, etc. with no luck.

The battery is charged.

Any ideas?

The next thing I was going to try was to re―burn a bootable CMR sd card, and see it will boot to it.
[Nook Touch Android Development] ros87:
If you're still stuck and want help, feel free to PM me :)
[Nook Touch Android Development] mali100:
Hi,

I'm sorry that this happend.

I'm having the same problem at the moment, my nook doesn't boot from the internal memory. I'm currently trying to find a fix for this.

If you have a backup made with noogie, use it, and your nook should be fine.

If you haven't, there is a workaround, that let's you at least use your nook until there is a fix:

Burn noogie to a sd-card

remove the uRamdisk on the sd-card,

put one of these uRamdisk on the sd-card http://xdaforums.com/showthread.php?t=1337653

put in the sd-card and boot.

This should allow you to boot normally, as long as you don't remove the sdcard. If it doesn' boot, there is something wrong with the data on your /system partition (but it should be fine, because the restore itself seems to work, but is killing something other necessary for the boot process). If it doesn't boot, contact me again, I can probably provide you with a fix for that.

I'm currently trying to find a real fix. My assumption is, that it is related to the partition table.
[Nook Touch Android Development] jhedfors:
Thanks for your help!

Making progress, however, it looks like I am boot-looping at the "Rooted Forever" screen. At least it is doing something! :)
[Nook Touch Android Development] mali100:
I think I found the error. Please try to rename the file "mlo" on the boot partition to "MLO". It seems the internal omap boot-loader is reading case-sensitive from the fat-partition :confused:
[Nook Touch Android Development] jhedfors:
Actually, this was already in all caps, but I realized my renaming of the uRamdisk did not take. I fixed that, and now boots up.

Thanks for your help!
[Nook Touch Android Development] italiano1964:
I too was stuck after doing a restore from a backup. I was able to fix everything by burning n2T-Recovery file .02 image (the .01 file didn't fix the problem) to uSD card, followed by erase/deregister.

http://xdaforums.com/showthread.php?t=1289233
[Nook Touch Android Development] mali100:
Please try to restore the attached backup. You only have to replace the uramdisk on your Sd-card with the one in this zip (you don't need the other files in the archive).

Extract the attached fix_boot.zip on the sdcard. (Please check that the create folder hierarchy is x:\clockworkmod\backup\fix_boot\boot.vfat.tar)

Then reboot with the sdcard inserted, use Backup and Restore -> Restore -> fix_boot.zip.

After the restore remove the sdcard and try to reboot (the recovery could be stuck, and you may have to force a reboot by pushing the power button for 10 seconds).

After that, the nook should boot normally. If not, put the old uRamdisk back on the sdcard and boot from the sdcard.
[Nook Touch Android Development] jhedfors:
That worked! Thank you so much for your help!
[Nook Touch Android Development] mali100:
The problem with the restore function is identified, and I will release a new fixed recovery.

Restoring backups made with version prior and including RC1 are faulty and will end in a non booting state. It isn't important with which version you restore, if the backup was made with Beta1, Beta2 or RC1 it will fail!

If you only need the backups of /system and /data and not the one from the boot partition you can just delete the boot.vfat.tar file in the /clockworkmod/backup/backupdate/ folder and restore it and you will be save.

If you have installed a bad boot-backup, follow the instructions in this post http://xdaforums.com/showpost.php?p=19881764&postcount=35

Sorry for all the trouble.
[Nook Touch Android Development] mali100:
Hi,

I uploaded a new version. Backups made with RC2 should be save. If you want to make shure, open the boot.vfat.tar of the backup that you have made (sdcard:\\clockworkmod\backup\date_and_time) and check if the filename "MLO" is written in uppercases:

"MLO" -> good

"mlo" -> bad

There is a new ugly bug, that I couldn't fix: After the restore of the boot-partition the recovery doesn't respond to the buttons. You have to hard reboot. The restore process itself works fine.

It would be great if someone who has the knowledge and the time could help fixing this bug. I attached the NST specific recovery files in this post. To build the recovery you need the Cyanogenmod sources. The attached files have to be extracted to device/bn/zoom2 and can be build with

. build/envsetup.sh

lunch full_zoom2-eng

make -j4 recoveryimage

The recovery gets stuck in the ui_wait_key() (bootable/recovery/ui.c) function. It seems the input_thread doesn't receives new key hits.
[Nook Touch Android Development] italiano1964:
Which zip is the new, fixed one? The one at the bottom of the above posting, labeled zoom2?
[Nook Touch Android Development] mali100:
zoom2_source_rc2.zip are just the files to build the recovery yourself. The new recovery is in the opening post.
[Nook Touch Android Development] LastSilmaril:
CWM: ALWAYS a good decision m-f***er! Thanks so much for this!

Can I use ROM Manager as a UI? Or is that a no-no?
[Nook Touch Android Development] mali100:
You can't. ROM Manager recognizes the NST as Nook Color and doesn't allow you to do anything.
[Nook Touch Android Development] :
Can this be done manually using noogie? Or perhaps you could make a 4gb image (or tell me how to :)
[Nook Touch Android Development] mali100:
I'm not sure what you want to do. If you want to replace the recovery on your nook, you can use noogie, just replace the files uRecRam and uRecImg with uRamdisk and uImage from the install_cwm_recovery_rc2.zip. The SD-Card Images boot directly from the SD-Card and don't change the devices recovery.

You can write the 2GB-Image to a 4GB Card and use it with the only downside that only 2GB of space are useable.

If you want a SD-Card with the full 4GB of space, write the attached img onto your card and extract the attached boot-files on the card.
[Nook Touch Android Development] :
Thanks!

Yeah, I was referring to using Noogie. I saw uRecRam and uRecImg, but wasn't sure if you had to do anything else to replace it :)
[Nook Touch Android Development] GabrialDestruir:
I feel a need to point out that if you replace the current recovery files on the NST's Boot Partition then you won't be able to use the recovery disk if anything goes wrong you'll be stuck relying purely on CWM.

With that in mind, I'd also wait til it's in an actual release, not just RC before you decide to replace your device's recovery files.
[Nook Touch Android Development] mali100:
Thats correct, but its easily possible to switch back to the stock recovery using install_stock_1.1_recovery.zip from CWM.

The only reason that it is still RC is that I can't fix the sstuck after restore bug. Everything else works fine (at least no one reported any problems, and I also didn't experienced any).

Anyway, I will add a short warning.
[Nook Touch Android Development] than33:
THANK FOR THIS!

Now we have properly hacked android device. Now it is time to cook proper ROM to flash from CWM recovery.

Please tell me if ADB should work from recovery. Beacause ADB says there is no device.
[Nook Touch Android Development] mali100:
ADB works fine from cwm, but you have to add the usb-id to a config-file. You should find the necessary informations in the threads about adb over usb.
[Nook Touch Android Development] GabrialDestruir:
Try heading into #nookcolor on irc.freenode.net and see if nemith can help you out with the issue. He may just have an idea about what causes it or could probably point you in the right direction about the cause.
[Nook Touch Android Development] than33:
no, there is no ADB device at all. There are only two devices for external usb drives. nothing more.
[Nook Touch Android Development] mali100:
Then there is something wrong with your adb installation. Do you see the nook when it is normally booted?
[Nook Touch Android Development] than33:
only via ADB wireless

Maybe it is my ADB in fact...

I will check this on another computer
[Nook Touch Android Development] winstonma:
Sorry I am a newbie. I just use touchnooter to root my N2T. I'd like to know the right steps to install CWM.

I d/led the 2GB version, extracted and there is a img file. What should I do with my 2GB card now. Thanks
[Nook Touch Android Development] mali100:
You write the img-file to an SD-Card (NOT DIRECTLY ON TO THE NOOK), as you did when you made your touchnooter SD-Card.

When you insert the SD and reboot, CWM will start (this will not install CWM, just start it from the SD-Card). There is really no need to install CWM on the device as long as you aren't developing and need it constantly.
[Nook Touch Android Development] winstonma:
I tried WinIMA method but it didn't work.
[Nook Touch Android Development] herofmm:
Try win32diskimager. It never failed for me.

https://launchpad.net/win32-image-writer/+download
[Nook Touch Android Development] traycold:
hi,

would it be possible to modify the CWM in order to implement a new feature in the storage or advanced menu?

I would need something like "fix system filesystem", that would run e2fsck command:

e2fsck -p /dev/block/mmcblk0p5

(please consider that in my case the automatic repair just worked, but maybe you know a better/safer way to set e2fskc, in order to fix system filesystem).

Currently, i have to: either boot with CWM sd-card, and launch the command through ADB; or boot with Noogie on linux, unmount system and launch the command from linux shell.

Having this feature directly in CWM would be way most easier! :cool:

I need sometimes to launch e2fsck since i'm making some experiment with framework.jar, involving several "push" of the file to Nook (using ADB): i found that this way, probably due to this file being in use, the disk space of the previous version of the file is somehow "corrupted", and after some time i run out of space on system filesystem ('df -h' says /system is full; while 'du -h /system' tell me that it is full only at 60-70%, i.e. what normally would be for system dir, without corrupted file!). Running the above e2fsck command reveal some corrupted files (something wrong with atime, if i remember well) and fix the issue.

Thanks for your help.
[Nook Touch Android Development] mali100:
hi traycold,

i made you an update.zip that executes

e2fsck -p /dev/block/mmcblk0p5

Just put it on your sd-card and use the install zip from sd-card option in CWM. I tried it and it should work, if you have any problems, let me know.
[Nook Touch Android Development] GabrialDestruir:
Would it be possible to get a copy of this that mounts internal /media too so you could put zips there and shrink down the image size required by an sdcard version of CWM?
[Nook Touch Android Development] traycold:
I tried it and it works perfectly. Thank you very much.
[Nook Touch Android Development] mali100:
I 'll take a look into it.
[Nook Touch Android Development] mali100:
The functionality to use the /media partition for update.zips is already included. Just use "install zip from sdcard" and then "choose zip from internal sdcard". If you want a shrinked down image, please make it yourself, as I currently have no access to my dev-box.
[Nook Touch Android Development] brendan10211:
Can i use this without an sd card? My parents don't like me using my _own_ money to buy things.

I kinda boot-looped my nook, by the way.

EDIT:

I just got a lexar SD card, 4gb... It is not working. I hold down the buttons until the screen changes, then I let go. What next?
[Nook Touch Android Development] mali100:
If you want to start cwm from the sdcard you don't have to hold the buttons, it starts automatically when the sdcard is present during boot.
[Nook Touch Android Development] brendan10211:
When I tried writing the image to the sd card, and loading it in, it just booted normally. Is this a problem?

Also, I am not sure how long to hold the buttons.
[Nook Touch Android Development] Googie2149:
You don't hold any buttons.
[Nook Touch Android Development] RubenRybnik:
I've burned CWM image onto the sdcard and copied a the files from the minimaltouch directions onto the card after cwm burn so I could install those. When I reboot with the sdcard in, it properly goes into CWM, however when I choose "Install from zip" cwm stats "Can't mount /sdcard/" am I missing something here?

EDIT: Chalk this up to user error ... I can't believe I did this, but word to the wise, mounting works much better when the micro sd is securely seated in the slot, lol ... sorry for the post ;)
[Nook Touch Android Development] Bonnie_Raitt:
Does this CWM allow me to format system, data,cache, etc? I am having a problem and it has been suggested that I use CWM to format my system partition. Here's the thread if you care to look.

http://xdaforums.com/showthread.php?p=24531703#post24531703
[Nook Touch Android Development] klausef:
Could you please upload the source code for this?

Thanks!
[Nook Touch Android Development] mali100:
http://xdaforums.com/showpost.php?p=20018397&postcount=38

You need the cyanogenmod source and build environment and you should check this post from koush http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
[Nook Touch Android Development] roustabout:
Having this environment available is great!

I just wrote a script for it that lets you link

/sdcard to

/data/media

this means you can use an sdcard for BN content. The device's storage limit is gone, and you can manage all of your files in Calibre.

Posted the script at http://www.mediafire.com/download.php?physd5t39dxfenx

and the full instructions at http://nookworks.blogspot.com/2012/05/fat-glowworm-using-your-sd-card-as.html
[Nook Touch Android Development] Sepharite:
Does this work with an SDcard larger than 2GB? Like 16GB?
[Nook Touch Android Development] brendan10211:
Yes, but the image will make the SD card think it is 2GB. I recommend grabbing a second, smaller (2gb) sd card and using that for clockwork, because if you only have one, you will have to remove it each time you boot.

Hope this helped! :D
[Nook Touch Android Development] Renate:
I've finally got around to doing something with this.

Since I am very minimal, I just downloaded install_cwm_recovery_rc2.zip from the first page,

unzipped it, then copied uImage to /boot/uRecImg and uRamdisk to /boot/uRecRam

That's all the functionality I would need to modify/patch things.
[Nook Touch Android Development] Renate:
I've found the Clockwork Recovery to be most useful.

I just copied over the two files to uRecImg and uRecRam.

That gives me a toehold when I screw something up on my Nook.

Just these two files by themselves provide ADB over USB.

It works fine when it works, but often the adbd seems to crash.

I noticed that the adbd in uRecRam is smaller than the one I use normally.

I replaced sbin/adbd in uRecRam and it still behaves about the same.

(The size that I'm using now is 134,136)

Any idea why this is so problematical?
[Nook Touch Android Development] rtoussaint:
How do I make a backup? I'm no stranger to CWM, but making a backup or a backup to internal sdcard fails for me. SD Card free space is 239MB (I have nothing installed locally) and I have an empty 4GB micro sd inserted. Boot and System are backed-up succesfully, but backup data fails. I get a generic error: Error while making a backp image of /data.

I've also tried the rom_update.zip, this fails with a status 7 error (filesystem?).
[Nook Touch Android Development] ApokrifX:
Renate,

Does it crash by itself after some time or when you execute some adb command?

It's gotta be a way to get a dump to see what adbd needs.

I think /data/anr is for java apps only...

I'm definitely not an expert in this area... :o
[Nook Touch Android Development] centralpark:
Help please

Did this enable you to install clockworkmod recovery onto your microsd card without having an adapter?

I currently don't have an adapter, so I'm looking for a way to install this without having one. :)
[Nook Touch Android Development] Renate:
If you have ADB or noogie working somehow, you can put those two files in the boot directory of the internal SD card.

You don't need any external SD card at all.

Boot with both lower side buttons pushed and it will go to CWR

or if your thumbs are tired, you can do this in ADB:

echo XXX > /rom/devconf/BootCnt
reboot
[Nook Touch Android Development] centralpark:
I don't have ADB or noogie working...oh well.

I have tried moving the files in ES file explorer as Super User...but each time I reboot the files disappear from the root directory of the internal sd card.

Thanks for trying to help :)
[Nook Touch Android Development] centralpark:
Would it be possible to create an apk file that would enable/disable multitouch?
[Nook Touch Android Development] centralpark:
I finally got adb up and running. However, when i type the following command, I get the error:

adb push uImage /boot/uRecImg

failed to copy 'uImage' to '/boot/uRecImg': No such file or directory

Do you have any ideas for what has gone wrong? Thanks so much! :confused:
[Nook Touch Android Development] Renate:
mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[Nook Touch Android Development] Renate:
People have been having so much trouble getting this all to work so I thought I'd repeat a few things.

First, safeguard you MAC, serial number, public key and hash of private key.

Any one of these will do, but all three will be better.

Use noogie and make a full backup

Copy over the p2 (/rom) partition to somewhere safe.

Copy over rombackup.zip from the p3 (/factory) partition to somewhere safe.

Clockwork Recovery uses two partitions on the internal SD card, p2 (/rom) and p7 (/cache).

If the p7 (/cache) partition is not ext3 and not mountable, CWR will complain loudly about /cache

If the p2 (/rom) partition is not vfat and not mountable or missing some files CWR will not boot at all.

USB ADB will work with Clockwork Recovery.

For Windows, you must have the correct driver installed.

You will know that everything is working when the taskbar icon show two separate devices,

one is the two USB Mass Storage devices and the other is the ADB interface.

Note that the USB ADB daemon on CWR seems to die upon disconnects.

See:

http://xdaforums.com/wiki/BN_Nook_Simple_Touch/Installing_ADB

http://xdaforums.com/wiki/ADB
[Nook Touch Android Development] Renate:
This part is still correct.

Getting ADB over USB to work from Clockwork Recovery has been problematical for me.

It doesn't seem to work easily, although I've found a few hints to make it more reliable.

Boot into CWR from powered off. Apparently the USB interface likes a power reset.

Before connecting the Nook to the desktop do an adb kill-server, then an adb usb.

Connect the USB cable, there should be USB connect bongs.

Go to the "safely disconnect hardware" icon and click on it, but do not disconnect anything.

There should be two lines indicated:

"Safely remove Android Composite ADB Interface"

"Safely remove USB Mass Storage Device - Drives (X:, Y: )"

Do adb shell

This part is not really relevant.

Now here is the weird part. I'm not sure how it ever worked.

I was getting this error:

- exec '/system/bin/sh' failed: No such file or directory (2) -

There is no /system/bin/sh or a symlink! Yet it used to work.

CWR uses everything in /sbin to leave room for mounting a normal system.

inside the ramdisk for CWR is init which specifically mentions /system/bin/sh

I extracted init from the ramdisk, modified it and reinserted it.

Now the adb shell works fine on CWR, but I can't figure out how it used to work!

modfile init 1364c 2f 73 62 69 6e 2f 73 68 00 00 00 00 00 00

(modfile is my utility but you can see what I'm doing. Use your hex editor.)

/system/bin/sh => /sbin/sh

Edit

Oops, I figured it out.

The adbd in CWR and the adbd you normally use in a rooted Nook are not the same.

Both have hard-coded into them the shell.

CWR adbd => /sbin/sh

Nook adbd => /system/bin/sh

(I have no idea what the shell path in init is doing, but it seems to work ok modified.)
[Nook Touch Android Development] digixmax:
Some months ago I had imaged sd_2gb_clockwork-rc2 to a SDcard in building a MinimalTouch SDcard. Recently I wanted to repartition/reformat that SDcard for another use, and found out that MiniTool Partition Wizard was not able to delete the existing FAT32 partition created by the sd_2gb_clockwork-rc2 image. I tried using SDformatter but it could not even see the SDcard (and hence reformat it) until after I first reformatted the SDcard with Windows.

As such I am curious as to what makes the FAT32 partition of this image so problematic for usually partition tools to handle it.
[Nook Touch Android Development] wozhere:
bump.
[Nook Touch Android Development] OverByter:
Windows only mounts the first partition on removable devices, if you inserted the card into the nook and then tried it should see both partitions.

OB
[Nook Touch Android Development] :
Ugh. Come on guys, do we really need to use USB at all?

Just get SwiFTP, mount all your partitions with Terminal Emulator and boom, you can access your whole filesystem over wifi. USB for file transferring is old news!

:D
[Nook Touch Android Development] Renate:
USB for file transferring is secure.

It's easier to just leave the WiFi off.
[Nook Touch Android Development] :
Well, okay. But if you have working WiFi, file transfer is much easier (at least for me) with ADB/SwiFTP.

Just my personal preference. :)
[Nook Touch Android Development] javelinanddart:
[MENTION=499922]mali100[/MENTION]

Does writing the image to the internal memory still brick the device? because the 1337 ROM Thread Says to write it to the internal memory but this thread says not to...

Also I'm confused on How to install the recovery to the internal memory. The OP and the post under it doesn't clearly outline the process.
[Nook Touch Android Development] :
1337 ROM's image is different than the image here that will brick ya if you write it. You can follow the 1337 ROM instructions to the letter and it'll work great.

Is this not clear enough?

You copy install_cwm_recovery_rc2.zip to the root of your microSD card, boot into CWM, and install the file using the Install zip from sdcard function.
[Nook Touch Android Development] javelinanddart:
Sorry. Didn't realize you could boot the recovery from the sdcard. Not used to that
[Nook Touch Android Development] :
Oh, lol.

You just write the .img file from sd_2gb_clockwork-rc2.zip to the microSD card, turn off your Nook, put in the microSD card, and turn it back on. Then you're in CWM and you can install the file. :)
[Nook Touch Android Development] Valentin4ou93:
I put the .img file on my SD card , but when I turn on the nook and push lower left and right keys appears screen that wants me to perform Factory reset . Can't get to recovery :confused:
[Nook Touch Android Development] kazikas:
You don't need to push any buttons, just insert SD and turn on your Nook. And you have to write (win32 Disk Imager or dd command) *.img not just put it in.