[RECOVERY] Official CWM 3.2.0.1 Update (Support for newer NCs!)

Search This thread
By:
Advanced…
N

nemith

Senior Member
Jun 20, 2010
218
456
CWM has been updated officialy to 3.2.0.1! See the Changelog and FAQ below for more information!

Changelog:
  • 3.0.0.5 - Initial official release for the nook. Only supported ext3. Had bootloop errors with the 1.1.0 update. (Note: Unofficial builds supported ext4 but not both at the same time)
  • 3.0.0.6 - No significant changes to 3.0.0.5 officially. (Note: Unofficial builds supported ext3 or ext4 but not both at the same time)
  • 3.0.0.8 - Broken build. Blame the samsung phones for messed up additions.
  • 3.0.0.9 - Adds official support for ext4 as well as compatability for ext3. (i.e. No need to swap recovery for different ROMs). Fixes "Always boots into recovery" with 1.1.0 updated u-boot.bin
  • 3.0.1.0 - Adds support to for /sd-ext to recovery.
  • 3.0.2.8 - Sets /system to ext2. You can now backup and restore your stock roms! Delete/Update all 3.0.0.5 threads to point to 3.0.2.8 for all rom types. Rom Manager now pushes a recovery kernel as well as the ramdisk!! No need to manually install recovery kernel. Just flash the lastest from RomManager and you are done!
  • 3.2.0.0 - Support for newer nooks with the 5G /data parition! New .32 kernel is included which fixes the freezing after formatting /data! (/data format issues. Don't Use)
  • 3.2.0.1 - Fixes a bug with 3.2.0.0 (actually a build issue) where ext3 (/data and /cache) wouldn't be formatted properly (they were but CWM was bombing out)
    *Recommended *

RomManager can now push the recovery kernel. No need to manually install via CWM or ADB! Flash from RomManager and rock and roll.

Q: Why should I upgrade?
As of the official version 3.0.0.9 there CWM supports both ext3 and ext4 ROMs with a single recovery image. This means no more of this swapping back and forth between different versions of CWM! 3.0.2.8 sets /system to ext2 to allow for proper backing up and restoring of stock roms!

This version also fixes issues with the 1.1.0 version of u-boot.bin. Some with this version may experience that your NookColor will always boot back into RomManager. This is now fixed (as of 3.0.0.9)
Click to expand...
Click to collapse

Q: But I have CWM <insert older version> I am good right?
Always use the latest found on this post or on RomManager. Older version are not supported
Click to expand...
Click to collapse

Q: I used RomManager to install CWM but now i can't use backup or restore
This should be fixed. Report any issues to me either on this thread or via PM
Click to expand...
Click to collapse

Q: I upgraded CWM and now my market doesn't work.
Installing CWM doesn't alter any rom or data files which shouldn't have any affect on recovery. There is something else that may have affected your market.

No worries though you can try the following to try and fix it:

  • If you are using CM7. Upgrade to the latest nightly (which will be after tonight: 3/3)
  • Try clearing the following: For "My Apps," go to manage apps, market, uninstall updates, clear market cache. Then delete data for Google Framework Services.
Click to expand...
Click to collapse

Q: I have upgraded but now I am having issues?
So some of you are still having issues with this new CWM version. PLEASE PLEASE PLEASE give me the following information:

  • What you are trying to do/accomplish. Be as detailed as possible
  • What rom you are running and what rom you are upgrading to (if applicable)
  • IMPORTANT! Grab a recovery.log from your nookcolor. You can do this either through adb or through the advanced menu. If I don't have this then there is little I can help with.
Click to expand...
Click to collapse

Q: How do i grab the recovery.log?
Method 1: ADB
After setting up adb type:

Code: 
adb pull /tmp/recovery.log

You are done. (This is why everyone should learn and setup ADB. It really is stupid simple)


Method 2: Save from the menu
From the ClockworkMod Recovery main screen do the following

  1. Select 'Advanced'
  2. Select 'Report Error'
  3. There is now a copy of recovery.log on your sdcard. Transfer the sdcard to a computer or boot into your rom and mount your sdcard on your computer.
Click to expand...
Click to collapse
 
Last edited:
  • Like
Reactions: robbieas, guta84, crucialdude and 63 others
D

davidukfl

Senior Member
Apr 19, 2010
529
198
Seattle
www.crypto-designs.com
i flashed this earlier today, at first it kept bootlooping so i used the remove CW zip and got rid of it. The 2nd install went fine (both times i rebooted before booting into CW)

however CW says it cannot mount system so i'm unable to make a full backup
 
thecubed

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,458
Austin, TX
Excellent! I 'll have a new installclockwork.zip and universal bootable sd out here as soon as I get back from skiing :)

Thanks!
 
J

John Kotches

Senior Member
Apr 6, 2009
565
68
Collinsville, IL (STL Metro)
So I'm stuck in the CM boot loop. Can I install from the boot-looping CM or do I flash it from the SD loaded CM?

No problem either way, just curious what the best approach is?

Moar gees with gginggerbread and tapatalk!
 
H

Homer_S_xda

Senior Member
Dec 5, 2010
427
61
Can the img file be written to an SDcard? Also, can Nandroids made with 3.0.0.5 be restored using the update?

Homer
 
  • Like
Reactions: nemith
N

nemith

Senior Member
Jun 20, 2010
218
456
Homer_S_xda said:
Can the img file be written to an SDcard? Also, can Nandroids made with 3.0.0.5 be restored using the update?

Homer
Click to expand...
Click to collapse

Yes. There is nothing special about the images written to an sdcard. You can even rename the files to uImage and uRamdisk to have it boot without the two-finger salute on the sdcard.
 
N

nemith

Senior Member
Jun 20, 2010
218
456
davidukfl said:
the tmp folder is empty. In the clockwork folder on the SD card the boot.img file is in there though.

When i create a backup it says cannot mount system, and when i got to advanced and hit mount system it says the same thing
Click to expand...
Click to collapse

There should always be a /tmp/recovery.log. You need to grab this while in recovery via adb

Code: 
adb pull /tmp/recovery.log
 
KitF

KitF

Senior Member
Dec 14, 2010
413
79
Philadelphia
kit.im
I can't mount /system either. Using CM7. I also have a dual-boot partition, but I doubt that matters.

from log:

mounting /system!
W:failed to mount /dev/block/mmcblk0p5 (No such device)
Error mounting /system!

Also:

E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p7 (No such device)

edit: Here's the full pastebin
 
Last edited:
You must log in or register to reply here.

Similar threads

thecubed
[RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD (1.1 Compatible!)
Replies
300
Views
343K
J
Jsilva124
D
Android 3.0 Honeycomb Preview Image v04 - 2/7/2011
Replies
2K
Views
1M
fattire
fattire
cicada
[ZIP][DEV][ROM] Nookie Froyo 0.6.8 (02/15) CWM flashable!
Replies
1K
Views
408K
S
stevedavid678
C
[RECOVERY] Making an updated bootable ClockworkMod SD
Replies
152
Views
317K
T
tomudei
G
[NC][1.2][1.3] ManualNooter 4.6.16
Replies
2K
Views
810K
D
Dakaro

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 66
    N
    nemith
    CWM has been updated officialy to 3.2.0.1! See the Changelog and FAQ below for more information!

    Changelog:
    • 3.0.0.5 - Initial official release for the nook. Only supported ext3. Had bootloop errors with the 1.1.0 update. (Note: Unofficial builds supported ext4 but not both at the same time)
    • 3.0.0.6 - No significant changes to 3.0.0.5 officially. (Note: Unofficial builds supported ext3 or ext4 but not both at the same time)
    • 3.0.0.8 - Broken build. Blame the samsung phones for messed up additions.
    • 3.0.0.9 - Adds official support for ext4 as well as compatability for ext3. (i.e. No need to swap recovery for different ROMs). Fixes "Always boots into recovery" with 1.1.0 updated u-boot.bin
    • 3.0.1.0 - Adds support to for /sd-ext to recovery.
    • 3.0.2.8 - Sets /system to ext2. You can now backup and restore your stock roms! Delete/Update all 3.0.0.5 threads to point to 3.0.2.8 for all rom types. Rom Manager now pushes a recovery kernel as well as the ramdisk!! No need to manually install recovery kernel. Just flash the lastest from RomManager and you are done!
    • 3.2.0.0 - Support for newer nooks with the 5G /data parition! New .32 kernel is included which fixes the freezing after formatting /data! (/data format issues. Don't Use)
    • 3.2.0.1 - Fixes a bug with 3.2.0.0 (actually a build issue) where ext3 (/data and /cache) wouldn't be formatted properly (they were but CWM was bombing out)
      *Recommended *

    RomManager can now push the recovery kernel. No need to manually install via CWM or ADB! Flash from RomManager and rock and roll.

    Q: Why should I upgrade?
    As of the official version 3.0.0.9 there CWM supports both ext3 and ext4 ROMs with a single recovery image. This means no more of this swapping back and forth between different versions of CWM! 3.0.2.8 sets /system to ext2 to allow for proper backing up and restoring of stock roms!

    This version also fixes issues with the 1.1.0 version of u-boot.bin. Some with this version may experience that your NookColor will always boot back into RomManager. This is now fixed (as of 3.0.0.9)
    Click to expand...
    Click to collapse

    Q: But I have CWM <insert older version> I am good right?
    Always use the latest found on this post or on RomManager. Older version are not supported
    Click to expand...
    Click to collapse

    Q: I used RomManager to install CWM but now i can't use backup or restore
    This should be fixed. Report any issues to me either on this thread or via PM
    Click to expand...
    Click to collapse

    Q: I upgraded CWM and now my market doesn't work.
    Installing CWM doesn't alter any rom or data files which shouldn't have any affect on recovery. There is something else that may have affected your market.

    No worries though you can try the following to try and fix it:

    • If you are using CM7. Upgrade to the latest nightly (which will be after tonight: 3/3)
    • Try clearing the following: For "My Apps," go to manage apps, market, uninstall updates, clear market cache. Then delete data for Google Framework Services.
    Click to expand...
    Click to collapse

    Q: I have upgraded but now I am having issues?
    So some of you are still having issues with this new CWM version. PLEASE PLEASE PLEASE give me the following information:

    • What you are trying to do/accomplish. Be as detailed as possible
    • What rom you are running and what rom you are upgrading to (if applicable)
    • IMPORTANT! Grab a recovery.log from your nookcolor. You can do this either through adb or through the advanced menu. If I don't have this then there is little I can help with.
    Click to expand...
    Click to collapse

    Q: How do i grab the recovery.log?
    Method 1: ADB
    After setting up adb type:

    Code: 
    adb pull /tmp/recovery.log

    You are done. (This is why everyone should learn and setup ADB. It really is stupid simple)


    Method 2: Save from the menu
    From the ClockworkMod Recovery main screen do the following

    1. Select 'Advanced'
    2. Select 'Report Error'
    3. There is now a copy of recovery.log on your sdcard. Transfer the sdcard to a computer or boot into your rom and mount your sdcard on your computer.
    Click to expand...
    Click to collapse
    View
    6
    M
    Mistar Muffin
    Flashable zip for version 3.0.1.0

    I made something for those that don't want to mess with adb and mounting partitions:

    http://muffinworld.net/android/nookcolor/clockwork/cwmr_3.0.1.0.zip

    Flash this using your current CWMR (either eMMC or bootable SD version will work). It will put the latest recovery image + kernel on your eMMC boot partition. You can launch to it as normal by choosing reboot to recovery in CM7 or by holding NOOK button + PWR at boot.

    -Muffin
    View
    5
    woot1524
    woot1524
    Ok, here's a guide to flash CWM 3.0.1.0 onto the eMMC.

    1: If you do not have any version of CWM on your eMMC. Meaning you never EVER installed it ever.
    Step 1: create a bootable CWM SD-card. It doesn't matter what version of CWM. You can use the images from this thread: http://forum.xda-developers.com/showthread.php?t=922870
    Step 2: Download the Flashable .zip of CWM 3.0.1.0 from the first post of this thread.
    Step 3: Copy said .zip file onto the root dir. of your bootable CWM SD-card
    Step 4: Boot to SD-card
    Step 5: Flash the .zip file
    Done


    2: If you have installed a previous version of CWM on your eMMC (such as 3.0.0.6) or tried to install CWM via Rom-manager, again on your eMMC. And now you cannot boot into CWM via pwr+home. OR when you boot the eMMC(internal) and have anything other than 'touch the future of reading' as the first splash screen.
    Step 1: Have a bootable CWM SD-card, any version will work.
    Step 2: Get the recovery repair flashable .zip from this thread: http://forum.xda-developers.com/showthread.php?t=958748
    Step 3: Boot to SD-card
    Step 4: Flash recovery repair .zip


    3: If 2 did not work for you. AKA you still cannot boot into CWM on the eMMC with pwr+home.
    Step 1: Have a bootable CWM SD-card, any version will work
    Step 2: Get the CWM root-safe removal tool from this thread: http://forum.xda-developers.com/showthread.php?t=914690
    Step 3: Get the CWM 3.0.1.0 flashable .zip from the first post of this thread.
    Step 4: Get the kernel for your specific system from dalingrin's thread, which is here: http://forum.xda-developers.com/showthread.php?t=925451
    Step 5: boot CWM SD-card
    Step 6: Flash CWM root-safe removal tool
    Step 7: Flash CWM 3.0.1.0 .zip
    Step 8: Flash your specific kernel you got on step 4.
    Step 9: Reboot

    2 and 3 also will fix most 'stuck at 'n' screen' and 'stuck at 'touch the future of reading''

    I hope this clears everything up.
    View
    2
    N
    nemith
    clockworx said:
    I was running Honeycomb V4, and installed this, then switched over to Nookie Froyo just to get easy root so Rom Manager could run. I cannot for the life of me seem to get into Recovery. I've tried:

    1) Manual flash from the OP
    2) Boot w/ Power + n key (I think this is right)
    3) Switch to Nookie Froyo, Rom Manager ran fine, Reboot into manual recovery and "Install ROM" both did nothing. (just rebooted back into Nookie) Booting with Power + n also isn't doing anything.

    Am I missing some really obvious step?
    Click to expand...
    Click to collapse

    It seems that some people may have replaced their u-boot.bin at some point to a version that will not boot into recovery.

    Try grabbing a u-boot.bin from the official 1.1.0 update and use adb to push that to your /boot partition.
    View
    2
    anurbanlegend
    anurbanlegend
    ovar said:
    And where do I push it? I can't find a boot directory when browsing my phone with adb.
    Click to expand...
    Click to collapse

    The first post has the code to mount the boot partition. Then just push the u-boot.bin over.

    EDIT: try
    Code: 
    adb shell busybox mount / -o rw,remount
adb shell busybox mkdir /boot
adb shell busybox mount /dev/block/mmcblk0p1 /boot
adb pull /boot/u-boot.bin u-boot.bin.bak
adb push u-boot.bin /boot/u-boot.bin
adb shell busybox umount /boot
    View

New posts