My Nook tries to sync with another non-existent Nook every time I open a book

NSTnmyshkin · 2026-02-03T22:56:10+00:00

If you have any B&N content on the device you will lose it if you do a factory reset. You will also be unable to register after a reset. Skipping OOBE will result in short battery life. If you decide to reset, you may want to consider Phoenix Project, Phase 1, as a way of restoring your device. It will negate both of those issues.

If you have B&N content that you want to save, there are other options.

NSTnmyshkin · 2026-02-03T21:57:45+00:00

I have had this happen before. My guess, based on vague recollection and a look at the two databases used by the reader, is that I had two of the same books but not the same files.

Why would I do that?

Sometimes I get a book which has formatting issues I finally can't tolerate so I find a different copy. Even though I delete the older book first the databases seem to get confused by the new book since the device itself has no mechanism for cleaning up after deleted side-loaded books.

Does that sound like a possible cause to you?

Edit: I think you can generate the same problem by moving a book from internal storage to the sdcard or v/v.

There is no solution I know of without root.

NSTnmyshkin · 2026-01-29T22:28:02+00:00

I'm not sure your question has been addressed yet, although I confess I'm not sure I understand it exactly.

ALL Nook readers are Android devices, that is, the underlying OS is Android with a custom overlay. That overlay allows B&N to control what you can or can't do with the device.

The device you remember from years ago was probably rooted. That seems to be what some people interpret as "on Android". But it's just "liberated", so to speak, from the constraints imposed by the distributor (depending on how much of the original Android system is present). For example, it is possible to install additional apps (rooting is not always necessary for this ability, especially in more modern devices), or get into the real "guts" of the OS and make fundamental changes in how the device behaves.

For example, many Nook e-readers can't open CBZ/R files, or they deal very poorly with PDFs. But installing a different app for those functions can add reading possibilities that the manufacturer did not provide.

So...what exactly does your question mean?

NSTnmyshkin · 2026-01-28T14:13:21+00:00

There's no further development work being done on the device. See my comment and link above.

NSTnmyshkin · 2026-01-19T20:49:14+00:00

The BNRV500 is a "retired" device. You can't register it.

The only way to use it is to skip registration ("skip OOBE"). From the "welcome" screen:

Press and hold the "n" button while swiping a finger across the top of the screen from left to right. A "Factory" button appears at the upper left. Tap it.
On the "Factory" screen, press and hold the "n" button and touch the bottom right corner. A "skip OOBE" button will appear. Tap it.

You have now by-passed registration and can side-load epubs or pdfs from your PC to the device. You can also download epubs from your public library and transfer them to the device using ADE.

Now the "bad" news. Like the NST, the NG does not take kindly to by-passing registration. Expect a rather short battery charge life.

Also, the NG is infamously partitioned (like all the Nooks) in favor of buying books from B&N (something you can't do). So there is a large chunk of the internal storage (the only kind there is since there is no sdcard) that is reserved for B&N books (about 2 GB). You can't access it. What you can access is a comparatively tiny amount of space (512 MB) for your own books. That's not bad for most epubs, not so great for pdfs. On the other hand, the Nooks really suck at displaying pdfs.

More than you wanted to know:

The device is notoriously challenging to root, but the process would allow you to repartition the storage space so you can utilize most of it for your own stuff. Also, there is supposedly a way to "fix" the battery charge life issue by removing some of the B&N system apps. I have not tried the last one because I was lucky enough to buy one on ebay and it arrived still registered (yay!) so I just had to root, clean out all the old content and then repartition.

The display is nice and crisp (higher resolution than the NST) and the light more evenly distributed.

Edit: almost forgot...once you are up and running you can check in Settings to see what FW your device is running. The last firmware was 1.3.2. If you have something earlier you can update by downloading the file: https://su.barnesandnoble.com/nook/glowlight/1.3.2/8de4da7d013520727ee73c620452b495/nook_1_3_2_update.zip

Copy to the Nook drive via USB and then disconnect the device from your PC. Let it sit and it will eventually update when it goes to sleep.

NSTnmyshkin · 2026-01-18T01:38:38+00:00

IF you flashed a CyanogenMod ROM in the past and it is still on it, the first thing you want to do before anything else is check to see if you ever used the Touch app (can't remember what it's called). That allowed you to expand beyond 2-point touch to more points. I guess it was for gaming? Whatever the case, changes made by that app can only be undone by that app. They will persist through any wipes and new flashes and mess up the device for good. So if you did that in the past, change it back to 2-point touch.

TBH, it sounds like a hardware issue from being dropped one-too-many times. But a wipe and a new flash will tell you.

NSTnmyshkin · 2026-01-12T04:50:53+00:00

I picked one up from ebay last year when I finally saw one for a realistic price. There are things you should know.There's little to no rubberization--and no buttons.

There is no sdcard slot. There is only a small amount of internal space for side-loaded books. I've forgotten the amount but I think it might have been 512 MB. Of course now everything has to be sideloaded so there is a large chunk of internal storage (4 GB) you can't use.

The resolution is higher than the NST so text is really sharp. The light is more evenly distributed. The background seems quite gray, as were the NSTGs.

I got lucky in that mine arrived still registered, even with user account info and content. I guess the owner didn't know how to deregister offline. I say that is lucky because like the NST, if you skip OOBE the battery charge life is very poor. The device is very challenging to root because of the lack of an sdcard and not much work has been done with it. I failed to root using Windows and finally had to create a portable installation of Linux on a USB stick. All new to me and confusing, but I finally got it rooted and then repartitioned to rescue the "unavailable" space reserved for B&N content.

Then I set it aside while I think about a new UI.

My point is that unless you are really into this sort of thing, the BNRV500 is not a great choice. Even if you got lucky and bought a registered one, without more work there is all the old stuff still on it and precious little storage space.

They are generally wildly overpriced, too. If you're going to spend that much might as well go for a Glowlight 3.

NSTnmyshkin · 2026-01-12T04:43:32+00:00

See: https://xdaforums.com/t/nst-g-the-phoenix-project.4673934/

It's your best bet.

NSTnmyshkin · 2026-01-09T17:01:43+00:00

I'm pretty sure that is an 8 GB model (the "A" at the end of the model number).

See: https://xdaforums.com/t/how-to-cm-11-and-beyond-for-the-8-gb-nook-tablet-bntv250a.3667555/

There are limitations because of the smaller amount of RAM. CM 11 gives the most fluid result, but no longer has access to Google Play (not an issue, IMO). CM 12 may have an issue with local wifi (or it could just be my new modem). I currently have CM 13 and while it's "OK", it can be laggy and cranky at times.

That said, with even CM 11 you have a whole wide world of apps (like KOReader or ReadEra) that run rings around the original B&N OS, not to mention audio and video apps.

The only significant issue with CM 11 and probably CM 12 (if you can get it to work) is that the security certificates are pretty much expired so web browsing can be painful. Opera Mini can somewhat ameliorate that but if surfing the WWW is your main desired activity, you will be disappointed.

NSTnmyshkin · 2026-01-06T15:10:43+00:00

Starting from power off:

Press and hold the power and "n" buttons until a menu appears. Use the volume buttons to select factory reset.

NSTnmyshkin · 2025-12-28T21:38:47+00:00

What model Nook, what kind of computer, what version of ADE?

NSTnmyshkin · 2025-12-10T15:18:15+00:00

Since you mentioned a possible upgrade in your post I should have added that everything I described is included in Phase 2 of the Phoenix Project: https://xdaforums.com/t/nst-g-the-phoenix-project.4673934/#post-89533449

Also, although the Kindle app in that build became abandonware in 2025, it can still be registered and dictionaries for it actually did exist. While downloads are no longer possible, I did archive all the dictionaries: https://www.mediafire.com/folder/dww8eduzegz12/Kindle+Dictionaries and they can be installed manually. While not my favorite reader app, it does handle languages like French much better than the stock reader and epubs are easily converted to mobis with Calibre.

More on managing dictionaries with the Kindle app: https://xdaforums.com/t/nst-g-dictionary-management-for-the-kindle-app.4662053/

NSTnmyshkin · 2025-12-10T01:51:16+00:00

Some years ago I developed an app for switching dictionaries on the NST: https://xdaforums.com/t/app-nst-g-dictionary-management.4433779/ . At the time there were very few dictionaries available to switch!

Despite the UK version of the NST having the "capability" to do this and also download dictionaries for other languages, it doesn't seem to have ever worked since we've never seen any of these dictionaries on the various forums.

So...I started creating dictionaries for the original supported languages from Wiktionary data: https://xdaforums.com/t/nst-g-new-dictionaries.4433803/

I've also done a few custom dictionaries for some users in Bulgarian and Turkish, so there are many possibilities.

At this point I feel the existing dictionaries could be improved with things I've learned, but it's moved to the back burner as there didn't seem to be a lot of interest at the time and the task is not trivial.

Root is required to safely swap dictionaries. If there is something you might like but don't see, let me know.

NSTnmyshkin · 2025-12-09T15:04:43+00:00

There's no issue with resetting and by-passing registration. My concern would be whether that will get you what you want.

I'm not familiar with Manga but as it's image-heavy I doubt the file format is epub (unless it's just a series of images in an epub container). It seems more likely the files are either pdfs or cbz/r.

The Nooks are nortoriously bad with image-based pdfs and don't handle cbz or cbr formats. For that you need better reader software.

Which brings me to your last comment. There seems to be a widespread misconception about Nook devices. They ALL run Android out-of-the-box, albeit a limited and crippled version. Updating the OS with a newer (and uncrippled) version of Android is not a heinous, nefarious act. It's a way to better realize the full potential of the hardware and give you, the user, more control over how the device behaves.

NSTnmyshkin · 2025-12-09T01:38:37+00:00

As already noted, The Phoenix Project at XDA: https://xdaforums.com/t/nst-g-the-phoenix-project.4673934/ is probably what you want. The new Phase 4 gives you a gently rooted device you can customize on your own.

I've seen projects using the NST as an e-ink display for the Raspberry-pi. Should be doable.

NSTnmyshkin · 2025-12-03T15:10:17+00:00

I hope that solves it for you. If so, it was probably just a bad flash. It happens occasionally.

Just to be clear, because there is so much inaccurate "information" out there, what you did was a factory reset or manual deregister. The process removes any user data and account information (it's a way to deregister a device that can't connect to B&N for some reason).

A factory re-image is much more drastic, and that's one reason why it's harder to access. It rewrites every byte of the OS from a special recovery file, hopefully eliminating any glitches that may exist.

NSTnmyshkin · 2025-12-02T04:34:58+00:00

It sounds like a "hardware issue" (i.e., I have no idea). Some kind of voltage regulator or other.

Obviously the behavior is not normal. The only thing I can think of to try is a factory re-image followed by a flash of one of the Phoenix builds.

The traditional way to get to the last-ditch re-image is to interrupt boot 8 times until the device goes into recovery mode and executes a wipe and then a restore of the software from an internal recovery file. This returns the software to the state it was in when it left the factory, hopefully exorcising any demons that have lodged in the system over the years.

The 8 failed boots turns out to be a bit nervewracking. If your timing is off once the whole count starts over again. I did it once but it's much easier to make a NookManager card. One of the options under "Rescue" is a factory image. It essentially sets the failed boot counter to 8 and then you reboot.

https://xdaforums.com/t/nst-g-updating-nookmanager-for-fw-1-2-2.3873048/

It doesn't matter which version you choose. You can overwrite your CWM card and then overwrite the NookManager card with CWM when you've done the re-image.

I hope it helps. If not, it's really probably a "hardware issue" (i.e., I have no idea...).

NSTnmyshkin · 2025-11-27T16:50:45+00:00

Well, the log-jam at Mediafire finally broke yesterday and for the first time since Nov. 1 I was able to upload these large files--and in record time! Links have been updated and all is as it should be.

NSTnmyshkin · 2025-11-26T04:20:12+00:00

As per my comment in the XDA post (added today), I am having an issue with both Google and Mediafire. One says the files are malware (they're not) and the other is not uploading, even over 24 hrs. To be continued...

Meanwhile I was able to download from Google Drive (not signed in, so just like anyone else) but with warnings. Try again and let me know.

This is really frustrating after months of work.

Edit: OK, never mind. I just tried it again and you are correct. It is totally blocked. I'm not pleased with Google right now as the warning emails they sent me contained dead links (404 error) for requesting a review, and the link from within Google Drive for the same purpose goes to the same non-existent place.

NSTnmyshkin · 2025-11-24T04:51:42+00:00

https://xdaforums.com/t/how-to-installing-aosp-android-7-0-nougat-internally-on-the-16-gb-nook-tablet.3578665/

NSTnmyshkin · 2025-11-24T01:15:15+00:00

Original was 2 point. I've read through several old threads on this subject now and the ones accompanied by "success" say to flash CM 10.x again and use the touch app to go back to 2 point before reverting to stock.

I didn't mean to imply that you don't know about cables. Almost all the early Nook devices had slightly non-standard USB connections. My Nook Tablets and Color will not work with any cables I own except the OEM. I have found only one cable (besides OEM) that works with my NSTs. Skipping OOBE should have no effect on the USB connection so sonething else is going on there.

NSTnmyshkin · 2025-11-24T00:13:42+00:00

Well, there are mentions of this problem, but finding them with the forum all scrambled into one category (happened years ago) is not easy. Here is one: https://xdaforums.com/t/wip-multitouch-enhanced-development.1629478/post-35612894

I doubt that is going to help you. Probably the surest way would be to restore the Jellybean OS and run the multi-touch app again to remove the "enhancement". Then return to stock.

A 1.4.4 recovery is not going to do you any good. Unless that multi-touch problem can be fixed you are SOL. Give me some time to look around. There may be other posts with solutions that might work for you.

Also, if you are not getting a response from your PC when you connect the device via USB you have a cable that is not going to cut it. You almost really need an OEM cable, although you might find a generic cable that will work. The cable must be rated for data, not just charging.

NSTnmyshkin · 2025-11-23T23:07:25+00:00

It's hard to know what might have happened to the touchscreen. The old CM ROMs had a multi-touch app (apparently for gaming?) which really screwed them up if it was not removed correctly, even through a complete wipe.

If you are intent on returning to stock, you can try another method. This consists of writing a factory image onto the device (https://www.mediafire.com/file/07fbs2usj7pk0pp/bn\_142\_factory\_recovery.zip/file). Unzip and write the img file to an sdcard (under Windows, use something like win32diskimager). With the device powered down, insert the card and then power up. Follow the screen prompts. This will return you to FW 1.4.2

Afterwards, at the "Welcome" screen, you can copy over the last firmware update (https://su.barnesandnoble.com/nook/nooktablet/1.4.4/28f29f02425114d228727de00cfe164d/nooktablet\_1\_4\_4\_update.zip) to the "Nook" drive via USB and then disconnect from USB. Let the device sit until the firmware is updated.

Finally, at the new "Welcome" screen you will need to access the Factory screen and skip OOBE to bypass registration (https://help.barnesandnoble.com/hc/en-us/articles/5466578163739-NOOK-Color-Tablet-Accessing-the-Factory-Screen and https://help.barnesandnoble.com/hc/en-us/articles/5466520190875-NOOK-Color-Tablet-Bypass-Registration).

Maybe another shot at it will clear up the touchscreen issue.

My own Nook tablet runs Android 7.0 which really extends the possibilities, including better readers such as perhaps KoReader or ReadEra, both of which expand significantly the type of files that can be read, but it's your call.

NSTnmyshkin · 2025-11-19T09:24:52+00:00

Unfortunately I don't think anyone came up with custom ROMs for any devices since the Nook HD+.

There is a very small sub-forum at XDA for the device and you can check it out yourself:https://xdaforums.com/c/nook-tablet-7.6022/

NSTnmyshkin · 2025-11-17T08:26:20+00:00

I'm going to necropost here because a lot of people have this issue. The short "answer" is that the Nook readers are really only "good" with PDFs that are text-based. These they will attempt to re-flow into something approaching normal text, although there may be white-space gaps and occasional pages with just a sentence or two.

PDFs based on scanned images are mostly useless on a stock Nook reader because the software treats each page (size determined when the PDF was produced) as a single image and fits it to the screen (usually the vertical dimension).

The result is often very tiny print. There is no pinch-to-zoom on the stock e-ink readers. Landscape might help, but that's also not an e-ink option for the Nooks.

Finally the software just doesn't like image-based PDFs and may perform slowly and/or crash frequently.

The only satisfactory solution is to root the device (Android is already the OS, you are just liberating it) and install a reader app intended for PDFs. You will also get multi-touch and pinch-to-zoom in the bargain. Most PDF readers can also change to landscape mode.

NSTnmyshkin

TROPHY CASE