1. Check out our companion app, Forums for Android! Download from Google Play

General VERY unusual for a signed update- not being publish ready

Discussion in 'Android Devices' started by rushmore, Jul 19, 2010.

  1. rushmore

    rushmore Well-Known Member
    Thread Starter
    323

    Nov 13, 2008
    8,267
    1,355
    323
    Kentucky
    I am still a tad miffed how we have to debate about a signed update.

    1. Updates are signed to prevent non-root users from messing their devices up and increasing carrier support costs.

    2. If the update was not signed, rooters should have no prob installing.

    3. How did a signed update get released to the streets? This is a HUGE security breach, since it is very easy for anybody to download and update, where these situations are normally for rooters only and rooting is more of an obstacle for a general population to update.

    This seems to be the first time a signed update has leaked that may not be the official update. If I were HTC and VZW, I would be investigating this- ASAP to prevent again.

    Otherise this update is one of three things,

    1. Hacked and signed (doubtful)
    2. Intended to be the update to publish, but a last second issue cropped up too late to stop a release to a small amount of devices
    3. This is the real deal
     

    Advertisement

    Skipdawg likes this.
  2. adrynalyne

    adrynalyne Well-Known Member
    213

    Jul 15, 2010
    1,507
    885
    213
    It happens all the time. That said, signed updates are needed for testers too.

    Rooters cannot install not due to the signing issue, but the radio and firmware flashing issue. They do not work using a nonstandard recovery.

    One could feasibly use unrevoked's tool to reinstate their stock recovery, stay rooted, and apply the leaked ota without issue.
     
  3. rushmore

    rushmore Well-Known Member
    Thread Starter
    323

    Nov 13, 2008
    8,267
    1,355
    323
    Kentucky
    Looks like a possible reason was posted today:

    The update was (maybe) stopped due to close proximity of Froyo. Decision apparently made to release this update along with Froyo, rather than two updates within a few weeks of each other. Kind of puts more concern on that radio update issue you point out. If same radio- no problem.

    This of course assumes this is not all a new evolution of the original information ;)
     

Share This Page

Loading...