Database Users

Booting Android from sd card on Dream/G1

Hi all,
Here are my findings about how to boot android from an SD card, useful for example to test development Android builds without messing your phone. This procedure was inspired by legacy GNU/Linux boot process and then should work on most hardware with a flashable recovery.
########################################
I can't stress enough the fact that this procedure is targeted to experienced user. A good knowledge of linux/android booting process is more than required. This procedure is not meant to be useful to most people given its limitations (no recovery mode, rebuild of boot.img required)
########################################
I won't propose a step by step tutorial as it's better to understand how to do it and adapt the procedure to each need.
Two modifications are required:
1. Declare to mount sd card partitions instead of internal flash volumes. This has to be done in the init.rc script.
For example:
mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
with
mount ext2 /dev/block/mmcblk0p6 /system
2. For some reasons, in the boot process, sd card partitions generally show up later than the mount actions, so it is generally necessary to add a timer in init binary to give to to the kernel to detect sd card partitions before mounting them (adding a sleep(5) after the "A N D R O I D" text in init.c is enough).
Build your special boot.img embedding those two modifications and flash it on the recovery volume of your phone. Now, booting into recovery will launch the system on your sd.
Regards,

I would like to report success on booting the G1 from a system located on sd card (cyanogenmod 4.2.7.1). I will describe the procedure step by steps when every thing is okay.
There is just an issue that you might have encountered during cyanogenmod ROM cooking, all wireless connexions (wifi, BT, GSM) do not work. The same system on flash if okay. I made a diff on boot log messages and the only notable difference is this error :
E/MemoryHeapBase( 83): error opening /dev/pmem_gpu0: Permission denied
E/MemoryHeapBase( 83): error opening /dev/pmem_gpu1: Permission denied
E/MemoryHeapBase( 83): error opening /dev/hw3d: Permission denied
I tried to chmod 0555 /dev/pmem* with no success.... Any idea ?

Although I finally managed to have a usable system, this work is still experimental. Please fell free to test and report success, failures here so I can improve the thing.
Let's see how we can boot a copy of cyanogen ROM 4.2.7.1 located on sd card. The main purpose is to test future ROMs (eclair ?) without messing up your phone...
DISCLAIMER : This procedure is targeted to experienced user. I am not responsible if you loose your data, your phone or your Mom !
Prerequisites are :
- adb and fastboot operationnal on your host computer
- Boot image file boot.img :
http://www28.zippyshare.com/v/19654421/file.html
- files data.cpio.gz, system.cpio.gz (data.cpio.gz and system.cpio.gz are unmodified images of a fresh install of cyanogen ROM that fit the modified boot.img) from :
http://www15.zippyshare.com/v/57489279/file.html
http://www15.zippyshare.com/v/13077582/file.html
1.
Create 3 partitions on sd card. The first one (vfat) is to store your music, videos etc. The second and the third will hold /data and /system. Result shoul look like this :
# fdisk /dev/block/mmcblk0
Command (m for help): p
Disk /dev/block/mmcblk0: 1977 MB, 1977614336 bytes
64 heads, 63 sectors/track, 957 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 864 1741792+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 865 903 78624 83 Linux
/dev/block/mmcblk0p3 904 957 108864 83 Linux
Command (m for help):
2.
Copy data.cpio and system.cpio on the first partition of your sd card.
3.
Connect to your device with adb :
adb shell
4.
Mount mmcblk0p2 on temporary folder and extract user.cpio.gz archive :
mkdir /dev/tmp
mount /dev/block/mmcblk0p2 /dev/tmp
cd /dev/tmp
gunzip -c /sdcard/data.cpio.gz | cpio -i
cd /
umount /dev/tmp
5.
Mount mmcblk0p3 on temporary folder and extract system.cpio.gz archive :
mount /dev/block/mmcblk0p3 /dev/tmp
cd /dev/tmp
gunzip -c /sdcard/system.cpio.gz | cpio -i
cd /
umount /dev/tmp
6.
Reboot the phone in bootloader :
adb reboot bootloader
7.
Boot the phone with custom boot image :
unzip boot.img.zip
fastboot boot boot.img
Reports are welcome !

I haven't tried this, but great idea. Well done.
Maybe a nice additional idea would be a boot-menu style idea. Eg, detect OS on mem card and display a menu of "Internal" or "SD Card"?

I'm on it but as it will imply flashing people's phone, I need more testing and suggestions from experienced hackers. I only own my G1 for 5 days...

I acytually just started a thread about this in the Dream development subforum!
Some suggestions:
-Use a recovery image to boot the ROM on the sd card (look at modifying the CM recovery image) if this is possible. This way, you can boot from sd card when you want to, by booting into recovery image, without interfering with the flashed rom at all. No worries that flashin a new rom will require a reflash of your bootloader. Also, you can use the ROM installed in flash after a reboot without any hassle, which would be very useful when testing a ROM from the SD if it doesn't work very well and you need a working phone.
-Have the /data and /system-partition as folders on the 4th partition on the SD card, or as logical volumes on a primary one. Why?
Well, many people have their sd-cards set up with fat, extX, swap in that order. The partition layout you have described here simply isn't compatible with that, and will require a separate SD card just for this testing (which everyone might not have).
I must say, I think this is a GREAT idea! I so often want to test a few ROMS, but often they don't get the test-time they deserve because I need to swicth back to my working environment for job/uni the day after. This would be a great way to test a ROM thoroughly. And also it would be the best way to give a ROM a quick testdrive. switchroming back and forth is, for all its simplicity, hassle.

Using the recovery is the only way I found at the moment to boot from the sd card and was about to extend cm recovery with a dedicated menu Nevertheless, there will be a limitation with that: it will not be possible to use a different kernel for the system on sd as it will have to use the kernel of the recovery... Anyway, many custom roms around here use cm kernel (even those I saw with eclair) so it is not so problematic I think (tested Eugene373 AOSP20 yesterday). Anyway, it is possible to adapt the recovery with a test kernel...
I think I found a workaround for sd partitionning scheme pb, using bind mounts but I have not tested already. I will work on it this WE.

If I remember correctly you can use the command "reboot recovery" from the recovery shell to reboot again into recovery. It could mean that it is possible to choose what (kernel) to boot after the reboot. Even cyanogenmod has made quite a few changes to the kernel since the recovery image came out, and I think it would not be a very good solution to use the same kernel as the recovery image for all ROMs loaded via SD. (Especially the Hero ones won't work at all, I'm afraid.
It could also be possible maybe, to tweak the built-in bootloader into booting form either SD-card or from the internal flash? It already has the possibility to boot different things on different keypresses (home for recovery mode, and camera for fastboot). I have (again) no idea of its capabilities for reading anything off of the sd card, though.

I get your point naguz . I am not satisfied either with the solution of using the recovery kernel to boot the system on sd. I found that it adds quite much complexity to the init process: I tweaked the recovery executable to add an entry to boot from sd but I faced troubles in services startup and pre-init definitions. I think that the solution of using the recovery menu to choose to boot from sd have to be abandoned as it will require heavy additional changes to the init.rc scripts of the second system and will break its advanced features.
The ideal solution (as you suggested) would be to tweak the bootloader to boot natively from the sd card but unfortunately, we do not have the sources of the SPL (tell me if I am wrong) so it is definitely not possible.
The remaining solution is to use the recovery partition to flash the boot image of the second system. I works well, just press the home key and the second system boots ! The drawback is that you do not have recovery any more... Personnaly, I don't find that so problematic as I is still possible to boot a recovery image with fastboot when needed, so I think I will stick to this solution. I somebody have another solution, I am ok to investigate...

Aha, it makes sense that booting the sd directly from recovery mode would mess something up. I would think some of the same problems would be faced when booting the kernel from the recovery partiotion, doesn't it look like a different device to the kernel? Well, if it works, it works.
Regarding the source of the SPL, I have no idea, but I know hyakuro (a (former?) user here) has released a modified one. Trying to get in touch with him
As for the latest method: Is the recovery partiotion big enough to hold both the recovery image AND the kernel? If so, one could maybe have both. Maybe make a new "recovery image" that can either boot from sd or boot recovery image? Just throwing out ideas here.
Personally I don't see the big problem with not having a recovery image, as I would (in a dual-boot scenario) already have another, working install on the flash that I could use if the one booted from sd wasn't good enough. Re-flashing the recovery image could also be done from the working ROM in flash, for those without the SDK tools.
I think, however, that quite a few people will object to not having a recovery image.
Btw, was your latest working test done with one (4th) partition on the sd card for loading the ROM from SD? If so, new instructions please. I'd like to give it a try.

I think that it is technically impossible to boot directly from the sd, even with the sources of the SPL as drivers are required to drive the sd that can not be included in a SPL. It is the same issue on PC with PCMCIA network cards for instance. IPL+SPL has to be seen more or less like a simple BIOS...
The recovery partition size is not a matter her. The problem is the lack of control over what has to be booted as the only action we can make in the SPL is the HOME key to choose a regular boot or a recovery boot (the system on SD here). I think I have a good knowledge now of the boot process and I think we can not got further than that, despitely...
I am now trying to have /data and /system on the same partition, mount them on /mnt and bind mount each directory on /system and /data but with no succes . investigating....

Okay, bind mounting was a dumb idea of mine. The solution is to create an extended partition with 2 logical drives in it, so partitions are:
[1-3] FAT and/or EXTX and/or swap as needed (I have personnaly just one partition here)
4 extended
5 ext2 for /data
6 ext2 for /system
Now its time to bake a boot.img with the kernel of the system on the sd card + the ramdisk. I do not explain how to do that, google knows :
1.
In the ramdisk image, put my modified init program attached hereater
2.
In the init.rc script, change the lines that mount /data and /system :
mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
with
mount ext2 /dev/block/mmcblk0p6 /system
and
mount yaffs2 [email protected] /data nosuid nodev
with
mount ext2 /dev/block/mmcblk0p5 /data
Flash boot.img on the recovery and reboot in recovery... That's all.

Jahrome,
Trying the idea on the HTC has a subtle difference. So I'm curious what change you put in the /init process.
Lets say the image one wants to use is the 'eclair' branch. This branch uses vold, so the block device, such as '/dev/block/mmcblk0p#', does not appear to be created until the vold service is started, which is after the init.rc mount operations. So the mount proposed does not work.
Curious what changes you made to the init process that might give me some ideas of what might be the simplest change. It seems that there is a relatively easy solution, that I don't yet see.
Ideas (or additional questions to clarrify) appreciated...

Hi Dale !
On which HTC are you trying the trick ?
First your trouble is not related to eclair as I successfully booted eclair on my G1 with this trick. You need to add a timeout in init so as it waits for the kernel to detect sd card partitions (need to recompile init, or use my recompiled init).
Vold has nothing to do at this point
Hope this helps

Init Delay for SDisk
Thanks for the reply. That's what I needed, it seems so ungraceful.
I thought vold was enabling something to make the kernel's discovery of the SD partitions. It is "by coincidence" that the log of the vold occured shortly before the adding of the block-device event. My apologies for not recognizing the coincidence of the log entries.
I had hoped the solution was a bit more "graceful", though I can't say what that would be or why a sleep is "ungraceful". I would like a "mount retry for n-seconds" option in the init.rc, that would be slick. Nonetheless I will add in a sleep-spin-check for a few seconds.
For the record, we are discussing the change to:
android-source: .../system/core/init/init.c
code-routine: main()
code-location: Somewhere after the "A N D R O I D" text
code-change: add in a sleep spin-check of some sort
I appreciate the comment that all we need is just a sleep. I think this completes the thread?!

Most interesting...
This is something akin to how I am using my company's Android solution for the Beagle Board...
In that environment, the entire kernel and rootfs are located on a SD/MMC card. The environment variables and boot script are stored in the NAND chip
through a "setenv" command. The U-boot monitor on the hardware defaults to run the boot script unless there is any user interaction. This image can then be converted into a typical distribution that can be flashed and ran without the SD card...
I have wondered about the implementation of this approach on my G1, but I have not had time to test it out. It is good to see that there are others that are interested in this as well...
I will be following this thread and will try to help in any way if I can... meaning if I can get some free time...
If you are interested in our Beagle Board solution, it is open source and can be found by a simple Google search using "Android rowboat"...
L8R...

very easy fix.
rename the /init to /init.android (or whatever you like)
create an init script. have it prompt on boot too boot from sd or internal. symlink the init.rc from /system. That way you only need one boot.img for multiple builds. We've been doing this a really long time on the android on vogue project. My development phone is simple, I hold down the menu button if I want to boot from the sdcard otherwise it boots from the internal.
Oh and don't worry about this.
jahrome said:
log messages and the only notable difference is this error :
E/MemoryHeapBase( 83): error opening /dev/pmem_gpu0: Permission denied
E/MemoryHeapBase( 83): error opening /dev/pmem_gpu1: Permission denied
E/MemoryHeapBase( 83): error opening /dev/hw3d: Permission denied
Click to expand...
Click to collapse
That's just that you don't have HW3D enabled in your kernel. It's important to note that if you're trying to use multiple builds that eclair with 3d and donut use different kernels.

Exactly the vogue and kaiser have been doing this for ages. If you want you can also boot ext2 and squashfs images. It's pretty simple stuff.

Anyone have a backup of the files in post #3? I've been trying this solution with files of my own creation (as in: my own cooked boot.img, and data/system files) but it doesn't seem to get past the G1 boot screen (as in: blank screen.) I've also tried the recovery boot solution however it gives me the same reaction. It leads me to believe the problem lies in my boot file.

ok anyone interested in creating a simple step by step manual? and can someone post the files again please?

[Q] How do I partition the eMMC to support Custom ROMs?

I bought my NC last week and immediately rooted it with out a hitch using ManualNooter for stock 1.2. In the process of trying to flash Phiremod my NC locked up in CWM when doing a wipe data/factory reset as instructed. I did a hard reset and tried to load Phiremod any way, which failed. I ended up using the backup I made of the rooted clean stock OS and it is working.
I read this thread
http://forum.xda-developers.com/showthread.php?t=1077973
and mine has the same issue of a partitioned eMMC that only reports 1GB. This prevents me from loading custom ROMs and side loading any applications.
One of the posts on that last thread mentions how dual booting essentially repartitions your eMMC to allow for the said dual booting, so I tried the "Step 1" in the repartition process here...
http://forum.xda-developers.com/showthread.php?t=959461
And it failed, but did boot back into my stock rooted OS.
My question is...
Is there a way to repartition my NC with what seems to be a new partition scheme that B&N moved to so that I can load custom ROMs, sideload programs, and/or dual boot off of eMMC?

Would like to see this answered as well.

grab your oars....
I'm in the same boat.... I have the 1 gig partition on my new Nook.
I can boot from SD ok but I would rather blow out the stock and save my SD.
Help?
MBK

Anyone out there can help us repartition the newer nooks?

side load partition 1 gb on newer NC's
guys check this out. I am doing it now and will report back after I get this done.
http://forum.xda-developers.com/showthread.php?t=914690
boot repartition with stock 1.0.0 or 1.0.1, then side load 1.2 update from b&n site:
http://www.barnesandnoble.com/u/nookcolor-support-software-update/379002520/
If I read all this correctly.. this should do the trick. as well as re-enabling apk installs correctly with rooted stock?

Already tried that.
You'll get a 1.0.0 or 1.0.1 with 0 Space available and you cannot sideload because of that. All that does is re-write the folders and not partition it.
I even tried changing the factory.zip with an older version in the /emmc and did a system/data wipe through the 8 boot fails and power + n reset.

One possibility
jb7038 said:
Anyone out there can help us repartition the newer nooks?
Click to expand...
Click to collapse
If you are familiar with fdisk and mkfs.ext2 or are willing to learn, and can boot a rooted OS from the SDcard, it should be trivial to delete, resize, repartition, and reformat /data (0p6 -- ext3), /cache (0p7 -- ext3) and /media (0p8 -- vfat). Do note the size of the partitions (especially 0p7/cache) before deleting them.
Then, when you restart the NC, it should recreate the contents of /data and /media to virgin content (meaning you better have backed up any non-B&N content). You will have to reregister with B&N, so you should probably do this on an UNROOTED Nook.
This is an experiment that I have wanted to try, but have not had the time; I've been too busy doing other experiments, like having B&N do the intentional repartitioning. I was using internal dual boot before, but uninstalled it before the repartitioning, because I knew there would not be enough space for dual boot afterwards.

I'm just unfamiliar with the block sizes and the commands to partition/change it.
/dev/block/mmcblk0p6 115 789 5421906 83 Linux
/dev/block/mmcblk0p7 790 834 361431 83 Linux
/dev/block/mmcblk0p8 835 965 1052226 c Win95 FAT32 (LBA)
Click to expand...
Click to collapse
6 938MB 6490MB 5552MB logical ext3
7 6490MB 6860MB 370MB logical ext3
8 6860MB 7937MB 1077MB logical fat32 lba
Click to expand...
Click to collapse
____________________________________________
I do have the NC I'm suppose to send back that's fully wiped.
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
4 heads, 16 sectors/track, 242432 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
~ #
Click to expand...
Click to collapse
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
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
(parted)
Click to expand...
Click to collapse
I'd be willing to partition it myself before I send it back if someone could walk me through it.

DeanGibson said:
If you are familiar with fdisk and mkfs.ext2 or are willing to learn, and can boot a rooted OS from the SDcard, it should be trivial to delete, resize, repartition, and reformat /data (0p6 -- ext3), /cache (0p7 -- ext3) and /media (0p8 -- vfat). Do note the size of the partitions (especially 0p7/cache) before deleting them.
Then, when you restart the NC, it should recreate the contents of /data and /media to virgin content (meaning you better have backed up any non-B&N content). You will have to reregister with B&N, so you should probably do this on an UNROOTED Nook.
This is an experiment that I have wanted to try, but have not had the time; I've been too busy doing other experiments, like having B&N do the intentional repartitioning. I was using internal dual boot before, but uninstalled it before the repartitioning, because I knew there would not be enough space for dual boot afterwards.
Click to expand...
Click to collapse
Dear God I would love to try but honestly I don't know a think about command line linux. Also, mine is already rooted, but I can always take it back to stock.
If someone gets this to work please document the process. I would really like to be able to use the internal memory for custom ROMs and be able to side load programs.

Anyone that can help us?

Unable to to Boot after CM7 install

A friend of mine tried to install CM7 on his NookColor. Something went wrong and so he brought it to me. I've done dozens of these. I thought it would be an easy fix so I stuck in my trusty SD boot card with encore_CM72-MiRaGe-03042012. I booted into CWM and did a factory reset and installed encore_CM72-MiRaGe-03042012. I booted it up and expected it to be fixed.
It did the same thing this time which is to boot to the initial splashcreen and then go blank. You can tell the screen is still backlit, but it never changes. You have to hold the power button for 30 seconds to turn it off.
When I boot back into CMW I see some unexpected messages
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
I tried installing CM7 again and watched the messages closely. It says
Installeding update
Install from sdcard complete.
Reboots the same way
Can anyone point me in the right direction to fix this? Thanks

Well, I spent all day yesterday Googling and searching all the forums on XDA Of course I started with Dummies Guide to Fixing 'My Nook Won't Boot'. It is incredibly out of date and is likely to do more harm than good. I think that if it is going to be a sticky, then at least it should show current, relevant information.
I tried [HOW-TO] : Restore Nook Color back to stock EASILY!. I was unable to format several of the partitions specified, but proceeded anyway. It appeared to install OK, but now I am stuck at the N when it boots.
I am continuing to search but I keep running into dead links, downloads that say they will take 5 hours, and references to outdated files. I really would appreciate some knowledgeable help here guys. Thanks

I have the same deal. I think since the WIP clockwork update. I've tried most of the fixes from the links as I still have most. I tried everything you have as well as trying restoring and using different versions of clockwork and trying to get a cache up to no avail. The please keep me posted because this is the first replica of my situation. I am using an Asus t101 now so I'm in no hurry but I've had me NC forever and love the reading size.
Good luck.
How do you create or fix the cache for e:? I can you ADB into clockwork?

Just in case anyone ever reads this thread I thought I would give some more information regarding my problem.
I am able to get into CWM 3.2.0.1 internally. I stiil can't get any ROM loaded though. ( I have loaded several different ROMS to the NC previously including the CM7 nightlies from 75 to 130, so I am well versed in how to do it).
I'm thinking there is something wrong with my partitons. I'm not well versed in exactly what happens during the boot process and what is on each partiton.
I though it might be useful for those people who know about this stuff if I supplied more info (since my eyesight is giving out from reading so many threads)
If I go into the mounts and storage menu and do severals format, this is what I get.
Format system - Error formatting /system!
Format data- Error formatting /data!
Format cache- Error formatting /cache!
I was afraid to format emmc or boot.
Does this help anyone?

Have you tried creating a bootable CWM SD card? That always helps me out when things get screwy.
Tried the EMMC recovery repair?
p.s. - NEVER format Boot. You'll have many a difficulty if you do.

I do have a CWM SD card and can boot to that as well.
Neither one works. I tried installing
nookcolor_1_4_1_update.zip
update-nc-stock-1.3.zip
encore_CM72-MiRaGe-03232012.zip
All leave me where I am now

How old is the nook?
What happened when your friend tried to install cm7? What was going on with it prior to installation?

Don't really have much info.
I have no idea how old the NC is.
I believe that the guy had stock B&N running and tried to install CM7 (verson unknown) with a bootable microSD card, I don't know if he was using the latest CWM on the card.

Um........mail it to me. I'll fix it.
Minimum fees apply.

Here's another clue.
I have a dual boot SD card made based on the instructions in
[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [3/26].
If I use it on a stock B&N NC, the SD card works correctly.
If I use it in the borked NC, it still boots into a black screen.
I would prefer to try to resolve this mayself. I have 20+ years in PC support and feel if I can just get the right information, I can fix it.
If I can't get it done in the next 3 or 4 days, I may take you up on it. However, the frind would have to OK it and I don't know how he feels about sending it off. Thanks
BTW, I tried plugging in the USB cable to see if maybe I could try some ADB magic, but the laptop slings an error when trying to load the driver.

Let me amend that last post. I tried the dual boot (this time using the alternate boot image) and successfully got into CM9. Does this help me?

I am trying to find a way to fdisk or mount a way to change pemissions to rw,mode=0755 or but cannot find the usb yet. I will see what I can google.
Seems the emmc permissions are wrong possibly.
Edit: this is what my mount says about the nook when I mount it to linux:
/dev/sdb on /media/0838-AA8D type vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks)

Since I have thee NC booting to CM9 off the SD card, I thought I would load ADB and see if there was something I could do..
I went to [Ref] Nook Color Links |Guides|How To|Utilities| Etc. 12/26 Read FIRST =) in the developer's section and went to the referenced
•Nook Color USB Drivers and ADB Setup (WinXP&7)
The links in that thread are dead. Can someone point out a link to the current prefered method?

have you tried
[UPDATE ZIP] Stock 1.2 update.zip flashable from CWM
from showthread.php?t=1050520

This is nookcolor easy adb 3:
http://db.tt/b3XfztAY
And the USB files file NC:
nookcolor usb
http://db.tt/QRhksG2n

Hi there,
If you are able to boot to CM9 off the sDcard. Try opening up terminal emulator and enter the following commands:
Code:
$ su
# fdisk -l /dev/block/mmcblk0
and paste the output here. That should give you you're EMMC partition layout.
-Racks

Yeah, what racks said. Sounds like you formatted your emmc boot partition to me. In one of the old resurrected threads that you posted to, the OP flat out says they formatted boot.
Don't format boot, everyone.
Post the output of racks command, and we'll know for sure.
If you just formatted (read: erased) the boot partition, then your ROM partition should be intact. That means 8 failed reboot can load the stock firmware. It may be a last-ditch effort for many, but it doesn't require any adb knowledge our even a computer, so I tend to recommend it early.
Reboot as it is loading the cyanogen screen eight times while holding down power,n, and the volume keys. If it doesn't work the first time, do the entire sequence again. Of course, if you enter rack's command, you will see if your ROM partition is still intact which is required for this method to work.

[email protected]:/ # fdisk -l /dev/block/mmcblk0
Warning: invalid flag 0x00,0x00 of partition table 5 will be corrected by w(rite)
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 935 7060567+ 5 Extended
[email protected]:/ #

Bonnie_Raitt said:
[email protected]:/ # fdisk -l /dev/block/mmcblk0
Warning: invalid flag 0x00,0x00 of partition table 5 will be corrected by w(rite)
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 935 7060567+ 5 Extended
[email protected]:/ #
Click to expand...
Click to collapse
Yep, your missing the last 4 partitions which are /system, /data, /cache, /media. Which you would need to flash any rom. You're gonna have to re-create them by using fdisk from and SDcard ROM (eg. CM7 or CM9). There's a thread here somewhere that dealt with all that. I'll browse through and see if I can find it for you.
-Racks

This it?
http://forum.xda-developers.com/showthread.php?t=958748
Not sure how to rebuild the missing partitions yet. Appreciate the help fellas.

[HOWTO] flash stock rom without internal sd (Movinand chip damaged and removed)

This guide for GTP1000 internal SD damaged and removed
This link is guide how to remove movinand chip:
http://forum.xda-developers.com/showthread.php?t=1877585
How to flash Overcome Stock ROM
- to prepare you must have
Overcome gb_Stock_save_v5.tar (modem.bin needed),
overcome_kernel_v4.0.0.tar or CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
and root explorer.apk,
- make 3 partition on microSD, 1st fat32, 2nd ext4, 3th ext4,
example : 16 gb -> 13.6gb fat32, 2gb ext4, 0.4gb ext4
use gparted on linux or MiniTool Partition (Windows)
- remove hidden.rfs, movinand.mst from GB_Stock_Save_v5.tar
- copy root explorer.apk to microSD, then plug to gtp1000
- turn on download mode, flash by odin, DON'T CHECK REPARTITION
- after finished, auto restart and will showed error MBR bla bla
(because movinand doesn't exists anymore), ignore it,
if doesn't boot but cwm recovery then wipe factory reset/data, wipe partition,
reboot system
- wait for about 5 - 10 minute, then turn off
- download mode, Flash kernel your choose (must be suport ext4), restart automaticaly when finished. wait until everyting done.
- Unplug usb from PC, on your gtab go to setting, application,
check mark -> Unknown source
development,
check mark -> USB debugging
- connect usb to PC, use adb from PC, and follow this code:
c:\adbtool\adb shell
~$
if your access not root then type
~$ su
take a look your GTP1000 superuser message, then tab allowed
~# mount -t vfat /dev/block/mmcblk0p1 /sdcard
- run my files on your gtab, explore and install root explorer.apk
- open root explorer, tap mount R/W, tap and hold vold.fstab on /system/etc,
select "open in text editor" edit follow this:
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = disable
discard = disable
format_option = -r 1558
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
asec = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
save, exit from root explorer, restart gtab, and profit
Edit:
If overcome kernel fail then try CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar

One think i wanna know..
Why internal-sd broken??
I dont know is corrupt is similar with broken or not but overcome kernel (now with my personal kernel) on recovery mode with parted command can solve my internal-sd problem..

I don't know why
May be oc then over heating or else, but last i use is wifi theater for a long time then turn off by self, stuck on samsung logo when i turn on again
So i restock with overcome, nothing happen, restock samsung firmware, nothing happen too, edit some rc not work too, edit file on /system/etc/init.d and vold.fstab not fully function.
Google it, and found someone (CrhisCTX)with the same problem and he fix by removed movinand chip.
http://forum.xda-developers.com/showthread.php?t=1877585
Sent from my GT-P1000

Would you share your personal kernel for me or us
Sent from my GT-P1000

Btw,
Remove partition and recreate it by parted, doesn't work for me, when i restart partition will back as it, and data still there, some kind read only partition, i don't know
Sent from my GT-P1000

goofey2012 said:
Btw,
Remove partition and recreate it by parted, doesn't work for me, when i restart partition will back as it, and data still there, some kind read only partition, i don't know
Sent from my GT-P1000
Click to expand...
Click to collapse
Im sorry my english is not good enough but can u give 'mount' and 'parted /dev/block/mmcblk0 print' result ?
If internal-sd broken so which partition u use for /data ? As long as i know /data use mmcblk0p2 and if internal-sd broken i thing u can use that partition too..

Yes it is, thats why i create 3 parition. Fat32,ext4,ext4
After remove movinand chip from main board, mmcblk1 automaticaly known as mmcblk0, but the blocks still on /sys/devices/platform/s3c-sdhci.2/mmc_host/mmc1
mmcblk0p3 mount as /preload (note: on gb)
mmcblk0p2 mount as /data
mmcblk0p1 not automaticaly mount as /sdcard
So thats why i need edit vold.fstab manualy
Sent from my GT-P1000

Mmm i see maybe internal-sd is realy broken not only corrupt.. coz if only corrupt parted, fat.format, mkfs.ext2 or other command can solve it..

savie said:
Mmm i see maybe internal-sd is realy broken not only corrupt.. coz if only corrupt parted, fat.format, mkfs.ext2 or other command can solve it..
Click to expand...
Click to collapse
Can you share the code how to mount external sd like your pic attach in other thread.
savie said:
How about this one...
Click to expand...
Click to collapse
Sent from my GT-P1000

mounting script
Sorry for late respon.. I only add that script to init.d folder.. Make sure mmcbkl1p2,3,4 as ext4 if that partition as rfs so need edit ext4 to rfs on script file..
I use that script to check/modify my 2ndRom on 1stRom..

savie said:
mounting script
Sorry for late respon.. I only add that script to init.d folder.. Make sure mmcbkl1p2,3,4 as ext4 if that partition as rfs so need edit ext4 to rfs on script file..
I use that script to check/modify my 2ndRom on 1stRom..
Click to expand...
Click to collapse
I think your script doesn't change /data to mmcblk1p2
Sent from my GT-P1000

goofey2012 said:
I think your script doesn't change /data to mmcblk1p2
Sent from my GT-P1000
Click to expand...
Click to collapse
Yupz its doesnt as i say before it only help me to know my 2ndRom is exsist when i use my 1stRom..
Dont confuse with double mount /system (thats bugs on my kernel till now) in fact its /system running on mmcblk1p2

i would to thank you
so i've try it but i know nothing about android system files so i 'm a big noob )
but :
i 've flashed like you say just the rom i ve used overcome 7 4.10
How to flash Overcome Stock ROM
- to prepare you must have
Overcome_7_Series_v4.1.0_Wipe
overcome_kernel_v4.0.0.tar or CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
- make 3 partition on microSD, 1st fat32, 2nd ext4, 3th ext4,
example : 16 gb -> 13.6gb fat32, 2gb ext4, 0.4gb ext4
use gparted on linux or MiniTool Partition (Windows)
and edit vold.fstab with note pad with
- open Overcome_7_Series_v4.1.0_Wipe in winrar "windows users",vold.fstab on /system/etc,
select "open in notepad ++" edit follow this:
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = disable
discard = disable
format_option = -r 1558
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
asec = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
save your new file in the overcome zip and boot your gtp1000 tab in recovery mod and go to install zip from internal and let do it the gtp1000 will reboot , it's take time so and you will see your fat 32 partition as internal sd ))) i hope taht answer will help
thank too all develloppers

why only this stock ROM can be flashed ? I want arabic stock ROM how can I flash ? I tried but with no success

Weird ! I followed all steps but I don't see my FAT partition ( 13gb ) in phone Storage ! what's wrong ?
what's working vold.fstab I have to use to solve that ?

bump !

psytr0nic said:
Weird ! I followed all steps but I don't see my FAT partition ( 13gb ) in phone Storage ! what's wrong ?
what's working vold.fstab I have to use to solve that ?
Click to expand...
Click to collapse
yes
mine too
please help..
what to do ...

im not sure this thing work really ... I tried about 3 times on 3 different phones! best seem to change emmc chip

I'm curious as to feasibility of either swapping this Chip for a larger 32GB Chip, or simply replacing it if need be.
Seems to me the hard part would be finding the correct kind of Glue to use though. I can't imagine that getting hold of these Chips would be any more harder then any other Part of the P1000...

cocomeoo said:
yes
mine too
please help..
what to do ...
Click to expand...
Click to collapse
let me see your vold.fstab

[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