adb logcatI know how to get to ADB, but could you tell me what the command is to get/view the logcat?
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.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...
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.
I tried adb logcat, this is all I get:adb logcat
Alternatively, you can use "adb logcat > something.txt" and it will write the logs to a file
Ctrl+C stops the logging.
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?
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.
It's not a recovery.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
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?
Never had a problem with class 10 cards myself...NC does not play well with Class 10, according to the reports. Class 6 is as fast as it gets at the moment....
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.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
Ok, this is the problem. If formatting failed, the script does not check the status (and mount too).Went through everything else just fine until:
Writing superblocks and filesystem accounting information
Sat there eternally...
hard power off then power on...
these are normal.goes through extracting with some errors in /tmp/backuptool.sh's not existing...
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 don't have 16g card myself.It might indeed be a problem.
I've noticed in other threads people reporting that 16gb cards didn't work. Kernel issue?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)
Unfortunatley I don't have one either.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?