USE AT YOUR OWN RISK. You are responsible if you mess up your tablet.
NOTE: ONLY MESS WITH Partitions 10 & 11 (media and userdata)
This Wipe Data error E: format_volume: make_extf4fs failed on /dev/block/mmcblk1p2 is normal we all have it and it doesn't harm your device
Repartitioning your Nook Tablet requires (you must have):
* ADB drivers working on your PC
* CWM installed either to Internal (EMMC) or SDCARD
BEFORE START:
Watch the whole video and read the post first, once done you are now ready to start!
Click to expand...
Click to collapse
Big Thanks to @meghd00t
1. BACKUP INTERNAL SDCARD AND ROM
* To backup your Internal SDcard a.k.a: /media partiton, MyNook, /emmc:
Connect your Nook Tablet to your PC via USB, Turn on USB storage and copy all your files from MyNook to a folder in your PC.
* To backup your current ROM:
Boot into CWM, then go to backup & restore >> backup (external SDcard) so you can restore your /data later on.
Please NOTE that if you don't have a larger sdcard you will have to backup your current ROM to Internal SDcard, in which case you must use the method above to copy the clockworkmod folder to your PC.
2.0 PREPARATION:
IF YOU COME FROM THE OLD REPARTITION METHOD...
Code:
> cd path-to-adb-drivers
[B]> adb shell[/B]
# parted /dev/block/mmcblk0
(parted) toggle 10 lvm
# quit
2.1 REPARTITION:
Code:
# sgdisk -e /dev/block/platform/mmci-omap-hs.1/mmcblk0
This will write the secondary gpt label and remove the parted prompt found error fix?
Code:
# sgdisk /dev/block/platform/mmci-omap-hs.1/mmcblk0 -d 11 -d 10
This will delete partition 10 & 11 media and userdata
Code:
# sgdisk /dev/block/platform/mmci-omap-hs.1/mmcblk0 -n 0:0:+12G -n 0:0:0
# sgdisk /dev/block/platform/mmci-omap-hs.1/mmcblk0 -c 10:media -c 11:userdata
This will re-create both media (change +12G to whatever you need) and userdata will use the rest, then it'll set the name of the partitions
3. REBOOT YOUR DEVICE INTO CWM:
Code:
Ctrl+c to exit shell mode
> adb reboot recovery
This will exit from shell mode and reboot into recovery again. If adb reboot recovery doesn't work for you then do it manually.
4. FORMAT PARTITIONS:
Code:
> adb shell
# mkdosfs -F32 -n MyNook /dev/block/mmcblk0p10
# make_ext4fs -L userdata /dev/block/mmcblk0p11
Ctrl+c to exit shell mode
> adb reboot
> adb kill-server
This will start adb shell mode, format partition 10 to FAT32, format partition 11 to EXT4, exit shell mode, reboot your device to system and stop adb server from keep running.
5. RESTORE YOUR DATA
Reboot back into CWM recovery
CWM >> backup and restore >> Advanced restore >> /data
Click on this link to see the Old Method
~ Veronica
This ought to be stickied. I assume this will also work for the 8GB NT, although of course numbers need to change to reflect the fact that it's only 8GB.
Old Method
Hello, i decided to create this thread as the OP in this one hasn't been Updated with the solution for Repartiton your 16GB Nook Tablet and i see there is still people asking about how to do this and i've had to give the link of the "hidden" post over and over again.
Big Thanks to @tselling for put in risk his NT and post instructions for this, please go here and Thank him!
Repartitioning your Nook Tablet requires (you must have):
* ADB drivers working on your PC
* CWM installed either to Internal (EMMC) or SDCARD
* Tools: parted, tune2fs, e2fsck << Download this ONLY if you need them: parted is not found,etc
Boot into CWM, then go to backup & restore >> backup or backup to internal so you can restore /data after the repartitioning process since we are going to delete and recreate it.
IT DOESN'T MATTER WHAT ROM YOU HAVE INSTALLED, THE PROCESS IS MADE WHILE IN CWM SO MEDIA AND DATA PARTITIONS ARE NOT BEING USED
THIS PROCEDURE IS NOT REVERSIBLE UNLESS YOU RUN THE RIGHT COMMANDS TO REVERT THE PARTITIONS BACK TO DEFAULT SIZE
Here is a quick summary: Start parted on mmcblk0 from adb shell. Fix the errors. Delete partition 11 (userdata). Resize partition 10 (media) to make it larger... use the original start position and change the end position to make it the size you want. Recreate partition 11... use the end position from partition 10 as the new start position and use the original end position. Name partition 11 "userdata". Print the partition table along the way to make sure that its what you want. Exit parted. Use tune2fs and e2fsck to convert the ext2 partition back to an ext4 partition. Reboot back into CWM, restore your data partition and then reboot.
Click to expand...
Click to collapse
HOW DO I REVERT THIS PROCESS BACK TO STOCK???
"The bold text is the prompt and commands. The non-bold parts are screen output"
Remember that userdata is where most apps install. If you install alot of games you don't want to reduce it too far, 2.5GB - 2GB is probably ok for most people.
~ $ cd path-to-adb-drivers
ONLY IF YOU GET parted: not found: * You should had downloaded NT_repartition_files.zip uncompressed it and placed the files where adb is located already *~ $ adb push parted /system/bin * tune2fs and e2fsck may or may not be needed *~ $ adb push tune2fs /system/bin
~ $ adb push e2fsck /system/bin
Click to expand...
Click to collapse
~ $ adb shell
* daemon not running. starting it now on port xxxx *
* daemon started succesfully *
~ # 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
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.6GB 12.9GB ext4 userdata
(parted) rm 11 * This will remove partition #11 *rm 11
rm 11
(parted) resize * You're entering to resize mode *resize
resize
Partition number? 10 * Partition #10 will be resized *10
10
Start? [1611MB]? * <---| enter *
End? [2684MB]? 11.6GB * Give a value between 11.6 and 13.6 that will leave you with>> 11.6GB: 4GB for /userdata | 13.6: 2GB for /userdata *11.6GB
11.6GB
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
(parted) mkpartfs primary ext2 * This will re-create partition #11 in the empty space and format it to ext2 *mkpartfs primary ext2
mkpartfs primary ext2
Start? 11.6GB * This value must concide with what you set in End? [2684MB]? 11.6GB before *11.6GB
11.6GB
End? 15.6GB * This value can't be changed. Must be 15.6GB *15.6GB
15.6GB
(parted)
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4326MB ext2
(parted) name 11 userdata * This will name partition #11 "userdata" *name 11 userdata
name 11 userdata
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4326MB ext2 userdata
(parted) quit
quit
quit
Information: You may need to update /etc/fstab.
~ # tune2fs -j /dev/block/mmcblk0p11 * From here the convertion process of partition #11 to ext4 has started *tune2fs -j /dev/block/mmcblk0p11
tune2fs 1.41.6 (30-May-2009)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
~ # e2fsck -fDp /dev/block/mmcblk0p11
e2fsck -fDp /dev/block/mmcblk0p11
/dev/block/mmcblk0p11: 11/529056 files (0.0% non-contiguous), 49429/1056092 blks
~ # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p11
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p11
tune2fs 1.41.6 (30-May-2009)
Please run e2fsck on the filesystem.
~ # e2fsck -fDp /dev/block/mmcblk0p11
e2fsck -fDp /dev/block/mmcblk0p11
/dev/block/mmcblk0p11: Group descriptor 0 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 1 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 2 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 3 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 4 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 5 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 6 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 7 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 8 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 9 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 10 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 11 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 12 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 13 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 14 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 15 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 16 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 17 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 18 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 19 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 20 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 21 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 22 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 23 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 24 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 25 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 26 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 27 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 28 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 29 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 30 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 31 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 32 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Adding dirhash hint to filesystem.
/dev/block/mmcblk0p11: 11/529056 files (0.0% non-contiguous), 49429/1056092 bl
ks
~ # 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) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4326MB ext4 userdata
(parted) quit
quit
quit
Ctrl+c to exit shell mode
~ $ adb kill-server
Now reboot back into recovery (advanced option).
Go to backup & restore>> Advanced restore>> data to restore your data (apps), make sure you pick the correct folder of your latest backup, once done reboot system. ENJOY!
BONUS: Manage all your books including B&N downloads in calibre
Thanks to @roustabout
Also, once you've done this you can also shell in and
Code:
$ adb shell
# cd /data/media/B&N Downloads
# rm -r *
# cd ..
# rmdir B&N Downloads
# ln -s "/media/B&N Downloads" "B&N Downloads"
Ctrl+c to exit shell mode
$ adb kill-server
This points your B&N library to your /media folder for downloading, helpful if you want to manage all your books in Calibre.
~ Veronica
I am sorry for noob question, but is this a tutorial on how to expand that miserable 1gb user data space and steal more space from 12gb locked internal memory?
schtuka said:
I am sorry for noob question, but is this a tutorial on how to expand that miserable 1gb user data space and steal more space from 12gb locked internal memory?
Click to expand...
Click to collapse
lol yes Mr.
~ Veronica
too much text. someone make a youtube video. tks.
xdahgary said:
too much text. someone make a youtube video. tks.
Click to expand...
Click to collapse
strictlyrude27 said:
For ****'s sake. It's a bunch of commands you enter on the command line. OF COURSE THERE'S A LOT OF TEXT.
Click to expand...
Click to collapse
Actually the commands are few...
"The bold text is the prompt and commands. The non-bold parts are screen output".
I did it in less than 10 minutes and reading the tutorial twice.
~ Veronica
Like a charm. So happy. F bn
In the guys defense, not having ever used adb before, it took me about 30 minutes to do it last night. I had a hard time figuring out how to make the computer see the Nook while in CWR. Once I got that figured out, it went pretty fast.
Ok, I am trying to follow the instructions before actually doing it ... bear with me..
So I boot in CWM Recovery.
Do the backup.
Then what? Open cmd on my computer and go to shell?
I am familiar with ADB, but I am confused about at what point in the script you change the size of media 10 and data 11...... I see that 2GB of user data 11 will be enough for me. What size the media 10 should be? I remember from GParted that you have to divide equally the space....
Also, it says in the end of summary to reboot back to CWM. I thought we are in CWM doing the script the whole time. When did we reboot?
Thanks.
For noob like me, I actually wish to have some briefing about the commands. For example, in case I want to have less then 12GB of media data, 10GB may be, which number that I should change?
--------------
Edit: I guess
End? [2684MB]? 11.6GB
11.6GB
11.6GB
(parted) p
to
End? [2684MB]? 10GB
10GB
10GB
(parted) p
Correct me if I'm wrong. My NT is still on the way to my house
schtuka said:
Ok, I am trying to follow the instructions before actually doing it ... bear with me..
So I boot in CWM Recovery.
Do the backup.
Then what? Open cmd on my computer and go to shell?
I am familiar with ADB, but I am confused about at what point in the script you change the size of media 10 and data 11...... I see that 2GB of user data 11 will be enough for me. What size the media 10 should be? I remember from GParted that you have to divide equally the space....
Also, it says in the end of summary to reboot back to CWM. I thought we are in CWM doing the script the whole time. When did we reboot?
Thanks.
Click to expand...
Click to collapse
After the backup you plug your NT to your computer (you must have adb working already) open the cmd on windows and "cd" to the path of adb files then "adb shell" as explained in the tutorial.
You first resize/extend media partition (10) because that is the one mounts in your PC ("MyNOOK")
The part that the size is changed for /media is here:
(parted) resize
resize
resize
Partition number? 10
10
10
Start? [1611MB]?
End? [2684MB]? 11.6GB >> in this part 11.6GB is set to leave 4gb for userdata, i personally set it to 13.6GB so that leave 2GB for userdata as i don't install heavy apps and games like crazy.
11.6GB
11.6GB
The userdata partition is recreated after with what is left:
Start? 11.6GB >> as you can see its the same value that was set before in End? [2684MB]? 11.6GB of the /media partition
11.6GB
11.6GB
End? 15.6GB
15.6GB
15.6GB
As stated in the tutorial this is made while in CWM , you reboot back into it just to restore your data,nothing else. Let's put it this way when the windows updates install in your PC it ask you to reboot right? Sometimes reboots are required why? don't ask just do it is easy and it won't harm your device gee
~ Veronica
camapghe said:
For noob like me, I actually wish to have some briefing about the commands. For example, in case I want to have less then 12GB of media data, 10GB may be, which number that I should change?
--------------
Edit: I guess
End? [2684MB]? 11.6GB
11.6GB
11.6GB
(parted) p
to
End? [2684MB]? 10GB
10GB
10GB
(parted) p
Correct me if I'm wrong. My NT is still on the way to my house
Click to expand...
Click to collapse
hMM I THINK YOU'RE CONFUSED this is for users that want their /media partition bigger not /userdata (we are shortening userdata) why would you want this? simple because you can copy all your media: music, videos, movies, books, etc. to /media (which mounts to your PC as MyNOOK) so you don't use your sdcard to host them all.
Userdata is where apps install when you download them so think first of a size that works for you, and what partition you think you will give it more use.
~ Veronica
@Veronica: I'm confused indeed. I usually install tons of games + apps on my phone. That's why I don't want the partition where device stores those things internally small.
I guess I just follow exactly (and blindly) to the tut. Professional guys here must be right.
xdahgary said:
too much text. someone make a youtube video. tks.
Click to expand...
Click to collapse
FYI, if you ever unlock bootloader, install CWM, root and install custom ROM for a HTC Wildfire S from scratch, I swear you will just bang the phone up
Just out of curiosity, as I have not done this before, but can you string commands together with ampersands as you can in a Linux Bash terminal? If so, it could be one (albeit very long) command...
Thank you Veronica. I will try it at work right now. 6LV26081EP701653Y
So I did everything according to OP. Within CWM went to Advanced/Reboot to recovery/restore
Trying to restore my backup and I am getting:
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Error while formatting /data
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
....... help?....
I still have your ROM on sdcard. Should I try to install it instead of backup?
Tried to install your ROM from sdcard. Rebooted and now just sitting on white NOOK screen.
Am I FUBARed? I can't get to CWM.
schtuka said:
Thank you Veronica. I will try it at work right now. 6LV26081EP701653Y
So I did everything according to OP. Within CWM went to Advanced/Reboot to recovery/restore
Trying to restore my backup and I am getting:
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Error while formatting /data
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
....... help?....
I still have your ROM on sdcard. Should I try to install it instead of backup?
Tried to install your ROM from sdcard. Rebooted and now just sitting on white NOOK screen.
Am I FUBARed? I can't get to CWM.
Click to expand...
Click to collapse
Something you did wrong while using the commands can you tell me the values that you gave to /media and /userdata please.
Turn off your device, turn it on by long pressing power and "N" button for 5 seconds (let me know if you get the white screen with the box), then let go power and N buttons and it ishould boot into CWM after that box.
Other alternative if you cant boot internally to CWM is to prepare an sdcard and boot into CWM from there.
You need to get into CWM.
I used same numbers as in OP. I mean just copy and paste from OP.
Yeah. I got to CWM what should I do now?
Thanks
schtuka said:
I used same numbers as in OP. I mean just copy and paste from OP.
Yeah. I got to CWM what should I do now?
Thanks
Click to expand...
Click to collapse
wipe cache and advanced> dalvik cache.
Restore only data this way:
* Go to Backup&restore> Advanced restore> data
* wipe cache and dalvik again just in case (i always do that when restoring).
~ Veronica
Same error:
Restoring data...
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Error while formatting /data
I think I made a mistake. Perhaps the usb drivers I used to format were not Nook Tablet specific. I have same computers at work and at home and once I got into ADB shell I thought it was good to go. Now I am looking at device manager and it is just says
-Android phone
Android composite ADB interface
Also looking through USBviewer I see too many Android devices. Including Nook Tablet USB Composite device connected and Nook Tablet ADB Interface not connected.
Related
Hello, sorry if this is repost but...
Few days ago I rooted my nook tablet with CM7 Alpha, I used Indirects App to Flash to Recovery. it was running perfectly fine until 7 hours ago when I turned it off, then it went into cwm with this error;
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 followed instructions posted by CelticWebSolutions here but the problem is when I try to run the adb shell command I get this error attached photo below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I tried Indirect's after running the script it boots and the white screen with brown box comes on and doesn't go away, when I restart it it goes back to cw and showing that error I posted above. I don't know what to do from here.
Thank you for your help in advance.
http://forum.xda-developers.com/showthread.php?p=22049356
[HOW-TO] Use ADB tool | Android Debug Bridge
~ Veronica
Sent from my Nook Tablet using xda premium
I bricked, and was able to load cwm but I could not get adb to work. I used Adam's Method, the instructions to flash in windows are after item 6, which is what I used.
http://forum.xda-developers.com/showthread.php?t=1470910
[UnBrick]TOTAL WIPE and reflash back to 1.4.0 via Ubuntu Recovery --Now Easier!!!!
I burned a gpardted live cd to partition the sd card. I used a 16g. Someone I think posted they used a 4, but it wasnt big enough for me.
It took a few times rebooting, (at least i didnt think it was working?) but i finally let it sit a bit and it started working.
Good luck.
Thank you for all your responses, I never got to try the solution posted above because my NT gets stuck on the white background with a brown box and I don't know what to do or get out of there. It powers on perfectly fine then doesn't move beyond the screen.
I'm going to scour the internet and see if I can find the solution.
Again thank you everybody for your answers.
You don't have your ADB drivers set up correctly for the NT. You need to have ADB and the adb_usb.ini (both included with Indirect's nook&zergy root zip) Use the USB deviewer to remove any mass storage ports, anything google, or android related. Then restart the PC, plug in the NT and select the driver (located in Indirect's post with the nook&zergy zip).
icebergtz said:
Thank you for all your responses, I never got to try the solution posted above because my NT gets stuck on the white background with a brown box and I don't know what to do or get out of there. It powers on perfectly fine then doesn't move beyond the screen.
I'm going to scour the internet and see if I can find the solution.
Again thank you everybody for your answers.
Click to expand...
Click to collapse
I sent you a PM
Same here. I followed the directions per this post, and while it did fix the mount errrors, the only way I can boot into CWM is by using an SD card. Without the card, it just sits at the white screen with the box.
Finally!
I got it fixed on my end by reinstalling CWM to the internal drive. Here are my directions:
1) Make yourself a bootable SD Card, with root priviledges. I used this one here:
http://forum.xda-developers.com/showthread.php?p=21275927#post21275927
2)With the NT off, put the freshly made card in, and boot with it into CM7
3)Download Indirect's Nook Recovery Flasher into the nook and install it
http://forum.xda-developers.com/showthread.php?t=1458630
4) Use that Recovery Flasher to reinstall your INTERNAL CWM.
5) Using your computer, or your nook, download into the nook whatever rom you want to reinstall. Here is a link for CM7 Alpha:
http://forum.xda-developers.com/showthread.php?t=1481826
6) Turn off NT, remove sd card, and boot into CWM by holding Power + N
That solved it for me, and I had tried just about everything else in these forums for recovery. Turns out somehow the internal CWM was messed up.
Flumoxed by E:Can't mount . . .
After several days and hours of reading through this and many other threads I'm still stuck I'm still stuck in a CWM Recovery Loop and am getting:
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/
CURRENT STATUS:
My NT is booting into internal CWM and I have ADB access to the NT.
Yet when I mount /sdcard and and run Indirect's "Brick_Fix" script (fix.bat) I get this:
---------- MD5.TXT
xloader.img 414334166dc3d1d3687cf5b466bcae7a
Ensure your sdcard is mounted or else this wont work!
is it mounted?
Press y for yes and N for no.
Please make your decision:y
The system cannot execute the specified program.
The system cannot execute the specified program.
Pinging 1.1.1.1 with 32 bytes of data:
Request timed out.
Ping statistics for 1.1.1.1:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
The system cannot execute the specified program.
now it's fixed!
Pinging 1.1.1.1 with 32 bytes of data:
Request timed out.
Ping statistics for 1.1.1.1:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
And when using these commands in ABD (from this post http://forum.xda-developers.com/showpost.php?p=23104727&postcount=26 ) yields the following results:
C:\Windows\system32>adb shell mount -t /dev/block/mmcblk0p6 /data
mount: mounting /dev/block/platform/mmci-omap-hs.1/by-name/userdata on /data fai
led: No such file or directory
C:\Windows\system32>adb shell dd if=/dev/zero of=data/BCB bs=1 count=1088
1088+0 records in
1088+0 records out
1088 bytes (1.1KB) copied, 0.006714 seconds, 158.3KB/s
C:\Windows\system32>adb shell dd if=/dev/zero of=data/BootCnt bs=1 count=1
1+0 records in
1+0 records out
1 bytes (1B) copied, 0.000091 seconds, 10.7KB/s
Any suggestions at this point would be very welcome - I'm flumoxed by what I keep reading should be a pretty easy problem to fix because it's so common.
For that error...
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/
run parted while in CWM and pick fix:
~ $ adb shell
* daemon not running. starting it now on port xxxx *
* daemon started succesfully *
~ # 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
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
* Bold parts are the commands
~ Veronica
Veronica, if you were here I would kiss you!
(But that would only get me in trouble with the wife so you'll have to settle for a donation instead)
I am back up and running NT CM7 Alpha now.
Thank you!
Thank you!
Thank you!
GPT corrupted?
hi, it seems that I have a trouble now, week ago I buy my NT, try to root but unsuccessful. I think my nook had damaged GPT table.
I try use parted via ADB? and that what I get:
~ # ./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) p
p
p
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.6GB 12.9GB ext4 userdata
(parted) rm
rm
rm
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Partition number? 11
11
11
(parted) p
p
p
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.6GB 12.9GB ext4 userdata
(parted)
so, my partition table still unchanged, and I cant resize 10`s partition
(parted) resize
resize
resize
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Partition number? 10
10
10
Start? [1611MB]?
End? [2684MB]? 12.6GB
12.6GB
12.6GB
Error: Can't have overlapping partitions.
(parted)
I try this method for back to stock
http://forum.xda-developers.com/showthread.php?t=1470910
it work fine, but my problem still exist, every time that I reboot my nook it start registration process every time,
and when I try install CWM internally I get error screen on reload
"that error occurred ? try go to BN if this still" - some like this....
is any solution for me exist? Please, HELP!!!!!
P.S. Sorry, for my bad english
lavero.burgos said:
For that error...
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/
run parted while in CWM and pick fix:
~ $ adb shell
* daemon not running. starting it now on port xxxx *
* daemon started succesfully *
~ # 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
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
* Bold parts are the commands
~ Veronica
Click to expand...
Click to collapse
Hello, I have this exact problem, but when I run parted, I only get asked if this is a gpt table, no other errors to fix ?? "print" lists the partitions but no errors to fix. So the Ubuntu wipe still gets stuck writing zeros and the magic sd card method (raywaldo) does not finish. Any ideas ? Thanks
E:Can't mount errors, can usb driver right
Know-Fear said:
You don't have your ADB drivers set up correctly for the NT. You need to have ADB and the adb_usb.ini (both included with Indirect's nook&zergy root zip) Use the USB deviewer to remove any mass storage ports, anything google, or android related. Then restart the PC, plug in the NT and select the driver (located in Indirect's post with the nook&zergy zip).
Click to expand...
Click to collapse
I am having the same problem:
I get the following errors on the nook:
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 have downloaded ADB, and USB deviewer but I can't get the nook to show in windows device manager correctly
To tj3ven:
You need to delete the drivers windows installed for your NOOK and reinstall the drivers that are here on XDA. Search for ADB+FASTBOOT+DRIVERS and that will fix you.
Also, I am using windows to try to fix my partitions. I have a similar problem as sailerph, when I go to print I get no option to fix, it just lists my partitions and some basic information about them, I have no option to fix them. Anyone have any ideas?
scuzzo500 said:
To tj3ven:
Also, I am using windows to try to fix my partitions. I have a similar problem as sailerph, when I go to print I get no option to fix, it just lists my partitions and some basic information about them, I have no option to fix them. Anyone have any ideas?
Click to expand...
Click to collapse
I am having same issue. E: /cache errors in CWM & when I run parted print command it only lists the partition table and gives no option to fix. The table appears to be correct when comparing to the numbers in other threads. I am on 8GB NT so I can't use Adam's total wipe. Any help?
Now my SON bricked it and the old fix ain't workin'!
Sigh . . . like father like son. I gave my son my old Nook Tablet for his birthday (I have a Nexus 7 now) and guess what he did! Yep, he ignored my repeated warnings to ignore the alert and he bricked it.
HOWEVER, the fix that Veronica gave me last time won't work because I'm getting the following when I issue the "print" command in parted:
C:\Windows\system32>adb shell
~ # 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
Warning: /dev/block/mmcblk0 contains GPT signatures, indicating that it has a
GPT table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted -- possibly by a program that doesn't
understand GPT partition tables. Or perhaps you deleted the GPT table, and are
now using an msdos partition table. Is this a GPT partition table?
Yes/No? y
y
y
Model: MMC 016G4A (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB media
11 2684MB 15.6GB 12.9GB ext4 userdata
(parted)
I don't know where to go from here! A little help.
And BTW, I gave Veronica a donation for solving my problem last time - just though y'all would like to know!
You can try restoring to stock ROM by flashing flash_stock_1.4.2.zip posted at Succulent's recovery-tools repository https://github.com/succulent/acclaim_recovery_sdcard, or by using this method http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/.
An Unbrick Guide for 16GB Tablet. I am not responsible for damage, otherwise this should fix any damage. But am more than happy to help.
meghd00t's 8GB and 16GB partition rescue sdcard: http://forum.xda-developers.com/showthread.php?t=1562130
For whatever reason the repartitioning card didn't work on my 16gb tablet, which is why I had to do it manually.
When to use this guide
1. If you used parted to remove your entire partitions and cannot recreate them in parted
2. If 1 is true, and you can't boot into Clockworkmod
3. If 2 is true and nothing will boot at all--the only exception being booting from the sd card--and it just won't turn on at all and get into any splash screen.
4. If everything else has failed
5. If all the above are true but you can boot Clockworkmod from an sd card. This is important.
If your nook will boot into cwm, then your partitions are fine. If you would like to, however, you can still use this to fix your nook, but I insist you try other methods around the development section before trying this one. This is a long process, and most other solutions for an otherwise dead nook can easily be solved, and a lot faster. This should only be used as a last resort. Otherwise if you just want to experiment around a bit, feel free!
------
Okay. So, visit Goncezilla's thread on making a bootable cwm-sd:
http://forum.xda-developers.com/showthread.php?t=1446987
Download the files on the first method ("METHOD 1- SDCARD")
Instead of a 50mb partition, just make a 2gb partition, make sure it's formatted to fat32 and enable boot, and lba flags. I reccommend at least a 2gb microsd. Anyways, unzip the files that are provided, but put them in the root folder of the sd card, not "SDCARD". Make a folder called blk.
Go to lavero.burgos' topic on "restoring partitions with dd":
http://forum.xda-developers.com/showthread.php?t=1570022
Download the provided files: mmcblk0p1, mmcblk0p2, mmcblk0p3, and mmcblk0p4. Place them in the "blk" folder.
Download the two files provided by meghd00t here:
http://forum.xda-developers.com/showpost.php?p=24805392&postcount=74
unpack gdisk and sgdisk to the root folder of the sdcard. unpack "scripts" into the same root folder of the sdcard. Don't worry about the mess. Now make sure your nook is off by pressing and holding the power button for like 15 seconds. Then, insert the the microsd card into your nook. Connect the cable to the nook and either to the wall adapter or to your box. Let it boot into cwm. Once in, open up a terminal. First thing you want to do:
Code:
$ adb start-server
$ adb devices
now make sure your device's serial number shows up, and that it shows your nook in recovery. Now, this next part is very important. VERY important. I wish I would have done this before. But even so, there is always hope!~ But still, make sure you follow this next step:
Code:
$ adb shell
~ # mount sdcard
~ # dd if=/dev/block/mmcblk0p5 of=/sdcard/blk/mmcblk0p5
This will backup your rom partition, which holds important information, like serial no. and MAC address. You'll be happy you did this before.
**Note, if it brings up an error, make sure the sdcard is mounted, try again, and cd over to /sdcard/blk to make sure that the rom partition is there safely. If it brings up an error and everything is mounted, try changing the extension name to "mmcblk0p5.img" when you use disk dump.
Optionally, it might be smart to backup the rom partition to your computer:
Code:
~ # exit
$ adb pull /sdcard/blk/mmcblk0p5 /path/to/backup
So now, you've got all the files you need. For the sake of argument, I'll assume you have made a cwm backup before your nook died. So, go ahead and destroy your nook completely:
Code:
~ # cd sdcard
/sdcard # ./sgdisk -Z /dev/block/mmcblk0
And now re-create it:
Code:
/sdcard # ./sgdisk /dev/block/mmcblk0 -a 256 -n 1:256:511 -n 0:0:1023 -n 0:0:31743 -n 0:0:65535 -n 0:0:163839 -n 0:0:262143 -n 0:0:1019903 -n 0:0:2273279 -n 0:0:3145727 -n 0:0:+12G -n 0:0:0
This is a lot easier than re-creating the partitions with parted by the way. I'd like to give a special shout out to meghd00t for compiling these static binaries for ARM. Thanks! This is a full stock partition, if you want meghd00t's 10gb media, 2.8gb userdata partitions:
Code:
/sdcard # ./sgdisk -c 1:xloader -c 2:bootloader -c 3:recovery -c 4:boot -c 5:rom -c 6:bootdata -c 7:factory -c 8:system -c 9:cache -c 10:media -c 11:userdata /dev/block/mmcblk0
Now follow up:
Code:
/sdcard # ./sgdisk -p /dev/block/mmcblk0
verify the list is correct. Now do this:
Code:
[b]/sdcard # cd /sdcard/sbin
/sdcard # ./genptable /tmp/genptable[/b]
This will create a partition table, the stock nook tablet modified gpt table in /tmp
Code:
/sdcard # mv /tmp/genptable /sdcard/blk
~ # dd if=/sdcard/blk/genptable of=/dev/block/mmcblk0
You now have your partition table back that will pass consistency checks! but we aren't done yet. We need to reformat everything:
Code:
/sdcard # cd sbin
/sdcard/sbin # ./mkdosfs -F 32 /dev/block/mmcblk0p5
/sdcard/sbin # ./mkdosfs -F 32 /dev/block/mmcblk0p6
/sdcard/sbin # ./mkdosfs -F 32 /dev/block/mmcblk0p10
/sdcard/sbin # cd ../../
~ # dd if=/sdcard/blk/mmcblk0p1 of=/dev/block/mmcblk0p1
~ # dd if=/sdcard/blk/mmcblk0p2 of=/dev/block/mmcblk0p2
~ # dd if=/sdcard/blk/mmcblk0p3 of=/dev/block/mmcblk0p3
~ # dd if=/sdcard/blk/mmcblk0p4 of=/dev/block/mmcblk0p4
~ # dd if=/sdcard/blk/mmcblk0p5 of=/dev/block/mmcblk0p5
Who just got their Serial number back. :]
Now this next part is confusing, but for some reason make_ext4fs didn't want to work for me, so I had to do it the painful way:
Code:
~ # parted /dev/block/mmcblk0
(parted) rm 7
(parted) rm 8
(parted) rm 9
(parted) rm 11
(parted) mkpartfs primary ext2 134MB 522MB
(parted) mkpartfs primary ext2 522MB 1164MB
(parted) mkpartfs primary ext2 1164MB 1611MB
Now the userdata partition all depends on how big you made your media partition. But I will go ahead and use the stock settings
Code:
(parted) mkpartfs primary ext2 2684MB 15.9GB
(parted) quit
~ # tune2fs -j /dev/block/mmcblk0p7
~ # e2fsck -fDp /dev/block/mmcblk0p7
~ # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p7
~ # e2fsck -fDp /dev/block/mmcblk0p7
~
~ # tune2fs -j /dev/block/mmcblk0p8
~ # e2fsck -fDp /dev/block/mmcblk0p8
~ # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p8
~ # e2fsck -fDp /dev/block/mmcblk0p8
~
~ # tune2fs -j /dev/block/mmcblk0p9
~ # e2fsck -fDp /dev/block/mmcblk0p9
~ # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p9
~ # e2fsck -fDp /dev/block/mmcblk0p9
~
~ # tune2fs -j /dev/block/mmcblk0p11
~ # e2fsck -fDp /dev/block/mmcblk0p11
~ # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p11
~ # e2fsck -fDp /dev/block/mmcblk0p11
~
~ # parted /dev/block/mmcblk0
[b]
(parted) name 7 factory
(parted) name 8 system
(parted) name 9 cache
(parted) name 11 userdata
[/b]
(parted) print
Now verify that your table looks like, or at least similar, to this. Basically, you want to make sure everything is formatted correctly:
Code:
Model: MMC 016G4A (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.9GB 12.9GB ext4 userdata
If something looks a bit off, go back and repeat the appropriate step.
Code:
(parted) quit
~ # umount sdcard
~ # exit
Go ahead and shut down the device. Remove the sdcard, and turn it back on with the power button.
Status: xloader, bootloader, recovery, and boot partitions were all flashed and should be working perfectly. Which means you have probably noticed yourself booting into cwm, which is a good sign!!
Now, insert an sdcard that has your original cwm backup. And go ahead and restore your backup. Wipe /cache. Reboot the nook. You should see a splash screen. Dead nook... alive!11!
That's pretty much it. I'm just happy my nook is working. Hopefully this will help someone out who has a dead nook and has no clue how to fix it, like I did. If you have any questions, let me know so I can try to help. If you notice an error or inconsistency in my guide, please let me know so I can fix it before someone breaks their nook because of me. Sorry about reformatting the ext4 partitions guys. Since make_ext4fs wouldn't work for me, that was the only other way I knew how to do it. If someone can post what they did to reformat to ext4 using make_ext4fs, I'll edit the post to accomodate everyone else.
Thanks to: meghd00t, lavero.burgos, AdamOutler, tselling, and CelticWebSolutions.
Thanks for finding time to make this.
All i can say is Bravo!
We need more of this guides coming up.
2TU!
Nice guide.....
Sent from my Non-B&N Tablet running CM7
Very nice guide for dead nook, may i advice you to put a link for meghd00t recovery for 8GB NT so 8gb users work with the proper cwm recovery for them. I will be linking to this guide in my Unbrick thread.
Also would be good if you advice people to try alternative methods if they don't have dead dead nooks and with this i mean people that their boot block(s) is working and they have just flashed wrong recovery or flashed a rom that they should had not. This is advanced and if people have messed enough with their devices to competely wipe the partitions and more then im sure they will have fun with this .
Big thanks to meghd00t for build the tools and the cwm recovery for 8GB NT.
~ Veronica
lavero.burgos said:
Very nice guide for dead nook, may i advice you to put a link for meghd00t recovery for 8GB NT so 8gb users work with the proper cwm recovery for them. I will be linking to this guide in my Unbrick thread.
Also would be good if you advice people to try alternative methods if they don't have dead dead nooks and with this i mean people that their boot block(s) is working and they have just flashed wrong recovery or flashed a rom that they should had not. This is advanced and if people have messed enough with their devices to competely wipe the partitions and more then im sure they will have fun with this .
Big thanks to meghd00t for build the tools and the cwm recovery for 8GB NT.
~ Veronica
Click to expand...
Click to collapse
Thanks!
I did try to say when to use the guide at the beginning but I will be more specific most definitely, to make sure users don't get confused!
demetris_I said:
Thanks for finding time to make this.
All i can say is Bravo!
We need more of this guides coming up.
2TU!
Click to expand...
Click to collapse
It was kind of hard, because I couldn't remember where all the topics I used went to. Like Goncezilla's cwm sd files. I couldn't find them anywhere! I apologize for taking so long though. I'm really lazy...... not my greatest strength1!
Thank you though! I'm glad I finally figured it out1; :]
okey, so I get this error:
/sdcard # ./sgdisk -Z /dev/block/mmcblk0
/sbin/sh: ./sgdisk: not found
EDIT: never mind it didn't mount the sdcard had to restart the computer and nook then it worked.
EDIT2: now I got this error
/sdcard # /sdcard/sbin/genptable
Usage /sdcard/sbin/genptable <raw_output_file>
/sdcard # mv /tmp/genptable /sdcard/blk
mv: can't rename '/tmp/genptable': No such file or directory
Pete1612 said:
okey, so I get this error:
/sdcard # ./sgdisk -Z /dev/block/mmcblk0
/sbin/sh: ./sgdisk: not found
EDIT: never mind it didn't mount the sdcard had to restart the computer and nook then it worked.
EDIT2: now I got this error
/sdcard # /sdcard/sbin/genptable
Usage /sdcard/sbin/genptable <raw_output_file>
/sdcard # mv /tmp/genptable /sdcard/blk
mv: can't rename '/tmp/genptable': No such file or directory
Click to expand...
Click to collapse
Did you do the genptable script?
EDIT: Aw, son of a..!! I messed up, hang on, give me a second.
EDIT 2: oKAY, I fixed it. I'm sorry about that, my mistake. i bolded the text so you can see what I fixed.
okey that worked and now I get this if I do dd:
~ # dd if=/sdcard/blk/mmcblk0p1 /dev/block/mmcblk0p1
BusyBox v1.19.4-cm7 static (2012-02-04 22:27 +0100) multi-call binary.
Usage: dd [if=FILE] [of=FILE] [ibs=N] [obs=N] [bs=N] [count=N] [skip=N]
[seek=N] [conv=notrunc|noerror|sync|fsync]
Copy a file with converting and formatting
if=FILE Read from FILE instead of stdin
of=FILE Write to FILE instead of stdout
bs=N Read and write N bytes at a time
ibs=N Read N bytes at a time
obs=N Write N bytes at a time
count=N Copy only N input blocks
skip=N Skip N input blocks
seek=N Skip N output blocks
conv=notrunc Don't truncate output file
conv=noerror Continue after read errors
conv=sync Pad blocks with zeros
conv=fsync Physically write data out before finishing
Numbers may be suffixed by c (x1), w (x2), b (x512), kD (x1000), k (x1024),
MD (x1000000), M (x1048576), GD (x1000000000) or G (x1073741824)
EDIT: It has to be dd if=/sdcard/blk/mmcblk0p1 of=/dev/block/mmcblk0p1 you forgot the of=
EDIT2: mkpartfs primary ext2 2684GB 15.9GB I think the 2684GB is supposed to mean mb
EDIT3: so after doing your tutorial my partition table looks like this:
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.3MB 33.6MB 17.3MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4
8 522MB 1164MB 642MB ext4
9 1164MB 1611MB 447MB ext4
10 1611MB 14.5GB 12.9GB fat32 media
11 14.5GB 15.9GB 1443MB ext4
as you can see a bunch of names for the partitions are missing, how can I name them
Pete1612 said:
EDIT: It has to be dd if=/sdcard/blk/mmcblk0p1 of=/dev/block/mmcblk0p1 you forgot the of=
Click to expand...
Click to collapse
Yeah, yeah laugh away. I always forget it, I'm just half dumb okay? <.<;
Pete1612 said:
EDIT2: mkpartfs primary ext2 2684GB 15.9GB I think the 2684GB is supposed to mean mb
Click to expand...
Click to collapse
The laughter doesn't stop. ;_;
Pete1612 said:
EDIT3: so after doing your tutorial my partition table looks like this:
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.3MB 33.6MB 17.3MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4
8 522MB 1164MB 642MB ext4
9 1164MB 1611MB 447MB ext4
10 1611MB 14.5GB 12.9GB fat32 media
11 14.5GB 15.9GB 1443MB ext4
as you can see a bunch of names for the partitions are missing, how can I name them
Click to expand...
Click to collapse
Ooh. I forgot about that!!! Thanks for reminding me actually. You know, you've helped me with a lot of errors I've made. :l Just go back into parted and do this:
Code:
(parted) name 7 factory
(parted) name 8 system
(parted) name 9 cache
(parted) name 11 userdata
And that should do it. Go into cwm and either flash an old backup or one of the other roms.
By the way, while you're at it, do me a favour. When in clockworkmod, on the terminal, if you enter "adb devices" does it show your nook with your original serial number? This is the part I am most concerned apart. I want to make sure the serial number stays intact.
And I'm sorry for taking so long to respond. I was replacing my stupid laptop's old keyboard. It had broken shift and backspace keys. Which is probably why I seemed illiterate most of the time.
okey so I did adb devices and I only get zeros, the problem is though I couldn't pull partition 5 from my nook because the partition table was completely destroyed (and as far as I know partition 5 has the serial number and the mac adress in it)
EDIT: so I tried to install CM 7.2 which was succesfull. Then I rebooted my nook and it goes into CWM (internal).
EDIT2: just tried the recovery bootloop fix and it didn't help
Pete1612 said:
okey so I did adb devices and I only get zeros, the problem is though I couldn't pull partition 5 from my nook because the partition table was completely destroyed (and as far as I know partition 5 has the serial number and the mac adress in it)
EDIT: so I tried to install CM 7.2 which was succesfull. Then I rebooted my nook and it goes into CWM (internal).
EDIT2: just tried the recovery bootloop fix and it didn't help
Click to expand...
Click to collapse
Ok i know about this one and it might help. Flash stock 1.4.2 recovery and then run the stock 1.4.2 update.zip from sdcard. More info in my thread where it says ATTENTION 8GB USERS but works for 16GB aswell.
~ Veronica
Sent from my BNTV250A using xda premium
well and where can I find the stock recovery and the 1.4.2 ? the problem is, if this method doesn't work, am I still able to run CWM sd card?
Did you take out the microsd card? Dumb question but yeah.
Okay, I see the problem:
EDIT3: so after doing your tutorial my partition table looks like this:
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.3MB 33.6MB 17.3MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4
8 522MB 1164MB 642MB ext4
9 1164MB 1611MB 447MB ext4
10 1611MB 14.5GB 12.9GB fat32 media
11 14.5GB 15.9GB 1443MB ext4
Click to expand...
Click to collapse
Boot is a secure partition that's supposed to start at 16.8mb not 16.3mb
Hmm...hmmm... Try doing "dd if=/sdcard/blk/genptable of=/dev/block/mmcblk0" one more time. And then repost your partition table.
Pete1612 said:
well and where can I find the stock recovery and the 1.4.2 ? the problem is, if this method doesn't work, am I still able to run CWM sd card?
Click to expand...
Click to collapse
Yes, you can still run CWM from sdcard. It's probably the best thing about the nook amirite.
okey I"ll do the bootpartition fix. I changed the micro sd card becuase my bootable sdcard couldn't safe all the mmcblk0px files...
Alrighty. Let me know what happens
nope it's still at the same place:
Model: MMC 016G4A (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.3MB 33.6MB 17.3MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 14.5GB 12.9GB fat32 media
11 14.5GB 15.9GB 1443MB ext4 userdata
EDIT: can I redo the boot partition and if yes how ?
Pete1612 said:
nope it's still at the same place:
Model: MMC 016G4A (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.3MB 33.6MB 17.3MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 14.5GB 12.9GB fat32 media
11 14.5GB 15.9GB 1443MB ext4 userdata
EDIT: can I redo the boot partition and if yes how ?
Click to expand...
Click to collapse
Hmm. You can't. Because parted will automatically revert it back to 16.3MB.
Try the process again, but this time dd genptable before you create the partitions, then create the partitions with sgdisk and let me know what it says.
what do you think about the Ubuntu total recovery before I do anything else ?
Hi, Experts.
I am new to rooting and I think I screwed up my NB 16GB. I used ubuntu to connect into my NB and there is only /rom but no devconf folder. My serial number is now 0000000000000000. I am going through the steps of http://forum.xda-developers.com/showthread.php?t=1570022 but I can't download mmcblk0p8 and there is no mmcblk0p5. How can I get these 2 files? How do I know which mmc I need to restore? I can't even boot into CMW.
I can only boot to CM7 via sdcard. Is there any thread to guide me on how to recover via CM7 instead of ubuntu? Thanks.
Change to linear or full view and then you can download, i just checked and that works. I don't know why in grid view it wouldn't download but i guess is a bug in minus.com.
About mmcblk0p5 i moved it to another private folder and i will be giving the link only if needed that way i have more control of it. If you still need it the pm me and i'll give you the link.
Edit: I modified the folder's view to linear so now you can download.
~ Veronica
Now it says file does not exist
Hi, Veron.
Thanks for your reply. I tried but now it says file does not exist. I have problem previously with other files and I tried on IE, FF and Chrome. Only IE allows me to download but mmcblk0p8 is the only 1 I can't download with all browser.
ayoyo1001 said:
Hi, Veron.
Thanks for your reply. I tried but now it says file does not exist. I have problem previously with other files and I tried on IE, FF and Chrome. Only IE allows me to download but mmcblk0p8 is the only 1 I can't download with all browser.
Click to expand...
Click to collapse
Hmm thats weird because i changed the folder's view and clicked on download link of mmcblk0p8 and it started to download. Im using Ubuntu now with chromium but you should be able to. Clean your cache (Ccleaner recommended) and try again
~ Veronica
I still can't download mmcblk0p8. Is there a way for me to test which partition is corrupted and if I need mmcblk0p8? Maybe I just need to do some and not all.
ayoyo1001 said:
I still can't download mmcblk0p8. Is there a way for me to test which partition is corrupted and if I need mmcblk0p8? Maybe I just need to do some and not all.
Click to expand...
Click to collapse
Describe better your problem, what exactly you did that it got corrupted or bricked. Did you format some partitions in cwm? Or what?
~ Veronica
Sent from my SGH-I897 using xda premium
I am a novice in Android. I went into storage card, erase some of the partition. Now I can only boot into CM7. I can't boot into CWM. If I took out the CM7 sdcard, it will not start nor will not show the N logo. Taking out the card also no effect. It is just showing black screen. Even with usb plug/unplug also will not boot to CWM. Is there anyway to restore the partition from CM7 terminal emulator? Any commands? Using CM7 to restore seems like my last resort
I am from Singapore and I can't possibly do a return in USA.
Please post the parted outcome of print command to see what you have done to your mmcblk0.
ayoyo1001 said:
I am a novice in Android. I went into storage card, erase some of the partition. Now I can only boot into CM7. I can't boot into CWM. If I took out the CM7 sdcard, it will not start nor will not show the N logo. Taking out the card also no effect. It is just showing black screen. Even with usb plug/unplug also will not boot to CWM. Is there anyway to restore the partition from CM7 terminal emulator? Any commands? Using CM7 to restore seems like my last resort
I am from Singapore and I can't possibly do a return in USA.
Click to expand...
Click to collapse
I will help you out tomorrow/later may 7. if you can run CM7 from sdcard then you will be able to run cwm from sdcard as well.
~ Veronica
Sent from my SGH-I897 using xda premium
Thanks. Will wait for your great posting.
ayoyo1001 said:
Thanks. Will wait for your great posting.
Click to expand...
Click to collapse
I went into storage card, erase some of the partition
Click to expand...
Click to collapse
Can you explain better that, what OS were you running when you erased the partitions?
For now you have to start burning a cwm image from here to your scard. Why that version? because it was compiles with some useful tools in it that will help you unbrick your device.
Note: would be better if you have 2 sdcards.
Once you have cwm running from sdcard please go to this post, run parted, post the output of print and ignore the rest.
To be explicit i just need this output:
~ $ cd path-to-adb-drivers
~ $ adb shell
* daemon not running. starting it now on port xxxx *
* daemon started succesfully *
~ # 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
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.6GB 12.9GB ext4 userdata
Click to expand...
Click to collapse
... We take it from there.
~ Veronica
you mean the command below?
parted /dev/block/mmcblk0
I don't have the NT with me now. I will try out tonight when I reach home.
ayoyo1001 said:
you mean the command below?
parted /dev/block/mmcblk0
I don't have the NT with me now. I will try out tonight when I reach home.
Click to expand...
Click to collapse
read carefully and follow instructions , post what I have requested. the commands are the ones in bold
~ Veronica
Sent from my NookTablet using xda premium
Noted. I will do it tonight. Thanks.
Hi, here's the screenshots.
[email protected]:~/Downloads/android-sdk-linux/platform-tools$ sudo ./adb devices
[sudo] password for xda:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0000000000000000 recovery
[email protected]:~/Downloads/android-sdk-linux/platform-tools$ ./adb shell
~ # 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
Warning: /dev/block/mmcblk0 contains GPT signatures, indicating that it has a
GPT table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted -- possibly by a program that doesn't
understand GPT partition tables. Or perhaps you deleted the GPT table, and are
now using an msdos partition table. Is this a GPT partition table?
Yes/No? y
y
Model: MMC 016G4A (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB rom
6 83.9MB 134MB 50.3MB bootdata
7 134MB 522MB 388MB factory
8 522MB 1164MB 642MB system
9 1164MB 1611MB 447MB cache
10 1611MB 2684MB 1074MB media
11 2684MB 15.6GB 12.9GB userdata
(parted)
Hope you find it useful. Thanks.
ayoyo1001 said:
Hi, here's the screenshots.
[email protected]:~/Downloads/android-sdk-linux/platform-tools$ sudo ./adb devices
[sudo] password for xda:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0000000000000000 recovery
[email protected]:~/Downloads/android-sdk-linux/platform-tools$ ./adb shell
~ # 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
Warning: /dev/block/mmcblk0 contains GPT signatures, indicating that it has a
GPT table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted -- possibly by a program that doesn't
understand GPT partition tables. Or perhaps you deleted the GPT table, and are
now using an msdos partition table. Is this a GPT partition table?
Yes/No? y
y
Model: MMC 016G4A (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB rom
6 83.9MB 134MB 50.3MB bootdata
7 134MB 522MB 388MB factory
8 522MB 1164MB 642MB system
9 1164MB 1611MB 447MB cache
10 1611MB 2684MB 1074MB media
11 2684MB 15.6GB 12.9GB userdata
(parted)
Hope you find it useful. Thanks.
Click to expand...
Click to collapse
Hmmm oh well i don't know how you did this but your partitions does not have file system e.g fat32, ext4 format.
I assume you get 00000000000000 because rom partition got wiped as well and so your device has no serial ID to show up.
You'll have to use this method and after you fix it (hopefully that works right away) use this to have a serial ID again, i'll have to give you the link of my rom partition (mmcblk0p5) by pm as i keep it private and im giving the link only to the ones that need it by pm request. Let me know if you have any problem, post it and i'll see what i can do.
~ Veronica
I'm also new to rooting and I'm experiencing a similar issue with my NT. I derped up when using the instructions here to fix my nook's partition tables. Long story short, I thought I had backed up my mmcblk0p5 and well apparently it didn't save. When I reconnected my nook via adb my serial was all 0'ed out.
Any help? I think the only way to fix this massive derp is a copy of someone else's mmcblk0p5. If there are any other suggestions, I'm up for trying it...
UkeFox
hi guys,
i have a bricked 8GB nook tablet and it has been so as i had wrongly flashed a 16gb rom onto it.
now it has a 16gb partition table layout and cannot go back to stock.
Veronica has suggested the following solution to get my tablet unbricked.
so i request you guys, if you have a working 8GB nook tablet, please copy the partition table layout onto a SD card and send it to me..
Originally Posted by lavero.burgos View Post
@axay - im afraid you will need the help of a 3th user that own a 8GB nook Tablet to perform the following steps in order to get you a copy of a 8GB nook tablet genptable as i don't have one:
First he needs to have the following:
1. Sdcard with enough space, min 2gb.
2. Ubuntu up and running
3. working ADB
Steps:
1. In an empty or formatted sdcard create a folder named blk
2. Download script.zip and unzip its content in the root of the sdcard
3. Boot into internal CWM, plug device to PC, open a terminal as issue the following commands:
This will create and copy the stock nook tablet gpt partition table in /tmp and later will be moved to the blk folder located in your sdcard
Code:
$ adb devices
$ adb shell
~ # cd /sdcard/sbin
~ # ./genptable /tmp/genptable
~ # mv /tmp/genptable /sdcard/blk
~ # exit
$ exit
Thats all, now please upload the genptable file so @axay can use it to restore his Nook Tablet. Thanks!
-------------------------------------
@axay once you get the genptable file you need to copy it to your sdcard and issue the following commands in a Terminal while in CWM sdcard:
Code:
$ adb devices
$ adb shell
~ # cd /sdcard
~ # dd if=/sdcard/genptable of=/dev/block/mmcblk0
~ # exit
$ exit
After that run parted again and post the output, please note that you may need to format the partitions and possibly eliminate and recreate them depending of the damage. So im going step by step, in case you need to go farther then i will post the other steps.
Here is the parted print output that i found of a 8GB Nook tablet, use it to compare it with yours:
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 5620MB 4010MB fat32 media
11 5620MB 7734MB 2114MB ext4 userdata
let me first say that virtually none of what follows is my own work!
I have simply 'tweaked' and plagiarized the brilliant postings made by others, to hopefully make it all a bit more idiot proof for newbies, and lesser mortals such as myself. (respect to 'tselling' in particular) ...
Note that this only for 16GB Nooks that have been rooted, and with CM Recovery available
I'm sure it would work on the 8 gigs, but don't know the figures to use
background:
after rooting, installing CWmod, and a CM 10 rom on my 16 gig Nook Tablet by following the great guides on here, I then wanted to go the whole hog and repartition it.
initially, Veronicas post here: http://forum.xda-developers.com/showthread.php?t=1531120
seemed the best, as I could get 12 Gig for myself. sadly it did not work for me as my copy of Cwmod does not support 'sqdisk' - but I learned a lot nonetheless.
I then found 'tselling's great post here:http://forum.xda-developers.com/showpost.php?p=22157605&postcount=25
I eventually resized my partitions to approx 4GB & 9GB, but not without some issues.
the posting stated that all actual commands were in bold, eg: 2nd command was (parted) print but this failed.
“back in the day”, I was very good with MSDOS and batch files, so I knew in my heart that I had missed something obvious!, yep! - (parted) is the screen response, print is the command ... from then on it was all a bit of a doddle
so here is my two pennyworth:
preparation: read everything at least once! ... and ensure you have done a full CM backup !
1. from all the great guides on here, ensure that you know how to connect your Nook to a PC,install drivers, and 'ADB' etc, and how to get into an ADB Shell.
2. the method works via CW Recovery, which can be either from an sdcard, or installed internally, (as mine is). do not continue until you are comfortable with all that
3. reboot your Nook into Recovery, cable it to your PC, and get ADB running.
4. run command ADB devices, then ADB shell to ensure you have connectivity.
5. all the actual commands to enter into your PC are in red (some are just single letters)
6. screen responses from ADB are in black (but not bold)
7. my comments and observations are in blue (but not bold)
8. despite the length of this post, (and my blathering), the whole process takes less than 10 minuets, and only entails the copying and pasting of 24 commands from here, onto your PC
9.some of the screen responses you will get are not exactly as I have got shown below. (this is simply because I had already done it once for 4 & 9 gig, and this was my 2nd run for 12gig.)
10.even if you mess up, don't panic, as the backup you made earlier can easily be restored with your CM recovery, and you are good to go again.
11. so let's start:- below are the commands to copy into your PC (remember, red lines only)
~ # 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 (here we are simply asking it what partitions we currently have, but we don't get them until we do the 2 required 'fixes' that follow)
print
print
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.6GB 12.9GB ext4 userdata
(parted) rm 11 (removing partition 11, it needs to be removed as most of that space will be needed for partition 10 to stretch in to)
rm 11
rm 11
(parted) resize
resize
resize
Partition number? 10 (partition 10 is the one we want to the be largest, so it is to be resized))
10
10
Start? [1611MB]? (1611MB is end of partition 9, so don’t' anything -just hit enter key only)
End? [2684MB]? 13.6GB (increased from tsellings 11.6GB) (I put an extra 2 gig here as the original instructions ended up with 9 gig and 4 gig)
(also, there will be a pause here whilst it completes)
13.6GB
13.6GB
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 13.6GB 12GB fat32 media lvm
(now making partition 11, which was removed earlier)
(parted) mkpartfs primary ext2
mkpartfs primary ext2
mkpartfs primary ext2
Start? 13.6GB (ie: - where partition 10 ended earlier)
11.6GB
11.6GB
End? 15.6GB
15.6GB
15.6GB
(another pause here whilst it does it)
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 13.6GB 12GB fat32 media lvm
11 11.6GB 15.9GB 2326MB ext2
(success! look at nos 10 & 11 -my partitions are now 12GB and 2.36Gb,rather than the 4 & 9 as in the original 'tsellings' posting)
(parted) name 11 userdata (just naming partition 11)
name 11 userdata
name 11 userdata
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4326MB ext2 userdata
(parted) quit (just quitting 'part' only, and staying in the ADB shell)
quit
quit
(Information: You may need to update /etc/fstab - I did.)
~ # tune2fs -j /dev/block/mmcblk0p11
tune2fs -j /dev/block/mmcblk0p11
tune2fs 1.41.6 (30-May-2009)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
~ # e2fsck -fDp /dev/block/mmcblk0p11
e2fsck -fDp /dev/block/mmcblk0p11
/dev/block/mmcblk0p11: 11/529056 files (0.0% non-contiguous), 49429/1056092 blks
~ # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p11
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p11
tune2fs 1.41.6 (30-May-2009)
(now running e2fsck on the files system)
~ # e2fsck -fDp /dev/block/mmcblk0p11
at this point, my system did not show all the 'fixed' responses as in 'tselling's original post but it did end with the same confirmation that all was ok,
ie:
/dev/block/mmcblk0p11: 11/529056 files (0.0% non-contiguous), 49429/1056092 bloc ks
so it is ok to continue
~ # 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) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4326MB ext4 userdata
(parted) quit (simply quitting 'part')
quit
quit
~ # reboot recovery (finally, the last command)
at this point the Windows CMD box on your PC will drop out of ADB, and your Nook will reboot back into Recovery,
where, from “backup and restore - advanced restore” you can restore your data partition only.
Reboot system yet again, and all should be fine
I have attached photo of mine.
...........................................................................................................
Also, once you've done all this you can, if you wish, go back into an ADB shell and enter the following commands one at a time
cd "/data/media/B&N Downloads"
rm -r *
cd ..
rmdir "B&N Downloads"
ln -s "/media/B&N Downloads" "B&N Downloads"
this points your B & N library to your /media folder for downloading, helpful if you want to manage all your books in Calibre.
...............................................................................................................
again,
many thanks, and my full respect and appreciation, to all those whose knowledge and postings here at XDA have made all this possible for the less experienced amongst us.
Kevin
ps: it's a pity though that I do not know ADB as well as I do MSDOS, else I would have compiled a 'batch file' or script to make it automated.
Wow. Thanks. This was just what I needed. For some reason, I simply couldn't get my PCs at home to load the appropriate USB driver update for my Nook. So I did it on my Mac. I have RARELY ever opened a shell on a mac. But with a couple searches, a download or two, and this simple guide, not only did I get my nook to show up on my mac (via CWM) but to also adjust my partitions.
Awe-Some!
:good::good:
nooknut said:
Wow. Thanks. This was just what I needed. For some reason, I simply couldn't get my PCs at home to load the appropriate USB driver update for my Nook. So I did it on my Mac. I have RARELY ever opened a shell on a mac. But with a couple searches, a download or two, and this simple guide, not only did I get my nook to show up on my mac (via CWM) but to also adjust my partitions.
Awe-Some!
:good::good:
Click to expand...
Click to collapse
glad it was of some use mate,
but remember, it was not really a result of my knowledge, all I did was put it all together a bit more simply.
carkev said:
glad it was of some use mate,
but remember, it was not really a result of my knowledge, all I did was put it all together a bit more simply.
Click to expand...
Click to collapse
Understood. It takes a village.
Same here
nooknut said:
Wow. Thanks. This was just what I needed. For some reason, I simply couldn't get my PCs at home to load the appropriate USB driver update for my Nook. So I did it on my Mac. I have RARELY ever opened a shell on a mac. But with a couple searches, a download or two, and this simple guide, not only did I get my nook to show up on my mac (via CWM) but to also adjust my partitions.
Awe-Some!
:good::good:
Click to expand...
Click to collapse
Nook was recognized as NookTablet without driver from recovery, instead of ADB device or something, so I couldn't update driver for it, as it didn't
Took me 40 minutes to finally give up and open my work mac. Worked like magic from there.
Can anyone explain why this happens on windows?
---------- Post added at 12:37 AM ---------- Previous post was at 12:20 AM ----------
Did the whole guide (thanks a big for really easy-to-follow guide), because I thought that it's totally locked and unusable with Cyanogenmod. And then I understood that it's actually used by CM for apps, apps data and cache.
So I have few questions.
1. After some time of usage, do you feel that 2GB is enough for all apps and their data?
2. Is it possible to make apps that do additional download use internal storage (the freed 12GB) instead of requiring external SD? Is it maybe a matter of mounting it as sdcard1 somehow?
3. Is it totally impossible to use same partition both for apps and for media and just mount some folders right way?
Sorry for the noob questions, i'm just totally new to android partitioning and mounting.
CrazyShot said:
Nook was recognized as NookTablet without driver from recovery, instead of ADB device or something, so I couldn't update driver for it, as it didn't
Took me 40 minutes to finally give up and open my work mac. Worked like magic from there.
Can anyone explain why this happens on windows?
---------- Post added at 12:37 AM ---------- Previous post was at 12:20 AM ----------
Did the whole guide (thanks a big for really easy-to-follow guide), because I thought that it's totally locked and unusable with Cyanogenmod. And then I understood that it's actually used by CM for apps, apps data and cache.
So I have few questions.
1. After some time of usage, do you feel that 2GB is enough for all apps and their data?
2. Is it possible to make apps that do additional download use internal storage (the freed 12GB) instead of requiring external SD? Is it maybe a matter of mounting it as sdcard1 somehow?
3. Is it totally impossible to use same partition both for apps and for media and just mount some folders right way?
Sorry for the noob questions, i'm just totally new to android partitioning and mounting.
Click to expand...
Click to collapse
I'm glad that you managed it ok with you Mac and the only thing I can think of re Windows USB drivers is that sometimes windows can have too many drivers on it ( from other devices that you may not use anymore) and it gets confused
this has happened to me, and I use a simple utility I found called USBDeview with which it is easy to uninstall drivers for old phones/printers etc.
it can be found here: http://www.nirsoft.net/utils/usb_devices_view.html
as to your other 3 questions, 2 gig for apps has proved more than enough for me,
but I don't know enough to advise on you with Qs 2 & 3.
fstab
Hi, something that I missed in your guide.
You said you modified "fstab".
Can you tell what is it and why/how to modify it, or point to good article about it?
CrazyShot said:
Hi, something that I missed in your guide.
You said you modified "fstab".
Can you tell what is it and why/how to modify it, or point to good article about it?
Click to expand...
Click to collapse
I'm sorry mate. but I can't remember!
I picked up everything from either Veronica's or Tselling's original posts as I said,
and can only assume that this was something I actually did whilst doing the process.
I don't have the Nook anymore, so cannot go through it again as I did. having said that it probably isn't that important
CrazyShot said:
Hi, something that I missed in your guide.
You said you modified "fstab".
Can you tell what is it and why/how to modify it, or point to good article about it?
Click to expand...
Click to collapse
Fstab is a file that checks where your drive partitions are mounted. For example, on Linux, it's stored as a file called /etc/fstab, and you modify it if you want to map other harddrives or partitions (or even ISO images and such) to a mountpoint.
It is VERY important. If you mess up your fstab, your computer or device may be unable to boot, depending on how much you mess it up (but your data will remain intact).
sagirfahmid3 said:
Fstab is a file that checks where your drive partitions are mounted. For example, on Linux, it's stored as a file called /etc/fstab, and you modify it if you want to map other harddrives or partitions (or even ISO images and such) to a mountpoint.
It is VERY important. If you mess up your fstab, your computer or device may be unable to boot, depending on how much you mess it up (but your data will remain intact).
Click to expand...
Click to collapse
thanks, good advice - obviously I was quite lucky with whatever I did!