Related
Hi - I have a rooted Galaxy Nexus running 4.0.3 ICS and decided to connect up to my work Exchange server. They enforce a security policy that requires the phone to be encrypted. I ran the hour long encryption process and it all runs fine. Now I want to remove work email and do a factory reset. This is where I run into problems.
I run the gui factory reset, the phone reboots but never resets. I boot into recovery mode and attempt the reset but it can't mount /sdcard so the reset doesn't happen.
Any ideas to assist would be appreciated.
OK, so after an entire day at work (!!) I managed to work out that I needed to blow away my /data/media (/sdcard on Galaxy Nexus) partition which was encrypted and recreate. That was no mean feat ! But now I am well versed in the use of ADB and Fastboot !
So I managed to push up the 'parted' tool to remove and create my partition 12. I then recreated it and converted to ext3 then ext4. So now I have a working phone again and will not be encrypting it again !
The problem I have is that I can not remember the original partition size. What I have recreated is shown below.
~ # 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
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB ext4 cache
12 1218MB 15.4GB 14.2GB ext4 userdata
(parted)
Can someone please tell me what their Galaxy Nexus partition table looks like ? I am not sure if it makes any difference, but I am with Telstra here in Australia and have a 16GB Nexus.
Any help is appreciated.
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 ?
Sorry for my English.
I have NT 16G with CM7. After waking device from sleep, I was unable to toggle wi-fi state, it stuck on "Turning off.." message. When I tried to restart tablet, it shutdown but not boot up. Just stuck with blank screen and backlight on. So I held power button to shut it off. Then turn it on again.
After that, I can't change anything in internal memory. Device turns on and works for some time, but then restarts on it's own and go back to state before wi-fi problem. Any changes, as new/removed files, applications etc, revert back. Even full wipe via Ubuntu didn't work: after reboot everything back to previous state.
In dmesg I have message
Code:
mmcblk0: retrying using single block read
Any suggestions?
Can you boot into cwm? Try fixing permissions and try again.
soshite said:
Can you boot into cwm? Try fixing permissions and try again.
Click to expand...
Click to collapse
It didn't change anything. Looks like I have hardware damage. Is it possible?
Its a kernel regression, you need to format that mmcblk0 and re-create.
If this doesn't work sent for replacement as it may be a faulty chip.
How can I format it? It doesn't accept any changes. Is there any other way?
Reformatting the internal partition can be a screwy and hard thing to do. Not because it's hard to format, but simply because it's hard to retrieve the original table. Because the first 4 partitions are very secure, They need to be matching perfectly with Barnes & Noble's partition table. I recommend you just try my guide on unbricking stuff:
http://forum.xda-developers.com/showthread.php?t=1605664
I've tried your method too, with no results.
mm_d said:
I've tried your method too, with no results.
Click to expand...
Click to collapse
Interesting. :l Have you tried booting off the sdcard? What do your partition table look like? Do you have it by any chance?
Yes, I boot via sdcard into CWM, CM7, Ubuntu. From sdcard everything works.
parted output don't show anything unusual
Code:
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 12.0GB fat32 media msftres
11 13.6GB 15.9GB 2315MB ext4 userdata
mm_d said:
Yes, I boot via sdcard into CWM, CM7, Ubuntu. From sdcard everything works.
parted output don't show anything unusual
Code:
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 12.0GB fat32 media msftres
11 13.6GB 15.9GB 2315MB ext4 userdata
Click to expand...
Click to collapse
So everything looks fine. Have you dumped xloader bootloader recovery and boot partition using lavero.burgos. images??
Sent from my NookTablet using XDA
dd back the partitions, you will find a backup of them if you search the forum
I've tried it already. It didn't change anything.
Any errors?
No.
So remove partitions 1by1 format and re-create.
I cant see anything else to work.
You can use a custom recovery with excellent tools for you made by meghd00.
I recommend to use that.
After this report back.
I've tried meghd00t method already. No results.
parted log
Code:
~ # 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
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 12.0GB fat32 media msftres
11 13.6GB 15.9GB 2315MB ext4 userdata
(parted) rm 11
rm 11
(parted) rm 10
rm 10
(parted) rm 8
rm 8
(parted) print
print
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 12.0GB fat32 media msftres
11 13.6GB 15.9GB 2315MB ext4 userdata
Are you on linux?
Yes.
mm_d said:
Yes.
Click to expand...
Click to collapse
sudo fdisk /dev/block/mmcblk0
demetris_I said:
sudo fdisk /dev/block/mmcblk0
Click to expand...
Click to collapse
You talking about tablet or PC?
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
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!