1.0.1 update going back to 1.0.0 - Nook Color General

I have a problem where my NC seems to prefer 1.0.0. So far, every time I manually update it to 1.0.1 it eventually (not immediately) goes through another update automatically & ends up at 1.0.0. I have manually updated to 1.0.1 five times now & am currently back to 1.0.0.
Is there some file that makes it want to do this? How can I stop it?

read through this
http://forum.xda-developers.com/showthread.php?p=9952509
Originally Posted by blamejake
I went from 1.0.1 back to 1.0.0 by going through the power-off/power-on cycle 7-8 times.
Interesting, so is this to say that there is a READ ONLY version of the 1.0.0 ROM on the device and even if you bork /system you can recover from that?
If so, that's really cool. And why not, there's enough space in the thing for it..

Related

Disabling otacerts on 1.0.1 + using shop

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.

Nook won't root

I don't understand what's going on. I am not a noob; I've rooted 10+ android devices and have been in the mobile game since windows mobile 5.
I follow all instructions to the T from here
http://nookdevs.com/NookColor_Rooting
Everything goes as it should until it is time for the final reboot. Instead of displaying a new boot animation, it simply gets stuck at the screen with the lowercase "n" that says the blurb about adobe at the bottom.
Same both with the SD card in, and without it.
I am able to salvage the situation by doing the 8 interrupted boot plus the homescreen and power key. Started from scratch again - updated to 1.01, reflashed the sd card, etc.
Same result. This is a brand new device, just bought today.
Any ideas? You don't think they killed the root exploit, do you?
I believe I just figured out the problem. The link in the WIKI to the B&N 1.01 update is outdated and incorrect - it links to the incompatible 1.1 update instead, which is not autonooter supported.
Those instructions worked for me. It sounds as if your boot partition is completely empty. Are you using Auto-nooter 2.12.25? That is the version you need to use if your NC is already running 1.0.1.
edit:
Just saw your update. In that case in the B&N link replace 1.1.0 with 1.0.1 eg:
http://images.barnesandnoble.com/presources/download/nookcolor/v1.1/Sideload_update.zip
should be:
http://images.barnesandnoble.com/presources/download/nookcolor/v1.0.1/Sideload_update.zip
otherwise there are a couple other threads where people have thrown up the 1.0.1 sideload update.
computerpro3 said:
I believe I just figured out the problem. The link in the WIKI to the B&N 1.01 update is outdated and incorrect - it links to the incompatible 1.1 update instead, which is not autonooter supported.
Click to expand...
Click to collapse
The link has not changed, the B&N reference within it has. But perhaps something should be tweaked on the URL for now, or the instructions. Done.

BN Registration information question

Howdy, I am running rooted stock NC with the build.prop edit to stop the 1.1 update. This is (well finally successful due to my own errors) working out just great! However, I am unable to register my device anymore through the NC as it says there is an issue and reflashes me without any chance to stop it thus forcing me to restore it back again.
Is there a place within the com.bn.*** series of files or elsewhere that I could edit to have the device report back as being registered and such?
I thought perhaps if I did not go into the store section of the nook, I would be good to go, however when I went into magazines it threw me FOTA again.
Any ideas are greatly appreciated!
error DAD1202 in lower left corner?
nope, when i restored and managed to get the build.prop edit to work (i hadnt rebooted to finalize) the green N was there telling me I am updated, go into the about your nook and build is 1.1 as well. Everything is fun UNLESS I go into any aspect of the nook store, then I get an unregistered device and it makes me factory fresh again.

How to sideload 1.2 update to a 1.1 rooted NC?

Hey there Guys & Gals,
Searched throughout the forums and couldn't seem to find a straight answer on this.
I originally rooted my wife's 1.0.1 NC using Autonooter. That worked out great and then I was able to sideload the 1.1.0 NC updated using ROM Manager and CWR to apply the pre-rooted update ROM (this is where I got the pre-rooted sideload: http://forum.xda-developers.com/showthread.php?t=932145). After that I used an SQL editor to turn all the software updates to manual. This manual switch has held the 1.2.0 update off and everything is working great.
However, I'm really interested in 1.2.0 and would love to apply another sideloaded, pre-rooted update IF that exists. Does anyone know if this is out there? It sounds like most NC owners are running CM7 now as opposed to going down the stock rooted (no ROM) version of the NC. Is there anyone who was successfully able to load up rooted 1.2 from rooted 1.1 without having to resort to an alternate ROM?
As a side question, has any 1.1 NC owners had success with the Netflix app or does that absolutely require at least 1.2 to work correctly?
Thanks for your help!!!
-Stephen
Wanted to bump this one again in case anyone had any suggestions. If not, I'll let this thread die.
Same boat here. I'm still running 1.1 with updates set to manual but I have CM7 on SD. I would also like to update to 1.2 but as far as I know, the only way to do it is to return to stock, unrooted 1.1 and then apply the 1.2 update from B&N. After that, you have the manual nooter option to root 1.2.
Have not been able to get Netflix to work on either stock 1.1 or CM7 with and edited build.pro file. It doesn't show up in the Market so I haven't even been able to try to get it to work.
I know there's a CWM-compatible stock 1.2 ROM floating around the dev forum, but I don't know about pre-rooted. It would at least save you unrooting 1.1.
Sounds like best option is to use the 1.2 CWM capable update and then autonoot again... hmmmm. Everything is working great now and I don't want to mess anything up, but netflix and flash are both very tempting...

[Q] Rooted NC 1.1 (w/ Autonooter 3.0) - Update?

I rooted earlier this year a NC with autonooter 3.0 and its been working fine but I haven't paid much attention since. I skipped the 1.2 update, not sure how, but now there is 1.3 update.
We have been using fine since the root and never has it tried to update to 1.2, but everyone seems worried about skipping these updates. Have I been lucky? Is this 1.3 update going to happen whether I want it to or not?
We have used the nook, rebooted several time with a dead battery and never has an update happened. Am I missing something? I'm happy with the NC asos with this root, and still buy things from the BN store and Market.

Categories

Resources