ArchLinuxARM for the leo (HTC HD2) - Native Boot
This is only tested with MAGLDR 1.13 on the T-Mobile US HD2, though there's no reason it shouldn't work on a global one, as NAND isn't touched.
Working:
Wi-Fi (with NetworkManager)
Not Working:
Bluetooth
2D & 3D Acceleration (though kgsl and freedreno drivers are in use, the userland isn't patched/installed/tested yet)
Audio
Installation (to the third partition of the SD card)
This procedure is intended only for advanced users. By providing a 6GB F2FS image, the system will boot reasonably quickly and not run out of space, however, it can't be stored as a file on the internal memory - it has to be a partition of its own because of the FAT32 filesize limit of 4GB.
You will need at least 3 MBR primary partitions on the SD card. The third one must be 6GB or larger. Since F2FS volumes can't yet be resized, any space above 6GB on that partition is useless. When this scheme is created, gunzip the provided root.img.gz and write it to the 3rd partition. Then, make the first FAT32 (if it isn't already), make a directory in root of the FAT32, and put the the linux kernel zImage.
Booting
Select the directory you created as the Android SD directory in MAGLDR and boot the system. There will be no console, and you will get a jumbled screen during boot. Eventually, lightdm will start up and you will be on your way.
Logging in
The username is "arch" and the password is "arch". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
You can try to get reroute audio by modprobing "snd-mix-htc-leo" and setting the mixer settings. The system wasn't set to do this at each boot due to serious issues with the concept of copying a 2.6.32 alsa driver into 3.0 and just compiling - it barely works and has a huge propensity to hang during load.
Read Me
I realize this will be difficult to install for most users. I did not provide commands because I don't want anyone wiping and formatting the wrong disk. Eventually, I'll implement a way to make this installable via image. The initramfs issues with the kernel I'm using will first have to be investigated, and then the ext4 issues will. Since Arch Linux uses systemd, I can barely get it to boot with kernel = 3.0, let alone 2.6.32. All my other ports use 3.4, which already requires patches to work after the introduction of udevd version 217.
Downloads
root filesystem image compressed with gzip: https://drive.google.com/file/d/0B4WUjKii92l2ZTNraFpVb2tHbVE/view?usp=sharing
3.0.101 kernel (thank you to maniacx at github for initially sharing the source): https://drive.google.com/file/d/0B4WUjKii92l2aGdGLUYxMm9KSWM/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_leo
Also available for:
Nexus 7 2013 (flo): http://forum.xda-developers.com/nex...fficial-archlinuxarm-release-n7-2013-t2969301
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
This phone just won't die.
This is what? The 20th OS to run on the HD2?
Hi There Dear friend ...
Hi there Dear @castrwilliam were looking for an OS for my HD2 to use it through Mouse and KB ( USB Host ) is there anyway I can get any os on My HD2 using them ? ( because mine's TS is broken and doesn't work ) ... Thanks in advance
With Best Wishes
Hitman1376
OTG *should* work on this with external power. Bluetooth most likely does not. Do you have an SD card with a 6GiB third partition?
Sure ...
castrwilliam said:
OTG *should* work on this with external power. Bluetooth most likely does not. Do you have an SD card with a 6GiB third partition?
Click to expand...
Click to collapse
I have an 8 GB SDcard ... with external power ? How ? ... Thank in advance
With Best Wishes
Hitman1376
@castrwilliam
Great job!i will download, resize mmc, install, try...
whatever issues you are facing, post them, maybe i can help after squeezing some free time
Main things are issues on the kernel.
When you try to boot with an initramfs that is compressed, you get either "garbage in compressed da" rand the kernel hangs right then - presumably before it even finishes that printk - or "unknown compression algorithm: " and then vorrupted garbage is output. This prevents me from making image boot doable.
I had this problem a long time ago with GCC 4.9 on a 3.4 flo kernel, but I've tried major versions of 4.6 through 4.9 and none get any further. Also, there's a commit upwards of mine that changed the kernel config from using ARM_UNWIND to FRAME_POINTER for debugging. I tried with each.
Also, when you boot with an ext4 rootfs on mmc, any attempt to write to root gets you an Invalid Argument, when the FS is mounted rw... very strange, but somehow I have a feeling it has to do with systemd trying to do something unsupported/untested on 3.0.x midway through boot, and f2fs lets it work either because it doesn't support it anyway, or because f2fs was backported - possibly with features that aren't in the ext4 driver already.
castrwilliam said:
Main things are issues on the kernel.
When you try to boot with an initramfs that is compressed, you get either "garbage in compressed da" rand the kernel hangs right then - presumably before it even finishes that printk - or "unknown compression algorithm: " and then vorrupted garbage is output. This prevents me from making image boot doable.
Click to expand...
Click to collapse
regarding initramfs, we have problems with magldr and 3.0.x kernels, that needs a workaround.
there's a patch for kernel (which you probably have already) for magldr boot, where you need to add 6mb of 00's to initrd.gz (not sure if for initramfs too) in order to boot on magldr
more explained: https://github.com/Gilbert32/androi...mmit/77351b60841f1b53c203b4621ea37ba521fa70a9
wondering why the 3rd partition is not itself formatted to f2fs? It can be done from an f2fs sd recovery.
I can't get this to boot from magldr, I have ~3gb fat32 p1, ~4gb ext4 p2 and 6.4gb ext4 p3
It reboots within about 6 seconds after showing white stripes on screen (just as with boot attempts using 3.0 kernels without the 6mb of zeros in initrd.gz)
I get the attached dmesg
Edit; tried making a file with 6mb of zeros called initrd.gz and putting it in the boot folder on sdcard, but the same thing happens.
feherneoh said:
For me it works with both MAGLDR and cLK
But for cLK I have to do a liveboot from PC using fastboot
EDIT:
Why are you using EXT4 on mmcblk0p3? Seems like that is the problem, as as far as I know f2fs can only be mounted with fs type defined, so probably it will only accept an f2fs partition as root
Click to expand...
Click to collapse
I just assumed it would be ext4 with an f2fs image, no wonder no replies to my first post
will try it with f2fs partition when I have time, thanks
feherneoh said:
just dd the image onto that partition, or format partition, and copy image's contents over
Click to expand...
Click to collapse
Actually I have formatted p3 to f2fs, and am adb pushing it from pc using f2fs sd recovery. It does take time though, been over an hour
Edit; oops it just reported "no space left on device", going to have to resize the partition I think. perhaps f2fs reserves more space than ext4, so needs to be bigger than the 6.4gb which worked when installing to ext4.
feherneoh said:
Don't push the whole image, just the files on it. It should be less than 6 GB, I'm using it from a 4GB card with a 3GB f2fs partition
Click to expand...
Click to collapse
Can't seem to mount the image in windows unrecognised fs
can only think to put the img onto sdcard fat32, loop mount it from f2fs recovery terminal and copy it to p3. Or get Linux on pc.
I just installed this. This is great. Thanks.
Is the display going to be always on?
Deleted... wrong thread
Related
Due to popular demand I have created a size-agnostic SDCard CM7 installer.
Also allows to install unmodified CM7 builds on SD card.
Current version: 1.3
Grab the installer image here:
http://crimea.edu/~green/nook/generic-sdcard-v1.3.img.gz
it's a ~9M image that would unpack into ~130M disk image.
Also note - not all SD cards are created equal. Here is a thread of interest is you have not bought one yet: http://forum.xda-developers.com/showthread.php?p=12964262
Short version: buy Sandisk-branded class 4 microSD cards.
Write the image on your SD card. I tested with 2G, 4G and 8G cards and all worked.
Any uSD card of 1G or bigger in size should work if it is recognized by your nook.
Write on Windows by using WinImage and on Linux/MacOS X by using dd (to the entire device, not one of the partitions. The device name should not have any numbers at the end. The command is something like dd if=/somewhere/generic-sdcard.img of=/dev/sdX bs=1024k)
After done with writing, eject and then re-insert the uSD card into your computer.
Download a CM nightly build from here http://download.cyanogenmod.com/?device=encore (It is recommended to choose -87 nightly or later. If you plan to use prior version for initial install, stick with installer 1.2.1 for a different u-boot version)
Or just use your own update-cm-*-KANG-signed.zip file that is produced if you do your own builds.
The image would correctly detect unmodified CM7 builds and would make necessary adjustments to make them work on SD card.
Put the file to the SD card (there is only one partition). Don't change the name of the file.
unmount the uSD card and insert it into the nook.
Boot from this SD card. It'll boot and will update you on progress.
When it's done, it'll power off.
That's it, you now have CM7 on your SD card.
How to install market and gapps:
After you have booted into the CM7 on SD card for the first time and set up wifi access (important!)
Go to http://wiki.cyanogenmod.com/index.php?title=Latest_Version and at the end there is a table with various google apps versions. Get the one suitable for your cyanogen version (CM7 is the latest for now). The file is named gapps-....zip
shutdown your nook and take the SD card out, insert it into your computer.
Copy the gapps-... file to the SD card on the first partition (titled boot) without changing the file name.
Insert the uSD card back into the NOOK and boot into "Recovery mode" (hold nook N key and then press and hold power until the "Loading..." message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the bootloader "Loading..." 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).
Alternatively if you do not want to fight the timing, boot normally into Android, then from desktop hold power key until a poweroff menu appears, In the poweroff menu choose "reboot", in the next menu choose "recovery" and press "OK". The nook would reboot straight into recovery.
How to update to a new build:
put the new build you want to try on the first partition. (the name must be update-cm-*.zip or cm_encore_full*.zip or just update-*.zip)
Boot from the SDcard in the recovery mode (see above) and the new snapshot would be installed.
The partition layout would be preserved, filesystems are NOT reformatted, so your data should be safe.
Installing other stuff:
Booting in recovery mode would install all files that are named "update-..." and end with .zip The files would then be deleted! Most of the packages should work, but I only tested a subset and not entire syntax of updater script is implemented. Certainly format and delete are not implemented.
OC Kernel installation instructions:
Starting with v1.2.1 there are no special instructions, install normally as described above.
Partition layout for the SD cards depends on size:
Less than 600M - unsupported.
up to 1G cards gets: system of ~300M and data of the rest of space. No FAT partition
2G cards (more than 1G up to 1800M) gets: 300M system, 612M data, rest is FAT sdcard
more than 2G cards gets: 460M system, 975M data, rest is FAT for sdcard.
How to update if you already installed using older version of the installer and don't want to reinstall (understandably):
Get update zip from http://crimea.edu/~green/nook/update-genimage-1.3.zip
Put the zip file as is onto the first partition of your sdcard..
reboot into recovery (triggered by the keys, the reboot into recovery does not work yet).
The new version would be installed and you are done.
You can combine this installation together with updating to .32 kernel in one step. Just put the update-cm file and the update-genimage-1.3.zip to the first partition. Make sure there is still at least 1M of space left!
Changes in 1.3
Install u-boot.bin and MLO loaders if provided.
Fixed a problem that led to overwrite of recovery kernel if a nightly was installed more than once)
(only in full image) updated u-boot to ignore BCB as that was a common source of problems. (that's why this version is not recommended for initial install with older nightlies, those don't provide a more correct u-boot for later operations. It's fine to do the update from older installer release, though)
Changes in 1.2.1
Really fixed dalingrin kernel packages installation
A bit more robust handling of install scripts
Changes in 1.2
Updated to new u-boot from B&N 1.2 update
Ability to obey BCB in eMMC (allows reboot into recovery from CM7)
Hopefully simplified the timing to trigger recovery boots from keyboard
Added support for Dalingrin's kernel update packages
The v1.1 version that is known good to work with 2.6.29 kernel releases is located at http://crimea.edu/~green/nook/generic-sdcard-v1.1.img.gz
This is very cool, thanks! My father bought a nook color after seeing mine, and after hearing what I have been able to get mine to do (thanks to the efforts of all the devs here) he has wanted to play a little more with his. Thanks to you, I have an easy way to set up the SD card and then ship it up to him. I can give him a taste without having to force him to even root his yet. Thanks again!
Very nice! Thanks.
Care to share the dates and differences between your build and say CM's? or perhaps a link to your builds progress?
I know you have done great work with BT, didn't want to get off topic, but I'm curious.
Thanks again.
12paq said:
Very nice! Thanks.
Care to share the dates and differences between your build and say CM's? or perhaps a link to your builds progress?
I know you have done great work with BT, didn't want to get off topic, but I'm curious.
Thanks again.
Click to expand...
Click to collapse
I did not work on BT (other than helping with testing), so I don't claim any credits there.
The difference between standard build and my build so far is only that my build has patched init files to boot from SD right in the zip file. (CM7 checkout as of today ~12pm), it was only created for testing, before I rolled the code that could update vanilla builds to work on SD cards.
You can use unmodified CM7 nightlies with this sdcard image now. The image itself does not contain any CM7 code, you need to copy zip file with it after writing the image to the SD card, but before attempting to boot.
Verygreen, I believe you have won the game. Congratulations!
Ah yes, I stand corrected, you created the first CM7 sd bootable for testing of BT.
Thanks again for your time on this latest project!
First off, this works very well! Thanks!
Now, after getting CM7 running on the sdcard, I plug the device into the usb port on my computer and instruct it to mount the sdcard. But, instead of the sdcard partition being mounted, the emmc partition is mounted.
Was that intentional or is it a bug?
Thanks
Thanks very easy to setup!
atomclock said:
First off, this works very well! Thanks!
Now, after getting CM7 running on the sdcard, I plug the device into the usb port on my computer and instruct it to mount the sdcard. But, instead of the sdcard partition being mounted, the emmc partition is mounted.
Was that intentional or is it a bug?
Thanks
Click to expand...
Click to collapse
New code in CM7 actually should cause both internal MMC AND sdcard to be mounted.
That is unless you used 1G sdcard, 1G sdcard does not have any mountable free space and then you'd only see emmc content as mountable.
verygreen said:
New code in CM7 actually should cause both internal MMC AND sdcard to be mounted.
That is unless you used 1G sdcard, 1G sdcard does not have any mountable free space and then you'd only see emmc content as mountable.
Click to expand...
Click to collapse
I'm using an 8Gb sdcard and I can access both the emmc and sdcard partitions through ADB but only the emmc partition is mounted.
So, I just need to try this with a different nightly build until I find one where the issue is corrected?
Well, I tried it with both cm_encore_full-25 and cm_encore_full-26 and still only the emmc partition is mounted.
atomclock said:
I'm using an 8Gb sdcard and I can access both the emmc and sdcard partitions through ADB but only the emmc partition is mounted.
So, I just need to try this with a different nightly build until I find one where the issue is corrected?
Well, I tried it with both cm_encore_full-25 and cm_encore_full-26 and still only the emmc partition is mounted.
Click to expand...
Click to collapse
As long as everything is mounted internally I don't think my changes broke anything else, so if there is a bug it's in the CM7 build itself.
I don't actually mount my nook on the computer, so I don't even know how to enable it by default come think of it.
I just know there was an ongoing work in this area to allow simultaneous mounting of multiple volumes and I heard it was already included, though I am not 100% sure about that.
To verygreen:
Well, I'm certainly doing something wrong here:
1. Using Win32DiskImager release 0.2 r23, i burnt my 2 GB with your generic.... .img image.
2. Copied your update.... .zip (on a second attempt an original cm_encore... .zip, plus gapps-GB-20110307-...zip, as installer was asking for it, at least to inflate), now I suspect your "put" is not equal to my "copy".
3. Tried to boot, enjoyed the penguin and boot scroll, but after everything was finished and prepared to "really" boot the boot was executed from my eMMC instead.
aludal said:
To verygreen:
Well, I'm certainly doing something wrong here:
1. Using Win32DiskImager release 0.2 r23, i burnt my 2 GB with your generic.... .img image.
2. Copied your update.... .zip (on a second attempt an original cm_encore... .zip, plus gapps-GB-20110307-...zip, as installer was asking for it, at least to inflate), now I suspect your "put" is not equal to my "copy".
3. Tried to boot, enjoyed the penguin and boot scroll, but after everything was finished and prepared to "really" boot the boot was executed from my eMMC instead.
Click to expand...
Click to collapse
Yes, the automatic reboot boots into eMMC for now, I am looking into it.
So just reboot again with the card in.
also, don't put gapps on the card at the first try. This combination does not boot for me into the desktop for some reason that I did not get to the root of. Possibly because it want internet connection setup that still is not if you try it on your first boot.
Thanks verygreen! This is a fantastic build! I was able to quickly and easily install this on my sd card.
Thanks again!
verygreen said:
Yes, the automatic reboot boots into eMMC for now, I am looking into it.
So just reboot again with the card in.
also, don't put gapps on the card at the first try. This combination does not boot for me into the desktop for some reason that I did not get to the root of. Possibly because it want internet connection setup that still is not if you try it on your first boot.
Click to expand...
Click to collapse
Somehow I went into non-booting phase, lol. My guess is after booting into my rooted Eclair with bookmarks-and-other-stuff-to SD I've got me an SD card not really good for "second" boot. Just have no idea what Eclair might do to that EXT4.
Anyways, repeated the experiment, now with pressing Power for >5 sec. Has booted into CyanogenMod 7 without a problem.
Can't do whatever testing: missing GAPPS very mucho! Please, Mr. verygreen, compile it into your image. In any case, I'm not really interested in swapping nightlies on this card -- by the last commits they didn't change much/significantly since n18. Just a static SD image of CM7 n26 + latest (03072011) Gapps will be a very desirable "mod" of yours. In any case you did exactly that (minus Gapps) for n17. Sure, there's a complete procedure of building SD image, but it's obviously much better followed when with a Linux box, and I don't have it.
aludal said:
Somehow I went into non-booting phase, lol. My guess is after booting into my rooted Eclair with bookmarks-and-other-stuff-to SD I've got me an SD card not really good for "second" boot. Just have no idea what Eclair might do to that EXT4.
Click to expand...
Click to collapse
Supposedly nothing. I routinely boot into eclair and then insert CM7 sdcard and it's fine.
aludal said:
Can't do whatever testing: missing GAPPS very mucho! Please, Mr. verygreen, compile it into your image. In any case, I'm not really interested in swapping nightlies on this card -- by the last commits they didn't change much/significantly since n18. Just a static SD image of CM7 n26 + latest (03072011) Gapps will be a very desirable "mod" of yours. In any case you did exactly that (minus Gapps) for n17. Sure, there's a complete procedure of building SD image, but it's obviously much better followed when with a Linux box, and I don't have it.
Click to expand...
Click to collapse
I can't distribute gapps, like I said
Well, until I figure out why recovery boot does not work what you can try to do is this:
after initial install was successful (and you setup your wireless), power off the nook, get the sd card.
Download gapps-gb-...zip and put it on the first partition.
move the uImage file to uImage.bak and uRamdisk to uRamdisk.bak.
Copy uRecImage to uImage and uRecRam to uRamdisk.
boot with the resulting image. It should say that it found the gapps archive and unpack it.
After it flushes caches and reboots, power off, put the sd card back into the computer
move uImage.bak to uImage and uRamdisk.bak to uRamdisk
boot off the card again, hopefully the gapps are working after that.
Please let me know if any problems arise.
verygreen said:
Supposedly nothing. I routinely boot into eclair and then insert CM7 sdcard and it's fine.
I can't distribute gapps, like I said
Well, until I figure out why recovery boot does not work what you can try to do is this:
after initial install was successful (and you setup your wireless), power off the nook, get the sd card.
Download gapps-gb-...zip and put it on the first partition.
move the uImage file to uImage.bak and uRamdisk to uRamdisk.bak.
Copy uRecImage to uImage and uRecRam to uRamdisk.
boot with the resulting image. It should say that it found the gapps archive and unpack it.
After it flushes caches and reboots, power off, put the sd card back into the computer
move uImage.bak to uImage and uRamdisk.bak to uRamdisk
boot off the card again, hopefully the gapps are working after that.
Please let me know if any problems arise.
Click to expand...
Click to collapse
I just tried following your directions for installing the gapps zip file. After renaming the uImage and the uRamdisk files the nook boots to your recovery with the penguin shows up with the follow:
Populating /dev using udev: done
Initializing random number generator....done
modprobe: chdir (2.6.32.9): No such file or directory
Starting network...
Detected Standard B&N nook layout, emmc first
It appears the SD card is already properly formatted
Skipping format
Mounting /dev/mmcblk1p1 as /boot
Looking for the install images....
Initial Install files not found
Please download it from nook.linuxhacker.ru
and put on first partition of this SD card
the name should start with updatei-cm and end with .zip
Then the cursor just sits. No installation of the .zip file. Do I have to have the original cm zip file on the sd card with the gapp zip file? I thought it was posted that doesn't work.
Also thanks for the great work on this so far.
Absolutely Fantastic and pain free. You have done a great service.
Thanks
verygreen -
Would this work with an Android 3.0 Honeycomb Preview build, instead of a CM7 build ?
Modra76 said:
I just tried following your directions for installing the gapps zip file. After renaming the uImage and the uRamdisk files the nook boots to your recovery with the penguin shows up with the follow:
Populating /dev using udev: done
Initializing random number generator....done
modprobe: chdir (2.6.32.9): No such file or directory
Starting network...
Detected Standard B&N nook layout, emmc first
It appears the SD card is already properly formatted
Skipping format
Mounting /dev/mmcblk1p1 as /boot
Looking for the install images....
Initial Install files not found
Please download it from nook.linuxhacker.ru
and put on first partition of this SD card
the name should start with updatei-cm and end with .zip
Then the cursor just sits. No installation of the .zip file. Do I have to have the original cm zip file on the sd card with the gapp zip file? I thought it was posted that doesn't work.
Also thanks for the great work on this so far.
Click to expand...
Click to collapse
Seeing the same. Also tried naming the gapps file "update.zip", to no avail.
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...
Hey guys im a bit frustrated right now:
ive created the partitions just like in this guide:
http://forum.xda-developers.com/showpost.php?p=22201029&postcount=43
Ive got 2x Ext4 partitions and an active primary fat32 with about 100megs on it. You can find some screenshots in the attachments.
The Problem is if i restart my nook it doesnt pop up with cwm, it just normaly boots.
Did i forget something?
To make it boot you need to active the LBA flags, but i think 7. Right click on the new Primary partition and make sure "Set Active" is selected from the Modify submenu step is the equivalent of LBA flags in gparted ubuntu but i could be totally wrong. That is an important step. That is the hint
~ Veronica
yea i have done that, next to the "Primary" it says "active" so yeah..
Try rebooting the NT with the USB cable attached to the computer. This has worked for a few people.
yea tried that to but didnt change anything :/
That being the case, I'm sorry to say that you probably have a messed up partition, flag or something else is wrong with the SD card or it's structure.
I would recommend (although it is more work) that you try the Linux Partition method. The additional work will come from having to find a bootable version of Linux.
I created a brief outline of various methods HERE. Perhaps you could one a go and use Gparted instead of Windows to partition the SD.
It's worth a shot.
thanks ill try tomorrow
EDIT: ignore post.
Sent from my BNTV250 using Tapatalk
well i tried again to put these files on, this time using ubuntu and it still doesnt boot. ive setted the flags and put the files from http://forum.xda-developers.com/showthread.php?t=1446987 into my "root" partiotion which has the boot flags and so on but it still doesnt boot cwm. Do i need to press any keys while booting?
My Nook Tablet is rooted btw, should i do a factory reset and maybe make a movie? I really dont know what more i can do
Try the following (Linux) to unzip the files and get them on the SD. This could be the problem. Simply opening them and dragging them might not properly decompress them. Thank you to CelticWebSolutions for the following steps which I copied from the CM7 Rom Thread.
Open a terminal window and issue the command:
sudo file-roller
You will be asked for your password and after that a zip software window will open up, click open open and find the file "NT-CWM-SD.zip".
Drag all the files form this archive into your newly created system partition on your sd.
This can take a couple of minutes to actually complete so be patient, often it looks like it's finished but it's still copying in the background.
Close all windows and right click on your SD card on the desktop and select to "safely remove drive" if files are still writing to the disk it will warn you and the warning windows won't disappear until the files have finished writing to you SD.
Make sure you leave the SD in there until this process has finished otherwise your card probably won't work.
do you mean system partition or boot partition?
Edit:
my created partitions are all primary:
first partition with the cwm files on it: 50MB - Primary - FAT 32 - boot and lba flag
second partition: nothing on it - 2000MB - Primary - EXT4 - no flags
third partition: nothing on it - 2000MB - Primary - EXT4 - no flags
Pain12345 said:
do you mean system partition or boot partition?
Click to expand...
Click to collapse
Boot. My bad on choice of words. Bottom line is the card should look the same as the first one you tried. I'm only trying to insure that the files get extracted properly.
Also, to eliminate possible variables that may be causing yourissue, make sure the USB cable is plugged in when you try to boot.
Fingers crossed.
yea copied the files like you said and it still doesnt work. The nook does start and instantly boots "nook reader" not cwm. I really dont know what mroe i should do, i might record a movie if im home.
While booting the nook i have connected the usb cable
Thats how my partitions look like:
first partition with the cwm files on it: 50MB - Primary - FAT 32 - boot and lba flag
second partition: nothing on it - 2000MB - Primary - EXT4 - no flags
third partition: nothing on it - 2000MB - Primary - EXT4 - no flags
Edit2:
i didnt fill the sdcard with zeros, should i do this b4 partitioning?
Also my Nook is rooted, does this matter?
Indirect's APK?
I couldn't get the SD card method to work either and then I found Indirect's APK and that worked perfectly, just a thought... It's in the development section.
Really trying to help you here. Honestly I have never used the method in the actual CWM thread but I have successfully on two occasions created bootable SD cards. It is my understanding that it is the way the card is partitioned that tells and allows the system to "boot" from it. That said I have copied the instructions from the CM7 Rom thread below which use the Linux GParted partitioning method. Not having the SD card setup properly is the only thing I can think of to help at this point besides perhaps that you have a bad card. Try the below (which it sounds like you already have) just to be 100% sure the card is setup properly.
Delete all partitions on your SD card first using GParted and use the following
------------Thanks CelticWebSolutions--------------------
Open GParted select your SDcard in the top right hand side of the window.
Select create partition table form the device menu select the empty space on the newly wiped SD card and click the paeg icon with a green plus on it, a window will appear with some boxes to fill in, change the box that says New Size (Mib) to 50, Change file system to Fat32 and write boot in the label., then click add.
Again click on the unallocated space and add another partition as around 2000(MiB) as EXT4 and label it as system (LandMaster Note: Not needed for CWM only)
Add a 3rd partition in unallocated space again of about 2000(MiB) EXT4 and label it as data. (LandMaster Note: Not needed for CWM only)
now you have three partitions waiting to be created click the green tick to apply your changes
Once changes have applied right click on boot and select the menu item 'Manage Flags', tick boot and lba and close the window, your SDCard is now ready to get it's data for it to work
-------------------------------------------------------
You DONT even need the 2nd (system) and 3rd (data) partition as outlined above if all you want is a bootable CWM. Just one (I used 74MB) MS-DOS (FAT32), Active Partition with "boot" and LBA" flags set.
Lastly, since you are rooted you could always flash the internal recovery partition with CWM using the method in This Thread and get into CWM by clicking reboot recovery from within the app.
I never did ask .... What is your ultimate goal?
I spend a few more hours to it and it still doesnt work. Via the app i can run cwm but only via the app. The goal is that i have a working recovery sd card if i brick my nook..
I installed ubuntu on my computer and i did exactly the same steps like you have posted but it wont work. Ive also tried multiple other sd card but that didnt change anything
Maybe any development settings on the nook that i should change?
As i live in germany would maybe anyone of u sell me a working sd card with cwm on it so i can test?
Pain12345 said:
I spend a few more hours to it and it still doesnt work. Via the app i can run cwm but only via the app. The goal is that i have a working recovery sd card if i brick my nook..
I installed ubuntu on my computer and i did exactly the same steps like you have posted but it wont work. Ive also tried multiple other sd card but that didnt change anything
Maybe any development settings on the nook that i should change?
As i live in germany would maybe anyone of u sell me a working sd card with cwm on it so i can test?
Click to expand...
Click to collapse
Thats what I thought and it is a good plan. Unfortunately I'm stumped.
Albert Wertz is in the SD Card "business". Check with him to see about getting one.
FYI, now that you have CWM "written" to the internal recovery partition you should be able to enter recovery even if you can't boot the tablet to android.
N+Pwr from off condition should do the trick.
Pain, sorry, I just saw this thread. I made a small update to the instructions. I left out something which I thought was obvious. This was a fault on my part. Did you label each partition correctly? It should be BOOT, system, and data.
I used this method (don't forget the ext4fsd part) and it does work. But if you're still having trouble the CD-boot version of Ubuntu will work just fine too.
i allready have ubuntu running on a cd, in the past i labeld it "boot" (case sensitiv - all small letters) so this could be the fault?
Edit:
i can see that cwm work, it pops up 4 a half second or even less if i start the nook but than it instantly disappears
after installing cwm on my NT after that (my B&N store has been disabled and it doesn't let search, download, or view anything on the store..... has anyone a solution to this issue
NOTE: to build CM10.1 SD card, see http://forum.xda-developers.com/showpost.php?p=36685310&postcount=1.
[Caveat emptor: adopt/follow this guide at your own risk].
FWIW, below is a digest of the process to create a SD card running CM10.0 builds by XDA Developer Succulent which is posted at his blog http://iamafanof.wordpress.com and which I have used to build a CM10.0 SD card for my 16GB Nook Tablet:
Download the pair of files cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip and cm-10-yyyymmdd-UNOFFICIAL-acclaim_sd_hd.zip from http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/, and SD_Boot.zip from http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/.
Download gapps-jb-20121011-signed.zip from http://goo.im/gapps/gapps-jb-20121011-signed.zip.
Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create 4 partitions: boot (Primary, FAT32), system (Primary, Ext4), data (Primary, Ext4), and sdcard (Primary, FAT32). Set the partition ID type for the boot partition to 0x0C FAT32 LBA and set its Active flag (otherwise the SDcard will not be bootable). Once this is done, the boot partition should appear as a (read/write accessible) drive under Windows. (Note that you can adjust the suggested sizes of the partitions upward to fill up the entire SDcard; FWIW the sizes I use on my 8GB card for the 4 partitions are, respectively: 0.5GB/0.5GB/2GB/[remainder of SDcard]).
Copy to the boot partition of the SD card the following files from cm-10-yyyymmdd-UNOFFICIAL-acclaim_sd_hd.zip: boot.img (in folder p2), flashing_boot.img, MLO, recovery.img, u-boot.bin.
Modify the zip files using drag and drop with winrar/winzip (do not extract and repack the zip files):
Replace updater-script in folder META-INF\com\google\android of cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip with the updater-script from in folder p2 of cm-10-yyyymmdd-UNOFFICIAL-acclaim_sd_hd.zip.
Replace vold.fstab in folder system/etc of cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip with the vold.fstab from folder CM10_Jelly_Bean\1_os of SD_Boot.zip.
Replace updater-script in folder META-INF\com\google\android of gapps-jb-20121011-signed.zip with the updater-script in folder CM10_Jelly_Bean\p2\gapps of SD_Boot.zip.
Copy to the boot partition of the SD card cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip and gapps-jb-20121011-signed.zip (that get modified with the replacement updater-scripts and vold.fstab files in the above steps).
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 SDC Recovery.
[Optional but recommended step, in case you accidentally forget to replace the updater-script file(s)] Select Backup to backup your current NT config (/boot, /recovery, /system, and /data).
Select "Install zip from SD card" and install the modified cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip file.
Select "Install zip from SD card" and install the modified gapps-jb-20121011-signed.zip file.
Select "Power off" to turn off the NT.
Boot the NT from its power off by inserting a powered USB cable; after about a minute you should see boot animation lasting for a few minutes followed by initial wifi network and google account setup process, after which your CM10 on SD is ready for use.
A few additional points worth noting:
If you plan to backup your NT current ROM config then add to the boot partition size at least 600MB for each backup (to save space you can copy/archive backup data folders to your PC and remove their copy from the boot partition).
Generally the lower rating (and also cheaper) class 4 SD cards are more suitable for running a ROM than the higher classes 6 and 10 cards (since the latter are optimized for large & sequential block read/write at the expense of random read/write). So if you happen to use a class 10 or 6 card and your apps frequently crash or freeze, consider switching to a lower class SD card.
Did you ask succulent if it was OK to post his work here? Someone already did it in the dev section and he was a little upset that he wasn't even consulted about it.
Sent from my CM 10 SD nook tablet. Thanks devs.
Thanks for the tutorial. I've used XDA for a long time and loaded lots of custom ROM's, but I'm finding this Nook Tablet situation ridiculously complicated. I'm having trouble understand your step number 8.
"Copy to the boot partition of the SD card and gapps-jb-20121011-signed.zip..." doesn't make grammatical sense. Is there a typo here?
sanjosanjo said:
Thanks for the tutorial. I've used XDA for a long time and loaded lots of custom ROM's, but I'm finding this Nook Tablet situation ridiculously complicated. I'm having trouble understand your step number 8.
"Copy to the boot partition of the SD card and gapps-jb-20121011-signed.zip..." doesn't make grammatical sense. Is there a typo here?
Click to expand...
Click to collapse
I just looked at it and it appears you are failing to read it. There are clear and concise instructions as provided by Succulent and cut and pasted by digimax.
It clearly says to copy the ROM and the gapps.
Sent from my CM 10 SD nook tablet. Thanks devs.
SlowCobra96 said:
I just looked at it and it appears you are failing to read it. There are clear and concise instructions as provided by Succulent and cut and pasted by digimax.
It clearly says to copy the ROM and the gapps.
...
Click to expand...
Click to collapse
There were indeed typos in the cited paragraph (thanks to sanjosanjo for spotting them), and I already fixed them.
digixmax said:
There were indeed typos in the cited paragraph (thanks to sanjosanjo for spotting them), and I already fixed them.
Click to expand...
Click to collapse
Did you reword them from succulents site because those are what I used when I did my SD card and I had zero issues following them.
Sent from my CM 10 SD nook tablet. Thanks devs.
On Step 8, did you mean to copy the cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip to the boot partition instead of the cm-10-yyyymmdd-UNOFFICIAL-acclaim_sd_hd.zip because in step 12 you say to install cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip? I've followed your steps for replacing the files, but did not put the sd_hd.zip on the SD card, only the normal acclaim.zip.
I'm going to try it now and see what happens.
Edit: says installation aborted. This was when trying to install the cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip that has had the files replaced from the sd_hd.zip
LucasMN said:
On Step 8, did you mean to copy the cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip to the boot partition instead of the cm-10-yyyymmdd-UNOFFICIAL-acclaim_sd_hd.zip because in step 12 you say to install cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip?
...
Click to expand...
Click to collapse
Yes (I corrected it).
LucasMN said:
...
Edit: says installation aborted. This was when trying to install the cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip that has had the files replaced from the sd_hd.zip
Click to expand...
Click to collapse
I had neglected to indicate in step #3 that the partition type of /system and /data is (Primary, Ext4).
digixmax said:
FWIW, below is a digest of the process to create a SD card running CM10 builds by XDA Developer Succulent which is posted at his blog http://iamafanof.wordpress.com and which I have used to build a CM10 SD card for my 16GB Nook Tablet (caveat emptor: adopt/follow it at your own risk):
Click to expand...
Click to collapse
thanks for this great thread digixmax. what is the difference between your method and just directly writing succulent's IMG file to a card?
his post looks like it was updated 12/25, although perhaps the image file is from 12/08. is yours updated since then?
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
zeiss74 said:
thanks for this great thread digixmax. what is the difference between your method and just directly writing succulent's IMG file to a card?
his post looks like it was updated 12/25, although perhaps the image file is from 12/08. is yours updated since then?
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Click to expand...
Click to collapse
First off, just to be clear: I did not invent this process, rather my post is intended to be a streamlined digest of Succulent's blogs on how-to build CM SDcard -- including in particular the blog http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/. This process gives you the maximum flexibility at the outset in sizing the partitions, creating extra partitions, etc. This process has also worked for some of the other CM10 builds that are available on XDA such as ChrisHoffman's and Hashcode's builds, as well as the Paranoid Android build posted on Succulent's blog.
Succulent's pre-made SD card image is the simplest/quickest way to create a bootable SDcard of his CM10 builds: you just download and write the image to SDcard and it's ready to go. It's possible to adjust the partition sizes after the image is written to the card but with some risks of messing up the partition table which could make the SDcard not bootable. There have also been reports that NTs running these images appear to have same identical MAC address, thus any two of these NTs will not be able to get on the same LAN (e.g., in the same household WiFi LAN) at the same time.
Re: Succulent's v12/25: I just flashed it (internally on emmc) today and it works great, but he has not posted cm-10-xxxxxxxx-UNOFFICIAL-acclaim_sd_hd.zip for it so you'll have to wait a bit if you want to build the image from scratch.
digixmax said:
First off, just to be clear: I did not invent this process, rather my post is intended to be a streamlined digest of Succulent's blogs on how-to build CM SDcard -- including in particular the blog http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/. This process gives you the maximum flexibility at the outset in sizing the partitions, creating extra partitions, etc. This process has also worked for some of the other CM10 builds that are available on XDA such as ChrisHoffman's and Hashcode's builds, as well as the Paranoid Android build posted on Succulent's blog.
Succulent's pre-made SD card image is the simplest/quickest way to create a bootable SDcard of his CM10 builds: you just download and write the image to SDcard and it's ready to go. It's possible to adjust the partition sizes after the image is written to the card but with some risks of messing up the partition table which could make the SDcard not bootable. There have also been reports that NTs running these images appear to have same identical MAC address, thus any two of these NTs will not be able to get on the same LAN (e.g., in the same household WiFi LAN) at the same time.
Re: Succulent's v12/25: I just flashed it (internally on emmc) today and it works great, but he has not posted cm-10-xxxxxxxx-UNOFFICIAL-acclaim_sd_hd.zip for it so you'll have to wait a bit if you want to build the image from scratch.
Click to expand...
Click to collapse
thanks!
also, dumb question but if you "remove SD card" in step 14, how is "CM10 on SD ready for use" in step 15? do you reinsert it?
zeiss74 said:
also, dumb question but if you "remove SD card" in step 14, how is "CM10 on SD ready for use" in step 15?
Click to expand...
Click to collapse
Mistake on my part, leave the card in the NT.
ok, worked great (the second time). the first time i used 7zip to change the zip files, but then i read a readme.txt from succulent that said to only use drag and drop with winzip/winrar to change the zip files, so i downloaded winrar and it worked. the first time i got the "installation aborted" error.
thanks again, i'm super excited to try CM10. been wanting to update this NT for some time now.
Just an FYI it isn't the pre-made image file that causes the repeating MAC Address it is something in the CM 10 build. I have 2 NT 16's running different build dates of CM 10 SD and both have identical MAC Addresses. Somewhere in the build of CM 10 it appears that it is taking the MAC Address from a developer unit and applying it to everyones NT. Or so it would appear.
SlowCobra96 said:
Just an FYI it isn't the pre-made image file that causes the repeating MAC Address it is something in the CM 10 build. I have 2 NT 16's running different build dates of CM 10 SD and both have identical MAC Addresses. Somewhere in the build of CM 10 it appears that it is taking the MAC Address from a developer unit and applying it to everyones NT. Or so it would appear.
Click to expand...
Click to collapse
My NT has the same MAC address regardless of whether it's running stock, running CM10 internally or off SD card.
I think there is something wrong with your build images or possibly with your NTs (you can look up the NTs' MAC addresses in /rom/devconf/MACAddress on their emmc).
digixmax said:
My NT has the same MAC address regardless of whether it's running stock, running CM10 internally or off SD card.
I think there is something wrong with your build images or possibly with your NTs (you can look up the NTs' MAC addresses in /rom/devconf/MACAddress on their emmc).
Click to expand...
Click to collapse
So I have 2 broken NT's that despite the stock os showing the correct MAC Addresses and even the Mac config files showing the correct to the individual NT Mac address, when I load CM 10 despite not doing anything to change the configuration files other than updater-script, I broke it? Really?
And on top of that the pre-made images are known to have the same Mac address. Though the exact same files, sans imager program, couldn't possibly be problematic?
Somehow I doubt your stock os, if your using the succulent build for cm10, has the same Mac address.
Does your MAC end in 9f:fd ?
Sent from my CM 10 SD nook tablet. Thanks devs.
SlowCobra96 said:
So I have 2 broken NT's that despite the stock os showing the correct MAC Addresses and even the Mac config files showing the correct to the individual NT Mac address, when I load CM 10 despite not doing anything to change the configuration files other than updater-script, I broke it? Really?
And on top of that the pre-made images are known to have the same Mac address. Though the exact same files, sans imager program, couldn't possibly be problematic?
Click to expand...
Click to collapse
If your two NTs running stock OS still show two distinct MAC addresses then I don't think you have broken the NT per-se. Most likely you simply didn't properly build one or both of CM10 SDcard images. Your problem is the type Succulent often refers to as "residue" problems.
Somehow I doubt your stock os, if your using the succulent build for cm10, has the same Mac address.
Click to expand...
Click to collapse
It is the same MAC address, but believe whatever you want.
Does your MAC end in 9f:fd ?
Click to expand...
Click to collapse
Nope.
Then im a ****ing idiot and you are a god. Shrug. I am an not adverse to admitting when I am wrong, however in this situation I don't believe I am. Apparently my 2 NT's are completely special. Oh wait, anyone running the Image files have the same issues. There is nothing shared between the two NT's. SD cards arent shared. Not a single file is shared. Not even the build date of the CM 10 files is shared. So again I say, there is a problem with the SD version of CM 10 not reading the correct MAC. How you got lucky with your mac reading correctly from SD and EMMC I don't know, especially considering anyone else that has multiple NT's in the same house suffers the same issue.
i have two followup questions to help me better understand this setup.
1. what are the different partitions on the card? and why wouldn't we make the boot partition as large as can be? i went to back up my NT apps (about 100) to bring them to my CM10 card, and they are 800MB, and the only partition i can copy them to from my PC is boot. so i'm out of luck with 500MB (250 MB free). also, since boot is the only partition i can access from my PC, it means that's where all my videos and music will have to be copied. so it seems like i should make boot 4+ GB. i don't own any large apps (like those 2 GB racing games) so i would guess my other partitions don't need to be huge. am i missing anything? with the tablet up and running but few apps, the 0.5GB boot partition is about 50% full, the 0.5 GB system partition (no longer labeled such) is 64% full, while 2GB data and 4.5GB sdcard are 5% and 0% used (per minitool)
2. if this doesn't change the stock NT, then what are steps 10 and 11 doing? where are they installing something? from the SD card to the SD card, maybe in another partition? do i need to keep those zip files on the boot partition once they are installed?
thanks for any assistance to help my understanding.
I have a 128 GB microsd and I do not want FAT32 on it. I have MIUI 8 (Android 5.1.1) with 3.10.49 kernel, TWRP 3 and root. For some reason mount doesn't work at all, it always produces error "Invalid argument". I tried replacing it with one from BusyBox but it didn't help. Some forum guys told me that I should add the card to fstab (which AFAIK is located inside boot.img), and edit the config of vold (which is located I have no idea where). Also this. All I understood from there is that there is some storage_list.xml and I should edit it. Again, searching through forums led me to this path framework-res.apk\res\xml\storage_list.xml.
But still! I have no idea where this framework-res.apk is located and how do I unpack-repack it.
All info that I'm desperately trying to extract from google is outdated or related purely to cyanogen >_< Please give some instructions
You wrote you don't want FAT32. Other filesystem than that isn't supported by MIUI which is why you won't succeed to show your card content by editing anything. You need a 3rd party libs with your filesystem support.
See here, worked for me http://forum.xda-developers.com/showthread.php?p=61142640
or install a custom app with your filesystem support (eg. Paragon NTFS).It works either.
Sent from my phone by Tapatalk
Dude, that's the f$#@ed up part, you see.
> If you use KitKat
And I'm using 5.1.1 which is technically lollipop.
I'm seeking for a support as close to native as it can be, so I'm not involving any "mounting" crapware, especially Paragon's products, I'm fed up with their ext4 4 windows driver which gave me countless BSODs and corrupted files.
You said that MIUI doesn't support anything but FAT32, but that's not 100% true. It by default supports only FAT32 for external storage. But at the same time it mounts internal storage (which is of course in ext4) no problem. So I guess it's not *unable* to use ext4 (or f2fs, which is AFAIK supported by any kernel after 3.10.*) for external storage, it's just not enabled by default, and the question is how do I properly use that ability of android to mount ext4 (and/or f2fs)
UPD: I have to apologize for posting "also this" in the initial post w/o actually giving the link, here it is.
This is what seems actually related, but I'm too noob to understand what am I supposed to do to mount the damn card
First, the ROM and/or (especially) kernel should have F2FS support, then ramdisk should be modified with fstab edited so it could mount F2FS partitions at boot.
Other than that, it's impossible.
Sent from my ASUS_Z00A using XDA Labs