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.
Related
So i thought i'd start with cooked roms since the internal memory is kinda low.
So i started by upgrading the current stock rom 2.73(sigh) and everything works sweet,
next i partition the memory card (4gb) like said in this guide Partition Guide
All good so far!
Next step was to ofc flash the recovery part with flashrec since i have hboot and all,
and that worked well while going after the guide Flashrec guide for noobs like me
boots wonderfully into Cyanogens recovery mode.
Meanwhile i prep the memory card with MoDaCo Custom ROM 2.4
and make sure the phone is rooted by this guide root guide. after i reboot to recovery. made a backup first!(thank god for that option), and after that installed the custom rom.
So far so good eh ?
Once in the phone i started appstosd just to see if it works at all
(remind you that i can login by adb shell with su so should work ?)
and all i get is "your memcard is not partitioned lets do that" well okey then,
I drag the meter so it gets 500mb for ext2, press apply and then new screen comes with a reboot button,
I press it and nothing at all happens.(also pressed the "always allow")
Well maybe it's auto since it should be with MoDaCo lastest rom. but nope nothing goes to the sdcard.
tried doing latest stock rom with root instead of custom rom, and still appstosd gives me the same thing,
refuses to boot. even tried to reinstall the custom rom 3 times, where one of those just rebooted all the time.
Any idea what's going on here ? should be more out there with the same problem ?
cepet said:
Any idea what's going on here ?
Click to expand...
Click to collapse
Yup, you didn't read the release notes for the MoDaCo ROM carefully enough.... Apps2SD works automatically. So long as your card has a second ext2/3 partition it will be recognised and your apps moved to it. No user interaction is required.
On another note, try using Amon Ra recoery image. It's the latest.
cepet said:
So i thought i'd start with cooked roms since the internal memory is kinda low.
[...]
I drag the meter so it gets 500mb for ext2, press apply and then new screen comes with a reboot button,
[...]
Click to expand...
Click to collapse
Maybe the problem is with the ext2 partition. Modaco's works with ext3. If you have a ext2 instead of a ext3 you shouldt upgrade the partition. You can do that from the recovery-image from AMON_Ra
thanks a lot for the tips about amon_ra and all! worked flawlessly , still had to go by flashrec tho.
But what still bothers me is appstosd, both first and second release.
Fully confirmed that root is working both through the phone and adb shell, but still appstosd won't work manually,
don't want the monaco rom tbh, wanna go with stock rom.
Doesn't bother me a bit that i have to do it manually everytime(appstosd that is).
So i'm rooted and appstosd installed, but still appstosd1 tells me that my card is wrongly formatted(did it in amon_ra) then i wiped it clean in amon_ra and tried appstosd2 so it can partition it for me, after i press apply i get the "reboot" button that doesn't work.
Any ideas ?
Thanks in advance!
I currently have cwm .8 and vegan 5.1.1 running without issue and backed up.
I have tried several different gingerbread roms and all of them get stuck on the static image screen before the boot animation.
I have made sure to wipe boot, system, data, dalvik, and cache as well as running Calkulin's Format.zip all prior to rebooting. I also have tried installing the ROMs with or without the Google apps addition. All with the same results.
Internal SDcard partitioned to 2048/0
Is there anything else I can try?
Are you sure they are all hanging at the boot screen? Most of the roms first boot takes a awhile for the cache to get filled with the data it needs to perform.
After the first few boots everything usually goes smooth from then on.
Roxxas049 said:
Are you sure they are all hanging at the boot screen? Most of the roms first boot takes a awhile for the cache to get filled with the data it needs to perform.
After the first few boots everything usually goes smooth from then on.
Click to expand...
Click to collapse
I am a patient fellow. I waited 20min at minimum for each ROM and none have ever made it to the animated boot screen.
I'm having the same issue with mine.. vegantab 5.1 works fine..
none of the gingerbread based roms get passed the viewsonic logo for me.
Same problem here.
All of the GB roms freeze at the android screen.
I have tried everything, I am a serial flasher on my D1 and on the gtab with the froyo builds and consider myself very familiar with the process and it still confuses me...
These are all new gTabs right? Have any of you repartitioned the internal sdcard yet? That option is in CWM recovery. There is a thread on it somewhere too. Basically it wipes the /SDCARD space and repartitions it. The FAQ thread has information on partition sizes too: http://forum.xda-developers.com/showthread.php?t=874258
ramerco said:
These are all new gTabs right? Have any of you repartitioned the internal sdcard yet? That option is in CWM recovery. There is a thread on it somewhere too. Basically it wipes the /SDCARD space and repartitions it. The FAQ thread has information on partition sizes too: http://forum.xda-developers.com/showthread.php?t=874258
Click to expand...
Click to collapse
I have been using the highly recommended 2048/0 as I did not see any details in the threads for the GB ROMs detailing otherwise. Sorry I forgot to mention that in my OP.
-edit-
Repartitioned to 2048/0 and also tried 4096/256. Issue persists
TNT lite 4.40 works Great.
bambamishere said:
TNT lite 4.40 works Great.
Click to expand...
Click to collapse
still a 2.2 ROM
Some progress! Following these steps will erase EVERYTHING from your device including the internal SD. Backup everything before you start.
After doing another restore to stock using nvflash
wipe everything via cwm (boot, system, data, cache, dalvik)
repartition sd to 4096/256
copy vegan ginger edition over to internal sd
it installed and booted up!
-edit-
and then I tried to install gapps and it won't boot again
Ran out of battery power to fully test but finally got it to boot after gapps install. Here are the steps I had to take:
wipe everything via cwm (boot, system, data, cache, dalvik)
repartition sd to 4096/256
Restore to stock using nvflash
did not let it boot into stock
reinstall .8 cwm from external sdcard
in cwm copy vegan ginger edition.zip and gapps.zip over to internal sd
Installed ROM then gapps
reboot
(note: after returning to stock I did not wipe anything with cwm)
genei.09 said:
Ran out of battery power to fully test but finally got it to boot after gapps install. Here are the steps I had to take:
wipe everything via cwm (boot, system, data, cache, dalvik)
repartition sd to 4096/256
Restore to stock using nvflash
did not let it boot into stock
reinstall .8 cwm from external sdcard
in cwm copy vegan ginger edition.zip and gapps.zip over to internal sd
Installed ROM then gapps
reboot
(note: after returning to stock I did not wipe anything with cwm)
Click to expand...
Click to collapse
Good work, quick question, you said you reinstalled cwm from external sdcard, does that mean you used the "cwmod_microsd.zip" from the "[STICKY][GUIDE] Install ClockworkMod, a ROM, Flash Player, and the Market Fix" post?
I have always used the internal one and was wondering if that made a difference.
wadsface said:
Good work, quick question, you said you reinstalled cwm from external sdcard, does that mean you used the "cwmod_microsd.zip" from the "[STICKY][GUIDE] Install ClockworkMod, a ROM, Flash Player, and the Market Fix" post?
I have always used the internal one and was wondering if that made a difference.
Click to expand...
Click to collapse
Yes that should be the same file. Looks like it was recently renamed as I had it labeled external rather than microsd. It isn't really a different cwm I used it so I wouldn't have to let the stock OS boot up and I kept it on the external sdcard so when I repartitioned the internal card I wouldn't loose it. I reloaded to stock many, many, many times trying to get this to work.
I'm currently using the experimental VEGAN Ginger Edition. It has some nice features but the videos for Dungeon Defenders don't play, and the keyboard is a little strange.
genei.09 said:
Ran out of battery power to fully test but finally got it to boot after gapps install. Here are the steps I had to take:
wipe everything via cwm (boot, system, data, cache, dalvik)
repartition sd to 4096/256
Restore to stock using nvflash
did not let it boot into stock
reinstall .8 cwm from external sdcard
in cwm copy vegan ginger edition.zip and gapps.zip over to internal sd
Installed ROM then gapps
reboot
(note: after returning to stock I did not wipe anything with cwm)
Click to expand...
Click to collapse
This work for anyone else? These Woot batches are introducing some issues.
I've had my tablet since early Feb. and I had issues with GB roms when I started trying them too. I found that the steps that worked best for me were pretty much the same as above. Mine are assuming that the tab is coming from something other than stock...
Wipe data,cache,dalvik and Battery Stats... (not sure the battery stats wipe matters)
NV Flash back to stock
Load CWM .08
Repeat Wipe
Load GB Rom
Repeat Wipe
Load rom devs recommended gapps version
Reboot
This USUALLY results in success. I still have mixed results getting gapps installed with some GB roms...once in a while I have to change up the steps and reboot PRIOR to gapps.
I've only had to repartition a few times, but the 2/0 option is the norm for me...and I usually only have to do this after I've made a big mistake, or things start to act "off" with the tablet.....
I think I read in one of the posts over on the dev side that most of the roms are written with the stock bootloader in mind and that it's just good policy to learn NVFlash and use it if you have any issues going from one rom to another.
I've been spending A LOT of time on this site since I got my gtab, too much probably. Usually, about 6 pages into a rom post, the answers to whatever issues we have with install are answered. It seems like mostly page 1 - 4 are people excited to flash...or saying thanks... pages 4 to like 10 are full of the answers to the questions "Why can't, Why didn't, how come..."...and then 10 - 10000 are just plain fun to read. ;-)
Good luck, this Tab is a ton of fon. I was super excited when the woot sale went down. I figure if even 4 or 5 more programmer types ordered one....that could mean 4 or 5 new roms for us to play with!
pceasar said:
This work for anyone else? These Woot batches are introducing some issues.
Click to expand...
Click to collapse
Worked for me last night. Using external sd CW.... Did not work from internal....
*shrug*
so far
3 tablets - internal memory cw install --- only vegan / tnt lite
2 tablets - 1 install of asop (gingerbread) 1 install of vegan GB experementals - one with clymson kernal one with pershot....
I'm just saying...
akodoreign said:
Worked for me last night. Using external sd CW.... Did not work from internal....
*shrug*
so far
3 tablets - internal memory cw install --- only vegan / tnt lite
2 tablets - 1 install of asop (gingerbread) 1 install of vegan GB experementals - one with clymson kernal one with pershot....
I'm just saying...
Click to expand...
Click to collapse
What process did you follow is it the same as tdg2100
Edit: I follow the same process as TDG2100 and it works w00t!! I think this should be included in a sticky somewhere people are going to struggle with this if they don't know how to get out of it.
Also question. Does this mean EVERY ginger ROM I have to flash has to go back via the NVFlash ROM route or can I just upgrade? Just curious, though at this point CM7 w/TT I doubt I'll be changing soon.
tdg2100 said:
I've had my tablet since early Feb. and I had issues with GB roms when I started trying them too. I found that the steps that worked best for me were pretty much the same as above. Mine are assuming that the tab is coming from something other than stock...
Wipe data,cache,dalvik and Battery Stats... (not sure the battery stats wipe matters)
NV Flash back to stock
Load CWM .08
Repeat Wipe
Load GB Rom
Repeat Wipe
Load rom devs recommended gapps version
Reboot
This USUALLY results in success. I still have mixed results getting gapps installed with some GB roms...once in a while I have to change up the steps and reboot PRIOR to gapps.
I've only had to repartition a few times, but the 2/0 option is the norm for me...and I usually only have to do this after I've made a big mistake, or things start to act "off" with the tablet.....
I think I read in one of the posts over on the dev side that most of the roms are written with the stock bootloader in mind and that it's just good policy to learn NVFlash and use it if you have any issues going from one rom to another.
I've been spending A LOT of time on this site since I got my gtab, too much probably. Usually, about 6 pages into a rom post, the answers to whatever issues we have with install are answered. It seems like mostly page 1 - 4 are people excited to flash...or saying thanks... pages 4 to like 10 are full of the answers to the questions "Why can't, Why didn't, how come..."...and then 10 - 10000 are just plain fun to read. ;-)
Good luck, this Tab is a ton of fon. I was super excited when the woot sale went down. I figure if even 4 or 5 more programmer types ordered one....that could mean 4 or 5 new roms for us to play with!
Click to expand...
Click to collapse
Worked for me also.
Matt
I had the same issue and I fixed it by:
1) Boot to clockwork
2) Go to mounts and storage and click "format system"
3) Then wipe data/factory reset
4) After that clear the cache
5) Then go to advanced and wipe dalvik cache
6) Install cm7
7) Install gapps
8) Reboot
Now everything is working for me.
Hi XDA !
I also am stuck at the ViewSonic Birds window - I know how to install CWM etc but I cannot get this to be recognized on a PC via USB. Its almost like the USB isnt started on the GTablet. How do I reboot this thing? Holding down the Power and + button has no effect...
This thread is for noobs by noobs , a place to talk about the app so that we don't clutter the ROM threads .
I hope this works out and helps anyone including myself with using this app.
Here is another GUIDE by JJsax posted on The Root Of All EVO that is a lot more detailed then this one.
The Official forum for BootManager is Init2winit if you would like to learn even more about the app.
As I learn about this app ,as to how and what works with it I'll update this and maybe it will help everyone out that is trying to use BootManager.
This app also works with EVO 3D's with hboot 1.50 s-on
Thank XDA member mnomaanw for that information.
If you use this app and have the time to reply to this post , please share what ROMs you've got to work and a little info on how you installed it. This way I can add it to the op to make it easier and faster for everyone to find.
This is what I've learned so far.
How to install* ROMs via Boot Manager...
Thank seraph863 for filling me in and writing this up. I just changed a few details cause his was for a specific ROM.
MAKE SURE THE ROM IS ON THE ROOT OF YOUR SD CARD NOT IN ANY FOLDERS
1.)* PURCHASE Boot Manager. It does a License check upon boot, so your jacked version will just give you a headache. Seriously, I tried it. Doesn't work.
Here is a Market link to Boot Manager if you didn't already purchase it.
1.a) IF you didn't purchase it... WIPE ALL Boot Manager data and files, including the folder on your SD Card. Then buy it and let it setup again.
2.) Open SuperUser. Hit Menu -> Settings -> Disable Logging.
3. Open BootManager. If you're at work and on Wi-Fi, you may not pass the License check due to firewall issues. If you get a black screen, or license failures, switch to 3/4G and try again.
4.) If all is good, you're asked to Setup the Phone. Do so now. [ You will need to set up your Phone ROM any time you flash a new ROM or kernel to your phone ROM.]
5.) Once installed, hit Menu -> Settings -> Force Large Boot.img
6.) Swipe right to Slot 1. Hit Install .zip and browse to your downloaded ROM.zip file. Make sure to check the Wipe System, Data, and Cache boxes so that it will wipe before it flashes the ROM. Select EXT4 as the file structure.
[This is the important part. This build will take a LONG time. Do NOT use your phone while it is running.]
8.) Once the install has been successful if you need to flash a kernel , theme gapps etc..., go back to Slot 1 and select Install .zip (again). Choose the .zip file. Do NOT wipe system, data or cache. It will ask you to over write it just hit OK.
9.) You should now be ready to boot to your new ROM! Celebrate!
Since this is for the EVO 3D I recommend to always use ext4 as your file structure.
If you get any error messages start over.
Known working ROMs to my knowledge.
These are ROMs that I've set up.
Infected Eternity Phone ROM and sd ROM
KMyers CM7 beta 7.4* with gapps ext4 sd ROM
MeanROM ext4 sd ROM
TrevE Zone v2.3.12 ext4 phone and sd ROM
Mikrunny ext4 phone ROM and sd ROM
XDA members setups
JJsax setup
CDMA Evo3D
hboot 1.50 s-on
TWRP 2.0 touch recovery
Phone ROM SteeleROM 2.73
ROM1 CM9 (The latest version couple days old)
ROM2 Evervolve ICS
mnomaanw's set up
PhoneROM: ViperROM Redline v2.5 RC2
ROM1:CyanogenMOD9
ROM2:MIUI v2.1.6
I've found it to work better to flash and set up my ROM on the phone ROM and then back it up and restore it to a slot.
If your having problems restoring backups and your using TWRP recovery try using CWM. I was having issues with TWRP and since I went back to CWM (touch and 5.0.2.0 both work great but there is no usb mount on the touch version) and I haven't had a single issue restoring a backup to a ROM slot.
My setup will be changing all the time.
CDMA EVO 3D
Eng Hboot s-off
Radio 1.06.00.1216
Phone ROM Infected Eternity Sense 3.0
ROM1 Mikrunny
ROM2 EVOZone
ROM3 SteelROM
ROM4 MeanROM Aria51
Thank you for putting this here. I know I'm to blame for going off topic in some threads about Boot Manager.
I too am having issues getting a ROM to load into slot 1.
Here's my setup...
SteeleROM 2.73
Anthrax #2 kernel
Over 5GB of storage space available.
HBOOT 1.50
TWRP 2.0 recovery (the newest touch one)
I load steele just fine as the phone ROM then try to load CM9, or whatever other ROM into slot 1 it goes through everything then it get's killed at mounting img's. I have it setup for screen on, to load large files, and I even have SU logging turned off. This happens everytime I try to load a ROM into slot 1 it just kills it and never finishes 100%
JJsax said:
Thank you for putting this here. I know I'm to blame for going off topic in some threads about Boot Manager.
I too am having issues getting a ROM to load into slot 1.
Here's my setup...
SteeleROM 2.73
Anthrax #2 kernel
Over 5GB of storage space available.
HBOOT 1.50
TWRP 2.0 recovery (the newest touch one)
I load steele just fine as the phone ROM then try to load CM9, or whatever other ROM into slot 1 it goes through everything then it get's killed at mounting img's. I have it setup for screen on, to load large files, and I even have SU logging turned off. This happens everytime I try to load a ROM into slot 1 it just kills it and never finishes 100%
Click to expand...
Click to collapse
Mine say they install fine and they finish but when I hit boot to the slot it just gets stuck on the splash screen.
I had TrevE Zone on my phone ROM but just switched to eternity. I got MeanROM to install in slot 2 and it booted up fine and is running great but thats the only one I out of the 3 I tried. I set the boot.img to large or what ever the setting is cause thats what they said to do in the video on the site for the app. My real issue though is that restoring my backup to a slot it installs to my system memory. I would like to be able to install backups cause I've read they run better. Hopefully some that knows more about this will come in here and school us a little, I'll even add it to the op and make this a guide if we get enough info.
Here's my quick and dirty instructable I posted in the CM9 thread.
How to install this via Boot Manager...
1.) PURCHASE Boot Manager. It does a License check upon boot, so your cracked version will just give you a headache. Seriously, I tried it. Doesn't work.
1.a) IF you didn't purchase it... delete ALL Boot Manager files, including the folder on your SD Card. Then buy it and let it setup again.
2.) Open SuperUser. Hit Menu -> Settings -> Disable Logging
3. Open BM. If you're at work and on Wi-Fi, you may not pass the License check due to firewall issues. If you get a black screen, or license failures, uninstall BM and delete the folder. Switch to 3/4G and try again.
4.) If all is good, you're asked to Setup the Phone. Do so now.
5.) Once installed, hit Menu -> Settings -> Force Large Boot.img
6.) Swipe right to Slot 1. Hit Install .zip and browse to your downloaded CM9 .zip file. Wipe System, Data, and Cache. Select EXT4 as the file structure
7.) This is the important part. This build will take a LONG time. Do NOT use your phone while it is running.
8.) Once the install has been successful, go back to Slot 1 and select Install .zip (again). Choose the Google Apps .zip file. Do NOT wipe system, data or cache.
9.) You should now be ready to boot to your new ROM! Celebrate!
Warning: Several users report to NOT use any Backup app such as Titanium to restore your apps and data, since the apps on this ROM are very very different. Your mileage may vary.
FYI I'm doing this by memory, so the minor steps might not be accurate (i.e. disable Superuser logging).
If you get any error messages, start over. I assure you, this process worked for me step by step.
Go to their official forum
Applications-->boot manager
You will find my thread named [REF]working and not working rom list
There are many phones
And if you test a rom that is not listed please report if it is working or not
Thanks
Sent from my HTC Desire S using XDA Premium App
I saw your guide in the cm9 thread and tried it with no luck I did exactly what you said and everything seemed to go fine but when I hit boot to ROM on slot one where I installed the ROM I'm stuck on the splash screen. Any ideas why? Thanks for the help also.
kylon said:
Go to their official forum
Applications-->boot manager
You will find my thread named [REF]working and not working rom list
There are many phones
And if you test a rom that is not listed please report if it is working or not
Thanks
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
I was on there I even posted my issue and my log but haven't gotten any help. I did see your list of ROMs but didn't know if its up to date.
I'll have another look at it cause I really want to get this to work and its driving me crazy cause I can usually figure problems out on my own or by searching but I just can't get this.
Thanks for the replies.
linsalata28 said:
I saw your guide in the cm9 thread and tried it with no luck I did exactly what you said and everything seemed to go fine but when I hit boot to ROM on slot one where I installed the ROM I'm stuck on the splash screen. Any ideas why? Thanks for the help also.
Click to expand...
Click to collapse
Which ROM are you using?
I would start over. Use a file manager to delete your ROM from the SD Card and take another image. Make sure you have plenty of storage on your SD card. You could also try clearing the Cache and Dalvik.
You can always get back to your phone ROM manually by booting to Recovery and flashing sdcard\bootmanager\phonerom\update.zip
Edit: Don't forget to check "Use Large boot.img" within Boot Manager
seraph863 said:
Which ROM are you using?
I would start over. Use a file manager to delete your ROM from the SD Card and take another image. Make sure you have plenty of storage on your SD card. You could also try clearing the Cache and Dalvik.
You can always get back to your phone ROM manually by booting to Recovery and flashing sdcard\bootmanager\phonerom\update.zip
Edit: Don't forget to check "Use Large boot.img" within Boot Manager
Click to expand...
Click to collapse
Should I just delete the whole bootmanager folder and clear the data for the app also?
another thing is why when I restore a backup to a slot its installing to my internal memory?
Yeah I just had another look at your list and there aren't many ROMs for this phone on there and they look old.
Thanks again for the help.
It up to date
Anyway gflame is busy
What do you do to install the rom
And wich rom?
Sent from my HTC Desire S using XDA Premium App
I wiped everything out and starting over. I'm going to just try and install viperom in one slot and see if that boots, then I'm going to try and restore a backup to another slot from within a ROM slot to see if that will fix my internal memory issue cause it wont have anywhere to install to . I'll post back with what happens.
kylon said:
It up to date
Anyway gflame is busy
What do you do to install the rom
And wich rom?
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
I disabled logging in su checked off larg boot.img then whet to slot one hit install zip choose cm9 ext4 then checked all the wipe opinions, when that finished I flashed the gapps the same way but without wiping . Everything finished with that I didn't get any errors but when I went to boot to that slot it just hung at the splash screen.
I did that 2 times with cm9 , 1 time with the Eternity ROM sense 3.0 r130 , 1 time with Team Nocturnal's Blackened ROM and they all got stuck at the splash screen.
I did get MeanROM to work using those same steps last night.
Now with the restore of my backup I did basically the same thing but it doesn't give any wipe options when you install it but it would get an error saying boot.img something like that and then I would get a low memory popup saying I only had about 30mb left internal memory when I had over 800mb when I started.
Edit: I have about 6gb free on a 16gb class 10 sd card. I believe its a Samsung card I think.
Edit2: I finished flashing viperom and now that to is stuck on the splash screen. Is there a way to wipe caches for that slot and fix permissions like you would for a regular ROM in recovery if something like this happened.
I'm really starting to think I wasted $3 this is very frustrating sorry.
Thanks for your replies and trying to help.
I went into recovery to go to flash the update zip to restore my phone ROM but when I open the bootmanager folder I don't see anything in it. I'm using twrp 2.0 recovery. Could this have something to do with my problems?
linsalata28 said:
I went into recovery to go to flash the update zip to restore my phone ROM but when I open the bootmanager folder I don't see anything in it. I'm using twrp 2.0 recovery. Could this have something to do with my problems?
Click to expand...
Click to collapse
The steps in your previous post were all correct, except you said you turned OFF "Use large boot.img" ? Make sure that option is ENABLED (has an X on it)
I'm confused as to why the app is trying to install to your internal memory... Mine installs to my SD Card. Make sure the USB cable is not plugged into the phone, and try increasing your screen timeout so it doesn't sleep during the install.
The fact that you're getting the splash screen means you're getting somewhere. Maybe you're being too impatient on the install? Wait a few minutes even after it says Install Complete before continuing.
seraph863 said:
The steps in your previous post were all correct, except you said you turned OFF "Use large boot.img" ? Make sure that option is ENABLED (has an X on it)
I'm confused as to why the app is trying to install to your internal memory... Mine installs to my SD Card. Make sure the USB cable is not plugged into the phone, and try increasing your screen timeout so it doesn't sleep during the install.
The fact that you're getting the splash screen means you're getting somewhere. Maybe you're being too impatient on the install? Wait a few minutes even after it says Install Complete before continuing.
Click to expand...
Click to collapse
I said I checked the larger boot.img off meaning it was enabled sorry for that misunderstanding. I flashed 2 of the slots last night and didn't even test them till today so I don't think that its cause I'm not waiting long enough. Why would none of the folders inside of the bootmanager folder show up in twrp recovery? Could I copy and paste the phone update.zip to the root of my sd card so that I can recover without having to nand restore cause I've already wiped and restored about 10 times trying to get this to work.
Sent from my Eternity 3D using tapatalk
linsalata28 said:
I disabled logging in su checked off larg boot.img then whet to slot one hit install zip choose cm9 ext4 then checked all the wipe opinions, when that finished I flashed the gapps the same way but without wiping . Everything finished with that I didn't get any errors but when I went to boot to that slot it just hung at the splash screen.
I did that 2 times with cm9 , 1 time with the Eternity ROM sense 3.0 r130 , 1 time with Team Nocturnal's Blackened ROM and they all got stuck at the splash screen.
I did get MeanROM to work using those same steps last night.
Now with the restore of my backup I did basically the same thing but it doesn't give any wipe options when you install it but it would get an error saying boot.img something like that and then I would get a low memory popup saying I only had about 30mb left internal memory when I had over 800mb when I started.
Edit: I have about 6gb free on a 16gb class 10 sd card. I believe its a Samsung card I think.
Edit2: I finished flashing viperom and now that to is stuck on the splash screen. Is there a way to wipe caches for that slot and fix permissions like you would for a regular ROM in recovery if something like this happened.
I'm really starting to think I wasted $3 this is very frustrating sorry.
Thanks for your replies and trying to help.
Click to expand...
Click to collapse
My phone:
Phone ROM: SteelROM 2.72
Slot 1: AOSP ICS - wifi doesn't work
Slot 2: CM9 - (google talk and books FC)
Slot 3: MIUI
Slot 4: CM7 (kmeyers)
Boot Manager has a problem trying to restore from a NAND backup, it did the same thing to me where it was installing to the phone's internal memory. I was trying to figure out the problem, but I moved on without success.
I've had the best time installing tricking ROM's by this method. I installed CM7 to a slot, booted into CM7 and installed the ICS and CM9 from there. It's been pretty successful.
If you are getting it to freeze with mounting images, I came across this issue because my SD card did not have enough room. You can try to free up some more space to see if this is the same issue.
I had most problems installing due to not enough space on my SD card, I now have a 32gb card, and have had no issues
Also, I've never had to set it to large boot.img to get things to work, and make sure you disable logging in SU, and use EXT4
---------- Post added at 02:08 PM ---------- Previous post was at 02:04 PM ----------
linsalata28 said:
I said I checked the larger boot.img off meaning it was enabled sorry for that misunderstanding. I flashed 2 of the slots last night and didn't even test them till today so I don't think that its cause I'm not waiting long enough. Why would none of the folders inside of the bootmanager folder show up in twrp recovery? Could I copy and paste the phone update.zip to the root of my sd card so that I can recover without having to nand restore cause I've already wiped and restored about 10 times trying to get this to work.
Sent from my Eternity 3D using tapatalk
Click to expand...
Click to collapse
To quickly get back to your phone ROM (make sure you setup your phoneRom in boot manager first to create the update.zip file, you need to recreate this anytime you change the ROM or Kernel for your phoneROM)
Boot into Recovery
Install the update.zip inside the \boot manager\phonerom\update.zip (not sure if location is accurate, but you get the idea)
Reboot system
Phone should boot to phone ROM, or you can install any other update.zip from your slots, to boot to them etc
spookytay said:
My phone:
Phone ROM: SteelROM 2.72
Slot 1: AOSP ICS - wifi doesn't work
Slot 2: CM9 - (google talk and books FC)
Slot 3: MIUI
Slot 4: CM7 (kmeyers)
Boot Manager has a problem trying to restore from a NAND backup, it did the same thing to me where it was installing to the phone's internal memory. I was trying to figure out the problem, but I moved on without success.
I've had the best time installing tricking ROM's by this method. I installed CM7 to a slot, booted into CM7 and installed the ICS and CM9 from there. It's been pretty successful.
If you are getting it to freeze with mounting images, I came across this issue because my SD card did not have enough room. You can try to free up some more space to see if this is the same issue.
I had most problems installing due to not enough space on my SD card, I now have a 32gb card, and have had no issues
Also, I've never had to set it to large boot.img to get things to work, and make sure you disable logging in SU, and use EXT4
---------- Post added at 02:08 PM ---------- Previous post was at 02:04 PM ----------
To quickly get back to your phone ROM (make sure you setup your phoneRom in boot manager first to create the update.zip file, you need to recreate this anytime you change the ROM or Kernel for your phoneROM)
Boot into Recovery
Install the update.zip inside the \boot manager\phonerom\update.zip (not sure if location is accurate, but you get the idea)
Reboot system
Phone should boot to phone ROM, or you can install any other update.zip from your slots, to boot to them etc
Click to expand...
Click to collapse
What cm7 ROM would you recommend ? For some reason I couldn't see files inside of the BootManager folder but I checked and they are there. I have about 5gb free on a 16gb card ,I was looking into getting a 32gb if I get this app working.
Sent from my Eternity 3D using tapatalk
try
http://forum.xda-developers.com/showthread.php?t=1393613
I upgraded my card, I had about 3-4 gb free and was having problems, but once I upgraded I haven't had many since
I've purchased boot manager and when i run it, it says "application not licenced" Any fix?
spookytay said:
try
http://forum.xda-developers.com/showthread.php?t=1393613
I upgraded my card, I had about 3-4 gb free and was having problems, but once I upgraded I haven't had many since
Click to expand...
Click to collapse
cm7 worked thanks.
[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!
I've basically spent my entire day off from work trying to root my Nook Tablet 8GB to get CM10.1 put on it, and I'm ready to yank my hair out. A while back I successfully got CM10 on an sdcard and have been running that from the sdcard while my warranty was still active (just in case). Now my warranty's run out, and CM10 had been running sluggish for a while, in spite of my cleaning off all unnecessary files regularly. So I figured I'd try an internal ROM install. After hunting around for some really good detailed instructions for noobs (because I totally am one), I found this post (http://forum.xda-developers.com/showthread.php?t=2037368) and decided that even though it looked inefficient to go from CM7 to CM10, it broke the steps down enough for me to follow along.
However, I'm now stuck with CWM not reading the sdcard once it's time to install CM7 and gapps from the zip files. I keep getting the message, "No files found." I've tried unmounting the sdcard (and mounting "sd-ext," just for kicks), and it says, "Error unmounting /sdcard." If I try choosing "format /sdcard," it says, "E:format_volume failed to unmount '/sdcard.'" I've tried popping it out and back in multiple times. I've tried formatting in SDFormatter over again (even did a full overwrite erase, which takes forever, b/c I got a message saying the device doesn't support flash erase). I've been using Minitool to ensure that the partition is always FAT32, primary, set to active. I've gone into the stock OS and used a workaround I found to ensure that it will install apps from unknown sources. I've tried doing the root again from the beginning (which is a pain in the butt because I only have 1 sdcard to use for both the root and the ROM, so I have to keep switching the files out). I have no idea what I could be doing wrong, but I fear that it's something really basic.
Does it matter that I'm leaving the partition labeled "boot" for the ROM install? Is there a better way to put the files on the sdcard besides just with a Windows drag and drop? Is there a way for me to reboot the Nook from within CWM to maybe force it to read the sdcard fresh (keeping in mind that the sdcard no longer has the CWM files on it by that point)? I've seen some info online about people having issues with this class of sdcard, but I really don't want to spend the money on a new one until I rule out the possibility of a stupid user error. I'm also loathe to give up and go back to running a ROM from the sdcard because I've already put over 8 hours into trying to make use of the full Nook memory... If anyone has suggestions, I'd greatly appreciate it. Please keep in mind that any instructions will need to be very, very basic, though.
CWM version 5.0.2.8
sdcard type: SanDisk 8GB Class 4
Files on the sdcard: cm-7-TEAM-B-BETA1-signed.zip and gapps-jb-20130301-signed.zip
MidnightFrost1701 said:
I've basically spent my entire day off from work trying to root my Nook Tablet 8GB to get CM10.1 put on it, and I'm ready to yank my hair out.
...
Click to expand...
Click to collapse
There is no point in flashing CM7 if you're aiming to immediately flash CM10 on top of it.
To flash CM10.x, I'd suggest you try the process outlined at http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1. See http://forum.xda-developers.com/showpost.php?p=42985699&postcount=117 if you'd like to use a more recent CM10.1 build.
...
Files on the sdcard: cm-7-TEAM-B-BETA1-signed.zip and gapps-jb-20130301-signed.zip
Click to expand...
Click to collapse
You'll need an older version of gapps to go with CM7, see http://goo.im/gapps.
digixmax said:
There is no point in flashing CM7 if you're aiming to immediately flash CM10 on top of it.
To flash CM10.x, I'd suggest you try the process outlined at http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1. See http://forum.xda-developers.com/showpost.php?p=42985699&postcount=117 if you'd like to use a more recent CM10.1 build.
You'll need an older version of gapps to go with CM7, see http://goo.im/gapps.
Click to expand...
Click to collapse
Thank you, I'll try that tonight after work! After having been through the steps in the original instructions so many times, I'm familiar enough with things like Minitool Partition Wizard that I can get by with slightly less noobish instructions now. So that's one silver lining... [crosses fingers]
It seems to have worked! The first time I tried to turn it on after the install, the screen went and stayed black after the initial Cyanoboot screen. So I forced a reboot, but it appears to be running just fine! Thanks for the help!