Which is the latest firmware for the One XL?

Search This thread

sandys1

Senior Member
Jun 4, 2010
763
165
hi - I'm referring to the firmware, not an RUU or OTA.
For example, from this thread - I see that firmware ver 2.15.0000 comes from 5.08.111.2 ROM.

Is there any later firmware than the 2.15 above ? I'm using CM11 and the only way I can flash firmware is through the adb tool (I dont have windows), so want to figure this out.
 

twistedddx

Senior Member
Oct 23, 2010
963
577
Is there any later firmware than the 2.15 above ? I'm using CM11 and the only way I can flash firmware is through the adb tool (I dont have windows), so want to figure this out.

The newest firmware is inside Brightstar 5.13.1540.2.
Orange 5.14.61.2 and HTC Hong Kong 5.08.708.3 both also have newer firmware than T-Mobile 5.08.111.2 but are not the newest.

Brightstar 5.13.1540.2:
Kernel: 3.4.10-gefd4656
hboot: 2.18.0000
radio: 1.34a.32.45.21_10.142.32.34a
adsp: 33.1.0.45.1128
wcnss: 1031145
tp_syn3202: 3.2_PR1293981
tz: 001.138.020
sbl1: 001.138.004
sbl2: 001.138.009
sbl3: 001.138.007


T-Mobile 5.08.111.2:
Kernel: 3.4.10-g08ef01e
hboot: 2.15.0000
radio: 1.31a.32.45.16_2_10.141.32.34a
adsp: 33.1.0.45.1128
wcnss: 1031145
tp_syn3202: 3.2_PR1293981
tz: 001.138.019
sbl1: 001.138.003
sbl2: 001.138.007
sbl3: 001.138.005
 
Last edited:

sandys1

Senior Member
Jun 4, 2010
763
165
The newest firmware is inside Brightstar 5.13.1540.2.
Orange 5.14.61.2 and HTC Hong Kong 5.08.708.3 both also have newer firmware than T-Mobile 5.08.111.2 but are not the newest.

Thanks for that !

Would you know how to extract just the firmware from that file so that it can be flashed by doing fastboot oem rebootRUU and
fastboot flash zip <PathToFirmware.zip>, similar to how turge extracted it for 5.08.111.2 ?

Thanks again...
 

twistedddx

Senior Member
Oct 23, 2010
963
577
Would you know how to extract just the firmware from that file so that it can be flashed by doing fastboot oem rebootRUU and
fastboot flash zip <PathToFirmware.zip>, similar to how turge extracted it for 5.08.111.2 ?
.


Ensure s-off and supercid first.

You could create your own unofficial firmware.zip like Turge did that includes some img's that the OTA you are installing may be missing. I think the following will be easiest though.

Ensure 3.17/3.18 complete firmware or better as base is installed on phone, eg 3.18 RUU or previously updating to 3.xx/5.xx officially with HTC OTA. This can be skipped if you are certain you have already installed this or Turges 5.08.111.2 firmware.
Download T-Mobile 3.17.111.1 OTA (or similar complete 3.17/3.18):
http://fotadl.htc.com/OTA_EVITA_UL_...129.32.34a_release_300591m6ejdlmoq874n7fw.zip

Open zip, extract firmware.zip

fastboot oem rebootRUU
fastboot flash zip firmware.zip <<repeat if you get error please flush again immediately. Typically this needs to be done 2-3 times. When it completes without please flush again message you can reboot the phone.
fastboot reboot


If this step is not done you run a higher risk of the device being bricked in the update.


I would suggest reboot to ensure firmware is completely written to device before moving to next firmware.zip package.


Download Brightstar 5.13.1540.2 OTA:
http://fotadl.htc.com/OTA_EVITA_UL_....17.1540.4_release_342737ulobjpm2t4w05mnr.zip

Open zip, extract firmware.zip
fastboot oem rebootRUU
fastboot flash zip firmware.zip <<repeat if you get error please flush again immediately. Typically this needs to be done 2-3 times. When it completes without please flush again message you can reboot the phone.
fastboot reboot



NOTE: HTC official firmware.zip includes boot.img and recovery.img. You will need to reinstall custom recovery and your installed ROMs matching boot.img.

NOTE #2: CM install scripts do not include hboot 2.18 (it includes 2.14, 2.15, 2.16 and 2.17). You would need to hand edit the updater-script for such ROM's to get them to install.

NOTE #3: The above instructions account only for the software versions listed above. Do not assume these instructions can be used for past or future firmware.zip files obtained from past/future OTA. You must always account for the fact OTA expects your phone to already be functional with a particular previous software version. OTA firmware.zip typically does not include files that are expected to already be installed on the device. Updating from unexpected software versions will likely end in a bricked phone. Whereas RUU files contain complete firmware.zip.
 
Last edited:
  • Like
Reactions: Heisenberg

redpoint73

Inactive Recognized Contributor
Oct 24, 2007
15,254
6,968
What is the reason for wanting the "latest" firmware? I haven't been following CM11 closely (so maybe I'm missing something here), but in general the AOSP ROMs don't require the "latest" firmware, its just the Sense 5 ROMs that act wonky if your firmware (probably radio in particular) is outdated.

So unless I'm missing something, it seems like you are going through a lot of extra work and risk of bricking the phone for no real reason. If you don't do the steps exactly right as twistedddx listed them, you run a high risk of instantly bricking the device (and the only way back is JTAG). In particular, if you don't update the hboot modules correctly (sbl1, 2, and 3 all need to be compatible), its a brick.
 
Last edited:

redpoint73

Inactive Recognized Contributor
Oct 24, 2007
15,254
6,968
For example, from this thread - I see that firmware ver 2.15.0000 comes from 5.08.111.2 ROM.

2.15 is not technically a firmware number. Its just been often posted here "2.15 firmware" as a sort of shorthand for "the firmware modules that came with hboot 2.15". Each module has different numbers (tz, sbl1, etc.), as twistedddx posted in Post #2 above. Checking the number for each module is the only way to check for what is "latest".
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Would you know how to extract just the firmware from that file so that it can be flashed by doing fastboot oem rebootRUU and
    fastboot flash zip <PathToFirmware.zip>, similar to how turge extracted it for 5.08.111.2 ?
    .


    Ensure s-off and supercid first.

    You could create your own unofficial firmware.zip like Turge did that includes some img's that the OTA you are installing may be missing. I think the following will be easiest though.

    Ensure 3.17/3.18 complete firmware or better as base is installed on phone, eg 3.18 RUU or previously updating to 3.xx/5.xx officially with HTC OTA. This can be skipped if you are certain you have already installed this or Turges 5.08.111.2 firmware.
    Download T-Mobile 3.17.111.1 OTA (or similar complete 3.17/3.18):
    http://fotadl.htc.com/OTA_EVITA_UL_...129.32.34a_release_300591m6ejdlmoq874n7fw.zip

    Open zip, extract firmware.zip

    fastboot oem rebootRUU
    fastboot flash zip firmware.zip <<repeat if you get error please flush again immediately. Typically this needs to be done 2-3 times. When it completes without please flush again message you can reboot the phone.
    fastboot reboot


    If this step is not done you run a higher risk of the device being bricked in the update.


    I would suggest reboot to ensure firmware is completely written to device before moving to next firmware.zip package.


    Download Brightstar 5.13.1540.2 OTA:
    http://fotadl.htc.com/OTA_EVITA_UL_....17.1540.4_release_342737ulobjpm2t4w05mnr.zip

    Open zip, extract firmware.zip
    fastboot oem rebootRUU
    fastboot flash zip firmware.zip <<repeat if you get error please flush again immediately. Typically this needs to be done 2-3 times. When it completes without please flush again message you can reboot the phone.
    fastboot reboot



    NOTE: HTC official firmware.zip includes boot.img and recovery.img. You will need to reinstall custom recovery and your installed ROMs matching boot.img.

    NOTE #2: CM install scripts do not include hboot 2.18 (it includes 2.14, 2.15, 2.16 and 2.17). You would need to hand edit the updater-script for such ROM's to get them to install.

    NOTE #3: The above instructions account only for the software versions listed above. Do not assume these instructions can be used for past or future firmware.zip files obtained from past/future OTA. You must always account for the fact OTA expects your phone to already be functional with a particular previous software version. OTA firmware.zip typically does not include files that are expected to already be installed on the device. Updating from unexpected software versions will likely end in a bricked phone. Whereas RUU files contain complete firmware.zip.
    1
    I agree with Redpoint, there's absolutely no benefit to flashing this firmware, only risk, unnecessary risk.

    Sent from my Evita