yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] exploitz:
Hello, Ive come over from this thread here: http://xdaforums.com/showthread.php?t=2776785&page=16

Im trying to update my firmware to 2.22 from 1.54. Im s-on and I have cid TMOBO10.

Using the guide in the OP I get error 99 when trying to flash the fastboot zip. Another xda member troubledshooted with and me we got nowhere. So I downloaded HTC Sync Manager and installed the drivers and I tried using the FUU provided by sneakyghost. It won't flash either! I get error 171. Usb Connection Error. Sounds simple.. I have a brand new oem sync cable that Im using here! Why isnt it working? Thanks for any help :)
[One (M8) Android Development] Behold_this:
Ignore the error code. Your problem is you're s-on. The FUU firmware package is not signed and so you will never be able to flash it while you are s-on. This thread is geared towards s-off users. Maybe you missed the top of the OP:

Please refer to sunshine s-off to get yourself squared away.
[One (M8) Android Development] exploitz:
I was using sapplegater's firmware.zip file. Same error 99.

I didnt know if you could tell me why my fastboot flashes werent working. Both your fastboot zips and his firmware.zip do the same thing in fastboot. I followed the tutorial in your post to guide me.
[One (M8) Android Development] Behold_this:
Lock your bootloader
[One (M8) Android Development] exploitz:
Oh you are my favorite person. 1 MILLION times thanks to you :) I asked sapplegate but he said no. Glad I got your second opinion.
[One (M8) Android Development] Behold_this:
It's only necessary due to you being s-on
[One (M8) Android Development] exploitz:
I know, I want s-off but money is too tight right now. Thanks for your help again.

I didnt realize it wiped out my system when I relocked. Having to go through some hoops now lol :P
[One (M8) Android Development] Sneakyghost:
Hi Sir,

yes i did indeed misunderstand you. I was under the impression you still had an "old" (meaning 1.54 or something like that) firmware running. But it does not change very much now. Only thing it changes that it obviously destroys my theory that its the old firmware/new rom what causes this.

Thanks for clearing that up. The end result, a FUU fixes this, remains the same though.

So, Firmware ruled out, remains to be seen if it's Philz Touch or just a dodgy hardware that causes this. Waiting for more cases to compare to turn up. I can't repro it.
[One (M8) Android Development] Sneakyghost:
Cake? What you on about? :laugh:

Hey buddy thanks for trying. As i said, i flashed Philz and System switched to dalvik, coming from ART. Tried the same with TWRP, system kept using ART. I did something funny before flashing Philz though, could have caused the switch too. Can't remember what i did exactly anymore. Yesterday was crazy. Too much sh!t at once.
[One (M8) Android Development] donmarkoni:
TWRP cake. ;) The latest one without empty OS line bug. I guess that's the one you are using, right?
[One (M8) Android Development] Sneakyghost:
http://xdaforums.com/showpost.php?p=54345881&postcount=96

[EDIT]

That was the wrong post i linked.

Here's [MENTION=1131176]Garmig[/MENTION]s kind post with the link to [MENTION=333497]migascalp[/MENTION]'s fixed version http://xdaforums.com/showpost.php?p=54309870&postcount=76
[One (M8) Android Development] tiho5:
One of those reports about faulty twrp backups was from me.

I am very busy lately and can't post and be active on xda as much. But I'm still reading and following everything and this time I will take the time to support Marko on this matter.

I know I wasn't doing anything wrong, because I was using twrp recovery since quite some time, but I started noticing backups not having the right size. Some of the imgs were noticeably smaller. Completion time was suspicious. So I decided to check and yes, restore wasn't possible. But the thing which bothered me most was that ALL THESE TIMES TWRP REPORTED SUCCESSFUL BACKUP!

I reported this number of times in the thread, sent logs, made different backup tests, many of which came out to be incomplete. Again a success was reported by twrp.

Nobody there made anything and/or paid attention.

In such a situation Phil would react almost immediately. He is much more responsive and that's admirable. And a big advantage. Despite the Aroma issue, which isn't recovery fault rather outdated Aroma support.

Phillz recovery has other interesting advantages and is indeed fast, plus reliable. On top the dev is responsive, and so... I switched to it of coarse. Never had a problem.

I think that Venom team would have had a true support in recoveries field if they have turned to Phil. He makes changes (even minor ones) to please his users not to mention what he could do if he had the need and request of a whole community of such caliber.

I mean look at the close rapport between Flar and Venom team (other ROMs teams too) and how good that is. And always recoveries devs, although being so important, never had been that close around. So pretty much many ROM devs often have to spend time instructing and helping their users on recoveries issues.

(may be I shouldn't mention this, but I saw this happen and I wasn't happy: there was also one unfortunate case in the early times of the HTC One m8 form when I think Turge was a bit irritated by one of Phil's comments which wasn't intentional and so these 2 sides "aren't very close now", which I think isn't something the community could gain from, but that is my opinion...)

Thank you Sneaky, Marko and the rest here for researching, testing, providing and trying stuff to help others! I wish I had the time to be here too doing the same, but these days this just isn't possible.
[One (M8) Android Development] Sneakyghost:
Thanks for your opinion buddy :D but this is not about recovery blaming but more about finding out why these weird three corrupted data partitions turned up. Among the involved factors were recoveries. So, gotta look at them as well, right?

And Team Venom simply works with TWRP because it supports the OTA mechanism best and doesn't need anyone to put extra work in. It just works. The dev team has so much on their plate that they simply don't want to go bug hunting on another field. Its just time and energy saving. No one says one is better than the other. People who don't want to use TWRP can do so. They'll just have to figure out bugs on their own, while we do, to some extend, help with bugs encountered in TWRP.

It's all good, you know. I was using Philz myself for quite some time. Just moved over to TWRP because of the support, i gotta work with it if i want to support it. And to be honest, the mentioned issues do not happen at the moment. ;)

Now, can we drop this and have this a Firmware thread that's looking for potential firmware issues, again? Thanks :D
[One (M8) Android Development] pjdannie:
Hi there I am looking for some advice here as I am thinking of updating to 2.22 and viper 2.2, I am currently running the following:

C:\adb>fastboot getvar all

INFOversion: 0.5

INFOversion-bootloader: 3.16.0.0000

INFOversion-baseband: 1.15.2133156.UA13G

INFOversion-cpld: None

INFOversion-microp: None

INFOversion-main:

INFOversion-misc: PVT SHIP S-OFF

INFOserialno: SH43GWM

INFOimei:

INFOimei2: Not Support

INFOmeid: 00000000000000

INFOproduct: m8_ul

INFOplatform: hTCBmsm8974

INFOmodelid: 0P6B10000

INFOcidnum: VODAP001

INFObattery-status: good

INFObattery-voltage: 0mV

INFOpartition-layout: Generic

INFOsecurity: off

INFObuild-mode: SHIP

INFOboot-mode: FASTBOOT

INFOcommitno-bootloader: ab0efa49

INFOhbootpreupdate: 11

INFOgencheckpt: 0

all: Done!

finished. total time: 0.025s

I have also got a modified hboot from this thread:

http://xdaforums.com/showthread.php?t=2710503

I was hoping I could set super CID then use your 2.22.401.5 full stock with wipe firmware zip

and then flash the correct TWRP

and finally the ROM

then wipe cache

I am sorry for my ignorance here as I have read that I should revert the hboot to standard only I do not have the original.

Will/should I be ok in doing this?

Any advice or pointers would be greatly appreciated.

Thanks in advance

Pj
[One (M8) Android Development] Sneakyghost:
Generally not a problem, although i have switched to a policy of "no firmware update while a modified hboot is installed" due to security concerns.

Sadly, the thread you linked does not offer back-to-stock untouched versions of the respective hboots. Not the best strategy but oh well. To each their own. If the provider thinks its safe, his decision.

I can't do much for you except telling you: go ahead. Just flash the firmware. It'll be ok with 99% certainty. Just to let you know, the bricks we saw earlier this year were - maybe- due to a hboot not fit for the update. That's why i stopped doing hboots altogether. Because this maybe 1% chance.

So, I'd say you're pretty safe. 100% safety is impossible anyway.

So, what you do is change to SuperCID and then just run the 2.22.401.5 FUU and then flash TWRP and then flash the ROM (put it on your external SD).

Your MainVer is blank by the way, you are running the bugged TWRP that deletes this info. So i have no idea what firmware you are on but i guess its 1.54 because you got the Radio from that version. Your hboot? Hmm. Next time, ask the dude you get your red text removal from to provide you with an untouched stock copy as well.
[One (M8) Android Development] pjdannie:
Thank you !

Thank you,

I just needed someone who knows what they are talking about to confirm what I thought I could do with what I have.

I also take on board what you say about the modified hboots and how important it is to get the right file from the right source and furthermore be able to revert the modifications.

Thank you again,

You are a tremendous help and wizard imho,, just like all the devs involved with the top mods for our M8 devices.

Cheers

Pj

p.s. I may have to request a modified hboot from you once I have rebuilt my complete preference of settings and apps on the new base and rom.
[One (M8) Android Development] Sneakyghost:
No worries as long as you understand how to flash a hboot...

Thanks for the compliments, i'm not a wizard tho, just don't want bricks happening with my stuff.
[One (M8) Android Development] Behold_this:
Maybe not a wizard, but certainly a guru. There's no denying it. I think the users simply realize the many hours we put into figuring these things out so they don't have to.

Plus...

"friends don't let friends flash drunk...or uninformed" (as the case may be).
[One (M8) Android Development] pjdannie:
Thank you again!

Successfully upgraded to 2.22.401.5 FW

flashed TWRP

and the 2.2 Venom ROM

all I have left is to request that you modify my hboot to remove the red text

I like doing things as well as my limitations allow and eagerly await your instructions.

Thanks again if your modesty will permit..

ok so I have my hboot.img file

using the following adb commands

adb shell

dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img

exit

adb pull /sdcard/hboot.img

this is as about as far as I could confidently go

Well I could hex edit the file but my experience is really running out here and I am likely to not do it properly.

I also am not too sure on how then to package the hboot .img - once modified to a RUU compliant .zip

again your sterling advice here is greatly appreciated.

Pj
[One (M8) Android Development] the_rooter:
I am on Verizon are these steps to be followed for the update
[One (M8) Android Development] digitard:
Nope.

There is no updated Verizon firmware. Unfortunately until September, when they announced they'd update to 4.4.3, you wont have updated firmware for Verizon.
[One (M8) Android Development] Sneakyghost:
Well the "steps" as in procedure are valid for VZW and Sprint as well, just there is no current firmware for VZW.

Also, I'm not providing it because the inability to read constantly leads to people cross flashing and damaging their phones. Just read back a few pages and you'll find confused T-Mobile users that just flash international and vice versa... It's not as bad for them because the problems are minor but it's like you see in various depressing sci-fi movies, vast parts of humanity need to be protected from doing stupid things.

I used to believe that good info suffices to enable judgement in every user but alas! People always go for the download links before informing themselves...

mobile post
[One (M8) Android Development] pjdannie:
Thank you for the Hboot(s)

I have downloaded the stock and modified versions from the pm, greatly respected and appreciated.
[One (M8) Android Development] digitard:
Well, yeah. Like Sneaky said getting the firmware ON the device is the same, but Verizon is different (probably due to the added CDMA support) so you have to wait until they get their firmware out there.
[One (M8) Android Development] RockStar2005:
Hi Sneaky,

I read through your post and understood it as best I could, and then flashed the latest T-Mobile ZIP firmware you have posted (2.22.531.5, Combined) using ADB from my pc. Everything (that really mattered) went just fine for the most part. The only thing is, my OS is still blank in HBOOT even after flashing TWRP and rebooting a few times. It's not a big deal really, but what did I do wrong? Also, the firmware build # showing in "Settings --> About" is 2.22.401.5, not 2.22.531.5, which again is

still fine

as it meets the minimum requirements for the great and powerful ViperOne M8 v2.1.0 (that volume control switch in Misc rocks btw!! thanks!!). I'm just wondering why it was 2.22.531.5.

Please let me know when you have time. I really appreciate all you guys do for us rooted and S-OFF'd M8 owners, and I will continue to spread the word about ViperOne as well!

Thank You,

RockStar2005
[One (M8) Android Development] c5satellite2:
Vzw has been delayed due to a GPS bug, should be available by mid September.
[One (M8) Android Development] dgtiii:
[MENTION=5874212]RockStar2005[/MENTION],

1. No need to quote the entire OP, it's bad form and it's going to piss people off.

2. Did you flash the fixed TWRP version for Sprint that fixes the no show OS bug? Search the TWRP threads, not a firmware or rom issue, it's a TWRP bug.

3. OS version in Settings>About is your rom version, not your firmware version, they are independent of each other mate.
[One (M8) Android Development] n1234d:
I had a corrupted data partition too, remember, I'd asked you to take a look over at my thread? Anyways, that was still earlier than these (I think) and I had wierd artifacts showing up on the screen, so I had it replaced..
[One (M8) Android Development] sgndroid1:
A little confusion. I have an AT&T phone running with T-Mobile service. The phone is s-off, super cid an all. I'm currently running venom 2.2 using the latest AT&T firmware. Everything seems to be working fine, even calls over Wi-Fi. Should I install the new T-Mobile firmware on my AT&T phone while running on T-Mobile service?
[One (M8) Android Development] RockStar2005:
Hey dgtiii,

1) Ok will do!

2) I did read that it was a TWRP thing. I see. No, I flashed my usual TWRP, not the fixed one. I didn't use the Sprint one (because I'm T-Mobile), but I tried flashing back to TWRP via what was supposed to be a fixed TWRP I got elsewhere, but some problems arose, and I had some issues come up with my phone, which I've since fixed by flashing with my usual TWRP.

3) Yeah, that I already knew. Well under "software info", if I tap on "more", I see "Build #" there, and it matches up with the Build # of the firmware zip file I flashed. That's what I was referring to.

Do you have a link to that thread possibly?

Thank You,

RockStar2005
[One (M8) Android Development] agentbardall:
Was having issues

sat for a whole day trying to get this to work in the end i finally figured out what was wrong posting this as i hope it will avoid somone else having to spend a whole day figuring this out.

originally my device was fully unlocked and with S-OFF so i continued too assume this was the case and of course assumption makes and assofuandme. i fully admit the only reason this hadnt worked was......ME....

The guide the files all solid.

If you are having issues go into your bootloader and double check everything turned out my OS version was blank my S-off at some point had become S-on. in the end i had to use sunshine s off and then use the method 3 on a different thread. This problem made it so that firewater(that had originally s-offed my device) also didnt work and generally ****ed up my ability to do what i want with my device
[One (M8) Android Development] Sneakyghost:
In fact, I didn't remember that because I didn't recognize it as being the same. If it was the same, did you try to fix it with a FUU or RUU and did that not work? Because then it wasn't the same.

What could be the same though is that it is the hardware being a bit flakey. A few bad blocks in the chip might be enough to make it unstable. It'll still work and there are solid control mechanisms in all these chips to deal with bad blocks, yet sometimes those fail. Bad blocks happen about as often as dead pixels. I have two M8 in my household, both have dead pixels and likely so, bad blocks.

If you're under the impression everything is running fine, leave as is. Never touch a running system.

If you're like me, you'd think T-Mobile service + T-Mobile firmware = better UX.

Do you not experience excessively long boot times and no boot animation?
[One (M8) Android Development] n1234d:
I think that although the symptoms were the same, the underlying reason wasn't.. It seems more likely that it would've been lots of bad blocks, because of the random artifacts on the screen as well as TWRP rebooting in the middle of a rom install. Could these happen to other users because of a corrupted data partition? And all the symptoms started with a ROM install, I think it was ARHD.. So maybe most of the provisioned extra blocks were bad, and when I flashed it, it killed all of them, and caused all the problems..

I didn't try flashing an fuu zip, just ran to get it replaced within the 14 days :P

[/QUOTE]
[One (M8) Android Development] Sneakyghost:
Oh I see. Well the other three seemed to have it gotten resolved by reformatting the data partition by either the FUU or manual mk4fs method. So you'd have had a chance. Pity you didn't try but I can see how you needed to keep the deadline.

mobile post
[One (M8) Android Development] n1234d:
Yeah, they're not very nice about warranty here., I didn't want to take any chances.. Besides, I've got a much better screen now :D

And the Indian variant, I just discovered is actually the m8_uhl although the bootloader says m8_ul and it works with the International/dev ed/gpe firmwares..
[One (M8) Android Development] Sneakyghost:
Oh good to know! Thanks for the info. Yea i can see the warranty sh!t we do have very bad warranty here as well, HTC is always finding a reason to get out of it, even with my Elevate "premium" support i got virtually NOTHING.
[One (M8) Android Development] RockStar2005:
Hey dgtiii,

I checked around on xda and found this posting under Sprint M8:

http://xdaforums.com/showthread.php?t=2717924

It appears that the TWRP Manager app mentioned there is for all carriers, not just Sprint, so I tried it on mine (I chose m8 since I'm GSM/T-Mobile). All it did was flash the same recovery I already have on my phone now (2.7.1.0-m8), and the OS info in HBOOT is still blank. So I just uninstalled now.

What do you suggest now?

Thank You,

RockStar2005
[One (M8) Android Development] sgndroid1:
It boots just fine. Actually, it even boots faster then before.

Edit: I'm fixing to flash the T-Mobile firmware then. Just to be safe and preventing from my phone getting bricked. Can I install a T-Mobile firmware on an AT&T phone?

I have an AT&T phone running on T-Mobile.
[One (M8) Android Development] blurp76:
Hi, i've tried to look in different guides, but i was unable to find the right procedure to backup my current firmware.

I'd like to a have a copy in case something goes wrong, and maybe to share it here (version 1.54.161.5, VODAP405)

How can i make a backup?

Thanks!
[One (M8) Android Development] donmarkoni:
Have you read and searched? It's in the OP, third post: "Atasks" - Batch Script. ;)
[One (M8) Android Development] blurp76:
Ok sorry, i missed that, so it's option 22, right? I tried to run it but i got an error that adbd couldn't run as root in production build, so i manually dumped all 46 partitions from an adb shell as root.

All good, now i've got the full 46 partitions dump on my pc.

Though, I still can't understand which mmcblk0pXX is which file in firmware.zip. I tried to cross the the google spreadsheet of the partition layout in this thread with another firmware.zip i download and for several files i can't find the corrisponding mmcblk0pXX.

Is there any tool to build the firmware.zip from the mmcblk0pXX files?

Thanks!
[One (M8) Android Development] donmarkoni:
Yep, 22. Glad you did it by yourself. :good:

There is Partition Layout Info in Other Stuff - post #3, with names side by side with partition numbers. Don't get confused, some partitions don't show up in FW's, so no names. ;)
[One (M8) Android Development] Sneakyghost:
You've done very well there with figuring out how to do it manually yourself :D more than most users accomplish...

Err... if you want to offer a RAW backup, which this is, make sure to only offer the partitions which would also be in a RUU. This is because some partititions include device specific info like Serial, IMEI and maybe more i don't know. We do not have any experience available of someone cloning a full raw backup to another device, we don't know if it can be done or if there are security measures in place that prevent the device from functioning if this is done.

After all, cloning a device can be abused for criminal stuff and i am pretty sure, manufacturers try everything to prevent such a move.
[One (M8) Android Development] Sneakyghost:
I've had the very same question in Venomroms-Support the other day and i said i honestly don't know the answer. Fact is, AT&T is more alike T-Mobile US than any other carrier, frequency wise, but we also know people with AT&T service running international firmware seem to cope ok.

Further, we know that the CWS__001 CID does not technically differ from the regular international CID's and also not from the T-Mobile device. This means you can easily run the T-Mobile FullWipe FUU, build up your favorite ROM, then test all radios (LTE, 3G, 2G, BlueTooth, WiFi, GPS, NFC) and see if they always work. You may want to observe the regular usage of the bands throughout a week maybe to see how it performs in signal strengths and band-switching. After that, you could do the same with the international firmware and see if you find any difference in performance and functionality.

I would be appreciative if you'd be willing to run such an extensive test and later share your findings. It will help the ROM support. Not only ViperOne. I think every ROM might profit from people doing such tests.
[One (M8) Android Development] sgndroid1:
Alright, I took the plunge. I did the full wipe firmware. Installed twrp, Venom8, update to 2.2. Every seems working fine so far. WiFi calling is working. Data seems fine so far at home. I'll let you know if I get any improvements on areas I was having problems with.

Thanks again for your help..
[One (M8) Android Development] Sneakyghost:
No worries thanks for being up to some reporting :D

Which one did you pick though? TmoUS or international?