Sunday, July 19, 2009

OTAs in JFv1.51

If you are on the US or EU versions of JFv1.51, you'll likely get an OTA update notification soon, if you haven't already. I had accidentally left in the otacerts.zip file, which allows OTAs to be downloaded and verified.

For now, there are a few possible work arounds.

1. delete the otacerts.zip file manually. The file is at /system/etc/security/otacerts.zip  But keep in mind if you use this method your phone will continuously re-down the OTA and try to verify it, which is bad on your bandwidth usage and your battery life

2. Replace /system/build.prop on your phone with the one from the ADP1 version of JFv1.51

3. chmod 000 the OTA file in /cache (unconfirmed solution, but is likely to work)

Or you can ignore the popups for now, and wait for my new release based on the new update (CRC1). I promise to "disable" the OTA mechanisms in a better way than simply deleting otacerts.zip :). I should be able to get something out soon (next few days)

In the meantime, even if you accidentally hit "accept" on the popup, it won't be able to install the update when it gets into recovery, so you aren't at risk of losing root access.

64 comments:

  1. Hey JF great to read an Android update from you, any chance of some details of what the update will contain? All the best, Rob.

    ReplyDelete
  2. thanks for the heads up

    ReplyDelete
  3. sweet I was wondering about that update

    ReplyDelete
  4. Will there be an update for the 1.51 ADP builds with the latest security update?

    ReplyDelete
  5. Thanks for the explanation!

    Question: is there a place where we can download just the /system/build.prop file from the ADP1 version of JFv1.51?

    It's not a big deal for me if there isn't such a place. I'm just trying to save some effort, if possible. If not, I'll just wait for the CRC1 update.

    Oh, another question: I presume that the CRC1 update will be available for installation via JFUpdater, correct?

    ReplyDelete
  6. JF: Thanks again for all your hard work.

    Just because I'm curious, do we know for sure its an attempt to close root?

    ReplyDelete
  7. Thanks for the update, I'll be watching for CRC1 .... it will be available via JFUpdater right ... ?

    ReplyDelete
  8. If it's not too much trouble, maybe you could include the following patch to fix a bug that was introduced in the 1.5 update:

    https://review.source.android.com/#change,9780

    (certain official HTC multifunction audio adapters stopped working with the 1.5 release!)

    Not sure if this patch was already included in this latest update.

    ReplyDelete
  9. @HippoMan:
    The build.prop file out of the JFv1.51_CRB43-ADP_BuildEnvironment.tar.gz archive:
    http://www.files.to/get/733234/wa5pny6i1a

    ReplyDelete
  10. Option #3, no joy. I'll wait for the true update, and keep hit that annoying "Install Later" button.

    ReplyDelete
  11. I went to a Site that had the update, that I download but did not install since I am waiting to see what JF does.
    But I downloaded it just to do it, what can I say.

    Maybe I did not do it right, but the update file is less than 1MB.

    And from what I read it's nothing major, just some security fixes. So I look at it as more of a patch, and a small one at that.

    But I saw this all in passing when looking to install HTC Hero on my G1. (That I am doing tonight. Wish me luck. LOL. I can't leave the phone alone. I have had Cupcake for a couple months and I am already being unfaithful.)

    ReplyDelete
  12. What if it's doing the constant re-download thing without otacerts having been removed? Is there any way to stop that?

    ReplyDelete
  13. Since a new build will be forthcoming for CRC1, could you slip in the -noatime mount option for the sdcard mount code in runme.sh? Thanks!

    ReplyDelete
  14. MichaelSF - A friend installed the Hero OS on his ADP, he said it looked very impressive but felt buggy - possibly due to the dev phone having less CPU and RAM than the Hero.

    ReplyDelete
  15. So, a couple of interesting additions.
    doing a chmod 000 /cache/*.zip seems to help.

    Until you reboot. Then, it seems to reset the permissions to make it a readable file, and then the update wants to apply

    ReplyDelete
  16. JF and anyone else who knows a damn- I had my friend root my phone back in May so I could get the ADP 1.5 early, and now he's left Berkeley working in Seattle (hmm for who i wonder). I did an update from "dream_devphone-userdebug 1.5 CRB21 147201 test keys" to JF1.51US last night. I did not wipe the phone before the update.
    I just noticed that my dialer doesn't work anymore- it force closes whenever I try to call someone- anyone (HELP ME JESUSF!) know how to fix this or where I can get a new dialer app? Should I just wait until the next build (hopefully no one calls me in between)????

    thanks

    ReplyDelete
  17. Hey all, I tried just downloading the build.prop from krisz's post and zipping it with the package but applying the update fails.

    ReplyDelete
  18. That would be a welcome modification to help reduce the number of unnecessary writes to SD media.

    ReplyDelete
  19. I just rooted today and used your build cupcake build crb43 ..runs sweet and all ..... when is the update for the new one coming (crc1) or did it drop already ....

    ReplyDelete
  20. Hey JF, great work. Could you consider to add the FUSE-kernel module to your next release, because that would allow the use of sshfs, smbfs, ftpfs and so on, making exchanging files to android very easy....

    ReplyDelete
  21. # pwd
    /system/modules
    # find | grep fuse
    ./2.6.27-00392-g8312baf/kernel/fs/fuse
    ./2.6.27-00392-g8312baf/kernel/fs/fuse/fuse.ko

    ReplyDelete
  22. Hey Nate / JF,

    Even with the chmod command no joy even between reboots. Probably because the file no longer shows in /cache/... where else would the OS store it? Or can I not see it because I removed my own permissions?

    ReplyDelete
  23. Danny,

    I donlt think the update feature works that way. There is usually something that has to tell the update program what to replace / swap and where to...

    ReplyDelete
  24. hey Jf quick question i know u have something new comin out which is great im a prode supporter of ur roms but i have one problem with it, and i know u can fix it please can u optimize the volume for the speaker it's so low. i tried the hero rom and the ringer was so high and clear. so im askin please please can u make it high and again thanx a bunch for ur hard work people like u is why i love phones.

    ReplyDelete
  25. When will the CRC1 US, EU, ADP be released? It's been over a week. I'm not trying to rush you, I'm just wondering hehe.

    ReplyDelete
  26. It would also be nice to see the auto mount option instead of ext2. This would help greatly with the ext3 apps2sd partitions most people are using.

    ReplyDelete
  27. any clue to when the update will be ready? tnx

    ReplyDelete
  28. I just came around to root my phone and install JF. Kudos to you for making your firmware builds available. They are working perfectly and the multitouch features are neat. I am really impressed.

    So thank you and keep up the good work!

    ReplyDelete
  29. JF I think you're great for the modified OS, I was wondering if with your CRC build of the ADP 1.51 would you be including any bug fixes? At one point I was flashing my phone with ADP 1.51 once a week because I would get random bugs maybe a week or so after installing. Some examples : force closing (my browser, the market app, other random programs), I would tap on or open something up and it wouldn't open, various bugs that seem like stability issues. I wanted to have the U.S. 1.51 build, but that build is un-stable still, which is why I am using ADP 1.51. When I had the U.S. Cupcake 1.51 build after about a week of use it would force close everything. Sometimes a restart would fix the problem most times it wouldn't. I was just wondering if you fix bugs in the builds because I love your work. I had a whole nother build (not a JF build) when I first rooted my G1 which was completely un-usable so I'm not trying to be critical, I was just wondering. Thanks!!

    ReplyDelete
  30. Update....
    1. Go to terminal emulator
    2. chmod 111 cache/*.zip
    3. cd cache/
    4. ls
    5. rm {filename listed above will have 'signed' in it}.zip

    This made the annoying pop up go away for me... for two days now. I think this will work till OTA pushes the update to the phone again.

    ReplyDelete
  31. Could you also please add the auto mount option for the ext partition on SD? In current images this is still ext2. Most people probably switched to ext3 by now and auto will mount both.

    ReplyDelete
  32. Strange the update tmobile was forcing has stopped. It seems I am getting alot of slowdown now. I have a rooted phone so what the scoop on the new build? Haven't heard anything. What about donut isnt it suppose to drop soon? I want to keep root but not at the cost of being sluggish.JesusFreke keep up the great builds and can you give us all an update and maybe a glimpse of what you are going to put in the new build anything new besides the crc update. Thanks man.

    ReplyDelete
  33. Hi Dave,

    I am in the same boat, I still have the file, ever find a solution? This has caused me to go over 10GB this month with tmobile

    ReplyDelete
  34. GCC for da mobile phone :-)

    ReplyDelete
  35. I have replace the /system/build.prop, and now i get a notify it's an update available. It's an another update with 884kb.

    ReplyDelete
  36. Hi guys,
    I'm very confused, I'm using JF Update Checker and I just installed the last update but it stills showing:
    Firmware Version: 1.5
    Kernel version 2.6.27-00392-g8312baf jesusfreke@spork #1
    Build number: dream_devphone-userdebug 1.5 CRB43 148830 test-keys

    Is it the last version?

    Thanks

    ReplyDelete
  37. Has there been any progress with the JF Update, the media makes it sound like there is a gaping security hole without the patch....

    ReplyDelete
  38. Maybe its me but I had my phone rooted. I was getting the install update for the crc fix but then it stopped asking me if i wanted to update and now my bluetooth isnt working properly. Is there a new build or update from JF? Or can someone recommend a differnt build anyone have any issues?

    ReplyDelete
  39. Thanks, I've been simply to stupid to locate the modules on Android. Works like a charme, thanks.

    ReplyDelete
  40. So how does it look like with that patch?

    ReplyDelete
  41. When IS it coming out?

    ReplyDelete
  42. I'd back up my data, wipe it and reinstall the latest JF.
    It works like a charme on my android.

    ReplyDelete
  43. Having a rooted G1 with your JF-Image is just cool, but unfortunately none of the three workarounds works for me and after a few weeks, the update notification becomes pretty annoying. Any other suggestions what one could do to get rid of it?

    ReplyDelete
  44. Hey jf this is kinda off topic but I was wondering if u we're working on a hero build lik a lot of othr devs are

    ReplyDelete
  45. Any news on the update? Seems it also fixes a security hole that could leave your android phone \broken\:

    http://www.androidcentral.com/android-sms-flaw-fixed-previous-android-update

    ReplyDelete
  46. Any word on when an update will be available? I was going to roll my own with -noatime, but if something will be forthcoming soon I'll hold off. Thanks!

    ReplyDelete
  47. I'm getting the update notification every 20 minutes and have tried all suggestions. Really frustrating. Anyone know of a REAL fix?

    ReplyDelete
  48. Hi - I've updated to JF 1.51 Cupcake ADP1 via JF Updater.

    When I go to About > Kernel Version, I get:

    2.6.27-00392-g8312baf
    jesusfreke@spork #1

    Is this correctly showing the updated version? Any hints on how to tell?

    Many thanks.

    ReplyDelete
  49. You can edit it yourself. remount /system with rw and edit /system/etc/fstab - keep in mind this is only valid for ext filesystems, not vfat, so it's not valid for fat32, etc, filesystems.

    ReplyDelete
  50. So, what is up with this new update? I am tired of clicking Update Later. Are you even making updates to your rom anymore?

    ReplyDelete
  51. Did JF die or something? Getting near a month with no news from him.

    ReplyDelete
  52. Thanks, krisz! And sorry for the late response.

    ReplyDelete
  53. Yes, I am now noticing the same thing with the new buid.prop. Now I'm going to try the "chmod 000 /cache/*.zip" solution. Since I rarely reboot, this should be enough to block the notices until CRC1 is ready.

    ... knock on wood.

    ReplyDelete
  54. 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

    ReplyDelete
  55. 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.

    ReplyDelete
  56. 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.

    ReplyDelete
  57. come back dude i love ur stuff

    ReplyDelete
  58. 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???

    ReplyDelete
  59. "I should be able to get something out soon (next few days)"

    Where is it? This sux!

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

    ReplyDelete
  61. Would it be possible to include crc37 update also?

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

    ReplyDelete

Note: Only a member of this blog may post a comment.