Database Users

Problem with rooted nook touch and bn home

Ok, 1st time posting. I rooted my nook without a problem. But somehow I can't get to my bn home screen now. I probably did something stupid with settings. I used the method on this website for rooting, followed all directions. I can get to my current book by using the bookmark symbol, but can't get to the bn homescreen with my library etc, Please help!

Probably the Nook's memory is full, try to reboot it
Hi there. After rooting my second Nook (with TouchNooter, if i'm not mistaken) I also started having that kind of issues: the BN Home, Library and sometimes even the Book icons cease to respond, or do it very slowly.
I think it happens when the memory is full, and the problem disappears when I reboot it.
If you never rebooted it before: long press (for about 5 seconds) the Power button until the "Turn off Nook" dialog appears, then press "Power Off". Wait a sec, and long press the power button again until the screen goes blank and the Nook reboots.
If the dialog doesn't pop up and the device ceases to respond, don't panic; it's turned off all the same. Long press the Power button one or more times until it comes back to life.
Hope this helps, and good luck!

thispdxgirl said:
Ok, 1st time posting. I rooted my nook without a problem. But somehow I can't get to my bn home screen now. I probably did something stupid with settings. I used the method on this website for rooting, followed all directions. I can get to my current book by using the bookmark symbol, but can't get to the bn homescreen with my library etc, Please help!
Click to expand...
Click to collapse
Which method for rooting did you use?
What have you tried so far to get to your home screen?
* Have you tried the home button on Button Savior?
* Have you tried the library app in your app drawer?
What happens if you try these?
--

[Q] NST & Touchnooter install kinda sorta

Renate NST suggested I post this in this forum
To all the developers - Thanks in advance for all the GREAT work!
The Saga
Installed touchnooter-2-1-31 and NST hung on install.
Waited an hour and rebooted
NST booted to "walking dots"
Used n2T-Recovery_0.2
Went thru "start-up" dialog (register, etc) and got the machine running again.
Noticed that NST SW was at 1.0
Updated NST to 1.1.2
Installed touchnooter-2-1-31.
Boot screen was "Read Forever"
Android fired up.
Missed the select ADW - should have done that
Button Savior wanted Superuser - should have done that
Buttons on side grayed out
Used n2T-Recovery_0.2 again
did not get me to the "register" start-up dialog
Updated NST to 1.1
Installed touchnooter-2-1-31 again
Boot screen is still "Read Forever"
Same action on buttons - grayed out
So .... my take on this is given the multiple installs I have scrambled something but good.
Is there a way to get to square zero?
Will the erase and de-register do that?
Is there a way to correct the ADW / Button Savior issues?
Is there a way to get to Android despite to side buttons?
Thanks in advance for any help.
The NST works as a reader - so I'm not dead - just wounded

I think you're jumping the gun on doing recovery. When you reboot, aren't you at the ADW Launcher screen? It's been a while since I rooted my NST using TouchNooter (TN), but I believe you can launch the Superuser app after a basic TN root and change the settings for any apps you goofed on (e.g. Button Savior). Just launch Superuser, click the icon of the desired app at left, then click the little android icon at right to toggle the Status between Allowed and Denied.
Erase & Deregister Device in Settings->Device info should suffice to get you back to an unrooted state for a repeat attempt, assuming you can get to it. I've used it many times. If not, power off, then press & hold the lower left & right buttons as you power back on for a few seconds to get a factory reset option. I believe this would have helped you after that first TN hang. You could just retry after a factory reset and reboot. (Haven't had to do this myself, so not 100% sure.)
Download and install Default App Manager from the Google Market to change your default launcher so you can set it to ADW, or whatever you prefer. This works for changing defaults for any app, so is a good thing to keep around.
For the side buttons, do you mean the hard side buttons? You can change those settings with the Side buttons option in NookTouch Tools.
Also in NTT, you can change the 'n' button behavior to take you straight to your home app (ADW) if you don't like the QuickLaunch menu (I do). Be sure to check the Show extra action buttons in recent option, and you'll get Back, Home, Menu, Search and Orientation buttons (just like Button Savior) when you long-press the 'n' button, as well as your most recent apps.
As I mentioned in a separate post, I prefer to use NookTouch Tools to override the B&N QuickLaunch options to eliminate the need for Button Savior or similar apps altogether. Between a QuickLaunch option or two, and the extra options in the recent apps dialog, I've got those options covered. I did remap two of the hardware side buttons to Back and Menu just because they're handy.
I've had very good luck using TouchNooter, but you do have to read the step-by-step directions carefully. There are ways around most problems if you can get to ADW.
Good luck with it!

bobstro said:
I think you're jumping the gun on doing recovery. When you reboot, aren't you at the ADW Launcher screen? It's been a while since I rooted my NST using TouchNooter (TN), but I believe you can launch the Superuser app after a basic TN root and change the settings for any apps you goofed on (e.g. Button Savior). Just launch Superuser, click the icon of the desired app at left, then click the little android icon at right to toggle the Status between Allowed and Denied.
Click to expand...
Click to collapse
It boots to the reader ... buttons are there on the right side, but grayed out and non-functional (no superuser on button.savior)
So .. is there something I can boot from off the SD card that would allow me to
1.) Set ADW as the default, and / or
2.) Give Button.Savior the Superuser permissions?
Erase and Dereg is available as I only have access to the reader and not ADW.
Thanks for the help folks!

Were I the original poster, I would recover from my nonrooted backup image and re-root, or if I could not find it or found it but found that it was not 1.8 gig in size, would force factory reset (first, erase and deregister, then 8 failed, IIRC, to get both /system and /data wiped.)
Once I'd done a full reset, if I'd needed to do it that way, I'd boot from noogie and make my backup.
Then i'd reroot, probably using one of the Clockwork-based tools rather than the Touchnooter system, as it seems that
folks are sometimes seeing TN not quite finish (it happened to me on occasion) and the Clockwork tools seem to be
very robust, enough so that the Glownooter uses clockwork.
I actually like to really baseline something like this and be sure there's no odd cruft hanging out in /system or /data that may confuse me later.

WorkenOnIt said:
It boots to the reader ... buttons are there on the right side, but grayed out and non-functional (no superuser on button.savior)
Click to expand...
Click to collapse
You're definitely seeing some odd behavior. I always wound up at ADW on any reboot.
Erase and Dereg is available as I only have access to the reader and not ADW.
Click to expand...
Click to collapse
You should still be able to get to it via Settings->Device Info. In my experience, erase and dereg was sufficient to make another rooting attempt, but you might want to get back to ground zero. The restore option you've been using, a restore from backup as roust suggests, or doing the 8 failed boot attempts are all options. Be sure to update to whatever version of firmware you want before attempting.
Roust: After you do a CWM noot, what version does Device info show? Mine always shows 1.1.0 after TN, even though I updated to 1.1.2 previously. This has to do with some of the framework tweaking, IIRC. My TN may be old by now.

To all,
Thanks for all your help.
I did an Erase and Deregister.
That appeared to work
Checked firmware - was 1.1.0
Tried to reload TouchNooter (2-1-31)
Screen hung again - like the first time.
Waited 30 minutes and pulled the SD and rebooted.
Boot screen still says "Read Forever"
Went thru the startup dialog and selected the ADW launcher and allowed superuser on the button.savior.
I can now "complete the action" with the ADW launcher and the side keys function.
Everything appears to be working ...
Gmail gets to the account ..
Now why does it still say "Read Forever"?
Anyway - again - thanks for the help
This can be closed ... but I dont think it is "solved"

WorkenOnIt said:
[...] Screen hung again - like the first time.
Click to expand...
Click to collapse
When TN completes, you just get the black screen. This is not spelled out in step 8 of Gabrial's procedure, but it is mentioned in the on-screen instructions. Is that what you were seeing?
Boot screen still says "Read Forever"
[...] Now why does it still say "Read Forever"?
Click to expand...
Click to collapse
When I first power mine on, I get the "Read Forever" screen which is shortly followed by the rolling dots as the device boots. After a few moments, I get the slider unlock screen. Is that what you're seeing?
If so, I think that's normal.
Once you unlock, you're at the ADW screen now, right? Or at least you can get back to it in some way?

bobstro said:
When TN completes, you just get the black screen. This is not spelled out in step 8 of Gabrial's procedure, but it is mentioned in the on-screen instructions. Is that what you were seeing?
When I first power mine on, I get the "Read Forever" screen which is shortly followed by the rolling dots as the device boots. After a few moments, I get the slider unlock screen. Is that what you're seeing?
If so, I think that's normal.
Click to expand...
Click to collapse
Screen never blanked .. it did in tries #2 and #3 .. but not #1 and this last one
I thought it would say "Root Forever" ... but hey, as long as it works!
bobstro said:
Once you unlock, you're at the ADW screen now, right? Or at least you can get back to it in some way?
Click to expand...
Click to collapse
It boots to the "Home" reader .. but buttons on side (House) get me to the ADW / Reader selection

WorkenOnIt said:
[...] It boots to the "Home" reader .. but buttons on side (House) get me to the ADW / Reader selection
Click to expand...
Click to collapse
Good to hear it's working. If you don't like the side buttons that Button Savior uses, you can use Nook Touch Tools to provide a couple of alternatives.
You should also be able to change your default Home app using the technique I described above.
IIRC, the "rooted forever" screen only shows during the rooting process. I think Noogie uses that.

[Q] NST - not sure if rooted..

So I've rooted my Nook a long time ago but now had some problems with it so did a hard reset (using this method:
Code:
Turn off your N2E completely.
Turn it on again by holding down power, and then,
as soon as the screen flashes, begin holding down the bottom page turn keys on the left and right of the device until the screen flashes with a message asking if you want to do a factory reset.
Click the home key twice, and you should be on your way.
Then, since I couldn't enter the Android home screen (launcher) I tried to root it using the Lifehacker guide, but it turned out unsuccesful (when I entered the SD card, I didn't have the ROOTED FOREVER screen, just the ordinary Root Forever). I also had a B&N registration process on startup, which I gladly did. I skipped the android registration process, but didn't get the option to select the launcher. So now I'm on the usual Nook Home screen and can't change it, but when I hold the NOOK button pressed I got a message "no recent applications", which I think indicates a presence of Android? So how can I get the android launcher again? Searching for launcher does not work

The question is whether you have a launcher installed and whether it is the preferred activity.
You can try ADB and look for the launcher.
Then you can look at /data/system/packages.xml and see if you selected the stock Home.apk as your preferred-activities instead of the launcher.

Resetting the 'Home' button?

Hi again..
I seem to have set the Nook ST glowlight to go to relaunch instead of the B&N homepage . Now when I click on 'n' and 'Home', it goes to the Relauncher instead.
Is there a way to reset this so it goes to the B&N page again?

I *think* that if you just install another launcher (anything from the market) you will be presented with the possible choices again when you try to access "Home". Then you can select the default B&N Home screen and later uninstall the added launcher.

Yeah, I installed Launcher 8 recently and this didn't trigger that option again. It is there when I do some things, but I think I asked it to remember my choice for the Home button. I am used to Windows OS and when you do something like that, you can always rectify it, by using either default programs or file associations etc. Android must have something similar, no?

When you make a default choice there is a message that tells you where you can reset the option but it seems to refer to a utility that is not accessible the way the Nook is configured. Can't remember exactly what it says but I've run into the problem before and what I offered seemed to work for me. Did you reboot after installing the additional launcher? I guess the other alternative is to UNinstall all of the Android launchers you've added and reboot. Then there would be no alternative to the Nook "Home". Assuming that works you could then reinstall your launcher of choice. It's a pain, I know. I've "rebuilt" my Nook many times while trying to get over the learning curve. Finally bought an additional SD card so I could save a backup every so often when I'm trying out something new. That's come in handy.
No, it's not like Windows at all (which some people would probably say is a good thing).

No need to uninstall anything. With reLaunch go to the app "nook touch mod". Using this app you can map the nook button to anything you want including the B&N Home page.

Unfortunately this doesn't work either. You can set the 'n button' to do anything but bring up the small taskbar at the bottom, which then takes you to the Home page you have set up.
What I wanted back was the ability to hit the n button, and then be offered the choice of relaunch or B&N home. I can still get to the B&N homepage when the unit starts from being powered down. It's not the end of the world, but a little frustrating.
I haven't even tried to sideload apps or anything yet. And my one attempt to download a book ended when it seems my download location is set as an SD card.. I used to think I was tech savvy. It's only going to get worse. :silly:

gozo81 said:
Unfortunately this doesn't work either. You can set the 'n button' to do anything but bring up the small taskbar at the bottom, which then takes you to the Home page you have set up.
What I wanted back was the ability to hit the n button, and then be offered the choice of relaunch or B&N home. I can still get to the B&N homepage when the unit starts from being powered down. It's not the end of the world, but a little frustrating.
I haven't even tried to sideload apps or anything yet. And my one attempt to download a book ended when it seems my download location is set as an SD card.. I used to think I was tech savvy. It's only going to get worse. :silly:
Click to expand...
Click to collapse
There is a Android App "Default App Manager" on Google play that may work.

gozo81 said:
Unfortunately this doesn't work either. You can set the 'n button' to do anything but bring up the small taskbar at the bottom, which then takes you to the Home page you have set up.
What I wanted back was the ability to hit the n button, and then be offered the choice of relaunch or B&N home. I can still get to the B&N homepage when the unit starts from being powered down. It's not the end of the world, but a little frustrating.
I haven't even tried to sideload apps or anything yet. And my one attempt to download a book ended when it seems my download location is set as an SD card.. I used to think I was tech savvy. It's only going to get worse. :silly:
Click to expand...
Click to collapse
I had a vague notion that NookTouchModManager didn't work with Glowlight, but I might be wrong. If it does work, then you don't want to set the "N" button to bring up Home. Rather you want to set the QuickNav Home button to "default". That's going to get you the B&N page you seek. But that means you will need a way to access your app drawer/launcher as well. For that purpose either one of the other QuickNav buttons could be reassigned OR you could assign a long press of the "N" button to initiate the launcher.
If NTMM doesn't work with Glowlight then I stand by the original idea: uninstall any launchers and reboot. With no alternative, you should get the B&N Home screen unless you have in some other way reassigned the QuickNav Home button.
Don't get discouraged. As a noob (still...) I had to start over quite a few times and there were times I was sure I had bricked my Nook. But I didn't.

Nook simple touch tousch screen unresponsive

Hi I have a nook simple touch. I have factory reset it, and its stuck on the language selection screen as the touch screen is unresponsive.
The nook is on 1.2.1.
I have cleaned the screen with IPA, and used a bush to clean the edges of the screen.
Several months ago I replaced the battery, and its been working well since until now, and I have charged the battery fully.
I can't see any IR beams with my phone - I do see some blinking with a separate IR remote
Would be grateful for any suggestions to fix my nook.
Thanks

Do you have ADB working?
Your problem is that you factory reset it and now you probably have no ADB.
mdwsmith said:
I can't see any IR beams with my phone - I do see some blinking with a separate IR remote
Click to expand...
Click to collapse
Remotes are designed to work at 20 feet.
The NST Neonode zForce is designed to work at 4 inches and use the minimum of power.
When not actively being touched it only flashes periodically a single (or two? I forget) LED (instead of 26).
It's the lower left corner.
There's an app for the NST in my sig called Touch-1.0.apk
It will show a diagram of the rays and show which ones are blocked.
Most of the lines should be light gray.
Dark or dotted lines are occluded.
You may have one or two of those on the edges.
It's hard to get the bezel aligned nicely.
Use a cotton swab on the edges, the screen itself hardly matters.
When I fire up my old NST I usually have no touch sensitivity until I clean the bezel.
Code:
C:\>adb install Touch-1.0.apk
C:\>adb shell am start -n com.temblast.touch/.Touch
First thing, try a cotton swab with water going around the bezel.
Use a couple wet, then one dry.

mdwsmith said:
Hi I have a nook simple touch. I have factory reset it, and its stuck on the language selection screen as the touch screen is unresponsive.
Click to expand...
Click to collapse
Seems odd that you got to that point, presumably using the touch screen, and suddenly the screen won't respond. A few things come to mind:
1. Is it still on that screen? If so, is it even on? Perhaps the system crashed for some reason and it just left that image on the screen--or perhaps some hiccup caused the device to enter a fugue state. Either way, a forced restart with the power button might be in order.
2. Try swiping two fingers across the screen from right to left. This bit of "finger magic" was related to me a long time ago when I made a post similar to yours. Suddenly my screen would not respond! I thought the proposed "fix" was near ridiculous, but it worked! I've had the same thing happen to me very infrequently, sometimes even on the "drag to unlock" screen just after trying to wake up the device. The two-finger swipe always sorts it.
3. You are on 1.2.1 after a factory reset. I don't remember the setup sequence exactly, but at some point you're going to run into trouble unless you have skipped OOBE. Maybe the device has reached the "trouble" point?

This might be wrong place to ask this question but here it is anyway. I vaguely recall that in some thread were said that it is possible to place current version of software in factory reset partition so that when you are forced to do a factory reset you do not have to do all the upgrades after that. Am I wrong?

SJT75 said:
This might be wrong place to ask this question but here it is anyway. I vaguely recall that in some thread were said that it is possible to place current version of software in factory reset partition so that when you are forced to do a factory reset you do not have to do all the upgrades after that. Am I wrong?
Click to expand...
Click to collapse
This post: https://forum.xda-developers.com/t/nst-nstg-rom-1337-rom-apr-9.2931567/post-59790217 suggests a way to replace the factory recovery when it has been displaced by emmc CWM. Presumably the method could be used for what you suggest--if it is correct.
Although not exactly the same thing, you can come close by doing a factory reset, updating to FW 1.2.2 and then making a backup. NookManager can do all of that without rooting (I think...). I've done this for each of my three devices. As you say, it saves steps.

@renate,
Thanks for your help - I think your correct "Your problem is that you factory reset it and now you probably have no ADB."
I downloaded the platform tools and using
.\adb devices
list no devices.
Whats the best way of gettin adb working - I'm aware some files are missing from the forum.....
Thanks
Marcus

Well, there's a ton of ways to skin this cat.
Me? I'd use OmapLink to boot from the ROM bootloader into ClockworkMod recovery.
Code:
omaplink.exe aboot.bin u-boot12.bin uRecImg uRecRam
If your drivers aren't set up already this can be a bit painful.
Then you can go and mount system and data and configure things how you want.
Code:
# /system/bin/sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=1 where name='adb_enabled';
sqlite> .q
# echo -n 1 > /data/property/persist.service.adb.enable
The problem is that your regular system is working well enough it might be hard to get to a recovery or something on the SD card.
This is the easiest way for me, but @nmyshkin probably knows more ways.

I have a clockwork recovery sd card that I can boot from and adb into. I mounted system and data and tried via the CWM menu and then via windows powershell terminal;
PS C:\Users\mdwsm\Downloads\platform-tools_r31.0.1-windows\platform-tools> .\adb.exe install Touch-1.0.apk
Performing Push Install
Touch-1.0.apk: 1 file pushed, 0 skipped. 29.5 MB/s (11760 bytes in 0.000s)
/sbin/sh: pm: not found
PS C:\Users\mdwsm\Downloads\platform-tools_r31.0.1-windows\platform-tools> .\adb.exe shell am start -n com.temblast.touch/.Touch
/sbin/sh: am: not found
so some success, but I'm guessing cwm does not support running apks via adb?
Thanks Marcus

Oh, so you can get to CWM?
CWM does not include the Android subsystem so you can't use anything that uses that, like pm or am.
You can use things like sqlite3 or Linux utilities to change some things.
CWM does not use the touch screen, but it uses a normal kernel so it does load the drivers.
You can do the following:
Code:
C:\>adb shell
~ # cat /dev/input/event2
�!K���K���K�������
=�����f����J����
J��6
Touch the screen, you'll get something similar if the screen is working.

Hi, Unfortunately my replacement battery after 6 months seems to be faulty, which may or may not be responsable for some of these issues. I'd like to thanks the posters here for supporting me - its much appreciated keeping a 10 year old device going and avoiding waste.
XDA is great for this I have had the nook touch for 10 years, and i still have a nook HD+ still going - like the screen on that one good for comics.
May have to look for another e reader kobo clara looks good but eill have to see ahat supported well by XDA.
Thanks again Marcus

mdwsmith said:
I can't see any IR beams with my phone - I do see some blinking with a separate IR remote
Click to expand...
Click to collapse
Hi there, I'm in a similar boat here with my NSTG. What does your line here mean exactly? Should I be able to see the IR beams shining at the edge of the Nook screen? I haven't used mine in years so I can't remember if I should.

DannySolo said:
Hi there, I'm in a similar boat here with my NSTG. What does your line here mean exactly? Should I be able to see the IR beams shining at the edge of the Nook screen? I haven't used mine in years so I can't remember if I should.
Click to expand...
Click to collapse
reply from renate indicated that even if working the ir beams are liklely too faint to see in a phone camera (which can see IR)

IR remotes are blasters. They put a few hundred milliamperes into an IR LED to work at 20 feet.
The Neonode Zforce sensor works at a couple of inches.
Phone cameras are inherently IR sensitive. That's why they have "IR cut" filters in front. Something has to be pretty bright to blast through. The Raspberry Pi "IR" camera is just a normal camera without the filter. Colors look weird because it's sensing the IR too.
Yes, you can detect the pulsing of the Zforce LEDs but you'll need an IR photodiode hooked up to an oscilloscope.
The lower left corner pulses during idle to see if it has to start doing a full screen scan.
In any case, Touch-1.0.apk can tell you what's going on.
Ha! It took long enough to find this stupid picture.

Strangely, when I was putting in the SD card with NookManager the English language option became selected?!?! I could not reproduce this or any other on screen action.

DannySolo said:
Strangely, when I was putting in the SD card with NookManager the English language option became selected?!?! I could not reproduce this or any other on screen action.
Click to expand...
Click to collapse
?
NookManager is to boot from "power off". If that's how you started it and didn't see the first menu, then the card is defective in some way.
That said, I am not optimistic about using it. My suggestion was predicated on the ability of the adbgrab utility to give you remote touch access via your PC. It now appears that does not work.
It is possible to use series of sendvents via adb to "touch" the screen at specified coordinates but I think that would try the endurance of even the most single-minded enthusiast. Assuming you had some sort of plan to harness the hardware buttons.
I just don't see a realistic way forward without touch access.

Tabbing (slowly) and hitting enter (slowly) should be able to get most controls on a window.

Renate said:
Tabbing (slowly) and hitting enter (slowly) should be able to get most controls on a window.
Click to expand...
Click to collapse
Should is not does.
On the first "tab" press after the mirror of the home screen is displayed the device Search function is activated. That function icon exists nowhere on my home screen. Subsequent "tabs" move the cursor in the search entry field.
Next I tried something simpler like the app drawer (only six options). I opened that from the touch screen, refreshed, and then hit "tab". Lo and behold, device Search opened again.... It's really excited about searching all the books on the device. Again, no such icon in the app drawer.
So returning to the app drawer via the touch screen and refreshing, I hit "enter". The first icon is now highlighted and hitting the right "arrow" key moves the highlighting to the second icon.
Now we're getting somewhere. (but this only seems to work with launcher icons; on the home screen, for example, the status bar icons can't be accessed)
Hitting "enter" again opens the app that is highlighted, but a refresh is needed to make the mirror correspond to the actual device.
(Ha-Ha, PgDn turns on the glowlight...whoops, PgUp takes me back to the home screen...)
So...yeah, you can do some really basic stuff in unexpected ways. But when it comes to really interacting with an app screen, I'm stuck. For example, the attached screenshot. The up and down arrow keys scroll from top to bottom of the list and back. But there appears to be no way to select an individual item (no..."tab" opens device Search...). Not that the user would be wanting to get a crossword puzzle, but the problem of getting your desired input across to an app in this way is significant.
Out of curiosity I opened the NookTouch ModManager app which I had previously suggested to the user as a way to harness ten function options from the hardware buttons. But once I got it open using the utility, I had no way to navigate the screen to choose the options I wanted, not even on the opening screen with just two large menu bar selections, similar to the crossword item display.
So I can't see this working for him. It has potential, but unless there is further magic I am not getting, it just won't do the job.
And BTW, Touch-1.0.apk does not run properly (at least not for me). It seems to crash back to Home without doing or displaying anything.

Did you try the arrow keys?

Renate said:
Did you try the arrow keys?
Click to expand...
Click to collapse
Yes.
"The up and down arrow keys scroll from top to bottom of the list and back. But there appears to be no way to select an individual item."
That does not mean scrolling down the list one item at a time, rather that the entire list shifts. No indication that any single item is targeted. "Enter" has no effect there.