yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] Renate:
To answer my own question, the fingerprint is:

NOOK/ntx_6sl/ntx_6sl:4.4.2/KOT49H/50.0.118_user:user/release-keys

My patch for rotation of sleep images still works fine.

See glow45patch.zip (I've got to come up with a better naming/organization scheme).

The patch for white Launcher wallpaper doesn't seem to work, this need investigation/rewrite. still works fine.

I forgot to sign the thing. APKs need to be signed with something even in /system/app or /system/priv-app.

I was pleasantly surprised how quickly I could clean up from this full rewrite of /system.

I just had to re-modify:

default.prop
sbin/adbd
fstab.E60QD0
init.rc
init.E60QD0.usb.rc
android.policy
partner.apk
[Nook Touch General] Mnurlan:
Please, help me: for quite a long already I am experiencing a problem: while I read a book in AlReader a pop-up message appears, offering a set of options: Close the reader … etc., i.e. a dialog window that is usually triggered by pressing (tapping) Back in AlReader. I have tried to re-write the (custom) ROM (firstly I was holding a ReLaunch for a culprit, but now it is not present, so it is not the one to blame) – the same story – during the reading process you got (in random pattern) pop-up messages offering to close the reader. I have tried FBReader – it will simply (randomly) close and that is it. I am pretty sure the same would happen with Cool Reader. I personally believe that some stray currents are the culprit here, and already got tired and sick of it, and thinking about purchasing some Amazone e-book reader. Anyone got any ideas?

Nook Glowlight Plus, ROM: ZeroLab Nooter (Solemn Edition), plus XPosed, NGP Toolkit, root (Super SU). Launcher - Zeam Launcher.
[Nook Touch General] Renate:
"Close the reader", etc? Never seen this, but I don't use that software.

Is it something that could be swipe activated?

The over-sensitivity of the capacitive touch screen and the capacitive home button on the Glow2 is well known.
[Nook Touch General] Mnurlan:
I have assigned "BACK" action to EXIT action in this AlReader, which is triggered by tapping Home button
[Nook Touch General] krnark:
After update nnglow2.img dont' mount disk.
[Nook Touch General] Renate:
Correct, it doesn't. That's kind of the point.

If you were going to use Neo Noogie to do a full internal restore (or backup) from the desktop you wouldn't want anything mounted.

If you want /system mounted (in read write):

# mount /system

Guess what the command is for the other partitions. :p
[Nook Touch General] krnark:
I mean booting from nnglow2.img don't mount/connect/make any new disk on PC (Windows), but I try nnglow3.img and it's works. I think it's cos reshuffled mmc after update 50.0.118, so it's like Nook 3.
[Nook Touch General] Renate:
I just used nnglow2.img on my white Glow2 and I can see in Windows diskmgmt.msc all eight partitions.

It didn't assign a drive letter to the entire thing, which is how you are supposed to use it for full physical backup/restore.

This seems to be more a Windows problem.

Are you seeing all eight partitions in diskmgmt.msc?

(I'll look into what's up with the drive letter.)
[Nook Touch General] krnark:
No, with nnglow2.img I don't see any new drive in diskmgmt.msc, but adb shell working normal. With nnglow3.img I can see 3,69Gb drive with 9 partitions (2nd and 9th it's unused space actually) and H: letter on 5th partition.

Hmm, I have two BNRV510 with 49.2.37 and 50.0.118, and on 49.2.37 I have same behavior, with nnglow2.img I don't see any new drive.
[Nook Touch General] Renate:
Well, I'm all confused. I don't know how many what Nooks you have, what you're trying and what the results are.

Don't even bother trying or telling me about using nnglowX.img with Nook Glow Y where X!=Y.

Use the proper nnglowX.img on the Nook GlowX.

If it doesn't work:

# getprop|grep usb
[sys.usb.config]: [ums,adb] [color=red]<- should be response[/color]
[sys.usb.state]: [ums,adb]

# cat /sys/devices/platform/fsl-usb2-udc/gadget/lun0/file
/dev/block/mmcblk0 [color=red]<- should be response[/color]

# ls /dev/block
mmcblk0 [color=red]<- should be response[/color]
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8

Since Neo Noogie doesn't use the internal flash itself, if there are any differences between versions it must lie with u-boot or hwcfg.

I'll add my NTX hwcfg analyzer to the images sometime soon.
[Nook Touch General] krnark:
Sorry to waste your time, I solved problem. With nnglow3.img I have Device Manager->Portable Devices->H:\, but with nnglow2.img Device Manager->Portable Devices->NOOK. Just click "Update Driver" on "NOOK" label and voila, Windows install Mass Storage driver. :)

---------- Post added at 09:46 PM ---------- Previous post was at 09:27 PM ----------

Can you give me any advice about teardown, please? I have one book with stuck power button. May be should used heat gun, suction cup? Very strong adhesive in book.
[Nook Touch General] Renate:
You know, I still don't know which devices you own and which one you are speaking about.
[Nook Touch General] krnark:
I bought four Nook Glowlight Plus (BNRV510) in one lot on ebay, about $30. Two of them in good working shape, one with cracked screen and one with defect power button.
[Nook Touch General] Renate:
Use a single-edge razor blade inserted perpendicularly into the crack on the right, top and bottom sides and pry gently up.

Open the display as if hinged on the left hand side.

The flex cables are a bit too short.

You should probably disconnect them when it opens 45 degrees.

The same goes for reassembly.

If you do this too much and are unhappy with stickiness/fit, replace the tape.

https://www.microcenter.com/product/507366/ifixit-tesa-double-sided-tape-4-mm-wide
[Nook Touch General] krnark:
Thanks, I will try.
[Nook Touch General] Swiftloke:
I'd like to re-open this discussion, as I have a Glowlight 2 (BNRV510) freshly rooted in front of me that I wish to use as a typewriter. What needs to be done to enable OTG on this device?
[Nook Touch General] Renate:
Oh, some of those quotes were very old.

I've had a working thing for quite a while now.

The Glow2 does not have any means to supply current to the USB socket.

You will have to use a back-powering hub.

Yes, I do the pullup trick.

I have it written as a daemon so that no special security access to mmap or su (by UsbMode) is required.

You need two things:

The daemon usbhostd

The latest UsbMode-2.2.apk

You need to put usbhostd in /system/bin and chmod 755 it.

You need to modify /init.rc (which is packed in the ramdisk, use imgutil.exe).

Put this at the end.

service usbhostd /system/bin/usbhostd
class late_start
oneshot
[Nook Touch General] Swiftloke:
Thanks a ton for the work on getting OTG up. I've managed to install the usbhost daemon and your UsbMode utility, and it seems I have a "correctly" back-powering USB hub that is charging the Nook while it is connected to a power supply. However, out of the three keyboards I've tried (two wireless, one wired) and the mouse I tried, nothing seems to register with the Nook- the keyboards won't input any characters, and the USB utility states that no keyboard is connected. I have used the utility to set the USB port to Host Mode. Might there be something I'm missing? I'm using a Sabrent HB-UMLS USB hub.
[Nook Touch General] Renate:
Ok, first check:

Reboot, connect USB to desktop, ADB shell. Are you connected?

In UsbMode-2.2.apk (you do have version 2.2?) hit the host button.

Does your ADB shell connection drop (indicating that at least it switched out of peripheral mode)?

If it didn't disconnect:

Check if daemon is running: ps | grep usb (-> /system/bin/usbhostd)

Check if pipe exists: ls -l /dev/usb* (-> /dev/usbhost)

Try manually: echo 1 > /dev/usbhost (make sure there is a space between the 1 and the angle bracket).

Look at logcat for anything about "usbhostd": adb logcat *:s usbhostd

If it did disconnect:

Connect up your OTG/hub connector.

You are using a USB OTG adapter?

UsbMode is indicating charging?

Does the View USB show the hub's ports.

Plug something into the hub, (tap the View USB tree for refresh), do you see it?

Is there a check mark by the device (indicating driver)?
[Nook Touch General] Swiftloke:
Thanks for the detailed error checking, I'm sure it's bound to be helpful to others in future.

Seems the issue resolved itself the moment I connected to a computer, ADB shell'd in, then enabled host mode, causing a disconnect- at this point, the keyboard was recognized, and the "View USB" tab was correctly populated with all devices that were connected to the hub. Even the mouse works! Thanks again for all your hard work!

I'll update later to see if it's necessary to connect over ADB or if you just need to connect to any peripheral mode device i.e. a charger and then perform the host mode switch.
[Nook Touch General] Renate:
It shouldn't be necessary.

I just put that in so that you get a clear indication that something switched.
[Nook Touch General] vinhphucng25:
thanks
[Nook Touch General] ssdyj:
Hi Renate,

Thank you very much for so many helpful posts. Follow your guide, with Neo Noogie, I have successfully backup the image of my Nook Glowlight 3.

A question about fonts and dictionary substitute. For rooted Nook Simple Touch, the default fonts and dictionary of Nook BNreader app can be directly replaced by renamed .ttf and .db files. However, Glowlight 3 is different from Nook Simple Touch. As you said, the fonts files are hidden in partner.apk, more difficult to be replaced.

If not bothering too much, could you please let me know how to modify partner.apk, in order to replace some default fonts and dictionary of BNreader app, for rooted Glowlight3 as well as Glowlight 7.8? Personally, I prefer the default reader app, and really hope to improve its performance with other necessary fonts and dictionary. Although I am not familiar with Android OS, and not good at script compared with graphical operation, I would like to have a try.
[Nook Touch General] Renate:
Well, partner.apk is a big pig.

About 16 megs of it is those "screensavers", in 3 different resolutions no less.

You can take that 16 megs out, but then you have to fix the res\values\public.xml (part of apktool process) and also res\values\arrays.xml

I have a tool for doing just that but I haven't mentioned it elsewhere yet (purgeres.exe).

Then there's fonts unders assets/fonts too (I forgot how much).

bnereader.apk also has fonts under assets/fonts

If you wanted to change fonts and have the names match up you'd have to change a few things in the selection bits.

But seriously, if you look at how much analytics are in bnereader, you can be excused for not using it, even if you're not paranoid.

Or else keep WiFi off all the time.
[Nook Touch General] eriol1:
WiFi off is definitely good advice, that's what I used to do when I still had my ngp.

If wifi always off isn't practical for whatever reason, a firewall can come in handy.

I use afwall (frontend for iptables) on all my android devices. It's just so satisfying when an app like the keyboard for example gets denied internet access :cool:
[Nook Touch General] ssdyj:
Thanks a lot for your reply, Renate. It seems that modifying partner.apk and bnereader.apk to replace fonts is too complex for unprofessional. I am not able to explore the solution without step by step instruction, so in this stage, it is probably more feasible to put extra fonts in external storage.

I am still curious. Since default dictionary replacement is difficult, is it possible to use other dictionary in default BNereader? I found one of your threads, “Alternative dictionaries”, about adding new dictionary files to Nook, instead of replacing the default one. However, most of the posts are based on Nook Simple Touch. Does Lookup-1.1.apk work well on Nook Glowlight 3 and Glowlight plus 7.8? If so, could you please kindly post an updated guide?

Moreover, I have a .mobi format dictionary file for kindle. Do you have any idea how to convert it to .db format, or other format that suitable for Lookup-1.1.apk?

Thank you again.
[Nook Touch General] Renate:
Lookup-1.1.apk certainly works on the Glows.

It will even work on modern Androids (but I didn't really tailor the screen for smaller than Glows, I should do that.)

As far as the the integration with bnereader.apk to other dictionaries, I haven't looked at that.

I looked at some of the mechanisms, but I don't even see where the dictionaries are.

I suggest that you simply try Lookup-1.1.apk and see if it addresses any of your needs.

The only external interface that it has is the "dictionary" scheme.

# am start -d 'dictionary://chat' -a android.intent.action.VIEW
[Nook Touch General] ssdyj:
Thank you for your reply, Renate. I installed Lookup-1.1.apk and added a new dictionary in Glowlight3 successfully, with the code:

C:\>adb install Lookup-1.1.apk

C:\>adb shell mkdir /sdcard/Dictionaries

C:\>adb push dict.db /sdcard/Dictionaries

However, when I long-press a word in epub to look up, nothing different, only default English dictionary works.

Did I miss anything? Should I input the code “# am start -d 'dictionary://chat' -a android.intent.action.VIEW” in adb?
[Nook Touch General] Renate:
No. As I presumed the connection between the B&N stock reader is pretty hard-wired.

It's not like an open intent or anything.

It would take some patching of the reader to allow an external dictionary.

For reference:

com.bn.nook.reader.ui.ReaderMainView$2.processLookupButtonClick(String, String, String, String)

does startActivity() for

com.bn.nook.dictionary.LookupFullDefinitionActivity

Since I never use the B&N reader I probably won't get around to this.
[Nook Touch General] ssdyj:
Many thanks, Renate. I will switch to other more open Apps, maybe Koreader, to have a try :)
[Nook Touch General] vinhphucng25:
Hi [MENTION=4474482]Renate NST[/MENTION],

I rooted the Nook Glowlight 3 & install KoReader work perfectly with 4 buttons (I edited the imx-keypad file).

And I did the same to the Glowlight Plus and even edited the ime-keypad file but it was opposite 2 sides - mean: left upper is next, down is forward but right upper is forward, down is next.

I replaced the file in my Nook GL3 for the Plus but it's NOT working.

Please help me!!!

Thank You and Regards,
[Nook Touch General] Renate:
Sorry, I was napping. :)

Do you mean the GLP Glow2 6.0" or the GLP Glow4 7.8"?

Erm, duh, the Glow2 doesn't have buttons!

You can always use my UsbMode.apk (in signature) to see what a button does.

I had to charge up my Glow4.

I'll look into this soon...

This /system/usr/keylayout/imx-keypad.kl works fine for me.

key 116 POWER WAKE
key 102 HOME WAKE
key 191 MENU
key 192 BACK
key 193 PAGE_UP
key 194 PAGE_DOWN

Just make sure that you don't have any typos or Windows CR/LF in there.

As per normal B&N that file has lots of useless stuff in it.

You only need 6 lines for 6 buttons.
[Nook Touch General] ssdyj:
Hi Renate,

I am now using AlreaderX as reader app, and Bluedict as dictionary app. They are better than original B&N reader. However, the pop-up windows of the new apps are always too big to be fully displayed on the screen.

In new apps, some setting functions are implemented through pop-up windows. Unfortunately, since pop-up windows cannot be displayed fully, text or buttons on the edge cannot be seen or click. For instance, in Bluedict, I cannot customize toolbar because there is no “OK” button at the bottom of the screen.

Both of the two new apps have pop-up windows issues, while they can work well on cell phone, so it seems that it is my Nook glowlight 3 who has pop-up bugs.

Do you have any suggestion to deal with this problem? I have tried to reduce Nook’s font size, but it didn’t work.

Thank you very much.
[Nook Touch General] Renate:
Are both of these apps from the same folks?

Usually folks will put something like this in res/values/styles.xml

<item name="android:textSize">@dimen/TextSize</item>

And then in res/values/dimens.xml

<dimen name="TextSize">14sp</dimen>

And then in res/values-large/dimens.xml (or some other modifier)

<dimen name="TextSize">20sp</dimen>

This goes for all sorts of dimensions, padding, margins, sizes.

Sometimes people put a ton of different cases in.

I like to keep it fairly simple, as in above.

Usually, the case is different, something designed for phones that looks too small on a large tablet.

Do you know how to use apktool? Do you know how to sign? Take the app apart.

The hard part can be determining which of the modifiers is applicable to your device.

If you re lazy and just want to make this work for yourself, you can delete all the values-whatever directories except the plain values directory.

Then you can modify the files in that directory and know that it will make a change.

If you want to make a fix to send to the developers you'll have to do more specific work.
[Nook Touch General] ssdyj:
Many thanks, Renate.

The two apps are from different developers.

I've heard of apktool. If the problem is not caused by Nook’s bug, but by the adaptability of app design, I will contact the developers to request a fix to allow the apps fit more devices. If it doesn't work, I'll try to modify it myself later. :)
[Nook Touch General] dennisweelvdput:
Got the usbhost working. But cannot see it in Android. Any tips how to write to the USB stick or get sound file to play?
[Nook Touch General] Renate:
Well, that all looks good.

Did you modify init.rc to use usbhostd?

So, the devices are on there and their drivers are loaded.

Your audio adapter has little volume buttons, press them and see on UsbMode.apk and just generally.

I've not tried a USB flash. You'll need to mount it.

First, look in /dev/block for something new.

Then try:

# mount -t vfat /dev/block/whateveritwas /mnt/media_rw/extsd

If this all works you can add it to the fstab.

But seriously, it's easier to solder in an SD card: https://xdaforums.com/t/adding-an-sd-card-to-glowlights-2-3-4.3944830/

Mmm, for the audio it looks like B&N removed all the alsa audio stuff.
[Nook Touch General] dennisweelvdput:
Would have loved to get audio working. As for the stick:
[Nook Touch General] Renate:
Huh? You want sda1

Also, you're not rooted.
[Nook Touch General] dennisweelvdput:
I Don t know what it should be. And I am rooted, altho therminal for Android didn't recieve su rights. mi
[Nook Touch General] dennisweelvdput:
And yes i Am a real noob. But hope to be quick study 😄
[Nook Touch General] dennisweelvdput:
The USB audio buttons worked. On screen the soundslider went to max and down to min. So proof that it is working. But unfortunately no sound (would love to know how to get the sound files back and working) 🙃
[Nook Touch General] dennisweelvdput:
I think this is the place to be.

But have no clue how to progress. Any tips?
[Nook Touch General] Renate:
By that, I meant that you want sda1.

/dev/block/sda1

I don't know what user you are in your terminal and whether such a user can mount but you haven't shown me yet that you can't.

This may be easier if you use ADB over WiFi.

C:\>adb tcpip 5555
restarting in TCP mode port: 5555
C:\>adb connect 123.123.123.123:5555
connected to: 123.123.123.123:5555
C:\>adb shell
#

Obviously "123.123.123.123" is an example, you have to find the IP.

Getting a USB flash drive to work on this is a bit pointless.

The power consumption is not going to be so good.

The data rate is not going to be so good.

You have to operate the USB through UsbMode which is not as convenient as just plugging in.

And you have this thing hanging off your Glow.

The only possible argument would be if you have a permanent wired installation.
[Nook Touch General] dennisweelvdput:
Makes sense. Is a lot of wirering. But audio would still be cool? Is that somehow do-able?
[Nook Touch General] Renate:
Well, you've gotten this far, aren't you going to see if you can get the USB flash going anyway?

The Glow4 has (and the Glow2/3 doesn't):

/system/lib/hw/audio.a2dp.default.so
/system/lib/hw/audio.primary.imx6.so
/system/lib/hw/audio.r_submix.default.so
/system/lib/hw/audio.usb.default.so
/system/lib/hw/audio_policy.default.so
/system/lib/libtinyalsa.so

You might be able to get this working.

Debug using the alsa utilities.
[Nook Touch General] dennisweelvdput:
USB audio makes device reboot.

BUT usb-stick works 😄👍
[Nook Touch General] dmkbox:
Hi. I'm sorry to dublicate my post here.

I'm bricked my Glowlight plus 2015.

I'm install twrp. After that I wipe all partition, forgot to uncheck system. Than I flashed custom firmware.

Now I have continuous NOOK logo. i'm able to do factory reset withour luck. Windows cannot identify device

What should I do? I can open my Nookand connect via UART. But what's next?
[Nook Touch General] inpsydout:
Hi! I Bought an NG+ a couple of years ago, but hadn't even touched it since, because I didn't want to spoil the ability to root, sideload apps, etc.

Can someone please give me a recap or point me in the direction of what I can do with it?

Basically, I guess I'd like to read web articles, load pdfs, and load/read ebooks. What else is possible with it?

Sorry, I tried to read through the thread but I'm not tech-savy so I don't understand much, and couldn't find a starting point.

I'd really appreciate it, thanks.

Edit:

I had this NG+ on shelf because I wanted to root.. And now, when I made space to do it... I couldn't get past upgrade screen during startup. I upgraded and now I guess I messed up because it wont show 'development options' when I tap software version 3 times.. instead it asks "Are you sure you want to redo a full sync of your content"?

I guess my device is just as good as a brick now :( damn B&N you suck
[Nook Touch General] Renate:
It's 7 taps on Build Number to get Developer Options.
[Nook Touch General] inpsydout:
In settings, there's ABOUT and in there, there's this Menu with no Build Number.

They probably changed it in the last release.
[Nook Touch General] nmyshkin:
Just guessing here--I don't have one of these. Earlier in the thread somewhere is this:

Clearly, your image does not show "software version". How about "app version"? Worth a try (but I doubt that tapping wildly "10 times or so" is really necessary).

Edit: or, try tapping on the "n" logo--this works for the Glowlight 3
[Nook Touch General] inpsydout:
Thanks, it worked. I tried to install TWRP but it's too complicated and instructions aren't easy to follow from anywhere.. Appreciate you help anyways
[Nook Touch General] nmyshkin:
Tapping which one? (for the benefit of someone else...)

Edit: which directions are you trying to follow for TWRP?
[Nook Touch General] inpsydout:
The N logo on top.

I was trying to install this:

https://xdaforums.com/t/gp-g3-gp7-8-twrp-alternative-firmware.4074347/

I'll try again another day.. I'm just not savvy enough.

I tried ADB on command prompt but couldn't get it to work. Typed cd, pressed enter, then dragged abd.exe, pressed enter, and a lot of info shows up, but then when I try adb commands, they don't work.
[Nook Touch General] nmyshkin:
If you're having issues wth adb and are not using a Mac, I recommend this package: https://xdaforums.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790

On installation you'll get a unique command prompt window just for adb that may resolve some of the common annoying issues.

None of us is savvy enough (except @Renate), so we just read and re-read, ask for help and then ask again. Nothing like a good night's sleep.
[Nook Touch General] nmyshkin:
Also with adb, you can cd to the directory where it is installed ( unless you've set up paths), but from there just type something like "adb devices". If the device is connected properly you should see a message about adb starting and finally a string of characters representing the device.
[Nook Touch General] Renate:
ADB is really annoying in that if you type something wrong (or even just don't tell it what to do) it will spit out pages of unhelpful help.

C:\>adb.exe devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
12345678 device
C:\>adb.exe shell
$ cd sdcard
$ ls -l
some_file
another_file