Related
which uRamdisk to Replace into touchnooter-1.6.24 to make it work on 1.1 is not clear (there are 2 of them).
The answer is ONLY /nooter/boot/uRamdisk (don't touch the one in the root)
with this configuration (and the framework.jar) i got it to work on the first boot, no need to make the 3 boots sequence.
concluding (starting from an 1.1 virgin system):
download touchnooter-1-6-24.zip
extract touchnooter-1-6-24.img
download one of those uRamdisk
download framework.jar
replace ONLY /nooter/boot/uRamdisk in touchnooter-1-6-24.img
replace framework.jar in touchnooter-1-6-24.img
write touchnooter-1-6-24.img on the SD
just 1 boot as usual to the android welcome page,
then remove the SD,
reboot,
double skip as usual
NookColorTools - disable and re-enable non market apps (uncheck and check it again),
Youtube (error 401),
Gmail
and finally...
Market (install at least 1 application with this version, search doesn't work)
now (after you have installed 1 app) eventually replace Vending.apk with this to enable search
i also putted this inside my touchnooter, the 2 .jar into the framework directory and the apk into the app but this shouldn't be necessary...
this is how it worked for me, enjoy
Since i don't have enough posts for development forum, i will post this here, may be someone can move it to the right place, i'm not used to spam, but this 10 posts rule seems to encourage new users to spam 10 posts around...
move it here if you can
I think what you are addressing is exactly apeine's problem:
changed both uramdisk ... Booted with SD in and it either locks up or goes to regular nook (on 12 tries, 10 lock ups and 2 going to regular nook)
Click to expand...
Click to collapse
Incidentally, how long did it take to boot and work on the first try? With 1.0.1 firmware I rooted three nooks and left it for over 30 minutes on the first one without success. Then on the other two I was impatient and gave it two boots. So I never let 1.1.0 go on that long before rebooting since I assumed it was going nowhere.
Kralik said:
I think what you are addressing is exactly apeine's problem:
Click to expand...
Click to collapse
yes, that's why i wrote this, i cannot reply in the development section because i have too few posts on the forum
Kralik said:
Incidentally, how long did it take to boot and work on the first try? With 1.0.1 firmware I rooted three nooks and left it for over 30 minutes on the first one without success. Then on the other two I was impatient and gave it two boots. So I never let 1.1.0 go on that long before rebooting since I assumed it was going nowhere.
Click to expand...
Click to collapse
In my case it took slightly longer than a normal boot, no freeze at all, just about 1-2 minute on "Rooted Forever", then some time, may be 1-2 minutes on the nook dots screen with the dots moving (they never froze) and then the android guy page, no more than 4-5 minutes globally.
Anyway when i used touchnooter on 1.0.1 the first time, i had to reboot 2 times as you reported, same problem, more or less, may be the freezing at boot is something which happens, but not regularly
thank you for the description!
so if i understood correctly, there's no drawback with this method, everything works as it was before upgrade to 1.1.0, including the Market?
what about the installed apps, especially the non-free ones? (I've purchased OrientationControl)
can I simply download it from Market again, or should I backup the APK file and copy it back after upgrade/root?
glezmen said:
thank you for the description!
so if i understood correctly, there's no drawback with this method, everything works as it was before upgrade to 1.1.0, including the Market?
Click to expand...
Click to collapse
Yes, my nook behave exactly as with 1.0.1
glezmen said:
what about the installed apps, especially the non-free ones? (I've purchased OrientationControl)
can I simply download it from Market again, or should I backup the APK file and copy it back after upgrade/root?
Click to expand...
Click to collapse
No idea, never bought an app, just free ones, but to keep an .apk backup is always a safe choice
about orientation... i remember Orientation Switch and this (just in case someone wanted rotation for free)
glezmen said:
what about the installed apps, especially the non-free ones? (I've purchased OrientationControl)
can I simply download it from Market again, or should I backup the APK file and copy it back after upgrade/root?
Click to expand...
Click to collapse
You can re-install purchased apps from Market whenever you want.
Celebom said:
about orientation... i remember Orientation Switch and this (just in case someone wanted rotation for free)
Click to expand...
Click to collapse
thanks for the hint, I will have a look on it (especially if i can't download the app again for free )
btw 1 EUR was not a big pain (I tried ADW launcher and rotation before, but it was not really convenient)
As long as you have market working with your prior GMail account, you should have no problem redownloading both your free and paid apps.
Thanks. Worked like a charm.
I first installed Astro File Manager, which is the second one in the list under the "Productivity" -> "Top Free". This allows me to install Vending.apk (Market where the search function works), and then follow it with Titanium Backup.
Using Titanium Backup re-installed all the apps from my previous backup, plus installed the XorZone's NookTouchTools for 1.1 (jars are different from 1.0.1).
I'm not sure what the significant difference is between the firmwares, but I understanding that the screen refresh is a bit quicker, and that the battery report is more accurate (previously batt reading would fluctuate when first turned on).
As for the firmware upgrade.... my STR just did not want to download the upgrade, even though I set the screensaver to 1 hour. There could be several reason why this didn't work, such that I don't live in US, or the process of rooting had modified something (even thought I factory reset it).
In the end I just connected it using USB, and loaded it into the root directory of the my STR (a simply file copy in Windows XP). Then the upgrade started a minute after the copy.
Thanks for your guide! I've just finished rooting my 1.1 Nook Simple Touch firmware
Remember everybody :
ONLY REPLACE URAMDISK IN NOOTER/BOOT/ (OF TOUCHNOOTER .IMG FILE)
uRamdisk mirror?
Hello, guess I shouldn't have started without all the downloads but I assumed they would be somewhere? any alternative downloads for uRamdisk_rooted because all the links are broken.
Thanks
I want to root my nook simple touch - what works TODAY?
Hi all.
I find this thread interesting and helpful. I have noted that a lot of the information here, on nook developers, or in two articles I read (one in lifehacker.com and the other in Que Publishing) all contain help that includes links to files that are either not there or I can't find.
Can someone point me to a current simple solution that will allow me to root my nook and toggle between the original home screen and the better Android one?
Thanks in advance!
Halfhoff said:
Hi all.
I find this thread interesting and helpful. I have noted that a lot of the information here, on nook developers, or in two articles I read (one in lifehacker.com and the other in Que Publishing) all contain help that includes links to files that are either not there or I can't find.
Can someone point me to a current simple solution that will allow me to root my nook and toggle between the original home screen and the better Android one?
Thanks in advance!
Click to expand...
Click to collapse
ButtonSaviour should have been installed with the Root, so just look for a transparent(translucent?) arrow button thing on the right screen, near the middle. It might be hard to hit it. The Home button on that will be like hitting the Home button on a normal Android device, and when you press the Quick Nav button, the home on that will lead to the B&N home unless you used Xor's mods to change what it leads to.
broken link..........
+1
All the links that I find on the internet for the uRamdisk_rooted file appear broken also...
Markey1979 said:
All the links that I find on the internet for the uRamdisk_rooted file appear broken also...
Click to expand...
Click to collapse
uRamdisk, rooted, adb wireless, fixed init, 1.1 and 1.1.2
http://code.google.com/p/nst-recovery/downloads/detail?name=uRamdisk_wireless_adb_init_1.1_1.1.2.zip
uRamdisk, rooted, adb usb, fixed init, 1.1 and 1.1.2
http://code.google.com/p/nst-recovery/downloads/detail?name=uRamdisk_usb_adb_init_1.1_1.1.2.zip
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.
This is a public service announcement, in some unrelated research I just stumbled upon this bug in 2.0.4 kernel where it is unable to write data to external sdcard (not sure about internal), the kernel messages clearly show IO errors, but if you use android transfer (or whatever other mtp transfer tool) to write your files, no error is reported even though the files are badly damaged as result (not 100% of the time, but frequently enough, esp. if you are writing a lot of data).
Also sometimes nook just panics (and reboots) in the middle of a write.
Clearly there was nothing like that in 2.0 ROM, I have not really tried 2.0.2, so don't know how is the situation there.
If you have not updated to 2.0.4 and plan to heavily use external sdcard, it might be a good idea to skip this update and I hope B&N's next update will address this problem.
This means no harm if the nook updated to 2.0.4 when you first started the nook and it connected to the internet, right?
Only to those people who either had firmware previous to 2.0.4 and then update after use of the sdcard, right?
r1c47 said:
This means no harm if the nook updated to 2.0.4 when you first started the nook and it connected to the internet, right?
Only to those people who either had firmware previous to 2.0.4 and then update after use of the sdcard, right?
Click to expand...
Click to collapse
No, this means if you run 2.0.4, then reads and writes from/to sdcard (not sure about internal eemc) are unstable, can cause data corruption (i.e. write is claimed to succeed, but in reality it fails) and reboots of the device when accessing sdcard (due to kernel panics).
verygreen said:
No, this means if you run 2.0.4, then reads and writes from/to sdcard (not sure about internal eemc) are unstable, can cause data corruption (i.e. write is claimed to succeed, but in reality it fails) and reboots of the device when accessing sdcard (due to kernel panics).
Click to expand...
Click to collapse
Is it possible to revert back to a previous version? where can we download the firmware?
thank you.
carlyle070 said:
Is it possible to revert back to a previous version? where can we download the firmware?
thank you.
Click to expand...
Click to collapse
You can reset and it will take you back to 2.0.0. But when you try to register it will upgrade you. The only solution is to skip registration and immediately do someone0's all in one before turning on wifi. Skip registration by skipping OOBE as described in my HD+ tips thread linked in my signature. Then wait for B&N to fix the kernel with another update.
Or another option is to just not use an SD.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
You can reset and it will take you back to 2.0.0. But when you try to register it will upgrade you. The only solution is to skip registration and immediately do someone0's all in one before turning on wifi. Skip registration by skipping OOBE as described in my HD+ tips thread linked in my signature. Then wait for B&N to fix the kernel with another update.
Click to expand...
Click to collapse
Actually my updated 2.0.4 does not go back to 2.0 after reset, I already tried.
verygreen said:
Actually my updated 2.0.4 does not go back to 2.0 after reset, I already tried.
Click to expand...
Click to collapse
What does it go to? I meant complete reset, like 8 failed boots. Did it come with 2.0.4 out of the box?
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
What does it go to? I meant complete reset, like 8 failed boots. Did it come with 2.0.4 out of the box?
Click to expand...
Click to collapse
I believe it went to 2.0.4 The initial "registration" screen changed to the new way of doing things.
verygreen said:
I believe it went to 2.0.4 The initial "registration" screen changed to the new way of doing things.
Click to expand...
Click to collapse
If you got to the registration screen that means you let it update to 2.0.4 before that. To skip OOBE you need to catch it on the first screen, before you turn on wifi.
Skip OOBE instructions: Volume up, tap lower right screen. Choose factory, then volume up, tap lower right screen again. Select Skip OOBE.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
If you got to the registration screen that means you let it update to 2.0.4 before that. To skip OOBE you need to catch it on the first screen, before you turn on wifi.
Volume up, tap lower right screen. Chose factory, then volume up, tap lower right screen again. Select Skip OOBE.
Click to expand...
Click to collapse
Right.
So I did factory reset (home + power on startup, then home - home), once more right now to be sure.
On the first OOBE step it shows the screen with system info, and version listed there is already 2.0.4
If you look into 2.0.4 update log (in /cache/recovery), you can see they update /factory content there as well.
verygreen said:
Right.
So I did factory reset (home + power on startup, then home - home), once more right now to be sure.
On the first OOBE step it shows the screen with system info, and version listed there is already 2.0.4
If you look into 2.0.4 update log (in /cache/recovery), you can see they update /factory content there as well.
Click to expand...
Click to collapse
No, factory reset just clears data. You need to do 8 failed boots to get new system. Just interrupt boot eight times. Or you can add something to /system.
Edit: That factory they are updating is in /system/etc/factory. That is what tells them has been updated already. It is some patch files.
BTW, I was able to capture one of the update zips (the one for 2.0.4). It is 18 MB. I could send to you if you are interested.
Sent from my Nook HD+ Running CM10 on SD
verygreen said:
This is a public service announcement, in some unrelated research I just stumbled upon this bug in 2.0.4 kernel where it is unable to write data to external sdcard (not sure about internal), the kernel messages clearly show IO errors, but if you use android transfer (or whatever other mtp transfer tool) to write your files, no error is reported even though the files are badly damaged as result (not 100% of the time, but frequently enough, esp. if you are writing a lot of data).
Also sometimes nook just panics (and reboots) in the middle of a write.
Click to expand...
Click to collapse
I'm trying to parse this into practical terms: are you saying these errors occur when writing from a PC to /ext_sdcard over MTP, or only when writing to /ext_sdcard from the HD+ itself (i.e. downloading from a browser or copying files w/ a file manager)?
I've written quite a bit of data to a 64GB SD over MTP with no panick reboots and I've accessed some of those files quite heavily and not found any corrupted. In fact, I started using the HD+ for this purpose because the only card reader I had handy was failing with large tranfers (otherwise I would avoid MTP). I don't know that I've ever written to /ext_sdcard from the HD+ itself, though--all app data lands internally on /sdcard, and I mostly load media over USB, so for all intents and purposes the card could be read-only.
Out of curiosity, what kind of file transfers were you attempting when you got these errors (what kind of files/jobs from where to where)?
Taosaur said:
I'm trying to parse this into practical terms: are you saying these errors occur when writing from a PC to /ext_sdcard over MTP, or only when writing to /ext_sdcard from the HD+ itself (i.e. downloading from a browser or copying files w/ a file manager)?
Click to expand...
Click to collapse
both.
I've written quite a bit of data to a 64GB SD over MTP with no panick reboots and I've accessed some of those files quite heavily and not found any corrupted. In fact, I started using the HD+ for this purpose because the only card reader I had handy was failing with large tranfers (otherwise I would avoid MTP). I don't know that I've ever written to /ext_sdcard from the HD+ itself, though--all app data lands internally on /sdcard, and I mostly load media over USB, so for all intents and purposes the card could be read-only.
Out of curiosity, what kind of file transfers were you attempting when you got these errors (what kind of files/jobs from where to where)?
Click to expand...
Click to collapse
Well, check your dmesg. I guess it also depends on sdcard, but all cards I tried locally here report io errors with 2.0.4
I'll try to remember to check next time I'm moving files (assuming I don't migrate fully to CM10 in the meantime ). Otherwise I'll just ride it out--there's nothing too vital on the card that isn't duplicated elsewhere. Am I correct in thinking I'd have to run dmesg right after an operation to get useful data? Is there any way to check for errors or corruption after the fact?
Taosaur said:
I'll try to remember to check next time I'm moving files (assuming I don't migrate fully to CM10 in the meantime ). Otherwise I'll just ride it out--there's nothing too vital on the card that isn't duplicated elsewhere. Am I correct in thinking I'd have to run dmesg right after an operation to get useful data? Is there any way to check for errors or corruption after the fact?
Click to expand...
Click to collapse
dmesg after the write is the most sure-fire way.
You can try md5sum next time you reboot too, I guess. (to avoid cached copies that would be correct, till they expire from cache).
Okay, I have an HD, and I know that the kernels and the hardware are somewhat different. I'd like to see if this is an issue on the HD. I learned how to do dmesg. But what should I look for? The file is way too large to copy to this post. Thanks!
sent from my Nook HD using xda premium
So is there a way to go back to 2.0.0 and stop the auto update ?
sorrowuk said:
So is there a way to go back to 2.0.0 and stop the auto update ?
Click to expand...
Click to collapse
Yes, look a few posts back. Do the 8 failed boot (or add something to /system) and when it boots back up do the skip OOBE (instructions above). Then block automatic updates immediately either by using someone0's all-in-one or his settings mod which only does block OTA and unknown sources. His all-in-one is in it's own thread and his settings mod is in the second post of my HD+ tips thread.
It will auto update immediately if you don't skip OOBE. And if you skip OOBE you will not have access to your account.
So there is not a way to have access to your account and be on 2.0.0 ?
sorrowuk said:
So there is not a way to have access to your account and be on 2.0.0 ?
Click to expand...
Click to collapse
No, but if all you are wanting is access to your books, you can download the nook reader app and register that. You will have to use that reader which is not as nice as the stock reader though. And you still don't have access to your apps account.
You have to do the all-in-one in order to get the app on play store. Or if you have the app already you could sideload install it.
The simplest solution is to not use an SD with stock 2.0.4 and wait to see if B&N updates to a newer kernel without breaking root.
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
My nook touch (unrooted) runs 1.2.2, but it has bugs now ( the home button doesn't work most of time, screensaver goes on in several seconds during reading, etc. ). I think a reinstallation of the firmware may most likely resolve the issues. ( already tried erase and deregoster, doesn't change anything, as expected ). But the problem is after putting the update zip file into nook's root directory, nook just erases it without doing anything. So my question: any tool can be used to force nook reinstall the update zip without checking version number? Thx in advance for any help.
smjohn1 said:
My nook touch (unrooted) runs 1.2.2, but it has bugs now ( the home button doesn't work most of time, screensaver goes on in several seconds during reading, etc. ). I think a reinstallation of the firmware may most likely resolve the issues. ( already tried erase and deregoster, doesn't change anything, as expected ). But the problem is after putting the update zip file into nook's root directory, nook just erases it without doing anything. So my question: any tool can be used to force nook reinstall the update zip without checking version number? Thx in advance for any help.
Click to expand...
Click to collapse
You need to do a factory re-image so that the onboard OS version will be older than 1.2.2.
Power down. Then restart, and as soon as the "Read Forever" screen appears, press and hold the two lower hardware buttons. Wait for the prompt. Once the Nook is re-imaged it will accept the update again.
Thank you, but by two lower hardware buttons, you mean the page turning buttons?
nmyshkin said:
You need to do a factory re-image so that the onboard OS version will be older than 1.2.2.
Power down. Then restart, and as soon as the "Read Forever" screen appears, press and hold the two lower hardware buttons. Wait for the prompt. Once the Nook is re-imaged it will accept the update again.
Click to expand...
Click to collapse
Ha, I tried, but problem is the Home button doesn't work. Any other suggestions? Thanks.
smjohn1 said:
Ha, I tried, but problem is the Home button doesn't work. Any other suggestions? Thanks.
Click to expand...
Click to collapse
Yes the two lower "page turning" buttons. Is the "n" button used during that sequence? I didn't remember that. I guess that's in the prompts. Well, I dunno. NookManager can be used to trigger the factory image, but if you say that requires the not-working button, then you are SOL. Even CWM is going to need that button to select options.
nmyshkin said:
Yes the two lower "page turning" buttons. Is the "n" button used during that sequence? I didn't remember that. I guess that's in the prompts. Well, I dunno. NookManager can be used to trigger the factory image, but if you say that requires the not-working button, then you are SOL. Even CWM is going to need that button to select options.
Click to expand...
Click to collapse
Any tools that can be used to peek into Nook's file system through PC ( Linux ) to delete something and add something to trigger re/installation? The whole reason I am trying to reinstall is that the Home button doesn't work most of time, and I checked it is not a hardware problem.
smjohn1 said:
Any tools that can be used to peek into Nook's file system through PC ( Linux ) to delete something and add something to trigger re/installation? The whole reason I am trying to reinstall is that the Home button doesn't work most of time, and I checked it is not a hardware problem.
Click to expand...
Click to collapse
AFAIK what you want to do (if you knew exactly what) requires root access--which you don't have. There is an app that has an option which makes the NST very angry and triggers a no-escape factory reset (I've fallen victim to it once), but to install it you would need--you guessed it--root.
I honestly don't remember whether the factory reset option of NookManager is promptless or just the usual. Seems to me it just takes off once you remove the card and the device reboots, but I could be misremembering. I have another day of work on something and then I will be doing a reset on one of my devices, so I could tell you then.
nmyshkin said:
AFAIK what you want to do (if you knew exactly what) requires root access--which you don't have. There is an app that has an option which makes the NST very angry and triggers a no-escape factory reset (I've fallen victim to it once), but to install it you would need--you guessed it--root.
I honestly don't remember whether the factory reset option of NookManager is promptless or just the usual. Seems to me it just takes off once you remove the card and the device reboots, but I could be misremembering. I have another day of work on something and then I will be doing a reset on one of my devices, so I could tell you then.
Click to expand...
Click to collapse
Thank you very much. Waiting for your experiment results.
1) I can do root. But I couldn't find the package any more. Any pointers?
2) What do you by removing the card? Which card? I was planning to open the back cover and remove the battery, but then I found out you would need a T5 Torx screwdriver, which I don't have. So I gave up.
smjohn1 said:
Thank you very much. Waiting for your experiment results.
Click to expand...
Click to collapse
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.
nmyshkin said:
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.
Click to expand...
Click to collapse
Thanks a lot and I am in US!
Everything you said was correct with only one minor thing: NookManager doesn't have to be updated to 1.2.2. As is, it will boot. But after factory re-image, 1.2.2 has to be applied, otherwise Nook cannot register due to Nook server's TLS issue even NST says network connection problem.
Thanks again for this wonderful guide. Hope this is useful to other (unlucky) people.
As for my NST, after reinstallation, the Home button still doesn't work. So I have to believe it seems to be hardware problem and the cover has to be opened.
nmyshkin said:
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.
Click to expand...
Click to collapse
See the previous one.
smjohn1 said:
Thanks a lot and I am in US!
Everything you said was correct with only one minor thing: NookManager doesn't have to be updated to 1.2.2. As is, it will boot. But after factory re-image, 1.2.2 has to be applied, otherwise Nook cannot register due to Nook server's TLS issue even NST says network connection problem.
Thanks again for this wonderful guide. Hope this is useful to other (unlucky) people.
Click to expand...
Click to collapse
Yes the only reason to update NookManager is to root 1.2.2
I'm sorry about the apparent hardware issue. I don't know where to go with that, but just to throw this out: rooting with NM installs NookTouchMod which would allow you to reassign the "n" button function to another hardware button. Awkward and less than ideal but perhaps a way to salvage the device if all else fails.
nmyshkin said:
Yes the only reason to update NookManager is to root 1.2.2
I'm sorry about the apparent hardware issue. I don't know where to go with that, but just to throw this out: rooting with NM installs NookTouchMod which would allow you to reassign the "n" button function to another hardware button. Awkward and less than ideal but perhaps a way to salvage the device if all else fails.
Click to expand...
Click to collapse
Wonderful and thx again!
Already rooted, and after reboot, saw "Home" and "ReLauncher", chose "ReLauncher", and then the setting icon at upper right. Lots of functions, but didn't see NookTouchMod or where can set up buttons functions. Only saw "Screen buttons behavior" in the Advanced Settings, but these are not to set hardware buttons.
The only I need is in a book reading mode, press a button to return to the library, so that can switch to another book easily. But I guess I am closer now
smjohn1 said:
Wonderful and thx again!
Already rooted, and after reboot, saw "Home" and "ReLauncher", chose "ReLauncher", and then the setting icon at upper right. Lots of functions, but didn't see NookTouchMod or where can set up buttons functions. Only saw "Screen buttons behavior" in the Advanced Settings, but these are not to set hardware buttons.
The only I need is in a book reading mode, press a button to return to the library, so that can switch to another book easily. But I guess I am closer now
Click to expand...
Click to collapse
Mmm....Relaunch. Not my favorite, but many people like it for its "simplicity". There is a way in Relaunch to get to an "app drawer" type screen which shows all the installed apps. That's where you'll find NTM and everything else. The sad truth is, I can't tell you how to get there. For me, Relaunch is counter-intuitive and strange, but I do know that thereis an app drawer as I have seen it myself back in the day when all this was new to me. I've done a cursory forum search but come up empty. That's the other thing that always riled me up about Relaunch. It's like its operations are a secret. There must be documentation somewhere, but I don't know where. I have a vague recollection that at the center bottom of some screen or another there is an actual app drawer symbol, but getting to that magic screen is the issue.
I'll keep looking, but right now I'm coming up empty.
Edit: in the long run, once you find NTM and reassign the "n" button, you might be better served by having the standard B&N home screen as your default launcher. This would provide you with your accustomed functions, easy access to the Library via the quick-nav buttons, etc. You could assign along press of the same button to bring up Relaunch for the few times you'll want it.
nmyshkin said:
Mmm....Relaunch. Not my favorite, but many people like it for its "simplicity". There is a way in Relaunch to get to an "app drawer" type screen which shows all the installed apps. That's where you'll find NTM and everything else. The sad truth is, I can't tell you how to get there. For me, Relaunch is counter-intuitive and strange, but I do know that thereis an app drawer as I have seen it myself back in the day when all this was new to me. I've done a cursory forum search but come up empty. That's the other thing that always riled me up about Relaunch. It's like its operations are a secret. There must be documentation somewhere, but I don't know where. I have a vague recollection that at the center bottom of some screen or another there is an actual app drawer symbol, but getting to that magic screen is the issue.
I'll keep looking, but right now I'm coming up empty.
Click to expand...
Click to collapse
You are right again. I do see "app drawer" at the bottom. Inside there are things like "library", "setting", "app (amazon)", "Kconnect", etc., just couldn't find NTM.
I could reboot to Home too, but I didn't find NTM either. Anyhow, I will dig and search too, and report back here.
Thx again.
smjohn1 said:
You are right again. I do see "app drawer" at the bottom. Inside there are things like "library", "setting", "app (amazon)", "Kconnect", etc., just couldn't find NTM.
I could reboot to Home too, but I didn't find NTM either. Anyhow, I will dig and search too, and report back here.
Thx again.
Click to expand...
Click to collapse
You're fast.
Info on basic ReLaunch functions here: https://github.com/yiselieren/ReLaunch. NTMM icon looks like big bold "n" with a bold little broken circle in it. Gotta be there.
Edit: ...unless....something went awry during the rooting process. You can root "again" with no harm/no foul and watch carefully this time the list of "dones" to make sure it did not throw an error for NTMM.
nmyshkin said:
You're fast.
Info on basic ReLaunch functions here: https://github.com/yiselieren/ReLaunch. NTMM icon looks like big bold "n" with a bold little broken circle in it. Gotta be there.
Edit: ...unless....something went awry during the rooting process. You can root "agai n" with no harm/no foul and watch carefully this time the list of "dones" to make sure it did not throw an error for NTMM.
Click to expand...
Click to collapse
OK, I think I need to go back to basics:
1. here is the NM used: http://download.doozan.com/nook/NookManager-0.5.0.zip
2. Here are some screen shots from relaunch:
1) relauncher
2) all apps installed ( from the middle icon at the bottom ): no NTMM there
3) and 4) settings ( from right icon at the top )
3. I don't see a way to install other Android apps, except from Amazon stores ( which I didn't try ) but not from Google App store. Did I install a "wrong" version of NM?
4. One more thing: I "rooted" again, finished quickly, and no changes after boot ( My guess is NM sees the same root package to decide not to do anything ).
Any advice?
----------------------------------------------------------------------------------------------------
After posting above, I installed NTMM-0.4.0.apk successfully, but it says it needs modified jars. From https://forum.xda-developers.com/showthread.php?t=1991048 and https://github.com/doozan/NookTouchPatches.
So NTMM wasn't installed during root.
Now my questions:
how to install these patches? I am using Linux with no adb ( I don't want to use adb anyway ), any apk file that can be written to sdcard for quick and easy installation?
and does this patch work for 1.2.2?
smjohn1 said:
OK, I think I need to go back to basics.
Click to expand...
Click to collapse
Yes, I think you missed some important points from what I wrote previously. Here is the only sequence that is going to give you the desired result:
1. Factory re-image
2. Install 1.22 update
3. Register
4. Prepare NookManager card from here.
5. Update NookManager card following the directions here. You MUST do at least the update for 1.2.2 or root will not be successful and your device will be messed up. Other updates are optional, but know that some apps like Amazon App Store are dead. Other updates deal with these issues.
6. Boot with the NookManager card inserted.
*Optional* 7. Make a back-up of your registered device running 1.2.2. This can save you extra steps if you need to go back for any reason or suffer some catastrophe that seriously messes with your system.
8. Root using NookManager. Watch the screen for check for any failures.
9. Reboot, choosing ReLaunch as a launcher (but do not set as default yet).
10. Use NTMM to assign "n" button function ("Home") to some other hardware button. This is how you will get to QuickNav buttons.
11. Use NTTM to assign long-press of your reassigned "n" button to ReLaunch.
12. Reboot.
13. Select "Home" as default launcher (i.e., check the little box before choosing "Home". This choice can be changed later if you want.
Now you're back to a functioning system. Additional apps are installed by moving the apk file from your PC to a folder on your NST ("Download"?) and tapping the app icon in ReLaunch. Apps are uninstalled by long-pressing the app icon (I think).
The Amazon App Store is useless as you can read in the directions for updating NookManager.
Don't skip any steps.
nmyshkin said:
Yes, I think you missed some important points from what I wrote previously. Here is the only sequence that is going to give you the desired result:
1. Factory re-image
2. Install 1.22 update
3. Register
4. Prepare NookManager card from here.
5. Update NookManager card following the directions here. You MUST do at least the update for 1.2.2 or root will not be successful and your device will be messed up. Other updates are optional, but know that some apps like Amazon App Store are dead. Other updates deal with these issues.
6. Boot with the NookManager card inserted.
*Optional* 7. Make a back-up of your registered device running 1.2.2. This can save you extra steps if you need to go back for any reason or suffer some catastrophe that seriously messes with your system.
8. Root using NookManager. Watch the screen for check for any failures.
9. Reboot, choosing ReLaunch as a launcher (but do not set as default yet).
10. Use NTMM to assign "n" button function ("Home") to some other hardware button. This is how you will get to QuickNav buttons.
11. Use NTTM to assign long-press of your reassigned "n" button to ReLaunch.
12. Reboot.
13. Select "Home" as default launcher (i.e., check the little box before choosing "Home". This choice can be changed later if you want.
Now you're back to a functioning system. Additional apps are installed by moving the apk file from your PC to a folder on your NST ("Download"?) and tapping the app icon in ReLaunch. Apps are uninstalled by long-pressing the app icon (I think).
The Amazon App Store is useless as you can read in the directions for updating NookManager.
Don't skip any steps.
Click to expand...
Click to collapse
Ha, the step missed was 5, as it was difficult to change the files. But I remade an NM card ( there must be something wrong with the old one ), afterwards it was to update NM to 1.2.2.
Now buttons are reassigned and this reader is usable again ( I don't plan to make it a full android pad, as there are already too many tablets in house ). So this e-reader owes its life to you. Big thanks!
One last thing: how to reset Default back to Home instead of Relaunch? ( The re-root was quick, as it probably installed NTMM. But reboot doesn't give chance to reset default back to Home, it still goes straight to Relaunch. Of course I can live with it, but it would be nicer to configure as you suggested. )
smjohn1 said:
One last thing: how to reset Default back to Home instead of Relaunch? ( The re-root was quick, as it probably installed NTMM. But reboot doesn't give chance to reset default back to Home, it still goes straight to Relaunch. Of course I can live with it, but it would be nicer to configure as you suggested. )
Click to expand...
Click to collapse
If there is a way to access the App Manager through ReLaunch, you can run down the list until you get to ReLaunch and there remove any default actions associated with it.
If that is not obvious then the next easiest thing is to install yet another launcher! So you could transfer a copy of ADW Launcher from the NookManager update page to your NST and install it. If you then reboot it will trigger the App Picker dialog again because now there is a new choice. Before you select "Home", be sure to tick the little check box.
Then you can uninstall ADW Launcher. It's possible that may trigger another App Picker with the remaining two choices but I don't think so.
Once that's sorted you can finish your button reassignments. I think ReLaunch actually hijacks some of the QuickNav buttons so you might have to use NTTM to return them to default or pick completely new assignments, as you like.
I'm glad you were able to get the device back in a usable state. I love my NST for reading. After all these years I think it's still a great little piece of technology.