yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M7)] xx_bishop_xx:
Hello-

I am running the latest ViperOne ROM, and I began to have the "no voice" issue the other day. I was able to flash the latest firmware that you have posted here, but I the "no voice" issue still persists. I did dirty flash the ROM again as well. Any suggestions?

Strange, when I check the software information it shows baseband version=1.13.41.0702 which I guess is fine, but the build number=6.09.401.5 CL366813 release-keys...that doesn't seem to match.

*edit* Of course my software number=ViperOne 7.0.1 and I'm not certain how to determine the actual software number.

Thank you.
[Verizon HTC One (M7)] Uzephi:
Software number is the Rom. 7.0.1 is based off 6.09.401.5 from the international one. That is why it says that. I had odd issues when flashing my nandroid. I had to dirty flash viper again and run the firmware zip twice to fix it.
[Verizon HTC One (M7)] WillyRy:
Many people are having this issue.

Head over to the main m7 Venom page and there's many posts of fixes and links to a dedicated Q&A fix thread.
[Verizon HTC One (M7)] Nazo:
So, for the record, as you probably already know, the latest firmware link is still not up after all this time. What you may not know is that the 2.10 signed firmware file appears to be corrupted (errors in several key files in the archive.) I've downloaded multiple times from multiple mirrors and always get the error that it has "too many links" in the flasher. When I test the archive on the PC it fails in a number of files and I think even says unexpected end of archive as if the download were incomplete (unless every single of my multiple downloads managed to fail somehow without an error, it's the source.)
[Verizon HTC One (M7)] santod040:
What are you talking about? :confused: No I don't know... :o

Latest firmware has been up since the day it was released.

Link works just fine and takes you here: LINK

All previous versions are fine as well.

The issues you are having are on your end.

If you wanted help, asking would have worked better then blaming the files provided.

It has more to do with how you are applying and/or opening the files then it does with your download, I'm sure...

But all files posted are complete and fine.

You are the only one with any issues with them and the latest firmware is definitely available in the second post.
[Verizon HTC One (M7)] Nazo:
I misspoke and meant the ROM -- the RUU to be specific. The 5.28 version has been gone for a long time, for some reason there are no in-betweens like 4.10, and the 2.10 signed is corrupted.

I'm trying to return a phone to stock and it's getting pretty hard to actually do.
[Verizon HTC One (M7)] santod040:
http://xdaforums.com/showthread.php?t=
[Verizon HTC One (M7)] Nazo:
Somehow the thread number didn't make it in the URL.

Anyway, more than anything else it's just a FYI that the one file is damaged and should probably be reuploaded. I'm guessing the latest RUU isn't going up any time soon (ever?) and I'm not setting out to blame anyone.
[Verizon HTC One (M7)] santod040:
Since this seems to be a repeat of your thread in Q&A, I will repost my reply from there:
[Verizon HTC One (M7)] Nazo:
Ah, sorry, this is actually separate. It was from when I was following the guide. That was just a FYI since I thought perhaps the file should be reuploaded.

However, now I'm not certain of even that. ARE the ZIP files supposed to appear to be corrupted if tested in an archive manager? I did get that "too many links" error on the 2.10 signed (I opened it in the archive manager after that error trying to see why it said that and while trying to extract the archive manager informed the the files were corrupted,) but I just noticed the signed 1.10 also appears to be corrupted when I open it. Is the encryption somehow applied to the data within the ZIP file itself but not as a standard "password" style encryption method, or are these files corrupted after all? If they are corrupted then surely they do need to be reuploaded. Otherwise nevermind.

It's odd though. I get the corruption from multiple sources and it seems unlikely that they would all go bad, right? The 2.10 decrypted works great from one of the same sources (I never tried any others -- AndroidFileHost can be pretty slow and these > 1GiB files take quite a while.) I'll admit I didn't try the 1.10 decrypted.
[Verizon HTC One (M7)] santod040:
Signed ruu files are encrypted from HTC and cannot be opened in a zip utility.

Ones that have been decrypted can be opened in a zip utility.

All files posted are working and are fine, no need to reupload any of them.

"Too many links" error typically means you are trying to apply the update incorrectly (fastboot rather then ruu mode, etc) or you have the file nested inside of too many directories on your PC.

Usually it's the first reason.

I believe this error can also come up when trying to apply an older ruu on top of a device already running newer firmware, which is probably what you ran into.

But again, you cannot open an encrypted ruu file with a zip utility...that's why there is a tool for decrypting and some of those have been done and made available as well.
[Verizon HTC One (M7)] Nazo:
Ah, sorry for the false alarm then. It's odd though, you'd think the data inside the image files would be the only thing encrypted, not parts of the archive via a non-standard method. I didn't expect that and it didn't even occur to me at the time of the first post when it just seemed like one file had been uploaded incorrectly (or somehow damaged on the file host.) In all fairness, it IS a nonstandard way of encrypting, lol.
[Verizon HTC One (M7)] disconnecktie:
A much easier and effective way to check for corrupt zips is doing a md5 check. If yours doesn't match the one supplied on afh then you know your download was corrupt. This isn't a fault of Santod. Bad downloads can just happen sometimes.
[Verizon HTC One (M7)] Nazo:
My thought was that the original upload itself was damaged. Thus the MD5 on AFH would match the corrupted file. And I was never looking to pass blame or something. It was just a FYI that it should be reuploaded if it was really corrupted. Nothing more, nothing less.
[Verizon HTC One (M7)] disconnecktie:
If the initial upload was corrupted then close to a thousand people would have the same corrupted download.
[Verizon HTC One (M7)] neutronjeff:
Hey, on stock we're getting themed apps from HTC, hopefully the wait for Lollipop isn't too much longer.
[Verizon HTC One (M7)] Youngtusk:
Santod is the F---ing Man.

As usual, Santod is the man. Thanks for this sir, I think this is the third of fourth time you've made the tools I need to fix my stupid mistakes that almost brick my phone. Not to mention your ROMs are always the ones I end up using after trying a whole bunch. $10 for you, wish I could afford more.

Thanks man, you rock!
[Verizon HTC One (M7)] neutronjeff:
[MENTION=1862878]movers[/MENTION]i: Verizon HTC One (M7) Owners! Thank you for your amazing patience. We've received TA on L OS, OTA starting on Thursday.
[Verizon HTC One (M7)] bdizzle1686:
So, [MENTION=1331268]santod040[/MENTION] or [MENTION=4310221]disconnecktie[/MENTION] , did I read right that if I flashed the full odex Rom and stock recovery, I'll be able to successfully take the lollipop OTA that were FINALLY about to get?
[Verizon HTC One (M7)] neutronjeff:
If you're rooted, just wait a bit for Santod to work his magic. No need to go through the headache of taking the OTA.
[Verizon HTC One (M7)] bdizzle1686:
I know, but honestly I've always preferred being on stock rooted when possible. Believe it or not, I've always preferred stock rooted Rom n then modding it to my own liking, rather than custom roms.
[Verizon HTC One (M7)] Lt. Belspur:
Don't take the OTA. Repeat don't take the OTA.

You might end up relocking your boot loader and it will cost you $25.00 to Sunshine it.

You should not be prompted to anyway. Santod usually removes that option.

Just wait for Santod to recompile the OTA for your flashing pleasure.

Plus we will have to upgrade our firmware first.

Patience, Patience, Patience
[Verizon HTC One (M7)] bdizzle1686:
I'll wait a lol while, but I've already bought sunshine. An HTC OTA has NEVER relocked a boot loader or turned S-off back to S-on..

I will wait as always to make sure this is verified, but as far as I know, it's never happened before on a HTC OTA.

But thanks for the advice. If [MENTION=1331268]santod040[/MENTION] DOES push out his usual firmware and Rom packages, I'll probably go that route as the only cpu I have access to at the moment is my sister's laptop, and I haven't set up adb or anything for fastboot yet anyways, and God knows I'm not going without root, so I gotta get that Set up 1st anyways.

---------- Post added at 01:11 PM ---------- Previous post was at 01:02 PM ----------

its here! Waiting confirmation on what best course of action is , there's a firmware upgrade *1 of 2* available
[Verizon HTC One (M7)] Lt. Belspur:
Just wait. We have waited this long, what is a few more days. LOL.

It's a two part update.

Oh, and yes an OTA can relock the bootloader. HTC Thunderbolt. I know. I wrote the procedure after the ICS update came out. See my signature.
[Verizon HTC One (M7)] disconnecktie:
Just wait. Taking the ota when you're rooted is a big pain in the ass. If everything isn't perfect the update will fail to install and you'll be left picking up the pieces. I don't recommend taking it unless you have experience doing so. Plus if you have to lock (which I don't think you do) there is a possibility that the update might include an hboot that sunshine can't unlock. Considering this is an aging device there is a chance that jcase may not bother updating sunshine for it again.
[Verizon HTC One (M7)] santod040:
If you wanna wipe your device and go pure stock, Dottat posted an RUU that will wipe your phone and put you on the latest stock update.

Then you reflash twrp and go on your way...

Otherwise I'll have stock rooted flashable roms up as free time allows.

Not in a huge hurry since the RUU is posted and others are now posting their idea of modified firmwares.

Although I do mine a bit differently...so I'll still be posting mine as I always have.
[Verizon HTC One (M7)] Lt. Belspur:
I am waiting for yours. :D
[Verizon HTC One (M7)] bdizzle1686:
I ALREADY TOOK the 1st part of the ota and it looks as if it went through successfully... Im rebooting now...

---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------

I already spoke with [MENTION=3472611]dottat[/MENTION] earlier n he said it doesnt / wont relock the bootloader
[Verizon HTC One (M7)] bdizzle1686:
[MENTION=1331268]santod040[/MENTION] and everyone else, just wanted to let everyone know santods tools from this thread DID work. Just flashed stock odex 443 Rom, used flashify to flash stock recovery, then took the OTA . Dottat confirmed with me that this is the same method he tested and it did not relock the boot loader, so tomorrow I'll reflash twrp and get rooted again, too tired tonight honestly
[Verizon HTC One (M7)] santod040:
Firmware Updated to 6.22.605.3 Lollipop 5.0.2

Multiple firmware zips added to Post #2.

Please read the following, as posted in the second post.

If you are confused, ask before you do anything, but I have tried to make it pretty clear.

LOLLIPOP 6.22.605.3

Please read carefully:

Lollipop came in two OTA's.

The first one contained a firmware package and so did the second one.

In the first firmware package, there is the new radio and other files that get replaced by the second firmware package.

So I am posting both the first firmware package and the second one.

Also, I am posting a FULL combo package that I put together, which will apply all files from both, leaving you with the latest of all the firmware including the radio from the first OTA.

I am posting that Full combo modified without the stock recovery and boot.img.

Most users should be able to just simply flash the Modified Combo Firmware zip and be all set.

These will all have the recovery and boot.img removed, so that you do not have to reflash Twrp and are not stuck with a secure boot.img.

Firmware from LP Pre-Update

Firmware from 2nd LP Update

6.22.605.3 Firmware Combo for m7vzw Lollipop (This is all most users should need) LATEST***
[Verizon HTC One (M7)] bdizzle1686:
Any possibility of releasing an UN-secure boot img. For those who took the ota? We need to flash an unsecure boot img to flash custom kernels, right?
[Verizon HTC One (M7)] santod040:
Correct and yeah I will put one up shortly...

Trying to get a rom or two together as well.
[Verizon HTC One (M7)] bdizzle1686:
You r a GOD Santod!
[Verizon HTC One (M7)] ohbuckeyeman:
Thanks for all you do Santod. Worked like a charm. Would love if it made the M7 support XLTE, but I know we don't have the hardware support for it. Is VoLTE possible on M7?
[Verizon HTC One (M7)] santod040:
To my knowledge, it doesn't support either unfortunately..

The m8 was the first One to support VoLTE and XLTE if I recall.

It was supposed to get some enhanced calling features in Lollipop I thought, maybe better video calling support, not sure to be honest.

I'm not seeing anything else obvious yet anyways.
[Verizon HTC One (M7)] santod040:
Did see they added this above and beyond what's in the Gsm ramdisk, so hmmm....

# VoLTE porting s
service imsqmidaemon /system/bin/imsqmidaemon
class main
user system
socket ims_qmid stream 0660 system radio
group ims radio net_raw log qcom_diag

# imsdatadaemon starts with root and UID will be downgraded to SYSTEM.
service imsdatadaemon /system/bin/imsdatadaemon
class main
user root
socket ims_datad stream 0660 system radio
group ims radio wifi net_raw log qcom_diag net_admin
disabled

on property:sys.ims.QMI_DAEMON_STATUS=1
start imsdatadaemon

service ims_rtp_daemon /system/bin/ims_rtp_daemon
class main
user system
socket ims_rtpd stream 0660 system ims
group ims net_raw diag qcom_diag log
disabled

on property:sys.ims.DATA_DAEMON_STATUS=1
start ims_rtp_daemon

on property:persist.cne.UseCne=none
stop cnd

service cnd /system/bin/cnd
class core
socket cnd stream 660 root radio
# VoLTE porting e
[Verizon HTC One (M7)] santod040:
:o

Added to second post:

LOLLIPOP

6.22.605.3 Insecure stock boot.img only***LATEST

fastboot flash boot boot.img
[Verizon HTC One (M7)] santod040:
Full Odex rooted stock rom is done, which is the basis for the rest.

Will get the others finished as well, tomorrow after work, and upload all 4 variations.

For now, I must get to bed, work at 4am....
[Verizon HTC One (M7)] Lt. Belspur:
And what did I say:

"Don't take the OTA"

All you had to do was wait not even 24 hours to get Santod's version.

Santod, Thank you for releasing this very quickly.
[Verizon HTC One (M7)] cesium:
Thanks for all your hard work! Can't wait to hopefully flash tonight :)
[Verizon HTC One (M7)] bdizzle1686:
Hey [MENTION=1331268]santod040[/MENTION] or anybody else who can help, so with the filename of the insecure boot img. Being- 6.22.605.3_insecure_m7vzw-LP_boot , can somebody tell me what exactly the command I need to type in fastboot is?

I know santod put the example fastboot flash boot boot.img, so would the EXACT command I need to type be

Fastboot flash boot 6.22.605.3_insecure_m7vzw-LP_boot.img ??

I'm kinda new to fastboot n sitting at my cpu now n just want some confirmation before I do something stupid.. so if [MENTION=1331268]santod040[/MENTION] or [MENTION=4310221]disconnecktie[/MENTION] or anybody else could chime in n help me out here, it would be GREATLY appreciated!
[Verizon HTC One (M7)] Lt. Belspur:
Post #2 has the instructions
[Verizon HTC One (M7)] bdizzle1686:
I know, I read it, im just not 100% sure if im understanding it correctly , so thats y im asking if I Typed the correct command in my previous post.. could u tell me if the command I wrote is correct? I based it off of whAt santod wrote in his instructions, just wanted to make sure I read and understood it correctly...
[Verizon HTC One (M7)] Lt. Belspur:
That is correct if you did not rename the file.

Have you ever flashed a boot.img or firmware before?
[Verizon HTC One (M7)] santod040:
Yes, enter command as you stated or rename it for simplicity.

As long as that image is flashed to boot, the name doesn't really matter. :)
[Verizon HTC One (M7)] bdizzle1686:
on 4.4.3, BUT that was a recovery flashable boot.img fromthe guys who made the Élite Lunar kernels.. Ive never done it through fastboot though. I just got done flashing twrp through fastboot, first time Ive ever done that. Im now successfully rooted again, just need to do the boot .img now.

Thanks. N I can just do it from fastboot mide right? I dont go into ruu mode, correct?

I appreciate your guys help & patience, I HAVE read everything, im just really overly OCD , especially when it comes to my phone and like to make sure about something, rather than just rushing into it without fully understanding things.
[Verizon HTC One (M7)] chaosz3ro:
Just follow the directions exactly as they're stated in his post? Copy and paste if you want to be extra careful. Everything is laid out in the second post EXACTLY what you need to do.
[Verizon HTC One (M7)] Lt. Belspur:
Yes, but I warned you not to take the OTA. You rushed right into it and look what you have to do now. Your quote "rather than just rushing into it without fully understanding things."

When it comes to flashing, you must have patience. One wrong move and your bricked.

We are here to help. Just listen to the experts. :D
[Verizon HTC One (M7)] bdizzle1686:
Ok so the only question I have left n the LAST flashing I have left to do, I know I have the right command, I'm just unsure of 1 thing still, and as u said, I definitely DON'T wanna make the wrong move n be f*'d , i need to flash the boot.img in REGULAR FASTBOOT MODE, just as I flashed the twrp recovery, CORRECT?
[Verizon HTC One (M7)] Lt. Belspur:
fastboot flash boot boot.img

Make sure the Boot.img is the name of the file you want to flash
[Verizon HTC One (M7)] bdizzle1686:
Should I do fastboot Érase caché Or any other commands after?

---------- Post added at 04:06 PM ---------- Previous post was at 03:23 PM ----------

Thanks for all the help guys, really appreciate it n now I have some experience with fastboot .. Now has anyone used or can recommend any custom kernels that work with the newest lollipop update???
[Verizon HTC One (M7)] Lt. Belspur:
Not necessary.

You will have to wait for a DEV to compile one from the source code for stand alone use. That may take a while. Will have to wait for HTC to release it.

Santod has kernels, but there in his other ROM'S
[Verizon HTC One (M7)] bdizzle1686:
Would those kernels (Nukernel) work on the stock rooted rom, s-off, unlocked bootloader with insecure boot.img?

Reason I ask is because earlier this month on Santods NuSense6 lollipop rom I used Flashify to make a backup of the Nukernel in the rom...
[Verizon HTC One (M7)] carngeX:
Just to double check...the 6.22.605.3 firmware/radios that were posted are ok to flash while running NuSenseSeven, right?
[Verizon HTC One (M7)] Lt. Belspur:
Yes they are. Combo flashed without a hitch.
[Verizon HTC One (M7)] carngeX:
Thought so, just wanted to double check. Thanks!
[Verizon HTC One (M7)] bdizzle1686:
According to [MENTION=4428185]brymaster5000[/MENTION] , his elite lunar kernel is compatible, he says that HTC already released the source code back when lollipop sense 1st came out. He said VZW was just way late (which is a HUGE understatement)
[Verizon HTC One (M7)] brymaster5000:
It should. I used the 5.0.2 source from a while back. It looks like they've been posting a bunch of 5.0.1 source files. Let me know if it doesn't and I might update if need be.

Edit: Sorry realized this wasn't my kernel thread after replying.

Sent from my Elite N6
[Verizon HTC One (M7)] aceof89:
I was running NuSense7 with what was the latest firmware. I followed the steps in Post #2using the COMBO file and at the point of running 'fastboot flash zip firmware.zip' for the 2nd time as specified it seems to have failed. Here is how it ended:

(bootloader) [RUU]UZ,rcdata,0

(bootloader) [RUU]UZ,rcdata,100

(bootloader) [RUU]WP,rcdata,0

(bootloader) [RUU]WP,rcdata,100

(bootloader) ...... Successful

(bootloader) start image[emmc_fw32] unzipping & flushing...

FAILED (status read failed (Too many links))

finished. total time: 23.201s

c:\adb>

My phone now has a triangle with an exclamation point in it in all 4 corners of the screen. Any ideas on what I can do now? Thanks.
[Verizon HTC One (M7)] santod040:
Were you in RUU mode or in fastboot?

Did you have the last firmware before this already flashed?
[Verizon HTC One (M7)] aceof89:
Fastboot via Power + Vol Down

Almost definitely since I want to be on latest once you post. I took screenshots of baseband, etc but of course they are inaccessible right now on the phone. I recall 1.13xxx as a baseband if that helps though.
[Verizon HTC One (M7)] santod040:
ReRead the instructions, firmware is flashed in RUU mode.
[Verizon HTC One (M7)] aceof89:
added

Does the info below indicate I did it wrong? I'm not sure where I went wrong but am willing to follow the steps again in post 2 if you think it will help same triangles . The 2nd point in Post #2 said to boot into Fastboot mode which is why I answered that way. Sorry if I confused you.

C:\WINDOWS\system32>cd c:\adb

c:\adb>fastboot oem rebootRUU

...

(bootloader) Start Verify: 0

OKAY [ 0.063s]

finished. total time: 0.063s

c:\adb>fastboot flash zip firmware.zip

target reported max download size of 1526722560 bytes

sending 'zip' (24690 KB)...

OKAY [ 1.929s]

writing 'zip'...

(bootloader) zip header checking...

(bootloader) zip info parsing...

(bootloader) checking model ID...

(bootloader) checking custom ID...

(bootloader) start image[hboot] unzipping for pre-update check...

(bootloader) start image[hboot] flushing...

(bootloader) [RUU]WP,hboot,0
[Verizon HTC One (M7)] santod040:
That looks normal.

I have a feeling you maybe didn't fully update the previous firmware first.

Or else you are having a fastboot driver issue.

You can find an HTC specific fastboot in the last page or two of Dottat's thread you might wanna try.

I would also probably try reflashing the previous firmware, and then try the new one again.
[Verizon HTC One (M7)] aceof89:
Ok, thanks. Can you tell me how to get out of the HTC screen with the 4 triangles? Sorry for asking but I'm in unfamiliar territory. I did grab the other fastboot files as suggested. Vol Down + Power gets me to the same screen.
[Verizon HTC One (M7)] santod040:
If holding volume down after restart doesn't get you back to fastboot, then you'll probably have to try and run the RUU posted by Dottat.

I've never been stuck in that mode myself, but have read lots about it online over the years with many HTC devices.

It's typically from a bad firmware/RUU flash and flashing an RUU is typically the fix.

Maybe your download was corrupt. Not really sure, but like I said, never ran into that myself....sorry.