Database Info

[Q] Problems with Viper Rom

Hello,
i'm having a lot of trouble with the viper made rom ( http://forum.xda-developers.com/showthread.php?t=2667758). I'm new here, so i cannot post it there.
My problems began when i try to install the updates. I have installed the original rom version 3.0.0. i get the OTA message, but when i try to install it in recovery, the phone can't mount the sd card, and the installation doesn't continu. I tried to do it manually (using the download link i found in one of the posts) and that seemed to work.
Then i got another OTA notification, to upgrade to version 3.1.0, but when i tried to boot after the installation, i couldn't enter my sim pincode, and when i reboot, the phone keeps looping. I have to install the original rom twice (once with and one time without wiping) before the ROM boots normally.
What am i doing wrong?
i'm on Hboot 1.25 and radio:1.15.50.05.29
I'm S-on (RL)

It seems that viper made a fll rom, with the updates included.

Wrong Hboot?
Martin_Weterholt said:
Hello,
What am i doing wrong?
i'm on Hboot 1.25 and radio:1.15.50.05.29
I'm S-on (RL)
Click to expand...
Click to collapse
I'm not sure but i think it starts with your Hboot, maybe one of the older members can verify, but according to the rom it requires Hboot version 2.15 or 2.16.
I am in the process of updating my Hboot by downloading and flashing the RUU as well as achieving S-OFF status

fidodaj said:
I'm not sure but i think it starts with your Hboot, maybe one of the older members can verify, but according to the rom it requires Hboot version 2.15 or 2.16.
I am in the process of updating my Hboot by downloading and flashing the RUU as well as achieving S-OFF status
Click to expand...
Click to collapse
You need to update hboot first
2.15 is most compatible i suppose

LS.xD said:
You need to update hboot first
2.15 is most compatible i suppose
Click to expand...
Click to collapse
Question. Is there a way for me to upgrade the hboot without the ruu wiping everything? Or will I just have to make a backup. I plan to go s-off before upgrading the hboot.

fidodaj said:
Question. Is there a way for me to upgrade the hboot without the ruu wiping everything? Or will I just have to make a backup. I plan to go s-off before upgrading the hboot.
Click to expand...
Click to collapse
If you're S-OFF ist possible I think

No, you don't need to update the hboot. I am on 1.06 and Viper works fine...in fact any ROM works fine for me but that's another story. The updated firmware (2.13 or 2.15) is required only for Android 4.4.x KitKat due to a check present in the updater-script. There's no such check nor requirement for previous Android versions and Viper 3.x is based on Android 4.2.2
The problems first could come from not being S-Off...this makes impossible to flash the kernel from recovery so any OTA that has a kernel is not flashed properly. I remember that 3.1.0 has also a full ROM ZIP, maybe is good if you flash that one from recovery and flash the kernel after that in fastboot. Also it could matter the recovery you're using, I would recommend latest TWRP
Sent from nowhere over the air..

Rapier said:
No, you don't need to update the hboot. I am on 1.06 and Viper works fine...in fact any ROM works fine for me but that's another story. The updated firmware (2.13 or 2.15) is required only for Android 4.4.x KitKat due to a check present in the updater-script. There's no such check nor requirement for previous Android versions and Viper 3.x is based on Android 4.2.2
..
Click to expand...
Click to collapse
In the viper rom forum post it says ROM firmware required hboot 2.15/2.16.. Am I to j just ignore tha? Or is it that it is only required that hboot (2.15/2.16) if you are s-on and s-off can do whatever you like? Lol

You need hboot 2.16 for Radio 1.20
And to Flash hboot 2.16 you will need S-OFF
Sent from my loved HTC One S using (most time buggy) Tapatalk

LS.xD said:
You need hboot 2.16 for Radio 1.20
And to Flash hboot 2.16 you will need S-OFF
Sent from my loved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
Actually I'm on hboot 2.15 with Radio 1.20.XX
I know this doesn't help... just saying..
To contribute smth. To get the most out of the Viper 3 Rom, everyone should upgrade their Radio to 1.20.XX. And this is actually why you need to S-OFF.

[HELP] How to downgrade hboot

Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person

the_ziom said:
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
Click to expand...
Click to collapse
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !

benJX said:
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
Click to expand...
Click to collapse
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right

the_ziom said:
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
Click to expand...
Click to collapse
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.

I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks

dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!

rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.

dr3amsINdigital said:
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
Click to expand...
Click to collapse
Wise choice, yeah you are right, the bricks were when they were flashing the zips in recovery. Its actually pretty safe in RUU mode but what's the point of risking it.

benJX said:
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
Click to expand...
Click to collapse
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
HELP my device does not see any memory and i cant flash any rom hellpp

the_ziom said:
HELP my device does not see any memory and i cant flash any rom hellpp
Click to expand...
Click to collapse
What hboot are you on now? Did you run an RUU to downgrade?

rosswhite said:
What hboot are you on now? Did you run an RUU to downgrade?
Click to expand...
Click to collapse
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone

the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Which recovery did you flash? Try TWRP 2.7.0.0.

the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Can you boot on stock android rom installed by the ruu ?

rosswhite said:
Which recovery did you flash? Try TWRP 2.7.0.0.
Click to expand...
Click to collapse
i already have twrp 2.7 and i flashed phillz and still nothing

benJX said:
Can you boot on stock android rom installed by the ruu ?
Click to expand...
Click to collapse
yes but i formated my memory to instal a pac man rom

the_ziom said:
yes but i formated my memory to instal a pac man rom
Click to expand...
Click to collapse
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.

####

benJX said:
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
Click to expand...
Click to collapse
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp

So many developers and only 2 can help me
Please I'm begging for help

the_ziom said:
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
Click to expand...
Click to collapse
Flash stock recovery : http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Then Clear Storage from bootloader and flash TWRP recovery

Hboot

Hey guys I've looked around and I just can't seem to find what I'm looking for, does the hboot version matter? I am on 1.14, but the phone is still s-on , I would like to flash 4.4 roms but I wanted to know if I should ruu to the newer hboot and start from there.
Thanks
Sent from my HTC One S using xda app-developers app

Silentwidow said:
Hey guys I've looked around and I just can't seem to find what I'm looking for, does the hboot version matter? I am on 1.14, but the phone is still s-on , I would like to flash 4.4 roms but I wanted to know if I should ruu to the newer hboot and start from there.
Thanks
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Most of roms are usable on 2.15 hboot and lower (which comes with last ruu), so why not give it a try with your actual hboot ?
I would say you to update your hboot but since it wipes sdcard it's quite annoying
What you can do is make a backup and then try the rom you want, if you notice any issue, restore your backup or update through latest ruu.
For some reasons you'll probably need to manually update the radio to 1.20 or 1.35 (I don't recommend this last one since I had random reboots with it), but you need to s-off. I you do, I advise you to use rumrunner.

benJX said:
Most of roms are usable on 2.15 hboot and lower (which comes with last ruu), so why not give it a try with your actual hboot ?
I would say you to update your hboot but since it wipes sdcard it's quite annoying
What you can do is make a backup and then try the rom you want, if you notice any issue, restore your backup or update through latest ruu.
For some reasons you'll probably need to manually update the radio to 1.20 or 1.35 (I don't recommend this last one since I had random reboots with it), but you need to s-off. I you do, I advise you to use rumrunner.
Click to expand...
Click to collapse
If he's on 1.14 he can't flash a KK ROM unless he's not modifying the updater-script in the ROM zip. The check there gives an error if someone tries to flash a KK ROM on a hboot other than 2.13.0000, 2.13.4444 or 2.15.0000

Rapier said:
If he's on 1.14 he can't flash a KK ROM unless he's not modifying the updater-script in the ROM zip. The check there gives an error if someone tries to flash a KK ROM on a hboot other than 2.13.0000, 2.13.4444 or 2.15.0000
Click to expand...
Click to collapse
Yes on Vanir AOSP I had to do this to make it flashable on 2.16 (btw thx for your guide )
Sent from my ElementalXed One S

[Q] Updating to CM 11

Hello
Im trying to update my HTC One S from CM 10.2 to CM 11. (Just install cm and gapps and wipe cache and dalvik).
Unfortunatly I am not able do so, I always end up with an endless bootanimation.
I found no specific information about my problem on the internet, I just heard something about HBoot 2.16.
So my question is do I need Hboot 2.16 to update to CM 11? And is there a way to do so without losing my data?
Thanks in advance.
My current setup:
CM 10.2
Hboot 2.15
TWRP 2.7.0.8
Unlocked but S-On (RL)
Maxanier

maxanier said:
Hello
Im trying to update my HTC One S from CM 10.2 to CM 11. (Just install cm and gapps and wipe cache and dalvik).
Unfortunatly I am not able do so, I always end up with an endless bootanimation.
I found no specific information about my problem on the internet, I just heard something about HBoot 2.16.
So my question is do I need Hboot 2.16 to update to CM 11? And is there a way to do so without losing my data?
Thanks in advance.
My current setup:
CM 10.2
Hboot 2.15
TWRP 2.7.0.8
Unlocked but S-On (RL)
Maxanier
Click to expand...
Click to collapse
Don't you forget to flash the boot.img after flashing the rom ?
Also I'm not sure but I guess it's better to do a full wipe (without internal storage of course) before upadting from a version to another.
Don't care about 2.16 hboot it's only needed for few sense roms. Official CM11 updates are built for 2.15

benJX said:
Don't you forget to flash the boot.img after flashing the rom ?
Also I'm not sure but I guess it's better to do a full wipe (without internal storage of course) before upadting from a version to another.
Don't care about 2.16 hboot it's only needed for few sense roms. Official CM11 updates are built for 2.15
Click to expand...
Click to collapse
Ok, I did not flash the boot.img, did not know I had to to this, I will try it later.
Thanks

Is it possible to flash the Boot Image with the recovery or is the only way by the fastboot command?
My Setup:
CM 11
HBoot 2.15
CWM v6.0.4.8
Unlocked but S-ON

To my knowledge, you need to use fastboot as you are S-ON. If you can, try to get S-OFF, it will be simpler.
Envoyé de mon HTC One S en utilisant Tapatalk

Ok thank you! I already tried S-Off but it doesen't worked. Is S-Off possible with hBoot 2.15?

A7X_2010 said:
Is S-Off possible with hBoot 2.15?
Click to expand...
Click to collapse
Yes, try Rumrunner.

I did S-OFF with rumruner.. Reed carefuly instructions.
http://forum.xda-developers.com/showthread.php?t=2487888
h-boot 2.15 is regular.
You're S-ON. Open rom.zip.
Copy "boot.img" to another folder.
Boot phone in bootloader. Plug cable. "Fastboot USB" will show on screen.
Open comand promt. Type this : "fastboot flash boot boot.img".
Ready.

CM12.1 with hboot2.16 can't install via TWRP need older hboot?

Hi there,
hboot 2.16.0000
rooted, unlocked and S-OFF
TWRP 2.8.7.0
CM 12.1 nightly from 29.07.15
Can't install the CM via TWRP, seems like a problem with hboot 2.16, I think CM12.1 is only running up to hboot 2.15.4444 right?
I searched the whole internet, but can't find a hboot 2.15.0 or 2.15.4444 for my "htc one s "ville" (T-Mobile)"
Could anybody help me?
Thanks!!!!

eurix said:
Hi there,
hboot 2.16.0000
rooted, unlocked and S-OFF
TWRP 2.8.7.0
CM 12.1 nightly from 29.07.15
Can't install the CM via TWRP, seems like a problem with hboot 2.16, I think CM12.1 is only running up to hboot 2.15.4444 right?
I searched the whole internet, but can't find a hboot 2.15.0 or 2.15.4444 for my "htc one s "ville" (T-Mobile)"
Could anybody help me?
Thanks!!!!
Click to expand...
Click to collapse
Did you try to flash the correct version for your phone? There are different links provided for the different hboot versions in the CM thread. The file you need is "cm-12.1-20150729-UNOFFICIAL-ville.zip" and not "cm-12.1-20150729-NIGHTLY-ville.zip". Besides you cannot use the update function of CM on hboot 2.16 since it only downloads the official versions for hboot 2.15.

OK, thanks!
I didn't recognize that there are two different CM downloads...
I flashed back to hboot 2.15 and installed cm12.1 nightly with twrp, SUCCESS!!
Installation on hboot2.15 of CM12.1 with CWM isn't working... dont know why...
But hey, Phone is running.. thanks