From my understanding there are roms that can be flashed to the nand memory (wiping out the stock b&n crap), roms that can be burned to the emmc, and roms that can be burned to and booted from an SD card.
Provided I understand that right, ideally I want to have Gingerbread installed on the emmc and possibly either Nookie or the modified Eclair rom on the rom memory..
Am I understanding this correctly? Is this setup possible? If this is possible, could you then burn a THIRD rom to an SD card and also boot from that?
There is a thread somewhere with a script to change boot priorities and allowing you to boot into any OS, but I just want to ensure I fully understand how this thing works before I go attempting to flash 3 OS versions lol
This Nook is just my toy, I bought it the day I saw the honeycomb port so I just want to play around with different rom setups till honeycomb is stable and ready to be flashed the nand memory.
Thanks for any help to further my understanding, it's greatly appreciated.
My understanding is there is no nand on the nook which makes sense.
Roms that flash to emmc actually replace the stock rom image.
There are only two ways to install roms: to internal flash memory (EMC) and external flash memory (SD), so the answer is "no".
However, it should be possible with modified uRamdisk (or u-boot so it would run different init/init.rc, which would mount different partitions/subdirs) to have multiple roms on a single SD card.
ah ok I see...so the there is no rom/nand memory and the stock rom is stored of the emmc? So at most you could have one rom on the emmc and one on the external SD?
That makes alot more sense. Thanks for clarifying guys. I'm about to flash Honeycomb to the emmc, wish me luck ha
Related
[mbm]: nookcolmp: dd the emmc to an sd card, change a few paths (the env.txt, the init.rc and the vold.conf
According to mbm... Getting a rom running off an sd is quite simple,.
Seriously cool.
Love to be able to do this. Be nice to be able to try builds easily, with destroying the stock image too badly. Hope some details get posted!
I actually have mine doing this at the moment, just mounting a ext2 partition on the SD instead of the internal one. I tried Froyo and Eclair from an Emulator ROM, but no go. Also tried a Motorola Droid ROM, which I'm currently trying to recover from The inability to run updater-script's is a pretty big pain in the but, and that's the issue I had with the Droid ROM.
Very exciting stuff going on here. I look forward to being able to run a clean rom on the device to get an idea of what it's true capabilities are.
I know this is an old post, but I'm really looking to get the stock rom booting off the SD card. It would make other development testing less concerning.
I'd be interested in trying this myself, but I don't know what to do about the varying emmc partition sizes to SD card sizes.
Thanks for any advise or assistance!
Cheers!
I know, its not truly bricked. But as of right now it'll only power up if connected to USB power source and will only boot as far as landscape Android text with a blinking underscore. Part of why I didn't get it fixed last night was my unwillingness to leave and aquire a larger micro SD card. I'll be leaving work in a couple hours to go get some stuff to get this thing working again (its 2 days old) heres the recovery plan:
Aquire 4GB + MSD card
Flash a stock 1.1 ROM (the one thats pre-rooted here)
Install (sideload) that stock joint
Read that Elephant book that comes with the Nook because its working again
From there I'm a little confused. Can I flash Clockwork to a MSD and then use that to flash CM7? Or am I oversimplifying here?
From my trial and error the only thing I have gotten to "un-brick" is to boot into monsters pack then switch cards (i used the 128mb version and it removed the rest of the space on my 2gig card) then format cache and system in the mount section of clockwork. then head to install zip and installed a complete restore to 1.0.1. when thats done I head to BN site and got the side load to 1.1.whatever and let it do its thing. From there your up to date and just like new and can then try and "re-brick" it. Ive had mine for less than a week and done this a few times now cause I am never satisfied.........
The nook is never bricked unless it has a hardware failure. One of the great things about the nook is that it has a very early hook in the boot sequence that checks for presence of a bootable SD card. Creating a bootable SD card is easy. Follow the thread which instructs how to make a CWM bootable SD card. You need to choose between the EXT3 or EXT4 version depending on which ROM you will flash. CM7 requires EXT4 version of CWM. If you try to use the wrong CWM version you will get the outcome that you just observed, stuck at android text. If you want to flash the stock 1.1 rom, then you'll need the CWM EXT3 version.
I had the exact same issue. I used this:
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
from the HC v4 on eMMC thread and it solved the issue and I have since flashed just about everything available with success, including dual boot ROMs. I am using a 1gb card.
Calla969 said:
I had the exact same issue. I used this:
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
from the HC v4 on eMMC thread and it solved the issue and I have since flashed just about everything available with success, including dual boot ROMs. I am using a 1gb card.
Click to expand...
Click to collapse
I'll try this and see if I can get it booted. Thanks.
nswenson said:
The nook is never bricked unless it has a hardware failure. One of the great things about the nook is that it has a very early hook in the boot sequence that checks for presence of a bootable SD card. Creating a bootable SD card is easy. Follow the thread which instructs how to make a CWM bootable SD card. You need to choose between the EXT3 or EXT4 version depending on which ROM you will flash. CM7 requires EXT4 version of CWM. If you try to use the wrong CWM version you will get the outcome that you just observed, stuck at android text. If you want to flash the stock 1.1 rom, then you'll need the CWM EXT3 version.
Click to expand...
Click to collapse
That makes things much clearer for me. I knew CM7 required EXT4, but was unaware that the CWM flashed MSD would be properly formatted and couldent be bothered to boot in Linux to do it. Blame lack of sleep. Thanks!
I've been successfully using phiremod's ROM in eMMC but now also want to be able to use original stock Nook config. I can restore NC back to out-of-box configuration but am looking for best dual boot solution so I can still play with HC, froyo, cm7, etc. Here are my questions:
1. Do any of the dual boot options let stock Nook share eMMC with another ROM?
1a. Can only specially modded ROMs be dual booted from eMMC?
2. Can the original stock Nook be run from SD?
3. Can phiremod's ROM share eMMC with another ROM or can it run from SD?
4. Can I do a Titanium backup of all of my phiremod-running apps and restore them in another ROM (I don't want to have to re-download and configure all my Market apps again)?
Sorry for all the questions but I tried to get all of them in one place.
TIA
I've had some of the same questions too.
I'd like to keep stock on the eMMC but be able to play with HC, CM7, Froyo on eMMC too... (right now I'm running stock/rooted on the eMMC, and Froyo and HC on different MicroSD cards)
If I correctly understand what I've read, it does appear the answer to your question 1 & 1a is YES... When dual booting ROMs on the eMMC (or SD for that matter), it appears that the eMMC needs to be repartitioned, and the roms edited/adjusted to point at the correct partitions on the eMMC. There is a thread which contains already "edited for dual boot" roms. see -> http://forum.xda-developers.com/showthread.php?t=959461 and there is a "script file" to move the stock nook rom into dual boot. (I haven't been brave enough to try it)
As for question 2, from what I read in another thread, running the stock NookColor rom from SD would also take adjusting the image/rom to point to the SD card partitions instead of the eMMC partitions. I haven't found any work being done on this, as there doesn't seem to be much demand for it.
I'm hoping someone more knowledgeable than me comes along to verify my understanding is correct, and properly answer your questions.
memman said:
I've been successfully using phiremod's ROM in eMMC but now also want to be able to use original stock Nook config. I can restore NC back to out-of-box configuration but am looking for best dual boot solution so I can still play with HC, froyo, cm7, etc. Here are my questions:
1. Do any of the dual boot options let stock Nook share eMMC with another ROM?
1a. Can only specially modded ROMs be dual booted from eMMC?
2. Can the original stock Nook be run from SD?
3. Can phiremod's ROM share eMMC with another ROM or can it run from SD?
4. Can I do a Titanium backup of all of my phiremod-running apps and restore them in another ROM (I don't want to have to re-download and configure all my Market apps again)?
Sorry for all the questions but I tried to get all of them in one place.
TIA
Click to expand...
Click to collapse
1 and 1a are definitely yes, look at the dual boot thread in the development section.
I hear #2 is possible but I haven't seen much of it yet, it may exist.
For #3, phiremod is based on CM7 which doesn't have an SD version as far as I know...it's definitely possible to dual boot if someone makes a dual boot compatible version.
For #4, I don't see a reason why you couldn't. Titanium backup has always worked across multiple roms and devices.
THANK YOU IN ADVANCE FOR ANY HELP! I'm dead new with android and just got a Nook HD+ 32gb (groupon deal $130)
anyway, I've done a ton of reading on here and watched a bunch of youtube vids- i don't know if people use overlapping terminology that means the same things or what.. and also seems like theres a lot of opinions in the forums.
I want basically the full android experience and root access- like i said, never used any android, but i like toying around with these things. BUT i also really want a fully stable platform- don't want constant crashing or it reseting on me.
questions i have-
1)the CWM is the "program" (don't know the correct terminology) that basically gives me the access to back up and install new roms, root, etc? TWRP does the same thing- but i understand you don't use that?
2)If i have a BRAND NEW nook HD+ do i need to back it up before messing with it OR are the "stock rom" zips you provided just that?
2) with the SD card image, do i need to put a specific image on the specified sd card. i.e. 4gb SD gets a 4gb image? or is the image universal to whatever size SD card i get?
2a) What problems am i going to run into using my mac to make the SD card, if any? what program do i need to use?
4) when you back up through CWM where does it save it? to the SD card?
4a) this is where i was confused about the image, reading into some of the posts it led me to think the image file took up the entirety of the
SD card.
4b)So in the future i could just boot from the SD card and would have the option to flash the stock rom back on the HD+ if desired? and/or
go back to CM?
5) what is DUALBOOTING? and NANDROID? how do they tie into CWM and CM10. very confused about this.
6) any disadvantage to flashing the EMMC vs booting from SD card every time? I THINK i want to flash the emmc, i don't want to be tied to booting from the SD card everytime- if I'm understanding that correctly.
7)what is this "trim" lag problem? couldn't really figure out what people were talking about.
thanks a ton for any help you can give me- I'm sure you receive a lot of questions!
-Sonny
santinod15 said:
THANK YOU IN ADVANCE FOR ANY HELP! I'm dead new with android and just got a Nook HD+ 32gb (groupon deal $130)
anyway, I've done a ton of reading on here and watched a bunch of youtube vids- i don't know if people use overlapping terminology that means the same things or what.. and also seems like theres a lot of opinions in the forums.
I want basically the full android experience and root access- like i said, never used any android, but i like toying around with these things. BUT i also really want a fully stable platform- don't want constant crashing or it reseting on me.
questions i have-
1)the CWM is the "program" (don't know the correct terminology) that basically gives me the access to back up and install new roms, root, etc? TWRP does the same thing- but i understand you don't use that?
Click to expand...
Click to collapse
CWM (ClockworkMod) is a recovery program that allows you to do just what you said. TWRP is also a recovery, but uses the touch screen instead of hardware keys to control it.
2)If i have a BRAND NEW nook HD+ do i need to back it up before messing with it OR are the "stock rom" zips you provided just that?
Click to expand...
Click to collapse
You can either use the CWM backup tool to return your device to stock (including any data you have already created, like registration) or the plain stock zips I have will also return you to stock, but the way it was when you got it new before registering.
3) with the SD card image, do i need to put a specific image on the specified sd card. i.e. 4gb SD gets a 4gb image? or is the image universal to whatever size SD card i get?
3a) What problems am i going to run into using my mac to make the SD card, if any? what program do i need to use?
Click to expand...
Click to collapse
Since you have a Mac, the best way to do it is the new procedure without burning an image. Since I don't have a Mac, I don't know the exact programs to use. I think SDFormatter comes in a Mac version. And I know there are lots of mac partitioning programs to set the first partition active. And using the procedure does use all of the SD, so it is best to use a relatively small one, 2-4GB.
4) when you back up through CWM where does it save it? to the SD card?
4a) this is where i was confused about the image, reading into some of the posts it led me to think the image file took up the entirety of the
SD card.
4b)So in the future i could just boot from the SD card and would have the option to flash the stock rom back on the HD+ if desired? and/or
go back to CM?
Click to expand...
Click to collapse
It saves it either to the SD card or internal memory, you choose.
Yes it uses all of the SD if you use the new procedure. But you need that if you choose to backup to SD. A backup takes about 1.5GB.
And yes, save the SD for future use, like restoring backups or installing new ROMs.
5) what is DUALBOOTING? and NANDROID? how do they tie into CWM and CM10. very confused about this.
Click to expand...
Click to collapse
Dual booting means having one operating system on internal memory (also called emmc for Embedded MultiMedia Card) and one installed to a bootable SD. Most people that dual boot have stock on internal and CM on SD. They are separate and independent from each other.
Nandroid just means internal memory. So a nandroid backup means backing up whatever you have on internal memory.
6) any disadvantage to flashing the EMMC vs booting from SD card every time? I THINK i want to flash the emmc, i don't want to be tied to booting from the SD card everytime- if I'm understanding that correctly.
Click to expand...
Click to collapse
The only advantage to booting to CM on SD is it leaves internal memory untouched for warranty reasons. The disadvantage is it runs slower and is less stable.
7)what is this "trim" lag problem? couldn't really figure out what people were talking about.
Click to expand...
Click to collapse
LAG is a complex issue to explain. If you are used to hard drives getting fragmented and slowing down your system, LAG is similar but a different mechanism with solid state flash drives. TRIM is a process to undo what causes LAG. But some of the solid state chips in these devices have a bug and when TRIM is run, it bricks the chip, making it unusable.
thanks a ton for any help you can give me- I'm sure you receive a lot of questions!
-Sonny
Click to expand...
Click to collapse
leapinlar said:
CWM (ClockworkMod) is a recovery program that allows you to do just what you said. TWRP is also a recovery, but uses the touch screen instead of hardware keys to control it.
You can either use the CWM backup tool to return your device to stock (including any data you have already created, like registration) or the plain stock zips I have will also return you to stock, but the way it was when you got it new before registering.
Since you have a Mac, the best way to do it is the new procedure without burning an image. Since I don't have a Mac, I don't know the exact programs to use. I think SDFormatter comes in a Mac version. And I know there are lots of mac partitioning programs to set the first partition active. And using the procedure does use all of the SD, so it is best to use a relatively small one, 2-4GB.
It saves it either to the SD card or internal memory, you choose.
Yes it uses all of the SD if you use the new procedure. But you need that if you choose to backup to SD. A backup takes about 1.5GB.
And yes, save the SD for future use, like restoring backups or installing new ROMs.
Dual booting means having one operating system on internal memory (also called emmc for Embedded MultiMedia Card) and one installed to a bootable SD. Most people that dual boot have stock on internal and CM on SD. They are separate and independent from each other.
Nandroid just means internal memory. So a nandroid backup means backing up whatever you have on internal memory.
The only advantage to booting to CM on SD is it leaves internal memory untouched for warranty reasons. The disadvantage is it runs slower and is less stable.
LAG is a complex issue to explain. If you are used to hard drives getting fragmented and slowing down your system, LAG is similar but a different mechanism with solid state flash drives. TRIM is a process to undo what causes LAG. But some of the solid state chips in these devices have a bug and when TRIM is run, it bricks the chip, making it unusable.
Click to expand...
Click to collapse
THANK YOU.. so much answered for me
Hello All,
TLDR
Are there any CM based ROMs that are preconfigured to be loaded entierly onto an external SD? Any kernels/recoveries that have mount points modified for full external SD (not swap)? Any way to do this manually?
Longer Version
About two years ago my i9000 died to the failure of the internal memory. I tried all of the normal recovery procedures but nothing worked so I concluded it was toast and moved on. Recently I thought it would be a good backup phone in the event that found myself between sales of my main phone so I decided to revive it by loading the OS entirely on an external SD. This is a bit of a rabbit hole and finding information that actually worked was quite challenging. Almost all of the threads have to do with swapping internal/external cards to gain memory but I don't want to swap, I want everything on the external card.
Eventually I found build based on XXJVU (2.3.6) that was pre-configured to install (via ODIN) and run off of the external card directly. It works but it's dog slow. The problem is the 3e recovery won't flash anything that isn't signed so I can't move to a CM based rom. And, when I flash another kernel/recovery like speedmod, it's doesn't "know" about my unusual storage configuration so any further flashing fails.
At this point I'm open to any suggestions. Maybe the solution is simple and I'm doing something wrong. As far as I can tell, I need a CWM/TWRP based recovery that has it's mount points modified to the external SD card. I don't care to move all the way to KitKat, I'd be happy to get onto CM in basically any version. At some point along the way (4.2/4.3?) the mount point configuration moved out of vold.fstab and into the kernel which basically requires a kernel compiled specifically for this problem. If it's easier, I'd be happy to run the version just prior to this change so I can edit the mount points manually.
If anyone has suggestions or threads I should be reading that would be helpful. Just to be clear, I am currently using the phone, rooted with 2.3.6 and installed entirely on the external SD.
Thanks
Read this. I don't think there are any preconfigured CM based ROMs for external SD card installation.
Also this is a way to fix your broken internal memory. It might work.