Notes on Recovery Booting (1.5 vs. 2.1) and OTAs


Last Updated:

  1. erisuser1

    erisuser1 Well-Known Member This Topic's Starter

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    All,

    I spent some time rolling back my Eris this evening, putting it completely back to stock, including installing the 1.47.0000 S-ON (locked) bootloader.

    This post is mostly for documentation purposes, but I did discover the answers to some long-standing questions of mine - look for these trivial nuggets highlighted in green down the post a little bit.

    "Stock" in this case means

    Eris Cupcake 1.5 - v 1.17.605.1 (Last Eris 1.5 release)
    Eris Eclair 2.1 - v 2.36.605.1 ( = Leak-V3 = "Official" RUU )
    Eris Eclair 2.1 - v 2.37.605.4 (July OTA)

    The objective of this exercise was to figure out primarily if the copies of OTA files that I had on hand would verify & work correctly. I have a couple more than these on file, but the ones I worked with were:

    1) OTA_Desire_C_Verizon_WWE_2.36.605.1_1.17.605.1_release_0420.79112f65.zip
    81,504,835 bytes ; MD5 signature: 9a3a82e4b5afb4e885b41d28085b9adc

    2) OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
    13,437,426 bytes; MD5 signature: 6c509776a039149c392940025a13cff9

    3) 06cb731fe7f3.OTA_Desire_C_Verizon_WWE_2.37.605.4_1.17.605.1_release.zip
    79,318,831 bytes ; MD5 signature: d480a50f3fc450d7bc13cb277820c688


    #1 takes a Cupcake/1.5 Eris with the "1.17.605.1" software (the last 1.5 Eris release), and upgrades it to the same software as Leak-V3 or "Official" RUU - that is, 2.36.605.1

    #2 takes a 2.1 Leak-V3 Eris ( = "Official" RUU ), and upgrades it to the July 2010 OTA software.

    #3 takes a Cupcake/1.5 Eris with the "1.17.605.1" software (the last Official 1.5 Eris release), and upgrades it directly to the July 2010 OTA for 2.1 - the last Official 2.1 Eris release


    Any of these files would be installed by moving them to the root folder of the SD card, renaming them to "update.zip", starting the recovery boot, entering the correct key sequence to get the recovery menu, and finally - selecting the menu item which flashes "update.zip" from the SD card. In fact, I tried all three sequences indicated above (successfully) with the 1.47.0000 S-ON bootloader in place. (You might recall that the 1.47.0000 bootloader was part of the MR1 and MR2 RUU releases in December '09 and January '10).

    Here were the minor discoveries I made along the way:

    [SIZE=+1]The 1.47.0000 bootloader will not start the Recovery boot using the Vol-Up+End key combination.[/SIZE]

    This certainly explains why folks reported difficulties in the past with entering recovery using the Vol-Up+End key combination - it only applies to the 1.49.0000 S-ON and 1.49.2000 S-OFF bootloaders. The alternative (for 1.47.0000) is to start HBoot first (Vol-Down+End), or Fastboot (Send+End), and then traverse the menus in those modes to get the Recovery boot.

    (BTW - also - the "SIMLOCK" and "CLEAR STORAGE" menu items appear in the 1.47.0000 Hboot menu - but not in 1.49.xxxx)

    Second tidbit

    [SIZE=+1]You get past the recovery boot "splash screen" in the 1.5 stock recovery by pressing the Home (softkey) and then the End key together (Home softkey first)[/SIZE]

    In the 2.1 stock recoveries, a splash screen is also presented on stock recovery booting - but for these recoveries, you press Vol-Up+End (a second time) after the recovery splash screen appears to get to the recovery menu.


    OK, bored now? I told you these finds were trivial!

    eu1
     

    Advertisement
    scary alien, doogald and Podivin like this.
  2. scary alien

    scary alien not really so scary Moderator

    Joined:
    Mar 5, 2010
    Messages:
    21,681
    Likes Received:
    22,040
    You hate a mystery, eh, eu1?

    Good to finally have an explaination of the wacky booting-into-recovery issues. Thank you for this.

    Also, my eyes couldn't help making me read this line this way:

    ...yeah, I know, sophomoric humor...guilty as charged! ;)
     
  3. eorourke

    eorourke Member

    Joined:
    Apr 7, 2010
    Messages:
    15
    Likes Received:
    0
    Can you post a link to the OTA update? I have a phone that meets the criteria and the person doesn't want me to root their phone...
     
  4. erisuser1

    erisuser1 Well-Known Member This Topic's Starter

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    Yes, I do love a mystery - such as, which OTA is eorourke talking about? (My post that he quotes mentions three of them explicitly).
     
  5. erisuser1

    erisuser1 Well-Known Member This Topic's Starter

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    Screw it; here's all three. I *cough* found these on the internet.

    1) OTA_Desire_C_Verizon_WWE_2.36.605.1_1.17.605.1_release_0420.79112f65.zip
    81,504,835 bytes ; MD5 signature: 9a3a82e4b5afb4e885b41d28085b9adc
    MultiUpload.com - OTA_Desire_C_Verizon_WWE_2.36.605.1_1.17.605.1_release_0420.79112f65.zip

    2) OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
    13,437,426 bytes; MD5 signature: 6c509776a039149c392940025a13cff9
    MultiUpload.com - OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip

    3) 06cb731fe7f3.OTA_Desire_C_Verizon_WWE_2.37.605.4_1.17.605.1_release.zip
    79,318,831 bytes ; MD5 signature: d480a50f3fc450d7bc13cb277820c688
    MultiUpload.com - 06cb731fe7f3.OTA_Desire_C_Verizon_WWE_2.37.605.4_1.17.605.1_release.zip


    eu1
     
  6. Podivin

    Podivin VIP Member VIP Member

    Joined:
    Nov 29, 2009
    Messages:
    3,679
    Likes Received:
    881
    Thanks for the chuckle, EU1 ;)
     
  7. eorourke

    eorourke Member

    Joined:
    Apr 7, 2010
    Messages:
    15
    Likes Received:
    0
    Thanks - I needed 2.37.605.4
     

Share This Page

Loading...