Disabling otacerts on 1.0.1 + using shop - Nook Color General

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.

Related

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.

[Q] Rooted NC and future updates.

I have a rooted NC with stock 1.1 firmware. Im just wondering what's gonna happen when the 1.2 update comes down? Will have to re-root it? If I do then I guess we'll have to wait until someone figures it out and produces a new boot image right? If so then I might not update until that's figured out.
ajaik said:
I have a rooted NC with stock 1.1 firmware. Im just wondering what's gonna happen when the 1.2 update comes down? Will have to re-root it? If I do then I guess we'll have to wait until someone figures it out and produces a new boot image right? If so then I might not update until that's figured out.
Click to expand...
Click to collapse
If you don't do anything, it will update and break root and you will have to wait till that is rooted, HOWEVER! There are tutorials out there that have step-by-step on how to disable the updater, if that's what you want.
If I disable the updater, is it simple to re-enable later when the new rooting process has been figured out?
I would like to know also. Since the new update is supposed to come out by the end of the month I just thought I would keep WiFi off at all times until I researched the best solution.
JLCollier2005 said:
If you don't do anything, it will update and break root and you will have to wait till that is rooted, HOWEVER! There are tutorials out there that have step-by-step on how to disable the updater, if that's what you want.
Click to expand...
Click to collapse
Will 3rd party Apps you've purchased still be present on the device and usable?
Apparently, you just have to rename /system/etc/security/otacerts.zip to /system/etc/security/otacerts.zip.bak
Some people seem to have still gotten updates after renaming though. It's a little vague and some of the info might be outdated. This could potentially throw a wrench in a lot of people's tablets.
Your purchased apps are stored by google. Yes they will still be there. I actually had purchased items from my phone show up on my book...quick download and good to go.
Now, after an update, you may lose them until it's rooted again...
Sent from my LogicPD Zoom2 using XDA Premium App
yeah, if you let the update go through, I can almost say for sure you'll lose access to the apps until you root again and probably redownload them)
To be safe get "Titanium Backup" and Purchase it's ProKey from the Market. Using it you can Batch Backup your Apps and App Data. Then if anything happens you can always Recover your Apps. (Batch Restore needs Pro Key)
For help using Titanium Backup read this Lifehacker article:
http://ca.lifehacker.com/5784857/how-to-set-up-a-fully-automated-app-and-settings-backup-on-android
____________________________________________________
Sent from Nookie Froyo using Tapatalk
If i update it breaks root will I still be able to use the apps that don't require superuser? Meaning can I still use what apps are already in the Nook
sent from my nook color

Stock 1.2 Released with Android 2.2! DETAILS:

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

[Q] Autonooter for 1.2?

Any word on an autonooter for 1.2? Or maybe a rough time frame as to when there will be one? All I can find is manualnooter...
No real time frame as of right now. When the network location stuff is ironed out in a safe way, then an autonooter version might come out. The autonooter format seams to do a better job of implementing everything that it is written to do. ManualNooter is still a great safe product that can be used right now, it is just lacking the network location information.
ManualNooter for all intents and purposes is AutoNooter.
The only thing stopping MN from becoming an AN is before I started school I had been looking for a viable way to make CWM flashable cards Auto-run compatible. I have a method of getting the cards to run the updates automatically but for CWM to do it based on an auto-run script it has to be modified to run the script and therefore the "AutoNooter" update.zip. While I have done this to a couple of versions I started school before I could hammer out the best way to implement this in such a way that other users wouldn't have to reflash for an auto-run capable card and therefore an AN capable card.
The old method of AutoNooter that was used for all pre 1.2 versions is a deprecated method and honestly no one should be trying to recreate that method for new B&N version updates. With ManualNooter and when I can put some time into it, AutoNooter, users have a way of actually seeing when the process is done as opposed having to wait for that reboot or just randomly turning it off cause they thought 30 seconds was too long to wait.
GabrialDestruir said:
ManualNooter for all intents and purposes is AutoNooter.
The only thing stopping MN from becoming an AN is before I started school I had been looking for a viable way to make CWM flashable cards Auto-run compatible. I have a method of getting the cards to run the updates automatically but for CWM to do it based on an auto-run script it has to be modified to run the script and therefore the "AutoNooter" update.zip. While I have done this to a couple of versions I started school before I could hammer out the best way to implement this in such a way that other users wouldn't have to reflash for an auto-run capable card and therefore an AN capable card.
The old method of AutoNooter that was used for all pre 1.2 versions is a deprecated method and honestly no one should be trying to recreate that method for new B&N version updates. With ManualNooter and when I can put some time into it, AutoNooter, users have a way of actually seeing when the process is done as opposed having to wait for that reboot or just randomly turning it off cause they thought 30 seconds was too long to wait.
Click to expand...
Click to collapse
One of the two remaining issues for MN is IMEI apps force closing. Has anyone gotten the [Beta] IMEI generator... to help with this issue in MN roms?
lschroeder said:
One of the two remaining issues for MN is IMEI apps force closing. Has anyone gotten the [Beta] IMEI generator... to help with this issue in MN roms?
Click to expand...
Click to collapse
I don't believe DizzyDen's IMEI program will work with the ManualNooter flash. It should however work to patch the full stock 1.2 ROMs but obviously this is undesirable unless you wish to go back to bone stock.
Dizzy's latest betas however have a feature to pull the framework.jar and your S/N via ADB (or ADB wireless), patch the framework.jar with a psuedo IMEI based on your S/N, and push the modified framework.jar back to your device via ADB. I see no reason why this method wouldn't work with rooted stock.
If you try it be sure to post in Dizzy's thread and let him know what happed.
Martian21

[Q] Which method of stopping Auto-Update is easiest/best?

I looked back and read many "apparent" ways to stop automatic updating for the KFHD, but what is the best way that actually works? I just got my KFHD for Christmas and rooted it the other day but I am a noob and it took me ages to actually figure out how to do. So I don't want it to unroot itself.
Also how often is the KFHD's software actually updated and does each update wreck the root? Like I said I'm such a noob with this stuff!
Thanks in advance!
Callum77 said:
I looked back and read many "apparent" ways to stop automatic updating for the KFHD, but what is the best way that actually works? I just got my KFHD for Christmas and rooted it the other day but I am a noob and it took me ages to actually figure out how to do. So I don't want it to unroot itself.
Also how often is the KFHD's software actually updated and does each update wreck the root? Like I said I'm such a noob with this stuff!
Thanks in advance!
Click to expand...
Click to collapse
I moved ota.zip to downloads and renamed it to a .bak--I am still on 7.1.5 no updates, fast simple.
Chelle01 said:
I moved ota.zip to downloads and renamed it to a .bak--I am still on 7.1.5 no updates, fast simple.
Click to expand...
Click to collapse
Isn't it otacerts.zip? You can find it in system/etc/security folder. I think amazon has figured a way around this if you are running newer software versions already. Nice to know that it will still work if you are running older system versions. I tried it,actually deleted the .zip, and received an update. This was on an 8.9 running 8.1.3(ota to 8.1.4,most current) but most things work the same on the different models.
I've recently tried this, can't confirm if it works, but will let you know: disabled all services within the the ADCP(Amazon Device Client Platform) apk . I use Rom Toolbox, a great app with all the tools you'll need.
Reviving an old thread, but the Androidcowboy states that as of June 16, 2013, renaming the otacerts.zip file still works on the KFHD.
Link
-T
EDIT: I made the change but am still waiting to see if it works. He has not failed me in the past with his information.

Categories

Resources