yashsingh1/xdaforums huggingface dataset:
[HTC One S] Tronar:
Which HBOOT for ViperOneS 2.2.0 and Tampered issue

Hi,

I am done rooting and flashing my HTC One X and installing the latest ViperX 3.5.0. Great ROM BTW.

So I am not an expert but also not a complete noob on these thing.

Now I wanted to do the same for my wife's HTC One S. And I am stumbling from problem to problem. I am reading all kinds of threads for hours without getting any closer to a workable solution. And I am afraid to brick the phone or do something that can't be reversed afterwards.

I wanted to Flash ViperOneS 2.2.0 on it. IT's a phone from O2 Germany, does not seem to be branded (at least not in the boot animation),

but has the CID O2___102.

It came with Android-Version: 4.0.3 and HTC Sense Version: 4.0 (Software-Nummer: 1.53.207.3) and HBOOT shows the following information and version numbers:

VLE PVT SHIP S-ON RL

HBOOT-1.06.0000

RADIO-0.15.31501S.19_2

OpenDSP-v21.1.0.32.0314

I am 98% sure it's an S4 and not an S3, since the TWRP4 worked and the processor is limited to 1500 MHZ.

Now my questions:

1. do I need to upgrade my HBOOT from 1.06 to 2.15 (or something else) as I had to for my HTC One X. There is no warning or a list with requirements in the OP, so that's why I am not sure and googling something like "Requirements for ViperOneS 2.2.0" doesn't yield any usable results.

2. If so, what would be the recommended way to do so? Installing a RUU or doing the S-OFF thing and then flashing just a single HBOOT-file?

Can anybody link me to an O2 Germany original RUU download for upgrading my HBOOT to 2.15 with it?

3. If HBOOT 1.06 should be fine, is there anything else required to flash ViperOneS 2.2.0 except of course having done a successful unlock of the bootloader and having TWRP2.5.0.0 installed (I did both so far)

4. last but not least: unlocking and flashing TWRP 2.5.0.0 resulted in the following text in HBOOT now:

***TAMPERED***

*** UNLOCKED ***

VLE PVT SHIP S-ON RL

and everytime I am booting into recovery I get this legal "developer only" warning in red. I've read that flashing HBOOT 1.14 is supposed to get rid of that problem, but since I have no clue which ROM would work with that HBOOT I didn't dare to do so so far.

Any help is greatly appreciated.

Sorry, if I should ask any redundant questions, but I have only a limited amount of time and after googling and reading for several hours now, I am just tired and frustrated with the whole topic and tons of outdated information of people warning to flash a higher HBOOT, because it can't be reversed or isn't necessary or whatnot but no clear answer to my questions.

A short answer to my questions with a link to a good set of instructions would be more than sufficient and maybe helping other people that just received their HTC One S fresh out of the box.
[HTC One S] rustykwak:
You dont need to upgrade or downgrade hboot 1.06 is fine to be honest S-off is the way to go but you dont need to you just need to fastboot flash the boot.img or you'll just bootloop.

Also if you s-off you can get rid of the tampered & the annoying red warnings!

here's some links

S-OFF

HBoots after S-off to remove warnings

Also it is recommended to only use TWRP upto 2.3.3.0 dont know where you got 2.5.0.0

TWRP Link

Good look its all fairly easy! :)
[HTC One S] nieves53:
Thank by mistake...LOL...the hboot you have is good, you don't need to go to a higher hboot. 1.06 can flash almost anything without problems, is the same hboot I have. I haven't had any problems flashing roms or radios. Therefore if you already have a custom recovery go ahead and flash your rom
[HTC One S] Sneakyghost:
Give it a day or two.

Depends on when you get a feeling for how the ROM is running, it's quirks and little something's.

Let it have a day and a full charge/drain cycle at least and then just observe it. I usually don't flash anything fancy for at least a week so I'm able to better tell issues apart. But then again I'm supposed to take a closer look at things by definition of a tester. So, I'd say a day or two is good.

Sent from Viper 2.2
[HTC One S] psylooooo:
The google map navigation crash is a jellybean bug I think, I've try with bulletproof, elementalX kernel and full wipe + reinstall with stock kernel but same thing... my favorite app doesn't works :(
[HTC One S] Evil-Monkey:
on elemental 3.4 "2D" mode doesn't crash while 3D does almost imediately. I'm guessing 2D and 3D mode are toggled through the red/white compass on the screen while in navigation app. I haven't tested this on any other kernel.

echó en Android
[HTC One S] eterno13:
Eyeballer uptade to 2.5.0.0
[HTC One S] psylooooo:
The app crash on stock, bulletproof and elementalX kernels, I don't tried in 2D mode but I saw on some forums that works, who have the google navigation working ? I think it's the same for all.
[HTC One S] rustykwak:
yep seen he's just updated the OP!
[HTC One S] ryanshew:
No need to wait...I flashed ElementalX right after first boot.

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2

---------- Post added at 08:25 PM ---------- Previous post was at 08:10 PM ----------

Try this .apk...it's the one I use and I don't have any problems. Delete/uninstall your current maps apk first (with titanium backup or a root explorer) and then copy/paste the below apk to /system/app/...set permissions, and reboot.

https://docs.google.com/file/d/0ByXzavK4pmfhNndyT2tmTm5RU1k/edit?usp=drive_web

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
[HTC One S] psylooooo:
I just send you a request, can't acces your file without your permission :p
[HTC One S] sebi112:
Any plans on fixing the autobacklight ?
[HTC One S] Sneakyghost:
So you still didn't get the message then? I think it is the last time i am saying this now.

Its broken files left over from other installs somewhere on the chip with a high probability.

The suggested fixing-attempt is running the JB RUU and afterwards do "Clear Storage" from within Fastboot mode.

Kernel Changes are not expected to help.
[HTC One S] ryanshew:
Try this...I didn't know that about Google drive, that's stupid...

http://db.tt/1qX1mYmP

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
[HTC One S] Tronar:
Well, I got the TWRP 2.5.0.0 from the official site. The same link you just posted. ;) They just upgraded to 2.5.0.0 two days ago, so that's maybe why you didn't know. But 2.4.x.x has been released in January. Any reason why you still suggest using the old 2.3.3.0 instead of a newer one? Are they buggy or anything? :confused:

But anyhow, thank you very much for confirming that staying on HBOOT 1.06 is no problem for ViperOneS 2.2.0. I was just puzzled because for the HTC One X the newest HBOOT was a crucial requirement to get the latest ViperX ROM running. So I thought the same logic would apply to the HTC One S.

Is there any advantage in upgrading the HBOOT to 1.14 or 2.15 (except for getting rid of the warnings)? Or disadvantage?

And why would you still recommend going S-OFF if the bootloader is already unlocked. As far as I understand, it would only potentially save you the separate flashing of the BOOT.IMG. I don't mind doing that extra step. I am not sure if saving that little effort justifies jumping through all the hoops to get S-OFF.

I am going to flash the ViperOneS 2.2.0 now first thing and then start reading through your links. Thanks again!

P.S.: do you maybe have a link to the latest or most recommended radio to use with ViperOneS 2.2.0 ? I don't want anything fancy, just reliable WiFi and Mobile Data access.

P.P.S. I read through the links you posted above. I had already found those, but were afraid to do so because of all the brick warnings unless it is absolutely necessary. Is there any other way to get to HBOOT 1.14 without going for the Super CID and S-OFF?

Also the instructions in the thread "Facepalm S-Off for the HTC One S" are talking about flashing some OTA firmware and the following requirement:

------------------

2.) Download zip that matches your model id and move it in your working directory (do not unzip it!):

OneS PJ4010000-OneS.zip

------------------

I am not sure if I can use that zip or not for my German O2 CID phone and where to look to know if it matches my model id (whatever "model id" means in that context. Are we talking about "One S vs. One X" or "S4 vs. S3" or "S4 unbranded vs. S4 O2"???)

And I am not crazy enough to start a process potentially bricking my phone without being 100% sure that I have the right files ready and that post is unfortunately not helping at all in that regard. :)
[HTC One S] vovanius:
Well, issue number ONE from post #4832 solved :) Flashed radio 1.13 and now i have 2% battery drain overnight in airplane mode (was 1%/hour), and overall battery life gets better. Issue number (2) not solved though, will try to mess with kernels.
[HTC One S] ryanshew:
Do not upgrade your hboot if you are not going to s-off. You can flash the boot.img in recovery on your hboota well as radios, the higher ones cannot. The only thing the higher hboots will give you is more restrictions.

PS there is a lot more to s-off than what you mentioned. Higher hboots will not get rid of the red warning you want to get rid of...you only can get rid of that with s-off, them flashing a modified hboot.

That file your asking about is the right one for your phone...there only is one file. You have to change your cid to super cid for s-off.

And yes, the higher twrp cannot flash viper for some and are buggy in other ways as well.

By the way, you are making things way more complicated than they need to be.

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
[HTC One S] rustykwak:
Yep I noticed an update to 2.5.0.0 after I posted although there has not been any feedback on the thread regarding this new version, The reason I recommended 2.3.3.0 is that later versions caused problems flashing roms & a few other issues, Personly I would stick with 2.3.3.0 until its been tested by many or you may suffer issues & extra work to correct wasting your own time!

If your happy to boot.img flash each time great but if you want to remove the red warnings then at the moment the only way is with the modified Hboots which can only be used once you have S-Off, which you need to read the instructions at least twice to make sure you understand them but it is real easy if you follow the instructions by the letter, The Brick warnings are always there to prewarn you there also on most roms and other dev stuff dont be put off just read all the guides thoroughly & you wont have a problem!

Radios are pretty much each users own preference you need to just try some & find what works best for you! Tecardo Radios

Also when flashing viper read & follow the instructions well to save you time & effort :)
[HTC One S] PeQuEsan:
Should we, ViperOneS users, receive the Google Play update (4.0)?
[HTC One S] knevelsg-j:
There's a thread where you can download it in the themes and apps section.

Here's the link: http://xdaforums.com/showthread.php?t=2227989
[HTC One S] Wouter06:
Sure, Google Play is an app like any other. It will update itself when time comes..

Unless it's bound to an Android version to get it. But until now I haven't heard that.

So just wait ;)
[HTC One S] Tronar:
Yeah, I just learned that the hard way. I tried to install ViperOneS 2.1.0 with TWRP 2.5.0.0 and the installation screen already had a weird blueish taint. I just thought WTH and continued but then it finished way to fast. It seemed to stop right after wiping the partitions. The error log showed that it couldn't find an installer file within the ROM.zip. So I tried first to install the older ViperOneS 1.2.1 with the same result. So I remembered your warning, flashed TWRP 2.3.3.0 and voila the ViperOneS 2.1.0 installed without any problems!

I can only warn everybody else to use anything higher than TWRP 2.3.3.0 for now. Unless you want to waste your time or somebody has confirmed that 2.5.0.1 or higher do not suffer from the same problems any more. But 2.5.0.0 is definitely buggy as hell or at least not compatible with the Viper-Roms.

Ok. I just thought why bother with Super-CIDs und S-OFF if flashing the right RUU would upgrade my HBOOT and Radio anyways.

I guess having the *** TEMPERED *** warning in the bootloader is just a cosmetic issue, right?

As well as the red legal warning during the HTC Boot Loading screen. Then I will just tell my wife to ignore it.

I just wanted to take the opportunity to get rid of all that mess BEFORE I am going through the cumbersome process of transfering all the contacts, calendar entries whatsapp messages, shazam tags, dictionaries, images, ringtones and whatnot from her old phone, because usually those procedures kill all the user data on the phone.

That's what I was doing for my One X and am doing for the last two days for the One S. I was so naive to think that after having gone through the learning curve for the One X the One S would be a lot quicker. Now I know better... :silly:

But still a lot better than wasting hourse looking for some stupid force close issues, because of an unwiped cache. :cool:
[HTC One S] Sneakyghost:
Went through TWRP 2.5.0.0 now.

Old themes partially working but hiding and changing new options.

Restoring older Backups without issues.

NOT installing Viper.

ColorShift with Aroma (of course) still present (probably needs alterations from Amarullz in Aroma, not TWRP)

Wipes not thoroughly tested but the routines run through without issues.

To sum it up: It still isn't usable for Viper users probably. I doubt that i am the only one facing these issues.
[HTC One S] Zer0r:
Forget it. I don't think this ROM will update. All the developers are on other phones now. So am I - bought Droid DNA and happy about it!
[HTC One S] torxx:
This is not true

Sent from my HTC One X
[HTC One S] mmhs:
Today i had an really strange crash...

after using 2.2 with elemental x @ vanille and stock cpu for a while without any problems my phone went very hot today and i saw an hard to see htc logo. could not do anything else then push down and power for 10 seconds.

After that my phone did not reboot anymore, stuck at the HTC logo.

I'm lucky i've got an nandroid backup from couple of weeks ago and my phone works again but i'm really curious what caused this??
[HTC One S] Tronar:
Ok, thanks. I will stay with HBOOT 1.06 then for now. It's just that setting up your system, getting your apps re-installed and your contacts re-synced is such a time-consuming process, that I don't want to do all that only to find out that for some reason I have to go through a procedure that wipes the whole user content again.

Yeah, I guess I will just leave it like it as for now, unless the tempered flag or the error message are more than just a cosmetic issue.

Well great. So why does he then put a phrase like "Download zip that matches your model id" into his instructions???

That's only creating more confusion!

Yeah, just found out the hard way and flashed back to good old 2.3.3.0

Funny way of putting it. I'd like to have a smooth and easy process as well.

But this organically grown assembly of helpful information, important information, outdated information and opinions from half-wits distributed over several threads each with at least hundreds of pages isn't really making things easy. Especially not if you never know if the set of instructions you just discovered is still valid or already outdated, but nonetheless always filled with warnings like "Only do this if you REALLY know what you're doing" or "We already got a brick. Be careful" etc.

And to make things worse, after flashing TWRP the HTC One S was showing warnings like *** TEMPERED *** in the bootloader and a red warning text during every boot that I've never ever seen before on my HTC One X. That makes you a little nervous, if you only find threads on how to get rid of it but not, what it actually does and means and if it has any consequences to just leave it alone.

Any time I have to root a new type of phone it's a three day odyssey through all the information. The only thing you can really recycle is how to install and use the ADB drivers, but beyond that every phone seems to be different enough to confront you with more than one new issue. Plus sometimes having experience with another phone isn't always helpful. For the One X you have to upgrade your HBOOT. How am I supposed to know that for the One S it's NOT required??? Adding a "what's required / not required" section on the first page next the installation instructions might help, but I don't want to start another Meta-Discussion.

Nonetheless, thank you for your help and thanks to the Viper Team for the great ROM.
[HTC One S] PeQuEsan:
Anyone else is having problems to sync desktop chrome bookmarks (error syncing) with your android account (for stock browser, not Android Chrome)? Or is it Titanium Backup account restore option that has messed something up?

Any way to "reinit" accounts?. I've tried just erasing and configuring it again... No joy. And I would prefer not to have to start over again... :(

Thanks a lot.
[HTC One S] k1llacanon:
Torxx don't you have your one yet? Because you stoll send messages from your one x
[HTC One S] Rampage:
Is it a problem for you if he has more than 1 phone?

Gesendet von meinem HTC One S mit Tapatalk 2
[HTC One S] ahsm:
Is there going to be a 4.2 version of Viper?
[HTC One S] Rampage:
No, because there is no official sense with android 4.2 by HTC.

Gesendet von meinem HTC One S mit Tapatalk 2
[HTC One S] psylooooo:
Thanks I'll try that :good:

---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------

I'll try to flash a RUU to see if that's the problem :p
[HTC One S] IntelligentAj:
I seriously must be the only one not experiencing any problems with TWRP 2.4.4.0. I've flashed every ROM with that and I've had no problems whatsoever, Aside from the Wi-Fi not working but I know I can't change that till I S-off and install a new radio(1.14 HBOOT). My flashlight also seems incapable of turning off once I turn it on, does anyone else have this problem?
[HTC One S] k1llacanon:
No problem it's a question, and I wasn't even directing the message at you so don't reply next time thank you
[HTC One S] Evil-Monkey:
You should try latest CWM by Blackwing, works great.

echó en Android
[HTC One S] luddeblaesild:
It because you accidentally press the home button on the lockscreen, go into venom tweaks and disable the option to start flashlight on home long press on lockscreen tab.

Sent from my One S
[HTC One S] IntelligentAj:
I thought I wiped my presets but maybe not

And TWRP 2.4.4 works excellently for me in every respect. I changed from CWM but I like TWRP much better?
[HTC One S] blackcell1:
unable to reactivate google sync. does anyone know a method to fix this bug or does it need to be patched ?
[HTC One S] Sneakyghost:
Unfortunately, I have to agree on nearly every aspect of your post.

Unfortunately too though, most people have had to learn that this is the way things are in the custom ROM world.

I once looked after a thread from a HD2 Dev and did all this information aggregating and instruction-fast-food so people can have an easier experience. I kept that thread company for over a year.

That thread had three times as many posts at the end and not an inch less confusion. Now, one could argue that that was due to me not writing good guides. I even believed that for a while and asked for support in those endless, time consuming hours of designing instructions. Not ONE person came to help.

By now I know my guides where good.

The problem we see here we also had there. People weren't reading or not understanding for various reasons.

The lesson I learned was simple: it's not worth the effort.

Still, I offered to take on a guide section for this ROM and to maintain it. People said it's not needed because we have a search function here. By now I fully understood why. These guides you ask for are immensely time consuming because I, we would have to do all the research. If there was the slightest sign of it being helpful, no doubt me or someone else would do it. But every page you find posts that prove these guides worthless.

People have given up on this. It is much easier to learn like I, we, all of us had to: using the search and getting to know the device the hard way.

And yes, every device is very, very different even though in theory, it wouldn't need to be.

I'm sorry you have to go through so much pain.

Sent from Viper 2.2

---------- Post added at 08:27 PM ---------- Previous post was at 08:20 PM ----------

U talking about that sync circle in sync settings always indicating an error? If so, I can tell you that my phone has that too but things are syncing correct nonetheless. I suspect that being a problem on the side of the Google servers.

Sent from Viper 2.2

---------- Post added at 08:33 PM ---------- Previous post was at 08:27 PM ----------

Mate, you might be the only one having set up your phone right so far. I discussed that flashing problem with Torxx and Dees_Troy from Team Win today and it turns out there's a good chance we can't flash on newer TWRP because of a required SD wipe which I always recommend but didn't do myself. As soon as I find time I will further investigate this. My problem as of now is, that my phone refuses to accept the 3.16 RUU and I can't follow my own recommendations. Also, my time is quite limited.

But the fact you can use the newer TWRP indicates that it might be something I and some others are doing wrong.

Tecardo also confirmed a successful flash on the newest TWRP.

So definitely something I will try to hunt down with the help of some guys once I find time.

Thanks for pointing out that it works for you.

Sent from Viper 2.2
[HTC One S] Sneakyghost:
So why do you think Torxx would even consider to reply to your smart questions.

You already told everyone on thread I didn't like you so I can be straight with you as you'd probably expect me to be anyway.

The thing is you don't need to attempt to make good conversation or smalltalk here anymore especially since you where so kind to let everyone know that you found out how to cheat on the donate thing. I dare say I'm by far not the only one having negative feelings towards your comments lately.

I'd advise you to strictly stick to a rather passive forum participation around here.

Sent from Viper 2.2
[HTC One S] he_stheone64:
AW: [ROM][S4][18 JAN] Team Venom presents: ViperOneS 2.0.0 | Sense 4.+ | 4.1.1 | Twea

We will work on that soon, don't forget that this is initial release. Next thousand tweaks are in the oven :D

Sent from my HTC One S
[HTC One S] Phantom Pt. II:
Re: [ROM][S4][18 JAN] Team Venom presents: ViperOneS 2.0.0 | Sense 4.+ | 4.1.1 | Twea

Could you guys have a look at expanding the maximum allowed of Apps in a folder on the home screen?

It's limited to 16 Apps. All my games don't fit in one folder.

<3

And didn't the header have a big text with the date next to it?

Only shows me the small day and date now
[HTC One S] he_stheone64:
AW: [ROM][S4][18 JAN] Team Venom presents: ViperOneS 2.0.0 | Sense 4.+ | 4.1.1 | Twea

God, that's really slow. So sorry :D

Sent from my HTC One S
[HTC One S] Co5min:
I`m not pushing or anything just thought I wasn`t able to find those tweaks myself. I`m very patient... You guys are amazing.
[HTC One S] he_stheone64:
AW: [ROM][S4][18 JAN] Team Venom presents: ViperOneS 2.0.0 | Sense 4.+ | 4.1.1 | Twea

I will check, once we finished adding current to dos (which is already a long list of adding new stuff).

Sent from my HTC One S
[HTC One S] torxx:
AW: [ROM][S4][18 JAN] Team Venom presents: ViperOneS 2.0.0 | Sense 4.+ | 4.1.1 | Twea

And the fact that HTC removed this mod from every JB device, the mod needs to be rewritten by m0narx

Sent from my HTC One X