[Q] How to create reduced zip file for dd img ??? - Nook Color Q&A, Help & Troubleshooting

Please excuse me if this has already been discussed in NC & NT Forum but for me it was impossible to get an answer any where for past 3 days of googling or XDAing. Please also excuse me if I am asking dumb questions.. but this one keep taking my attention day and night
I was trying to make dd image for my own study of Android system and noticed one thing that some DD Img can be compressed to below 260mb but others exceeds over 600mb. Can't find reason why..
To be specific.
I created two different SD card using verygreen 1.3 size-agnostic method.
1. verygreen 1.3 w/ used CM7 nighty 252 build. on Sandisk 4GB
2. verygreen 1.3 w/ Mireage Kang 7.2 build on Sandisk 8GB
After I confirm those cards are working, I did not install anything but created img file with command
(Ubuntu 11.10)
For #1
DD if=/dev/sdb of=cm7n252.img
For #2
DD if=/dev/sdb of=cm7MK.img
then result was as expected.
#1 img file about 3.8GB
#2 img file about 7.8GB
I winzip two files to see how much they will be compressed. and result surprised me.
-winzip with ultra compression-
#1 over 680mb for 4GB
#2 over 280mb!!! for 8GB
Can anyone explain me why? or How to create reduced zip for DD img?
Thank you for your time in advance

Related

[Q] weird partitions sd card

[ROM][CM7] Size-agnostic SD Card image and CM7 installer for SD Cards. with updater
I wrote to sd card with v1.1 img then - safely removed sd
copied nookie-froyo zip to boot section.
I have only 2 partitions one 115mb and 7.** with no file system ( Mini tool PTH )
1 st. try had 4 partitions the middle two bad and last 5.5 with rom on that section after attempted to boot in nook. Got error that original image was not present.
used windisk32 .2 to write to sd
is class 4 8gb.
2nd try had 2 partitions one with boot img. and nookie zip. other partition 5.5 gb FAT
used hp to get disk "back" 1time 7.4gb, 2nd. time got back all but few kb's.
any ideas what I'm doing wrong ??
I'm having a little trouble following your post. However, the one thing jumps out at me. You are using an a tool designed to install CM7 (android 2.3) to install nookie froyo (android 2.2).
Try using it with one of the files it was designed for:
http://download.cyanogenmod.com/?type=stable&device=encore
Thankyou
got it to boot CM7 and market

[Q] Newbie CM7 n87 SD backup question

Hello,
As the title says, I'm a new CM7 user (running verygreen's SDcard installer, using the 1.3 generic image, with nightly 87, no OC). This is running beautifully, except for one thing... I didn't use a big enough SDcard to start with and now I'm faced with looking for the right way to migrate to a larger card (or alternatively to make use of the NC's built-in eMMC in some fashion to augment the current SDcard).
Can someone tell me if the following approach will work? And is it the right/best way?
1. Use Win32Imager to make a full disk image of the current card (4GB).
2. Write the image to a new 8GB or 16GB card. At this point I should have a perfect copy except that there'll be wasted space on the card past the final partition.
3. Boot into a Linux recovery type LiveCD and use gparted to expand the final partition to use up the rest of the space.
4. Am I done? (crosses fingers?)
The goal of this move is to give myself some room to drop movies, music, etc. onto the /mnt/sdcard partition (which I believe is called /media by NC Stock 1.2?) Will what I described work?
Thanks in advance,
fuul4nook
P.S. One extra question, will the fact that my NC is a blue dot cause any problems with the idea? And if not, is there any way I can use the eMMC partitions while running CM7 from SDcard?
fuul4nook said:
Hello,
As the title says, I'm a new CM7 user (running verygreen's SDcard installer, using the 1.3 generic image, with nightly 87, no OC). This is running beautifully, except for one thing... I didn't use a big enough SDcard to start with and now I'm faced with looking for the right way to migrate to a larger card (or alternatively to make use of the NC's built-in eMMC in some fashion to augment the current SDcard).
Can someone tell me if the following approach will work? And is it the right/best way?
1. Use Win32Imager to make a full disk image of the current card (4GB).
2. Write the image to a new 8GB or 16GB card. At this point I should have a perfect copy except that there'll be wasted space on the card past the final partition.
3. Boot into a Linux recovery type LiveCD and use gparted to expand the final partition to use up the rest of the space.
4. Am I done? (crosses fingers?)
The goal of this move is to give myself some room to drop movies, music, etc. onto the /mnt/sdcard partition (which I believe is called /media by NC Stock 1.2?) Will what I described work?
Thanks in advance,
fuul4nook
P.S. One extra question, will the fact that my NC is a blue dot cause any problems with the idea? And if not, is there any way I can use the eMMC partitions while running CM7 from SDcard?
Click to expand...
Click to collapse
You should be able to do what you want but use Easeus Partition Manager to extend the 4th partition on the SD to get full use of the card. I don't know what you mean by "blue dot", but you can access 5 gb on the emmc directly through apps if it's music or video. You can also use File Expert or Root Explorer to store what you want on the emmc partition, which will then also be available when you boot into the stock NC rom.

Size-staggered or size-agnostic CWM 3.2.0.1 SD images?

Does anyone have links to different-sized images (eg 1GB, 4GB, 8GB) of the current CWM build, or would it be possible to create a size-agnostic image like verygreen's ROM installer? I'm only aware of the 1GB image linked in eyeballer's CM7 + CWM to eMMC thread, and some people like to keep multiple .zips and nandroid backups on those cards rather than or in addition to installing CWM internally.
You can just use one of the older images, and copy the boot files over to your card... It will boot the new version. I don't know how to make a size-agnostic image... but I could make a 2 and 4 GB image, if it would help.
As long as you have the new mlo, u-boot.bin, uImage, and uRamdisk files on the card after flashing the most recent images... I know it boots the newest version.
I don't need them myself, but I see a lot of people screwing themselves up by following old threads and ending up with old CWM on blue-dot NCs.
Gotcha,
Here's a thread that details how to make one of the older images into a 3.2.0.1 card. It has the new files in a zip to copy over.
http://androidforums.com/nookcolor-...workmod-version-3-2-0-1-recovery-sd-card.html
Like I said, I know it works because I've done it. Even though I've repartitioned my blue dot nook into the old partition scheme anyway.
In case anyone stumbles in this thread actually looking for the images, the following will suffice for one-time-use cards to root or flash:
eyeballer said:
Download 1gb CWM 3.2.0.1 sdcard image from here. MD5 of .zip: 1319739d33642ed860e8044c3d55aa56. (I made this based on work in this thread. credit: to cmstlist and DizzyDen, and kevank for hosting). You really only need the 1gb image for this guide, no matter what the size of your card is. A smaller image will burn faster, and when you're done with the guide you can reformat the card anyway.
Click to expand...
Click to collapse

[Q] whats the difference in these codes?

I am working on fixing by crashed nook, trying to reinstall the original nook before adding CM10 on bootable microsd.
Looking through various posts about creating a bootable microsd I see some form or another of the following code-
dd if= /Users/mycomputername/Desktop/imagename.img of=/dev/disk#
or
sudo dd bs=4m if=imagename.img of=dev/disk#
to write the clockwork file to the card... whats the difference in the two methods?
tim
tbrandenstein said:
I am working on fixing by crashed nook, trying to reinstall the original nook before adding CM10 on bootable microsd.
Looking through various posts about creating a bootable microsd I see some form or another of the following code-
dd if= /Users/mycomputername/Desktop/imagename.img of=/dev/disk#
or
sudo dd bs=4m if=imagename.img of=dev/disk#
to write the clockwork file to the card... whats the difference in the two methods?
tim
Click to expand...
Click to collapse
You do not say which operating system you are running on. The first statement is usually used on a Mac and the second one on Linux. Sudo is just the Linux command to put it into root mode.
Sent from my Nook HD+ running CM10.1 on emmc.

Post raw .img for each partition for android install via dd?

So, I don't have access to a linux PC with a SD Card reader, only Windows/MacOS. My Mac will allow me to use gdisk to create the partition table correctly, but it will not allow me to see the individual android partitions due to the hybrid MBR setup and MacOS not playing nicely. I'd like to use this method to install Android onto a larger SD card for a CFW/emuMMC/Android setup.
So, my request is that someone take the initial android 32gb img and dd each individual partition to a separate .img file (I think there should be 7), that I can then use to dd onto my SD card. I think if I have that, I can complete this project. I plan on writing it up as a guide once I can get it to work.
Thank you in advance!
I'm trying to make an image of my complete sd card with all the partitions on it but I can't find how to do it, can you point me in the right direction
I Figured it out

Categories

Resources