Venom User Agreement - PLEASE READ BEFORE DOWNLOAD
This Agreement contains the complete and entire understanding and agreement between you and the providers of this ROM ("Licensor") and supersedes any previous communications, representations, or agreements, verbal or written, related to the subject matter of this Agreement. This Agreement may not be modified or amended orally, impliedly, or in any manner not set forth in writing or permitted by this Agreement.
This Agreement may be amended by Licensor at any time and without notice, but only by amending this document as posted in Team Venom ROM threads or Team Venom ROMs, unless otherwise agreed to in writing by you and Licensor.
READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT CAREFULLY BEFORE ACCESSING OR USING THE CONTENT.
THE OFFICIAL WORK OF TEAM VENOM, INCLUDING VENOM ROMS, TWEAKS, MODS, CODE AND ALL ANCILLARY TEAM VENOM PROVIDED SOFTWARE IS COPYRIGHTED AND LICENSED. IT IS NOT SOLD NOR BOUND BY OPEN SOURCE SHARING OR LICENSING. BY ACCESSING OR USING THIS CONTENT YOU ARE ACCEPTING AND AGREEING TO THE TERMS OF THIS LICENSE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY THE TERMS OF THIS LICENSE AGREEMENT, YOU ARE NOT PERMITTED TO USE OR ACCESS THE CONTENT. THE ONLY EXCEPTION TO THE ABOVE IS IN CASES WHERE TEAM VENOM ROMS ARE DISTRIBUTED WITH A CUSTOM KERNEL, IN WHICH CASE SAID KERNEL IS FULLY GPL COMPLIANT AND FULL KERNEL SOURCE WILL BE PROVIDED VIA PUBLICLY ACCESSIBLE WEBSITE IN AGREEMENT WITH APPLICABLE OPEN SOURCE POLICIES REGARDING DISTRIBUTION OF SOURCE CODE FOR MODIFIED LINUX KERNELS.
Licensor hereby grants to you, and you accept, a nonexclusive, nontransferable license to use the content only as authorized in this License Agreement.
Except as authorized in this Agreement, no copies of this ROM or any portions thereof may be distributed by you or any person under your authority or control. You agree that you will not assign, sublicense, transfer, pledge, sell, lease, rent, lend, or otherwise dispose of the ROM, or any part thereof, or share your rights under this License Agreement, including passwords and user names. You agree that you will not disassemble, decompile, convert to another programming language, or otherwise translate the content, and that you will not rent, lease, or lend the content, or any component of it, in violation of 17 U.S.C. §§ 109(b)(1). You agree that you will not alter, publish, copy, cut, modify or transform the content, or any component of it, in any form to any storage medium, known or unknown, for any purpose whatsoever, except as authorized. You will be held legally responsible for any trademark or copyright infringement that is caused or encouraged by your failure to abide by the terms of this License Agreement.
Licensor reserves the right to deny access to any person or to terminate this license for any reason if Licensor reasonably believes that is not being used for its intended purpose, or for any other reason in the sole discretion of Licensor.
You acknowledge and agree that the ROM content is a proprietary product of Licensor, protected under the copyright law. You further acknowledge and agree that all right, title, and interest in and to the ROM content, including associated intellectual property rights, are and shall remain with Licensor. You agree that only currently serving Team Venom members working on official Team Venom Projects may modify, distribute, or use the ROM and its contents.
THE CONTENT IS LICENSED "AS IS," AND LICENSOR DISCLAIMS ANY AND ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. DOWNLOADING, INSTALLING, AND/OR USE OF THIS ROM DEMONSTRATES COMPLIANCE WITH ALL TERMS OF THIS AGREEMENT. IF YOU DO NOT WISH TO ABIDE BY THE TERMS OF THIS AGREEMENT YOU MUST CEASE USING THIS ROM AND ALL TEAM VENOM APPLICATIONS.
Limitation of Liability
In no event shall Licensor be liable for any indirect, incidental, consequential, special, or exemplary damages or lost profits, even if Licensor has been advised of the possibility of such damages. SOME STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU.
No Guarantee of Correctness - No Legal Advice - No Medical Advice
The ROM has been prepared and/or obtained for general information and entertainment purposes only and is not intended to provide legal, medical, tax, or professional advice. You acknowledge that Licensor, its owners, partners, employees, officers, directors, attorneys, and agents do not promise or guarantee that the ROM is correct, complete, or up-to-date. There is no guarantee that the ROM is correct, complete, or up-to-date for any specific circumstance.
Information Collected Automatically
This ROM automatically collects technical information when you connect to VenomHUB or check for OTA updates. Examples of this type of information include the type of phone operating system you are using as well as your IMEI for phone/user identification purposes and for OTA Update functionality. Information collected for the purposes of utilizing VenomHUB or OTA ROM updates will not be shared and is inaccessible publicly.
You expressly agree that this License Agreement shall be governed by, and construed in accordance with, the laws of jurisdiction in which Licensor resides, to the exclusion of any other applicable body of governing law. This Agreement is entered into in that jurisdiction and not any other jurisdiction.
The following exceptions apply to the above:
In the case of Team Venom Theme Apks, you are permitted to modify, host, and redistribute solely for use in official Team Venom Viper ROMS. You agree that said modified Apks will be properly labeled as Team Venom Theme Apks. Further you agree that under no circumstances will said modified Apks be utilized in any projects that are not explicitly sanctioned by Team Venom, collectively. This includes but is not limited to: Unofficial Beta releases and ‘Kangs’. Team Venom takes no responsibility for issues arising from modification or redistribution of aforementioned Theme Apks.
11. What are the correct sizes for custom carrier logo?
12. How do I update my firmware?
@Red5 has created some very detailed instructions on updating your firmware. While it's not required, I highly recommend upgrading it since it improves the responsiveness of the touch panel and upgrades your radio to a newer version.
I will use this post to keep everyone up to date with the latest themes for Viper One. The Official Theme Thread can be found here, and all questions regarding theming or contributions towards theming can be posted over there.
This post will be a go-to for all user contributions in this thread. I will also try to upload to the HUB when I get a chance, but all links will remain here as well. A lot of the icon packs such as the ones found in this post will also install and work on the One.
SENSE ICON PACKS:
Install apk then select using Venom Tweaks > Sense > Icon Pack
Red themed clocks by @mwr666 Red 4x1 Sense Clocks by mwr666 This zip from one of my other threads is fully compatible with Viper One. You can mix and match clocks and backgrounds however you want. As more themers do mods to the 4x2 weather clock, I will probably combine all into an aroma zip.
Generally speaking, Firmware does not have much to do with the ROM. As such, the ViperOne thread does not need a special section on this subject and i will only be brief with this.
However, at some rare occasions, it does make sense to talk about Firmware in relation to the ROM. I will try to catch some of that to avoid repeat questions.
For those who want to dive right in, you may hop over to my dedicated thread, which also features links to further firmware threads (i am not able to keep that up-to-date at all times, so you might find more current solutions in the other firmware threads).
Is GSM firmware compatible with CDMA (Sprint/Verizon) or vice versa? A:
Please don’t cross-flash firmware! The HTC ONE for CDMA (for example M7_wls / MID PN0720000) has two partitions more than the M7_ul variant and is very different in many aspects. Only this ViperOne ROM can run on GSM and CDMA (currently only Sprint), not so much the firmware. IF you managed to flash GSM firmware to your CDMA HTC ONE, i recommend going HERE and fix.
Do we need to have Firmware version matching ROM version? A:
General answer: NO.
In some situations, an update to your firmware can prove useful nonetheless. When that will be necessary cannot be told up front. A good rule of thump might be to update firmware, whenever there is a change of Android base version, e.g. upgrading from Android 4.4 to Android 4.4.2.
Generally, you will notice the necessity by following the daily postings of users. If you see lots of random errors popping up and people getting angry with each other, the trolls coming out and telling everyone to wipe over and over again, it might be time to start over and reboot to bootloader, update all partitions to the latest version and wipe as good as you can and reflash a virgin copy of ViperOne.
A good example was the update from ViperOne 2.7 (Android 4.2.2) to ViperOne 3.xx (Android 4.3), where a good share of people faced considerable issues with their phones, which could be solved by updating the firmware and wiping the whole chip. Oh and, yeah, updating base enabled people to redeem the free Google Drive Storage offer.
Important information: People who have not yet set their NAND security to OFF might face unexpected and unwelcome obstacles obtaining S-OFF after a firmware update via the official update channel. For the HTC One, the methods Revone, Moonshine are tied to particular firmware versions and an uninformed early update often ruins chances to get the NAND security toggled off. However, Rumrunner and lately Firewater exploits allow to obtain S-OFF on more hboot-versions so far. HTC hasn’t patched those two yet (Current as of February 2014)…
How do i update firmware? A:
S-ON Phones can have this: backup your system in recovery, copy backup to PC, backup your files from SDCard too, then run the latest available RUU (at time of writing that was 3.22 for WWE, 3.24 for T-Mobile) and then update via HTC OTA function, after that, copy your backup back to phone and then restore your NANDROID or else: flash ViperOne clean (recommended). Notice: you might need to lock your bootloader (fastboot oem lock) again to be able to run a RUU. Unlock again after you’re done and reflash the custom recovery as first step.
The fastest way is via Fastboot or “FUU”. Method explained in my thread, link see top of post. S-OFF Phones only.
This method includes a RUU derivate i made, which works like the original RUU but has the system.img removed. It is much smaller this way and easier to download. I like to refer to it as "The FUU" (Firmware Update Utility).
It comes in 2 flavors: 1.) Full Stock WIPE version has everything in it except the system.img and is fit to fully update your M7 from as low as version 1.20 up to the latest. It will wipe the SDCard and leave any ROM in the system partition damaged and non-functional (sometimes it would still boot though, depending on what ROM you currently run). You will need to reflash your custom stuff such as recovery, kernel, splash screen or ROM afterwards. Make sure you backup your SDCard contents before running this. This "FUU" is the most proper way to update your phone. All you do is run it in windows, then flash TWRP (ideally, for ViperOne) and then push the rom.zip via adb push command to the phone's SDCard (while booted to recovery). 2.) Combined No-Wipe FUU without the SDcard repartitioning files and TWRP Recovery already added. It also has the Kernel and Ramdisk files removed and doesn't touch the splash screen either. Theoretically, you may use this to update your firmware from as low as 1.20 up to the latest without having to reflash your ROM or even backup/restore your SDCard contents. I have done this version for those of you who believe it works or simply dont have the time to do the full thing. I am NOT recommending it though. It has given me various troubles in the past.
Then we have the ZIP’s that are also in the FUU as stand-alones for fastboot RUUmode: 3.) Full Stock WIPE RUUmode zip - same as the above FUU version, just the zip, for flashing it manually via Fastboot / RUUmode. For the Linux or Mac OSX fraction or those who just dont need the RUU file bloat. 4.) Combined No-Wipe ZIP - same as the above FUU version, just the zip, for flashing it manually via Fastboot / RUUmode. For the Linux or Mac OSX fraction or those who just dont need the RUU file bloat.
Does it matter if i update firmware before or after flashing ViperOne? A:
Technically, i have repeatedly faced issues if i picked some firmware package that only included vital stuff like hboot, radio, adsp and such and flashed that on a fully set up system.
Symptoms often included the WiFi becoming less functional, less reliable, mobile data issues, Wifi/Data switching getting slow and bad, issues with file access permissions on SD, problems with access to the phone from PC etc. etc.
So i have adopted a policy of always recommending a full wipe and full firmware flash (not just a collection of the most popular partitions) and then flashing ViperOne after that.
Why does my phone show backlight illumination and black screen while charging when powered off? A:
Reason: change in hboot and recovery by HTC. Expected behavior: charging animation like Samsung has while the phone is charging in OFF state. It is now never fully turning off while charging but booting into recovery, charging mode instead. Cause of Black Screen: older custom recoveries not having included HTC's current charging binaries from current stock Recovery. Use TWRP 126.96.36.199 and higher. It will show a charging animation.
Can be run on existing ROM, doesnt wipe, updates everything, hboot is stock, not hex edited. In other words: safe. The example FUU is different than those i do as “full stock” variants, those would wipe. This one doesn’t. To find out more, head over to my thread linked at top of post.
How do i determine my current “Firmware Version”? A:
I believe there is some wrong info circulating the HTC Fora. People keep saying when running fastboot getvar all it will report the Firmware Version in the line “Version-Main”. This is not always true though. Fastboot getvar all or alternatively getvar mainver pulls a version it finds in the MISC partition. Source
So how does that version string get there? It is being taken from the android-info.txt file in any firmware zip that you flashed. The last zip you flashed determines what will be reported by the getvar function. So if you mess around with Firmware.zip’s and RUU’s a lot, chances are, that the version reported there is not equivalent to what you are already running. Often the android-info.txt has version entries not appropriate for the actual zip contents, for compatibility reasons, because it wasn’t done properly or whatever.
The "Firmware" as a concept like we use it on XDA does not exist in HTC's terms. HTC does NOT differentiate between the /System Partition (what we know as "the ROM") and the other 36 partitions. Hence, if you run getvar all or getvar mainver on a stock phone, it will report correctly. It does not go looking for a fictitious place where it would find a separate "Firmware" version. That place it is looking at is the Misc Partition and that’s correct as long as you haven’t messed with lots of different Firmware zips.. So, if you happen to run a hybrid system with a ROM from one base and the other partition images from another base or multiple bases (like hboot from 1.27, radio from 4.06 and ROM from 4.19) the getvar function will report as "Version-Main" what it finds in /misc/, precisely the last zip you flashed determines the string put there.
Example: you flashed a radio with a RUUmode zip from Base 4.19 but the android-info.txt is maybe still an old one because the dude who made the zip, just dropped the new radio into an old existing zip, the getvar function will later report that old version as your mainver.
To check your firmware: boot to bootloader and look at the combination of hboot version and radio version - if you didn't flash those separate, the combination will let you know what base you are on (each OTA and RUU has the radioversion in its name).
Finding out your firmware is a game of guesses and knowing what you did to your device and where you are coming from.
If totally lost, you can still open your hboot with a hex editor and search for the build date line and compare to others, do hash compares with existing partition images on e.g. my thread etc etc blah blah.
Long story short: you better know what you do because finding out your firmware is going to be difficult if you don't.
With a file explorer ( I use root explorer) go to system>customize>ACC and open the default.xml file in text editor, scroll all the way to the bottom and find: <item type="interger" name= "sku_id">6</item>, then change the number (6) according to your carrier.
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?