Database Users

[Q] Firmware Upgrading

I have a Nook Simple Touch eReader. Info says its Model Number is BNRV300.
I want to upgrade Firmware from 1.0.0 to 1.1.2 or something like that.
I have tried to update it using an image that should upgrade the firmware. But it did't.
I saw the Device info after doing that and it showed me that firmware were actually 1.0.0.
It didn't change at all.
I though it was updated (so I think info was not true) when i tried to root the device with the rooter made for 1.1.
After rooting the eReader became crazy!!!
It didn't turn on until I reset it twice. And when I say reset, I mean Factory Reset.
That is erasing every configuration and everything else from the Nook by pressing power button before pressing for 1 min down buttons.... The first time it erased all the things that were in the memory and configurations.
The second time, it installed the original Firmware image again.... The time between the rooting and the second reset was awful.
I really though that my eBook was dead... :crying:
But it's not. It's alive due to the Factory Reset that comes with the device.
I want to upgrade it 'cause the Android that lasts when I make the rooting is horrible.
The Internet Search doesn't work. The Android market neither. The only things that work are Facebook, Google Talk, Calculator and Book Reader that comes with the Nook.
I would like to install at least another PDF Reader (the original one is only useful to reading literature. If I want to read some of my study books (things that I do so often because of the college). It's really uncomfortable. The font size is so TINY. I can't see it. That happens because those texts have images, and the reader doesn't fit them. I want to see texts turning the screen. This would help me a lot...), Oxford Dictionary (my mother language is not English. Excuse me if I make grammar mistakes. Thanks to the Google chrome spell checker also....), DRAE (Spanish Royal Academy's Dictionary), and make Opera Mini work.
I installed Opera Mini. It crashes when launched... Office viewers crash too.
This Android is really annoying
It's not useful at all!!!
Rooter used to root Nook: touchnooter-1-6-24.zip
Thanks for your attention. I hope you answer
PD: Internet says I can upgrade this nook to 1.1 I ask if I can upgrade to 1.1.2 or something higher.
How can I root it without that frightening risk of having Nook dead in the way it was before due to the upgrading and rooting???

The latest update is 1.2.1 and is available on the nook site. Or I posted a CWM package to do it.
https://sites.google.com/site/xcdguides/nook/nookregion

Root Device
theronkinator said:
The latest update is 1.2.1 and is available on the nook site. Or I posted a CWM package to do it.
Click to expand...
Click to collapse
Thank you. I'm doing what you say right now. I'll tell you if it works.
Also I have a doubt. How can I do the rooting in a relatively safe way? I need the Android functions. Specially Market to download applications and Opera mini. I don't know a better web browser for Android.
That's just to read some blogs. Um! I forgot to ask if there is a way to unlock android installer...
I tried to install an APK application downloaded from Internet (The Oxford Dictionary) and Android tell me it was not able to install applications who don't come from Android Market....
If it is possible, thank you. If not, thank you too

It worked!!
theronkinator said:
The latest update is 1.2.1 and is available on the nook site. Or I posted a CWM package to do it.
Click to expand...
Click to collapse
You are a ****ING GENIUS!!!
This thing worked perfectly. I have 1.2.1 installed. Thank u a lot.
Now I ask again for the rooting, if it's not so annoying. THANKS THANKS

I rooted my nook myself and didn't use any of the methods posted on here, it took me ages of trying different methods to get it all working, used adb, cwm packages etc, unless you know what you're doing, you'd be better using one of the premade packages here
http://forum.xda-developers.com/showthread.php?t=2040351
and here:
http://forum.xda-developers.com/showthread.php?t=2086582

theronkinator said:
I rooted my nook myself and didn't use any of the methods posted on here, it took me ages of trying different methods to get it all working, used adb, cwm packages etc, unless you know what you're doing, you'd be better using one of the premade packages here
http://forum.xda-developers.com/showthread.php?t=2040351
and here:
Click to expand...
Click to collapse
Thanks to everyone. I have already rooted my Simple Touch. It's beautiful.
I have just another question.
It's a little annoying for me to use a different reader from Barnes and Noble's one.
This one is really good. It has just the problem that it has no zoom, and it has not the ability of rotating the document....
I've tried with several PDF readers. The only one who has an relatively acceptable behavior is ezPdf, but it's not good...
That's the only thing I'm still needing. I have now Oxford Advanced Learner's Dictionary, a Spanish definitions dictionary and a Spanish-German Dictionary. Those three ones were fully installed in the SD. There's not need to have wi-fi turned on to look for meanings or translations!!! :laugh:
This point was a full success. I'm really happy to have those dictionaries in my Nook. That stuff is absolutely useful :victory:
But I have just this little point. Excuse me if I go too far
I will make a more accurate question. Is there a PDF reader, compatible with Android 2.1, similar to Barnes and Noble's one (I mean, as good as Barnes and Noble's Reader ), that is able to zoom and rotating the document?
Or an almost equivalent question: Can I patch in any way this reader to have, specially, the ability of rotating the screen?
I have configured the device in the way it shows me almost everything, but not reader , in landscape mode.... How can I make the reader show things in this mode?, as Opera and the most of the other applications do... ::good:
Thank you again.
The Noot Manager is just AMAZING.
And the CWM based upgrading is amazing too

It's a hilarious thing to realize that when you make a question in these forums, it happens often that you answer your own question by searching a little in the Internet.
I found the answer for my question, curiously, in this forum.
And this PDF Viewer is THE ONE: forum.xda-developers.com/showthread.php?t=1186949
An open source applications modified by a guy of the community xda-developers
This is the closest thing I found to Barnes & Noble's reader application.
It renderizes very quickly. It save some data on a cache up to 10MB. And another useful thing: It's able to rotate de document!!!
It's just what i was searching for :victory:
Thank you for everything.

[Q] Nook ST Glowlight Root Not Working at All

I was given the impression by many sites posting a Nook Simple Touch with Glowlight as rooted and a working Google Play.
I got the instructions here: http://forum.xda-developers.com/showthread.php?t=1675706 and followed the links to those files. I'm on Linux, so dd is no problem.
The rooting process was not difficult, but almost nothing works.
-Both browsers launch, but do not do anything despite trying a search phrase or URL.
-Google play does not launch. No feedback. Just nothing.
-Nook ColorTools doesn't launch.
-Amazon Marketplace works, but, since the device is locked to B&N, I can't install Overdrive.
-The "settings" button points to the B&N Nook settings.
-If I'm not careful, I end up at the B&N home screen and cannot get back to the Android desktop. For example, trying to launch Android's settings puts me in the B&N settings and I cannot return to the Android environment.
My original goal was to use the device to read books from my library system using Overdrive app. It's a new-ish device as of 2013-October. Maybe it's not well suited, or something has changed?
Not sure where to start for useful information to track down the issues. Is there a way to turn on logging so there's some information to post?
Thanks for your patience.

There are lots of images and lots of tools floating around and coincidentally, lots of strangeness.
In response to "fails, no feedback, just nothing", I'm sure that logcat is telling exactly what the problem is.
You need to acquaint yourself with logcat and post selected bits of it here.
On any system there is just one Settings.apk and SettingsProvider.apk.
Whichever you have (B&N custom or Android stock) will determine what you see.
I use library books all the time without hacking the DRM.
I don't use the OverDrive app on the Nook because it ties you to the OverDrive reader (which is a piece of junk).
I use Adobe Digital Editions on my desktop and the stock B&N reader.
(There is no evil tie to B&N that prevents you from installing OverDrive or anything else.)
Getting back to a launcher requires a hacked android.policy.jar
It also requires that you selected the launcher as your default Home intent completer.
ButtonSavior can be used if you don't have a hacked jar.

What I would have added to that guide you linked to as requirement would be to make sure you have a backup first before rooting/installing gapps.
Things certainly don't sound like everything is installed and happy.
Being a newish device you will on firmware 1.2 perhaps even 1.2.1 a lot of older threads / tools / tweaks can be for v1.0 or v1.1. If you are on 1.2 then update to 1.2.1 before rooting. There are also minor differences between having a US and UK version firmware.
Get Google apps on NST NSTG sometimes can take a day or so. Signing into youtube sometimes helps. Searching for apps may require the search market app.
If you have a backup restore and try Nookmanager its a bit more user friendly.
---------- Post added at 11:00 PM ---------- Previous post was at 10:27 PM ----------
Try to avoid using class 10 sdcard for your rooting I have read there are problems without kernel fixes [Although that's pure theory on my part I've used them in the past. Then again I did not think to check log for problems like that then)
I really don't want to compile one myself presently as I have no environment setup and those that I've seen like latuk's here don't have support for glowlights.

The device was running 1.2.1 What ended up working was NookManager with NTGAppsAttack.
Renate, my nook default glowlight had no method to browse the Internet with the stock firmware, and my local library system has an app that installed easily once I could use a browser. It looks like the library system's app does all the DRM then downloads. The device still has the B&N apps, so I'll try to read the books from the library in it.
Thanks to all.

asphalt_jesus said:
Renate, my nook default glowlight had no method to browse the Internet with the stock firmware,
.
Click to expand...
Click to collapse
You should have a browser on stock. Its called browser.

Crispy3000 said:
You should have a browser on stock. Its called browser.
Click to expand...
Click to collapse
If it did, it wasn't obvious. It booted to a B&N URL where I could do B&N book consuming, but that's it. No browser settings under the "settings" menu, no Android-style menu to list/execute installed apps on the device.
It's entirely possible I missed it. I was busier trying to root the thing.:victory:

Google Books: no basket/cart so can't buy books.

Using gbooks_10_16.apk I can search and get a book list, but nothing happens when I click a book. The basket/cart and pay apparatus is missing. Does anyone know how I can fix this?
I've also tried gb152.apk, but this doesn't seem to work at all.
I rooted with Nook Manager and then ran NTGAppsAttack (both v.050). NTGAppsAttack went fine until I clicked on Market only to find there were no apps at all anywhere. I left the Nook near my wifi, with wireless on, for hours and finally What's App appeared. I'd have preferred something simpler, but installed it anyway and then, having doubts, uninstalled via the Apps Drawer. I then upgraded the Market and installed SearchMarket, which just brings up the search keyboard. However, it finds apps, thpough only free ones, and downloads them. The Market still shows only What's App, though something else appeared briefly. There was no Books app in the Apps Drawer, so I downloaded the above versions.

caromcm said:
Using gbooks_10_16.apk I can search and get a book list, but nothing happens when I click a book. The basket/cart and pay apparatus is missing. Does anyone know how I can fix this?
I've also tried gb152.apk, but this doesn't seem to work at all.
I rooted with Nook Manager and then ran NTGAppsAttack (both v.050). NTGAppsAttack went fine until I clicked on Market only to find there were no apps at all anywhere. I left the Nook near my wifi, with wireless on, for hours and finally What's App appeared. I'd have preferred something simpler, but installed it anyway and then, having doubts, uninstalled via the Apps Drawer. I then upgraded the Market and installed SearchMarket, which just brings up the search keyboard. However, it finds apps, thpough only free ones, and downloads them. The Market still shows only What's App, though something else appeared briefly. There was no Books app in the Apps Drawer, so I downloaded the above versions.
Click to expand...
Click to collapse
So just to be sure, you are using the NST?
You will see very few/no apps via the Market app. Sometimes the category list will dredge up an app or two (free), but you need SearchMarket to find anything. I think you are right about only free apps. It may be that the old apps cannot negotiate the security transactions for paid apps.
And on that topic, the non-function of the store in Gbooks is your least problem. Have you noticed that it doesn't upsync?! I and others have done a pretty thorough investigation of the various versions that will run on the NST.. The version you mention has a functioning reader but can't upsync. I think up to 1.3.5 the reader still works (going from memory here...) but no upsync. The oldest version that will currently sync is maybe 1.5.2, but only if you can get the book to actually display, which is more miss than hit.
I played with Gbooks for a long time, even though I've never used it. I don't think it's doable without a serious rewrite of the source.

If you haven't already, you'll need to update the certificates on your nook as described in this thread: http://forum.xda-developers.com/showthread.php?p=65344931
Some older versions of Google Books will work, but maybe not all of the features. I have Books version 1.2.2 and can download purchased books from my library, although I purchased them on other devices. You can't purchase books on the old version of the Market or the books app since our nooks don't have Google Play Services, but you should be able to download books purchased on other devices (but same account.
You won't find many compatible apps in the Market at this point, and purchased apps have to be downloaded to other devices and then side loaded to the nook (assuming they're compatible). Some older working versions of apps can be found here on XDA.

cjpicci said:
If you haven't already, you'll need to update the certificates on your nook as described in this thread: http://forum.xda-developers.com/showthread.php?p=65344931
Some older versions of Google Books will work, but maybe not all of the features. I have Books version 1.2.2 and can download purchased books from my library, although I purchased them on other devices. You can't purchase books on the old version of the Market or the books app since our nooks don't have Google Play Services, but you should be able to download books purchased on other devices (but same account.
You won't find many compatible apps in the Market at this point, and purchased apps have to be downloaded to other devices and then side loaded to the nook (assuming they're compatible). Some older working versions of apps can be found here on XDA.
Click to expand...
Click to collapse
Does your version upsync? If so can you post a copy of the apk?

nmyshkin said:
So just to be sure, you are using the NST?
You will see very few/no apps via the Market app. Sometimes the category list will dredge up an app or two (free), but you need SearchMarket to find anything. I think you are right about only free apps. It may be that the old apps cannot negotiate the security transactions for paid apps.
And on that topic, the non-function of the store in Gbooks is your least problem. Have you noticed that it doesn't upsync?! I and others have done a pretty thorough investigation of the various versions that will run on the NST.. The version you mention has a functioning reader but can't upsync. I think up to 1.3.5 the reader still works (going from memory here...) but no upsync. The oldest version that will currently sync is maybe 1.5.2, but only if you can get the book to actually display, which is more miss than hit.
I played with Gbooks for a long time, even though I've never used it. I don't think it's doable without a serious rewrite of the source.
Click to expand...
Click to collapse
Yes, I'm using the NST. I haven't looked at syncing because as I understand it this is just a question of convenience when reading on multiple devices, which is not my aim. I just want to get books onto the Nook. Many thanks.

cjpicci said:
If you haven't already, you'll need to update the certificates on your nook as described in this thread: http://forum.xda-developers.com/showthread.php?p=65344931
Some older versions of Google Books will work, but maybe not all of the features. I have Books version 1.2.2 and can download purchased books from my library, although I purchased them on other devices. You can't purchase books on the old version of the Market or the books app since our nooks don't have Google Play Services, but you should be able to download books purchased on other devices (but same account.
You won't find many compatible apps in the Market at this point, and purchased apps have to be downloaded to other devices and then side loaded to the nook (assuming they're compatible). Some older working versions of apps can be found here on XDA.
Click to expand...
Click to collapse
Many thanks. This is very interesting, but I'll have to wrap a wet towel round my head before going back to the thread you suggest! Too late at night now.

nmyshkin said:
Does your version upsync? If so can you post a copy of the apk?
Click to expand...
Click to collapse
It seems to upsync last read pages, roughly anyway since the formatting varies for different devices. Since this old version doesn't support anything like notes or highlights, I'm not sure what else it could sync.
What's the best/most practical way to share files on xda? While I've been lurking for quite some time, I only created an account fairly recently.

cjpicci said:
It seems to upsync last read pages, roughly anyway since the formatting varies for different devices. Since this old version doesn't support anything like notes or highlights, I'm not sure what else it could sync.
What's the best/most practical way to share files on xda? While I've been lurking for quite some time, I only created an account fairly recently.
Click to expand...
Click to collapse
You can attach the apk file using the options below as you compose your reply or if you're not able to do that yet you can provide a link to any safe place where you can store a copy (Dropbox, etc.) so that people can access the file.
This is sort of amazing. I've never run into a version number like that and am really curious to see what it can do. Casual reading and syncing are all I would care about.

nmyshkin said:
You can attach the apk file using the options below as you compose your reply or if you're not able to do that yet you can provide a link to any safe place where you can store a copy (Dropbox, etc.) so that people can access the file.
This is sort of amazing. I've never run into a version number like that and am really curious to see what it can do. Casual reading and syncing are all I would care about.
Click to expand...
Click to collapse
I've solved my problem now. I've been trying to download books from Google, first to my NookST and then to my laptop. But I'm running 32-bit Linux on my laptop and Google, like Adobe, seems determined to exclude Linux from the world of ebooks. So I downloaded to my Android phone and was quite surprised when the book also appeared on my Nook. I was offered the option of syncing, but decided not to be too ambitious in case it caused problems with the rather old Nook software.
It may have helped that I did all the NTGAppsAttack process on my Nook (I didn't want to go to the laptop because of the Linux problem). After I typed in my phone number I first tried to confirm on the phone and, when that didn't work, typed in the confirm number on my Nook. So perhaps the 2 devices finally got quite firmly linked.
I'll have a go at attaching the Google Books version I'm using, gbooks_10_16.apk.
I got it from another post on this forum. The reader works well but doesn't have a search facility.

nmyshkin said:
You can attach the apk file using the options below as you compose your reply or if you're not able to do that yet you can provide a link to any safe place where you can store a copy (Dropbox, etc.) so that people can access the file.
This is sort of amazing. I've never run into a version number like that and am really curious to see what it can do. Casual reading and syncing are all I would care about.
Click to expand...
Click to collapse
Here's the md5 for the attached file generated by Android File Verifier:
bde6462cde86e0521d0b78270e11adb4
I think I probably got this apk when it was posted a long time ago, but I can't remember for sure. I just let Lookout scan it again and it came up "safe", for whatever that's worth.

cjpicci said:
Here's the md5 for the attached file generated by Android File Verifier:
bde6462cde86e0521d0b78270e11adb4
I think I probably got this apk when it was posted a long time ago, but I can't remember for sure. I just let Lookout scan it again and it came up "safe", for whatever that's worth.
Click to expand...
Click to collapse
Well done!! People have been searching for a version of GBooks that would sync for years! I can confirm that this works with free books from Google as well as user-uploaded books. I don't have any books purchased from Google so could not check that.
As with other versions, it helps to have a hardware key assigned to "menu" in order to access things like font size, etc., while reading (I use a long-press of the lower right button).
This is really a great discovery. I'll have to update the various other threads with a pointer to your post.

nmyshkin said:
Well done!! People have been searching for a version of GBooks that would sync for years! I can confirm that this works with free books from Google as well as user-uploaded books. I don't have any books purchased from Google so could not check that.
As with other versions, it helps to have a hardware key assigned to "menu" in order to access things like font size, etc., while reading (I use a long-press of the lower right button).
This is really a great discovery. I'll have to update the various other threads with a pointer to your post.
Click to expand...
Click to collapse
Glad it's working for you too! I can't remember for sure, but I think this version might've been recommended by someone else before. I'll have to look through my old bookmarks...

nmyshkin said:
Well done!! People have been searching for a version of GBooks that would sync for years! I can confirm that this works with free books from Google as well as user-uploaded books. I don't have any books purchased from Google so could not check that.
As with other versions, it helps to have a hardware key assigned to "menu" in order to access things like font size, etc., while reading (I use a long-press of the lower right button).
This is really a great discovery. I'll have to update the various other threads with a pointer to your post.
Click to expand...
Click to collapse
Thanks for all the info, guys. Second time you've steered me in the right direction, nmyshkin. NB Attaching the apk file was difficult because the process was incredibly slow (and not even a whirligig). Lots of notices about scripts that had stalled. I'm running Linux Mint 17 (Cinnamon) 32-bit; browser is Firefox.

My rooted unregistered Nook Simple Touch chews battery like crazy

I got a Like New NST, reset it, unregistered it, and rooted it. I haven't replaced the kernel yet. But I have noticed that (even before I rooted it) the battery consumption is unacceptable. I've seen some old threads about this (for example https://forum.xda-developers.com/showthread.php?t=1475070) , and some suggested removing some APKs like Phone.apk and TelephonyProvider.apk, while others suggested removing or disabling some B&N-related APKs.
The thing is that some other threads seem to imply these solutions are bogus and that they don't really help. There is a lot of conflicting information spread around on this topic.
Does anybody know if there is a solution to this issue? I'm really loving the NST, it's an amazing reader in all ways except for this glaring issue.
Thanks!

Winston S. said:
I got a Like New NST, reset it, unregistered it, and rooted it. I haven't replaced the kernel yet. But I have noticed that (even before I rooted it) the battery consumption is unacceptable. I've seen some old threads about this (for example https://forum.xda-developers.com/showthread.php?t=1475070) , and some suggested removing some APKs like Phone.apk and TelephonyProvider.apk, while others suggested removing or disabling some B&N-related APKs.
The thing is that some other threads seem to imply these solutions are bogus and that they don't really help. There is a lot of conflicting information spread around on this topic.
Does anybody know if there is a solution to this issue? I'm really loving the NST, it's an amazing reader in all ways except for this glaring issue.
Thanks!
Click to expand...
Click to collapse
I sympathize and don't want to add to the conflicting information. Read what I wrote here: https://forum.xda-developers.com/showpost.php?p=78287581&postcount=2 under "Decrapify system/app". I can tell you definitively that Phone.apk has little or nothing to do with your battery drain. I did a major study on that issue a long time ago: https://forum.xda-developers.com/nook-touch/general/battery-usage-phone-apk-t3341370

nmyshkin said:
I sympathize and don't want to add to the conflicting information. Read what I wrote here: https://forum.xda-developers.com/showpost.php?p=78287581&postcount=2 under "Decrapify system/app". I can tell you definitively that Phone.apk has little or nothing to do with your battery drain. I did a major study on that issue a long time ago: https://forum.xda-developers.com/nook-touch/general/battery-usage-phone-apk-t3341370
Click to expand...
Click to collapse
Thank you for all your work, you are very methodic and logical, and I appreciate your generosity sharing all your knowledge about the NST (I have been reading up on different things here before I decided to buy one.) :good:
So, to condense all this, it looks as if neither deleting Phone.apk nor disabling B&N apps helps with battery consumption. Also, am I correct in concluding that having an unregistered Nook (or a Nook which is offline, even if registered) will invariably result in poor battery life? That's quite unfortunate, as I was planning to use my NST as a fully offline device.

Winston S. said:
So, to condense all this, it looks as if neither deleting Phone.apk nor disabling B&N apps helps with battery consumption. Also, am I correct in concluding that having an unregistered Nook (or a Nook which is offline, even if registered) will invariably result in poor battery life? That's quite unfortunate, as I was planning to use my NST as a fully offline device.
Click to expand...
Click to collapse
Almost, but fortunately not quite right. Although B&N did some questionable stuff when they cobbled together the NST/G system, I don't think they expected the devices to spend a lot of time online. If the system detects that there is no WiFi, it just slaps a post-it on its internal "refrigerator" to remind it to try a check-in later. All of that happens pretty quickly and in the grand scheme of things Android where stuff is not always killed outright even when you've finished with it, it's not a Big Deal.
So register and forget. It's the easiest path to device stability and the intended power consumption pattern.

nmyshkin said:
Almost, but fortunately not quite right. Although B&N did some questionable stuff when they cobbled together the NST/G system, I don't think they expected the devices to spend a lot of time online. If the system detects that there is no WiFi, it just slaps a post-it on its internal "refrigerator" to remind it to try a check-in later. All of that happens pretty quickly and in the grand scheme of things Android where stuff is not always killed outright even when you've finished with it, it's not a Big Deal.
So register and forget. It's the easiest path to device stability and the intended power consumption pattern.
Click to expand...
Click to collapse
Thank you again, I suppose if that's the case then I will register my NST. A couple questions: So if I register the device and never again connect to Wireless that "refrigerator post-it" won't expire?
And, most importantly, if I register with B&N will they push the 1.2.2 update on my device, or can I prevent that without any ill effect? I'd really like to stick to 1.2.1.
EDIT: I read your previous OP about the 1.2.2 OTA update, and your link for how to block it here: https://forum.xda-developers.com/showpost.php?p=34433959&postcount=3
Renate NST also suggested deleting /system/app/DeviceManager.apk, but I don't know if this would be problematic with the B&N registration issue I'm trying to fix to begin with.
Is there a preferred way to do this and still keep the device registered and battery life unscathed?
I appreciate your help!

Winston S. said:
Thank you again, I suppose if that's the case then I will register my NST. A couple questions: So if I register the device and never again connect to Wireless that "refrigerator post-it" won't expire?
And, most importantly, if I register with B&N will they push the 1.2.2 update on my device, or can I prevent that without any ill effect? I'd really like to stick to 1.2.1.
EDIT: I read your previous OP about the 1.2.2 OTA update, and your link for how to block it here: https://forum.xda-developers.com/showpost.php?p=34433959&postcount=3
Renate NST also suggested deleting /system/app/DeviceManager.apk, but I don't know if this would be problematic with the B&N registration issue I'm trying to fix to begin with.
Is there a preferred way to do this and still keep the device registered and battery life unscathed?
I appreciate your help!
Click to expand...
Click to collapse
I think since you are just starting out working with the device and don't have work to lose by updating and re-rooting, registering and then updating (you can do it manually by downloading the file yourself) is your best bet. The device keeps a "last date contacted" and "next date to try contact" in settings.db. If there is no WiFi, it will just keep changing the dates. That's all.
OTOH, if you do not update but NEVER connect to WiFi, there will probably be no issue. The method to block updates "works", as I found, but it did not prevent the occasional reboot when I was connected to WiFi, so I finally just threw in the towel and updated my devices, starting over from scratch. I'm happy with the many changes I've made since, so it worked out for me. Not sure why you want to stay with 1.2.1. It is virtually identical to 1.2.2 and I don't believe there is anything on-site here that worked with 1.2.1 which doesn't also work with 1.2.2. All B&N did was patch contacts with their servers for TLS 1.2 compliance.
Deleting/disabling DeviceManager will give your NST Alzheimers as far as your registration is concerned and it will just begin wondering why it can't remember who it is and how/when to phone home--wherever that is. One of the problems with disabling B&N apps is that there are also jar files which don't get disabled and the system still tries to fool with those. You can delete/disable those as well but the more you niggle at the system architecture the more unstable the device becomes and the more things fail to work properly (like the Reader and Library).
Like I said before, it's better AND easier to just treat the device the way it was designed as far as updating or registering. You don't have to use a credit card, you don't even have to use a real e-mail address, I suppose. Then when all that is out of the way you can just install your own launcher and set the "n" button to Home. Voila! You'll never see or hear from the B&N stuff again and your battery will last a good long time.

nmyshkin said:
I think since you are just starting out working with the device and don't have work to lose by updating and re-rooting, registering and then updating (you can do it manually by downloading the file yourself) is your best bet. The device keeps a "last date contacted" and "next date to try contact" in settings.db. If there is no WiFi, it will just keep changing the dates. That's all.
OTOH, if you do not update but NEVER connect to WiFi, there will probably be no issue. The method to block updates "works", as I found, but it did not prevent the occasional reboot when I was connected to WiFi, so I finally just threw in the towel and updated my devices, starting over from scratch. I'm happy with the many changes I've made since, so it worked out for me. Not sure why you want to stay with 1.2.1. It is virtually identical to 1.2.2 and I don't believe there is anything on-site here that worked with 1.2.1 which doesn't also work with 1.2.2. All B&N did was patch contacts with their servers for TLS 1.2 compliance.
Deleting/disabling DeviceManager will give your NST Alzheimers as far as your registration is concerned and it will just begin wondering why it can't remember who it is and how/when to phone home--wherever that is. One of the problems with disabling B&N apps is that there are also jar files which don't get disabled and the system still tries to fool with those. You can delete/disable those as well but the more you niggle at the system architecture the more unstable the device becomes and the more things fail to work properly (like the Reader and Library).
Like I said before, it's better AND easier to just treat the device the way it was designed as far as updating or registering. You don't have to use a credit card, you don't even have to use a real e-mail address, I suppose. Then when all that is out of the way you can just install your own launcher and set the "n" button to Home. Voila! You'll never see or hear from the B&N stuff again and your battery will last a good long time.
Click to expand...
Click to collapse
The main reason I want to avoid 1.2.2 is because I tend to value stability overall, and since most of the stuff here was created by the era of 1.2.1 or before, I am leery of doing something that will make things less compatible. Plus I am distrustful of B&N changes on a device this old. I also thought I had read you explaining some changes that needed to be done after a 1.2.2 update to make something work (NM, maybe? I forget.)
So my question was more along the lines of whether, when I register the device, it will be flagged immediately for update and cause some trouble if I don't, or even if the update will be downloaded in the background without me being able to do anything about it. I suppose I could always patch the sqlite file to disable OTA updates and then register. That would be the safest way to go. And you need to use ADB for this to work, right? There is no way to edit the file onboard the NST itself?
I can't wait for the battery consumption to be normal, because I am really enjoying my NST with its great ergonomy and the ability to install different readers. Mine is going to be a dedicated offline ebook reader, but a great one. And much of the reason it is so amazing is thanks to folks like you and Renate who have contributed so much. :good:

Winston S. said:
The main reason I want to avoid 1.2.2 is because I tend to value stability overall, and since most of the stuff here was created by the era of 1.2.1 or before, I am leery of doing something that will make things less compatible. Plus I am distrustful of B&N changes on a device this old. I also thought I had read you explaining some changes that needed to be done after a 1.2.2 update to make something work (NM, maybe? I forget.)
So my question was more along the lines of whether, when I register the device, it will be flagged immediately for update and cause some trouble if I don't, or even if the update will be downloaded in the background without me being able to do anything about it. I suppose I could always patch the sqlite file to disable OTA updates and then register. That would be the safest way to go. And you need to use ADB for this to work, right? There is no way to edit the file onboard the NST itself?
Click to expand...
Click to collapse
There's really no reason to be concerned about the 1.2.2 update. It's all fine. B&N would not go to the trouble on an old device like this only to somehow wreck it. It's just a TLS security update and involves connection to their servers. Since you do not intend to use the device online, the only minor issue (resigning Opera Mobile browser-- which I've already provided elsewhere) is moot for you.
As for changing the OTA flag, you can do it via ADB if you install sqlite3. This is probably best since moving settings.db back onto the device after editing can be tricky. But you could eliminate the entire tango by just updating to 1.2.2 and going on with your life

nmyshkin said:
There's really no reason to be concerned about the 1.2.2 update. It's all fine. B&N would not go to the trouble on an old device like this only to somehow wreck it. It's just a TLS security update and involves connection to their servers. Since you do not intend to use the device online, the only minor issue (resigning Opera Mobile browser-- which I've already provided elsewhere) is moot for you.
As for changing the OTA flag, you can do it via ADB if you install sqlite3. This is probably best since moving settings.db back onto the device after editing can be tricky. But you could eliminate the entire tango by just updating to 1.2.2 and going on with your life
Click to expand...
Click to collapse
Thank you for clarifying that, I think I have had an overdose of information from reading too many threads in a short span of time and somehow I got the idea NookManager had some sort of issue after the 1.2.2 update that required some tinkering. The fact that the update is limited to the TLS update means it doesn't affect me, so things would be OK. On the other hand, not installing the update also seems like wouldn't be an issue and I really wanted to get ADB going anyway to install things wirelessly, so the most logical path seems to go through the minimal effort required to change that setting anyway. It turns out I already have sqlite3 installed (I am running an Ubuntu system,) so even more reason to do this!
I'll be reading up on the way to get ADB working.
BTW, I know you have proposed probably changing NookManager to address different issues you have encountered. Let me know if I can be of any help. I have no experience building Android components and limited experience compiling, but I would be happy to learn a new skill.
Thanks! :good:

@nmyshkin I easily managed to change the OTA setting through USB ADB. (I'm keeping track of all this process so when I have everything set up I will create a thread for posterity to help anyone else with the same questions.)
Now, the problem I wasn't anticipating is that I didn't foresee the battery problems, so I used that procedure to avoid the Register prompt on startup (Bypass OOBE procedure.) But of course now I don't know how to register the Nook. Do I need to reset to Factory using NookManager, root, disable OTA, and then register? It would be nice if there is a way to avoid this?
EDIT: Searching through another thread I saw your suggestions (almost 3 years old) to use the DeviceRegistrator, so after creating a B&N account I did and it said that the registration was successful, but in Settings the Account is showing up as unavailable, so I restarted the NST, and still I am getting Account Unavailable under Settings. Does the Device Registrator not work anymore? Or have B&N stop registering NST devices?
So I checked by logging into the B&N account and as expected there are no NSTs linked to my account. The DeviceRegistrator app has a few options (Register Device, Authenticate Device, Register User, and Authenticate User.) I didn't touch the User options so I guess that is to create a new account. I just used the "Register Device" option. Do I need to Authenticate Device too, or is this just not working anymore?
I read somewhere that there is also another app called OOBE Reg or something like that that basically runs the default registration procedure, but I haven't found that app in my NST.

I actually went down a similar rabbit hole myself at one point when I was investigating selective disabling of B&N apps, etc. Yes, you need to authenticate. That may or may not have the desired effect. Right now DeviceRegistrator is your only option. It may or may not be possible to authenticate a rooted device by this method.
Having said that, maybe it's time to take a step back and ask yourself whether all this angst is worth the end result when the path of least resistance will yield an equally functional result. The answer to that depends, in part, on how much other stuff you have already done. But before you do more things don't forget that the basic device needs to be in optimum working condition (like not eating battery) first.

nmyshkin said:
I actually went down a similar rabbit hole myself at one point when I was investigating selective disabling of B&N apps, etc. Yes, you need to authenticate. That may or may not have the desired effect. Right now DeviceRegistrator is your only option. It may or may not be possible to authenticate a rooted device by this method.
Having said that, maybe it's time to take a step back and ask yourself whether all this angst is worth the end result when the path of least resistance will yield an equally functional result. The answer to that depends, in part, on how much other stuff you have already done. But before you do more things don't forget that the basic device needs to be in optimum working condition (like not eating battery) first.
Click to expand...
Click to collapse
I will Authenticate using DeviceRegistrator and see if it works. The Catch 22 is that if I revert to Factory and then register the device I might have a problem with the 1.2.2 update I want to avoid (but yes, I realize at this point my aversion to 1.2.2 is basically irrational.) So I will try this approach first and report back. I will double check to see if the Nook Device shows up in my B&N account too, and I'll report again.
I agree 100% about putting the device in a sound baseline state before installing a lot into it. I'm documenting all that I do, and when I reach that state I'll create a thread about it. Hopefully it can be of use to someone down the road, because I do see new NST units being bought still every week in eBay.
I was relieved that ADB over USB was already enabled by installing NookManager and that I only needed to create a couple of files in my Ubuntu machine for it to work.

Winston S. said:
I was relieved that ADB over USB was already enabled by installing NookManager and that I only needed to create a couple of files in my Ubuntu machine for it to work.
Click to expand...
Click to collapse
That's actually news to me. I had thought the flag for WiFi ADB was set. I've never tried USB.

nmyshkin said:
That's actually news to me. I had thought the flag for WiFi ADB was set. I've never tried USB.
Click to expand...
Click to collapse
Yes, apparently ADB Konnect is set up so that if you start ADB Wireless it sets the flag, and then unsets it. I just tried ADB through Wireless and it also works.
To update on the DeviceRegistrator, I tried to Authenticate the Device and it didn't work (I got a banner saying that the operation is no longer supported.) So it looks like I will need to restore to Factory, register, and then root (which defeats the purpose of disabling OTA updates, as I can't do that until I root.)

@nmyshkin, is resetting the Nook to factory by using "Erase & Deregister Device" option in the stock Nook Settings the same as resetting to factory.zip from NookManager or holding the two Page Back hardware buttons on startup?
I reset mine using the "Erase & Deregister Device" menu option, and then registered and rooted it again, but still I am having problems with CoolReader (I am using the cr3_0_49_13.apk posted in the relevant thread.) Basically, there are no options to set the refresh interval where they should be, and the Options interface is black. Somebody mentioned this as well but they fixed it by restoring to factory, so I'm wondering what the deal is. Is this the only version of CoolReader people use with the NST?

Winston S. said:
@nmyshkin, is resetting the Nook to factory by using "Erase & Deregister Device" option in the stock Nook Settings the same as resetting to factory.zip from NookManager or holding the two Page Back hardware buttons on startup?
I reset mine using the "Erase & Deregister Device" menu option, and then registered and rooted it again, but still I am having problems with CoolReader (I am using the cr3_0_49_13.apk posted in the relevant thread.) Basically, there are no options to set the refresh interval where they should be, and the Options interface is black. Somebody mentioned this as well but they fixed it by restoring to factory, so I'm wondering what the deal is. Is this the only version of CoolReader people use with the NST?
Click to expand...
Click to collapse
No, erase and deregister does just that. It removes your account info and settings. The factory reset is an actual reimaging of the device from the protected onboard image. This can be done with the two button technique, NookManager or eight failed boot attempts.
I'm afraid I can't help much with CoolReader. I once had a version installed but found it had way too many settings for me. I ended up using only the screensaver/book cover option but that was pretty silly and I eventually got rid of and wrote my own app for that.
I located the version for the other fellow, but that's the extent of my knowledge. I'll try it in a bit and see what you're talking about.

nmyshkin said:
No, erase and deregister does just that. It removes your account info and settings. The factory reset is an actual reimaging of the device from the protected onboard image. This can be done with the two button technique, NookManager or eight failed boot attempts.
I'm afraid I can't help much with CoolReader. I once had a version installed but found it had way too many settings for me. I ended up using only the screensaver/book cover option but that was pretty silly and I eventually got rid of and wrote my own app for that.
I located the version for the other fellow, but that's the extent of my knowledge. I'll try it in a bit and see what you're talking about.
Click to expand...
Click to collapse
Please, don't waste any time with CoolReader. As usual, you saved the day. I'll reimage the device using the correct procedure, as I mistakenly believed this is what the Erase and Deregister option did. I think this will take care of the CoolReader weirdness, and if not I have found that NoRefresh works remarkably well with it anyway. Thank you!

Winston S. said:
Please, don't waste any time with CoolReader. As usual, you saved the day. I'll reimage the device using the correct procedure, as I mistakenly believed this is what the Erase and Deregister option did. I think this will take care of the CoolReader weirdness, and if not I have found that NoRefresh works remarkably well with it anyway. Thank you!
Click to expand...
Click to collapse
Mmm.....I see nothing in that version of CoolReader thats looks anything like it was adapted for the NST. I got that version from a e-book blog post link so shame on me for passing along bogus stuff. It's definitely NOT the version I once had installed (whatever that was...). The current market version is incompatible and the "new" CoolReader GL installs but does not run. I took a look at the CR home at SourceForge and there are many versions available there but it would be trial-and-error with them--and maybe there is no magic bullet. If you search for "CoolReader" on the forum you will find a variety of references. In some lists of "working" apps there are version numbers. Tracking down one of those might be a start.

nmyshkin said:
Mmm.....I see nothing in that version of CoolReader thats looks anything like it was adapted for the NST. I got that version from a e-book blog post link so shame on me for passing along bogus stuff. It's definitely NOT the version I once had installed (whatever that was...). The current market version is incompatible and the "new" CoolReader GL installs but does not run. I took a look at the CR home at SourceForge and there are many versions available there but it would be trial-and-error with them--and maybe there is no magic bullet. If you search for "CoolReader" on the forum you will find a variety of references. In some lists of "working" apps there are version numbers. Tracking down one of those might be a start.
Click to expand...
Click to collapse
Thank you for looking at this. I am a little confused, because you helped @ALinkToTao who was having problems with it, and he seems to imply that the version linked here which you referred him to ended up working for him..
So I'm just going to write that off to him being confused about the version he ended up installing. I will see if I find something that works, thanks again.

Winston S. said:
Thank you for looking at this. I am a little confused, because you helped @ALinkToTao who was having problems with it, and he seems to imply that the version linked here which you referred him to ended up working for him..
So I'm just going to write that off to him being confused about the version he ended up installing. I will see if I find something that works, thanks again.
Click to expand...
Click to collapse
Yeah, so I need to redeem myself there. In my lame defense, I was just going with what was posted here: https://blog.the-ebook-reader.com/2...artial-refresh-and-page-button-support-video/
Clearly that is bogus. So I checked out @wozhere's listed working version, or something close.
I think the place to start is with the 3.1.2 series from the SourceForge home of CoolReader. The attached version looks a lot more like what I remember and has screen refresh options (only visible as settings while viewing a book).
There were many more options on the version I once had, so this one is a starting point only.

Nook Simple Touch Network Problem - a success story that raises more questions

First of all, thanks to nmyshkin and all the other folks who have put in the time and effort both to develop tools and solutions for the NST and to document the process to share with others. I wanted to document my own recent experience in case it’s of any help to anyone with similar issues.
A little background: I've been using a NST since 2011, which my (US-based) parents bought for me at the time. I've usually kept wifi turned off, except to occasionally connect in order to sync the clock, and I've sideloaded books from my Mac using Adobe Digital Editions and Calibre.
I'd originally written here that I'd never rooted the device; however, years ago I did remove the two default User Guide books from the library. Unless there's a way to do this without root, or unless I just hid the books on a shelf and then forgot about them, then I must have rooted it at the time, at least temporarily.
In 2013, I cracked the device's screen, so I picked up a used on on eBay and swapped the guts from my old one to the chassis of the new one. At least I think that's what I did...it was some time ago, and I didn't document the process.
At any rate, on to the present.
In the evening on 2022-04-26, I took out my NST to read a book, and I was greeted by the “new device” sequence of prompts (as if my device had never been used and needed to be set up for the first time). I believe that the first page I was shown was language selection, but I never saw this page again in this entire process, so I cannot be sure. I stepped through the menus (accepting agreement, choosing time zone, connecting to wifi), but after connecting to wifi, I got a “Network Error” and could not proceed.
Taking to the internet, I found out that this error is usually related to B&N servers no longer being online, and that I should try to bypass the registration entirely. The directions given for this involved factory resetting to get to the Welcome page, holding the top right page turn button and swiping the top of the screen left to right, tapping the Factory button that appears, holding the top right page turn button and tapping the lower right corner of the screen, and finally tapping the "Skip Oobe" button that appears. I found these directions in the following sources, among many others:
https://www.reddit.com/r/nook/comments/ex61b3
I should note that at no point in this entire process was I ever able to get the hidden Factory button to pop up, despite finding these directions all over the internet. I attempted to factory reset several times (reboot and immediately press the two lower page turn buttons as soon as the screen flashes), attempted to factory re-image using NookManager (https://forum.xda-developers.com/t/nst-g-updating-nookmanager-for-fw-1-2-2.3873048/), and while these resets were successful, I never was able to access the hidden Factory menu at the welcome screen.
I also at this time downloaded and manually installed the Nook 1.2.2 update from B&N, in case I had not done so before (https://help.barnesandnoble.com/app/answers/detail/a_id/4212/~/having-trouble-connecting-to-your-nook?#ManualDL). To make the update happen automatically, I copied the file to the Nook’s internal storage from a computer, put the Nook to sleep, and waited a minute or two until the Nook found the file and started the update. B&N says that this update is necessary to allow connection to their servers, so it seemed like a logical thing to do; however, at this point, this update neither gave me access to the Factory menu nor allowed me to register my device on the B&N servers.
Doing some more reading, I found that UK devices were cut off from their servers a few years ago, and some industrious people came up with a ways to use these devices anyway, the most common being to replace the Nook’s firmware with the US firmware using the “Nook Region Changer” SD card, which is based on clockworkmod (CWM).
https://forum.xda-developers.com/t/nst-g-dealing-with-non-us-aka-uk-devices-in-2021.4233411/
https://web.archive.org/web/20210821235751/https://sites.google.com/site/xcdguides/nook/nookregion
https://forum.xda-developers.com/t/nst-g-update-fw-1-2-2-uk-unofficial.4360889/
I decided to give this a try, in case my device happened to be a UK or other international device (although I was fairly certain it was US based, because I am located in the US and the device listed time zones from the US…though I suppose it could have been Canada?). The directions I followed were a mix of the second and third links above:
I downloaded the nook_region_changer file (from the first of the three links above) and used Etcher to make a bootable microSD
I followed steps 3-10 in the third link from nmyshkin: power down, boot into CWM, backup, wipe dalvik cache, wipe data/factory reset
I then switched to steps 7-9 in the second link (archive.org): install rom_backup.zip, install nook_1_2_update_US_CWM.zip, reboot twice
Following these steps, I was now getting a slightly different welcome screen when I booted into the Nook firmware, which matches the one in the YouTube video cited earlier in this post, except without the Back button. Unfortunately, I did not take a picture of what my screen looked like before this flash (though I’ve done a little digging into this, which is toward the bottom of this post). Nonetheless, I was still unable to access the hidden Factory menu, and I was also unable to register the device with B&N.
I then decided to apply the B&N 1.2.2 update once again, copying the file to the Nook’s internal storage and putting the Nook to sleep so that it could update. Following this update, the Welcome screen remained the same, and the hidden Factory menu was once again inaccessible. However, this time, my device was able to connect to the B&N servers, and I was able to finish setup.
Things now seem to be in working order.
—————
Some thoughts from afterward:
I’m not sure why my device decided to re-initialize in the first place, as I’ve been using it for the past decade or so, I always keep my Nook’s wifi turned off, and I had sideloaded a book to the device just a few days earlier, opened the book at that time, and everything had been working normally.
I wonder if the Factory menu is only available on international Nook devices. I have no idea why I was never able to access this menu throughout the process, though I did find one other user who had the same problem a couple of years ago (this was the post that pointed me at the nmyshkin custom UK firmware post that became a part of my solution in the end): https://forum.xda-developers.com/t/nook-simple-touch-network-problem.4130461/
This user was also based in the US, so it’s possible that my hypothesis about the Factory menu being inaccessible from US firmware is correct; however, I would have to install some other firmware to check, and as my device is finally working, I don’t want to risk it.
I believe that what clued me in to needing to update to the latest B&N firmware (despite this not solving things once before) was this post by nmyshkin in another thread: https://forum.xda-developers.com/t/...mple-touch-update-1-2-2.3971367/post-80341393
On that note, I don’t know why my device was unable to register after the first time I applied the B&N firmware update.
It’s possible that my device wasn’t a US-firmware device. As I mentioned briefly at the beginning, my original Nook was a gift from my parents in 2011 (and thus was probably a US device), but its screen became damaged and I purchased a second one from eBay. I don’t recall what was wrong with the second one (maybe a bad battery, maybe something else?), but I do remember taking both devices apart and mixing the two of them as I put them back together, presumably to use the good screen from one and…something…from the other. So there’s a chance that the brains of this device are from the second Nook, though it seems unlikely, as my B&N account (through a computer web browser) showed the serial number of this device as having been registered in 2011, which is when I got the first Nook (which was presumably a US device). It also seems likely that I'd have wanted to keep the working internals from the old device and just use the screen from the new one.
A second thought on the unable-to-register-the-first-time-I-updated-my-Nook problem. As I mentioned above, I was getting a slightly different Welcome screen on my device prior to flashing a different firmware with Nook Region Changer. I did not take any pictures at the time, but I believe the old screen looked like this (https://u-mercari-images.mercdn.net/photos/m86876116644_1.jpg?1598739388), and the new one looked like this (https://shopgoodwillimages.azureedge.net/production/48/8-9-2021/35449379212449Nele.JPG). These images are attached to this post, with “Welcome to your all-new NOOK” for the old Welcome screen and “Welcome to your NOOK Simple Touch” for the new. What is also interesting to me is that the other person I found online who was unable to access the hidden Factory menu on the welcome screen (see link above) mentioned the old text, “Welcome to your all-new NOOK,” in their description as well.
Perhaps this is a much older firmware? I wasn’t able to check, because I couldn’t get into a working Nook to look at its version. I remember seeing the announcement a few years back that 1.2.2 would be necessary and that I would need to update if I wanted the device to continue working. I’m not sure whether or not I ever did that, but it seems likely considering I remember the post. One theory is that perhaps if a NST is running a very old firmware, it is unable to directly update to 1.2.2 and requires intermediate updates, which could be why flashing the firmware using Nook Region Changer allowed the later update to 1.2.2 to happen successfully. This would also explain why, after the first time I installed the 1.2.2 update in this most recent series of events (prior to the Nook Region Changer flash), I was still unable to register (and I still had the old Welcome screen).

the.sting said:
I wonder if the Factory menu is only available on international Nook devices.
Click to expand...
Click to collapse
No, it should be available from all devices in general working order. Clearly something else was going on with yours.
the.sting said:
This user was also based in the US, so it’s possible that my hypothesis about the Factory menu being inaccessible from US firmware is correct; however, I would have to install some other firmware to check, and as my device is finally working, I don’t want to risk it.
Click to expand...
Click to collapse
It ain't broke (now). So leave it be. But...I would definitely use NookManager to make a backup. You don't have to root in order to do that (I think).
the.sting said:
It’s possible that my device wasn’t a US-firmware device. As I mentioned briefly at the beginning, my original Nook was a gift from my parents in 2011 (and thus was probably a US device).
Click to expand...
Click to collapse
The differences are subtle, but since you've flashed the UK version now, the point is moot. The opening screen on the US version is the Welcome screen. The opening screen on the UK version is the Language picker, followed by the Welcome screen. Alas, I didn't pay that much attention to any differences in the Welcome screens between the two versions so your attached images don't ring any bells.
In the UK version the dictionary is the Oxford English and the Settings app is a little more expansive, including a dictionary management section (which does not work). Also, the locale or language picker is not fixed on "US English".
the.sting said:
One theory is that perhaps if a NST is running a very old firmware, it is unable to directly update to 1.2.2 and requires intermediate updates, which could be why flashing the firmware using Nook Region Changer allowed the later update to 1.2.2 to happen successfully. This would also explain why, after the first time I installed the 1.2.2 update in this most recent series of events (prior to the Nook Region Changer flash), I was still unable to register (and I still had the old Welcome screen).
Click to expand...
Click to collapse
I have never heard anything like this, but as they say, anything is possible (though I doubt this one).
Wow. You've been on quite a ride! I'm glad if anything I put together was helpful. Again, I strongly suggest a backup. It's possible there is a hardware fault in the device that caused it to run a factory re-image. If that happens again, a backup to restore would be handy.

Thanks, nmyshkin! Your posts were incredibly helpful in navigating my way through this.
It sounds like I must have had a US version previously. I have a fuzzy memory that I may have had the language picker the first time I found my Nook in the initialization sequence, but at that point I was just trying to get through it to use the device again, so I wasn't paying that much attention. But every subsequent time that I factory reset it, it went straight to the welcome screen.
I'm actually currently running the US firmware; I flashed the US image that comes with the Nook Region Changer package rather than the custom UK one that you put together. The custom UK one was the next thing I was going to try, but the device allowed me to register after the flash and subsequent update, so I never got there.
I did run a backup using the clockworkmod tools in Nook Region Changer prior to making that flash, which resulted in several files being generated on the SD card (see attached image -- the times are wrong, but the files with "Today" timestamps are presumably the ones generated by the backup). I'll make sure to perform another backup now that things are working. Would you suggest I use NookManager rather than clockworkmod?
I still have no idea why I was never able to get the Factory button to appear, but it sounds like the "Skip Oobe" workaround has its downsides anyway, so I'll stick with what's working now.
Thanks again!

the.sting said:
I did run a backup using the clockworkmod tools in Nook Region Changer prior to making that flash, which resulted in several files being generated on the SD card (see attached image -- the times are wrong, but the files with "Today" timestamps are presumably the ones generated by the backup). I'll make sure to perform another backup now that things are working. Would you suggest I use NookManager rather than clockworkmod?
Click to expand...
Click to collapse
It has been said, but I cannot verify, that the CWM backups are not "complete". They are certainly better than nothing. The NookManager backup is a single file "image". That's the not-too-impressive extent of my knowledge on that score. I have used CWM backups to restore other devices before, so I might just be all wet on this topic.
the.sting said:
I still have no idea why I was never able to get the Factory button to appear, but it sounds like the "Skip Oobe" workaround has its downsides anyway, so I'll stick with what's working now.
Click to expand...
Click to collapse
I actually had a thought about that after my post. I've never used the hardware buttons for page turns. Never saw the sense. I have them assigned to various other functions but don't use them often. So I could be caught off-guard if, for example, one of them just decided not to work any more.....like the upper right one? Just a thought, but it's probably too easy!

Good to know, I'll look into making a NookManager backup.
nmyshkin said:
I actually had a thought about that after my post. I've never used the hardware buttons for page turns. Never saw the sense. I have them assigned to various other functions but don't use them often. So I could be caught off-guard if, for example, one of them just decided not to work any more.....like the upper right one? Just a thought, but it's probably too easy!
Click to expand...
Click to collapse
I hadn't considered this, as I also barely use the hardware buttons on the sides. But you seem to be spot on...I just checked, and the top right button is the only one of the four that isn't working for page turns either! Sometimes the simplest explanations turn out to be right.
Thanks again!

You can use UsbMode.apk (in the sig) to check the action of physical buttons (or USB or Bluetooth).
I don't use WiFi, I use a little utility to sync the time whenever I sync content over USB.
Such a utility is dependant on the exact syntax of the date command and the ability to directly get a # prompt without using "su".

nmyshkin said:
It has been said, but I cannot verify, that the CWM backups are not "complete". They are certainly better than nothing. The NookManager backup is a single file "image". That's the not-too-impressive extent of my knowledge on that score. I have used CWM backups to restore other devices before, so I might just be all wet on this topic.
Click to expand...
Click to collapse
In light of the fact that my top right page turn button doesn't work, do you have any thoughts on the NookManager backup process? Unfortunately, "Format remaining space on SD card" (which seems to be a precursor to making a backup) is selected by that top right button.

the.sting said:
In light of the fact that my top right page turn button doesn't work, do you have any thoughts on the NookManager backup process? Unfortunately, "Format remaining space on SD card" (which seems to be a precursor to making a backup) is selected by that top right button.
Click to expand...
Click to collapse
I should have seen that coming
I've been here before with another member, different button, same general issue. That time it was NookManager-1, nmyshkin-0.
The device has 6 hardware buttons. Whether it will recognize input from the remaining two with the instruction set that is loaded at boot remains to be seen. I've got a busy day, but it's the kind of busy that will allow my mind to wander. I'll see what turns up. Try not to have a device meltdown today.

the.sting said:
In light of the fact that my top right page turn button doesn't work, do you have any thoughts on the NookManager backup process? Unfortunately, "Format remaining space on SD card" (which seems to be a precursor to making a backup) is selected by that top right button.
Click to expand...
Click to collapse
OK, this time around the little grey cells have triumphed!
Do you know about ADB? If not, this will not do you much good, although it's fairly easy to install a minimal ADB package on a Windows machine (if you have one).
Anyway.....
It's possible to synthesize a button press using ADB, and NookManager gives you the option to start up ADB before you do much of anything else. Except there is a catch. The button that starts WiFi so you can connect with ADB is---you guessed it---also your dead button.
Not to worry. The left buttons are unused on that menu screen and I can easily alter that menu for you. All you would need to do is replace the file on the card with the altered one.
Then once WiFi is started, you have the option to start ADB (a left button) and are given the IP address to connect to.
The ADB command for sending a press of your non-working button is:
Code:
adb shell sendevent /dev/input/event0 1 407 1
(those are zeroes--both of them)
This would enable you to access the entire NookManager menu system (if the need ever arose), including the backup and restore functions. You just need to send that code each time you should press that dead button.
But you'd need ADB to do it.
Let me know if you want to pursue it. If this seems like too much for too little, keep your CWM backup safe somewhere. As I said before, I've used them to restore other devices.

Wow, thank you so much for putting the thought into this! I haven't worked with ADB, though it's something I would definitely be interested in investigating (I like to tinker). That said, I'm stretched a little thin to really dive in at the moment...getting married soon and otherwise a bit swamped with work.
I'll definitely save the CWM backup for now. Can I ping you here again if I'm interested in working on this later?
Thanks again!

the.sting said:
I'll definitely save the CWM backup for now. Can I ping you here again if I'm interested in working on this later?
Thanks again!
Click to expand...
Click to collapse
Absolutely. Congratulations on your approaching wedding!