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] Backing up Rooted NST

I'm a bit confused on backing up my NST after I've rooted. I rooted with TouchNooter...do I still follow the same process of booting from a SD Card with noogie.img and then reading and image or is there a different process I should use now that I'm already rooted?

A full backup (around 2GB) with noogie is the safest bet.
You can also adb pull the /rom directory for safekeeping.
You can also mount the /factory partition and adb pull rombackup.zip

Renate NST said:
A full backup (around 2GB) with noogie is the safest bet.
You can also adb pull the /rom directory for safekeeping.
You can also mount the /factory partition and adb pull rombackup.zip
Click to expand...
Click to collapse
Thanks! I'm following the instructions at:
http://nookdevs.com/Nook_Simple_Touch/Rooting/Manual
Section: "After you have written the SDCard"
#7 says I should see all 7 partitions after the NST completes the boot.
I am only seeing the boot partition (I'm using Win7 if that matters).
My NST has Rooted Forever showing on the screen. I also waited several minutes and tried several times.
Do I go ahead and image the NST or do I need to do something different so that the NST shows all 7 partitions?
Thanks
EDIT: Found the solution at:
http://forum.xda-developers.com/showthread.php?t=1759700
post#6

NST Backup only 1916928 kb
Imaged my rooted nook with both Win32DiskImager and RoadKill (and I was sure to select the physical drive). Both .img files show the same size of 1,916,928 kb. Shouldn't these be larger? If so, what am I doing wrong? Thanks.

1,916,928 kB * 1024 B/kB = 1,962,934,272 B
The allocated part of the Nook's physical is 1,958,739,968 B
So, it's big enough.

[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] "Install failed" - partition broken?

Hi all,
I've got NST (with 1.1.0 software initially). After trying to root it properly I decided to restore original image and try again, because some added reader apps didn't start.
I tried to format NST as disk (deleting partition) and to write the ISO image I had (with my first backup).
After all, NST started as usual with "Read forever" screen and than after 10-15 second got "Install failed" screen.
Tried several recovery tools, they work from MicroSD, but after starting without memory card NST runs into the same screen.
Also tried "Touch-Formatter v2" CWM from this post
http://forum.xda-developers.com/showthread.php?t=1475613
Everything goes as expected, excepts strings appear such as:
"Can't mount /cache/recovery/last_log"
"Can't mount /emmc/"
etc.
But after reboot I have the same screen - "Install failed".
Also NST is not recognized in Windows as a mounted drive, just "unknown drive" appears for a second and then green light on NST turns yellow, and it goes for reboot.
If I use "mount USB storage" in CWM, connected NST is recognised as "bad disk" by Partition Manager.
Could anybody help?

dfche said:
I tried to format NST as disk (deleting partition)...
Click to expand...
Click to collapse
Why? Why do people do this?
dfche said:
... and to write the ISO image I had (with my first backup).
Click to expand...
Click to collapse
Ok, how big was the image and how did you try to write it?
It sounds like you trashed your partitions.
Why not use ADB on CWR, go to a shell and see what's left of your internal flash.
Code:
# busybox fdisk -l /dev/block/mmcblk0
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux

Renate NST said:
Why? Why do people do this?
Ok, how big was the image and how did you try to write it?
Click to expand...
Click to collapse
Mine was ~76MB. I used WinImage to write it.
Renate NST said:
Why not use ADB on CWR, go to a shell and see what's left of your internal flash.
Code:
# busybox fdisk -l /dev/block/mmcblk0
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux
Click to expand...
Click to collapse
My Windows PC doesn't see it at all. I tried "adb shell" command - "error: device not found"

dfche said:
Mine was ~76MB
Click to expand...
Click to collapse
Uh-oh.
You just made a backup of your boot partition, 1 of 8 partitions.
A full backup is on the order of 1.9 Gigs.
I hope that your formatting didn't destroy all your data.
You need to get ADB working with CWR and see what the damage is.
Try not to dig a bigger hole for yourself.
Take a look around these forums, there is tons of stuff about people who did the same as you.

Renate NST said:
Uh-oh.
You just made a backup of your boot partition, 1 of 8 partitions.
A full backup is on the order of 1.9 Gigs.
I hope that your formatting didn't destroy all your data.
You need to get ADB working with CWR and see what the damage is.
Try not to dig a bigger hole for yourself.
Take a look around these forums, there is tons of stuff about people who did the same as you.
Click to expand...
Click to collapse
Fortunately, I succeded writing backup image (shared by somebody on these forums) on NST with Noogie. It was almost 2 GB in size.
Thanks a lot for support!

Mmm, if you just duplicate somebody else's credentials you'll have a hard time registering for things.
You need the stuff out of your own /rom partition.

Renate NST said:
Mmm, if you just duplicate somebody else's credentials you'll have a hard time registering for things.
You need the stuff out of your own /rom partition.
Click to expand...
Click to collapse
I don't think I'll buy books from the B&N shop, but...
I found only one file that may be related to ROM - "romrestore.zip" in the very first image of my device.

dfche said:
Mine was ~76MB. I used WinImage to write it.
Click to expand...
Click to collapse
I´ve made the same mistake... your backup is useless... the correct file are bigger.
To correct this you will need to recover the ROM partition (have unique informations about your device) and replace this partition in a nook backup.
You can try this tutorial: http://forum.xda-developers.com/showthread.php?t=2104145
But the backup image available is for NSTG.

dfche said:
"romrestore.zip" in the very first image of my device.
Click to expand...
Click to collapse
romrestore.zip sounds good but it actually contains no personalized data.
You need stuff like in /rom/devconf:
DeviceID
SerialNumber
MACAddress
PublicKey
HashOfPrivateKey
There is /factory/rombackup.zip which does have what you want.
You can mount the /factory partition with CWR.

Renate NST said:
romrestore.zip sounds good but it actually contains no personalized data.
You need stuff like in /rom/devconf:
DeviceID
SerialNumber
MACAddress
PublicKey
HashOfPrivateKey
There is /factory/rombackup.zip which does have what you want.
You can mount the /factory partition with CWR.
Click to expand...
Click to collapse
The problem is that I have erased my own partition with everything excepts that small 76Mb part... It seems that "factory" sector has gone too.
But I think it's generally not a problem, if I don't need any service that checks some unique ID.

i have theoretical method
boot with noogie image , and use recovery programs to recover format files ,but the main problem is (u had overwrite the exist partition) and i think u cant recover it anymore
last thing ..... try to write ur backup (the corrupt 78 MB) to an sd card and hope that will share the Rom partition
PS : i was have same problem& mistake .... but i was lucky that my backup was with rom partition i from my corrupt backup
good luck

Like I said in my another post, try this:
http://forum.xda-developers.com/showthread.php?t=2104145
Specially this part:
-Recovering Partitions of a NSTG Accidentaly Formated:
Write noogie.img in a SD Card with WinImage (run as Administrator)
Insert SD in Nook and Boot ("Root Forever")
Open as Administrator MiniTool Partition Wizard.
Select Nook drive and click in "Partition Recovery Wizard".
Do a copy of "rom" partition to another SD card (or format noogie card and paste rom)
Click in "Apply" (top bar in the left) and wait complete the modifications​

ipedro3 said:
Like I said in my another post, try this:
http://forum.xda-developers.com/showthread.php?t=2104145
Specially this part:
-Recovering Partitions of a NSTG Accidentaly Formated:
Write noogie.img in a SD Card with WinImage (run as Administrator)
Insert SD in Nook and Boot ("Root Forever")
Open as Administrator MiniTool Partition Wizard.
Select Nook drive and click in "Partition Recovery Wizard".
Do a copy of "rom" partition to another SD card (or format noogie card and paste rom)
Click in "Apply" (top bar in the left) and wait complete the modifications​
Click to expand...
Click to collapse
the main idea of recovery is that repair the MBR for the formatted/deleted partition , so ...... if u overwrite , all data will gone
anyway try and wish to u good luck

TWRP 2.6.3.0 unable to mount esternal SDcard

[SOLVED: See last post]​
Hi everybody !
That's aLL... I just flashed a SBF, performed a factory reset from motorola's recovery, rooted my phone, installed 2ndinit 2.3, flashed TWRP 2.6.3.0 and then Quark's 2014 01 20 CM11 build.
Did I miss some step in order to get the card mounted in recovery ?
By the way I can easily access it plugging the USB cable on my Ubuntu Linux desktop and choosing MTP/PTP/USBstorage.
EDIT: it was previously formatted ( it's a 32GB class 10 U1 card ) as a fat32 partition on Windows7

Alka-Seltzer PLUS said:
Hi everybody !
That's aLL... I just flashed a SBF, performed a factory reset from motorola's recovery, rooted my phone, installed 2ndinit 2.3, flashed TWRP 2.6.3.0 and then Quark's 2014 01 20 CM11 build.
Did I miss some step in order to get the card mounted in recovery ?
By the way I can easily access it plugging the USB cable on my Ubuntu Linux desktop and choosing MTP/PTP/USBstorage.
EDIT: it was previously formatted ( it's a 32GB class 10 U1 card ) as a fat32 partition on Windows7
Click to expand...
Click to collapse
Your SDcard is visible from file manager?
If not than is better to format it in a ... compact camera or something like this.!

pgreed said:
Your SDcard is visible from file manager?
If not than is better to format it in a ... compact camera or something like this.!
Click to expand...
Click to collapse
Thanks for your answer !
Yes it is; I can mount it on my desktop too as I previously said.
This happened to me 2 times after having installed Quarx's CM11 with the steps described before
Plugging it on my desktop results in a mounted partition on the file explorer ( nautilus ) but as an unmounted on the partitioning app ( Gparted ) with a broken filesystem but I am able to copy files

Bump!

Alka-Seltzer PLUS said:
Bump!
Click to expand...
Click to collapse
As I said before something similar happened to me and the only solution was to re-format entire SDcard in a compact camera. I tried to format in a android tablet and in the phone but always it gave errors. After formatted in camera all work fine and no error.

pgreed said:
As I said before something similar happened to me and the only solution was to re-format entire SDcard in a compact camera. I tried to format in a android tablet and in the phone but always it gave errors. After formatted in camera all work fine and no error.
Click to expand...
Click to collapse
I should try but ... uhm ... my question is: why does the same card mount ever on every recovery ( TWRP 2.6.3.0 included ) but not any more after 2014 01 20 build ?
If I would restart from scratch without doing anything on the card( flashing a SBF, root, 2ndinit, TWRP 2.6.3.0, CM11 ) it should be mounted until the first CM11's boot: I did it 2 days ago. I just used the same card without formatting it: TWRP 2.6.3.0 does mount it only on the first shoot.
After the first CM11's boot it won't be mounted anymore.
sudo fdisk -l
Code:
Disk /dev/sdc: 32.1 GB, 32090619904 bytes
64 testine, 32 settori/tracce, 30604 cilindri, totale 62676992 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificativo disco: 0x70707573
Questa non sembra una tabella delle partizioni.
Probabilmente è stato scelto il dispositivo sbagliato.
Dispositivo Boot Start End Blocks Id System
/dev/sdc1 ? 1701998450 3638285201 968143376 d Sconosciuto
/dev/sdc2 ? 1701995885 2246105740 272054928 a OS/2 Boot Manager
/dev/sdc3 ? 1769087090 3538458322 884685616+ 6f Sconosciuto
/dev/sdc4 ? 2885681152 2885734849 26849 a OS/2 Boot Manager
dmesg|tail
Code:
[16595.451780] sd 7:0:0:0: Attached scsi generic sg3 type 0
[16595.451862] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.451871] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.466630] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.466647] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.469344] sdc:
[16595.472449] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.472461] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.472471] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[16595.775667] FAT-fs (sdc): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Oh LoL: it mounts flawlessy and really on the fly and I can manage aLL files!
sudo dosfsck -w -r -l -a -v -t /dev/sdc
Code:
dosfsck 3.0.16 (01 Mar 2013)
dosfsck 3.0.16, 01 Mar 2013, FAT32, LFN
Checking we can access the last sector of the filesystem
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automaticaly removing dirty bit.
Boot sector contents:
System ID "MSDOS5.0"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
65536 bytes per cluster
540 reserved sectors
First FAT starts at byte 276480 (sector 540)
2 FATs, 32 bit entries
1958912 bytes per FAT (= 3826 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 4194304 (sector 8192)
489600 data clusters (32086425600 bytes)
63 sectors/track, 255 heads
0 hidden sectors
62676992 sectors total
...
...
...
Checking for bad clusters.
Reclaiming unconnected clusters.
Checking free cluster summary.
Performing changes.
/dev/sdc: 3703 files, 238236/489600 clusters
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automaticaly removing dirty bit.
Click to expand...
Click to collapse
uhm ... I'm just writing zeros to the entire drive:
Code:
sudo dd if=/dev/zero of=/dev/sdc
Let's see if it helps

SOLVED​
Okka roLLa !
So... trying to reformat the card via CM11 results in a random reboot; trying to wipe it on TWRP fails too.
I wrote zeros another 2 times in between and than i putted it into the defy, mounted it as USB Mass Storage in order to partition it with GParted creating 2 primary partitions ( 1024GB ext3 and aLL the other avaiable space FAT32 ) and now it is seen from recovery without mounting it :good:

I have the same problem: after installing any of the recent CM11 nightlies (since the autobot builds began), TWRP is unable to mount my sdcard. (It's a 16GB class 10 made by Topram.) I've tried fully formatting the card in my PC (as FAT32), also checked it for errors and bad sectors. So far as I can tell, there's nothing wrong with the card.
Earlier versions of CM11 (from pre-autobot builds, like the December 29th build) have no trouble mounting the card in recovery, and the latest builds of CM11 have no trouble reading from and writing to the card when the rom is fully booted; only TWRP is unable to mount it. Strangely, TWRP has no trouble mounting an older and slower 2GB card.
@Alka-Seltzer PLUS, I'd rather not use the workaround that you described above, because the last time I tried screwing around in TWRP trying to get it to mount the sdcard, I ended up hard-bricking my old defy.
So, does anyone know whether it is possible to replace the recovery in the latest nightlies with a recovery from an earlier build? I'm not sure exactly what files I'd need to replace in the CM11 zip file, or whether a simple replacement would even work. I tried taking what I thought were the correct files from the December 29th build and flashing them over the February 22 nightly, but that just soft-bricked the phone and I had to start over from sbf.

Proverbs2 said:
I have the same problem: after installing any of the recent CM11 nightlies (since the autobot builds began), TWRP is unable to mount my sdcard. (It's a 16GB class 10 made by Topram.) I've tried fully formatting the card in my PC (as FAT32), also checked it for errors and bad sectors. So far as I can tell, there's nothing wrong with the card.
Earlier versions of CM11 (from pre-autobot builds, like the December 29th build) have no trouble mounting the card in recovery, and the latest builds of CM11 have no trouble reading from and writing to the card when the rom is fully booted; only TWRP is unable to mount it. Strangely, TWRP has no trouble mounting an older and slower 2GB card.
@Alka-Seltzer PLUS, I'd rather not use the workaround that you described above, because the last time I tried screwing around in TWRP trying to get it to mount the sdcard, I ended up hard-bricking my old defy.
So, does anyone know whether it is possible to replace the recovery in the latest nightlies with a recovery from an earlier build? I'm not sure exactly what files I'd need to replace in the CM11 zip file, or whether a simple replacement would even work. I tried taking what I thought were the correct files from the December 29th build and flashing them over the February 22 nightly, but that just soft-bricked the phone and I had to start over from sbf.
Click to expand...
Click to collapse
Maybe there's a misunderstandig: the steps i described have been done with the microSD outside the phone; I did it with the card inserted in an adapter !

Alka-Seltzer PLUS said:
Maybe there's a misunderstandig: the steps i described have been done with the microSD outside the phone; I did it with the card inserted in an adapter !
Click to expand...
Click to collapse
Thanks for the reply. I'm still not sure that I understand your steps. Did you use gparted on your linux PC to create an ext3 partition and a FAT32 partition on the sdcard, then put the sdcard back into the phone and now TWRP recognizes it? If so, which partition does TWRP recognize, the ext3 or the FAT32?
In any case, I'd rather not resort to such a workaround, since I don't trust the latest version of the TWRP recovery (which hard-bricked my old defy). I would prefer to downgrade the recovery to the version that was working fine on the earlier CM11 builds (e.g. the December 29th build). Does anyone know how to do that?
Thanks in advance!

That's right: I did use gparted on my linux PC to create an ext3 partition and a FAT32 partition on the sdcard, then putted the sdcard back into the phone and now TWRP does recognize it.
The FAT32 is recognized, the ext3 i do not know because i did not look for it yet ^_^

Alka-Seltzer PLUS said:
That's right: I did use gparted on my linux PC to create an ext3 partition and a FAT32 partition on the sdcard, then putted the sdcard back into the phone and now TWRP does recognize it.
The FAT32 is recognized, the ext3 i do not know because i did not look for it yet ^_^
Click to expand...
Click to collapse
Wow, that actually worked! I just used gparted to fix the partition table and reformat the entire sdcard as FAT32 (I only created one partition), and now the card is recognized in TWRP! :good:
Apparently there was something wrong with the partition tables on my sdcard, and even a full format in Windows 7 didn't fix it, nor did the Windows disk check utility detect the problem, but Linux saves the day again!

Alka-Seltzer PLUS said:
I should try but ... uhm ... my question is: why does the same card mount ever on every recovery ( TWRP 2.6.3.0 included ) but not any more after 2014 01 20 build ?
If I would restart from scratch without doing anything on the card( flashing a SBF, root, 2ndinit, TWRP 2.6.3.0, CM11 ) it should be mounted until the first CM11's boot: I did it 2 days ago. I just used the same card without formatting it: TWRP 2.6.3.0 does mount it only on the first shoot.
After the first CM11's boot it won't be mounted anymore.
sudo fdisk -l
Code:
Disk /dev/sdc: 32.1 GB, 32090619904 bytes
64 testine, 32 settori/tracce, 30604 cilindri, totale 62676992 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificativo disco: 0x70707573
Questa non sembra una tabella delle partizioni.
Probabilmente è stato scelto il dispositivo sbagliato.
Dispositivo Boot Start End Blocks Id System
/dev/sdc1 ? 1701998450 3638285201 968143376 d Sconosciuto
/dev/sdc2 ? 1701995885 2246105740 272054928 a OS/2 Boot Manager
/dev/sdc3 ? 1769087090 3538458322 884685616+ 6f Sconosciuto
/dev/sdc4 ? 2885681152 2885734849 26849 a OS/2 Boot Manager
dmesg|tail
Code:
[16595.451780] sd 7:0:0:0: Attached scsi generic sg3 type 0
[16595.451862] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.451871] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.466630] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.466647] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.469344] sdc:
[16595.472449] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.472461] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.472471] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[16595.775667] FAT-fs (sdc): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Oh LoL: it mounts flawlessy and really on the fly and I can manage aLL files!
sudo dosfsck -w -r -l -a -v -t /dev/sdc
Code:
dosfsck 3.0.16 (01 Mar 2013)
dosfsck 3.0.16, 01 Mar 2013, FAT32, LFN
Checking we can access the last sector of the filesystem
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automaticaly removing dirty bit.
Boot sector contents:
System ID "MSDOS5.0"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
65536 bytes per cluster
540 reserved sectors
First FAT starts at byte 276480 (sector 540)
2 FATs, 32 bit entries
1958912 bytes per FAT (= 3826 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 4194304 (sector 8192)
489600 data clusters (32086425600 bytes)
63 sectors/track, 255 heads
0 hidden sectors
62676992 sectors total
...
...
...
Checking for bad clusters.
Reclaiming unconnected clusters.
Checking free cluster summary.
Performing changes.
/dev/sdc: 3703 files, 238236/489600 clusters
uhm ... I'm just writing zeros to the entire drive:
Code:
sudo dd if=/dev/zero of=/dev/sdc
Let's see if it helps
Click to expand...
Click to collapse
I think the problem here is that there is no partition table on your card, just a file system; you put a file system directly on the sd card, rather than creating a single partition spanning all of the card. Your file system would end up on /dev/block/mmcblk0 rather than /dev/block/mmcblk0p1, and twrp.fstab doesn't include an entry for that, so it doesn't get mounted.
This might be easy to fix, but testing the fix might also hard-brick the phone in question, as Proverbs2 discovered. It doesn't seem to be a hardware issue, and the overwhelming standard is for SD cards to have a partition table, so we're probably best off warning about such cards and not touching them at all. Whatever software you used to format your SD card initially needs to be fixed, though.

Proverbs2 said:
So, does anyone know whether it is possible to replace the recovery in the latest nightlies with a recovery from an earlier build? I'm not sure exactly what files I'd need to replace in the CM11 zip file, or whether a simple replacement would even work. I tried taking what I thought were the correct files from the December 29th build and flashing them over the February 22 nightly, but that just soft-bricked the phone and I had to start over from sbf.
Click to expand...
Click to collapse
I think there was a recent change to use separate kernels for recovery and normal 2nd-boot. You'd need to replace /system/bootmenu/2nd-boot/ramdisk-recovery with the old /system/bootmenu/2nd-boot/ramdisk-recovery and /system/bootmenu/2nd-boot/zImage-recovery with the old /system/bootmenu/2nd-boot/zImage (no "-recovery" suffix), I think, and I'd expect it to just work then. Don't touch the new /system/bootmenu/2nd-boot/ramdisk and /system/bootmenu/2nd-boot/zImage.

[PROBLEM SOLVED Time ago]
PhilipCetero said:
I think the problem here is that there is no partition table on your card, just a file system; you put a file system directly on the sd card, rather than creating a single partition spanning all of the card. Your file system would end up on /dev/block/mmcblk0 rather than /dev/block/mmcblk0p1, and twrp.fstab doesn't include an entry for that, so it doesn't get mounted.
This might be easy to fix, but testing the fix might also hard-brick the phone in question, as Proverbs2 discovered. It doesn't seem to be a hardware issue, and the overwhelming standard is for SD cards to have a partition table, so we're probably best off warning about such cards and not touching them at all. Whatever software you used to format your SD card initially needs to be fixed, though.
Click to expand...
Click to collapse
Alka-Seltzer PLUS said:
SOLVED​
Okka roLLa !
So... trying to reformat the card via CM11 results in a random reboot; trying to wipe it on TWRP fails too.
I wrote zeros another 2 times in between and than i putted it into the defy, mounted it as USB Mass Storage in order to partition it with GParted creating 2 primary partitions ( 1024GB ext3 and aLL the other avaiable space FAT32 ) and now it is seen from recovery without mounting it :good:
Click to expand...
Click to collapse
Thanks for your answer but I do not realize what was wrong doing it my way ( now the card gets mounted ) !
After having write zeros on the card i tried to partition it in 3 different ways:
1) Booting up CM11 and letting it ask to format the empty card ( I thought it was supposed to create a partition table with a FAT32 partition spanning all the space on the microSD ) but it always resulted in a random reboot and a not partitioned card.
2) Entering TWRP and letting it partition the SDcard using its menu: it returns that the recovery tries to mount any partition which is supposed to be created from an empty card Maybe the card should have had at least a partition table in order to be partitioned ? This question let go to this another one: isn't TWRP able to write a partition table on an empty microSD ?
3) My way: using Gparted whom prompts a window which says to create a partition table before partitioning the device.

Alka-Seltzer PLUS said:
Thanks for your answer but I do not realize what was wrong doing it my way ( now the card gets mounted ) !
Click to expand...
Click to collapse
There's nothing wrong with your way! I just thought an explanation of what went wrong would be helpful. To actually fix it, gparted is what I would use, too; and now you've used it everything should work flawlessly
Sorry for the confusion: I was talking about fixing TWRP to recognize such cards (which it should) and working with them (which it shouldn't, because of the risk it's a broken card and we end up Proverbsing the phone).

is there any new solution?
or can i mount(in twrp) /dev/block/mmcblk0 sdcard
and install my new rom and do away