yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] jago25_98:
andrewed,

check out the Alphasmart. It's very very old but build like a tank. It's not very good for editing but for raw text input and a rock bottom price it's still fantastic.

The Nook could still be useful though. If you power the USB to get host mode working you could still use the Nook for editing in the right workflow.
[Nook Touch General] kenpoole:
Is there any way to get the epub reader to rotate its presentation? I want the power connector to be at the top of the device when I read to avoid bending the usb wire/stress the connector. I tried to find a way in the store but it did not rotate automatically, and I did not see a setting to allow it.
[Nook Touch General] Renate:
None of the Nooks have an accelerometer, so automatic rotation is out.

Normally I use apps that you can select the orientation.

You can switch to another app and the orientation will stay the same.

Many devices prevent you from using reverse portrait. I have no idea why.

[b]Glow2[/b]
/system/framework/framework-res.apk
res\values\bools.xml:
<bool name="config_allowAllRotations">false</bool>
res\values-sw600dp-v13\bools.xml:
<bool name="config_allowAllRotations">true</bool>

[b]Glow4[/b]
/system/framework/framework-res.apk
res\values\bools.xml:
<bool name="config_allowAllRotations">false</bool>
res\values-sw600dp-v13\bools.xml:
<bool name="config_allowAllRotations">false</bool>

It turns out that this config value only has to do with accelerometer orientation switching.

If an app requests an orientation, it gets it.

I've checked on Glow2 & Glow4 and I can do upside-down apps.

I wrote a cheesy app that does nothing (except it's upside down).

When I switch to an app that doesn't have fixed orientation it stays upside down.

You might have to patch your launcher so that it leaves the orientation alone.
[Nook Touch General] Renate:
I've become quite fond of upside down.

On the Glow2 it means that it stands flat on a table instead of wobbling on the bump of the USB connector (even without a cord).
[Nook Touch General] Renate:
The Glow4 is not markedly different from the Glow3.

For info on how to add your own sleep images in rotation and make the Wallpaper white see https://xdaforums.com/nook-touch/general/ngl3-screensaver-images-t3946008
[Nook Touch General] helpful_info:
Hi - I was thinking of getting the new 2019 Glowlight Plus. However I am not very technical and would appreciate some help with basic questions

1) I will use it mainly to read using the Kindle app. Is it as simple as installing a launcher and Kindle APK without rooting or do I need to root to get Android apps to work properly? I had asked this question in another thread but may not have categorized it correctly

2) I read a number of forums from a few years earlier which said Nook would get stuck in boot animation when restarted with a launcher such as Nova or ReLaunch.

Would this still happen with the new Glowlight plus and what would I need to prevent this?

Thanks
[Nook Touch General] mach281:
I rooted the GLP and installed ReLaunchX and the Kindle app. Boot takes a bit longer, and then playing with the power button then hitting cancel at the reboot request brings up main screen. This is inconvenient but nothing more since I don't reboot often.

Re the compatible Kindle app v. 8.22.0.15 I have installed, you may not want to use it as your primary reader. The fonts are relatively thin compared to the Nook's with no apparent way to increase the thickness. Moreover the default page turn animation is annoying, with no setting to disable. Then you have page turn buttons that don't work with 3rd party apps. Instead, I convert my Kindle books to epub with my own prefered font and load them onto the GLP. Problems solved.
[Nook Touch General] helpful_info:
Thanks for posting about your experience - this was very helpful

1) Do I need to root to sideload the Kindle and Reluanch app or can I do it as long as I enable developer options and then USB Debugging?

2) I read through this thread but was not clear about which exact files I need to root. Let me know if you have link which has all the files and instructions to root

3) When you reboot, what is the sequence with the power buttons to exit the boot animation? Do you hold down the power button for a while and a menu appears or is it some other sequence?
[Nook Touch General] mach281:
You want to root first otherwise you won't be able install a launcher to access your 3rd party apps like the Kindle. In a nutshell you need to get USB debugging running on the Nook side and ADB installed on your computer first. Here are the instructions I followed:

https://xdaforums.com/nook-touch/general/how-to-root-set-nook-glowlight-3-t3802331

Then you download apks you want to install on the Nook to your computer and then install to Nook via the ADB install commands in a terminal.

To exit animation let it run a few minutes so it finishes the boot in the background. Then hold the power button down. When the reboot/power/cancel menu comes up select Cancel. This works for me.

When it's all set up you can install apps like Yalp or Fdroid to install other apps and maintain any updates or use a built-in web browser instead of the PC-to-Nook install.
[Nook Touch General] Renate:
That's strange.

My Glow4 stops the animation by itself.

# getprop|grep bootanim
[bn.bootanim.exit]: [0] [color=red]<-- wackiness put in by B&N[/color]
[init.svc.bootanim]: [stopped]
[service.bootanim.exit]: [1]

/system/priv-app/partner.apk seems to be using the bn.bootanim.exit

/system/bin/bootanimation seems to be using listening for either bn.bootanim.exit or service.bootanim.exit

When you start up, before you power/cancel what does the above command say?
[Nook Touch General] helpful_info:
Thanks for all the detail.

You had mentioned the the default page turn animation was annoying. Is this the page curl on the Kindle Android or is it the case that the Kindle redraws every page on page turn and the screen flashes?

I read on another website that the Kindle Android app would redraw the white background on each page which would make the page flash on every turn. Did you experience that as well?

Thanks
[Nook Touch General] mach281:
[init.svc.bootanim]: [running]
[service.bootanim.exit]: [1]

---------- Post added at 11:15 PM ---------- Previous post was at 10:59 PM ----------

I didn't mention the page refresh flashes before, only the page turn animations. 3rd party apps don't seem to change the Nook's default refresh rate, which I'd love to be able to adjust in the settings to a higher frequency for those dark background apps which are unusable due to the heavy staining.
[Nook Touch General] Renate:
Well, maybe our systems are different.

# md5 /system/bin/bootanimation
5b480ed4280bb271f734f71386ffd2ef /system/bin/bootanimation
# getprop|grep finger
[ro.build.fingerprint]: [NOOK/ntx_6sl/ntx_6sl:4.4.2/KOT49H/50.0.88_user:user/release-keys]

Easiest and quickest way to fix this: just rename bootanimation bootanimation.bak

Booting you won't see any animation at all and it will just jump to your launcher.

Other way: grab another bootanimation from an older Glow release.
[Nook Touch General] mach281:
Bootanimation MD5 identical.

However getprop|prep finger yields

[NOOK/ntx_6sl/ntx_6sl:4.4.2/KOT49H/50.0.133_user:user/release-keys]

Bootanimation rename is unsuccessful as it complains Nook is a read-only file system.
[Nook Touch General] Renate:
Of course it is.

# mount -o rw,remount /system
# cd /system/bin
# mv bootanimation bootanimation.bak
[Nook Touch General] mach281:
Maybe I'm doing something wrong here. Response to mount command:

shell@ntx_6sl:/ $ mount -o rw,remount /system
mount: Operation not permitted
[Nook Touch General] Renate:
Sorry, you have to be rooted.

Note that you've got $ and not #.
[Nook Touch General] mach281:
I thought I was. Perhaps the last software update changed that? Re-running rootnook.sh again I get the following:

/Users/Dragonfly/Downloads/rootGLP-3/rootnook.sh: line 13: [: too many arguments
adb: error: cannot stat 'files': No such file or directory
pkg: /data/local/tmp/.nookrooter/eu.chainfire.supersu.apk
Failure [INSTALL_FAILED_INVALID_URI]

Restarting adbd as root... /Users/Dragonfly/Downloads/rootGLP-3/rootnook.sh: line 29: [: too many arguments

sh: /data/local/tmp/.nookrooter/doroot.sh: No such file or directory
Rooted.

Thanks for your assistance.
[Nook Touch General] mach281:
I couldn’t resolve the issue using the Mac so I used Windows which had its own numerous adb “unauthorized” issues. But I was finally able to root [again?] and rename the animation file. Now it starts up with a black screen and proceeds to the start screen.
[Nook Touch General] dorb87:
Hi,

Has anyone discovered how to use the Bluetooth to attach a keyboard?
[Nook Touch General] Renate:
I didn't have any problem pairing a keyboard. https://xdaforums.com/showpost.php?p=79905414&postcount=32

Did you try:

adb shell am start -n com.android.settings/.bluetooth.BluetoothSettings
[Nook Touch General] dorb87:
My apologies, I should have been more clear. I was looking into buying one, and was hoping to use a Bluetooth remote to page turn. Glad to hear this model is capable of that.
[Nook Touch General] dorb87:
Hi Renate,

Would you happen to know of a way to change the sleep screen to a picture instead of the BN stuff? The N+ Toolkit doesn't seem to work for the screensaver like it had on previous models.

Also, that worked great to bring up the Bluetooth settings and it found the keyboard. Works awesome.

Thanks!
[Nook Touch General] dorb87:
Hi Renate,

I fear I may have bricked my Nook already. I went to do a factory reset, but it never loaded recovery. No matter how many times I hard power down and then back up, it just loads a black screen and sits. Doesn't list in Fastboot or ADB at this point. Is there any coming back from this?

It still makes a ding when plugged into Windows, if that is of any help to diagnosis.

Ran imxboot, and It didn't find a device. In device manager this is the info that comes up for it:

Unknown USB Device (Configuration Descriptor Request Failed)

USB\VID_0000&PID_0003\6&1963D76C&0&4

Even Newer Update: I was able get the device into fastboot by connecting to PC, hard power off. Then N Button + Power. Can you possibly explain what my next steps would need to be? I tried flashing the Recovery and Boot img from an update.zip I found on another recent thread. But that still isnt booting up. Could you possibly point me in the direction of starting fresh on the device via fastboot and the update.zip?

I also have tried flashing Ryogo's TWRP img, which flashes fine in Fastboot, but then I issue Fastboot Reboot Recovery, and it doesn't load up into Recovery, just the black screen.

I'm happy to try anything to get this going again, even crack it open and use a console cable, etc.

If you could please work some of your Nook Wizardry, I would be so appreciative. Thanks!

More Info: I've tried flashing both the stock Nook Recovery and TWRP. Neither load, but TWRP makes the screen flash white before going black. Stock stays black. I noticed when booting regular with just the power button from powered off, if TWRP is installed, the screen flashes white. Not so with stock Recovery installed. So I think it's trying to get to Recovery on regular boot as well, but not getting there.
[Nook Touch General] Renate:
Sorry, I was asleep at the wheel.

If you have fastboot, it's probably better (and easier) to try to boot images rather than flash them.

C:\>fastboot boot myimage

Are you sure that your TWRP image is good? Do you have a link for it?

Apparently your uboot is ok.

If something is slightly wrong it might be booting TWRP but no screen.

Did you check to see if you have ADB afterwards?

It's hard to tell exactly what is failing without a console.
[Nook Touch General] dorb87:
So this is the TWRP image I have tried. https://github.com/Ryogo-Z/nook_ntx_6sl_twrp

I have tried to boot the recovery image as well, rather than flash and it does the same. ADB never comes up, which leads me to believe it's not loading recovery for some reason, but trying. Also leads me to believe the screen controller didn't give out, and it's not the system working fine behind a dead screen. Do you think if some kind soul with the 7.8" pulled their system.img, boot.img, and the other partitions, I could flash them with Fastboot, would that help anything if the System is at fault?

If not, I'd be happy to get a UART console. Please forgive my newness, but does that require any soldering at all? That is something I'm unfamiliar with, but hey if the Nook is dead otherwise, I'm always down to learn.
[Nook Touch General] Renate:
I don't see any full prebuilt images here.

To get a console temporarily working, you can just use a friction fit connector, you don't have to solder.

(As a matter of fact, soldering is a bit of a pain with the conformal coating and no thermals on the grounds.

I wouldn't introduce anybody to soldering this way.)
[Nook Touch General] dorb87:
Sorry about that, this is the link: https://github.com/Ryogo-Z/nook_ntx_6sl_twrp/releases/download/3.3.1/twrp.img

Now for the UART and the friction fit connector, would you possibly be able to point me to which item I need to purchase, and I will order?

Is this a good UART cable? https://www.amazon.com/ADAFRUIT-Ind...ords=uart+console&qid=1576427774&sr=8-1-fkmr0

Regarding the friction fit connector, that I've been unable to track down. Is there a particular site you order from?
[Nook Touch General] Renate:
That UART cable uses 5V data, so it's really not good for much stuff today.

The Glow2, 3, 4 use 3.3V

I have a bunch of the Adafruit FTDI friends, a bit pricey, but it is a genuine FTDI chip, not like most Chinese stuff.

https://www.amazon.com/dp/B00NAY1VJ2

By friction fit I meant using jumper wires with square pins in the ends, stuck into the hole and hold down the cable with something so that it puts enough sideways pressure on the hole to make contact.

Connect TX, RX and Gnd.

Leave anything labelled VCC, +5V, +3V disconnected!!!
[Nook Touch General] Renate:
Well, that TWRP doesn't work for me on my Glow4.

It looks like it is for the Glow4.

After it boots there is not a UART console.

I didin't dive any further.
[Nook Touch General] dorb87:
Interesting, a couple questions for you.

1) I will open a bug report with the creator of that TWRP image, what behavior are you seeing when you boot it? Does your screen flash white briefly to clear, and then sit at a black screen?

2) Which Recovery are you currently using on your 7.8", the stock? If so, would you be willing to pull that img and I could try booting that and see if it loads?
[Nook Touch General] RyogoNA:
Glowlight Plus 7.8 and Glowlight 3 is the same thing in regards of firmware, so yes, that TWRP should work just fine.

I recall reports from some users that TWRP worked just fine on Glowlight Plus 7.8, that's why it is stated as supported on github.

---

First we need to establish - if TWRP does not boot or it boots but does not update the screen?

If if boots - then normal adb console should be available through usb, cannot say anything regarding uart.

Also, "fastboot boot twrp.imp" may be unreliable, sometimes it won't work and flashing recovery may be a better option then.
[Nook Touch General] dorb87:
There was a firmware update available when I started it for the first time, and I performed that. Is it possible the firmware update post-Stock 7.8" changed something?

It sits on a black screen, ADB isn't up in the background. Tried flashing or booting straight to it. Both do the same thing. The screen goes white as if refreshed, then goes black. Left it on for over an hour, periodically checking to see if anything came up in ADB. No luck.
[Nook Touch General] RyogoNA:
Well, since bootloader gets updated too... theoretically - yes, practically - I'd highly doubt so.

The bad news is - I do not own a device so I'm unable to do any proper testing. So, I don't think it would be possible to solve the issue quickly.
[Nook Touch General] dorb87:
Well I'd send you this one since it's a brick, but it was an early Xmas present, so I should probably wait to tell I broke it. :D

Is there anything I can do to help troubleshoot it for you?
[Nook Touch General] Renate:
Screen? What are you talking about? My Glow4 doesn't have a screen. I broke it months ago. :p

That's alright, I don't really need a screen. I use my UART and adbgrab.

(adbgrab does screen grabs and allows clicking on the screen.)

I guess that I still have stock recovery on my Glow4.

It's got no ADB and there is UART log output but no console shell.

I'll make a recovery image with ADB.
[Nook Touch General] dorb87:
Oh no, that's not good. I made it about 6 hours before I broke my device. Hopefully the stock Recovery will do the trick. I believe it's currently stuck trying to boot into a recovery that doesn't load fully. Really appreciate your help.
[Nook Touch General] Renate:
Neo Noogie recovery image for the Glow4 is in the signature.

Here's a screenshot. :p
[Nook Touch General] dorb87:
Wow thank you so much. So there is progress now. When I boot up the Nook after flashing your recovery, it does load up. And I now I have ADB! Still won't load the OS, though.

I tried to do an wipe command from shell in ADB, but it was rejected.

Also tried to flash a zip and it said

"adb: sideload connection failed: closed

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: closed"

I really hate to be a further bother, could I ask what next steps would you take with just ADB and Fastboot. I am such a novice, beyond sideloading a bit, ADB is over my head.

This is what's in my root directory (so seemingly all there):

# ls

RTL8189_init.rc

acct

charger

default.prop

dev

file_contexts

fstab.E70Q50

init

init.E70Q50.rc

init.E70Q50.usb.rc

init.rc

initlogo.rle

proc

property_contexts

root

sbin

sdcard

seapp_contexts

sepolicy

sys

ueventd.E70Q50.rc

ueventd.rc

I wonder if it's still trying to perform the factory reset I issued from the OS that started this whole mess. and why it only will boot to Recovery but the file system is there. Would there be a way to cancel that in the system from ADB?
[Nook Touch General] Kramar111:
Please add it here https://xdaforums.com/nook-touch/development/neo-noogie-backup-restore-glow2-glow3-t3784575

Thanks
[Nook Touch General] Renate:
I will. I still have some more cleaning up to do on all the Neo Noogies.

If you're sure that you have a good update, you can install it manually.

First, download the latest (from 2 minutes ago) nnglow4.img from the signature.

It makes things a bit easier by not locking /.

# mkdir data
# mount -t ext4 /dev/block/mmcblk0p4 /data
# mkdir system
# mount -t ext4 /dev/block/mmcblk0p5 /system

See this post: https://xdaforums.com/nook-touch/general/nook-glowlight-plus-t3230323/post80114208

Get update-binary out of the update zip.

C:\>adb push myupdate.zip /data/local/tmp/
C:\>adb push update-binary /data/local/tmp/

# cd /data/local/tmp
# chmod 755 update-binary
# ./update-binary 1 1 myupdate.zip

Yes, yes, I will/should add something to make mounting easier...
[Nook Touch General] dorb87:
Just wanted to confirm so I don't make my situation worse for myself. I see a updater-script file and a update-binary, but no updater-binary. (within that ZIP) I am guessing to use the update-binary, but just to be sure could you confirm?

Edit: A little googling has further confirmed my suspicion to try update-binary

---------- Post added at 09:51 PM ---------- Previous post was at 09:34 PM ----------

So I get this when I execute the final command listed from shell:

ui_print Upgrade : ALL

ui_print

progress 0.100000 3

script aborted: This package is for "ntx_6sl" devices; this is a "".

ui_print This package is for "ntx_6sl" devices; this is a "".

ui_print
[Nook Touch General] Renate:
Yes, it should be "update-binary".

As the linked post says:

# setprop ro.product.device ntx_6sl

(Before you do the ./update-binary 1 1 zip)
[Nook Touch General] dorb87:
My apologies, I hadn't see that. So I think things are getting closer. It threw another error though.

adb shell
# mkdir data
# mount -t ext4 /dev/block/mmcblk0p4 /data
# mkdir system
# mount -t ext4 /dev/block/mmcblk0p5 /system
# exit
PS C:\Users\hcors\Downloads> adb push update-binary /data/local/tmp/
update-binary: 1 file pushed. 1.3 MB/s (1791756 bytes in 1.319s)
PS C:\Users\hcors\Downloads> adb push 78.zip /data/local/tmp/
78.zip: 1 file pushed. 1.3 MB/s (216975365 bytes in 160.056s)
PS C:\Users\hcors\Downloads> adb shell
root@android:/ # cd /data/local/tmp
root@android:/data/local/tmp # chmod 755 update-binary
root@android:/data/local/tmp # setprop ro.product.device ntx_6sl
root@android:/data/local/tmp # ./update-binary 1 1 78.zip
ui_print Upgrade : ALL
ui_print
progress 0.100000 3
ui_print Target device check: ok
ui_print
ui_print installing system...
ui_print
progress 0.500000 15
Creating filesystem with parameters:
Size: 377487360
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 1440
Label:
Blocks: 92160
Block groups: 3
Reserved block group size: 23
Created filesystem with 11/23040 inodes and 2939/92160 blocks
mount: failed to mount /dev/block/mmcblk0p5 at /system: Device or resource busy
minzip: Can't create containing directory for "/system/app/Browser.apk": No such file or directory
minzip: Extracted 0 file(s)
failed to mkdir /system/fonts/DroidSans-Bold.ttf: Read-only file system
symlink: failed to symlink /system/fonts/DroidSans-Bold.ttf to Roboto-Bold.ttf: making parents failed
symlink: failed to symlink /system/fonts/DroidSans-Bold.ttf to Roboto-Bold.ttf: No such file or directory
script aborted: symlink: some symlinks failed
ui_print symlink: some symlinks failed
ui_print
[Nook Touch General] Renate:
Try it from a fresh start.

This time do a mkdir /system (as before), but no mount /system.
[Nook Touch General] dorb87:
PS C:\Users\hcors\Downloads> adb shell
# mkdir data
# mkdir system
# mount -t ext4 /dev/block/mmcblk0p4 /data
# exit
PS C:\Users\hcors\Downloads> adb push 78.zip /data/local/tmp/
78.zip: 1 file pushed. 1.3 MB/s (216975365 bytes in 160.074s)
PS C:\Users\hcors\Downloads> adb push update-binary /data/local/tmp/
update-binary: 1 file pushed. 1.3 MB/s (1791756 bytes in 1.322s)
PS C:\Users\hcors\Downloads> adb shell
# cd /data/local/tmp
# chmod 755 update-binary
# setprop ro.product.device ntx_6sl
# ./update-binary 1 1 78.zip
ui_print Upgrade : ALL
ui_print
progress 0.100000 3
ui_print Target device check: ok
ui_print
ui_print installing system...
ui_print
progress 0.500000 15
Creating filesystem with parameters:
Size: 377487360
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 1440
Label:
Blocks: 92160
Block groups: 3
Reserved block group size: 23
Created filesystem with 11/23040 inodes and 2939/92160 blocks
minzip: Extracted 820 file(s)
ui_print installing firmware...
ui_print
progress 0.100000 2
progress 0.100000 2
progress 0.100000 2
package_extract_file: can't open /cache/u-boot.bin for write: No such file or directory
package_extract_file: can't open /cache/logo.jpg.header for write: No such file or directory
package_extract_file: can't open /cache/logo.jpg.raw4 for write: No such file or directory
progress 0.100000 2
ui_print install complete!
ui_print
ui_print script succeeded: result was [install complete!]

So this time it says it completes, but the result takes place in a fraction of a second. Much too quick to have extracted 200 meg from the zip (I think). The result is that it doesnt boot, the screen does nothing. Unable to boot back into Neo Noogie recovery until I flashed it again with Fastboot. Have ADB back. Is this thing toast?
[Nook Touch General] Renate:
It's after breakfast, no toast today.

Try:

# mkdir /cache

And if that doesn't work:

# mkdir /cache
# mount -t ext4 /dev/block/mmcblk0p6 /cache