Hi guys,
Searched quite a bit and cannot find how to update this. Running CyanogenMod version 11-20140117-UNOFFICIAL-hummingbird (Android 4.4.2). Rooted long ago and haven't updated anything on the tablet in forever because it was just how I liked it. I could boot into the standard Nook OS and view the Nook eShop (or whatever they call it now), or I could boot into Cyanogen Mod and run standard Android apps.
However now because they updated the Nook OS to include TLS 1.2 some many months ago (Transport Layer Security 1.2) I cannot load any of the Nook shop stuff without this update. When I try to update it within the Nook OS it tells me there's an update, proceeds to download it, tells me it will restart and apply the update, but then it never updates and just comes back into the Nook OS as if it just dropped the update. I used AFN to dual boot from the SD card - wondering if there's something in this setup that freezes out updates from happening.
Anyone have any ideas how I can get the TLS 1.2 update to take?
Thanks for ANY help... Really appreciate it!
So, I answered my own question by taking a chance. I pulled the SD card out and just booted directly into Nook OS and let it take the update that way. Rebooted after update (no SD card inserted) and the update took. Put the SD card back in and booted into Nook OS to make sure everything was still ok - no issues. Rebooted into CyanogenMod after that and still no issues.
I'll leave this here in case someone in the future comes looking for a similar question/answer.
Just a guess, but most of the B&N devices cannot be updated if rooted. So you might need to unroot, do the update, then root again.
Umm, I'm guessing you just overlooked my follow up post/reply up there ^^^ where I said I figured it out. It did update, even with being rooted.
Related
Hi guys, i really need some help here. I bought my NC at the beginning of this month and I'm pretty sure the version is 1.1.0
I wanted to restore my rooted NC back to stock but i accidentally restore it to 1.0.1 instead.
While running on 1.0.1
1) My device can't be registered. I think since I've restore it to 1.0.1, they won't allow me to register my device.
2) I've done the skip out of box experience and tried to do an update to 1.1.0 using the sideload update file (by connecting it to my pc and transferring the file directly)but nothing seem to work.
Can someone please help me?
Does anyone has the stock 1.1.0 file in full which I can try to load it in through clockwerk ?
Yeah, I'm kind of in the same boat. I tried to make a bootable sd card with froyo on it, and I ended up corrupting my Nook's system somehow. I followed the process to restore my nook to stock, but it went back to 1.0.1. Previously, I had updated to 1.1.0.
Now I would like to go back to 1.1.0 and use Autonooter 3.0 to reinstall eclair. But I wasn't able to sideload the 1.1.0 firmware.
Anybody have any tips? Thanks.
i've managed to reset it 1.2.0 instead. What i did was to skip out of the box effect in order to skip the need to register. I connected my NC to a pc and transfer the 1.2.0 update manually. After this ejecting, after a few mins it will start to auto update.
Received the update notification this morning, happily started downloading and installation.
Like some out there, the tablet rebooted and it seemed to install but up to about 1/4 progress it froze with a central honeycomb logo with exclamation mark. Thought it was part of the process, left alone for an hour but nothing happened, hence rebooted with a notification of 'update failed'.
Searching through google and xda forum the last 2 hours -- have tried the unrooting the device, plugging in to power, removing sd card to no avail.
Someone has also suggested to restore wpa_supplicant file under system/bin. I don't remember altering the file at all, and when I check the file it is dated 29/3/2010... i bought my device in April, hence assuming it has not been altered either by myself or from any app. Like wise for the telephony files as well, as I haven't changed anything to try to stop the cell standby issue to improve battery life.
I am left with no options unless someone has a better idea. I have not uninstalled any pre-loaded apps. Rooted with Gingerbread (and as I said tried unrooted and re-rooted without success in updating).
Thoughts?
Current build:
Android version 3.0.1
Kernel 2.6.36.3
Build no. Acer_A500_1.139.04_COM_GEN1
Failed system update to 4.010.24
I am located in Melbourne, Australia.
(Last thing would be to download the actual rom and update via CWM.)
open /cache/recovery/last_log on your tablet use root explorer
ypu will know whats wrong
I'm in Melb too, and that particular update has failed to download about 5 times now, and when it finally downloaded, it came up with a message saying "update invalid" or something along those lines. I'm gonna wait til I get home to try and update again.
altering WPA_Supplicant file is something you would've done so your tab would connect to ad hoc networks. Must be something else.. did you alter any other files? I'm working on this same issue. frustrating as f*#%
I was running stock rooted 3.01 and was failing updates over and over until I flashed back to the stock recovery using the Acer recovery apk. As soon as I did that and tried the ota update again it worked right away... once 3.1 was installed I rerooted using iconia root 2.1 and flashed cwrecovery back to tablet... let me know if this helped
acorsino said:
I was running stock rooted 3.01 and was failing updates over and over until I flashed back to the stock recovery using the Acer recovery apk. As soon as I did that and tried the ota update again it worked right away... once 3.1 was installed I rerooted using iconia root 2.1 and flashed cwrecovery back to tablet... let me know if this helped
Click to expand...
Click to collapse
Same for me. Had to go back to stock recovery for the OTA update to work.
Mine failed the first time. I rebooted and it worked the second time.
I tried using Acer Recovery Installer 1.5, checking Stock USA 1.141.07_COM_GEN1 and touched "install recovery image", rebooted, and nothing happened?
My build number remains 1.139.04_COM_GEN1
I am sure I have missed something...
Tried downloading and installing the 5th time, still failed and stuck at the same progress bar of 1/4 followed by that annoying honeycomb with exclamation mark logo.
mashilu said:
I tried using Acer Recovery Installer 1.5, checking Stock USA 1.141.07_COM_GEN1 and touched "install recovery image", rebooted, and nothing happened?
My build number remains 1.139.04_COM_GEN1
I am sure I have missed something...
Tried downloading and installing the 5th time, still failed and stuck at the same progress bar of 1/4 followed by that annoying honeycomb with exclamation mark logo.
Click to expand...
Click to collapse
If you see the little bee fail screen, it is not the stock recovery, but still CWM.
mashilu said:
Received the update notification this morning, happily started downloading and installation.
Like some out there, the tablet rebooted and it seemed to install but up to about 1/4 progress it froze with a central honeycomb logo with exclamation mark. Thought it was part of the process, left alone for an hour but nothing happened, hence rebooted with a notification of 'update failed'.
Searching through google and xda forum the last 2 hours -- have tried the unrooting the device, plugging in to power, removing sd card to no avail.
Someone has also suggested to restore wpa_supplicant file under system/bin. I don't remember altering the file at all, and when I check the file it is dated 29/3/2010... i bought my device in April, hence assuming it has not been altered either by myself or from any app. Like wise for the telephony files as well, as I haven't changed anything to try to stop the cell standby issue to improve battery life.
I am left with no options unless someone has a better idea. I have not uninstalled any pre-loaded apps. Rooted with Gingerbread (and as I said tried unrooted and re-rooted without success in updating).
Thoughts?
Current build:
Android version 3.0.1
Kernel 2.6.36.3
Build no. Acer_A500_1.139.04_COM_GEN1
Failed system update to 4.010.24
I am located in Melbourne, Australia.
(Last thing would be to download the actual rom and update via CWM.)
Click to expand...
Click to collapse
Hi .. try to do that...
the uploaded file helped and solved my issue..i'm now running Honeycomb 3.1
Solution posted by Bob here: (correct the link below "www")
w w w.androidtablets.net/forum/acer-iconia-tab-a500-forum/18444-update-failed-help.html
Here's the WPA_Supplicant from my A500, after the 3.1 update. Hope this works for you guys.
I'm not sure what the extension is for the A500, but I had to add .zip to be able to upload it. Try removing the .zip before using it. Also, remove the 'original'. I added that to keep it straight on my tablet.
Good Luck.
Bob
p.s: sorry i'm a newbie here and can't post link outside the forum at the moment..
just follow the steps described by Bob!
I did see that different logo, which I subsequently rebooted as I thought it's frozen again.
Interestingly, I tried to push for another system update, attempt no. 7, and now, it progresses and complete update!!! Woo hoo!
Thanks for all the help. I still don't know which one sorts what out though... Cheers!
I had successfully manual nootered my NC with Manual Nooter 4.6.16 and was happily using the NC for a month.
Then suddenly the root is gone and I am back to the factory 1.01...
Any ideas on what might have caused that? I don't think anyone forced the factory restore by holding certain buttons down. I also don't think that the battery was fully drained because I had been keeping it charged.
How can I see if any part of my old configuration still exists (apps downloaded, screen layout, etc)? Is it possible that everything from the rooted configuration is still there but something got corrupted and it rebooted into factory 1.01?
Any suggestions for preventing this from happening again?
BTW I used the appropriate version of CMR to do the manual nooter and still have that SD card so rerooting is not an issue. Just trying to figure out what happened...
FWIW since magically going back to 1.01 I haven't been prompted by B&N to auto update to 1.2 ...
Thanks in advance for any advice or ideas...
Doug
Sent from my HTC Evo 4g (Android 2.2) using Forum Runner
I don't know what cause but gotta be something.
AFAIK, never heard of this case once before.
Back in the good old days --Feb or Mar -- I accidently hit Share Books on the BN menu and it did a factory reset ....back to no root.
Hi All,
Went to use my NC this morning (running CM7 from uSD card) and found it locked up.
No biggie, just shut it down and powered back up, only to get our buddy the Penguin, as though I'd booted into recovery (although I hadn't). After indicating that it found nothing to install or update, it shut down.
Booted again (still with uSD card in) it entered recovery mode again.
Figuring the card might have been hosed, I put in a backup, created yesterday-same result.
Hmmmm....
I pulled the card and let it boot to the original 1.3 O/S internal. All went well, then I got a quick message that an update was being applied (?). My heart sank, thinking that I'd had 1.4 pushed out to me, and God only knows what that update might do the the NC.
I quickly went to the menu to check the software version, and it still showed 1.3.
I shut it down, replaced the uSD and rebooted.
All is well now.
Any ideas about what might have happened? Anyone else have this experience?
Thanks!
Dan
You would not get a B&N update pushed out while you're booted into CM7. As for what happened.... You said you got a new SD and it fixed it? Perhaps your SD just died?
khaytsus said:
You would not get a B&N update pushed out while you're booted into CM7. As for what happened.... You said you got a new SD and it fixed it? Perhaps your SD just died?
Click to expand...
Click to collapse
I wouldn't have thought so, but when I booted into internal memory (no uSD card in place) I got the "updating" notice.
In fact the "new" card (which was a backup of the first) did the same "boot to recovery" as the original.
After the original O/S did its "updating" both cards worked exactly as expected, booting into CM7, and both cards have worked perfectly since.
That's why I'm calling it a "glitch"
The device was apparently "tricked" into booting to recovery and continued to do so from any of my CM7 uSD cards. I went so far as to access the boot menu and make sure that it booted the uSD and did so "normally", yet the penguin kept rearing it's cute little head.
Only allowing the NC to boot into its own O/S, which triggered the phantom "update", fixed the issue.
In short: After update to 1.1.2, rooting methods don't work for me. Each time after root, Nook stuck on «nook» screen with 5 circles below (dot continue running until battery discharges completely, screen refreshes non-regularly), except 1st boot with MinimalTouch, which asked about signing-in and location services.
Any help appreciated.
Long story:
Some time ago, I've been beginning with NST 1.0.1, and rooted is successfully with TouchNooter. After it updated to 1.1, and I re-rooted it, successfully again, now with «Market & Setup Script Kit» (which uses uRamdisk-replacing method).
But I didn't turn off OTA update, just not to miss new firmware.
One day about a week ago, it ceased to boot, not going beyond «nook» screen with running dot in 5 circles. I did reset with holding left & right bottom buttons, but it didn't help.
When I booted noogie, I found apparent uRamdisk.old (left from prev. rooting) near uRamdisk, and renamed it to uRamdisk. Nook booted normally, allowed me to register, and let me use it as reader.
But still, I wanted to root.
Tried both touchnooter-2-1-31 and MinimalTouch, both with same result (not loading beyond running dot). Tried installing 1.1.2 in non-rooted mode, and updating again. With MinimalTouch, it boots to sign-in 1st time, but reboots when it should go to home screen. 2nd time an on, it does not boot beyond running dot.
Currently my nook is working, non-rooted, with 1.1.2 firmware. Each time I began from this state.
http://nookdevs.com/Nook_Simple_Touch_restore_to_stock
Haven't tried these but supposedly can revert you back to original firmware then maybe upgrade to 1.1, root, and turn off updates?
I tried the 3rd method on my unrooted nook that had 1.1.2, it claimed to work but version still showed up as 1.1.2.
Regardless I used touchnooter to root and haven't had any issues since. Still shows 1.1.2 in version info but it's rooted and running fine.
Well, I've used methods #2 and #3 several times, and it doesn't help (surprisingly).
I don't think there will be any difference with #1.
What helped me to go back is n2T-Recovery_0.1.img from that post, which initiated full restoration (and it worked). Once I also used full initial backup, from which I retrived some files to undo rooting. I didn't flash it back ever, because I am not sure it's done correctly, as its size differs from one stated in backup article, and is 1'962'934'272 bytes long (exactly same as size on disk).
funny, I've just rooted with uRamdisk_wireless_adb_init_1.1_1.1.2.zip. Now will try to install google apps.