Database Info

[Q] I need help please, completly lost....

Hi,
i've got a htc desire S and surprise, surprise i've run into another problem (most probably caused by me right now phone is in a state of "zombification" (freezes at boot screen, boots to hboot screen but loops back to hboot screen when choosing recovery or factory wipe)
I was running edymion v3.5 base release, with pdroid. but i noticed apps kept crashing/ force closing (facebook, default mail, youtube etc) bypassed most of these by reinstalling them or finding alternatives. few weeks later loads of the app started crashing, especially the camera (cashing limited to default and background apps). I decided that a reinstallation of endymion MIGHT fix this so i factory wiped using clockworkmod recovery and reflashed endymion + pdroid.
Alas, it froze on the HTC boot screen. this had happened before when i tried rooting and all..... so i did what i did before...http://forum.xda-developers.com/showthread.php?t=1728513
which failed cause the update kept stopping midway, so i pulled battery, and repeated a few times, tried using a RUU and a OTA
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
and
OTA_Saga_S_HTC_Europe_2.10.401.8-2.10.401.5_release_225212pe4gpljm46wwfk8i
these failed as well, either stopped halfway or completed then freeze on HTC boot screen.
Phone is s-off from revolutionary, no clockworkmod now (thanks to multiple wipes) and i dont think it is rooted anymore....
here is data that may help
fastboot screen
-revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 4057mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Mar 10 2011, 14:58:38
please advice....
P.S. sry this was so lengthy, thought more details would help fix it quicker

is your device still recognized by adb? if YES then this should enable you flash a recovery through fastboot.
exert from 4ext touch thread which is what I'd recommend that you use.
Code:
There's a [URL="http://www.4ext.net/ddl/saga/recovery.zip"]direct download[/URL] for a version you can flash via fastboot.
Download this file
Unzip it
check md5sum of the included image file
attach device through USB to PC
flash through fastboot
Code:
fastboot flash recovery recovery.img
I'd then suggest a full wipe and attempt to include a custom ROM

ben_pyett said:
is your device still recognized by adb? if YES then this should enable you flash a recovery through fastboot.
exert from 4ext touch thread which is what I'd recommend that you use.
Code:
There's a [URL="http://www.4ext.net/ddl/saga/recovery.zip"]direct download[/URL] for a version you can flash via fastboot.
Download this file
Unzip it
check md5sum of the included image file
attach device through USB to PC
flash through fastboot
Code:
fastboot flash recovery recovery.img
I'd then suggest a full wipe and attempt to include a custom ROM
Click to expand...
Click to collapse
Thanks for replying, i was begining to lose hope
unfortunately it does not register with adb since it won't switch on. But it DOES register with fastboot, so i'm trying it right not. So far it has stopped moving at
c:\Users\ME\Desktop\adroid>fastboot flash recovery recovery.img
sending 'recovery' (6038 KB)...
OKAY [ 1.021s]
writing 'recovery'...
But i'll give it some time before trying again, will report back soon
update:
Soo, waited a while, then tried flashing again. stopped at the exact same spot (writing 'recovery')

If you manage to flash a recovery, search for guide to change your misc version. Then search for a guide to change your bootloader. There is one in my signature. Finally download a T-Mobile RUU since your phone is branded. Do not flash any other versions
Sent from my HTC Desire S using xda app-developers app

amidabuddha said:
If you manage to flash a recovery, search for guide to change your misc version. Then search for a guide to change your bootloader. There is one in my signature. Finally download a T-Mobile RUU since your phone is branded. Do not flash any other versions
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
thanks, can't seem to flash recovery though, stops and just stays at "writing recovery"

Getting stuck when trying to write one of the partitions is bad news.

Jack_R1 said:
Getting stuck when trying to write one of the partitions is bad news.
Click to expand...
Click to collapse
lol yea, i've pretty much given up. trying to find some one who can fix it, buti guess i'll have to wait to get a new phone

In which case, you surely have nothing to loose sending the dead device in for warranty fix, best leave the battery out.
Sywepd form my DsereiS

htc one s boots to logo then turns off - need to recover data

Hi, was advised to post here instead as my phone is in fact the HTC One S Model PJ40110.
The issue with the phone is that upon pressing the power button, the phone vibrates, the HTC logo comes on and after about 20 seconds just shuts off. I need to recover some data first, the data from the internal memory not the sd card.
The phone is S-ON
I can get into the hboot menus but not sure on how to proceed to be able to recover the data.
Fixing this for a friend, i dont believe she is capable of rooting.. etc not sure how the phone ended up this way.
Appreciate your guidance

Not sure why you want "the data from the internal memory not the sd card"
You could unlock the bootloader and flash a custom recovery and mount usb storage to copy the pictures and media.
For S4 version of HtC One S
http://forum.xda-developers.com/showthread.php?t=1583427
After that you can run a RUU.exe to return to stock.
You will have to relock the bootloader
fastboot oem lock
Run the RUU when the phone is in bootloader.
http://www.androidruu.com/index.php?developer=Ville

Hi and thanks for the reply.
Basically I want to recover the contacts and any other personal data that was not on the sd card.
Will it be possible with this method or will it just bring the phone to life but wipe the data?

exclusivebiz said:
Hi and thanks for the reply.
Basically I want to recover the contacts and any other personal data that was not on the sd card.
Will it be possible with this method or will it just bring the phone to life but wipe the data?
Click to expand...
Click to collapse
Yes, you are right. When you unlock the bootloader and press "yes" I believe it wipes your phone. Sorry, wasn't thinking about that.
Sorry, couldn't help. There may be some adb commands, to pull the data, but I don't know them.
Contacts would be saved via google though. So not to worry about that.

Is it possible to boot into recovery? Then you could use adb.

I could boot into hboot. Are you referring to that as recovery mode? would you have any steps on using adb for recovering data?
Im not well versed yet with the backend of the android platform.

Some more details on the phone
*** locked ***
vle pvt ship s-on rl
hboot-2.15.0000
radio-1.11.50.05.28
opendsp-v31.1.0.45.0815
emmc-boot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.631.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **
(bootloader) imei: **
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: **
(bootloader) battery-status: good
(bootloader) battery-voltage: 4083mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Ive been reading some more on fastboot and tried to give it a go with a clockwork recovery img and "fastboot boot" command.
I get the following
downloading 'boot.img'...
OKAY [ 1.070s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.073s
Is this because S-On? Anyway around it?
What can adb do in regards to recovering data?
Thanks for your help thus far guys.

exclusivebiz said:
I could boot into hboot. Are you referring to that as recovery mode? would you have any steps on using adb for recovering data?
Im not well versed yet with the backend of the android platform.
Click to expand...
Click to collapse
In hboot click on recovery.
With "adb shell" you should have access to the phone. With "adb pull <filename>" you can transfer files to your pc.
Don't know about contacts.
---------- Post added at 07:48 AM ---------- Previous post was at 07:44 AM ----------
exclusivebiz said:
*** locked ***
vle pvt ship s-on rl
...
Ive been reading some more on fastboot and tried to give it a go with a clockwork recovery img and "fastboot boot" command.
I get the following
downloading 'boot.img'...
OKAY [ 1.070s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.073s
Is this because S-On? Anyway around it?
Click to expand...
Click to collapse
This is because the bootloader is locked. You could unlock it at http://www.htcdev.com/ but don't do that. It will erase the phone.

hi, thanks for the reply, i will work on setting this up.
question - how do i know the files names, is there a directory/file listing command so i see everything available that i can "pull"?

hi, so i got into hboot menu then clicked on recovery, waited for the red triangle and finally pressed volume up and power to pull up another menu consisting of the following:
Android system recovery ,3e.
...
reboot system now
apply from sd card
apply from phone storage
apply from cache
wipe data/factory
wipe cache partition
I understand this is the recovery section but when i connect my phone to the computer and run adb devices it shows blank. When i ran adb - s [serial number] shell i get error:device not found.
I did it a few times and one time i got
adb -s [serial] shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
How do i get it to find the device?
Running Win 7 64 bit here

I just broke the whole phone..

Hello! Before you guys flame me with messages of how much dumb I am or anything similar - don't bother, i already know it and i regret it...
So... I have AT&T HTC One X, with Hboot 2.14, CID CWS__01 which i just destroyed as much as i could >.> Let me reproduce things i've tried..
First of i changed my CID to 11111111 and unlocked the bootloader - took me an hour, but i did it and it was working...
I've installed recovery, even rooted the ROM... But that wasn't enough - i wanted to install ParanoidAndroid ( and i didn't read that it needs S-OFF, realized that just after i installed it and rebooted the phone )..
So after a reboot, the white HTC logo it just went black screen and nothing else... So i've began to look up on forums if someone else had this kind of a problem...
Then i tried another 2 ROM's, which worked as well as PA - just black screen...
So i thought - maybe i'll do everything from scratch ? Why not, I changed CID back to stock, wiped everything etc. and locked the bootloader....
But now I've got a weird problem - i can't change CID with "fastboot oem writecid" - it returned me error
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.282s
Click to expand...
Click to collapse
So now i have no access to recovery, so i can't even do anything to the storage, the phone doesn't boot up, tried RUU for ATT version ( RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105 - i guess its for HBoot 1.44, not 2.14 >.> ) it just showed me an error that it couldn't send data to the phone and i should check my connection to the phone ( drivers are installed and working fine )
I've also tried fastbooting the OTA zip to the phone - well, the phone is on S-ON and it just declines any zip that i try to flash
Also i lost connection to ADB - its impossible to connect to it while phone is in bootloader, right? : /
So i'm left with empty phone without any rom, recovery - anything...
Is there any way of fixing it ? Its 5th hour where i just sit and try to look up for any information, but I just can't find anything...
I guess i just hard bricked the phone and i can try to play some volleyball with it >.>

Your mistake was thinking that you needed s-off to flash the ROM(s), you don't, all you needed to do was flash the boot.img via fastboot after flashing the ROM with your recovery. There's an Evita FAQ thread which contains this information stickied at the top of the q&a section you've posted this thread in . This is in no way intended to flame you, just show you the catalyst point for this mayhem.
Anyway, what is your current CID? Check it with this command:
Code:
fastboot oem readcid
You must be connected in fastboot mode (bootloader) in order for fastboot commands to work (and in answer to your question, no, adb does not work in fastboot mode, only in Android and in recovery).
Transmitted via Bacon

thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT28GW304238
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3403mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
Click to expand...
Click to collapse
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )

prechcik said:
thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )
Click to expand...
Click to collapse
Glad to see you're all working now. But you need to edit your IMEI out of your post asap, never post your IMEI publicly.
Transmitted via Bacon

[Q] lot's of problems

Hi, not sure this is the correct place to ask but i have a sensation that is stuck in a boot loop( brought from EBay) and i wish to return it to stock, hboot is 1.27.0000 image is 3.32.161.11, radio 11.23.3504.07_m2, bootloader unlocked via HTCDev but S-ON and i cannot find a ruu or image to return to stock, (unable to boot into recovery phone just loop's) all the ruu's I've found i receive signature fail error, I've also tried several post's in the fourm that tell me how to flash a custom rom while being s-on but nothing seem's to work, again signature fail error I've also flashed several recovery images via fastboot all completed ok but ether bootloop or freeze my phone, being newish to flashing rom's ect am I doing something wrong?
Any help would be appreciated.

theconverter said:
Hi, not sure this is the correct place to ask but i have a sensation that is stuck in a boot loop( brought from EBay) and i wish to return it to stock, hboot is 1.27.0000 image is 3.32.161.11, radio 11.23.3504.07_m2, bootloader unlocked via HTCDev but S-ON and i cannot find a ruu or image to return to stock, (unable to boot into recovery phone just loop's) all the ruu's I've found i receive signature fail error, I've also tried several post's in the fourm that tell me how to flash a custom rom while being s-on but nothing seem's to work, again signature fail error I've also flashed several recovery images via fastboot all completed ok but ether bootloop or freeze my phone, being newish to flashing rom's ect am I doing something wrong?
Any help would be appreciated.
Click to expand...
Click to collapse
did you try this ruu?
RUU_Pyramid_ICS_Vodafone_UK_3.32.161.11_R_Radio_11.69A.3504.00U_11.23.3504.07
i can't find a working link right now

rzr86 said:
did you try this ruu?
RUU_Pyramid_ICS_Vodafone_UK_3.32.161.11_R_Radio_11.69A.3504.00U_11.23.3504.07
i can't find a working link right now
Click to expand...
Click to collapse
Hi,Yep tried that one still getting signed error.
Thanks for looking

You have to get an RUU according to your CID.Get into your bootloader (by pressing power + vol-) and when you see fastboot usb give the command fastboot getvar all.Then copy-paste everything here except your imei and serialno so we will be able to help you further. If you cannot find an RUU for your CID you have to S-OFF your device so you be able to change your cid. After that you can flash any RUU.
You probably have bootloop issues with custom roms because you are S-ON user and you have to flash mannually the kernel.Just extract the boot.img from the rom zip you flash from your recovery in the folder you have fastboot and then flash it from your bootloader by using the command fastboot flash boot boot.img.Then your custom Rom should be working. After that you can S-OFF your bootloader with runrummer or with juopunutbear as long as you have already unlocked your phone with HTC_dev.
** Also after S-OFF it would be nice to upgrade your radio to the latest. **

lot's of problems
Gatosbil said:
You have to get an RUU according to your CID.Get into your bootloader (by pressing power + vol-) and when you see fastboot usb give the command fastboot getvar all.Then copy-paste everything here except your imei and serialno so we will be able to help you further. If you cannot find an RUU for your CID you have to S-OFF your device so you be able to change your cid. After that you can flash any RUU.
You probably have bootloop issues with custom roms because you are S-ON user and you have to flash mannually the kernel.Just extract the boot.img from the rom zip you flash from your recovery in the folder you have fastboot and then flash it from your bootloader by using the command fastboot flash boot boot.img.Then your custom Rom should be working. After that you can S-OFF your bootloader with runrummer or with juopunutbear as long as you have already unlocked your phone with HTC_dev.
** Also after S-OFF it would be nice to upgrade your radio to the latest. **
Click to expand...
Click to collapse
Hi Gatosbil, info below many thanks for you help
rm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.161.11
(bootloader) serialno: ****************
(bootloader) imei: ****************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.568s

theconverter said:
Hi Gatosbil, info below many thanks for you help
rm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.161.11
(bootloader) serialno: ****************
(bootloader) imei: ****************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.568s
Click to expand...
Click to collapse
the only ruu you can use since you are on S-ON is the one i told you in my previous post
otherwise install 4ext recovery
enbale smartflash from 4ext
flash a custom rom
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command

rzr86 said:
the only ruu you can use since you are on S-ON is the one i told you in my previous post
otherwise install 4ext recovery
enbale smartflash from 4ext
flash a custom rom
here is the latest version of 4ext
extract the recovery.img and flash it via fastboot command
Click to expand...
Click to collapse
Thank you for your reply, I have run the ruu that you suggested in your first post but i'm still in a boot loop and being a ruu I do not know how to extract the boot image to flash it ( as this has stopped the boot loop problems in my previous phone). is there a boot.img available?
When i click on the link for 4ext you posted I cannot find the download link also can i flash 4ext being s-on
Looking forward to your reply.
Had to remove the outside link being a new member cant post outside link with less than 10 posts

theconverter said:
Thank you for your reply, I have run the ruu that you suggested in your first post but i'm still in a boot loop and being a ruu I do not know how to extract the boot image to flash it ( as this has stopped the boot loop problems in my previous phone). is there a boot.img available?
When i click on the link for 4ext you posted I cannot find the download link also can i flash 4ext being s-on
Looking forward to your reply.
Had to remove the outside link being a new member cant post outside link with less than 10 posts
Click to expand...
Click to collapse
in the ruu thread there is somewhere how to flash ruu manually
maybe from there you can locate the boot.img
about the recovery link i think you have to sign in in 4shared site
and yes you can flash 4ext while on S-ON as long as the bootloader is unlocked

rzr86 said:
in the ruu thread there is somewhere how to flash ruu manually
maybe from there you can locate the boot.img
about the recovery link i think you have to sign in in 4shared site
and yes you can flash 4ext while on S-ON as long as the bootloader is unlocked
Click to expand...
Click to collapse
I think ill give up with this phone, i have flashed 4ext via fastboot and still wont boot into recovery ( just loops)
also installed from sd card update ect ect still loops, could this be a hardware fault with the phone?

theconverter said:
I think ill give up with this phone, i have flashed 4ext via fastboot and still wont boot into recovery ( just loops)
also installed from sd card update ect ect still loops, could this be a hardware fault with the phone?
Click to expand...
Click to collapse
i really don't know mate

rzr86 said:
i really don't know mate
Click to expand...
Click to collapse
Hi, just a update ive fixed my phone, :laugh: done so by making a gold card following the tut's on this fourm installed 4ext via the card booted into recovery cleared dalvik cache ect and now boot's without any loop's.
Looking forward to flashing cyanogenmod and maybe going s-off
Many thanks for all your help and suggestions ill hit the thanks button for you.
Just need to mark as " solved " not sure how ( mod's ? )

Can't flash any recovery to HTC One S

Hello.
I have been fighting very long time with this, I was digging through this forum and rest of the Internet for possible solutions and I'm stuck.
I am using Linux Mint 17.2.
I have HTC One S - probably s4 version - which does not boot into any system or recovery.
I am able to get to this point where I can see this menu:
- fastboot
- recovery
- factory reset
- clear storage
- simlock
- image crc
- show barcode
At the top of the screen I see the following info:
*** UNLOCKED ***
VLR PVT SHIP s-OFF RL
CID-11111111
HBOOT-2.15.0000
RADIO-1.35a.32.45.27
OpenDSP-v33.1.0.45.1128
eMMC-boot
Dec 14 2012, 17:10:57:7799
Every time I was trying to flash something new, I did the "factory reset" and "clear storage", so probably now there is no OS nor recovery (if I am wrong please explain, I want to know why I can't succeed).
I think I have the S4 version of the phone (ville). Anyway, I tried to flash recovery for S3 version as well.
After typing "sudo fastboot devices" in console I can see:
FA37KW401167 fastboot
The command "adb devices" does not bring any results.
I was trying to flash recovery with the command "sudo fastboot flash recovery <recovery.img>"
I have no idea what I am doing wrong. It seems I have unlocked bootloader, security turned off, even I have changed CID. Since I am on Linux and I can see fastboot device, it is not a driver issue (right?)
I can also give you the result of "sudo fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.35a.32.45.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA37KW401167
(bootloader) imei: 359901043437330
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4******
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
The only thing which worries me is empty version-main, but I have no idea why and how to fix it.
If you have any clue, please help me. I hope I have not made any lame thing, I was trying to carefully read everything I have found on the Internet and I have no other idea except asking here.
mormegil6

In fastboot mode, you can't see the device with adb, this is normal. From your getvar all, I understand that you have an S4/ville. Your radio version is not a recommended one but it should not be a problem.
When you say that you tried to flash recoveries, which ones did you actually use? From my tests, you should try the modified one from there: http://android.cmphys.com/twrp-ville/
2.8.6.5 is the best one and have a nice button in Wipe: Format Data. It can save wrong fstabs, symlinks and things like that.
Anyway, you should try an RUU to restore your system as new. As your CID is 1111111, you can put the generic european one (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe on androidruu.com). As you're using Linux, the RUU .exe won't work, even in Wine. If you can't access a Windows computer, I can provide you a way that works well under any Linux.

I think I understand why I am not seeing anything in ADB - to see something there, I would need to have "USB debugging" option set in Android. And since there is no Android..
I tried with the following recoveries:
r2-modaco-recovery-clockwork-touch-ville
twrp-2.1.6-ville
recovery-clockwork-touch-5.8.3.1-ville
recovery-clockwork-touch-6.0.4.8-ville
recovery-clockwork-6.0.4.8-ville
twrp-2.8.7.0-ville
twrp-2.6.3.0-villec2
I have been rooting phones and flashing different OS previously (Galaxy Ace GT-S5830, Xperia Go ST27i), but I have never met "RUU". I saw some posts connected with HTC One S, but since I was not sure what it is, I was not trying to do anything there. This is sort of "stock-ROM-and-recovery-set"?
I have access to Windows 8.1, but I was using Linux to avoid driver issues. I will switch now to Windows and I will try the options you suggested. (as a Linux fan, I would also like to know how to manage this RUU on Linux, the more I can do on Linux the better )

An RUU is a program that will put your phone in a restore mode and push a big zip with almost every partitions. This is a big exe with a nice GUI, adb, fastboot and a ZIP.
From Linux it's running those commands :
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip <archive.zip>
fastboot reboot
Search XDA and you'll find better documentation.
Envoyé de mon HTC One S en utilisant Tapatalk

Thanks a lot for your help!
The recovery you recommended did not work, but the RUU did. I was not sure if I would know which zip file to use from my Linux, so I used the EXE on my Windows 8.1. Obviously I had driver issues - this fix solved them: http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
So now I have my HTC One S working like a charm. I am not sure what this RUU did - is the phone locked again? Or the security and CID were changed? I would like to install CyanogenMod there, and I hope I will not have any issues again.
Thousands of thanks once again!

No your phone is not locked and no the CID was unchanged. You should install a recovery (TWRP) and you can install CyanogenMod. Don't forget the Google Apps zip.