Related
Too much tweaking, I think and probably deleting the wrong thing, but my rooted ST now has an identity crisis. In the Settings section under "About Your NOOK" it says "unavailable" for Owner, Account, and Software version (it's 1,21).
On the B&N home screen it just looks and looks for updated info (even when Wi-Fi is on) and the Shop screen is the same.
I've restored all the B&N apks to the system/app directory (from the 1.21 zip), rebooted, etc. This did help with some functionality, like the limited book info on double-tap which was not working before. But clearly my registration info is gone or garbled.
Is there a way to invoke OOBE without deregistering the device and starting all over? Is there some little file to delete that will make it think it's in OOBE state when rebooted (as if I haven't already deleted enough...)? I've tried DeviceRegistrator but it fails (can't get past the empty line for Pref URL Options).
Any ideas short of deregistering (if that will even work now)?
I'm using the stock nook reader and renate's Library.apk. How can you make sure the last read icon on the top bar corresponds to the last read file in the library?
I am not sure where this icon gets its link. It doesn't seem to always open the last read file.
I've been thinking about asking this question (although I am using the stock reader AND library apps). My "reading now" button is getting really cranky of late. It often just goes to the first page (cover) or sometimes it goes to the first page AND displays a two-option message about the different current reading positions in two Nook readers (!) and which one do I want (generally neither is correct). Right now the only sure way to get to the correct page is to go to the Library screen and select the book from there. So the Nook does remember, but the Reading Now button is not functioning properly.
For a time I had a number of B&N apps disabled (renamed ".bak") and gradually discovered the imponderable connections that seemed to render little things inoperable. I've had to restore quite a few of the apps to running to keep everything functioning except Nook Community (because the constant "nagifications" drove me crazy) but this button behavior has me baffled (as does the reference to two Nook readers!)
I wonder, are you using any sort of "cleaning" app? I am using Clean Master and find it helpful in freeing up memory but I'm beginning to think that some of the data it is throwing out might just contain the info that the button needs to function properly. It certainly messes with Tasker.
The "Last Read" icon on the status bar sends out the intent com.bn.nook.launch.LAST_BOOK
This would normally be handled by Home.apk
If you deleted Home.apk and are using my Library.apk it has its own receiver for that.
Depending on which version Nook software you have it will query
content://com.bn.nook.reader.providers.lastreadingpointprovider/
content://com.bn.nook.reader.common.providers.lastreadingpointprovider/
The LRP database is maintained by the Reader(RMSDK).apk.
Checking for the latest modification gives you the last book read.
My Library.apk sends an intent out to open that book.
Currently Library.apk does not update the order of books displayed in "Last read" unless the refresh button is hit.
Two things to look for if you are having problems:
If you let the battery die and the WiFi is always off the clock time will be wrong.
If you crash or shutdown improperly Reader(RMSDK).apk will not get a chance to update the LRP.
P.S. I just noticed a possible anomaly if you read PDF's in the reader too.
Oh! It just occurred to me one thing.
I remember opening a book that you have been reading already and it opens at page 1.
This was tied to opening the book in different ways.
There are different ways to open a book:
Through the "Last Read" icon and stock Home.apk
Through the stock Library.apk
Through my Library.apk
Through a file manager application
The LRP database is /data/data/com.bn.nook.reader.activities/databases/lastreadingpoint.db
Code:
CREATE TABLE lastreadingpoint
(_id integer primary key autoincrement,
ean text, // file URI
luid text,
offsetrmsdk text, // subfile path fragment
lastupdated long, // Unix milliseconds last read
bookdna int, // always 1?
sync_status int // always 1?
);
ean (which normally might stand for European Article Number, i.e. "UPC") is a URI, not a path.
Code:
sqlite> select ean from lastreadingpoint;
file:///sdcard/Books/aboveall.epub
...
There may be cases where a single book gets different ean's.
If you could look at LRP and see if this is so?
I actually managed to locate that db file on my own (!) and what seemed to be a companion with related information (readerlocal.db). They seemed to be full of junk info (books that had since been removed, etc.) although there were no duplicate entries, which is what I had suspected.
Anyway, I got a little "brave" (i.e., foolhardy) and decided to clean up both files in a parallel way. Then I pushed them back, reset the permissions and rebooted.
Yikes. My Nook is set to go to the B&N Home screen only on reboot. That screen flickered and flashed, never filling in any of the images. I could still use the "N" button to access other parts of the system and they were working fine, but any return to the Home screen via the Back button showed it was still in distress.
So....restore from backup...again.
It seems OK for now. I have noticed that the little "refresh" button in the Library does sometimes seem to go on and on and on without any accomplishment. I have suspected the issue was how I accessed the book-in-progress as you described. Since I sometimes read more than one book at a time, I'm all over the place with how I do things (including a Library icon in my App home screen). I'm going to try being more disciplined for a while and see how it behaves.
nmyshkin said:
I actually managed to locate that db file on my own (!) and what seemed to be a companion with related information (readerlocal.db). They seemed to be full of junk info (books that had since been removed, etc.) although there were no duplicate entries, which is what I had suspected.
Anyway, I got a little "brave" (i.e., foolhardy) and decided to clean up both files in a parallel way. Then I pushed them back, reset the permissions and rebooted.
Yikes. My Nook is set to go to the B&N Home screen only on reboot. That screen flickered and flashed, never filling in any of the images. I could still use the "N" button to access other parts of the system and they were working fine, but any return to the Home screen via the Back button showed it was still in distress.
So....restore from backup...again.
It seems OK for now. I have noticed that the little "refresh" button in the Library does sometimes seem to go on and on and on without any accomplishment. I have suspected the issue was how I accessed the book-in-progress as you described. Since I sometimes read more than one book at a time, I'm all over the place with how I do things (including a Library icon in my App home screen). I'm going to try being more disciplined for a while and see how it behaves.
Click to expand...
Click to collapse
Would it be possible to write an app that simulates opening the last read book from only one of the Library apps and then map that to the last read icon to simplify this whole system?
mergen3107 said:
Guys, if you are concerned about why sometimes the last read option goes to the 1st page, then it was already fixed by our forum users somewhere here. (I could hardly remember and trace where it all started but finally it was successfully solved)
Just install a file this package (internal.db deep in the 'data' folder. You could delete 'system' folder - this is hyphenations dictionary for Russian) through cwm or replace it manually (the zip contains detailed path) and here you go.
Click to expand...
Click to collapse
Now that was an interesting trip! Once I had Google do some translating there were a number of really interesting posts that were (mostly) intelligible. I'd want to compare that modified internal.db file with what's already on my Nook before I did any replacing. A lot of the work from that site is "russified" (not surprisingly) and there may be other changes there not really needed/wanted, but it's a good start.
I noticed in another posting there that someone said there is a related issue with in what state the Nook is connected via USB. Apparently the hypothesis is that if you don't connect while in the Library you stand a good chance of scrambling the "reading now" database entry. I've certainly been hooking up with my Nook in all kinds of states, so if that's correct, no wonder my database file was so messed up!
Installation of the internal.db file from the Russian source will not work. I've tried a side-by-side comparison of the file with the one from my Nook (FW 1.21) and there are differences (beyond the region identifier, which is easily changed). It's not at all clear what changes have been made or from what firmware the modified file came. In any case, it causes havoc when exchanged for the native internal.db
The Russian discussion points to this thread on XDA which approaches (and apparently solves) the problem another way. I'm going to give it a try.
nmyshkin said:
Installation of the internal.db file from the Russian source will not work. I've tried a side-by-side comparison of the file with the one from my Nook (FW 1.21) and there are differences (beyond the region identifier, which is easily changed). It's not at all clear what changes have been made or from what firmware the modified file came. In any case, it causes havoc when exchanged for the native internal.db
The Russian discussion points to this thread on XDA which approaches (and apparently solves) the problem another way. I'm going to give it a try.
Click to expand...
Click to collapse
Do I read this correctly, http://bit.ly/Q7MytN from that thread there should be no problem if renates Library.apk is used exclusively and the stock Library.apk has the bug?
I've just received Nook simple touch. It was bought from USA and sent to Bangladesh. After unpacking, I powered on the device and followed the steps. At one stage it connects with the wifi network successfully. Then, It shows error message -"Sorry we're having trouble setting up your Nook...."
I communicated with Nook support and share the serial number. Their feedback was "my Nook is disabled, that's why it is not registering..." usually the device is disabled for lost, stolen etc cases. But I told that the device was purchased from bestbuy.com and it reached to me with intact packet. Also I have invoice of it. But they told me to talk to Bestbuy.com.
Later, I called to Nook's hotline asked that where the issue is related to the location from where I'm trying to use it. Feedback was - Nook is useable only from USA and UK having a valid credit card. It cannot be used from Bangladesh.
Now, what should I do to make it workable from Bangladesh?
Maybe this from the Mobileread.com Nook forums:
As long as the epub files you wish to load on the machine are without DRM, like those in Mobileread's own library, the answer is yes. In fact, that is how I've been using the Nook ST for the last week. I'm setting this reader up for my mom who doesn't have wifi or internet access. Since I'm going to sideloading everything anyway, it seemed stupid to bother with registering the nook.
Here's how after you initially charge the nook and activate the unit:
How to Skip OoBE Experience
1. Enter the Factory Screen by holding the TOP RIGHT Button and slide your
finger across the top of the Nook from left to right. A button labeled
"Factory" will appear in the top left of the screen.
2. Once in the Factory screen, hold down the TOP RIGHT Button and tap in the bottom right of the screen.
3. A new button will appear labeled "Skip Oobe". Tap that and you're done!
While you are at it, you might consider installing the latest software update, which you can manually d/l on your computer and install on the nook via USB.
http://www.barnesandnoble.com/u/Soft...uch/379003175/
------------------------------------------------------------------------------------------
But....be aware that a few subsequent posts in the same thread suggested that battery drain was unusually high when using the Nook unregistered. Maybe there are other solutions out there.But it's a start.
You can gut all the B&N stuff if you like.
You will not be able to read B&N DRMed purchased content.
You will still be able to use it for Adobe Digital Editions from OverDrive (which have other DRM).
That's how you read library books (at least here).
When unregistered B&N can use a lot of current.
Turning WiFi on but never actually using it since it was started uses a lot of current.
Turning WiFi on, using it for something, leaving it on is not nearly as bad.
Sounds confusing? It is.
I'm intrigued by this problem and have done some reading online about various peoples experiences. Many had the device registered in the US before taking possession in their respective countries. Some use non-US credit cards without any problem. It seems that there are differences which may be related to firmware versions and perhaps even to changing B&N policies (many of the posts I read are 2-4 years old).
There's a lively Russian Nook users group over on the-ebook.org. Reading through a rough Google translation (always fun) it seems that the standard approach there is to select a US time zone (change it after registration) and skip the credit card part. It might be easier to set up a B&N account on the B&N website first (although that does require a credit card--surely they accept valid international CCs?). In any case, there don't seem to be any additional issues mentioned by the Russians with regard to registration. Curious.
The OP does not state if the intent is to purchase ebooks from B&N or just to have a functioning eink reader for side-loaded material. I guess it is possible to root without registering if you never want to interact with the B&N store, then remove the B&N stuff that is causing the battery drain (or however much of the B&N stuff you want to remove).
It would help to have more info about the intended use for the Nook in question. Meanwhile, shame on BestBuy....
[addendum: Aha! Try this thread]
Thanks a lot nmyshkin
Now I able to use Nook by using you bypass method. Also the battery drain seems faster (40% in 3days).
Another problem is wifi connectivity. I want to use wifi to browse internet (using the hidden trick). How can I do it?
sameee781 said:
Now I able to use Nook by using you bypass method. Also the battery drain seems faster (40% in 3days).
Click to expand...
Click to collapse
Yes, as warned. This is the reason to pursue other options because the battery ought to last for a few weeks, not a day or two.
Another problem is wifi connectivity. I want to use wifi to browse internet (using the hidden trick). How can I do it?
Click to expand...
Click to collapse
Unless you have a very early firmware release (unlikely at this date of purchase), you probably can't use that old trick. It was "fixed" in the second or third firmware update so that the default Android browser became unreachable without rooting.
If you want internet access (and/or email, etc.) your best bet is to root the device. To my mind the easiest way to accomplish this is with NookManager. If you want Google apps (and access to the Play Store for more apps) then you can do that after rooting here, or follow the link to it in the NookManager post.
However, unless you want to selectively delete some B&N stuff after rooting, it would be better if you could get the device registered before you root. Now that you know at least one work-around to get the Nook sort of running, maybe try a factory reset and then approach the registration as the Russians have and see if it works for you.
nmyshkin said:
However, unless you want to selectively delete some B&N stuff after rooting, it would be better if you could get the device registered before you root. Now that you know at least one work-around to get the Nook sort of running, maybe try a factory reset and then approach the registration as the Russians have and see if it works for you.
Click to expand...
Click to collapse
Could you please suggest the Russian method by which I'll be able to register?
sameee781 said:
Could you please suggest the Russian method by which I'll be able to register?
Click to expand...
Click to collapse
Look up back at post #4. But you will have to do a hard reset first so that the Nook goes back into registration mode.
Hi nmyshkin
As mentioned in post#4, I didn't find Nook registration trick in the-ebook.org
If you have a launcher installed you can simply select "OOBE" (Out Of Box Experience).
If you don't have a launcher installed, ADB:
Code:
adb shell am start -n com.nook.oobe/.o.ORoot
(That's dot, small O, dot, capital O)
If you are not rooted you'll have to follow the other instructions above.
sameee781 said:
Hi nmyshkin
As mentioned in post#4, I didn't find Nook registration trick in the-ebook.org
Click to expand...
Click to collapse
According to the Ruskies, you should select a US time zone during registration and skip the credit card (I didn't enter a credit card when I did my registration and everything went just fine--it says you can skip). I don't recall the entire registration process any more, but if you need to enter an address, use a fictional US address, something like "125 First Street, Montebello, CA 90640" (the little town where I grew up...). Ditto for a phone number if needed (818-792-6942) For an email address, something without a country identifier would be best, like a Gmail account you can tie to the Nook.
After registration is successful you can change the time zone in the Settings panel.
As an afterthought, a credit card on file is needed if you plan to have any dealing with B&N. For example, I was curious to see if I could get one of the "Friday Free" ebooks from B&N, even with my rooted and much amended Nook. Although the ebook was free I could not access it without a credit card on file. Once I gave them the card info I had no trouble selecting the ebook and it appeared (by magic!) on my rooted Nook within a few minutes. So whatever I've done so far has not broken that process. Now whether I'm going to be interested in reading that book, I have no idea, but I had to try the process
@nmyshkin & Renate
Current status -
I've rooted my nook using NookManager and installed NTGAppsAttack. I've installed Facebook app but cannot use it properly as it shows internet connection issue. But I can bowse internet using operamini. I've tired to use facebook using operamini. But I could not able to write dot in email address field and unable to login. These are the minor problem because my primary objective is to read books.
The main problem is battery drain. So, I want to register the device to solve battery drain issue. If I follow your instruction, will the battery drain issue be resolved? Or I should unroot it and try to register?
sameee781 said:
@nmyshkin & Renate
Current status -
I've rooted my nook using NookManager and installed NTGAppsAttack. I've installed Facebook app but cannot use it properly as it shows internet connection issue. But I can bowse internet using operamini. I've tired to use facebook using operamini. But I could not able to write dot in email address field and unable to login. These are the minor problem because my primary objective is to read books.
The main problem is battery drain. So, I want to register the device to solve battery drain issue. If I follow your instruction, will the battery drain issue be resolved? Or I should unroot it and try to register?
Click to expand...
Click to collapse
I'm not entirely clear on the order of operations with regard to registration vs. rooting. Registration WILL solve the battery drain problem, so however that can be achieved, that's the way to go, I think. If you can, with your rooted Nook, start the registration process, then try that. If there's no way to invoke registration without resetting to factory, then do that and root again after you have registered successfully.
I don't know anything about Facebook but it may be a challenge with an older browser. BTW, there is general agreement that Opera Mobile works better on the Nook than Opera Mini. You can get that from the Amazon App Market or sideload it directly from the Opera archive here. But first, you need to clear the registration/battery drain hurdle.
Registration is not appearing if I restart the device. As I've skipping oobe it is not going to registration page. If I use DeviceRegistator it gives error.
sameee781 said:
Registration is not appearing if I restart the device. As I've skipping oobe it is not going to registration page. If I use DeviceRegistator it gives error.
Click to expand...
Click to collapse
Yes, once when my too-much altered Nook lost its identity I tried to use DeviceRegistrator and it failed for me too.
NookManager is your friend. Put the SD card back in your Nook and boot it up. Choose the "Restore Factory Image" (or whatever its called).
Then try to register as described earlier with your unrooted Nook. If that works, put the SD card back in again and root. Then proceed from there as you like.
nmyshkin said:
Yes, once when my too-much altered Nook lost its identity I tried to use DeviceRegistrator and it failed for me too.
NookManager is your friend. Put the SD card back in your Nook and boot it up. Choose the "Restore Factory Image" (or whatever its called).
Then try to register as described earlier with your unrooted Nook. If that works, put the SD card back in again and root. Then proceed from there as you like.
Click to expand...
Click to collapse
Should I not face the similar problem like first time? Here is the screenshots taken at the time of getting started with my Nook. The problem was also mentioned in the first post.
sameee781 said:
Should I not face the similar problem like first time? Here is the screenshots taken at the time of getting started with my Nook. The problem was also mentioned in the first post.
Click to expand...
Click to collapse
I have no idea, but I would sure get closer to the router/modem on your Wi-Fi network so that you have a better than "fair" connection.
The one thing which has worried me about the registration process as described by the Russians is that surely the B&N server can tell if the registration info is coming from a server outside the US (or UK). Even faking the time zone doesn't seem likely since the information won't match the server clock that is sending it. But that's what they say worked.
Anyway, what do you have to lose? The Nook is fairly useless as a reading device if you have to charge it every day--or more often. You need to try registering it again. If it doesn't work, then you try something else.
nmyshkin said:
Anyway, what do you have to lose? The Nook is fairly useless as a reading device if you have to charge it every day--or more often. You need to try registering it again. If it doesn't work, then you try something else.
Click to expand...
Click to collapse
Yes, anyhow I've to solve battery drain issue otherwise the device will become useless. That's why I'll also be there in this forum for your help.
-I tired to register near from my wifi router. Also tried by making my phone (Galaxy S4) as portable wifi hotsport. Both are Failed. I'll try again and again....
-In my device there are only few timezone options available, all are US time zone. There should not be issue selecting any one of them.
I'm thinking about their authentication policy. May be their server is checking the originator IP address first which is a non US IP for my case. Hence, it is giving error.
sameee781 said:
I'm thinking about their authentication policy. May be their server is checking the originator IP address first which is a non US IP for my case. Hence, it is giving error.
Click to expand...
Click to collapse
Yes, I thought about that too, although enough people from outside the US claim to have been able to register without any problem (few details, of course....). I suppose you could try a free proxy server (Google), but most of the free ones seem to be transparent enough that they are detected as not being truly from the country of "origin". Still, if all else fails, it's another possibility.
I've found some open proxy proxy server IP
http://www.xroxy.com/proxy-country-US.htm
How can I configure this proxy so that the device IP seem to be a US IP? I've a wimax wifi router and android phone having wifi hotspot feature.
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.
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!