Related
I just started a wiki here
USB Host mode
I am hoping that you who actually know how to do it would help develop a set of instructions that are simple enough for a literate, adventurous non-tech (like me) to follow.
UPDATE: The wiki now has a complete list of installation instructions. You'll have to hunt through verygreen's thread below for operating instructions till they organized on the wiki.
The wiki and this thread (where noobs like me can post) are based on verygreen's
[WIP] USB Host support (working)
I asked verygreen and ros87 to do the USB Host mode for the Nook Simple Touch. Verygreen announced success within 48 hours. The hack has gotten whipped into shape there with the amazing help of ros87, Renate NST, mali100, and other superb xda people.
The project started at mobileread.com:
Project: E-Paper Tablet (touch-typable!)
Thanks to fellow mobilereaders for support, especially Kumabjorn, poliorcetes, and nealsharmon for donating money for devices.
The wiki is super rough. It assumes a new device in the box and a non-tech user. I started the instructions to show how simple they need to be. I will continue helping with that because it does seem difficult for techs to believe just how lost we can be with this stuff. My goal is to bridge the gap between techs and literate users so that non-programmers who want to type on the NST can. If you are an expert writer of users manuals, maybe you would help, too.
Honestly, I don't know the first thing to do now that my NST is on and registered. For example, I don't even know if I need to:
root the NST first
install adb (which I also don't know about)
or what. I have studied the thread, so I will be familiar with the terms. But I'm completely clueless about actually doing the hack. I managed to unbox my refurbished NST, update its software to 1.1.2 and install a microSD card. The issue is, what exactly should be done now? Please leave your answers in the wiki! Thank you!
I would say the best way to start is from eded333's Minimal Touch http://forum.xda-developers.com/showthread.php?t=1346748 . That gives you a nice system with market and a launcher to install and start your texteditor or writing apps.
If I find some time i will create a small update-package that installs all the necessary things for the usb-host mode.
Cool. Will the 1.1.2 NST software update screw any of this up? I have it installed now because it fixed wifi connection issues that affected me.
andrewed said:
Cool. Will the 1.1.2 NST software update screw any of this up? I have it installed now because it fixed wifi connection issues that affected me.
Click to expand...
Click to collapse
1.1.2 is fine. You can still use eded333's MinimalTouch to root it and get a launcher.
Awesome. Will dive in, then!
As promised I created a small update package, to install all the necessary files and tools.
It is installable via Clockwork Recovery in the same way as eded333's MinimalTouch, which should be installed first, to get root, a launcher and a working Market.
Requirements:
Software version 1.1 or 1.1.2 (1.1.2 is recommended, as it fixes WLAN issues)
root, a launcher and working market (I recommend using eded333's MinimalTouch)
What it does:
changes the kernel to NST-kernel v0.1 with USB-Host and multitouch support
changes the uRamdisk to a uRamdisk with fixed init (needed for USB Input devices) and adb-usb
installs the busybox and sqlite binaries
adds the permission node for multitouch to /etc/permissions/required_hardware.xml
installs the app UsbMode-1.2 and the NullKbd-1.1 by Renate NST
adds the permission to enable the NullKbd
changes the qwerty.kl and qwerty.kcm.bin to the remapped one by Renate NST
installs the NookColorTools, so you can switch to the NullKbd
DISCLAMER and WARNING:
I'm not responsible for bricked devices, dead SD cards, lost data, fried USB-Devices. Make a backup before you try anything described here!
USB-Host support is still WIP (work in progress), the battery drain is noticeable higher.
this is the first release and only tested by myself, so don't expect it to be bulletproof.
Credits go to:
verygreen, ros87 and everybody who helped with the USB-Host mode,
Renate NST, for all the effort making USB-Host support userfriendly (USB-Mode app, NullKbd, key remapping, testing),
wheilitjohnny and arkusuma for the Multitouch support,
eded333, for his great MinimalTouch,
Download:
usb-host-mt-pack_0.1.zip
Thanks, mali100.
I'd just like to point out that you can switch to the NullKbd just by hitting the Ctrl key and selecting it from the popup IME picker.
Renate NST said:
I'd just like to point out that you can switch to the NullKbd just by hitting the Ctrl key and selecting it from the popup IME picker.
Click to expand...
Click to collapse
Nice easter-egg didn't noticed this before. Thanks
Ok, I will have to get a card reader. In the meantime, I'm getting a grip on the instructions by reading through the fine print. It led me to the noogie/backup process.
It says I need a class 6 microSD card. but I got a class 2 as per verygreen's instructions for the hack itself. Do I definitely also need a class 6 card just for the backup, or can I use my class 2 card?
Now that the hack is finally in reach, I want to do it right.
andrewed said:
Ok, I will have to get a card reader. In the meantime, I'm getting a grip on the instructions by reading through the fine print. It led me to the noogie/backup process.
It says I need a class 6 microSD card. but I got a class 2 as per verygreen's instructions for the hack itself. Do I definitely also need a class 6 card just for the backup, or can I use my class 2 card?
Now that the hack is finally in reach, I want to do it right.
Click to expand...
Click to collapse
I'm using a 4G class 2 micro SD card for NOOGIE and it's fine.
where to?
Hi where to put content of META-INF? (dont wanna root again...)
mrWax said:
Hi where to put content of META-INF?
Click to expand...
Click to collapse
The META-INF folder contains the insallation script and the interpreter for the script, they are used by CWM to install the package and not copied to the nook.
(dont wanna root again...)
Click to expand...
Click to collapse
If you mean that your device isn't rooted, and you don't want to, then I have to tell you that root is needed to switch between usb-host mode and peripheral-mode, so root is mandatory.
If you mean your device is already rooted and you don't want to redo it, then don't worry, this package doesn't contain files that root the nook.
I had already rooted my nook another way...now what?
Friends,
I rooted my Nook using the instructions here (SalsichaNooter):
http://www.youtube.com/watch?v=O05Y7C9a4eU
I didn't use the Clockwork method. I don't know how to revert and go back to your original instructions. I tried downloading usb-host-mt_pack-0.1.zip and installing the apps only but that didn't work.
Any suggestions on how I should go about the process without Clockwork? Or should I follow these directions to install clockwork even though I'm already rooted with SalsichaNooter?
I really would like to get a keyboard working on my Nook and feel like I'm so close.
nealsharmon said:
I didn't use the Clockwork method. I don't know how to revert and go back to your original instructions.
Click to expand...
Click to collapse
You don't have to revert anything, a device rooted with salsichanooter works fine.
I tried downloading usb-host-mt_pack-0.1.zip and installing the apps only but that didn't work.
Click to expand...
Click to collapse
That's because you also need another kernel and uramdisk and some configuration, that gets done by the updatepackage.
Any suggestions on how I should go about the process without Clockwork? Or should I follow these directions to install clockwork even though I'm already rooted with SalsichaNooter?
Click to expand...
Click to collapse
This update-package can only be installed with the Clockwork-mod recovery. You don't have to install CWM on the Nook, just write it to a sdcard (like you did with the salsichanooter image), copy the updatepackage onto the sdcard, put the card into the nook and reboot. The Nook then boots into Clockworkmod Recovery, then you got to "install zip from sdcard", choose the usb-host-package, click yes and wait, eject the sd card, and click reboot.
thank you
Thanks for your input. I will try the process you suggested.
It worked!
mali100 said:
You don't have to revert anything, a device rooted with salsichanooter works fine.
That's because you also need another kernel and uramdisk and some configuration, that gets done by the updatepackage.
This update-package can only be installed with the Clockwork-mod recovery. You don't have to install CWM on the Nook, just write it to a sdcard (like you did with the salsichanooter image), copy the updatepackage onto the sdcard, put the card into the nook and reboot. The Nook then boots into Clockworkmod Recovery, then you got to "install zip from sdcard", choose the usb-host-package, click yes and wait, eject the sd card, and click reboot.
Click to expand...
Click to collapse
I followed your instructions and it worked. Thank you very much.
Still Not working
I'm very new at this.
I have followed the above directions and patched with usb-host-mt-pack_0.1 successfully but my two USB keyboards are still not working.
I originally rooted my nook using TouchNooter 2.1.31.
I am using an OTG cable and am getting the solid green light after turning off current and selecting Host.
When i plug either keyboard (or bluetooth dongle for that matter) State changes from a_idle to a_host.
Other results:
Keyboard: none
all fields below that are blank.
Any suggestions on how i should proceed? Could this just be a matter of the keyboards not being compatible? What are the recommended keyboards?
Many thanks!
When you are having trouble, try a wall-powered hub (at least as a test).
I have seen where it switches to a_host but it's not really connected.
The "View USB" button is helpful and will show VID/PID.
If for some screwy reason you have a keyboard that is non-standard,
a lack of a black dot will indicate no driver is loaded.
Renate NST said:
When you are having trouble, try a wall-powered hub (at least as a test).
I have seen where it switches to a_host but it's not really connected.
The "View USB" button is helpful and will show VID/PID.
If for some screwy reason you have a keyboard that is non-standard,
a lack of a black dot will indicate no driver is loaded.
Click to expand...
Click to collapse
Thank you, Renate. That worked great. My Bluetooth is working and I'm using my apple wireless keyboard to word process. My arrow keys don't work so I have to do some touching or backspacing to edit in google documents.
I have a chronic case of CVS (eye condition). This is really gonna help me. Do you recommend a stand with space at the bottom for the cord?
Thank you so much!
Stand? I love mine. http://forum.xda-developers.com/showthread.php?t=1661902
You can use either a desk stand or the little bendy tripod.
The arrow keys should work, but they get rotated when in landscape mode.
There is a mod to make them not rotate.
http://forum.xda-developers.com/showthread.php?p=30260821&highlight=keyinputqueue#post30260821
Hello,
I'm new to the Nook Simple Touch and received it today. It's awesome so far!
1. Could someone tell me how I install CWM with it, is there a guide? I can't find any guide on the development section on xda, sorry.
2. Also, what is the best method to root my NST? Touch Nooter or Minimal Touch or another one?
3. Is there a stock ROM somewhere? I would want it, if I want to set my Nook back to the default settings and wipe everything if I'll mess it up somehow.
4. Can I update to the latest version 1.1.2 if I want to
+ root it
+ install CWM
+ install the multitouch function from here: http://forum.xda-developers.com/showthread.php?t=1563645
Is everything of this working with 1.1.2 or do I need 1.1.0?
5. And my last question is, what's the difference betwen N2E and NST in the development thread? (I know, NST = Nook Simple Touch, but what is N2E? I thought it's also the Nook Simple Touch)
I'm really, really sorry for those questions, but I'd be very happy if someone could answer them. I don't want to make something wrong with my beloved NST.
Thanks in advance!
Greetings,
Draygon
Welcome to the community!
Before you do anything, you're going to want to backup your Nook. Each Nook contains information specific to that Nook, such as the MAC address, serial number, etc., so this backup will be what will restore you to a stock out-of-the-box Nook. Just make sure you have an external card reader to write noogie.img to the SD card.
CWM is here, but there's no real reason to install it to the device itself. It's easier to install it to an SD card and just put that in when you need it. There's no custom ROMS yet, and it's better to use the backup you made earlier (hopefully).
Also, for rooting and installing multi-touch, I made a mini quick-start guide here.
For the most part, we haven't noticed much difference between rooting 1.1.0 vs. 1.1.2. And N2E stands for Nook Second Edition (this Nook came first).
Enjoy your Nook!
Hello Googie, Thanks a lot for your answer, they helped me a lot!
For sure I'll do the backup at frst.
Am I able to use N2E from the development forum on the NST? (like touchnooter?)
So, it's safe to update to 1.1.2 and root it? Because I have seen a few people on this forum complaning about bugs with a rooted 1.1.2, which aren't there with a rooted 1.1.0, such as that the search function is not working in the play stote with a rooted 1.1.2.
Would you recommend touch nooter or minimal touch?
Draygon said:
Am I able to use N2E from the development forum on the NST? (like touchnooter?)
Click to expand...
Click to collapse
The N2E is simply another name for NST, so it's safe to use anything with that name.
Draygon said:
So, it's safe to update to 1.1.2 and root it? Because I have seen a few people on this forum complaning about bugs with a rooted 1.1.2, which aren't there with a rooted 1.1.0, such as that the search function is not working in the play stote with a rooted 1.1.2.
Click to expand...
Click to collapse
There's not much difference between 1.1.2 and 1.1.0. B&N just addressed some WiFi issues with this update, not much has changed otherwise. And Google caused the searching issues by replacing Market with Google Play, it's just coincidence that the update came out when Google changed it.
Draygon said:
Would you recommend touch nooter or minimal touch?
Click to expand...
Click to collapse
I myself use Minimal Touch, but I haven't tried TouchNooter before. TouchNooter has some extra things with it (like a tool that under-clocks the CPU when it's not in use to save battery), but some times it fails to install correctly. And there's also the possibility that Market just won't work for 24 hours... but it's broken anyway.
Thanks again for the answers.
There's just one problem I have, which won't let me backup my NST:
From this guide: http://forum.xda-developers.com/showthread.php?t=1142983
I want to use the guide to backup the NST for windows 7 (post #2),
There's a big problem: the link to the noogie.img (which should be here: http://nookdevs.com/NookTouch_Rooting) was deleted.
1. Where can I get this noogie.img now? Could someone please upload it?
2. And the next problem is, how do I boot the noogie.img, if I have it? jocala just wrote, that you have to boot it. Not, how to boot it.
Thanks in advance!
http://www.thoughtsofthemasses.com/noogie.img.gz
burn the image it to sdcard, switch off your nook, plug in sdcard and turn nook on.
And small puzzle at the end: what does following message say about the nookdev page?
10:50, 11 January 2012 Spec (Talk | contribs) deleted "NookTouch Rooting" (content was: '#REDIRECT Nook_Simple_Touch/Rooting/Manual')
Are there any requirements that a microSD card must fill when used for this purpose? I have two fail notches on my lipstick case.
The first time I pulled a 256mb microSD card from an old phone; fail. Later I read it is recommended to use a Class 6 or greater. I bought a Class 10. Again, fail.
The adapter is electrically passive so that should not be a factor, right?
I never pay attention to that class stuff.
I always buy the Micro Center brand 4GB at $5.50 because they are only $1.50 more than 2GB.
Apparently they are Class 4.
Thank you, Renate NST. Then my problem lies elsewhere.
Between WinImage and Win32DiskImager has either shown a higher success rate for this project? Is one generally preferred by the community?
I use Win32DiskImager.
I've got about 10 different backups on my hard drive right now.
I've bricked my Nook multiple times trying to hack internals and restored from backup.
My backups end up by being 1,957,616,640 in size.
I don't use Clockwork or anything.
Thank you for providing the file size, that was helpful.
Is it odd that that the second backup (using noogie.img and DiskImage_1_6_WinAll.exe) was almost twenty-five times larger than the first? 79,675,392 verses 1,958,739,968.
If your backups are about 1.9xx Gigs then you are correctly backing up the entire physical internal memory of the Nook.
If your backups are 70 Megs or so you are either backing up only one of the 7 partitions on the Nook or
else you are backing up your SD card with Noogie on it.
Note:
After writing a Noogie image to an SD card you will find that the total size of the SD card has been reduced to 70 Megs or so.
To reclaim the entire size of the SD card for other uses you will need some tool like Partition Magic.
Windows Disk Management can not by itself repartition SD cards.
There's also something out there called SD formatter.
Or once you have your Nook running, you can just format it from that.
You have all been so very helpful. After watching the noob video I figured you people ate noobs for lunch.
Renate, you were right: I backed up the SD card. I hate to think of all the others who have done the same and won’t know the backup is useless until they need it. It’s an easy mistake to make but knowing an approximate file size was an excellent deterrent against disaster. Thanks for the heads up.
The rest was pure voodoo but I’m rooted. Still, there were some surprises and I have two final questions.
• Between failed rooting attempts, while in original mode, I updated the NS2 to 1.1.2. After rooting the device is using 1.1.0. Should I look for a way to root into 1.1.2 or just be content?
• Also while in original mode I wanted to change the registered gmail account for the device. I created a second B&N account using my preferred gmail, then did an “Erase and Deregister” to reregistered the device with the preferred gmail account. However, after rooting I couldn’t log into YouTube with my reregistered, preferred gmail, only the first gmail was accepted. Yet, when looking in Settings\Device Info\About Your Nook\Owner, my preferred gmail (not the first gmail) is listed. How do I get the rooted Nook to recognize my preferred gmail address in the market?
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
Hello fellow nook owners. My Nook is running 1.1 with TouchNooter. I just noticed there is and update for 1.2 and a alternate root method. My question is how would I go about updating to 1.2. In the NookManager thread it says, "If you've tried rooting your nook unsuccessfully with another utility, it's best to do a factory restore (from NookManager, choose the "Restore" menu and then "Restore factory.zip") and, if your nook came with older firmware, upgrade to the latest 1.2.1 firmware." Does that mean I can install NookManager with what I have now and then do the factory restore?
I apologize if this has been answered before. I am reading through all these separate threads trying to make sense of it, but want to be on the safe side. Thanks for reading.
Odp: [Q] Revert back to stock from touchnooter
NookManager is not something you install, it is an interactive utility which let's you root, backup or restore your nook to default. Restore will extract what is in your factory.zip, after wiping whole data. So I suggest that you push expected system's version, so you will no longer need to perform upgrades, just root after that.
I am on my phone so I won't post steps to do that, they are somewhere here.
Wysłane z mojego GT-I5700 za pomocą Tapatalk 2
domi.nos said:
So I suggest that you push expected system's version, so you will no longer need to perform upgrades, just root after that.
Click to expand...
Click to collapse
Thanks for the quick reply. I am a little unclear where you say, "push expected system version". Are you saying to install the 1.2 update like they recommend on the Barnes and Noble site?
Manual Download Instructions
1. From your computer, click here for the software update file. Select Save and select Desktop as the location. Do NOT modify or change the downloaded file's name in any way. Do NOT open the *.ZIP file.
2. Tap Settings on your NOOK's Quick Nav Bar, then tap Device Info and make sure your NOOK battery charge is at 20% or more.
3. Connect your NOOK to your computer using the USB cable that came with your NOOK. A new, removable drive should show up in My Computer (Mac users will see the NOOK drive appear on the desktop or in devices). You should also see a "USB Mode" message on your NOOK screen.
4. From your computer, drag and drop the downloaded *.ZIP file onto the main directory of the NOOK drive. Do NOT open or unzip the file. You should not create a new folder on the NOOK drive or add the file to any other existing folder.
5. Eject or Safely Remove the NOOK drive after the file transfer is complete.
6. Your NOOK will automatically recognize the file after a few minutes when it goes to sleep mode, and proceed to install the updates.
7. Please do not turn off your NOOK during the installation process.
8. Once the installation is completed, your NOOK will automatically restart.
9. The software has been successfully updated; tap on the small "n" that appears in the status bar for additional information.
Click to expand...
Click to collapse
Thanks again for reading and offering any help. It is much appreciated, Its what keeps me coming back to XDA.
toebee76 said:
Thanks for the quick reply. I am a little unclear where you say, "push expected system version". Are you saying to install the 1.2 update like they recommend on the Barnes and Noble site?
Thanks again for reading and offering any help. It is much appreciated, Its what keeps me coming back to XDA.
Click to expand...
Click to collapse
If you want to upgrade FW version after using any "Nooter" you should perform 'factory reset' (this will remove all your apk's and settings obviously so back them up using for example. 'Titanium Backup'.)
As far as I remember, after rooting Nook no longer sees the update.zip in 'NOOK drive'.
- Revert back to unrooted state (factory reset, manually or using NookManager).
- reboot
- register nook once again
- put update.zip in "NOOK drive" (internal memory)
- put nook to sleep and let it upgrade itself
- let it boot into newly installed 1.2.x
- register nook once again
- turn nook off
- run NookManager again to get root access on new FW
- use 'NTGAppsAttack' to get 'Google Play' on FW 1.2.x
I guess what 'domi.nos' is trying to say is that you could replace your factory.zip (stored in Nook's internal partition) containing FW 1.x with the one containing FW 1.2.x.
After this procedure every time you perform 'factory reset' your nook should revert to FW 1.2.x instead of FW 1.1.x.
Am I right, domi.nos ?
Odp: [Q] Revert back to stock from touchnooter
Yes, i find it better because in my case it was harsh to update using BN instructions.
Wysłane z mojego GT-I5700 za pomocą Tapatalk 2
osowiecki said:
If you want to upgrade FW version after using any "Nooter" you should perform 'factory reset' (this will remove all your apk's and settings obviously so back them up using for example. 'Titanium Backup'.)
As far as I remember, after rooting Nook no longer sees the update.zip in 'NOOK drive'.
- Revert back to unrooted state (factory reset, manually or using NookManager).
- reboot
- register nook once again
- put update.zip in "NOOK drive" (internal memory)
- put nook to sleep and let it upgrade itself
- let it boot into newly installed 1.2.x
- register nook once again
- turn nook off
- run NookManager again to get root access on new FW
- use 'NTGAppsAttack' to get 'Google Play' on FW 1.2.x
I guess what 'domi.nos' is trying to say is that you could replace your factory.zip (stored in Nook's internal partition) containing FW 1.x with the one containing FW 1.2.x.
After this procedure every time you perform 'factory reset' your nook should revert to FW 1.2.x instead of FW 1.1.x.
Am I right, domi.nos ?
Click to expand...
Click to collapse
I guess I don't understand why the B&N firmware update process itself doesn't upgrade the internal copy used
for a factory reset. Why leave this up to the user to figure out? As a back-out stopgap if the 1.2.x firmware is found
defective?
Presumably 1.2.x has been tested a lot before being issued to the user community. Stop laughing.
After all, by definition, 1.x has been found to be defective, otherwise they wouldn't have bothered issuing 1.2.x.
So how can the possibility of a defect in 1.2.x justify keeping around the known defective 1.x in the factory
reset zip? Plus the Nooks are awesome in that it's impossible to brick them(short of taking a screwdriver blade to
the SD slot).
Does somebody know what their reasoning is for this?
Thanks guys. Updating now!
Just because a new version was released doesn't mean the old one was corrupt. If a new feature was added, that justifies the new release, but the old one was in no way broken.
Also, you have a known working firmware archive, any updates could have corruption, bricking the system if used. From a dev standpoint, best to keep a known good version as backup in case something goes wrong, even if there is a vital update.
Backup
I used a backup from another NST to restore my NST, now I noticed my NST has the same MAC address and ID as the other machine. What can I do to get it's identity back?
Unless you have some backup of your nook, you don't have a lot of options. I have to see if the serial and MAC address are on a label anywhere.
If you can some how find the info, you can mount your image, and edit the files that keep it by hand to show your info instead. This is why dd style images aren't always recommended.
In the future make a back before installing or hacking, and make a backup before attempting to restore. The process isn't always fool proof so it helps to roll back.
steveharr said:
I used a backup from another NST to restore my NST, now I noticed my NST has the same MAC address and ID as the other machine. What can I do to get it's identity back?
Click to expand...
Click to collapse
Sorry, took a while to respond, because I forgot which forum this was on.
Anyway, if you still have the box, the serial number should still be on that.
If you no longer have the box, but you did register it with your account, you can pull it up on B&N's website. Log in, goto "My Nook", and then "Manage My Nook". Mouse over the picture of the nook, and it will show you your serial number.
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.