Database Users

[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24 Problem

Hello:
I had a 1.0.0 NST successfully rooted TouchNooter 1.6.24.
Following instructions from this forum, I updated it to 1.0.1:
Using the NST power button, I did a Factory Restore
Then, I applied TouchNooter 1.6.24 using this thread instructions.
Even though it booted properly rooted, and on 1.0.1 B&N NST software, I didn't pass trough the step:
"13. Enable Location Services when given the option."
Also, I even though I am able to connect to Wi-Fi, when I tried to activate:
"14.[...] launch Youtube from Go Launcher's App Drawer"
the YouTube app didn't respond.
However, I am able to open Gmail and sync it properly... but when I open the Market I can't seem to connect to my apps, nor to install new ones.
So here goes the questions ;-)
1) Is there a way to repair this?
2) If not or if is too much of a hassle to do so, how can I unroot my NST back to factory (1.0.0) state? With a Factory / hard reset like this or otherwise?
I don't mind loosing data, since almost all of my books are on a SD Card.
3) After unrooting, registering the 1.0.0 device in B&N and updating it to 1.0.1, will I be able to apply TouchNooter 1.6.24 succesfully again?
Awaiting your kind replies,
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author

For the record, the instructions above on factory reset are incorrect. The 6-8 power cycles method does not format /system (only /data, I think) or return you to the original firmware. This method, however, does. (Note that once you upgrade to 1.1.0, it seems like the backup partition is upgraded to it as well, so unfortunately you'll be stuck with it unless you were prescient enough to make a backup of your Nook's internal drives .)
1. Turn off your N2E completely.
2. Turn it on again by holding down power, and then,
3. as soon as the screen flashes, begin holding down the bottom page turn keys on the left and right of the device until the screen flashes with a message asking if you want to do a factory reset.
4. Click the home key twice, and you should be on your way.
Note that this absolutely destroys your shelves, notes, and other information, and you will be asked to register your Nook with BN again.
Hope this is helpful for people; it took a while for me to come across.

LastSilmaril said:
Hope this is helpful for people; it took a while for me to come across.
Click to expand...
Click to collapse
It is certainly helpful for me! Thank you very much!
I if I understood you properly, this method end with the NST unrooted, yes?
BTW, how do you backup the NST internal drives: simply plugging the Nook to an USB port on a PC and copying the NST internal drive thus exposed or otherwise?
Finally, how does one backups the Shelves information: names, books included in each one and so forth: copying the internal NST drive or otherwise?
Already very gratefully yours,
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author

sarmasm said:
It is certainly helpful for me! Thank you very much!
I if I understood you properly, this method end with the NST unrooted, yes?
BTW, how do you backup the NST internal drives: simply plugging the Nook to an USB port on a PC and copying the NST internal drive thus exposed or otherwise?
Finally, how does one backups the Shelves information: names, books included in each one and so forth: copying the internal NST drive or otherwise?
Already very gratefully yours,
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author
Click to expand...
Click to collapse
I already sent you a PM with the link to backup/restore, but I guess it's worth reposting it here.
http://forum.xda-developers.com/showthread.php?t=1142983
From what I understand, yes, the nook should be factory-fresh afterward.
I do not know of a way to backup shelves separate than the general backup method, which of course, if you are making a backup of a rooted system, will not give you an unrooted system on reboot.

LastSilmaril said:
For the record, the instructions above on factory reset are incorrect. The 6-8 power cycles method does not format /system (only /data, I think) or return you to the original firmware.
Click to expand...
Click to collapse
I'm sorry mate but that is incorrect:
1: 8 interrupted boot attempts (Factory Restore)
- Will extract the factory image onto /system and put you back to 1.0.0
- Will not give you a factory fresh NST
- Will not touch your existing data
2: Booting while pressing left and right bottom buttons (Factory Reset)
- Will wipe all your your /data and settings.
- Will not give your a factory fresh NST
- Will not touch your system
LastSilmaril said:
(Note that once you upgrade to 1.1.0, it seems like the backup partition is upgraded to it as well, so unfortunately you'll be stuck with
Click to expand...
Click to collapse
Triggering System Restore on 1.1 will still put you back to 1.0.0
Open up a adb shell and try for yourself:
Code:
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot

[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24: UnRooting?
Ros:
Will any of the above methods unroot my NST?
If not, how may I unroot it: with nookRestore, otherwise, or not at all?
Awaiting your kind reply,
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author

ros87 said:
I'm sorry mate but that is incorrect:
1: 8 interrupted boot attempts (Factory Restore)
- Will extract the factory image onto /system and put you back to 1.0.0
- Will not give you a factory fresh NST
- Will not touch your existing data
2: Booting while pressing left and right bottom buttons (Factory Reset)
- Will wipe all your your /data and settings.
- Will not give your a factory fresh NST
- Will not touch your system
Triggering System Restore on 1.1 will still put you back to 1.0.0
Open up a adb shell and try for yourself:
Code:
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Click to expand...
Click to collapse
Aha, I must have misunderstood, because I tried using nookRestore, which I though was the same as doing the 8 uninterrupted boots, my nook still looked like it was semi-rooted: I could still access the normal Android launcher and programs. What's more, after I did the L+R reset, I could *not* access the Android launcher, AND the version number had gone from 1.0.1. So I guess something is very screwed up here? This explains why when I did the L+R reset to 1.1 why I still didn't have WiFi though (I didn't know it was still 1.1; just shut it off and restored my 1.0.0 image, which I now understand to be compromise).
Now that I'm on 1.0.0, is there any advantage to using nookRestore again (ADB doesn't work, either by WiFi or USB) to try to get things to work? Or is there no solution to unrooting, whatsoever, unless/until you or someone else releases some sort of customized installer?
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
And I am sorry for misinforming you, sarmasm
-e
---------- Post added at 09:49 AM ---------- Previous post was at 09:39 AM ----------
LastSilmaril said:
What's more, after I did the L+R reset, I could *not* access the Android launcher, AND the version number had gone from 1.0.1. So I guess something is very screwed up here?
Click to expand...
Click to collapse
No, I see what happened. I ran nookRestore, and this got me back to 1.0.0 (I didn't check the version number afterward, so I didn't know it changed) but didn't get rid of the Android launcher and such. THEN I did the L+R reset, and it *appeared* to be unrooted because the uRamdisk was replaced (...right? from your pm), but any modifications elsewhere would still remain.
So again, is there no hope? Running nookRestore again won't do anything, right? I do not know which files touchNooter modified outside of /data and /system (which at this point have both been wiped, since I have already ran nookRestore and L+R Reset)...
Ah, this is frustrating...

LastSilmaril said:
Aha, I must have misunderstood, because I tried using nookRestore, which I though was the same as doing the 8 uninterrupted boots
Click to expand...
Click to collapse
It is the same thing, nookRestore just tricks your NST into thinking it has had 8 failed boots.
LastSilmaril said:
my nook still looked like it was semi-rooted: I could still access the normal Android launcher and programs.
Click to expand...
Click to collapse
Yes, because the launcher resides in /data/app which is not touched by Factory Restore.
The Google apps however, resides in /system/app and should normally be removed by a Factory Restore.
LastSilmaril said:
What's more, after I did the L+R reset, I could *not* access the Android launcher
Click to expand...
Click to collapse
Yes because /data/app is wiped by Factory Reset (L+R)
LastSilmaril said:
Now that I'm on 1.0.0, is there any advantage to using nookRestore again
Click to expand...
Click to collapse
Unless you have something that's not working properly, then no.

[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24: UnRooting?
LastSilmaril said:
And I am sorry for misinforming you, sarmasm
Click to expand...
Click to collapse
No harm done: I'm sitting on my hands, on NST rooting, resetting and/or updating until I get more clear input on the matter.
Thanks for your prompt reply!

[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24: UnRooting?
ros87 said:
It is the same thing, nookRestore just tricks your NST into thinking it has had 8 failed boots.
[...]the launcher resides in /data/app which is not touched by Factory Restore.
The Google apps however, resides in /system/app and should normally be removed by a Factory Restore.
Click to expand...
Click to collapse
So, just to be clear and avoid any confusion whatsoever: using nookRestore (or a Factory restore i.e. 8 interrupted boot attempts) will remove the touchnooter 1.6.24 from my 1.0.1 rooted NST and result in a (as close as possible, user data issues appart) 1.0.0 stock NST, yes?
Awaiting your kind reply,

sarmasm said:
No harm done: I'm sitting on my hands, on NST rooting, resetting and/or updating until I get more clear input on the matter.
Thanks for your prompt reply!
Click to expand...
Click to collapse
Not sure why market isn't working for you but you can always try to do a Restore, Reset, Register, Update to 1.0.1 and then TouchNooter it again, it won't do any harm.
Using nookRestore is probably the simplest way to trigger Restore.
Just don't try to update to 1.1.0 if you want to use TouchNooter as it's currently not compatible with it.

[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24: UnRooting
ros87 said:
Not sure why market isn't working for you but you can always try to do a Restore, Reset, Register, Update to 1.0.1 and then TouchNooter it again, it won't do any harm.
Using nookRestore is probably the simplest way to trigger Restore.
Click to expand...
Click to collapse
Thanks!
BTW, why the Reset after the Restore?
ros87 said:
Just don't try to update to 1.1.0 if you want to use TouchNooter as it's currently not compatible with it.
Click to expand...
Click to collapse
I hear you: I've been following some threads on the matter and it does seems an unstable issue, for the time being.
Very gratefully yours,

ros87 said:
It is the same thing, nookRestore just tricks your NST into thinking it has had 8 failed boots.
Yes, because the launcher resides in /data/app which is not touched by Factory Restore.
The Google apps however, resides in /system/app and should normally be removed by a Factory Restore.
Yes because /data/app is wiped by Factory Reset (L+R)
Unless you have something that's not working properly, then no.
Click to expand...
Click to collapse
I *do* have something that's not working properly When I upgrade to 1.1.0 from 1.0.0 from this, WiFi does not work. I suspect this is due to the rooting.

LastSilmaril said:
I *do* have something that's not working properly When I upgrade to 1.1.0 from 1.0.0 from this, WiFi does not work. I suspect this is due to the rooting.
Click to expand...
Click to collapse
Do a restore + reset + register + upgrade to 1.1
If that still doesn't help, install one of my rooted ramdisks for 1.1 with the Noogie method and do a adb logcat to see what's going on.

ros87 said:
Do a restore + reset + register + upgrade to 1.1
If that still doesn't help, install one of my rooted ramdisks for 1.1 with the Noogie method and do a adb logcat to see what's going on.
Click to expand...
Click to collapse
I did all that and it still doesn't work, but it seems like this is a problem with my router, because it works with a different one. Will doing the 1.1 root and running 'logcat' catch it? Thanks a lot, ros.
---------- Post added at 07:01 PM ---------- Previous post was at 06:35 PM ----------
LastSilmaril said:
I did all that and it still doesn't work, but it seems like this is a problem with my router, because it works with a different one. Will doing the 1.1 root and running 'logcat' catch it? Thanks a lot, ros.
Click to expand...
Click to collapse
LOL, so I did did the noogie ramDisk root, and now, WiFi works without any issues. What part of enabling ADB over WiFi would cause that to happen?

LastSilmaril said:
LOL, so I did did the noogie ramDisk root, and now, WiFi works without any issues. What part of enabling ADB over WiFi would cause that to happen?
Click to expand...
Click to collapse
Hard to say, but I have had similar issues earlier where my NST suddenly would not obtain an IP from a known router, but still work on other routers.
Didn't care to look into it back then and the problem went away on itself.

LastSilmaril said:
LOL, so I did did the noogie ramDisk root, and now, WiFi works without any issues. What part of enabling ADB over WiFi would cause that to happen?
Click to expand...
Click to collapse
Before I give this a try, I wanted to check: do you have ADB working over WiFi after applying the noogie ramDisk root to the 1.1.0 firmware?
Thanks!

[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24 Problem Solved!
Hello:
I've been waiting to see how the TouchNooter situation was resolved for the NST 1.1 update so I hadn't reseted my NST 1.0.1 just yet.
The thing his, yesterday I activated the wi-fi access at home, and just for the heck of it I used the GApp Android Market...
...and it worked just fine: I was able to download and update stuff (Go Launcher, Opera Mini) just as I expected (and wasn't able to) right after the 1.0.1 update and TouchNooter 1.6.24 re installation.
What happened in between? Other that booting normally a few times, which I always had been able to since the 1.0.1 update and TouchNooter 1.6.24 re installation, I sincerely don't know
Go figure... but thank you all for your kind advice and patience.
I'll be now watching closely the 1.1 update + TouchNooter 1.11.11 installation and see if and when will it be GApps (Market) compatible, specially so for those of us which are not very good or at least not dangerous at slicing root folders and files manually
Very gratefully yours,

rooting problem
I rooted my nook simple touch 1.0.1 with touch nooter 2-1-31. After I wrote the touchnooter to my microsd card, I put it in. There were a set of instructions. That told me to wiat until screen flashed, and to then remove the sd card and reboot. I did all that and now it is stuck on the third circle when it is trying to boot up and it flashes and goes from 1 to 2 to3 then flashes and does the process again, can somebody help me? It doesn't work anymore

Nookguy32 said:
I rooted my nook simple touch 1.0.1 with touch nooter 2-1-31. After I wrote the touchnooter to my microsd card, I put it in. There were a set of instructions. That told me to wiat until screen flashed, and to then remove the sd card and reboot. I did all that and now it is stuck on the third circle when it is trying to boot up and it flashes and goes from 1 to 2 to3 then flashes and does the process again, can somebody help me? It doesn't work anymore
Click to expand...
Click to collapse
http://nookdevs.com/Nook_Simple_Touch_restore_to_stock
Don't use TouchNooter with FW older than 1.1.x
You can get the 1.1 update from here
https://code.google.com/p/nst-recovery/downloads/list
(use CWM to upload it to your NST)
Read first, act later etc..

Request for N2E 1.1 Rom Image

I had backup a stock 1.1 image before, but deleted that in an accident....
So, anyone here can help me with this?
I would like to turn the rooted N2E back to stock 1.1 and upgrade it to 1.1.2
Thanks!

Each Nook carries information specific to itself. If we were to give you one of our backups, it would cause problems for you and the person that gave you the backup.

wheilitjohnny said:
I had backup a stock 1.1 image before, but deleted that in an accident....
So, anyone here can help me with this?
I would like to turn the rooted N2E back to stock 1.1 and upgrade it to 1.1.2
Thanks!
Click to expand...
Click to collapse
Use this:
http://forum.xda-developers.com/showthread.php?t=1475613
it will bring you to stock NST with the 1.1 update, make a new backup and update if you wish to the 1.1.2.

Oh...
then any method to unroot it beside just pulling back the image?
can i just replace a few files?
anything beside the uImage and uRamdisk?

[Q] Would Voodoo OTA Rootkeeper Maintain Root from 1.1.0 to 1.2.1?

My rooted Nook Simple Touch has firmware version 1.1.0. I've never been OTA updated to 1.2.x (currently 1.2.1).
After doing some research, it sounds like there are some improvements to the Nook Reader (especially the dictionary) that would make a firmware upgrade to 1.2.1 desirable.
I have Voodoo OTA Rootkeeper installed and the app indicates that I have my protected superuser copy available.
I've never had to restore root using this app. Can someone indicate to me if:
1) I could update the firmware without losing root
2) How exactly does the app work? If you lose root permissions, how do you access the app to restore?
3) is it worthwhile to do so, or are there other downsides?
Thanks.

It's simple, manualy update NST with the instruction on B&N website. Root with Nook Manager.

dflt said:
It's simple, manualy update NST with the instruction on B&N website. Root with Nook Manager.
Click to expand...
Click to collapse
Thanks. I used TouchNooter last time, will have to get up to speed with Nook Manager. Am I correct in assuming that none of my apps or other data would be lost doing this?

If you don't do a factory reset, then no but you are risking battery drain.

dflt said:
If you don't do a factory reset, then no but you are risking battery drain.
Click to expand...
Click to collapse
Could you kindly explain why the battery drain would occur? Also is it worth going to the trouble of doing this?

Unroot from 1.2

Hi, I had rooted my nook using NookManager, and now I want to get back to stock (best would be 1.0).
I tried n2T-Recovery_0.2 without success (after first boot it shows that it is 'reseting nook' but then it is still rooted 1.2.
Any idea how to solve it?

primosz said:
Hi, I had rooted my nook using NookManager, and now I want to get back to stock (best would be 1.0).
I tried n2T-Recovery_0.2 without success (after first boot it shows that it is 'reseting nook' but then it is still rooted 1.2.
Any idea how to solve it?
Click to expand...
Click to collapse
Best option: Restore the backup you took with NookManager from before you rooted it.
Since you've tried another method I assume you didn't take a backup before rooting.
But I think that your Nook probably is no longer rooted but still has some apps on it that are installed along with rooting (ReLaunch, ADB Konnect, Amazon Market, NootTouchModManager). Factory restore (what n2T-Recovery does) doesn't wipe the data partition where some of the apps are installed. ReLaunch is one of them so if you still have ReLaunch you can use it to uninstall them but I don't think you'll be able to uninstall ReLaunch itself. The easiest thing might be to reroot, then use ADB to see what's in your /data/app folder and uninstall everything there with ADB. Finally use n2TRecovery to force a factory reset.

I tried with CWM + http://forum.xda-developers.com/showthread.php?t=1475613
worked like charm
thanks for effort straygecko.

Go back to Stock ROM from 1337 ROM

Hi,
A couple of months back I had installed 1337 ROM on my Nook ST. However, I would now like to go back to stock ROM. Is using Nook Manger and selecting Restore factory.zip option the correct way? If not what steps should I follow?
Thanks

Using Nook Manager is the way to go. I know that there is a factory reset option available, though I can't remember that it is called. (I don' have either of my NSTs with me at the moment, so I can't check.)

David0226 said:
Using Nook Manager is the way to go. I know that there is a factory reset option available, though I can't remember that it is called. (I don' have either of my NSTs with me at the moment, so I can't check.)
Click to expand...
Click to collapse
Thanks for the prompt reply, however one thing that is bothering me is that I don't have a factory.zip file. Is it required or is it already present in an internal partition?

bit_junky said:
Thanks for the prompt reply, however one thing that is bothering me is that I don't have a factory.zip file. Is it required or is it already present in an internal partition?
Click to expand...
Click to collapse
I believe it is in the internal partition, but I am not sure if the 1337 ROM changes that or not.

David0226 said:
...
I know that there is a factory reset option available, though I can't remember that it is called.
Click to expand...
Click to collapse
Assuming that both the stock recovery and factory ROM image in the backup partition are intact, one should be able to trigger a reset to factory-fresh condition by using the "8 failed boots" method -- power on the Nook and as soon as the screen flash on press power button to turn it off, do this 8 times.

bit_junky said:
Hi,
A couple of months back I had installed 1337 ROM on my Nook ST. However, I would now like to go back to stock ROM. Is using Nook Manger and selecting Restore factory.zip option the correct way? If not what steps should I follow?
Thanks
Click to expand...
Click to collapse
Have you had any success so far? I just tried 1337 but it didn't work well on my device and restored to the original firmware. However I made a full backup image of my Nook (including boot partition and stock recovery) before installing Clockworkmod.
If you have not made this backup and installed Clockworkmod to your internal memory, it may be a bit more difficult for you to restore to the original firmware.