[Q] Updating to 1.1 on touchnooter rooted touch - Nook Touch General

I have a Touch rooted with Touchnooter. My touch doesn't seem to want to update to 1.1 (I know doing so will kill GAPPS, but I'm okay with that). I've waited for the update to be pushed and I've also put the update file in my Nook directory. Is there something about Touchnooter that prevents the Touch from updating?

I haven't tried to update after using touchnooter, dont really know if it blocks nothing, OTA or prevents from updates, OTA or manullay, but you should restore a copy of your nook if you have it, or use nookrestore and then force a reset to also delete /data.
Or use adb to force restore
adb shell
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Click to expand...
Click to collapse
and then reset normally and if it dosnt let you, force reset, force it shutting down your nook, then starting it up, and when the screen flickers press right and left bottom buttons, hold for 5+ seconds.
That will erase /system (restore) and /data (reset), and you should be able to update.

I do have a backup copy, but I was hoping I wouldn't have to do a restore to get the update. I mean, I'd really like to avoid that.
Have others been able to update their Touchnooter Touches to 1.1 without reverting?

kunchers said:
I do have a backup copy, but I was hoping I wouldn't have to do a restore to get the update. I mean, I'd really like to avoid that.
Have others been able to update their Touchnooter Touches to 1.1 without reverting?
Click to expand...
Click to collapse
Updating a TouchNootered NST have caused troubles in the past and is likely to do so with this update as well.
Even if it worked for other users it might not work for you as people do different things to their rooted NST.
I know it's a hassle, but you should really restore+reset your NST before updating if you want to avoid problems.

The OP's post has given me some hope as I do not wish to unroot/re-root-/update at this time, but have kept my NST's wireless off as I'm afraid of getting the update.
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?

TJay99 said:
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?
Click to expand...
Click to collapse
There's nothing in TN 1.6.24 that will block updates.
If you want to make sure, here's the cleanest way of doing so:
Block BN OTA Updates the EASY way
Yes, it's a Nook Color thread but it would work for Nook ST aswell.

TJay99 said:
The OP's post has given me some hope as I do not wish to unroot/re-root-/update at this time, but have kept my NST's wireless off as I'm afraid of getting the update.
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?
Click to expand...
Click to collapse
Blocking updates is also covered here http://forum.xda-developers.com/showthread.php?t=1346748 but with adb and sqlite.
Search for Blocking OTA updates: on the thread.

Yeah, I hear you. I gotta just do it. Strange though, why my Nook won't update.
ros87 said:
Updating a TouchNootered NST have caused troubles in the past and is likely to do so with this update as well.
Even if it worked for other users it might not work for you as people do different things to their rooted NST.
I know it's a hassle, but you should really restore+reset your NST before updating if you want to avoid problems.
Click to expand...
Click to collapse

Thanks ros87 and eded333 for the information.
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
If that's not the case, what other procedures must I do in order to get it done? For instance, there are sections entitled "Setting up adb on the nook touch" and "Setting up root access on NST through adb and installing busybox". Would I need to do any part of those processes?
Much obliged if you can clear up that one matter for me!

I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.

Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse
Hi, Kralik.
I wonder if it would keep downloading/deleting the update file in a perpetual cycle, though. Isn't that what would happen?

TJay99 said:
Thanks ros87 and eded333 for the information.
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
If that's not the case, what other procedures must I do in order to get it done? For instance, there are sections entitled "Setting up adb on the nook touch" and "Setting up root access on NST through adb and installing busybox". Would I need to do any part of those processes?
Much obliged if you can clear up that one matter for me!
Click to expand...
Click to collapse
Touchnooter has adb enabled over wifi (If i'm not wrong), so you wouldnt have to enable it again, go directly into the OTA.

TJay99 said:
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
Click to expand...
Click to collapse
You should be good to go if you install jdk + android sdk.
With TouchNooter 1.6.24 you should allready have adb access enabled via wifi.
---------- Post added at 08:34 PM ---------- Previous post was at 08:33 PM ----------
Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse
Interesting, I need to take a closer look at the update process some day

Yep, same behavior with mine.
Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse

TJay99 said:
Hi, Kralik.
I wonder if it would keep downloading/deleting the update file in a perpetual cycle, though. Isn't that what would happen?
Click to expand...
Click to collapse
That is my guess. Without knowing for sure you're left with two unpleasant options:
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
2) Your nook actually updates and destroys everything!
So you might take the time to "block" OTA updates as other have mentioned. But then there's option...
3) You go through the rigors and just get the 1.1.0 firmware upgrade over and done with, rerooting afterwards.
*I wonder if this is related to the "I rooted my nook and now my battery life is toast" thread?

This is an excellent point. I've also experienced pretty sad battery life since applying Touchnooter.
I'll just bite the bullet and restore/re-root.
Kralik said:
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
*I wonder if this is related to the "I rooted my nook and now my battery life is toast" thread?
Click to expand...
Click to collapse

kunchers said:
This is an excellent point. I've also experienced pretty sad battery life since applying Touchnooter.
I'll just bite the bullet and restore/re-root.
Click to expand...
Click to collapse
This is the best time to do that, finally got Gapps to work on 1.1 manully, at last!
If you wish to try it, here is my post:
http://forum.xda-developers.com/showthread.php?t=1346748

Kralik said:
That is my guess
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
Click to expand...
Click to collapse
A good and interesting guess.
There are intervals defined for the update checks, but maybe if it finds an update but are unable to apply it, it end up in a loop..

GApps aren't actually that hard to enable if you use TouchNooter 1.6.24 and manually replace /nooter/boot/uRamdisk and /system/framework/framework.jar with the updated versions. Other than that step, very little difference in the rooting processes. If one is going to restore to factory and build up from there, what is the advantage to wading through all the manual steps?

Kralik said:
GApps aren't actually that hard to enable if you use TouchNooter 1.6.24 and manually replace /nooter/boot/uRamdisk and /system/framework/framework.jar with the updated versions. Other than that step, very little difference in the rooting processes. If one is going to restore to factory and build up from there, what is the advantage to wading through all the manual steps?
Click to expand...
Click to collapse
At this moment, fun, learning, and stability (for the moment it allways works, but I need more feedback from people that tried it) eventually, when I delete all the blob that Gapps dosn't need for them to work, and is installed on the default package of Touchnooter (Don't get me wrong I really think its a great method) you will get a cleaner install.
Anyway, If you don't want to go through all the steps you can use the new 1.1 Touchnooter to get root, and then use my GApps method.

Related

Nicely rooted Nook Touch got "unrooted" - few thoughts

Dear fellows,
I got nicely rooted Nook Touch (and have never asked such dummy questions) with plenty of applications working on it - all of them uploaded and tested via try/error approach. Unfortunately, I did not use it for quite some time.
Now, can see:
1) the left-handed hardware buttons stopped to work - the upper one was used as a "Back" button, the one below it as a "Settings"
2) Cannot connect via adb from my laptop
3) Some programs like AdFree started to push a kind of annoying messages like "Unable to get root. I was unable to get root access, without this you cannot install a replacement hosts file", etc.
1), 2) and 3) make me think that somehow my NST got "unrooted". How can it happen and what I can do ? I am thinking of rooting it again, but will I lost all the .apk-s installed, etc..?
Any ideas really appreciated, many thanks in advance
Any help ?
Thanks in advance!
Sounds to me that your NST got updated.
Go into Settings and check your software version.
Hi ros,
I thought of this as well. Unfortunately I can't remember if it was 1.0.1 prior rooting or just 1.0.0. At the moment it is definitely 1.0.1. I saw that B&N has just released 1.1.0 too ..
As far as I remember xe-autonook.bat had the section that blocks OTA updates,
also after rooting I did not got over the official update procedure (update screens, restarts, etc.), so seems to be something else ...
Anyway, since it already happened - if I choose the option to root it again - will I destroy everything - is it rewriting /system/apps, etc.?
Thanks
nook_touch said:
Hi ros,
Anyway, since it already happened - if I choose the option to root it again - will I destroy everything - is it rewriting /system/apps, etc.?
Click to expand...
Click to collapse
Hmm, what root method did you use in the first place?
Autonooter ? The one that is using the xe-autonook.bat - replacing the uRamdisk and then doing few other steps, the bat mentioned above is just automating the procedure.
Now I did check .. and voilla - now the firmware is 1.1.0, so basically the OTA update took place and that's why the NST got unrooted. Do you see any possibilities beside rooting from scratch ? I just want to keep the installed applications and settings
Thanks
nook_touch said:
Autonooter ? The one that is using the xe-autonook.bat - replacing the uRamdisk and then doing few other steps, the bat mentioned above is just automating the procedure.
Now I did check .. and voilla - now the firmware is 1.1.0, so basically the OTA update took place and that's why the NST got unrooted. Do you see any possibilities beside rooting from scratch ? I just want to keep the installed applications and settings
Thanks
Click to expand...
Click to collapse
Use TouchNooter, it'll reroot you and you don't have to wipe /data
Great, thanks Gabrial!
Will try 1.11.20, which seems to be compatible to NST 1.1.
Result:
- su on terminal emulator is behaving as expected
- GMail running (never could get it running before)
- Market running (the same as GMail - never got running it before, used Amazon Appstore due to this reason)
...
- thankful, great and nice work, when I saw the bottom left sign on the initial ("Rooted Forever") window - "GabrialDestruir", I just realized who replied to me, cheerz!
Hi guys,
However I am wondering whether should I find a way to disable the OTA updates or whether to wait and receive the B&N and then reroot (as I did now for 1.1) ?
Thanks again
Is there no way of stoping the autoupdate? I worked a lot on that install ...
Thanks!
Gogolo
Gogolo2 said:
Is there no way of stoping the autoupdate? I worked a lot on that install ...
Thanks!
Gogolo
Click to expand...
Click to collapse
There is: http://forum.xda-developers.com/showpost.php?p=20069283&postcount=9
Thanks a lot, sorry Im a noob: Where can I get the ip of my simple touch?
Best Regards
edit: I use Adb over Usb : "adb devices" ist then correct?
Ok, worked. Sorry about the post and thanks very much for all your work on this nice device!
Gogolo2 said:
Thanks a lot, sorry Im a noob: Where can I get the ip of my simple touch?
Best Regards
edit: I use Adb over Usb : "adb devices" ist then correct?
Ok, worked. Sorry about the post and thanks very much for all your work on this nice device!
Click to expand...
Click to collapse
No problem, but remember, the best way to say thanks is to click the thanks button

Keep Root through OTA

Read up on this in my Google New reader app.
Just installed it to see if it works on our tabs, and it appears to.
What I believe it does is make a backuo of your root.
Before you do an OTA, you uninstall root (after you've backed up root) through the app, then after OTA you restore your root.
For those of you that like to stay stock, but have root, here's the link.
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper
interesting But i bet acer is Already working on patching this... I also think that is what takes them so long to push updates.. Patching holes. to prevent dev. on There devices that we PAID For ...APPLE Ceo did not die He Quit and it working with Elvis at Acer... Giggles..
erica_renee said:
interesting But i bet acer is Already working on patching this... I also think that is what takes them so long to push updates.. Patching holes. to prevent dev. on There devices that we PAID For ...APPLE Ceo did not die He Quit and it working with Elvis at Acer... Giggles..
Click to expand...
Click to collapse
I guess you didn't understand what it does?
Doesn't your sig say "reading is power"?
yes i read what it does.. Just not sure how long it will remain valid and i d/loaded it will check it out give it a try
erica_renee said:
yes i read what it does.. Just not sure how long it will remain valid and i d/loaded it will check it out give it a try
Click to expand...
Click to collapse
It does nothing to the bootloader, merely retains root. After you backup root with the app, you get your OTA, then restore your root through the app.
OK What i do not understand.. is IF it can retain root thru the OTA.. ota updates change they system file permissions and protects them. The use some type of exploit to root the device. This app is doing the same Am i correct.. And if i am acer can plug that exploit. Also.. is this works to reroot afer a ota unrootes the device.. why will this not just root the tablet as well. looks like someone could take it apart and create a new way to root the tablet without DOWNGRADING or flashing a new rom..
IS the above true or am i just STUPID For thinking all of this... the dev might know something that is not known on the a500 forums ...
I can tell you exactly how it works.
In Linux there is a command called chattr which allows you to change the attributes on a file like in Windows (readonly for example). However, in Linux it is much more powerful. So, what you do, is set the chattr bit so NOBOBY can modify a file. Not even root. If root wants to change it, then root has to remove that bit first.
So, if you want to keep root you chattr it. Then when the update.zip runs and walks through the /system folder it cannot remove the su sticky bit because it has been chattr'ed.
However, some updates delete everything in the /system/xbin folder therefore the tool makes a backup to another folder called /system/backupsu. This backup usually remains. Usually, that is, unless ACER loads a NEW /system image. Like they need to expand the size, or want to reload everything, then they lay down a NEW system image and it's gone. ALL GONE.
Some ask, why don't you chattr to another folder other then system, well most other mount points have su sticky bit turned off, therefore making su not work from another mount.
So will ACER plug the chattr hole? I don't think so, this in the kernel and part of the file system. They could walk the system mount and un-chattr everything, but then again you can just use another approach.
The chattr trick normally only works on simple OTA's. For example, I think when ACER went to 3.2 they relaid down system. I could be wrong, I'd have to check my notes. But thankfully, most vendors don't reload system that often so you'r find that chattr'ng the su file works 99% of the time.
Hope this helps,
TD
---------- Post added at 06:25 PM ---------- Previous post was at 06:10 PM ----------
Also, 411 on rooting.
To root, you find a hole and then set the 'sticky bit' on an executable so it now runs as root for example: rwsr-xr-x. Notice the 's' in the owner permissions. When this file is executed it runs with the owners permissions on the file system. So to make a simple root, just copy the ash shell to /system/xbin make the file owned by root and then set the sticky bit. Now, if you are not root, you just run /system/xbin/ash and because this version of ash is owned by root and has the sticky bit set, you get the root(#) because the ash shell is now running as root.
So, you use the exploit to gain root and then set up a program to give you root anytime you want it. Usually that program is named su. Now, when an update runs, it walks the entire /system tree resetting all files to rwxr-xr-x which removes the sticky bit and breaks root.
What is heartbreaking, is you now need to use the exploit to get root so you can set back your sticky bit. If the update patched your exploit then you have find another one.
So, the question is, once you get root, how do you keep it. Using chattr is one way therefore if the update removes your exploit, hopefully it doesn't matter because you 'locked in' your sticky bit with chattr.
This is why once any version is rooted you can root most any other version. It now becomes possible to move back and forth through OTA's while allowing you to keep root. But time traveling a root OTA is only possible into the future, you can never go back in time prior to the invention of the root. But you can always travel forward with root. This is exactly how we root the 3.2.1. We take a tablet that has 3.0.1 on it and use iconia root exploit to root it. Then we lock it, add other backdoors, and roll forward in time through the minefields of the OTA's until it stops. Hopefully, you still have root. In other words, it's the flux capacitor and is what makes future rooting possible.
So it doesn't matter, as long as you chattr (chatter), because who cares if ACER's heart goes pitter patter <<== Sounds like a Roll'n Stone lyrics <lol>
"Don't you know the crime rate is going up, up, up, up, up
To live on this forum you must be tough, tough, tough, tough, tough
You got rats at ACER dreaming of the west side
Software bugs on upgrades
What a mess, this forum says chatter (chattr), so my root won't be shattered
My brains been battered, splattered all over this forum
but what's that matter.
Ah look at me, my root is chattr'ed
I'm not wanting my root shattered
Look at me- I'm a chattr'ed, look at me
Man time to go drink heavily.
"SOFTMOD" app
SORRY PPL COMPLETELY CONFUSED 2 DIFFERENT TOPICS IN 2 DIFFERENT THREADS - ALZHEIMER's RULES OK!! - Deleted this response
timmyDean your making my head spin. Thanks for the info.
ok as I was thinking this works unless acer pushes a full os.So I will continue to stay on custom roms.giggles
erica_renee said:
ok as I was thinking this works unless acer pushes a full os.So I will continue to stay on custom roms.giggles
Click to expand...
Click to collapse
Actually, I went back to 3.1 today to test it out. It worked through all updates, including full updates
kjy2010 said:
Actually, I went back to 3.1 today to test it out. It worked through all updates, including full updates
Awesome.
It seems interesting
Click to expand...
Click to collapse
kjy2010 said:
Actually, I went back to 3.1 today to test it out. It worked through all updates, including full updates
Click to expand...
Click to collapse
You the man. I could not recall if 3.0.1 to 3.1 to 3.2 did a system reload. What some OEM's do is erase /system. Lenovo did that when they went from 11 to 12 and then from 12 to 13. But, I could not recall if ACER did. You'll find that chattr works 99% of the time, maybe 100% on an ACER. That's why I turn off OTA's so they don't occur automatically. Then when one becomes available, I download and look at what they're changing before allowing it. This is really important now that they've locked the bootloader. If you take an OTA and it patches your root exploit, removes chattr, deletes your backup su, and breaks root then you might be stuck in the future with no root. If this happens you have to hope there's a way back without root.
So thanks.
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
erica_renee said:
ok as I was thinking this works unless acer pushes a full os.So I will continue to stay on custom roms.giggles
Click to expand...
Click to collapse
Not a full system, it's how they load it is the key. They push full systems all the time and they really just copy over all new which keeps chattr'ed files. They really have to reformat /system (or destructively destroy it). They'll do this if they need to increase the size, change from ext3 to ext4, etc.
Hope this helps
TD
Thanks sirs for this if we get the doubtful ota I might do this n sell the tap to my little brother or keep it who knows lol
Sent from my HTC Inspire 4G using Tapatalk
timmyDean said:
You the man. I could not recall if 3.0.1 to 3.1 to 3.2 did a system reload. What some OEM's do is erase /system. Lenovo did that when they went from 11 to 12 and then from 12 to 13. But, I could not recall if ACER did. You'll find that chattr works 99% of the time, maybe 100% on an ACER. That's why I turn off OTA's so they don't occur automatically. Then when one becomes available, I download and look at what they're changing before allowing it. This is really important now that they've locked the bootloader. If you take an OTA and it patches your root exploit, removes chattr, deletes your backup su, and breaks root then you might be stuck in the future with no root. If this happens you have to hope there's a way back without root.
So thanks.
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
Not a full system, it's how they load it is the key. They push full systems all the time and they really just copy over all new which keeps chattr'ed files. They really have to reformat /system (or destructively destroy it). They'll do this if they need to increase the size, change from ext3 to ext4, etc.
Hope this helps
TD
Click to expand...
Click to collapse
Yes i do understand. Maybe i did not explain what i was saying correctly.. Acer's update is not aware or looking for those files. There for they do not touch them. as they are just scanning and updating files to reflect there changes.. I to agree that its likely this will remain valid.Atleast we know it is for the os updates and release that are available up to now..
erica_renee said:
Yes i do understand. Maybe i did not explain what i was saying correctly.. Acer's update is not aware or looking for those files. There for they do not touch them. as they are just scanning and updating files to reflect there changes.. I to agree that its likely this will remain valid.Atleast we know it is for the os updates and release that are available up to now..
Click to expand...
Click to collapse
Exactly, so much for being blonde <lol>

Nook Simple Touch 1.1.2 and rooting

Hi everyone. I'm a long time computer builder/hacker and am just getting into the Nook Simple Touch and rooting. I see that 1.1.2 just came out.
-Should I update to that firmware and them root?
-Will current rooting techniques work with the new firmware?
-Is it possible and easy to unroot?
Thanks in advance for your help. I have done some searching but am having trouble finding the answers and dont want to waste even more time. I hope you understand and I can't wait to get into this rooting thing!
Guyman2 said:
[...] -Should I update to that firmware and them root?
Click to expand...
Click to collapse
The update incorporates wifi fixes that can be useful if you use it on the road, or suffer a router that v1.1.0 had problems with. I'd recommend it, yes. I haven't seen any downside.
-Will current rooting techniques work with the new firmware?
Click to expand...
Click to collapse
Yes. I did a complete wipe on mine running v1.1.0, updated to v1.1.2 and used the normal TouchNooter 2.1.31 process. Everything worked exactly as it did on v1.1.0, including having to wait 24 hours for the Market to activate.
-Is it possible and easy to unroot?
Click to expand...
Click to collapse
Hmm. I had no problem wiping and reloading mine. Not sure if that constitutes a 100% unroot, but I think it does. I had no problems.
Thanks in advance for your help. I have done some searching but am having trouble finding the answers and dont want to waste even more time. I hope you understand and I can't wait to get into this rooting thing!
Click to expand...
Click to collapse
I just made a point of following Gabrial's instructions in the first post, and everything went smoothly. If you have reasonable expectations, the NST rooted is a great little device. I think you'll be pleased.
[EDIT: Since writing this, I began having problems searching in the Android Market. I rolled back to B&N v1.1.0 and re-rooted, and STILL am having that problem. I don't know why this only started recently, and I do not think it's related to v1.1.2, but I wanted to post it here as fair warning. Also, after rooting using TN, the device info screen showed 1.1.0 after having updated to 1.1.2. I'm changing my recommendation to "do it if you're having wifi issues" for now.]
Thank you for such a wonderful and detailed post. My micro SD card should be here tomorrow and I cant wait to root it. I have a gmail account but not a youtube. Is it imperative to link gmail and youtube to root this? I would post in that thread, but as a new user i have to wait for 10 posts to do that. Thanks!
Wonderful. Since I had a mishap when screwing with framework-res.apk, I am going to do a full wipe. This is cool!
Guyman2 said:
Thank you for such a wonderful and detailed post. My micro SD card should be here tomorrow and I cant wait to root it. I have a gmail account but not a youtube. Is it imperative to link gmail and youtube to root this? I would post in that thread, but as a new user i have to wait for 10 posts to do that. Thanks!
Click to expand...
Click to collapse
YouTube and Gmail are linked -- or at least can be. Go to YT in your desktop browser, and you should be able to sign in using your Gmail credentials. (Google is assimilating EVERYTHING!)
You do need to link to Google for Market functionality, so yes, you probably do need to do it in practical terms.
---------- Post added at 11:33 AM ---------- Previous post was at 11:32 AM ----------
brendan10211 said:
Wonderful. Since I had a mishap when screwing with framework-res.apk, I am going to do a full wipe. This is cool!
Click to expand...
Click to collapse
The "8 failed boot" process should let you reload the default firmware your unit shipped with if you need to get out of a bootloop situation.
Just a reminder that a FULL IMAGE BACKUP is strongly recommended before you start monkeying with too much, ideally on Day One. Unlike other NOOK devices, you can badly, if not permanently, screw up a NST if you wipe out some system information. Be sure to read through the various threads before going too far!
So I should restore my nook to factory? Will that do anything to the partitions?
brendan10211 said:
So I should restore my nook to factory? Will that do anything to the partitions?
Click to expand...
Click to collapse
If you're stuck, it's an option. My understanding is that:
The "8 failed boots" procedure will restore the firmware your NST shipped with.
The "Unregister and Wipe" procedure from settings will wipe all user data off the internal system.
I was not able to manually update from v1.1.0 to v1.1.2 if previously rooted. Not sure if that's normal, but I had a lot of cruft on my unit, so just did both procedures. Files on my uSD were untouched.
I'm following your guide and see that making a backup is recommended. I would post in that forum, but as a new user here, i am not allowed to there. they say to follow these instructions:
BACKUP/RESTORE N2E Win7
Grab a copy of Roadkil's free DiskImager for backup and restore.
and a copy of free MiniTool Partition Wizard at:
Boot nook with noogie.img : nookdevs.com/NookTouch_Rootin (the "Rooted Forever" screen) and connect to your computer via USB.
Use DiskImager to copy your Nook partition to a file, being sure to select "Physical Disk" in the drop down list.
http://forum.xda-developers.com/showthread.php?t=1142983
However when i follow this step I get to a link that doesn't work. Thus I cannot backup my nook:
Boot nook with noogie.img
Any ideas? Thanks. Again, I'd post the link that wont work but the damn forum wont let me post outside links until i do 8 more posts. This is frustrating as HELL. But you should be able to find out what my problem is from the details i am so kindly allowed to post.
Or maybe I shouldnt bother backing up, since as another user pointed out, after a few failed boots it automatically will store its original firmware. What do you guys think?
You need to be sure that you use a program to write noogie.img to an SD card (I'll post a link to one when I have time), and be sure that you do not write the image to the SD card when it is in the Nook! You need to use an external card reader. After that, you just turn your Nook off, put the SD card into your Nook, and turn the Nook on.
Thanks guys for taking time to make these posts. This should help me in figuring all this stuff out.
so do i need to root the nook BEFORE backing it up? isnt that what noogie.img does?
A quick update: There do seem to be some annoyances if using existing TouchNooter versions to root B&N 1.1.2. If you haven't already done so, and aren't suffering from the wireless issue, you might hold off a bit until the exact implications are better known.
If you've already done it, it shouldn't be the end of the world either.
---------- Post added at 10:03 AM ---------- Previous post was at 10:02 AM ----------
Guyman2 said:
so do i need to root the nook BEFORE backing it up? isnt that what noogie.img does?
Click to expand...
Click to collapse
No. Noogie just exposes the normally inaccessible NOOK partitions so you can back them up. Noogies doesn't root anything. It's recommended to make a backup of your pristine device BEFORE rooting, in case anything goes wrong.
Thanks! How do i get noogie.img? the link on the backup page doesn't work and I dont want to get the wrong version. Any idea how long it takes for the next rooting version to come out?
Guyman2 said:
Thanks! How do i get noogie.img? the link on the backup page doesn't work and I dont want to get the wrong version. Any idea how long it takes for the next rooting version to come out?
Click to expand...
Click to collapse
It does look like the download link to noogie.img.gz is broken, even on the redirected Nook Devs page.
Yeah, that article is removed. Does anyone have a noogie.img they can slap in dropbox public?
Man, they dont make this easy. The direction suck, links aren't working, sheesh. Unlocking the original iPhone was easier! I sure hope this gets updated somewhat soon.
I have noogie.img somewhere on my PC, I'll get it uploaded in about an hour.
Thanks, i hope you can find that file. Since the directions are so vague, do i need a special program to put the file onto an SD card? Or just drag and drop? Thanks. I really hope to get this completed soon.
bobstro said:
It does look like the download link to noogie.img.gz is broken, even on the redirected Nook Devs page.
Click to expand...
Click to collapse
hi bobstro,
i tried restoring my backup to my nook to update it to 1.1.2. i followed everything as said in http://forum.xda-developers.com/showthread.php?t=1142983
but after the restore process, my nook still has the android but it is as it was in the beginning, i mean like a fresh rooted nook(all apps gone).
is this supposed to happen? is it ok, if i update my nook with android in it?
Guyman2 said:
Thanks, i hope you can find that file. Since the directions are so vague, do i need a special program to put the file onto an SD card? Or just drag and drop? Thanks. I really hope to get this completed soon.
Click to expand...
Click to collapse
You don't need to follow those instructions, it's all automated now. You only need noogie.img to create a backup now. Now to find that image...
Edit: Here you go!

Can the NST with v1.2.2 be rooted?

I got my first ereader, a lightly used NST and am thoroughly delighted with how much easier it is to read than on my phone or laptop. I was hoping to remove some of the bloatware as all my books are sideloaded using Calibre, but my version is 1.2.2. I couldn't find any reference to this new version on the Nookmanager thread. Can I still root it with this version?
Additionally, I am finding it hard to organise and find my EPUBs on it. The shelf function requires manual selection, which will take a while for a lot of books. At the moment I'm just keeping 5-10 books at a time of what I'm actively reading, but ideally I'd like to have my whole collection on there. If I were to root it, are there any library apps which would group the books by tags? A bit like how Calibre does it?
If not, what workarounds have people with large collections on the NST used?
fsa259 said:
I got my first ereader, a lightly used NST and am thoroughly delighted with how much easier it is to read than on my phone or laptop. I was hoping to remove some of the bloatware as all my books are sideloaded using Calibre, but my version is 1.2.2. I couldn't find any reference to this new version on the Nookmanager thread. Can I still root it with this version?
Additionally, I am finding it hard to organise and find my EPUBs on it. The shelf function requires manual selection, which will take a while for a lot of books. At the moment I'm just keeping 5-10 books at a time of what I'm actively reading, but ideally I'd like to have my whole collection on there. If I were to root it, are there any library apps which would group the books by tags? A bit like how Calibre does it?
If not, what workarounds have people with large collections on the NST used?
Click to expand...
Click to collapse
1.2.2?! Are you sure it's an actual NST? There is nothing past 1.2.1 for the NST that I know. Look under Settings>Device Info>About Your Nook. The model number of the NST is BNRV300.
That is really odd. It definitely has the model no you mentioned and says v1.2.2. Now that you mention it, I can't find the 1.2.2. on the B&N software updates section of their website, but found a reference to it on another forum where a user says their NSTG updated to it automatically when on wifi this January.
Should I be worried?
fsa259 said:
That is really odd. It definitely has the model no you mentioned and says v1.2.2. Now that you mention it, I can't find the 1.2.2. on the B&N software updates section of their website, but found a reference to it on another forum where a user says their NSTG updated to it automatically when on wifi this January.
Should I be worried?
Click to expand...
Click to collapse
I don't know anything about software version 1.2.2. However, if you would like to try rooting it, I would start with this thread.
Minimal rooting - back to basics. If you can get a minimal root with those instructions, the other more "advanced" (or not) rooting tools should also work.
fsa259 said:
That is really odd. It definitely has the model no you mentioned and says v1.2.2. Now that you mention it, I can't find the 1.2.2. on the B&N software updates section of their website, but found a reference to it on another forum where a user says their NSTG updated to it automatically when on wifi this January.
Should I be worried?
Click to expand...
Click to collapse
I would not worry. In a pinch you could do a factory reset and return to the original firmware which is not 1.2.2 I'm sure. Then you could use the 1.2.1 update zip to get it ready for NookManager. If indeed B&N is pushing an update (I've not seen it and have used WiFi regularly) you can avoid WiFi until you've rooted with NM. If there is some kind of update it may involve security issues for those purchasing B&N books with their devices. That would explain why I have not seen it.
nmyshkin said:
I would not worry. In a pinch you could do a factory reset and return to the original firmware which is not 1.2.2 I'm sure. Then you could use the 1.2.1 update zip to get it ready for NookManager. If indeed B&N is pushing an update (I've not seen it and have used WiFi regularly) you can avoid WiFi until you've rooted with NM. If there is some kind of update it may involve security issues for those purchasing B&N books with their devices. That would explain why I have not seen it.
Click to expand...
Click to collapse
Thanks for your reply.
After creating a back up I attempted to root with NM and in the final screen everything had positive remarks except 'PackageInstaller not modified' and 'ModManager not available for 1.2.2'. I figured I needed these two, so I went through the deregistration and restore to factory settings and booted to NM to avoid connecting to wifi. Strangely, on the NM main menu, it still says the system is 1.2.2.
I'm not sure if I'm missing something. I'll try factory reset again, but I'm not sure how else to get back to 1.2.1
fsa259 said:
Thanks for your reply.
After creating a back up I attempted to root with NM and in the final screen everything had positive remarks except 'PackageInstaller not modified' and 'ModManager not available for 1.2.2'. I figured I needed these two, so I went through the deregistration and restore to factory settings and booted to NM to avoid connecting to wifi. Strangely, on the NM main menu, it still says the system is 1.2.2.
I'm not sure if I'm missing something. I'll try factory reset again, but I'm not sure how else to get back to 1.2.1
Click to expand...
Click to collapse
There are two distinct "factory" operations. The one you describe just deletes user info and settings.
The other one reimages the device from a hidden and protected factory image--that won't be 1.2.2. That's the one you want. One way to get there is by eight failed boot attempts. That's very tedious. There is another way involving holding one of the buttons down during boot. Let me see if I can find it.
Edit: power down. Power up and as soon as you get anything on the screen press and hold the two bottom buttons until the factory restore dialog appears.
nmyshkin said:
There are two distinct "factory" operations. The one you describe just deletes user info and settings.
The other one reimages the device from a hidden and protected factory image--that won't be 1.2.2. That's the one you want. One way to get there is by eight failed boot attempts. That's very tedious. There is another way involving holding one of the buttons down during boot. Let me see if I can find it.
Edit: power down. Power up and as soon as you get anything on the screen press and hold the two bottom buttons until the factory restore dialog appears.
Click to expand...
Click to collapse
Ah, now I understand, I didn't realise there were two different options. Thank you for this.
Unfortunately it has lead to something very strange: I held the two bottom buttons on restart, went through both prompts confirming if I want to factory reset. It went through the process and at the selecting WiFi screen I restarted to boot to NM which still says the system is 1.2.2! Could it be that the forced update to 1.2.2 also wrote over the protected factory image?
Edit: I found these instructions and am keeping my fingers crossed they work to get 1.2.1 back
https://sites.google.com/site/xcdguides/nook/nookregion
fsa259 said:
Ah, now I understand, I didn't realise there were two different options. Thank you for this.
Unfortunately it has lead to something very strange: I held the two bottom buttons on restart, went through both prompts confirming if I want to factory reset. It went through the process and at the selecting WiFi screen I restarted to boot to NM which still says the system is 1.2.2! Could it be that the forced update to 1.2.2 also wrote over the protected factory image?
Edit: I found these instructions and am keeping my fingers crossed they work to get 1.2.1 back
https://sites.google.com/site/xcdguides/nook/nookregion
Click to expand...
Click to collapse
Yes. That was going to be my next suggestion. I hope it works.
nmyshkin said:
Yes. That was going to be my next suggestion. I hope it works.
Click to expand...
Click to collapse
Thank you so very much for your help. 1.2.1 was installed successfully and rooting worked a breeze!
I found an old version of ES Explorer on here and I'm now just adding '.disable' to the apks as recommended on another thread here to optimise the NST.
Once again, many thanks!
Rooting with NookManager
The answer to the original thread question is "yes". See https://forum.xda-developers.com/nook-touch/general/nst-nstg-fw-1-2-2-update-t3785566
@nmyshkin ...
Its true there is a version 1.2.2 ... i just got a mailer for update ... specifies 29 June 2018 as the last date after which managing and purchases from the nook store will be blocked rescinded !!!
please respond on this thread ... HERE

Rooted Nook Simple Touch connects to internet, won't communicate with servers

I rooted my Nook in 2014. I hadn't used it since 17 or 18 and now nothing communicates. I can't get the kindle app to sync or anything. Is it done?
NookRoot93 said:
I rooted my Nook in 2014. I hadn't used it since 17 or 18 and now nothing communicates. I can't get the kindle app to sync or anything. Is it done?
Click to expand...
Click to collapse
Two separate issues:
1. For the Kindle app, see this post: https://forum.xda-developers.com/nook-touch/general/elses-nook-simple-touch-kindle-app-stop-t3205615
Post #24 in that thread gives a step-by-step process for copying the updated cacerts.bks file (found at the end of post #10) to your NST.
2. You don't say what browser you are trying to use. Updating the cacerts.bks file may help, but you need a browser that can handle TLS 1.2 security protocols. Opera Mobile 12.1 is an example.
Since I missed the 2018 update, it can't communicate with Nook servers. I just reset the device and I now it's just done. I noticed several other people had this happen recently online with non-rooted Nooks. I have another rooted Nook I can try. I didn't try any browsers, just the kindle and app stores. I did notice my gmail did work.
NookRoot93 said:
Since I missed the 2018 update, it can't communicate with Nook servers. I just reset the device and I now it's just done. I noticed several other people had this happen recently online with non-rooted Nooks. I have another rooted Nook I can try. I didn't try any browsers, just the kindle and app stores. I did notice my gmail did work.
Click to expand...
Click to collapse
When I meant done, I meant I can register it now because while connected to WiFi it says it's not, and tho' I'm layman, I'd take it as not communicating with servers due to software version.
NookRoot93 said:
When I meant done, I meant I can register it now because while connected to WiFi it says it's not, and tho' I'm layman, I'd take it as not communicating with servers due to software version.
Click to expand...
Click to collapse
You are correct, only 1.2.2 firmware will permit you to register now. If that's what you want to do, download the update zip from the B&N website. With your NST at the "welcome" screen, connect the device via USB to your PC and move the zip onto it. Disconnect from USB and let the NST sleep on its own. It will update. Then you can proceed with registration, rooting, etc.
nmyshkin said:
You are correct, only 1.2.2 firmware will permit you to register now. If that's what you want to do, download the update zip from the B&N website. With your NST at the "welcome" screen, connect the device via USB to your PC and move th.e zip onto it. Disconnect from USB and let the NST sleep on its own. It will update. Then you can proceed with registration, rooting, etc.
Click to expand...
Click to collapse
Hi. I can't seem to find the update zip file as downloadable from B&N site. If you could help provide a link, thanks in advance. The only update I found was for Nook HD or is that one ok?
NookRoot93 said:
Hi. I can't seem to find the update zip file as downloadable from B&N site. If you could help provide a link, thanks in advance. The only update I found was for Nook HD or is that one ok?
Click to expand...
Click to collapse
Go here: https://help.barnesandnoble.com/app/answers/detail/a_id/4212 and scroll down to Nook Simple Touch. Follow the "download" link.
nmyshkin said:
You are correct, only 1.2.2 firmware will permit you to register now. If that's what you want to do, download the update zip from the B&N website. With your NST at the "welcome" screen, connect the device via USB to your PC and move the zip onto it. Disconnect from USB and let the NST sleep on its own. It will update. Then you can proceed with registration, rooting, etc.
Click to expand...
Click to collapse
nmyshkin said:
Go here: https://help.barnesandnoble.com/app/answers/detail/a_id/4212 and scroll down to Nook Simple Touch. Follow the "download" link.
Click to expand...
Click to collapse
Hi. I found the update. Thank you! New problem. I can't get my new laptop to recognize the Nook via USB. It only charges. Do you have a good, instructional link on how to get a driver to recognize the device?
NookRoot93 said:
Hi. I found the update. Thank you! New problem. I can't get my new laptop to recognize the Nook via USB. It only charges. Do you have a good, instructional link on how to get a driver to recognize the device?
Click to expand...
Click to collapse
It's always something.
According to B&N (https://help.barnesandnoble.com/app.../~/nook-simple-touch---transfer-files-from-pc) you don't need any special drivers for a PC to recognize the NST, but I do recall back in the Win XP days that we had to massage a .inf file to get the PC to see the NST. I've searched for that info (which is what you should do) on the forum and generally via Google bu failed to find it. The information is there somewhere.
If you've got a Mac or are running Linux, then I truly have no idea.
WIN 10. I've tried adding drivers, legacy hardware....maybe I can try on a Win 7 tonight.
I got the update installed. Thanks again!
NookRoot93 said:
WIN 10. I've tried adding drivers, legacy hardware....maybe I can try on a Win 7 tonight.
Click to expand...
Click to collapse
Hello again. I've got the Nook updated and rooted via NookManager. My previous way was the rooted forever root(?). So...can I read kindle titles on the device? That's really the main reason I rooted it in the first place. Are there apps that still work for it? It looks like not much does. Is there a link for legacy apk to download? Thank you so much for the help you've provided me!
NookRoot93 said:
Hello again. I've got the Nook updated and rooted via NookManager. My previous way was the rooted forever root(?). So...can I read kindle titles on the device? That's really the main reason I rooted it in the first place. Are there apps that still work for it? It looks like not much does. Is there a link for legacy apk to download? Thank you so much for the help you've provided me!
Click to expand...
Click to collapse
Yes, you can install the Kindle app and read mobi format ebooks, either side-loaded or from your local library Overdrive system, but you'll have to update the cacerts.bks file first because the security certificates in the stock file have died. There is an option described in the second post in the updated NookManager thread, but it's probably easier if you didn't do it during rooting to do it manually.
Here's what I wrote:
"Some certificates have expired (like the one for Amazon.com). Some editing and updating of our file was done by XDA member @tshoulihane here: https://forum.xda-developers.com/showpost.php?p=65344931&postcount=10 (use the more complete file).
Recently I came across a CM 7 ROM (Honeycomb) and harvested the cacerts file from there. You can find it here: https://forum.xda-developers.com/nook-touch/general/nst-g-revisiting-cacerts-bks-t3872617. This also works with Amazon.com and contains many other certificates than our original file--but some are expired."
So grab one of the files and then follow the directions in post #24 of this thread: https://forum.xda-developers.com/nook-touch/general/nst-g-revisiting-cacerts-bks-t3872617
As for other apps, there are many that still work quite well. Follow the link in my signature for a zip to download of all the apps I currently use. If you don't see something there that you think you want, just ask. Someone may have a working copy.
Sorry for the late reply. I didn't see your last post.
NookRoot93 said:
I got the update installed. Thanks again!
Click to expand...
Click to collapse
Can you tell me how you did it? I don't seem to find a way to get the file to my nook.
velayo said:
Can you tell me how you did it? I don't seem to find a way to get the file to my nook.
Click to expand...
Click to collapse
Are you talking about the B&N 1.2.2 update? If so, download the zip from the B&N website. Then connect your device to your PC via USB and copy the zip file to the root of the NOOK drive (not the sdcard). Then wait. The device needs to sleep before it notices the update and installs it.
You need to revert to stock to do this and you can do it on the "Welcome" screen without going any further.
nmyshkin said:
Are you talking about the B&N 1.2.2 update? If so, download the zip from the B&N website. Then connect your device to your PC via USB and copy the zip file to the root of the NOOK drive (not the sdcard). Then wait. The device needs to sleep before it notices the update and installs it.
You need to revert to stock to do this and you can do it on the "Welcome" screen without going any further.
Click to expand...
Click to collapse
Thank you!! My NSTG wasn't mounting on Windows. Had to reset and then it mounted. @nmyshkin Thanks for keeping our devices alive. I appreciate everything you do!!

Categories

Resources