[NST][CWR][RC2] Clockworkmod based Recovery - fixed backup issue

[centralpark]

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

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

 

[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

Would it be possible to create an apk file that would enable/disable multitouch?

 

[centralpark]

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.

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!

 

[Renate]

mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot

 

[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.

1. Use noogie and make a full backup
2. Copy over the p2 (/rom) partition to somewhere safe.
3. 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://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
http://forum.xda-developers.com/wiki/ADB

 

[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.)

 

[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.

 

[wozhere]

bump.

 

[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

Sent from my SPH-D710VMUB using Tapatalk 2

 

[NOOK!E]

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!

 

[Renate]

USB for file transferring is old news!

USB for file transferring is secure.
It's easier to just leave the WiFi off.

 

[NOOK!E]

USB for file transferring is secure.
It's easier to just leave the WiFi off.

Well, okay. But if you have working WiFi, file transfer is much easier (at least for me) with ADB/SwiFTP.

Just my personal preference.

 

[javelinanddart]

Well, okay. But if you have working WiFi, file transfer is much easier (at least for me) with ADB/SwiFTP.

Just my personal preference.

@mali100
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!E]

@mali100
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.

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.

To replace the standard recovery of the N2E, copy also the install_cwm_recovery_xx.zip to the sdcard, boot into CWM and use the install zip from sdcard option to install it (it just replaces uRecRam and URecImg in the /boot partition, so you can also do it manually, if you want).

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.

 

[javelinanddart]

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.

Sorry. Didn't realize you could boot the recovery from the sdcard. Not used to that

 

[NOOK!E]

Sorry. Didn't realize you could boot the recovery from the sdcard. Not used to that

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.

 

[Valentin4ou93]

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.

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

 

[kazikas]

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

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.

 

[NOOK!E]

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

As @kazikas said, when you use CWM the "sdcard-written-img" way, you don't need to press the two bottom buttons. You only press those buttons to get to CWM recovery if you have CWM installed as your device's recovery (which I'd recommend).

Also, you can use WinImage to write the .img to the sdcard. Make sure that you don't use your Nook to mount the sdcard onto your PC, though - use an adapter instead.

 

[Valentin4ou93]

Maybe it was problem with win32 imager ..wrote tje .img again and it's now working . Thanks for the fast response anyway