How to Root GlowLight Nook Touch with TinyNoot (Video)

Nook Glow Rooted

The Nook Touch with GlowLight has been out for a little over two weeks now. The first week a few developers that knew what they were doing were able to root their Nook Glow with a manual rooting method, but that is a little advanced for most people, including myself (Windows doesn’t make it easy).

Luckily there’s now a super-easy method for rooting the Nook Glow thanks to a package called TinyNoot that was put together by Roustabout over at XDA from tools the community has developed in the past year since the Nook Touch was released, including CWM, MinimalTouch, and Touchnooter.

The package doesn’t include Google apps (here’s an install guide for GlowNooter, which does have Google apps), but TinyNoot does root the Nook Glow and installs some important apps needed for a rooted Nook Touch, and comes with the Amazon appstore for easy access to apps. Check out this review of the rooted Nook Glow for a video showing it in action.

After getting things setup with Amazon, I downloaded the Opera Mini web browser and was able to download some additional apps not available from Amazon through alternate appstores.

All in all, TinyNoot does pretty much everything a regular rooted Nook Touch can do minus the Google apps. Plus the GlowLight works!

I was eagerly waiting for something like TinyNoot to come along for the Nook Glow and it is surprisingly easy to use. Here’s my version of the install instructions; the original thread can be found at XDA.

If you want to have access to Google’s appstore, use this alternate rooting guide for GlowNooter instead.

How to Root Nook Glow with TinyNoot

Step #1: Create a Backup

It is strongly advised that you create a backup of your Nook Glow before rooting it or modding it in any way. A backup essentially creates a snapshot of your Nook in its exact current state so you can revert back to it if something goes wrong after rooting or if you want to un-root.

Nook Touch Backup and Restore Guide »

Step #2: Create CWM MicroSD Card

1. Download a clockwork-rc2.zip file from over at XDA to your computer and then extract it. Inside you’ll find an image file. I’m using a 2GB card so I used 2gb_clockwork-rc2.img.

2. Plug a blank microSD card into your computer. If your computer doesn’t have a card reader built-in you will need an sd card reader (don’t use your Nook!).

3. For Windows, open WinImage as administrator and Select Disk > Restore Virtual Hard Disk image on physical drive. Select the microSD card from the list and hit OK. Now locate and select the clockwork-rc2.img file to open (make sure to select “All files” from the drop-down list to get img files to show up). After hitting Yes, WinImage will write CWM to the microSD card.

4. Once that’s finished, download these two TinyNoot files and then place them on the CWM microSD card you just created; don’t extract the TinyNoot zip files.

TinyNoot Part 1
TinyNoot Part 2

Step #3: Using CWM to Install TinyNoot

1. Power off your Nook Glow completely. Insert the CWM card, and then power your Nook on. A clockworkmod logo will appear and then a menu. Here’s how the buttons work:

  • Left Page Buttons: BACK
  • Top Right Page Button: UP
  • Bottom Right Page Button: DOWN
  • “n” button: SELECT
  • Power Button: TOGGLE DISPLAY

2. Use the bottom right page button to move the cursor to “install zip from sdcard” and then press the “n” button to select.

3. Now select “choose zip from sdcard” and install the tinynoot-1-of-2-.zip file first to root. Scroll down to Yes to confirm.

4. Once that’s done “choose zip from sdcard” again and then install the second tinynoot package, 2 of 2.

5. After both TinyNoot packages are installed, use a left button to back out to the main CWM menu and then remove the microSD card and select to “reboot system now”.

Tip: Once your Nook Glow loads the first time after rooting, make sure to check the small box when asked to “complete action using” and then select ADW launcher. That way you can get to the Android homescreen by default and use the “n” button to bring up the menu to go to the regular Nook’s homescreen.

Tip #2: Before you can install any apps, you need to open the Nook Color Tools app and then uncheck and recheck the “Allow non-Market apps” box.

Here’s a video tutorial for those of you unfamiliar with how CWM works, along with a couple of getting started tips. I’ll post an in-depth video review showing the rooted Nook Glow in action in a day or two. Update: here’s the link to the rooted Nook Glow review, plus tips and tricks post. It includes a 10 minute video showing the rooted Nook Glow in action.

Video Tutorial: Using CWM to Install TinyNoot

TinyNoot for Glowworm

Related Articles:

34 Responses to “How to Root GlowLight Nook Touch with TinyNoot (Video)”

  1. After flashing zip 1 of 2, I recommend a restart of the device (without removing the card.)

    this is because the last commands in zip 1 are
    unmount(“/data”);
    unmount(“/system”);

    zip 2 does include the mount commands, though, so it may be possible to run the two commands back to back, but the advice from the developers of minimal nooter, which my method derives from, is to do a reboot between the flashes.

    However, they also recommend a full boot sequence (since they’re trying to set up gapps.)

    It may be possible to collapse both of my files into a single installer. It would take me some time to test that, though.

    • Thanks for the heads-up Roustabout. I added 3b to the directions about rebooting to be on the safe side. I did it twice without rebooting (I screwed up the first video and had to start over again) and it worked okay, the re-mount must be doing the trick.

  2. You devs are amazing. Thanks for the post Nathan. If only I had a PC instead of a Mac.

    Also, thanks for your 10.1 inch tablet advice. Much appreciated. I think I will go with the Asus.

  3. FYI, I’m not a dev so much as a cobbler. I’ve had about one original thought. This rooting package is cobbled together from the minimal touch team’s packages and from various Android apps.

    You can do this from a mac — the hardest part is writing the clockwork disk image, and you do need make the mac NOT unzip the rooting tools (which it will by default; they have to be zips.)

    There’s a discussion of how to do it that touches on doing it from a mac in this thread:

    http://forum.xda-developers.com/archive/index.php/t-987735.html

    The most reliable way to do it on a Mac will be to open up the terminal and use dd.

  4. Thanks for the info roustabout! I was under the impression that only PC users could tinker with this stuff. I will take a look.

    Again, you are still amazing! Thanks!

  5. I might get the Glowlight Nook Touch and root it, but I want to be sure of its capabilities first. It has am infrared touch screen, a virtual keyboard, wifi, a browser, and runs Android 2.0. It cannot play audio. Can it read, send and compose E-mail? Can it run Froyo or higher, and can it handle useful Android apps?

    I planned to get the Iriver Story HD, which is similar to Nook Touch only it has a physical keyboard in place of a touch screen, but it does not run Android and I am not sure if it can do E-mail or notes. I decided to go the route of Android, audio, faster processors and connectivity features, rather than E-ink or high-end color screens. My second choice would have been the Kobo Vox, were it not for its mediocre specs. Android ICS is attractive, so is Bluetooth and “USB On-The-Go”, but these are not available for Kobo Vox, Nook Touch or other E-ink readers. (Or are they?)

  6. The iRiver Story HD is an android device, but there’s not much of a modding community around it. It has a 1024×768 display, though – the NST/NSTG/Kobo Touch all run 800×600.

    I think you must be referring to the Kobo Touch? The up side to the Kobo is that a lot of things which require root on the NST are apparently just there – a web browser, for example. There is a modding community for the Touch, mostly focused around the mobilereads forums, it looks like.

    ICS isn’t available for any e-ink device that I know of.

    The NST/glowworm are running android 2.1, not 2.0 and are the group of devices I know most about.

    There was a while when I was running gmail on my NST, but abandoned that – others still do. Be aware that until gapps are ported to the glowworm, mail client support won’t include the gmail app but looks to include k9 and other mail clients.

    On the NST, USB host mode has been enabled, meaning you can attach a keyboard. The USB host mode, combined with a USB to bluetooth dongle, opens up support for audio; there’s an active project on the host mode support over at XDA and there is a dev working on audio – the nice thing is that a lot of the Android kernel was left intact.

    My impression is that host mode is still kind of buggy and probably won’t be available for the glowworm for a bit.

    On the up side, the glowworm is selling fast so there may well be a resurgence of devs with the devices – or not, because the straight NST is so cheap now that that may get more focus.

  7. Have you determined if this affects battery life yet?

  8. I’d go with the gloworm for its E-ink, touchscreen and Android system. I wouldn’t bother about audio or an external keyboard. It should have a virtual keyboard, right? I can do without the E-mail, just having reading and writing would be fine.

  9. This is a great article. I tried it step by step and I can get all the way to the rebooting part. However, when I boot er’ back up my NST/G just flashes the glow light on and off and never gets past the screen with the five dots. I tried a factory rest (holding the two lower bars and all) and I still can’t get past the “5 dot” load screen. Any help with this would be greatly appreciated.

    Oh, and if it matters I tried the TouchNooter.img before I tried the TinyNoot steps here. Perhaps that is how I messed it up. If I can’t figure this out I have a pretty expensive rectangular coaster. Sigh..

    • Using Touchnooter first definitely screwed something up. There’s usually some way to get your Nook back, even if you didn’t make a backup, which it sounds like you didn’t. But I don’t know of said fix. Maybe if you could find a Virgin copy of the 1.1.5 firmware…

  10. Nathan, I did find the 1.1.5 factory.zip and used the clockwork RC2 from this article to “reset” it back. Once it was working again I followed this post again and she’s working! Glowlight is even working great. One thing I am worried about… Is it possible for someone to post a “hacked” factory .ZIP with some kind of spyware that would capture my personal information as I access Amazon, Google Apps, etc?

    Here is the ZIP file I used:
    http://www.mailpen.com/download/factory-1_1_5.zip

    Here is the post that I got it from:
    http://forum.xda-developers.com/printthread.php?t=1623616&pp=50

    Perhaps I’m just being paranoid. I’m new to this. Also, is it normal to see popup messages asking to “allow super user access” when I open some of the apps on the app tray? Thank you so much for responding to my comment. My Nook ST/G is better than ever!!

  11. Excellent that you were able to restore. You probably could have done so also using the 8 failed boots method. Touchnooter applied to unsupported devices is annoying but doesn’t muck around with the recovery partitions (nor does tiny nooter.)

    The superuser dialogs are normal. You can get rid of them, but doing so wouldn’t be a great idea – you’ll only see them the first time you launch an app, if you leave the “remember this” tickbox ticked. It’s a good idea to be aware of which apps are asking for superuser rights.

    The factory.zip file you downloaded was posted by Dean Gibson, one of the folks I learned a great deal about clockwork from. Anything is possible, but I’d put Dean installing malware in that file extremely low on the probable list. I’d trust Dean more than myself not to miss a command and screw things up!

    Now, bear in mind that much of the rest is somewhat tongue in cheek, mostly intended to get you to think about relative risks:

    Speaking of unknown files grabbed off the intertubes and running your device with them – have you unpacked the zip files for rooting that I posted, to confirm that at least the filenames are what I said they were? Did you read the scripts in tinynooter to be sure I wasn’t practicing malicious script-fu?

    My clockwork script could have pumped your nook full of parasites and it’s much more likely to be used than Dean’s factory.zip – many folks who wanted factory.zip know how to poke into a file and were looking into that file specifically to see what-all was on the glowworm.

    Mine, on the other hand, could be part of my nefarious plot to use the glowworm platform to launch my attack on NORAD and retrieve nuclear launch codes and store them as footnotes to Ann of Green Gables in your library. :)

    There was and is almost certainly a copy of factory.zip on own device. When you boot from noogie you should grab it. (you were, I hope, planning to make a backup of your glowworm?) Look at the third partition. There’s a copy of factory.zip there; if you’d like, you can reflash and reroot using that as your basis (also grab rombackup.zip, as that has files you’ll want to have access to if you truly flatten your glow!)

    Once you’ve done that, you can backup your device from a state that you know all of the files on and only need to worry about the set that I got you to copy in, that put up dialogs frequently while you use your device :)

    (the clean, known, and you owned it start state assumes that the CWR restore process did not copy Dean’s file into that partition; I don’t think it does, I think that it just runs the commands in the factory.zip file, which amount to format /system, format /boot, copy in /system, copy in /boot. It certainly would not be a bad idea, even now, to do an erase and deregister – that will format /data and any remaining, possibly unwanted, add-ons from touchnooter will be removed that way.)

    -rwxrwxrwx root root 116428373 2012-03-28 05:04 factory.zip

    is the creation date and size on my copy of factory.zip.

    Again, I’m glad your device is working and you have it rooted – just bear in mind how much you paid for tiny nooter and what the warranty on it read : )

  12. Thanks…what great instructions!!! Worked perfectly first time through.

    Any idea when Android Marketplace-Google Play will be available for the Nook STG?

  13. The first glowlight root from Gabrial D (touchnooter) is now available, with Android market support.

    Check it out at

    http://forum.xda-developers.com/showthread.php?t=1675706

  14. Tried to root my Nook Simple Touch yesterday. All went fine but I could not install none of the apps I downloaded from 1mobile. Always the same error – “Parse Error. There is a problem parsing the package”. I tried to uncheck and recheck the “Allow non-Market apps” box several times without any effect. I could not install any of the applications I had on the SD card – no file browser installed during the rooting (or is there one).

    Rooted nook was in every other respect functioning just fine. Can somebody tell me what went wrong?

    Many thanks and a nice day to you all,

    Peter

  15. I’ve rooted using tinynoot and am quite happy with it. I am just curious though, if I wanted to do the new GlowNooter would I have to restore back to the stock image first? Thanks.

  16. it says access denied when writing the img file…

  17. Hey Nathan. Thanks for the clear directions and video. When I try to download the browser or the other apps you mention from the Amazon Appstore, they don’t appear in myapps or in the app drawer(?). A blank message pops up after attempting to install.

  18. That is really interesting.

    When you refer to myapps, you’re referring to the menu choice that pops up after launching the Amazon appstore and viewing only the apps tied to your account? I don’t know of a myapps section that’s available in the launcher which is why I’m trying to sound out which myapps menu you’re referring to.

    Has the Amazon appstore app offered to or tried to update itself? They regularly update that tool – I wonder if it needs to update on your device. My NSTG Amazon appstore is currently at release-2.6.53 and seems functional. I installed it with tinynoot, and remember that it wanted to update itself relatively early on.

    If I’m right that you’re referring to the Amazon appstore’s “my apps” menu, it sounds like a login problem at Amazon – if there’s nothing visible in that menu, I think Amazon doesn’t have those apps ‘on file’ for you.

    Have you tried logging into your amazon account on a different device, adding a free app for download to your nook device, then firing up the appstore on the Nook?

  19. Hi, Thanks for the instructions.

    My question is: Can I root the Nook before registering it with B&N since I live outside of US and I dont have a US billing address? Basically, can I start the rooting right after I take the Nook out of the box and will it be able to download the free B&N books after rooting?

    Thanks a lot.

  20. Hey!

    Is there any way that the Nook Glow might be getting USB Hostmode support anytime soon? I want to type with a really light keyboard!

  21. I followed this guide to remap the Nook’s hardware buttons:

    http://forum.xda-developers.com/showpost.php?p=18113297&postcount=4

    Changed the left next/prev buttons to volume up and volume down so that I can scroll pages with Kindle and Mango (both have to be enabled in the app’s settings)

  22. how to install coolreader and other apps?
    I can’t install apps

  23. Hey Nathan, I have the same trouble that John. I first tried to root with the GlowNooter but after the install gets freezed in the reboot. So I tried with the Tiny root and works fine. Yet, as John I cant install anything from Amazon Appstore (after re-checking the thing of tutorial), a blank banner pops up and stops the installation. After I tried by installing apks or appstores from the other suggested websites and when I open the downloaded file (from the nook browser) pops up a banner saying “parse error. ther is a problem parsing the package”)… :(

    So finally I can install no applications… there is any other way to instal .apk without a browser, say from the SD Card, but I have no file explorer yet….

    Any ideas?

    cheers