Related
!! Important: Make a backup of your Nook device first !!
Resize partitions
1. Download Gparted LiveCD
2. Extract onto FAT / FAT32 USB memory stick or burn to CD-ROM
3. If on a USB memory stick, run \utils\win32\makeboot.bat from the memory stick.
Do NOT run makeboot from a hard disk!
4. Boot computer from USB device into Gparted
5. Connect your Nook running Noogie of a Micro USB card (this will make the partitions visible to Gparted).
6. Resize the last partition (nr 8) labelled "data" (= Barnes & Nobles content)
Make sure to move the partition to the far right.
7. Move the next-to-last partition (nr 7) labelled "cache" without resizing it.
8. Extend the next-to-next-to-last partition (nr 6) labelled "nook" (Side loaded content) to fill the gap.
9. Remove USB cord, Micro USB card and boot your Nook.
10. In Settings you can inspect the amount of storage space.
I received errors when the partitions were about to be moved on the disk.
I changed the partitioning resize to field where it says "Align to:" from "MiB" to "Cylinder". After a 2nd attempt and doing each partition individually all worked out well.
For those only with Windows, download Gparted LiveCD iso image and use virtualbox to boot from it. It still worked well.
Edit: I successfully repartitioned two of my Nook Simple Touch using the method above + virtualbox + Gparted LiveCD iso.
Surprisingly, the size of partitions in my two NST were slightly different, suggesting that the physical size and location of partitions don't matter as long as their order and type in the partition table are as expected and the size is big enough to hold files there. I resized and moved the last three partitions as I wanted several times and made sure they work well.
Factory reset, upgrade to 1.2.1 (this seems to require the cache partition to be big enough to hold the firmware update file: something like 128MB worked for me), rooting all worked well with resized partitions. I ended up shrinking the cache partition down to 32MB and the data partition to 128MB, reserving 1.11GB for the side-loaded contents. I'm sure the system partition can also be shrunken, but I didn't go that far.
Why a live cd? Does installing gparted to whatever linux flavor you're using not work?
I don't use linux on my PC... only on hacked router & nas.
Goggles2114 said:
Why a live cd? Does installing gparted to whatever linux flavor you're using not work?
Click to expand...
Click to collapse
So dump Noogie on a microsd card run noogie and while noogie's running plug nook into pc? Do you just plutg it in and it does everything auto, or does something in noogie need to be run? Does this work on a nook touch glow?
Sorry to sound so dense but rooted using NookManager.
Edit more to the point it's throwing up an error when trying to move sdb8 around. It shrank fine just won't move. Not sure why. Not getting any useful error messages. Just 'can't have overlapping partitions.'
Odd. I was able to move it twice and get it to behave. Yet do the same n one move and Nothing. Apologies for the rinning Log just. Meh. The rest of the partitions resized in one step. sdb8 was the one that needed two steps.
Aaaand Success. Showing up as having 913MB free as opposed to like 212 or whatever.
Edit: now I'm getting a constant 'low space' warning from nook (understandable.) And installing apps is hit/miss on if they'll actually install. Keeps claiming space issues.
Query. Do apps install to the BnN partition or where?
Good to hear another success story. In my case I squeezed all the way to 1.45GB for the side-loaded contents. boot/rom/system/cache/data partitions are shrunken, and factory partition is busted. I had to use fdisk instead of GPartED to completely recreate the partition table, though.
I think, apps are installed to the data partition (the 8th one) under /data/app. Before being installed it's downloaded to cache partition (the 7th one). In my case I gave 16M for cache and 128M for data. If you are low on the data partition and have some space left on the system partition, you can move apps from /data/app to /system/app.
Goggles2114 said:
So dump Noogie on a microsd card run noogie and while noogie's running plug nook into pc? Do you just plutg it in and it does everything auto, or does something in noogie need to be run? Does this work on a nook touch glow?
Sorry to sound so dense but rooted using NookManager.
Edit more to the point it's throwing up an error when trying to move sdb8 around. It shrank fine just won't move. Not sure why. Not getting any useful error messages. Just 'can't have overlapping partitions.'
Odd. I was able to move it twice and get it to behave. Yet do the same n one move and Nothing. Apologies for the rinning Log just. Meh. The rest of the partitions resized in one step. sdb8 was the one that needed two steps.
Aaaand Success. Showing up as having 913MB free as opposed to like 212 or whatever.
Edit: now I'm getting a constant 'low space' warning from nook (understandable.) And installing apps is hit/miss on if they'll actually install. Keeps claiming space issues.
Query. Do apps install to the BnN partition or where?
Click to expand...
Click to collapse
What's the point of doing all this?
You gave a list of instructions, but not the goal they achieve.
L_R_N said:
What's the point of doing all this?
You gave a list of instructions, but not the goal they achieve.
Click to expand...
Click to collapse
Which post are you referring to?
Troute said:
Which post are you referring to?
Click to expand...
Click to collapse
.c0.'s original post.
His instructions describe how to use gparted to resize the partitions on the NST to make full use of the memory available after you have rooted it. I've used gparted before so maybe they were clearer to me than to others but the thread title was the main clue.
Troute said:
His instructions describe how to use gparted to resize the partitions on the NST to make full use of the memory available after you have rooted it. I've used gparted before so maybe they were clearer to me than to others but the thread title was the main clue.
Click to expand...
Click to collapse
I kind of thought that Nook's internal 2GB flash is already sanely formatted (i.e. most space is dedicated to the partition that is mounted at /media). If that is not the case, then that should be noted in the first post. It would also be cool if it said exactly how much space each partition has (I think i saw these partitions back when i've used Noogie to make initial backup of my device, but i don't remember the details), and how much space you would gain, and on which partition (and where it is mounted).
L_R_N said:
I kind of thought that Nook's internal 2GB flash is already sanely formatted (i.e. most space is dedicated to the partition that is mounted at /media). If that is not the case, then that should be noted in the first post. It would also be cool if it said exactly how much space each partition has (I think i saw these partitions back when i've used Noogie to make initial backup of my device, but i don't remember the details), and how much space you would gain, and on which partition (and where it is mounted).
Click to expand...
Click to collapse
Thanks! i did the work 880MB for side loaded content now!!!
on one of my NST i had an issue resizing the FAT32 partition and i had to format it to make it work.
Other than that all went ok!
Thanks
How to maximize RAM available for apps
I found this easy to read table here.
I doubt that I will ever download books from B&N. I want to minimize the space for that. I infer that I should minimize partition 8 that gets mounted to \data. Is there a practical / actual minimum for this?
I see that anything I copy in from my PC over USB is going into media. 100MB should be more than I need. I could put in an SD card for this sort of thing if it grows.
My question is, which partition do I want to increase to make the maximum available to apps downloaded from the google marketplace?
If an application requires a minimum of 512 MB of RAM, which partition(s) do I need to set >= 512?
New additional question: Upon some further research, I see that you can use sd cards for swapfiles to increase system RAM up to a maximum of 4GB. Does anyone know if it is possible to use this built-in storage for the same purpose?
.c0. said:
!! Important: Make a backup of your Nook device first !!
Resize partitions
1. Download Gparted LiveCD
2. Extract onto FAT / FAT32 USB memory stick or burn to CD-ROM
3. If on a USB memory stick, run \utils\win32\makeboot.bat from the memory stick.
Do NOT run makeboot from a hard disk!
4. Boot computer from USB device into Gparted
5. Connect your Nook running Noogie of a Micro USB card (this will make the partitions visible to Gparted).
6. Resize the last partition (nr 8) labelled "data" (= Barnes & Nobles content)
Make sure to move the partition to the far right.
7. Move the next-to-last partition (nr 7) labelled "cache" without resizing it.
8. Extend the next-to-next-to-last partition (nr 6) labelled "nook" (Side loaded content) to fill the gap.
9. Remove USB cord, Micro USB card and boot your Nook.
10. In Settings you can inspect the amount of storage space.
I received errors when the partitions were about to be moved on the disk.
I changed the partitioning resize to field where it says "Align to:" from "MiB" to "Cylinder". After a 2nd attempt and doing each partition individually all worked out well.
Click to expand...
Click to collapse
I have a little (maybe big?) problem. Can't partition with Gparted Live, as gparted scans my /dev/sdb (nook) infinitely. If I plug out my nook, other partitions (in my case: /dev/sda) become visible and ready. Looks like my nook hangs gparted. Tried on 2 different PCs and no effect. Tried different version of Gparted Live (i486 & amd64) - still nothing.
Of course noogie is inside the nook unit, ready and steady. Already made a backup of (non-rooted) device, plus partitions are visible in Minitool Partition Wizard on Windows 7.
What to do in this situation? Is Linux the only safe way to repartition device? Or maybe Minitool would be as effective and safe?
If Linux is the only way to go, how to make nook visible to Gparted?
Please, experts.
DJ Athlon said:
I have a little (maybe big?) problem. Can't partition with Gparted Live, as gparted scans my /dev/sdb (nook) infinitely. If I plug out my nook, other partitions (in my case: /dev/sda) become visible and ready. Looks like my nook hangs gparted. Tried on 2 different PCs and no effect. Tried different version of Gparted Live (i486 & amd64) - still nothing.
Of course noogie is inside the nook unit, ready and steady. Already made a backup of (non-rooted) device, plus partitions are visible in Minitool Partition Wizard on Windows 7.
What to do in this situation? Is Linux the only safe way to repartition device? Or maybe Minitool would be as effective and safe?
If Linux is the only way to go, how to make nook visible to Gparted?
Please, experts.
Click to expand...
Click to collapse
If Gparted doesn't work for you, I'd highly recommend Minitool Partiton Wizard - it's what I used to partiton my Nook. Nice, easy UI, too.
Yeah, I often work with Minitool, but is it as safe as Gparted when it comes to nook?
DJ Athlon said:
Yeah, I often work with Minitool, but is it as safe as Gparted when it comes to nook?
Click to expand...
Click to collapse
Yeah, it is. Just make sure to make a Noogie backup before repartitoning.
Sorry for bugging you, but can't shrink userdata(ext3). What to do? Delete that partition and re-create it or...?
DJ Athlon said:
Sorry for bugging you, but can't shrink userdata(ext3). What to do? Delete that partition and re-create it or...?
Click to expand...
Click to collapse
Yes, delete and recreate is the way to go.
Please, people, help me
Write step to step guide for work with Minitool Partiton Wizard
I want to free the reserved space for B&N books of my NST ver. 1.2.1
The device is already rooted.
I installed Minitool Partiton Wizard on my PC, but after connecting it thru USB cable with my Nook, it only see "official" 240MBs.
Cannot find other around 750 MB reserved storage for B&N books ?
What to do
Explain to me, please
Dear Members!
I did the stupid thing of using a tool, not completly knowing what it does.
After using TouchEraser.zip I installed Alpha-FormatTouch-2.zip using clockwork.
I tried to boot the device, no luck...
Clockwork says:
can't mount /cache/recovery/log/log
can't open /cache/recovery/log/log
can't mount /cache/recovery/log/last_log
can't open /cache/recovery/log/last_log
Please help!
Stupidly enough I don't have the devices own factory image.
What to do now?
ok , first boot with noogie image and lets see what partion u got , if u have got rom partions so take a copy all files from it and take backup from the whole nook and do this steps in this post
http://forum.xda-developers.com/showpost.php?p=30722156&postcount=2
but u must try to recovery ur nook partition rom especially cuz very important ..... before do anything above .... i will keep continue active in this thread
good luck
only one partition on on gParted...
Do You think theres any way to fix it? how?
If CWR came up that far then the /rom partition must be ok.
All we know is that the /cache partition has a problem.
That's a disposable partition, you can format the /cache partition.
Be careful, don't make anything worse.
auerg said:
Do You think theres any way to fix it? how?
Click to expand...
Click to collapse
as Renate say ..... dont make anything more worth .... so can u type fdisk for ur nook to see all ur partition table info???
Pretty screwed...
speedman2202 said:
as Renate say ..... dont make anything more worth .... so can u type fdisk for ur nook to see all ur partition table info???
Click to expand...
Click to collapse
I did but what it listed is ONLY ONE 1,8 gb partition. Toucheraser probably wiped the whole table (
I'd need a tool to restore the original filesystem or a factory image ( I don't have my own...).
I found one for glowlight, but probably I shouldn't write that to my mormal NST.
Alpha-FormatTouch-2.zip using clockwork.didn't work.
I'm pretty screwed...
Get Clockwork Recovery working on an SD card.
Get ADB setup and connected to CWR.
Run nookpart.sh from a shell (download the script from my signature).
This will recreate the partitioning without formatting or writing any of them.
You can then see if/what you can mount.
Use either the mount options in CWR or the mount command in ADB.
U kidding with me. Did u format the whole partition.? I suggest u try again and boot ur nook with noogie image and the all sevsen partition will show to U?
Tru agan man. Good luck
Sent from my NOOK using xda app-developers app
resurect nook
Renate NST said:
Get Clockwork Recovery working on an SD card.
Get ADB setup and connected to CWR.
Run nookpart.sh from a shell (download the script from my signature).
This will recreate the partitioning without formatting or writing any of them.
You can then see if/what you can mount.
Use either the mount options in CWR or the mount command in ADB.
Click to expand...
Click to collapse
I even can`t do that!,"my" nook simple are "dead" after, i delette all the memorie intern with MINI TOOL PARTITION WIZARD, without make backup or copy room, very nervius then, with CLOCKWORK RECOVERY in a sd card y instal a program call ALPHA FORMAT TOUCH2, after that my nook are iresponsive .no sd card function
any more no usb conection just charge, ¿can is posible resurrect it by some way?
dummy56 said:
...
i delette all the memorie intern with MINI TOOL PARTITION WIZARD, without make backup or copy room,
...
¿can is posible resurrect it by some way?
Click to expand...
Click to collapse
The only way I can think of to quasi-resurrect your Nook is if you can obtain a full image backup of another Nook (e.g., boot it up with noogie and read/save its entire drive as an image file) then write the backup image file back to your Nook (after booting it up with noogie) -- but then the two Nook devices will have identical device-specific data (e.g., encryption keys, WiFi MAC address, etc.), which can cause Internet access/communication problems of various sorts.
The batery are charged but it won't power on , after i install ALPHA FORMAT TOUCH2
maybe i kill him.
Wow, this is an old thread!
The Nook Simple Touch was/is a simple device.
With its SD card it's almost completely unbrickable.
Add in the stuff we've learned in the last few years about booting over USB and it's almost unsinkable.
First, whenever somebody says "dead", it's never clear what the state is.
Until you get to the point where the screen is initialized you don't know what's going on.
If you have Windows where it goes "bong" when you plug in a USB device, see if it "bongs" when you connect/power up/power down.
As said above, you'll probably need to find a full NST image somewhere.
similar to this http://forum.xda-developers.com/showthread.php?t=2322762
-------------------------------------------------------------------------
the batery are charged the machine have no image and whent i plug in a usb, no screen are inicialized just windowsXP said "OMAP3630 - No driver found". :silly:
Dear Renate, may I kindly ask you to provide the command prompt syntax here for dummies like me: "Run nookpart.sh from a shell (download the script from my signature)"? I know how to use adb, but with a ready syntax only.
And I have a spare completely bricked NSTGL, it was brought to me bricked already, managed to write an image from my current NSTGL using MiniTool Partition Wizard, and was able to open it in Windows Explorer, could see all files and folders, could add, copy and delete anything, but never succeeded in seeing any sign of life at the Nook's screen (nothing at all, never), and tried everything with a battery - disconnected it, pressed the switch button at the mainboard for some time, charged fully etc., then one unhappy day I have tried to overwrite it with a new image, but forgot to delete all partitions first and it crashed during the writing process in MiniTool Partition Wizard and now it is recognized by Windows (bang) and shown as a (some) drive but I cannot open it. Obviously I have damaged the partition table, and since then was unable to restore it, and now came across your messages here. Although, I am afraid restoring the partition table will do me no good, as it already showed no sign of life with a healthy image onboard. And I would appreciate it if you provide here a syntax for adbsync too
Mnurlan said:
Dear Renate, may I kindly ask you to provide the command prompt syntax here for dummies like me: "Run nookpart.sh from a shell (download the script from my signature)"? I know how to use adb, but with a ready syntax only.
...
And I would appreciate it if you provide here a syntax for adbsync too
Click to expand...
Click to collapse
I think a simpler, more expedient alternative to any adb-based method would be:
Use a disk-imaging tool (such as win32diskimager) and write to SD-card the image Noogie.img
Boot your live NSTGL off the Noogie SD-card and connect it to your PC via USB
Use the disk-imaging tool to read/save the NSTGL drive image to a file on your PC
Disconnect your live NSTGL from your PC
Boot your bad NSTGL off the Noogie SD-card and connect it to your PC via USB
Use the disk-imaging tool to write the file containing previously saved image of the live NSTGL drive to the bad NSTGL drive.
When writing out a disk image, make sure that you select the correct target drive (in particular don't select by mistake your PC "C:" drive).
Afterward you will have to figure out how to resolve the issue of the two Nook devices having identical device-specific data (e.g., encryption keys, WiFi MAC address, etc.), which can cause Internet access/communication problems of various sorts.
@Mnurlan I think @digixmax has it about right.
Just copying a whole image over is probably the easiest way.
If you have a raw image of the whole disk then the partitioning comes over just like all the other data.
@dummy56 if your device is IDing as OMAP3630 then what you have there is the bootloader.
The easiest thing to try would be just like above, with noogie and a full 2GB image from a friend.
Depending on what got overwritten, you might be able to fix things with just a recovery and ADB.
2 digixmax and 2 Renate
This is exactly what I did, remember I said that I received the "bad" NSTGL bricked already, so of course I took an image of my healthy (live) NSTGL FW1.2.0 to overwrite (re-write) whatever was left on "bad-dead" NSTGL, and I know in details how to write-read-save an image with win32diskimager, just during the second attempt I forgot to delete all partitions first and that resulted in damaged partitions - that is my educated guess. I would like to point out that my first attempt was successful (I have copied a healthy image of my live NSTGL to a bad one) and I was able to read-see-delete-add anything to NSTGL in Windows Explorer whenever I connect that dead NSTGL to PC directly, without a Noogie.
I am afraid, the screen has been damaged somehow (although it looks visibly intact), as it never showed any sign of life, no matter whatever I've tried.
And now the problem is that no Nook's partition appears in the MiniTool Partition Wizard window, only SD-card with Noogie, so I have nowhere to write an image. This is why I thought the culprit is - a damaged partition table. I have tried to use the GParted Live CD, but my notebook failed to boot on it, so I just postponed it for a while, as I had to leave for my rotation. Currently I am away from home and I left that "bad" NSTGL at home, and won't be able to do anything about it until I am back on Feb. 18.
And having two Nook devices having identical device-specific data is the least of my problems as I am pretty sure that I can easily do without W-Fi functionality of that Nook should I manage to revive it somehow, which I doubt.
Mnurlan said:
This is exactly what I did, remember I said that I received the "bad" NSTGL bricked already, so of course I took an image of my healthy (live) NSTGL FW1.2.0 to overwrite (re-write) whatever was left on "bad-dead" NSTGL, and I know in details how to write-read-save an image with win32diskimager, just during the second attempt I forgot to delete all partitions first and that resulted in damaged partitions - that is my educated guess.
...
And now the problem is that no Nook's partition appears in the MiniTool Partition Wizard window, only SD-card with Noogie, so I have nowhere to write an image. This is why I thought the culprit is - a damaged partition table.
Click to expand...
Click to collapse
Since Wiin32DiskImager can read/write from/to a raw physical device, there is no need to clear/fix the partition table of the bad NSTGL using MiniTool or GParted before re-imaging it.
As long as your bad NSTGL when booted on Noogie appears as a raw physical drive in Win32DiskImager's drive-selection menu, you can re-image the bad NSTGL using the raw drive image of the good NSTGL.
NSTGL in question appears as (some) drive in Windows Explorer window, but does not appear in the Wiin32DiskImager's drive selection window, and I run it As Administrator
Hi, I have a Nook Simple Touch device with a traditional problem of improper backup of 76 MB before rooting.
Now I have managed to retrieve files from the /rom partition (/devconf folder with 20 files like serial no, public key etc.) - I have them in my laptop as regular files as well as 16 MB partition image on SD card.
Would anybody be so kind to offer a full recovery method? I believe backup of somebody's full image and then overwriting the /rom partition would revive the device?
How much of your partition table is left, if any, and how familiar are you with linux?
Were it me, I might have a go at creating just the first partition - boot from noogie, connect to a linux box, and use fdisk to create the partition.
I'd then try doing a
dd if=single.partition.backup.img of=/dev/mmcblk0p1
(writing my boot backup to the partition I just created) and see if that file wasn't enough to bootstrap the other partitions. Depending on how you created the backup, you may have the boot flag set and the partition table stored; so long as you haven't actually put data on the other partitions yet, it may be possible to at least trigger the onboard restore.
These are values that work on the glow, and I believe on the touch as well:
Disk /dev/block/mmcblk0: 2000 MB, 2000683008 bytes
128 heads, 32 sectors/track, 954 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LB
A)
Of the partitions, I still have:
- boot (I believe it is somewhat corrupted, but this I can restore from the backup)
- NOOK (FAT32) - should be OK, I see files in it;
- cache (Ext3)
- data (Ext3) - seems to be corrupted
Missing: factory (Ext2); one untitled partition and one unallocated segment.
Backup was created with Roadkil's DiskImage, with a source being the locigal drive (original boot partition).
I'm not good at Linux, but I know how to create partitions using Windows tools.
OK, I can try to recreate the boot partition and the rom partition, and restore the backup to it, then I'll see what happens.
Disk configuration for NST is different from the NSTG:
Cylinters: 238 Heads: 255 Sectors: 63
Nook is resurected!
Yes, I have managed to revive the Nook Simple Touch who had survived deletion of all partitions and restore of just the boot partition!
You will need for this:
- an micro SD card and card reader;
- Noogie;
- Minitool Partition Wizard (or other partition management software, if you like and it can do partition recovery and copying);
- ClockworkMod (sd_2gb_clockwork-rc2.zip)
- Alpha-FormatTouch-2.zip - to be copied onto ClockworkMod SD card;
The principle is this:
- first of all, do a PROPER backup of your device - backup ENTIRE PHYSICAL DISK (2 GB) into the image file.
- Using Minitool Partition Wizard, do a partition recovery operation - you should find all your deleted partitions - but do not apply changes yet!. However, due to improper restore of logical disk to a physical disk, the disk config info probably became corrupted and disk size appears to be 78MB, so you won't be able really restore the partitions. So, using Minitool Partition Wizard, do a copy of the recovered partitions one by one onto the SD card - and start with the most important rom partition. From Partion Wizard, you should be able, using Explore function, to check if the partition has all necessary files (20) like serial no, public key, mac address etc.
- from SD card, you can create a backup image of each partition on your hard disk.
- after you have copies of all necessary partitions (boot, rom, nook are vital; others are optional), you need to do a wipe on the NOOK disk to delete all partitions and the disk to obtain the original size of 2 GB.
- on an empty disk after wipe, you have to restore the partitions in the order:
1. restore, by copying using Minitool Partition Wizard, the boot partition (78 MB, FAT32, Primary, set it Active)
2. restore, by copying using Minitool Partition Wizard, the rom partition (16 MB, FAT32, Primary)
3. create manually new partition factory (190 MB, Ext2, Primary)
4. create manually new partition (no label) (288 MB, Ext2, Logical)
5. copy from backup partition NOOK (240 MB, FAT32, Logical)
6. create manually new partition cache (Ext3, 240 MB, Logical)
7. create manually new partition data (Ext3, 801 MB, Logical).
Then, boot the Nook from ClockWorkMod SD card, and format /system, /cache, /data partitions;
afterwards, install from zip card - Alpha-FormatTouch-2.zip.
And, hopefully, your Nook will be alive again!
(Now, I'm sure, you won't forget to do a proper backup of your working Nook :fingers-crossed
Yes, you save my nook. Thanks to your method i could revived my /rom.
but all is not done for me . i have a UK NST Glow and the glow is not working. I would like to update to firmware1.2 and may be this glow will function again. But When i plug the usb, windows cann see the drive but i don't have access to it. i have the message "please insert disc in F: drive"
wow wow wow . At last i successed to update to FW 1.2 for my almost bricked UK NSTGL. Now i have a US NSTGL but nevermind. now time to backup correctly.
but i'm not sure your method is fully working. I had to make a partition table with renater script "nookparted.sh" and then use roustabout's comment "dd if=boot.img of=....". and after that i put update 1.2.
In one week i have learn so much with my broken backup.
Hello, new here so hope it's ok to hijack this thread slightly, seems the original issue has been solved and I think my problem is similar although I'm way out of my depth here... I've managed to brick my nook, and although I took a backup which is AFAIK correctly sized 1.86gb I can't restore it. I've tried putting noogie and cmw on the sd card but it's refusing to boot, I suspect I nonced the partition table up and can't even get the nook to register when I plug it in to the PC now. I suspect is obvious I'm a dumb noob but if anyone could help point me in the right direction it would be much appreciated
welcome to the brave new world of the "bricked forever" and endless nights.
Nobody blames you since everybody and their mothers seem to fall into the trap even if they are told to make a good backup.
i had read so much threads to resurect my nook that i don't exactly know how i made it through, but here are some indications:
Here are the objectives:
1) make a correct backup of your bricked nook: -> you can make after all stupid commands and you 'll come back to this point.
2) you'll have to resurect your /rom or your rombackup.zip (inside factory).
3) have the correct partition of your nook
4) reinstall the rom
for 2) this thread gives a way to get back your /rom. read carefully even roustabout's comment can really help
for 3) thanks to Renate NST in this http://forum.xda-developers.com/showthread.php?t=1805936&highlight=to+stock and her script "nookpart.sh" i could have a correct size for my partition. (method with wizard partition gives wrong cylinders alignement). read all of this thread it is really rich.
for 4) if you reach that point that should be easy.
Thanks for the welcome and the reply jjinkou2.
I'm guessing I need to work on the nook through a PC. I've currently got 2 PCs, one running window 7 and one on vista, I'm mainly working on the W7 machine. When I plug the nook in to it, a device briefly shows up as the h: drive in My computer but then immediately disappears and so I can't actually access it yet. I note that roustabout mentions working in Linux, if I had a Linux machine available would it be easier to get it to recognize the nook?
Edit: Just tried plugging the nook into my vista machine (which it has not been used on before) and the Found New Hardware window briefly pops up but then vanishes and I get a message on the taskbar: Device driver software was not successfully installed - OMAO3630 Device unplugged. Is there a fix for this pelase?
Some easy instructions here http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
you'll need to install android sdk and check usb install in the extra.
Search for a file named "ADB + Fastboot + Drivers.zip" in the forum to easily have the adb.
With windows the usbdriver can be tricky to install. i had to use usbdview (look for it in google) and uninstall all B&N mass storage and OMAP3630.
The driver for usb inside the previous zip might not work also. i found one in the forum but can't find it right now.
Edit
found the usb driver that worked for me
http://forum.xda-developers.com/showthread.php?t=1125094
Excellent, thanks very much! Not entirely sure how I managed it but I managed to get to a point where I could use the method shown by budriunas and my nook is now working again, albeit with an older firmware and the glow light isn't working but at least it's not bricked! Now just to get the light working and then root the damn thing without killing it....
budriunas said:
Yes, I have managed to revive the Nook Simple Touch who had survived deletion of all partitions and restore of just the boot partition!
You will need for this:
- an micro SD card and card reader;
- Noogie;
- Minitool Partition Wizard (or other partition management software, if you like and it can do partition recovery and copying);
- ClockworkMod (sd_2gb_clockwork-rc2.zip)
- Alpha-FormatTouch-2.zip - to be copied onto ClockworkMod SD card;
The principle is this:
- first of all, do a PROPER backup of your device - backup ENTIRE PHYSICAL DISK (2 GB) into the image file.
- Using Minitool Partition Wizard, do a partition recovery operation - you should find all your deleted partitions - but do not apply changes yet!. However, due to improper restore of logical disk to a physical disk, the disk config info probably became corrupted and disk size appears to be 78MB, so you won't be able really restore the partitions. So, using Minitool Partition Wizard, do a copy of the recovered partitions one by one onto the SD card - and start with the most important rom partition. From Partion Wizard, you should be able, using Explore function, to check if the partition has all necessary files (20) like serial no, public key, mac address etc.
- from SD card, you can create a backup image of each partition on your hard disk.
- after you have copies of all necessary partitions (boot, rom, nook are vital; others are optional), you need to do a wipe on the NOOK disk to delete all partitions and the disk to obtain the original size of 2 GB.
- on an empty disk after wipe, you have to restore the partitions in the order:
1. restore, by copying using Minitool Partition Wizard, the boot partition (78 MB, FAT32, Primary, set it Active)
2. restore, by copying using Minitool Partition Wizard, the rom partition (16 MB, FAT32, Primary)
3. create manually new partition factory (190 MB, Ext2, Primary)
4. create manually new partition (no label) (288 MB, Ext2, Logical)
5. copy from backup partition NOOK (240 MB, FAT32, Logical)
6. create manually new partition cache (Ext3, 240 MB, Logical)
7. create manually new partition data (Ext3, 801 MB, Logical).
Then, boot the Nook from ClockWorkMod SD card, and format /system, /cache, /data partitions;
afterwards, install from zip card - Alpha-FormatTouch-2.zip.
And, hopefully, your Nook will be alive again!
(Now, I'm sure, you won't forget to do a proper backup of your working Nook :fingers-crossed
Click to expand...
Click to collapse
Thank you so much. My nook is back. I described my work in http://forum.xda-developers.com/showthread.php?p=34746242#post34746242.
jjinkou2 said:
wow wow wow . At last i successed to update to FW 1.2 for my almost bricked UK NSTGL. Now i have a US NSTGL but nevermind. now time to backup correctly.
but i'm not sure your method is fully working. I had to make a partition table with renater script "nookparted.sh" and then use roustabout's comment "dd if=boot.img of=....". and after that i put update 1.2.
In one week i have learn so much with my broken backup.
Click to expand...
Click to collapse
how did you do a partition table?? i have run nookpart.sh but i still get the problem : "When i plug the usb, windows cann see the drive but i don't have access to it. i have the message "please insert disc in F: drive"
nookpart.sh will partition the internal memory exactly like it was.
This is important if you actually still have valid data but the partition table was destroyed.
If partitions are not looking correctly they may need to be formatted.
Don't be too quick to repartition/reformat until you know what the situation is.
i have used nookpart.sh but still no good, here is the result when i execute nookpart.sh. Everything works except internal storage not mounted correctly i think, i want to update to 1.2
edit: see my thread http://forum.xda-developers.com/showthread.php?p=48015536#post48015536 for more details
I recently had my 1 tb hdd on my sony laptop replaced with a 180 gig ssd. I let best buy do the switch because it was free and I figured why not. When I got it back with a clean install on the ssd there is only 95 gigs free. The c drive says 95 free out of 129 total. I knew I wouldn't get the whole 180 but why only 129? Just wondered if this is normal or not as this is my first ssd.
It's a matter of multiplication. 2 to the 10th power is 1024, so numerically you get a so-called 180 (or what not) but since the OS reads storage in terms of powers of 2, you get a different number.
Now, on the other hand, 130 seems way too low. I would say to go to disc management and see if there's another partition. Since this is a laptop, it likely has a recovery partition (unless you know your old drive didn't have one).
Sent from my LG-P999 using xda premium
Recovery partition is indeed the most likely reason. Disk Management will show you what the full size of the storage device (SSD in your case) is, as well as what volumes ("drives") it contains, and whether there's any unpartitioned space. It will also let you delete and resize partitions.
The easiest way to launch it on Win8 is to right-click the Start button (or hit [Win]+x) and select Disk Management from the menu, although you can also type "disk" into Start search and go to Settings, or type "diskmgmt.msc" and hit [Enter] immediately.
Thanks for the replies. I will check into the disc management.
Sent from my Galaxy Nexus using xda premium
Thanks guys I found the disc management and I see that there are 4 other partitions besides my c drive. Would anyone know what ones are safe to delete if any?
OEM : 260 mb
Recovery: 1.44 GB
EFI System: 260 mb
Recovery: 36 GB
Im assuming I should probably keep the OEM and EFI partitions but what about the two recoveries. I have a recovery flash drive which is how the os got flashed to this ssd in the first place.
Thanks again if anyone has time to help me out.
ROORnNUGZ said:
Thanks guys I found the disc management and I see that there are 4 other partitions besides my c drive. Would anyone know what ones are safe to delete if any?
OEM : 260 mb
Recovery: 1.44 GB
EFI System: 260 mb
Recovery: 36 GB
Im assuming I should probably keep the OEM and EFI partitions but what about the two recoveries. I have a recovery flash drive which is how the os got flashed to this ssd in the first place.
Thanks again if anyone has time to help me out.
Click to expand...
Click to collapse
Both of the recoveries should be safe to delete, yea, though you'll have to resize the main partition (not hard, but not really for novices either) to get it back on there.
ROORnNUGZ said:
Thanks guys I found the disc management and I see that there are 4 other partitions besides my c drive. Would anyone know what ones are safe to delete if any?
OEM : 260 mb
Recovery: 1.44 GB
EFI System: 260 mb
Recovery: 36 GB
Im assuming I should probably keep the OEM and EFI partitions but what about the two recoveries. I have a recovery flash drive which is how the os got flashed to this ssd in the first place.
Thanks again if anyone has time to help me out.
Click to expand...
Click to collapse
For the amount you gain I would suggest only deleting the 36 Mb partition. Do you really need the extra space?
One expands a partition by deleting the partitions that are not desired and then increasing the size of the active partition. It is not hard to do from the control panel. The only consideration is that to expand a partition, I believe the space has to be adjacent to the existing partition. This means that you may be limited as to which partitions can be retained and still provide a single space for your active partition.
Ok cool I think I will be safe to delete the 36 gig recovery since I have a recovery flash drive. I will look up some more info on deleting and expanding partitions. I'm no expert but I can handle following instructions so I should be able to figure it out. Thanks again.
Expanding a partition is trivial, although (as @stevedebi said) it has to be adjacent (specifically, it must be located directly before) a block of free space. Deleting a partition that is right after your C drive will easily let you expand the C drive. Just right-click the drive (in Disk Management) and select Extend (might be Expand, something like that; it'll be obvious). It will default to using the maximum available size; confirm that dialog and a few seconds late you will have a newly enlarged drive.
The recovery was located right after the c drive so I was able to expand the c drive but first I had to delete the recovery through the command line. I found some you tube instructions and it was easy.
Sent from my Galaxy Nexus using xda premium
This is win8 right? Deleting the recovery partition means you can't boot into the recovery environment. Though I was under the impression the recovery partition needed to be only a GB at most, since the actual recovery tools are stored on the main partition.
Sent from my 820 using Board Express
link68759 said:
This is win8 right? Deleting the recovery partition means you can't boot into the recovery environment. Though I was under the impression the recovery partition needed to be only a GB at most, since the actual recovery tools are stored on the main partition.
Sent from my 820 using Board Express
Click to expand...
Click to collapse
Not sure about other systems, but my Toshiba has the option to make recovery media.
Sent from my IdeaTabA2109A using xda premium
I had already made a recovery flash drive using the sony software. This is what was used to install windows 8 on the ssd when it was put in. So I assumed that is as good as a recovery partition. Hopefully that is correct. I probably just can't use the refresh pc options anymore and would have to do a clean install with the flash drive. There is also still a 1.44 gig recovery partition that I left. So maybe that smaller one is made by windows and the larger one I deleted was from sony.
sorry if in the wrong section but i need a bit of help in partitioning a hard drive.
see attachment
i have shrunk a partition and i want to put it back but has somehow been separated from it's host (C: drive) and the efi drive is now in the way so now i cant merge the D: partition back to the C: partition because there no longer neighbors. how can i move the EFI partition over or the D: partition so that i can merge them back together?
xdarkmario said:
sorry if in the wrong section but i need a bit of help in partitioning a hard drive.
see attachment
i have shrunk a partition and i want to put it back but has somehow been separated from it's host (C: drive) and the efi drive is now in the way so now i cant merge the D: partition back to the C: partition because there no longer neighbors. how can i move the EFI partition over or the D: partition so that i can merge them back together?
Click to expand...
Click to collapse
I do not believe you can merge partitions while the system is running. If i remember correctly, you have to reformat the entire hard drive in order to do that. Taking away from one partition is an operation which usually has no way of undoing without losing data.
You need a couple of utils.
MiniTool Partition Wizard (freeware) http://partitionwizard.com
Acronis True Image 2014 (trialware) http://acronis.com/homecomputing/trueimage
Make a bootable USB from each of the provided tools. The TrueImage boot USB will work w/o limitation (trialware only affects the Windows app). You only need the boot images; once that's done, you can uninstall the tools.
Am assuming that D: is empty. Boot to USB and use TrueImg to back up the ESP (EFI system partition). If C: has user data, back it up as well (onto a separate storage device). Use PartWiz to nuke the D: and ESP partitions, recreate a 200MB partition at the end of the drive, and expand C: to fill the rest. Use TrueImg to restore the ESP to the 200MB partition.
This kind of thing can also be done from any Linux liveCD worth mentioning; they all include parted and usually a graphical front-end to it (either gparted or qtparted, sometimes something else too). Parted is capable of moving partitions and of resizing them.