[Q] How to change Boot/Power Off screen for NSTG with firmware 1.2.1 ? - Nook Touch General

How do you change the Boot/Power Off screen for a NSTG (Nook Simple Touch Glowlight) with firmware 1.2.1 ?
It's rooted etc, and I've read existing threads about doing this, but they relate to earlier firmware versions.
e.g.
This one is for firmware up to 1.0.1, so I'm reluctant to try the old replacement .jar file .
and this one, although simpler, does not seem to work as I could not find the appropriate image in the framework-res.apk file
TIA!

antboy9 said:
How do you change the Boot/Power Off screen for a NSTG (Nook Simple Touch Glowlight) with firmware 1.2.1 ?
It's rooted etc, and I've read existing threads about doing this, but they relate to earlier firmware versions.
e.g.
This one is for firmware up to 1.0.1, so I'm reluctant to try the old replacement .jar file .
and this one, although simpler, does not seem to work as I could not find the appropriate image in the framework-res.apk file
TIA!
Click to expand...
Click to collapse
It's actually very easy - no modified .jars or anything are necessary. Here's a quick key:
• The "Your Nook is completely off" images are located in /system/assets/shutdown_images. They are all easily edited .png files which can be copied and replaced at will. :good:
• The "black/white dots" animation images are located in /system/assets/boot_images, and they are also easily edited .png files which can be copied and replaced at will.
• The "Read Forever" screen is a bit harder - it is located in /boot (accessible via mounting or via booting Noogie) and is named booting.pgm. It is a .pgm file, which is only editable by converting it to .png and then converting it back when the editing is complete.
Hope this helps you out, and be sure to post again if you have any more questions!

ИΘΘK¡€ said:
• The "Your Nook is completely off" images are located in /system/assets/shutdown_images. They are all easily edited .png files which can be copied and replaced at will.
Click to expand...
Click to collapse
Thanks a lot, yes it was easy, at least it was easy using adb.
In case others find it useful:
adb connect <ip address>:5555
adb pull /system/assets/shutdown_images/cold_boot_screen.png
___
backup that file from the directory and put the new one in its place, locally
___
adb shell
mount -o remount,rw -t ext2 /dev/block/mmcblk0p5 /system
exit
adb push cold_boot_screen.png /system/assets/shutdown_images
adb reboot

antboy9 said:
Thanks a lot, yes it was easy, at least it was easy using adb.
In case others find it useful:
adb connect <ip address>:5555
adb pull /system/assets/shutdown_images/cold_boot_screen.png
___
backup that file from the directory and put the new one in its place, locally
___
adb shell
mount -o remount,rw -t ext2 /dev/block/mmcblk0p5 /system
exit
adb push cold_boot_screen.png /system/assets/shutdown_images
adb reboot
Click to expand...
Click to collapse
Another way to do it (the way I normally do it) is to use SwiFTP, which is an FTP server which is hosted on your Nook that is accessible from the PC. You don't even have to push/pull anything; you can just copy the image file you want to edit to your hard drive from the server, edit it, and then just paste it right back into the server. It works perfectly.
Post again to let me know if you'd like the .apk for the FTP server app!

ИΘΘK¡€ said:
Another way to do it (the way I normally do it) is to use SwiFTP, which is an FTP server which is hosted on your Nook that is accessible from the PC. You don't even have to push/pull anything; you can just copy the image file you want to edit to your hard drive from the server, edit it, and then just paste it right back into the server. It works perfectly.
Post again to let me know if you'd like the .apk for the FTP server app!
Click to expand...
Click to collapse
Hi, thanks. Yes I would like the .apk for the FTP server app.
Does it get around the read-only issue?

antboy9 said:
Hi, thanks. Yes I would like the .apk for the FTP server app.
Does it get around the read-only issue?
Click to expand...
Click to collapse
Here it is.
And yes, it does get around the read-only issue. However, you do have to change the directory in [FTP server app]/Advanced Settings.../Stay in folder (which is originally /sdcard) to /, or else you will get a "Permission denied" on the PC.
Enjoy! :good:

There are any number of graphic programs that can convert to/from the PGM graphic file format used in the boot partition.
There is also my Windows command line utility nookbits.exe available in the signature.

Related

Android img files

Okay I know this is a very noob question, how do I open android .img files And I have run a number of different search queries and still haven't found the answer.
jimmydafish said:
Okay I know this is a very noob question, how do I open android .img files And I have run a number of different search queries and still haven't found the answer.
Click to expand...
Click to collapse
what do you want to do with the img? dump it or just flash it?
if you got some kind of linux distro installed, just go (in terminal) to the dir where the image file is located, and type "file filename.img" if it returns something like ext2 filesystem, simply do:
mount -o loop filename.img /mnt
and the file will be mounted on /mnt, so you can access it using cd /mnt
if it returns something like VMS Alpha executable, you will have to download unyaffs, and if you want to repackage it later on, mkfs.yaffs2,
to get the file's content, just run unyaffs filename.img, and you will have the file content right in the folder with the img file...
if you don't have a linux distro installed, you can simply get virtualbox, and download the latest ubuntu iso file... mount the file in virtualbox and install ubuntu (it's quite easy)...
oh and incase you need them some basic commands:
Code:
ls - lists current folder content
cd folder - allows you to switch to a specific folder, like if you type ls, and you get the folder android listed just type cd android... if you want to go back to your home folder, type ~/...
sudo command - allows you to run specific commands as superuser (root... you can also just switch to user root by typing sudo su, so you won't need sudo every single time)
rm file / rm -R folder/file - allows you to remove files and with the parameter -R also folders ;)
hope this helped
emulator
What if i want to use the .imgs in the emulator/AVD? Any tips?
Thanks.
tdh_andy said:
What if i want to use the .imgs in the emulator/AVD? Any tips?
Thanks.
Click to expand...
Click to collapse
use mkfs.yaffs2.

Guide to install LXDE on samsung galaxy s

So 3 days of trying to install ubuntu on chroot and a little knowledge of linux and terminal, i was rather surprised to log into it and there i was, faced with an LXDE interface.
I want to thank coralic, burningbroccoli, lifehacker, josh_axeY and backfireNL for supplying the information i needed to make this possible.
So a brief overview of whats going to be done. First we will need to root our galaxy s in order to access terminal. An ubuntu image will be created and used in chroot environment by mounting (loading) it. Finally a vnc server will be setup and will be logged in using androidVNC.
So for the guide i suppose!
Guide:
First your going to need to root your phone. This is to access terminal and enter the commands required. This is taken from backfireNl's easy way to root your phone.
1. Download: 2.1 Update .zip
2. Put update.zip to root of /sdcard (not /sdcard/sd) (not on the physical SD card but the Internal SD card/Phone Memory)
3. Turn off phone
4. Hold down volume up + home button + power (tip: release the power button for half a second when you see the samsung logo)
5. Phone will reboot into recovery mode
6. Wait until you see the Recovery Screen and then release the buttons
7. With the volume down key go to the option: "apply: /sdcard/update.zip"
8. Press the home button
9. Phone will start updating
10. Phone reboots... and there you go! your phone is rooted!
So that wasnt too hard was it? Although once you have done this, you will need to download a couple of programs from the market. Goto market and download the following programs:
-Busybox
-Terminal Emulator
-androidVNC
Ensure all of these are installed as this is what you shall need in order to successfully run LXDE on your phone.
Next is the image for the install! i will post up an image file for download although for the sake of people wanting the whole info on how-to here it is.
1) login on your ubuntu machine and fire up terminal.
2) login as the super user by entering "sudo su"
3) you will be required to enter your su password, enter this and you will be logged in as root
4) In terminal enter "apt-get install rootstock"
5) One this package is all installed, enter the following code into the computer terminal:
sudo rootstock -f localhost --login ubuntu --password ubuntu --imagesize 1G --notarball --dist lucid --seed ssh,tightvncserver,lxde,expect
6)The image will be stored in the home folder. The image will need to be a .img file or it wont work. So extract the file if necessesary and rename the file so it reads "ubuntu.img"
7)Now you will need to put the ubuntu.img on the phone. The directory which it needs to be installed into is "/sdcard/ubuntu/"
8) All done for this step!
Ok so you have everything setup and ready to do the fun part! so lets get everything mounted and configured!
1)Open up terminal emulator on your phone
2)enter "su". this logs you in as superuser
3)I found you will need to make the following directories in order to work, so in terminal emulator enter:
mkdir /data/local/mnt
mkdir /data/local/mnt/proc
mkdir /data/local/mnt/dev
mkdir /data/local/mnt/dev/pts
4)enter "cd sdcard" then "cd ubuntu"
5)You will then be in the folder with the image. Type into terminal:
export HOME=/root
export USER=root
export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
busybox mount -t ext3 ubuntu.img /data/local/mnt
busybox mount -t proc proc /data/local/mnt/proc
busybox mount -t devpts devpts /data/local/mnt/dev/pts
busybox chroot /data/local/mnt /bin/bash
/etc/init.d/ssh start
6) Although it doesnt seem it, your now into your distro!
Okay so your into your distro but it looks all horrid and "text based". wouldnt it be lovely to see a proper desktop? so lets go!
1) enter into terminal "apt-get install x11vnc" this installs x11vnc to your phone. This may take a while depending on how your connected to the net
2) once x11vnc is installed, type "x11vnc -storepasswd" and enter a password. It will ask to verify the password so enter it again, then enter "y" to setup a password for it
3) first enter "vncserver" to initiate the server on your distro. For some reason without this, androidVNC will start to connect then crash
4)finally enter "x11vnc -usepw -find"
now your x11vnc is setup using a password hooray! last step in this guide and you will be away in no time! So is everyone ready?
1)hit the button on the bottom to return to the desktop but keep terminal emulator running
2)goto androidVNC and enter the following:
Nickname: root
Password: (whatever password you setup in x11vnc)
address: localhost
Port: 5900
color format can be anything, i set it to 4 bpp and use local mouse pointer
3)Simply click "connect" and viola! welcome to your impressive lxde environment!
This has been done before although i tried to do every step, base it around the phone as much as possible so no connecting to the computer.
any questions or problems i will try my best to help you guys, and thanks for the guys who helped me on this voyage.
i will write a bash script soon to try and incorporate as much of the manual typing in as possible
good luck!
Things which need to be done:
Upload image: Completed! - http://www.megaupload.com/?d=H55O5UEM
Bash script for terminal emulator: Completed, needs to be uploaded
Bash script for setup process of terminal emulator: Not completed
Startup script for image: Not completed
Youtube video: Not completed
Include internet browser and x11vnc in image file: Not completed
If anyone has any recommendations on how to make the process easier please let me know and i will try my best
Good to see the info consolidated into one post!
Cheers for the shoutout.
no probs your information helped me soo much, i just thought it would be good for someone to goto a post and go "oh yeah thats how to do it" instead of going to loadsa websites
i will try it very soon, thank you.
awesome!
When will you post your img file? I'll have a try.
I have no ubuntu installed, I'm using ArchLinux.
okay ive written a bash script to automate most of the process although there are a few things i could tweak before im fully happy
i have also posted a youtube video to demonstrate how easy it is! the first post will be updated with the link.
people ask me the reason for doing this and i have 2 replies:
1)to show the true potential of this phone (and working in a phone shop it really works)
2)for development purposes. Things like this are the next step in unlocking the true potential of the phone
lijgame: Im just uploading it now for you
Good work, will give it a try. And what about any browser ? Like firefox ?
hi.
okay so this is installing ubuntu into a chrooted environment and vnc'ing to it.
does anyone know if it is possible to blow away android and install pure debian on it? does anyone know of a hardware list on the sbc in this thing and what sort of support one might need to hack in to get a such a thing to work?
I will apologise now for the delay in image upload, the image file is 1gb and im having trouble finding a place to upload it.
In terms of installing a clean debian would need more than just a straightforward port. You would be looking at making an environment which supports the arm architecture, porting all of the drivers over, creating an option to support telephony, messages and gps too. If you wanted a debian environment it would probably be best to either run it like how the n900 does or getting a distro of it which is specifically made towards mobiles and modifying it.
Although you have an extremely good point there! Tell you what, once ive got everything running on here i will have a look and see what i can do in terms of atleast getting a debian shell running or a limo version
.kiz said:
I will apologise now for the delay in image upload, the image file is 1gb and im having trouble finding a place to upload it.
Click to expand...
Click to collapse
Just create zip/tar-ball of img file and it will become around 300MB. Then you can upload it on multiupload (or megaupload/rapidshare/mediafire).
I just created that image too and will be testing on my Galaxy S soon, so if its working for me then I will upload my image too.
Thanks for your good work
haha i shouldve really thought about compressing the file really
this will be a pre-image im just working on getting a better image with optimization, x11vnc and firefox
okay guys the first post is edited with the image for the install.
http://www.megaupload.com/?d=H55O5UEM
I am currently in the process of playing about with images to include everything you need, so soon enough i will have an image with everything you need to get started
Tnx for the credit!
Ubuntu image is uploaded and ready to go, im currently working on a better image so when ive finished that, it shall be released.
Also i have recently installed an internet browser and it is functioning properly. I will post screenshots soon
.kiz said:
okay guys the first post is edited with the image for the install.
http://www.megaupload.com/?d=H55O5UEM
I am currently in the process of playing about with images to include everything you need, so soon enough i will have an image with everything you need to get started
Click to expand...
Click to collapse
The image is only 11MB and is corrupted
Moreover, I tried to mount my ubuntu.img to /data/local/mnt but it is giving error (sort of -> loop back device can't be mounted: No such file or directory) although I created and checked /data/local/mnt directory which exists
Try creating a second loop device with: mknod /dev/loop2 b 7 0
fslateef said:
The image is only 11MB and is corrupted
Moreover, I tried to mount my ubuntu.img to /data/local/mnt but it is giving error (sort of -> loop back device can't be mounted: No such file or directory) although I created and checked /data/local/mnt directory which exists
Click to expand...
Click to collapse
im guessing because the image is corrupt, your unable to mount it.
I have just uploaded my bash script making it easier to mount each time.
bash script: http://www.megaupload.com/?d=CEU6R5J4
Image file: http://www.megaupload.com/?d=H55O5UEM
ensure you have made the directories explained in my first post.
pop the hsetup.sh file inside /sdcard/ubuntu (along with your image)
then fire up terminal emulator and type:
su
cd sdcard
cd ubuntu
sh hsetup.sh
This mounts everything for you and logs you into LXDE, all you need to do after is type in:
/etc/init.d/ssh start
vncserver
x11vnc -find
Then log in using androidVNC
i will attempt to upload the file to another location and i will test the image file to ensure its not a compression error
i apologise, ive just looked at the zip file and it is corrupt.
just compressing a new one and i will upload it
.kiz said:
im guessing because the image is corrupt, your unable to mount it.
Click to expand...
Click to collapse
Nops, I am using my own created ubuntu.img file according to your command which is 1GB in size .....
fslateef said:
Nops, I am using my own created ubuntu.img file according to your command which is 1GB in size .....
Click to expand...
Click to collapse
I found the problem. As mentioned by ArminC, I found that there isn't any loop device node in my mobile hence I created one and its mounted
Great ... Now going ahead .....

[Q] Honeycomb Keyboard

I'm kinda new to android
I've started to delete useless apps through Titanium Backup(acer staff,games etc) , and exidently deleted smth connected with honeycomb stock keyboard.
Now every time when i want to use stock keyboard, pops up a messege "The application Android keyboard (process com.google.android.inputmethod.latin) has stopped unexpectedly. plz try again".
Ive tryied to reset factory data but it wont helped. Is thera any solution for this problem? if there no, plz tell how to completely reset tablet) ive read "system Images " thread but i didn understand some things
here is my recover steps: (for a500 which is bricked)
for a500 is normal:
root it
put the system.img into a500
connect to the computer with adb and follow the codes:
su
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
then reboot
Click to expand...
Click to collapse
connect to the computer with adb and follow the codes:
su
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
what that means)
You might very well have ruined your tablet.
I'm not a developer or coder so I can't make any sense of the code you posted but if a reset didn't fix it then you've certainly deleted something important. Hopefully someone has some ideas.
If not, then maybe you can return it? And next time, don't delete something unless you know what it is you're deleting.
ok ive recovered from image, but now wifi is not working , what should i do?
There are posts about having to change file permissions to fix wifi. Search this forum, there are a few.
edit - linked post
http://forum.xda-developers.com/showthread.php?t=1074449&highlight=wifi+permission
yeah ive read this but i dont know how to move that files to system folder on devide, wifi is down , so i cant download any file managing apps from market and theres no any file managers on stock Rom
If you've got the adb working, you can use the command mv to move the file.
I'm not sure of the exact path involved, but for example. the file is in /mnt/sdcard/filetobemoved and needs to go into /sytem/lib/modules
mv /mnt/sdcard/filetobemoved /system/lib/modules
That'd put it in the location you need. To change the permissions, you'd use the command chmod
chmod 655 /system/lib/modules/filetobemoved
The 655 is an octal(0-7) representation of the file's permissions. I'm not sure what permissions it needs, but you could try 655 as a start unless someone else knows for sure.
if you want, hit me up on msn, I can try to walk you through it: [email protected]
Glebaka said:
ok ive recovered from image, but now wifi is not working , what should i do?
Click to expand...
Click to collapse
Ah *phew* Good to hear.
gammaRascal said:
Ah *phew* Good to hear.
Click to expand...
Click to collapse
lol How'd he get in that shape to begin with? Any idea what exactly it was he deleted that bonked his system?
muqali said:
lol How'd he get in that shape to begin with? Any idea what exactly it was he deleted that bonked his system?
Click to expand...
Click to collapse
No clue. I really should start reading up on HC app development and at least familiarize myself with that environment.
I haven't rooted yet cause I'm e'scarded to.
ahh i cant replace that files , somehow installed astro manager(through docsttogo) but i cant remove/replace/rename that files in system/lib/modules it says i dont have permission to do this.
tryed in connectbot type "mv /mnt/sdcard/filetobemoved /system/lib/modules"
got this "failed on '/system/lib/modules/filename' - cross-device link"
im rooted what if
Glebaka said:
ahh i cant replace that files , somehow installed astro manager(through docsttogo) but i cant remove/replace/rename that files in system/lib/modules i dont have permission to do this.
tried connectbot tryied "mv /mnt/sdcard/filetobemoved /system/lib/modules"
got this "failed on '/system/lib/modules/filename' - cross-device link"
im rooted
Click to expand...
Click to collapse
type mount and paste/retype the line that has /system in it. It might be mounted read only.
or try the cp command in place of mv
edit - also, the filetobemoved is just an example. I think one of the filenames is bcm4329.ko but I'm not sure. so /system/lib/modules/bcm4329.ko would be the full path
ah im total noob tried cp instead of mv it said permission denied .
t
ype mount and paste/retype the line that has /system in it. It might be mounted read only.
Click to expand...
Click to collapse
i didnt get that (
edit - also, the filetobemoved is just an example. I think one of the filenames is bcm4329.ko but I'm not sure. so /system/lib/modules/bcm4329.ko would be the full path
Click to expand...
Click to collapse
yeah thats i know)
Are you logged into the tablet using adb's shell? I've only used that once on a different tablet, but iirc the commands are standard Unix/Linux commands. Someone correct me if I'm wrong but aren't you already logged in as superuser like this? You don't need to 'sudo' or 'su' to switch over do you?
I'm not familiar enough with this specific environment to figure out what might be keeping you from placing those files in that location. The command to check the partitions mount options is
mount
It should return a bunch of text, one line of which is gonna be the /system partition. If it's ro(read only) then you can't write to it and would need to remount it.
yeah it looks like it is "ro"
ive got /system ext4 ro
how to remount)
My knowledge of adb is limited as well. All I know is that I can connect to it, type: adb devices (in the command prompt) to make sure it sees my tab then 'adb push filename.extension /directory/structure' to force files... Conversly, I think adb pull filename.extension /directory/structure will grab files on the tab if you know what they are called and where they are located.
Glebaka said:
yeah it looks like it is "ro"
ive got /system ext4 ro
how to remount)
Click to expand...
Click to collapse
what was the /dev/block/mtdblock for /system?
there is a number after it...for example /dev/block/mtdblock1
mount -o rw,remount -t ext4 /dev/block/mtdblock1 /system
would remount it read/write, provided that it is mtdblock1, change the number depending on what your device has.
yeah now /system have "rw", but it anyway refuses to copy using mv(failed on '/system/lib/modules/filename' - cross-device link"
) or astro manager
Glebaka said:
yeah now /system have "rw", but it anyway refuses to copy using mv(failed on '/system/lib/modules/filename' - cross-device link"
) or astro manager
Click to expand...
Click to collapse
If cp won't put it there either, I'm out of ideas. Maybe ask in the other thread how they were able to copy/move the file and set the permissions?
I know it may not be really classy, but how about downloading an .apk That will let you mount the drive, to an sd card in a computer then transfer that to the Acer. (If it's an extreme case and nothing else will work..not condoning piracy, but don't know what would work...)
or is it possible to copy the system data from a Titanium backup and send it over so he can restore the missing files?
This following step I can't be responsible for it's safety. It looks safe to my eyes, but proceed having been forewarned. I did some research and you might be able to use dd to get the file there.
dd if=/mnt/sdcard/filname of=/system/lib/modules/filename

How to get your Nook to work with a USB keyboard...

Theres a great article here about how to get your Nook Simple Touch working with a USB keyboard:
http://lararthompson.wordpress.com/2013/03/19/e-ink-writing-101/
It's windows based of course but I've worked out how to get it all going using Linux via Nook Manager.
Heres what to do for Linux:
I'm assuming you already rooted your nook using Nook Manager too if not you need to start with that.
Start up Nook Manager and start the ssh.
This will give you an ip address.
From your main computer type:
Sudo ssh [the ip address that Nook Manager gave you]
You will need to give a password for the sudo on your computer and then you will need to give the password for the Nook which in this case is root.
Now type:
mount -t vfat /dev/block/mmcblk0p1 /boot
which is the magic. To check it worked:
cd /boot
ls
which should show a bunch of files including uImage.
Next you need to copy what are basically the kernel and root images to the nook.
These are the files uImage and uRamdisk that are in the zip file:
http://forum.xda-developers.com/attachment.php?attachmentid=866780&d=1327194445
You need to unzip this and get the files out of there.
Now type
exit
into the ssh session.
We now use secure copy to get the files across:
sudo scp /home/freya/Downloads/TouchK/uImage [email protected]:/boot
sudo scp /home/freya/Downloads/TouchK/uRamdisk [email protected]:/boot
obviously the ip address needs to be the one that Nook Touch Manager gave you and not the daft one I just made up!
You also probably wont have a home folder called freya etc. This obviously need to point to where you unzipped those files.
I'm hoping you can work out what I mean here.
Anyway the 2 files should copy over and then you can go to Nook Manager and restart the Nook.
It should now be using the new kernel and you then just need to install the usb .apk etc as in the other article but you are already most of the way there.
Hope this helps other people, it's taken me a few weeks to assemble all the info to get this working, but now it works great. Oh and I'm using the latest nook 1.2.1 or whatever it is and it works great for me, so it might be a bit of a myth about needing an early version of the firmware.
Freya
Also wanted to add a HUGE thankyou to Jeff who created the Nook Manager (which actually works and makes everything soooo much easier) but also I want to thank him for coming to my rescue, and saving me even more weeks of banging my head against a wall.
Thanks Jeff!

How to Root and set up a new Nook Glowlight 3

I got tired of having to jump between a bunch of threads when setting up my Glowlight 3. So I'm consolidating directions into one post in the hopes that it'll save others time and trouble. Credit for instructions should go to the people who actually wrote them: arnchav of mobileread; RyogoNA, Silent eInk, cazar and Renate NST here on xda; and everyone who figured out the root exploit, sideloading, the devs behind Relaunch, RelaunchX and F-Droid. Material lifted from their original posts (linked at the bottom).
Now, this is going to walk you through doing a few things:
A) Setting up a progam called ADB on your computer so that it can talk to your NG3
B) Adding a "Launcher" app to your nook so that you can access other apps you sideload later
C) Root theNook so that you can do more stuff with the settings, including the ability to...
D) Fix a bug that, after installing a launcher, causes the NG3 to get stuck on the loading screen after rebooting
Before you start, you need to set up ADB on your computer. Follow the instructions linked here. The rest of this post will assume you're using Windows, but won't be hugely different from other OSs.
Here we go:
To set up ADB on your nook:
1. On your Nook, go to Settings>About. You should see the serial number, app version, etc. At the top of that page, there is a nook icon. Tap that icon rapidly until the developer menu opens.
2. Tap "Android Development Settings" and check the box for "USB debugging".
3. At the Developer options screen you are on (where you checked the box), hit the back arrow at the top-left of the screen to go back. But do not exit the developer menu.
4. On your computer, open a command prompt and navigate to the folder where you put adb (in my case I typed in "cd adb/platform-tools")
5. Plug the USB in to the nook. When the nook prompts you to turn on USB mode, do so. At the adb command prompt, type adb devices. ADB should recognize the nook, but say that it is unauthorized.
6. From windows, eject the nook to disconnect nook's file sharing. Once the nook's USB file sharing screen goes away, you should be able to see the developer menu again. Tap "Allow Debugging" one time! There will be no confirmation, just do it one time.
6. Unplug the USB, plug it back in, turn on USB mode when prompted. Back in the command prompt, type adb devices again. This time it should see the device and simply say "device" where it used to say "unauthorized". Congratulations! You can now install a launcher.
To install a launcher, like RelaunchX
1. Download your launcher apk of choice. If you don't know what to pick, try RelaunchX, and download the latest version from plusz's thread here: https://www.mobileread.com/forums/showthread.php?t=284418 (n.b. To make things easy, ignore his suggestion to get it through F-Droid as you'll need a new launcher to use F-Droid in the first place. Just download the apk).
2. In Command prompt, type adb install <filelocation>, where filelocation is the complete address of the apk. If you have file explorer open, you can just type adb install then a space, then drag the file in to the terminal and it will copy the location for you. (Make sure again that there is a space between "install" and the path or it won't work).
3. ADB should do it's thing and you will get a "success" message in Terminal.
4. Eject the nook from the PC. Shortly after the connection is cut, a window should open on the nook allowing you to select either the nook launcher or your new launcher. If you use RelaunchX, you may get a warning that it wasn't built with this device in mind. You can ignore it, it works great on this device.
This is all great, except there's a bug in how B&N set up the device that only shows up if you install a new launcher. If you reboot the device, you'll be stuck on the boot animation until you do weird things like hold down the power button for a long time to pull up the reboot/power off options (only seems to sometimes work). To fix that, we actually have to disable, remove, or replace the boot animation file itself.
To root:
1. Download the modified Glowlight Plus script attached here ("rootGL3.zip" - almost identical to cazar's rooGLP-3 script package, but with one line changing the model number from 510 to 520)
1. Enable USB debugging in Developer options
2. Connect USB cable and make sure your nook is showing up in 'adb devices'
3. Extract rootGLP.zip and run rootnook.cmd (or rootnook.sh on linux)
To fix (read: disable) the buggy boot animation:
1. Connect your nook to the computer again
2. (windows) open a command prompt and and navigate to the folder that adb is in.
3. Enter the following commands, in order:
Code:
adb shell
su
mount -o remount, rw /system
mv /system/bin/bootanimation /system/bin/bootanimation.bak
reboot
OPTIONAL: To restore a working boot animation (steps above will replace broken boot animation with a black screen that goes away after a few seconds)
1. Download the attached zip
2. If it's not still connected, connect the Nook to the computer again and tap the button on the nook to turn on USB mode when prompted,
3. On your computer, open up the Nook in Explorer(/Finder/your file manager of choice). Open up the NOOK Folder if you see one.
4. Copy the file inside the zip (bootanimation) to that folder on the Nook.
5. Eject the nook (as in, in windows, click the option to safely remove it as a device) but keep it physically connected
6. Open a command prompt(/terminal/whatever you use for adb) and navigate to the folder that adb is in.
7. Enter the following commands:
Code:
adb shell
su
mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system
cp /storage/spsd/NOOK/bootanimation /system/bin/bootanimation
cd /system/bin
chmod 755 bootanimation
reboot
You now have a rooted Nook Glowlight 3 that'll boot into a launcher of your choice! You can now sideload apks of your choice using adb the same way you installed RelaunchX.
Have fun!
Sources for these instructions:
https://www.mobileread.com/forums/showpost.php?p=3632665&postcount=118 (how to sideload onto nook 3)
https://forum.xda-developers.com/showpost.php?p=75717722&postcount=113 (same as above, diff user)
https://www.mobileread.com/forums/showthread.php?p=3632665#post3632665 (to get RelaunchX)
https://forum.xda-developers.com/showpost.php?p=64191791 (for nook GLP rooting script)
https://forum.xda-developers.com/showpost.php?p=76042888&postcount=127 (to fix boot animation loop)
HELP! I DID THIS A LONG TIME AGO AND NOW MY NOOK GLOWLIGHT 3 IS STUCK ON THE LOADING SCREEN!
Don't worry, this is fixable. What's happened is that Barnes and Noble pushed out a system update that undid almost everything except that part that breaks the boot animation thing (specifically it overwrites the directory with everything that gives you root access and a working boot animation, but left your custom launcher in place).
All you have to do is re-do most of the steps above. Start from the "to root" step - even if the device is stuck on a boot animation, you should still be able to use adb. After redoing the steps, your GL3 should work normally again.
Unfortunately it looks like this is going to happen every time B&N pushes a system update, but that's not that often.
If someone knows a step-by-step way to replace the stock bootanimation with the 4.6 bootanimation file (zipped up and attached here, thanks to RyogoNA), let me know and I'll update the OP. I tried used adb shell to copy it to /system/bin/bootanimation, but I still just get a black screen on startup in its place.
jptiger said:
I still just get a black screen...
Click to expand...
Click to collapse
Mmm, did the copy of bootanimation work?
Did you:
Code:
/system/bin # chmod 755 bootanimation
Tried that, but I got an error about a Read-only file system, even after using su. What's the basic thing I'm missing?
jptiger said:
Tried that, but I got an error about a Read-only file system, even after using su. What's the basic thing I'm missing?
Click to expand...
Click to collapse
Got a private message pointing me to the command I was missing, apparently from a how-to page in Russian. For anyone else trying to do this, try:
Code:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system
cd /system/bin
chmod 755 bootanimation
Can't get adb devices to give autorhized access to ng3 w 4.9.2.24 os
First off thank you for doing this work, and I am excited to root my ng3!
In trying to follow your directions on rooting, I am hitting a snag. The os is not operating in the anticipated manner. When I do the usb unplug and replug and hit the usb debugging checkbox I can not get authorization.
Please help!
Thanks in advance!
Trouble with root
Hi,
Thanks for putting this all together. However, I'm having trouble with the root step.
You'll have to put the link together because as a new poster I can't post links.
Any help would be appreciated!
imgur . com
/a
/ckm0jRq
xelcho said:
First off thank you for doing this work, and I am excited to root my ng3!
In trying to follow your directions on rooting, I am hitting a snag. The os is not operating in the anticipated manner. When I do the usb unplug and replug and hit the usb debugging checkbox I can not get authorization.
Please help!
Thanks in advance!
Click to expand...
Click to collapse
Hmm. Did you get authorization after following the directions under "To Set up ADB on your Nook"?
L3R0k2b2 said:
Hi,
Thanks for putting this all together. However, I'm having trouble with the root step.
You'll have to put the link together because as a new poster I can't post links.
Any help would be appreciated!
imgur . com
/a
/ckm0jRq
Click to expand...
Click to collapse
Ooh, that's exotic. I've never seen that before. Just going off the error text, you might need to find a newer version of adb somewhere online. Try that or try a different computer?
Adb is super stable for many years now, although it can fail to connect to your device properly for many reasons.
Can you reach developer menu navigating with nooks keys? I sometimes enable /disable /enable usb Debug, followed or preceded by revoking all PC's permissions. These are all standard options in android phones s system. menus. Rebooting nook may help too, and numerous times I've seen bad cables get in my way. Tip, just because a cable works with one device is not a guarantee it's working everywhere.
RE: STEP 6. "From windows, eject the nook to disconnect nook's file sharing."
Note:
1. The location of the eject menu is where you typically see "Safely remove hardware and eject media" in the windows taskbar.
2. After attempting to eject your Nook GLP, you may get a window that pops up that says "Windows can't stop [your device]" because a process is using it -- and you may not be able to track down which process is using it (for me, closing all windows and apps didn't help). If this is the case, hit "WINDOWS+X >> Shut down or Sign Out >> Sign out" -- then log back in. This *should* stop all processes and allow you to proceed to the next step (it did for me).
*My Nook GLP recently updated and I lost root. This also caused the startup animation to continue non-stop (but holding the power button and then selecting cancel from the options allowed me to select which launcher I wanted to use).
** Additionally, I had one other issue. My (windows) laptop wouldn't recognize my nook at all. Turns out it was the USB cable. So if you have that issue, try using a different USB cable -- preferably the one that came with your nook.
Missing epubs
So I followed the instructions, everything comes up great. I can sideload apps, I have a new launcher etc. But if I copy a file (epub or otherwise) into the NOOK folder on my PC and then browse to the NOOK folder using the file manager on the Nook reader, its empty. At first I thought it was an issue with the file manager, so I installed another one. Same thing.
When I load epubs into the NOOK folder and open the B&N launcher, it sees the books and adds them to my library. But for whatever reason I can not find where the epubs are using a file manager. I even tried using grep to search for the file I copied in adb shell but it doesn't come up with anything. Anyone know whats going on and how to fix it?
Never mind its under /storage/spsd/
mount: Operation not permitted
I get this error after typing in the mount -o ... command.
Any help apprecidated!
root file missing
Hey, @jptiger In the setup instructions the rootgl3.zip file is missing a link now... Does anyone have an active link to this file, or another working root process? I couldnt find one by searching online..
Misssing files
I rebooted my nook recently and it comes back up but when I got /storage/spsd/ its empty. When I attach my nook to my pc, I can see all my books. So I did the following:
Code:
adb shell
su
busybox find / -name "*.epub"
The only files that it shows are the sample epubs that come with the Nook. I am kind of stumped as to how the files show up when I browse the nook as a usb drive. But will not show up when browsing for them via the nook itself or adb. Any thoughts?
Heretic09 said:
I rebooted my nook recently and it comes back up but when I got /storage/spsd/ its empty. When I attach my nook to my pc, I can see all my books. So I did the following:
Code:
adb shell
su
busybox find / -name "*.epub"
The only files that it shows are the sample epubs that come with the Nook. I am kind of stumped as to how the files show up when I browse the nook as a usb drive. But will not show up when browsing for them via the nook itself or adb. Any thoughts?
Click to expand...
Click to collapse
It looks like the flash memory on the Nook maybe going bad. There was a bunch of .chk files in the hidden LOST folder. Reformatting it and copying the books back to the nook seems to have fixed the problem for now. I may have to invest in the Kobo Clara HD in the future.
andjosgra said:
Hey, @jptiger In the setup instructions the rootgl3.zip file is missing a link now... Does anyone have an active link to this file, or another working root process? I couldnt find one by searching online..
Click to expand...
Click to collapse
That's weird. I don't know why they took down the original attachment. I can't find it, but I've gotten the on from the NGP+ and modified it the way they did with the originals. It's attached to this post, give it a shot.
EDIT: I uploaded the version attached here to the OP, but with the original name. The two zips have the same contents.
Heretic09 said:
So I followed the instructions, everything comes up great. I can sideload apps, I have a new launcher etc. But if I copy a file (epub or otherwise) into the NOOK folder on my PC and then browse to the NOOK folder using the file manager on the Nook reader, its empty. At first I thought it was an issue with the file manager, so I installed another one. Same thing.
When I load epubs into the NOOK folder and open the B&N launcher, it sees the books and adds them to my library. But for whatever reason I can not find where the epubs are using a file manager. I even tried using grep to search for the file I copied in adb shell but it doesn't come up with anything. Anyone know whats going on and how to fix it?
Click to expand...
Click to collapse
adb can't access NOOK storage when it's still connected to PC. Eject the device under BNRV520 (should say "NOOK: (F" or similar), but do not disconnect. Then you can find files in both adb and later NOOK's file manager when you disconnect. (should be under /storage/spsd/)
Guide is great though. Thank you all so much! Fast and easy! (unlike making a B&N account)
btw, I had to run "adb shell su" instead of 'adb shell' -> 'su' to get su priviledge, so maybe try that.
what is the adb command to manually launch relaunchx? the launcher option stopped working, and i can't get it to run at all.
Happy to report that the excellent instructions work great on the new 7.8" Glowlight Plus that got released yesterday. Change the model number to BNRV700 in the rootnook.cmd file and you're good to go!

Categories

Resources