[COLLECTION] HTCU U11 – RUU/Firmware/Recovery/OTA/Backups

Search This thread

ggreen

Senior Member
Jun 16, 2008
53
0
problem to boot

HI,
I unlocked bootloader and root HTC u11 2 month ago. Now I unroot phone and relock phone.
But now I cant boot to android because phone is encrypted and my PIN doesnt work.

I would like to get back to FULL OFFICIAL rom to can use google pay. With unlocked bootloader not work..
I can only to get to download mode
STATE

RELOCKED
PRODUCTION
htc_ocnuhl PVT S-ON
LK-1.0.0.0000
RADIO 8998-2003210-1905141529
OpenDSP v11.6.00347.CB8998_0711
OS-3.34.401.1

SEcurity chcecking failed DENY

When I tried download 2PZCIMG_OCEAN_UHL_P90_SENSE10GP_MR_HTC_Europe_3.34.401.1_Radio_8998-200321-1905141529_release_signed.zip copied to SD card rename to 2PZC10000.zip and boot to download so nothing happened.

Recover mode wrote device corrupted...
Please how to fix it ??
 
Last edited:

Flinny

Recognized Developer
Nov 22, 2011
2,252
8,396
45
Sunderland
In the little spare time that I have at the moment, I've started looking at getting android 10.0 booting. If somebody could point me to a system and boot dump from a single sim variant P device that would help me greatly :)

Thanks,

Nick.
 
  • Like
Reactions: Golv and Boskoel03

Golv

Recognized Developer
Jan 17, 2012
2,135
4,428
In the little spare time that I have at the moment, I've started looking at getting android 10.0 booting. If somebody could point me to a system and boot dump from a single sim variant P device that would help me greatly :)

Thanks,

Nick.
You can use RUU and DecryptTool:
Pie RUU 3.34.401.1 for WWE
OCEAN_UHL (Single SIM), Product ID: htc_ocnuhl, CIDs: HTC__001 / HTC__002 / HTC__034 / HTC__M27 | MID: 2PZC10000

2PZCIMG_OCEAN_UHL_P90_SENSE10GP_MR_HTC_Europe_3.34.401.1_Radio_8998-200321-1905141529_release_signed.zip
 
  • Like
Reactions: ziand

Flinny

Recognized Developer
Nov 22, 2011
2,252
8,396
45
Sunderland

MoreHelp

New member
Dec 7, 2019
2
0
Need Help

kernel: lk
product: htc_ocnuhljapan
version: 1.0
version-main: 1.27.401.12
version-bootloader: 1.0.0.0000
mid: 2PZC10000
cid: SBM__802


I can not find the same firmware please Help.
 

insigniared

Member
Jun 30, 2010
44
2
correct rru or zip?

Hi, I have this HTC U11 factory unlocked but actually briked, so I need to find out the apropiate .zip/RUU file.
It says that the phone is a htc_ocnwhl
Would you guys please tell me wich RUU or ZIP would be suitable for my phone?
Thank you
:cowboy:
 

Attachments

  • IMAG0481.jpg
    IMAG0481.jpg
    269.4 KB · Views: 167

grat_master

Senior Member
Aug 29, 2011
122
7
Montreal, QC
I made a DSP "patched" version of this firmware here: https://www.androidfilehost.com/?fid=4349826312261632935
SHA-1: A68976B6A78D0CD41E4ACA7993972E8A0751CDF2

The only difference between this one and the original is that the "patched" version contains the dsp.img from 2.42.617.7 in order to allow voice calls to work on users of AOSP ROMs such as LineageOS. See: https://forum.xda-developers.com/showpost.php?p=80620553&postcount=1267

Do you have stock recovery ?

I went from android 8 to Pie and I'm about to flash twrp and magisk but would like to have the possibility to go back to stock if there is another update. I suppose I can't use a 2.42.617.7 RUU once I get on 3.37.617.1 ?

Thanks !

edit : now I can't seem to be able to mount storage to flash magisk, always asking for decryption password. Also wifi can't find hidden networks. What did I do wrong ?
 
Last edited:

Golv

Recognized Developer
Jan 17, 2012
2,135
4,428
edit : now I can't seem to be able to mount storage to flash magisk, always asking for decryption password.
You need FORMAT /data in TWRP and reboot in TWRP again (keep in mind that you will lose all data on internal memory card, all user apps and settings of all apps).
 
Last edited:

The_Walking_Playground

Senior Member
Nov 30, 2017
652
345
Well, now how can I bring this phone back to life? if there is no RUU, therefore there isn't a .zip stock rom also.
Am I correct?
Thank you again
Hi,

You can try flashing the firmware zip from the Pie OTA. It should be uploaded in the thread somewhere. You could also flash the last Oreo system image via fastboot and then flash the Pie OTA zip, which should get your device working again.

TWP
 
  • Like
Reactions: insigniared

grat_master

Senior Member
Aug 29, 2011
122
7
Montreal, QC
You need FORMAT /data in TWRP and reboot in TWRP again (keep in mind that you will lose all data on internal memory card, all user apps and settings of all apps).

Alright here is what I did :

I rextracted stock recovery from 3.37.617.1
Flashed it
Factory reset
Flashed 3.3.1.0 twrp
Booted to recovery, now it asks for a password so I tap cancel
Went to Wipe and did Format Data
Rebooted to bootloader then recovery
Computer can see HTC U11, only folder is TWRP
I moved magisk to internal storage of U11
TWRP can't see it.

I cant see magisk from twrp.

What did I do wrong ?

edit : nevermind, I found it. It is in /data/media.
 
Last edited:

grat_master

Senior Member
Aug 29, 2011
122
7
Montreal, QC
Pie RUU 3.37.617.1_R2 for US Unlocked

BS_US001 2PZC50000

MD5: a55b2a46c47b65eca5f96dedf598869f

2PZCIMG_OCEAN_WHL_P90_SENSE10GP_MR_NA_Gen_Unlock_3.37.617.1_R2_Radio_8998-200321-1905211056_release_545430_signed_2_4.zip

decrypted hosd_signed.img from RUU 3.37.617.1_R2: hosd_3.37.617.1_R2_signed.img

THX @dianamavrilk

I suppose you need to do those steps but with the 3.37.617.1 RUU instead of the 2.42.617.7 ?

Downgrading From Pie 3.37.617.1_R2 to Oreo 2.42.617.7 US Unlocked
Must have TWRP installed
All data will be erased and back to Oreo stock

Required files
hosd_signed.img
HTC Dev info tool

1. Connect the phone into computer and boot the phone into bootloader
2. flash hosd_signed.img "fastboot flash hosd hosd_signed.img"
3. once its done boot into TWRP and run the HTC dev info tools.
4. Change the version number into 2.42.617.7 and hit Save apply all changes
5. Run the Oreo RUU downloaded from HTC website

Your phone back to Oreo
 

sherchem

Member
Jul 15, 2017
15
1
Pie RUU 3.37.617.1_R2 for US Unlocked

BS_US001 2PZC50000

MD5: a55b2a46c47b65eca5f96dedf598869f

2PZCIMG_OCEAN_WHL_P90_SENSE10GP_MR_NA_Gen_Unlock_3.37.617.1_R2_Radio_8998-200321-1905211056_release_545430_signed_2_4.zip

decrypted hosd_signed.img from RUU 3.37.617.1_R2: hosd_3.37.617.1_R2_signed.img

THX @dianamavrilk

Hi;
my phone (same CID and MID) is also bricked (FASTBOOT RELOCKED), In that case if I would be able to move this RUU to the sd card will it work?
Is there another option for me besides waitng for htc to realease the pie RUU.exe?
I cant downgrade to OREO since my bootloader is locked.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 50
    34257567313_c0671aefca_b.jpg

    This thread has the aim is to provide you with one single thread to find what you seek and where every user can participate by sharing files and/or links to.

    Here's a list of all variants as thankfully provided by @Kisakuku:
    • htc_ocndtwl - China (Dual SIM)
    • htc_ocnuhl_jp - Japan (Single SIM)
    • htc_ocnuhl - Asia / EMEA (Single SIM for carriers and HTC direct sales)
    • htc_ocndugl - Asia / EMEA (Dual SIM for HTC direct sales)
    • htc_ocnwhl - North America (Single SIM US Unlocked, Sprint)

    Helpful links:


    I cannot accept any liability and/or responsibility for these firmware packs. I am not able to go through the process of testing each pack, hence community members are called to test these on their own.

    Regards 5m4r7ph0n36uru


    32720096555_cdab9a4997_m.jpg

    1. Post #2: Google Spreadsheet with download links
    2. Post #3: Firmware flashing methods by @Sneakyghost
    3. Post #4: General Information by @Sneakyghost
    4. Post #5: How-To Guidelines
      • 1. How-To flash a RUU using the SD card method
      • 2. How-To restore an untouched/pristine system image using a Nandroid Backup
      • 3. How-To manually flash an OTA Update
    5. Post #6: RUU Errors & Fixes

    31877367484_f88c9d6a33_m.jpg

    This thread wouldn't be as good as it already is without all those contributes named at the end of this thread. Thanks again to all of you sharing your files and knowledge that enables me to hold up this thread.

    There are some special thanks I want to express to

    @Sneakyghost by whom's firmware threads I gained the most, if not all, my knowledge about firmware reagarding HTC
    @Captain_Throwback for creating and maintaining the HTC RUU decrypt tool, as well as maintaining all those TWRP Recoveries
    @nkk71 for creating and maintaining the HTC RUU decrypt tool, as well as the MultiROM Mod on my past HTC devices


    XDA:DevDB Information
    [GUIDE][Collection] HTCU U11 – RUU/Firmware/Recovery/OTA/Backups

    Contributors
    @5m4r7ph0n36uru, @ziand_, @Kisakuku, @OMJ, @JEANRIVERA, @blueberry60, @Golv, @sergos1221, @topjohnwu, @andybg40, @Petert87, @sirioo

    Created 2017-05-25
    Last Updated 2017-06-24
    46
    [Collection] Spreadsheet with download links


    Recent Additions:

    Please remember: you're writing to boot-critical parts of your phone. If anything goes wrong along the way, your phone might be bricked.

    • 2019/02/09 - 2.42.709.86 RUU thanks to @ziand
    • 2018/10/12 - 2.42.709.82 Nandroid thanks to @ziand / 2.33.91.7 Nandroid thanks to @korom42
    • 2018/10/12 - 2.42.709.7 DUGL Nandroid, 2.42.709.7 > 2.42.709.82 DUGL OTA thanks to @ziand
    • 2018/10/11 - 2.42.709.6 > 2.42.709.7 DUGL OTA, 2.33.401.19 DUGL Nandroid thanks to @ziand / 1.27.89.10 RUU thanks to @ziand and @migascalp / Updated all OTA links possible to AFH links thanks to @ziand, and removed those whhich are no longer working, due to HTC's server changes
    • 2018/09/19 - 2.33.401.19 Nandroid thanks to @scotty2000 / 1.13.161.7, 1.27.161.5, 1.27.161.10, 2.33.161.11 Combined FullWipe Firmware thanks to @Petert87
    • 2018/09/18 - 2.33.161.11 > 2.33.161.12 OTA, 2.33.161.12 Firmware, Nandroid & Stock Recovery thanks to @Petert87
    • 2018/09/15 - 2.33.401.10 > 2.33.401.19 OTA thanks to @ziand
    • 2018/09/06 - 2.42.400.3 DUGL RUU thanks to @ziand
    • 2018/08/24 - 2.42.617.7 RUU ZIP thanks to @ziand / 2.42.400.6 > 2.42.400.7 DUGL OTA thanks to @desean
    • 2018/08/12 - 2.33.91.6 Nandroid thanks to @korom42 / 2.42.617.7 Nandroid thanks to @8bitbang / 2.42.617.7 NoWipe Combined Firmware thanks to @darwinmach
    • 2018/01/13 - EMEA DUGL: 1.27.401.11 > 2.33.401.10 OTA thanks to @jhil110/@sirioo, 2.33.401.10 Stock Recovery thanks to @ziand_ / EMEA UHL 1.27.401.12 > 2.33.401.10 OTA / 2.31.709.1 > 2.42.709.1 OTA, Stock Recovery & Nandroid thanks to @ziand_ / 2.31.617.2 > 2.42.617.1 OTA, Stock Recovery thanks to @JEANRIVERA / RUU (EXE & ZIP) thanks to @OMJ / Nandroid (AFH) thanks to @ziand_
    • 2017/12/28 - 1.11.701.5 > 1.28.710.4, 1.28.710.4 > 1.29.710.5, 1.29.710.5 > 2.33.710.9 OTAs added thanks to @GraeFNZ
    • 2017/12/17 - 1.27.400.8 > 1.27.400.21 OTA, 1.27.400.21 RUU & Nandroid thanks to @Kisakuku / 1.27.118.5 > 1.27.118.12 OTA, Nandroid & Stock Recovery thanks to @buttie / 1.27.1405.7, 1.35.1405.2 RUUs & 1.27.1405.6, 1.27.1405.7, 1.35.1405.2 Nandroids thanks to @liweichen6 / 1.28.617.30 > 2.31.617.2 OTA & Nandroid thanks to @OMJ / RUU (.EXE/.ZIP), Stock Recovery, Combined NoWipe & Full Wipe Firmwares thanks to @Kisakuku / 1.27.400.21 > 3.31.400.6 OTA thanks to @goodman_east / Stock Recovery, Combined FullWipe & No Wipe Finmares thanks to @Kisakuku
    • 2017/11/03 - 1.28.651.40 > 1.28.651.50 thanks to @OMJ / 1.28.651.50 RUU (EXE & ZIP), Combine FullWipe & NoWipe Firmwares, Stock Recovery, Nandroid thanks to @Kisakuku / 1.27.401.11 (DUGL) OTA thanks to @Electronic Punk / 1.27.401.11 (DUGL) Combined FullWipe & NoWipe Firmware, Stock Recovery thanks to @Kisakuku / 1.27.401.11 (DUGL) Nandroid thanks to @ziand_ / 1.27.401.12 (UHL) OTA thanks to @axst_68 / 1.27.401.12 (UHL) Combined FullWipe & NoWipe Firmwares, Stock Recovery as well as 1.28.617.30 RUU (EXE & ZIP), Combine FullWipe & NoWipe Firmwares, Stock Recovery, Nandroid thanks to @Kisakuku
    • 2017/10/15 - 1.27.401.5 UHL RUU, Combined FullWipe &NoWipe Firmware, Nandroid / 1.27.401.5 DUGL RUU, Combined FullWipe & NoWipe, Nandroid by @Kisakuku
    • 2017/09/14 - 1.27.401.5 Stock Recovery by @Kisakuku
    • 2017/09/12 - 1.27.401.5 OTA by @axst_68
    • 2017/09/10 - 1.28.709.6 OTA by @topjohnwu, 1.28.709.6 Recovery, Combined FullWipe & NoWipe Firmware, Nandroid by @Kisakuku
    • 2017/09/03 - 1.27.401.5 OTA & Nandroid by @ziand_, Recovery by @Kisakuku / 1.28.651.3 OTA by @OMJ, Nandroid, RUU, Recovery, Combined FullStock & Combined noWipe Firmware / 1.27.400.8 Nandroid, RUU, Recovery, Combined FullStock & Combined noWipe Firmware all by @Kisakuku / 1.27.1405.4 & 1.27.1405.6 RUU by @liweichen6 all added to the spreadsheet
    • [...]
    • 2017/07/08 - Initial release of the newly created spreedsheets with all links provided as of today

    Disclaimer

    You are aware that writing to security protected, boot-critical partitions increases your risk to lose the device exponentially. You understand and agree that I cannot be held responsible for such or any other damages. The flash process is theoretically safe and well tested, however you are the brains behind the wheel and you are solely responsible for the execution of the process. I will not accept any liability. The method itself is developed by Google and HTC, I only provide access and information to it and I am trying my best to make it understandable and simple. Do not use this if you have difficulties understanding what this is!

    You understand that you should not do it if you are not willing to accept this risk.
    42
    Announcement

    Dear XDA Community,

    I have already hinted in one of my last posts that I would have marked this thread as discontinued at the latest when the new HTC Flaggshiff, the HTC U12, appeared.

    Unfortunately, it is becoming more and more a pain to maintain this thread, because there are users who keep asking questions about why one RUU is made available available, but not another. Instead of being satisfied with the contributions in this thread and being thankful for what others have contributed, individual users are still asking for more. They even expect people to know why HTC Corp. is acting the way they are doing. My goal has always been to support this community with what I support here a little bit and to continue the work of great people like @Sneakyghost, @Captain_Throwback and so many more, which I can't even mention here.

    Instead of a simple thank you, I often only get questions about questions and the expectation of the users that they get all the answers fed with the spoon - or that leaked RUUs be provided on my own costs because they don't want to pay for the service through which they are provided. This is no longer XDA as it once was and, in my opinion, should be again. Unfortunately, this thread has always remained only a shadow of the spirit in whose sense it should have been led. XDA has always been a forum of developers for developers, where every user could acquire his knowledge, and above all wished to learn by himself! These times seem to be long gone. The star of the modders fades away and good teams (cf. Team Venom) leave the scene, which without them will no longer be what it once was. And I understand only too well why they do this. Not only due to dwindling user numbers of the provided ROMs, but also due to the fact that users no longer seem to be prepared to deal with the subject of modding in such a profound way to learn to understand all the associated opportunities and risks themselves. AND because they are no longer satisfied with the features that the team integrates, but rather always and always request additional features, without thinking about the effort involved in implementing them, let alone whether they are possible at all.

    Long Story short: I have therefore decided not to continue this thread after the carnival days in Germany. The thread is frozen in the current status and the spreadsheet will no longer be maintained.

    Many greetings
    5m4r7ph0n36uru

    PS: if any of the fellow contributers would like to take over, let me know via PM.
    24
    At this point I would like to take this opportunity to express my sincere thanks to all those who have contributed to this thread - and will continue to do so in the future through their contributions.

    Special thanks also to all the developers, Recognized Contributors and many more who have taught me so much in the field of Rooting, Modding, and Custom ROM since my days with the HTC Desire (aka Bravo) and have given me so much, which has made my devices to something better than they already were.

    I would also like to thank the moderator team, who always helped me with words and deeds, and made this thread something I like to remember. Please forgive me for my occasionally rougher choice of words, if my patience was exhausted at some times.

    I have come a long way here in the forum, even if my number of posts does not give a direct hint. After devices like the HTC Desire, Sensation, One X, M7, M8, M9, and 10 (but also the Moto G 1st Gen., Sony Xperial L, Samsung Tab2 and others), the HTC U11 will most likely be the last of its kind - the last device I have modified extensively and still modify thanks to developers as @j to the 4n and @LeeDroid.

    Starting with the HTC U12 (aka Imagine) I will rely on the features of the Stock ROM, and end this long way for the time being. We have a saying: You never go entirely. My point is that I will remain a silent reader with XDA and will try to help other users in the Q&A sections of this forum from time to time. Only the nerves to run my own threads are just not sufficiant at the moment - whether the external conditions here and/or in work life. Maybe the time will come when I'll be more active with XDA again - you never know.

    New career challenges, marriage and so much more :)

    Thus for one last time I quietly say: Goodbye everybody and thanks for everything I've been able to learn from you!
    23
    32567527592_36bafaa846.jpg

    As some questions within this thread already showed that people don't read the OP, which includes all linked threads linked to in post #1, I'll leave the follwing here. With courtesy of our fellow contributer @Sneakyghost who allowed me to use his work in this thread, I'll quote his explanations on flashing methods, as well as the provided firmware.zip variants below.

    If S-OFF will get available I'll double check all what's written below and alter it to reflect the the currrent situation on the HTC U11 if needed. For as long as we don't know what still holds true on the U11, I'll leave his fabulous work untouched as a quote.

    The whole thanks and respect for this work belongs to @Sneakyghost. Thanks again to you mate!

    Flashing methods:
    • The safest way is still HTCs RUU and OTA method. US RUUs can be accessed via HTC's US Support Site. Jump to your device, then click "View" and scroll down for the download-link. The page has Dev/Unlocked (617), Sprint (651), AT&T (502) and T-Mobile US (531) covered. RUU's are superior to other flashing methods because they carry lab tested combinations of partition images and the method itself is also known to work well (plus the psychological advantage).
      Other than HTC's original OTA's which are "incremental", My packages are always FULL packages (applies to my NoWipe as well! It can also be considered a FULL update as opposed to incremental) - with these you can safely jump from a very old firmware right up to the newest. Following this original RUU / OTA method, come the methods most suitable for my packs:
    • My preferred method is the "Fastboot method", which needs a PC or Mac or Linux computer. I will be detailing how to fastboot flash firmware further down.
    • The "SDCard Method" can be considered the fastest and most suitable for people without a PC. I will be detailing how to SDCard flash firmware further down.

    An explainer to the ZIP variants provided here:
    • Full Stock WIPE ZIPs:
      NOTICE: FullStock zips currently permanently break the phones ability to receive HTC stock OTA's - to restore your OTA functionality, refer to post #5 for more information!
      Only System removed (and encryption broken) - Everything else stock! This type of zip also re-flashes the /data partition with HTC's DZDATA files (meaning you loose everything on your internal SDCARD). Also replaces the Kernel, recovery and Splash1 with latest stock images! The /system partition will not be touched. (Else this would be a RUU.zip). It also includes the "apppreload.img" with all the carrier-bloatware (WWE has no bloat in there!).

      Be sure to put a ROM onto your EXTERNAL SD before proceeding with a Full WIPE ZIP! If you forgot to put a zip on your sdcard: you can reflash TWRP with Fastboot (use my batch tool) and then choose between ADB file push, MTP transfer or even USB mass storage transfer mode. Last but not least you can take out the sdcard and use a card-reader with your computer. Phone will NOT boot without ROM reflash after using this!
    • NoWipe ZIPs:
      These packages are modified. This type of ZIP updates basic Firmware partitions, does not touch the /data partition, leaves kernel, splash and ramdisk (in order to support custom ROM's modifying ramdisk) alone. The "apppreload.img" is removed, the bloatware partition will remain unchanged (to remove already existing bloat permanently flash apppreload.img from International/WWE/401, it is an empty image). Recovery will be replaced with the current TWRP. Phone should in most cases boot normally after using this.
    • And what you won't get here (fine print):
      Since this is a Firmware Update Thread and not a ROM thread, you do NOT EVER get a ROM (a.k.a "System.img" or plain: "System" here. You understand and agree that you cannot have this from me. You also acknowledge that I cannot be blamed for your non-booting phone due to you not reading or not understanding this. You may find stock system backups here

    How to flash firmware.zip's using fastboot

    Prerequisites:

    You need ADB and Fastboot on your PC. To get ADB and Fastboot up and running I strongly suggest you use my "Batch Tool" setup, because it contains an updated htc_fastboot, which is 100% working with the HTC 10 . This is important: the generic Google fastboot from SDK API Level 24 (latest at time of writing) is NOT FULLY COMPATIBLE.

    The method outlined here does apply to my zips as well as HTC signed zips. The difference is, that for my zips, S-OFF is mandatory, while HTC signed zips can under certain conditions also be flashed to S-ON phones, however, different prerequisites and risks apply there. I will not cover HTC signed zips here as they are fundamentally different in some aspects while the flashing method remains the same.

    Note: use "htc_fastboot" with my batch tool. If you use another ADB/Fastboot set, it will probably be Google Fastboot and then the commands should be starting with "fastboot".

    Step-By-Step:
    1. If device is booted into Android, reboot into download mode by running:
    Code:
    adb reboot download

    NOTICE: adb reboot download is new since the M9 for those who come from earlier HTC devices - zips can be flashed in download mode or RUUMode, both work. The on-screen status report is more detailed in download mode. This making it the preferred flashing mode for now.

    1.a Or else, if your device is in a different state or you just prefer the button method:
    In Android: Press and hold Power and VolDown at the same time for approx. 15 seconds, when the screen and charging LED go dark immediately let go of power, keep holding VolDown a little longer.
    During Boot and sometimes when booted into Recovery: Press and hold Power, VolDown and VolUp at the same time for approx. 15 seconds, when the screen and charging LED go dark immediately let go of power and VolUp, keep holding VolDown a little longer.

    When in download mode, use the VolUp and VolDown buttons to navigate up and down and use Power to confirm.

    2. Now place the Firmware_xx.zip into your adb/fastboot folder (which will be "C:\Android\com" if you use my Batch Tool).

    3. Followed by:
    Code:
    htc_fastboot flash zip Firmware_xx.zip
    (replace "Firmware_xx.zip" with the name of your zip)

    4. Now check the console output. It should approximately look like this log:

    NOTICE: this flash log is taken from a NoWipe (not all images included) flash on an HTC 10. New is (compared to M7, M8) that the checking routine is way more sophisticated and Controller Firmware for e.g. the touch panel or the Infra Red Remote (One Series only, not available on the HTC10) and the like do NOT get flashed if the checks determine that they are already up-to-date. Images that do not get flashed show "BYPASSED", which is NOT an error.


    Important: Should you decide to flash in RUUMode (instead of Download Mode like suggested further up), the flash process halts at around 90% on phone screen! This is normal and a safety precaution! The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output to make sure it is safe to reboot! The bar will only fill up to 100% once you type:
    Code:
    htc_fastboot  reboot
    Important: Download Mode flashes finish at 100% on phone screen and in console and ask you to hit Power to return to Download Mode screen.

    IF you encounter any errors which are not "FAIL90", have a look into Post #3 or ask in the thread! DO NOT reboot the device until you have an idea what happened!

    5a.
    Code:
    htc_fastboot reboot-bootloader
    or press Power to return to Download Mode screen - depending on the mode you used to flash the zip. In Download Mode and Bootloader you can go to either regular reboot or shut-down the device via button navigation.

    5b. Optional:
    Code:
    htc_fastboot reboot
    to just reboot the phone to Android.​

    How to flash firmware using SDCard Method
    Prerequisites:
    • Compatible SDCard, should be formatted with FT32 for older firmware, newer firmware can also handle ExtFS formatted cards.
    • A firmware.zip you would like to flash, taken from Post #2 (Downloads)
    • Phone charged up at least 30% (will fail with low power warning if lower than 30%)

    Step-By-Step:
    1. Rename your firmware.zip to exactly "2PS6IMG.zip" - make sure you enable "show file extensions" in Windows Explorer, if you rename it on your PC. Else you might end up with a "2PS6IMG.zip.zip" which won't flash.

    2. Copy your "2PS6IMG.zip" over to the root of your SDCard. Use a cardreader, or MTP protocol in Android or Recovery, or USB Mass Storage protocol in Recovery, or ADB push the file in Android or Recovery - many methods available.

    3. Now, if device is booted into Android, reboot into download mode by running:
    Code:
    adb reboot download

    3.a Or else, if your device is in a different state or you just prefer the button method:
    In Android: Press and hold Power and VolDown at the same time for approx. 15 seconds, when the screen and charging LED go dark immediately let go of power, keep holding VolDown a little longer.
    During Boot and sometimes when booted into Recovery: Press and hold Power, VolDown and VolUp at the same time for approx. 15 seconds, when the screen and charging LED go dark immediately let go of power and VolUp, keep holding VolDown a little longer.

    4. Once Download Mode starts, it will "see" the 2PS6IMG.zip and ask you (yellow text at bottom of screen) if you want to flash the firmware. Press VolUp to confirm and proceed with the flash, or press VolDown to cancel and continue into Download Mode UI.

    5. Now check the screen while it flashes. It should stop at "end UI updating. Press Power to continue" - the phone will now shut off! To turn it back on, press and briefly hold power again.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone