[RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD (1.1 Compatible!)

hacku · Feb 16, 2011

thecubed said:
(We now have 128mb, 1gb, 2gb, 4gb, and 8gb images!)

This may be a stupid question, but I'd rather be safe than sorry. So these different size images, do you download the one corresponding to the size of the SD card that you'll be using to boot?

I'm only downloading CWR, so if I'm putting it on a 8GB SD card I should download the 8GB image, right?

thecubed · Feb 16, 2011

hacku said:
This may be a stupid question, but I'd rather be safe than sorry. So these different size images, do you download the one corresponding to the size of the SD card that you'll be using to boot?

I'm only downloading CWR, so if I'm putting it on a 8GB SD card I should download the 8GB image, right?

Yes.

Download the proper sized image for your SD card. If you download the 128mb image and put that on your 8gb card, it would temporarily resize your 8gb card to 128mb, which would be of no use for making nandroid backups.

hacku · Feb 16, 2011

Thanks! This worked great...

I now have Honeycomb running in eMMc and it's smoooooth.

Crimton · Feb 17, 2011

mightybrick said:
I think the rootpack on the mirror is corrupted. I'm only getting a 20mb file that will not extract. The rootpack downloading from the original host is very slow.

same here. i cannot get it to extract successfully and what is extracted is only 22MB and has the same name as the tar.gz. getting an error during extraction

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

edit: the mirror and original download are not the same size

fpga_guy · Feb 17, 2011

fpga_guy said:
I cannot seem to "buy" books from BN after updating the ROM to 1.1 and rooting. I tried these methods:

Method 1
Register stock 1.0.1 NC
Upgrade by copying 1.1 to NC via usb cable as suggested by BN
Root with Rootpack 0.7
Everything works but browsing for book from BN.

Method 2
Register stock 1.0.1 NC
Root with Rootpack 0.7
Load Nook Color V1.1.0_r2 [01/29/2011] by Decad3nce
Still can't buy books.

Did 1.1 do something? There is along thread regarding using BN features at stores with 1.1.

Thanks again

I posted this question in http://xdaforums.com/showthread.php?p=11411627#post11411627

It appears that if you root 1.1 with Rootpack 0.7 the "Shop" feature where you can browse and buy books is disabled. The symptom is that the Shop program just hangs and FC.

I had to restore to stock and then use Auto-nooter 3.0.0

jttraverse · Feb 17, 2011

running CWR still causes the CWR boot loop..

thecubed said:
There's no problems using my rootpack to root 1.1, the only bug at the moment is the installclockwork.zip seems to get people stuck in CWR.

Just use the new rootpack to root 1.1 and install CWR from within 1.1 using rom manager.

Interesting development in case no one else has noticed this. I had previously cleared everything and gone back to stock v1.1. I then used the Monster Root Pack to root my Nook, but this time did not install CWR (because of previous experience where I got stuck in the boot loop back to CWR). After things came up nicely, then I installed CWR from inside ROM Manager and things seemed fine. Rebooting works normally if I turn the device off and on.
What I've found, however, is that if I go into ROM Manager and from there I select the option to reboot to CWR, it does reboot--but afterward it is again back to the CWR boot loop. At that point I have to use the original 128mb Rootpack and run the 'uninstallclockwork' zip in order to be able to reboot normally. I can reinstall CWR just fine, and everything seems to be functional as long as the Nook is not rebooted using the 'reboot to CWR' from inside ROM Manager.

So, there may be some issue either with the way the Monster Root Pack does things, or maybe with how ROM Manager ties in with CWR, or maybe just CWR itself on v1.1. But I think maybe I need to go back to stock and root the device with Autonooter instead and see if CWR behaves the same way after that.

Anyone else seen this?
-JTT

PMDColeslaw · Feb 17, 2011

Im lost, lol. I followed the directions in the wiki and I was able to flash the root.zip and gapps.zip. I reboot and everything comes up fine. When I try to launch youtube, it just reloads the extras app drawer. Also when I try to use the SoftKeys app it says unable to execute as root. What am I doing wrong? I just got my NC today and its version 1.0.1

thecubed · Feb 17, 2011

jttraverse said:
Interesting development in case no one else has noticed this. I had previously cleared everything and gone back to stock v1.1. I then used the Monster Root Pack to root my Nook, but this time did not install CWR (because of previous experience where I got stuck in the boot loop back to CWR). After things came up nicely, then I installed CWR from inside ROM Manager and things seemed fine. Rebooting works normally if I turn the device off and on.
What I've found, however, is that if I go into ROM Manager and from there I select the option to reboot to CWR, it does reboot--but afterward it is again back to the CWR boot loop. At that point I have to use the original 128mb Rootpack and run the 'uninstallclockwork' zip in order to be able to reboot normally. I can reinstall CWR just fine, and everything seems to be functional as long as the Nook is not rebooted using the 'reboot to CWR' from inside ROM Manager.

So, there may be some issue either with the way the Monster Root Pack does things, or maybe with how ROM Manager ties in with CWR, or maybe just CWR itself on v1.1. But I think maybe I need to go back to stock and root the device with Autonooter instead and see if CWR behaves the same way after that.

Anyone else seen this?
-JTT

This seems to be a known bug for Clockwork. I believe it's related to the boot manager (u-boot) for 1.1.

For now, I'd recommend against installing clockwork to your internal storage and instead relying on a SD card for using clockwork until this is sorted out.

smashbottom · Feb 17, 2011

thecubed said:
This seems to be a known bug for Clockwork. I believe it's related to the boot manager (u-boot) for 1.1.

For now, I'd recommend against installing clockwork to your internal storage and instead relying on a SD card for using clockwork until this is sorted out.

I just opened the package rooted and such, installed clockwork and I'm now stuck on this rotation, how do I exactly get out of it?

thecubed · Feb 17, 2011

smashbottom said:
I just opened the package rooted and such, installed clockwork and I'm now stuck on this rotation, how do I exactly get out of it?

use the uninstallclockwork.zip file in the rootpack. it seems to set things back to normal.

jhnstn00 · Feb 17, 2011

I have cwr installed on internal via your update zip. How to I get to recovery? I like quickbook to het to recovery, does that work?

Sent from Continuum 2.2 w/ Sensation 1.2 (Awesome)

fwdixon · Feb 17, 2011

jhnstn00 said:
I have cwr installed on internal via your update zip. How to I get to recovery? I like quickbook to het to recovery, does that work?

Sent from Continuum 2.2 w/ Sensation 1.2 (Awesome)

Power + n for

Sent from my SCH-I500 using Tapatalk

jhnstn00 · Feb 17, 2011

fwdixon said:
Power + n for

Sent from my SCH-I500 using Tapatalk

Thanks

Sent from Continuum 2.2 w/ Sensation 1.2 (Awesome)

smashbottom · Feb 17, 2011

thecubed said:
This seems to be a known bug for Clockwork. I believe it's related to the boot manager (u-boot) for 1.1.

For now, I'd recommend against installing clockwork to your internal storage and instead relying on a SD card for using clockwork until this is sorted out.

thecubed said:
use the uninstallclockwork.zip file in the rootpack. it seems to set things back to normal.

Thank you!

For those that are having a similar problem like me, I found the downloadable file here:

legacyschool.us.to/nookdev/clockwork/0.7/zips/extras/

smashbottom · Feb 17, 2011

I've done the "Install zip from sdcard" and selected Removeclockwork... I install it, and reboot the device and clockwork still starts back up! Anyone have any other ideas?

thecubed · Feb 17, 2011

smashbottom said:
I've done the "Install zip from sdcard" and selected Removeclockwork... I install it, and reboot the device and clockwork still starts back up! Anyone have any other ideas?

...did you remember to remove the SD card?

If the SD card is in, the device will ALWAYS boot to clockwork.

If you format the SD card, it will go back to being a normal SD card, and you can leave it in on boot without the device booting to clockwork.

smashbottom · Feb 17, 2011

thecubed said:
...did you remember to remove the SD card?

If the SD card is in, the device will ALWAYS boot to clockwork.

If you format the SD card, it will go back to being a normal SD card, and you can leave it in on boot without the device booting to clockwork.

Maybe that was it, I had the SD card in, but now I'm getting the black screen where it will not bootup, or flash.

I've done everything in this thread with no luck:
http://xdaforums.com/showthread.php?t=949699

I've tried both the rootpack or the clockware recovery image...

I even tried hitting the Power button alone many times, and with the home button... attempting to get the 8 fail thing.

I then attempted to put the auto-nooter3 on the SD card, no luck, no screen flash or anything....

I have two nook color's I'm playing with, therefore I've formated the card multiple times using a different android device...

fwdixon · Feb 17, 2011

smashbottom said:
Maybe that was it, I had the SD card in, but now I'm getting the black screen where it will not bootup, or flash.

I've done everything in this thread with no luck:
http://xdaforums.com/showthread.php?t=949699

I've tried both the rootpack or the clockware recovery image...

I even tried hitting the Power button alone many times, and with the home button... attempting to get the 8 fail thing.

I then attempted to put the auto-nooter3 on the SD card, no luck, no screen flash or anything....

I have two nook color's I'm playing with, therefore I've formated the card multiple times using a different android device...

plug it into a pc and see if it gets detected. It may be on but the screen isn't. Happens occasionally. You can either wait for the battery to die or disconnect and reconnect the battery cable (pull the back off, and there is a little plug for the battery cable up near the volume buttons)

smashbottom · Feb 17, 2011

fwdixon said:
plug it into a pc and see if it gets detected. It may be on but the screen isn't. Happens occasionally. You can either wait for the battery to die or disconnect and reconnect the battery cable (pull the back off, and there is a little plug for the battery cable up near the volume buttons)

Thank you, I've rooted many devices without problems... I was thinking, "If I could just tear the damn battery out it'll probably work fine."

I unplugged the battery and plugged it back in, no luck. No nothing. I attempted to plug it into the computer and nothing...

For an unbrickable device, I've sure done a good job at not allowing myself to get it to turn on...

and it's been on the charger all afternoon, except when I was fiddling with it

thecubed · Feb 17, 2011

smashbottom said:
Thank you, I've rooted many devices without problems... I was thinking, "If I could just tear the damn battery out it'll probably work fine."

I unplugged the battery and plugged it back in, no luck. No nothing. I attempted to plug it into the computer and nothing...

For an unbrickable device, I've sure done a good job at not allowing myself to get it to turn on... and it's been on the charger all afternoon, except when I was fiddling with it

Woah, hold up.

So, now you get nothing on the screen when you turn it on with NO sd installed?

What happens if you boot it with my rootpack SD in?

...if it shows CWM when you boot with my rootpack SD, then it just means that you hosed your /boot partition.

Check around here for the complete restore to stock .zip. It has a complete partition backup that should set you straight, no need to ever pull the battery.

(I may be incorrect, but with our device, there should never be a need to pull the battery-- holding the power button for 20 seconds will trigger the cpu to power off. It's not a software thing- it will ALWAYS work.)

[RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD (1.1 Compatible!)

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Member

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Member

Member

Inactive Recognized Developer

Member

Senior Member

Member

Inactive Recognized Developer

Similar threads

Top Liked Posts