Well,
(I guess I'm back..)
Here's a flashable ZIP of HC v4 to install on eMMC.
Note: 30.03.11
These packages (zip) can't make it complicated for you to go back to other roms, with working recoveries, etc.
Please flash the file found on this post before flashing another rom, if you wish to use, for example, CM7.
THIS WILL ERASE YOUR INTERNAL MEMORY (CWR as well)!
This is:
- Deeperblue's HC for NC (installed on eMMC), see http://forum.xda-developers.com/showthread.php?t=936995
- With dalingrin's OC kernel (1100) instead of stock HC kernel, see http://forum.xda-developers.com/showthread.php?t=925451
- Gapps included (I ended up using jleecong's files) see http://forum.xda-developers.com/showthread.php?t=937752
- Root (su) included (credit goes to chhaggerty and NuroSlam) see http://forum.xda-developers.com/showthread.php?t=941445)
All usual disclaimers apply. Please do not try this if not absolutely sure of what you are doing. Cicada's Froyo on eMMC is a far better option for people looking for stability. I must urge you to consider that deeperblue's HC for Nook Color is under constant upgrade. This means HC v5 could be available very soon.. Maybe you should wait until a more stable version of HC is available. Though deeperblue has done a great job at resolving issues.
NOTE: This version works well, but still has a few bugs..
MAJOR Credit goes to deeperblue for a his impressive work on HC. CM team for helping him. Dalingrin for his constant achievements regarding stable OC kernels..
To avoid having a black screen on boot, I've removed permissions on 'bin/newfs_msdos'. This prevents boot partition from getting corrupt. This means you won't be able to format an SD card from your NC once this is installed. Do it from you PC, or manually with ADB and parted/fdisk.
------EDIT-----
This last paragraph means that some apps won't install while SD is mounted. Either remove SD when having problems with app not installing, or restore permissions (chmod 777 system/bin/newfs_msdos) on newsfs_msdos. If you choose latter option, do not attempt to format SD from your NC from that moment and beyond!
------EDIT-----
I decided to leave dalingrin's kernel by default, as I found that perfomance was noticeably better. If people wish to have a flashable zip to restore to stock HC, please say so.
Instructions:
This file should be used with IOMonster bootable CWR SD image (could also work with internal CWR, but internal CWR will be removed during installation, and if internal CWR crashes during install your NC wont boot again. If that happens to you use the CWR SD and you'll be fine). Download the image, burn to SD and only then copy this flashable zip at the root of the SD.
Download CWR SD image here: http://forum.xda-developers.com/showthread.php?t=922870
Boot with SD inserted, go to 'mounts and storage', and:
- format system, then data and THEN format boot (CWR may crash, simply hard reboot, format should have worked).
- still in mounts and storage, check that system, data are not mounted (it should say 'mount data', not 'unmount data')
- go back with power button, go to 'install zip from sdcard'
- go to 'choose zip from sdcard'
- select 'HC-v4-emmc.zip'
Wait until the end of install. Be patient. It should say 'Install from sdcard complete'. Don't panic if the progress bar doesn't show progress. As long as it says 'Done, all finished'.
Turn off NC.
Remove SD card.
Boot and be happy..
HC/eMMC flashable ZIP file: http://www.multiupload.com/797T7K393P
md5sum c962b33ba234bad6581d573a11cef7ee
Thank you.
PS: it seems that I've left LauncherPro installed on this version. If you're not happy with it, just remove it. I for one have changed LPro settings to open app drawer instantly (see speed options). This does give a slick impression.
PS2: mirrors are welcome.
PS3: FYI, I've personnaly tried out converting data (p6) and cache (p7) to ext4, and making necessary tweaks for it to work along with Dalingrin's kernel. It does seem a bit more responsive. I'm willing to share my uRamdisk with ext4 support, but you need to know how to convert you eMMC partitions. This is risky business and I won't recommend it. This version here is ext3 only. Sorry.
Click to expand...
Click to collapse
EDIT-02-21/2011 ------
Second edition release of HC v4 on eMMC
flash with Ext4 Bootable SDCard (see http://forum.xda-developers.com/showthread.php?t=959240).
H4 v2 second edition release, with a few tweaks and updates:
- System, data and cache fs will convert to EXT4, minor performance boost.
- Gingerbread Gapps added: Market, Maps, Gmail, Calendar, Contacts, Talk.
- SD card format now works, thus no more issues with installing apps when card inserted (storage menu doesn't always refresh, change setting tab and back)
- Removed LauncherPro, can be installed from market
- More apps available in market, still many missing (i.e, angry birds)
- Ad-hoc fix added
- Rooted, working su (Thanks to j4mm3er). Superuser installed and working
- CWR Ext4 integrated with ugly workaround. Use RecoveryBootUtility app to boot to CWR on internal (Without the need for a bootable SDCARD). Booting to CWR with power+n will not work. You will have to boot to HC, then use Utility app to boot to CWR.
Do not use this internal CWR to flash Froyo or Eclair, use previous Ext3 Bootable CWR sdcard and format system, data and cache before doing so. The Ext4 integrated CWR will only work for this HC version (not previous) and for CM7.
- Added my USB Mass storage utility app (if you're having trouble with a mounted partition, make sure it's unmounted from NC before using utility, i.e unmount sdcard before mounting it to pc). Use this to open sdcard or media on your PC.
- Calendar fix added.
- Maps 5.0, do not upgrade to 5.1. It won't work on HC.
- Gallery 3d added -> working gallery.
- Various tweaks..
Issues:
- Many apps don't work.
- Talk may disconnect sometimes, you'll have to make sure you time settings are correct (don't use automatic setting). You can also try changing time, Force close Talk and launch it again. Sorry for this..
- Location won't work. This is a preview, supposed to be working on a Virtual emulator. Only Mock locations work. If you're adventurous, try enabling mock locations in settings, installing 'Android developer shell' on NC, enabling telnet server in app, and using:
- geo gpsSpoofer start
- geo gpsSpoofer fix [latitude] [longitude]
(geo -help if you have trouble with commands.)
You'll have a working spoofed location. Reboot will erase it..
- Other issues, I'll update if required. I've struggled to get other apps working. But without HC's source, it's pretty much impossible..
NOTE: oddly enough, I've launched maps 5.0 this morning and, though it's asking me to enable location provider, it found my location just a few seconds after opening the app... I don't know it it's Latitude related. I'll investigate..
Instructions:
These differ from above instructions, but you can refer to them if you have a doubt.
- Boot to Ext4 Bootable CWR SD with zip file on it.
- In mounts and storage, format /system, /data and /cache -> MANDATORY!
- In the same menu, make sure /system aren't /data aren't mounted
- make sure sdcard is mounted
- choose zip from sdcard
- flash file WAIT, be patient! Progress will not display, but it will work.
- Remove sdcard, boot to HC.
HC-v4-emmc-2nd-edition flashable zip: http://www.multiupload.com/47M6MIFS9A
117.33 MB
ac42f8ca2d04e15b8981593e60b0abc1 HC-v4-emmc-2nd-edition.zip
Mirror, thanks to MikeSpears:
http://mikeservers.net/nookdev/honeycomb/HC-v4-emmc-2nd-edition.zip
The internal CWR workaround is ugly to say the least. So if you NC should refuse to boot or bootloops, which I hope won't, flash this boot repair that I'm adding just in case. Just flash it, no need for formatting.. Use a bootable CWR SD Card.
HCext4-boot-repair flashable zip: http://www.multiupload.com/LN64D4RXEY
6.8 MB
cf963da4043d91d7f4bf8f784cd02d95 HCext4-boot-repair.zip
Mirrors are welcome.
Do not use this internal 3.0.0.6 CWR to flash Froyo or Eclair, use previous Ext3 Bootable CWR 3.0.0.5 sdcard and format system, data and cache before doing so. The Ext4 integrated CWR will only work for this HC version (not previous) and for CM7.
Click to expand...
Click to collapse
EDIT - 02/18/2011 ---
Google Calendar app fix:
Added Calendar.apk, CalendarProvider.apk, GoogleCalendarSyncAdapter.apk and new framework.jar(.zip) to attached files.
- All .apk files must be pushed to /system/app, with 6775 permissions.
- framwork.jar [rename by removing '.zip', this ISN'T a zip file] must be pushed to system/framework, replacing current file.
Note: Simple fix, Added "SyncStateContentProviderHelper.java (smali)" to 'com/android/internal/content', in framework.jar.
I'm sorry, I don't have time to make a flashable zip of this just yet. Maybe a good Samaritan will..
This hasn't been tested on other NC's than mine. Please try and post your feedback.
Feel free to use this in other HC/Gapps threads, so that everyone can benefit from this.
-----------------
Click to expand...
Click to collapse
Note: 30.03.11
These packages (zip) can't make it complicated for you to go back to other roms, with working recoveries, etc.
Please flash the file found on this post before flashing another rom, if you wish to use, for example, CM7.
Sam
Welcome Back
Mediafire mirror:
http://www.mediafire.com/?a307d9un2cg8y36
Mediafire Nook Folder, includes "most" needed files:
http://www.mediafire.com/?aaqb74f9po8f9
Click to expand...
Click to collapse
Welcome back and anxiously awaiting your hard work!
Will the sdcard mount on this build?
wow so in on this.
as soon as some non newbs test it out
Just tested it (from a fresh 1.0.1 install of eclair and using the market CWR), works flawlessly. (Just be patient with the CWR, it takes awhile and theres nothing indicating wether it froze or not so wait at least 10minutes before thinking it failed). SD card mounted flawlessly and Pandora/Youtube work fine. You're also given an option to use LauncherPro or the HC launcher at boot.
Thanks Sam
P.S. for those who prefer the default launcher like myself I suggest you open up spare parts and set Window Animations and Transition Animations to instant.
So why does this have to mess with cwr?
Thanks for your work here
This will not override our CWR and in case there is a problem we shouldn't have a problem getting back into it to recover our backups, correct?
Any idea if Rom Manager will work okay with this?
This will erase internal CWR.
You would be better off with some sort of backup SDcard with Monster's image. Tha way you keep a working CWR with your backups all in the same place..
Backups are stored on the sdcard. This only erases internal boot, system and data.
I wouldn't count on CWR/Rom manager with HC just yet..
Sorry.
Just buy a rescue SD. That's my advice to you..
Sam
Sent from my LogicPD Zoom2 using Tapatalk
Amazing! This runs exceptionally well, thank you so much!!
samuelhalff said:
This will erase internal CWR.
You would be better off with some sort of backup SDcard with Monster's image. Tha way you keep a working CWR with your backups all in the same place..
Backups are stored on the sdcard. This only erases internal boot, system and data.
I wouldn't count on CWR/Rom manager with HC just yet..
Sorry.
Just buy a rescue SD. That's my advice to you..
Sam
Sent from my LogicPD Zoom2 using Tapatalk
Click to expand...
Click to collapse
Awesome thanks. I can't wait to try this later.
YOU are THE
Man,
Samuel, you have made owning this thing so much fun.
Great Job dude!
Having a minor issue here,When I download an app in the market, it's is starting download, and thats all.
I'm not sure if this issue is a problem with Deeper-blue's image or installing it to the eMMC but for some reason the market alongside adb install give errors saying "INSTALL_FAILED_INSUFFICENT_STORAGE" Despite having 786MB available. If anyone has any ideas please post
Stop Google Framework and clear cache. Stop market and clear cache. Re-boot. That should clear it up.
I was just about to flash nookie froyo zip, but my real dream seems to have come true. Nook Color with flashable honeycomb already. Speechless. All I can say THANK YOU. So happy I got this device.
My youtube app plays about 1 second of the vid sound and then crashes.. never shows the video
Wow - This is really sick / installed beautifully / Market looks like it doesn't download (yet) / gotta install some basics / like astro to get some apps back / guess i'll try adb...
Mediafire mirror:
http://www.mediafire.com/?a307d9un2cg8y36
Mediafire Nook Folder, includes "most" needed files:
http://www.mediafire.com/?aaqb74f9po8f9
The nook color has some truly incredible developers, thanks for all your work guys.
Related
THIS UTILITY IS FOR FASCINATE TOUCHWIZ FROYO/GINGERBREAD ONLY
UPDATED FOR EC09 GINGERBREAD
I have created a format utility that can be used from within CWM3 recovery. Just select the ZIP in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
--------
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4, then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
--------
Packages updated: 6/28/2011 - 12:57PM EST
EXT4 Format ALL (formats everything): http://www.mediafire.com/?6hx7f8g7c8vv6xz
EXT4 Format CACHE: http://www.mediafire.com/?2621a888ydv41mg
EXT4 Format DATA: http://www.mediafire.com/?ck2bb340yybpe4z
EXT4 Format DBDATA: http://www.mediafire.com/?ahxzs8xsyyvemed
EXT4 Format FOTA: http://www.mediafire.com/?42ijpi67grdb6mm
EXT4 Format PREINSTALL: http://www.mediafire.com/?d42as1l3pdbhr2t
EXT4 Format SYSTEM: http://www.mediafire.com/?rgs46hhq8qd951t
--------------------
If you like my work, consider donating, or thanking me by clicking the thanks button
thanks for this
navenedrob said:
I have created two format utilities that can be used from within CWM3 recovery. Just select the type of file system you want to use, select it in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with either RFS or EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4 or RFS (depending on script used), then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
Click to expand...
Click to collapse
Ok, I think I'm having a complete idiot moment here so please be patient with me. What would be the benefits of me running this on my device that is currently running jt's CM7 with OTB 1.5 kernel and EXT4 (voodoo for those who don't know) already converted? Thanks in advance.
It would be of no use. Unless you need to format your entire device.
So this would be a good thing to flash in place of wiping between rom flashes? Does it have any benefits compared to a regular data and cache wipe when you are already converted to ext4?
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
navenedrob said:
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
Click to expand...
Click to collapse
Ok, so basically what you are saying is this would be ideal to use instead of data/cache/dalvik wipe for rfs to rfs and ext4 to ext4, correct? Thanks in advance.
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
navenedrob said:
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
Click to expand...
Click to collapse
Just to let you know, I ran the ext4 package and I got some serious lag issues after I installed my rom and it actually starting going into a soft boot loop. It began to act very weird and unstable. I booted back into recovery and I wiped everything the way I usually do and formatted the system/data/dbdata/cache manually in mounts and storage and reinstalled. It's better than it was but it still seems like it is kinda slower and more laggier than it was before I ran the package. Any ideas? Thanks man.
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
navenedrob said:
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
Click to expand...
Click to collapse
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Not really sure exactly, it actually could have been a few different things causing the "issues". I'm going to try your exact scenario and see what happens.
kidserious said:
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Click to expand...
Click to collapse
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Coreyc1123 said:
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Click to expand...
Click to collapse
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
kidserious said:
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I had these same symptoms one time that I installed kasonate v7, but after reflashing, the next time it didnt.
I know you're not talking about the same cm version, but they might be related and not related to the format utility.
Ok, I ran this package again to make sure that I didn't do something wrong and to see if I would get the same results. I ran the package, flashed cm7 then gapps then OTB GB 1.5. all from the recommended recovery in your post. Again I ended up in a soft boot loop and wifi was acting up again and was causing a boot loop. So once again I booted into recovery and wiped data/cache/dalvik normally and formatted manually via mounts and storage and reinstalled again and she's running like a dream. Very weird but I must say I am very happy with the results I ended up with, regardless of how I got them. So obviously, this was not your intention for it to be done this way but I do see an improvement in responsiveness, speed and memory being freed up. Before, my free internal memory was 1.49 and now it is 1.52. Thank you sir, I appreciate this.
Thanks for this utility! Works great. Went from Jt's cm7 to the miui/touchwiz rom and ran the utility in between. My phone is running faster than ever and no issues. Thanks again!
Sent from my SCH-I500 using XDA App
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
stephenj37826 said:
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You're welcome, the utility enables a few nice options as far as file system performance is concerned, that Voodoo doesn't at this time.
Do tell oh and thanks a million
Sent from my SCH-I500 using XDA App
Hello everyone i have just bought a droid eris to pass my time until septemeber/october. it should be stock android 1.5/1.6. I wanted to know how to go about installing this rom? i read this is one of the most stable and reliable which is what i want. I know the basics of how to flash as per the sticky and youtube videos, but was wondering if there's any guide specific to CELB froyo from stock? Thank you in advance!
You should be able to just use the One Click Root app by Jcase from the Market to root the phone (follow all of the rebooting instructions) and just flash the rom like normal. It's been a little while since I tried CELB, but I don't remember doing anything else.
Flash the ROM and flash the google apps as well, make sure to use the verison of GAPPS listed in his thread and not one of the newer gingerbread ones.
how do you go about installing gapps? put on root of sd card then..? also, do i have to first flash the root-me.zip or can i replace that with the CELB froyo rom?
manchintz said:
how do you go about installing gapps? put on root of sd card then..? also, do i have to first flash the root-me.zip or can i replace that with the CELB froyo rom?
Click to expand...
Click to collapse
The Q&A and stickys on top here has very detailed steps, please take time to read & follow it closely - also, if you go to the Wiki on the top & follow it, there's an entire section dedicated to the Eris, everything you'll need and tools/links on what & where to find/download.
Yes, select the correct Gapps - it should have a *mdpi* strings in the filename as you do NOT want to use the *gb* file as your gapps - and yes, it go on the root of the sd card. I find it very helpful & useful to start with a clean & freshly FAT32 formatted SD card, 8 MB microSD will do just fine (and, if in a pinch, go with a 4 MB card).
To do things right, flash the root-me.zip first and make sure the phone rebooted properly, and is running - you should not have to reactivate the device or update the PRL (by doing a *22891)
After you confirmed that the phone's been rooted, proceed with the CELB rom loaded on the SD card - but only after you do a NAND backup, just in case - then, flash gapps - and reboot the phone, be patient as it could take 5 to 10 minutes to boot up the new ROM for the 1st. time - and when you see the Welcome Screen with the Android, you are ready to setup & customize the phone. Do it slow & take your time - AND, make sure your battery is fully charged. Have fun & good luck !
manchintz said:
how do you go about installing gapps? put on root of sd card then..? also, do i have to first flash the root-me.zip or can i replace that with the CELB froyo rom?
Click to expand...
Click to collapse
Actually, as long as you have Amon_RA recovery running, there is no reason to flash rootme.zip first. That's intended only for the stock Eris build, to give you the apps and settings that you need to allow apps that require root-level access to run. CELB has all of that built-in.
The CELB thread has a location that shows where to download a zip file that includes the Google apps. So, the flash procedure, in a nutshell, would be:
- copy the CELB and gapps zip files to your SD card
- restart in Recovery
- Backup/Restore menu
- Nandroid backup (just in case...)
- back to the main menu, then to the Wipe menu
- Wipe data/factory reset
- Wipe Dalvik cache
- Back to the main menu, then to the Flash a zip from SD card menu
- choose the CELB zip file from the list
- Back to the Flash a zip from SD card menu
- choose the gapps zip file
- restart the phone
everything worked out, except now, it's not recognizing my 8gb sd card? what is going on??
It recognizes my 1gb micro sd, but not the 8gb microsdhc i originaly used to root it in the first place..help?
all is good! thank you all
MAJOR UPDATE 2/22/12: While the process hasn't changed too much, the key files have all been replaced for greater flexibility, and they are NOT compatible with the old method using rookie1's prep-dualboot zip. See this post for an update path from the old method to the current one.
This guide details how to repartition your internal storage and install two operating systems, or ROMs, side by side. If you're looking for a SD install that leaves the Nook's main storage untouched, you're in the wrong place (see my sig).
This guide takes advantage of the multiboot functionality built-in to CM7.1 nightlies since about #140. As such, it is not compatible with CM7.0.x builds or with earlier boot menus.
What you'll get: Whatever two ROMs you install, each will have a nearly 2GB /data partition for apps and they will share a nearly 2GB /media partition for storage, and both will have access to the SD card for more storage. At startup you will see either a small green bar labeled "CyanogenMod," or the word "cyanoboot" in blue. Both boot menus work the same:
Do nothing, and your primary system will boot
Hold down both volume buttons, and your alternate system will boot
Hold down 'n' for a more detailed boot menu
Hold 'n'+power and recovery will boot (if you installed CWM internally).
All of these actions must be taken in the first couple seconds, before a "loading" message appears below the logo. Once you see a confirmation message, you can release all buttons.
DISCLAIMER: As usual, YOU are responsible for changes YOU make to YOUR device. This process is intermediate difficulty level. It probably shouldn't be the first thing you've ever done with ClockworkMod Recovery, and you probably shouldn't just follow the steps if you don't understand them. If you don't know how your NC is currently partitioned, turn back now. If you want to preserve your warranty, turn back now. Here be serpents; be so warned.
Following the guide as-is with all default options gets you a stock 1.4.1* install on secondary and a CM7 install on primary. I hope you can figure out what to substitute where for different results.
*I don't have access to a CWM-flashable 1.4.2 zip right now, but there are instructions for making one here.
The Guide
Prerequisites:
CWM on either SD or internal recovery (internal recommended)
Wi-Fi access
Materials:
repartitionDual2GBdata
BNpri2alt
reformatData
1.4.1-keep-CWM (IF you're not starting with an up-to-date stock install)
CM7.1+ OR MiRaGe's CM7.2 OR unofficial CM9 nightlies (w/ compatible gapps)
CM7 gapps(look near the bottom of the page)
Steps:
Put all materials in your SD card's root directory (DO NOT UNZIP).
Boot into CWM.
From CWM main menu, "backup and restore" and "backup."
From CWM main menu, "install zip from sdcard," and "choose zip from sdcard."
Choose the repartitionDual2GB file.
Reboot recovery. If you have internal CWM and no boot menu, you may need to use the rhythm method:
verygreen said:
hold nook N key and then press and hold power until the {first} message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the {first} message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long
Click to expand...
Click to collapse
Repeat step 4 and choose reformatData
If your backup in step 3 was stock, you can "backup and restore" then "restore" and skip to step 13.
Otherwise, repeat step 4 and choose 1.4.1-keep-CWM.
When it finishes, hold the power button to shut down, remove your CWM card (if applicable), and power back on.
Complete B&N registration process¹
Power off and boot back into CWM (may require rhythm method above).
Repeat step 4 and choose BNpri2alt.
From CWM main menu, in "mounts and storage," format system, data, and cache.
From CWM main menu, choose "Advanced" and "Wipe dalvik cache."
Repeat step 4 and choose CM7 update zip.²
Reboot into main partition and set up Wi-Fi.
Reboot into alt partition (hit both volume buttons at once on "CyanogenMod" loading screen) to make sure it's working.
optional: install gapps, keysmod, etc from CWM.
¹Any mods you want to make to stock, do it now: update to a newer version, root with Manual Nooter (if rooting 1.4.x firmware, follow the linked instructions but use MN 5.12.20), flash keysmod, overclock kernels, or anything else CWM-flashable.
²If you backed up an existing CM7/9 install in step 3, then after step 16 just install gapps, install keysmod if you want it, then from CWM's main menu, Backup & restore > Advanced Restore, and restore data only from your most recent backup. When you boot into CM7 (not tested with CM9), it will be just like you left it.³
³Steps 17 and 18 may look unnecessary, but several users experienced force closes in their CM7 installs when they didn't take these steps.
Other Resources:
CMpri2alt: Moves a CyanogenMod install from the primary partition set to the alternate partition set
BNalt2pri: Moves a stock install from the alternate partition set to the primary partition set
CMalt2pri: Moves a CyanogenMod install from the alternate partition set to the primary partition set
Revert dual boot: deletes the alternate partition set and alternate boot files. Does not restore stock partition sizes, but must be run prior to partitioning back to stock.
1.4.1 full restore: removes CWM from internal recovery, does not affect partitioning
1.4.1-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Steps to back up and/or update both partitions
Instructions to rename boot files created with j4mm3r's old multiboot
Possible fix for rooted stock boot-looping at 'n' screen on secondary
Credits:
repartitionDual2GB and reformatData provided by DeanGibson
1.4.1 zips provided by rajendra82
possible boot-loop fix provided by sryan1983
BNpri2alt, BNalt2pri, CMpri2alt and CMalt2pri are minor alterations of DeanGibson's files
revert-dualboot is a minor alteration of rookie1's remove-dualboot
Racks11479 provided key info for the above alterations
________________________________________________________
Old Resources (Do Not Use with Current Method):
prep-dualboot
froyo-to-dualboot
Remove dual boot: returns partitioning altered with prep-dualboot to stock (1GB/5GB, non-blue-dot)
1.2 full restore: removes CWM from internal recovery, does not affect partitioning
1.3-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Video documenting setup for a CM9 (Ice Cream Sandwich Alpha) dual boot with Nook Color stock 1.4.1
Old Credits:
1.2 full restore provided by nemith: thank here
prep dual boot and remove dual boot by rookie1: thank here
froyo-to-dualboot from jasoraso: thank here
1.4-to-alt from jasoraso: thank here
You can thank me with the button below, or if you feel real strongly about it, you can make a donation at my blog.
UPDATE 5/25/12: Removed the prerequisite for 1GB/5GB partitioning. A little bird named jicama confirmed that the newer partitioning script doesn't care if you start with a blue dot NC. Prep-dualboot would carve the alt partitions out of /media, which doesn't work if /media's not big enough. RepartitionDual just deletes the last three partitions (/system, /data and /media) and makes new partitions from the now-unallocated space, so as long as you have the right number of partitions, it doesn't matter how big they are.
Added to my Subscribed list !! ...Thank you
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
oppy said:
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
Click to expand...
Click to collapse
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7? Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Taosaur said:
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7?
Click to expand...
Click to collapse
Yes.
Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Click to expand...
Click to collapse
Okay, I'll do that and post results. Thanks.
EDIT: Looks like that did it. Seems to work fine, other than some app FCs, which, from what I've read, are fairly common. Thanks for the assist!
I worked that info into the OP. I've done this process twice now without taking those steps and without getting FCs, but you're not the first to report them.
I was a bit confused about the backup and restore part also. Seeing as my Nook was stock to start, I probably didn't need to do that step, and might have actually caused a problem or two by restoring data that didn't exist to start.
Still working great. The only FCs I've had so far were while trying to run Facebook.
Excellent guide! Thanks for all the work on this, it works great.
This is an awesome guide. Thanks for the help. I've been wanting to do this for a while.
Thanks man.
I appreciate you putting all the tools in one place, and I especially appreciate you posting that us blue dot people needed to repartition to 1gb data before doing this; I should've figured that, but I didn't for some reason.
Moving 1.3 to the dual boot partition as I type
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
SCrid2000 said:
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
Click to expand...
Click to collapse
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Taosaur said:
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Click to expand...
Click to collapse
Thanks man. That's what I figured.
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
This is the best thing EVER. I got sick of the nook app on my CM7 build, so this worked flawlessly.
I am running the CM7.1.0 RC1 build, and everything runs smooth as silk
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3. You would have to use j4mm3r's multiboot and the matching stock-to-secondary file found in this thread: http://forum.xda-developers.com/showthread.php?t=1156909
Nevermind, dumb question.
Updated with a link to CM7.1 stable
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
TomMelee said:
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
Click to expand...
Click to collapse
I'll just leave these here:
Taosaur said:
this guide is not compatible with CM 7.0.x sta(b)le releases, nor branch ROMs based on those builds
Click to expand...
Click to collapse
Taosaur said:
Phiremod 7+
Click to expand...
Click to collapse
Taosaur said:
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3.
Click to expand...
Click to collapse
Try installing regular CM 7.1.
rabi347 said:
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
Click to expand...
Click to collapse
Sounds like you got close. I would say start over at step 5.
Hello NookPeeps!
TRIPLE-BOOT your nook color with Stock on EMMC and Dualboot CM7/CM9 on your SDcard!!
________________________________________________________________________________
Update 5/4/12: Flashable zip update for Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL. See second post for more info. ________________________________________________________________________________
Update 3/26/12: Flashable zip update for Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL / MIUI GB & ICS. See second post for more info.
________________________________________________________________________________
Update 3/6/12: Flashable zip update for Mirage CM7.2 / ICS CM9. See second post for more info.
________________________________________________________________________________
Update 3/4/12: Seems we're still having some issues with the Mirage/ICS image being uploaded to the server. I've removed it from the techerrata server for the time being. Please download the file from the 4shared and Wupload links I posted at the bottom of this post. Sorry for all the trouble.
________________________________________________________________________________
Update 3/2/12: New flashable zips for Mirage CM7.2 / ICS CM9 / MIUI 2.2.4. All downloads will now be hosted on the TeamWin Techerrata server. Links are now at the bottom of this post. For info on the updates, please see second post.
________________________________________________________________________________
Update 2/19/12: New flashable zip for MIUI 2.2.3 and update for my DualbootSD CWM Recovery (nandroid capable!). See second post for download and instructions.
________________________________________________________________________________
Update 2/17/12: New flashable zip update for ICS w/ Cornerstone by OnSkreen v2. See second post for download and instructions.
________________________________________________________________________________
Update 2/2/12: New flashable zip updates for Mirage and ICS. See second post for download and instructions.
________________________________________________________________________________
Update 1/27/12: Updated OP with working download links. Please let me know when a link goes down so I can reup. Big thanks to user "terra-starr" for hosting on his dropbox account.
________________________________________________________________________________
Update 1/19/12: New flashable zip update built this morning. See second post for download and instructions.
________________________________________________________________________________
Update 1/17/12: Gapps Calendar, Email and TTS Fix. See second post for download and instructions.
________________________________________________________________________________
Well it's been a while since I've updated my DualbootSD thread. But since things are much bigger and better now with CM7 and CM9. Figured I'll prep a new IMG file that you can dualboot Mirage CM7 Kang and the latest greatest ICS CM9 off one SDcard. I did this because I do love ICS but still have the need to go back to CM7 for my own personal reasons, but figured I'd share it with everyone as well.
1-I've prepped the image file to be 3.7gb, so that no one will have issue's burning it to a 4gb SDcard or larger.
2-Both roms share the same SDcard partition. So on a 4gb card, the available space is limited to 1.4gb.
3-If you use an 8gb SDcard. To get use of the remaining storage on your SDcard. Just burn the image and then use EASUS Partition Manager to extend the SDcard partition. (Which is the 7th partition on the card)
4-Primary boot is Mirage CM7 Kang from his 01/13/2012 build (uImage/uRamdisk)
-V6 SuperCharger by zeppelinrox included (read below on how to install)
5-Secondary boot is ICS CM9 was built on 01/14/2012 with the following additions (uAltRam/uAltImg):
-Added telephony-permissions-fix by Samiam303 to allow phone specific apps to show in market
-Added bootanimation fix by Homer_S_XDA (make sure you thank him)
-Make sure you thank Samiam303 for posting the zips on his thread here
6-Gapps included but not baked into the rom, read below to find out how to install
7-This .img also includes a modded CWM Recovery that only works with .zips from this thread. Do not use it to flash with anything else besides .zips prepped by me for this thread!
Please follow below instructions completely before posting issues!
___________________________________________________________________________________
1-Download the .zip at the bottom of this post
2-Follow the same directions as you would burn a NookieFroyo SDcard from NookDevs.com here.
3-After you burn the card, plug the SDcard into your nook and power on. Leave it alone and it will boot to the primary boot which is Mirage CM7 Kang and connect to a wifi connection.
4-Power off nook or reboot and boot to secondary boot which is ICS CM9 by holding down the volup+voldown together during boot and it should boot up Alternate Boot which is (uAltImg/uAltRam)
5-Once booted to ICS CM9, again connect to a wifi and then power off.
6-Now power on nook again and this time hold down the button to get to the boot menu and choose SD Boot --> uRecImg/uRecRam.
7-Choose to 'Install zip from SDcard --> Choose zip from SDcard --> Now choose, gapps-GB-20110828-signed-DualbootSD.zip. Once that's completed now choose, gapps-ICS-20111125-2-DualbootSD.zip
8-After you're done flashing both Gapps, now you're ready to boot into your roms and sign into market. I don't think I need to go any further explaining how to do so.
9-Optional, but if you want to supercharge your Mirage CM7 Kang with the V6 SuperCharger Script by zeppelinrox. All you have to do is boot the Mirage and start up Terminal Emulator and do the following:
- su
- cd /sdcard
- sh V6*
- choose option 0 (fastest scroll)
- choose 9
- choose option 16 to reboot
10-Please be patient with your roms. Give it a minute or two on first boot. It also depends on what brand and class of SDcard you have. I've tested it on both a Sandisk 8gb Class 4, as well as a PNY 4gb Class 2. The roms ran much better on the Sandisk than it did on the PNY card. Read this thread by Blue6IX for more info on SDcard read/write speeds.
11-Oh for the ones that are gonna take this image and start selling it on Ebay as well as N2A, you guys suck!! But to each his own I guess.
12-And finally enjoy your DualbootSD roms!! Now you can triple-boot your nook!
Take it or leave it, just hope you enjoy it.
Thanks to all the devs for all their hard work in getting these great ROMs for our Nook Color.
Credits:
Fattire and the CyanogenMod Team
Koush(for his CWM Recovery)
Samiam303
Mrg666 (for Mirage CM7 Kang)
Homer_S_XDA (for the bootanim fix)
zeppelinrox (for the V6 SuperCharger Script)
Hockeyfamily737 (for MIUI v2.2.4)
TeamWin (for graciously allowing me to my files with them)
If I'm forgetting someone, please let me know!
Download:
You can now find all my downloads on the TeamWin techeratta server. Thanks eyeballer & kevank! All roms are categorized into their own folders. All zips should be in sequential order by date. Their is also a miscellaneous folder which contains all other optional zips that you would like to flash.
http://techerrata.com/browse/nook/racks
Click to expand...
Click to collapse
If I've helped in some way, please say thanks in one way or another!
Thanks,
Racks
Update 5/4/12
_________________
Flashable zip for Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL
-Mirage CM7.2-RC1 latest build 4-16-2012. (Primary boot)
-ICS CM9 non-OpenGL & OpenGL builds. 5-1-2012. (Secondary boot) Thanks again to eyeballer for letting me use his build for our dualbootSD.
-Remember to flash gapps after flashing the roms.
-Download the zip and place it on the SDcard partition of your DualbootSD rom
-Everyone should know how to flash by this point. If not, you should continue reading.
-After done flashing, reboot and you should be good to go!
-FYI: I'll try to update with flashable zips when ever I have time. But for now.. I've written a tool that will convert any standard rom zips for my DualbootSD. Check out the "Convert2Dualboot-SD Tool" thread HERE for more info!! Good luck and happy flashing!
______________________________________________________________________________________________
Update 3/26/12
_________________
Flashable zip for Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL / MIUI GB & ICS
-Mirage & MIUI flashable zips will flash to primary boot. Only ICS CM9 will flash to secondary.
-Mirage CM7.2-RC1 latest build 3-23-2012. (Primary boot)
-MIUI Gingerbread 2.3.9 & ICS Alpha v4 MIUI 2.3.9 (Primary boot)
-ICS CM9 non-OpenGL & OpenGL builds. 3-25-2012. (Secondary boot) Thanks again to eyeballer for letting me use his build for our dualbootSD.
-Remember to flash gapps after flashing the roms.
-Download the zip and place it on the SDcard partition of your DualbootSD rom
-Everyone should know how to flash by this point. If not, you should continue reading.
-After done flashing, reboot and you should be good to go!
-If after flashing a rom and it gets all wonky you might want to go ahead and try using an app like Titanium Backup and backup all your apps. Then boot into the CWM for DualbootSD that is included with the DualbootSD image and got to "mounts and storage" and choose to format either /system1 & /data1 for primary boot or /system2 & /data2 for secondary boot. And then flash the update zips that you have just downloaded and see if it makes any difference.
______________________________________________________________________________________________
Update 3/6/12
_________________
Flashable zip for Mirage CM7.2 / ICS CM9
-Mirage CM7.2 latest build 3-4-2012. It says 3-5-2012 because that's the date when it was prepped for dualbootSD.
-ICS CM9 non-OpenGL build. 3-5-2012. OpenGL is broken at the moment. You'll find it much smoother with OpenGL disabled though. But no flash. Thanks again to eyeballer for letting me use his build for our dualbootSD.
-Remember to flash gapps after flashing the roms.
-Download the zip and place it on the SDcard partition of your DualbootSD rom
-Everyone should know how to flash by this point. If not, you should continue reading.
-After done flashing, reboot and you should be good to go!
______________________________________________________________________________________________
Update 3/2/12
_________________
Flashable zip for Mirage CM7.2 / ICS CM9 / MIUI v2.2.24
-First off I want to thank TeamWin, specifically Eyeballer & Kevank for setting me up with their server to host my files. Everything will be in much better order now! Thanks guys!
-Mirage CM7.2 update 3-1-2012. More info here.
-ICS CM9 OpenGL update 3-1-2012. My repo is full of changes uncommited at the moment. So eyeballer was nice enough for me to use his build.
-MIUI v2.2.24. Thanks to hockeyfamily for allowing me to prep this for my dualbootSD. This will install in the primary boot. So it will replace your current Mirage build. It is also recommended that you perform a full wipe when going from one rom to the next. You can do so by booting into the CWM that is included with the dualbootSD and go to "mounts and storage" and choose to format "/system1" "/data1". Remember to also wipe cache.
-For MIUI v2.2.24, after flashing. Make sure you download and flash "gapps-MIUI-v2.2.24-20111125-DualbootSD.zip"
-Gapps ICS 2-24-2012 are borked for some reason. I will reupload when I figure out what's going on.
-There's also a flashable zip for the new CM9 bootanimation in the miscellaneous folder if you want to flash that after flashing the rom.
-Download the zip and place it on the SDcard partition of your DualbootSD rom
-Everyone should know how to flash by this point. If not, you should continue reading.
-After done flashing, reboot and you should be good to go!
______________________________________________________________________________________________
Update 2/19/12
_________________
Flashable zip for MIUI 2.2.3
1. MIUI 2.2.3 updated by 'hockeyfamily737'. This zip will replace your first boot rom on your DualbootSD. Which would be your CM7 rom. See more info here about MIUI 2.2.3.
2. If after flashing you find it unstable and since this is a completely new rom, I would recommend when booting into the DualbootSD CWM Recovery, go to 'Mounts and Storage' and choose to format '/data1' before flashing. You might not have to, and although MIUI is based off CM7. I'm not sure how it will affect your system without doing so.
3. Remember to flash the CM7 gapps that was included w/ your dualbootSD as well.
DualbootSD CWM Recovery Update v2:
1. You can now perform a full Nandroid backup of your DualbootSD, if you have the room to do so of course.
2. Unfortunately, when doing a Nandroid backup, it will backup both roms. I haven't edited the code to give you the option of which rom to backup yet. Maybe sometime in the future.
3. You can now choose which system you would like to wipe dalvik-cache for.
4. Restore only the /system you choose to by performing an 'Advance Restore' in the CWM menu
5. I will work on specific nandroid backups as well as fix permissions on next release.
-Download the zip and place it on the SDcard partition of your DualbootSD rom
-You should know how to flash by now.
-After done flashing, reboot and you should be good to go!
Download:
Update-Encore_MIUI_2.2.3_DualbootSD_02192012.zip
MD5: d47de4896f2df81832b1462616701a3c
4shared
CWM-DualbootSD_v2-Nandroid-Capable.zip
MD5: 01b46e85f7b5e8f35b32a0f3a5070dc7
4shared
Click to expand...
Click to collapse
______________________________________________________________________________________________
Update 2/17/12
_________________
Flashable zip for CM9 ICS w/ Cornerstone by OnSkreen v2.
-Baked in Cornerstone by OnSkreen! This is just a beta test. So if you want something stable, do not flash this! But if you want to test out what else would be possible for our Nook Color, go ahead and flash!
-Got alot more to work out before it's fully functional, but it works!
-Fixed phone UI layout. Now tablet UI layouts correctly. Thanks hacdan for the help.
-Check this post for screenshots and bug reports.
-Remember to flash the gapps as well.
-Remember to flash the calendar, email, tts syncing fix.
-Download the zip and place it on the SDcard partition of your DualbootSD rom
-Follow same directions as below for flashing.
-After done flashing, reboot and you should be good to go!
Download:
Update-Encore_CM9_DualbootSD_02132012_OnSkreen_v2.zip
MD5: 35042448b8c3ff6a837ddf133562c2dd
4shared
Click to expand...
Click to collapse
______________________________________________________________________________________________
Update 2/2/12
_________________
Flashable zips for Mirage build "MiRaGe-02012012" and CM9 ICS which was built this morning for you flashaholics out there.
-See MiRaGe thread for info on the latest update here.
-For ICS, I went ahead and included the updated SGX drivers as per Fattire's post here. Remember this is experimental!!
-For ICS don't forget after flashing gapps to flash the calendar, email, tts syncing fix from below as well.
-Download the zip and place it on the SDcard partition of your DualbootSD rom
-Follow same directions as below for flashing.
-After done flashing, reboot and you should be good to go!
Download:
Update-Mirage_CM7_DualbootSD_02012012.zip
MD5: 3800a7702cb540feb1153d20f471e9d3
4shared | Dropbox
Click to expand...
Click to collapse
Update-Encore_CM9_DualbootSD_02012012.zip
MD5: bf49f76849740cb0f78883017cc430b0
4shared | Dropbox
Click to expand...
Click to collapse
______________________________________________________________________________________________
Update 1/19/12
_________________
Here's a flashable zip built this morning for you flashaholics out there.
-This includes the fix for multi-touch to function properly by keyodi.
-You might have to reflash gapps as well as the calendar, email, tts syncing fix from below.
-Download the zip and place it on the SDcard partition of your DualbootSD rom
-Boot to the Modded CWM Recovery that is included with the DualbootSD by choosing SD Boot --> uRecImg/uRecRam from the boot menu.
-Choose 'Install zip from SDcard' --> Choose zip from sdcard --> Update-Encore_CM9_DualbootSD_01192012.zip
-If you have the gapps*.zip and the calendar-email-tts-fix*.zip. Go ahead and flash it now.
-After done flashing, reboot and you should be good to go!
Download:
Update-Encore_CM9_DualbootSD_01192012.zip
MD5: 3f791ce4d8680e3334feb3bb5be014e7 (I had the incorrect md5 listed before. Thanks 'Michigeezer' for pointing it out to me! )
Wupload | Fileserve | Dropbox
Click to expand...
Click to collapse
______________________________________________________________________________________________
Update 1/17/12
_________________
I wasn't aware there was a fix for the Calendar and Email syncing issues until it was brought up to me by webdroidmt here. So I went ahead and prepped a flashable .zip for the fix.
-Download the zip and place it on the SDcard partition of your DualbootSD rom
-Boot to the Modded CWM Recovery that is included with the DualbootSD by choosing SD Boot --> uRecImg/uRecRam from the boot menu.
-Choose 'Install zip from SDcard' --> Choose zip from sdcard --> gapps-ics-calendar-email-tts-fix-DualbootSD.zip
-After done flashing, reboot and you should be good to go!
Download:
gapps-ics-calendar-email-tts-fix-DualbootSD.zip
MD5: 68e57b1b716657d385e350dee3f3b147
Wupload | Fileserve | Depositfiles | Dropbox | 4shared
Click to expand...
Click to collapse
______________________________________________________________________________________________
Reserved! Finally I've reserved the second post on my own thread!!
Well I don't plan on updating the roms often unless there are some major changes that calls for it. And I've made it simple for everyone to do so once that day comes. As I stated in the OP this .img comes with a modded CWM Recovery that is meant only for .zips that are prepped for this thread!
So I will be prepping update.zips when the day calls for it. Till then please enjoy your DualbootSD roms! And please keep issues with the DualbootSD in this DualbootSD thread and not clog up the other threads. I'll try and post known issues as the days go by.
Thanks again!
-Racks
Hey Racks. It says on your post that this dualboot is for the sdcard. How about for eMMC? Any chance for that? Thanks and awesome work, man.
quick hints
volup+voldown together during boot should get you to the altboot automatically without having to go through any menu. (Not that I don't love the menu!)
Nook Color Tweaks should allow you to set a default boot configuration.
fattire said:
bolup+voldown together during boot should get you to the altboot automatically without having to go through any menu. (Not that I don't love the menu!)
Nook Color Tweaks should allow you to set a default boot configuration.
Click to expand...
Click to collapse
Huh, didn't know that?!
I've edited my OP with you're tip.
Fattire always the gentleman and always willing to lend a helping hand to make our lives that much easier.
Hats off to you sir for all that you've done for us NookPeeps!
-Racks
Wow, great timing racks I was just looking for a way to experiment with CM9 without losing CM7. This saves me having to switch cards (which I would invariably lose altogether). I guess it only works with your prepped CM7/9 builds though? Not that it matters, just making sure I understand correctly.
mtr33 said:
Wow, great timing racks I was just looking for a way to experiment with CM9 without losing CM7. This saves me having to switch cards (which I would invariably lose altogether). I guess it only works with your prepped CM7/9 builds though? Not that it matters, just making sure I understand correctly.
Click to expand...
Click to collapse
This is a prepped .img file with CM7/CM9 on it. If there are any updates. Only use the .zips from this thread because not only CWM Recovery has been modded to work only with the dualboot card. The zips itself needs to be modified to flash correctly. As well as modified ramdisk, fstab.... etc. to boot and work correctly with the DualbootSDcard.
But you could always use TitaniumBackup and backup all your apps and restore it to the Dualboot card if you wished. It should work. Haven't tried it myself though.
Good luck!
Racks
Should the gapps be included as part of the SD image? When I attempt to install update from SD, I am getting a No files found. message.
Thanks for this image. This is awesome!
---------- Post added at 02:09 AM ---------- Previous post was at 02:06 AM ----------
Sorry, please ignore. I did not correctly boot via SD. My bad
Thanks again!
Thanks Rack, I'll give it a try soon.
Is CM9 the prebuilt one or your own compiled?
P.S: Thanks for posting on G+. Don't check these forums much
AidenM said:
Is CM9 the prebuilt one or your own compiled?
P.S: Thanks for posting on G+. Don't check these forums much
Click to expand...
Click to collapse
Compiled. Since the last prebuilt (sneakpeakfullofbugs2.zip) was from much earlier than 1/14/12.
-Racks
I bet I was one of the first to download your ROMS at a little after 10 last night. My husband is probably mad at you and me, since I played with my NC until after 2 am!
This is SO COOL! This takes me back to my first experience with Android, which was running Donut from an SD card in my old HTC Touch. Your ROMS are much faster, but so is the NC.
The file installs really easily to a uSD card. I have a bunch of cl 2 and cl 4 SD cards. None of them benchmark very fast, so I used a SanDisk Cl 4 8GB card that benches at .60, using the testing method in this thread. (Note, if you are using Crystal Disk Mark to test with, use 50MB file size and the 4k QD32 test for writing.) Mirage seems way faster than the NC's 1.3 software, which I am running blocking OTA updates.
I downloaded a bunch of the apps I use on my 3D EVO. I didn't try the Titanium Backup thing, as I doubt the app data would work from my phone, which is running a rooted Stock (Sense) ROM.
It took me a minute to figure out how the changing of selections worked in recovery. Maybe it's standard for CWM, but I haven't ever run it, preferring Amon_RA and then TWERP. Use volume up and down keys to move up and down the list. Then hit the home key (Nook button) to change your selections.
I forgot to mention, though I did flash both gapps zips, (from recovery), at least on Mirage, I had to download Maps, GMail and others from the Market. I'm not sure if I missed a step or something.
I have run CM on my OG EVO, as well as my 3D EVO. I like it very much, but I also like some of the widgets in Sense. I'll have to get a calendar widget for my NC. I am using GOWeather for a weather and digital clock widget.
I have already thanked you on your first post, racks, but I thank you again. I hate to sound piggy, but is there any chance you could make up a zip that includes Miui? It's not my favorite ROM, and there are problems with the Market on the NC. But it would be fun to be able to switch back and forth and show it off to my friends that run Miui on their phones.
OK...I installed and everything is perfect. Thanks Racks
I previously had cm7 and cm9 (both latest nightlies)on two separate SDcards. Because of this, and that fact I didn't want a lot of duplicate files, I had all my media and Titanium Backup directories (cm7 and cm9 with different dir names)on my internal sdcard. My emmc is stock un-rooted NC 1.4.1.
So I burned the img on a SanDisk 8GB cl4 SDcard, expanded the sdcard partition and followed the install proceedures. When complete I downloaded Titainium Backup from the market, pointed it to the correct backup, and restored all my apps for each OS.
All worked great...
racks11479 said:
Compiled. Since the last prebuilt (sneakpeakfullofbugs2.zip) was from much earlier than 1/14/12.
-Racks
Click to expand...
Click to collapse
Cool.
Also, if I flash CWM from ROM Manager in one of the sd roms it will still flash to the emmc right?
Thanks.
smarcin said:
I bet I was one of the first to download your ROMS at a little after 10 last night. My husband is probably mad at you and me, since I played with my NC until after 2 am!........................
I have already thanked you on your first post, racks, but I thank you again. I hate to sound piggy, but is there any chance you could make up a zip that includes Miui? It's not my favorite ROM, and there are problems with the Market on the NC. But it would be fun to be able to switch back and forth and show it off to my friends that run Miui on their phones.
Click to expand...
Click to collapse
Hahaha, awesome. This is why I try to contribute what I can to this community. It's comments like these that makes it all worth while. Oh and I might (might being the keyword) prep an MIUI update zip for the dualboot card. It will probably replace the primary boot though. No ETA's yet.
bobshute said:
OK...I installed and everything is perfect. Thanks Racks ...........................
So I burned the img on a SanDisk 8GB cl4 SDcard, expanded the sdcard partition and followed the install proceedures. When complete I downloaded Titainium Backup from the market, pointed it to the correct backup, and restored all my apps for each OS.
All worked great...
Click to expand...
Click to collapse
Thank you sir for confirming that backing up and restoring with Titanium Backup worked without a hitch!
AidenM said:
Cool.
Also, if I flash CWM from ROM Manager in one of the sd roms it will still flash to the emmc right?
Thanks.
Click to expand...
Click to collapse
Yeah, I wouldn't do that though. I have no idea what will happen. But most likely it would just flash to emmc boot. Let me know what happens if you do happen to be brave and do so.
racks11479 said:
Hahaha, awesome. This is why I try to contribute what I can to this community. It's comments like these that makes it all worth while. Oh and I might (might being the keyword) prep an MIUI update zip for the dualboot card. It will probably replace the primary boot though. No ETA's yet.
Thank you sir for confirming that backing up and restoring with Titanium Backup worked without a hitch!
Yeah, I wouldn't do that though. I have no idea what will happen. But most likely it would just flash to emmc boot. Let me know what happens if you do happen to be brave and do so.
Click to expand...
Click to collapse
Ok. trying it now.
P.S Can i have your address? I'll give you a visit if it doesn't work
lol j/k thanks!
Edit
OK just flashed it and it booted!
AidenM said:
Ok. trying it now.
P.S Can i have your address? I'll give you a visit if it doesn't work
lol j/k thanks!
Edit
OK just flashed it and it booted!
Click to expand...
Click to collapse
Ok, so I guess you just flashed CWM Recovery to your EMMC then. Can you try booting to the uRecImg/uRecRam off the SDboot just to make sure it didn't replace the modded one I had there?
Thanks!
Racks
racks... is it possible to have dual boot in the emmc?
Tapatalkin' it from my rooted NookColor running CM7 MiRaGe [KANG] [7.2 RC] overclocked @ 1.2 GHz
racks11479 said:
Ok, so I guess you just flashed CWM Recovery to your EMMC then. Can you try booting to the uRecImg/uRecRam off the SDboot just to make sure it didn't replace the modded one I had there?
Thanks!
Racks
Click to expand...
Click to collapse
Yeps it booted fine.
les02jen17 said:
racks... is it possible to have dual boot in the emmc?
Tapatalkin' it from my rooted NookColor running CM7 MiRaGe [KANG] [7.2 RC] overclocked @ 1.2 GHz
Click to expand...
Click to collapse
It is possible, but someone has to prep the .zips to flash to the correct partitions. If someone wants to take a crack at it. Just download one of the .zips from rookie1's thread here. And take a look at the edify script, you would also need to modify the uRamdisk so it boots the correct /system as well.
Don't have time for that at the moment. Working on something else with another dev for you great people!
-Racks
[See post http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123 for the new version of this post with updated links/pointers to Succulent's recent CM10.1 builds as well as CWM/TWRP recovery tool compilation].
[Caveat emptor: adopt/follow this guide at your own risk].
I've been running CM10 build by XDA Developer Succulent version 12/08 on SD card since its release ten days ago, and its reliable/stable performance has crossed the threshold for me to finally take the plunge and install it internally on emmc.
FWIW, here the process I used to install CM10 internally on my 16GB Nook Tablet (i.e., on its emmc).
Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on SD card a Primary FAT32 partition, and set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows. If you are going to use this card for backing up your NT, keep in mind that each backup will require at least 600MB (for a barebone stock or CM config) and size the partition accordingly.
Obtain and copy to the SD card the following files:
MLO, u-boot.bin, and flashing_boot.img in SD_boot.zip obtained from http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/
either one of the two recovery program image files: cwm_6012_sd.img (ClockworkMod Recovery (aka CWM)) in CM9-10_CWM_v6.0.1.2_8-16gb_tools_sdcard.zip, or twrp_2220_sd.img (TeamWin Recovery Project (aka TWRP)) in CM9-10_TWRP_v2.2.2.0_8-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958, rename it to recovery.img. If you want to try out (or use) both, name your alternate choice altboot.img.
the file cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip from http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
the file gapps-jb-20121011-signed.zip from http://goo.im/gapps/gapps-jb-20121011-signed.zip
Put the SD card into the NT, and boot from its power off by inserting a powered USB cable. Press and hold the N button as soon as CyanoBoot comes up to get the boot menu to display.
Select either SDC Recovery (or Alternate Boot depending on which recovery tool you want to use).
Select Backup to backup your current NT config (/boot, /recovery, /system, and /data). Before proceeding to next step, see note (ii) near the end of this post.
Select Wipe data & factory reset.
Select install zip from SD card and install cm-10 zip file.
Select install zip from SD card and install gapps zip file.
Select power of and remove SD card from NT and power NT on again using the power button (alternatively you can just remove SD card and select reboot).
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored)
A few additional points worth noting:
Installing CM10 ROM and gapps will override your NT's BN-provided boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using backup process in step #5 above, safekeep the backup data on your PC/Laptop and better yet archive it on CD/DVD. Your media files in the NT media partition BN allocates for user should be intact.
To play it safe you should do the above in 2 phases: steps 1 through 5, then exit recovery and remove and mount SD card on PC to verify that backup data got newly created; then insert SD card and continue steps 6 through 9.
CWM and TWRP use different backup archive formats, so keep this in mind if you decide to switch. Furthermore, CWM has changed its archive format going from release 5.x to 6.x, so I think it would be prudent to save a copy of the recovery program together with the backup data it generated. (FWIW I prefer the tar/zip compatible backup data structure TWRP uses (which CWM 5.x had also used) over the BLOb structure which CWM 6.x use -- but YMMV).
To restore from backup data, boot into SD card and select from boot menu the same recovery program that was used to create the backup data, then select the particular backup dataset (indexed by date/time) you want to reinstall on your NT.
I would advise against blindly using other functions of the CWM and TWRP without looking up info and researching to understand what they really do.
See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
My thanks to all the developers who collective work created this wonderful ROM as well as the tools and info I made use of to install it. IMHO this ROM helps make the Nook Tablet one of the best-value tablets for the money (at least at the moment).
great post...fwiw here's my experience to get two NT16's up and running (I started with an old CM7 on both of them).
Backup nook with titanium backup on existing 32GB card.
Take screenshots for replacements
Reset nook to stock (1.4.2) and update to latest (1.4.3) with a fresh SD Card with repart.img copied to root (my red 2GB card):
http://raywaldo.com/2012/06/make-unbrick-repartition-image/
http://www.youtube.com/watch?v=Nu6e4m62tFc
c. 1.4.3 can be downloaded from B&N site directly. (http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/)
Create a CWM SD Card (ideally 4GB SanDisk) as per these instructions - http://raywaldo.com/2012/05/root-nook-tablet-with-cwm-sdcard/
Copy CM7 BETA and compatible GAPPS onto this card or another blank one. You can get the files from here: http://forum.xda-developers.com/showthread.php?t=1481826 and http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
Boot into this CWM Card, wipe data/wipe cache and dalvik cache. Install zip from sdcard (either current or pop in the new one). Choose cm-7 beta first, then gapps. Remove sd card. Reboot. Wait a while for it to set itself up.
Go into settings/applications and clear the cache for google market/play.
You now have CM7 installed and can setup the basics (google, wifi etc..)
Insert your 32GB (or 16 or 8 or whatever) Sandisk SD Card (it should ideally have the Titanium Backup folder from step 1, any media you want in Music and Movies folder and the CM10 and gapps zip in the downloads folder -- and that's it!)
Once mounted, download Goo Manager from the google play store and run it, accepting superuser requests.
Choose settings menu and "Install OpenRecoveryScript" and it should install openrecovery twrp recovery manager. Once it has installed and informed you of success, reboot into recovery (this is important), upon reboot hold the "n" and choose internal emmc recovery from the menu.
You will now find yourself in TWRP. From the install menu, add the CM10 PURE AOSP 4.1.2 JBV06.1-Hashcode and then the gapps-jb-20121011-signed.zip and swipe to confirm flash. This is it. Fingers Crossed!
NOTE: On one NT 16 (I have two), step 12 DID NOT WORK. It wouldn't install the CM10...zip -- and simply rebooted itself or hung...so I powered off, and rebooted to the CWM Card in #6..and used CWM to wipe caches etc… and then installed the two zips...and voila.
hope it helps.
digixmax said:
I've been running CM10 build by XDA Developer Succulent version 12/08 on SD card since its release ten days ago, and its reliable/stable performance has crossed the threshold for me to finally take the plunge and install it internally on emmc.
Click to expand...
Click to collapse
How do you feel about it now that you've installed it internally? I took the plunge as well today, but I'm not sure it's runs any better internally than it does from the sd card. Having said that, it runs so incredibly well from the card, so it's really hard to beat, but still... I'm actually having more issues with the internal install than the sd version.
I had had enough of the stock reader (that I'm actually pretty fond of) not remembering my place in sideloaded books, so I didn't feel I had anything to loose and am glad I made the install though. Installed once makes it easier to reinstall when an even better build comes along.
I made the switch since the stock ROM was so barebone and clumsy I virtually never use it since I had the NT, and the rooted stock ROM is just marginally better -- I found out there are so many apps I 've been using on CM10 that are simply not available for BN's (Android) Gingerbread. I also like the fact that I can now reboot (if ever needed) untethered.
I think performance-wise it runs about the same as it was running on SD, if it's better then it's not yet noticeable.
What kind of issues are you having with your new setup?
Some apps misbehaved. Didn't install properly or gave error messages. I decided to re flash and this this second install hasn't had any issues at all. Same files from the same card.
It is nice to have it internally and be able to switch sd cards should I want to.
Sent from my Barnes & Noble Nook Tablet using Tapatalk 2 and SwiftKey
I ran into a problem with v12/08: when I connect the NT to the PC I do not get the “USB connected” notification with option to “turn on the USB storage”, and thus cannot access neither the emmc media partition nor the sdcard. The problem exists with both CM10 running on emmc and running on sdcard. Furthermore when running on sdcard, hitting “storage” in “settings” results in a force-close of “settings”.
I am curious if anyone else has the same problem, or I am just missing some setup setting somewhere.
In the meantime, I am back to running another ROM off SD.
Those storage setting issue I had with the 1118 build but not with later ones. Connection to PC work fine but I don't think I need to do the turn on USB thing. No PC nearby at the moment
Edit: I am now near a PC, and I do get the "touch to turn on USB" or words to that effect. So it works as it should..
Sent from my Nook Tablet using Tapatalk 2 and SwiftKey
Thanks, I've tried reinstalling a couple of times (as well as installing a different ROM) without success.
I found the answer to my problem: I was used to getting the full-screen alert “USB mass storage” (upon insertion of tethered USB cable), and didn’t notice the tiny alert “USB connected” on the status bar (which when pulled down would in turn launch the “USB mass storage” alert).
Question: I'm not new to rooting and flashing, but am new to NT. I rooted my wifes NT, installed a launcher to switch back and forth, and loaded a few apps. I did not change the stock recovery and used a boot sdcard to run an older version of CWM. I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Sent from my SAMSUNG-SGH-I317 using xda premium
Dean1650 said:
Question: I'm not new to rooting and flashing, but am new to NT. I rooted my wifes NT, installed a launcher to switch back and forth, and loaded a few apps. I did not change the stock recovery and used a boot sdcard to run an older version of CWM. I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Cm7 is a gingerbread rom, it can be flashed by cwm 5 and 6 both. But cm10 is jellybean and must be flashed with cwm 6 only (or twrp) . And once you have cm7, you get cyanoboot (2nd bootloader) which is necessary to load cwm6, whether its internally flashed recovery or SD card recovery.
If you still have your bootable SD card, boot into recovery and check the version (cwm 5 most likely) , then do the longer, but simpler method - stock > cm7 > flash cwm6 internal and boot into it from cyanoboot > cm10.
I see the difference between the 2 methods..a few more questions. I dont see where or how recovery gets flashed in the first method. Looks like either/both are used but not flashed. In both methods, I dont see any sdcard additional partition requirements so can I assume everything can get copied to the boot partition? Haven't looked at the card I made yet, but if CWM is current enough for CM7 it should work fine. I appreciate this thread. It has cleared up a lot of questions.
Sent from my SAMSUNG-SGH-I317 using xda premium
Dean1650 said:
...
I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Click to expand...
Click to collapse
Yes, you can use this process to go directly from stock or rooted stock to CM10 -- I used it to go from rooted 1.4.3 directly to CM10. With SD-based flash, there is no need to go the circuitous multi-stage flashing process.
And if you use Succulent's CM10 builds from http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/ his ROM zip files all include emmc recovery so you don't even have to separately flash recovery as you would have with other ROMs. I think his approach, in addition to being convenient, has the benefit of avoiding intermediate states where there is potential incompatibility between ROM and recovery versions (which I think is conducive to causing bootloop).
Of course if for some reason you later prefer a different version of recovery than the one he includes (CWM 6.0.2.5) you can always reflash your particular choice of recovery by itself.
FWIW I am running Succulent's cm-10-20121225-acclaim-HD.zip (GCC 4.6) at the moment and it works great.
Dean1650 said:
I see the difference between the 2 methods..a few more questions. I dont see where or how recovery gets flashed in the first method. Looks like either/both are used but not flashed. In both methods, I dont see any sdcard additional partition requirements so can I assume everything can get copied to the boot partition? Haven't looked at the card I made yet, but if CWM is current enough for CM7 it should work fine. I appreciate this thread. It has cleared up a lot of questions.
Click to expand...
Click to collapse
Everything that gets flashed via recovery (either CWM or TWRP) comes in zip archive form, and this applies to ROM, gapps, as well as recovery itself. (If you ever want to flash recovery, the simplest way is to get a recovery zip file, such as one of those with keyword emmc from http://forum.xda-developers.com/showthread.php?t=1640958, and flash it from SD using the process in the first post, just as you would flash a ROM build or gapps).
If you are curious about what gets installed and where, just open (but don't extract) the to-be-flashed zip file (e.g., using winrar/winzip/7-zip): everything except the META-INF folder is what get installed, and the updater-script file in META-INF\com\google\android\ (which you can open using a text editor like notepad) contains installation script detailing where (i.e., which partition on the NT) various components of the zip file get installed.
Typical ROM builds zip contain boot.img which gets installed on /boot partition, and a bunch of system files and apps to be installed on /system partition. Succulent's ROM builds also include recovery which gets installed on /recovery partition. Finally gapps apps get installed on /system as well.
Really, really appreciate this OP, the replies, and the knowledge. VERY helpful. Wont do this til the 1st and will let you know the results... Again, THANKs
Sent from my SAMSUNG-SGH-I317 using xda premium
Well your method worked flawlessly. I had a few minor operator errors but it went just as you explained. I did, however, have a fatal bug in the rom. Not sure who to report it to, but while messing around in settings I tried to change the color of the clock in the status bar. It totally blew away systemui. I tried everything I knew of to restart and recover but had to resort to wipe/factory reset. Could not figure out what data file got corrupted. That in turn made me have to flash the gapps again because none of the Google apps worked including play store. The net result is to add 1 more step to your method. BEFORE messsing with settings, and after the initial setup is complete, boot to recovery and do another backup..I forgot to mention I flashed 20121231, which is the latest release. Thank you so much for your knowledge and reseach. STOCK ROOTED TO CM10 RELEASED.
Sent from my SAMSUNG-SGH-I317 using xda premium
Stuck on backup in CWM 6.0.1.2
My 16gbNT is currently running Team_B CM7. I'm trying to install Kuzma30's CM10.1 from a SD card. Following the instructions from this OP. While trying to perform my backup the process gets about 3/4 of the way through and then sticks at the file named "generic11.lda". It doesn't continue after that and I have left it alone for a considerable amount of time. Any idea what's causing the stick? I've tried it about three or four times with occasionally sticking at different files but it is still about 3/4 of the way through. Backup will not finish.
Any help is greatly appreciated.
I'd suggest trying a version of CWM that is considered compatible with CM7, e.g., CM7-9_CWM_v5.5.x_8gb-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958 (but then remember to flash CM10.1 with 6.0.1.2).
Also check and make sure that you have enough space on your SDcard (you can/should remove backup data associated with failed partial backup attempts).
Backup success, Install failure
digixmax said:
I'd suggest trying a version of CWM that is considered compatible with CM7, e.g., CM7-9_CWM_v5.5.x_8gb-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958 (but then remember to flash CM10.1 with 6.0.1.2).
Also check and make sure that you have enough space on your SDcard (you can/should remove backup data associated with failed partial backup attempts).
Click to expand...
Click to collapse
Backup successful! Thanks button pressed. Now on the install I used CWM 6.0.1.2 and I'm not allowed to complete the install. It aborts installation and gives the following error:
"Installing update...
set_perm: some changes failed
E:Error in /sdcard/cm-10.1-20130102-UNOFFICIAL-acclaim.zip
(Status 7)
Installation aborted."
Any ideas?
Your guide is quite clear but somehow it is not working for me. I have a fresh NT 8GB with stock 1.2 on it.
I obtained the 6 files you mention:
- u-boot.bin
- MLO
- flashing_boot.img
- recovery.img (= cwm_6012_sd.img)
- gapps-jb-20121011-signed.zip
- cm-10-20121231-NOOKTABLET-acclaim-HD.zip (from: http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/)
I copied them to a 16GB 10x SD card and placed the SD card in my NT.
The problem is that whatever I do, it always boots the stock os and never into Cyanoboot. I know I have to connect the NT to my computer with USB and wait for it to boot, but even then it only load the stock OS.
Am I doing something wrong here?
Help much appreciated!