Comments on: OTAs in JFv1.51

By: Custom Firmware von zx128 - unslaved - Seite 15 - Android-Hilfe.de

Custom Firmware von zx128 - unslaved - Seite 15 - Android-Hilfe.de — Tue, 08 Sep 2009 07:59:39 +0000

[...] [...]

By: Guest

Guest — Thu, 20 Aug 2009 02:16:29 +0000

Hmm. A month later and still no CRC1 update. Maybe it’s time to switch to cyanogen.

By: franta

franta — Wed, 19 Aug 2009 20:19:50 +0000

Would it be possible to include crc37 update also?

By: Djerk Geurts

Djerk Geurts — Tue, 18 Aug 2009 08:09:33 +0000

FYI. Just had an OTA pushed (UK) 1.5 CRC37 which is a 45MB download and according to “more info” contains a security fix…

By: BeEoTcH

BeEoTcH — Mon, 17 Aug 2009 22:44:27 +0000

“I should be able to get something out soon (next few days)”

Where is it? This sux!

By: RichieDaze

RichieDaze — Mon, 17 Aug 2009 20:07:55 +0000

Hey JF, did you get locked up again…jk..Lol. We’re still waiting for your update. But since it’s not out yet, it makes us wonder what NEW (energy + time) consuming project your working on. Time flys when your having fun or with problems. Don’t forget us…
By the way are you hiring???

By: david

david — Mon, 17 Aug 2009 03:47:27 +0000

come back dude i love ur stuff

By: Reggie

Reggie — Sun, 16 Aug 2009 13:49:00 +0000

Any idea on when the update is coming out??? I’ve been checking the JF updater for the past month with no joy.

I deleted the signed-kila….zip file from the cache folder. I also changed the permissions on the actual cache folder with chmod 000 cache (not sure what this does to other programs on the OS but the only thing I see in there is a download.apk file which has been there since I’ve been tweaking this thing). This makes it stop till a reboot. I hadn’t had the issue for weeks until I went on travel. It’s like when you are around new towers the file gets pushed to you again.

By: HippoMan

HippoMan — Sat, 15 Aug 2009 14:48:26 +0000

PS: I forgot to mention that deleting the otacerts.zip file does seem to work at disabling these upgrade requests, but I’m concerned about the bandwidth and battery usage from the system’s continuing attempts to re-download and verify that file.

By: HippoMan

HippoMan — Fri, 14 Aug 2009 20:33:24 +0000

Well, I updated build.prop, but I kept getting upgrade notices. So then I invoked “chmod 000 /cache/*.zip”. However, around 20 minutes later, I got yet another upgrade request.

I’ve been getting these periodically since earlier today (Aug. 14). Since neither the new build.prop nor the “chmod 000″ thing are working, does anyone have any idea how to stop these new upgrade notices?

Despite the reassurances, I’m still nervous that I’ll lose root if I accept this upgrade. Am I overreacting?

By the way, the OTA file in /cache that I chmod’ed to 000 is dated July 19, and it’s named “signed-kila-CRC1-from-CRB43-FIX.7ca4a1d7.zip”, in case that’s important.

Also, the info about the new build.prop that I recently installed is this: size = 2152, checksum (from the “sum” command) = 31941 3