I've created a few flashable zip files to ease the eMMC dual boot setup. You can flash them using Clock Work Recovery.
Warning: Only specially packaged flashable dual boot ROMs like the ones I packaged below will flash to dual boot partition. Other flashable zips will overwrite your default boot.
Seems there is a problem flashing the zips from CWM on SD. See this post for a workaround, or use CWM on eMMC.
Just a word on booting into recovery. With the dual boot u-boot.bin, I have changed the button combo to VOL UP + VOL DOWN for recovery. So if you want to go to recovery, remember this is the key combo you need to hit. Not Power + n.
1. Prepare dual boot - http://dl.dropbox.com/u/20480343/prep-dualboot-0.1.zip
Flash this zip file will setup the dual boot partitions. If your NC is already setup using my previous dual boot script, there is no need to flash this again.
Note 1 - This does a resize of your /media partition. You data on /media should be intact. If you want to be safe, backup your /media before flashing.
Note 2 - /media partition will be resized to about 3.9 GB. If your existing data on /media is more that 3.9GB, you won't be able to flash this.
2. Remove dual boot - http://dl.dropbox.com/u/20480343/remove-dualboot-0.1.zip
If you want to revert to stock, simply flash this file.
3. Dual boot ROMs
Now the dual boot ROMs. These will be flashed to the dual boot partitions (partition 9 and 10) on eMMC. Hold 'n' button while powering up to boot into dual boot ROM.
My modified u-boot.bin based on B&N 1.2 source - Seems previous version is having compatibility issues with 2.6.32 kernel. This is updated base on B&N 1.2 source. Flash using CWM. It only overwrites the u-boot.bin on boot partition. Boot message should show "(multi)U-Boot v0.3 loading..." after flashing this zip.
Flashable dual boot Nookie Froyo v0.6.8
Flashable dual boot Honeycomb Preview v04
Flashable dual boot HC v04 with gapps - credit goes to pauljohnson75
Flashable dalingrin's 1.1GHz OC kernel for dual boot HC - credit goes to dalingrin for the oc kernel, and pauljohnson75 for creating the dual boot flashable
Flashable zip to move your stock Eclair to dual boot partition v02 - This is not really a ROM strictly speaking. To avoid infringing B&N IP, no file from stock ROM is included in this zip. Scripts in this zip simply copies your stock ROM partitions and make the necessary adjustment to ramdisk. After flashing this, you will have an identical ROM setup on your dual boot partition. You are free to do whatever to your default ROM. For example, you can flash other ROMs to overwrite your default ROM. You will still be able to boot into stock eclair by holding 'n' button. Only thing to note is if the other ROMs you flash overwrites u-boot.bin, you will lose the dual boot capability.
Flashable dual boot CM7 nightly (cm_encore_full-22)
Note 1 - You can flash this using CWM 3.0.0.5. Newer version of CWM not required.
Note 2 - This will convert secondary /system and /data partitions to ext4. They will not be compatible with other dual boot ROMs any more. You need to flash remove-dualboot-0.1.zip, then prep-dualboot-0.1.zip, before flashing other dual boot ROMs.
Note 3 - This will wipe your dualboot data partition.
Link not longer working
unknown.soul has packaged dalingrin's OC kernels for dual boot. Get them below. thanks unknown.soul
Eclair
Froyo
CM7
Honeycomb
Also gapps
Google Apps
Credits
cicada for Nookie Froyo. My update scripts are also based on his NF flashable.
deeper-blue for Honeycomb.
cm7 dev team for porting CM7 to NC
other xda developers who have contributed to NC community.
Holy Crap! How am I supposed to get any REAL work done today?
This is crazy awesome. I'm downloading everything right now. i will let you know how it goes.
Thank you!!!
Wow, this makes dual booting so much easier! thanks man!!
For real though, I have a deadline today and you come along and release this! You sir are awesome!!! Gonna flash it right now and then hopefully I can get some work done.
I see CM7 was just released. Would I be able to flash this to my dual boot partition?
racks11479 said:
For real though, I have a deadline today and you come along and release this! You sir are awesome!!! Gonna flash it right now and then hopefully I can get some work done.
I see CM7 was just released. Would I be able to flash this to my dual boot partition?
Click to expand...
Click to collapse
Normal flashables will flash to default partitions. That will overwrite your default boot OS. I have to package these flashable zips specifically to flash to dual boot partition. They are not compatible.
rookie1 said:
Normal flashables will flash to default partitions. That will overwrite your default boot OS. I have to package these flashable zips specifically to flash to dual boot partition. They are not compatible.
Click to expand...
Click to collapse
Yeah, I'd figured as much.... was hoping and wishing that under some miracle way it would have been possible. Thank you again for your hard work on this. It's pretty much made my day.
This is awesome downloading now. Are these just the base Roms or do they include any of the Google apps?
No gapps included.
get it here http://forum.xda-developers.com/showthread.php?t=917660
Is it possible to overclock this? If so, how?
racks11479 said:
No gapps included.
get it here http://forum.xda-developers.com/showthread.php?t=917660
Is it possible to overclock this? If so, how?
Click to expand...
Click to collapse
how does one push gapps and oc kernel in context of dual bootsetup?
rookie1 said:
I've created a few flashable zip files to ease the eMMC dual boot setup. You can flash them using Clock Work Recovery.
Click to expand...
Click to collapse
If I want to use this but keep oc 1100 for both froyo and eclair how do i do that. also if I want to install gapps on the froyo part of dual boot what mount commands do i need to push it to right place in adb?
Canadoc said:
If I want to use this but keep oc 1100 for both froyo and eclair how do i do that. also if I want to install gapps on the froyo part of dual boot what mount commands do i need to push it to right place in adb?
Click to expand...
Click to collapse
Not sure about the overclocking. I would really like to know how as well.
But with gapps. I didn't use adb. I just placed the unzipped gapps folder on my sdcard and installed it through terminal emulator in dev tools on my nook.
su
mount -o remount,rw /system
cp -r /sdcard/gapps/system/* /system
exit
Thats about it!
racks11479 said:
Not sure about the overclocking. I would really like to know how as well.
But with gapps. I didn't use adb. I just placed the unzipped gapps folder on my sdcard and installed it through terminal emulator in dev tools on my nook.
su
mount -o remount,rw /system
cp -r /sdcard/gapps/system/* /system
exit
Thats about it!
Click to expand...
Click to collapse
thanks will try this
what type of quadrant scores u getting on 800?
Just ran a quadrant of 969.
racks11479 said:
Not sure about the overclocking. I would really like to know how as well.
But with gapps. I didn't use adb. I just placed the unzipped gapps folder on my sdcard and installed it through terminal emulator in dev tools on my nook.
su
mount -o remount,rw /system
cp -r /sdcard/gapps/system/* /system
exit
Thats about it!
Click to expand...
Click to collapse
Can we access sdcard from either booted rom?
I flashed the NF one, and yes I'm able to mount and access my sdcard
Did anyone have any problems installing? I followed the instructions and I can get Nook Honey to boot but Nookie Froyo gets stuck at the Android_ screen, before the OS actually starts loading. I've tried reverting back to stock and starting over, and still no luck. Any suggestions would be greatly appreciated.
Awesome
Not sure how I did this but I didn't do a wipe or any formats before I installed all three zips. I installed all three at once from inside clockwork. Anyway my nookie froyo that I had setup perfect is still there just like I left it inculding the overclocked kernel. And if I hold down the n key and boot it boots right into Honeycomb not sure how I did this but its awesome. Thanks rookie1, now I just need to get gapps onto Honeycomb.
For oc kernels remember the file name is uFImg for the second boot. For those of you pushing an OC kernel to the alternate boot.
pauljohnson75 said:
Not sure how I did this but I didn't do a wipe or any formats before I installed all three zips. I installed all three at once from inside clockwork. Anyway my nookie froyo that I had setup perfect is still there just like I left it inculding the overclocked kernel. And if I hold down the n key and boot it boots right into Honeycomb not sure how I did this but its awesome. Thanks rookie1, now I just need to get gapps onto Honeycomb.
Click to expand...
Click to collapse
Why did you flash all 3 zips? You can only install one ROM on the new partition. I believe that this doesn't touch your original setup at all. It only flashes the rom on the new partition that was created.
Ok if someone can please help.
I have dual boot set up with eclair as stock boot and my n boot gives me froyo.
used titanium backup and have my froyo mostly back up and running though some apps caused soft reboots during the reinstall from TB.
Froyo seems to be running fine with what is installed so far. Flash is workig but since only getting quadrants in the 900-960 range it is kinda choppy. Was hoping there was a way to get the oc kernel onto the froyo boot as it is still present on the original eclair boot. The only real advantage for me of Froyo is that it should be faster and flash. But since it is not overclocked.....
Any ideas how to get the froyo oc kernel to the right place?
Related
First, I would like to thank cicada for the 0.6.8 image, thecubed for sdcard bootable CWR image, shad0wf0x for his stock images, dalingrin for his kernel, and samuelhalff for his help and his CWR image that I customized. This should fit on a 2GB or larger sdcard.
Please donate to the developer. Here is the original thread. http://forum.xda-developers.com/showthread.php?t=883175
This will erase your internal memory!
Flash with CWR
4/23/11
Went back to the 3/13/11 dalingrin's kernel
Made some changes in uRamdisk
Bluetooth is working
Wireless seems more stable
Try this without wiping data if you are coming from an earlier version
Changelog:
4/19/11
Added a status bar toggle
Added a feature to put up a notification as to the status of the status bar (this feature can be turned off in Nookie-Froyo Utils)
Added QuickDesk
Cleaned up the icons (I am finally happy with them... draw9patch)
Updated Nookie-Froyo Utils
Point of interest: If you set QuickDesk as your default launcher and add the status bar toggle to QuickDesk, you will be able to double tap the home button to hide or show the state bar.
This is a CRW zip. It will add some apps to /data/app but will not touch anything else in data so anything you've customized should still be there. So, DO NOT WIPE DATA. Also this zip will not touch cache, so if you have any problems you might format cache, but only do this if you are having problems. I hope by doing it this way will will eliminate any of the market problems we have had in the pass.
4/3/11
Status Bar and Notification window in black
No-frills CPU Control added
Added the following lines to init.rc
Code:
# sd card read speed fix
write /sys/block/mmcblk0/bdi/read_ahead_kb 2048
Updated NookColor Utils and rename it Nookie-Froyo Utils
- Forced Status Bar options added
- Change density and added new densities options
- Moved Reboot to about tab
- Added Poweroff to about tab
Updated to dalingrin's 3/31/11
Cleaned up the spacing on the status bar... Icons are not jammed up against the clock
This will not touch the /data partition
3/18/2011:
This should work on the eMMC version as well. I don't have a CWR package yet. Will make one tomorrow. If you want you can preview it now. You will not have to run softkeys as a service, but set the physical button to be one tap launcher and two taps softkeys for any app that hides the statusbar.
Unzip the attached framework.zip and copy to /system/framework/
This will be difficult for Windows users unless you have adb installed, but I would like some Linux users to test it out. I will try to write a script/app that will unzip and copy directly on the device. If someone else wants to write the script that would be okay too. I am try to avoid making everyone re-image their sdcard just to get the update.
Now to the good stuff, I have everything, messages, buttons and icons on the status bar centered vertically and the drop down notification bar is full screen at 160 LCD density.
Let me know how you like it and how you installed it. We need to come up with a easy install for non-techies that boot to the sdcard.[/COLOR]
Nookie Froyo 0.6.8.custom.3 eMMM
Put on dalingrin's latest kernel. (If you want to overclock it, you must use SetCPU)
Went back to using ClockworkMod Recovery 3.0.0.5
Changed build.prop back in a hope to improve video
LauncherPRO <----------
Nookie Froyo 0.6.8 eMMM
Change resolution back; I hated it
Applied the last patch I posted
Put on dalingrin's latest kernel
Using ClockworkMod Recovery 3.0.0.6
Nookie Froyo 0.6.7 eMMC (.2)
Added custom bootanimation.zip designed just for us Chuck6993. Thank you Chuck6993. If you like the bootanimation, please visit his thread and get him some love. http://forum.xda-developers.com/showthread.php?t=952188
An awsome utility to mount your /media and /sdcard to your pc. Thanks Samhalff. This is still at the beta stage and he would love to here from us for future improvements. Here is his thread. http://forum.xda-developers.com/showthread.php?t=952456
I wrote a script that will kill mediaserver. Just type kms as superuser in the terminal. It will automatically respawn, so you might have to do it again a couple of times. If your nook is running slow, it is most likely the mediaserver.
Nookie Froyo 0.6.7 eMMC (.1)
Added a mount command to init.rc for /media
Added an environmental variable for INTERNAL_STORAGE
Zeroed out unused space to make the image smaller
Added some software
DO NOT UNINSTALL THE SOFTWARE INSTALLED BY CICADA (Apparently, removing this software is reason for our market woes.)
Froyo 0.6.6 Custom eMMC (.2)
Replace /etc/vold.fstab with samuelhalff's vold.fstab
Change /mnt/media to /media in /etc/vold.fstab
Added a mount command to init.rc for /media
Added an environmental variable for INTERNAL_STORAGE
Zeroed out unused space to make the image smaller
Recovery Thread
Market Fix that seems to work well by ViralCipher
Images:
4/23/11 nookie-froyo.0.6.8.custom.7
4/19/11 nookie-froyo.0.6.8.custom.6
4/3/11: Nookie-Froyo.0.6.8.custom.5
Nookie Froyo 0.6.8 Custom eMMC .3
Nookie Froyo 0.6.8 Custom eMMC .2
PATCH: Apply after Nookie Froyo 0.6.8 Custom eMMC 1100 ghz OC
Nookie Froyo 0.6.8 Custom eMMC 1100 ghz OC
Nookie Froyo 0.6.7 Custom eMMC (.2)
Nookie Froyo 0.6.7 Custom eMMC (.1)
Froyo 0.6.6 Custom eMMC (.2)
Froyo 0.6.6 Custom eMMC (.1)
Froyo 0.5.9 and Stock 1.0.1 (Full - Boot and System) 2GB or larger sdcard. Point of Interest: For some reason, Win32DiskImager cannot handle this file, but WinImage works fine or just use dd in linux.
Froyo 0.5.9 Flash only
Burn to sd card... why not a flashable zip
i have 2 questions, does this fit on a 2gb sdcard, and do we burn it to the sd card like with the auto nooter? also, right this boots off the sdcard and does nothing to the internals?
edit
wait so it does mess with the emmc? which means we can format the sdcard on another android device and the nook will still run nf?
straby187 said:
Burn to sd card... why not a flashable zip
Click to expand...
Click to collapse
Unzip it. Burn that image to an sdcard. Then flash eMMC with CWR.
DiscoPh3v3r said:
i have 2 questions, does this fit on a 2gb sdcard, and do we burn it to the sd card like with the auto nooter? also, right this boots off the sdcard and does nothing to the internals?
edit
wait so it does mess with the emmc? which means we can format the sdcard on another android device and the nook will still run nf?
Click to expand...
Click to collapse
This is for eMMC and yes it will fit on a 1gb or higher sdcard. There is an image out there that will run from the sdcard.
whats different between this and other emmc versions posted?
Mytos-xda said:
whats different between this and other emmc versions posted?
Click to expand...
Click to collapse
You will not have to burn samuelhalff's CWR image then copy my sdcard /system and /data over to eMMC. This will put it directly on the eMMC.
brianf21 said:
You will not have to burn samuelhalff's CWR image then copy my sdcard /system and /data over to eMMC. This will put it directly on the eMMC.
Click to expand...
Click to collapse
is CWR integrated into the emmc after running this?
Mytos-xda said:
is CWR integrated into the emmc after running this?
Click to expand...
Click to collapse
No, I don't believe that CWR is working with froyo on the nook. I might be wrong about this.
Thanks Brian!
Any fixes? About to test now. Does market work out of the box?
more_xda said:
Thanks Brian!
Any fixes? About to test now. Does market work out of the box?
Click to expand...
Click to collapse
Tried in windows. Working great. Even installed flash 10.1 and watched some live video on Justin TV. Flash is surprisingly smooth. Market launches and displays all the software available, but fails to download. Any workarounds?
more_xda said:
Thanks Brian!
Any fixes? About to test now. Does market work out of the box?
Click to expand...
Click to collapse
Market works, update flash first then clear market cache then framework data, then reboot. Then update the rest.
No fixes, spent most of my time trying to figure out CWR and get everything on a 1 GB card. In addition to have a little family emergency in the middle of everything.
sec6 said:
Tried in windows. Working great. Even installed flash 10.1 and watched some live video on Justin TV. Flash is surprisingly smooth. Market launches and displays all the software available, but fails to download. Any workarounds?
Click to expand...
Click to collapse
Market works, update flash first then clear market cache then framework data, then reboot. Then update the rest.
brianf21 said:
Market works, update flash first then clear market cache then framework data, then reboot. Then update the rest.
Click to expand...
Click to collapse
To update flash does one just download it from the market? Also Is this version overclocked at all. Do over clocked versions still have the potential to overheat/explode due to the battery regulator being disabled or has that problem been remedied?
Downloading now
more_xda said:
To update flash does one just download it from the market? Also Is this version overclocked at all. Do over clocked versions still have the potential to overheat/explode due to the battery regulator being disabled or has that problem been remedied?
Downloading now
Click to expand...
Click to collapse
Flash can be updated from the market. This is not overclocked. Note to others: if you overclock it let me know how it goes and I will make an image of it. The battery issue has been fixed.
brianf21 said:
Market works, update flash first then clear market cache then framework data, then reboot. Then update the rest.
Click to expand...
Click to collapse
Did this, shut down. Then hit power to reboot. Won't boot now.
sec6 said:
Did this, shut down. Then hit power to reboot. Won't boot now.
Click to expand...
Click to collapse
Did you put in an sdcard? Try plugging in usb cable.
brianf21 said:
Did you put in an sdcard? Try plugging in usb cable.
Click to expand...
Click to collapse
Yes had an SD card installed (not the one with the image). I'm re-flashing again to see if I can get it to boot. I'll try the usb cable as well. I'll let you know.
sec6 said:
Yes had an SD card installed (not the one with the image). I'm re-flashing again to see if I can get it to boot. I'll try the usb cable as well. I'll let you know.
Click to expand...
Click to collapse
Sometimes, you just have to hold the button a long time (20 seconds or so).
brianf21 said:
Sometimes, you just have to hold the button a long time (20 seconds or so).
Click to expand...
Click to collapse
No go. Any suggestions for getting the boot repaired so I can boot and get things going again?
Will probably just try the boot repartition from the other emmc froyo thread. Will this work?
UPDATE: Since some of you guys are still finding this useful, I updated the CWM version to 3.0.2.8. Please note that ROM Manager is the best way to install CWM 3.0.2.8. You should only need this .zip if you need to restore the B&N boot loader.
There are a number of CWM installable .zip files being distributed that break Clockworkmod in a way that Rom Manager will not fix. This .zip file will reinstall the B&N bootloader (to enable the recovery buttons) and install ClockworkMod on your internal memory. This .zip will only help if you have installed a "flashable" .zip and can no longer get into CWM by holding N + Power on boot.
This file can be installed with IOMonster's bootable CWM to re-enable the ability to use CWM without an SD card.
How to use:
1) Create a bootable CWM SD card from the link above.
2) Mount the SD card on your computer and copy the RecoveryFix.zip file to it.
3) Boot the Nook into CWM from the SD card.
4) Choose "install zip from sdcard"
5) Choose "choose zip from sdcard"
6) Browse to the RecoveryFix.zip and select it.
7) Choose "Yes - Install RecoveryFix.zip"
CWM should now work by booting and holding the N + Power buttons.
Technical details:
The bootloader (u-boot.bin) file included with the stock image has code to look for the recovery key sequence on boot. It also contains the "Touch the Future of Reading" splash screen. Some of the update .zip releases include a custom uboot.bin (to change the splash screen) that does not look for the recovery keys...so there's no way to boot into recovery without an SD.
Currently the only automated way to put the correct files back is by using one of the stock recovery .zips. These take the entire system back to stock though. All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition. This can also be easily fixed by booting any image from an SD card and copying these files manually.
is this for use with any flashable rom or only certain ones? i'm on hcv4 and want to make sure this is safe to use before flashing it.
This worked fantastic! Thank you!
byproxy said:
is this for use with any flashable rom or only certain ones? i'm on hcv4 and want to make sure this is safe to use before flashing it.
Click to expand...
Click to collapse
This is a standalone fix - its only necessary if you've flashed a rom and could no longer boot into CWM recovery afterward.
thanks again xawen!
Thanks so much for this! Great work!
Signature verification failed
Will This work with the Froyo builds?
Thanks
huemedia said:
Will This work with the Froyo builds?
Thanks
Click to expand...
Click to collapse
It should work with any build. It does not replace any of the build specific files, just the boot loader and the recovery images.
Works on phiremod (CM7). I was stressing why I couldn't reach my internal recovery, but was too lazy to do any research on the matter. Just stumbled upon this and everything is fixed again
Just what I was looking for... thanks!
omarsalmin said:
Works on phiremod (CM7). I was stressing why I couldn't reach my internal recovery, but was too lazy to do any research on the matter. Just stumbled upon this and everything is fixed again
Click to expand...
Click to collapse
what do you mean by "everything is fixed again"?
I like phiremod and all, but no internal storage is irking me and I want to go back to rooted stock and try to make a CM7 bootable SD.
Flashed this, now I'm stuck on the "Touch the Future of Reading" splash screen. Running CM7 nightly latest, dalingrin's 1100MHz Overclock.
Edit: Trying to boot, won't get past that damn splash screen. Tried reflashing cm7-encore-full-5.zip, gapps, got nothing. Going to try flashing the overclock again and see if that helps.
Edit2: No dice. I don't have a backup, either. Guess I have to flash a whole new boot.img?
This should be stickied. There are a LOT of CWR files around here right now.
oshigeru said:
Flashed this, now I'm stuck on the "Touch the Future of Reading" splash screen. Running CM7 nightly latest, dalingrin's 1100MHz Overclock.
Edit: Trying to boot, won't get past that damn splash screen. Tried reflashing cm7-encore-full-5.zip, gapps, got nothing. Going to try flashing the overclock again and see if that helps.
Edit2: No dice. I don't have a backup, either. Guess I have to flash a whole new boot.img?
Click to expand...
Click to collapse
Same thing kept happening to me. I would hold down the power button or power+n button or power+volume up + n button to get the NC to shut down. Then, I'd press the power+volume up + n button for a few seconds; this would get it to boot into CWR. From CWR I'd select reboot system. After that it would have no problem fully booting (until the problem happeend again). I did notice that after a while the startup boot took longer. After pressing the power button to power on the NC it would take several seconds before the "touch the future of reading" screen to come up, and it would take several more seconds (30 or so) for it to get past that screen.
I'm not sure what the beneft is of doing this; as long as I have a CWR bootable microSD with me (always in the NC's case) I don't need this.
xawen said:
There are a number of CWM installable .zip files being distributed that break Clockworkmod in a way that Rom Manager will not fix. This .zip file will reinstall the B&N bootloader (to enable the recovery buttons) and install ClockworkMod on your internal memory. This .zip will only help if you have installed a "flashable" .zip and can no longer get into CWM by holding N + Power on boot.
This file can be installed with IOMonster's bootable CWM to re-enable the ability to use CWM without an SD card.
How to use:
1) Create a bootable CWM SD card from the link above.
2) Mount the SD card on your computer and copy the RecoveryFix.zip file to it.
3) Boot the Nook into CWM from the SD card.
4) Choose "install zip from sdcard"
5) Choose "choose zip from sdcard"
6) Browse to the RecoveryFix.zip and select it.
7) Choose "Yes - Install RecoveryFix.zip"
CWM should now work by booting and holding the N + Power buttons.
Technical details:
The bootloader (u-boot.bin) file included with the stock image has code to look for the recovery key sequence on boot. It also contains the "Touch the Future of Reading" splash screen. Some of the update .zip releases include a custom uboot.bin (to change the splash screen) that does not look for the recovery keys...so there's no way to boot into recovery without an SD.
Currently the only automated way to put the correct files back is by using one of the stock recovery .zips. These take the entire system back to stock though. All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition. This can also be easily fixed by booting any image from an SD card and copying these files manually.
Click to expand...
Click to collapse
This fixed my nook. Thanks!!!!!
Works - after a few tries!
Really appreciate the work. Thanks!
While I keep my boot disk with me, I am very happy to have the ability to power+N into CWR.
Great work, thanks m8s!
xawen said:
All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition.
Click to expand...
Click to collapse
Can you be more specific about exactly which u-boot.bin, uRecRam and uRecImg files are included - including source and version ?
ADude said:
Can you be more specific about exactly which u-boot.bin, uRecRam and uRecImg files are included - including source and version ?
Click to expand...
Click to collapse
This .zip has the stock (B&N) u-boot.bin and the uRecRam and uRecImg for CWM 3.0.0.5. It was built a while ago to fix an issue with specific CMW installable Froyo .zip files that were being distributed. I haven't seen any CM7 images with this problem, but if anyone still has a need for this I can update to a current CWM version and post tonight.
xawen said:
This .zip has the stock (B&N) u-boot.bin and the uRecRam and uRecImg for CWM 3.0.0.5. It was built a while ago to fix an issue with specific CMW installable Froyo .zip files that were being distributed. I haven't seen any CM7 images with this problem, but if anyone still has a need for this I can update to a current CWM version and post tonight.
Click to expand...
Click to collapse
Aha - I looked more closely and saw that it is an old thread that was brought to the surface by a "thanks" comment.
question
So I flash this fix and can get into CWM 3.0.0.5, then I flash the official CWM 3.0.1.0 and can no longer get into recovery. I also tried the manual procedure using adb. Still no dice.
What am I doing wrong?
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
Select 'Advanced'
Select 'Report Error'
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
Thank you Nemith
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
davidukfl said:
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
Click to expand...
Click to collapse
What rom are you running?
Nice! Thanks!
Sent from my DROIDX using Tapatalk
nemith said:
TL;DR: If you use RomManager go upgrade it in RomManager NOW!
Click to expand...
Click to collapse
My RomManager still sees 3.0.0.5 as the latest version.
Chahk said:
My RomManager still sees 3.0.0.5 as the latest version.
Click to expand...
Click to collapse
I provided a link/instructions to manual flash cwm. This may help.
Stock 2.1 rom
Sent from my DROIDX using Tapatalk
davidukfl said:
Stock 2.1 rom
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Grab /tmp/recovery.log from your device after you try to do a nandroid backup.
Thanks!
Excellent! I 'll have a new installclockwork.zip and universal bootable sd out here as soon as I get back from skiing
Thanks!
Thanks for the info. I have been waiting for this.
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!
John Kotches said:
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?
Click to expand...
Click to collapse
Either should work since both are ran from RAM.
Can the img file be written to an SDcard? Also, can Nandroids made with 3.0.0.5 be restored using the update?
Homer
nemith said:
Grab /tmp/recovery.log from your device after you try to do a nandroid backup.
Thanks!
Click to expand...
Click to collapse
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
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.
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
nemith said:
Either should work since both are ran from RAM.
Click to expand...
Click to collapse
I'll probably shove remove cw onto the bootable sd card and then push cw again from rom manager.
Moar gees with gginggerbread and tapatalk!
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
Updated rom manager with cm7 nightly 7. Worked flawlessly.
I had downloaded a version of this file from a post embedded deep inside one of the threads over here (sorry can't find it right now), but upon examination of its contents, I discovered some issues:
1. The checksums on the files in contained in the the original zip file showed that B&N had at least two versions of 1.3.0 update you can download from them, and the zip I got contained an older version so I put in the latest files in there.
2. There were unnecessary files included inside the original zip file, I deleted those, and only included what was needed.
3. There were errors in the script syntax, which I corrected, so that the proper commands are run during the update, and the proper sed substitutions are made during the editing of the unpacked init.rc inside the ramdisk.
What this zip will do is replace any older version of a B&N ROM on the alternate eMMC partitions of a dual booting configurations to the latest versions. This will prevent B&N from pushing the 1.3.0 update to you OTA, and messing up your dual boot setup. Just put the zip on your sdcard, boot into CWM recovery, and apply the zip. I apologize in advance for not giving credit to the original creators of the scripts here.
Note: There have been two different protocols for a dual booting u-boot.bin, with an older one relying on the files u-boot.altimg, and u-boot.altram to specify the names of the secondary boot ramdisk and kernel, and a newer one assuming that they are named uAltRam, and uAltImg respectively. This update conforms to the new u-boot.bin protocol. If you are still using the old one, you will have to get root access to /boot and edit the two files to point to uAltRam and uAltImg.
So if you want try it out, here it is:
http://www.mediafire.com/?gcrpzzc0kdoxcjx
MD5 Sum: 51e24c1e5eff11ba5ea481a63f7404eb
Update
I have now uploaded files for B&N Update 1.4.1.
The first file (MD5 Sum: 4ff1d9764663278c3f51e2e2c9d841a6) is meant to update a pre 1.4.1 Stock B&N ROM on secondary /system through CWM:
https://rapidshare.com/files/52135913/secondary_update_NC_stock_1_4_1.zip
The second file (MD5 Sum: c1506816fbfb8c419fbbc4afe1b12887) is meant to update a pre 1.4.1 Stock B&N ROM on primary /system through CWM without messing with recovery;
https://rapidshare.com/files/869435270/primary_update_NC_stock_1_4_1_keep_CWM.zip
The third file (MD5 Sum: ab1307c55a2c35c91d339c8037ce9a78) is meant to update a pre 1.4.1 Stock B&N ROM on primary /system through CWM, replacing recovery and all:
https://rapidshare.com/files/2059644016/primary_update_NC_stock_1_4_1.zip
None of these files will wipe user apps and data, so if you wish to do that, boot into recovery and wipe from there. [This will work on primary /data partition only]
Please note: If the B&N Stock ROM is rooted, you will lose root upon updating.
Thanks!
This worked beautifully! I flashed it from my sdcard after booting into CWM on my primary partition on emmc.
I'm betting you got the original from jasoraso in this dual boot thread: http://forum.xda-developers.com/showpost.php?p=17122342&postcount=142
What I would love is a straight CWM-flashable 1.3 ROM, to include in my up-to-date (for now) guide for setting up the dual boot, rather than having to set up and move 1.2, then update to 1.3.
That is possible to do by combining three of the steps. You need commands from the scripts from the prepare dual boot zip to resize /media and create the secondary system and data partitions, then the part of the script from the file that copies the contents of /data from primary to secondary and replaces u-boot.bin , and then my file which formats secondary /system and puts 1.3.0 there, and copies the latest kernel and patched ramdisk onto /boot. I can put such a file together, but I wouldn't be able to test it. The Nook belongs to my wife, and and you get the rest of the drift.
PS - You can use my file as is after running prepare dual boot and copy stock to secondary. It is not necessary to update secondary to 1.2 before going to 1.3.
Sent from my SAMSUNG-SGH-I897 using XDA App
rajendra82 said:
That is possible to do by combining three of the steps. You need commands from the scripts from the prepare dual boot zip to resize /media and create the secondary system and data partitions, then the part of the script from the file that copies the contents of /data from primary to secondary and replaces u-boot.bin , and then my file which formats secondary /system and puts 1.3.0 there, and copies the latest kernel and patched ramdisk onto /boot. I can put such a file together, but I wouldn't be able to test it. The Nook belongs to my wife, and and you get the rest of the drift.
Click to expand...
Click to collapse
Wait...what? What I'm talking about is a 1.3 zip made to work with CWM and in no way doctored to account for dual booting, just like the 1.2 zip one would otherwise use.
rajendra82 said:
PS - You can use my file as is after running prepare dual boot and copy stock to secondary. It is not necessary to update secondary to 1.2 before going to 1.3.
Click to expand...
Click to collapse
Have you tested this theory? I found that when I did not register my B&N install while it was on the primary partition, I was unable to boot into it on the secondary partition.
Taosaur said:
Wait...what? What I'm talking about is a 1.3 zip made to work with CWM and in no way doctored to account for dual booting, just like the 1.2 zip one would otherwise use.
Click to expand...
Click to collapse
Are you talking about updating an already rooted 1.0/1.1/1.2 Nook Color. I am sure the scripting to do that is exactly the same as what is in the 1.2 zip file. Just replace the 1.2 files inside the zip with the equivalent files from the 1.3 update. Make sure the portions which install su and busybox are included, and build.prop spoofig is applied. I am not sure it is worth it building such a zip file though. One is better off just applying the B&N update, and then rerooting with manual nooter. What I created was for people that have already doctored the setup for dual booting. In such a case, the B&N update would either fail, or would replace the primary partition instead.
Taosaur said:
Have you tested this theory? I found that when I did not register my B&N install while it was on the primary partition, I was unable to boot into it on the secondary partition.
Click to expand...
Click to collapse
No way to get around having to register the primary partition image first. Once that is done it could be moved to secondary and then updated straight to 1.3 instead of going 1.2 first.
I have a dual boot eMMC NC. I am not sure which setup I use but the last time I updated the CM7 nightly, I lost the dual boot until I installed the u-Boot again. I suspect I have the setup that looks for altFImg. So this is not going to work for me. I have 1.2 rooted which I use only occasionally. I am not even sure what is in 1.3 but I am curious.
yelloguy said:
I have a dual boot eMMC NC. I am not sure which setup I use but the last time I updated the CM7 nightly, I lost the dual boot until I installed the u-Boot again. I suspect I have the setup that looks for altFImg. So this is not going to work for me. I have 1.2 rooted which I use only occasionally. I am not even sure what is in 1.3 but I am curious.
Click to expand...
Click to collapse
All you need to do is boot into CM7, mount /boot as root, and then rename uFImg to uAltImg, uFRam to uAltRam, and then change the text inside u-boot.altimg and u-boot.altram to point to the new names instead of the old ones. This will keep you dual booting under the old u-boot.bin, and even after a new protocol u-boot.bin (like that installed by CM7) gets pushed to your Nook Color. Once you have done that, you can update the secondary to 1.3 using my zip file if you want.
rajendra82 said:
Are you talking about updating an already rooted 1.0/1.1/1.2 Nook Color. I am sure the scripting to do that is exactly the same as what is in the 1.2 zip file. Just replace the 1.2 files inside the zip with the equivalent files from the 1.3 update. Make sure the portions which install su and busybox are included, and build.prop spoofig is applied. I am not sure it is worth it building such a zip file though. One is better off just applying the B&N update, and then rerooting with manual nooter. What I created was for people that have already doctored the setup for dual booting. In such a case, the B&N update would either fail, or would replace the primary partition instead.
Click to expand...
Click to collapse
I wouldn't know what to change and what to leave alone, myself, but I think you're making this more complicated than it needs to be. I'm talking about installing 1.3 using CWM, regardless of how the device is partitioned or what was on the primary partition previously. Like the files in this thread, but 1.3: http://forum.xda-developers.com/showthread.php?t=1050520.
I understand that you were just cleaning up jaso's update-dualboot-to-1.3 file. I used the original and it worked fine, but it would have saved me a couple steps (and would be more useful in a guide for setting up dualboot) to simply install 1.3 rather than 1.2 to the primary partition when setting up. The reason I started with 1.2 is because it is the most current stock ROM available for CWM. What I would like is to avoid a historical re-enactment of stock OS development altogether. A general-purpose, CWM-flashable 1.3 ROM would be broadly useful, but is so far lacking as far as I've seen.
1. Do you envision this to be an uprooted stock 1.3 update ROM (either as primary or the only boot option) ? I just don't see the need for this to be CWM flashable. It is very easy to get there by resetting the device to stock, and then updating the device to 1.3.0 using the B&N file, and restoring dual boot as need be. If one has any older stock ROM running on primary, the B&N update will get them to 1.3 while losing root. There is no need to apply 1.2 update first.
2. Do you envision this to be for already rooted single or primary booting 1.1/1.2 users? There is once again no need to create any file for this. One can simply apply the B&N update, and then rerun manual nooter, and restore dual booting to the secondary.
3. The only users with no clear upgrade path are those who have already moved the B&N ROM to secondary. That's why I fixed up the zip file, and shared it. I am glad the original file worked for you despite the script errors. I can see other setups where it would have failed though.
I am not trying to make this more complicated than it needs to be. The Nook Color is just capable of being set up in so many ways, there isn't simply going to be a single update method that will work in all scenarios.
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm envisioning it as a one step, starting-point-agnostic means of establishing a 1.3 stock install, whether for setting up a dualboot or for any other purpose. Its usefulness is made evident by the three-page thread devoted to CWM-flashable 1.2 images: http://forum.xda-developers.com/showthread.php?t=1050520
Taosaur said:
I'm envisioning it as a one step, starting-point-agnostic means of establishing a 1.3 stock install, whether for setting up a dualboot or for any other purpose. Its usefulness is made evident by the three-page thread devoted to CWM-flashable 1.2 images: http://forum.xda-developers.com/showthread.php?t=1050520
Click to expand...
Click to collapse
Then the best bet is two step process:
1. Wipe device and restore to factory stock.
2. Download B&N 1.3 update file from website and place it on the root of SD card. Let the device recognize it, and apply it.
Once the 1.3 update gets applied, you are free to reroot, install CWM, set up dual booting, or whatever the next step may be.
It is the only method that will work in all circumstance as it involves starting from scratch regardless of setup. If want to preserve any of your current setup, no one step file will work for all circumstances. Some people have the stock firmware rooted, others do not. Some have the stock as the only internal boot, others have it as primary option of a dual booting configuration, while others have it as a secondary option. Some have stock recovery and run CWM off the sdcard when needed and want to update their recovery to the latest stock version, others want to keep the CWM recovery, and not update the recovery. There simply is no way file to cope with all these options.
rajendra82 said:
All you need to do is boot into CM7, mount /boot as root, and then rename uFImg to uAltImg, uFRam to uAltRam, and then change the text inside u-boot.altimg and u-boot.altram to point to the new names instead of the old ones. This will keep you dual booting under the old u-boot.bin, and even after a new protocol u-boot.bin (like that installed by CM7) gets pushed to your Nook Color. Once you have done that, you can update the secondary to 1.3 using my zip file if you want.
Click to expand...
Click to collapse
You lost me at mount
Seriously, I am trying to see if what I have is compatible with your update before I apply the update. I have a couple of useful apps on my CM7 and I have lost the password. I don't want to be stuck without CM7 or start over again. I can live without the 1.3 update though. So I want to make sure I am up to the task of finding and renaming these files if I have to.
With that said, how do I mount the /boot partition? I go into terminal emulator and give the su command. Then I tried mount /boot but that didn't work.
Thanks for your help.
rajendra82 said:
1. Wipe device and restore to factory stock.
Click to expand...
Click to collapse
...the only means of doing so "that will work in all circumstance" and in any way resembles a single step is flashing a stock zip via CWM. Why not use an up-to-date zip? The usefulness of such files is demonstrated by the fact that:
such files exist for past stock versions
those files are in use
files like yours are used to work around the non-existence of up-to-date stock zips
If you're so comfortable working with update files, you very likely could have produced such a file in less time than you've spent rationalizing away the clearly demonstrated need for them. Tell you what, in all likelihood I can just swap a few files from B&N's 1.3 zip into the existing CWM-flashable 1.2 zips, correct? Which files do I replace?
Anyone?
---------- Post added at 02:15 PM ---------- Previous post was at 01:58 PM ----------
yelloguy said:
You lost me at mount
Seriously, I am trying to see if what I have is compatible with your update before I apply the update. I have a couple of useful apps on my CM7 and I have lost the password. I don't want to be stuck without CM7 or start over again. I can live without the 1.3 update though. So I want to make sure I am up to the task of finding and renaming these files if I have to.
With that said, how do I mount the /boot partition? I go into terminal emulator and give the su command. Then I tried mount /boot but that didn't work.
Thanks for your help.
Click to expand...
Click to collapse
I don't know for sure, but wouldn't rajendra's update create properly-named boot files alongside the old, improperly named ones? Wouldn't the multiboot built in to recent CM7 builds then look for and boot from the more recent, properly named files? I can't confirm that's how it would work, but it's what I would expect.
Taosaur said:
I don't know for sure, but wouldn't rajendra's update create properly-named boot files alongside the old, improperly named ones? Wouldn't the multiboot built in to recent CM7 builds then look for and boot from the more recent, properly named files? I can't confirm that's how it would work, but it's what I would expect.
Click to expand...
Click to collapse
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
The fix is simple: to rename the files. But I need to know how before I take the plunge.
yelloguy said:
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
Click to expand...
Click to collapse
Right, but if you run a CM7 update, it would replace your uboot again. I'm not saying do it, just wondering out loud if it would work.
yelloguy said:
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
The fix is simple: to rename the files. But I need to know how before I take the plunge.
Click to expand...
Click to collapse
In order to rename the files, you can do the following:
1. Boot into CM7 (or any other place where you have command line root access)
2. Create a temporary directory at a location where you have read write access.
3. Type su in a terminal session to gain root access and then mount mmcblk0p1 at the temporary location you created using the command:
mount /dev/block/mmcblk0p1 <full path to the directory you created>
4. Now use Astro to go over to the directory you created and mounted mmcblk0p1 into. You should see:
u-boot.bin which is the bootloader
u-boot.bin.stock which is the backup of the old stock bootloader
uImage and uRamdisk which are your primary kernel and ramdisk
uFImg and uFRam which are your secondary kernel and ramdisk (and whose names are mismatching the CM7 bootloader protocol)
u-boot.altimg and u-boot.altram, which are text files per the old bootloader method containing names of uFImg and uFRam
5. Rename uFImg to uAltImg, uFRam to uAltRam. And edit the contents of u-boot.altimg and u-boot.altram to match the new file names.
6. Reboot as usual into primary or secondary.
Now if an CM7 update ever replaces your u-boot.bin, you will not lose dual boot, as you have it set up as uAltImg and uAltRam per the new protocol.
Sent from my SAMSUNG-SGH-I897 using XDA App
---------- Post added at 03:24 PM ---------- Previous post was at 03:06 PM ----------
Taosaur said:
...the only means of doing so "that will work in all circumstance" and in any way resembles a single step is flashing a stock zip via CWM. Why not use an up-to-date zip? The usefulness of such files is demonstrated by the fact that:
such files exist for past stock versions
those files are in use
files like yours are used to work around the non-existence of up-to-date stock zips
If you're so comfortable working with update files, you very likely could have produced such a file in less time than you've spent rationalizing away the clearly demonstrated need for them. Tell you what, in all likelihood I can just swap a few files from B&N's 1.3 zip into the existing CWM-flashable 1.2 zips, correct? Which files do I replace?
Anyone?
Click to expand...
Click to collapse
I am sorry if you think I am rationalizing, but that was not my intention. I just wanted to point out that the files you linked to do not meet your own criteria.
Take for example the file update-nc-stock-1.2-keepcwm-signed.zip that you point to as missing in an up to date 1.3 version. That file will update a Nook Color to 1.2, but will keep CWM recovery. It however will make someone whose Nook Color 1.1 was rooted using autonooter lose root. A person that has been dualbooting to CM7 on secondary will lose that ability as well after applying that update. So unlike what you think, this is not a file to update stock 1.2 update under all circumstances regardless of what the starting point is. It has a specific use (update fro, a pre 1.2 stock primary eMMC boot, no dualboot, CWM recovery installed). Creation of an all situation stock restore file is impossible IMO, and the best you can do is wipe and apply 1.3 B&N stock update. You or I could technically create another equivalent file with update-nc-stock-1.3-keepcwm.zip /system files, kernel, ramdisk, etc., but this file would be subject to the same side effects as the original.
---------- Post added at 03:30 PM ---------- Previous post was at 03:24 PM ----------
Taosaur said:
Right, but if you run a CM7 update, it would replace your uboot again. I'm not saying do it, just wondering out loud if it would work.
Click to expand...
Click to collapse
It would work. If you apply my zip, there will be a uAltImg and uAltRam in /boot (in addition to uFImg and uFRam). If you apply another update that pushes the CM7 bootloader, it will then look for these files with trying to do an alternate boot, and would boot into a unrooted stock 1.3.
rajendra82 said:
In order to rename the files, you can do the following:
1. Boot into CM7 (or any other place where you have command line root access)
2. Create a temporary directory at a location where you have read write access.
3. Type su in a terminal session to gain root access and then mount mmcblk0 at the temporary location you created using the command:
mount /dev/block/mmcblk0 <full path to the directory you created>
Click to expand...
Click to collapse
I get an error:
mounting <paths> failed: Device or resource busy
Any ideas?
yelloguy said:
I get an error:
mounting <paths> failed: Device or resource busy
Any ideas?
Click to expand...
Click to collapse
I see a typo in my command (stupid Swiftkey X). It should be:
mount /dev/block/mmcblk0p1 <some directory>
Also try typing just mount in terminal to see if /dev/block/mmcblk0p1 is already mounted somewhere else.
rajendra82 said:
Take for example the file update-nc-stock-1.2-keepcwm-signed.zip that you point to as missing in an up to date 1.3 version. That file will update a Nook Color to 1.2, but will keep CWM recovery. It however will make someone whose Nook Color 1.1 was rooted using autonooter will lose root. A person that has been dualbooting to CM7 on secondary will lose that ability as well after applying that update. So unlike what you think, this is not a file to update stock 1.2 update under all circumstances regardless of what the starting point is. It has a specific use (update fro, a pre 1.2 stock primary eMMC boot, no dualboot, CWM recovery installed). Creation of an all situation stock restore file is impossible, and the best you can do is wipe and apply 1.3 B&N stock update. You or I could technically create another equivalent file with update-nc-stock-1.3-keepcwm.zip /system files, kernel, ramdisk, etc., but this file would be subject to the same side effects as the original.
Click to expand...
Click to collapse
Riiiiight... it would install stock 1.3 to the device. That's the intended behavior. The point is to avoid the unnecessary step of updating in any process that includes flashing stock to the sole or primary partition. One example of such a process would be a fresh dual boot setup. That it does not update or otherwise rely upon an existing install is the point.
Granted, such a file would not repartition the device, but it would install up-to-date stock in one step regardless of how a device is partitioned (1/5, 2/5, 5/1 or dual boot).
Hello you DualBooters and Triplebooters out there!
SDCacheMount for SD-Roms
Well, this idea came to me because many users of my triple-boot SD were getting tired of the rebuilding of system-cache when every time they had to switch between roms. What I have here is a small script that will install to /system/etc/init.d The script will run at boot time and create a 100mb .img file to be used for /cache. This way each rom will have its own dedicated /cache partition so to say. This will also benefit anybody that dualboots (eg. EMMC / SD-Rom). I've prepped two different versions. One for my triplebooters out there and the other for anyone running a rom off an SD card.
Things to note:
-This will dd a 100mb .img file to your /sdcard partition of your sd-rom on first boot. What this means is that before the system progresses any further the img file needs to be created so that the /system can use it as the /cache partition.
-It will sit at a black screen for up to 1 minute possibly. So please be patient!!!
-The dd'ing of the .img only happens on first boot. So once the cache .img is created. Boot time will be normal on successive boots.
-Make sure you have enough space on the /sdcard partition of your sd-rom.
-So for Dualbooters you will need at least 100mb free
-For Triplebooters you will need at least 200mb free
-Now you can switch between EMMC roms and SD roms without having to wait for /cache to rebuild every single time.
DOWNLOAD:
DUALBOOTERS ( EMMC / SD )
**You should be able to flash this from a standard CWM Recovery or rename the .zip file to begin with "update-" for Verygreens method.**
SDCacheMount_DualBooters.zip
Click to expand...
Click to collapse
TRIPLEBOOTERS ( EMMC / DUALBOOT-SD )
**You should only use the CWM Recovery that is included with my Dualboot-SD**
SDCacheMount_TripleBooters.zip
Click to expand...
Click to collapse
Big thanks to:
DizzyDen for helping me out with the script
Shumash for troubleshooting it for me
Inportb for some guidance
HacDan for his sense of humor
Hope this helps a few of you Nookers out there!
Thanks,
Racks
Reserved?!
Great job! gonna have a try on this
So the main advantage of this script is smaller booting time?
And this is the case when you switch Roms only between emmc and sd or also 2 different roms from same sd?
Unleashed from my Nook Color at 1.2G
RASTAVIPER said:
So the main advantage of this script is smaller booting time?
And this is the case when you switch Roms only between emmc and sd or also 2 different roms from same sd?
Unleashed from my Nook Color at 1.2G
Click to expand...
Click to collapse
The advantage of the script is that each AOSP will have its own dedicated cache and not all be utilizing the same space for all the cache.
RASTAVIPER said:
So the main advantage of this script is smaller booting time?
And this is the case when you switch Roms only between emmc and sd or also 2 different roms from same sd?
Unleashed from my Nook Color at 1.2G
Click to expand...
Click to collapse
The most obvious effect is that booting between the various ROM's is seamless (except for the minimal wait at the blank screen) and fast. It makes switching between the AOSP's very easy. The less obvious, behind the scenes effect is as Dizzy describes.
It should be noted that if you flash an updated or newer ROM, you will also need to reflash the SDcacheMount.zip.
shumash said:
The most obvious effect is that booting between the various ROM's is seamless (except for the minimal wait at the blank screen) and fast. It makes switching between the AOSP's very easy. The less obvious, behind the scenes effect is as Dizzy describes.
It should be noted that if you flash an updated or newer ROM, you will also need to reflash the SDcacheMount.zip.
Click to expand...
Click to collapse
Yes correct, thank you. I'll make note of that in the OP. Also note that once the .img cache is created, although you have to reflash the SDCacheMount after flashing a new rom. It won't have to create a new .img. The script will detect if one exist already and if so, proceed to boot. But if you don't flash the SDCacheMount right after flashing the new ROM. /cache will default back to /emmc
-Racks