Related
Hi,
I rooted my Nook Color (version 1.0.1).
Thereafter I Updated my Nook Color to version 1.1.
Then I changed wifi settings to accept adhoc wifi.
Then I loaded a few android apps from the Market place.
Everything was working till BN decided to wipe off all this on April 26th when my Nook got reset (is it because of a bug associated with version 1.2?). All my books and apps got wiped off. I had to deregister the device to get the access to BN books.
Thereafter I tried rooting it again to get the Market Place going and application loaded. But it wouldn't work.
I tried updating to version 1.2 - that too didn't work.
Only thing I can do with it now is just read BN books.
No access to other apps or the books I purchased from Amazon using Kindle app for Nook.
Can anyone help me with getting this rooted properly and get the Nook working with Market place with either version 1.1 or version 1.2?
Appreciate your assistance.
thanks.../ br.darshan
Managed to push it to v 1.2
Managed to wipe and install v 1.0.1 and then update v 1.2
Then installed CWM and then used the Manual Nooter. The system works fine. I can access Market Place. However the device itself is not recognized by the Market place (its shown as unknown device with no maker or model name) and as such I am unable to download any apps from the market place.
Any body knows whats going on? How do I re-register or update the market place to recognize the Nook Color properly?
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.
Has anyone been able to install the new version of Kindle (3.4.0) for Android on a rooted Nook Touch? It's supposed to work for Android 2.1+, but the update doesn't show up in the Market for me, and if I uninstall Kindle entirely, and then re-download and reinstall it, I get version 3.2.0 again. If I try to sideload the apk, I get a Parse Error.
I'd really love to get the updated app installed, because it shows the page numbers from the original book, which would be useful leading my students through a textbook.
OK, then, let me ask a different question: has anyone successfully installed the new Kindle for Android version, or am I the only one with a problem?
Seriously, has no one else tried to install the new version of Kindle for Android? You can tell what version you have by looking at the app in Titanium Backup. It's a serious bummer that I bought this Nook because I could easily read both Nook and Kindle e-books, and less than two months later the thing won't install the latest version of Kindle.
MTKnife said:
Has anyone been able to install the new version of Kindle (3.4.0) for Android on a rooted Nook Touch? It's supposed to work for Android 2.1+, but the update doesn't show up in the Market for me, and if I uninstall Kindle entirely, and then re-download and reinstall it, I get version 3.2.0 again. If I try to sideload the apk, I get a Parse Error.
I'd really love to get the updated app installed, because it shows the page numbers from the original book, which would be useful leading my students through a textbook.
Click to expand...
Click to collapse
3.2.0 is the version from market and works on all nook touch. 3.4 is from Amazon appstore and is DRM protected. The apk will only installed on a Nook touch signed in with the orignal amazon account.
fpga_guy said:
3.2.0 is the version from market and works on all nook touch. 3.4 is from Amazon appstore and is DRM protected. The apk will only installed on a Nook touch signed in with the orignal amazon account.
Click to expand...
Click to collapse
No, 3.4.0 is also in the Android Market--I know that because 1) the new version was announced on Android Central (and a lot of other places), 2) the version number is listed in the Android Market description, and 3) I successfully downloaded it, from the Market, onto my phone, and verified the version number in Titanium Backup. I also just verified, on my phone, that page numbers work (though you have to tap the bottom of the screen or select "Go to" to see them).
Good idea to try the Amazon Appstore version--but unfortunately, Kindle for Android doesn't even show up in the Appstore for my Nook. That does lead to another question, though: has anyone successfully downloaded and installed Kindle 3.4.0 from the Amazon Appstore?
Actually, I just tried another tactic, and transferred the 3.4.0 Titanium Backup files to the Nook. I first tried restoring 3.4.0 over the top of 3.2.0--this appeared to be successful, but when I opened the app it was still 3.2.0. I then uninstalled 3.2.0 and tried the restore of 3.4.0 again, and it simply hangs: it's apparently, for some reason, not compatible with the Nook Touch. I wonder if there's some way that could be fixed?
Here's the link to the Amazon Appstore APK, courtesy of Amazon itself!
Googie2149 said:
Here's the link to the Amazon Appstore APK, courtesy of Amazon itself!
Click to expand...
Click to collapse
Thanks. I have the Amazon Appstore installed--that's not the problem. The problem is Kindle for Android, which doesn't show up in the Amazon Appstore (and I have copies of the APK of Kindle for Android). I am able to find and install other apps from the Appstore, though for some apps I get a Parse Error when I try to.
MTKnife said:
Thanks. I have the Amazon Appstore installed--that's not the problem. The problem is Kindle for Android, which doesn't show up in the Amazon Appstore (and I have copies of the APK of Kindle for Android). I am able to find and install other apps from the Appstore, though for some apps I get a Parse Error when I try to.
Click to expand...
Click to collapse
I have BN 1.1.0 for the Touch. Kindle 3.2 shows up when I go to Market - not Android Central but the google market. Kindle 3.4 shows up when I go to Amazon Appstore. My understanding is that for Market, only apks that install shows up.
What version of Touch are you on and how did you root the Touch?
I'm using SalsichaNooter, though I tried to install the APK under MinimalTouch (which is I what I rooted with this time, after doing a factory restore). It is definitely not the case that all apps that show up in the Appstore can be installed: for example, Application Folder Pro is one I've purchased (for my phone) and that shows up on the Nook, but I get a "Parse Error" when I try to install it.
And yes, you're right that it says 3.2 in the Android Market, under the actual version number; I was looking instead at the changelog, which says 3.4. However, that's only for the Nook: for my Evo 3D, the version that shows up in the Android Market is 3.4.
Before I go putting another ROM on this thing, have you actually been able to install version 3.4.0 of Kindle for Android from the Amazon Appstore, and if so, what ROM are you using?
If I install the Kindle app from the Android Market on my NST running B&N 1.1.0, I get v3.2.0.35. If I install it on my NC running B&N 1.4.1, I get 3.4.0.156.
The NST is only running 2.1 Eclair, while the NC is running 2.2 Froyo. On the Kindle Market page, it says the current version "varies with device", so I suspect that's the underlying issue
The rooters don't change the actual ROM you're running. Not sure what you mean by another ROM.
Chances are it's not running properly because it needs Froyo or higher, meaning that the NST is just not compatible no matter what you try.
bobstro said:
If I install the Kindle app from the Android Market on my NST running B&N 1.1.0, I get v3.2.0.35. If I install it on my NC running B&N 1.4.1, I get 3.4.0.156.
The NST is only running 2.1 Eclair, while the NC is running 2.2 Froyo. On the Kindle Market page, it says the current version "varies with device", so I suspect that's the underlying issue
The rooters don't change the actual ROM you're running. Not sure what you mean by another ROM.
Click to expand...
Click to collapse
All of the custom ROM's available for the Nook Touch are the same version of Android, 2.1 (Eclair), but there are several different ROM's available (four that I know of): in the usual Android parlance, if the firmware is modified at all (even though it's based on the original firmware), it's called a new ROM. When you root your Nook, you're not merely rooting it, but actually changing some of the stuff in the original ROM, including, for example, the framework files--if you look inside the MinimalTouch package, for example (since that one comes as a ZIP file, it's easy to look at), you'll see all the files that are changed.
However, as a later poster noted, the problem seems to be that Kindle 3.4 runs only on Android 2.2+, rather than Android 2.1+; Amazon doesn't appear to have bothered to document this, and that's the source of my confusion.
Safe to say, then, "putting another ROM on" won't fix this problem. You'll still be running 2.1 Eclair, no matter which rooter you try. I think you're stuck with the older Kindle version on this device, at least for now. I'm not aware of any ongoing efforts to put Froyo on this device.
MTKnife said:
All of the custom ROM's available for the Nook Touch are the same version of Android, 2.1 (Eclair), but there are several different ROM's available (four that I know of): in the usual Android parlance, if the firmware is modified at all (even though it's based on the original firmware), it's called a new ROM. When you root your Nook, you're not merely rooting it, but actually changing some of the stuff in the original ROM, including, for example, the framework files--if you look inside the MinimalTouch package, for example (since that one comes as a ZIP file, it's easy to look at), you'll see all the files that are changed.
However, as a later poster noted, the problem seems to be that Kindle 3.4 runs only on Android 2.2+, rather than Android 2.1+; Amazon doesn't appear to have bothered to document this, and that's the source of my confusion.
Click to expand...
Click to collapse
They're not different ROMS. They just aren't. All you're doing is rooting the device, not replacing the ROM.
I rooted my Nook a while back (still even on the 1.0.0 firmware), but only now started looking into updating it. I saw the update for the Kindle on my Sensation versus the NST, but I'm not sure I see a compelling reason to try to force the update (though a real page numbers would be nice).
Is the hardware even capable of running Froyo? Maybe it's just the e-ink screen, but it seems slow enough just with Eclair.
hardware is capable of running froyo but there is no froyo rom for NST. :-D
It's already been stated, but to summarize:
The new Kindle app needs Android 2.2 and above, the NST is only at 2.1.
There are no roms for this device at the moment, and probably never.
See attached older version that I just installed on a Simple Touch no problem.
3.2.0.35 shows up in the Market on my rooted NST. It's just the newer version that doesn't.
Newspapers
I have recently discovered that reading newspapers/magazines is only really possible with the older versions (Kindle-2.0.5.103970165.apk : http://www.freewarelovers.com/android/app/kindle) because the overview page of a multistory object on the newer versions 3+ does not accept gestures (swipe up and down are ignored or interpreted as clicks) so it is impossible to scroll. The gestures work fine in every other part of the program just not in the overview. The only apparent downside of version 2 is that there is no dictionary which I sometimes miss.
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.
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.