take a NSTG back to stock

Search This thread

srgarfi

Senior Member
Jul 30, 2012
79
0
Barcelona
I now have an image copied with DiskImage and a devconf folder with my stuff =)

But
Code:
~ # mkdir /fact
mkdir /fact
~ # mount -t ext2 /dev/block/mmcblk0p3 /fact
mount -t ext2 /dev/block/mmcblk0p3 /fact
mount: mounting /dev/block/mmcblk0p3 on /fact failed: Invalid argument
 

Renate

Recognized Contributor / Inactive Recognized Dev
There's two possibilities there, either the Glow has a bit different partition sizes than the touch
or else the formatting of your factory partition got bashed.

In any case, you are lucky to have backed up all your /rom
You could take someone elses full Glow backup, restore that, then restore your /rom

Check to see if the other partitions are good.
Just mount them with vfat, ext2, ext3, as the case may be.
 

srgarfi

Senior Member
Jul 30, 2012
79
0
Barcelona
Lucky me!
Code:
~ # mount -t vfat /dev/block/mmcblk0p1 /boot
mount -t vfat /dev/block/mmcblk0p1 /boot
mount: mounting /dev/block/mmcblk0p1 on /boot failed: Invalid argument
~ # mount -t ext2 /dev/block/mmcblk0p5 /system
mount -t ext2 /dev/block/mmcblk0p5 /system
mount: mounting /dev/block/mmcblk0p5 on /system failed: Invalid argument
~ # mount -t vfat /dev/block/mmcblk0p6 /media
mount -t vfat /dev/block/mmcblk0p6 /media
mount: mounting /dev/block/mmcblk0p6 on /media failed: No such file or directory

~ # mount -t ext3 /dev/block/mmcblk0p7 /cache
mount -t ext3 /dev/block/mmcblk0p7 /cache
mount: mounting /dev/block/mmcblk0p7 on /cache failed: Invalid argument
~ # mount -t ext3 /dev/block/mmcblk0p8 /data
mount -t ext3 /dev/block/mmcblk0p8 /data
mount: mounting /dev/block/mmcblk0p8 on /data failed: Invalid argument
~ #

Someone willing to share a full backup of his Glow? I promise I'll overwrite /rom with my own data :fingers-crossed:
 

speedman2202

Senior Member
May 16, 2012
358
41
Cairo
If somebody with a Nook Glow would simply do an fdisk -l we could see if the partitioning is right.

i guess he need partitioning info for NSTG , then he can just replace from any full back up or his incomplete backup the boot partition files , factory partition and rom partition ..... then the nook will work "like my case" , and thx to Renate , she helped me in that

just try found an full backup or do what i told u , but if u want to exchange files between ur nook and other backup image , u boot with noogie image for ur nook and burn ur backup on SD card , and try open them by any linux OS and copy files between them


good luck :)
 

speedman2202

Senior Member
May 16, 2012
358
41
Cairo
hey , dont refer to ur nook device that may ur device get deactive by BN , try just here or dont say any info about ur device serial

anyway here many pple can help u , just be patient
 

Renate

Recognized Contributor / Inactive Recognized Dev
If you get bored waiting you can always just format the partitions that aren't mountable.
The vfat and ext2 ones are easy, but the ext3 formatter seems to be missing out of busybox and friends.
If you get all 7 (excluding the extended #4 partition) mountable then you can try restoring from the 1.1.5 factory.zip:
http://xdaforums.com/showpost.php?p=25557213&postcount=10
 

srgarfi

Senior Member
Jul 30, 2012
79
0
Barcelona
I'm leaving on sunday for a 1 week shift, and I intended to take the nook with me. Now that I've realized it wont' happen, I can wait another week and see if someone shares the partition info.
 

speedman2202

Senior Member
May 16, 2012
358
41
Cairo
Back from work, nobody has yet posted the info :crying:

i suggest u that go to glownooter thread and read all posts and then pick some members and send them pm's and ask them send u their NST glowwihite partioning info .... and send them the method also becoz may all is a beginner


that's my idea for now ..... good luck
 

srgarfi

Senior Member
Jul 30, 2012
79
0
Barcelona
i suggest u that go to glownooter thread and read all posts and then pick some members and send them pm's and ask them send u their NST glowwihite partioning info .... and send them the method also becoz may all is a beginner


that's my idea for now ..... good luck

thanks speedman2202, I did as you suggested.
Let's hope someone answers my call...

I also posted on Reddit, B&N forums, Mobileread and a few other places where I saw NSTG actvity, no luck yet :(
 

stilger

Senior Member
Jul 29, 2007
163
43
thanks speedman2202, I did as you suggested.
Let's hope someone answers my call...

I also posted on Reddit, B&N forums, Mobileread and a few other places where I saw NSTG actvity, no luck yet :(

Here ya go... From my NSTG.

# busybox fdisk -l /dev/block/mmcblk0
busybox fdisk -l /dev/block/mmcblk0

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 (LBA)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux
 
  • Like
Reactions: Renate and srgarfi

srgarfi

Senior Member
Jul 30, 2012
79
0
Barcelona
Here ya go... From my NSTG.

Thanks stilger !!

To mee it looks the same as the partition of the NST Renate NST sent....but with a different number of cylinders.
So I modified Renate's sh and tried this on my NSTG, and no it did not boot: Install Failed screen again.



Most probably something went wrong because fdisk -l returns nothing.
 

srgarfi

Senior Member
Jul 30, 2012
79
0
Barcelona
Did it again "old school", I mean typing commands in the adb shell prompt and this is the result:

Code:
D:\nook_root\adbshell>adb shell
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes

              Device Boot      Start         End      Blocks  Id System
/dev/block/mmcblk0p1   *           1          38       77808   c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2              39          46       16384   c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3              47         141      194560  83 Linux
/dev/block/mmcblk0p4             142         926     1607680   5 Extended
/dev/block/mmcblk0p5             142         285      294896  83 Linux
/dev/block/mmcblk0p6             286         405      245744   c Win95 FAT32 (LBA)
/dev/block/mmcblk0p7             406         525      245744  83 Linux
/dev/block/mmcblk0p8             526         926      821232  83 Linux
~ #

But the nook won't boot: install failed.

I'm running out of ideas here....
Perhaps the best option would be to write the full image of a working NSTG and overwrite /rom with my salvaged information?

thanks everyone.
 

Renate

Recognized Contributor / Inactive Recognized Dev
So, what we now know:
The Glow uses the exact same partition sizes as the Touch.
The Glow uses a slightly bigger capacity internal SD card (which make absolutely no difference).

Since you've already tried mounting all the partitions, the answer is that the formatting of those partitions has been bashed.

As before, you have two options:

1) Get a full Glow backup from somebody, install with Noogie, then overwrite the /ram partition with your saved personal config.

2) Correctly format all the partitions that are not mountable and update using the CWR and the factory.zip
 

srgarfi

Senior Member
Jul 30, 2012
79
0
Barcelona
2) Correctly format all the partitions that are not mountable and update using the CWR and the factory.zip

How would I do that?

Ina previous message you said:
Code:
mkdir /fact
mount -t ext2 /dev/block/mmcblk0p3 /fact
adb pull /fact/factory.zip
adb pull /fact/rombackup.zip
then it would be as easy as applying factory.zip from CWR.
Bu tI don't know how to correctly format /dev/block/mmcblk0p3
 

Renate

Recognized Contributor / Inactive Recognized Dev
Either mmcblk0p3 is ok, in which case you can pull the stuff off it
or else it is bashed and you can format it to clean things up.

Somebody posted factory.zip here:
http://xdaforums.com/showpost.php?p=25557213&postcount=10

Only format partitions that are broken and can't be mounted.
Code:
mkfs.vfat -n boot /dev/block/mmcblk1p1
mkfs.vfat -n rom /dev/block/mmcblk1p2
mkfs.ext2 -L factory /dev/block/mmcblk1p3
mkfs.ext2 -L system /dev/block/mmcblk1p5
mkfs.vfat -n media /dev/block/mmcblk1p6

Partitions mmcblk1p6 & mmcblk1p7 are ext3 types.
I haven't found a good way to format them.
Partition Wizard can format ext3 but it will bash your partition tables.
You can try that then redo the partitioning afterwards.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    thanks speedman2202, I did as you suggested.
    Let's hope someone answers my call...

    I also posted on Reddit, B&N forums, Mobileread and a few other places where I saw NSTG actvity, no luck yet :(

    Here ya go... From my NSTG.

    # busybox fdisk -l /dev/block/mmcblk0
    busybox fdisk -l /dev/block/mmcblk0

    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 (LBA)
    /dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LBA)
    /dev/block/mmcblk0p3 47 141 194560 83 Linux
    /dev/block/mmcblk0p4 142 926 1607680 5 Extended
    /dev/block/mmcblk0p5 142 285 294896 83 Linux
    /dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LBA)
    /dev/block/mmcblk0p7 406 525 245744 83 Linux
    /dev/block/mmcblk0p8 526 926 821232 83 Linux
    2
    BootCnt is a 4 byte little-endian count of the number of boots.
    To make a value >= 0x00000008 is not difficult.
    Since echo normally terminates with a NL (0x0a) just send 3 chars of any kind.
    Code:
    echo 000 > /rom/devconf/BootCnt
    reboot
    (The shell also takes the reboot command.)
    1
    There are drivers and drivers.
    As a composite USB device the Nook uses both the stock Windows Mass Storage driver and the Google ADB driver.

    See: http://xdaforums.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
    1
    If somebody with a Nook Glow would simply do an fdisk -l we could see if the partitioning is right.
    1
    Well, you've got beyond this point, but if somebody wants to check their partitions,
    then they can put the attached zip on the SD card and run it as an update on CWR.
    It will either fail on an assert or tell you that all partitions are mountable.

    You format a single partition, you can't format "the whole thing".

    You can access the whole internal SD card through noogie and use
    Linux or Windows tools to format the individual partitions.