Database Users

[Q] Cannot Format /Data

Whenever I try to format /data through CWM 3.0.2.8, it returns the message.
error while formatting /data
Click to expand...
Click to collapse
Also when I try to restore a backup, CWM cannot format /data.
I've also tried to install CM7. It says it completed its install in CWM but when I reboot, it retains the OS (rooted stock 1.2) I was currently on.

Me too. I just updated to MR1 and I am trying to restore the /data directory and I can't.

There's one thing I noticed about this refurb'd nook color. The space available in the device info is 1GB. Shouldn't it be higher or did they change the file structure with the latest models?
Also, I went into ADB and mounted EMMC. The last modified date for the files in there is May 4th.
Edit
Not sure if this would help.
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
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 (LB
A)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/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 (LB
A)
~ #
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
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 6490MB 5552MB logical ext3
7 6490MB 6860MB 370MB logical ext3
8 6860MB 7937MB 1077MB logical fat32 lba
(parted)
Click to expand...
Click to collapse

Someone responded back to me on this forum.
http://androidforums.com/b-n-nookcolor/333668-format-internal-partition.html#post2672750
Barnes & Noble has started shipping new NOOK Color devices that are partitioned to allow only 1 GB of "user sideloaded" storage. The remaining 7 GB are partitioned for the OS, apps from the new B&N Apps store, and items downloaded directly from B&N. For the typical (non-rooted) device, the user would have to use the microSD slot for additional storage. I suspect you got one of the newly partitioned devices, which is why you are now seeing only 1 GB instead of the previous 5 GB of storage available.
Click to expand...
Click to collapse
Is there anyway to repartition the new devices or I'm stuck with this? If not, it's going to prevent me from dualbooting. This might also be the cause of my second problem, installing CM7 and still ending up with the original OS.

Oh man am I glad I found this thread. I was freakin' out when I couldn't load phiremod onto my newly purchased NC. Turns out I can only see 1GB of storage like the others in this thread. Hopefully some one will find a way to repartition the newer devices otherwise I am stuck with a rooted NC running the stock ROM with no way to return it.

You can just "Reset to factory default" and it'll remove the root. Then you can try to return it or exchange it. I'd probably say this if they ask for a reason...
"It's showing 1GB space as opposed to 8GB space as advertised"
Though I'm wondering why install CM7 doesn't change anything. After installation, it still boots up the stock OS.

jb7038 said:
You can just "Reset to factory default" and it'll remove the root. Then you can try to return it or exchange it. I'd probably say this if they ask for a reason...
"It's showing 1GB space as opposed to 8GB space as advertised"
Though I'm wondering why install CM7 doesn't change anything. After installation, it still boots up the stock OS.
Click to expand...
Click to collapse
Trying to load new ROMS fails because I can't do a data wipe as instructed.

I wonder if they made it so that outside sources can't write or modify /data now but it's still rootable with manualnooter.. I can format the other partitions through CWM and restore them easily.
EDIT
http://www.barnesandnoble.com/nookcolor/features/index.asp?cds2Pid=35583
*1GB = 1 billion bytes; Actual formatted capacity may be less. Approximately 5GB available to store content, of which up to 4GB may be reserved for content purchased from the Barnes & Noble NOOK Store.

I am not sure what kind of security they could have on the actual partitions, but the dual boot ROMS show that resizing the partitions should not be to hard, though it does mean you may lose data (possibly).

I don't mind losing my /data. I rather be able to install CM7 or something on the EMMC as opposed to running it on the SD.
I'd be grateful if someone could show me how to partition it so it's back to the original partition, 4gb/4gb as opposed to 7gb/1gb I think.

I hope something is figured out soon.

Here's the solution to anyone following this thread.
http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110

I had this problem too.. bought a brand new nook color... this is what i did using CWM 3.0.2.8 to boot off SD...
1. used manual nooter 4.5.6
(after applying had all types of popup force close messages about /media this /media that)
2. changed my patitions to match this post
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(Note: Although it said that it didnt write the partitions it actually did)
3. did the 8 boot reset and nook button reset...
(This didn't reset the partitions actually and I had 5.sumthin GB free space not 1GB as before)
4. Manual nooted again then installed Phiremod 6.2 and Dalingrin's Kernel 042411 for cm7....

Sparks1641 said:
I had this problem too.. bought a brand new nook color... this is what i did using CWM 3.0.2.8 to boot off SD...
1. used manual nooter 4.5.6
(after applying had all types of popup force close messages about /media this /media that)
2. changed my patitions to match this post
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(Note: Although it said that it didnt write the partitions it actually did)
3. did the 8 boot reset and nook button reset...
(This didn't reset the partitions actually and I had 5.sumthin GB free space not 1GB as before)
4. Manual nooted again then installed Phiremod 6.2 and Dalingrin's Kernel 042411 for cm7....
Click to expand...
Click to collapse
I did this too and it scared the crap out of me when it kicked me out of fdisk. I thought I hosed it for good. Then when I did the 8 resets it kept going into CWM on the 8th reset. It wasn't until I rebooted it from CWM did it go and reflash itself.
Man that was scary. I thought I had a $250 paper weight.

I was a little freaked out when the fdisk said it didn't work... But reading around I seen that its almost impossible to break it as long as you don't mess with the first 3 partitions so what was the worse case I figured... This must be an issue with the CWR though.. Probably just updating the CWR to format different sizes of the partitions... A format with offset and length feature in an advanced menu... then we can change the sizes to what we want.. But going forward until CWR gets updated every new nook probably gonna have to do the partition change... Not like that's a big deal...

I bought a Nook Color used off craigslist cus they "bricked" it. I thought, no prob, through in the CWM uSD card, erase the data and system, and throw 1.2 on to root.
Can't erase the Data!
They said it was only a few weeks old. I'm guessing it was a refurb with new partition, they tried to root it somehow, and messed it up, then gave up.
Let's hope this fixes it!

Let us know if the partition thing works.. that would be cool.. GL.....

Sparks1641 said:
Let us know if the partition thing works.. that would be cool.. GL.....
Click to expand...
Click to collapse
I did the repartition here:
http://forum.xda-developers.com/showthread.php?t=1094371
and it worked like a charm - finally have CM7 on my 4th Nook!
Thanks to DeanGibson.

[Q] Unable to back-up nook touch

I just bought a nook simple touch and i want to start playing with it, but, before i do this, i want to make sure i have a backup for it.
My problem is that i am unable to see the hidden partiton (the large one). I use ubuntu linux, but i also tried looking for it on windows, following the instructions from this link.
the df -h output is:
Code:
[email protected]:~$ sudo df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 21G 8.1G 12G 42% /
udev 3.8G 12K 3.8G 1% /dev
tmpfs 1.6G 1.2M 1.6G 1% /run
none 5.0M 8.0K 5.0M 1% /run/lock
none 3.8G 684K 3.8G 1% /run/shm
/dev/sda1 100M 28M 73M 28% /media/winboot
/dev/sda2 52G 50G 1.4G 98% /media/Windows
/dev/sda7 189G 178G 1.7G 100% /media/alex
/dev/sda6 31G 16G 14G 53% /home
/home/burfee/.Private
31G 16G 14G 53% /home/burfee
/dev/sdb 237M 82M 156M 35% /media/NOOK
and of course, when i create the image using dd, it looks like this:
Code:
[email protected]:~$ dd if=/dev/sdb of=my_nook_bk.img bs=1M
239+1 records in
239+1 records out
251641856 bytes (252 MB) copied, 15.2308 s, 16.5 MB/s
on windows, also, Roadkil's free DiskImager also sees just this small partition.
there probably is some protection b&n set on the device, but couldn't find any post related to this issue.
my model number is BNRV300
What options do i have?

Use Roadkil - backup the physical disk not the partition - this will of course depend on the number of drives you have - on my laptop it is disk 1 1.86G

as i said, roadkill doesn't see that partition either

Are you booting from a sdcard with noogie (is rooted forever written on the screen)?
If you just boot normally you can only access the media partition and the sdcard.

oh, so this is it... no, i didn't boot with noogie. i booted it normaly. seems like i missed that step. will try with noogie. many thanks!
L.E.: i just figured out why i missed that step - the nookdevs.com site is down so the link didn't work. any reliable source to get that image?
Thanks

@up, right here http://dl.dropbox.com/u/17432768/noogie.zip

ok, i created it. does this look ok to you?
Code:
[email protected]:~$ fdisk -l my_nook_bk.img
Disk my_nook_bk.img: 1962 MB, 1962934272 bytes
128 heads, 32 sectors/track, 936 cylinders, total 3833856 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
my_nook_bk.img1 * 32 155647 77808 c W95 FAT32 (LBA)
my_nook_bk.img2 155648 188415 16384 c W95 FAT32 (LBA)
my_nook_bk.img3 188416 577535 194560 83 Linux
my_nook_bk.img4 577536 3792895 1607680 5 Extended
my_nook_bk.img5 577568 1167359 294896 83 Linux
my_nook_bk.img6 1167392 1658879 245744 c W95 FAT32 (LBA)
my_nook_bk.img7 1658912 2150399 245744 83 Linux
my_nook_bk.img8 2150432 3792895 821232 83 Linux

Looks ok.
Happy hacking

ok, so i was a bit skeptical about the image because i encountered some problems while doing it so i started over.
i'm having some problems with dd when i'm writing the images. before writing the noogie image using dd in linux, my microsd looks ok in gparted (with fat32 filesystem)
After doing this:
Code:
[email protected]:~/Nook/Nook-touch-rootkit$ sudo dd of=/dev/mmcblk0p1 if=noogie.img
155648+0 records in
155648+0 records out
79691776 bytes (80 MB) copied, 35.8831 s, 2.2 MB/s
it shows unknown for file system and cannot be mounted anymore...
the image i used before (to get the output from the previous posts was created on windows with roadkil, but now that doesn't work either.
microsd is class 4
what could be wrong? if i write other images to the disk everything is ok, but the images to root the nook do not work.

afaik the noogie image is in superfloppy format (no partition table, only the filesystem) and thats why gparted doesn't recognizes it.
But the sd-card with the noogie image on it should be mountable on windows and linux (its fat32).
Maybe you could try an other cardreader.

this is very weird... i managed to write the image to the card using "ImageWriter" (aplication for linux) which i think runs the same code i run in the terminal... i don't get what's wrong...
because if i'm doing something wrong i can't be sure that my backup image is ok.
L.E.: my image is ok, just tested it after messing up the rooting process

I think your problem is, that you should write the noogie image to /dev/mmcblk0 and not to /dev/mmcblk0p1 (on the sd-card, NOT on the nook itself).

Question how do I write the noogie image to the SD card with windows??
As said already I looked at the backup thread as said by previous poster but the link is not working.
I did get the noogie image from the other link provided but how do I copy/write the image to the SD card in windows.
Thnx in advance
Edit:
I think I found something in an other thread, they use this program (win32diskimager) to write a .img to a SD card. Will try this one out.

I used this program win32diskimager to write noogie.img to sdcard in the following manner:
- Select noogie.img as "Image File"'
- Select SD card as device
- Click the button "Write"
Then I waited untill it was finished. Put SD card in Nook Touch, started up the Nook, but no screen with "Rooted Forever" showed up and if I continued with the next step, trying to make a copy of the the Nook partition with Roadkils DiskImager then I could not see the 1.82GB partition of the Nook.
Can someone help me on the way.
I started the Nook but did not yet finish registration before I tryed the above. I was in the middle of registration, but decided to make a backup first, so switched off the Nook and did what I described above (my idea was that after the backup of my Nook to skip the registration, as described somewhere else and then root the Nook).
Hope someone could give me some answers.
Edit:
Indeed when I skipped the registration and again booted from the SD card previously made with the noogie.img I got the "rooted forever" screen and I was able to make a backup of my Nook partition. Thnx a lot everyone for making such nice descriptions, OK now try to root it.....

pow3rflow3r said:
I used this program win32diskimager to write noogie.img to sdcard in the following manner:
- Select noogie.img as "Image File"'
- Select SD card as device
- Click the button "Write"
Then I waited untill it was finished. Put SD card in Nook Touch, started up the Nook, but no screen with "Rooted Forever" showed up and if I continued with the next step, trying to make a copy of the the Nook partition with Roadkils DiskImager then I could not see the 1.82GB partition of the Nook.
Can someone help me on the way.
I started the Nook but did not yet finish registration before I tryed the above. I was in the middle of registration, but decided to make a backup first, so switched off the Nook and did what I described above (my idea was that after the backup of my Nook to skip the registration, as described somewhere else and then root the Nook).
Hope someone could give me some answers.
Edit:
Indeed when I skipped the registration and again booted from the SD card previously made with the noogie.img I got the "rooted forever" screen and I was able to make a backup of my Nook partition. Thnx a lot everyone for making such nice descriptions, OK now try to root it.....
Click to expand...
Click to collapse
CAn you please expand on how you got the nook to boot from the SD card (any special key presses?) I managed to write the noogie image on to an SD card. Inserted the card in the nook. Powered it down and then back up again, but didn't see any option to boot from the card. Not sure If I've missed something here.
Thanks in advance

arvindar_n said:
CAn you please expand on how you got the nook to boot from the SD card (any special key presses?)
Click to expand...
Click to collapse
If the img file is written correctly to the SD-Card the nook will boot from the SD-Card. No need to press anything.

I cannot get noogie image working too. Have the img "burned" to SD card. Tried 2 different cards 4GB class6 and 8GB class10.
Tried to power on connected or disconnected from PC, Nook just starts up normally and then claims SD is not recognized and should be formatted.
Any ideas?

lluf said:
I cannot get noogie image working too. Have the img "burned" to SD card. Tried 2 different cards 4GB class6 and 8GB class10.
Tried to power on connected or disconnected from PC, Nook just starts up normally and then claims SD is not recognized and should be formatted.
Any ideas?
Click to expand...
Click to collapse
It's quite simple really, the Noogie.img weren't correctly written onto your SD card.
There can be several reasons for this, but most likely it's your card reader.
I.E. the built in card reader on my old HP Pavilion doesn't support raw access in a proper way and I had to buy an external card reader for it to work.

Hey I'm having a similar challenge as arvindar_n...
I just got a new nook simple touch and am looking to back it up.
Doing a google search lead me to the Backup/Restore N2E post.
The instructions say to:
1. Boot nook with noogie.img : (the "Rooted Forever" screen) and connect to your computer via USB.
2. Use DiskImager to copy your Nook partition to a file, being sure to select "Physical Disk" in the drop down list.
Step 1 seemed to work, I used winimage and wrote nookie.img onto a sd card
I put the sd card in the nook, let it reboot and was greeted with the "Rooted Forever" screen but it just sits there...not sure if that's the first problem.
Step 2, using DiskImager, I'm suppose to select Physical Disk. The challenge I'm having is there are 0-7 Physical Disks! My confusion is that none of the sizes are the 1.82 partition I'm reading about. I can see a 239.98 and 120.08 but no other physical drive besides my regular disk drive.
Please advise!

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.

[Q] Unbricking Nook Simple Touch after lost partitions - I've made it!

Hi, I have a Nook Simple Touch device with a traditional problem of improper backup of 76 MB before rooting.
Now I have managed to retrieve files from the /rom partition (/devconf folder with 20 files like serial no, public key etc.) - I have them in my laptop as regular files as well as 16 MB partition image on SD card.
Would anybody be so kind to offer a full recovery method? I believe backup of somebody's full image and then overwriting the /rom partition would revive the device?

How much of your partition table is left, if any, and how familiar are you with linux?
Were it me, I might have a go at creating just the first partition - boot from noogie, connect to a linux box, and use fdisk to create the partition.
I'd then try doing a
dd if=single.partition.backup.img of=/dev/mmcblk0p1
(writing my boot backup to the partition I just created) and see if that file wasn't enough to bootstrap the other partitions. Depending on how you created the backup, you may have the boot flag set and the partition table stored; so long as you haven't actually put data on the other partitions yet, it may be possible to at least trigger the onboard restore.
These are values that work on the glow, and I believe on the touch as well:
Disk /dev/block/mmcblk0: 2000 MB, 2000683008 bytes
128 heads, 32 sectors/track, 954 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)

Of the partitions, I still have:
- boot (I believe it is somewhat corrupted, but this I can restore from the backup)
- NOOK (FAT32) - should be OK, I see files in it;
- cache (Ext3)
- data (Ext3) - seems to be corrupted
Missing: factory (Ext2); one untitled partition and one unallocated segment.
Backup was created with Roadkil's DiskImage, with a source being the locigal drive (original boot partition).
I'm not good at Linux, but I know how to create partitions using Windows tools.
OK, I can try to recreate the boot partition and the rom partition, and restore the backup to it, then I'll see what happens.
Disk configuration for NST is different from the NSTG:
Cylinters: 238 Heads: 255 Sectors: 63

Nook is resurected!
Yes, I have managed to revive the Nook Simple Touch who had survived deletion of all partitions and restore of just the boot partition!
You will need for this:
- an micro SD card and card reader;
- Noogie;
- Minitool Partition Wizard (or other partition management software, if you like and it can do partition recovery and copying);
- ClockworkMod (sd_2gb_clockwork-rc2.zip)
- Alpha-FormatTouch-2.zip - to be copied onto ClockworkMod SD card;
The principle is this:
- first of all, do a PROPER backup of your device - backup ENTIRE PHYSICAL DISK (2 GB) into the image file.
- Using Minitool Partition Wizard, do a partition recovery operation - you should find all your deleted partitions - but do not apply changes yet!. However, due to improper restore of logical disk to a physical disk, the disk config info probably became corrupted and disk size appears to be 78MB, so you won't be able really restore the partitions. So, using Minitool Partition Wizard, do a copy of the recovered partitions one by one onto the SD card - and start with the most important rom partition. From Partion Wizard, you should be able, using Explore function, to check if the partition has all necessary files (20) like serial no, public key, mac address etc.
- from SD card, you can create a backup image of each partition on your hard disk.
- after you have copies of all necessary partitions (boot, rom, nook are vital; others are optional), you need to do a wipe on the NOOK disk to delete all partitions and the disk to obtain the original size of 2 GB.
- on an empty disk after wipe, you have to restore the partitions in the order:
1. restore, by copying using Minitool Partition Wizard, the boot partition (78 MB, FAT32, Primary, set it Active)
2. restore, by copying using Minitool Partition Wizard, the rom partition (16 MB, FAT32, Primary)
3. create manually new partition factory (190 MB, Ext2, Primary)
4. create manually new partition (no label) (288 MB, Ext2, Logical)
5. copy from backup partition NOOK (240 MB, FAT32, Logical)
6. create manually new partition cache (Ext3, 240 MB, Logical)
7. create manually new partition data (Ext3, 801 MB, Logical).
Then, boot the Nook from ClockWorkMod SD card, and format /system, /cache, /data partitions;
afterwards, install from zip card - Alpha-FormatTouch-2.zip.
And, hopefully, your Nook will be alive again!
(Now, I'm sure, you won't forget to do a proper backup of your working Nook :fingers-crossed

Yes, you save my nook. Thanks to your method i could revived my /rom.
but all is not done for me . i have a UK NST Glow and the glow is not working. I would like to update to firmware1.2 and may be this glow will function again. But When i plug the usb, windows cann see the drive but i don't have access to it. i have the message "please insert disc in F: drive"

wow wow wow . At last i successed to update to FW 1.2 for my almost bricked UK NSTGL. Now i have a US NSTGL but nevermind. now time to backup correctly.
but i'm not sure your method is fully working. I had to make a partition table with renater script "nookparted.sh" and then use roustabout's comment "dd if=boot.img of=....". and after that i put update 1.2.
In one week i have learn so much with my broken backup.

Hello, new here so hope it's ok to hijack this thread slightly, seems the original issue has been solved and I think my problem is similar although I'm way out of my depth here... I've managed to brick my nook, and although I took a backup which is AFAIK correctly sized 1.86gb I can't restore it. I've tried putting noogie and cmw on the sd card but it's refusing to boot, I suspect I nonced the partition table up and can't even get the nook to register when I plug it in to the PC now. I suspect is obvious I'm a dumb noob but if anyone could help point me in the right direction it would be much appreciated

welcome to the brave new world of the "bricked forever" and endless nights.
Nobody blames you since everybody and their mothers seem to fall into the trap even if they are told to make a good backup.
i had read so much threads to resurect my nook that i don't exactly know how i made it through, but here are some indications:
Here are the objectives:
1) make a correct backup of your bricked nook: -> you can make after all stupid commands and you 'll come back to this point.
2) you'll have to resurect your /rom or your rombackup.zip (inside factory).
3) have the correct partition of your nook
4) reinstall the rom
for 2) this thread gives a way to get back your /rom. read carefully even roustabout's comment can really help
for 3) thanks to Renate NST in this http://forum.xda-developers.com/showthread.php?t=1805936&highlight=to+stock and her script "nookpart.sh" i could have a correct size for my partition. (method with wizard partition gives wrong cylinders alignement). read all of this thread it is really rich.
for 4) if you reach that point that should be easy.

Thanks for the welcome and the reply jjinkou2.
I'm guessing I need to work on the nook through a PC. I've currently got 2 PCs, one running window 7 and one on vista, I'm mainly working on the W7 machine. When I plug the nook in to it, a device briefly shows up as the h: drive in My computer but then immediately disappears and so I can't actually access it yet. I note that roustabout mentions working in Linux, if I had a Linux machine available would it be easier to get it to recognize the nook?
Edit: Just tried plugging the nook into my vista machine (which it has not been used on before) and the Found New Hardware window briefly pops up but then vanishes and I get a message on the taskbar: Device driver software was not successfully installed - OMAO3630 Device unplugged. Is there a fix for this pelase?

Some easy instructions here http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
you'll need to install android sdk and check usb install in the extra.
Search for a file named "ADB + Fastboot + Drivers.zip" in the forum to easily have the adb.
With windows the usbdriver can be tricky to install. i had to use usbdview (look for it in google) and uninstall all B&N mass storage and OMAP3630.
The driver for usb inside the previous zip might not work also. i found one in the forum but can't find it right now.
Edit
found the usb driver that worked for me
http://forum.xda-developers.com/showthread.php?t=1125094

Excellent, thanks very much! Not entirely sure how I managed it but I managed to get to a point where I could use the method shown by budriunas and my nook is now working again, albeit with an older firmware and the glow light isn't working but at least it's not bricked! Now just to get the light working and then root the damn thing without killing it....

budriunas said:
Yes, I have managed to revive the Nook Simple Touch who had survived deletion of all partitions and restore of just the boot partition!
You will need for this:
- an micro SD card and card reader;
- Noogie;
- Minitool Partition Wizard (or other partition management software, if you like and it can do partition recovery and copying);
- ClockworkMod (sd_2gb_clockwork-rc2.zip)
- Alpha-FormatTouch-2.zip - to be copied onto ClockworkMod SD card;
The principle is this:
- first of all, do a PROPER backup of your device - backup ENTIRE PHYSICAL DISK (2 GB) into the image file.
- Using Minitool Partition Wizard, do a partition recovery operation - you should find all your deleted partitions - but do not apply changes yet!. However, due to improper restore of logical disk to a physical disk, the disk config info probably became corrupted and disk size appears to be 78MB, so you won't be able really restore the partitions. So, using Minitool Partition Wizard, do a copy of the recovered partitions one by one onto the SD card - and start with the most important rom partition. From Partion Wizard, you should be able, using Explore function, to check if the partition has all necessary files (20) like serial no, public key, mac address etc.
- from SD card, you can create a backup image of each partition on your hard disk.
- after you have copies of all necessary partitions (boot, rom, nook are vital; others are optional), you need to do a wipe on the NOOK disk to delete all partitions and the disk to obtain the original size of 2 GB.
- on an empty disk after wipe, you have to restore the partitions in the order:
1. restore, by copying using Minitool Partition Wizard, the boot partition (78 MB, FAT32, Primary, set it Active)
2. restore, by copying using Minitool Partition Wizard, the rom partition (16 MB, FAT32, Primary)
3. create manually new partition factory (190 MB, Ext2, Primary)
4. create manually new partition (no label) (288 MB, Ext2, Logical)
5. copy from backup partition NOOK (240 MB, FAT32, Logical)
6. create manually new partition cache (Ext3, 240 MB, Logical)
7. create manually new partition data (Ext3, 801 MB, Logical).
Then, boot the Nook from ClockWorkMod SD card, and format /system, /cache, /data partitions;
afterwards, install from zip card - Alpha-FormatTouch-2.zip.
And, hopefully, your Nook will be alive again!
(Now, I'm sure, you won't forget to do a proper backup of your working Nook :fingers-crossed
Click to expand...
Click to collapse
Thank you so much. My nook is back. I described my work in http://forum.xda-developers.com/showthread.php?p=34746242#post34746242.

jjinkou2 said:
wow wow wow . At last i successed to update to FW 1.2 for my almost bricked UK NSTGL. Now i have a US NSTGL but nevermind. now time to backup correctly.
but i'm not sure your method is fully working. I had to make a partition table with renater script "nookparted.sh" and then use roustabout's comment "dd if=boot.img of=....". and after that i put update 1.2.
In one week i have learn so much with my broken backup.
Click to expand...
Click to collapse
how did you do a partition table?? i have run nookpart.sh but i still get the problem : "When i plug the usb, windows cann see the drive but i don't have access to it. i have the message "please insert disc in F: drive"

nookpart.sh will partition the internal memory exactly like it was.
This is important if you actually still have valid data but the partition table was destroyed.
If partitions are not looking correctly they may need to be formatted.
Don't be too quick to repartition/reformat until you know what the situation is.

i have used nookpart.sh but still no good, here is the result when i execute nookpart.sh. Everything works except internal storage not mounted correctly i think, i want to update to 1.2
edit: see my thread http://forum.xda-developers.com/showthread.php?p=48015536#post48015536 for more details

[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