[Q] Nook simple touch home screen problem

[Q] Nook simple touch home screen problem - Nook Touch General

So this is my first post and I just rooted my nook simple touch using touchnooter. I unknowingly changed the soft keys on the right side of the screen to take me to the nook home screen and not to the android home screen. Now i cant get it back. or get to the homescreen for android at all? Can someone please help?

ADB pull /data/system/packages.xml
Edit the file so that there is nothing in the preferred-activities section:
Code:
<preferred-activities>
</preferred-activities>
ADB push /data/system/packages.xml
Be sure to select the correct thing the next time your Nook asks you what to do.

Related

[Q] Anyone living in DFW area? I need a huge help!!

Hello you all...
I am an idiot living in DFW area. I have had my nook color since last November and beginning of this year, I've rooted the bloody machine. I don't know what I was thinking. Everyone told me that the process takes only ten minutes or so, and it took me two full days. I should have known that I wasn't smart enough to mass with the machine and should have left it alone.BUT, I did root using the auto rooter file.
This afternoon, I decided to take my nook color back to its default setting and did the 8X thing before preregistering first. Now all I see is the scratched up "n" logo with" with the flashing "color" written beneath and the sickening green robot and the "nook color devs" logo at the bottom right.
It was a gift from my husband which means a lot to me, and I am not in position to just chunk it and buy a new one.
So, is there anyone living in the DFW area who can help me in person. I am only asking this because I am not smart enough to follow all the suggestions and directions that I will get (hopefully). I can show my appreciation to your help with small amount of B&N gift card. Please let me know if there is anyone who is smart and kind hearted to help me out.
Thank you.

ntishlias said:
Hello you all...
This afternoon, I decided to take my nook color back to its default setting and did the 8X thing before preregistering first. Now all I see is the scratched up "n" logo with" with the flashing "color" written beneath and the sickening green robot and the "nook color devs" logo at the bottom right.
Click to expand...
Click to collapse
You didn't do the 8x thing... be patient and try again, sometimes it seems like a 9x or 10x thing. I have done it a couple of times and just resorted not to count but to keep stopping the boot until it starts booting with the update screen.

bluepen61 said:
You didn't do the 8x thing... be patient and try again, sometimes it seems like a 9x or 10x thing. I have done it a couple of times and just resorted not to count but to keep stopping the boot until it starts booting with the update screen.
Click to expand...
Click to collapse
Hi bluepen61,
Unfortunately, I did see the update screen. After the update screen and the installing process was finished, I got stuck in the same screen.
I am so sickn' tired of looking at the same screen, I am very very close to
throwing the thing on the wall to be just done with it!

ntishlias said:
Hi bluepen61,
Unfortunately, I dod see the update screen. After the update screen and the installing process was finished, I got stuck in the same screen.
I am so sickn' tired of looking at the same screen, I am very very close to
throwing the thing on the wall to be just done with it!
Click to expand...
Click to collapse
Patience, do the 8x provess again.
Sent from my NOOKcolor using XDA Premium App

First, if you were able to get the thing rooted, then you are not an idiot (even if it took you two days). If the thing boots at all (which it does by your description...it just gets stuck somewhere), then this can be fixed. Don't throw it out, and dont get too frustrated.
I know you don't think that you can do it, but I can tell you that rooting the Nook is actually harder than installing a custom operating system of returning to the stock operating system.
There is a good thread that gives you step-by-step directions to getting your device back. I can let you know which steps to follow, and we can help if you get stuck...just post here again if a step is giving you trouble and we can guide you through it. I will assume that you want to return the thing to the original stock operating system. If you want to do anything more from there, then it will be easy because you will already know how to do this.
First, go to this thread:
http://forum.xda-developers.com/showthread.php?t=1030227
Read the entire first post. If you don't understand what he is talking about, that is OK.
Now go to the section that starts with "On with the guide:" in bold letters.
For step one in this section:
Download the sd card image that is linked in the first sentence. It is a zip file, so you will have to 'unzip' it before you can do anything with it. I will assume that you know how to do this, but if not it is quite easy. If you are using Windows 7 or XP, just double click on the file like you would any other file or folder. It will open up as a folder and you will see a file with the extension ".img" in the folder. Just drag and drop this somewhere outside of the zip folder (like on your desktop). There are also specific programs for doing this - the thread references a program called 7zip that you can download and use if you like.
For step two in this section:
Now that you have the sd card image, you need to 'burn' it (or copy it) to your micro SD card. If you don't have one of these, you only need a 1gb card and they are very cheap at places like Walmart. You will obvisouly also need a way to plug this card into your computer. Hopefully your computer has a place to plug SD cards in - most newer machines do. If not, then you will also need to pick up an SD card reader that plugs into a USB port on your computer. You will need to download either one of the programs linked in this step - either "win32diskimager" of "winimage". I use the first one and it works well. Once you have that downloaded, you will need to run the program as an administrator. This is done in windows 7 by right-clicking on the icon that runs the program, and then selecting 'run as administrator'. If you are on Windows XP, it should work fine without this. Once it is running, follow the directions that they give you in the thread - there is a link there that shows you exactly how to run the program and how to select your ".img" file from above. If you have trouble with this, post the issue here.
Now go down to the section labeled "Epilogue" in bold letters. Go to step #4. You want to follow the link in that step to download the file called "update-nc-stock-1.2-signed.zip". Once you have this file downloaded, copy it directly over to your sd card that you prepared above - do not unzip it or otherwise modify it.
If you have gotten this far, then you have done the hardest part. Power down your nook, put your sd card in the device, then turn your Nook back on. You should boot into something called ClockworkMod Recovery. It will be a text-based list of commands. The volume up and down buttons lets you navigate through the commands on the screen, the nook 'N' button on the bottom front of the device is equivalent to the 'enter' button that you press to select a command, and tapping the power button will let you back up one menu screen if you select the wrong thing. You want to use the volume down button and highlight the command 'install zip from sdcard'. Press the nook 'N' button to select this option. Use the volume down button again to highlight the 'choose zip from sdcard' command, and press the 'N' button again. You shoud now see a list of all the files contained on your sdcard. Use the volume down button to highlight the file "update-nc-stock-1.2-signed.zip", then press the 'N' button again. It will ask you to verify that you want to want to do this - select the option confirming that want to proceed and press the 'N' button again. It will take a few minutes, but a message will appear when it is done. At this point, hold the power button in for 8-10 seconds until the machine turns off. Take out your sd card, then turn the power back on. You should boot into the stock 1.2 operating system and your nook is revived.
It seems like a lot, but like I said if you were able to root it then you can do this. If you get stuck, post which step is giving you trouble and we can get you through it.

uk nst vs us nst

diff 1.1 us nst from 2011 vs 1.2 uk nst from 2day
rootfs
pastebin u4M1xRkJ
rom
pastebin uWSAcZ6Y
factory
pastebin XWnXjUeM
data
pastebin PgvewxzB
cache
pastebin P4Wqh1DV
boot
pastebin E3NeJP96
uk cache/recovery/log
pastebin uPLHxivA
Shows uk nst is just old us nst wi software update & new battery (lico vs mcnair)
uk nst manufacture date & mainboard sn is older than us nst from nov 2011
think cache/recovery/log shows b&n updating my uk nst from a 1.1 us nst
= b&n made too many nsts for us market, now they selling them here
= to update us nst to use uk store, think just need to replace factory/factory.zip on an old us nst wi factory/factory.zip from a uk nst & do factory restore

to update us nst to use uk store, think just need to replace factory/factory.zip on an old us nst wi factory/factory.zip from a uk nst & do factory restore
Click to expand...
Click to collapse
I'm happy to test this out if anyone can point me towards a uk factory.zip

can't post links, so http ge.tt forwardslash 4C0LRwQ forwardslash v forwardslash 0

I can confirm that flashing the uk factory.zip onto a us nook works just fine.

Anyone tried "downgrading"?
Hmmm, is the implication from this that it might be possible to "downgrade" to the US version of the software in order to root the device and gain the benefits of full access to android?
I don't know about the other UK owners, but I have no intention of ever buying a book from the Barnes and Noble web-site/store. I like the spelling of my books to be correct after all!
I might give this a go tonight and see where I get to.
John

johnjtaylor said:
I don't know about the other UK owners, but I have no intention of ever buying a book from the Barnes and Noble web-site/store. I like the spelling of my books to be correct after all!
Click to expand...
Click to collapse
Ha ha - as an Englishman in New York (well, actually Annapolis) I can relate!
I never know what spelling to teach my kids!

Well that's pretty straightforward the language is called "English" after all!
<grins, ducks and runs>
John

johnjtaylor said:
Hmmm, is the implication from this that it might be possible to "downgrade" to the US version of the software in order to root the device and gain the benefits of full access to android?
I don't know about the other UK owners, but I have no intention of ever buying a book from the Barnes and Noble web-site/store. I like the spelling of my books to be correct after all!
I might give this a go tonight and see where I get to.
John
Click to expand...
Click to collapse
Curses, foiled again! The US nook glowlight has no downloadable firmware..... grrrr

jeff_kz said:
I can confirm that flashing the uk factory.zip onto a us nook works just fine, however, I skipped the OOBE so I can't confirm that the registration process works.
Click to expand...
Click to collapse
I apologise if this is a stupid question, but can you (or anyone else) possibly point me in the direction of how to use this file?
I've done some research (including a search for 'nook simple touch factory.zip'), found out lots of stuff and downloaded lots of files, but I can't find any information on how to use this factory.zip file.
I did find that this is a standard folder/component of the Nook base installation, but how to use it with a stock firmware to effectively turn my US Nook into a 'UK Nook', I have no idea.
I would be really grateful for any help/information

To change the system software, replace the old factory.zip on partiton 3 with the factory.zip from the desired platform and then repeatedly interrupt the boot sequence to force a system restore. You will have to re-root after the system restore.
Code:
adb shell mount -t ext2 /dev/block/mmcblk0p3 /tmp
adb push factory.zip /tmp/factory.zip
adb shell umount /tmp
adb reboot
As soon as the "Read Forever" screen is visible,
Press and hold the power button until the screen briefly blanks white and then redraws the "Read Forever" screen
Briefly release the power button and then go to step 1
Repeat the above two steps six times, finally allowing the system to boot without holding down the power button.
If you've done all the steps correctly, you'll see the system restore screen which will replace your system software with software in factory.zip

jeff_kz said:
To change the system software, replace the old factory.zip on partiton 3 with the factory.zip from the desired platform and then repeatedly interrupt the boot sequence to force a system restore. You will have to re-root after the system restore.
Code:
adb shell mount -t ext2 /dev/block/mmcblk0p3 /tmp
adb push factory.zip /tmp/factory.zip
adb shell umount /tmp
adb reboot
As soon as the "Read Forever" screen is visible,
Press and hold the power button until the screen briefly blanks white and then redraws the "Read Forever" screen
Briefly release the power button and then go to step 1
Repeat the above two steps six times, finally allowing the system to boot without holding down the power button.
If you've done all the steps correctly, you'll see the system restore screen which will replace your system software with software in factory.zip
Click to expand...
Click to collapse
Thanks for the information.
Stupid question alert - the Nook has to be rooted before I do the above? If so, is there a guide? I rooted my old NST (non-glowlight) some time ago but I have since sold it. I now have a nice new shiny NST glowlight (US version) which I want to load the UK firmware onto.
Any pointers would be gratefully received.
Many thanks in advance.

nookingtom said:
Thanks for the information.
Stupid question alert - the Nook has to be rooted before I do the above? If so, is there a guide? I rooted my old NST (non-glowlight) some time ago but I have since sold it. I now have a nice new shiny NST glowlight (US version) which I want to load the UK firmware onto.
.
Click to expand...
Click to collapse
but what is the advantage to running a uk nook over a us? The US store is cheaper, i think, and if you do the conversion you can't register your nook anymore right?

So just to let you know... You can also apply that zip in CWM. It will not break your Nook Touch. It will not update propertly as well, it is somehow strange, so im making a factory reset now...

[Q] Messed up my phone

Hello!
I have messed up my Note 3 a lot. When booting it up, it gives me error "Unfortunately, com.sec.android.sviewcover has stopped." This comes up instantly again after pressing the "OK" button (I have 0.5 seconds to do something between these errors). After entering the PIN code and unlocking the lock screen I get the error "Unfortunately, TouchWiz Home has stopped (and just shows a black background)." I can still access the settings by pulling down the Action Bar.
I'll start with some background facts:
- Rooted my phone about 3 months ago. It has worked great this far.
- Today I managed to enter a too high value in the "Textdroider DPI" app, and after restarting the problems began.
Now I've factory reset the phone as that was the only thing I could do but that didn't change anything.
I'm so screwed. Can anyone help me?
EDIT: It's a Note 3 SM-N9005 N9005XXUGNG1

I had the same thing happen on my Note 10.1 the other day while messing around with DPI settings. Touchwiz doesn't play nicely with different screen densities and it crashes. There is a file in the /system folder called build.prop. Inside this file there will be a line that looks like this:
Code:
ro.sf.lcd_density=###
.
On a completely stock N9005 (I have the exact same model) this value should be 480. All you need to do is edit this line and reboot.

teh_geek said:
I had the same thing happen on my Note 10.1 the other day while messing around with DPI settings. Touchwiz doesn't play nicely with different screen densities and it crashes. There is a file in the /system folder called build.prop. Inside this file there will be a line that looks like this:
Code:
ro.sf.lcd_density=###
.
On a completely stock N9005 (I have the exact same model) this value should be 480. All you need to do is edit this line and reboot.
Click to expand...
Click to collapse
Firstly, thanks for your reply!
Is there any way I can access the /system folder from my computer?

Skrube said:
Firstly, thanks for your reply!
Is there any way I can access the /system folder from my computer?
Click to expand...
Click to collapse
Yes there is. It's a bit technical however and it depends on what recovery you're running. I've managed to solve this problem on my tablet running TWRP.
I also found something else you can try to do to hopefully get rid of the force close messages temporarily. Boot up your phone, connect it to your PC and (assuming USB debugging is enabled) run the following command from a terminal:
Code:
adb shell wm density 480
You mentioned in your previous post that you have rooted your phone, so I'm going to assume you're somehow familiar with commands and ADB
If all goes well, your screen density should change on the fly. Reboot your phone at this stage and if this gets rid of the force close messages and allows you to interact with your device, it should be quite easy to edit the build.prop file. Just go to the Play Store, install a root file manager (or better yet the application you used in the first place - Textdroider DPI) and edit the file. Make sure you set the density to 480.

teh_geek said:
Yes there is. It's a bit technical however and it depends on what recovery you're running. I've managed to solve this problem on my tablet running TWRP.
I also found something else you can try to do to hopefully get rid of the force close messages temporarily. Boot up your phone, connect it to your PC and (assuming USB debugging is enabled) run the following command from a terminal:
Code:
adb shell wm density 480
You mentioned in your previous post that you have rooted your phone, so I'm going to assume you're somehow familiar with commands and ADB
If all goes well, your screen density should change on the fly. Reboot your phone at this stage and if this gets rid of the force close messages and allows you to interact with your device, it should be quite easy to edit the build.prop file. Just go to the Play Store, install a root file manager (or better yet the application you used in the first place - Textdroider DPI) and edit the file. Make sure you set the density to 480.
Click to expand...
Click to collapse
Yes! I got it working now. (had some issues with adb and permissions but got it sorted)
Thanks a lot for your help!

No problem. Glad I could help Just remember to be careful when messing around with screen densities and to always keep a build.prop backup in case something goes wrong

How to force reinstall nook simple touch update 1.2.2

My nook touch (unrooted) runs 1.2.2, but it has bugs now ( the home button doesn't work most of time, screensaver goes on in several seconds during reading, etc. ). I think a reinstallation of the firmware may most likely resolve the issues. ( already tried erase and deregoster, doesn't change anything, as expected ). But the problem is after putting the update zip file into nook's root directory, nook just erases it without doing anything. So my question: any tool can be used to force nook reinstall the update zip without checking version number? Thx in advance for any help.

smjohn1 said:
My nook touch (unrooted) runs 1.2.2, but it has bugs now ( the home button doesn't work most of time, screensaver goes on in several seconds during reading, etc. ). I think a reinstallation of the firmware may most likely resolve the issues. ( already tried erase and deregoster, doesn't change anything, as expected ). But the problem is after putting the update zip file into nook's root directory, nook just erases it without doing anything. So my question: any tool can be used to force nook reinstall the update zip without checking version number? Thx in advance for any help.
Click to expand...
Click to collapse
You need to do a factory re-image so that the onboard OS version will be older than 1.2.2.
Power down. Then restart, and as soon as the "Read Forever" screen appears, press and hold the two lower hardware buttons. Wait for the prompt. Once the Nook is re-imaged it will accept the update again.

Thank you, but by two lower hardware buttons, you mean the page turning buttons?

nmyshkin said:
You need to do a factory re-image so that the onboard OS version will be older than 1.2.2.
Power down. Then restart, and as soon as the "Read Forever" screen appears, press and hold the two lower hardware buttons. Wait for the prompt. Once the Nook is re-imaged it will accept the update again.
Click to expand...
Click to collapse
Ha, I tried, but problem is the Home button doesn't work. Any other suggestions? Thanks.

smjohn1 said:
Ha, I tried, but problem is the Home button doesn't work. Any other suggestions? Thanks.
Click to expand...
Click to collapse
Yes the two lower "page turning" buttons. Is the "n" button used during that sequence? I didn't remember that. I guess that's in the prompts. Well, I dunno. NookManager can be used to trigger the factory image, but if you say that requires the not-working button, then you are SOL. Even CWM is going to need that button to select options.

nmyshkin said:
Yes the two lower "page turning" buttons. Is the "n" button used during that sequence? I didn't remember that. I guess that's in the prompts. Well, I dunno. NookManager can be used to trigger the factory image, but if you say that requires the not-working button, then you are SOL. Even CWM is going to need that button to select options.
Click to expand...
Click to collapse
Any tools that can be used to peek into Nook's file system through PC ( Linux ) to delete something and add something to trigger re/installation? The whole reason I am trying to reinstall is that the Home button doesn't work most of time, and I checked it is not a hardware problem.

smjohn1 said:
Any tools that can be used to peek into Nook's file system through PC ( Linux ) to delete something and add something to trigger re/installation? The whole reason I am trying to reinstall is that the Home button doesn't work most of time, and I checked it is not a hardware problem.
Click to expand...
Click to collapse
AFAIK what you want to do (if you knew exactly what) requires root access--which you don't have. There is an app that has an option which makes the NST very angry and triggers a no-escape factory reset (I've fallen victim to it once), but to install it you would need--you guessed it--root.
I honestly don't remember whether the factory reset option of NookManager is promptless or just the usual. Seems to me it just takes off once you remove the card and the device reboots, but I could be misremembering. I have another day of work on something and then I will be doing a reset on one of my devices, so I could tell you then.

nmyshkin said:
AFAIK what you want to do (if you knew exactly what) requires root access--which you don't have. There is an app that has an option which makes the NST very angry and triggers a no-escape factory reset (I've fallen victim to it once), but to install it you would need--you guessed it--root.
I honestly don't remember whether the factory reset option of NookManager is promptless or just the usual. Seems to me it just takes off once you remove the card and the device reboots, but I could be misremembering. I have another day of work on something and then I will be doing a reset on one of my devices, so I could tell you then.
Click to expand...
Click to collapse
Thank you very much. Waiting for your experiment results.
1) I can do root. But I couldn't find the package any more. Any pointers?
2) What do you by removing the card? Which card? I was planning to open the back cover and remove the battery, but then I found out you would need a T5 Torx screwdriver, which I don't have. So I gave up.

smjohn1 said:
Thank you very much. Waiting for your experiment results.
Click to expand...
Click to collapse
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.

nmyshkin said:
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.
Click to expand...
Click to collapse
Thanks a lot and I am in US!
Everything you said was correct with only one minor thing: NookManager doesn't have to be updated to 1.2.2. As is, it will boot. But after factory re-image, 1.2.2 has to be applied, otherwise Nook cannot register due to Nook server's TLS issue even NST says network connection problem.
Thanks again for this wonderful guide. Hope this is useful to other (unlucky) people.
As for my NST, after reinstallation, the Home button still doesn't work. So I have to believe it seems to be hardware problem and the cover has to be opened.

smjohn1 said:
Thanks a lot and I am in US!
Everything you said was correct with only one minor thing: NookManager doesn't have to be updated to 1.2.2. As is, it will boot. But after factory re-image, 1.2.2 has to be applied, otherwise Nook cannot register due to Nook server's TLS issue even NST says network connection problem.
Thanks again for this wonderful guide. Hope this is useful to other (unlucky) people.
Click to expand...
Click to collapse
Yes the only reason to update NookManager is to root 1.2.2
I'm sorry about the apparent hardware issue. I don't know where to go with that, but just to throw this out: rooting with NM installs NookTouchMod which would allow you to reassign the "n" button function to another hardware button. Awkward and less than ideal but perhaps a way to salvage the device if all else fails.

nmyshkin said:
Yes the only reason to update NookManager is to root 1.2.2
I'm sorry about the apparent hardware issue. I don't know where to go with that, but just to throw this out: rooting with NM installs NookTouchMod which would allow you to reassign the "n" button function to another hardware button. Awkward and less than ideal but perhaps a way to salvage the device if all else fails.
Click to expand...
Click to collapse
Wonderful and thx again!
Already rooted, and after reboot, saw "Home" and "ReLauncher", chose "ReLauncher", and then the setting icon at upper right. Lots of functions, but didn't see NookTouchMod or where can set up buttons functions. Only saw "Screen buttons behavior" in the Advanced Settings, but these are not to set hardware buttons.
The only I need is in a book reading mode, press a button to return to the library, so that can switch to another book easily. But I guess I am closer now

smjohn1 said:
Wonderful and thx again!
Already rooted, and after reboot, saw "Home" and "ReLauncher", chose "ReLauncher", and then the setting icon at upper right. Lots of functions, but didn't see NookTouchMod or where can set up buttons functions. Only saw "Screen buttons behavior" in the Advanced Settings, but these are not to set hardware buttons.
The only I need is in a book reading mode, press a button to return to the library, so that can switch to another book easily. But I guess I am closer now
Click to expand...
Click to collapse
Mmm....Relaunch. Not my favorite, but many people like it for its "simplicity". There is a way in Relaunch to get to an "app drawer" type screen which shows all the installed apps. That's where you'll find NTM and everything else. The sad truth is, I can't tell you how to get there. For me, Relaunch is counter-intuitive and strange, but I do know that thereis an app drawer as I have seen it myself back in the day when all this was new to me. I've done a cursory forum search but come up empty. That's the other thing that always riled me up about Relaunch. It's like its operations are a secret. There must be documentation somewhere, but I don't know where. I have a vague recollection that at the center bottom of some screen or another there is an actual app drawer symbol, but getting to that magic screen is the issue.
I'll keep looking, but right now I'm coming up empty.
Edit: in the long run, once you find NTM and reassign the "n" button, you might be better served by having the standard B&N home screen as your default launcher. This would provide you with your accustomed functions, easy access to the Library via the quick-nav buttons, etc. You could assign along press of the same button to bring up Relaunch for the few times you'll want it.

nmyshkin said:
Mmm....Relaunch. Not my favorite, but many people like it for its "simplicity". There is a way in Relaunch to get to an "app drawer" type screen which shows all the installed apps. That's where you'll find NTM and everything else. The sad truth is, I can't tell you how to get there. For me, Relaunch is counter-intuitive and strange, but I do know that thereis an app drawer as I have seen it myself back in the day when all this was new to me. I've done a cursory forum search but come up empty. That's the other thing that always riled me up about Relaunch. It's like its operations are a secret. There must be documentation somewhere, but I don't know where. I have a vague recollection that at the center bottom of some screen or another there is an actual app drawer symbol, but getting to that magic screen is the issue.
I'll keep looking, but right now I'm coming up empty.
Click to expand...
Click to collapse
You are right again. I do see "app drawer" at the bottom. Inside there are things like "library", "setting", "app (amazon)", "Kconnect", etc., just couldn't find NTM.
I could reboot to Home too, but I didn't find NTM either. Anyhow, I will dig and search too, and report back here.
Thx again.

smjohn1 said:
You are right again. I do see "app drawer" at the bottom. Inside there are things like "library", "setting", "app (amazon)", "Kconnect", etc., just couldn't find NTM.
I could reboot to Home too, but I didn't find NTM either. Anyhow, I will dig and search too, and report back here.
Thx again.
Click to expand...
Click to collapse
You're fast.
Info on basic ReLaunch functions here: https://github.com/yiselieren/ReLaunch. NTMM icon looks like big bold "n" with a bold little broken circle in it. Gotta be there.
Edit: ...unless....something went awry during the rooting process. You can root "again" with no harm/no foul and watch carefully this time the list of "dones" to make sure it did not throw an error for NTMM.

nmyshkin said:
You're fast.
Info on basic ReLaunch functions here: https://github.com/yiselieren/ReLaunch. NTMM icon looks like big bold "n" with a bold little broken circle in it. Gotta be there.
Edit: ...unless....something went awry during the rooting process. You can root "agai n" with no harm/no foul and watch carefully this time the list of "dones" to make sure it did not throw an error for NTMM.
Click to expand...
Click to collapse
OK, I think I need to go back to basics:
1. here is the NM used: http://download.doozan.com/nook/NookManager-0.5.0.zip
2. Here are some screen shots from relaunch:
1) relauncher
2) all apps installed ( from the middle icon at the bottom ): no NTMM there
3) and 4) settings ( from right icon at the top )
3. I don't see a way to install other Android apps, except from Amazon stores ( which I didn't try ) but not from Google App store. Did I install a "wrong" version of NM?
4. One more thing: I "rooted" again, finished quickly, and no changes after boot ( My guess is NM sees the same root package to decide not to do anything ).
Any advice?
----------------------------------------------------------------------------------------------------
After posting above, I installed NTMM-0.4.0.apk successfully, but it says it needs modified jars. From https://forum.xda-developers.com/showthread.php?t=1991048 and https://github.com/doozan/NookTouchPatches.
So NTMM wasn't installed during root.
Now my questions:
how to install these patches? I am using Linux with no adb ( I don't want to use adb anyway ), any apk file that can be written to sdcard for quick and easy installation?
and does this patch work for 1.2.2?

smjohn1 said:
OK, I think I need to go back to basics.
Click to expand...
Click to collapse
Yes, I think you missed some important points from what I wrote previously. Here is the only sequence that is going to give you the desired result:
1. Factory re-image
2. Install 1.22 update
3. Register
4. Prepare NookManager card from here.
5. Update NookManager card following the directions here. You MUST do at least the update for 1.2.2 or root will not be successful and your device will be messed up. Other updates are optional, but know that some apps like Amazon App Store are dead. Other updates deal with these issues.
6. Boot with the NookManager card inserted.
*Optional* 7. Make a back-up of your registered device running 1.2.2. This can save you extra steps if you need to go back for any reason or suffer some catastrophe that seriously messes with your system.
8. Root using NookManager. Watch the screen for check for any failures.
9. Reboot, choosing ReLaunch as a launcher (but do not set as default yet).
10. Use NTMM to assign "n" button function ("Home") to some other hardware button. This is how you will get to QuickNav buttons.
11. Use NTTM to assign long-press of your reassigned "n" button to ReLaunch.
12. Reboot.
13. Select "Home" as default launcher (i.e., check the little box before choosing "Home". This choice can be changed later if you want.
Now you're back to a functioning system. Additional apps are installed by moving the apk file from your PC to a folder on your NST ("Download"?) and tapping the app icon in ReLaunch. Apps are uninstalled by long-pressing the app icon (I think).
The Amazon App Store is useless as you can read in the directions for updating NookManager.
Don't skip any steps.

nmyshkin said:
Yes, I think you missed some important points from what I wrote previously. Here is the only sequence that is going to give you the desired result:
1. Factory re-image
2. Install 1.22 update
3. Register
4. Prepare NookManager card from here.
5. Update NookManager card following the directions here. You MUST do at least the update for 1.2.2 or root will not be successful and your device will be messed up. Other updates are optional, but know that some apps like Amazon App Store are dead. Other updates deal with these issues.
6. Boot with the NookManager card inserted.
*Optional* 7. Make a back-up of your registered device running 1.2.2. This can save you extra steps if you need to go back for any reason or suffer some catastrophe that seriously messes with your system.
8. Root using NookManager. Watch the screen for check for any failures.
9. Reboot, choosing ReLaunch as a launcher (but do not set as default yet).
10. Use NTMM to assign "n" button function ("Home") to some other hardware button. This is how you will get to QuickNav buttons.
11. Use NTTM to assign long-press of your reassigned "n" button to ReLaunch.
12. Reboot.
13. Select "Home" as default launcher (i.e., check the little box before choosing "Home". This choice can be changed later if you want.
Now you're back to a functioning system. Additional apps are installed by moving the apk file from your PC to a folder on your NST ("Download"?) and tapping the app icon in ReLaunch. Apps are uninstalled by long-pressing the app icon (I think).
The Amazon App Store is useless as you can read in the directions for updating NookManager.
Don't skip any steps.
Click to expand...
Click to collapse
Ha, the step missed was 5, as it was difficult to change the files. But I remade an NM card ( there must be something wrong with the old one ), afterwards it was to update NM to 1.2.2.
Now buttons are reassigned and this reader is usable again ( I don't plan to make it a full android pad, as there are already too many tablets in house ). So this e-reader owes its life to you. Big thanks!
One last thing: how to reset Default back to Home instead of Relaunch? ( The re-root was quick, as it probably installed NTMM. But reboot doesn't give chance to reset default back to Home, it still goes straight to Relaunch. Of course I can live with it, but it would be nicer to configure as you suggested. )

smjohn1 said:
One last thing: how to reset Default back to Home instead of Relaunch? ( The re-root was quick, as it probably installed NTMM. But reboot doesn't give chance to reset default back to Home, it still goes straight to Relaunch. Of course I can live with it, but it would be nicer to configure as you suggested. )
Click to expand...
Click to collapse
If there is a way to access the App Manager through ReLaunch, you can run down the list until you get to ReLaunch and there remove any default actions associated with it.
If that is not obvious then the next easiest thing is to install yet another launcher! So you could transfer a copy of ADW Launcher from the NookManager update page to your NST and install it. If you then reboot it will trigger the App Picker dialog again because now there is a new choice. Before you select "Home", be sure to tick the little check box.
Then you can uninstall ADW Launcher. It's possible that may trigger another App Picker with the remaining two choices but I don't think so.
Once that's sorted you can finish your button reassignments. I think ReLaunch actually hijacks some of the QuickNav buttons so you might have to use NTTM to return them to default or pick completely new assignments, as you like.
I'm glad you were able to get the device back in a usable state. I love my NST for reading. After all these years I think it's still a great little piece of technology.

How to access my Nook Glowlight 3 without registration?

Hello everyone,
Could you show me how to access my Nook Glowlight 3 without registration ?
Current firmware: 50.0.117
Thank you!

Well, I usually bypass the registration by popping the thing open, hooking up a 3.3V UART interface and getting a root console.
I've never really looked into if there were secret hand signals to bypass the registration.
So I looked at the disassembled code to see what was there.
All the OOBE (Out-of-box-experience) stuff is in /system/priv-app/bnereader.apk
The welcome screen is com.nook.app.oobe.o.WelcomeIntroActivity
This calls com.nook.viewutils.KeyHeldHelper to see if a particular button is held down
and also com.nook.viewutils.MultiClickListener to see if you tap three times.
I held the button and tapped three times and I got com.nook.app.util.DiagnosticActivity (as in the screen grab).
(You can also get here if you had a shell with)
Code:
# am start -n bn.ereader/com.nook.app.util.DiagnosticActivity
The problem? The key you have to hold down while tapping is the volume up key.
What? You don't have a volume up key?
The way I held down the volume key was with a USB keyboard, but that can only be done when you're rooted.
You could also pipe raw events to the input system if you were rooted.
I'm certainly interested in someone contradicting me, but this seems like a dead end.

Ok, I'm going to contradict myself.
As I said, the Welcome Intro screen needs the volume up key and a triple tap.
There is also the com.nook.app.oobe.RegisterUserLogin screen
This can be bypassed by holding the Lower Left and the Upper Right and giving a triple tap.
Obviously, this would only work on the Glow3 which has buttons.
Unfortunately, the Glow2 has the exact same code.
I can't seem to get this one to work on an (already rooted) Glow3.
If you have a Glow3 try the LL/UR/triple tap.
Yes, this should work on the Glow3 if you are at a page with email/password/etc.
I can't get there because I'm intercepted by the WiFi page.

It's not working
Hello
I have Nook Glowlight 3, I tried the LL/UR/triple tap many times on login screen. but it don't work
Thank you!
Renate NST said:
Ok, I'm going to contradict myself.
As I said, the Welcome Intro screen needs the volume up key and a triple tap.
There is also the com.nook.app.oobe.RegisterUserLogin screen
This can be bypassed by holding the Lower Left and the Upper Right and giving a triple tap.
Obviously, this would only work on the Glow3 which has buttons.
Unfortunately, the Glow2 has the exact same code.
I can't seem to get this one to work on an (already rooted) Glow3.
If you have a Glow3 try the LL/UR/triple tap.
Yes, this should work on the Glow3 if you are at a page with email/password/etc.
I can't get there because I'm intercepted by the WiFi page.
Click to expand...
Click to collapse

dnt83 said:
I tried the LL/UR/triple tap many times on login screen. but it don't work
Click to expand...
Click to collapse
You know, there are more secret touches and broken code all over.
I found another one, but I can't seem to get this to work either.
It's on this screen. There are four touch spots.
The bottom two when pressed and held should show a version number at the top center of the screen.
The top two, in some pattern (that I'm still looking at) should respond with the Easter Egg which gets you to the Diagnostic.
I'm working on it, but you can try too.
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.

Renate NST said:
You know, there are more secret touches and broken code all over.
I found another one, but I can't seem to get this to work either.
It's on this screen. There are four touch spots.
The bottom two when pressed and held should show a version number at the top center of the screen.
The top two, in some pattern (that I'm still looking at) should respond with the Easter Egg which gets you to the Diagnostic.
I'm working on it, but you can try too.
Click to expand...
Click to collapse
Thank you very much for your support
The bottom two it showed version.
I tried the top two it no work

dnt83 said:
I tried the top two it no work
Click to expand...
Click to collapse
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.

Renate NST said:
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.
Click to expand...
Click to collapse
Yes, it worked
Thank you very much!

Renate NST said:
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.
Click to expand...
Click to collapse
Hello
Could you show me next step to root it?
Thank you!

Renate NST said:
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.
Click to expand...
Click to collapse
Hello
I rooted and can work in adb shell, could you show me how to skip oobe?
Thank you!

dnt83 said:
how to skip oobe?
Click to expand...
Click to collapse
You need to install a launcher so that you have something "Home" to run.
Also:
Code:
# pm disable com.nook.partner/.oobe.WelcomeScreenActivity

Renate NST said:
You need to install a launcher so that you have something "Home" to run.
Also:
Code:
# pm disable com.nook.partner/.oobe.WelcomeScreenActivity
Click to expand...
Click to collapse
Yes, Thank you
I already installed custom firmware
Thank you very much for your support!

And if anybody is wondering, this works on all 5.0 Nooks, Glow2, Glow3, Glow4

Hi, I just picked up a new Nook Glowlight Plus (the 2019 7.8" model) and am trying to get started using it without the compulsory registration. My understanding from the start of this thread is that I should be able to root it, install an alternate launcher, disable the oobe.WelcomeScreenActivity, and I'm off to the races.
I have gotten as far being able to see the device with adb and connect to it, but I can't root it. adb seems to be working as normal (e.g., I can "adb shell" in as I would expect) but any attempts to push files with "adb push" fail. After attempting adb push, the device disconnects from adb and can no longer be seen until I physically unplug and re-plug it. Interestingly, adb push of a directory _does_ create the directory structure on the Nook -- just not any of the actual files...
Any help debugging this is appreciated...
A log of what I'm seeing is here:
https pastebin.com / ti4qB6Xr
(Sorry, I can't post direct links yet, and didn't want to spam the thread with a wall of text...)
Thanks!
---------- Post added at 02:58 AM ---------- Previous post was at 02:52 AM ----------
I should also mention that if I start to go through the on-device Welcome screen (choose timezone, choose wifi network and enter password), before actually getting to the login screen, I'm prompted to allow it to download a firmware update. I did not allow the update, in case a) the update changes something that would make rooting or installing a new launcher more difficult, and b) I don't want to miss the opportunity to note the download link and fetch an extra copy of the update in case it's useful later.
But if the download link is already known to the community, and if the update is unlikely to change anything that rooting/launchers depend on, I would also try letting it download, and then going to the login screen and trying the lower-left+upper-right+triple-tap bypass mentioned earlier in the thread.
Please let me know if I should try this.
Thanks.

So "adb push" is still not working, but I was able to root the device with shell chicanery. I tarred/gzipped the exploit payload, base64 encoded it, and used a shell loop to transfer it a line at a time:
Code:
c=1
cat nookrooter.tgz | base64 -e | while read line
do
echo "$c" >&2 ; c=$(expr $c + 1)
echo "$line" | adb shell 'busybox head -1 | busybox tee -a /data/local/tmp/nookrooter.tgz.b64 > /dev/null'
done
At ~64k base64-encoded lines, it took a bit over an hour to transfer. After base64-decoding, checking the md5 on both sides, and untarring in the right spot, it rooted just fine:
Code:
frappe/home/chris/nook/root-glp/rootGLP-3-13998# adb shell id -u
uid=0(root) gid=0(root)
That said, I'd still love to get some guidance on this device from folks who are familiar with it. Any idea why adb push might consistently fail? Is my basic understanding of how this whole process works is correct? Does it matters if I allow the device to complete the OTA firmware update before going farther?
My intent for the device is to use it as a standalone e-reader. I don't want to ever connect it to a network, nor to run any apps on it other than an e-reader. Public domain e-book content will be converted to EPUB (or, occassionally, CBZ or PDF) with Calibre (specifically the ebook-convert CLI) and copied via USB. I don't need to use "shelves" or whatever the Nook paradigm is for organization, nor will I "manage" the device with Calibre; "management" as such will be strictly copying individual files into a flat directory structure from the shell. I'm not too fussy about fonts, and don't need (or want) much more than the ability to click on a book and page-up/page-down through its contents.
I'm an experienced C/Unix developer, but have never used Android before.
Any help and pointers are much appreciated.
Thanks!

CrisCraigMorgan said:
But if the download link is already known to the community...
Click to expand...
Click to collapse
Yes, the manifest of the updates is discussed here: https://forum.xda-developers.com/nook-touch/general/software-updates-wifi-t4136097
CrisCraigMorgan said:
So "adb push" is still not working...
Click to expand...
Click to collapse
Strange. Why didn't you try adb install on the apk?
Maybe the adb on your host is broken. Try this.
adb push something
Did it fail?
adb devices, is it "gone"?
lsusb, really?
adb kill-server
adb devices, is it "back"?

Renate NST said:
Yes, the manifest of the updates is discussed here: https://forum.xda-developers.com/nook-touch/general/software-updates-wifi-t4136097
Click to expand...
Click to collapse
Thanks!
Renate NST said:
Strange. Why didn't you try adb install on the apk?
Click to expand...
Click to collapse
I'll try installing some apk that way. But in the case of the root payload, there are other files in addition to the one APK.
Renate NST said:
Maybe the adb on your host is broken. Try this.
adb push something
Did it fail?
Click to expand...
Click to collapse
Yup, I tried experimenting with other files, smaller files, individual files rather than directories -- all files failed (though, as noted, directories were created in the case of trying to push a local source directory).
Renate NST said:
adb devices, is it "gone"?
lsusb, really?
adb kill-server
adb devices, is it "back"?
Click to expand...
Click to collapse
I can run some more experiments later. The pastebin log above shows what I saw: immediately after any attempt to use "adb push", "adb devices" showed no devices. I didn't check usbconfig (FreeBSD here, not Linux, but that shouldn't matter), but there were no kernel messages about the device detaching (until I physically pulled the USB cable), so I suspect that the device would still have shown as attached.
Thanks!

So having rooted my Nook, I went ahead and installed the l2.apk launcher posted here https://forum.xda-developers.com/nook-touch/general/normal-launcher-nook-t3966911; disabled com.nook.partner/.oobe.WelcomeScreenActivity; renamed the bootanimation file; and rebooted.
When the device rebooted, it just displayed a message that said, "Unfortunately, com.nook.partner has stopped" and nothing else. Re-enabling com.nook.partner/.oobe.WelcomeScreenActivity restored it to its original boot-up behaviour.
So I think I must be missing something basic about the boot process, or rooting generally.
Should it be sufficient to just have another launcher installed? Do I have to do something particular to invoke it during the boot process?
Should I install TWRP? Alternate firmware, as described here: https://forum.xda-developers.com/nook-touch/general/gp-g3-gp7-8-twrp-alternative-firmware-t4074347 ?
Another question I have is about keeping root access across reboots. I can unpack the exploit in rootGLP-3.zip (from https://forum.xda-developers.com/nook-touch/general/how-to-root-set-nook-glowlight-3-t3802331) and run it to gain root; but when I reboot the device, I lose root again until I re-run the exploit. I tried setting /system/bin/busybox suid root, but then "busybox su" returns "unknown user root" -- I'm guessing because it's calling getpwuid(), but there's no /etc/passwd so the call fails. Could I just create /etc/passwd to define root? I also tried copying the "su" binary in the exploit dir into /system/chris/bin/ and setting it suid root, but this also fails (with no output). I could just write the three-line version of su that calls
Code:
setuid(0); exec("/system/bin/sh")
, but I have no idea how to compile code for this thing. Anything I'm missing here?
Thanks.

I played around a bit more with adb push. Still consistently failing, but restarting the local adb server does at least re-establish connectivity without unplugging/re-plugging the device. Definitely sounds like a problem with my local adb install rather than the device. Considering that I have a(n admittedly super-janky) method to transfer files, I don't feel a strong need to debug it right now.
Code:
frappe/home/chris/nook-13599# usbconfig | grep 1.6
ugen1.6: <BarnesAndNoble BNRV700> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
frappe/home/chris/nook-13600# adb devices -l
List of devices attached
MY_SERIAL_NUMBER device usb:1:6 transport_id:19
frappe/home/chris/nook-13601# adb push ReLaunchX_2.1.5-app-debug.apk /data/local/tmp/
adb: error: failed to copy 'ReLaunchX_2.1.5-app-debug.apk' to '/data/local/tmp/ReLaunchX_2.1.5-app-debug.apk': couldn't read from device
ReLaunchX_2.1.5-app-debug.apk: 0 files...ped. 7.6 MB/s (131056 bytes in 0.016s)
frappe/home/chris/nook-13602# usbconfig | grep 1.6
ugen1.6: <BarnesAndNoble BNRV700> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
frappe/home/chris/nook-13603# adb devices -l
List of devices attached
frappe/home/chris/nook-13604# adb kill-server
frappe/home/chris/nook-13605# adb devices -l
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
MY_SERIAL_NUMBER device usb:1:6 transport_id:1
frappe/home/chris/nook-13606# adb shell
[email protected]_6sl:/ # id
uid=0(root) gid=0(root)
[email protected]_6sl:/ # ^D

CrisCraigMorgan said:
Anything I'm missing here?
Click to expand...
Click to collapse
There's all sorts of "rooting" stuff here, but I just prefer a simple replacement of adbd in the ramdisk with one that doesn't switch to user "shell".
I don't want/need/like the chainfire stuff hanging around.
Sorry, I've lost track of where everything here is as I've never used any exploit method.
As for your launcher stuff, did you check logcat to see if there is any obvious reason why partner.apk is dying?
Code:
adb logcat
Have you tried:
Code:
adb shell am start -n com.android.launcher/com.android.launcher2.Launcher
Was the Launcher even installed correctly?
Code:
adb shell pm list packages -f launcher

Database Users

welcome