Related
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
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.
I'm a bit confused on backing up my NST after I've rooted. I rooted with TouchNooter...do I still follow the same process of booting from a SD Card with noogie.img and then reading and image or is there a different process I should use now that I'm already rooted?
A full backup (around 2GB) with noogie is the safest bet.
You can also adb pull the /rom directory for safekeeping.
You can also mount the /factory partition and adb pull rombackup.zip
Renate NST said:
A full backup (around 2GB) with noogie is the safest bet.
You can also adb pull the /rom directory for safekeeping.
You can also mount the /factory partition and adb pull rombackup.zip
Click to expand...
Click to collapse
Thanks! I'm following the instructions at:
http://nookdevs.com/Nook_Simple_Touch/Rooting/Manual
Section: "After you have written the SDCard"
#7 says I should see all 7 partitions after the NST completes the boot.
I am only seeing the boot partition (I'm using Win7 if that matters).
My NST has Rooted Forever showing on the screen. I also waited several minutes and tried several times.
Do I go ahead and image the NST or do I need to do something different so that the NST shows all 7 partitions?
Thanks
EDIT: Found the solution at:
http://forum.xda-developers.com/showthread.php?t=1759700
post#6
NST Backup only 1916928 kb
Imaged my rooted nook with both Win32DiskImager and RoadKill (and I was sure to select the physical drive). Both .img files show the same size of 1,916,928 kb. Shouldn't these be larger? If so, what am I doing wrong? Thanks.
1,916,928 kB * 1024 B/kB = 1,962,934,272 B
The allocated part of the Nook's physical is 1,958,739,968 B
So, it's big enough.
I made a big and foolish mistake and wrote noogie.img directly to the NOOK2 istead of SD card. So evereytime I boot the nook2, the screen shows 'rooted forever' even I remove the SD card. Because the windows doesn't recognize the nook2 in the usb mode, I cannot use roadkil's diskimage to write my bakcup image.
Maybe I'll buy a new one for my fault.:crying:
Did you ever backup your /rom partition?
If you only wrote Noogie (~79 Megs) you may be alright.
That would trash the partition tables and the /boot partition but /rom, /factory and all the rest of the partitions should be ok.
Since it's booting ok with noogie right now, the thing to do is to do a full backup.
That way you can save the chance of recovering the /rom or /factory partition.
Renate NST said:
Did you ever backup your /rom partition?
If you only wrote Noogie (~79 Megs) you may be alright.
That would trash the partition tables and the /boot partition but /rom, /factory and all the rest of the partitions should be ok.
Since it's booting ok with noogie right now, the thing to do is to do a full backup.
That way you can save the chance of recovering the /rom or /factory partition.
Click to expand...
Click to collapse
Yes, I messed up the Noogie (~79 Megs) stuff as you said.
I used to restore my nook system using a file 'NOOK ROOT ROM v2.4.img'(1.82Gb). Could you instruct me how to unbrick it safely? Thanks alot.:good:
You're not very clear.
Did this 'NOOK ROOT ROM v2.4.img' get saved directly from your Nook?
Nooks have unit-specific data on them, including serial number, MAC address and various security keys.
If you just clone somebody's info over you may cause problems for them or you.
That's why I asked if you had backed up your /rom partition. Did you?
So far, you might not have destroyed things too badly.
If you copy a ~1.9GB image that you got from somewhere else, then you will have lost forever the unit-specific data.
That's why I asked you to use noogie to copy what is left of the internal memory on your Nook to a safe place on your PC.
http://reviewhorizon.com/2011/07/how-to-restore-nook-touch-n2e-to-its-default-factory-state/
cached:
http://webcache.googleusercontent.c...y-state/&client=firefox-a&hl=en&gl=uk&strip=1
http://forum.xda-developers.com/showthread.php?t=2608815
http://forum.xda-developers.com/showthread.php?p=53545426
http://forum.xda-developers.com/showthread.php?t=1475613
http://forum.xda-developers.com/sitesearch.php?q=factory reset nook touch
Renate NST said:
You're not very clear.
Did this 'NOOK ROOT ROM v2.4.img' get saved directly from your Nook?
Click to expand...
Click to collapse
Yes, I've backup my system as soon as I got my nook. It's a 1.86Gb img file.
wozhere said:
http://reviewhorizon.com/2011/07/how-to-restore-nook-touch-n2e-to-its-default-factory-state/
http://forum.xda-developers.com/showthread.php?t=2608815
http://forum.xda-developers.com/showthread.php?t=1475613
http://forum.xda-developers.com/sitesearch.php?q=factory reset nook touch
Click to expand...
Click to collapse
I'll do some research on your links. Thanks dude.
With the CWM and Touch-Formatter v2, I've done the following steps --- "Copy the zip onto the root directory of the sdcard you burned the CWM.(Don't extract them)
Insert the sdcard on your nook, and boot it.
On CWM select install zip from sdcard
Then select choose zip from sdcard
Select Alpha-FormatTouch-2.zip, click yes and wait till the process finishes.
Go back, eject the sd card, and click reboot.
But after reboot, the nook is stuck in 'Read Forever' sopt.
I have my original img file, but I don't know how to restore the image using DiskImage because there's something wrong with USB(maybe nook's system is messed up) and I CAN'T find the 1.82 drive.
leewaye said:
With the CWM and Touch-Formatter v2, I've done the following steps --- "Copy the zip onto the root directory of the sdcard you burned the CWM.(Don't extract them)
Insert the sdcard on your nook, and boot it.
On CWM select install zip from sdcard
Then select choose zip from sdcard
Select Alpha-FormatTouch-2.zip, click yes and wait till the process finishes.
Go back, eject the sd card, and click reboot.
But after reboot, the nook is stuck in 'Read Forever' sopt.
I have my original img file, but I don't know how to restore the image using DiskImage because there's something wrong with USB(maybe nook's system is messed up) and I CAN'T find the 1.82 drive.
Click to expand...
Click to collapse
the back up u got if it was before write noogie image to ur nook directory .. so u saved ur nook ..... i will repeat ... if u got back up from ur nook directly with (1.8 GB size almost) before u write noogie image on ur nook ... so u ok!!!
from that point follow my instructions to recover ur nook:
1- get sd card and write noogie image to it ( dont mess ur hard disk drive ... i do it once and i got recover all my HDD files )
2- insert the sd card that on nook and power on ur nook and rooted for ever logo will show as soon as u do ( if ur nook doesnt power on so far then plug ur nook in charger cuz need to charging)
3- connect ur nook to ur pc and will show as a SD card
4- download this program "Roadkil's disk image" (go google search and download)
5- install/open the program and u will see all partitions and all disks on ur pc ... let say u only connected 1 HDD with capacity 500GB then u will find that Disk 0 (500 GB) and Disk 1 (1.89 GB) and Disk 2 (removable) , then choose that disk "Disk 1 (1.89 GB) " and make sure disk size 1.89 GB
6- choose the image directory from ur pc and then Hit start
7-and after it finish ..... do safely remove and unplug the SD card from ur nook and power on ur nook and it should be working fine
but before do anything .... how u do backup for u nook and got this file .... if u read recovery/restory ur nook and read and know how u do recovery then proceed the steps i said to u .... but plz if there more details u want tell us , go a head before do anything
thx
I've saved my nook.I wish to express my gratitude to speedman2202,wozhere and Renate NST for your immense practical help.:laugh:
To conclude the experience that I learn from unbricking my nook touch, there're 2 issues to mention:
1.In my first step,Nook can be formated to restore factory system With the CWM and Touch-Formatter v2.http://forum.xda-developers.com/showthread.php?t=1475613
2.In my case,after reboot, the nook is stuck in 'Read Forever' sopt and windows cannot recognize Nook USB drive.Do the following steps as speedman2202 directs
speedman2202 said:
the back up u got if it was before write noogie image to ur nook directory .. so u saved ur nook ..... i will repeat ... if u got back up from ur nook directly with (1.8 GB size almost) before u write noogie image on ur nook ... so u ok!!!
from that point follow my instructions to recover ur nook:
1- get sd card and write noogie image to it ( dont mess ur hard disk drive ... i do it once and i got recover all my HDD files )
2- insert the sd card that on nook and power on ur nook and rooted for ever logo will show as soon as u do ( if ur nook doesnt power on so far then plug ur nook in charger cuz need to charging)
3- connect ur nook to ur pc and will show as a SD card
4- download this program "Roadkil's disk image" (go google search and download)
5- install/open the program and u will see all partitions and all disks on ur pc ... let say u only connected 1 HDD with capacity 500GB then u will find that Disk 0 (500 GB) and Disk 1 (1.89 GB) and Disk 2 (removable) , then choose that disk "Disk 1 (1.89 GB) " and make sure disk size 1.89 GB
6- choose the image directory from ur pc and then Hit start
7-and after it finish ..... do safely remove and unplug the SD card from ur nook and power on ur nook and it should be working fine
Click to expand...
Click to collapse
Everything shall be retored and the Sun will rise tomorrow again
another important thing to mention is that u can resore system with every correct IMG file as long as the model match. i actually write my system with a img file i download from another guy's img. Now my system is a android version in which i can install some apps.
Thanks guys again. Have a nice day!!:good:
leewaye said:
I've saved my nook.I wish to express my gratitude to speedman2202,wozhere and Renate NST for your immense practical help.:laugh:
To conclude the experience that I learn from unbricking my nook touch, there're 2 issues to mention:
1.In my first step,Nook can be formated to restore factory system With the CWM and Touch-Formatter v2.http://forum.xda-developers.com/showthread.php?t=1475613
2.In my case,after reboot, the nook is stuck in 'Read Forever' sopt and windows cannot recognize Nook USB drive.Do the following steps as speedman2202 directs
Everything shall be retored and the Sun will rise tomorrow again
another important thing to mention is that u can resore system with every correct IMG file as long as the model match. i actually write my system with a img file i download from another guy's img. Now my system is a android version in which i can install some apps.
Thanks guys again. Have a nice day!!:good:
Click to expand...
Click to collapse
did u download nook image from website and write it to ur own nook??!!!
i hope not!!!! :\ , if u do ... ur wifi wont work .... just u can use ur nook as a e-reader only and no benefits to root :|
speedman2202 said:
did u download nook image from website and write it to ur own nook??!!!
i hope not!!!! :\ , if u do ... ur wifi wont work .... just u can use ur nook as a e-reader only and no benefits to root :|
Click to expand...
Click to collapse
My wifi still works well except that my nook shop account is a issue. But I think I can solve it with my own .pmf file to restore my account info.
I finished a utility for recovering files out of a saved Nook backup.
It should be able to recover the /rom partition even if you overwrote the first 79 Megs.
Is anybody interested in trying this?
leewaye said:
My wifi still works well except that my nook shop account is a issue. But I think I can solve it with my own .pmf file to restore my account info.
Click to expand...
Click to collapse
if the image u downloaded and burn it to ur nook contain rom partition of the image publisher ... then when u try his image u now own another device details ( another serial number , Mac address and other changed details) .... so i think when u burn/write the image to ur nook ... it was successfully registered and no need to register again ......anyway the main issue that u have the same Mac address from other device and that may do conflict with u and for sure ..... try get ur own Unique nook device Rom files By Renate utility and thx to her she still keep on developing such these things
thats why i said " i hope not do that" cuz there is another ways for recover deleted/formatted partition
thx
UPDATE: try and check this utility by Renate .... it will help u
http://forum.xda-developers.com/showthread.php?t=2643687
Renate NST said:
I finished a utility for recovering files out of a saved Nook backup.
It should be able to recover the /rom partition even if you overwrote the first 79 Megs.
Is anybody interested in trying this?
Click to expand...
Click to collapse
ummm .... try publish beta test ... and lets see other user says about ur new utility ....and when it success .... publish a full thread about recover ur nook with/with out backup image
thx to Renate
best regards ^^
wozhere said:
http://reviewhorizon.com/2011/07/how-to-restore-nook-touch-n2e-to-its-default-factory-state/
cached:
http://webcache.googleusercontent.c...y-state/&client=firefox-a&hl=en&gl=uk&strip=1
http://forum.xda-developers.com/showthread.php?t=2608815
http://forum.xda-developers.com/showthread.php?t=1475613
http://forum.xda-developers.com/sitesearch.php?q=factory reset nook touch
Click to expand...
Click to collapse
I tried all this methods but they are dont work for me. I havent got a working backup. I can create backups now, manage the particions etc... I think i need a backup file and i need to overwrite the root particion with my own stuff. :S Is this possible?
Backup now what you do have.
Try to extract the /rom partition files using this: http://forum.xda-developers.com/showthread.php?p=53347856
The Issue
Hi, I have a Nook Simple Touch that gets stuck trying to boot. First I see the Barnes and Noble Screen, Next for a brief moment it tries to load a Rom and shows a small nook icon with a loading bar. Next it says "Install Failed". I am unable to do anything other than a factory reset, which doesn't help.
Background
I should add that the device previously was working fine, then one day it froze as I was highlighting some text. When I tried to boot it, it was stuck in the scenario described above. I believe it was already updated to 1.2.2 with seemingly no issues.
What I've tried:
I have tried restoring it back with noogie and a backup, and I have also tried the Nook Manager- Rescue from .zip and Rescue from backup to no avail. Still get that same blasted "Rom Restore Image" Screen followed by "Install Failed".
I have an update from Barnes and Noble called "nook_1_2_update.zip" which I tried to copy over to the nook but the file is too large.
Any ideas? I love this thing and don't want to let it go!:crying::good:
I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?
Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Trigrammaton said:
... I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
Im not quite sure. Another version, etc...
You can use NST boot partition image from this post
For preparing another booting SD card too...
Trigrammaton said:
Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
If you restore the image from a different device the serial number, MAC address, etc. will be messed up. You will never be able to register the device. This may not be an issue, but just so you are aware.
nmyshkin said:
If you restore the image from a different device the serial number, MAC address, etc. will be messed up.
Click to expand...
Click to collapse
The serial number is written inside the little door for the SD card (if you haven't worn it off).
The serial number and the MAC are also on a sticker in the inside.
ucy74 said:
I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?
Click to expand...
Click to collapse
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen. What do you mean by "new" sd? If i put a blank sd into the slot and boot?
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!
Trigrammaton said:
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen.
Click to expand...
Click to collapse
Super, it means so You can connect to Your Nook and dump boot partition files to PC using ADB.
What do you mean by "new" sd? If i put a blank sd into the slot and boot?
Click to expand...
Click to collapse
You can copy files dumped above onto vfat formated SD card. Then try to boot from this "new" - freshly prepared card. Check whats happen.
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Click to expand...
Click to collapse
NOT SO FAST!!! Do not put linked partinion into nook! There are different cases and commands to do that. If You are new to ADB lets try to dump boot partition first, as mentioned before. Maybe there will be not necessary to replace whole partition rather than single file.
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!
Click to expand...
Click to collapse
Prepare this dumped SD first. We try to heal it to make bootable...
Thanks! I will give it a whirl this weekend and report back. Really appreciate you taking time to respond - Very kind of you!