Hi,
I have a problem that hopefully can be easily fixed. Heeeelp!
After rooting with SalsichaNooter3 , unrooting, re-rooting. Well, basically trying everything (for fun), I’m ending with a Nook that have no storage space available. At one point, my Nook was connected to the same PC where I was doing a Wi32Image with SalsichaNooter to the SDCard. The image might have been written to the Nook instead of the SDCard (here I’m not sure). The Nook would not boot, so after different manipulation, I can now boot the Nook with original recovery firmware 1.0.0 but there is no storage available. I can download from B&N shop, read, do all of what is expected from this device but the NOOK folder doesn't appear when connected to the PC. If I look at ‘Available storage’ in the settings menu, I get ‘0. 00B free of 0.00B’
I tried ‘erase, reset Nook’ from the menu, also the recovery with the power-left,right bottom buttons. I tried with n2T-Recovery 0.1 and 0.2. All seems to properly do their job but the storage partition still doesn’t seem to be available.
I suspect that the ‘boot’, ‘rom’ and ‘firmware’ partition are proper since I can boot, register and use the device so I tried with Partition Wizard to adjust the ‘*:NOOK’ and ‘*:userdata’ partition (formatting, change ID, etc), without success.
I don’t have a valid backup – I did my original backup using the drive ref. instead of the physical disk (I know, I should have read more - sniff).
Below is the screen shoot of Partition Wizard. Does anyone have an idea? Have none left. Maybe replacing the NOOK partition from a valid image using Partition Wizard would work but I don’t have access to such image.
Thanks.
For those interrested in my solution.
Inspired by this thread:
http://forum.xda-developers.com/showthread.php?p=16818990
I recreated the image partitions under linux with dd and sfdisk and repopulate the boot, factory, rom and empty name partition with my broken backup.
Write image to Nook using Noogie and RoadKill Disk Image.
Did a factory restore with power+2 lower side button method to be on safe side.
Seems to work nicely with extra space for sideloading (used the same space assigments as describe in the above thread).
Now, my recovered 1.0.0 version doesn't seems to apply the updates - but that's another story.
Cheers,
GM
I was able to update my Nook touch to 1.1 by resizing the partition. Seems that the system needs more space in the ./factory area (I think) to apply an update. The resizing modification specified in the above didn't left enough space.
Thanks.
You should take the time to update your title with [Solved]
ros87 said:
You should take the time to update your title with [Solved]
Click to expand...
Click to collapse
ha! ok. Done
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 mates!
Recently a friend of mine provoked me to root the NST i had for a month or something like. Followed this simple instruction - nookdevs[d]com/Nook_Simple_Touch/Rooting/Manual and messed things up quite badly:
I did backup before running SD with noogie.img which gave me the small .img of around 250mb. Well i thought that this is it and didn't dance while there was time to make backup on noogie step. At the point of restart the reader didn't reboot properly and i thought that writting backup image will bring back the happines. Obviously i was wrong and doing dd if=backup.img of=/dev/sdc wiped /boot and other crucial partitions of the system. So i can't do any tricks with reseting configs.
I've read some threads out here and the situation brings me to conclusion that i have a brick in my hands. But i thought that somehow there might be something else? Any ideas? Any chance to get original files of the system used for NST?
I've already tried Touch-Formatter and it didn't work out - just stuck on rebooting after installing .zip
Yeah more or less this is it.
From the size of 250M I'd guess that you backed up the /media partition.
Writing it back to your nook wiped out your /boot, /rom, and /factory partitions.
You'll have to copy a full image from somewhere.
You'll have to either copy somebody's personal info or fudge it.
Renate NST said:
From the size of 250M I'd guess that you backed up the /media partition.
Writing it back to your nook wiped out your /boot, /rom, and /factory partitions.
You'll have to copy a full image from somewhere.
You'll have to either copy somebody's personal info or fudge it.
Click to expand...
Click to collapse
+1
and see this post
http://forum.xda-developers.com/showpost.php?p=30454593&postcount=24
after everything going ok , try have a right backup (about 1.9GB)
good luck
Thanks mates for all the advices. Eventually 1.9GB image was the perfect solution for my problem:
1.Wrote noogies.img on MicroSD card
2.Plugged in NST with noogie card inside
3.Wrote 1.9GB image to the nook itself (not quite sure if two previous steps are acutally necessary but just to have it )
4.Switched on NST without noogie card.
And got everything working perfectly. As i didn't have any unique data for my NST, i just skipped registration. No problems so far. - to make clear i don't use B&N store as i leave in a really poor country where nobody has proper credit cards to buy anything in internet...)))
And after that rooted my NST in proper way and now everything looks fine!
Cheers!
PS. If somebody needs this 1.9GB for NST - just pm me, i will upload it somewhere and share it with you on condition that you won't register you nook - not to set up the person who shared the image (although i'm quite sure he is also not going to buy any books on B&N)
My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempting to restore a backup (which I didnt know was bad at the time)
Notes
1. I have two backups:
a) the first is 239mb which contains my ebooks and pdfs
b) the second is the boot partition (77mb) - I backed up again when when noogie was on micro SD
2. So basically (both backups) I backed up the NST without selecting the whole physical drive.
3. After a failed root, I tried to restore the backup (and seeing it fail), I decided to wipe the whole partition before attempting to restore again :crying:
4. Are there any restorable backup images that can be downloaded online? Or anything which can restore the partition table including the ROM partition with the serial address etc.
5. Please help me restore the Nook back to factory or any working state. Cos AFAIK i've bricked the device.
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen. N2Tsecurity doesnt work without the ROM partition.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)
Did you really wipe all the partitions (like write zeroes over the entire physical drive)?
Or did you just try to repartition it?
The question is whether you truly wiped out the /rom and /factory partitions.
Sometimes partitioning them correctly you can rediscover the file system.
The /rom partition is necessary, even ClockworkMod needs to be able to see it.
The /rom info is replicated in /factory/rombackup.zip
Renate's solution may work.
Also, there is a tool called testdisk available for linux that I've used to recover data and partition layouts before; I would expect that it may work a champ for situations like yours.
To use it, you would need a linux box or find a windows port and boot the NSTG or NST from the noogie disk.
Testdisk can recover deleted partitions automatically, including the all-important /rom partition.
That one's important because it contains device-specific info for your NST. It'll do it automatically, but you do need to read up on what commands to give it. You can also rebuild the table manually using fdisk (and I've done so successfully before.)
A windows file recovery utility might let you recover /rom as well (or the files from it.)
You most need the contents of /devconf, and there are lots of files there. I am not sure which ones are absolutely required.
My NST Glowlight is getting replaced due to hardware failure.
When I get the new device, could/should I restore my existing backup that I made using NookManager? Or should I just restore the apps (using Titanium Backup, for instance)?
I am hoping I can be lazy and just restore my latest backup image.
Should be the same device, firmware, etc. Just different serial numbers, I assume.
Jonathan
jdbow75 said:
My NST Glowlight is getting replaced due to hardware failure.
When I get the new device, could/should I restore my existing backup that I made using NookManager? Or should I just restore the apps (using Titanium Backup, for instance)?
I am hoping I can be lazy and just restore my latest backup image.
Should be the same device, firmware, etc. Just different serial numbers, I assume.
Jonathan
Click to expand...
Click to collapse
NookManager will restore everything including your ROM partition which has all of your device specific stuff like the serial number and keys for communications with B&N. You don't want to wipe out your new devices ROM partition. The very first thing you should do with your new device is make a backup and save it somewhere safe. Then you can backup your ROM partition from your new Nook before you restore the NookManager backup and then restore the ROM partition after. Probably easiest to do this with ADB - adb shell to mount the partition and ADB pull it over to your PC. Then push it back after restoring the NookManager backup.
straygecko said:
then restore the ROM partition
Click to expand...
Click to collapse
OK, so the only partition I need to retain on the new device is the ROM partition? That makes sense.
This is how I imagine doing this:
Backup the new device using noogie or NookManager
Using dd (I am on Linux), extract the ROM partition to its own separate image
Boot new device using noogie
Use dd to restore the backup I had previously made from the old device
Used dd to put the new ROM partition on the new device, overwriting what I just put there
All should be well, then, yes?
straygecko said:
Probably easiest to do this with ADB - adb shell to mount the partition and ADB pull it over to your PC. Then push it back after restoring the NookManager backup.
Click to expand...
Click to collapse
Ah, now I understand your first suggestion. That may be easiest, and remove some of my steps. Thanks!
jdbow75 said:
OK, so the only partition I need to retain on the new device is the ROM partition? That makes sense.
This is how I imagine doing this:
Backup the new device using noogie or NookManager
Using dd (I am on Linux), extract the ROM partition to its own separate image
Boot new device using noogie
Use dd to restore the backup I had previously made from the old device
Used dd to put the new ROM partition on the new device, overwriting what I just put there
All should be well, then, yes?
Click to expand...
Click to collapse
Yep that's the ticket.
Hmmmm... The plot thickens.
Browsing around the backup, I notice that there are copies of the rom in factory/rombackup.zip and factory/factory.zip/romrestore.zip and boot/romrestore.zip, although rombackup.zip is the only full copy.
Do I need to worry about these, or will they automatically be updated from the new device?
Of course, I could just restore the NOOK, system and userdata partitions, leaving factory, boot, rom, and cache untouched.
Thanks so much for your input.
jdbow75 said:
Hmmmm... The plot thickens.
Browsing around the backup, I notice that there are copies of the rom in factory/rombackup.zip and factory/factory.zip/romrestore.zip and boot/romrestore.zip, although rombackup.zip is the only full copy.
Do I need to worry about these, or will they automatically be updated from the new device?
Of course, I could just restore the NOOK, system and userdata partitions, leaving factory, boot, rom, and cache untouched.
Thanks so much for your input.
Click to expand...
Click to collapse
Glad you're looking around. I never thought about those. They won't be a problem for day-to-day use. Those other copies are used for when you invoke the factory restore function.
The partitions you listed to restore will work except that /boot/uRamdisk is modified to root the Nook so if you don't restore the boot partition you'll lose root. Probably easiest to replace uRamdisk on the new Nook with the one from your current Nook.