yashsingh1/xdaforums huggingface dataset:
[HTC 10 Guides, News, & Discussion] NickDVS:
I promise I looked first. I did the CTRL+F to find verizon on the page lol, I just didn't know about the CDMA thing.

Thanks for that link. Do you know which one I want to run the Viper 5.8? I would want the one with twrp, correct (second link)?

2.41.605.12 Firmware with stock boot.img and stock recovery removed(will NOT wipe)

(Recommended firmware zip ^^^ for most users)

2.41.605.12 Firmware with stock boot.img removed and Twrp3.1.0-1 included(will NOT wipe)

2.41.605.12 Full Stock Firmware with stock boot.img and stock recovery included(will replace/remove Twrp/will wipe)
[HTC 10 Guides, News, & Discussion] xunholyx:
Yeah, use the second one if you don't already have 3.1.0-1 installed. The first (for most users) expects you to have the latest TWRP already installed, but either way the second one is a good choice.
[HTC 10 Guides, News, & Discussion] NickDVS:
Perfect! I REALLY appreciate the help!:D:good::good:
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Recent Additions 2.46.617.2

Recent Additions

WARNINGS:

NoWipe tested. Working

FullStock untested.

Might cause another reboot after first boot and a "new SIM inserted" message. This is normal!

NOTES:

Dunno... nuffin?

CREDITS: [MENTION=453495]JEANRIVERA[/MENTION] for linking me with the RUU file.

Other stuff

Packing up. No more fiddling around on a saturday afternoon. Time for Barbeque
[HTC 10 Guides, News, & Discussion] xunholyx:
No-Wipe is tested now, and I had no problems. I had to flash it twice (90: pre-hboot update), but that was expected.
[HTC 10 Guides, News, & Discussion] Pauls57:
Just flashed the 2.46.617.2 no wipe. When I reboot to system and unlock, I get a pop-up which says "settings have been updated tap to restart" Restarting leads me back to the same point. Not sure what to do next. I've tried dirty flashing the rom (viper 5.9) but it didn't help.
[HTC 10 Guides, News, & Discussion] Sneakyghost:
It says in the release post: might lead to another reboot.

It should happen once and then not anymore. If it keeps happening I'm not sure what to do but I'd try to reflash the ROM.
[HTC 10 Guides, News, & Discussion] Pauls57:
Tried a couple things. Reflashed the firmware, shows correct software version in download mode, correct twrp version in recovery. Wiped data, cache and dalvik, reinstalled viper 5.9. Still the same. Just gets to settings have been updated and reboots. Perhaps I'll need to ruu? If so, is there a 2.46 version? I could only find 2.41
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Hmmm that is a little odd indeed.

Can you try the RUU please and report back?

The RUU link: http://dl3.htc.com/application/RUU_PERFUME_WL_N70_SENSE80GP_MR_NA_Gen_Unlock_2.46.617.2.exe
[HTC 10 Guides, News, & Discussion] i5lee8bit:
Can also confirm working NoWipe on US Unlocked on Viper 10 ROM without issues. Also running EX Kernel + Magisk/Magisk root in case anyone's wondering.

Used the 2PS6IMG.zip on root of external SD method. Installed in download mode, booted up, got the system restart message, next boot everything was fine.

Hope you get everything figured out pauls57!
[HTC 10 Guides, News, & Discussion] Pauls57:
RUU has booted fine. Now for the painful task of restoring the apps and viper.
[HTC 10 Guides, News, & Discussion] acupunk:
+1
[HTC 10 Guides, News, & Discussion] Ypallage:
I'm trying to update with the SD card method. I'm getting this error: FAIL14 RU_ZIP_INFO_ERROR android-info missing or malformed. I did everything correctly, so I think. No zip.zip, flashed trwp 3.1, correct name, tried to download the zip several times on different mirrors...

Anyone can help? Thx!
[HTC 10 Guides, News, & Discussion] mattie_49:
If your trying to downgrade firmware: and not s-off is the only thing that rings out to me.
[HTC 10 Guides, News, & Discussion] Sneakyghost:
RU_ZIP_INFO_ERROR android-info is a rather clear hint, is it not? HOSD isn't able to read the android-info.txt in the zip. There can only be so many reasons after two people already reported a working flash.

My first guess would be a bad download. Did you check the MD5 after download?
[HTC 10 Guides, News, & Discussion] aeroman:
works from download section pme_wl developer/unlocked Version on a pme_uhl (europe) variant of htc 10 ?
[HTC 10 Guides, News, & Discussion] Bob in Northern NJ:
[MENTION=1102297]Sneakyghost[/MENTION] I've read through the OP a couple of times now. Do I rename the combined no-wipe.zip file to 2PS6IMG.zip for the US unlocked version, or is that info imbedded somewhere in the file so that Download mode automatically finds it?
[HTC 10 Guides, News, & Discussion] Sneakyghost:
[emoji23]

Rename that zip as it had been done since I came to XDA (in 2012 at least, it was already done like that). Put renamed zip on sdcard (root directory), reboot to download mode, follow on screen prompts.
[HTC 10 Guides, News, & Discussion] Bob in Northern NJ:
Thanks! I only started using this method on the 10, and only a few months ago at that. Better to ask an expert than to forge ahead blindly and gum up the works!
[HTC 10 Guides, News, & Discussion] jtf420:
[MENTION=1102297]Sneakyghost[/MENTION] Google spreadsheet doesn't have a PMEUHL_2.46.617.2, otherwise suggested in post#2 and post#1447. I see only PMEWL link and file. Please correct me.
[HTC 10 Guides, News, & Discussion] Kisakuku:
Yes, because 2.46.617.2 is intended for US Unlocked / PMEWL. Probably a typo in Sneakyghost's posts.
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Recent additions 2.41.666.3 Bell Canada

Typo. Thanks for bringing it up. Corrected.

Recent Additions

WARNINGS:

NoWipe untested.

FullStock untested.

Might cause another reboot after first boot and a "new SIM inserted" message. This is normal!

NOTES:

I am not sure TWRP 3.1.0-1 works as expected for everyone. I cannot yet point my finger at TWRP, but I seem to be having trouble with flashing Viper10 with it, so when using the NoWipe variant and you run into flashing issues with flashing ROMs, please downgrade TWRP to 3.1.0-0 which worked fine for me before. All reports regarding failing ROM flashes need to be considered carefully for where to post - either TWRP or Viper10 thread, certainly not this thread. Why this unclarity? Because I have not had time to cross-flash stuff with different recoveries and different ROMs to find the misbehaving bit. I have solely tried to flash Viper10_5.9.0 full ROM once and failed with it, so the issue can be anywhere. I am aware of a few isolated incidents on Viper10 thread, but that is simply not enough for anyone to work on the issue at hand. Please do refrain from pointless accusations and help the respective devs to find out where the issue is by providing flash logs to either Captain Throwback and nkk71 on the TWRP thread or to the Viper guys at their respective ROM thread.

CREDITS: [MENTION=4987085]xunholyx[/MENTION] for linking me with the RUU file.

Other stuff

Nothing in particular, except I am frustrated cuz of the costs of renovating my flat. Not much left over. No money, no time. Please excuse my continued absence here on XDA. Too much to look after, still, too many bills to pay.
[HTC 10 Guides, News, & Discussion] hx3:
2.48.617.1 RUU for US Unlocked.

http://dl3.htc.com/application/RUU_PERFUME_WL_N70_SENSE80GP_MR_NA_Gen_Unlock_2.48.617.1.exe
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Recent Additions

WARNINGS:

NoWipe tested, working.

FullStock untested.

Might cause another reboot after first boot and a "new SIM inserted" message. This is normal!

NOTES:

I am not sure TWRP 3.1.0-1 works as expected for everyone. I cannot yet point my finger at TWRP, but I seem to be having trouble with flashing Viper10 with it, so when using the NoWipe variant and you run into flashing issues with flashing ROMs, please downgrade TWRP to 3.1.0-0 which worked fine for me before. All reports regarding failing ROM flashes need to be considered carefully for where to post - either TWRP or Viper10 thread, certainly not this thread. Why this unclarity? Because I have not had time to cross-flash stuff with different recoveries and different ROMs to find the misbehaving bit. I have solely tried to flash Viper10_5.9.0 full ROM once with the -1 version of TWRP and failed with it, so the issue can be anywhere. I am aware of a few isolated incidents on Viper10 thread, but that is simply not enough for anyone to work on the issue at hand. Please do refrain from pointless accusations and help the respective devs to find out where the issue is by providing flash logs to either Captain Throwback and nkk71 on the TWRP thread or to the Viper guys at their respective ROM thread.

[UPDATE] I had time to flash Viper10_5.9.0 with the older 3.1.0-0 TWRP to verify this misbehavior and alas! That rom also doesn't flash on that TWRP for me. This is another hint towards a specific hardware thing that prohibits certain flash parts. It is the boot.img flashing and patching, that fails, so it can very well be related to the HTC lock mechanism being at fault and preventing boot flashes for some odd, random reason on some phones.

There is work needed to narrow this down and I have zero time for this unfortunately. This means, if you run into this issue, I can only recommend to work that out yourself by e.g. Locking/unlocking again, by downgrading firmware to pre-nougat, by swapping out roms, etc etc... Just try everything and find out where this might be coming from.

I doubt it's related to the aroma binary, by the way, because it fails at a part where aroma isn't involved.

CREDITS: [MENTION=4987085]xunholyx[/MENTION] in Hangouts and [MENTION=2702530]hx3[/MENTION] her on thread for linking me with the RUU file.

Other stuff

Nothing in particular, except I am frustrated cuz of the never-ending story with renovating my flat, the constantly rising costs, the frustration. Not much left over. No money, no time. Please excuse my continued absence here on XDA. Too much to look after, still, too many bills to pay.
[HTC 10 Guides, News, & Discussion] xunholyx:
No Wipe is now tested and working as expected.

I got the "remote:90 hboot pre-update" (also expected) and flashed a second time, and it worked of course. :good:
[HTC 10 Guides, News, & Discussion] m.4_ts@yahoo.com:
Deleted
[HTC 10 Guides, News, & Discussion] mushufasas:
Hello,

I've been researching for 3 days now and cant find the RUU for mu phone. I have deleted the system in twrp.

kernel: lk

product: htc_acauhl

version: 1.0

max-download-size: 1141600000

serialno: HT6C31401202

version-main: 1.31.709.1

boot-mode: download

version-baseband: 01.01_U11440971_116.00.61205G_F

version-bootloader: 1.0.0.0000

mid: 2PYB10000

cid: HTC__621

S-OFF

Any help would be much appreciated.
[HTC 10 Guides, News, & Discussion] Slim Jim Guy:
Please, use the appropriate forums next time.

1.31.709.1 - HTC_Asia_TW - htc_acauhl (HTC 10 evo)

Download

MD5: 820258879EC042FE4DDD217595B98ABB

2PYBIMG_ACADIA_UHL_N70_SENSE80GP_hTC_Asia_TW_1.31.709.1_Radio_01.01_U11440971_116.00.61205G_F_release_493193_signed.zip
[HTC 10 Guides, News, & Discussion] mushufasas:
Will do. Much appreciate it!! Downloading it right now.
[HTC 10 Guides, News, & Discussion] xunholyx:
You have the HTC Bolt/10 evo, not the HTC 10. They are two different models and there are no firmwares for you here.

You have S-Off so that is good. First change to superCID (in download mode fastboot oem writecid 11111111 **eight ones**) then use the ROM.zip and instructions found in this thread.

After you flash that you should get OTA updates to the newest version.

Any further questions should be asked in that thread.

Good luck!

EDIT: I see now that someone has helped you out already with the proper RUU for HTC__621.
[HTC 10 Guides, News, & Discussion] mushufasas:
Thank you!! My phone is alive!! Sorry for posting in the wrong thread. Much appreciated.
[HTC 10 Guides, News, & Discussion] nitramus:
delete
[HTC 10 Guides, News, & Discussion] tibere86:
I was on RUU stock 2.48.617.1 (encrypted and unrooted) and flashed the PMEWL_2.48.617.1_Unlocked_TWRP3101_NoWipe.zip to gain TWRP without the need to use fastboot and a computer. Now, I do not get a data signal. Any suggestions?

Edit: Re-flashed RUU 2.48.617.1 and data is working again :good:
[HTC 10 Guides, News, & Discussion] bacon612:
Just an FYI, if youre running an AOSP rom and flash the lastest 2.48 no wipe, you'll loose your radio. Im not sure why AOSP roms are sensitive to this but they are. If you want the lastest firmware and are on AOSP, you have to relock and take a full RUU
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Thanks for the info but relock isn't required to run a RUU usually. It should run S-OFF unlocked just fine unless HTC changed something there.
[HTC 10 Guides, News, & Discussion] Black-FR:
Even S-ON unlocked works, if you first boot into ruu mode, via fastboot command.
[HTC 10 Guides, News, & Discussion] Sevi.666:
Thanks for firmware, but now my phone is now encrypted. :|
[HTC 10 Guides, News, & Discussion] 5m4r7ph0n36uru:
Did you use FullWipe=FullStock? If yes, well there's you answer why this happened.
[HTC 10 Guides, News, & Discussion] °Dexter°:
I tried to flash 2.48.617.11 (NoWipe) changing ModeID in android-info.txt (unzip with 7-zip, edit modelID with notepad++, rezipped with 7zip, normal compression), firmware flashed but system is encrypted now, I type in correct pwd but data appear to be corrupted.

Is there anything i'm doing wrong, developer fw aren't meant for "normal" devices?

I'm S-OFF, with Supercid too
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Recent additions 2.48.617.11 US Unlocked

Recent Additions

WARNINGS:

NoWipe tested, working.

FullStock untested.

Might cause another reboot after first boot and a "new SIM inserted" message. This is normal!

NOTES:

I have put in the new TWRP 3.1.1-0 without having seen any experience reports. You guys find out if it works for you. Else you need to replace your recovery the usual way, manually or as per their app.

CREDITS: [MENTION=4987085]xunholyx[/MENTION] in Hangouts for linking me with the RUU file.

Other stuff

Since I've had to end my relationship, I'll be here more often again until there's someone else to share time with ;) Sorry XDA, but you'll always be second.
[HTC 10 Guides, News, & Discussion] xunholyx:
No-Wipe is tested now. No problems.

I had to flash it twice (remote 90: hboot pre-update), but that was expected. :good:
[HTC 10 Guides, News, & Discussion] Blazin Chaos:
Is there actually any information about what is the true differences between any of the updated firmwares and what benefits they have improved upon?
[HTC 10 Guides, News, & Discussion] xunholyx:
Monthly security updates from Google, mostly.

Depending on what version you are updating from, they can also include performance improvements and fixes for various issues from previous firmwares.
[HTC 10 Guides, News, & Discussion] spacecowboy618:
Thanks again for the update. I had to replace the htc_fastboot.exe in the Batch Tool with another one because it kept giving me a fastboot application error. After that it worked great.
[HTC 10 Guides, News, & Discussion] Zzan:
I just had this same problem going from PMEWL_2.46.617.2_NoWipe_TWRP3101.zip where I have been for a couple of months to PMEWL_2.48.617.11_NoWipe_TWRP3110.zip

Though I did not use the SD Card method. I just used ADB and HTC_Fastboot like I always have.

I tried flashing again. Same results. Downloaded from a different mirror and re-flashed. Same results. Everything looks like it applied properly and no errors. Just stuck in a boot loop after restart.

Once I try to use the phone after reboot I get a pop-up: Settings successfully update. Tap to restart your phone

I restart and it happens every time.

I went back to PMEWL_2.46.617.2_NoWipe_TWRP3101.zip and now it is looping as well.

When I take out my T-Mobile sim I don't get the restart message and the device is usable (except phone/data related functions of course.) As soon as I replace the SIM card the reboot pops up and the loop continues.

Any way to break this loop?

EDIT: Ran the RUU as per Sneakyghost's suggestion below and phone is usable again. Now in the process of restoring backups.
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Yeah I've seen this happen a couple of times, although the reason evades me. No clue. What fixed this was to run a RUU and start over clean.
[HTC 10 Guides, News, & Discussion] Pauls57:
I Had this happen and ended up running an ruu to fix. I'm also on T-Mobile US. Is this only occurring on T-Mobile? Since it doesn't loop with the sim card removed, I'm wondering if a quick stop at T-Mobile for a replacement sim card would be an easier fix. Has anyone tried that?
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Nah man nothing to do with the SIM. Something wrong with the update process. Some messed up crap. RUU and fix.
[HTC 10 Guides, News, & Discussion] mrro82:
[MENTION=1102297]Sneakyghost[/MENTION] New T Mobile FW is out. Would you be able to work your magic on it?

http://www.htc.com/us/support/htc-10-t-mobile/news/
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Yeah can do. Tomorrow though. Bit tired right now.
[HTC 10 Guides, News, & Discussion] mrro82:
Awesome! Thank you!
[HTC 10 Guides, News, & Discussion] jbm76:
Telstra finally got the N update [MENTION=1102297]Sneakyghost[/MENTION]

If you want to do your magic - http://fotadl-az.htc.com/secure/OTA...1.95.841.3_release_5057557j9tp6dxjsowzxm3.zip
[HTC 10 Guides, News, & Discussion] jbm76:
Double post
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Recent additions 2.41.531.44 TMUS

Thank you, Sir.

I have TmoUS queued up already. Think i might be doing both today.

[EDIT] [MENTION=3806315]jbm76[/MENTION] mate I won't be able to do that Telstra thing. Its an OTA meant to update some 1.95.841.3 RUU/OTA.

I only have 1.21.841.8 RUU, then OTA from that to 1.53.841.6, then OTA from that to 1.80.841.1 - means I am missing at least one intermediate OTA or a newer RUU in between. I would need to have all OTA files building up to and including 1.95.841.3 or a RUU version of 1.95.841.3.

Since I am not going hunting for these files anymore, I'd need you (or anyone) with a fitting link at hand before I can start.

/back to kitchen. Chicken Tikka Time.

Recent Additions​

NOTES:

FullStock Untested

NoWipe tested, working

WARNINGS:

- nothing - the usual - dunno really

Credits: mrro82 for notifying us about the update
[HTC 10 Guides, News, & Discussion] jbm76:
The update after 1.80 was 1.95.841.3 which I thought you had, it was an OTA update. Only been 1 RUU which was 1.21.

Could you please double check? I was fairly certain you had everything.
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Oh good lord, yeah. Shame on me. I see it now. I was checking my stock OTA folder on my main machine and there was no 1.95.841.3. since I keep all stock files for at least two years, i was dead sure there was no firmware pack for it either.

Guess I've failed my standards there.

It's late now, might do that tomorrow then. Sorry for the mishap.
[HTC 10 Guides, News, & Discussion] jbm76:
All good, thanks for checking. Enjoy your rest mate..
[HTC 10 Guides, News, & Discussion] mrro82:
The T Mobile zip flashed just fine and everything is working. Thanks again [MENTION=1102297]Sneakyghost[/MENTION] !
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Which one? Or did you test both?
[HTC 10 Guides, News, & Discussion] mrro82:
Sorry. Just the no wipe. I didn't test the full.
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Recent additions 2.48.841.3 TELSTRA

Recent Additions

WARNINGS:

FullStock Untested

NoWipe tested, working

NOTES:

There is an additional "usb_typec_otp_ad.img" besides the regular "usb_typec_otp.img" and "usb_typec.img". This extra file was also introduced on the US Unlocked 2.48 release, but there, the "usb_typec_otp.img" is gone. I suspect, that one replaces the other and there should be no two of them. I left it in though, because it can also be that one patches the other and both are needed. Maybe when you guys flash this, test your USB C connection on all protocols and functions. I did a quick web search on USB TYPEC OTP but there is not much coming up, maybe "One Time Password" - maybe its an image relevant for USB security. Dunno. just see if something behaves oddly.

CREDITS:

[MENTION=3806315]jbm76[/MENTION] for linking the file and testing NoWipe.
[HTC 10 Guides, News, & Discussion] jbm76:
Flashed the no-wipe ver, and worked perfectly as I can see :) Thanks for your work mate! Always appreciated :good:
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Recent additions 2.50.617.2 US Unlocked

Recent Additions

WARNINGS:

untested.

NOTES:

- nothing right now -

CREDITS: [MENTION=4987085]xunholyx[/MENTION] in Hangouts for decrypting and sending me the RUU based firmware.

Other stuff

My girl still doesn't want to come back, so you'll have me around a little longer :D
[HTC 10 Guides, News, & Discussion] GottaStayFly:
umm.. so trying to flash the latest firmware (june security update) via using the batch tool, I am locked bootlaoder, S-OFF, and im getting an issue where I use the batch tool

and looking at your error list I have hardware failure??? My phone was working perfectly fine before the latest OTA killed my mobile data
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Yeah apparently so.

We've worked out this odd situation in the past months or so as being a probable hardware failure.

It isn't exactly uncommon. The chips can die.

You can still get the RUU these images were taken from, but you'll likely end up with a similar or identical error. The people encountering this before you were all unable to recover the phone.

I'd still try though. Go to HTC ROM download page and get the RUU. Run that. See what happens. And, please, report here as well if you have the time to spare. I'd be interested.

Thanks.
[HTC 10 Guides, News, & Discussion] GottaStayFly:
that is not the news I wanted to hear....... I actually already tried using a RUU and it ends up doing this....

RUU sending information goes to 3% on the bar, but than it gets stuck on updating boot for a good few mins.. while on the phone it hangs around 90% progress bar and just suddenly stops. RUU than gives me error 155​

and the stupid part is that my phone functions completely fine, storage doesn't have issues, I can do calls text receive and outgoing, wifi and bluetooth all works cept for data...
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Unfortunately, if the RUU doesn't fix it, there is not much more i can recommend. HTC's RUU is designed to run for most people without issues and fix most common flashing problems. If it doesn't, next escalation step would be HTC Service Center (which sucks big time, admittedly).

One thing you can still try is to run the rom.zip from inside the ruu.exe via the sdcard method outlined in the OP, as that would eliminate possible transfer/driver/usb stack issues.

But honestly, we've been through this and experience was that it was unfixable hardware damage. Dead Synaptics touch pad controller Chip in your case.
[HTC 10 Guides, News, & Discussion] nkk71:
Sneaky, let him use a different cable/hub/etc/etc, and post the whole thing, not a partial logs, sounds like a bad connection to me.

Or just use the sdcard method.
[HTC 10 Guides, News, & Discussion] Sneakyghost:
Like i said we've been through this and i don't think it's the connection, but to rule that out i already suggested to try the sdcard method. Thanks, buddy
[HTC 10 Guides, News, & Discussion] nkk71:
Could very well be a hardware problem, just looking at that partial log:

bootloader) tp_SYN3708.img@50%
[B](bootloader) ERR do_firmware_update_thread: waitpid failed: 0[/B]
(bootloader) ERR Flashing [tp_SYN3708.img] [B]timeout[/B]
(bootloader) ERR do_firmware_update_thread: kill unfinished child proces
(bootloader) s: 499

Could (I really mean *could*, not *is*) a connection issue.

I've *accidentally* had my cable removed during an RUU flash... it wasn't very funny :eek: