Related
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
I have bricked Nook Tablet BNTV250A (8gb) that I can't flash on any Rom. My partishions are completly missied so I can't even Restore from Factory.
But I still can boot from SD.
When I look my partishon I see this
~ # cat proc/partitions
major minor #blocks name
179 0 7766016 mmcblk0
179 1 7764992 mmcblk0p1
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15632384 mmcblk1
179 97 50176 mmcblk1p1
~ #
Can somebody help me and can I boot this tablet into Rom anyway? As I undestend my factory info (as MAC address) is dead but if you have any ideas I be happy.
Thank you.
Have you tried using repart.img at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/?
digixmax said:
Have you tried using repart.img at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/?
Click to expand...
Click to collapse
When I try to restore Nook Tablet to stock i see red X. Now I try binary for repart
Binary from this thead and my recovery shows simulair error:
http://forum.xda-developers.com/showthread.php?t=1513583
I try and reply.
digixmax said:
Have you tried using repart.img at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/?
Click to expand...
Click to collapse
I do all correctly?
[email protected]:~$ adb shell
~ # cd sdcard
/sdcard # parted /dev/block/mmcblk0 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? yes
yes
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? Fix
Fix
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 425952 blocks) or
continue with the current setting?
Fix/Ignore? Fix
Fix
Model: MMC 008G4B (sd/mmc)
Disk /dev/block/mmcblk0: 7952MB
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
digixmax said:
Have you tried using repart.img at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/?
Click to expand...
Click to collapse
Thanks so mutch! I after first step flash stock recovery and it works!
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!
This thread assumes there is no ROM released for recovery and you need to start from scratch to build a recovery.
After doing a lot of searching I have put together of list of items needed to build your own partition.xml file based on your specific device.
#1 A rooted phone is a must! You need to be able to backup all partitions including the partition table. Using DD is your friend here.
To build the partition.xml file you'll need the to know the following items at a minimum-
1 partition label
2 size in kb
3 type
There are other parameters such as bootable, readonly and filename but for purposes of this post we'll only work with the first three
You can use a variety of commands to get the partition label and size. e.g.-
# cat /proc/partition
# mount
# df
# parted /dev/block/mmcblk0
# ls -l /dev/block/platform/"some number".sdhci/by-name
Probably the most useful command will come from parted. (Assuming you already have it installed in your system. How to install it is another topic I won't cover here to keep this topic on track)
Code:
[email protected]_STUDIO_C_5_5_LTE:/system/bin # 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 H8G1e (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 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 524kB sbl1bak
4 135MB 136MB 1049kB aboot
5 136MB 137MB 1049kB abootbak
6 137MB 138MB 524kB rpm
7 138MB 138MB 524kB rpmbak
8 138MB 139MB 786kB tz
9 139MB 140MB 786kB tzbak
10 140MB 141MB 1049kB pad
11 141MB 143MB 1573kB modemst1
12 143MB 144MB 1573kB modemst2
13 144MB 145MB 1049kB misc
14 145MB 145MB 1024B fsc
15 145MB 145MB 8192B ssd
16 145MB 156MB 10.5MB splash
17 201MB 201MB 32.8kB DDR
18 201MB 203MB 1573kB fsg
19 203MB 203MB 16.4kB sec
20 203MB 237MB 33.6MB boot
21 237MB 2334MB 2097MB ext4 system
22 2334MB 2367MB 33.6MB ext4 persist
23 2367MB 2401MB 33.6MB ext4 apedata
24 2401MB 2669MB 268MB ext4 cache
25 2669MB 2703MB 33.6MB recovery
26 2703MB 2704MB 1049kB devinfo
27 2751MB 2752MB 524kB keystore
28 2752MB 2819MB 67.1MB oem
29 2819MB 2820MB 524kB config
30 2820MB 7818MB 4999MB ext4 userdata
You can see we can get the start, end and total size of each partition as well as the partition names.
Now we need to translate partition names into the "type" value in our partition.xml file. (Where type="some long string of numbers with dashes in between") Here is the list I have come up with so far assuming we have a GPT partition structure in our device. Always verify these values for your specific device! You have been warned.
Code:
098DF793-D712-413D-9D4E-89D711772228 rpm
0A288B1F-22C9-E33B-8F5D-0E81686A68CB modemst2
20117f86-E985-4357-B9EE-374BC1D8487D boot, recovery
20A0C19C-286A-42FA-9CE7-F64C3226A794 DDR
2C86E742-745E-4FDD-BFD8-B6A7AC638772 ssd
400FFDCD-22E0-47E7-9A23-F16ED9382388 aboot
57B90A16-22C9-E33B-8F5D-0E81686A68CB fsc
638FF8E2-22C9-E33B-8F5D-0E81686A68CB fsg
A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4 tz
D4E0D938-B7FA-48C1-9D21-BC5ED5C4B203 dbi or sdi depending on device
DEA0BA2C-CBDD-4805-B4F9-F428251C3E98 sbl1
EBBEADAF-22C9-E33B-8F5D-0E81686A68CB modemst1
EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 modem, pad, system, userdata, persist, cache
You can get these values from using the gptfdisk binary as seen in this post
forum.xda-developers.com/showpost.php?p=33358988&postcount=2 (Thanks to E:V:A)
or head on down to the spoiler section here and you can see what the labels look like- (Partition GUID Code)
https://translate.google.com/transl...ersion/index.php?t552073-420.html&prev=search
Lastly my assumption is that if the partition size is not evenly divisible by 1024 you would round up to the next nearest kb value.
33.6MB=33600kb
33600/1024=34406.4 (cant have a partial kb left over so round up)
34407
33.6MB=34407kb. Let's plug this vaule into our xml file
size_in_kb="34407"
I'm new at this. If ANY of this is wrong please comment and correct. I hope this will help!
Currently I am analysing partition.xml file in AndroidGo(nhlos) (chipset msm8909). I want to know what are the utilities of below parameters:
1) partition label
2) size in kb
3) type
4) bootable
5) readonly
For example: <partition label="boot" size_in_kb="32768" type="20117F86-E985-4357-B9EE-374BC1D8487D" bootable="false" readonly="true" filename="boot.img"/>
Please let me know , so that it will be helpful.