Renate
Recognized Contributor / Inactive Recognized Dev
If you have ADB working all you need is:
Code:
C:\>adb reboot recovery
Code:
C:\>adb shell
# reboot recovery
Nook Glowlight 3
- Thread starter Windsor1959
- Start date
Renate
Recognized Contributor / Inactive Recognized Dev
Code:
Disk /dev/block/mmcblk0: 7818 MB, 7818182656 bytes
4 heads, 16 sectors/track, 238592 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Partition Format Id Start End Size (bytes) Mount
--------- ------ -- ----- ------ ------------- ---------
mmcblk0 1 238592 7,818,182,656
mmcblk0p1 emmc 83 33 223 6,258,688 /boot
mmcblk0p2 emmc 83 609 1632 33,554,432 /recovery
mmcblk0p3 5 1633 26720 822,083,584
mmcblk0p4 ext4 83 26720 238080 6,925,877,248 /data
mmcblk0p5 ext4 83 1665 13952 402,653,184 /system
mmcblk0p6 ext4 83 13984 26272 402,685,952 /cache
mmcblk0p7 ext4 83 26304 26560 8,421,376 /device
mmcblk0p8 emmc 83 26592 26719 4,194,304 /miscRenate NST,
thank you, this is really helpful.
mmcblk0p3 - do you know what it could be? Looks like system + cache + device + misc together.
mmcblk0p4 - hmm... 7gb... that's interesting. Your nook shows single 6.5gb partition on PC or you have 1gb partition on PC and 5.5gb partition for nook content?
Also, how do you get such pretty output with list of partitions and sizes?
thank you, this is really helpful.
mmcblk0p3 - do you know what it could be? Looks like system + cache + device + misc together.
mmcblk0p4 - hmm... 7gb... that's interesting. Your nook shows single 6.5gb partition on PC or you have 1gb partition on PC and 5.5gb partition for nook content?
Also, how do you get such pretty output with list of partitions and sizes?
Last edited:
Renate
Recognized Contributor / Inactive Recognized Dev
That table is pretty much busybox fdisk -l /dev/block/mmcblk0
I add in the mounts from /fstab.E60QQ0 and mount.
I calculate out the byte sizes.
I should have a utility for doing that, but I seem to just knock out those tables when needed.
mmcblk0p3 is just the extended partion block.
A standard MBR can only contain 4 partitions.
Usually the 4th partition "escapes" you out to more partitions.
In our case, the 3rd partition mmcblk0p3 contains mmcblk0p5, mmcblk0p6, mmcblk0p7, mmcblk0p8.
There's no wasted space here except at the end of mmcblk04 where 16 MB is left unallocated.
This is so if they swap out the flash memory chip for another brand they won't have to redo the partitioning if the new chip has a few Megs less user space.
I add in the mounts from /fstab.E60QQ0 and mount.
I calculate out the byte sizes.
I should have a utility for doing that, but I seem to just knock out those tables when needed.
mmcblk0p3 is just the extended partion block.
A standard MBR can only contain 4 partitions.
Usually the 4th partition "escapes" you out to more partitions.
In our case, the 3rd partition mmcblk0p3 contains mmcblk0p5, mmcblk0p6, mmcblk0p7, mmcblk0p8.
There's no wasted space here except at the end of mmcblk04 where 16 MB is left unallocated.
This is so if they swap out the flash memory chip for another brand they won't have to redo the partitioning if the new chip has a few Megs less user space.
Here's a test TWRP build for GL3: https://nofile.io/f/EPqMcW4DSYG/twrp_bnrv520.img
I do not have device to test, so I would be grateful if anyone would like to test it.
warning: only for firmware 4.8 (beta).
I do not have device to test, so I would be grateful if anyone would like to test it.
warning: only for firmware 4.8 (beta).
Last edited:
Finally got my Nook Glowlight 3 and finding it impossible to get ADB authorized! Can see it in Terminal and have switched on and off debugging in Dev options but will not authorize. Any other ideas?
EDIT:
Cancel that - got it working!
Ok - best way of rooting and installing xposed?
EDIT:
Cancel that - got it working!
Ok - best way of rooting and installing xposed?
Last edited:
Should be possible with NGP Toolkit, but I've not seen any reports about how it works for GL3 (should work, theoretically).
Hi Renate NST,
Sorry for the late reply due to holidays. Been a couple of busy weeks
Nope, I did not touch the partner.apk (md5 373d15dae9f8af62d3a456a132e1d820 latest fw) AFAICT. So for now I renamed the bootanimation binary and settled for the black screen which does the trick and takes me to the ReLaunchX. I will try the partner/bnreader rename/remove later to see if this will also work. Will report back.
UPDATE: That didn't work out quite nice. Bootanimation stuck again. When I fixed it (renamed bootanimation to backup, reinstated partner/bnereader) I needed to go to the B&N registration once more. Nothing problematic though I could not fix.
I have a first gen Nook lying somewhere in the drawer and switched to Boox/Kobo/Remarkable over the last couple of years. This NG3 is something new in the house for a family member. Can I pull the NG2 fw from somewhere and do a local extract?
Thanks again,
cheers,
Martijn
Sorry for the late reply due to holidays. Been a couple of busy weeks
Nope, I did not touch the partner.apk (md5 373d15dae9f8af62d3a456a132e1d820 latest fw) AFAICT. So for now I renamed the bootanimation binary and settled for the black screen which does the trick and takes me to the ReLaunchX. I will try the partner/bnreader rename/remove later to see if this will also work. Will report back.
UPDATE: That didn't work out quite nice. Bootanimation stuck again. When I fixed it (renamed bootanimation to backup, reinstated partner/bnereader) I needed to go to the B&N registration once more. Nothing problematic though I could not fix.
I have a first gen Nook lying somewhere in the drawer and switched to Boox/Kobo/Remarkable over the last couple of years. This NG3 is something new in the house for a family member. Can I pull the NG2 fw from somewhere and do a local extract?
Thanks again,
cheers,
Martijn
Last edited:
Bootanimation from fw 4.6 (with service.bootanim.exit): https://1drv.ms/u/s!AlBgZahcgzeIkFz6H7dLRrhlP_nt
Whoa, an upgraded Simple Touch! Sign me up!
I liked the waterproofing and software of the NGP, but it just never felt quite as good as the NST. How does this compare, a few months after release?
I liked the waterproofing and software of the NGP, but it just never felt quite as good as the NST. How does this compare, a few months after release?
I just got mine for Christmas, having skipped the NGP, and it's very close to my Simple Touch in usability and controls. Lighter and smaller, so even easier to hold, but not so much lighter and smaller that it feels flimsy or has lost any functionality. I LOVE the new lighting system. I thought I liked the original light alot until I was able to adjust the light temperature, now I discover that I was wrong all along, and the original system was totally inferior. 
I still have an issue with having to come to places like this to figure out how to customize it, I prefer a more configurable reader like CoolReader than the built in B&N one, but on the other hand, it works nicely until I get motivated to actually sideload apps like that. My only issue is that they took away the 'Sleep' button from the top back. I like to put the thing to sleep manually before I stuff it in a bag, or when getting harassed by some flight attendant on a plane, and I haven't figured out how to do that yet.
But overall, I love it. Still not wanting to switch to a Kindle, the Nook still delivers. Simple, and perfect for what it's made for; reading.
I still have an issue with having to come to places like this to figure out how to customize it, I prefer a more configurable reader like CoolReader than the built in B&N one, but on the other hand, it works nicely until I get motivated to actually sideload apps like that. My only issue is that they took away the 'Sleep' button from the top back. I like to put the thing to sleep manually before I stuff it in a bag, or when getting harassed by some flight attendant on a plane, and I haven't figured out how to do that yet.
But overall, I love it. Still not wanting to switch to a Kindle, the Nook still delivers. Simple, and perfect for what it's made for; reading.
I had previously installed nova launcher and calibre companion (cc) and after getting this update and rebooting it wouldn't get past the loading screen (loading bar animation would continue to move). Used adb to reboot into recovery and went through reset process.
Enabled debugging mode, installed nova and cc, and after rebooting had same problem. Booted to recovery and reset again.
Tried installing just cc this time and had no issues after rebooting. Tried installing nova launcher and back to it not loading after reboot. Uninstall nova launcher via adb and it would load after reboot.
Tried with a different launcher (relaunchx) and had the same issue.
Anyone else having issues loading after a reboot with a launcher installed?
Thanks, that fixed it! Skimmed through those comments wondering why people were so interested in getting a new boot animation on an e-ink device
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
5
Did you delete/rename /system/priv-app/partner.apk?
B&N put its hooks in everywhere.
The bootanimation will not go away without partner.apk unless you do something.
On my Glow2 I just renamed partner.apk and bnereader.apk to backup files.
That does the startup correctly.
The Glow 3 modified /system/bin/bootanimation to use bn.bootanim.exit instead of service.bootanim.exit
You can take bootanimation out of a Glow2 or just delete/rename bootanimation.
You will then get a black screen until your home/launcher starts.3
Glow 3 is a BNRV520, not a BNRV510.
Change line #9 in the script.
Unrelated to your problem, but as info VID 2080, PID 000B.3Code:Disk /dev/block/mmcblk0: 7818 MB, 7818182656 bytes 4 heads, 16 sectors/track, 238592 cylinders Units = cylinders of 64 * 512 = 32768 bytes Partition Format Id Start End Size (bytes) Mount --------- ------ -- ----- ------ ------------- --------- mmcblk0 1 238592 7,818,182,656 mmcblk0p1 emmc 83 33 223 6,258,688 /boot mmcblk0p2 emmc 83 609 1632 33,554,432 /recovery mmcblk0p3 5 1633 26720 822,083,584 mmcblk0p4 ext4 83 26720 238080 6,925,877,248 /data mmcblk0p5 ext4 83 1665 13952 402,653,184 /system mmcblk0p6 ext4 83 13984 26272 402,685,952 /cache mmcblk0p7 ext4 83 26304 26560 8,421,376 /device mmcblk0p8 emmc 83 26592 26719 4,194,304 /misc3
Of course!
It pops easily. Use a thin knifeblade to get it started then work a guitar pick around.
The TTY is easy and obvious, 3.3V, 115200 8N1.
Code:root@ntx_6sl:/ #3That table is pretty much busybox fdisk -l /dev/block/mmcblk0
I add in the mounts from /fstab.E60QQ0 and mount.
I calculate out the byte sizes.
I should have a utility for doing that, but I seem to just knock out those tables when needed.
mmcblk0p3 is just the extended partion block.
A standard MBR can only contain 4 partitions.
Usually the 4th partition "escapes" you out to more partitions.
In our case, the 3rd partition mmcblk0p3 contains mmcblk0p5, mmcblk0p6, mmcblk0p7, mmcblk0p8.
There's no wasted space here except at the end of mmcblk04 where 16 MB is left unallocated.
This is so if they swap out the flash memory chip for another brand they won't have to redo the partitioning if the new chip has a few Megs less user space.
