Related
I bought my own nook color on saturday, there doesn't appear to be a factory image that can be restored. My new nook color came with version 1.01 preinstalled. Before turning it on the first time I put in nookie froyo and did a dd of all 8 of the stock partitions. Below is the zipped up .img files of mmcblk0p1/mmcblk0p5 (boot/system) from a stock untouched 1.01 nook color. I am also including the factory.zip. This should be enough to restore a bricked nook color with a corrupted boot or system partition. Many people have been able to restore to stock by just using the boot.img because after 8 failed boots it will do a factory reset.
To make this work you must have ADB working first. You may be able to get this to work on ADB Wireless, but I don't recommend it. For instructions on getting adb to work with the nook color go here:
http://nookdevs.com/NookColor_USB_ADB
To use these files unzip them to the sdcard portion of a nookie froyo sdcard, or just about any other rom that runs from the sdcard and run the following commands in an adb shell:
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
Boot
System
factory.zip
Thanks, you're a life saver!
samuelhalff said:
Thanks, you're a life saver!
Click to expand...
Click to collapse
Did it fix you samuelhalff?
Yes. But I only used boot.img. Then restored to stock with 8 failed boots. Dd'ing system will also work.
If it dosen't boot, do a factory reset with power+n.
Sent from my HTC Desire using XDA App
So if I put the factory.zip on /dev/mmcblk0p3 and replace the current one, when we do the 8 bad boot trigger we would get 1.0.1 flashed instead of 1.0.0 right?
Yes. And I would also do a power+n reset at the end, to avoid any problems.
Sent from my HTC Desire using XDA App
shad0wf0x,
I am having the same problem with my NC not booting after a failed attempt at
re-rooting. I will tell you in advance that I am VERY tech-phobic and don't comprehend all this command-line stuff well at all.
Given your original post above, could you please explain in layman's terms EXACTLY what steps to take to restore my NC to like-new? And hopefully it can be done with just simply putting some files on a micro SD and that's it. Please let me know from start to finish how I do this. Appreciate your help in advance.
vigeh4
P.S. I know I had no business doing this, but I screwed my unit up anyway. I already tried the 8-step interrupt thing before re-rooting but with no success.
vigeh4,
First download the first 2 files, system and boot, and then unzip them. Then you need to copy those 2 files (system.img and boot.img) to the sdcard, either while booted up in nookie froyo or by putting the sdcard in your computer. Then you must have adb working on your computer. open a command prompt or terminal(windows or mac/linux) and go to the location where your working adb is and copy and paste those commands into the window to run them.
Code:
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
shad0wf0x said:
vigeh4,
First download the first 2 files, system and boot, and then unzip them. Then you need to copy those 2 files (system.img and boot.img) to the sdcard, either while booted up in nookie froyo or by putting the sdcard in your computer. Then you must have adb working on your computer. open a command prompt or terminal(windows or mac/linux) and go to the location where your working adb is and copy and paste those commands into the window to run them.
Code:
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
Click to expand...
Click to collapse
Sorry, I am WAY confused about how to do this. This adb crap is over my head.
Maybe I just have a $250 paperweight at this point. If I mail you my NC, would you reset to "factory" for a small fee?
Thanks.
OMFG, thank you very much for these files and instructions.
I really thought I bricked it to the point of no return. I initially screwed it up when I installed Clockwork and wouldn't boot past "N", then after tinkering around some more, it wouldn't even turn on ... lol.
@vigeh
First you need to unzip those files you just downloaded. Second, you need to copy the "boot.img" and "system.img" (not the *.zip) to the "/SDCARD" folder on your SDCARD. I had to use WIFI FILE Explorer in Nookie Froyo cuz I messed up my nook so bad, i couldn't copy these files by turning on the USB Storage through the regular method. It took me days to figure this out cuz i'm kinda slow.
I hope you installed the Android-SDK on your computer already. If so, then go to the folder named "\platform-tools" on your PC - this is where ADB.EXE is located. Connect your nook and type "ADB DEVICES" just to make sure your nook is connected to the computer. It'll show up and tell you it is or not. If it is connected then do the following:
1. Type "ADB SHELL" then you'll see a "#" symbol after you hit enter.
2. Type "dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1" just the way it is written by the original poster (minus the "" marks)
at this point, it usually wont say anything. Just wait a few minutes and something will pop up. In my case, it says:
"477033984 bytes <454.9MB> copied, 138.757660 seconds, 3.3MB/s"
"#"
3. Type the second command next to the "#" sign "dd if=/sdcard/system.img of=/dev/block/mmcblk0p5"
wait another few minutes til the next confirmation pops up.
4. turn off nook, remove SD card
5. Hold the N button and the Power button at the same time and it'll ask you to reset the nook to factory settings.
I hope this helps you ....
well im a tard... i did this without reading that YOU CANNOT HAVE GOOGLE APPS!!!! so anyway Im trying to get back to a stock image, but i cant figure out how to copy 700 med +/- of images to 134 meg f free space. someone un-tard me plz . thanks
I have ClockworkMod Recovery installed, and if I put the factory.zip you provided on my sd card and use the option 'install zip from sdcard' will that in fact install factory settings on the nook?
I tried to do the 8 failed boots, but cannot get it to work with this installed.
shad0wf0x said:
vigeh4,
First download the first 2 files, system and boot, and then unzip them. Then you need to copy those 2 files (system.img and boot.img) to the sdcard, either while booted up in nookie froyo or by putting the sdcard in your computer. Then you must have adb working on your computer. open a command prompt or terminal(windows or mac/linux) and go to the location where your working adb is and copy and paste those commands into the window to run them.
Code:
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
Click to expand...
Click to collapse
How do you get to your "working adb?" I'm probably even more ignorant on this SDK stuff that vigeh4. I have SDK installed though.
How to get adb working is found here:
http://nookdevs.com/NookColor_USB_ADB
gconol said:
@vigeh
First you need to unzip those files you just downloaded. Second, you need to copy the "boot.img" and "system.img" (not the *.zip) to the "/SDCARD" folder on your SDCARD. I had to use WIFI FILE Explorer in Nookie Froyo cuz I messed up my nook so bad, i couldn't copy these files by turning on the USB Storage through the regular method. It took me days to figure this out cuz i'm kinda slow.
I hope you installed the Android-SDK on your computer already. If so, then go to the folder named "\platform-tools" on your PC - this is where ADB.EXE is located. Connect your nook and type "ADB DEVICES" just to make sure your nook is connected to the computer. It'll show up and tell you it is or not. If it is connected then do the following:
1. Type "ADB SHELL" then you'll see a "#" symbol after you hit enter.
2. Type "dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1" just the way it is written by the original poster (minus the "" marks)
at this point, it usually wont say anything. Just wait a few minutes and something will pop up. In my case, it says:
"477033984 bytes <454.9MB> copied, 138.757660 seconds, 3.3MB/s"
"#"
3. Type the second command next to the "#" sign "dd if=/sdcard/system.img of=/dev/block/mmcblk0p5"
wait another few minutes til the next confirmation pops up.
4. turn off nook, remove SD card
5. Hold the N button and the Power button at the same time and it'll ask you to reset the nook to factory settings.
I hope this helps you ....
Click to expand...
Click to collapse
Thanks to Shadowf0x for getting ABD to work
I have a question though, if I dont have the file "SDCARD" in my SD card then can I just make a new file and name it SDCARD, and put both of the .img's into it?
Sir a teema said:
I have ClockworkMod Recovery installed, and if I put the factory.zip you provided on my sd card and use the option 'install zip from sdcard' will that in fact install factory settings on the nook?
I tried to do the 8 failed boots, but cannot get it to work with this installed.
Click to expand...
Click to collapse
I'm not sure if that will work, I guess it's worth a try, however if you replace the existing factory.zip and do a factory reset you will restore back to 1.01 instead of 1.0 if you don't already have a nc that has 1.01 on it. I saw another thread about trying to use the factory.zip with cwm, but I didn't see anyone coming back and say it worked. How to flash back to stock is found here:
http://nookdevs.com/Flash_back_to_clean_stock_ROM
mmaner said:
well im a tard... i did this without reading that YOU CANNOT HAVE GOOGLE APPS!!!! so anyway Im trying to get back to a stock image, but i cant figure out how to copy 700 med +/- of images to 134 meg f free space. someone un-tard me plz . thanks
Click to expand...
Click to collapse
The nookie froyo sdcard partition for me was 900+m, and I've heard that all you need to do for this to work is to flash the boot.img.
Ign3nt said:
Thanks to Shadowf0x for getting ABD to work
I have a question though, if I dont have the file "SDCARD" in my SD card then can I just make a new file and name it SDCARD, and put both of the .img's into it?
Click to expand...
Click to collapse
You could try to mount the media partition in nookie froyo and put them there.
The partition is /dev/block/mmcblk0p8 and type is vfat.
shad0wf0x said:
The nookie froyo sdcard partition for me was 900+m, and I've heard that all you need to do for this to work is to flash the boot.img.
Click to expand...
Click to collapse
Ill try it tonight. thanks
I Highly suggest you follow the steps in this post first (http://forum.xda-developers.com/showthread.php?t=920347)
Froyo is completely stable and will give you a back up OS in case anything happens or you want to do something that doesn't work in HC.
Steps:
If anyone knows how to shrink a partition using parted please let me know. This would eliminate steps 2 & 3
QUICK EDIT WARNING: PLEASE READ: THIS IS BASED ON THE DUAL BOOT FROM ROOKIE1. FROM WHAT I KNOW THIS DOES NOT WORK ON 1.1.0 ONLY 1.0.1
(Note: Requires adb)
1 ) Have a working honeycomb v02 sd card (v03 has a custom kernel which causes rotation issues on the eMMC).
2) Install EASEUS (Windows) or gParted (Linux)
(if you need help with this just PM me)
3) Shrink the second partition of the SD card to 400mb
4) Download and extract my zip to your android/platform-tools folder
5) Run Internal.bat
Make sure not to format your sdcard from your nook while using this.
< standard disclaimer - I'm not responsible for whatever damage you did to your NC >
Also, the reason I did not post a clockwork zip or a dd img for system is I'm unsure of the legality of it, if someone else would like to then by all means do so.
PM me for any questions, and I would like to say thanks to samuelhalff, as without his help I never would've gotten it running from internal memory
Also, please make sure you know how to recover your nook color back to stock. Not only if something goes wrong, but since honeycomb isn't fully working yet.
That being said, if you run the dual-boot script first from rookie1 you'll always be able to fall back onto froyo to fix any issues.
----------------------------------------------------------------------------
How this works:
It copies the system partition from honeycomb onto the internal memory.
It then pushes my boot.img to your sd card.
Finally it overwrites your boot.img with mine
(My boot.img contains everything from rookie1's dual boot alongside the needed jar files included on honeycombs boot.img)
Download link:
http://www.multiupload.com/0TTH2OJS3C
Uploading fixed version now
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And for those who like doing everything manually. Here is Sam's modified uRamdisk. Make sure its on the bootpartiton alongside the jar files included in deeper-blue's release
Ramdisk: http://www.multiupload.com/90H38OX0S9
Also, the first time it starts up may take a few min. So be patient before trying to restart it
Thanks this will be very useful for myself and others. I'll report back with any issues.
Why must my laptop break today of all days?
Sent from my SPH-D700 using XDA App
marcusant said:
Why must my laptop break today of all days?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Sorry to hear that. I would say you could do it without one but you need the modified ramdisk inside my boot.img
Hey maybe i'm doing something wrong but i keep getting this error message:
rm failed for *, no such file or directory
i am not an expert on adb so this may be my fault, just reporting feedback for you.
tgallant21 said:
Hey maybe i'm doing something wrong but i keep getting this error message:
rm failed for *, no such file or directory
i am not an expert on adb so this may be my fault, just reporting feedback for you.
Click to expand...
Click to collapse
its not rm * its "rm * -r" as that is the recursive switch...
MattJ951 said:
I Highly suggest you follow the steps in this post first (http://forum.xda-developers.com/showthread.php?t=920347)
Froyo is completely stable and will give you a back up OS in case anything happens or you want to do something that doesn't work in HC.
Steps:
QUICK EDIT WARNING: PLEASE READ: THIS IS BASED ON THE DUAL BOOT FROM ROOKIE1. FROM WHAT I KNOW THIS DOES NOT WORK ON 1.1.0 ONLY 1.0.1
(Note: Requires adb)
1 ) Have a working honeycomb v02 sd card (v03 has a custom kernel which causes rotation issues on the eMMC).
2) Download and extract my zip to your android/platform-tools folder
3) Run Internal.bat
Make sure not to format your sdcard while using this.
Note: I'm not sure if you need to clear your data partition or not. I did, but it may not be required.
the steps under froyo would be : something similar to this (I dd'd HC data partition to the internal, so i'm not 100% sure of this)
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk1 /
mkdir data_temp
mount /dev/block/mmcblk0p6 data_temp
cd /data_temp [B]MAKE SURE THIS COMMAND WORKS BEFORE CONTINUING[/B]
rm * -rf
exit
< standard disclaimer - I'm not responsible for whatever damage you did to your NC >
Also, the reason I did not post a clockwork zip or a dd img for system is I'm unsure of the legality of it, if someone else would like to then by all means do so.
PM me for any questions, and I would like to say thanks to samuelhalff, as without his help I never would've gotten it running from internal memory
Also, please make sure you know how to recover your nook color back to stock. Not only if something goes wrong, but since honeycomb isn't fully working yet.
That being said, if you run the dual-boot script first from rookie1 you'll always be able to fall back onto froyo to fix any issues.
----------------------------------------------------------------------------
How this works:
It copies the system partition from honeycomb onto the internal memory.
It then pushes my boot.img to your sd card.
Finally it overwrites your boot.img with mine
(My boot.img contains everything from rookie1's dual boot alongside the needed jar files included on honeycombs boot.img)
Click to expand...
Click to collapse
You have verified this working with your boot.img? Mine gets hampered during the boot and locks up... I had the same issue when I was building my ramdisk for this purpose.... I am going to continue to look into this and will post anything I find.
Cheers!
A quick question:
You say not to format the SDCard while using this. Does this mean that there are still some system files on the SDCard after the procedure is done or can I format my card as FAT32 once the whole operation is done?
Ooglez said:
A quick question:
You say not to format the SDCard while using this. Does this mean that there are still some system files on the SDCard after the procedure is done or can I format my card as FAT32 once the whole operation is done?
Click to expand...
Click to collapse
I believe I may have included an incorrect boot.img in my original upload, im reuploading it now.
As for formatting the sd card, i'll clairfy that in the OP. Don't format the sd card from inside the nook. formatting it inside a computer is fine.
MattJ951 said:
How this works:
It copies the system partition from honeycomb onto the internal memory.
It then pushes my boot.img to your sd card.
Finally it overwrites your boot.img with mine
(My boot.img contains everything from rookie1's dual boot <B>alongside the needed jar files included on honeycombs boot.img)</B>
Click to expand...
Click to collapse
I think I see the issue, your dd image is lacking those jar files... I am going to try and add those files to my boot partition and go from there.... Disregard! per the post above this one.......
modembug said:
I think I see the issue, your dd image is lacking those jar files... I am going to try and add those files to my boot partition and go from there.... Disregard! per the post above this one.......
Click to expand...
Click to collapse
The boot.img must be from another project I was working on. It's using the wrong u-boot.bin and is missing the jar files. Updating main post in 20 seconds once it finishes uploading
And its up.
http://www.multiupload.com/KPDAPGYXSI
Also thanks for the feedback.
MattJ951 said:
The boot.img must be from another project I was working on. It's using the wrong u-boot.bin and is missing the jar files. Updating main post in 20 seconds once it finishes uploading
And its up.
http://www.multiupload.com/KPDAPGYXSI
Click to expand...
Click to collapse
Thanks for updating so quickly. I've been waiting to run Honeycomb off of EMMC. I'll let you know how it goes.
MattJ951 said:
The boot.img must be from another project I was working on. It's using the wrong u-boot.bin and is missing the jar files. Updating main post in 20 seconds once it finishes uploading
And its up.
http://www.multiupload.com/KPDAPGYXSI
Also thanks for the feedback.
Click to expand...
Click to collapse
I am getting ready to dd that image over as we speak, i will report back shortly...
No problem, let me know if it works and if it doesn't ill try updating it again. (I personally have it working but I didn't use a script, i entered the commands manually. Also make sure youre using v02 [though note: HC runs faster for some reason if you copy the data partition from v03 and dd it to the internal while running v02's system. v03 has problems with the kernel due to the 90degrees thing deeper added]
MattJ951 said:
No problem, let me know if it works and if it doesn't ill try updating it again. (I personally have it working but I didn't use a script, i entered the commands manually. Also make sure youre using v02 [though note: HC runs faster for some reason if you copy the data partition from v03 and dd it to the internal while running v02's system. v03 has problems with the kernel due to the 90degrees thing deeper added]
Click to expand...
Click to collapse
I am having issues with it locking up on "Android _ " could be due to crap on the data partition from the last boot.img... cleaning it off and trying again. Yeah I took a look at your bat file and just ran things manually... i have issues with unknown bat/sh files lol
UPDATE: okay, so its still locking up... did you dd the data partition or any of that stuff over as well? as of right now, i am running your boot.img and i DD'd the system partition from a working HC-SD, and i removed all files from the internal /data partition....
modembug said:
I am having issues with it locking up on "Android _ " could be due to crap on the data partition from the last boot.img... cleaning it off and trying again. Yeah I took a look at your bat file and just ran things manually... i have issues with unknown bat/sh files lol
Click to expand...
Click to collapse
Let me know if it works. The "Android _" screen originally locked up for me because of the uRamdisk. I'll upload the one Sam sent me which is included in the boot.img but maybe is causing problems for you.
The modified uRamdisk is now in the OP.
Nada, still no dice.... I have all the folders from HC /Boot with your boot files replacing uboot, uramdisk etc.. Still running into the same issue, might need to work busybox into this thing to see what is going on...
UPDATE: going to try dd'ing the /data part over to emmc /data..
modembug said:
Nada, still no dice.... I have all the folders from HC /Boot with your boot files replacing uboot, uramdisk etc.. Still running into the same issue, might need to work busybox into this thing to see what is going on...
UPDATE: going to try dd'ing the /data part over to emmc /data..
Click to expand...
Click to collapse
Thats not the problem. I realized my mistake.
where i wrote
adb shell dd if=/dev/block/mmcblk0p5 of=/dev/block/mmcblk1p1
it should be
adb shell dd if=/dev/block/mmcblk0p5 of=/dev/block/mmcblk1p2
if you run that it should boot correctly.
uploading a fixed version to the OP now
MattJ951 said:
Thats not the problem. I realized my mistake.
where i wrote
adb shell dd if=/dev/block/mmcblk0p5 of=/dev/block/mmcblk1p1
it should be
adb shell dd if=/dev/block/mmcblk0p5 of=/dev/block/mmcblk1p2
if you run that it should boot correctly.
uploading a fixed version to the OP now
Click to expand...
Click to collapse
which is why i run commands manually ;-) yeah I double check prior to DD and i have pushed the correct partition to /system... i have now pushed /data over and still no love... Can you dd your /boot and post it?
modembug said:
which is why i run commands manually ;-) yeah I double check prior to DD and i have pushed the correct partition to /system... i have now pushed /data over and still no love... Can you dd your /boot and post it?
Click to expand...
Click to collapse
That actually is my current /boot inside the 7z. Also i can't think of a reason why it wouldn't work.
I'll format my NookColor and try it to see if I can figure out whats going wrong.
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?
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