Related
Let's get some user experiences here to try to prove or disprove what, to me, seems like a gray area that many have jumped to conclusions about:
There was recently a post in a thread about someone who, after renaming etc/security/otacerts.zip while on 1.0.1 firmware (to disable auto updates), opened the B&N Shop and had all of his/her data wiped/restored. This poster claimed to have repeated it several times, all with the same result.
Afterwards, I didn't hear many others say much about it (I'm assuming if this were widespread it would be everywhere). Plus someone in the same thread even mentioned here that he got the reset WITHOUT having disabled the otacerts . . .
... Yet I keep hearing mentions in various threads about that one original incident as if it's a sure-fire thing that's bound to happen when you disable otacerts on 1.0.1.
So if you:
a) are on 1.0.1 firmware
b) renamed the otacerts.zip file to something else
c) have used the B&N Shop
... Please let us know what happened, so we can attempt to get a clearer view on this.
a) I'm on 1.0.1 auto-nootered
b) renamed otacerts.zip to otacerts.zip.disabled
c) B&N Shop works fine
@wvcachi, you mentioned in a different thread that you're on 1.0.0 right now. Did you disable the otacerts? If so, does shop work for you?
eyecrispy said:
@wvcachi, you mentioned in a different thread that you're on 1.0.0 right now. Did you disable the otacerts? If so, does shop work for you?
Click to expand...
Click to collapse
Yes, shop works fine for me on 1.0 after disabling otacerts (stayed on 1.0 because all but one Dolphin User Agents work properly on 1.0).
wvcachi said:
Yes, shop works fine for me on 1.0 after disabling otacerts (stayed on 1.0 because all but one Dolphin User Agents work properly on 1.0).
Click to expand...
Click to collapse
Ok cool. I'm gonna go ahead and disable mine tonight then. Have you experienced any other side effects on 1.0 since disabling certs?
Sent from my XDA app on my Nook Color
I'm with MkFly
1.01
Renamed
No problem
//from the nook COLOR
eyecrispy said:
Ok cool. I'm gonna go ahead and disable mine tonight then. Have you experienced any other side effects on 1.0 since disabling certs?
Sent from my XDA app on my Nook Color
Click to expand...
Click to collapse
None at all.
That post was mine and I later clarified that it was false.
The authorization errors/reseting turned out to be a recovery of data from using Titanium. You can recover apps, but not the data that associates itself with B&N apps otherwise you get the authorization error.
Disabling OTA certs will NOT break your BN shop.
leeh41 said:
That post was mine and I later clarified that it was false.
The authorization errors/reseting turned out to be a recovery of data from using Titanium. You can recover apps, but not the data that associates itself with B&N apps otherwise you get the authorization error.
Disabling OTA certs will NOT break your BN shop.
Click to expand...
Click to collapse
Haha cool, thanks for the clarification. Hope this thread has helped dispel some myths on the subject.
I'm a bit in the dark on this topic. Is there a thread somewhere that will show me how to disable otacerts properly? Can I do it with Root Explorer? What would/could happen if B&N rolls out an update and it's applied to a rooted Nookie?
See my sig for Nook info [1.01 A-n (2.12.25)] ... I renamed otacerts.zip to otacerts.OLD with no ill effects. I did get an authentication error after redoing A-n but I'm 99% sure that was from restoring system apps/data with Titanium Backup. I have stuck to just user apps/data and have had no issues.
Homer
supersoulfly said:
I'm a bit in the dark on this topic. Is there a thread somewhere that will show me how to disable otacerts properly? Can I do it with Root Explorer? What would/could happen if B&N rolls out an update and it's applied to a rooted Nookie?
Click to expand...
Click to collapse
All you're doing is renaming etc/security/otacerts.zip to something else. Root Explorer works just fine.
I may have misunderstood. I never allowed the update (by not going online) and I renamed etc/security/otacerts.zip to etc/security/otacerts.zip.old and it updated.
Sigh. I'm now on 1.0.1.
My side-loaded apps are there, but none will run. I tried to avoid this but I guess I have to do the autonooter thing.
Do I really have to wipe it or can I just run the autonooter as is?
But I'll start reading.
I would recommend wiping it (both system and app), loading 1.0.1 again from a file, then auto-nooter it. I had issues when I auto-nootered 1.0.1 with existing apps from 1.0.
sark666 said:
I may have misunderstood. I never allowed the update (by not going online) and I renamed etc/security/otacerts.zip to etc/security/otacerts.zip.old and it updated.
Sigh. I'm now on 1.0.1.
My side-loaded apps are there, but none will run. I tried to avoid this but I guess I have to do the autonooter thing.
Do I really have to wipe it or can I just run the autonooter as is?
But I'll start reading.
Click to expand...
Click to collapse
If you never went online, how did the update get on your NC? or do you mean you didn't go to B&N? Other people have mentioned just re-running Auto-nooter but YMMV.
Homer
supersoulfly said:
... What would/could happen if B&N rolls out an update and it's applied to a rooted Nookie?
Click to expand...
Click to collapse
Can anyone speak to this issue. Is there any danger of an OTA update bricking the NC? I assume it would just fail, but you know what they say about assumptions....
jerrykur said:
Can anyone speak to this issue. Is there any danger of an OTA update bricking the NC? I assume it would just fail, but you know what they say about assumptions....
Click to expand...
Click to collapse
It didn't brick mine. I was on 1.0 and was nootered (but didn't have the otacert.zip renamed). Got the update late December. Didn't have any issues until I auto-nootered over it. Then it started doing strange things, which I don't remember the specifics now. So I did a clean wipe and redid everything. All is well now.
Homer_S_xda, Sorry reading it again I see my post wasn't clear. I was happy with 1.0.0 and thought that renaming otacerts would prevent wifi updates.
I didn't have my nc online since the update came out, just using apps and as a reader. Previously my nc was rooted. Nookdevs says the 1.0.1 will fail on a rooted 1.0.0 nc but once I finally brought it online, it did update for me. My side loaded apps were there, but none would run. I believe nookdevs guide means downloading the 1.0.1 update and copying over will fail on a rooted nook but it seems the OTA update will install on a rooted 1.0.0.
So just wanted to say, renaming autocerts does not prevent updates (not from 1.0.0. -> 1.0.1 anyway). But if it failed for 1.0.0 I don't see why it would work for 1.0.1.
So I reset to factory defaults, reinstalled 1.0.1 and used autonooter. I was going to just run autonooter and not bother with reseting, but people advised I would be just asking for trouble.
From what I understand, there isn't a reliable way to prevent OTA updates. I thought android devices have a hosts file. I would have thought someone by now would have used wireshark to see where it's grabbing the updates and redirect that.
I'd rather dodge this again when the next update comes out (unless the next update provides something really useful or whatever)
But again, maybe I misunderstood the whole point of this thread. Is there another reason to disable otacerts? Cause it doesn't stop updates.
Today B&N launched their latest update for the Nook Color and it's a Big one. It includes Android 2.2!
I'll be updating once I'm done here as I have unrooted stock for this very purpose. I'll be back with my opinions on what it's like. For now, if you have Unrooted stock you can update from the URL below. Everyone else, drool over the Update's details and imagine what this could do for our Custom ROMs.
Update page:
http://www.barnesandnoble.com/u/nookcolor-support-software-update/379002520/?cds2Pid=35758
Details:
The NOOK Color Ver1.2.0 update contains new features and enhancements, including:
Access to shop a broad collection of popular NOOK Apps to enjoy great games, stay up to date on news and weather, and more
Full-featured free email to check and send web-based email (i.e., Yahoo, Gmail, Hotmail, AOL) all from one in-box
NOOK Color’s update to Android OS 2.2/Froyo offers system improvements, browser performance and a more complete Web experience giving customers access to enjoy even more video, interactive and animated content. NOOK Color now includes support for Adobe Flash Player
NOOK Kids exciting new Read and Play titles that bring animation, activities and stories together
NOOK Books Enhanced offer in-page video and audio in a growing number of titles
Enhancements to magazine navigation making it easier to enjoy even more of the growing selection of magazines in NOOK Newsstand
NOOK Friends (beta) to see your friends’ reading activities, swap books with LendMe, share recommendations and discover new titles
____________________________________________________
Sent from NookColor CM7 using Tapatalk
Does it have copy and paste for text fields?
Can you still boot to SD card? that is all I care about.
I want to know too did anyone confirm this?
is the zip off their website cwm flashable? i would assume not...
GorillaPimp said:
Does it have copy and paste for text fields?
Click to expand...
Click to collapse
Yes.
danbutter said:
Can you still boot to SD card? that is all I care about.
Click to expand...
Click to collapse
Yes. Dual booting with CM7 still works fine.
john10101 said:
is the zip off their website cwm flashable? i would assume not...
Click to expand...
Click to collapse
No.
Waiting for root.
epakrat75 said:
Yes. Dual booting with CM7 still works fine.
Click to expand...
Click to collapse
Sweet. I can not wait to update. CM7 runs perfectly off my Sandisk Class 4 8GB card, so even if they have blocked rooting, I am still willing to update. That said, as long as they allow dual booting, rooting should always be possible.
picopir8 said:
Sweet. I can not wait to update. CM7 runs perfectly off my Sandisk Class 4 8GB card, so even if they have blocked rooting, I am still willing to update. That said, as long as they allow dual booting, rooting should always be possible.
Click to expand...
Click to collapse
Dual booting from SD card is wired into the hardware, there is nothing they can do in software to stop it.
Will Rooted NC get the update?
I have rooted my NC.
I followed instructions for directly applying update with no luck.
Am I correct that the rooted NC will not receive update and that I must return to stock before I can get the new update?
PS If this is true, what is it about the rooted NC that prevents the update?
kernel version?
Can anyone post the kernel version after the update please?
leorob said:
I have rooted my NC.
I followed instructions for directly applying update with no luck.
Am I correct that the rooted NC will not receive update and that I must return to stock before I can get the new update?
PS If this is true, what is it about the rooted NC that prevents the update?
Click to expand...
Click to collapse
I would suggest flashing back to stock, re-register then applying the update from B&N. (That should remove the root) That what I am doing for a few people at work. Will report back on progress but logically that should work.
What's the point of going to 1.2 if it's not rooted yet?
Some important information from another Forum:
Successful download of update and install
File name: nookcolor_1_2_update.zip
File size: 190 MB (199,715,879 bytes) Size on disk: 190 MB (199,716,864 bytes)
MD5 checksum: D0B6323258F2793D19A1C9286E2AB753
Click to expand...
Click to collapse
if your 1.2 update fails, check the MD5 on the file against this one. If it is different, your downloaded update file is corrupt.
If I am rooted on just stock 1.1 using one of the autnooter methods what can I do to just flash back to stock and lose root. I saw one thread in the developer forum with a stock 1.1 zip file and figured I could try that. I do not mind losing root as I haven't really been keeping up with all the different roms being released lately and will be using it more for just reading books. Here is the thread I am referring to:
http://forum.xda-developers.com/showthread.php?t=945838
Stock 1.1 file works
I was rooted on 1.1 and installed the stock 1.1 file you refer to.
All went well and I was returned to stock 1.1.
Followed Barnes and Noble instructions for the downloaded update and file was recognized as soon as unit went to sleep.
Installation happened automatically and now I am at 1.2.
The kernel is 2.6.32.9... the os is froyo.
leorob said:
I have rooted my NC.
I followed instructions for directly applying update with no luck.
Am I correct that the rooted NC will not receive update and that I must return to stock before I can get the new update?
PS If this is true, what is it about the rooted NC that prevents the update?
Click to expand...
Click to collapse
I tried to install the update over an Autonootered 1.1. All that happened was the device rebooted and the update.zip file was deleted from the nook. I presume that I need to flash it back to an original version and then install the upgrade. I was hoping I could just layer this update on top of what I have so I wouldn't lose apps that are already installed.
If you have not modified anything after Autonooter, simply following the directions in the 'Flash back to clean stock ROM' wiki and you'll be presented with an out-of-the-box booting NC. After that, simply follow the 'Manual Download Instructions' posted at the Barnes & Noble website to update your NC to the official new stock v1.2.0 ROM.
If you're having trouble updating your NC with Unrooted Stock like me then here's what you need to do. You'll have to reflash to Factory Defaults.
Perform Step 1, Method 1; then Step 2, Method 1
http://nookdevs.com/Flash_back_to_clean_stock_ROM
This Reinstalls Stock v1.0 to System partition and then wipes your Data and EMMC partitions. You must perform both steps otherwise it won't work correctly.
Start up Your Nook and follow the Setup. Now download the Update ZIP and drop it on your EMMC's root. Tap the Power button to put the Nook to Sleep. Now Sit back as the Update is installed Automatically.
____________________________________________________
Sent from NookColor CM7 using Tapatalk
A friend who's nook is neutered but not updated wants me to update her nook to the latest Barnes and Noble Rom.
On my nook I run the latest CM7 nightly with OC kernel, and have no problem with CWR etc.
On hers, I want to keep it as stock as possible. Just want to update it to the latest stock ROM. And neuter it so she can use market etc.
What's the easiest way to go from a neutered 1.1 to a neutered 1.2 (or whatever is the recent B&N ROM update)? Thanks, and sorry if I got those ROM version numbers wrong.
Will it update itself?
Just wondering if I leave her alone for a week or two will she receive an OTA update automatically? (over wifi I guess?) (even if it's neutered?)
I would wait for a autonooter to come out for 1.2 before doing anything unless you like living on the edge.
I was using a nootered 1.0.1 this morning, had to format my system and Data partitions to restore the nook back to factory. Then i had to manually update to 1.2.
Now I've lost root capability and access to the market. The market that BN does offer is not very impressive.
Will Autonootered nook receive OTA update?
Anyone who Nootered their nook received the latest update? Thanks.
If you rooted your Nook won't update. If you want to update you have to perform a Factory reset. Go to Nookdevs and find the Remove Root page.
http://www.nookdevs.com/Portal:NookColor
____________________________________________________
Sent from NookColor CM7 using Tapatalk
If you are using a rooted 1.1, you will need to
1.) Flash Clockwork 3.0.1.0 (or newer) to a micro SD card (Google 'clockwork bootable' and look for a result from mrm3[dot]net)
2.) Download the compatible 1.2 signed image (plain, not keepcwm) and put it on the micro SD card that you just flashed. LINK
3.) Turn off your nook color, put in the micro SD card, and power it up.
4.) You will need to 'flash zip from SD card'. Choose the 1.2 file and flash it.
5.) Go back to main menu (the power button functions as the back button) and do a factory restore (this will clear cache as well)
6.) Pull the sd card from your nook color, then choose "reboot"
7.?) I got an install error on first boot. I waited until the screen turned off on its own, then powered back up. It properly booted to the initial registration screen
****Note, you need Clockwork 3.0.1.0 to flash the 1.2 image, otherwise you will get stuck at the 'n' screen when you try to boot.
I just got done flashing from a rooted 1.1 to stock 1.2. Now to tackle rooting 1.2
japzone said:
If you rooted your Nook won't update. If you want to update you have to perform a Factory reset. Go to Nookdevs and find the Remove Root page.
http://www.nookdevs.com/Portal:NookColor
____________________________________________________
Sent from NookColor CM7 using Tapatalk
Click to expand...
Click to collapse
I don't think that's the case.
My rooted 1.1 nook has been sitting untouched for about a week. I turned it on today and it looks like I got the OTA update (I am being asked to register when I turn it on as if it was a new nook). As I said, it was rooted and had the 1.1 update only.
japzone said:
If you rooted your Nook won't update. If you want to update you have to perform a Factory reset.
Click to expand...
Click to collapse
Not quite true. There's been anecdotal evidence that a rooted NC with CWM installed in emmc may prevent updates. But as others have mentioned many rooted NC have been updated.
fpga_guy said:
Not quite true. There's been anecdotal evidence that a rooted NC with CWM installed in emmc may prevent updates. But as others have mentioned many rooted NC have been updated.
Click to expand...
Click to collapse
Finished rooting after 1.2 update on my stock backup NC. The MN works just fine. I would suggest backuping up files and flashing back to stock (1.1.0) the rooted NC. Only way I know of to ensure a clean eMMC.
Then load the 1.2 downloaded file from BN and update. Then snag the MN to root.
Side note: Use latest CWR 3.0.2.8 and not 3.0.1.0
Once the 1.2 is rooted you'll probably need to do the "standard gapps" reset (clear cache & FC Apps the Google Framework). Then the entire Market will show.
Note also: some apps will fail to install (for me Angry Birds and Aldiko) Use Root Explorer to download the cut/paste file from downloadnull folder to sys/apps, rename and install using package installer.
Above worked for me earlier today.
Just wanted to get the work out that B&N announced on FB this morning (18 minutes ago as I post this) that there is a 1.3 upgrade to the NC.
From the B&N Community link on FB:
Starting today, NOOK Color owners have access to firmware version 1.3, a software update that enhances the best-in-class NOOK Newsstand by offering even more interactive versions of the country’s favorite magazines and newspapers.
Not only does this update offer access to new bestselling titles including People, Time, Sports Illustrated, Fortune, Parents and Fitness magazines, the new capabilities allow for Special Interactive NOOK Editions with enhanced content—like videos, audio podcasts, animations, photo galleries, and more—for select titles. Plus, print subscribers to People, Time, Sports Illustrated and Fortune can enjoy the NOOK Magazine™ versions on their NOOK Color at no additional cost.
Also included in the update are performance improvements and new features.
NOOK Color customers can enjoy these new features through a free software update available at www.nookcolor.com/update or provided over the air (OTA) to customers connected to Wi-Fi beginning this week.
For more details about this update, please read the full press release here.
Click to expand...
Click to collapse
Okay, I have an interesting situation...
I purposefully installed CM7 on a uSD (using verygreen's guide) to keep my NC stock while I am in my warranty and for other reasons.
At some point however, I must have used CWM's (ROM Manager) feature to Flash CWM Recovery. I know this because when I follow B&N's instructions to manually update to 1.3 the NC reboot's into CWM (I had previously removed my uSD with CM7 on it so there would be no trouble with the update process).
When the NC boots into CWM, it is with errors that it does not find a "signed" zip file and I can only reboot (which reboots back into the stock ROM just fine).
I haven't had much time (as I'm at work at the moment) to investigate this so my question is...does anyone know how to remove CWM that has been installed from the "Flash CWM Recovery" feature in ROM Manager? Or is there a way to bypass CWM during the 1.3 update process?
I was hoping to have this on 1.3 so I could play with it at lunch
Any ideas?
P.S. I am hoping to be able to remove CWM without resorting to flashing a new stock ROM if possible....
cdaters said:
Just wanted to get the work out that B&N announced on FB this morning (18 minutes ago as I post this) that there is a 1.3 upgrade to the NC.
From the B&N Community link on FB:
Click to expand...
Click to collapse
You are a little late.... http://forum.xda-developers.com/showthread.php?t=1231136
patruns said:
You are a little late.... http://forum.xda-developers.com/showthread.php?t=1231136
Click to expand...
Click to collapse
Saw that after I posted...I guess I'll have to follow them on twitter, heh
fwiw, I just loaded the stock rom over the top of my stock rom that had CWM flashed to the eMMC.
I wish that CWM had a feature to "un-flash" and that locations were not hard coded in the app (because it seems that it wants to install to eMMC every time) so it could be used interchangeably with the eMMC or a uSD installation of custom ROMs.
Perhaps verygreen's instructions should be updated. I have seen far too many people who ended up with custom coding on their eMMC and that is definitely a no no..... verygreen has not posted in over a month though he has been here.....
patruns said:
... verygreen has not posted in over a month though he has been here.....
Click to expand...
Click to collapse
Yeah. I had PM'd him regarding his installer a while ago but he has not responded either...he has fallen into "lurker mode"
I don't even know what I was thinking when I flashed it, probably just to see what it did with regard to running from the uSD more than anything else. I had previously been using CM7 on the eMMC before I went the CM7 from the uSD route.
Verygreen very clearly outlines the update process though if we just read his guide. I'll be the first to admit that I usually skim through things and jump right to it, heh, I am sure others do this too. So I can see where it is easy to miss. Even seasoned IT people like me miss things.
So I decided to root the nook this weekend and I'm having some issues that I can't get around.
I've rooted and ROM'd a few droids so far without an issue. I'm not an expert but I'm also not a noob.
I built up a bootable 1gb CWM and loaded up manualnooter-4-5-18 and manualnooter-4-6-16. CWM was pretty simple, and allowed me to load both of them up without an issue. (I've done both with and without a full wipe)
Once it reboots, it's perfect. market works, web works, rom manager permission fixes..everything works well.
The issue is once I power it off and back on, it's done. It hangs at the "Nook Color" splash screen (After the Read Everywhere and big grey N) and refuses to power up the OS. The onyl way i can get it back is to do a complete factory restore (power+vol button+N)
What am I doing wrong?
It sounds like you are suffering from the Flash / Air lockup problem. If you search the forums, there are links to download the zips that fix the issue.
I would also go to CWM 3.2.0.1 2.8 is rather old and 0.1 is a much easier experience especially on the new nooks.
I rooted two new nooks for my friend's kids Christmas presents last week. I used 3.2.0.1, Nooter 4-6-16 and used the adobe flash and air fixes and it went smooth.
Check this thread concerning the flash fix:
http://forum.xda-developers.com/showthread.php?t=1208896
Props to GMPOWER for his published answer.
Hope it works for you.
Ok cool, thanks OrionLTD. That sounds like my EXACT issue.
“jaromrnelson” continued the project, and has a more up to date version at the link below. His updated one will fix Adobe flash and Adobe Air. Once the fix has been applied, you should not have a problem whenever they update again.
LINK
Thanks GMPOWER, I'll try that one tonight.
Well... I tried these methods and I'm still boot looping as soon as Adobe updates from the Market.
el_bobbo said:
Well... I tried these methods and I'm still boot looping as soon as Adobe updates from the Market.
Click to expand...
Click to collapse
Take a look at http://forum.xda-developers.com/showpost.php?p=20456719&postcount=1631
Wiping and updating to 1.4.1 followed by the above should do nicely. It's working beyond expectations for me and some others.
That worked for me as well!
Although I had the old market at first after root.
I erased and deregistered and registered again and then applied the root 5-12-20 again and have newest market and so far so good, all is well
I might give that one a whirl, thanks guys.
The issue I had is that a newer version of Adobe had come out since GMPOWER's zip was released. There was another link in that thread to a newer zip (From another member) that ultimately resolved the issue.
There was one fix for boot loop involving Titanium backup, I used that one and never had the problem again.
I think that may be the one you are referring to?