Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,786,645 Members 38,857 Now Online
XDA Developers Android and Mobile Development Forum

take a NSTG back to stock

Tip us?
 
srgarfi
Old
#1  
srgarfi's Avatar
Member - OP
Thanks Meter 0
Posts: 79
Join Date: Jul 2012
Location: Barcelona
Default take a NSTG back to stock

Hi,

I succesfullly rooted my Nook glowlight, but when I tried to go back to stock with my nook backup I found the backup was not ok (just 77MB) and now I have a bricked NSTG that won't get past the "Install Failed" screen.
I've tried almost every method I could find in the forums, but none worked for me.

Is there anything else beside n2T and Alpha-Format I could try to revive my device?

TIA
 
Renate NST
Old
#2  
Renate NST's Avatar
Recognized Contributor / Recognized Developer
Thanks Meter 796
Posts: 1,973
Join Date: Feb 2012
Location: Boston
I think the most careful way to proceed here is to get a shell going and inspect the damage.
If you were lucky you just wiped out the first partition and the partition tables.
Reinstating the partition tables might make undamaged partitions visible.
It's important to preserve the device dependent info on the /rom partition.

If you copy over ClockworkRecovery onto an SD card you should be able to boot that.
Without selecting anything on the menus you should be able to get ADB working.
With an ADB shell you can run fdisk -l /dev/block/mmcblk0
As soon as you can get access to /rom I'd suggest that you back that up.

I'm sure somebody has other ways to get shell access.

 
srgarfi
Old
(Last edited by srgarfi; 31st July 2012 at 10:02 AM.) Reason: status update
#3  
srgarfi's Avatar
Member - OP
Thanks Meter 0
Posts: 79
Join Date: Jul 2012
Location: Barcelona
Quote:
Originally Posted by Renate NST View Post
I think the most careful way to proceed here is to get a shell going and inspect the damage.
If you were lucky you just wiped out the first partition and the partition tables.
Reinstating the partition tables might make undamaged partitions visible.
It's important to preserve the device dependent info on the /rom partition.

If you copy over ClockworkRecovery onto an SD card you should be able to boot that.
Without selecting anything on the menus you should be able to get ADB working.
With an ADB shell you can run fdisk -l /dev/block/mmcblk0
As soon as you can get access to /rom I'd suggest that you back that up.

I'm sure somebody has other ways to get shell access.
thanks for that I'll give it a try...

Sadly, I'm on a W7 box (not mine) and all I can see in the device manager is a nook with a yellow sign in it
ADB devices returns a blank list....
I tried updating the drivers for the nook: first uninstalled anything nooklike with usbdeview, and then pointed W7 to a folder where I had downloaded usbdrivers from this thread http://forum.xda-developers.com/show....php?t=1354487 but W7 keeps telling there are no drivers for nook in that folder.
If I boot without SD then the nook is recognized and USB drivers install fine. It's booting with CWM that the device is not recognized.

Stuck
 
Renate NST
Old
#4  
Renate NST's Avatar
Recognized Contributor / Recognized Developer
Thanks Meter 796
Posts: 1,973
Join Date: Feb 2012
Location: Boston
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://forum.xda-developers.com/wiki...Installing_ADB

The Following User Says Thank You to Renate NST For This Useful Post: [ Click to Expand ]
 
srgarfi
Old
(Last edited by srgarfi; 31st July 2012 at 03:22 PM.) Reason: info upd
#5  
srgarfi's Avatar
Member - OP
Thanks Meter 0
Posts: 79
Join Date: Jul 2012
Location: Barcelona
Quote:
Originally Posted by Renate NST View Post
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://forum.xda-developers.com/wiki...Installing_ADB
It worked:

D:\nook_root\adbshell>adb devices
List of devices attached
11223344556677 recovery


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

Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
4 heads, 16 sectors/track, 59776 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Device Boot Start End Blocks Id System
~ #

completely noob with the nook, can't seem to find /rom and Win32DiskImager does not find a device to read from to perform said backup
 
Renate NST
Old
#6  
Renate NST's Avatar
Recognized Contributor / Recognized Developer
Thanks Meter 796
Posts: 1,973
Join Date: Feb 2012
Location: Boston
The best bet would be to check with somebody with a Glow to see if the partitioning is the same as the Touch.
They could have even changed the exact size of partitions over time for the same model.
In any case, here are my partitions. You might try partitioning and not formatting and see if all the pieces fit properly.
Code:
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes

Partition  Format  Id  Start  End   Size (bytes)  Mount
---------  ------  --  -----  ---  -------------  --------
Total                     0   933  1,958,739,968
mmcblk0p1   vfat   0c     1    38     79,691,776  /boot
mmcblk0p2   vfat   0c    39    46     16,777,216  /rom
mmcblk0p3   ext2   83    47   141    199,229,440  /factory
mmcblk0p4          05   142   926  1,646,264,320
mmcblk0p5   ext2   83   142   285    301,989,888  /system
mmcblk0p6   vfat   0c   286   405    251,658,240  /media
mmcblk0p7   ext3   83   406   525    251,658,240  /cache
mmcblk0p8   ext3   83   526   926    840,957,952  /data
Unused                  927   933     14,680,064

 
srgarfi
Old
#7  
srgarfi's Avatar
Member - OP
Thanks Meter 0
Posts: 79
Join Date: Jul 2012
Location: Barcelona
Quote:
Originally Posted by Renate NST View Post
The best bet would be to check with somebody with a Glow to see if the partitioning is the same as the Touch.
They could have even changed the exact size of partitions over time for the same model.
In any case, here are my partitions. You might try partitioning and not formatting and see if all the pieces fit properly.
Code:
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes

Partition  Format  Id  Start  End   Size (bytes)  Mount
---------  ------  --  -----  ---  -------------  --------
Total                     0   933  1,958,739,968
mmcblk0p1   vfat   0c     1    38     79,691,776  /boot
mmcblk0p2   vfat   0c    39    46     16,777,216  /rom
mmcblk0p3   ext2   83    47   141    199,229,440  /factory
mmcblk0p4          05   142   926  1,646,264,320
mmcblk0p5   ext2   83   142   285    301,989,888  /system
mmcblk0p6   vfat   0c   286   405    251,658,240  /media
mmcblk0p7   ext3   83   406   525    251,658,240  /cache
mmcblk0p8   ext3   83   526   926    840,957,952  /data
Unused                  927   933     14,680,064
mmmm, a bit risky isn't it ?
I think I'll read the rest of the internets before proceeding I need to understand this.....

thanks again
 
Renate NST
Old
#8  
Renate NST's Avatar
Recognized Contributor / Recognized Developer
Thanks Meter 796
Posts: 1,973
Join Date: Feb 2012
Location: Boston
Quote:
Originally Posted by srgarfi View Post
mmmm, a bit risky isn't it ?
Well, you don't have anything at all in your partition table, not even the correct CHS.
If you tried this configuration and you can't mount the partition, then no harm is done.
It will only mount if the partition formatting makes sense.

 
srgarfi
Old
(Last edited by srgarfi; 31st July 2012 at 08:28 PM.) Reason: add link
#9  
srgarfi's Avatar
Member - OP
Thanks Meter 0
Posts: 79
Join Date: Jul 2012
Location: Barcelona
Quote:
Originally Posted by Renate NST View Post
If you tried this configuration and you can't mount the partition, then no harm is done.
It will only mount if the partition formatting makes sense.
Oh, ah, that changes everything! It's worth a try.
I need to find a dummy guide to perform this operations, any clues?

Edit: Found this, looks like a start http://forum.xda-developers.com/show....php?t=1279091

thanks again
 
srgarfi
Old
(Last edited by srgarfi; 31st July 2012 at 10:10 PM.) Reason: spelling
#10  
srgarfi's Avatar
Member - OP
Thanks Meter 0
Posts: 79
Join Date: Jul 2012
Location: Barcelona
booted in gparted live and took a peek at the Nook. This is what I found (sorry I don't know yet how to post images):

Device information
Model: B&N Ebook Disk
Size: 182 GiB
Path: /dev/sdb

Partition table: msdos
Heads: 255
Sectors/track: 63
Cylinders: 238
Total sectors: 3825664
Sector size: 512

Physical characteristics being so different I'm affraid trying to convert heads/cylinders from Renate's Touch to my Glo schema would be useless.

Could someone with a NSTG please share partition information?

Thank you all,

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes