Related
I'm new to the android ecosystem but I've always been jealous of swype users, is it possible to port this feature to the nook touch?
Just replace apk file of swype with default keyboard using Root Explorer in system/app
I tried installing a keyboard apk file into system/app file by copy and paste with ES file explorer but it said failed. is there a special app or procedure I need to do this with? and where did you get the apk file? I would like a keyboard with directional arrows (for spreadsheets) and numbers for faster input. Thanks
Are you sure system is r/w?
Sent from my GT-I5700 using Tapatalk
roryn3kids using ES file explorer use the following instructions and you'll have access to r/w root files:
1. Scroll down to Root Settings and enable Root Explorer and Mount File System.
Not sure if this next step was needed but I did it anyway
2. Once again from the setting menu click on File Settings and enable "Show Hidden Files"
then copy the file from your data\app folder to your system\app folder
Swype "friendliness" to nook STR
The instructions above worked fine for me.
The problem is that I found the apk somewhere (a rather new version but still not the latest) and, even when it works, I do not get any "word list menu" like the one shown in those Swype Howto videos.
This means that, either I use an extremely short vocabulary, or I waste 50% of the time correcting the suggested word...
For instance, let's say I wanted to write f***, Swype forces me to accept the word duck.
This is good, because then I have the time to think twice before swearing but in the end... hum, let's say it's not that productive.
Of course, I checked that the options are properly configured (or I think so)
Does it happen to any of you, nook STR users?
BTW, I might also say that I cannot install the beta from swype.com/category/get-swype/
Have any of you succeeded on this?
Not that I want to re-activate a Post that was last updated in August, but it's nice to have as much information regarding swype as possible in a single post.
Thanks
I just discovered the Swype feature on my galaxy player 4.0 and it's great!
Never used Swype before this, But Since finding it a few days ago, it's all I've used! lol
Hope you get it installed, cuz its awesome.
Ok, I have further investigated the Issue and I can confirm now that it is properly configured (I compared it with some other devices) so let's ask it the other way around...
Is there any nook-STR-user who properly installed Swype?
How did you do it or, better said, where did you get your swype from?
Thanks very much, and a happy new year!
(sent using my not-that-effective-but-still-funny-to-play-with swype keyboard )
My findings with SWYPE are :
1. when you set your keyboard to SWYPE and do FACTORY reset, you might get problem in the "re_registration" your Nook. For some reason, the factory reset will not erase everything and the device is looking for SWYPE keyboard - which is obviously not there. So you won't have any keyboard to type onto !!! Having not a backup might get you in serious trouble !!!
2. As mentioned over here, the word prediction/suggestion is not visible so really, there is the small nuisance when you have to correct few words. keep an eye on it, when writing.
3. You might find a little bit frustrating the highlighting of a pressed button. Well, OK ... the truth is, that it's TOTALLY ANNOYING !!! Have a look on my video on youtube so you know, what I'm talking about :
youtube.com/watch?v=OYKjvqhxJmU&context=C3503defADOEgsToPDskIus5a7mP57B922B9wWU5cP
But, this can be fixed !!!
youtube.com/watch?v=S3vwQSvjUYM&context=C34142eeADOEgsToPDskJDd6sKkvt8EqkgO74yVfe7
Big THANK YOU goes to "djdarkknight96". His solution is to make the "highlighting" transparent, so it doesn't bother you any more. There was an attempt to make the trace line transparent as well, but without success (FC). Please, have a look at his thread for more info.
P.S. : With the youtube links -> as a new member outside links are not allowed for me yet -> so please add "www"
zholy said:
My findings with SWYPE are :
1. when you set your keyboard to SWYPE and do FACTORY reset, you might get problem in the "re_registration" your Nook. For some reason, the factory reset will not erase everything and the device is looking for SWYPE keyboard - which is obviously not there. So you won't have any keyboard to type onto !!! Having not a backup might get you in serious trouble !!!
Click to expand...
Click to collapse
My findings with this are that the swype keyboard is actually still there, so you need to use adb to delete the apk file and, if you replaced the original, find that one and use adb to add it.
Anyone running Taboonay 2.0 and got cell standby off...? How
delete phone.apk and telephony.apk from system/app always works for me. I hear editing the build prop works for some and not for others, same with tabtools app.
shaun298 said:
Anyone running Taboonay 2.0 and got cell standby off...? How
Click to expand...
Click to collapse
Thanks I will give it a try. One warning to other 2.0 user, I added the wifi= thing to the build.prop file and rebooted. Took for ever to come up, lost the splash screen and running 10 times slower and when I touch the app botton at top right to go to applications, the screen goes blank and finaly goes back to desktop. I restored the backup build.prop and rebooted and had the same thing.
The file had correct permission.
Tried other things, but in the end just reflashed.
Thanks for the tip
Update.
deleteing phone.apk locked it up and had to hold power botton in.
deleteing the telphony did not crash anything.
Just renamed both files did not work seems everything in that folder gets run.
The cell.standby icon is still their but its not using the bat.
Maybe erase bat statts..?
Now got to go and see what broke. Im so burnt on roms I could puke, luck Im between jobs and have massive hours to play. Thanks for the help.
using Thor's latest kernel and editing build.prop did the trick for me, with no need to touch phone or telephony.
Hey guys. I've been an android user for the past 2.5 years and during my time using it, I've run into rooting and taking full control of my phone. BUT that comes with a price. And luckily, that price isn't that big of a deal (unless you really mess up your device by doing things you don't know anything about). A few tweaks and changes to your "build.prop, csc, lib....etc" contents with a reboot sometimes fixes problems real quick and you'll be a happy camper after thinking "oh sh*t! My phone sucks and this can't be fixed".
Without further a due, here are some of the annoying issues I've run into and after searching/asking I figured out how to fix them:
First of all, all I need from you to have is a root browser app and some simple knowledge about editing files in there, changing permissions, moving stuff around, and all that stuff. I personally use "root browser" app. It's up to you. Whatever app you're comfortable with is fine.
1. The annoying "AT&T address book subscription" or whatever they call it pop-up window that pops in your face every time you open your contacts.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well, not anymore [emoji16] thanks to @NunHugger for pointing that out for us in one of his posts on the alliance ROM thread (and I happened to be an OCD. I take a screen shot of every useful post that I think will help me in the future and throw it in my SD card)
Using your root browser app navigate to system/csc/feature.xml and find this
<CscFeature_Contact_EnableAAB>true<
and change the "true" to false. Save, reboot, and enjoy.
2. WiFi issues. Like, your wifi isn't sticking while you're using your phone. It disconnects constantly. Or you have to re-enter your password every time you reboot. That is easy as well. I am not sure who figured it out first, but I've seen some posts praising @Walter.White for finding that out. Thanks to him either way. He helps so much all the time regardless.
From your root browser, navigate to system/build.prop and find this
ro.securestorage.support=true
and change the "true" to "false". Reboot and enjoy.
3. If you flash an international based ROM, you may lose your AT&T 4GLTE signal icon and end up with only G4 in the status bar. Even though it doesn't mean you don't have LTE, but hell it's so annoying to look at.
That's a very easy one. From your root browser, navigate to system/build.prop and find this
ro.product.name=hltexx
And replace the "xx" with "att". Save, reboot, and enjoy.
Also, I don't know who figured it out first. it's an old one (since the note 2 days)
4. Losing screen rotation functionality.
Due to "debloating" especially for those who have just gotten root (thanks to @geohot) and they're debloating the hell out of their phones. LOL
Some problems might occur thanks to samsung for linking so many of their bloat to the device's main functions. I ran into this problem and it drove me crazy. Thanks to the power of Google search and this gentleman here @phyowaiummg for posting the solution for it. It's caused by removing samsung hub with titanium. Titanium removes this
"libgnustl_shared.so"
file (that apparently controls the rotation function on our phone) from system/lib when you uninstall samsung hub with it. Just find that file in another ROM zip file. Extract it and throw it into your system/lib. Change permissions to rw-r-r and reboot.
Do NOT delete. Just freeze with titanium. It's not worth it. You're only going to save 150+ MB by deleting all the bloat. IF you can't help it, then use "root app delete" app from play store and delete the bloat.
5. HOW TO FULL UNROOT AFTER TOWELROOT (how I did it. It worked for me):
First you need to be on stock ROM (assuming you have a backup of it).
a. Un-install recovery from SS then Un-install the app-SS- itself.
b. Open up your "root browser". On the very first page, just keep scrolling down and find "SS" folder. Delete that.
C. From supersu app, go to settings/full unroot and press that and continue accepting all the windows that pop up. (Do NOT reboot yet).
d. From root browser, navigate to system/app and look for the supersu apk and see if it's there. If so, delete it. If it's not there, then you may find it in system/prev-app or data/app. Delete the hell out of it wherever you find it.
f. From root browser, navigate to system/xbin and find busybox and su and delete both.
d. Now reboot and cross your fingers it works. It worked for me.
Let me know if it works for you as well, please!
6. If you don't like the 480 DPI on your phone and think that your apps are too big. Or you don't want to use any apps/xposed modules (or for some reason those modules didn't work for you) to change that, then there is a method for you to do so by only a small edit in your build.prop (Thanks to @UK2K for bringing it up to this thread. Make sure to smack his "like" button wherever you find his posts ) . Some folks say that 375 DPI is the perfect way to go.
You can do that by just opening your "root browser" app. Navigate to system/build.prop then find
ro.sf.lcd_density=480
and change 480 to 375, save, reboot, and, as always, enjoy!
If you would like to save the original just put a "#" at the beginning and make it look like this:
#ro.sf.lcd_density=480
and just create a new one by typing it like this:
ro.sf.lcd_density=375
then, save and reboot.
7. This is an awesome addition by @hp79. Make sure to smack his "like" button.
[Enable soft menu keys]
edit "/system/build.prop", and add at the bottom:
Code:
qemu.hw.mainkeys=0
[Optional] Disable hardwired buttons.
edit "/system/usr/keylayout/Generic.kl", comment out these two lines so it looks like this:
Code:
# key 139 MENU
# key 158 BACK
After using a while, I found it works best if I keep the hardware buttons enabled too. Back key is now on both left and right side so it's easier to reach when using with one hand.
[Optional] Disable 3-dot menu button. When you enable soft-keys, there will be an additional menu shown in every app. This could waste lot of space. You should have Xposed mod installed, then look for Noverflow, and install that.
Noverflow xposed mod.
This doesn't work on Galaxy S5 Port Update 4 ROM, but works well with stock NC2 ROM.
[Optional] Once softmenu keys are added, you have less screen space. The Dialer app doesn't know how to scale, so you would have the bottom row keys chopped off a bit. You can make change the DPI settings so it'll shrink and be able to see everything.
Default screen DPI is 480. I changed it to 450.
Edit file "/system/build.prop", look for the line with "ro.sf.lcd_density=480" and edit so it looks like this:
Code:
ro.sf.lcd_density=450
[Optional] Remove AT&T wifi autoconnect.
I don't know why, but even if I uncheck autoconnect AT&T wifi, it still keeps trying. And you can't really remove the profile either.
Edit "/data/misc/wpa_supplicant.conf"
Look for "ssid="attwifi". Change that to something like this:
Code:
ssid="attwifi-sucks"
8. For those who are having GPS not locking problems, I've found this fix on XDA YouTube channel. What it is, is just download the file that has your country's/region's name from this website and throw it into your system/etc then reset your permissions to rw-r-r and reboot. It worked like a boss for me and I hope that for you, too.
Just follow what this video says http://youtu.be/oU67XHD0kj4
-Another fix for the GPS, just in case the above didn't work for you, found by @39FarmallM (thank you, sir):
I am going to quote his post for you guys:
"http://www.rom-central.com/showthrea...te-3-Rom-N9005 <==[This is where he found his fixes]
[SOLUTION] GPS Fix - When moving back to Note 3 Rom {N9005}
Hi guys
A lot of users have GPS problems when they move back to a NOTE 3 ROM after flashing a S5 PORT ROM.
Here is a possible fix. Tested only on N9005
Solution 1
On your dialer type in this USSD *#0011#
Press menu key > press back
Press menu key > press key input > Q
Press menu key > press key input > 0000
Wait for a few seconds and the screen options will change
*MAIN MENU comes up
*Tap [2] UE SETTING & INFO
*Tap [1] SETTING
*Tap [2] SYSTEM
Press om UMTS (Not there)
Press on Common (Not there)
*Press on [3] NV Rebuild
Press on NV Rebuild (Just once)
*[3] ALL
Wait for 30 seconds and then shutdown your phone
Power On phone
GPS should work fine now
Recommend to use GPS STATUS app to reset and download AGPS Data
Solution 2
Assuming you are on a S5 Port ROM, make sure GPS is enabled
Boot into recovery and without wiping anything "dirty" flash a note 3 rom and reboot
There will be a lot of force closes once reboot is complete. Reboot back into recovery
Wipe data and reboot into the Rom again. There may be a few force closes. Reboot back into recovery
Wipe 3 times (data, cache, system, boot)
I recommend latest Philz Recovery (use intall new rom option to wipe) <== [This is for those who have unlocked bootloaders and are able to flash a custom recovery. It still works with Safestrap, just in case you wonder]
Restore or install your desired Note 3 rom
GPS should work fine
Thanks"
-A Third fix by @rogerinnyc (thank you, sir). And since he has attached a zip file for you guys then I will just give you the link to his post and you do the rest
Hope that helps some of you guys. If anyone has a fix that I don't know about, please just pm me and I'll add it to op. Enjoy fellas.
...!!!
The first one for getting rid of that stupid contacts sync thing worked great! Thanks!
I just destroy that software with Titanium backup anytime it is a problem.
Nice write up k-alz
Sent from my SM-N900A using Tapatalk
Here is a video that you guys might find interesting.
https://archive.org/details/ShmooCon2014_Arms_Race...Bootloaders
Walter.White said:
Here is a video that you guys might find interesting.
https://archive.org/details/ShmooCon2014_Arms_Race...Bootloaders
Click to expand...
Click to collapse
Thanks dude. that's pretty cool. they're very talented. I'm guessing our bootloader is going to be cracked soon?
Sent from my SAMSUNG-SM-N900A using Tapatalk
K-Alzwayed said:
Thanks dude. that's pretty cool. they're very talented. I'm guessing our bootloader is going to be cracked soon?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Great info thanks
tmoore3496 said:
Great info thanks
Click to expand...
Click to collapse
No problem buddy. Hopefully it helped you.
Thank you for this. You've started me on my way to digging through my files and editing. .. After research of course.
Sent from my SM-N900A using XDA app
Just got my note 3 a couple of days ago after selling my mega on AT&T. So nice to have root access again. Thanks for the tips. Really like getting rid of that annoying contacts pop up.
UK2K said:
Thank you for this. You've started me on my way to digging through my files and editing. .. After research of course.
Sent from my SM-N900A using XDA app
Click to expand...
Click to collapse
You're very welcome, man. Glad I could help
azpatterson3 said:
Just got my note 3 a couple of days ago after selling my mega on AT&T. So nice to have root access again. Thanks for the tips. Really like getting rid of that annoying contacts pop up.
Click to expand...
Click to collapse
Welcome to the awesomeness of our community where everyone is nice and very helpful.
DPI change
I don't think I saw this in your thread but following your editing of the build.prop file I would like to add that the stock dpi of 480 was too "big" for me so after some reading I saw a few recommend 375 but they were using apps.
So by opening build.prop after remounting it as rw look for the line:
ro.sf.lcd_density=480
change to 375
save
remount to readonly -ro
If you would like to save the original just put a "#" at the beginning:
#ro.sf.lcd_density=480
ro.sf.lcd_density=375
I'll look again to make sure I didn't dupe someone that's given this tip.
UK2K said:
I don't think I saw this in your thread but following your editing of the build.prop file I would like to add that the stock dpi of 480 was too "big" for me so after some reading I saw a few recommend 375 but they were using apps.
So by opening build.prop after remounting it as rw look for the line:
ro.sf.lcd_density=480
change to 375
save
remount to readonly -ro
If you would like to save the original just put a "#" at the beginning:
#ro.sf.lcd_density=480
ro.sf.lcd_density=375
I'll look again to make sure I didn't dupe someone that's given this tip.
Click to expand...
Click to collapse
Thanks, man. I'll add it to OP. :good:
K-Alzwayed said:
Thanks, man. I'll add it to OP. :good:
Click to expand...
Click to collapse
Sweet! My first mention! :laugh:
Thanks Sir.
Brilliant wi-fi fix!
Brilliant fix for the Wi-Fi problem. I softbricked trying to update last night and finally found a 4.4.2 file to load via Odin that worked and immediately was relieved I got it to work and pi$$ed when I realized wi-fi was wanky. This fix worked perfectly. Thanks for posting this. All my searching paid off. Haven't done any homework for college or done any work around the house yesterday or today, but got my Note 3 back up and running.
K-Alzwayed said:
Hey guys. I've been an android user for the past 2.5 years and during my time using it, I've run into rooting and taking full control of my phone. BUT that comes with a price. And luckily, that price isn't that big of a deal (unless you really mess up your device by doing things you don't know anything about). A few tweaks and changes to your "build.prop, csc, lib....etc" contents with a reboot sometimes fixes problems real quick and you'll be a happy camper after thinking "oh sh*t! My phone sucks and this can't be fixed".
Without further a due, here are some of the annoying issues I've run into and after searching/asking I figured out how to fix them:
2. WiFi issues. Like, your wifi isn't sticking while you're using your phone. It disconnects constantly. Or you have to re-enter your password every time you reboot. That is easy as well. I am not sure who figured it out first, but I've seen some posts praising @Walter.White for finding that out. Thanks to him either way. He helps so much all the time regardless.
From your root browser, navigate to system/build.prop and find this
ro.securestorage.support=true
and change the "true" to "false". Reboot and enjoy.
Click to expand...
Click to collapse
sethomas1975 said:
Brilliant fix for the Wi-Fi problem. I softbricked trying to update last night and finally found a 4.4.2 file to load via Odin that worked and immediately was relieved I got it to work and pi$$ed when I realized wi-fi was wanky. This fix worked perfectly. Thanks for posting this. All my searching paid off. Haven't done any homework for college or done any work around the house yesterday or today, but got my Note 3 back up and running.
Click to expand...
Click to collapse
No problem. Glad it helped [emoji16]
THANK YOU!
#4 - it was driving me crazy!
I actually didn't uninstall Samsung Hub but I did freeze it. Somehow that lib file went missing though.
jpstiehl said:
#4 - it was driving me crazy!
I actually didn't uninstall Samsung Hub but I did freeze it. Somehow that lib file went missing though.
Click to expand...
Click to collapse
Glad It worked for ya man
Here's some to add. One is for soft-menu, and the other is for disabling AT&T wifi by renaming the SSID.
[Enable soft menu keys]
edit "/system/build.prop", and add at the bottom:
Code:
qemu.hw.mainkeys=0
[Optional] Disable hardwired buttons.
edit "/system/usr/keylayout/Generic.kl", comment out these two lines so it looks like this:
Code:
# key 139 MENU
# key 158 BACK
After using a while, I found it works best if I keep the hardware buttons enabled too. Back key is now on both left and right side so it's easier to reach when using with one hand.
[Optional] Disable 3-dot menu button. When you enable soft-keys, there will be an additional menu shown in every app. This could waste lot of space. You should have Xposed mod installed, then look for Noverflow, and install that.
Noverflow xposed mod.
This doesn't work on Galaxy S5 Port Update 4 ROM, but works well with stock NC2 ROM.
[Optional] Once softmenu keys are added, you have less screen space. The Dialer app doesn't know how to scale, so you would have the bottom row keys chopped off a bit. You can make change the DPI settings so it'll shrink and be able to see everything.
Default screen DPI is 480. I changed it to 450.
Edit file "/system/build.prop", look for the line with "ro.sf.lcd_density=480" and edit so it looks like this:
Code:
ro.sf.lcd_density=450
[Optional] Remove AT&T wifi autoconnect.
I don't know why, but even if I uncheck autoconnect AT&T wifi, it still keeps trying. And you can't really remove the profile either.
Edit "/data/misc/wifi/wpa_supplicant.conf"
Look for "ssid="attwifi". Change that to something like this:
Code:
ssid="attwifi-sucks"
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
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.
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
See the previous one.
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.