[HOW-TO] CM 11 and beyond for the 8 GB Nook Tablet, BNTV250a

Search This thread
D

Deleted member 4861160

Guest
Neat writeup, friend! I am glad to see people are still playing around with these old tablets. I have a Nook Color and I can definitely confirm the fact that gapps basically kills it, but all roms made for it run decently without them. Sideloading is a hassle, but if you specifically want app compatibility that's the way to go.

Good luck as you continue to use the Nook Tablet!
 

Zayadlui

New member
Jan 7, 2015
4
1
Помогите решить проблему
Установлено (cm_acclaim-UNOFFICIAL-cm11-2015-11-19.zip)
Очень рад, но нажал обновить систему, обновление тачскрина выдало ошибку. После этого тачскрин вообще не реагирует. Вернул на заводскую, загрузился с SD карты (cm-10.1-20130202-acclaim-HD-SDC) тоже не работает.
Помощь
 

nmyshkin

Recognized Contributor
Nov 21, 2013
1,556
455
Help solve the problem
Installed (cm_acclaim-UNOFFICIAL-cm11-2015-11-19.zip)
I'm very glad, but I clicked to update the system, updating the touchscreen gave an error. After that, the touchscreen does not react at all. I returned it to the factory, booted from the SD card (cm-10.1-20130202-acclaim-HD-SDC) also does not work.
Help
I want to understand "update the system, updating the touchscreen"

Does this mean you tried the Touchscreen Firmware Flasher? If so, that app causes problems and is not easy to undo, but there is information in this forum somewhere about it.

Please confirm that this is your problem.

Via Google Translate:

Хочу понять "обновить систему, обновить тачскрин"

Означает ли это, что вы пробовали прошивальщик прошивки сенсорного экрана? Если это так, то это приложение вызывает проблемы, и его нелегко отменить, но где-то на этом форуме есть информация об этом.

Подтвердите, что это ваша проблема.
 
  • Like
Reactions: ipdev

Zayadlui

New member
Jan 7, 2015
4
1
I want to understand "update the system, updating the touchscreen"

Does this mean you tried the Touchscreen Firmware Flasher? If so, that app causes problems and is not easy to undo, but there is information in this forum somewhere about it.

Please confirm that this is your problem.

Via Google Translate:

Хочу понять "обновить систему, обновить тачскрин"

Означает ли это, что вы пробовали прошивальщик прошивки сенсорного экрана? Если это так, то это приложение вызывает проблемы, и его нелегко отменить, но где-то на этом форуме есть информация об этом.

Подтвердите, что это ваша проблема.
I installed the firmware, opened the applications, updated, wrote the touchscreen update (super su) rights, rebooted the tablet and that's it. I have not separately flashed only your firmware
-Рус
Ничего не устанавливал только прошивку и габсы. После установки всё работало, зашел в программы стало интересно что за обновление системы, нажал написало обновление системы тачскрин, нужны права суперпользователя, началось обновление и ошибка, перезагрузить, после перезагрузки тач перестал работать. Откатил через CW бекап, тоже самое, прошил 13, тоже самое прошил 10, тоже самое.... Откатил через Суд карту до заводских, тоже самое.
 
Last edited:

nmyshkin

Recognized Contributor
Nov 21, 2013
1,556
455
I installed the firmware, opened the applications, updated, wrote the touchscreen update (super su) rights, rebooted the tablet and that's it. I have not separately flashed only your firmware
-Рус
Ничего не устанавливал только прошивку и габсы. После установки всё работало, зашел в программы стало интересно что за обновление системы, нажал написало обновление системы тачскрин, нужны права суперпользователя, началось обновление и ошибка, перезагрузить, после перезагрузки тач перестал работать. Откатил через CW бекап, тоже самое, прошил 13, тоже самое прошил 10, тоже самое.... Откатил через Суд карту до заводских, тоже самое.
My understanding is that problems with the touchscreen update flashing app can only be undone with the same app. So if you can open the app again and return to 2-touch, that should solve the problem. If you have no touchscreen response at all, I'm not even sure that returning to stock (meaning a true factory re-image, not just flashing a backup) will solve the problem.

So if you had any screen response with the CM11, reflash that and try to open the touchscreen firmware updater to return to 2-touch. Whenever I flash any CM ROMs the first thing I do after boot is disable that app so I won't accidentally touch it. It's not a good thing.

Via Google Translate:

Насколько я понимаю, проблемы с приложением для обновления сенсорного экрана можно устранить только с помощью того же приложения. Так что, если вы можете снова открыть приложение и вернуться к 2-касанию, это должно решить проблему. Если у вас вообще нет сенсорного экрана, я даже не уверен, что возврат к исходному состоянию (имеется в виду настоящий заводской повторный образ, а не просто перепрошивка резервной копии) решит проблему.

Поэтому, если у вас был какой-либо ответ экрана с CM11, перепрограммируйте его и попробуйте открыть программу обновления прошивки сенсорного экрана, чтобы вернуться к 2-касанию. Всякий раз, когда я прошиваю какие-либо CM ROM, первое, что я делаю после загрузки, - отключаю это приложение, чтобы случайно не прикоснуться к нему. Это нехорошо.
 
  • Like
Reactions: ipdev

Zayadlui

New member
Jan 7, 2015
4
1
My understanding is that problems with the touchscreen update flashing app can only be undone with the same app. So if you can open the app again and return to 2-touch, that should solve the problem. If you have no touchscreen response at all, I'm not even sure that returning to stock (meaning a true factory re-image, not just flashing a backup) will solve the problem.

So if you had any screen response with the CM11, reflash that and try to open the touchscreen firmware updater to return to 2-touch. Whenever I flash any CM ROMs the first thing I do after boot is disable that app so I won't accidentally touch it. It's not a good thing.

Via Google Translate:

Насколько я понимаю, проблемы с приложением для обновления сенсорного экрана можно устранить только с помощью того же приложения. Так что, если вы можете снова открыть приложение и вернуться к 2-касанию, это должно решить проблему. Если у вас вообще нет сенсорного экрана, я даже не уверен, что возврат к исходному состоянию (имеется в виду настоящий заводской повторный образ, а не просто перепрошивка резервной копии) решит проблему.

Поэтому, если у вас был какой-либо ответ экрана с CM11, перепрограммируйте его и попробуйте открыть программу обновления прошивки сенсорного экрана, чтобы вернуться к 2-касанию. Всякий раз, когда я прошиваю какие-либо CM ROM, первое, что я делаю после загрузки, - отключаю это приложение, чтобы случайно не прикоснуться к нему. Это нехорошо.
Doesn't work for me everywhere
 

nmyshkin

Recognized Contributor
Nov 21, 2013
1,556
455
Doesn't work for me everywhere
Try this: https://forum.xda-developers.com/t/...om-touchscreen-firmware.2418744/post-44947574

Once you have booted CM10 from sdcard, run touch updater to return hardware to 2-touch.

Via Google Translate:

Попробуйте это: https://forum.xda-developers.com/t/...om-touchscreen-firmware.2418744/post-44947574

После того, как вы загрузили CM10 с SD-карты, запустите программу обновления касания, чтобы вернуть оборудование в режим 2-Touch.
 
  • Like
Reactions: Zayadlui and ipdev

Zayadlui

New member
Jan 7, 2015
4
1
Try this: https://forum.xda-developers.com/t/...om-touchscreen-firmware.2418744/post-44947574

Once you have booted CM10 from sdcard, run touch updater to return hardware to 2-touch.

Via Google Translate:

Попробуйте это: https://forum.xda-developers.com/t/...om-touchscreen-firmware.2418744/post-44947574

После того, как вы загрузили CM10 с SD-карты, запустите программу обновления касания, чтобы вернуть оборудование в режим 2-Touch.
It turned out, the firmware "cm-9-20120815-acclaim-restorefw" helped 😁
After I installed your "CM 13" everything is "OK"👌
 
Last edited:
  • Like
Reactions: nmyshkin

Stu Pedaso

Member
Jan 26, 2022
14
0
The ROMs

Updated and revised 11-29-20


Generally I disabled any stock stuff I could that I would not use. Anything past CM 11 has a maddening issue I call "peek-a-boo keyboard", most noticeable when using the browsers. The keyboard drops out while you are typing or simply refuses to open without a struggle. For CM 12.1, disabling the resident Android WebView app seems to fix the problem. For the rest, well it just gets worse as you ask more from the device.

Note: I have noticed that both my Nook Tablets (8 and 16 GB) run better if they've been on for a bit. If yours is cranky when it gets up in the morning, pouring coffee on it won't help, but a little siesta after boot may be just the thing :)

CM 11 (y)(y)(y)(y)(y)
https://www.mediafire.com/?gq1y21uz11lr1c0
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle

This is arguably the best choice for the BNTV250a if you want something other than the stock B&N ROM. It runs smoothly enough that you can even keep the PlayStore app on it and it will still behave reasonably. It would be even better without it. The only drawback with this ROM is that Android Webview cannot be updated. This means that some websites will not display properly (XDA, for example!) or may simply crash, regardless of what browser you choose to use. I found the antique stock browser to be surprisingly good, but Via also works well. Also, the SSL is in need of updating, so you will run into issues with some websites and apps like OverDrive.

The lesson that this ROM taught me is that these tablets are for casual use. You can't just load them up with apps and expect them to run well. Think about what you really would like to use the tablet for. Consider older versions of apps that will probably still have more features than you will ever want but are less taxing to the system. You can see from the attached screenshots how I eventually pared my choices down. I should probably pare it down even more. Most of the apps are older versions and I've kept the total count low, certainly less than on my 16 GB tablet and other devices. You don't want to exceed about half of the internal storage capacity.

That said, I did find the Trebuchet launcher troublesome and replaced it with Nova Launcher. I also don't care for the stock CM file manager and replaced it with an old version of ES File Explorer I use on other devices.

CM 12.1 (y)(y)(y)
http://www.mediafire.com/file/7zxc2e...K6-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle

Before you start installing apps the behavior is sprightly, even on the BNTV250a. As the internal space decreases and RAM use increases, it becomes a little less so. Even so, when running well I think it comes close to CM 11 (with GApps), albeit with more lag.

The stock browser seems like the best bet (I tried many), though it can be slow. It also tends to self-close when you start to download a file (the download continues and completes). The "peek-a-boo" keyboard with all browsers seems to be "solved" by disabling the stock Android WebView app.

For me this ROM has two major issues. When it is unhappy, it will simply shut down the tablet, literally turning it off. This used to sometimes happen when I ran it on my 16 GB model, so it's not the fault of the BNTV250a. The other issue is problems for apps writing to the external SD card. For a tablet with precious little internal space, you just don't want apps downloading into internal space or storing lots of data there. There is an edit to the file /system/etc/permissions/platform.xml which corrects this issue for some apps. Find the section of platform.xml below and add the last line:
Code:
<permission name=”android.permission.WRITE_EXTERNAL_STORAGE” >
<group gid=”sdcard_r” />
<group gid=”sdcard_rw” />
<group gid=”media_rw” />

This change enabled OverDrive and Kodi, for example, to download files to the external SD card. It might work for others.
Not as fluid as CM 11, but WebView issues are gone and you can access most up-to-date content (if slowly).

CM 13 (y)
https://archive.org/download/cmarchive_snapshots/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle

I was actually pleasantly surprised by its behavior on the BNTV250a--until I started to install apps. I had no problems with writing data or downloads to the external SD card. I kept the card formatted as "portable" because it was convenient for me, changing from ROM to ROM as I experimented, but the ability to extend the internal storage on to the external SD card is a real plus for a device with so little internal storage space.

If you elect portable storage you will eventually run into an app that can't write there. Kodi is an example, I'm sorry to say. I've tried many "solutions" to this problem but the only one that worked for me is to edit /data/system/packages.xml, adding the permission for each specific app you want. This is a long file and I did this using the editor from the CM File Manager. There are probably easier ways. After locating the app you want in the xml file, add this line anywhere between the <perms> and </perms> tags:
Code:
<item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" />
This change will be overwritten if the app updates, so you might want to keep that in mind.

The "peek-a-boo keyboard" issue is maddening (not solved by disabling Android WebView) and many apps are so slow you really need to take your blood pressure medicine first. Not a good option unless maybe you install only one or two apps.

AOSP 6.01 "Marshmallow" (n)
https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/7651670774
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle

This is one of the ROMs built by @amaces. The AOSP builds are very lean compared to CM ROMs so I was hoping this might perform somewhat better than CM 13. But I don't think it does.

The first big hurdle is enabling root. My thanks to @digixmax for pointing out the right tool. After first boot (or maybe even before, but I did it after) you need to flash UPDATE-SuperSU-v2.46.zip. Works perfectly.

The stock launcher is, well, funky. I replaced it with Nova Launcher but after installing a few other apps it was clear the system was under great stress. Lots of black screens and crashes. Not a good option for the BNTV250a.

AOSP 7.0 (n)(n)
https://www.mediafire.com/?5vcw8l603d3r5sc
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Xposed

This is another ROM by @amaces and what I run on my 16 GB tablet. On that device it is virtually flawless (with GApps). I really wanted to say the same for the BNTV250a, but I can't.

Enabling root for the ROM is achieved by installing me.phh.superuser.1033 (attached below) after first boot. The ROM appears to be odexed to Tingle and so you must flash the correct Xposed (for 7.0) and install the installer app along with the FakeGapps app as described in the previous post.

The stock launcher is pitiful and you need to install a root file manager to get anything done. The system is laggy and video is not smooth. Not even a potential option for the BNTV250a.

Lineage 14.1 (n)(n)
https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3262390066
(there are many versions of this ROM. The link takes you to the "obsolete" folder where you need to hunt down lnos_acclaim-ota-NJH47F.180211.zip. This seems to be the only version without the shut-down bug)
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle

This is a third ROM built by @amaces (his most recent for the NT). I didn't have much hope for this because if 7.0 was an issue, I didn't expect 7.1 to perform well.

The only native root capability is for ADB. To enable full root, you need to flash addonsu-14.1-arm.zip (attached below). I did that after first boot but perhaps it can be done along with the ROM.

Not surprisingly the ROM has the feel of CM. There appears to be a file manager but it is only a partial reflection of the native file explorer and is useless for the manipulations that need to be done, so you need to adb install a root file manager as described in the previous post.

The stock browser is complete rubbish. It looks to be Jello(?) but it is the most infuriating collection of electrons I have ever encountered. There are no navigational buttons, no bookmark button--no buttons at all! I really tried. I used gestures (some rude), I tried magic words (many of which do not appear in children's books). Nada. When I finally managed to reach my test site it was like wading through, well, Jello! So....attached below is the nice lightweight stock browser from AOSP 7.0. Navigate to /system/app/Browser and there you will find Browser2.apk. Rename it to something else and copy in the Browser2.apk attached below, setting file permissions to rwx-r-r. Reboot. If you are successful, you can delete the old, useless browser apk. To enable bookmarks, navigate to /system/app/BookmarkProvider and inside you will find the apk file. Tap to install. I don't know why this needs to be done, but it does even on AOSP 7.0. Reboot and you've got a functioning browser (rife with "peek-a-boo keyboard")

The ROM hates Kodi, crashing constantly. Video from other apps is not smooth. This particular version seems to lack the shut-down bug that plagues nearly every ROM after CM 13, but it's a small comfort. Not a viable choice for the BNTV250a.
I realoze just how old this stuff is, but I cannot seem to make ANY of this stuff load on my Nook Tablet.
WTH am I doing so wrong??
 

Stu Pedaso

Member
Jan 26, 2022
14
0
You'll have to be more specific. "ANY" as in from step 1???

Old or not, I just did this recently (again) and it worked fine for me.
I believe my biggest obstacle is just finding all of the right stuff. Most of the links I have come across are dead.
I can partition fine, I can image to my sd card fine, not really sure of the files, but my device just boots normally.
 

nmyshkin

Recognized Contributor
Nov 21, 2013
1,556
455
I believe my biggest obstacle is just finding all of the right stuff. Most of the links I have come across are dead.
I can partition fine, I can image to my sd card fine, not really sure of the files, but my device just boots normally.
So are you trying to follow my instruction in the first/second post? I've just checked all the links and they are fine.

It should not be necessary to partition your device. All of the ROMs I installed were done with the stock partitioning. You are not going to gain anything by partitioning (if you can find partition directions for the 8 GB model...) because the system is just eventually overloaded by what it is asked to do when you get much beyond CM 12.1.

If you are not able to boot from the sdcard, that is the place to start. The files must be placed on the card in the order specified and some tablets really need the power cord plugged in to boot from the card. Mine doesn't, but it seems common enough that other posters have emphasized it so it must be an issue. It's also possible that your card is the problem. There has been a lot of talk about cards in the distant past, but I have always used class 10 uHD cards without any problem. It's hard to find anything else these days without a special order.

Edit: please forgive me for the silly suggestion, but are you by any chance actually working with the Nook Color? I only ask because I purchased a "Nook Color" online awhile back and was totally frustrated as I tried to work with it. Never could boot from an sdcard. It turned out it was an 8 GB Nook Tablet and I had all the wrong files to work with.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Updated and revised, 11-29-20

    In this post I am presenting a way to slightly extend the practical range of the 8 gb Nook Tablet by using microG for Google Services Framework spoofing rather than the resource-hogging GApps. Although I have tested these ROMs thoroughly on the BNTV250a, they would all likely run just fine with GApps on the 16 gb model (I currently run AOSP 7.0 with GApps), while only CM 11 runs acceptably on the 8 gb model with GApps. Let's get that simple setup out of the way first.

    I selected the unofficial CM 11 ROM with the final security patches by Chris Hoffmann [https://www.mediafire.com/?gq1y21uz11lr1c0]. It is serviceable for me. The main drawback is the old WebView (which cannot be updated) resulting in the inability of browsers to display many sites properly, including the current default skin for XDA. Despite this, I've come to feel that it's perhaps the best option, with or without GApps. Installing this ROM is easy. Flash with the recovery listed in post #2, reboot, then flash a pico GApps package from Open GApps. To run the ROM without GApps, read on.

    I made a quick tour of CM 12.1, CM 13, AOSP 6.0 and AOSP 7.0, and Lineage 14.1. In the following post I'll lay out some pros, cons and hints based on my experiences. I flashed each ROM several times, trying different things, building the system from scratch each time rather than restoring apps from backup. That gave me a chance to work with each OS and see how it would perform not only during setup, but also during a shakedown/tweaking phase. What I can say about all of these ROMs is that GApps effectively kills each and every one on the BNTV250a.

    Life without GApps
    I, of course, tried side-loading apps without GApps. Easy, right? I thought so until I came to a few that whined about requiring Google Play Services to run. Even mundane things like the NPR News app, my local newspaper and MX Player are "GSF dependent" (Google Services Framework). Then I tried another app that would not install at all. Turns out it did a license verification check (it's free!) and saw no Google anything, so forget it. This was sort of news to me I suppose because even my lowly NST has GApps installed, so I never encountered this issue before. You can hunt around for apps elsewhere but if you pick up an app that happens to be featured in the PlayStore, you may be out of luck no matter where you got it from. Or maybe not.

    There is a project called microG by XDA member @MaR-V-iN. It consists of a lightweight set of apps (two at minimum, a third if you want location services) which provide the needed authentication to Google servers and/or inquisitive apps. There is a catch: the ROM must support "signature spoofing".

    These ROMs do not have that option. You can Google "signature spoofing" to read the pros and cons. This is just information. Caveat emptor, etc. There is an Xposed module called FakeGapps which enables signature spoofing. I tried this on a few ROMs and found it worked fine. At the time I started this there was no official Xposed update for Android 7.0 and as that was one of my targets, I started looking for something else [note: Xposed has since been updated to include Android 7.0 and beyond]. That led me to Tingle by XDA member @ale5000. This is a Python/ADB based method of automatically patching framework.jar to enable signature spoofing. This seemed to me a more direct and elegant approach. Although I was intimidated by it at first, I eventually just dove in. The only thing I didn't already have was Python and that was easy enough to install. The process is basically automatic once it gets going. Unfortunately it does not work for ROMs that are odexed or deodexed. The AOSP 7.0 ROM turned out to fall in that category. Xposed must be used there.

    OK, what can all this do for you? It can get you a spoof of Google Services Framework without GApps. Period. There are a few simple additions to allow for location services. It used to be that you could also enable Calendar and Contacts syncing. While Calendar is possible using an older version of microG, no version seems to support Contacts. As for PlayStore access, this is possible running microG with CM 11, but not beyond. It's just too resource intensive. For ROMs beyond CM 11 I found the Aurora Store (F-Droid) to work OK, although not always in the same way. On some ROMs you can use the anonymous Aurora Store login, on others you need to supply a Google account (email). Trial and error.

    The General Process

    If you have never "flashed" anything before that you can talk about at work, then you need some basic instructions for creating an SD card that will allow you to try out these procedures. The excellent instructions by @digixmax here will get you started with the SD card. You need to follow steps 1-2 to prepare the card, although the version of TWRP you use will depend on the ROM you want to try out (see second post for links). Also, the ROM itself will vary (see second post for links) and you will not want GApps (unless you are just installing CM 11 with GApps). The remainder of the steps (3-10, skipping 9) also describe the general process of flashing a ROM (or other "flashable" files like Xposed, etc.) using the SD card.

    1. Flash the ROM using an appropriate recovery (I have listed the ones I used in the following post)
    2. First boot, enable root, USB debugging and ADB

    EITHER
    3. Connect tablet to PC via USB and access via ADB ("adb devices"--some of these ROMs require that you approve PC access to the tablet via ADB, so check the tablet screen to approve that option if needed)
    4. Open a command window on the PC and navigate to your Python installation directory. Because I was not sure what I was doing I just dumped the entire contents of Tingle into the Python directory. That simplified path issues for me. Type "python main.py" and select option 1. Wait for the "all done", hit CTRL-c and kill ADB server. Disconnect tablet from USB and reboot.
    OR
    3. Flash appropriate Xposed for the OS; reboot
    4. Install Xposed installer app and FakeGApps.apk; use Xposed installer app to enable FakeGapps (signature spoofing); reboot

    5. Install root file manager of choice if desired (the CM stock file managers are totally capable of the following operations if given root access; the stock file explorers of the AOSP and Lineage ROMs may allow the same, although I have had mixed results. You can always install a root file manager via ADB before continuing if all else fails) A copy of ES File Explorer is attached below.

    for CM 11 without GApps but with the PlayStore:

    6. Move Phonesky.apk--i.e. the PlayStore-- (old, lightweight version from a KitKat ROM: http://www.mediafire.com/file/1c2f0n3k3cwsln7/Phonesky.apk/file) into /system/priv-app; set apk file permissions to rwx-r-r.
    7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
    8. Reboot
    9. Check microG Settings to be sure spoofing is enabled and other permissions are given; set to enable Google device registration; add an account. This process can be slow. Be patient. If you end up at a black screen, reboot and try again or see if the account is already established.
    10. Open the PlayStore. Do some searching. You want to give it time to auto-update (this process may be completely silent). Exit. Check Settings>Apps>Downloaded to see if PlayStore has shown up there. If it has, then it may be updated. You can check yourself to see if the version number is higher. If there is no update, access the PlayStore again and check again. Once you have an update, you're good to go.

    OR, for ROMs beyond CM 11:

    6. Use root file manager to create the folder "Phonesky" in /system/priv-app. Set folder permissions to rwx-rx-rx. Use root file manager to move "FakeStore" apk into /system/priv-app/Phonesky and set apk file permissions to rw-r-r.
    7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
    8. Reboot
    9. Check microG Settings to be sure spoofing is enabled and other permissions are given.

    It's a lot, but if I could do it many times over you could do it once :)

    In the end you'll have a tablet spoofing Google Services Framework so most apps will run without whining, but without the crushing weight of the PlayStore or the full GApps.

    Contacts, Calendar and Location
    Life without GApps doesn't mean you have to give up these three services. Just keep in mind that running background services can compromise a system that is already on the edge.

    I tested the instructions that follow on a BNTV250a, using the stock Contacts and Calendar apps.

    1. Contacts

    There are some places in "on-line land" that describe a method for enabling contacts sync. I have not found the various methods to work any longer. It is possible to sync Contacts using DavDroid. There is only one version that will run on CM 11 and the same app will run on the other ROMs as well (attached below). However, you are adding more overhead to a device that is already pushing the limits. In the end I opted to export my contacts in vcard format and read them in as a local file. The more socially active may find this unacceptable, but it works for me.

    2. Calendar

    To enable calendar sync you need an older version of the main microG app as the capability has apparently been left on the cutting room floor, so to speak. If you have already passed all that, don't despair, just replace the current version with the older one and reboot. If the system doesn't seem to like what is going on, you may need to go into recovery and clear the Dalvik and cache. You will also need a file from a GApps package for the ROM you are working on. A pico version from OpenGApps will be fine. The file you are looking for is GApps/calsync-all.tar.lz from which you use 7zip to extract GoogleCalendarSyncAdapter.apk. For CM11, move the extracted apk file into /system/app (file permissions: rw-r-r). For ROMs beyond CM11, create the folder /system/app/GoogleCalendarSyncAdapter (permissions: rwx-rx-rx) and place into it the apk file (permissions: rw-r-r). Reboot, then go to Settings>Apps and enable sync permission for the app (if it hasn't been enabled already).

    For Calendar to work, you must add the Google account to sync through Calendar. So if you've already added a Google account via microG or the ROM Settings app, you'll need to remove it. Calendar will not recognize it for some reason. Instead, open Calendar. microG will bring up the account sign-in screen. Once you manage to get through that you will have an account established for the device that will work with other Google apps (if you use any) and with Calendar.

    3. Location

    To enable location you will need to install an app which coordinates WiFi triangulation (something usually handled by GApps). There are two possibilities. You can get a Unified NLP apk from the microG download page. After installing the app you can check your microG settings to see if everything is OK. Then you can check Settings>Location and set it up the way you want.

    If you want to use Maps you will also need to flash a maps.zip file from microG. This contains a couple of library files for Maps. As far as the Maps app itself, I have never had good performance from any version of Google Maps on my devices--until now. That's because I went fishing for an older, less bloated version that would run on the BNTV250a. It works beautifully on all my devices from KitKat to Nougat and allows pre-cache of map areas which don't expire. I've attached a copy of the apk file below.

    Email

    The stock Email client works great (at least for GMail accounts) and looks a lot like GMail (no surprise there). If you have your heart set on GMail, version 4.5.2--from GApps for Jellybean--seems to run just fine with a footprint of about 11 MB. I've attached a copy below.
    2
    Doesn't work for me everywhere
    Try this: https://forum.xda-developers.com/t/...om-touchscreen-firmware.2418744/post-44947574

    Once you have booted CM10 from sdcard, run touch updater to return hardware to 2-touch.

    Via Google Translate:

    Попробуйте это: https://forum.xda-developers.com/t/...om-touchscreen-firmware.2418744/post-44947574

    После того, как вы загрузили CM10 с SD-карты, запустите программу обновления касания, чтобы вернуть оборудование в режим 2-Touch.
    1
    Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
    While you're becoming familiar again with the procedures, give me a day or two to update the post. I recently redid my BNTV250a with CM 13 to try some things and then finally went back to CM 11 using the MicroG components rather than GApps. I'm really happy with it, but I have to say that the tablet (just like my BNTV250 with AOSP 7) behaves better if it's been on for awhile. It can be really cranky if you try to start using it right after boot.

    So I'll update the post title to include CM 11 and add some details about CM 11 to the second post in a few days.
    1
    Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.

    C:\Python27>python main.py
    MENU

    1 - Patch file from a device (adb)
    2 - Patch file from the input folder

    > 1 adb

    ERROR: Missing adb => ['adb']

    NOTE: Only one binary per type is required

    ERROR CODE: 65

    Not sure what I'm doing wrong
    I don't remember seeing the "adb" after "> 1", but I may just not remember. So, just in case and to be really clear (in case I wasn't before):
    1. I assume you have adb working on your PC or you wouldn't have gotten to the Python step. Did you ever set the PATH for adb? I confess I never bothered until I tried this procedure. But you have to be able to access adb from the Python folder for this to work. If you're not sure, just cd to the Python folder and try starting adb. If it doesn't work then the PATH needs to be set. Here's a good description for Windows (scroll down to "Step 2"): https://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
    2. When I said I dumped the contents of Tingle into the Python folder, I meant that literally. There is no "Tingle" folder in my Python folder,but there are a bunch of extra files that are "Tingle". Just want to be sure.

    Those are my only ideas at present. I hope one of them does the trick!
    1
    Try this: https://forum.xda-developers.com/t/...om-touchscreen-firmware.2418744/post-44947574

    Once you have booted CM10 from sdcard, run touch updater to return hardware to 2-touch.

    Via Google Translate:

    Попробуйте это: https://forum.xda-developers.com/t/...om-touchscreen-firmware.2418744/post-44947574

    После того, как вы загрузили CM10 с SD-карты, запустите программу обновления касания, чтобы вернуть оборудование в режим 2-Touch.
    It turned out, the firmware "cm-9-20120815-acclaim-restorefw" helped 😁
    After I installed your "CM 13" everything is "OK"👌