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

Cannot get into recovery

Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(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.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(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
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks

I suggest reflashing kernel.
Wysłane z mojego HTC One S przy użyciu Tapatalka

jaco_lbn said:
I suggest reflashing kernel.
Wysłane z mojego HTC One S przy użyciu Tapatalka
Click to expand...
Click to collapse
Thanks, but I even cannot get into recovery

velvel said:
Thanks, but I even cannot get into recovery
Click to expand...
Click to collapse
Hm, really strange behavior, had couple of HTC phones but never seen something like this happening.
I did run RUU (first changed cid and relocked), everything went fine (no errors), but still cannot boot. My experience so far was that if RUU runs fine, you should boot without problem. Thinking more and more that there is some hardware problem, that is causing phone to bootloop.
If anyone has any idea, I would appreciate it a lot.
Thanks

Build me a scenario
velvel said:
Hm, really strange behavior, had couple of HTC phones but never seen something like this happening.
I did run RUU (first changed cid and relocked), everything went fine (no errors), but still cannot boot. My experience so far was that if RUU runs fine, you should boot without problem. Thinking more and more that there is some hardware problem, that is causing phone to bootloop.
If anyone has any idea, I would appreciate it a lot.
Thanks
Click to expand...
Click to collapse
According to your first post, everything seems to be okay. Your drivers are seeing the phone, and the phone is recognizing its hardware.
Which recoveries did you try to flash? (TWRP, CWM)
And which version?
Have you tried to reroot the device and flash a recovery again since running the RUU?
From my experience with running an RUU, you should be able to boot right away. What were the steps you took (in order) before you ran the RUU?
Sorry for all the questions, trying to establish a scenario.
[EDIT] Also, I see that you got the initial recovery from the CM11 ROM page. You didn't happen to flash a ROM that is meant for HBOOT 2.16 did you? I sure hope not. That could be a possibility as to why you can not boot anything.

42freelancer said:
Which recoveries did you try to flash? (TWRP, CWM)
Click to expand...
Click to collapse
I've tried both. fastboot flash recovery imgname would work fine, but I would again finish in bootloop after restart.
And which version?
Click to expand...
Click to collapse
TWRP_2.6.1.0_ville_4.2.2 and latest CWM
Have you tried to reroot the device and flash a recovery again since running the RUU?
Click to expand...
Click to collapse
You mean reunlock, not reroot, right? I've done reunlock so I could flash recovery.
From my experience with running an RUU, you should be able to boot right away. What were the steps you took (in order) before you ran the RUU?
Click to expand...
Click to collapse
I would run:
fastboot erase cache
fastboot reboot-bootloader
and then start RUU.
Sorry for all the questions, trying to establish a scenario.
Click to expand...
Click to collapse
You are welcome and thanks for the help.
[EDIT] Also, I see that you got the initial recovery from the CM11 ROM page. You didn't happen to flash a ROM that is meant for HBOOT 2.16 did you? I sure hope not. That could be a possibility as to why you can not boot anything.
Click to expand...
Click to collapse
No, 2.15 all the time...

velvel said:
I've tried both. fastboot flash recovery imgname would work fine, but I would again finish in bootloop after restart.
TWRP_2.6.1.0_ville_4.2.2 and latest CWM
You mean reunlock, not reroot, right? I've done reunlock so I could flash recovery.
I would run:
fastboot erase cache
fastboot reboot-bootloader
and then start RUU.
You are welcome and thanks for the help.
No, 2.15 all the time...
Click to expand...
Click to collapse
Try getting into bootloader and pushing the kernel this way: fastboot flash boot boot.img
you don't have to be in recovery for this. The phone is s-on right?
[edit] actually your security says it's off.

42freelancer said:
Try getting into bootloader and pushing the kernel this way: fastboot flash boot boot.img
you don't have to be in recovery for this.
Click to expand...
Click to collapse
No, it didn't work, this is something more serious
I've basically tried all I could think of, from doing RUUs (3 of them), flashing boot and recovery images, going 2.15, 2.16, locking/unlocking (obviously) and finally going S-On (ok, might be stupid, but I run out of ideas).
Bottom line is that all of the flashing worked for me, I get no error, but even simple fastboot boot recovery.img brings back the bootloop.
For example:
>fastboot flash recovery openrecovery-twrp-2.6.3.0-ville-selinux.img
sending 'recovery' (8668 KB)...
OKAY [ 1.108s]
writing 'recovery'...
OKAY [ 2.059s]
finished. total time: 3.173s
>fastboot reboot
and if I hold Vol- and select recovery in bootloader I am back to bootloop.
Same thing if I try:
>fastboot boot openrecovery-twrp-2.6.3.0-ville-selinux.img
I just do not understand why I am not getting any error message when flushing and is it possible that there is something wrong with the hardware that causes this behavior...

velvel said:
No, it didn't work, this is something more serious
I've basically tried all I could think of, from doing RUUs (3 of them), flashing boot and recovery images, going 2.15, 2.16, locking/unlocking (obviously) and finally going S-On (ok, might be stupid, but I run out of ideas).
Bottom line is that all of the flashing worked for me, I get no error, but even simple fastboot boot recovery.img brings back the bootloop.
For example:
>fastboot flash recovery openrecovery-twrp-2.6.3.0-ville-selinux.img
sending 'recovery' (8668 KB)...
OKAY [ 1.108s]
writing 'recovery'...
OKAY [ 2.059s]
finished. total time: 3.173s
>fastboot reboot
and if I hold Vol- and select recovery in bootloader I am back to bootloop.
Same thing if I try:
>fastboot boot openrecovery-twrp-2.6.3.0-ville-selinux.img
I just do not understand why I am not getting any error message when flushing and is it possible that there is something wrong with the hardware that causes this behavior...
Click to expand...
Click to collapse
Sounds like you have a soft brick on your hands.
Can you boot the device at all, stock or custom ROM?
Maybe reverting to COMPLETE STOCK and starting over fresh will help?
What was the last thing you did right before you got stuck?

42freelancer said:
Sounds like you have a soft brick on your hands.
Can you boot the device at all, stock or custom ROM?
Maybe reverting to COMPLETE STOCK and starting over fresh will help?
What was the last thing you did right before you got stuck?
Click to expand...
Click to collapse
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...

velvel said:
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...
Click to expand...
Click to collapse
And here we are. Do you happen to have the old All In One Kit that became obsolete, by hasoon2000? It has the function to flash your recovery back to stock. I found two mirrors on the internet, but because of the rules, I can't post them. But they are accessible through the internets if you use the right keywords.

42freelancer said:
And here we are. Do you happen to have the old All In One Kit that became obsolete? It has the function to flash your recovery back to stock. It's probably floating around the internet somewhere. If you don't I can try to find it.
Click to expand...
Click to collapse
Tried that too, no luck. Looks like I am getting a new paperweight

velvel said:
Tried that too, no luck. Looks like I am getting a new paperweight
Click to expand...
Click to collapse
If you haven't lost all hope, try reading through this and (Return to Stock - http://forum.xda-developers.com/showthread.php?t=2164783) see if you missed anything?
You seem pretty savvy in your HTC ONE S know-how. But it's always good to follow someone else's tutorial just for guidance.

Seems issue with Recovery, bootloop is normal
velvel said:
Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(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.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(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
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks
Click to expand...
Click to collapse
Hi,
Bootloop is normal for ROM geeks.
In your case, it seems your phone has issue with version of Recovery. I had this issue too and found correct Recovery @ http://techerrata.com/browse/twrp2/ville ....
You can give a try..:fingers-crossed::fingers-crossed::fingers-crossed:

velvel said:
Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(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.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(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
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks
Click to expand...
Click to collapse
Did you check the fast boot option in the powermenue under settings? If its check it will happen like ur problem.

velvel said:
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...
Click to expand...
Click to collapse
Have you tried this? :
--> flash STOCK recovery via fastboot or toolkit
--> Boot to bootloader --> Factory Reset(Userdata) / Clear Stotage (SD-card) (these commands only work with STOCK recovery)

Before I got the same problem, so in Bootloader I did Factory Reset and then flash the Recovery TWRP 2.6.3.0. Now it works

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

Stock AT&T XL won't boot after factory reset

I'm not sure where to start. My brother handed me his phone after stupidly following a friend's suggestion that his phone would be faster if he did a factory reset. The phone displays the white screen with the HTC logo, then goes to a black screen and gets stuck there.
I'm able to get to fastboot, but I'm not really sure where to go from there.
The phone's never been tampered with before. S-ON, locked bootloader.
Here's the text I'm seeing on fastboot:
Code:
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012 <- I assume this date is because of the factory reset?
If I understood correctly from what I've been reading, I'm probably gonna need to reflash a stock ROM from fastboot through adb.
I got this HTC_One_X_RUU_5.18.502.1.exe from one of the threads. How do I extract the ROM from there?
I'd appreciate if anyone pointed me in the right way. I'm a Samsung guy and this phone is absolutely alien to me.
EDIT: Here's some more info I got from fastboot:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(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: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Here goes Serial#
(bootloader) imei: Here goes IMEI
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3780mV
(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

How did he do the factory reset? Through recovery?
The symptoms you list are identical to what happens when flashing a new Rom without S-OFF.
My understanding is that due to write restrictions it can't copy the boot.img file to boot, which is required begin running the operating system.
I'm not sure if this is the case for factory resets though. So it may depend on how he tried to do the factory reset.
If the above situation is the case, then the fix is to flash the boot.img file of the same stock rom. Alternatively, you could flash a new rom and it's respective boot.img file.

He did that through fastboot. In fact he did the factory reset several times after the phone didn't boot.
I already tried flashing a boot.img from a ROM I found in the development section, but fastboot just says (remote:signature verify fail).
I have absolutely no freaking idea where to get that specific stock ROM. (It's 3.18.502.6, right?)
I added some extra info in the OP in case its useful.
EDIT: I downloaded the 3.18.502.6 OTA update, extracted the boot.img and the phone keeps spitting (remote:signature verify fail)

Since he flashed through recovery it may have screwed up because the bootloader is still locked (this may be the reason why you're getting errors too).
Unlocking the bootloader is what allows you to write to internal memory and is required to flash a rom.
I unlocked my bootloader using this nifty tool:
http://forum.xda-developers.com/showthread.php?t=2470972
This should then allow you to flash the boot.img file with the command
Code:
fastboot flash boot boot.img

I don't think flashing a boot.img is going to help. You're gonna need to run an RUU, either of these should be fine:
http://androidruu.com/getdownload.p..._10.130.32.34_release_signed_With_Partial.exe
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
Transmitted via Bacon

Hey timmaaa, thanks for the help.
This phone is insufferable. Now I'm getting this:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip rom_02.zip
sending 'zip' (798796 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.007s
I actually managed to flash rom_01.zip and now I'm able to boot into recovery.
When I'm on recovery the log says:
Code:
Can not mount SD Card (No such file or directory)
What would you suggest I do next?

Why are you doing that though? That's not how you use an RUU, you're not meant to extract anything, it's an executable file so all you do is connect your phone in bootloader mode and run the program. Plus, who knows what's been done to the device at this point with all the mucking around that's happened with it, flashing just the ROM component won't achieve the desired result. You need to run the RUU as intended so it can update all aspects of the phone and bring everything back into line. There's a pretty good guide to using an RUU here:
Running a Rom Update Utility (RUU) on the HTC One XL Evita
Follow that guide exactly and your phone will hopefully be revived.

I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.

Mighty_Rearranger said:
I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.
Click to expand...
Click to collapse
All good, is the phone booting now?
Transmitted via Bacon

Yup, it booted up alright. I think I'm gonna see how to install a custom recovery so I can fix it easier if he screws the phone up again.

Cool, I have detailed instructions for this device here:
http://forum.xda-developers.com/showthread.php?t=2593382

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.