Hi,
I've manually installed FW v.1.2.0 on my NSG. Rooting with Nook Manager went without any problems.
Now I'm trying to manually add gapps from glownooter 1.5.26 package. Since it is for older FW it causes hangs on loading screen.
While putting manually files from glownooter with adb, I've found that the root of the problems lies probably in framework.jar. It was patched to provide IMEI for registration purposes, but now it seems that new FW changed that file.
It would be great if it was possible to update authentication patch for fw v.1.2.0 following this thread:
http://forum.xda-developers.com/showthread.php?t=955847
Meanwhile I can boot fine, when the new framework.jar stays untouched. But then I can not go through android initial wizard - on the first screen I can not get through clicking on droid icon. If SetupWizard.apk is removed from nook system boots fine, but apps (apart from YouTube) does not start since device is not connected to google account.
I hope that with little help we would have gapps running on new fw.
zetet said:
Hi,
I've manually installed FW v.1.2.0 on my NSG. Rooting with Nook Manager went without any problems.
Now I'm trying to manually add gapps from glownooter 1.5.26 package. Since it is for older FW it causes hangs on loading screen.
While putting manually files from glownooter with adb, I've found that the root of the problems lies probably in framework.jar. It was patched to provide IMEI for registration purposes, but now it seems that new FW changed that file.
It would be great if it was possible to update authentication patch for fw v.1.2.0 following this thread:
http://forum.xda-developers.com/showthread.php?t=955847
Meanwhile I can boot fine, when the new framework.jar stays untouched. But then I can not go through android initial wizard - on the first screen I can not get through clicking on droid icon. If SetupWizard.apk is removed from nook system boots fine, but apps (apart from YouTube) does not start since device is not connected to google account.
I hope that with little help we would have gapps running on new fw.
Click to expand...
Click to collapse
Have you had any luck with this? having similar issues! When selecting 'My Channel' in Youtube, it gives a 'There was a problem authenticating' message.
Also used NookManager as all attempts at trying to root 1.2.0 with TouchNooter failed. It would never get past the 'your nook is starting up' page.
It came pre-installed with 1.2.0 but looks like I may have to downgrade to get the play store to work:
http://forum.xda-developers.com/showthread.php?t=2040040
Guantonio said:
Have you had any luck with this? having similar issues! When selecting 'My Channel' in Youtube, it gives a 'There was a problem authenticating' message.
Also used NookManager as all attempts at trying to root 1.2.0 with TouchNooter failed. It would never get past the 'your nook is starting up' page.
It came pre-installed with 1.2.0 but looks like I may have to downgrade to get the play store to work:
http://forum.xda-developers.com/showthread.php?t=2040040
Click to expand...
Click to collapse
Hi,
I managed to get through - at least partly. I mean I have working google apps, but market is not working. It seems that BnN changed their framework.jar and the already patched version from nooter is not working anymore - that is why after rooting with nooter Nook is not booting.
If getting working gmail etc. is enough I can give You detailed instructions to get it working - unfortunately it is not single step procedure.
zetet said:
Hi,
I managed to get through - at least partly. I mean I have working google apps, but market is not working. It seems that BnN changed their framework.jar and the already patched version from nooter is not working anymore - that is why after rooting with nooter Nook is not booting.
If getting working gmail etc. is enough I can give You detailed instructions to get it working - unfortunately it is not single step procedure.
Click to expand...
Click to collapse
I already have email working, it was mainly the Play store I was after, thanks anyway.
zetet said:
If getting working gmail etc. is enough I can give You detailed instructions to get it working - unfortunately it is not single step procedure.
Click to expand...
Click to collapse
Yes please, could you explain how to get gmail etc working?
I used k9 mail for my gmail account, I find it is more useful on the nook ereader.
Did you get google calendar working yet?
I created a diff from the glownooter's framework.jar (1.1.5) and the original. I then applied this diff to the 1.2.0 framework.jar. (This is without the debug information.) Although I have since deleted all the gapp stuff, it worked at one time.
This is my first post although I have been reading and researching off of xda for the last 6 weeks.
You have to know what you are doing. If you need help, let me know.
here is the patch I used:
I just posted an addon for NookManager to install Google Apps for firmware 1.2.0 and 1.2.1. The thread is http://forum.xda-developers.com/showthread.php?t=2086582 Hope you find it helpful.
BTW, I used an awk script to patch the smali instead of diff / patch. It's more resilient to changes in the firmware and the oddities of line numbers and baksmali labels. It should make creating a new patch for the next firmware simple. I also added a patch to services.jar to get the setup wizard working and eliminate the YouTube - GMail dance. I'm uploading all my work to github now and will link it from the above thread.
Related
The thread of ManualNooter for 1.2 stock is getting pretty long, so I'm asking this in a new thread. I've only used AN in in the past, so I had planned to wait for AN for 1.2. Reading about MN it seems to give me everything that AN did.
So the point of this post is to ask if there is any reason to wait for AN?
theroberts said:
The thread of ManualNooter for 1.2 stock is getting pretty long, so I'm asking this in a new thread. I've only used AN in in the past, so I had planned to wait for AN for 1.2. Reading about MN it seems to give me everything that AN did.
So the point of this post is to ask if there is any reason to wait for AN?
Click to expand...
Click to collapse
There is some issue with manual nooter (see the last page or so of the hread) I, and others, are suggesting that it needs some additional work.
As usual, caveat emptor
theroberts said:
The thread of ManualNooter for 1.2 stock is getting pretty long, so I'm asking this in a new thread. I've only used AN in in the past, so I had planned to wait for AN for 1.2. Reading about MN it seems to give me everything that AN did.
So the point of this post is to ask if there is any reason to wait for AN?
Click to expand...
Click to collapse
GabrialDestruir is the author of both the 1.0.0 and 1.0.1 AutoNooter as well as the author of the ManualNooter, so it's all good.
The reason it's "manaul" right now is he wanted to get it out there, even though it's not a "one step" process right now.
ManualNooter is ran basically like your normal CWM Update file.
AutoNooter implies to me anyways, that it does it all automatically just pop the card in.
MN works wonderfully, easy to do, do it now!
So then the manual nooter is working fine and the only thing being worked on still is creating the auto version?
All my apps save for Google Calendar, Swift Key and Angry Birds work great.
Angry birds now working via
dropbox and install with sd card out.
Thanks for the replies. Think I'll go ahead and do it.
I'm pretty new at this, but I was able to follow Manual Nooter pretty easily and seem to have most things working.
I just have one question (and pardon if it's already been answered somewhere); the usual Google Calendar app and the usual Google Contacts app that I'm familiar with don't seem to be there. Looking down in the files I see sync GoogleCalendarSyncAdapter.apk, GoogleContactsSyncAdapter.apk and ContactsProvider.apk, but not the Calender.apk, CalendarProvider.apk or Contacts.apk.
Anybody know why these are missing and how I can get them working?
Thanks.
Chris Bowerman said:
I'm pretty new at this, but I was able to follow Manual Nooter pretty easily and seem to have most things working.
I just have one question (and pardon if it's already been answered somewhere); the usual Google Calendar app and the usual Google Contacts app that I'm familiar with don't seem to be there. Looking down in the files I see sync GoogleCalendarSyncAdapter.apk, GoogleContactsSyncAdapter.apk and ContactsProvider.apk, but not the Calender.apk, CalendarProvider.apk or Contacts.apk.
Anybody know why these are missing and how I can get them working?
Thanks.
Click to expand...
Click to collapse
I'll be looking into Calendar and Contacts later this month if someone else doesn't get to it first as I have finals coming up.
I'm using MN 4.4.28 on 1.2 and have problem downloading B&N magazines (both those that were archived and new ones on subscription).
Message is "An Unexpected Error Occurred. Internal Error: Exception executing the command" for an attempt to update a subscription and "Unable to Download. Internal Error: Exception executing the command" for an attempt to download an archived magazine. Any way to fix?
See Later Post: MN 5.3 fixed the problem.
execdab said:
I'm using MN 4.4.28 on 1.2 and have problem downloading B&N magazines (both those that were archived and new ones on subscription).
Message is "An Unexpected Error Occurred. Internal Error: Exception executing the command" for an attempt to update a subscription and "Unable to Download. Internal Error: Exception executing the command" for an attempt to download an archived magazine. Any way to fix?
Click to expand...
Click to collapse
Uhm... not sure what could be causing this. Doubtful it has anything to do with MN/AN will look into it if anyone else has had this issue.
Flashed back to stock (using CWM backup). Magazines worked fine in stock. Ran MN 5.2 and problem is fixed! Thanks.
Is there a thread somewhere on XDA that gives any updates on when autonooter for those who want to wait for this program
execdab said:
I'm using MN 4.4.28 on 1.2 and have problem downloading B&N magazines (both those that were archived and new ones on subscription).
Message is "An Unexpected Error Occurred. Internal Error: Exception executing the command" for an attempt to update a subscription and "Unable to Download. Internal Error: Exception executing the command" for an attempt to download an archived magazine. Any way to fix?
Click to expand...
Click to collapse
I'm having this problem as well. Can't seem to interact with the B&N Store at all without getting some kind of "An Unexpected Error Occurred". Can't try to go back at the moment as I'm away from home. Anybody have another idea, otherwise just thought I'd report it in case it is something to be looked into.
Thanks.
Chris Bowerman said:
I'm having this problem as well. Can't seem to interact with the B&N Store at all without getting some kind of "An Unexpected Error Occurred". Can't try to go back at the moment as I'm away from home. Anybody have another idea, otherwise just thought I'd report it in case it is something to be looked into.
Thanks.
Click to expand...
Click to collapse
Try the later (5.2) MN. Fixed the problem for me.
report from a newbie - i am really new to xda, and a new owner of nc. i did a manual update in my stock NC from 1.1 to 1.2 last night, then seeing that autonooter was only approved for 1.1, i decided to try ManualNooter 4.5.6 (For Stock 1.2) (link below) It worked just fine for me. THANKS-ALL!
http://forum.xda-developers.com/showthread.php?t=1054027
Manual Nooter
First ---Thanks to everyone who's been working on getting this out so quickly. Even with the initial Market bugs it was way better then the stock option of 1.2.
I've updated the MN as it comes out and everything works just as others posted. Some apps from Market need the SD card removed to install and others install with no problem and sometimes all it takes is 'clearing data" to make it work. I also installed the NookHome app and love it!
Question: News and Weather which came with the .zip doesn't load at all. I tried clearing data - doesn't make a difference. When I click on the icon it tries to load but then just reverts to the home screen. Can't uninstall it either, no response when I click on uninstall (wanted to re-install to try fixing it that way). Any ideas what else I can try?
Manualnooter --News and Weather
I have the same problem. Tried to open News and Weather it turn screen black and went back to home screen.
Anybody have solutions for this?
TIA
I am definately a novice at rooting. The Nook Color is my first experience with an Android device, and I was able to run Manual Nooter fairly easy. Besides the usual obstacles of learning what CWM, root, flash, ROM, etc meant, and learning to burn an .img file on an SD card, it was fairly easy. I'm already looking beyond it, to see what the NC is capable of. Now if only I could get phiremod v6.3 to work....
I cannot get the market to install any applications, though it is working and searchable.
I rooted my nook2e with Xboxexpert's nooter.img and script package, and updated the vending.apk with no results. I ran touchnooter 1.6.24, and now the market works and is searchable, but none of the apps i pick will download, or install.
It's been incremental gains here and there though this whole process... just one last step to get market working!
(also, the youtube app wont run, and gmail says it must be synced with an account, but in the Settings tab for the nook, you cannot add any of the facebook/twitter/google account information, it just flashes the screen and goes back to the previous setting screen.
I had a similar problem. If you can get vending.apk it will fix the download problem
klong81506 said:
I had a similar problem. If you can get vending.apk it will fix the download problem
Click to expand...
Click to collapse
This is the one i updated to, didnt fix the downloading problem.
http://forum.xda-developers.com/showpost.php?p=15084704&postcount=51
ok, so, i fixed it, and here's how!
I cleared the nook, using the menues to do a factory memory wipe...
Then i put TouchNooter on an SD card, and installed that. Then i ran XboxExpert's batch script to install apps and change settings etc. Then i put the updated Vending.apk file on the sd card and ran that update twice... the first time it made the market not work at all.
but now it works and downloads and searches and everything!
I recently bought a new Nook N2E. It actually came with firmware 1.0.0 strangely enough. I did slap 1.1.0 on there.
I want to root this baby. My question is should I revert to 1.0.0, upgrade to 1.0.1, root with touchnooter and proceed with everyone else, or just manually root it noogie style? Or I could stay at 1.1.0 and rip out of touchnooter the things that are not working. I'm just looking for opinions.
volwrath said:
I want to root this baby. My question is should I revert to 1.0.0, upgrade to 1.0.1, root with touchnooter and proceed with everyone else, or just manually root it noogie style? Or I could stay at 1.1.0 and rip out of touchnooter the things that are not working. I'm just looking for opinions.
Click to expand...
Click to collapse
There's no simple answer to that.
In regards to Market things are a little messy on 1.1.0 right now, but we're working on it.
Some people claim they got Market working on 1.1.0, but GabrialDestruir is having trouble with finding a reliable solution for that and so do I.
If you absolutely want Market right now, then save you the trouble and go back to 1.0.1 + TouchNooter 1.6.24
If root is all you need atm, then just check out the updated uRamdisk thread.
ros87 said:
...If you absolutely want Market right now, then save you the trouble and go back to 1.0.1 + TouchNooter 1.6.24....
Click to expand...
Click to collapse
ros87:
If he does go back to 1.0.1/TouchNooter 1.6.2.4, won't the B&N update eventually download automatically and force the unit to update?
there is a way how to (successfully?) block OTA updates, just google it out. It is simple sqlite3 db update.
Thanks for the replies. I decided that since Ive never seen the N2E running android, I would go 1.0.1 and Touchnooter and it worked like a charm. Only thing I cant figure out how to do is change Google Sync from Push to Manual
Updated my rooted Nook touch to Ver 1.1.0, after reverting to factory version as received. Used the two modified files in the SD image, and after the third boot it worked. I get Youtube, Gmail, and Market successfully. Now I cannot install any non-market apps. Somewhere I saw a menu and accepted permissions which I thought would allow installation of many non-market APK's. Guess I need some help, but close to success.
Jim
"Install blocked" message appears "for security, your phone is set to block... Android Market", I had earlier checked accept non-market apps.
jmgazer said:
Updated my rooted Nook touch to Ver 1.1.0, after reverting to factory version as received. Used the two modified files in the SD image, and after the third boot it worked. I get Youtube, Gmail, and Market successfully. Now I cannot install any non-market apps. Somewhere I saw a menu and accepted permissions which I thought would allow installation of many non-market APK's. Guess I need some help, but close to success.
Jim
Click to expand...
Click to collapse
NookColorTools, even if non market apps is checked, uncheck and check it gain.
I've had success three times rooting it with full Market and search.
Here's what I did:
1) Backed up with noogie.img on SD and Roadkil's DiskImage.
2) Used nookRestore on SD to restore /system.
3) Erased and Deregistered to wipe /data.
4) Skipped B&N registration (I don't need/want it).
5) Applied 1.1 firmware update.
6) Used TouchNooter 1.6.24 on SD, modified with 1.1 uRamdisk and framework.jar.
7) Triple booted TouchNooter (gave it five minutes each time), removed card, rebooted, skipped Google registration.
8) Youtube --> GMail --> Market. Downloaded a program in Market.
9) Installed SearchMarket and ADB Wireless Widget. Enabled non-market apps with NookColorTools. Uninstalled YouTube (someone said this helps).
10) Used ADB over wireless to push Vending.apk from here. SearchMarket is no longer needed.
My original thread (with links and other details) is on MobileRead in the nook sections. As ros87 noted, GabrialDestruir hasn't got it to work, but I see no reason why it shouldn't if I've done it successfully on different devices. My guess is that some part of the process is being done differently.
TouchNooter's three boots went like this for me:
1st) Infinite loop of nook dots. I reset after about five minutes.
2nd) Complete freeze either on "Rooted Forever" or nook dots screen.
3rd) Success! and boot to Android Welcome. From here I removed the SD and rebooted.
I've been reading a lot of people reporting that they first tried TouchNooter and this failed, they then had to restore and try a different rooting method. Can this maybe mean that TouchNooter doesn't work anymore for some reason? Are there people which have recent successes with it?
I got it!
I tried it and failed, and panicked at first. I then realized I could reboot the device, but nothing happened still. ros82 has a great thread with backups, shown here
Anyway, I took the recovery option one, and put it into my NOOK Simple Touch and rebooted. It said resetting to factory, wait till done. When it finished, I was rooted for some reason!
Apparently that "restore to factory" doesn't get around to restoring the boot partition.
I can confirm TouchNooter works - I used 2.1.31 to root a new nook touch that I bought over the weekend (twice).
The device was running 1.1.0 out of the box and I had updated to 1.1.2 before the first attempt. That worked but "device info" showed 1.1.0 after the root, and I couldn't force update the firmware after. Market was working after the 1-day wait as well. I used the 8 hard resets to restore the device and tried again on the stock firmware. Same results. I ended up using the MinimalTouch method after updating to 1.1.2 to root while retaining the firmware update.
Touchnooter did NOT work for me.
I have a new NST, came with 1.1.1 stock, then I manually upgraded to 1.1.2. Registered to B&N, have downloaded several books and transferred some epub and pdf files.
Then tried to root:
Upon starting up the NST with the Touchnooter SD image I created, I got the touchnooter instruction screen, then 20 seconds later did see a quick flash to black, then immediately the Nook startup screen appeared with the 5 dots along the bottom.
The screen stayed there with only the first dot black and it hung.
Waited awhile....10 or 15 min.
Took out the SD card, powered the Nook off then back on without the Touchnooter SD card in it.
The Nook was NOT rooted. Went right to stock Nook screens with my books loaded.
Tried it 2 more times, same result.
WHY doesn't this work on my Nook?
didnt work for me either
looks like touchnooter worked for me, but then on reboot i dont get adw option, just normal nook boots.. tried also salsicha nooter, same thing, why doenst it work for me!!!!
Touchnooter not working
I am sure there is something I can do to get this working, no? Had firmware 1.0.1, used the Touchnooter 2.1.31 booted and saw the little android icon and I started the process. Skipped the sign in and enabled location service, then flash of the screen and back to nook reader home. Restart, no Android icon, just e-reader home screen. Updated firmware to 1.1, retried touchnooter 2.1.31, still nothing comes up on startup, just acts like an e-reader, SD card inserted or not.
Sounds to me like some of you are either missing the prompt to select the launcher on 1st restart, or it's not working for some reason. Do you see the little Button Savior button on the right of the screen? If everything worked, you should be able to use that to get back to ADW. If that doesn't work, your default launcher may be set to B&N's home screen. I'd recommend a complete wipe and try again. TN has worked very well for me on 1.1.x, but be sure to set ADW as your home default on 1st launch if that's what you want.
If you have updated to 1.2, be sure to read around before trying to root. Things have changed a bit, apparently.
No button savior
bobstro said:
Sounds to me like some of you are either missing the prompt to select the launcher on 1st restart, or it's not working for some reason. Do you see the little Button Savior button on the right of the screen? If everything worked, you should be able to use that to get back to ADW. If that doesn't work, your default launcher may be set to B&N's home screen. I'd recommend a complete wipe and try again. TN has worked very well for me on 1.1.x, but be sure to set ADW as your home default on 1st launch if that's what you want.
If you have updated to 1.2, be sure to read around before trying to root. Things have changed a bit, apparently.
Click to expand...
Click to collapse
Arrgg. Unfortunately no, I do not see the button savior on the right. I had it rooted a few months back and restored it to the plain e-reader before trying to re-root again. I thought I did a complete wipe by updating to 1.2. Should I go back to 1.1 and then try the µSD?
Cannot root my Nook touch
shadylady said:
I can confirm TouchNooter works - I used 2.1.31 to root a new nook touch that I bought over the weekend (twice).
The device was running 1.1.0 out of the box and I had updated to 1.1.2 before the first attempt. That worked but "device info" showed 1.1.0 after the root, and I couldn't force update the firmware after. Market was working after the 1-day wait as well. I used the 8 hard resets to restore the device and tried again on the stock firmware. Same results. I ended up using the MinimalTouch method after updating to 1.1.2 to root while retaining the firmware update.
Click to expand...
Click to collapse
I've tried auto-nooter and touchnooter and nothing I try works. My Nook is running version 1.1.0 and WAS rooted before but refuses to root now. I have the nooter image (linux using dd if= method) on the sd card but rebooting the device with the nooter card in it never ends with a rooted nook. It simply boots up normally and then complains that the sd card needs to be formatted. I've tried restting/deregistering the nook and trying again. No dice. This thing will not root.:crying:
praedoratrebates said:
I've tried auto-nooter and touchnooter and nothing I try works. My Nook is running version 1.1.0 and WAS rooted before but refuses to root now. I have the nooter image (linux using dd if= method) on the sd card but rebooting the device with the nooter card in it never ends with a rooted nook. It simply boots up normally and then complains that the sd card needs to be formatted. I've tried restting/deregistering the nook and trying again. No dice. This thing will not root.:crying:
Click to expand...
Click to collapse
- for NST FW 1.2 upgraded from NST with recovery image 1.1 only 'tinynooter' will work (as for now) . You will gain root + adb but not the Market/Google Play.
I
I.1 - do a full recovery (6 failed boot's in a row [reset the device just after it starts booting])
I.2- upgrade to 1.2 manually
I.3- run tinynooter from CWR.
or
II
II.1 - wipe system partition using CWR
II.2 - install 1.1 FW using CWR (from cwr_1.1_zip)
II.3 - upgrade to 1.2 manually
II.4 - apply 'tinynooter' using CWR
same procedure if you just want to root 1.1.
- I.1 or II.1 + II.2 + 'Touchnooter' or any other 'nooter' that used to work
----------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------
I.1 - http://nookdevs.com/Nook_Simple_Touch_restore_to_stock
I.2 / II.3 http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/
I.3 / II.4 http://forum.xda-developers.com/showpost.php?p=26015994&postcount=1
II.2 http://code.google.com/p/nst-recovery/downloads/list
Worked like a charm...after
I was having problems getting touchnooter to work. Running linux and using the dd command I found out I was screwing up the dd command slightly. I'd place the sdcard in my card reader and it would show up on my system as /dev/sdb1 (for instance) so I did the dd if=touchnooter.img of=/dev/sdb1 command but this produced a card that failed to boot even though the rooting software was clearly installed. Changing it to dd if=touchnooter.img of=/dev/sdb fixed the issue and a couple of days of problems rooting my nook became instant root upon reboot.
Now the problem I'm having is installing apps (or finding them). I try and install a google android app and it refuses to install saying my system security isn't setup to allow unsigned (or something like that) apps. I cannot find any security settings anywhere in what is provided by touchnooter that changes this. Also, while I can find a kindle reader app without issue in he amazon app store with a browser on my computer, it refuses to appear when I search the amazon app store from the rooted nook! WTF?
There seems to be a number of issues, in fact. The Opera Mobile app doesn't function, I cannot get gmail set to sync automatically, and I cannot get my yahoo email setup to work. Add to that the inability to install any apps beyond the base provided by touchnooter...I'm thinking of trying again only using the auto-nooter instead.
praedoratrebates said:
Now the problem I'm having is installing apps (or finding them). I try and install a google android app and it refuses to install saying my system security isn't setup to allow unsigned (or something like that) apps. I cannot find any security settings anywhere in what is provided by touchnooter that changes this. Also, while I can find a kindle reader app without issue in he amazon app store with a browser on my computer, it refuses to appear when I search the amazon app store from the rooted nook! WTF?
There seems to be a number of issues, in fact. The Opera Mobile app doesn't function, I cannot get gmail set to sync automatically, and I cannot get my yahoo email setup to work. Add to that the inability to install any apps beyond the base provided by touchnooter...I'm thinking of trying again only using the auto-nooter instead.
Click to expand...
Click to collapse
I suggest updating your nook to FW version 1.2
root with tinynoot as osowiecki shows in the previous post
you can then use adb to install apps
tinynoot will install nookcolortools- open this - and deselect and then reselect install non-markets apps.
this will allow you to install non-market apps
tinynoot doesn't include any google apps.
instead of gmail, I use k9mail - with this I am able to set up my gmail and other emails - all in one app.
Hi,
I just got an alert for update to 1.2.2 for NST and NSTG ...
Dear Customer,
We are writing to you regarding a necessary software update for one or more NOOK Devices registered to this email address.
On June 29th, 2018, Barnes & Noble will be upgrading the security software used for data encryption, known as Transport Layer Security (TLS), from Version 1.1 to Version 1.2.
Our records show that your NOOK does not have the most recent NOOK software version, which includes a very important new security update. If you do not complete this update your NOOK service will be interrupted. The following NOOK Devices require an update to be compliant with TLS Version 1.2:
NOOK Color
NOOK Tablet
NOOK HD
NOOK HD+
NOOK Simple Touch
NOOK Simple Touch with GlowLight
NOOK GlowLight
If your NOOK is updated before June 29th, 2018, you should not experience any interruption in your NOOK’s performance.
IF YOUR NOOK IS NOT UPDATED BEFORE JUNE 29TH, YOU WILL NOT BE ABLE TO MAKE ANY PURCHASES OR MANAGE THE NOOK CONTENT IN YOUR LIBRARY UNTIL THE UPDATE IS INSTALLED.
To verify the necessary software version for your NOOK, and install the TLS 1.2 security update on your NOOK, click here to locate the software update file associated with your device and follow the installation instructions on the page. Once installed, your NOOK will continue to function as expected.
If you have any questions, feel free to contact us at 1-800-THE-BOOK (1-800-843-2665) Monday-Friday 8AM-11PM ET and Saturday-Sunday 9AM-11PM ET.
Sincerely,
Barnes & Noble
So what do the experts advise we do ?
@Renate NST, @nmyshkin, @pinguy1982, @yattaro, ... experts for the NST/NSTG ???
my first reaction is ... can i update to 1.2.2 and still be able to create a 'dd' backup image of this update using noogie boot backup method ... will the noogie sd card allow backing up this new version as well ?
If so MY first order of business would be to ... take a noogie backup of the current state of your devices ... factory reset ... update to this latest update version 1.2.2 ... register device ... test your nook library for full functionality ... take a noogie backup of this new version ... and save this update !!!
We can then revert back to the first backup(the current state of our devices) and use the devices as we are using currently ...
that way we will have the update saved before 29th June deadline and depending on what course the active experts for our devices take !!!
Experts advise ?
OK, so FINALLY a downloadable update zip. I'm going to try this on a rooted NST (my spare for experiments) to see what happens. I suspect it will fail. Stay tuned.
Edit: Well, er..... I got distracted so if there were messages I did not see them. What I have now is a device that appears to function but has some issues. For example, in Settings>Device Info>About Your Nook, the "Software Version" is "unavailable". Double tap in the Library (I have one free B&N book there) brings up essentially a blank page with the message "Service Unavailable". So running the update from a local zip file on a rooted device is not going to work.
In my other posts regarding this update I noted that you can root a 1.2.2 device using Nook Manager with a few changes, but there are issues with installing some apps afterwards. That problem is--at least for now--beyond my pay grade. The real problem is that for those wishing to maintain B&N function without losing their customizations, the clock is ticking. It's possible that even if you don't buy from B&N but haven't disabled all their stuff because you want to keep the Library/Reader/Dictionary functioning the system is about to become annoying. I think I have seen the beginning of this already with random error messages about B&N servers even though I disabled automatic OTA updates.
We need a fix.
Update
I had a previous backup of an unregistered 1.2.2 NST so I returned to that, rooted with a modified NookManager, and tried to install all of the apps I use on my "real" NST. What I found was that everything installs (and, I assume, runs) except for Tasker 1.3.3u2 and Opera Mobile 12.1. Even Tasker-generated apps like my Screenshot and USB Audio install and run, but not Tasker itself.
I tried "sneaking" these apps in via adb. I got a [install_parse_failed_unexpected_exception]--and no install. I tried Opera Classic 12.9 with the same result.
When I originally tried this I posted a logcat and @Renate NST remarked that some apps were trying to use SHA-1 signatures and that the NST would only accept MD5. She suggested resigning the offending apps. Exactly why the new FW 1.2.2 was throwing up this problem when the old 1.2.1 did not, I don't know.
I've never had any luck with signing apps (or resigning them, for that matter). I really would like to have both Opera Mobile (the only decent browser for the NST) and Tasker both working.
Anyone with app resigning experience/luck?
Victory!
OK, so now we've got something!
Clearly most apps will install and run without issue. I found two (Taker and Opera Mobile) that would not. Problem solved: head on over to the PlayStore (you can use the YalpStore directly on the NST/G) and install ZipSigner. Copy your non-installing apk files to the NST/G and run ZipSigner. Select the input file (eg. Opera_Mobile_12_1_Generic_Opera_Armv5v7.apk) and essentially everything else can be accepted with defaults.
A new copy of the apk file is generated with a new signature that will allow installation and will run on FW 1.2.2!!!!! And it's so easy
At least it works for Tasker and Opera Mobile. YMMV.
Of course, if you want to update to FW 1.2.2 to maintain B&N function or to avoid potential misbehavior when B&N servers can't be contacted, you will have to start from stock...alas.
I have updated my original post on adapting NookManager to work with 1.2.2: https://forum.xda-developers.com/nook-touch/general/nst-nstg-fw-1-2-2-update-t3785566
I'm not sure about all of the compatibility issues with APK signing.
There was somebody who was having problems with SHA-1 signing not working on some software on some device.
At some point I switched signing my apps with MD5 to signing with SHA-1.
I've never had a problem installing those apps on my NST.
Code:
jarsigner.exe -digestalg SHA1 -sigalg SHA1withRSA -storepass [i]mysecret1[/i] -keypass [i]mysecret2[/i] [i]myapp[/i] [i]mystore[/i]
Signatures are additive. If you want to strip them you could use a ZIP tool or the unsign.exe tool in my signature.