[ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards.

dweezilz · Mar 21, 2011

that did it. I had to rename those files back to their original name and now it boots...got market, etc...! Nice. Not sure what happened though.

cybertimber2007 · Mar 21, 2011

BigBadSloth said:
I know how to get to ADB, but could you tell me what the command is to get/view the logcat?

adb logcat

Alternatively, you can use "adb logcat > something.txt" and it will write the logs to a file

Ctrl+C stops the logging.

verygreen · Mar 21, 2011

SCWells72 said:
EDIT 2: Okay, by explicitly installing Superuser and Busybox from the Market, I can get ROM Manager to install CWR with no errors, but I still can't seem to get into recovery mode, or at least if I do, it doesn't seem to think it needs to install anything. Bummer...

If you are not using v1.1 installer, did you update u-boot.bin? The u-boot.bin in the first image is not recovery-enabled it seems.

verygreen · Mar 21, 2011

dweezilz said:
For some reason after following this I always go back to the installer with the penguin. I removed the cm7 nightly zip but it still goes. I saw it install the apps though the first time. I did notice that I did NOT have a file called uRecRamdisk, it was named uRecRam. I named that one uRamdisk. Could that be the issue? Should I rename the bak's, back to their previous file names? Any help would be appreciated.

Yes, you need to rename .bak back if you do not update with the cm7 nightly zip because the gapps package does not contain the new kernel.
Best of all to do this is to upgrade to v1.1 then you can boot into "recovery" which will install all the stuff you throw into first partition as long as the naming in conforming to expected values (outlined in the first post).

BigBadSloth · Mar 21, 2011

cybertimber2007 said:
adb logcat

Alternatively, you can use "adb logcat > something.txt" and it will write the logs to a file

Ctrl+C stops the logging.

I tried adb logcat, this is all I get:

- exec '/system/bin/sh' failed: No such file or directory (2) -

SCWells72 · Mar 21, 2011

verygreen said:
If you are not using v1.1 installer, did you update u-boot.bin? The u-boot.bin in the first image is not recovery-enabled it seems.

I actually did use the v1.1 installer but then restored a TitaniumBackup of apps & settings from the previous installer to get my apps and settings moved over. I downloaded the u-boot.bin from the first post and there are differences, so I put that on and tried again. Still no luck. Any other thoughts?

verygreen · Mar 21, 2011

SCWells72 said:
I actually did use the v1.1 installer but then restored a TitaniumBackup of apps & settings from the previous installer to get my apps and settings moved over. I downloaded the u-boot.bin from the first post and there are differences, so I put that on and tried again. Still no luck. Any other thoughts?

Hm, I verified that the new u-boot works. It was kind of tricky to enter recovery mode and I managed to do it not from a first try, but it's definitely possible.
(after you have uRecRam and uRecImg properly named unlike what v1 did)

If you mean that after you rename the uRecImg and uRecRam to uImage and uRamdisk and then try to install something that is not full nightly update you cannot get into the android until you restore old uImage and uRamdisk, this is supposed to happen since the installer does not know where to get the proper kernel image and ramdisk if not supplied by the installed packages.

SCWells72 · Mar 21, 2011

verygreen said:
If you mean that after you rename the uRecImg and uRecRam to uImage and uRamdisk and then try to install something that is not full nightly update you cannot get into the android until you restore old uImage and uRamdisk, this is supposed to happen since the installer does not know where to get the proper kernel image and ramdisk if not supplied by the installed packages.

Aha! Breakthrough! I didn't realize I had to rename that direction to get it to pick up the new build. I'm golden now! Thanks for bearing with an Android newb!

FrayAdjacent · Mar 21, 2011

Awsome work.

Having SERIOUS difficulty getting into recovery to get the Market loaded. Out of about 20-30 reboots, I got it in (what I think is) recovery once. It went to the 'android _ ' prompt and blinked there for about 10 minutes. Then I powered it off and started it back up the 'normal' way. Went back to the same prompt. Kept doing it until I removed the gapps....zip from the boot partition.

I have not been able to get it back into recovery since. I've re-downloaded the gapps zip file, deleted it from the SD card and copied it back over a couple times.

Also ADB from my Windows box doesn't work. Device Mangler shows the composite ADB device, but ADB from the command line never sees the Nook.

As a suggestion, Green, perhaps update the utility to not only unpack/install CM7, but have it also install the gapps zip from the SD card at the same time?

verygreen · Mar 22, 2011

FrayAdjacent said:
Having SERIOUS difficulty getting into recovery to get the Market loaded. Out of about 20-30 reboots, I got it in (what I think is) recovery once. It went to the 'android _ ' prompt and blinked there for about 10 minutes. Then I

It's not a recovery.
The same installer thing with a penguin would constitute recovery mode.
You really need to hold power and N button all together and then keep holding for a second or two after the "Touch the future of reading" message,
then release the power button (or the unit would poweroff).

FrayAdjacent said:
As a suggestion, Green, perhaps update the utility to not only unpack/install CM7, but have it also install the gapps zip from the SD card at the same time?

It will work as in even on the first install it would unpack everything including the gapps if you put it there.
In my experience if you put gapps together with the initial install image, the boot will fail (will just sit at the ANDROID_ screen) and the traces look like it's due to gapps unable to register or something due to wifi not setup.

If your ADB does not recognize nook, make sure you added the nook device id to known devices list, check the wiki for instructions.

FrayAdjacent · Mar 22, 2011

Well, I got ADB working. Missed a step. RIF failure on my part.

Also re-read this thread and went through it with the 1.1 version of the utility and booting with the renamed uImage and uRamdisk. Worked like a charm!

Now all I need is a faster uSD card. Class 6 is still slow!

ADude · Mar 22, 2011

FrayAdjacent said:
Now all I need is a faster uSD card. Class 6 is still slow!

NC does not play well with Class 10, according to the reports. Class 6 is as fast as it gets at the moment.

Try doing other things, like Dalingrin's Overclocking Kernel.

DizzyDen · Mar 22, 2011

ADude said:
NC does not play well with Class 10, according to the reports. Class 6 is as fast as it gets at the moment....

Never had a problem with class 10 cards myself...

Some information regarding 16 gig SD's with this message... may help figure out what's going on with them....

Worked perfect on my class 10 8 gig card....

When trying on class 10 16 gig card went through with one error not seen on 8 gig card:

Code:

Partitioning the card ...

The number of cylinders for this disk is set to 1946.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)
Done partitioning, creating filesystems

Went through everything else just fine until:
Writing superblocks and filesystem accounting information

Sat there eternally...
hard power off then power on...
goes through extracting with some errors in /tmp/backuptool.sh's not existing...
Sat at Android_ eternally.. nothing could get past this

Can get into recovery... just not boot CM7.

MarkE08 · Mar 22, 2011

Thanks for making an easy way to test CM7 on SD

verygreen · Mar 22, 2011

DizzyDen said:

When trying on class 10 16 gig card went through with one error not seen on 8 gig card:

Code:

Partitioning the card ...

The number of cylinders for this disk is set to 1946.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)
Done partitioning, creating filesystems

This is harmless.

DizzyDen said:
Went through everything else just fine until:
Writing superblocks and filesystem accounting information

Sat there eternally...
hard power off then power on...

Ok, this is the problem. If formatting failed, the script does not check the status (and mount too).
So then the mount fails too, the unpacking happens to ramdisk.
Then when you reboot, your /system partition is not populated.
Also on next reboot the script blindly assumes that if the partition is really there, it must be suitably formatted already and does not reformat it.
Can you insert this sdcard into a computer now and format second partition with mkfs.ext4 (also 3rd just in case).
(hm, now that I think about it, there were two mkfs, for /system and /data,
which one hung?)
after that boot into "recovery" with the full CM .zip present. and it'd should be able to mount the freshly formatted stuff and unpack there.
[/quote]

DizzyDen said:
goes through extracting with some errors in /tmp/backuptool.sh's not existing...

these are normal.

cybertimber2007 · Mar 22, 2011

It might indeed be a problem.

Code:

There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

I've noticed in other threads people reporting that 16gb cards didn't work. Kernel issue?

verygreen · Mar 22, 2011

cybertimber2007 said:
It might indeed be a problem.

Code:

There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)

I've noticed in other threads people reporting that 16gb cards didn't work. Kernel issue?

I don't have 16g card myself.
Can you boot into emmc, insert 16g card and try mkfs.ext4 on 2nd and 3rd partitions of the sd card, then see what kernel messages do you get if any?

cybertimber2007 · Mar 22, 2011

verygreen said:
I don't have 16g card myself.
Can you boot into emmc, insert 16g card and try mkfs.ext4 on 2nd and 3rd partitions of the sd card, then see what kernel messages do you get if any?

Unfortunatley I don't have one either.
Btw, seems my post edit didn't save, but I mean to word it as "the problem might be at boot time", though I thought those issues were only for really old kernels and such. I'll try to get my hands on a 16gb if I can and test it out though, since I know what you are talking about

DizzyDen · Mar 23, 2011

I will do more testing as you asked when I get home this evening... I was just trying to provide you as much information as I could as to what I was seeing as it went through its process.

However, to answer the question as to which mkfs failed... I didn't see either one fail.

Will try the 16 gig test again tonight and try to take a pic of the screen when it is in the eternal hang up... you will be able to see all the text on the screen that way... IF the pic comes out good enough.

smartmind · Mar 23, 2011

Will your work can be used with the bottom status bar mod? And how?

[ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards.

Member

Senior Member

Senior Member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts