Database Users

Running into some issues while booting into Android

While booting into Android on my HTC Touch I am encountering some issues. Here is where I think things start going wrong.
"Rootfs loaded.
Checking for partition...
Using system image in /sdcard/android
e2sck 1.41.4 (27-Jan-2009)
ext2fs_check_if_mount: No such file or directory while determining whether /dev/block/loop0 is mounted.
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/loop)
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
mount: mounting /dev/block/loop0 on /data failed: Invalid argument
Failed
Failed to mount /data
/bin/sh: can't access tty: job control turned off
/"
I am using the file versions found here http://sourceforge.net/projects/androidhtc/files/latest
Any help is very much appreciated. Thanks!

if your running it from the SD card it sounds like the card needs to be reformatted

That makes sense. Sorry I am new to all this... can you tell me what format it needs to be in? I'll figure it out from there.

Stingray88 said:
That makes sense. Sorry I am new to all this... can you tell me what format it needs to be in? I'll figure it out from there.
Click to expand...
Click to collapse
fat32 is what you need to format it at.

It is in fat32 and I've reformatted multiple times, still doesn't work.
Are you sure it doesn't have to be in ext2? The error messages I get say it's looking for ext2...
EDIT: Yea there has to be more to this than just having it in FAT32 because I just tried 3 different cards all in FAT32. Can anyone help me out here?

did you make sure to rename the system, zimage and rootfs files??

I got it working!
I'm really not sure what it is that I was doing wrong before. I just kept trying the same things... and it finally worked this time.

Linux boot hangs
The text is far too small to read, and much of it is in non alphanumeric characters, but I am able to make out that something hangs for too many seconds.
I have tried more than one version for the Verizon Vogue variant.
I would like to get it to run. Then maybe even flash it.

Been Getting This Issue When I Flash Nightlies

Anyone know whats causing the following issue?
Recently when I download the latest Nightly's (to flash over current Nightly) and boot into recovery and try to flash the ROM, I get the following:
Code:
Installing Update......
E: Error in /sdcard/cm_vision_full-119.zip
(Status 1)
Installation aborted
Before I proceed with trying to flash the ROM I do clear cache and dalvik cache, I always do this. But lately Ive been getting that error when ever I download the file from the phone's browser (whether it be stock, Miren, etc) or even from computer and transfer it to SD card and try to flash. Sometimes when I download from my computer browser and transer to SD card it works the second time (or if I transfer the first file over again) but when I reboot into the ROM, apps are missing and etc. So it corrupted the install.
Things Ive tried with no success
1. Reformatting SD Card
2. Complete Data Wipe (which allows me to flash the Nightly with nothing previously installed) but when I try to flash a new nightly over the installed one same issue
3. Reinstalling Recovery
4. Downloading rom from either WiFi or Tmobile network
5. Going back to G2 Engineering Hboot
Im at the point where I frustrated with my G2 and want to throw it against a wall. The only way Im able to flash new Nightly's is through wiping the device, which gets tedious.

Bump someone has to have some solution.

is signature verification enabled in CWM? when you go to install zip from sdcard, make sure you toggle signature verification to OFF. not sure if this is what you're encountering, it almost sounds like a bad sd card too.

pmcqueen said:
is signature verification enabled in CWM? when you go to install zip from sdcard, make sure you toggle signature verification to OFF. not sure if this is what you're encountering, it almost sounds like a bad sd card too.
Click to expand...
Click to collapse
Signature verification is always off. I did try to turn it on to see if it made a difference, didn't. Ive pretty much tried everything I could think of.
I did have one issue with the SD card (dont know if it is related or not), when I was trying to copy a file to my SD under Ubuntu, it wouldnt let me saying the SD Card is read-only. I went into Windows and it let me transfer the files, so I dont know.

sounds like it could be SDcard related because its happening whether you download via the phone or computer. Have you tried wiping and formatting the SDcard and trying agian?

boost3d23 said:
Signature verification is always off. I did try to turn it on to see if it made a difference, didn't. Ive pretty much tried everything I could think of.
I did have one issue with the SD card (dont know if it is related or not), when I was trying to copy a file to my SD under Ubuntu, it wouldnt let me saying the SD Card is read-only. I went into Windows and it let me transfer the files, so I dont know.
Click to expand...
Click to collapse
do you have another sd card lying around that you can test with? a malfunctioning sdcard can manifest itself in some pretty wonky ways, including something like what you're describing. that would be my next move in troubleshooting.
seems especially likely since you've already tried downloading the rom different ways and whatnot.
do you have eng hboot? you could try fastboot flashing CWM again just to make sure nothing is going wrong there. I would do it manually via PC10IMG or fastboot flash rather than rom manager... I don't really trust the app to do any of its recovery functions "properly" anymore.

martonikaj said:
sounds like it could be SDcard related because its happening whether you download via the phone or computer. Have you tried wiping and formatting the SDcard and trying agian?
Click to expand...
Click to collapse
Tried wiping and reformatting the card many of times. Most of it through Clockworkmod recovery not through the PC though.
pmcqueen said:
do you have another sd card lying around that you can test with? a malfunctioning sdcard can manifest itself in some pretty wonky ways, including something like what you're describing. that would be my next move in troubleshooting.
seems especially likely since you've already tried downloading the rom different ways and whatnot.
do you have eng hboot? you could try fastboot flashing CWM again just to make sure nothing is going wrong there. I would do it manually via PC10IMG or fastboot flash rather than rom manager... I don't really trust the app to do any of its recovery functions "properly" anymore.
Click to expand...
Click to collapse
I do have another SD card that I could test with, haven't done that yet though. Will try it, wasnt sure if it was SD card related.
Yes I do have eng hboot; I flashed the G2 one then the Desire Z one (using the Virtous rom guide) and finally back to the G2 one. Thought that might of been the reason for the issues but turned out to not be.
And I agree I only use ROM Manager to do backups. Anyway I flashed the Clockworkmod 3.1.0.1 (by blahbl4hblah) through recovery and then went back to the one in rom manager. Havent tried installing it through fastboot. Will try that as well.

Ok I can say its not the SD Card or recovery. I flashed recovery again through fastboot and used a different SD Card. Still throws that error. I made sure to only copy my media to the SD Card and nothing from the previous one to make sure it wasnt some file on there that was causing the issue.
Edit: And here is the worst part. After the install fails and I reboot Im stuck at the HTC logo, so Im forced to wipe and reinstall.

Bump for a possible solution.

Another note. The same file I downloaded (didn't redownload) that throws that error when I try to flash it over a old Nightly, works when I wipe data/factory reset.
Ex. I downloaded Nightly 140 and try to flash it over Nightly 139, it throws that error. Now I wipe data/factory reset and flash that same Nightly 140 (didnt redownload) and flash it, it works.

What the heck is going on. I unrooted and re-rooted my G2 and still have this issue.

Bump still having this issue.
This is the CWM Recovery Error Log
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p25 (Invalid argument)
-- Wiping cache...
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
52624 inodes, 209715 blocks
10485 blocks (5%) reserved for the super user
First data block=1
Maximum filesystem blocks=262144
26 block groups
8192 blocks per group, 8192 fragments per group
2024 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Creating journal inode: done
This filesystem will be automatically checked every 34 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p27: 11/52624 files (0.0% non-contiguous), 10771/209715 blocks
Cache wipe complete.
E:unknown volume for path [/sd-ext]
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
-- Installing: /sdcard/cm_vision_full-145.zip
Finding update package...
I:Update location: /sdcard/cm_vision_full-145.zip
Opening update package...
Installing update...
about to run program [/tmp/backuptool.sh] with 2 args
Creating filesystem with parameters:
Size: 435943936
Block size: 4096
Blocks per group: 32768
Inodes per group: 6652
Inode size: 256
Journal blocks: 1663
Label:
Blocks: 106431
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/26608 inodes and 3437/106431 blocks
error: file_write: write: I/O error
E:Error in /sdcard/cm_vision_full-145.zip
(Status 1)
Installation aborted.

Have you checked md5 sum of downloads?
Sounds like either card corruption or filesystem corruption.
Tried doing any kind of chkdisk or equivalent on the card?
Sent from my HTC Vision using XDA Premium App

Mnementh666 said:
Have you checked md5 sum of downloads?
Sounds like either card corruption or filesystem corruption.
Tried doing any kind of chkdisk or equivalent on the card?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Yeah the MD5 sum of the downloads are okay.
Havent run a chkdisk of the SD card. Will do that. Ive reformatted the SD card and tried a different SD card and still have the same issue.
How do I know if it is a filesystem corruption and anyway to fix that?

Hmmm. Have you had any issues with connecting the phone and using as a usb drive? Maybe try copying a large (>250mb) file to the SD from your computer, and then copying back from phone to pc.
The read-only error you mentioned earlier is I think going to be the root cause, somehow. I'm not familiar offhand how the microSD can set RO or RW, but on the normal SD it's a switch.
Maybe something in the microSD card slot is causing errors?
Sent from my HTC Vision using XDA Premium App

Mnementh666 said:
Hmmm. Have you had any issues with connecting the phone and using as a usb drive? Maybe try copying a large (>250mb) file to the SD from your computer, and then copying back from phone to pc.
The read-only error you mentioned earlier is I think going to be the root cause, somehow. I'm not familiar offhand how the microSD can set RO or RW, but on the normal SD it's a switch.
Maybe something in the microSD card slot is causing errors?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Ran a chkdsk on the SD Card and no issues were found.
No problems connecting the phone to PC and using the usb drive. I tested transfering a 367MB file back and forth and it worked perfectly.
The interesting thing is Im not able to flash the Nightly ()without completely wiping) but Im able to use the same flashing method and flash a kernel perfectly without getting this error.
No clue what in the SD Card slot could cause the issue. The card is seated properly and locked into place.

Well... unfortunately, that taps out all my knowledge. Wish I could help more.
My thought on the card slot was just something (dust? Debris?) that got in there and is causing random intermittent r/w errors on the card. Basically like corrupting the file.
Do you download the nightly file through rom manager? Load the zip through same?
If yes... maybe download on pc, transfer to card, boot recovery, install directly.
You've probably tried that, and if so I apologize. I'm @ work and can't read the site, and replying and reading simultaneously isn't possible on tapatalk and I'm grasping at straws :-D
Sent from my HTC Vision using XDA Premium App

Mnementh666 said:
Well... unfortunately, that taps out all my knowledge. Wish I could help more.
My thought on the card slot was just something (dust? Debris?) that got in there and is causing random intermittent r/w errors on the card. Basically like corrupting the file.
Do you download the nightly file through rom manager? Load the zip through same?
If yes... maybe download on pc, transfer to card, boot recovery, install directly.
You've probably tried that, and if so I apologize. I'm @ work and can't read the site, and replying and reading simultaneously isn't possible on tapatalk and I'm grasping at straws :-D
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Nope there was no issue with SD card slot that I could see with the naked eye.
Honestly dont use ROM Manager at all. I either download from the phones browser (stock or Miren) or through my PC and transfer it to the SD; both resulting in the issue.
Here's what I think it is, I think its a issue with the phone's partition/filesystem. The result of switching to the Desire Z Eng Hboot. But Ive went back to the G2 Eng Hboot and stock Hboot, many times. So Im not sure.
Anyway thanks for attempting to help. You gave me some additional stuff to look into.

Touch-Formatter Problem

I tried to reset my nook back to stock, using Touch-Formatter but when I plug the SDcard I see this error message:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Could you please help me to solve this problem?

ur Cache partition need to format ..... try show ur fdisk info and try format it with the same partition sys (ext3)
and check other partitions if they mountable or not to avoid any error , best regards

speedman2202 said:
ur Cache partition need to format ..... try show ur fdisk info and try format it with the same partition sys (ext3)
and check other partitions if they mountable or not to avoid any error , best regards
Click to expand...
Click to collapse
thank you, but I dont found any nook partion in fdisk best regards.

abromr said:
thank you, but I dont found any nook partion in fdisk best regards.
Click to expand...
Click to collapse
try boot with noogie Image
and u will see ur nook partitions

speedman2202 said:
try boot with noogie Image
and u will see ur nook partitions
Click to expand...
Click to collapse
when I boot with noogie image I see in my NST screen Rooted Foreever, but in fdisk I see just 1 new partition (my SDcard)
same result with EASEUS PARTITION MASTER

abromr said:
when I boot with noogie image I see in my NST screen Rooted Foreever, but in fdisk I see just 1 new partition (my SDcard)
same result with EASEUS PARTITION MASTER
Click to expand...
Click to collapse
in fdisk, I have:
Disque 1 Amovible 1.82 Go en ligne (SDcard)
Disque 2 Amovible No media (Nook)
what to do to make the Nook disk visible and I can format it?
I think, I Delete All Partitions (step 4 in How to Restore) with MiniTool Partition Wizard when I executed the following link:
blog.the-ebook-reader.com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch/

did u take backup????

speedman2202 said:
did u take backup????
Click to expand...
Click to collapse
yes, I tooke backup image
I found the nook disk by without partitions (juste 1 primary partition 1.82Go)

abromr said:
yes, I tooke backup image
I found the nook disk by without partitions (juste 1 primary partition 1.82Go)
Click to expand...
Click to collapse
I deleted the backup image :crying:
it's possible to find the backup image in the internet?
if no, what can I do?

Carefully re-partition your Nook and see if there is anything salvageable.
There are update and recovery packages all over the 'net.
The problem is to get your personalized Ids and keys back.

try as Renate told but the main problem is every nook have it's uniq info (ID , Serial , Mac Address , Model...etc) so
i suggest u use any program recovery ro recover ur recovery IMage or go to a specialist and ask him to recover ur deleted data .... it can be recovered ..... or there's another solution , if u have friend own NST glowwhite , take a back up from him and burn in ur nook partition ... ur id and mac address will be like him . but i dont know if it will make wifi work or not .... but i suggest turn off ur wifi to avoid get error and just use ur nook for reading
good luck

Renate NST said:
Carefully re-partition your Nook and see if there is anything salvageable.
There are update and recovery packages all over the 'net.
The problem is to get your personalized Ids and keys back.
Click to expand...
Click to collapse
thanks, where i can find the Ids and Keys back?
Would the zip file Nook Simple Touch Full_Factory_Restore.zip work for me in this scenario? If so, where can I get the file?

speedman2202 said:
try as Renate told but the main problem is every nook have it's uniq info (ID , Serial , Mac Address , Model...etc) so
i suggest u use any program recovery ro recover ur recovery IMage or go to a specialist and ask him to recover ur deleted data .... it can be recovered ..... or there's another solution , if u have friend own NST glowwhite , take a back up from him and burn in ur nook partition ... ur id and mac address will be like him . but i dont know if it will make wifi work or not .... but i suggest turn off ur wifi to avoid get error and just use ur nook for reading
good luck
Click to expand...
Click to collapse
I recovered my backup image (size 1 958 739 968) is the good size?
wath can I do now?

abromr said:
I recovered my backup image (size 1 958 739 968) is the good size?
wath can I do now?
Click to expand...
Click to collapse
The backup image should be close to 1.86 GB, so your's could be good.
If in Windows, now you should:
1) create an sdcard to boot the nook from with noogie in it. Search the forum for noogie.img.gz and you should find instructions
2) insert the card in the nook, restart the nook, and hook it to your computer
3) in your pc run win32diskimager or diskimage and write your backup to the pyhisical disk that's 1.8g GB in size.
4) make sure nothing goes wrong, and if successful eject the sdcard and boot the nook normally.
good luck

srgarfi said:
The backup image should be close to 1.86 GB, so your's could be good.
If in Windows, now you should:
1) create an sdcard to boot the nook from with noogie in it. Search the forum for noogie.img.gz and you should find instructions
2) insert the card in the nook, restart the nook, and hook it to your computer
3) in your pc run win32diskimager or diskimage and write your backup to the pyhisical disk that's 1.8g GB in size.
4) make sure nothing goes wrong, and if successful eject the sdcard and boot the nook normally.
good luck[100/QUOTE]
thank you
in step 4, when I boot my nook I see always in the screen Rooted Forever :crying:
Click to expand...
Click to collapse

abromr said:
srgarfi said:
The backup image should be close to 1.86 GB, so your's could be good.
If in Windows, now you should:
1) create an sdcard to boot the nook from with noogie in it. Search the forum for noogie.img.gz and you should find instructions
2) insert the card in the nook, restart the nook, and hook it to your computer
3) in your pc run win32diskimager or diskimage and write your backup to the pyhisical disk that's 1.8g GB in size.
4) make sure nothing goes wrong, and if successful eject the sdcard and boot the nook normally.
good luck[100/QUOTE]
thank you
in step 4, when I boot my nook I see always in the screen Rooted Forever :crying:
Click to expand...
Click to collapse
lol
remove ur sd card then ur nook will boot up
congratulation at advanced
before i forget
also try connect ur nook to ur computer , cuz may be ur battery run out
Click to expand...
Click to collapse

speedman2202 said:
abromr said:
lol
remove ur sd card then ur nook will boot up
congratulation at advanced
before i forget
also try connect ur nook to ur computer , cuz may be ur battery run out
Click to expand...
Click to collapse
I tray this
I think my backup image is not good, is it possible to check this image? if yes how can I do it?
or this backup is not completely restored in my nook (I used Roadlik Disk Image)
Click to expand...
Click to collapse

abromr said:
speedman2202 said:
I tray this
I think my backup image is not good, is it possible to check this image? if yes how can I do it?
or this backup is not completely restored in my nook (I used Roadlik Disk Image)
Click to expand...
Click to collapse
ok , first boot with noogie image and open partion wizard and lets see ur partion info table
or try post to us fdisk
and u sure ur screen stuck with (Rooted for ever) or(read for ever)
Click to expand...
Click to collapse

speedman2202 said:
abromr said:
ok , first boot with noogie image and open partion wizard and lets see ur partion info table
or try post to us fdisk
and u sure ur screen stuck with (Rooted for ever) or(read for ever)
Click to expand...
Click to collapse
I restored the backup and bootted with noogie, the partition info using partition wizard is:
Partition: Disk 2
Capacity: 1.82 GB
Used: 0 B
Unused: 1.82 GB
File system: Unallocated
Status: None
So, I think the backup is not good.
With Partition recovery I recoveried the old partitions of my nook, and I boot with noogie, the partition info using partition wizard is:
attached screen print
which partitions are should I have?
Click to expand...
Click to collapse

abromr said:
speedman2202 said:
I restored the backup and bootted with noogie, the partition info using partition wizard is:
Partition: Disk 2
Capacity: 1.82 GB
Used: 0 B
Unused: 1.82 GB
File system: Unallocated
Status: None
So, I think the backup is not good.
With Partition recovery I recoveried the old partitions of my nook, and I boot with noogie, the partition info using partition wizard is:
attached screen print
which partitions are should I have?
Click to expand...
Click to collapse
if you run
Code:
fdisk -l /dev/block/mmcblk0
from within ADB you should see something like this:
Code:
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux
And you should be able to mount every partition without errors or warnings:
Code:
mount -t vfat /dev/block/mmcblk0p1 /boot
mount -t vfat /dev/block/mmcblk0p2 /rom
mount -t ext2 /dev/block/mmcblk0p3 /factory
mount -t ext2 /dev/block/mmcblk0p5 /system
mount -t vfat /dev/block/mmcblk0p6 /emmc
mount -t ext3 /dev/block/mmcblk0p7 /cache
mount -t ext3 /dev/block/mmcblk0p8 /data
if this is not you case, then it will take some time and expertise to revive your device.
You'd better go step by step and avoid mistakes (been there, done that) =)
Click to expand...
Click to collapse

[Q] In need of a BOOT.IMG dump

Long story short, I screwed up my internal memory partition table and believe I've got it back.
Problem: I need a dump of /dev/block/blkmmc0p1 (and p5) if at ALL possible from anyone that has a working Nook.Color.
My problem is similar to this one: http://forum.xda-developers.com/showthread.php?t=918772
If only the files on this page were still active on Mediafire: http://forum.xda-developers.com/showthread.php?t=919353
That's the long and short of it. If you guys want some additional info I can provide any information, but as I said, a dump of someones boot partition would definitely help.
Thanks all!
-Josh

Your PM to me says you flashed my 3 zips. I generally don't respond directly to PMs, I prefer the forums. I assume you meant my three zips in my partition repair thread. The repair 145678 zip has a dump of that partition built onto it. So if that flashed successfully, and it still will not let you boot, finding another dump file will not help. If you want one, extract the one from there.
You may need to describe more what you have done and how it is acting now.
Sent from my Nook HD+ running CM10 on Hybrid SD

OK, I'll just start from the beginning with what I've done:
I have a Nook Tablet (not talking about it, just saying... I'm in the right forum lol) and a friend got a Nook Color and wanted to know if I could soup it up the same way.
Well I had it working and like an idiot, I accidently used the Nook Tablet "swap storage" routine to make /sdcard1 <-> /sdcard0 instead of the one for the Nook Color. It took the flash fine and upon reboot it claimed that the SD Card needed to be prepared so I let it format the "card"
That's all she wrote so far. I rebooted it again and it wouldn't even come on. It was at 30% power when I told it to reboot, so I figured it was plagued by the sleep of death so I let it charge all night.
Woke up, still nothing.
I made a CWM bootable SD card and LO AND BEHOLD, it started up without a hitch!!! But it complained constantly of "/cache" not mounting to store its log files (that was earlier today and it has been a LONG day so I cant recount the exact error message). When I tried to install the ROM again, however it failed all around.
Your partition 2 repair file failed at first for me, that's how bad it was.
After many different attempts, I setup a bootable SD card with Nookie and get a little further.
With Nookie, I was able to FINALLY adb into the device and fdisk -l /dev/block/mmcblk0 which revealed an empty table and with wrong cylinder, head, and sector count, which I fixed by using the information found here: http://forum.xda-developers.com/showthread.php?t=942324
After that, I remade my CWM bootable SD card and got better results. /cache errors are gone and I was able to use all three of your zip files for repairing partitions (forgive me for not having the file names handy).
That has gotten me a little further, but now I keep getting errors about /boot not mounting.
Also, I haven't just been using CWM, but also TWRP (which thinks my serial number is all 0s), but when I manually mount /rom I can see in the devconf folder that my serial number has been restored (before I recreated partition table and ran your 3 zips, that wasn't even the case).
I'm sorry this is so scatter brained. I've been at it for a solid 10 hours all while laid up in bed with walking pneumonia, so..yeah...fun times..

It could also be that I didn't partition it properly because partition 1 (the only 1) seems to lose it's file system type every time, while the other 7 remain intact.

If it did not have the proper cylinder head count, how did you repartition it? That quoted thread just says what the proper layout should be, not how to repartition it.
Sent from my Nook HD+ running CM10 on Hybrid SD

Well, I'm not EXACTLY a total n00b. I looked up the busybox/fdisk syntax.
First I did fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0 (as it was reporting nothing right)
That command got me the proper size of the disk and I, with help of the "m" help command" recreated it to this (now that I have adb working in TWRP, I'm back to my preferred parted, so this is not an fdisk printout, but a parted printout):
Number Start End Size Type File system Flags
1 32.3kB 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7937MB 7477MB extended
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext3
7 1941MB 2311MB 370MB logical ext3
8 2311MB 7937MB 5626MB logical fat32 lba
In the past 5 minutes I have used mklabel to wipe partition table (shown above) again and am recreating them... again.
----EDIT-----
Here is that redone partition table:
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7944MB 7483MB extended lba
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext2
7 1941MB 2311MB 370MB logical ext2
8 2311MB 7944MB 5633MB logical fat32 lba

I'm not exactly a noob either and I could not find that -c -h -s command. I've been looking for that forever because I have a device that is showing the wrong count. So thanks.
Let me know how that new repartition comes out. I'll help if I can. I have all the images if you need them.
Sent from my Nook HD+ running CM10 on Hybrid SD

New layout:
Number Start End Size Type File system Flags
1 512B 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7944MB 7483MB extended lba
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext2
7 1941MB 2311MB 370MB logical ext2
8 2311MB 7944MB 5633MB logical fat32 lba
Of your 3 zips, 1, 4, 5, 6, 7, 8 repair seemed to work without error, but I'm back to partition 2 repair not working. ARGH, talk about a step backwards LOL.

jmh363905 said:
New layout:
Number Start End Size Type File system Flags
1 512B 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7944MB 7483MB extended lba
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext2
7 1941MB 2311MB 370MB logical ext2
8 2311MB 7944MB 5633MB logical fat32 lba
Of your 3 zips, 1, 4, 5, 6, 7, 8 repair seemed to work without error, but I'm back to partition 2 repair not working. ARGH, talk about a step backwards LOL.
Click to expand...
Click to collapse
I hope you saved an image of p3. That is critical.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
I hope you saved an image of p3. That is critical.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Hope of backing up any partitions went bye bye when I had to recreate the partition table the first time.
Now, is that the partition with devconf files or the factory.zip partition?
I'm still a bit unclear on that.

jmh363905 said:
Hope of backing up any partitions went bye bye when I had to recreate the partition table the first time.
Now, is that the partition with devconf files or the factory.zip partition?
I'm still a bit unclear on that.
Click to expand...
Click to collapse
P2 is the one with the devconf files. P3 has the factory.zip, but more importantly it has the rombackup.zip which was the backup of p2 when it was manufactured. That is what my p2 repair zip uses when it reconstructs p2. If you don't have that info, you will never be able to boot to stock again. But we can make dummy info so it can boot to CM. If you got a backup of the p2 before it died, you will be ok.
BTW, I just used your fdisk commands to fix my bad cylinder count. Thank you.
Sent from my Nook HD+ running CM10 on Hybrid SD

BTW, I just used you fdisk commands to fix my bad cylinder count. Thank you.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
No prob. That file is LOOOONG gone, but my only hopes are running CM10. Stock is for lusers. I have the serial number and wifi mac address written down so if we need to fake a few things, ANY help you can offer to get this thing working will be great.
I DID forget to mention that I have a TWRP backup of the Boot, Cache, System, and Data, but it won't restore :-/ I'm sure they're filled with all kinds of goodies.
Again, ANY HELP would be so great.
You tell me what you need me to submit and I'll be more than happy.

assert failed: (getprop("ro.product.device:") == "zoom2" || get prop("ro.build.product") == "zoom2") || getprop("ro.product.overallname:" == "NOOKcolor")
^^^ an error I'm getting trying to "install" the romrestore.zip file from my TWRP backup files. I'm not an expert, but is that saying my device and product name have been changed to something they shouldn't be?

jmh363905 said:
No prob. That file is LOOOONG gone, but my only hopes are running CM10. Stock is for lusers. I have the serial number and wifi mac address written down so if we need to fake a few things, ANY help you can offer to get this thing working will be great.
I DID forget to mention that I have a TWRP backup of the Boot, Cache, System, and Data, but it won't restore :-/ I'm sure they're filled with all kinds of goodies.
Again, ANY HELP would be so great.
You tell me what you need me to submit and I'll be more than happy.
Click to expand...
Click to collapse
You need to make three files to put in the devconf folder.
DeviceID has your 16 digit serial number
SerialNumber has the same info
MACAddress has your 12 digit MACaddress with no spaces or colons.
Also BootCnt should automatically get made by the system. It will not hurt to have a dummy one there. 4 bytes with nothing in it. That is the one that triggers an 8failed boot reset if it ever gets up to 8 in that file.
Also in the main folder should be a file call BCB (which means Boot Control Block). That should get created automatically by TWRP or CWM.
You get all that in there and flash a CM ROM and it should boot.
P3 does not matter unless there is a problem and stock recovery needs it. As long as you make sure that the DeviceID file is intact, you will never need p3.
Sent from my Nook HD+ running CM10 on Hybrid SD
---------- Post added at 06:50 PM ---------- Previous post was at 06:47 PM ----------
jmh363905 said:
assert failed: (getprop("ro.product.device:") == "zoom2" || get prop("ro.build.product") == "zoom2") || getprop("ro.product.overallname:" == "NOOKcolor")
^^^ an error I'm getting trying to "install" the romrestore.zip file from my TWRP backup files. I'm not an expert, but is that saying my device and product name have been changed to something they shouldn't be?
Click to expand...
Click to collapse
No, it is because the original device name was zoom2. You do not want to flash that anyway, since you do not have a working p3. It does the same as my repair p2 zip.
Sent from my Nook HD+ running CM10 on Hybrid SD

OK from ADB Shell, here are my commands so far:
cd /
mkdir rom
mount /dev/block/mmcblk0p2 rom
cd /rom
mkdir devconf
echo 2011460062572006 > DeviceID
echo 2011460062572006 > SerialNumber
echo 58671A19B85F > MACAddress
Do I need to chmod these files as well?

jmh363905 said:
OK from ADB Shell, here are my commands so far:
cd /
mkdir rom
mount /dev/block/mmcblk0p2 rom
cd /rom
mkdir devconf
echo 2011460062572006 > DeviceID
echo 2011460062572006 > SerialNumber
echo 58671A19B85F > MACAddress
Do I need to chmod these files as well?
Click to expand...
Click to collapse
Nope, once you verify those files are really there, just flash a CM ROM.
edit, well now that I think about it you might want to set it for 644. I usually flash those and that is what CWM sets them as.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
Nope, once you verify those files are really there, just flash a CM ROM.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
-- Install /sdcard/cm-10-20130324-NIGHTLY-encore.zip ...
Finding update package....
Opening update package....
Installing update.... (a couple minutes like it's doing something)
*Verifying filesystems....
* Verifying partition sizes...
E: Unable to mount '/boot' (tw_mount)
E: Unable to mount '/emmc' (tw_mount)
E: Unable to mount '/emmc' (tw_mount)
E: Failed to mount /emmc (Invalid argument)
E: Failed to mount /emmc (Invalid argument)
E: Failed to mount /emmc (Invalid argument)
Rebooting system after that yields in the same ole same ole: First, using the software reboot failes.....always.. I'm taken to a blank (not backlit) screen that I have to press and hold Power + Nook. If I press both of these and an SD card is present, I'll get recovery again. If an SD card isn't present, it just sits there with a blank screen. (not backlit)
Ready to put a hole through it. LOL

jmh363905 said:
-- Install /sdcard/cm-10-20130324-NIGHTLY-encore.zip ...
Finding update package....
Opening update package....
Installing update.... (a couple minutes like it's doing something)
*Verifying filesystems....
* Verifying partition sizes...
E: Unable to mount '/boot' (tw_mount)
E: Unable to mount '/emmc' (tw_mount)
E: Unable to mount '/emmc' (tw_mount)
E: Failed to mount /emmc (Invalid argument)
E: Failed to mount /emmc (Invalid argument)
E: Failed to mount /emmc (Invalid argument)
Rebooting system after that yields in the same ole same ole: First, using the software reboot failes.....always.. I'm taken to a blank (not backlit) screen that I have to press and hold Power + Nook. If I press both of these and an SD card is present, I'll get recovery again. If an SD card isn't present, it just sits there with a blank screen. (not backlit)
Ready to put a hole through it. LOL
Click to expand...
Click to collapse
Two things, look at my edit above. And did you format those partitions after creating them? You need to. flashing my repair zip and format zips will take care of 145678. You still need to manually format p2 as fat32.
Edit: It looks to me like TWRP is doing some more checking that CWM does not do. You might try using CWM while trying to fix this. Also the new TWRPs do not like my zips.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
Two things, look at my edit above. And did you format those partitions after creating them? You need to. flashing my repair zip and format zips will take care of 145678. You still need to manually format p2 as fat32.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
I verified that the files were still present after a reboot and they were (plus a Lost+Found directory indicates that there's an active, formatted partition), but I am going to go ahead and format both boot and rom with FAT32 file system:
ADB Shell Commands:
mkfs.vfat /dev/block/mmcblk0p1
mkfs.vfat /dev/block/mmcblk0p2
Then attempted restoring again. Same process as before, except NO errors AT ALL this time, so seeing it as a ray of hope, I followed it up with the GApps package (in hopes that THIS IS IT....)
Good news, PROGRESS has been made:
Now, WITHOUT an SD card, the unit will power on and give me the Cyanoboot Bootloader, but just hangs at loading from EMMC 01
What do you suggest now? ( and when this is all said and done with I'm gonna be needing your PayPal account so I can thank you)

Those other partitions need formatting too. Use my 5678 format zip.
Sent from my Nook HD+ running CM10 on Hybrid SD

Link2SD mounting /dev/block/vold/179:2 on /data/sdext2 failed: No such device

Hello. I install CM7 with this guide on wiki cyanogenmod org (Install_CM_for_jordan)
I create 2 primary partition on my sd card: FAT32 10GB and Ext4 5GB
I have fresh installation, connect WiFi, google account and I install Link2SD.
Then i Try (re)create mount script in Link2SD(Plus) I got following error:
Mount script error
Mount script cannot be created.
mount: mounting /dev/block/vold/179:2 on /data/sdext2 failed: No such device
I don't know how to fix it. I searched on forums but I can't understand. Can you help me fix it step by step?
I really need Link2SD. I used it on my previous phone and work great.
How I should fix this?

Hi,
I think your header tells it all.
/data/sdext2 failed: No such device. You formatted your sd card with ext4 but link2sd is looking for ext2.
Have your tried to format the 2nd partition of your sd with ext2?
In my point of view 5GB for the link2sd partition is too much. 1 GB should be sufficient.
Regards, Gazorbeam

Hello guys, I have the same problem. Thanks Gazorbem for your advice, but app itself asks about the system that it will search for (user can indicate whether it is ext2 or ext4 etc.) I tried all options available (although I know that my partition is in format ext3) but problem still remains - app still can't mount this partition