Related
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.
hey, I am new to the tablet world, I tried to search for this and look in the recent post and didnt really find the answer I was looking for....
So if I buy a new or refurbished Nook Color right now from B&N... will I be able to root it?!
this article is old... so I am not sure if this is the case?
any advice Please
WARNING - READ THIS FIRST: Barnes and Noble has introduced a new hardware revision which bricks your unit if you install their official 1.0.0 Firmware (A step needed to root). As of right now, Nooks with serial #s starting with 1003 (running firmware 1.5) cannot be rooted, and should NOT be attempted. See nookdevs New_Hardware_Revision for more details before you think of trying this!
Click to expand...
Click to collapse
from:
nooktalk.net/news/time-to-hack-root-your-nook
THANKS!
cant post the regular link yet
Just buy from eBay or Craigslist you'll find it cheaper n rootable
Sent from my NookColor using XDA Premium App
Well, where is the difference if I buy it new from eBay?! How is it more or less rootable...? If it is new it is new No matter where it comes from or?!
and 135$ for refurbished didn't seem bad... Or?!
Sent from my PC36100 using XDA App
First.... those may be Nooks and NOT Nook Colors... The newest firmware for Nook Color or Nook Tablets is 1.4.1 and you reference FW ver 1.5.
Also, I don't know of any NC's or NT's with serial numbers below 2000 first 4 digits.
Additionally, with the newer rooting tools available, you don't need to install anything prior to 1.4.1 to root them.
alexwick said:
[...] From:
nooktalk.net/news/time-to-hack-root-your-nook
Click to expand...
Click to collapse
At the very top of that article, it states:
Last Updated on Wednesday, 29 December 2010 12:54
You might find reading more recent articles a bit more revealing. A few things have happened since 2010.
I am aware the article is old... So short answer...
A new bought nook can be rooted?!?
Sent from my PC36100 using XDA App
Short answer, yes.
My base FW is 1.0.0. I'm running the 20120217 build of Mirage-Kang from eMMC.
I can't imagine how it could get much more rooted than this unless it would be to follow the directions to root it to the letter but if I did that then I wouldn't be much of an Asshole and I am a journeyman Asshole so there you have it.
Oh, and I don't feel terribly compelled to take it out of the case to look at the serial.
MISRy said:
Short answer, yes.
My base FW is 1.0.0. I'm running the 20120217 build of Mirage-Kang from eMMC.
I can't imagine how it could get much more rooted than this unless it would be to follow the directions to root it to the letter but if I did that then I wouldn't be much of an Asshole and I am a journeyman Asshole so there you have it.
Oh, and I don't feel terribly compelled to take it out of the case to look at the serial.
Click to expand...
Click to collapse
But do you have a Nook... or a Nook Color?
I mean yeah the Nook is rootable... but I didn't know a Mirage Kang was done for it.
Just ordered a refurbished nook color for 135$ hope will get it rooted fine... Which is the best thread for noobs here to get it rooted?!
Sent from my PC36100 using XDA App
alexwick said:
Just ordered a refurbished nook color for 135$ hope will get it rooted fine...
Click to expand...
Click to collapse
Since there is a manual nooter for the 1.4, there's no problem rooting it.
Which is the best thread for noobs here to get it rooted?!
Click to expand...
Click to collapse
Which rooting do you wish to do? If you want to run the stock B&N apps side by side with apps downloaded from the B&N market, then first register the refurbished system with B&N, then go to NC developer forum and look in "[NC][1.4.1] ManualNooter 5.02.19". That's a couple of minor version steps past the one I used, but it looked like its got it all pulled together from the three different sources of info I used last month.
I wanted to keep Nook Comics support in the stock ereader, so I opted for the manual nooter.
If you want to do a CM7/CM9/MIUI root, which installs alternate firmware for the system instead of modifying the existing firmware to allow Android market apps ... well then, I dunno, as after experimenting with a CM7 sd sidecard, I opted for the manual nooter approach. I'd look in the developer forum for the most recent thread with detailed install instructions for the firmware I wanted to install.
Pretty off topic, but this helped me when I needed to exchange a nook color that I had lost the box for. If you need your serial number, it is inside the flap that covers the micro SD slot.
There are other ways to find it, but if you are on the phone with support and a rooted nook, this is a useful thing.
I also just bought a refurb Nook Color. It is running 1.3.0 out of the box. I want to root it then install CM7. However I can't find any clear posts on how to. Either they are all for earlier FW or 1.4. Should I update to 1.4 before Nootering? If so which MNooter should I use? Or is it recommended to just Nooter 1.3? Again which Mnooter should I use for 1.3?
Thanks
BruceMcF said:
Since there is a manual nooter for the 1.4, there's no problem rooting it.
Which rooting do you wish to do? If you want to run the stock B&N apps side by side with apps downloaded from the B&N market, then first register the refurbished system with B&N, then go to NC developer forum and look in "[NC][1.4.1] ManualNooter 5.02.19". That's a couple of minor version steps past the one I used, but it looked like its got it all pulled together from the three different sources of info I used last month.
I wanted to keep Nook Comics support in the stock ereader, so I opted for the manual nooter.
If you want to do a CM7/CM9/MIUI root, which installs alternate firmware for the system instead of modifying the existing firmware to allow Android market apps ... well then, I dunno, as after experimenting with a CM7 sd sidecard, I opted for the manual nooter approach. I'd look in the developer forum for the most recent thread with detailed install instructions for the firmware I wanted to install.
Click to expand...
Click to collapse
Can I not install cm7 on the SD and the regular b&n system when boot from internal memory?!
Optimus V Prime said:
I also just bought a refurb Nook Color. It is running 1.3.0 out of the box. I want to root it then install CM7. However I can't find any clear posts on how to. Either they are all for earlier FW or 1.4. Should I update to 1.4 before Nootering? If so which MNooter should I use? Or is it recommended to just Nooter 1.3? Again which Mnooter should I use for 1.3?
Click to expand...
Click to collapse
You do not need to root the B&N firmware before loading CM7. You do need to decide whether you want to run CM7 on internal eMMC or external SD. If you plan to install CM7 to eMMC, you will over-write the B&N firmware, so rooting it is pointless. Once you've decided that, we can point you in the right direction.
There are also guides here on rooting B&N firmware that you can locate with a bit of searching.
---------- Post added at 03:18 PM ---------- Previous post was at 03:14 PM ----------
alexwick said:
Can I not install cm7 on the SD and the regular b&n system when boot from internal memory?!
Click to expand...
Click to collapse
Yes, you can.
alexwick said:
Can I not install cm7 on the SD and the regular b&n system when boot from internal memory?!
Click to expand...
Click to collapse
Yes, as I said, that's the setup I was using when I decided I prefer a manual nooter. Among your choices, you can:
(1) Replace the stock firmware with an alternative, such as CM7
(2) Run CM7 off a booting SD card and run stock B&N from internal memory
(3) Root the stock B&N system and then load and run Android market apps alongside the B&N built-in and B&N store apps.
I wanted to keep the features of the 1.4.1 ereader, including Nook Comics support, so for me (1) was out, and I only needed a few apps from the Android Store, so I finally settled on (3) to avoid having to boot back and forth between the two systems. But first I did (2) to try things out and get an idea of whether I wanted to root the B&N firmware or replace it with something like CM7.
Can I not install cm7 on the SD and the regular b&n system when boot from internal memory?!
Yes, as I said, that's the setup I was using when I decided I prefer a manual nooter. Among your choices, you can:
(1) Replace the stock firmware with an alternative, such as CM7
(2) Run CM7 off a booting SD card and run stock B&N from internal memory
(3) Root the stock B&N system and then load and run Android market apps alongside the B&N built-in and B&N store apps.
I wanted to keep the features of the 1.4.1 ereader, including Nook Comics support, so for me (1) was out, and I only needed a few apps from the Android Store, so I finally settled on (3) to avoid having to boot back and forth between the two systems. But first I did (2) to try things out and get an idea of whether I wanted to root the B&N firmware or replace it with something like CM7.
Click to expand...
Click to collapse
It think I wanna go for option 2&3, can I not root the B&N internal system and also run CM 7 from SD card?
Do I have to take the SD card in and out depending in which one i wanna boot!?
Also another question... The whole reason this rooting is done if I understand correctly is to have access to all the systems in the NC, where do I get the Apps from ? Do I still have to get them through the market? Or can I download them somewhere!?
Got a question... Git my nook today, and it seems to be lagging quite a bit sometimes... Is that normal? Sometimes tottaly unresponsive... Is this normal?!
Sent from my PC36100 using XDA App
alexwick said:
It think I wanna go for option 2&3, can I not root the B&N internal system and also run CM 7 from SD card?
Do I have to take the SD card in and out depending in which one i wanna boot!?
Click to expand...
Click to collapse
Taking the SD card in and out depending on which one I wanted to boot, then full power off and power on was the way I did it. Don't know if there's a better way, but never saw a better way mentioned.
You can indeed run CM7 from an SD card and root the B&N internal system. That would allow you to use Nook Tweaks in the CM7 side to, for example, run a keyboard off the USB port and overclock the chip ~ neither of which you can do with the stock kernel ~ and still have the use of the 1.4.1 ereader for Nook Comics or media-enhanced ebooks.
Get a main microSD card for the CM7 SD card install. Follow the CM7 SD card instructions to do the CM7 SD card install on the big card.
And then get another microSD card (2GB Class 4 is plenty) and follow the 1.4.1 manual nooter instructions to root the stock B&N kernel.
Also another question... The whole reason this rooting is done if I understand correctly is to have access to all the systems in the NC, where do I get the Apps from ? Do I still have to get them through the market? Or can I download them somewhere!?
Click to expand...
Click to collapse
If you follow the CM7 SD card install directions, you will have access to the full Android Market on that install. Same thing if you follow the 1.4.1 manual nooter instructions ~ you will have access to the Android Market via the Nook Color Application Manager, and if you want can put the Android Market on the B&N Home Screen.
Its best to have a gmail.com account already, for the Android market registration, so sign up for one of those before starting the process if you don't already have one. And from the Android Market, you can also install the other markets (Amazon, 1mobile, GetJar) if you prefer one of those.
alexwick said:
Got a question... Git my nook today, and it seems to be lagging quite a bit sometimes... Is that normal? Sometimes tottaly unresponsive... Is this normal?!
Click to expand...
Click to collapse
It can be laggy, especially if you have too much load on it. Sometimes I'm surprised at how many windows I have open in the stock browser. Turning it all the way off will shut down apps that you may have left unclosed, free up RAM, and its normally back to its normal self.
Mind, the gurus have Android apps that can be used to shut down individual apps, but the brute force approach seems to work for me.
thanks for the quick detailed reply...
for the LAGS, well I dont have hardly anything open... the only thing i installed and bought was from the market. Angry Birds... and it seems sometime it will not respond to the throwing of the bird, but just scale the screen... even to exit the game and after the game is closed it seems to not respond properly... having to tap a button 5 times until it responds... and than it works fine after a reboot... and than a couple hours later same thing in the game... ..
also it seems like internetpages like nick.com seem to load forever and are very laggy. I ahve a 10 MBIT Internet connectio over wifi, so that shouldnt be a problem....
To teh dual Systems...Do I also need a second 2GB card for the rooted internal stock system, or is that just for the installation of it!?
I actually do have a 16 GB and a 2 GB at home already...
"If you follow the CM7 SD card install directions, you will have access to the full Android Market on that install. Same thing if you follow the 1.4.1 manual nooter instructions ~ you will have access to the Android Market via the Nook Color Application Manager, and if you want can put the Android Market on the B&N Home Screen."
Click to expand...
Click to collapse
Well on my android phone... most of the apps are available I believe for free on the forums... is this similar here... or do I have to buy them!? BTW My phone is not rooted...
The System is some 1.3 version I received... will I need to update to 1.4 first!?
I also do already have a gmail account... its a german one though [email protected] but that should be fine ... It is the german GMAIL
Also linked the nook to th BN Store I believe...Is tehre any waay to check?!
Should I not be able to stream netflix... with the regular nook!?
ONCE AGAIN THANKS FOR YOUR TIME !!!!
alexwick said:
... also it seems like internetpages like nick.com seem to load forever and are very laggy. I ahve a 10 MBIT Internet connectio over wifi, so that shouldnt be a problem....
Click to expand...
Click to collapse
That's just the stock Android Browser and an 800MHz single core system with 512Mb RAM plowing through a site with all the bells and whistles and targetted at a PC. Try the Dolphin HD browser (its in the B&N store, and its free so no worry about having to re-download it from the Android market to your CM7 install) ... it has an option to hold off flash content until you actually want to run it that can really speed up some sites.
To teh dual Systems...Do I also need a second 2GB card for the rooted internal stock system, or is that just for the installation of it!?
I actually do have a 16 GB and a 2 GB at home already...
Click to expand...
Click to collapse
Installation ... you want a good sized card for the CM7 install, and reading and storing an image from a large card, then formatting it and writing the install card image, then saving the install card image, formatting, and restoring the CM7 install image is a royal pain.
Note that you probably want to keep the install card as a bootable recovery card. 1GB is enough to do the manual noot, but 2GB is enough to hold the recovery of the original stock B&N before you do the manual root. 4GB is even better, as it can hold a recovery of the stock B&N as well as a recovery of the system right after it is manually nooted, in case you do something later to get it messed up.
And you can get a 4GB Class 4 card for $5 with free shipping from Amazon ~ the new 32GB flash cards have pushed the price of the smaller ones way down ~ so to my mind that's worth it to be able to set aside a recovery card.
Well on my android phone... most of the apps are available I believe for free on the forums... is this similar here... or do I have to buy them!? BTW My phone is not rooted...
Click to expand...
Click to collapse
Yes. There are paid apps, but both the CM7 install or the manual nooter give full access to a wide range of free apps on the main Android Market, and allow you to install 1mobile, GetJar, or Amazon if you prefer any of those markets.
The System is some 1.3 version I received... will I need to update to 1.4 first!?
Click to expand...
Click to collapse
Not for the SD card install of CM7. Be sure to follow the instructions for making an SD card install on a 1.3 system.
You'll want to upgrade for a rooted stock B&N Kernel to 1.4.2, because its only 1.4 that has the updated ereader, Nook Color tailored Netflix app, likely B&N Store HuluPlus this Friday ... if you were replacing the stock Kernel, there's be no reason to update, and the installs for the 1.3 system are more mature ... but if you want to keep the B&N Kernel, upgrade to 1.4.2. before you lock it down from further OTA updates.
I also do already have a gmail account... its a german one though [email protected] but that should be fine ... It is the german GMAIL
Click to expand...
Click to collapse
I'd don't know from personal experience, but I've seen some warnings about it being best to have a gmail.com account. Just to be safe, I'd sign up for a gmail.com account and give your primary gmail account as the email account used to confirm that you are a real person. Save it in an "Accounts" folder in your main gmail if you are unlikely to use it for anything except the Android market.
Also linked the nook to th BN Store I believe...Is tehre any waay to check?!
Should I not be able to stream netflix... with the regular nook!?
ONCE AGAIN THANKS FOR YOUR TIME !!!!
Click to expand...
Click to collapse
Before you start working on the unit, go to the store (its on the navbar) search for apps and download a free app. Dolphin HD is a good one. If it downloads and installs, you are linked to the B&N store.
Please help I can't install Galaxy on fire 2 as it cancels the download and says a "file read error please try again"
I am running ARHD THE NEWEST ONE
alizafar said:
Please help I can't install Galaxy on fire 2 as it cancels the download and says a "file read error please try again"
I am running ARHD THE NEWEST ONE
Click to expand...
Click to collapse
I too am having this issue, though it could be just because I'm trying to run it on the TF300, which just came out recently.
Same here. But since RonDelgen said he got the same error on the tf300 i doubt it's a incompatilibity error with ARHD. Maybe someone with stock ICS could try to install it?
I have been playing Galaxy on Fire 2 for the last two days on my TF101. Stock, unrooted, .21. Only had one force close then after that stability. The latest update has fixed(for me) alot of the issues I have been having like force closes, bad game play and pixelated graphics. Because it is such a large file when I downloaded it I made sure I killed any unnecessary apps and had a stable network connection. Good luck. It is a great game.
After checking Fishlabs website this is a known issue which will be fixed soon. Sorry!
I think I found the issue
It's due to My tablet been rooted as the developers have a exploit of a sort in their app thus the game will not be playable on some rooted tablets, etc but as I workaround is downloaded them SD Files from the external sources and Voila! The game works!
alizafar said:
I think I found the issue
It's due to My tablet been rooted as the developers have a exploit of a sort in their app thus the game will not be playable on some rooted tablets, etc but as I workaround is downloaded them SD Files from the external sources and Voila! The game works!
Click to expand...
Click to collapse
Nothing to do with being rooted. I have an unrooted Transformer Prime and I am getting the file read error.
Downloaded GOF 2
This morning I rolled back ICS .21 to ICS .17(US) and was able to download the game. Don't know if Fishlabs fixed the problem or if there is a compatibility issue with the latest firmware. Just thought I would pass this on.
I had been getting the file read error on ARHD with test 17c kernel up until yesterday. Yesterday it suddenly decided to download fine and has been working great ever since.seems that they may have fixed the problem.
Sent from my Transformer TF101 using xda premium
If you have a microsd in..try taking it out..or make sure its formatted to fat32 (not microsoft's default). I had the same problem, formatted it in linux as fat32 (was exfat) and downloading worked.
One annoying feature of new Nook HD+ (and assuming Nook HD) is that during initial set up it will look for and force you to update (if one is found). There is a neat and really easy trick to bypass this process.
Once you get to that step in the process, during the process hold down the power button and force it to shut off by selecting "OK" in the prompt. You have to do it before it finishes downloading the update.
Once you power it back on you'll have to restart the whole process of entering your WiFi and information again. When you get to the point where the device looks for an update, it will look for a few seconds and determine that its got the latest version installed and proceed to the next phase.
To make sure you did it correctly just go into "Settings" and check the version. For me my default was 2.0.4, for you it may be different, but either way its not 2.0.5.
I've tested it multiple times and always with great success.
What about 2.0.4 do you prefer over 2.0.5?
Also, let us know if this actually stays on 2.0.4. Those of us who had already registered Nooks (both HD and HD+) when 2.0.5 came out got updated in spite of having turned off auto updates.
lkmiller said:
What about 2.0.4 do you prefer over 2.0.5?
Also, let us know if this actually stays on 2.0.4. Those of us who had already registered Nooks (both HD and HD+) when 2.0.5 came out got updated in spite of having turned off auto updates.
Click to expand...
Click to collapse
It was for rooting purposes, since at the time I couldn't find a rooting tool for 2.0.5, that's why. Also I too had registered once under 2.0.5, and when starting fresh found that this method does work regardless of what you initially registered under. Though it only buys you little time to do whatever modifications you need to to your device before it automatically updates you (you could also leave WiFi turned off too).
dcoke said:
It was for rooting purposes, since at the time I couldn't find a rooting tool for 2.0.5, that's why. Also I too had registered once under 2.0.5, and when starting fresh found that this method does work regardless of what you initially registered under. Though it only buys you little time to do whatever modifications you need to to your device before it automatically updates you (you could also leave WiFi turned off too).
Click to expand...
Click to collapse
What device are you running? Still would like your factory zip.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
dcoke said:
It was for rooting purposes, since at the time I couldn't find a rooting tool for 2.0.5, that's why. Also I too had registered once under 2.0.5, and when starting fresh found that this method does work regardless of what you initially registered under. Though it only buys you little time to do whatever modifications you need to to your device before it automatically updates you (you could also leave WiFi turned off too).
Click to expand...
Click to collapse
Ok, I thought that might be why. Thankfully we can root 2.0.5 now. But it's good to know this method of postponing that initial update if I ever need to reset and start over.
nook hd+ auto-updated after leapinlar root+cwm fixes
My Nook HD+ notified me last night that it had auto-updated to 2.0.6 but I was able to get back my original Nova Prime Launcher and the Google Play store continues to work (it broke Beautiful Widgets, but uninstalling it and reinstalling it fixed that)
I had originally rooted it from 2.0.5 using the Universal Root method here: http://forum.xda-developers.com/showthread.php?t=2062613
I had the following images installed:
NookHD-HDplus-Gapps+Extras-for-stock-rev1.zip
NookHD-HDplus-Universal-Root-rev1.zip
NookHD-HDplus-LocationServices.zip
Using CWM for here:
NookHDplus-bootable-CWM-6023-for-emmc-stock-4GB-rev1.zip
Note - I did not manually update or in anyway 'induce' the update, it just happened. Did I miss something in the instructions to prevent auto-update?
Atleast the play store and Nova Launcher keeps working (not had time to check if root is still working though) But I did notice that the B&N Home launcher keeps showing up more often than before (hitting apps and going back brings back Nova)
Thanks
vtmanryn said:
My Nook HD+ notified me last night that it had auto-updated to 2.0.6 but I was able to get back my original Nova Prime Launcher and the Google Play store continues to work (it broke Beautiful Widgets, but uninstalling it and reinstalling it fixed that)
I had originally rooted it from 2.0.5 using the Universal Root method here: http://forum.xda-developers.com/showthread.php?t=2062613
I had the following images installed:
NookHD-HDplus-Gapps+Extras-for-stock-rev1.zip
NookHD-HDplus-Universal-Root-rev1.zip
NookHD-HDplus-LocationServices.zip
Using CWM for here:
NookHDplus-bootable-CWM-6023-for-emmc-stock-4GB-rev1.zip
Note - I did not manually update or in anyway 'induce' the update, it just happened. Did I miss something in the instructions to prevent auto-update?
Atleast the play store and Nova Launcher keeps working (not had time to check if root is still working though) But I did notice that the B&N Home launcher keeps showing up more often than before (hitting apps and going back brings back Nova)
Thanks
Click to expand...
Click to collapse
We have known for a while that setting the OTA to manual does not seem to stop auto updates anymore. The good news is that it still accepts the root. Just flash universal root again.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
I might have found a way how to disable Nook HD OTA autoupdate feature.
For some reason setting com.bn.device.fota.mode to manual does not work, so there is more straight approach to solve this.
So far i have found two:
1) Once you have rooted your device it is just a matter of editing /etc/hosts file and adding couple of lines
127.0.0.1 nook.com
127.0.0.1 barnesandnoble.com
127.0.0.1 su.barnesandnoble.com
which effectively blocks access to autoupdates, but when you reboot your device, all your data will be erased (nook will restore itself to factory state). So some way around is needed.
2) There is an app on google store called "Android Firewall", install it. Once installed block Wifi for NookConnectivityService. GAPPS and browser will not be affected, you'll get norification "Wifi error". But otherwise wifi is fuctional.
2) There is an app on google store called "Android Firewall", install it. Once installed block Wifi for NookConnectivityService. GAPPS and browser will not be affected, you'll get norification "Wifi error". But otherwise wifi is fuctional.
Click to expand...
Click to collapse
Blocking NookConnectivityService kills connectivity to the Google Play.
greenya said:
1) Once you have rooted your device it is just a matter of editing /etc/hosts file and adding couple of lines
127.0.0.1 nook.com
127.0.0.1 barnesandnoble.com
127.0.0.1 su.barnesandnoble.com
which effectively blocks access to autoupdates, but when you reboot your device, all your data will be erased (nook will restore itself to factory state). So some way around is needed.
Click to expand...
Click to collapse
You can symlink the hosts file. See my HD/HD+ tips thread linked in my signature. Look at item 15. Of course there are othe ways to prevent the update, like symlinking build.prop and doing the white on white repair. But those just cause the update to fail, while this may prevent them even checking. If this works, I may update my CWM zip to include it.
EDIT: After researching this a little I have found an easy way to accomplish this. That is to use AdAway. You can safely use that program if you configure it to put the hosts file on /data. It automatically symlinks it for you. But you need to be rooted to use this app. And it has a feature where you can add your own sites to block. Just add those sites listed in the post above. Then every time AdAway updates its own list, it adds your list to it also. This will block B&N from using those sites to download their updates. But realize that it also blocks you from browsing their site.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
leapinlar said:
EDIT: After researching this a little I have found an easy way to accomplish this. That is to use AdAway. You can safely use that program if you configure it to put the hosts file on /data. It automatically symlinks it for you. But you need to be rooted to use this app. And it has a feature where you can add your own sites to block. Just add those sites listed in the post above. Then every time AdAway updates its own list, it adds your list to it also. This will block B&N from using those sites to download their updates. But realize that it also blocks you from browsing their site.
Click to expand...
Click to collapse
Nice! It works then Including it to CWM zip is a good idea, with a warning, that you get to loose one site. That rooting thing imho is the whole reason for not using it, but substituting with google play.
BTW Is your hybrid cm10.1 stable on nook hd+ ?
greenya said:
Nice! It works then Including it to CWM zip is a good idea, with a warning, that you get to loose one site. That rooting thing imho is the whole reason for not using it, but substituting with google play.
BTW Is your hybrid cm10.1 stable on nook hd+ ?
Click to expand...
Click to collapse
WARNING! Hybrid not for HD+ !!!
greenya said:
BTW Is your hybrid cm10.1 stable on nook hd+ ?
Click to expand...
Click to collapse
My Hybrid setup on the HD+ is experimental and a hacked version by me. And I am running verygreen's 1-07 version of CM10.1. The Hybrid works great and is very stable, but the CM10.1 is buggy.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
leapinlar said:
My Hybrid setup on the HD+ is experimental and a hacked version by me. And I am running verygreen's 1-07 version of CM10.1. The Hybrid works great and is very stable, but the CM10.1 is buggy.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Click to expand...
Click to collapse
Seems i missed somewhere something
datas0ft said:
Seems i missed somewhere something
Click to expand...
Click to collapse
You did not miss it. I just got it working this weekend and this is the first I have told anyone. I am going to test it a while before I even consider making it for anyone else. It does work but I had to manually configure some things. And it only works on CM10.1, not CM10. Until we get some better CM10.1's it does not really matter anyway.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
leapinlar said:
You did not miss it. I just got it working this weekend and this is the first I have told anyone. I am going to test it a while before I even consider making it for anyone else. It does work but I had to manually configure some things. And it only works on CM10.1, not CM10. Until we get some better CM10.1's it does not really matter anyway.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Click to expand...
Click to collapse
This news change many things. But seems verygreen is so busy last time or found something new interesting.
Anyway. If you need some "hard testing" (when testing may make item dead) then ask me. I have one item with no warranty and ... you know, its not mine ... and its not last one.
greenya said:
I might have found a way how to disable Nook HD OTA autoupdate feature.
For some reason setting com.bn.device.fota.mode to manual does not work, so there is more straight approach to solve this.
So far i have found two:
1) Once you have rooted your device it is just a matter of editing /etc/hosts file and adding couple of lines
127.0.0.1 nook.com
127.0.0.1 barnesandnoble.com
127.0.0.1 su.barnesandnoble.com
which effectively blocks access to autoupdates, but when you reboot your device, all your data will be erased (nook will restore itself to factory state). So some way around is needed.
2) There is an app on google store called "Android Firewall", install it. Once installed block Wifi for NookConnectivityService. GAPPS and browser will not be affected, you'll get norification "Wifi error". But otherwise wifi is fuctional.
Click to expand...
Click to collapse
Thank you for this. It works. I added the manual way to do it via AdAway to my HD/HD+ Tips thread and added a CWM zip to my HD/HD+ CWM thread to automatically do it for you if you are not rooted. Both threads are linked in my signature.
Sent from my Nook HD+ running rooted stock
leapinlar said:
Thank you for this. It works. I added the manual way to do it via AdAway to my HD/HD+ Tips thread and added a CWM zip to my HD/HD+ CWM thread to automatically do it for you if you are not rooted. Both threads are linked in my signature.
Sent from my Nook HD+ running rooted stock
Click to expand...
Click to collapse
Could you also just freeze the NookConnectivityService app using Titanium Backup - seems to work for me
docfreed said:
Could you also just freeze the NookConnectivityService app using Titanium Backup - seems to work for me
Click to expand...
Click to collapse
Someone earlier says doing that blocked his Google Play. Is yours working ok?
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Someone earlier says doing that blocked his Google Play. Is yours working ok?
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
If you mean the Play Store, yes no problem - I don't use any other Play apps (like music, books, etc.). I am on 2.06, rooted, ADW EX Launcher and see no issues whatsoever with WiFi (as a matter of fact, no issue signing in to BN.com and downloading one of my books.
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.