Related
This is one of those things that I've always assumed would work, but I don't think I've seen anyone actually confirm it or talk about it yet. Before doing any of this I did a clean wipe of everything, just to avoid confusion on my part.
Step 1) I DD'ed the entire filesystem to an 8GB microSD that I have.
Step 2) Mounted p1 from SD (which is a copy of P1 from internal)
Step 3a) Pulled ramdisk
Step 3b) Extracted ramdisk
Step 3c) Changed all mmcblk0 refs to mmcblk1 in init.rc
Step 3d) Recompiled ramdisk
Step 3e) Pushed ramdisk back to p1 on SD
Step 4) Shut down Nook, reboot, confirm via mount command that all mounted volumes are mmcblk1
As I said, this is nothing revolutionary, but I figured it could be good for testing, especially if anyone wants to take a shot at a potentially dangerous mod like recovery or installing a fresh /system. Also, if I ever seriously messed up my internal memory, I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way.
Very interesting. Thanks for the effort. Might be worth saving the image in case someone actually DOES brick their nook.
I'm curious as to the specifics. Aren't there several filesystems on the device? What did you do to pull/extract/recompile the ramdisk?
APKs
Are you able to install apk files to the emulated rom/nand on SD card...
also are you able to mount an extra partion on the card....
Thanks
"I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way"
That will be great if we can push those files back to NAND
FYI, Holding just power + Nook buttons for about 15-20 sec will bring up the factury reset screen.
nook'r said:
Are you able to install apk files to the emulated rom/nand on SD card...
Click to expand...
Click to collapse
I haven't yet, but I don't see why not. Nothing especially different about it as opposed to the internal filesystem.
nook'r said:
also are you able to mount an extra partion on the card....
Click to expand...
Click to collapse
Right now I left vold alone, so it rather stupidly mounts p1, which contains all the critical stuff. I don't see any reason why vold couldn't be made to point to another seperate partition. (which is what I did with some other trials when using the internal ramdisk to boot to /system on the SD - left p1 as a "sdcard" partition)
nook'r said:
"I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way"
That will be great if we can push those files back to NAND
Click to expand...
Click to collapse
I've backed up my own partitions individually. I suppose if I zero'd empty space and gzipped I could probably find some way to write the entire partition table to somewhere.
Would this be useful to someone who would want to dual boot with Ubuntu or MeeGo?
Could this be used to "dual boot" the fully stock Nook in store and then from card when you want to be free?
Homer
Homer_S_xda said:
Could this be used to "dual boot" the fully stock Nook in store and then from card when you want to be free?
Homer
Click to expand...
Click to collapse
This can be used for whatever you want to use it for. I've been running this way for quite a while, and everything works just as it would if you're running from the internal. It's just like dual booting on your PC.
The first (that I saw) and best documentation for setting this up can be found at:
http://blog.fsck.com/
axe2 said:
This can be used for whatever you want to use it for. I've been running this way for quite a while, and everything works just as it would if you're running from the internal. It's just like dual booting on your PC.
The first (that I saw) and best documentation for setting this up can be found at:
http://blog.fsck.com/
Click to expand...
Click to collapse
This is intriguing.
I would love to run everything off a micro sd and then pop it out to put it back to stock.
Would a 1GB micro sd work ok for this?
Someone needs to come up with an automated way to do this. That would be awesome.
moovius said:
This is intriguing.
I would love to run everything off a micro sd and then pop it out to put it back to stock.
Would a 1GB micro sd work ok for this?
Someone needs to come up with an automated way to do this. That would be awesome.
Click to expand...
Click to collapse
1GB is going to be too small to hold the whole system, but 4GB should work.
It should be something that would be scriptable assuming that the required tools exist on the standard rom, but I don't know if the tools are on there.
You could probably get to 1 GB if you dumped all the recovery junk and made media and data tiny. I'm trying to think if there's anything earing up tons of space besides /system.
Of course, just because you can doesn't mean you should.
how about multiple partitions on a 16gb
clockworx said:
This is one of those things that I've always assumed would work, but I don't think I've seen anyone actually confirm it or talk about it yet. Before doing any of this I did a clean wipe of everything, just to avoid confusion on my part.
Step 1) I DD'ed the entire filesystem to an 8GB microSD that I have.
Step 2) Mounted p1 from SD (which is a copy of P1 from internal)
Step 3a) Pulled ramdisk
Step 3b) Extracted ramdisk
Step 3c) Changed all mmcblk0 refs to mmcblk1 in init.rc
Step 3d) Recompiled ramdisk
Step 3e) Pushed ramdisk back to p1 on SD
Step 4) Shut down Nook, reboot, confirm via mount command that all mounted volumes are mmcblk1
As I said, this is nothing revolutionary, but I figured it could be good for testing, especially if anyone wants to take a shot at a potentially dangerous mod like recovery or installing a fresh /system. Also, if I ever seriously messed up my internal memory, I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way.
Click to expand...
Click to collapse
Think someone could put together a noob guide for this? I'd like to try running a rooted version of Nook Color from SDCARD (partitioned?) on my stock Nook Color.
If possible? Please & Thanks...
I'm opening a new thread as this is really the work of verygreen, racks11479, j4mm3r, stilger, and rookie1.... and I've hijacked their threads enough as I only did minor repackaging to put this together as a hopefully generic template image...
This is but an attempt to create a mostly generic SDcard template for installing all versions, as base for Froyo, CM7, or Honeycomb as an SDcard install...... Most of the features best lend themselves to CM7 as verygreen's Alternate (uAltImg/Ram) allows installing and upgrading all current variants of CM7... but with Recovery as CWR 3.0.1.0/Ext3/4 with verygreen's installer/upgrader as uAltImg/Ram it can handle all your CM7 variant install and upgrade/migrate to SDcard needs...
The generic 2GB expandable image is available from;
http://dev-host.org/aewwoavj437z/Nook-2GB-SDCard-CW3010-VGCM7InstallerAsALTinMultiBoot-v6.zip
I suspect/hope that this thread will fade fast from the first page but just hope it will be useful for folks when modeling and building generic SDcard bootable versions...
EDIT: For folks who just want to update just their existing SDcard boot partition and get this boot functionality
I removed the files you shouldn't change from an existing /boot dir and zipped up the rest and posted this zip in my dropbox
http://dl.dropbox.com/u/6922721/jtbnet-modified-bootfiles.zip
Just have your SDcard mounted as /boot on your PC and extract this zip to it to get the same boot options as my card...
The layout of the current .v6 template SDcard to allow it to fit on a 2GB minimum size card is;
Part. # Name FStype Alloc. size Free Space
1 /boot FAT32 149MB 120MB
2 /system EXT3 462MB 455MB
3 /data EXT3 964MB 948MB
4 /sdcard FAT32 39MB 38MB
This is a Generic 2GB expandable template SDcard image to use to create pretty much whatever bootable SDcard you want...
How it differs with earlier Generic SDcards is I reorganized the default, Recovery, and Alternate boot choices using j3mm4r's multi-boot bootloader.
I updated Recovery to the newest version CWR 3.0.1.0 modified to write to SDcard instead of Internal/eMMC memory partitions with the help of user stilger. This can be used for Backup and Restore of full cards... as well as installing of CW packages like Google Apps, and Custom CW Rom Install packages you can find for Froyo, Honeycomb Preview and Gingerbread in this forum...
I moved verygreen's CM7 Installer/updater to the Alternate boot choice... In verygreen's thread he uses this as the default Kernal and Ramdisk which gets overwritten by the package you install... thus the need for 2 cards or copying files around to reuse the original... with this as Alternate it doesn't get overwritten and thus is available next time you want to use it... like Install CM7 for the first time... then upgrade to the new Nitely the next day without need for finding and copying files or using 2 cards...
How verygreen's Installer/updater differs from CWR... With vg's installer you place the installable files on the /boot partition... this installer will install SDcard ready or agnostic installables AND will install eMMC designed version CM7 builds and do on the fly conversion to SDcard version during the install seemlessly...
CWR 3.0.1.0 for SDcard will expect the install zip or backup file to be on the 4th/sdcard partition and expects these to be agnostic installs as it doesn't do anything on the fly to make these run on SDcard... It they are built or modifed to run on SDcard thats fine and installing from this Recovery works as would be expected...
I extended the size of the boot partition to have ~120MB free to allow for installing larger images as the prior ~100MB space was too close to currently typical installable Custom Rom packages.
The 4th /sdcard partiiton is created Very small to fit on a 2GB SDcard and really needs to be expanded using Easeus Partition Manager on Windows or an equivalent program on your OS of choice to fit your size choice of SDcard...
I will offer some experience with SDcard here... I bought 10 different manufacturers, and Class/speed cards... I ran disk benchmarks for all and then used the ones that performed best for daily use... Sandisk brand is the most generally faster than the Class it's stamped... A Class 4 beats most brand's Class-6... I wanted the fastest... and settled on buying 8 cards as KingMax Class-10 SDcards, 4 4GB and 4 8GB, from buy.com... these aren't the cheapest cards by far, BUT in this case you DO get what you pay for...
So for daily use I'd reccommend the KingMax 8GB Class-10 cards as I've gotten better than 2000 Quadrant scores running these cards for Froyo, Honeycomb, and CM7 Gingerbread installs... this is as good or better performance than most scores I've seen from folks running the same installs on Internal/eMMC...
CM7 Install Example by User stilger
with comments added by jtbnet and xdabr:
----------------------------------
You *should* be able to do the following with the image provided in this thread on your 2gb card:
1. Download image from this thread (currently v6)
http://dl.dropbox.com/u/6922721/Nook-2GB-SDCard-CW3010-VGCM7InstallerAsALTinMultiBoot-v6.zip
2. Write this Image to your card (I use win32diskimager or dd in linux)
3. Use Easeus Partition Manager to extend the 30MB 4th FAT32 /sdcard partition to fit your current SDcard
4. Once the card is written, place the cm7 zip in the root of the boot filesystem.
(Should be a drive letter with boot in the name with files like uImage uRecImg etc on it)
http://mirror.teamdouche.net/?device=encore
5. Place the gapps zip of your choice in the same "boot" filesystem.
http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110307-signed.zip
6. Place SDcard in your Nook.
7. Turn on Nook.
8. Hit N button when it says Press any key for menu.
9. Choose SD and Alternate as your boot option
10. Let it finish. It says it will reboot but usually hangs for me so I give it 10 seconds after the screen goes black and long press the power button until it starts up...
11. Boot into CM7
TIP: To have rooted stock eclair version nook use the same sdcard partition (#4) as you use when booting on an SDcard bootable you can make one simple edit to the stock eclair /system/etc/vold.conf...
There are 2 definition blocks in the file... the first is for mount of internal eMMC partition 8 as /media, while the second block is to mount the 1st sdcard partition as /sdcard... to change this so that the 4th partition on the SDcard gets mount to /sdcard just Add a line;
partition 4
in the second block with your favorite editor like Root Explorer, or via adb pull,edit,push of the vold.conf file... and reboot...
I.E.:
## vold configuration file for zoom2
# modified for encore
volume_sdcard {
## This is the direct uevent device path to the SD slot on the device
media_path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
partition 8
media_type mmc
##mount_point /sdcard
mount_point /media
ums_path /devices/platform/usb_mass_storage/lun0
}
volume_sdcard2 {
## Currently points to internal eMMC, assumes eMMC is formatted as FAT32
media_path /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
partition 4
media_type mmc
##mount_point /media
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun1
}
Just to verify, this image has?
J4mm3r's multi-boot
CWM 3.0.1.0 but with correct mounts like racks11479's CWM 3.0.0.6 as uRecImg/Ram
verygreens installer as uAltImg/Ram
I had already done the same with racks CWM, but that's ext4 only I believe.
This will be great with CWM 3.0.1.0.
Thanks for putting this together
P.S. What is the CM7 vesion as uImage/uRamdisk?
Tried to burn the image on a 2Gb SDcard to look inside.
It's a 4GB image not 2GB.
bobshute said:
Tried to burn the image on a 2Gb SDcard to look inside.
It's a 4GB image not 2GB.
Click to expand...
Click to collapse
Sorry Bob... I uploaded the wrong image... Had a long day at work today so just getting to uploading a fresh image... this one IS 2 GB with larger/150MB /boot but a very small 4th /sdcard partition, and has formated system and data so won't boot to CM7 anymore but it's much cleaner...
Only thing this 2GB image only zips down to 800MB... strange as the wrong card I uploaded last night was a 4GB card I was testing with and with lots of data on system and data and it zipped down to 300MB... but this one is cleaner and does boot to CWR 3.0.1.0 as recovery and verygreen's CM7 install/updater as Alternate boot...
It's taking forever to upload so I may not be able to update the link in the original post till the morning as already well after midnight now...
bobshute said:
Just to verify, this image has?
J4mm3r's multi-boot
CWM 3.0.1.0 but with correct mounts like racks11479's CWM 3.0.0.6 as uRecImg/Ram
verygreens installer as uAltImg/Ram
I had already done the same with racks CWM, but that's ext4 only I believe.
This will be great with CWM 3.0.1.0.
Thanks for putting this together
P.S. What is the CM7 vesion as uImage/uRamdisk?
Click to expand...
Click to collapse
You are correct on what it has for uRecImg/Ram and uAltImg/Ram and yes Racks' 3.0.0.6 is Ext4 Only.... thus why I wanted to update to 3.0.1.0/Ext3 and Ext4...
That wrong 4GB upload from yestrday was the test card I had expanded and tested installing CM7 RC4 with UI tweaks to test VG's installer and then restored system and data from my normal card's backup to test CWR 3.0.1.0... so I mixed up the cards when I made the image and uploaded the expanded test 4GB version instead of the original blank 2GB version I started with...
Updated OP with cleaned up file...
Thanx to Verygreen's suggestion to zerofill the system and data partitions to allow for better compression I uploaded v4 where the zipped filesize is down to 420MB from prior zip of 770MB. OP link is updated...
I'm going to continue to see if I can find a way to make this significantly smaller while still containg all 4 mountable partitions and will upload any success story if/when it might occur...
I actually used the 2GB image itself booted to CWR and ran 'adb shell' to allow me to use the 'dd' command to zero fill the system and data partitions... THANX again to verygreen for that idea...
jtbnet said:
Thanx to Verygreen's suggestion to zerofill the system and data partitions to allow for better compression I uploaded v4 where the zipped filesize is down to 420MB from prior zip of 770MB. OP link is updated...
I'm going to continue to see if I can find a way to make this significantly smaller while still containg all 4 mountable partitions and will upload any success story if/when it might occur...
I actually used the 2GB image itself booted to CWR and ran 'adb shell' to allow me to use the 'dd' command to zero fill the system and data partitions... THANX again to verygreen for that idea...
Click to expand...
Click to collapse
jtbnet - I think zeroing the /data and /system file systems causes your script to fail. I put this image on an 8gb sd card today. I copied the latest Tablet Tweaks and gapps zip files to the boot partition rebooted into altboot.. It failed not being able to create files. Took the nook into recovery logged in via ADB and /system where full:
Before:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 250080 32 250048 0% /dev
/dev/block/mmcblk0p7 350021 52983 278967 16% /cache
/dev/block/mmcblk1p2 458925 458925 0 100% /system
/dev/block/mmcblk1p3 972436 972436 0 100% /data
Click to expand...
Click to collapse
Used recovery to format /data and /system.
After:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 250080 32 250048 0% /dev
/dev/block/mmcblk0p7 350021 52983 278967 16% /cache
/dev/block/mmcblk1p2 458925 8238 426992 2% /system
/dev/block/mmcblk1p3 972436 16424 906616 2% /data
Click to expand...
Click to collapse
Booted into alt boot after copying zip files to /boot again and everything installed fine.
stilger said:
jtbnet - I think zeroing the /data and /system file systems causes your script to fail. I put this image on an 8gb sd card today. I copied the latest Tablet Tweaks and gapps zip files to the boot partition rebooted into altboot.. It failed not being able to create files. Took the nook into recovery logged in via ADB and /system where full:
...
Used recovery to format /data and /system.
.
Booted into alt boot after copying zip files to /boot again and everything installed fine.
Click to expand...
Click to collapse
THANX
I had been just deleting the filler files in CWR (/system/zerofile and /data/zerofile) instead of formatting... BUT I think I have found the answer... I need to zerofill to cause the 2 partitions to compress reasonably... BUT if I create the files then sync,umount,re-mount then delete the files, sync, umount this frees space by freeing the inode but shouldn't actually touch the zerofill'd now freed space... so compression should be the same without the files...
I'll give this a try and upload v5 later hopefully...
EDIT: finally found time to upload v5... well mirror is still in process... /data and /system now empty and result is even a few bytes smaller...
Thank you jtbnet, but I am so confused.
Personally I'm mostly interested in SD card booting because I'd still like to leave the internal eMMC memory stock or near-stock.
But I get confused as to how the "size agnostic" approach ultimately writes to the card, whether it uses the NC or a PC as an intermediary to get the card written, how Clockwork Recovery comes into play if at all (I thought it was only used when you ARE futzing with the eMMC instead of cleanly booting off SD card), and more.
I would prefer a list of disk images I can write to an SD card with standard tools (I used "dd" on a Mac for brian's Nookie Froyo SD image), but it seems your mod here and the main size-agnostic installer are more complicated than that.
Is there a simple explanation you can give me (and other similar newbies)?
xdabr said:
Thank you jtbnet, but I am so confused.
Personally I'm mostly interested in SD card booting because I'd still like to leave the internal eMMC memory stock or near-stock.
But I get confused as to how the "size agnostic" approach ultimately writes to the card, whether it uses the NC or a PC as an intermediary to get the card written, how Clockwork Recovery comes into play if at all (I thought it was only used when you ARE futzing with the eMMC instead of cleanly booting off SD card), and more.
I would prefer a list of disk images I can write to an SD card with standard tools (I used "dd" on a Mac for brian's Nookie Froyo SD image), but it seems your mod here and the main size-agnostic installer are more complicated than that.
Is there a simple explanation you can give me (and other similar newbies)?
Click to expand...
Click to collapse
Check racks11479's thread for a good number of SDcard installable versions...
http://forum.xda-developers.com/showthread.php?t=998861
I do hope to find time to update the second post in this thread with some much better explanantion... but in short...
This is a Generic 2GB expandable template SDcard image to use to create pretty much whatever bootable SDcard you want...
How it differs with earlier Generic SDcards is I reorganized the default, Recovery, and Alternate boot choices using j3mm4r's multi-boot bootloader.
I updated Recovery to the newest version CWR 3.0.1.0 modified to write to SDcard instead of Internal/eMMC memory partitions with the help of user stilger. This can be used for Backup and Restore of full cards... as well as installing of CW packages like Google Apps, and Custom CW Rom Install packages you can find for Froyo, Honeycomb Preview and Gingerbread in this forum...
I moved verygreen's CM7 Installer/updater to the Alternate boot choice... In verygreen's thread he uses this as the default Kernal and Ramdisk which gets overwritten by the package you install... thus the need for 2 cards or copying files around to reuse the original... with this as Alternate it doesn't get overwritten and thus is available next time you want to use it... like Install CM7 for the first time... then upgrade to the new Nitely the next day without need for finding and copying files or using 2 cards...
How verygreen's Installer/updater differs from CWR... With vg's installer you place the installable files on the /boot partition... this installer will install SDcard ready or agnostic installables AND will install eMMC designed version CM7 builds and do on the fly conversion to SDcard version during the install seemlessly...
CWR 3.0.1.0 for SDcard will expect the install zip or backup file to be on the 4th/sdcard partition and expects these to be agnostic installs as it doesn't do anything on the fly to make these run on SDcard... It they are built or modifed to run on SDcard thats fine and installing from this Recovery works as would be expected...
I extended the size of the boot partition to have ~120MB free to allow for installing larger images as the prior ~100MB space was too close to currently typical installable Custom Rom packages.
The 4th /sdcard partiiton is created Very small to fit on a 2GB SDcard and really needs to be expanded using Easeus Partition Manager on Windows or an equivalent program on your OS of choice to fit your size choice of SDcard...
I will offer some experience with SDcard here... I bought 10 different manufacturers, and Class/speed cards... I ran disk benchmarks for all and then used the ones that performed best for daily use... Sandisk brand is the most generally faster than the Class it's stamped... A Class 4 beats most brand's Class-6... I wanted the fastest... and settled on buying 8 cards as KingMax Class-10 SDcards, 4 4GB and 4 8GB, from buy.com... these aren't the cheapest cards by far, BUT in this case you DO get what you pay for...
So for daily use I'd reccommend the KingMax 8GB Class-10 cards as I've gotten better than 2000 Quadrant scores running these cards for Froyo, Honeycomb, and CM7 Gingerbread installs... this is as good or better performance than most scores I've seen from folks running the same installs on Internal/eMMC...
Even 400M seems excessive for mostly zero filled card.
Basically your target compressed size should be the size of all real files on the card + a little bit.
Make sure you zero the extra fat partition and boot partition free space too as plenty of random data might be there.
verygreen said:
Even 400M seems excessive for mostly zero filled card.
Basically your target compressed size should be the size of all real files on the card + a little bit.
Make sure you zero the extra fat partition and boot partition free space too as plenty of random data might be there.
Click to expand...
Click to collapse
THANX...
I did think of that... after the fact... but the free space on those 2 partitions is <150MB which at the expected 4 to 1 compression I'm seeing would only save another ~35MB... so I didn't bother try and re-upload.... as less than 10% expected improvement... IF I need to upload another version I will include this in that version though...
I'd tend to agree with you on "your target compressed size should be the size of all real files on the card + a little bit." but the actual Used space is ~100MB, Total Space = 2GB, Unused space is thus around 1.9GB... so compression (1/5-1/4) really STINKS on this... but I'm not sure why as I've tried winzip and gzip with multiple levels of compression...
Thank you so much for the explanation, jtbnet, but it's hurting my noob brain!
It seems that most people like CM7 with Tablet Tweaks by mad-murdock. Could someone detail for me (step by step) the simplest way to get that in a bootable 2 GB SD card, preferably without involving a second card, and without touching the eMMC at all? I can't tell whether this project does that or not (and if so, how) or whether I should stick with racks11479's approach, or what. My apologies; I'm not usually this far behind.
Edit: I forgot that mad-murdock's Tablet Tweaks were already merged. So I guess just make that "CM7".
xdabr said:
Thank you so much for the explanation, jtbnet, but it's hurting my noob brain!
It seems that most people like CM7 with Tablet Tweaks by mad-murdock. Could someone detail for me (step by step) the simplest way to get that in a bootable 2 GB SD card, preferably without involving a second card, and without touching the eMMC at all? I can't tell whether this project does that or not (and if so, how) or whether I should stick with racks11479's approach, or what. My apologies; I'm not usually this far behind.
Edit: I forgot that mad-murdock's Tablet Tweaks were already merged. So I guess just make that "CM7".
Click to expand...
Click to collapse
You *should* be able to do the following with the image provided in this thread on your 2gb card:
1. Download image from this thread (currently v5)
2. Write this Image to your card (I use win32diskimager or dd in linux)
3. Once the card is written place the cm7 zip in the root of the boot filesystem. (Should be a drive letter with boot in the name with files like uImage uRecImg etc on it)
4. Place the gapps zip of your choice in the same "boot" filesystem.
5. Place sdcard in nook.
6. Turn on nook.
7. Hit N button when it says Press any key for menu.
8. Choose SD and Alternate as your boot option
9. Let it finish.
10. Boot into CM7
I did not provide you all the links but the CM7 nook image in mad murdocks Tablet Tweaks thread or the latest nightly for the nook (next nightly build should have Tablet Tweaks) should work. The gapps zip is also available at the CM site.
FYI - This image is based off the work of verygreen's thread: http://forum.xda-developers.com/showthread.php?t=1000957
Hopefully this will get you going.
Perfect recipe; thank you, stilger! Just what I (and likely lots of others) needed to know. I'll probably try this tonight.
I love this place.
stilger said:
You *should* be able to do the following with the image provided in this thread on your 2gb card:
1. Download image from this thread (currently v5)
2. Write this Image to your card (I use win32diskimager or dd in linux)
3. Once the card is written place the cm7 zip in the root of the boot filesystem. (Should be a drive letter with boot in the name with files like uImage uRecImg etc on it)
4. Place the gapps zip of your choice in the same "boot" filesystem.
5. Place sdcard in nook.
6. Turn on nook.
7. Hit N button when it says Press any key for menu.
8. Choose SD and Alternate as your boot option
9. Let it finish.
10. Boot into CM7
I did not provide you all the links but the CM7 nook image in mad murdocks Tablet Tweaks thread or the latest nightly for the nook (next nightly build should have Tablet Tweaks) should work. The gapps zip is also available at the CM site.
FYI - This image is based off the work of verygreen's thread: http://forum.xda-developers.com/showthread.php?t=1000957
Hopefully this will get you going.
Click to expand...
Click to collapse
THANX...
I'd add one step which is to use something like Easeus Partition Manager to extend the /sdcard partition to fill your larger than 2GB card between #2 and #3... as if only using the 2GB card image /sdcard is Only ~30MB big ... mostly just a Fat32 FS placeholder to allow extending...
jtbnet said:
THANX...
I'd add one step which is to use something like Easeus Partition Manager to extend the /sdcard partition to fill your larger than 2GB card between #2 and #3... as if only using the 2GB card image /sdcard is Only ~30MB big ... mostly just a Fat32 FS placeholder to allow extending...
Click to expand...
Click to collapse
You should take and add this step by step process to the first or second post.
Maybe even add links etc... Dunno. Up to you.
stilger said:
You should take and add this step by step process to the first or second post.
Maybe even add links etc... Dunno. Up to you.
Click to expand...
Click to collapse
THANX... Added your steps as an example in the Second post...
OK, I had used the flashing_boot.img posted here to repartition my nook. However someone in that thread found it difficult to create a ext3 partition to add the necessary files
So here is a linux shell script to create that image with B&N Stock 1.4.2 that you can use to re partition and restore your nook tablet it will work on both 8 and 16GB versions. It will format all partitions and force you to unrooted stock 1.4.2
files are at devhost now
http://d-h.st/users/meghd00t/
It is better for you to make your own image, the script has been amended to download the files if they are missing in the current directory.
Instructions to use.
download the attached mkrepartimg.sh.gz
gunzip mkrepartimg.sh.gz
chmod 755 mkrepartimg.sh
if you already have 1.4.2 update put it in the same folder
ubuntu users check if you have kpartx installed
apt-get update && apt-get install kpartx
sudo ./mkrepartimg.sh
this will download the necessary files and create the repart.img
write the repart.img to a sdcard with dd
power off the nook completely (hold power button for 30 sec)
insert the SD card you made into the nook
force boot from USB -
either boot with n and power, wait until it turns on and off then boot normally
or
power off completely and power on by connecting usb cable to PC or charger
screen will show 3 red x and after some time it will show a green check
now remove the sd card, reboot and allow it to do the factory restore.
and you are done.
Windows users go here - http://forum.xda-developers.com/showthread.php?t=1663836
I have had a few questions about the size of media partition.
You can change it very easily with sgdisk which was in my myrecovery.img and also in succulents CM 7.2 cwm images I have attached a script to download and make a suitable cwm image which you can run and then dd onto a sdcard boot into that cwm and issue these commands in a adb shell
for further details read this
Code:
sgdisk -e /dev/block/platform/mmci-omap-hs.1/mmcblk0
This will write the secondary gpt label and remove the parted prompt found error fix?
Code:
sgdisk /dev/block/platform/mmci-omap-hs.1/mmcblk0 -d 11 -d 10
first delete partition 10 & 11 media and userdata
Code:
sgdisk /dev/block/platform/mmci-omap-hs.1/mmcblk0 -n 0:0:+12G -n 0:0:0
sgdisk /dev/block/platform/mmci-omap-hs.1/mmcblk0 -c 10:media -c 11:userdata
now create both with the size you need for media (change +12G to whatever) and userdata will use the rest. and set the name of the partition
After that trigger a factory reset and that will format the partitions again or if you are already running something else first take a nandroid backup in cwm before you change the partitions and format these two in adb like this
Code:
mkdosfs -F32 -n MyNook /dev/block/mmcblk0p10
make_ext4fs -L userdata /dev/block/mmcblk0p11
again you will need my myrecovery cwm or succulents cwm these are the only ones with make_ext4fs
after formatting you can restore your nandroid backup
PS
No questions in PM please. I will not respond.
MLO - b&n 1.4.2
u-boot.bin - b&n 1.4.2
cyanoboot - http://forum.xda-developers.com/showthread.php?t=1522226
boot - clockworkmod http://forum.xda-developers.com/showthread.php?t=1466583
altboot - b&n flashing_boot.img modified http://forum.xda-developers.com/showthread.php?t=1554039
credits
fattire for cyanoboot
loglud for the page on hacking the kernel & boot.img
Indirect for the clockworkmod
AdamOutler for the ubuntu restore and the idea
jmeyerhead for the b&n flashing_boot.img
tselling for the partition hacks
succulent for sharing the device tree and answering all my questions on building a recovery and finally accepting all the patches.
and all the others on xda who have shrared all their knowledge and ideas that made this possible
PROs
simple no adb required
follows B&N partition table properly
keeps the Nook serial and other Information
works with all 8GB & 16GB tablets
CONs
inflexible about the 1.4.2 upgrade (otherwise no 8GB support)
You will get whatever B&N standard partition table is allowed for you device. Adam Outler suggested that I don't deviate from the B&N standard to keep the unbrick safe
This is a great idea but I can't get it to go after multiple tries (different SD cards, different boot methods, etc). I suspect it may have to do with how the SD card is being formatted; is there a trick to this?
Edit: Do I need stock recovery & not CWM?
meghd00t said:
so to simplify matters for all those who have bricked their nook here is my solution
.....STUFF SNIPPED.....
Format SDCARD < 2GB, Fat32 LBA Boot
copy the contents of this sdcard/ directory on to the root of the card
Click to expand...
Click to collapse
How do we do this step ?? I mean I know you want us to format our SDCARD 2GB or bigger as Fat32 LBA Boot. BUT How do you go about doing that ?? What do you use ??? ADB ? DOS/Win ?
Thanks !
Thibor69 said:
How do we do this step ?? I mean I know you want us to format our SDCARD 2GB or bigger as Fat32 LBA Boot. BUT How do you go about doing that ?? What do you use ??? ADB ? DOS/Win ?
Thanks !
Click to expand...
Click to collapse
Unfortunately, I can only tell you how to set it for boot and LBA in Linux or with a GParted Live disc. You may be able to do it with "Parted" via ADB. I'll try it and post back shortly.
my linux doesn't want to recorgnize adb when I'm in clockworkmod
If you're in Linux just use GParted to format the card and set the flags once the volume is created.
For those running Windows you can do this via ADB (I have to boot CWM and then go into ADB for Parted to work). This comes up often but I couldn't find a how-to on it to link to... kind of surprising that it wasn't already out there.
Format your sd card first... just personal preference so I can be sure the empty disk I'm looking when in parted is the one I want to adjust.
Open CMD as Administrator
(Type and execute what's written in blue below. Read comments in parenthesis but don't type them.)
parted /dev/block/mmcblk1
print
(verify that the disk listed is the correct one, there should only be 1 partition #1 it should be FAT32)
set 1 boot on
set 1 LBA on
print (look at the right under "flags" to be sure that "boot" and "LBA" are now set.)
quit
exit ADB as usual or continue as needed.
EDIT: Oh and SDCARD < 2GB means 2GB or smaller. You may have issues trying to use a card larger (this includes larger cards which are partitioned smaller).
Ok here is a sdcard image that you should be able to use with dd or win32diskimager to make the sdcard. This will work on any card 512MB or larger. I have made a 500MB partition and added the necessary files, you will still have to add the factory.zip (b&n 1.4.2 update)
http://dl.dropbox.com/u/64885133/meghd00t-r4.zip
and
http://dl.dropbox.com/u/64885133/meghd00tr4-sdimg.zip
Awww.... I thought the disc was easy enough to set up.
I've been playing around with this and it works fine. I found it responds the same way it did for me when I did the reformatting the past couple times: The "DO NOT TURN OFF YOUR DEVICE" warning doesn't go away. There's just a red X in the upper right corner which indicates it is working and not safe to turn off the device and after a minute or two it is replaced with a green check mark at which point you press and hold the power button for about 10 seconds to turn off the device. Remove the card and power back up.
The first time I ran this I was greeted with the notice that there was a problem and to restart the device and if the error occurs again to contact B&N support. Upon restarting it went through the first boot process normally.
I've been asked about the results from the former thread. I'll host a copy of the image file I've used to repartition as they're doing at B&N (5.50GB/7.45GB) with 1.4.0. I'll host it for a week or so, but it's 270MB so if someone wants to put it on a torrent of whatever, feel free.
Do a CWM backup first. Verify the MD5 checksum of the img file inside of the zip file after you download the image, before you burn it to make sure it's not corrupt... that would suck. MD5 = ae1d489a3b33f3e69360cc8e9c0bc096 You can check the checksum in Windows using a free app called WinMD5Free and you can burn the image with Win32DiskImager. This image does NOT load a boot manager. It boots straight in and repartitions and restores 1.4.0 with no prompts. Don't boot with this image if you are ready.
ONLY FOR 16GB NTs!!! --> http://www.fadingworld.com/NT/repart.img.zip
All credit for getting this img figured out (particularly the whole getting the NT to boot after the repartitioning) goes to meghd00t and probably the folks he thanks too.
EDIT: Finally compressed the img file and uploaded it so it's down to 270MB. This is a COMPLETE image, you don't need to change anything as long as you're fine with 1.4.0 and B&N's new partitioning scheme.
hmm the image doesn't work on CM7 do you need to have the stock rom installed ?
Pete1612 said:
hmm the image doesn't work on CM7 do you need to have the stock rom installed ?
Click to expand...
Click to collapse
I don't even need to look at the script to be quite confident that there is a check to ensure that the device "qualifies" before continuing... This is all based on B&N's own reflash system. These cards flash your NT with one version or another of the stock OS... you should revert to 1.4.0 - 1.4.2 first... They will not leave CM7 intact.
EDIT: Now megdh00t's image should still boot into cyanoboot and be able to load CWM. The image I've supplied just boots and runs the partitioning script immediately. If you're trying meghd00t's and it's not booting at all then verify the download and try booting from the card by turning off the Nook, insert the card, plug in the factory charge cable and that will turn it on and it should boot from the SD.... if that still fails try a different card. I keep a few 1GB and smaller SDs on hand just because larger SDs are problematic sometimes.
Thank you for the image. Quick ?s. Will this image work for a NT, with CM7 running on SD card only, stock B&N 1.40? And can I use this without hooking up the NT to a computer? If so, do I just pop the SD card with the image on it and viola I am repartitioned and still have 1.40? Any help will greatly be appreciated by this newby chick. . .
I've used the image I posted on two NTs now and I've tried both methods numerous times on my NT. I haven't had a single problem (except for when I do it on purpose). Both of the NTs were stock, rooted NTs. I don't have CM7 and have little interest in setting it up so I can only certify that this does work on a factory NT. If you have an alternate boot manager or CWM or CM7 flashed internally then you may very well have problems. If you're booting straight from SD and nothing has been changed in the NTs internal memory then it should run with any problem.
I've used the image you kindly provided CRE. It is stuck on the "Please Do NOT Turn Off Your Device. Installing New Software..."
There is a picture of a Nook in the center and a green check mark in the top right corner. How long should this take (I'm assuming it reboots itself after finishing)?
Edit:
I found your post from the previous thread:
"When I was ready to go it took several times of pressing the power button (I probably pressed every combination possible out of desperation) before it came to life. It booted up and came to the "DO NOT TURN OFF YOUR DEVICE" (or similar text) screen and a red X was in the upper right corner. Where I'm used to seeing this message go away and the Nook prompting me to eject my card before turning the device off all that happened was it remained on the warning screen but the red X was replaced with a green check mark after a couple minutes. Being paranoid, I probably left it on that screen for 30+ minutes before I finally forced it off, took out the card, booted into CWM, restored my backup image and now I'm all set! (My serial number was uneffected despite all my clumsy efforts to kill this NT). I had 1.4.0 installed and this image was made using files from the 1.4.0 acclaim_update.zip."
Thanks to you, meghd00t, and all others involved!
CRE said:
...If you have an alternate boot manager or CWM or CM7 flashed internally then you may very well have problems.
Click to expand...
Click to collapse
Yes, it does seem to be a problem, as it does not execute the scripts from the boot card.
Hey, I have an 8gb NT sitting on my desk which is bricked. I'll check this out tonight. If it works, then for sure I'll request that my Ubuntu Recovery be removed and yours take its place in the stickies. I just ask that you consider making one for the stock partition tables.. that way it can be official stock and not just an unbrick.
Cre- re repartion image
CRE, GOT YOUR P MESSAGE, NOT SURE HOW TO ANSWER PLY, BUT I WANTED TO THANK U. YES I AM BOOTING FROM SD WITH STOCK 1.4O. BUT I TAKE IT THAT I MUST CONNECT THE NOOK TO A COMPUTER, WHICH MUST BE DONE COVERTLY.:cool
AdamOutler said:
Hey, I have an 8gb NT sitting on my desk which is bricked. I'll check this out tonight. If it works, then for sure I'll request that my Ubuntu Recovery be removed and yours take its place in the stickies. I just ask that you consider making one for the stock partition tables.. that way it can be official stock and not just an unbrick.
Click to expand...
Click to collapse
Thank you for the feedback.
I have remade the images as per your instructions. Now you will get exactly what B&N gives you Only changes are in using the vfat portion of the sdcard to hold the factory.zip.
If you have some hosting then perhaps the original image with the ext3 partition for the factory.zip as per the details here http://forum.xda-developers.com/showpost.php?p=23946133&postcount=21 would also work. (now image attached here as bn_142_factory_recovery.zip )
Please review and let me have your comments
http://dl.dropbox.com/u/64885133/READMEv2.txt
http://dl.dropbox.com/u/64885133/meghd00tr4-v2.zip
http://dl.dropbox.com/u/64885133/meghd00tr4-v2-sdimg.zip
http://dl.dropbox.com/u/64885133/bn_142_factory_recovery.zip
Error 404
I try to download file: bn_142_factory_recovery.zip from the link above, but get Error 404. Please, put this file back. I am still try to unbrick Nook Tablet 8Gb. Thanks a lot!
hang on for a bit its uploading to dropbox very slowly, OK have at it it has uploaded now.
Thanks! I got it!
Hi,
I have a working rooted 8gb nook tablet. The tablet has stock recovery installed on it and I don't think I want to change it to cwm at this point, unless I absolutely have to. My question is -- can I use this method to backup my current ROM in case I do mess something up (like deleting build.prop file for instance)? The problem that I have is that the sd card ends up with only 50mb of free space after burning the image onto it and that is obviously not enough for the backup. I tried partitioning the card and creating an ext2 allocation (perhaps I need to use a different kind?) in addition to the tiny 50mb one, but cwm doesn't seem to recognize it and still tries to backup into the tiny space.
I would greatly appreciate any help.
Thank you.
Resize the partition of the SD card using a partition manager, or format the card and put these files on it (in root).
Forgot to mention in my original post that I did try resizing the 50mb partition to 1gb, but then the tablet just stopped booting at all. I had to take out the card and wait for a minute or two before it would start booting normally again.
I will try your files now. Thank you for quick response!
Nope, that did not work, unfortunately. It just booted normally, not from the sd card. But isn't the whole point of burning that image is to make the card into a 50mb one? I don't understand all the technicalities, but that seems reasonable, why else would they make it particularly 50mb large? And resizing the partition doesn't lead me anywhere either, as I mentioned above.
Maybe someone could point me in the right direction?
Right. So, the partition has to be checked as active if using MTP or flags should be on if using the other one. And the magical 50mb size allocation don't matter after all. Gotcha.
So, as the title suggests, I want to take my recovery image SD card that sitting around at 48MB and reformat it back to it's original size of 16GB. I've heard that we're supposed to use SDFormatter, or EaseUS Partition Master, or ADB, or Linux or use the Nook....
On the subject of using the Nook, turns out you CAN use it to format it to somewhere closer to the original size. Nook put it around 14.4G, with the card being a 16G. Is this normal?
Needless to say, I'm a bit lost. I'd like it back so I can put things back on it, or perhaps re-partition so I can have that CWM section yet also have access to my data, without it appearing to be a fraction of it's actual size.
Verfassergeist said:
So, as the title suggests, I want to take my recovery image SD card that sitting around at 48MB and reformat it back to it's original size of 16GB. I've heard that we're supposed to use SDFormatter, or EaseUS Partition Master, or ADB, or Linux or use the Nook....
On the subject of using the Nook, turns out you CAN use it to format it to somewhere closer to the original size. Nook put it around 14.4G, with the card being a 16G. Is this normal?
Needless to say, I'm a bit lost. I'd like it back so I can put things back on it, or perhaps re-partition so I can have that CWM section yet also have access to my data, without it appearing to be a fraction of it's actual size.
Click to expand...
Click to collapse
14.4 sounds about right for a 16G card, they're never quite they're true size, due to partition data, etc.
If you look in this forum, a bit further down, I posted a zip file of the CWM files, and if you format your card, copy the CWM files to the root, and flag it as bootable with parted, your NT should be able to boot from it.
lag0matic said:
14.4 sounds about right for a 16G card, they're never quite they're true size, due to partition data, etc.
If you look in this forum, a bit further down, I posted a zip file of the CWM files, and if you format your card, copy the CWM files to the root, and flag it as bootable with parted, your NT should be able to boot from it.
Click to expand...
Click to collapse
+1 lag0matic
fat32 is ... well fat... the partition tables and header info per sector take a good heaping bite right off the top. my PNY16gb in windows and linux formats to 14.7 gigs. so your right on the money for formatted capacity.
http://en.wikipedia.org/wiki/File_Allocation_Table
Regards!