Database Users

[How To] Root

TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43

Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?

adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome

Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.

Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer

point me to some functioning samsung drivers and I can do this!

If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.

Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?

Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine

For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)

NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"

OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse

Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.

Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks

rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!

Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again

Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.

Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks

Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.

For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related

[Q] USB Host for non-techs

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

[Q] Rooting newer Nook version: how to know which software?

I have a Nook Simple Touch Glowlight with software verion 1.1.5. All the information that I've been able to Google is for 1.1.2, in fact that is the version that I still see on the B&N website.
I _think_ that I have found a suitable way to root the device with Nooter but I would like to know how to confirm that in fact this is the right project for my software version. I'm sorry that I cannot post a link to the Nooter project, but I have less than 10 posts.
Thanks.

There are at least two methods that work with the Glowworm.
You should not use any method until after you have
- made a noogie disk
- booted from it
- backed up your device
- restored that backup to a test disk (a 2 gig or larger microSD card, for instance) and confirmed that the test results in a disk that has 8 partitions.
Many people have made the backup but not tested it; when they tried to restore, they did bad to fatal things to their devices. A very common failure on restore seems to be only getting one partition restored and blowing out the other partitions.
I don't know if the stuff that eded is working on has come to fruition yet - he was looking at building a tool that could detect whether it was run on an NST or NSTG and root appropriately to the device.
The two routes I know work are:
- glownooter, the nooter project tool, includes Google apps and market support
- tinynoot, pasted together from various tools, gives you minimal root without google apps and with amazon appstore. Will work with either NST or NSTG because it's approach is so minimalist.

Thanks, roustabout! I will be sure to test the backups before I install anything else, then. Good to know!
In any case, what I am most concerned about is getting the right version of the rooting software for my device. I see that Nook devices have different firmware and that certain tools only work with certain firmware versions. I see no mention of my firmware version in any tools' websites, hence my apprehension.

hence the value of a backup
I saw your request on that and I think one of the issues here is that so many folks use Windows exclusively, and the backup process is so easy on linux that trying to tell people how to do it in Windows is like jabbing yourself in the eye with a stick, given that linux is free, vmware player is free, and linux can be installed and used for this job entirely in vmware player. On the other side of the coin, if you know nothing of linux, even using dd correctly will be a challenge since there's a pretty steep learning curve behind setting up a new OS successfully just to be able to get backups off an 80-130 dollar device.
In your case: as of now, there is only one firmware release for the glowlight. This is why the folks with the tools aren't mentioning it, aside from 'this is for a glowlight.'

I didn't mention it, but I also use Linux at home (Kubuntu, like Ubuntu but with a better UI). So many people are now using Ubuntu that I find it surprising that the instructions even bother mentioning the OSes for which the operation is as difficult as you say. I remember when doing things in Linux was hard and Windows was easy, and at that time Linux was hardly ever mentioned!
In your case: as of now, there is only one firmware release for the glowlight. This is why the folks with the tools aren't mentioning it, aside from 'this is for a glowlight.'
Click to expand...
Click to collapse
I did not realize that the 1.1.5 release is glowlight-only. Great, thanks, I'm on to hacking this thing!

ok, so for you the backup process is:
- make the noogie disk
- put it into your device
- power cycle your device
- when it boots to "rooted forever," connect the USB cable to your linux box
- once the linux box mounts the NSTG as storage, pay attention to which device it is mounting it at. Assuming it's sdX:
- backup with dd if=/dev/sdX of=backup.img bs=1M
When that's done, disconnect your NSTG, throw media of some sort, larger than 2G, onto your box and test your restore with
dd if=backup.img of=/dev/sdY bs=1M
Once that's done, do an
fdisk /dev/sdY
and a
p to print the partition table.
You should have 8 partitions (and your backup.img file should be just under 2 gig.)
Hack away; if you ever need to restore, you can just drop the virgin image back on.
I take a snapshot like this of my device every so often since remembering how I got to whatever config I liked is harder than just backing it up.

Thanks for the backup instructions, the idea of testing it on a DVD-ROM looks to save quite a bit of trouble with the actual device..
I rooted with this terrific guide:
http://forum.xda-developers.com/showthread.php?t=1675706
The process was simple. I do have an issue where I need to install a Hebrew font but ES File Manager doesn't seem to see the root folders. I'm having a hard time googling my way out of this one, bu all the other little issues were fairly simple.
One issue that I will mention that was hard to solve was the inability to perform searches in the Market. This page helped me resolve that issue:
blog.the-ebook-reader . com/2011/07/15/rooted-nook-touch-fixing-market-search-and-other-tips-and-tricks-video/

I just figured out that the file manager has to have Root permissions enabled. I've enabled it and added some fonts to /system/fonts but I still cannot get Hebrew text to display on this device. All I get are the typical rectangles instead of characters. Any ideas about how to proceed?
Thanks.

Restore Nook 1.1.2
roustabout said:
Many people have made the backup but not tested it; when they tried to restore, they did bad to fatal things to their devices. A very common failure on restore .
Click to expand...
Click to collapse
1. I made this exact same mistake yesterday and I ended up with a bad backup.
2. My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempted to restore the backup (which I didnt know was bad at the time)
3. Please help me restore the Nook back to factory or any working state. Are there any restorable backup images that can be downloaded online?
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)

bubblewrapper said:
1. I made this exact same mistake yesterday and I ended up with a bad backup.
2. My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempted to restore the backup (which I didnt know was bad at the time)
3. Please help me restore the Nook back to factory or any working state. Are there any restorable backup images that can be downloaded online?
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)
Click to expand...
Click to collapse
Few people who will be knowledgeable will find your post buried here under this thread. i suggest that you simply start a new thread with a good descriptive title so that the gurus will find it.

Not sure how to get hebrew working. One assumes that in addition to the characters, you need it to right to left? If it's the latter, I know there was a thread discussing doing this with Arabic, and I'm not sure how that turned out. You can also google around for folks looking at this on, I think, mobilereads.

roustabout said:
Not sure how to get hebrew working. One assumes that in addition to the characters, you need it to right to left? If it's the latter, I know there was a thread discussing doing this with Arabic, and I'm not sure how that turned out. You can also google around for folks looking at this on, I think, mobilereads.
Click to expand...
Click to collapse
Actually, I think that I just need the fonts (or at least that would be a great first step). I put fonts with Hebrew glyphs in /system/fonts (using ES File Explorer in Root mode) but even after a restart it does not find the fonts (i.e. Hebrew text still shows as rectangles). I will fight with it some more in the coming days, if I don't succeed I will start a new, concise thread on the topic. There are plenty of Google posts on the subject, but all of the ones that I have seen (not Nook-specific) suggest that dropping the fonts is /system/fonts should be enough. Perhaps it is a permissions issue, I'll see if I can SSH into the device to see permissions.

dotancohen said:
I have a Nook Simple Touch Glowlight with software verion 1.1.5. All the information that I've been able to Google is for 1.1.2, in fact that is the version that I still see on the B&N website.
I _think_ that I have found a suitable way to root the device with Nooter but I would like to know how to confirm that in fact this is the right project for my software version. I'm sorry that I cannot post a link to the Nooter project, but I have less than 10 posts.
Thanks.
Click to expand...
Click to collapse
Sorry that I am so slow to respond, but I think this is the information you need to root a Nook with Glow on version 1.1.5
It uses Glownooter
http://blog.the-ebook-reader.com/20...using-glownooter-includes-googles-app-market/
and this is the backup routine
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/

ladykayaker said:
Sorry that I am so slow to respond,
Click to expand...
Click to collapse
Thank you! You don't need to apologize for taking time to respond, you are under no obligation! But I very much do appreciate your assistance and am happy to wait patiently! You will notice that I usually google issues first to try to save us both the time!
I think this is the information you need to root a Nook with Glow on version 1.1.5
It uses Glownooter
http://blog.the-ebook-reader.com/20...using-glownooter-includes-googles-app-market/
and this is the backup routine
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
Click to expand...
Click to collapse
Thank you. It seems that those posts are Windows-centric summerizations of information found here at XDA-developers. The root is pretty much the process that I used, but from the guide right here which has Linux directions as well.
By the way, the-ebook-reader site is often not responding for me. Is it just for me, or does everyone have trouble with that site?
Thanks!

version 1.2.0
UK glowlight ships with 1.2.0. Use tinynooter to root this. You may have issues installing apps atm though but you will get the browser at least.
http://forum.xda-developers.com/showthread.php?t=1961835

Thanks, Loney. In fact, I got this Glowlight in the US, and it reports that it has software verion 1.1.5. But the information will be good for others who might google this thread!

Nook Simple Touch Glowlight .. Need advice before rooting.

Hello all ...
Please .. I need some advice..
This is my first post. My sister has given me her Nook Simple Touch Glowlight. I would like to root it, as I've been looking for a device to keep notes and stuff on. I went as far as booting up with noogie.img and backing up the firmware. I don't know what to do, because I read that having a certain firmware changes everything? I don't think my sister updated the nook. Here is the information from the Settings / Device Info / About Your Nook.
Software Version: 1. 1. 5
Model Number: BNRV350
I read someplace that the sizes of the firmwares are different. The simple touch is 1. 82 and the simple touch glow is 1. 86.
Mine is 1 .82, but yet it has the glowlight? It says to hold the button down for two seconds to turn it on.
I see that B&N have new firmware for the nst & nstg. 1. 3 I believe. It said on the site that this firmware would be installed when the nook is idle. (via wifi) Anyway, I'm wondering if it would be ok to go ahead and root the thing, or upgrade the firmware first to maybe - 1. 2 (if I can find it?) before I do anything else? Oh and should I stay away from B&N's new 1. 3 firmware?
Thank You Very Much !!
WillyS.......

If you indeed have the Nook Simple Touch with Glowlight (black bezel), then the most recent stock firmware is 1.2.1 which can be downloaded here. I would recommend that you update to this as the first thing you do. Next you need to decide which of the multitude of rooting methods is best for you. You need to take into account what you wish to achieve by rooting the Nook and your skill/comfort level with the processes. I have followed many of the different processes, doing a factory reset between root versions. By far the easiest is Nook Manager. I, personally, prefer the Minimal rooting - back to basics method because it allows you to install just what YOU want. However, this method requires a fair amount of command line work.
EDIT: I made the assumption that you are in the US and have a US model. I believe there is a different firmware number for the international model. In any case, you should update the Nook to the most recent firmware before rooting.

Rooting nook .. Glowlight ..
Hello David and Thank You kindly for the reply!
Yes, mine is a Canadian version and it has the black bezel.
Thank you .. for correcting me on the firmware. I was looking at the wrong Nook version. (nook.barnesandnoble.com/u/software-updates-nook-glowlight/379004086)
I downloaded the correct 1. 2. firmware for the nook and I (like you) would rather install what I want to and have more control over what gets put on it. After I update the firmware, I'll come back and follow the links you provided. If you know what threads have the latest / newest info on rooting the nstg, can you please point me to it? (If you haven't already) Thank You Very Much for your help .. David.
Cheers
WS

You're welcome. If you are comfortable with a lot of manual, command line manipulation, start with the Minimal rooting - back to basics thread. There are many more and newer rooting methods, but each of them installs a bunch of apps that the creators use, which may or may not be of importance to you. If you start with the Minimal rooting - back to basics, you can then pick and choose the apps and modifications you want to apply to give you the best experience for YOUR needs. I am attaching the document I use to keep track of what I have done for your reference. Feel free to post any questions here.

Rooting Nook STG .. Firmware 1. 2 ...
Hi David and Thank You for the reference document.
Last night I downloaded 1.2.1 firmware and dumped it on the Nook. When I got up this morning I checked and 1.2 is installed. I looked around and found a 16gb Kingston (from GPS) SD-Card. It is only class 4, but it should be usable for the time being. I'll take a look online for a class 10. I don't know if there is any size, or class limitations, or not?
I'm at the rooting - back to basics thread. I'm going to read all this stuff over and see if I can figure it all out. Thanks again for your help and the document.
WS...

WillySizard said:
...
Last night I downloaded 1.2.1 firmware and dumped it on the Nook. When I got up this morning I checked and 1.2 is installed. I looked around and found a 16gb Kingston (from GPS) SD-Card. It is only class 4, but it should be usable for the time being. I'll take a look online for a class 10. I don't know if there is any size, or class limitations, or not?
...
Click to expand...
Click to collapse
Class 4 should work just fine. Since noogie only takes ~2GB (if I remember correctly) you don't really need a card any larger than 4GB to use this method of rooting. Having 8GB or 16GB card would be useful if down the road you will make use of the card to backup your Nook ROM & user-content for ease in recovery.

Don't really know where to go from here, or what to do ..
@ digixmax .. Thank You for the info on the SD-card. Good to know info!
@ david0226 .. I went to the page about rooting via the link and I have basic
understanding how / what needs to be done, but I'm not having much
luck finding and using the tools. I went and looked for the file used to
extract the 2 files from uRamdisk, but I couldn't find it. I did some reading
and looking around and found a program called Preboot (I think) by
Intel and it contained bootutil 32/64 and so on. I had to install preboot & then
uninstall it, to get bootutil and then install it. I tried using it to extract
the files, but I kept getting failed messages. Like invalid switch /x.
Invalid switch /v. Invalid file uRamdisk. I know I need to extract out 2
files: init.rc and default.prop. I tried to do so in the "Administrative Command
Window" on Win7_64bit, but it just wouldn't work with bootutil. Not the
one I had anyway. Any ideas? Thanks!
WillyS......

David0226 said:
...
I am attaching the document I use to keep track of what I have done for your reference. Feel free to post any questions here.
Click to expand...
Click to collapse
What extensions does "Extended Power Menu" provide?
Also, which uImage and uRamdisk do you use as uRecImg and uRecRAM?
TIA.

Here are the links to the relevant threads.
Extended Power Menu
Clockworkmod based Recovery post #75, see the entire thread here.
If you are going to do the Extended Power Menu, be sure to do the Clockworkmod based Recovery also or you risk wiping out everything you have done by accidentally hitting recovery in the Extended Power Menu. I you have installed Clockworkmod Recovery and accidentally hit "Recovery", it will just boot to Clockworkmod and give you a chance to back out.

@willys. I will have to look up the software I use and post tomorrow. Sorry I missed your question earlier.

@willys, I believe the program you want is "bootutil" which was written and shared by Renate NST. If you find a post by her and click on the yellow box in her signature, you will find links to the many custom programs she has written for rooting and managing rooted Nook Simple Touch devices.

David0226 said:
@willys, I believe the program you want is "bootutil" which was written and shared by Renate NST. If you find a post by her and click on the yellow box in her signature, you will find links to the many custom programs she has written for rooting and managing rooted Nook Simple Touch devices.
Click to expand...
Click to collapse
Yes, I had to go to her profile and I found it there. I'll do this part first and see how it goes. After that (I think?) I need to get an android program (some kind of Installer maybe?) to do some other work with. Anyway, one step at a time. All for now. Thanks! ... WS.

digixmax said:
Class 4 should work just fine. Since noogie only takes ~2GB (if I remember correctly) you don't really need a card any larger than 4GB to use this method of rooting. Having 8GB or 16GB card would be useful if down the road you will make use of the card to backup your Nook ROM & user-content for ease in recovery.
Click to expand...
Click to collapse
Class 2 and 4 will do just fine, in my case I used 520 Mb microSD card for installing various ROMs, tried quite a lot of them, always worked fine.

Almost done, but need a little more help . . .
Mnurlan said:
Class 2 and 4 will do just fine, in my case I used 520 Mb microSD card for installing various ROMs, tried quite a lot of them, always worked fine.
Click to expand...
Click to collapse
OK .. Thank You Mnurlan!
@David0226 ...
Just getting to the point where I'm ready to add programs. have edited uRamdisk and re-installed the two files. I've download android-sdk package and have installed it. I have been in the nook via wifi using ndb shell as root. I am now following your notes file. I've created the archive folder on the nook - /system/archive and I've been moving files over from /system/apps folder. I got Nook Manager written to the sd-card and I have PackageInstaller.adk from it, but I I'm not sure how I get that onto the nook. When I boot with NookManager, it ask if I want to root. I have already done that and it is working. Should I let it do it anyway?
Thank You!
WillySizard . . . .

@WillySizard ...
Connect to the Nook with adb then exit the adb shell back to your Windows command prompt. Once back at the command prompt, you should be able to install any package using this command ...
adb install {package_name.apk}

Nook Simple Touch Glowlight .. Need advice before rooting ..
David0226 said:
@WillySizard ...
Connect to the Nook with adb then exit the adb shell back to your Windows command prompt. Once back at the command prompt, you should be able to install any package using this command ...
adb install {package_name.apk}
Click to expand...
Click to collapse
Ahhh .. ok. Good enough then. That should get me off and running.
Thank You .. David. Sorry I'm being such a pest.

Me, also
Just paid $5 for a BNRV350 at a rummage sale.
I understand BN disabled the web browser with the current operating system.
I can get a Google search window (by repeated tapping on the "Google" or maybe the "404" or the "that's all" links that appear when I try the "connect to social" settings menu choice for Google. And "find my account" worked when given the Gmail userid (because the keypad on the Nook lacks a period for typing a proper email address, in this view).
And I can get a Twitter login page. Neither works well -- typing even a single letter into the password field resets the page, so it's letter, then tap in the field window, then another letter, then tap in the field window. Sometimes it shows a row of dots for characters already entered, other times those are invisible but the entries are still there.
Just curious to add to the above fellow's thread for anyone searching for this Nook model number, if anyone has advice or suggestions about making it useful.
Reverting to the original OS to have use of the web browser would be a welcome option, if that's possible. Pointers welcome. Right now this Nook has version 1.1.5 installed -- I gather that's one of the improved versions that killed the stock web browser.

Fix - Apps and websites not working after certificates expire

As identified in this post http://forum.xda-developers.com/showpost.php?p=65344931&postcount=10 lots of apps and websites have stopped working over the past year or so (depending maybe on your ROM). This has been traced to the root certificates (used to trust websites and set up secure ssl connctions) becoming out of date. Modern devices also have many more root certificates installed by default.
Note that this doesn't fix the google market on the nook touch, nor the kindle book store. It does fix the kindle app for syncing books purchased elsewhere.
I'll port the instructions over into this post later (see the link above for now). It requires root (so is slightly risky).
If you identify any more failing sites, please provide an https link which fails to open on the nook (but does work on a PC) and I'll add the root authority to my files. Anyone working on ROMs is welcome to redistribute my cacerts.bks

<reserved>

Aargh!
tshoulihane said:
As identified in this post http://forum.xda-developers.com/showpost.php?p=65344931&postcount=10 lots of apps and websites have stopped working over the past year or so (depending maybe on your ROM). This has been traced to the root certificates (used to trust websites and set up secure ssl connctions) becoming out of date. Modern devices also have many more root certificates installed by default.
Note that this doesn't fix the google market on the nook touch, nor the kindle book store. It does fix the kindle app for syncing books purchased elsewhere.
I'll port the instructions over into this post later (see the link above for now). It requires root (so is slightly risky).
If you identify any more failing sites, please provide an https link which fails to open on the nook (but does work on a PC) and I'll add the root authority to my files. Anyone working on ROMs is welcome to redistribute my cacerts.bks
Click to expand...
Click to collapse
I've been using your updated cacerts.bks file and it is great. In January another certificate expired and I'm fairly confident it's the reason a news app (News Republic) started throwing up security certificate errors and refused to connect with the server. I think I need to be able to do the certificate updates, but I am trying to avoid going down the SDK road (a massive download I will never use for anything else) and all those complexities.
Except, nothing else seems to work. There is an ancient thread in which people discuss various ways to update pre-ICS cacerts. Unfortunately, none of them work--I've tried them all. The browser idea seems promising and Opera Mobile responds as described, but then nothing happens to the cacerts.bks file.
Portecle looks really promising (images below). It can obviously open and inspect the cacerts.bks file (password: changeit). It shows the additions you made and also indicates the expired certificate.
So I went searching for a replacement and found something that seems like the right thing (attached as a zip). It imported easily into Portecle and then appeared along with the new ones you added.
Then I returned the file to the NST and made the permissions the same as the old file. A reboot put me in a loop out of which I just barely managed to recover by inserting my NookManager card at just the right moment.
So I don't get it. The bouncycastle files recommended in the CAcerts wiki for this task are too old to be available. Surprise.
I'm tempted to NOT fix the permissions on the cacerts.bks file when I return it to the NST because I once had a similar problem with a settings.db file and it turned out that restoring the "correct" permissions resulted in a bootloop while leaving them as they were when the file was copied back made it all work just fine. But I'm too timid to try that just now.
Any insights?

From my linked thread,
Download http://www.bouncycastle.org/download...dk15on-146.jar - this is used locally on your PC to manipulate the certificates and needs to be version 146 or 147 to work with android (or old android at least)
Click to expand...
Click to collapse
It seems that when I used a different version, I got a bootloop. Although the link I referenced seems to have died, the filename still turns up plenty of hits. http://polydistortion.net/bc/download/ for example (version 1.47).
I agree its a lot of pain, and I'm not sure I still have the toolchain download that I used for this work. I'll have a dig around...

tshoulihane said:
From my linked thread,
It seems that when I used a different version, I got a bootloop. Although the link I referenced seems to have died, the filename still turns up plenty of hits. http://polydistortion.net/bc/download/ for example (version 1.47).
I agree its a lot of pain, and I'm not sure I still have the toolchain download that I used for this work. I'll have a dig around...
Click to expand...
Click to collapse
Yipes. Well, I downloaded the jar file (many thanks...I did search on the file name and came up empty) and followed your example on the other thread. Everything behaved as it should. Except for the boot loop....... This time it was even harder to get out of it.
Two possibilities come to mind. My JDK is 1.8.0_73. Maybe that's too new to work properly. The other is that the certificate, despite playing nicely as far as console feedback went, is of the wrong format, although this does not show up in the feedback or in Portecle.
Anyway, I'm sufficiently intimidated now that I'm not going back there unless I have a better way of getting out of boot loops (since I'm doing ADB over Wi-Fi).
Edit: temptation... So I went back to the CAcerts Wiki and noticed they suggest Java 6. Now, of course, the Wiki is old, but so is the Java underlying the NST, so I found an install of Java 6 and put it on the laptop we have attached to the TV (which runs Kodi and very little else). Then I repeated the entire procedure with--supposedly--all the right components. Same dreaded bootloop. So either the certificate I have has an incompatible format, or I am just hopeless at this. Maybe both

all of the old bouncy castle api releases are archived on their ftp server under ftp://ftp.bouncycastle.org/pub. i managed to find the .jar files referenced in the other thread on there and updated my cacerts.bks using the cacerts wiki instructions a few days ago. hope it helps you. using the newer release gave me a bootloop as well, but once i grabbed the older version from their ftp all was good!

shadylady said:
all of the old bouncy castle api releases are archived on their ftp server under ftp://ftp.bouncycastle.org/pub. i managed to find the .jar files referenced in the other thread on there and updated my cacerts.bks using the cacerts wiki instructions a few days ago. hope it helps you. using the newer release gave me a bootloop as well, but once i grabbed the older version from their ftp all was good!
Click to expand...
Click to collapse
Which java version were you running?
Edit: Hmm....I'm not having any luck with the link you provided. Using an FTP client I am asked for a logon and in my browser (Firefox) it never connects.

Here we go: http://www.bouncycastle.org/archive/
Remains to be seen if that will do the trick for me...

the bootloop version was whatever bouncycastle.org has as their latest release.
the one i downloaded from the ftp that didn't bootloop was this one: bcprov-jdk16-146.jar
you'll need to ftp in and use the password "anonymous" and some bogus email to get onto the ftp. from that web version of the archive it should be this package: http://www.bouncycastle.org/archive/146/bcprov-jdk16-146.tar.gz
i'm running mac, so my default java was 1.6. i updated to 1.8 but that happened after i got this all up and running already. this was the version that was default:
$ /Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Commands/java -version
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-468-11M4833)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-468, mixed mode)
so jdk 1.6 + API 146 (or 147?) seems to be the proper mix.
at first i thought it wasn't working, because although i updated the cacerts.bks, the amazon kindle app kept saying "incorrect email/password". took me a while before i read the entire thread and realized that amazon now does two-step authentication so i had to enter the one time passcode they had sent to my email.
nmyshkin said:
Which java version were you running?
Edit: Hmm....I'm not having any luck with the link you provided. Using an FTP client I am asked for a logon and in my browser (Firefox) it never connects.
Click to expand...
Click to collapse

Well....progress, or at least I think so. This may be an easier method.
Go to http://www.bouncycastle.org/archive/ and download bcprov-jdk15on-146.jar
Go to https://sourceforge.net/projects/portecle/ and download potecle (an executable jar)
Unzip portecle. Rename the bcprov-jdk15on-146.jar to simply bcprov.jar and copy that into the unzipped portecle folder (overwrite the newer version already present).
To run portecle, just double-click on portecle.jar. You will get a statement about the 146 file being out of date, resulting in not everything working, but enough works for our purposes.
Copy cacerts.bks from your NST (system/etc/security) to your PC, open portecle and import your cacerts file (password is "changeit"). You now have a nice graphical interface for perusing and updating your certificates! If you have a *.cer certificate to update, rename the "cer" to "crt" and use the import function. It's really that simple. I tried it, copied the file back onto my NST, fixed the permissions and.......{drumroll}.......no bootloop I'm running jdk 1.8.x
That's the good news. The bad news is that I did not succeed in updating the entrust certificate. I added three from their website and while they did not break cacerts, they did not restore functionality to NewsRepublic, which is what I was hoping to do
So....this may work. It's certainly easy, but clearly you need to have the correct updated certificate to get the desired result. Duh.
Edit: OK, it's ALL bad news
Don't do any of this. It seems to go OK but yesterday I found I could not successfully open the NPR app. I thought, "well, another one bites the dust", but I was curious so I used SearchMarket to see if the app was still listed for the NST. It was. So maybe it got corrupted somehow? Anyway, I uninstalled it and was going to reinstall from the Market but suddenly I got messages about the download failing. Oh no, not another function going south?!
Well, it's all fine, but the problem was the cacerts.bks file that I had made using the method above. Although there is no bootloop on restart, there is bad ju-ju nonetheless. Restoring my backup of cacerts.bks fixed NPR and SearchMarket. So....don't go there (and the two people who thanked me, feel free to unthank me )