[Q] Factory restore - Nook Touch General

I need a .img of the original rom, where can i find? Thanks

Aran83 said:
I need a .img of the original rom, where can i find? Thanks
Click to expand...
Click to collapse
You cant, every NST is unique and using an image from another NST will cause trouble for both you and the NST it came from.

Thanks, nook is bricked but I can read the main partition, which .img I install?
Sorry for my english.

Aran83 said:
Thanks, nook is bricked but I can read the main partition, which .img I install?
Sorry for my english.
Click to expand...
Click to collapse
There's no img you can install.
You can try booting n2T-Recovery (v0.2) from a SD card and see if that helps. (Do not write that image to your NST!)
If not, send me a PM and I'll try to help you out

Something else you can try:
1) Flash noogie.img to an sd card.
2) Hook up your nook to a pc via usb once it has booted, and you should see all the partitions exported there.
3) In one of those partitions (recovery maybe? I'm struggling to remember), there's a factory.zip, which you can then install using the "Install from zip" feature of clockwork mod.
If you go this route, you'll have to reflash your sd card with clockwork mod after you've extracted the factory.zip using noogie.
Seems like kind of a pain, but I just recovered my device using this.

Remains in the screen ROOTED FOREVER and i can't do anything

I think, for michaelwill's method, you need to have linux running. I suggest you to try ros87's suggestion.

if I use backup from nook of my friend?

Aran83 said:
if I use backup from nook of my friend?
Click to expand...
Click to collapse
That is not a good idea, since each NookTouch has a unique information to register. If you are thinking of full restore from your friend's image (1.8GB image), it will overwrite your unique information. In that case, you and your friend's devices cannot register to BnN (or just one device). People says the info is stored in /rom. If you want to know more, you need to dig more. Otherwise try factory reset suggested by ros.

herofmm said:
That is not a good idea, since each NookTouch has a unique information to register. If you are thinking of full restore from your friend's image (1.8GB image), it will overwrite your unique information. In that case, you and your friend's devices cannot register to BnN (or just one device). People says the info is stored in /rom. If you want to know more, you need to dig more. Otherwise try factory reset suggested by ros.
Click to expand...
Click to collapse
Correct!
Using a image from another NST is a very very bad idea!
There are a lot of stuff that's unique to your NST stored in /rom and in rombackup.zip on the Factory partition.
This includes:
Serial Number
Main Board Serial
Product ID
Manufacturing date
SHA hash of Private Key
Public Key in modulus form
WiFi Calibration file
Some unique binary file for your eInk screen
MAC Address
Battery Type
Duplicating the serial will make you or your friend unable to register with B&N
Duplicating / Faking the private/public key pair, will most likely make you unable to register with B&N (I'm currently testing this)
Duplicating a WiFi calibration can cause degraded WiFi performance
Duplicating that EPD vcom file (eInk screen).. well who knows
Duplicating the MAC will cause network troubles if used on the same network.
The wrong Battery Type (I've seen three different so far) can cause charging troubles, and will cause incorrect charge indication.
Don't go there!

NookRestore.img
Try writing NookRestore.img to an mSD card. (You can get a copy at my website: NootRoot)

Hard reset
I had issues rooting my NST and got stuck in a boot loop. After digging and digging through forums I finally discovered the secret to a hard reset. The instructions said to hold the power and the two bottom side buttons down together for over 20 seconds. That worked! My NST was back to when I pulled it out of the box. I then proceeded to re rooting. (my mistake was I did not upgrade the OS before rooting). My bad. Hope this helps someone recover from a stuck boot loop.
Good luck.

chucktate said:
My NST was back to when I pulled it out of the box.
Click to expand...
Click to collapse
No it wasn't, Factory Reset doesn't remove root files or system apps installed by root tools, it only clears custom apps and settings.
While you might think it's back to stock, there are still leftover files and changes in /boot and /system

ros87 said:
Correct!
Using a image from another NST is a very very bad idea!
There are a lot of stuff that's unique to your NST stored in /rom and in rombackup.zip on the Factory partition.
Click to expand...
Click to collapse
Hi, I've just found a way around this - it is possible to restore somebody else's .img file, provided you've backup up your rombackup.zip. Then after, using Noogie, you can overwrite rombackup.zip and the contents of it which are on a different partition. The only danger is that you would potentially overwrite battery type config file, as Nook has couple of them. I gave it a try on mine and it seems fine.

sokoow said:
Hi, I've just found a way around this - it is possible to restore somebody else's .img file, provided you've backup up your rombackup.zip. Then after, using Noogie, you can overwrite rombackup.zip and the contents of it which are on a different partition. The only danger is that you would potentially overwrite battery type config file, as Nook has couple of them. I gave it a try on mine and it seems fine.
Click to expand...
Click to collapse
That is correct.
Problem is that most people who end up in a state where Factory Restore doesn't work has usually managed to overwrite their partition tables and part of the /rom partition.
And at this point it is too late to backup rombackup.zip as it's usually fragmented and cannot be recovered by ext2 file recovery tools.
So.. do a full backup before you do anything to your NST

I found if you restore with holding the two lower buttons it will remove all rooted files.

Googie2149 said:
I found if you restore with holding the two lower buttons it will remove all rooted files.
Click to expand...
Click to collapse
Read post 13 by ros87!
ros87 said:
No it wasn't, Factory Reset doesn't remove root files or system apps installed by root tools, it only clears custom apps and settings.
While you might think it's back to stock, there are still leftover files and changes in /boot and /system
Click to expand...
Click to collapse
Go to my website, download nookRestore.img and write it to an mSD card, Erase and De register, Power Off, then insert mSD then power up, then follow on screen instructions!

[OT - Removed]

[OT - Removed]

Torimu.Joji said:
I'll update the website and post links to XDA.
Click to expand...
Click to collapse
Thank you sir!
By posting proper links you help ensure that people get the most recent software and information

Related

[Problems & Questions] With Official 2.3 Update V2

Hello !
I am feeling really down today after been trying to get my phone working again.
There is a huge problem currently, I am really annoyed that it doesn't work at all.
First thing, my phone won't start after update it just boot loops and never seem to end it.
First thing I noticed /boot, /cache /system and most things are gone, I can load up recovery but nothing more. I have no idea what happened but the whole image folder was wiped and I had to myself put in the CWM recovery.
I can't do an upgrade "again" as it will be stuck @ the unpacking part without starting it at all.
I been trying with 2.3 V2 and with B133(My stock rom I got).
If anyone has a solution that can solve this problem please help out if you could. Also if you are about to tell me get this and that, please most cases I haven't seen any of the Firmware roms in @modaco wiki links work. Means I can't download them, so if you happen to have spare copy please upload it and link it to me. I have been googling and looking through this section twice, nothing really worked out.
Thanks in advance !
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
dancer_69 said:
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
Click to expand...
Click to collapse
Hello, thanks for the reply.
I have no idea about this .cust_backup partition and how I am supposedly to access it via windows. Also the thing you said about fixing partition within Windows, the check disk thing. I am not sure about that part either as I can load CWM and it can read the partitions but they are empty. Also there is nothing in this forums that contains original things, only way for me to fix this if someone have extra copy and can guide me on how and where to place the all needed files. I am pretty sure it's only things that are missing and I can't get a grip out of this.
So to sum up what my problem is.
I did an upgrade from 2.2 to 2.3 with official firmware, it worked out normally but after a reboot my phone became stuck in an endless loop, I can't do anything and it will not I repeat it will not allow me to "re flash" any firmware I tried so far, the 2.3 V2 and B133.
I am begging someone in this forum section, please if you have the knowledge about this problem care to help?
I can't get a refund out the phone warrenty is off and I do not have that much spare money.
Thanks in advance !
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Blefish said:
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Click to expand...
Click to collapse
The most common things I have already done, but do enlighten me what this "custom" parition is. Because in windows I do not see such partition I see a removable partition which I have now added a folder called image with these containing files.
http://forum.xda-developers.com/showthread.php?t=1370960
EDIT ** Also regarding to first person who said about Windows partition manager. The thing is I see a lot of partitions and there is no labeling for them, might be because they are ext2/3 or even something else? In anycase I can't do so much I just find it really odd I have many duplicates and I am guessing that must be errors... Because I am seeing the main recovery partition which has no label too... its at 240 MB where 135MB is used. Lastly there is my internal SD card empty and healthy still I can't reach it within Windows if I do not mount it...And can't now without going into the android OS. I Have loads of free space "partitions I don't understand why they are there".
**
Thanks for helping out, it feels not good to have a half dead phone, it's still not solved :'-(
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
dancer_69 said:
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
Click to expand...
Click to collapse
I have placed all things that I got from here.
http://forum.xda-developers.com/showthread.php?t=1370960
And I can't run the upgrade firmware, it gets stuck at first stage which is to unpack the the update.app thing.
It just stays like that not blinking and frozen.
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
dancer_69 said:
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
Click to expand...
Click to collapse
You are not understanding me :-(, I have wiped already millions of times in millions of different ways just to get it work. And no, I don't have the device connrected when I upgrade, it won't work properly then, I have tried to wait for the progress bar to "start" move it won't happen the battery will die, and nothing happened.
I can't go in with normal Recovery mode, can only go in with CWM, the normal recovery mode is really small, I mean only 3mb, while the froyo version is 5mb. Now I am asking if you have the time to upload the image files from 2.3 V2, the ones in forums are for V1. Which I don't know might conflict.
Thanks again for trying to help me out, this is really frustrating to get it to work.
**EDIT**
I worked it out !
I think I understood what you meant, I did as you told I started first with pluggin in the charger forced it to upgrade and now it's upgrading, thank you so much dancer_69. I was going to go tomorrow to buy a new 2nd hand smartphone. But now I can save my money for other things !
**EDIT of EDIT **
I seem to have downgraded to B133, I will try now with B158 2.3 V2 again and hopefully it will work now.
Yes, wasn't clear because I don' t remember what I've done and solve it. But I think that I did it like you discribed too.
Anyway I'm glad that was helpful(kind of)..
And don' t give up so soon with smartphone' s bricks, I've faced brick kind of problems many times and if the device it' s not completely dead, there is something you can do. Maybe need more search or many tries(sometimes the same things) but at the end(and of course If there isn't a hardware problem) device can unbrick.

failed rooting, glowlight not working. HELP!

Guys, I had quite bad experience rooting my glowlight nook with touchnooter . Basically messed smth up so it couldn't start (just kept flashing). didn't save my back up. had to do unrooting with the software 1.1 that I guess was from nook without glowlight. Unrooting went fine, but the glowlight function is not working anymore. does anyone know how to solve this or could give me a link to download the proper software? thanks!
dukenookem said:
Guys, I had quite bad experience rooting my glowlight nook with touchnooter . Basically messed smth up so it couldn't start (just kept flashing). didn't save my back up. had to do unrooting with the software 1.1 that I guess was from nook without glowlight. Unrooting went fine, but the glowlight function is not working anymore. does anyone know how to solve this or could give me a link to download the proper software? thanks!
Click to expand...
Click to collapse
you should read the instructions better next time...
but making errors is human and you have a cool nick
I'll hopefully receive my glow in two weeks and I'll upload my backup then
You should make an effort to salvage your personalized data in /rom.
There is all the info in the p2 partition (/rom).
There is also a backup copy in the p3 partition (/factory) as rombackup.zip
You might do this with noogie or CWR and ADB.
Zorkman said:
you should read the instructions better next time...
but making errors is human and you have a cool nick
I'll hopefully receive my glow in two weeks and I'll upload my backup then
Click to expand...
Click to collapse
I could use that backup too, to revive my nook =)
I have an open thread here with all the efforts done so far http://forum.xda-developers.com/showthread.php?t=1805936
Nook Glow Backup Image
I have a backup image of a NSTG that I am uploading right now ... and looks like it just finished. Here it is:
dl[dot]dropbox[dot]com/u/98836278/nook-glow-backup.img
When you have the image downloaded follow these instructions:
blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch/
As a new user I am not allowed to post outside links.
Downloading, thank you so much!!!
I'll post again with the results...
YES, YES, YES, YES !!!!!!
leadbella thank you a million times!!
I downloaded the image, and wrote it ot my nook.
By the end of the operation, which took some 9 minutes or so, the process ended abruptly:
error 27 writing to disk at sector 3825664
I opted to ignore it and reboot the nook, just to see what happened. The nook booted alright.
I then booted in CWR and replaced /rom with the contents of my own nook /rom which I had salvaged.
I then booted again, and performed all the process flawlessly.
So far I have registered the device again (no error here since /rom contains my sensitive data. Don't know if it would work if the data was from the original image, since MAC address, device SN and some other parameters would not match), loaded a couple of books and started reading again.
Just in time for another one week shift (leaving tomorrow)
Leadbella you saved my..... nook =)
Thank you, I owe you one.
No problem at all. Looks like it worked for srgarfi ... dukenookem please let me know when you have finished downloading the image. I need to use my dropbox for other things at some point, but I can keep it in there until you finish downloading the image. If the image link above no longer works and anyone needs a copy of this image feel free to send me a message and I will try to post it back up.
The image is from a just out of the box NSTG with no information and nothing added to it.
leadbella said:
No problem at all. Looks like it worked for srgarfi ... dukenookem please let me know when you have finished downloading the image. I need to use my dropbox for other things at some point, but I can keep it in there until you finish downloading the image. If the image link above no longer works and anyone needs a copy of this image feel free to send me a message and I will try to post it back up.
The image is from a just out of the box NSTG with no information and nothing added to it.
Click to expand...
Click to collapse
Thanks Leadbella. Downloaded the backup. Tried to follow the instructions, but the size of you file is almost 2 gb, too large for my microSD. Didn't expect the backup file to be that large. gonna go look for a larger sd card.
Renate NST said:
You should make an effort to salvage your personalized data in /rom.
There is all the info in the p2 partition (/rom).
There is also a backup copy in the p3 partition (/factory) as rombackup.zip
You might do this with noogie or CWR and ADB.
Click to expand...
Click to collapse
That totally didn't make any sence to me. Sorry for my ignorance. Are there any instructions to follow? thanks.
Could not register
Hey leadbella, thanks for uploading the backup image. I downloaded and worte it to my nook STG. However, I couldnt get pass the setup process. Everytime I reach the log in menu, it will have the error logging in msg. Do you know what might be wrong?
Zaotr0pe said:
Hey leadbella, thanks for uploading the backup image. I downloaded and worte it to my nook STG. However, I couldnt get pass the setup process. Everytime I reach the log in menu, it will have the error logging in msg. Do you know what might be wrong?
Click to expand...
Click to collapse
You should have saved your /rom files before ovewritting your nook with leadbella's image.
And I'm afraid there not anything you can do to recover your unique /rom files for your nook now.
Oh, I was concerned that Leadbella had posted an unedited backup...
so, what is going on?
first: if a post about partitions isn't comprehensible to you yet -- you probably shouldn't root your device until you do enough reading that you understand it a bit.
Putting leadbella's file onto an SD card probably won't work as a way to restore; when I recover from an image, I use a usb cable and write from my computer to my device.
Leadbella seems to have taken a complete backup image from the device - this will include the important /boot and /system partitions (which is good) but will also include the /rom partition, which unfortunately is unique to every device.
So, if you restore from that image and don't have access to your own /rom partition or recovery image, you're going to wind up attempting to register a second copy of Leadbella's Nook to your account. Fortunately for Leadbella, that won't work.
Now, what can you do to repair and get a corrected nook which can be registered?
I'm going to try an experiment - I'm going to start by backing my device up in its current state.
(I do this by making a Noogie disk
Booting from Noogie
Connecting to my computer
using the command dd if=/dev/sdX of=/dev/currentnookglow.img bs=1M
where X is the number of the device that pops up when I connect my NSTG to the USB port.)
That requires linux; if you don't have linux, you can install VMWare Player (Free) and then install linux in that.)
What I'm going to try doing:
- back my system up
- image with Bella's file
- delete the file /rom/devconf/MACAddress from the imaged device
- reboot the device
- see if I can now see the real, physical MAC address, either on the device (unlikely) or on my router (likelier)
If I can see the MAC address, recreate the file with the correct values for Mac and also create a correct file for serial number /rom/devconf/SerialNumber
Boot, and see if the device is registerable to my account.
BUT: right now, BN has blown out the Nook Touch register/deregister/register process. So I can't do the test until they fix that.
And if it does work, anyone trying it will need
- the noogie disk
- linux
For windows users, maybe, but I have not tried:
- a clockwork boot disk
- functioning ADB able to connect to your clockwork-booted device
(Some clockwork boots support ADB; some do not.)
as roustabout explains, you can write Leadbella's image to your nook (if in windows use win32diskimager or diskimage) and then take a look at the contents of /rom.
The fix the contents of macaddress and serialnumber, but only if you plan to use the nook with B&N services fix the rest of the necessary files.
If you just plan to use your nook as a standalone reader (yes, why not?) once registered you can just ignore the contents of /rom (at least until the next software update).
leadbella said:
I have a backup image of a NSTG that I am uploading right now ... and looks like it just finished. Here it is:
dl[dot]dropbox[dot]com/u/98836278/nook-glow-backup.img
When you have the image downloaded follow these instructions:
blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch/
As a new user I am not allowed to post outside links.
Click to expand...
Click to collapse
These links are both no longer available. Can someone post them to a mirror?
I'd really appreciate reup as well, since my backup is not working and I need to restore my NSTG.
before restoring from someone else's img, remember to salvage your own /rom partition since these files are unique to each device and you'll need them to register your nook prior to starting reading.
That said I can upload that IMG, but what's the best choice to do so? Any of the many filesharing services? Dropbox ? Google Drive?
require those images
Hi srgarfi, is it possible for you to please upload those images... i need them...
Please reupload the backup. I could really use it too.
the image I used, originally shared by LeadBella (thanks again!) is here:
https://www.dropbox.com/s/xikkjs627s9mw2r/nook-glow-backup.img
Remember to save your /rom files before applying the backup or you won't be able to register your nook on B&N to start reading.

[TUTORIAL] Recovering your Nook Simple Touch Glow

Disclaimer
Before even consider reading this, know that I cannot be held responsible if following these steps will: brick your device, make your girl friend break up with you, start third world war or do any other kind of damage.
Motivation
This tutorial is intended to help people who did not make a full backup of their device and applied the Alpha-FormatTouch-2.zip to their device and as a result lost the GlowLight feature. It took me a couple of days to figure out how to revert to factory settings, and thus, I hope that I can save others time.
Preliminary
You need
Nook Simple Touch Glowlight, semibricked
SD Card
SD card reader
Downloads
Download the following files:
factory.zip - downloads[dot]nanophysics[dot]dk/nstg/factory[dot]zip (if you have a copy of your own factory.zip -- found on the partition /factory/ -- use that instead)
[ClockworkMod - downloads[dot]nanophysics[dot]dk/nstg/sd_128mb_clockwork-rc2[dot]zip
Install Clockworkmod on SD card
On Mac OS X, plug in the SD card and find the device using
Code:
$ diskutil list
I will assume that your device is /dev/disk1. Unmount the disk
Code:
sudo diskutil unmountDisk /dev/disk1
and write the ClockworkMod to it
Code:
sudo dd if=128mb_clockwork-rc2.img of=/dev/disk1
Copy the factory.zip to the disk and eject it.
On Windows you can use Win32Imager.
Install factory image
Power off your Nook and insert the SD card. Then power it up. After a while the CWM menu will appear (if you get a white screen press right-down). Select "install zip from sdcard" using the right side navigation to go up and down and u to enter. If you enter the wrong menu you can go back on right up. Now select "choose zip from sdcard" and choose factory.zip. Finally, click the option saying "yes - install factory.zip"
After a few minutes the installation is complete and if everything went ok, you should now be back to the original factory software.
Reset user settings (optional)
If you want your Nook to be completely reset, you can optionally do a reset of your settings. Power off you Nook. Power it up again and hold left and right down simultaneously for around 30 s. Answer yes twice. After a while your Nook has been reset.
Backup
Finally, it is time to do what you should have done in the first place (and probably also the reason why you are following this tutorial): Make a full backup of your Nooks internal SD card. See blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch for more information.
Thanks for the tutorial. However i just had a few queries.
1. My NSTG is rooted and functioning normally. Only glowlight does not work. Does your tutorial apply to such a device too.
2. How can i take backups of my current /rom and /factory partitions so that i can restore them in case of any eventuality.
Thanks a bunch in advance.
i just erase every thing . now my nook is completely messed up.
I can't find your factory.zip would you mind resend it please ?
shank21101985 said:
Thanks for the tutorial. However i just had a few queries.
1. My NSTG is rooted and functioning normally. Only glowlight does not work. Does your tutorial apply to such a device too.
2. How can i take backups of my current /rom and /factory partitions so that i can restore them in case of any eventuality.
Thanks a bunch in advance.
Click to expand...
Click to collapse
If your NSTG is rooted, this may remove rooting - at least I think, I did not try. However, you can always reroot.
Regarding backup, I would make a full image backup before starting. If you have a Windows box, follow the instruction on blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch and make a full backup of your system.
I have only done backup of individual partitions on Linux: Boot the device with noogie.img and plug it in. On Ubuntu,t 6-8 partitions should immediately appear.
jjinkou2 said:
i just erase every thing . now my nook is completely messed up.
I can't find your factory.zip would you mind resend it please ?
Click to expand...
Click to collapse
There was missing a slash in the URL. It has been fixed.
Are you able to register a device reimaged using this factory.zip to your BN account?
If not, it's a bit of a pain for folks.
I have a disk image made via
dd if=/dev/block/mmcblk0p1 of=/part1.img bs=1M
This contains teh whole of a US NSTG's first partition; restoring it using
dd if=part1.img of=/dev/block/mmcblk0p1 bs=1M
allows me to boot my device, and the glow still works.
This seems to be more likely to restore the glow function yet preserve the ability to register with BN - the factory.zip method is not generic, as far as I know, it will restore some other person's NST serial number, mac address and other identifiers to your device, won't it?
If someone will PM me, I'll send a zipped copy of my .img file to them and let them try using it to recover glow function and their own registration in a nook glow. If that works, it can be posted more widely.
roustabout said:
This seems to be more likely to restore the glow function yet preserve the ability to register with BN - the factory.zip method is not generic, as far as I know, it will restore some other person's NST serial number, mac address and other identifiers to your device, won't it?
If someone will PM me, I'll send a zipped copy of my .img file to them and let them try using it to recover glow function and their own registration in a nook glow. If that works, it can be posted more widely.
Click to expand...
Click to collapse
Remark that I recommend that people use their own factory.zip image. Nevertheless, all these data you mention are stored on the rom partition. To my awareness this partition is only overwritten if one applies rombackup.zip, but not by factory.zip. Thus, your B&N shop should be fully functional afterwards. I did apply someone elses factory.zip first, and I had no problems registering my device. However, if anyone would experience such an issue, please drop a line in this thread.
In any case, you should always do a full system image before following tutorials like this one, or for that matter, before apply someone elses partition images to your own device.
roustabout said:
Are you able to register a device reimaged using this factory.zip to your BN account?
If not, it's a bit of a pain for folks.
I have a disk image made via
dd if=/dev/block/mmcblk0p1 of=/part1.img bs=1M
This contains teh whole of a US NSTG's first partition; restoring it using
dd if=part1.img of=/dev/block/mmcblk0p1 bs=1M
allows me to boot my device, and the glow still works.
Click to expand...
Click to collapse
Judging from your other post (http://forum.xda-developers.com/showthread.php?t=1836188&page=4), the partition you have made a copy of, is the boot partition? If glow was already working, it will still work after overwriting the boot image.
However, if it was not working already, it is very unlikely that installing a new boot image will resolve the issue described here, since it is a consequence having downgraded the OS.
I had not understood that the device you're targeting with this thread is an NSTG running 100% noo simple touch software - the thread refers to a problem with the alpha touch formatter, but I had not realized that was the outcome of the tool.
I've seen a few people describe their NSTGs as "fine, but not glowing any more" and had not seen those folks explain that they were running NST software on the NSTG.
For those folks, I had thought copying in the boot environment and kernel would be helpful. My understanding was that the kernel in the NSTG at software 1.1.5 was different than the NST kernel; I was thinking that getting the kernel and other boot hooks ready was what was really missing.
Fortunately, there's now a 1.2.0 updater out, and I suspect that soon there will be a CWM installable 1.2.0 update which will be super helpful. (Though folks will still need a partition table - I think that would be another use of writing in a viable first partition followed by a restart, to get the partition table straightened out before proceeding.)
roustabout said:
I had not understood that the device you're targeting with this thread is an NSTG running 100% noo simple touch software - the thread refers to a problem with the alpha touch formatter, but I had not realized that was the outcome of the tool.
I've seen a few people describe their NSTGs as "fine, but not glowing any more" and had not seen those folks explain that they were running NST software on the NSTG.
For those folks, I had thought copying in the boot environment and kernel would be helpful. My understanding was that the kernel in the NSTG at software 1.1.5 was different than the NST kernel; I was thinking that getting the kernel and other boot hooks ready was what was really missing.
Fortunately, there's now a 1.2.0 updater out, and I suspect that soon there will be a CWM installable 1.2.0 update which will be super helpful. (Though folks will still need a partition table - I think that would be another use of writing in a viable first partition followed by a restart, to get the partition table straightened out before proceeding.)
Click to expand...
Click to collapse
Ok. No this thread is not intended for people who have destroyed partition tables etc., but only for people who have downgraded their software by using NST recovering guides on their NSTG device. I found it relevant to explain how this is done, since many people complain that their NSTG works, except that glow light no longer works. If they look into the software version they find something below 1.1.5, like 1.1 which was my case. I could not find a guide which explained me what to do after screwing up the software, hence this guide.
Partition tables and "accidently formatting" is a completely other issue. In the end, here the main problem is that people do not make a backup as they assume that everything is going to be fine. I assumed that myself. However, at some point I will have a look at the rom partition, because I think it is quite limited amount of information you find their. It should be possible to restore your Nooks serial number -- it is written on the package of the Nook -- after applying another Nooks image. I just received my second Nook so I am going to try this at some point.
Thank you so much for sharing the solution.. finally my glowlight works now !!
shank21101985 said:
Thank you so much for sharing the solution.. finally my glowlight works now !!
Click to expand...
Click to collapse
Hic, I cannot download the image file, my backup file was deleted, anyone can upload that image for me?
Thanks so much:crying:
factory.zip
I know it's a long shot, but if anyone has a copy of the factory.zip from a glowlight I'd really appreciate it. I've installed a non-glowlight one for now, but would really love my backlight back!
Cheers!
john2k10 said:
I know it's a long shot, but if anyone has a copy of the factory.zip from a glowlight I'd really appreciate it. I've installed a non-glowlight one for now, but would really love my backlight back!
Cheers!
Click to expand...
Click to collapse
So did you actually replace the factory.zip with one for the NST or did you just run a restore from, say, NookManager? I'm not too sure about this, but I think it's kind of difficult to wipe the factory.zip. Anyway, since I'm not familiar with the NTG, and you seem to have done something that others have also done before, have a look at this old thread and see if it gets you anywhere:
http://forum.xda-developers.com/showthread.php?t=1936458
john2k10 said:
I know it's a long shot, but if anyone has a copy of the factory.zip from a glowlight I'd really appreciate it. I've installed a non-glowlight one for now, but would really love my backlight back!
Cheers!
Click to expand...
Click to collapse
Mmm......have a look at this:
http://waveswirl.blogspot.com/2013/01/xda-developers-tutorial-how-to.html
nmyshkin said:
Mmm......have a look at this:
http://waveswirl.blogspot.com/2013/01/xda-developers-tutorial-how-to.html
Click to expand...
Click to collapse
Its dead I need a glowlight factory image
can someone please re-upload the glowlight factory image please.... Thank you in advance

[Q] Seriously messed up glowlight

Hi lovely people,
Ive managed to mess up my glowlight - Ive managed to have a look at the partition table using noogie and the rom partition is showing as unallocated. I've tried data recovery to no avail. I dont suppose anyone has a complete image of a uk nook simple touch glowlight by any chance, or even just a copy of the rom partition that I can copy back into place using minitool partition wizard?
Thanks for reading folks
cortexbomber said:
Hi lovely people,
Ive managed to mess up my glowlight - Ive managed to have a look at the partition table using noogie and the rom partition is showing as unallocated. I've tried data recovery to no avail. I dont suppose anyone has a complete image of a uk nook simple touch glowlight by any chance, or even just a copy of the rom partition that I can copy back into place using minitool partition wizard?
Thanks for reading folks
Click to expand...
Click to collapse
I don't have a full image, but I do have a copy of the /rom partition for you!
Here you go! :good:
thenookieforlife3 said:
I don't have a full image, but I do have a copy of the /rom partition for you!
Here you go! :good:
Click to expand...
Click to collapse
Thanks :0)
Umm how do I use the qr code on my pc? I dont have a webcam or decent mobile phone
cortexbomber said:
Thanks :0)
Umm how do I use the qr code on my pc? I dont have a webcam or decent mobile phone
Click to expand...
Click to collapse
You don't need the QR code to download the .zip. Just click the name of the file up there ^, it's to the left of the "Click for QR Code" text.
thenookieforlife3 said:
You don't need the QR code to download the .zip. Just click the name of the file up there ^, it's to the left of the "Click for QR Code" text.
Click to expand...
Click to collapse
Doh! i thought it was just the one link.
Ive been using computers since the early 80's - embarrasing!
cortexbomber said:
Doh! i thought it was just the one link.
Ive been using computers since the early 80's - embarrasing!
Click to expand...
Click to collapse
The eighties? Wow, you're an old pro, then! :good:
I, on the other hand, wasn't even alive in the eighties!
Let me know how that /rom partition treats you.
thenookieforlife3 said:
The eighties? Wow, you're an old pro, then! :good:
I, on the other hand, wasn't even alive in the eighties!
Let me know how that /rom partition treats you.
Click to expand...
Click to collapse
Ha! Old Pro indeed Old yes. Pro? Definitely questionable. :good:
Will do. Just having trouble now creating a fat32 partition. The various programs ive tried only let me make a 16mb fat16 partition and after putting the rom data on it, the nook still doesnt want to boot. There may be other problems with the rest of the software. Ah well. I'll either get there or buy another e-reader )) But the challenge is more entertaining.
cortexbomber said:
Ha! Old Pro indeed Old yes. Pro? Definitely questionable. :good:
Will do. Just having trouble now creating a fat32 partition. The various programs ive tried only let me make a 16mb fat16 partition and after putting the rom data on it, the nook still doesnt want to boot. There may be other problems with the rest of the software. Ah well. I'll either get there or buy another e-reader )) But the challenge is more entertaining.
Click to expand...
Click to collapse
lol :laugh:
Have you tried booting NookManager from your sdcard and using the "Restore factory.zip" function? That seems to work very consistently.
thenookieforlife3 said:
lol :laugh:
Have you tried booting NookManager from your sdcard and using the "Restore factory.zip" function? That seems to work very consistently.
Click to expand...
Click to collapse
Just trying that now
cortexbomber said:
Just trying that now
Click to expand...
Click to collapse
No joy sadly. More scouring the internet later i think - House chores to do now. SIgh.
Mayn thanks for the rom and the rest of your advice tho
cortexbomber said:
No joy sadly. More scouring the internet later i think - House chores to do now. *sigh*
Many thanks for the rom and the rest of your advice tho
Click to expand...
Click to collapse
If it was logical, I'd totally give you a full image, but the problem is that each device has its own serial number - if I give you an image of my device, then your device will have mine's serial number, which won't work out so well!
I'd love to keep trying to help you, though - Nook Touch related things are really my forte.
Let's start at the beginning - in your first post, you said that "you managed to mess up your GlowLight". What did you do to mess it up?
Is/was your Nook rooted?
Will your device boot and be used properly, but the GlowLight itself just doesn't work?
thenookieforlife3 said:
If it was logical, I'd totally give you a full image, but the problem is that each device has its own serial number - if I give you an image of my device, then your device will have mine's serial number, which won't work out so well!
I'd love to keep trying to help you, though - Nook Touch related things are really my forte.
Let's start at the beginning - in your first post, you said that "you managed to mess up your GlowLight". What did you do to mess it up?
Is/was your Nook rooted?
Will your device boot and be used properly, but the GlowLight itself just doesn't work?
Click to expand...
Click to collapse
Hi again, sorry for not getting back sooner - that damned thing called life always gets in the way
Yeah, it was rooted. I had used cwm and had adw running as a front end and had installed the screen lock bypass, but the bypass didnt work out so well - quite a bit of battery drain - even when left on a table(so no accidental waking up) - i tried to return it to stock - cant remember what i did tho - and now it just starts with the read forever screen and gets no further - it also seems that it doesnt power off and stays on till the battery is flattened. Trying to boot from the sd card using either nook manager or noogie works just fine tho.
I can see the partitions though minitool partition wizard and the Rom partition is "unallocated" there is also an unallocated space of 56mb at the end of the partitions.
I have tried recreating a fat32 rom partition and then copying the rom backup info from the factory partition, but no joy. For some reason, no partition software I have could create a fat32 partition directly on the nook, so I had to create one on the pc and then copy it over :-/
Thanks for the continued help btw
cortexbomber said:
Hi again, sorry for not getting back sooner - that damned thing called life always gets in the way
Yeah, it was rooted. I had used cwm and had adw running as a front end and had installed the screen lock bypass, but the bypass didnt work out so well - quite a bit of battery drain - even when left on a table(so no accidental waking up) - i tried to return it to stock - cant remember what i did tho - and now it just starts with the read forever screen and gets no further - it also seems that it doesnt power off and stays on till the battery is flattened. Trying to boot from the sd card using either nook manager or noogie works just fine tho.
I can see the partitions though minitool partition wizard and the Rom partition is "unallocated" there is also an unallocated space of 56mb at the end of the partitions.
I have tried recreating a fat32 rom partition and then copying the rom backup info from the factory partition, but no joy. For some reason, no partition software I have could create a fat32 partition directly on the nook, so I had to create one on the pc and then copy it over :-/
Thanks for the continued help btw
Click to expand...
Click to collapse
Are you interested in getting back the B&N functions? Because if not, then what I can do is back up my rooted GlowLight, factory wipe it back to 1.1.5, bypass Oobe (B&N registration), update to 1.2.1, and then make an image of that for you.
Beware, though, you won't be able to use any of the B&N functions if you want me to do that, because your device will have mine's serial number. But don't worry, it won't share anything except for that, so your device will be plenty usable.
thenookieforlife3 said:
Have you already tried booting into NookManager and restoring factory.zip?
Are you interested in getting back the B&N functions? Because if not, then what I can do is back up my rooted GlowLight, factory wipe it back to 1.1.5, bypass Oobe (B&N registration), update to 1.2.1, and then make an image of that for you.
Beware, though, you won't be able to use any of the B&N functions if you want me to do that, because your device will have mine's serial number. But don't worry, it won't share anything except for that, so your device will be plenty usable.
Click to expand...
Click to collapse
Yeah, i tried factory reset with nookmanager, but when I pressed the button to choose factory reset, it came up with the screen that showed the start of progress, but nothing else happened - even after several hours.
by b&n function i assume you mean the shop etc - cant say I'm worried about that bit, but if It will be back to stock, with just the stock software on, that would be cool. )
How would I transfer the complete image? I presume fire up noogie and partition wizard, wipe(err backup) all the partitions on my nook and then copy your partitions over?
cortexbomber said:
Yeah, i tried factory reset with nookmanager, but when I pressed the button to choose factory reset, it came up with the screen that showed the start of progress, but nothing else happened - even after several hours.
by b&n function i assume you mean the shop etc - cant say I'm worried about that bit, but if It will be back to stock, with just the stock software on, that would be cool. )
How would I transfer the complete image? I presume fire up noogie and partition wizard, wipe(err backup) all the partitions on my nook and then copy your partitions over?
Click to expand...
Click to collapse
It will be back to stock, but you won't be able to register with B&N and/or buy any books from them. The Social features also will not work.
If you're interested, I'll make that image for you. See the "back up you Nook" link in my signature for a guide on making and restoring Noogie images.
thenookieforlife3 said:
It will be back to stock, but you won't be able to register with B&N and/or buy any books from them. The Social features also will not work.
If you're interested, I'll make that image for you. See the "back up you Nook" link in my signature for a guide on making and restoring Noogie images.
Click to expand...
Click to collapse
Yep! Interested doesnt quite describe it tho More like biting your hand off
cortexbomber said:
Yep! Interested doesnt quite describe it tho More like biting your hand off
Click to expand...
Click to collapse
EDIT - See OverByter's post below, it has shown me that this wouldn't work out.
Try his method. I'll only give you an image of my device as a last resort.
Your image will also have your mac address besides the serial number, don't think that this is the way to go, basically he'll have an unworkable clone of your device. Why doesn't he use cwm to wipe the partition and then either adb push the rom or use a flashable image?
OB
Sent from my SPH-D710VMUB using Tapatalk 2
thenookieforlife3 said:
Ah. :laugh:
I'm kind of busy with school work right now, but I'll try to get it to you today.
Check for PMs from me in a few hours or so. :good:
Click to expand...
Click to collapse
Hehe. Absolutely no rush. I just appreciate the help.
cortexbomber said:
Hehe. Absolutely no rush. I just appreciate the help.
Click to expand...
Click to collapse
Okay, I may actually have solved your problem! Try the following steps - it's called the "eight interrupted boot" method.
1. I am expecting your Nook is still stuck at the "Read Forever" screen. If it's not, go ahead and turn your Nook all the way off.
2. Now, press the power button to take it to the "Read Forever" screen.
3. After it's there, press and hold the power button again to make the screen flash black and go back to the "Read Forever" screen.
4. Perform step 3 seven more times.
5. After the 8th interrupted boot, your Nook will restore itself to the factory image that it came with right out of the box.
6. Done!
Hope this works! :good:

nst glowlight starting up stops every time

I bought a used nst glowlight (bnrv350), I made a backup, and then I tried to root using glownooter, but had a limited success : I could not install google market or opera mobile.
So I tried to restore the backup, but after "read forever, your nook is starting up", nothing happens, the message just stays there. I can boot with the back button, but it does the same.
I then tried to restore the factory image several times, using all the methods I could find in the internet, but it does the same as above. It has been going on for 24 hours.
The problem might have originated when I could not use winimage in my windows 10 computer to make the backup, and I used windows xp in a virtualbox in my linux computer instead. I used also dd, but I am afraid I don't remember the exact order. The backup size is 426.8 MB.
I reverted back to windows 10 with win32diskimager, with the same result.
Can anything be done ?
sinlog said:
I bought a used nst glowlight (bnrv350), I made a backup, and then I tried to root using glownooter, but had a limited success : I could not install google market or opera mobile.
So I tried to restore the backup, but after "read forever, your nook is starting up", nothing happens, the message just stays there. I can boot with the back button, but it does the same.
I then tried to restore the factory image several times, using all the methods I could find in the internet, but it does the same as above. It has been going on for 24 hours.
The problem might have originated when I could not use winimage in my windows 10 computer to make the backup, and I used windows xp in a virtualbox in my linux computer instead. I used also dd, but I am afraid I don't remember the exact order. The backup size is 426.8 MB.
I reverted back to windows 10 with win32diskimager, with the same result.
Can anything be done ?
Click to expand...
Click to collapse
That backup is too large, I think. Should be more in the neighborhood of 250 MB? Have you tried the factory re-image where you just see the booting up screen and then hold down the two bottom hardware buttons until you get a prompt?
It's difficult--but not impossible--to damage the factory image unless you've been messing with the partitions. If that method does not get you there, consider making a NookManager card and trying to access the re-image routine from its menu.
Thank you for your reply. I just used nookManager. After 5 seconds, it said the backup was successful, but there was no backup in the card. Similarly, it said that rooting was successful, but when I removed the card, it did the same as before : "starting up..." and it stays there.
Do you have another idea ? I downloaded the 1.2.2 update from the b&n site. Can nookManager install it ?
PS: The nook was already 1.2.2
Yes, I used the two lower buttons trick.
sinlog said:
Thank you for your reply. I just used nookManager. After 5 seconds, it said the backup was successful, but there was no backup in the card. Similarly, it said that rooting was successful, but when I removed the card, it did the same as before : "starting up..." and it stays there.
Do you have another idea ? I downloaded the 1.2.2 update from the b&n site. Can nookManager install it ?
PS: The nook was already 1.2.2
Yes, I used the two lower buttons trick.
Click to expand...
Click to collapse
5 seconds is not enough time for NookManager to correctly make a backup. And, backups can only be seen on the card if you connect your NSTG to your PC while NookManager is running. Otherwise the partition is invisible.
It's hard to know since I have no experience with the NSTG. If it were an NST I would suggest that you perform the region change flash, but it's not clear if that will remove your light function or, indeed, if the flash is deep enough to rewrite the areas of your device that appear to be preventing boot. AFAIK there are no ROM images for the NSTG available. But there might be. Somewhere.
I guess if you have exhausted all the possibilities, rather than trashing the device I would try the region change (just flash the US firmware again--I assume that's what's on there already). It may or may not preserve the glowlight capability, but it might at least produce a functioning e-reader. But only as a last resort.
Edit: Hmm.... seems like I've been down this winding road before: https://forum.xda-developers.com/showpost.php?p=72551413&postcount=57
But I emphasize that this process worked for a plain NST, not the NSTG, so it is an absolute last resort (and might not work anyway because you could have a completely different situation). Next thing is to look at the innards of the 1.1 updater and see if Glowlight updates could be substituted...
O.K. So here is a thread that contains a link to an NSTG image and the instructions to write to your device (read down in the thread).
https://forum.xda-developers.com/showthread.php?t=2608815
What "may" happen: your device could end up with a mismatched serial number and or MAC address depending on how this image was made. There is information on this forum for correcting the MAC address. Just a disclaimer. I don't know. IF this is successful, you can then do a manual update to 1.2.2 and then root with the updated NookManager. I've checked the link to the image and it is still good. I got a file that is about 245 MB--seems about right. Presumably you use the image in place of your backup in the restoring process described in the thread.
I am very grateful for your help, but I am afraid I need more. The nook is now functioning and I might not have done it without your hints. As you suspected, the serial number and mac address have changed (I wrote them down before all this). I suppose that's why it did not automatically upgrade to 1.2.2 . Also the device says it's connected to the internet, but it doesn't seem to be.
I searched xda (nstg mac address, nstg serial number), but I didn't find anything meaningful to me (there are posts by Renate and by ros87 but too complex). Can you help, please ?
sinlog said:
I am very grateful for your help, but I am afraid I need more. The nook is now functioning and I might not have done it without your hints. As you suspected, the serial number and mac address have changed (I wrote them down before all this). I suppose that's why it did not automatically upgrade to 1.2.2 . Also the device says it's connected to the internet, but it doesn't seem to be.
I searched xda (nstg mac address, nstg serial number), but I didn't find anything meaningful to me (there are posts by Renate and by ros87 but too complex). Can you help, please ?
Click to expand...
Click to collapse
Oy.
I didn't think you would act so rashly with all my disclaimers. Well, it's done. I actually don't think the MAC address is a big deal unless you begin to have issues.
Did you actually manage to register? If so then the serial number must not currently be in use and the change you effected was deep enough to pass muster. If not....well battery life is said to be shorter for devices that have skipped registration.
Correcting the MAC address is described (sort of) here: https://forum.xda-developers.com/showthread.php?t=1483600
As far as I can guess it involves editing a hex file. Doable, but maybe not needed. There is no way to correct the serial number. It is heavily encrypted with private keys. Again, if you managed to register then this is all moot.
How are you judging lack of internet connectivity?
I was not given the opportunity to register and I don't care about registration, but I'd like to have connectivity. The link you just gave me is for the ros87's thread that I mentioned, and I don't know how to use it. So I suppose I cannot upgrade to 1.2.2 . Should I root the device ?
PS : ros87's last activity was 2 years ago
EDIT : I copied nook_1_2_update.zip in the device and it was installed. I have now 1.2.2
sinlog said:
I was not given the opportunity to register and I don't care about registration, but I'd like to have connectivity. The link you just gave me is for the ros87's thread that I mentioned, and I don't know how to use it. So I suppose I cannot upgrade to 1.2.2 . Should I root the device ?
PS : ros87's last activity was 2 years ago
EDIT : I copied nook_1_2_update.zip in the device and it was installed. I have now 1.2.2
Click to expand...
Click to collapse
You didn't answer my question about connectivity. Are you not able to make a connection? With only the stock device there is nothing to connect to other than B&N. What does it say about "Owner" in the Settings?
Yes, you should root. Be sure to use the NookManager update or it won't work.
Before we even think about the MAC address issue you need root access and some way to tell if you actually have an internet connection. That means some kind of functioning browser, etc.
Do you still have that weird backup? If so, keep it safe somewhere. You may want that someday.
I tried to download a book and I got this : Unable to download, Internal error...
I can ping the nook from the computer.
I will look into rooting the device in 2 or 3 hours and then post again. I suppose this is what you're referring to :
https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048
Thank you for your patience with me.
sinlog said:
I tried to download a book and I got this : Unable to download, Internal error...
Click to expand...
Click to collapse
There is an entire galaxy of mystery contained in that statement. Download from where? Download with what? Do you have an sdcard inserted for storage?
nmyshkin said:
There is an entire galaxy of mystery contained in that statement. Download from where? Download with what? Do you have an sdcard inserted for storage?
Click to expand...
Click to collapse
I meant to download a book from the home page of the nook, where it says New reads. I am still unrooted and I don't leave an sdcard inserted.
sinlog said:
I meant to download a book from the home page of the nook, where it says New reads. I am still unrooted and I don't leave an sdcard inserted.
Click to expand...
Click to collapse
Hmm... I'm surprised there are any books populating that section at all since the device is not registered. In any case, that is no test of connectivity since without registration the NSTG will spit out all kinds of generic messages about connections and failures if you attempt anything that requires access of B&N servers--like buying/downloading a book (which you can't do unless you are registered).
Rooted with nookManager updated. Opera mobile needs to be reinstalled. I can connect to the computer using es file explorer, so wifi is ok. BUT I can't use nookManager because I can't read the icon labels. I'll restore the backup tomorrow and I will try another rooting method. There are 2 more, I think : tiny and glownooter. Are there others ?
sinlog said:
BUT I can't use nookManager because I can't read the icon labels.
Click to expand...
Click to collapse
? Do you mean ADW Launcher? You can fix the icon label issue in the Settings. As I recall the default font color is white. That needs to be changed to black. The size can also be changed. Depending on what icon style you pick the label will either be on one line or, if longer, on two. LOTS of Settings in ADW. Don't write it off without spending some time working with it.
Sorry, I used glownooter. It's a lot like touchnooter, with which I am familiar. I still have to sign in to my google account and to install opera mobile. I'll be back when finished.
Opera mobile is installed and working. I still can't sign in to google but I can use yalp store and that's good. Thanks again, nmyshkin, you saved my nook glowlight.

Categories

Resources