Database Users

Nook simple touch 1.2.1

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.

Just got an old Nook Simple Touch. Market not working. What can I do with it besides?

Ok, so I got an old Nook Simple Touch. In part because they can be had for such a cheap price on eBay these days and in part because they're among the few eInk based devices that run on Android and can actually be unlocked and more done with them than the manufacturers intended (I've used an old Kindle and man I hate how locked down and generally useless they are.) Actually, I was hoping I could do some neat stuff like setup daydream with weather info and a clock and all on it while the screen was "off" but I guess I forgot that this is a relatively new thing and it looks like it's based on a really really old Android version? Either way, I'm so used to CyanogenMod and its relatively near to AOSP nature that this thing is feeling horribly limiting and unpleasant to use for me.
Anyway, I've been searching around for various guides and such. I've found tools for rooting and putting the Google Market (yeesh, I forgot they used to call it "Market" ages ago.) It seems I needed to update the system to 1.1 for this (I had bootloops until I did, so clearly you have to have the right system version.) It seems there is a newer version or two beyond this though, but I didn't see root tools (I'm still hoping I can do more with this that might require root access to actually do.) Should I be updating beyond that? Namely, are there tools to actually root and all if I do?
Also, in the meantime, I'm running into troubles with the plain and simple fact that neither Google Market nor Amazon's app store installed by these tools work which may not be fixable. The thread on here says to add an account through Youtube first, then go to gmail and manually refresh over and over until it eventually crashes. After probably 15 minutes of this my hands were too tired to continue though. I just don't think it's supposed to take 15 minutes though. When I start the market it doesn't crash like that guide mentions either. Is there any other way to fix this? Is there any point? Obviously the market app is quite old, so perhaps it's simply never going to work? Is there some alternative way to find stuff that actually works on the NST? I thought to do F-Droid, but even it requires a newer SDK version apparently (I'm getting kind of curious what version of Android its base corresponds to. Does it predate 2.2? If so I may be in trouble since I don't think any of the stuff I was hoping I could put on there will go lower than 2.2.)
For this matter, is there a better way I can do stuff like loading apps? I was hoping to at least have a file manager to be able to use do stuff, but they didn't include one. I'll probably have to track down an apk. For now I'm having to actually use the network adb (I installed the version of the tools that was supposed to do adb over USB, but it doesn't even show up as an adb device at all for me to even so much as install a driver, so I guess it's not doing adb over USB as it should. The network method seems to work, though I'm not a big fan of leaving it wide open like that on principle really, yet remembering to manually change it on and off is a pain too.)
I realize this is a really old device and probably it is very limited what I can really do with it, but I was hoping I could at least squeeze a bit of use out of it. In particular, I'm going to need a much better reading app even if I use it for its intended purpose only. When I looked it up I had thought it was a close enough to stock Android that I'd be able to load up most apps I guess and I didn't think it would be so hard to even get anything on it.

Whew!
OK, let's start with basics. You didn't say how you rooted it but if you're working from 1.1 you probably are not getting the best out of the device. 1.21 is the final stock version. If you can get your NST back to stock, I would recommend doing so. Considering what you seem to have done already probably the easiest way to go is to use the NookManager route. Go here. Follow the instructions. There is info there for adding a Gapps package after rooting. But first get yourself back to 1.21 stock. Once that's done you can either use the Search Market tool from the Gapps package, or find apps on your computer and have them show up on the NST via the PlayStore, or side-load apps from the SD card or via ADB (default on that is WiFi with NookManager--you can install the ADB Konnect app and it works fine). There are plenty of alternate readers that run on the NST. I happen to like the stock reader very much, but to each his/her own.
When all that's done, everything depends on what your expectations are and what you want from your NST. There are a variety of kernals out there as well as USB host/audio mods. Although the Android system is old and the display limits what you can do, there are many apps that run well on the device and I personally get a lot of use out of mine, even more now that I have audio. Check out what I've done (second post) and look at what others have done (in the same thread).
There's a lot of good info in this forum on modifications, apps that run well (and don't) and many tips and tricks.

I think I have most of what I need with that actually, yes. I didn't realize from the guides I initially found that you could root or install third party components with a > 1.1 system version. With that stuff I do have a semi-working Google Market now and can actually install a lot more stuff than I thought. I see also my favorite reader app not only works, but apparently knows I'm running it on a device with an eInk screen and defaults to having eInk adaptations turned on.
Is there any way it can do anything like what I had sort of envisioned before btw? Eg on the screen "off" mode have some sort of thing that shows weather or news or something that updates every so often? (Nevermind the clock thing, that's probably a bad idea. I was just wondering about dedicating it to being sort of something like a clock with it plugged in all the time. Now I think maybe I can stop using my tablet for reading and use this instead.)

Nazo said:
Is there any way it can do anything like what I had sort of envisioned before btw? Eg on the screen "off" mode have some sort of thing that shows weather or news or something that updates every so often? (Nevermind the clock thing, that's probably a bad idea. I was just wondering about dedicating it to being sort of something like a clock with it plugged in all the time. Now I think maybe I can stop using my tablet for reading and use this instead.)
Click to expand...
Click to collapse
Sounds like you are having CM lockscreen widget withdrawal
Actually that seems like a job for Tasker. But it would be potentially messy. You'd need to:
1. Clear image in custom screensaver folder
2. Turn on wi-fi
3. Open weather/whatever app to update info
4. Take screenshot and save to custom screensaver folder
5. Close app
6. Turn off wi-fi
At that point when the Nook goes to sleep the info will be displayed on the lock screen. The question is whether Tasker can wake up the Nook and repeat this at desired intervals when you're not using it.
Also, have a look here for something along the same lines. Maybe you'll get an idea.

Ironically on my phone and tablet I keep it really simple. It's just that the eInk screen of the Nook can essentially be "always on" so to speak without draining the battery like mad (since it would only actually need to wake up every half hour or so for a frequent update schedule.)
But, all that said, it just doesn't sound like this is really worth all the effort. I guess I'm actually more used to newer versions of Android mostly rather than CyanogenMod specifically as they just have more power in what these things can do. With the Nook -- even unlocked and opened up -- it really sounds like the amount of time and effort required to even remotely approach such a thing is orders of magnitude higher. Well, that's fine. I had initially thought that I might maybe just use it as some sort of really neat "smart clock" type thing (at $35-ish on eBay you won't find many clocks that could come close to doing what an Android device could theoretically do) but in the end I don't think this is really all that realistic and definitely not worth the effort. On the other hand, now that I'm able to get more stuff actually running on it and open up its capabilities more I'm thinking I could maybe use this thing for something more akin to its original intended purpose: reading. From time to time I want my tablet to be able to do a bit more and I think this can do pretty well everything I care about beyond the basic reading stuff, so maybe I can stop carrying my tablet around all the time. (And for stuff like music I have a dedicated multimedia phone courtesy of eBay that's much better off really.)

Rooting and Fixing Samsung Galaxy Tab E (SM-T560NU) (and fixing -504 issue)

Disclaimer: I know this should go in the correct subforum for my device, but I'm having trouble navigating this site, altogether. I only see subforums for a handful of devices. So if there is a better place for this thread, I apologize
Oh, where to begin. My wonderful girlfriend got me this tablet back in october, since i said it'd be nice to have a linux based tablet so i wouldn't have apple telling me what i can and cannot do with my device (she saw that as a hint, even though it was more social commentary, but I'll take it). Anyway, I found the 16GB limitation problematic, so I decided to root it so i could use some sort of sshfs app to create a slow multi-terabyte harddrive space to steam small files (like music) from. Seeing as i had the thing for only a week and it's kind of expensive, even for a nurse, to buy for me, i chickened out and made due with a small 8GB microSD card which i just happened to have laying around.
Fast forward to a few days ago, I ordered from Amazon a 128GB microSD card (also from samsung), and decided to try to make due with that. Only to find out (and, if you're able to help me you've probably met the following issues yourselves) that the seemingly largest apps refuse to let you move them to external storage. Even better, there's some apps like Star Wars KOTOR (2.5GB) that say they let you move them, but in reality they stay on internal storage and create empty folders on the external medium. And then many apps cannot write and read to and from SD cards (like DOSbox Turbo), for reasons that completely stump me (which leads to me having to move dos games back and forth when i want to play one that saves). I then read about this wonderful feature called "Adoptable Storage," and promptly go through all sorts of things to try to enable it, only to find out that, since I have Android Version 6.0.1 from Samsung, that feature was disabled by them. After using the email support to berate them (they don't have a suggestion box), decided to try to come here and figure out how to properly root this device and figure out how to solve my space issue (I have 128GB of space that I need to use, but have no idea how to use it for what i need to use it for). By the way, a small shoutout to Samsung support, despite my very terse response, there clearly was a human being at the other end and this human was very, very civil and said that they'll pass it on as feedback (I got the impression that the employee either had the same issue or at least wanted me to know that there have been alot of complaints about this issue).
Anyway, now that that wall of text is over, this is how far i've gotten.
I know that XDA is reliable, they've had problems in the past with malware, but it was unintentional and the ship has been cleaned. I don't know about anywhere else, so the rooting instructions i find elsewhere i assume are probably correct, but i don't know where to get files for the process that i can trust, outside of XDA (and i'm having trouble finding the files i need, here).
I have a nice little article from techbeasts.com ( techbeasts.com/install-twrp-and-root-samsung-galaxy-tab-e/ ), but I don't know where their downloads came from and how many people checked them out for windows and android trojans and such.
So...
1. Is that article accurate for android 6.0.1?
2. Are those files safe (free from corruption and viruses)?
3. If they're not safe, where can I get safe files?
4. I like to develop programs, and I want to be able to develop apps for android as well. Once rooted, how does one test how their app would work on an unrooted device to ensure the app follows the "proper procedures?"
5. How do I deal with apps that are root sensitive? The point of all this is so that I can keep using my apps, so if they all break because i'm rooted that defeats the purpose.
6. Other than having to be careful with what i do (I've used Linux for years, and I occasionally like to code in assembly), that it voids my warranty, and that screwing up can make for a really bad day, is there anything else that I should know? This is, indeed, my first touch screen device outside of Nintendo products, because my V3xi is fine for me as a phone.
EDIT:
7. Forgot the most important question: How would I go about getting adoptable storage working on this device once it is rooted?
Forward: Given the nature of my question, the URL is absolutely necessary. After I've gotten my "10 useful posts" I'll fix the URL for future viewers.
EDIT2: Decided to take a chance. Ran into some issues finding the "stock firmware" which I ended up having to do. For those that have problem getting TWRP to stick, you gotta flash the stock firmware of the version you have currently installed. I tried to flash the original that it came with, which, for some reason, it didn't like at all.
Oh, and don't turn off OEM mode after everything's done. I assumed that after everything was installed it wouldn't second guess it and i could safely turn it off for added security if any app went rogue or something. Nope, must keep it on, so do regular backups. Turn off auto-updating, etc. I hear there's some sort of app that lets you "update safely." Not sure what it is, but unless you *NEED* it, don't do it.
And as a bonus note (so it shows up in the archives), some apps didn't install right (either google or the app developer's fault, but these apps weren't tied to this process [pokemon go and just about all the final fantasy games]). The kicker about this is is that you will not notice this UNTIL you uninstall the app, and reinstall it. Deleting the data before uninstalling the app will make it unstable. To find the data, i used
Code:
du / | grep "pokemon" > pokesearch.log
, since i knew that there should not have been a pokemon related directory on my droid at the time, since i needed to reinstall pokemon go because it was acting really fruity. Deleting the folders (actually, the last entry contains the rest, so it's easier just to delete the last one) allowed me to avoid the -504 issue (not to be confused with 504).
Code:
[email protected]:/data/data/com.termux/files/home # cat pokesearch.log
4 /mnt/expand/07aa2c40-4a8f-428c-afb9-7495df69eb26/user/0/com.nianticlabs.pokemongo/cache
1192 /mnt/expand/07aa2c40-4a8f-428c-afb9-7495df69eb26/user/0/com.nianticlabs.pokemongo/code_cache
12 /mnt/expand/07aa2c40-4a8f-428c-afb9-7495df69eb26/user/0/com.nianticlabs.pokemongo/shared_prefs
4 /mnt/expand/07aa2c40-4a8f-428c-afb9-7495df69eb26/user/0/com.nianticlabs.pokemongo/files
1220 /mnt/expand/07aa2c40-4a8f-428c-afb9-7495df69eb26/user/0/com.nianticlabs.pokemongo

Message me if have the same tablet on a system root
Sent from my SM-S907VL using Tapatalk

denakor said:
Message me if have the same tablet on a system root
Sent from my SM-S907VL using Tapatalk
Click to expand...
Click to collapse
We can talk here for the benefit of the community. Any problems you might have should be documented for the sake of the community. But, yes, the -504 error i mentioned above can only be solved through root, so, yes, i was successful.

Kohlrak said:
We can talk here for the benefit of the community. Any problems you might have should be documented for the sake of the community. But, yes, the -504 error i mentioned above can only be solved through root, so, yes, i was successful.
Click to expand...
Click to collapse
I have the same tablet
---------- Post added at 09:32 PM ---------- Previous post was at 09:28 PM ----------
keith thibodeau said:
I have the same tablet
Click to expand...
Click to collapse
Tablet just updated itself after I tried to root it .. MM 7.0.1 but I didnt ask it to

I disabled automatic updates (from settings and google play, 'cause it's in both places) to prevent this problem. There might be a new firmware for the tablet, but i'm sticking to this version. I'm not sure you can downgrade after you upgrade, though. You can take a shot, though, if you're not afraid of loosing data. I doubt this process will brick as long as you can get the official firm ware on backup incase something goes wrong.

Kohlrak said:
We can talk here for the benefit of the community. Any problems you might have should be documented for the sake of the community. But, yes, the -504 error i mentioned above can only be solved through root, so, yes, i was successful.
Click to expand...
Click to collapse
Now it seems impossible to root without pc

I had a few questions about modifying my old NST I recently dusted off

I've gotten back into reading lately, and I've been doing most of it on an iPad. I remembered yesterday that I had a NST lying around and went and dusted it off, charged it up, and moved some books over with Calibre. To nobody's surprise, I absolutely adore reading on it compared literally any LCD. I actually stumbled into finding out that there was an active modding scene around it just today and I've been going up and down some of these threads but I have a few questions.
First and foremost, my biggest reason for coming here was to get a modified firmware that allowed for faster refreshes/page turning. I've seen two major threads on this, but both are decently old and I've only ever seen newer questions/responses deal with installing an APK launcher on top of existing firmware. So my questions are:
1. Does the 1.2.2 firmware stop those old methods from rooting/working?
2. If not, why are they not the recommended methods anymore? Too complicated and greater risk to the device?
3. If not (1.), which of these two ROMs is recommended, and are there updated installation guides?
https://forum.xda-developers.com/showthread.php?t=2651053
https://forum.xda-developers.com/nook-touch/development/1337-rom-t2931567
Second, if neither of the custom ROMs are a good choice, I've seen both Relaunch and RelaunchX brought up as custom launchers, with multiple ways of installing them (Directly through ADB vs NookManager) and was looking for some opinions on that as well. Sorry in advance if I didn't search well enough, but any help is appreciated.

Daktyl198 said:
First and foremost, my biggest reason for coming here was to get a modified firmware that allowed for faster refreshes/page turning. I've seen two major threads on this, but both are decently old and I've only ever seen newer questions/responses deal with installing an APK launcher on top of existing firmware. So my questions are:
1. Does the 1.2.2 firmware stop those old methods from rooting/working?
2. If not, why are they not the recommended methods anymore? Too complicated and greater risk to the device?
3. If not (1.), which of these two ROMs is recommended, and are there updated installation guides?
https://forum.xda-developers.com/showthread.php?t=2651053
https://forum.xda-developers.com/nook-touch/development/1337-rom-t2931567
Second, if neither of the custom ROMs are a good choice, I've seen both Relaunch and RelaunchX brought up as custom launchers, with multiple ways of installing them (Directly through ADB vs NookManager) and was looking for some opinions on that as well. Sorry in advance if I didn't search well enough, but any help is appreciated.
Click to expand...
Click to collapse
1. Which old methods? The 1.2.2 FW update is mainly a TLS 1.2 compliance for connection to B&N servers. There are other minor "under-the-hood" changes, but nothing for the user. That said, the only rooting method that has been specifically updated for the 1.2.2 update is NookManager. Other methods may work. Or not. It would be trial-and-error, i.e., always start with a backup.
2. NookManager is, by far, the simplest and least intrusive layperson's method to root. With some customization you can tailor the initial result. Again, other methods may work.
3. There are no updates for the two ROMs you list. Both are based on the 1.2.1 firmware. This is where things get complicated. Since the TLS update of the 1.2.2 FW is only for the B&N server contact, you don't "lose" anything by staying with 1.2.1 FW. However, if your device is still in contact with B&N, it will attempt to update OTA at random intervals and fail, resulting in a spontaneous reboot. One or both of those ROMs may be structured so that there is no more contact with B&N servers--or all B&N stuff could be wiped out. You'd have to look into the dirty details (if any are given). My experience with attempting this kind of thing has not been good, but maybe that's because I always want to retain the B&N Library and Reader/Dictionary. I like them and they meet my needs. But keeping just a part of the B&N system is nearly impossible--at least it has proven so for me.
So.....I just leave all the B&N stuff alone and install my own stuff for everything but the Library and Reader. It works just fine and doesn't complain about not being able to contact B&N, etc. YMMV and your desires and needs may be quite different.
As for page refresh, there are a couple of approaches. Cool Reader has a version which includes e-ink page refresh settings. Also, some time in the distant past there was a post about changing the number of pages before a complete screen refresh (in the B&N reader). I was actually going to look that up this morning when I saw your post, so if I find it, I'll add that info later.
Edit: here's the info about changing the page refresh interval for the B&N reader: https://forum.xda-developers.com/showthread.php?t=1699481

For 3, there are useful things in those ROMs, but they may not be ideal for everyone if just installed as is.
For example, both run a handful of scripts at startup that may not be ideal for how some people want to use the Nook. The changes to the RAM management in particular were way too aggressive in my opinion.
But I did end up using one of those ROMs on one of my Nooks, just with most of the startup scripts disabled. On my other Nook running the stock firmware, I borrowed various bits and pieces from the custom ROMs. It just took some time to figure out what worked for me.
Sent from my KFKAWI using Tapatalk

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!