Database Users

UnRoot - where to find RC30

When I bought my phone it had RC30 on it. I suspect that if I have to return my phone they will expect at least RC30, I 'd prefer not to have to count on or wait for an OTA. So,.. I do know how to go to 29, but 30 can I D/L it somewhere...
I have seen the 30 to 33 upgrade but that is of not help sine obviously you have to be at 30 to use it.
I am currently rooted but would like to know the whole way out. Just in case.
Thanks.

you would have to go back to RC29 and use Any Cut to create a shortcut; activity/device info.. and the do OTA using the created shorcut
EDIT, not sure that shortcut will have the "update" key to OTA
EDIT; I found this, is the PLAT RC33 from RC30 update: http://forum.xda-developers.com/showthread.php?p=3300937

I follow you.
So lets see, use anycut to create a shortcut to update. Drop the keys for 29 and 29 back to the G1. Reboot use the anycut shortcut to execute the update/check and If all goes well an update occurs.... Good thinking, I like it buy I always deal in worst case scenarios...
What if THEY decide to stop issuing RC30 to prevent us rooters from coming back... I'd really like to find a D/L copy if possible.

Thanks ... I just saw your edit... that is for 30 to 33, well maybe, it is an unconfirmed full update hopefully it is what I am looking for... but if it is not my search continues.

they really dont care about the rc version as long isn't "JF"
EDIT; I also thing you can still returned with RC29, dont see why not

Yeah, I guess I just don't want any problems, since I bought my phone and it came with 30 on it I figure they might notice if I sent it back with 29...hehe maybe not. Anyway this is just me doing the worst case thing, just in case.
However, it might not make a difference now but it might later on down the road... when everyone is sitting at 33+++ and suddeny someone sends back a 29 phone...then again maybe not...

So no other guesses foe RC 30...hmmmm

So in my travels I have found the thread : http://forum.xda-developers.com/showthread.php?t=463779&highlight=rc29+nbh&page=1 which looks like it contains a link to the stock RC30 image..am I correct????
I was initially looking for a stock RC30 image since that is what my G1 came with...in case it had to go back and assuming I could flash it.
So an I correct in assuming that this is a valid way to return to the land of "stockdome"?

Help please - Root / ROM info

Greetings all
I realize the info I need is probably posted here... somewhere. But, at this point I am beyond confused.
I did the first, 2nd and the 3rd Eris leaks and my info is as follows
[Firmware - 2.1
baseband - 2.42.00.04.12
kernel - 2.6.29-8a03cb9a
htc-kernel and18-2#1
build - 2.36.605.1 cl165907 release-keys
software - 2.36.605.1
browser - 3.1
pri - 2.11_002
prl - 51920
Truthfully, I dont know what any of it means. I don't know if I am able to Root or not or even what I would be getting If I did or if I need to.
I also Don't know which of the dozen or so tutorials, fixes, ROM's etc I should trust, try or attempt or what they mean
What I do know is simple. I want the phone to work when all is said and done. Meaning, I want the GPS, Bluetooth, WiFi etc to all function properly.
What I would like is also simple and that is, to be able to get rid of the 1.2 dozen or so apps that I must constantly kill on this phone ( MP3 store, Voce Dialer, my uploads etc.) and the 20+ I have to kill on reboot. And have my phone run as smooth, fast and trouble free as possible.
The only widget I run is the weather, currently either 9s or weather bug and I also have a widget for Pandora and an app called music player on the home screen, but neither of those should be or need to be running, all syncs, auto updates, message / mail pushing are turned off or set to manual, this phone is a phone first, weather 2nd, and internet & email 3rd. all the other things are just toys to me. I would use the Sense weather widget if I could but I am
using Launcherpro so can only Open the sense weather app manually, not with the perfect 1x2 widget or full screen one. I also use the Sense Calender/ agenda app and would like to continue to do so.
I would also like, as I said, have everything else just work, the google account syncing, the market, all the other stuff that is needed in the background to make the unit function properly.
I Hope somebody out there understands what I am trying to convey to all of you, and I don't come off as being to demanding or inflexible. I am open to anything as long as it will do what I need. I know a lot of people here are Techies and want the latest, greatest, fastest etc. but I just need things to work. If that means staying with what I got, so be it.
My biggest grips with the phone is the crap that runs in the background, that I must kill and constantly restarts, even when the phone is idle. If this can be fixed in Root, I am all for it, if android 2.2 fixes this, ditto. if there is another way that doens't require any of this, I am open to suggestions on that as well.
But, I must stress, I do need this phone to simply work as intended. I am in the minority I am sure but I actually use the "phone" part more then anything else and need it to just work.
Maybe I don't need root! I really don't know. But as it stands now, with leak3 I will get no future updates or fixes unless I have it or something similar, Correct?
Thanks for any simplified help or advice on this
P.S if at all possible, please dont direct me to another link to read. Unless, that will do exactly what I am trying to accomplish and need the phone to do. And, is fairly simple to understand and execute. Not one full of links telling me, you need this, so go here and u will want that so go there etc..
This is realy important with the"ROM" issue, which I realy dont understand at all
Thanks in advance
Kalie

yes you can root it is benificial to most, and follow these instructions to ROOT after reading more into the matter. If you need any personal help still you may PM me tomorrow and i will at least help you find all the necessary resources and knowledge to decide if you should root or not.

Please move to general discussion.
I think the first thing that you really need to understand is that with Android things are going to run in the background, regardless of what you do. Background process run whether stock or rooted. There are no custom ROMs that somehow prevent background processes from running. It took me a long time to come to terms with this concept because I want to feel like everything on my phone is "clean". However, with Android the system is meant to run this way and the OS will stop processes only when needed. When you kill processes via task manager app or whatever you are simply wasting time, slowing down your phone, wasting battery, and maybe causing other "hiccups" in the operation of the system. As much as it feels good to make sure that stuff is not running you are really doing no good by constantly chasing your tail on this issue.
With leak v3 you can receive future updates. If you haven't already, you should be receiving the MR4 OTA update which includes some minor bug fixes.
Obtaining root is going to give you the ability to apply custom ROMs but I am not sure that this will accomplish what you have in mind. Custom ROMs do offer some significant performance enhancements but they will not stop background apps from running and all of them include a good number of the native apps that you want to get rid of (amazon mp3, etc). With root you can remove native apps but it is another required learning process.
Rooting your phone is more than just loading a custom ROM, it is a learning process that requires a lot of reading and understanding of how the operating system works, how to load custom ROMs, and all of the other things that come along with rooting.
I understand that you want to make this as easy as possible but learning is only easy if you are interested in what you are trying to do. I don't want to discourage you from rooting your Eris but I do think that you need to take some time to understand what it is that you are considering doing.
There are a lot of great resources on this site to use to educate yourself on the root process and what rooting really means for you. Good luck
mod, please move this to the general section, not a development topic, thanks.

"With leak v3 you can receive future updates. If you haven't already, you should be receiving the MR4 OTA update which includes some minor bug fixes.
"
Did I read this correctly?
Since I installed Leak 1 and the subsequent leak 2 and leak 3, I have not had any updates from verizon.
At what point in time, if ever, will I get an update from Verizon that does not come from a forum and or somebody claiming they figured it out and it's the same as the official, just "Not Official" since i am on the leaked version of Android 2.1
If I can eventually get 2.2 android, without going thru the Agg. of rooting and the trial and eroor with the many different ROMS, I would love that.
With that said, if there is something proven I can do , to undo what I have done ( Leak 1, 2 and 3) that will allow my phone then to be "Officialy" updated by verizon I would love to know how to do this
Thanks again for the Help
Kalie S

WaveSecure Serious Vulnerability!!

I'm using Modaco latest r8 rom with froyo 2.2. I noticed 2 things:
1. wave secure will not download my account data automatically when I factory reset. I need to register again which make it vulnerable. >> Anyone can disable wave secure
2. I don't even need to factory reset and I can reset wave secure by clearing the data in settings!!!!
I have tried in original HTC ROM 2.09(rooted) and flash in /system/app. same situation.
And I've tried that if wavesecure hasn't been register, you can't lock it from wavesecure.com or sms
I don't know if this is due to the nature of froyo or it's been like this since 2.1
wave secure is practically useless right now on my phone!!
Anyone can confirm this?

called them and they said they disabled the function for temp as they are working on some fix, it will be up again in 3 weeks as what they said

Yep, saw this on MoDaCo. Will not be renewing my WaveSecure subscription.

Lets be honest, it was a waste of money to begin with right.

This whole thing makes me wonder...can an Android phone REALLY be protected by these kind of softwares? Even assuming there are no security issues with the app..I mean,a lot of Android phones are rooted by their owners and all are rootable (?) without booting into the OS, so even if said apps are installed as system apps (just like wavesecure can be) what's preventing a "smart/geek" thief from pulling the battery, changing the simcard,(rooting a non-rooted phone), booting into recovery, mounting system and wreaking havoc through adb, including removing the security app?? Am i going on a wild goose chase or is all this sound??

MacCarron said:
This whole thing makes me wonder...can an Android phone REALLY be protected by these kind of softwares? Even assuming there are no security issues with the app..I mean,a lot of Android phones are rooted by their owners and all are rootable (?) without booting into the OS, so even if said apps are installed as system apps (just like wavesecure can be) what's preventing a "smart/geek" thief from pulling the battery, changing the simcard,(rooting a non-rooted phone), booting into recovery, mounting system and wreaking havoc through adb, including removing the security app?? Am i going on a wild goose chase or is all this sound??
Click to expand...
Click to collapse
Yeah, but I don't think the average mugger/thief is that smart
Sent from my HTC Desire using Tapatalk

So can I cancel my current subscription then and get a refund?

If you install wavesecure to /system/app and make sure its only there and not in /data/app as well then you should not have this problem.
Also wavesecure have gone through a rough month, got brought by Mcafee who in turn just got brought by Intel. They need to adjust to the new owners. They are (were) only a small company and lets face it their app is the best around by a long long way.
If you have any problems or suggestions on how to improve they usually listen (it was one of TeamVillain and a xda mod who suggested they make a update.zip for /system/app and a number of other improvements and they did it straight away).
Don't just say "oh no its not working" no app can protect your phone from the right people, if someone who knows all about rooting etc gets your phone then your screwed anwyay. But the average joe thug who steals your phone will get it, put in a new sim the alarm will go crazy then they panic, drop the phone and run. You can then use the tracker to find it, or give details to police.
Just put the apk in your rom next time before you flash in system/app and flash the rom. Restore data from a backup (but not the app) and you still get your market link too.

Lennyuk said:
If you install wavesecure to /system/app and make sure its only there and not in /data/app as well then you should not have this problem.
Also wavesecure have gone through a rough month, got brought by Mcafee who in turn just got brought by Intel. They need to adjust to the new owners. They are (were) only a small company and lets face it their app is the best around by a long long way.
If you have any problems or suggestions on how to improve they usually listen (it was one of TeamVillain and a xda mod who suggested they make a update.zip for /system/app and a number of other improvements and they did it straight away).
Don't just say "oh no its not working" no app can protect your phone from the right people, if someone who knows all about rooting etc gets your phone then your screwed anwyay. But the average joe thug who steals your phone will get it, put in a new sim the alarm will go crazy then they panic, drop the phone and run. You can then use the tracker to find it, or give details to police.
Just put the apk in your rom next time before you flash in system/app and flash the rom. Restore data from a backup (but not the app) and you still get your market link too.
Click to expand...
Click to collapse
While i agree with you that a witch hunt isn't the proper response and that it is unlikely that the average thief will know his way around adb, i have personally tried to remove wavesecure from /system/app...it works...i did it without breaking a sweat. I intentionally triggered the lock by attempting to uninstall the uninstall-protection, pulled off the battery, booted in recovery and got rid of wavese cure with a single command. Reboot and presto! A free phone . So it is true that there is no full-proof way to be safeguarded, at least using this software, and in my humble opinion the guys over at wavesecure should clearly state so on their website. And they don't always listen..there is a long story of noisy silences concerning op's issue...omissions, censorship etc etc. I got a free lifetime subscription so i'm not particularly yelling at anyone, just making hypothetis, but wouldn't you be quite pissed off if someone stole your phone and rendered it's security software (for which you payed) impotent just because he knew "SU"?

MacCarron said:
While i agree with you that a witch hunt isn't the proper response and that it is unlikely that the average thief will know his way around adb, i have personally tried to remove wavesecure from /system/app...it works...i did it without breaking a sweat. I intentionally triggered the lock by attempting to uninstall the uninstall-protection, pulled off the battery, booted in recovery and got rid of wavese cure with a single command. Reboot and presto! A free phone . So it is true that there is no full-proof way to be safeguarded, at least using this software, and in my humble opinion the guys over at wavesecure should clearly state so on their website. And they don't always listen..there is a long story of noisy silences concerning op's issue...omissions, censorship etc etc. I got a free lifetime subscription so i'm not particularly yelling at anyone, just making hypothetis, but wouldn't you be quite pissed off if someone stole your phone and rendered it's security software (for which you payed) impotent just because he knew "SU"?
Click to expand...
Click to collapse
The thing is though, if they knew SU and other commands chances are they will get around any protection whatever it would be.
But Wavesecure offers you a way to track the phone, you can still contact your carrier and get them to IMEI blacklist it, then track the handset down via wavesecure.

hi - just check out secrep5265.blogspot.com - thats interesting information concerning your discussion.

Does changing the date actually force the update check?

Can anyone confirm that changing the date actually forces a check? Though the idea has been tossed around here like truth for a couple of days, I have seen only one post where someone said it works. Everyone else has said something along the lines of: I came home and it was up.
Everyone knows that if you set the clock forward, it says that the system was checked under system updates. Sorry, but that's not proof that it checks. That's proof that update check clock changes. I am asking if anyone has proof that changing the clock date actually forces a check. Proof would be either:
1) Someone has had the update actually happen immediately after changing the clock; or
2) There's evidence of internet activity consistent with checking for an update.
Can someone who's gotten the update explain what it looks like? When you turned it on, did it come up right after the animation? If you did the date trick, did you click "set" and it popped up immediately on screen? I am starting to think that the date change thing is only slowing this down; it just resets the clock for the update, it doesn't actually force the check.
Anyone have any other ideas? I am supposed to be studying for a final which is certainly why I'm obsessing about this, but I really can't help it. Anything to take my mind off studying for that horrible class. This final is going to kill me. (Then again, it's the last one I will EVER take!!!)

No it hasn't worked for me.

Coldheat1906 said:
No it hasn't worked for me.
Click to expand...
Click to collapse
Thanks. It hasn't worked for many people. I'm curious if anyone knows if it CAN work, or if it's just a myth.

the update will appear as a notification on the lower right hand of your Xoom kin a like a notification like you are downloading something from the market.

slack04 said:
Can anyone confirm that changing the date actually forces a check? ...
Click to expand...
Click to collapse
On my Wifi only Xoom it forces a check.
For example;
1. My Xoom says it last checked for an update at 1:10pm and it is now 6:10pm on the same day
2. I change the date to one day in advance
3. I go to sytem updates and it says it last checked at 6:10pm
So it did force a check.
Whether or not an update is available for your Xoom is a different story.
The date change will force a check but not force the actual update.

laredo7mm said:
On my Wifi only Xoom it forces a check.
For example;
1. My Xoom says it last checked for an update at 1:10pm and it is now 6:10pm on the same day
2. I change the date to one day in advance
3. I go to sytem updates and it says it last checked at 6:10pm
So it did force a check.
Whether or not an update is available for your Xoom is a different story.
The date change will force a check but not force the actual update.
Click to expand...
Click to collapse
Sorry, but that's not proof that it checks. That's proof that update check clock changes. I thought that was clear in my first post. I am asking if anyone has proof that changing the clock date actually forces a check. Proof would be either:
1) Someone has had the update actually happen immediately after changing the clock; or
2) There's evidence of internet activity consistent with checking for an update.

you can force an update check using these steps:
1. hold power+volup, the xoom will reboot
2. after reboot go to system settings and check for updates

doin this hasn't worked for me at all. Tried several times even with reboots. Yes the time changes but doesn't mean it really did anything. Frustrated the Wifi users are rolling today and here I sit with 3G and nothing still.

ruinah said:
doin this hasn't worked for me at all. Tried several times even with reboots. Yes the time changes but doesn't mean it really did anything. Frustrated the Wifi users are rolling today and here I sit with 3G and nothing still.
Click to expand...
Click to collapse
Yesterday I re-imaged my xoom to stock but realized too late that I was using 3.0 instead of 3.0.1. I went in and changed the date and set it back to automatic. My Xoom immediately started downloading the 3.0.1 patch. That is about as much proof as I can provide.

Yes it does force a check
This is what shows up in the logcat after changing the date:
D/SystemClock( 8596): Setting time of day to sec=1307904965
D/SystemClock( 133): Setting time of day to sec=1305226357
D/Beautiful Widgets( 846): Received Weather refresh Intent
E/Beautiful Widgets( 846): Acquiring new WakeLock on an existing notheld instance
D/Beautiful Widgets( 846): Service for Weather started
V/Beautiful Widgets( 846): Service AccuWeather onStart()
D/Beautiful Widgets( 846): Service AccuWeather Thread started
I/Beautiful Widgets( 846): Provider is network
I/Beautiful Widgets( 846): Requesting location update
I/EventLogService( 247): Aggregate from 1307904746624 (log), 1307904746506 (data)
E/TelephonyManager( 247): Hidden constructor called more than once per process!
E/TelephonyManager( 247): Original: com.google.android.location, new: com.google.android.gsf
I/CheckinService( 247): Preparing to send checkin request
I/EventLogService( 247): Accumulating logs since 1307904965403
D/dalvikvm( 846): GC_CONCURRENT freed 867K, 13% free 8280K/9479K, paused 3ms+4ms
I/CheckinTask( 247): Sending checkin request (1486 bytes)
D/dalvikvm( 846): GC_CONCURRENT freed 561K, 12% free 8406K/9479K, paused 3ms+3ms
V/AlarmClock( 8642): AlarmInitReceiver finished
D/dalvikvm( 133): GC_CONCURRENT freed 3891K, 29% free 21271K/29639K, paused 4ms+10ms
D/CalendarWidget( 8547): Scheduled next update at [1307941200000] 00:00:00 (+603 mins)
D/dalvikvm( 846): GC_CONCURRENT freed 963K, 14% free 8177K/9479K, paused 5ms+7ms
D/dalvikvm( 846): GC_CONCURRENT freed 494K, 12% free 8348K/9479K, paused 4ms+3ms
D/dalvikvm( 227): GC_FOR_ALLOC freed 1629K, 3% free 124319K/127879K, paused 77ms
D/dalvikvm( 227): GC_CONCURRENT freed 519K, 3% free 124143K/127879K, paused 2ms+13ms
I/CheckinTask( 247): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
I/CheckinService( 247): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
As you can see I still haven't gotten 3.1

El Daddy said:
This is what shows up in the logcat after changing the date:
D/SystemClock( 8596): Setting time of day to sec=1307904965
D/SystemClock( 133): Setting time of day to sec=1305226357
...
...
...
I/CheckinTask( 247): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
I/CheckinService( 247): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
Click to expand...
Click to collapse
slack04 said:
Sorry, but that's not proof that it checks. That's proof that update check clock changes. I thought that was clear in my first post...
Click to expand...
Click to collapse
Well, there you have your proof. Now, go study and quit being such a d-bag. I guess you were not clear since you had to go back and edit your post after I submitted my initial response.

laredo7mm said:
Well, there you have your proof. Now, go study and quit being such a d-bag. I guess you were not clear since you had to go back and edit your post after I submitted my initial response.
Click to expand...
Click to collapse
Excuse me? Yeah, I edited the post to make my question more clear.
Your post was not useful; in fact it showed that you hadn't really thought through the process before you posted. I wasn't rude to you, I just pointed out the error in your logic, which made me realize that I should go back and clarify my question. Who's the "d-bag" here?

Huh? I edited my post to bold the checkin. I skimmed through this thread and thought I would confirm to people it did indeed check in. I'm not trying to show anyone up. Just trying to be helpful.
Wtf?
Sent from my Xoom using XDA Premium App

El Daddy said:
Huh? I edited my post to bold the checkin. I skimmed through this thread and thought I would confirm to people it did indeed check in. I'm not trying to show anyone up. Just trying to be helpful.
Wtf?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Thanks dude, you answered the question. He was actually talking to me; I couldn't tell you what his problem is, though. In any case, you've answered the question, so I'm going to go back to clock-changing-update-checking right now! Thank you!

well I'm just glad its been proven. And I don't agree with the ops original statement that it would have caused an issue if it didn't actually force a check. Only because I don't feel that changing the date would actually affect anything to do with checking for an update, either way it is checking the same server w/the same access codes.
For example, if someone would have 3.0 and set the date back to the xooms launch day and ran a check for an update would still be updated to 3.01 or if lucky 3.1.
Like the date on your xoom is only for creating time stamps on the xoom.

I explained how this works in my post below:
http://forum.xda-developers.com/showthread.php?t=1076295

RadDudeTommy said:
well I'm just glad its been proven. And I don't agree with the ops original statement that it would have caused an issue if it didn't actually force a check. Only because I don't feel that changing the date would actually affect anything to do with checking for an update, either way it is checking the same server w/the same access codes.
For example, if someone would have 3.0 and set the date back to the xooms launch day and ran a check for an update would still be updated to 3.01 or if lucky 3.1.
Like the date on your xoom is only for creating time stamps on the xoom.
Click to expand...
Click to collapse
It's moot at this point, but it was when you wrote your post also. What I was suggesting was that, if it wasn't actually checking by changing the date, then we could be stopping the actual update check from happening by trying, therefore setting us back by 12 hours (about the frequency of the automatic checks) every time we tried to "cheat." Of course, now that it's shown that the check does actually query the server (and that makes very little difference to when you actually get your update) my original guess (not statement) is obviously incorrect.

laredo7mm said:
Well, there you have your proof. Now, go study and quit being such a d-bag. I guess you were not clear since you had to go back and edit your post after I submitted my initial response.
Click to expand...
Click to collapse
+1
Really getting tired of this guy talking down to everyone. Don't know when I have ever see someone as condescending.
Sent from my ADR6300 using XDA App

RadDudeTommy said:
well I'm just glad its been proven. And I don't agree with the ops original statement that it would have caused an issue if it didn't actually force a check. Only because I don't feel that changing the date would actually affect anything to do with checking for an update, either way it is checking the same server w/the same access codes.
For example, if someone would have 3.0 and set the date back to the xooms launch day and ran a check for an update would still be updated to 3.01 or if lucky 3.1.
Like the date on your xoom is only for creating time stamps on the xoom.
Click to expand...
Click to collapse
Suppose our entire solar system was contained in a drop of water abiut to get wiped by a windshield wiper?

kyoteqwik said:
+1
Really getting tired of this guy talking down to everyone. Don't know when I have ever see someone as condescending.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
That's friendly.

[Q] Anyone know what ADCP does?

I notice there's always a system process called ADCP running, I think it stood for Amazon Device Control Program. Anyone investigated what it does and what happens if you disable it? I'm wondering if it's involved in any way with the OTA updates, and also what ramification disabling it has, like will the various Amazon programs not work right? I've not been adventurous enough to experiment with, in fact I've got my wifi off for now until it's clear whether the OTA update can be blocked by the methods discussed here.

jb0ne said:
I notice there's always a system process called ADCP running, I think it stood for Amazon Device Control Program. Anyone investigated what it does and what happens if you disable it? I'm wondering if it's involved in any way with the OTA updates, and also what ramification disabling it has, like will the various Amazon programs not work right? I've not been adventurous enough to experiment with, in fact I've got my wifi off for now until it's clear whether the OTA update can be blocked by the methods discussed here.
Click to expand...
Click to collapse
check this out
http://forum.xda-developers.com/showpost.php?p=20166149&postcount=1
essentially it connects the amazon apps to the kindle registration

I'm suspicious, I suspect it does more, and is the thing responsible for the OTA updates everyone is getting no matter what they do....

I really want to try and freeze it, but too afraid that it might actually be necessary...

Well I installed Droidwall and didn't give permissions to ADCP and so far my device is still registered and I can watch videos and use my books, can use the Amazon App Store (I gave it permissions, I don't think it's the program responsible). I've effectively disabled ADCP by not allowing it to connect to the internet, but it's still running in case it does, say, DRM services or something. All good and still on 6.2 (and I did do the other suggestions previously).

jb0ne said:
Well I installed Droidwall and didn't give permissions to ADCP and so far my device is still registered and I can watch videos and use my books, can use the Amazon App Store (I gave it permissions, I don't think it's the program responsible). I've effectively disabled ADCP by not allowing it to connect to the internet, but it's still running in case it does, say, DRM services or something. All good and still on 6.2 (and I did do the other suggestions previously).
Click to expand...
Click to collapse
Glad it worked for someone else too. I am not sure which process is actually responsible for downloading and installing the update though.
EDIT: Oh, I didn't post about DroidWall in this forum. I figured out DroidWall last night and we posted on Gizmodo about it.

An important element I overlooked, even after adding apps to the whitelist, you have to go back to Menu and enable firewall. It's NOT enabled by default even if you change whitelist apps. Even though I had it not running firewall until 10 minutes ago, I hadn't received update. Maybe moving otacerts.zip stopped it....

jb0ne said:
I'm suspicious, I suspect it does more, and is the thing responsible for the OTA updates everyone is getting no matter what they do....
Click to expand...
Click to collapse
I installed ADCP on CM7 when I was trying to find a way to get amazon video working. It brings up the page to register your kindle, but it never seemed to work right on CM7. There's a different apk for the OTA update, if I remember correctly.

You could put /system/etc/security/otacerts.zip back in and see if ADCP then lets your register your kindle.