Database Info

[Q] HTC One S Root OTA Update Questions

Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app

Problem Fixed
DrOfLife said:
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!

fsustrength said:
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
Click to expand...
Click to collapse
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.

TheAdictsPunk said:
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
Click to expand...
Click to collapse
I have also tried the steps and have run into the same problem. All is well when I flash into recovery, but when the phone starts updating about quarter or half-way through it also gives me the same red error message and the phone restarts soon after with no update. I have tried several times with the same problem.
However, thanks fsustrength for the instructions, before I was getting no where, but now I almost got it
Sent from my HTC VLE_U using xda app-developers app

ckpv5 said:
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One V after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
Note : for people with ERROR 155 UNKNOWN ERROR they need to go into HBOOT and select FASTBOOT and run the RUU to revert to stock (thanks Lloir)
And usually:
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
Click to expand...
Click to collapse
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1

Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did). I did in fact have and used the root keeper app, put it on temporary unroot, and flashed the stock rom and ran the update. Yet, I still run into the problem of the red error sign. I'm sure there is a factor that maybe could cause it to stop, but I cannot put a finger on it.
However, I did notice something while following the procedures of the guide on my phone. When I flash the stock rom on my phone, I have to re-download the system update. While downloading the system update I notice that some of my apps get root permissions from SuperSu in the background, even though in root keeper I temporarily took off root. Rootkeeper also states that my phone is unrooted. Could this problem cause the red error message? If so, any way to fix it?
Sent from my HTC VLE_U using xda app-developers app

DrOfLife said:
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did).
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I did! Last night I even tried flashing the recovery image through fastboot instead of the all-in-one kit. Then, even, the recovery image wouldn't flash all the way through... maybe our phones are having a problem with the recovery being reflashed and not the update at all.

I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.

mmceorange said:
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
Click to expand...
Click to collapse
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app

DrOfLife said:
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)

mmceorange said:
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
Click to expand...
Click to collapse
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app

DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Click to expand...
Click to collapse
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?

Rerooting
DrOfLife said:
So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I'm still running stock 1.84, but I'm rooted and unlocked. I do not have any kind recovery like CWM or TWRP. You may have to flash a stock recovery image in order to re-install the recovery of your choice. If you want to get rooted again try this method: http://forum.xda-developers.com/showthread.php?t=1577831 It's what I used to gain root. It's a rather easy to follow guide. I used this instead of the AIO kit.
I'm going to try and revert to locked and unroot in order to get the update. Wish me luck.

DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Oh lol sorry about that.
DrOfLife said:
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
Click to expand...
Click to collapse
Awesome!
DrOfLife said:
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I personally have never encountered that before, so I am of little help here. The suggestion above me sounds like the right direction though.

Red triangle error
dc211 said:
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Click to expand...
Click to collapse
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.

lonegunman0 said:
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
Click to expand...
Click to collapse
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!

skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?

Stock rom
mylegiscramped said:
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Click to expand...
Click to collapse
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
Yes i agree about the file detection. I'm running stock rom but i think i've just realised my problem. Although i have a stock rom my problem is that the stock rom i'm running is deodexed. I read somewhere that if the stock rom is tweaked in any way or if any bloatware is deleted you can't get OTA updates.
Hope this helped

Wouldn't an RUU fix any of those problems?

Yes it would
Sent from my HTC One S using xda app-developers app

[Q] Bricked/softbricked and Confused {2.20?}

So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?

wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
He probably forgot to flash boot.img in fastboot.
If you are bricked, this phone will not turn on and be listed as QHSUSB_DLOAD in windows.
edit: cwm + evita(htc one xl) = bad.
he needs TWRP

wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...

Crappyvate said:
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...
Click to expand...
Click to collapse
absolutelygrim said:
He probably forgot to flash boot.img in fastboot.
Click to expand...
Click to collapse
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?

wiiareonfire said:
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?
Click to expand...
Click to collapse
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM

First, extract boot.img onto comp. Move boot.img into adb files. Rezip Rom and transfer to sdcard. Fire up command prompt where you stored boot.img. type --> fastboot flash boot boot.img
Once successful, flash Rom IN RECOVERY. profit
Tell your FRIEND to follow posts before blindly flashing, he'd be more prepared
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium

Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium

absolutelygrim said:
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM
Click to expand...
Click to collapse
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
subarudroid said:
Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium
Click to expand...
Click to collapse
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?

wiiareonfire said:
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?
Click to expand...
Click to collapse
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1

Crappyvate said:
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1
Click to expand...
Click to collapse
Code:
C:\Android>adb reboot recovery
error: device not found
Surprisingly enough, you need to be booted into android for adb commands to work. Even the bootloader option for "recovery" gets me nowhere.
Out of nowhere, he tells me he tried to flash a rom.
Ali: the rom that i flashed hmmm.
if i sent that to you would you be able to do anything?
well, tried flashing?
Me: a download link would be preferable
but yes, i'll need that
Ali Haider: got it.
give me a few minutes.
what if the rom wasn't supported?
because i can't completely remember which of the several roms i tried to flash were the problem
Me: what do ya mean "not supported"
Ali:
like clockwork- it apparently doesn't work
Me:
gimme whichever you flashed most revently
a link
i'll need the boot.img
and if you don't know which rom, gimme a list to narrow it down
and i'll go one by one
Click to expand...
Click to collapse
TL;DR, he flashed with CWM and that's why it's screwed up.
Ladies and gents, we might be getting somewhere with this. Albeit, slowly, thanks to my friend who can't read the posts.

I think Crappyvate has the right idea here. You need to flash a proper recovery.
Sent from my One X using xda premium

subarudroid said:
I think Crappyvate has the right idea here. You need to flash a proper recovery.
Click to expand...
Click to collapse
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?

wiiareonfire said:
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?
Click to expand...
Click to collapse
What happens after flashing twrp in flashboot ? what msg do you get ?

Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?

wiiareonfire said:
Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?
Click to expand...
Click to collapse
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?

Crappyvate said:
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?
Click to expand...
Click to collapse
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?

I believe Fat32, but I may be wrong on that.
And you can use windows built in formatter.

wiiareonfire said:
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?
Click to expand...
Click to collapse
yep fat 32, dunno windows sorry...

Yup fat32. That what I did. My first hox I soft bricked as well with cwm
Sent from my One X using xda premium

I formatted with FAT32... It's still not accepting the file. TWRP crashes when the adb push command is finished. Is there something I'm missing?

[Q] Noob Alert. This could be one for you to get your teeth into...

...then again, I might just be being a complete moron and absolutely wasting a lot of people's time. I'm going to try anyway because everytime I Google my multiple problems I seem to get back to this website. Yes, I watched your noob video - I laughed a lot, and unfortunately and unintentionally I feel like I'm going to tick a few of the boxes at the end of it... If you can rescue me from my situation, I'll definitely make a donation towards the upkeep of your site (As long as you have a donation link.)
I have a HTC Sensation XE (with Beats Audio) and it being a Sunday afternoon I thought I would have a crack at rooting and applying custom firmware to me phone for the first ever time. I bet you can see where this is going. I downloaded the SDK Manager, HTC ONE X All In One tool, and the latest Cyanogen for my handset. I DID NOT S-OFF MY PHONE BEFORE JUMPING RIGHT IN FOR I AM AN IDIOT. So I rooted the phone, and all seemed to be going well, I had the Stock ROM, I believe they call it? But it was rooted as confirmed by Root Checker. AT THIS POINT I BACKED UP USING CLOCKWORK. I then got ahead of myself and tried to download the new Custom ROM. After getting aggrieved that the ROM was stuck on 86% consistently with ROM Manager I downloaded it to my PC. Put it onto my SD card. Went into recovery mode. Installed .zip via SD card.
This is where problems began. Once the installation was done I restarted my phone and got caught out by the little blue man, and I believe my screen was stuck in bootloop, where it just continually showed me his image - and the movements around him kept occurring, it didn't freeze. I tried to put the boot.img on from the .zip where I had downloaded it but it came to no avail, it still didn't boot past that point.
I was aggrieved and so restored my phone to the point I said I had backed up. Just after the root of the stock ROM. Then when I tried to boot this up, it got stuck at the Beats Audio symbol in similar vein to how it was stuck on the little blue man.
I turned my phone off, tried to wipe everything using 4ext recovery that I placed on the phone at this point. My All In One tool also stopped recognising my phone, constantly saying "error: device not found" when I tried to do something which it was not doing before the root. Furthermore, when I plug my phone into my PC, it doesn't offer me Removable Drive storage, but it does make the pinging noise which notifies me that the device is recognised. Now after all this, when I boot the phone it is stuck at the HTC screen with a white background and I don't know why it is now halting here as opposed to what it was earlier, could it be something to do with when I was trying to get the all-in-one tool to recognise my phone I tried to reflash recovery of 'Stock'? I really am upset about this and regret even attempting it as I am in love with my phone and can't really live without it. Please help and if I get a successfully, rooted phone I will be very happy and PROMISE to make a donation towards the site of what I can afford.
So please do me and your own site a favour and help me
BRIEF POINTS OF NOTE
ROOT SEEMED TO WORK FINE UNTIL ATTEMPTING TO PUT CUSTOM ROM ON
CUSTOM ROM WOULDN'T BOOT PAST BLUE MAN SCREEN AT FIRST, THEN BEATS AUDIO SCREEN AND THEN HTC SCREEN.
MY PHONE IS S-ON, UNLOCKED, PYRAMID PUT SHIP S-ON RL, HBOOT-1.29.0000,eMMC-boot,Mar 2 2012, 18.14.34
PC IS NOT CURRENTLY RECOGNISING MY PHONE AS A REMOVABLE DEVICE IN THE SENSE THAT IT WON'T ALLOW ME TO PUT ON ANY ITEMS.
I DO HAVE A SPARE, ACCESSIBLE SD CARD AND DO NOT CARE WHAT HAPPENS TO THE CONTENTS OF IT. IF THIS IS USEFUL.
Please. Help me. Thank you

don't panic.many as you had that issue.it is easy
from 4ext recovery enable smartflash and then immediately flash the rom
you should be fine

If it still fails to boot after reflashed with smartflash on, get boot.img from zip, place it in your fastboot/adb folder and flash it manually from fastboot: fastboot flash boot boot.img
Look for Asskicker's guide in General section. "flashing rom with s-on and Hboot 1.27+"
Sent from my HTC Sensation Z710e using xda app-developers app

rzr86 said:
don't panic.many as you had that issue.it is easy
from 4ext recovery enable smartflash and then immediately flash the rom
you should be fine
Click to expand...
Click to collapse
Unfortunately, this hasn't worked for me. I did this...
- Went onto 4EXT recovery.
- Went to tools.
- Clicked on 'Enable Smartflash'.
- Ensured it was on.
- Went to 'install .zip from SD Card'
- Found the Cynagon MOD.
- "Finding update package... Opening update package... Installing update... Install from SD Card complete."
- Rebooted phone.
- A pending update to your boot partition has been detected. Your ROM will reboot once [and then it reboots]. The first time it came up with this though. It said something about how there had been an error.
- Got stuck at the HTC screen again.
I'd just like to reaffirm that before something happened (I believe it was when I tried to flash to stock recovery), my phone was getting to the Beats Audio/Little Blue Man Screen. Now it's getting to the HTC screen.
That donation to the site is still in promise!

matekaneve said:
If it still fails to boot after reflashed with smartflash on, get boot.img from zip, place it in your fastboot/adb folder and flash it manually from fastboot: fastboot flash boot boot.img
Look for Asskicker's guide in General section. "flashing rom with s-on and Hboot 1.27+"
Sent from my HTC Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
This also didn't work for me. It appeared to run entirely successfully. I rebooted the phone using 'fastboot reboot' and it still got stuck at the same screen.

ElliotHorne32 said:
Unfortunately, this hasn't worked for me. I did this...
- Went onto 4EXT recovery.
- Went to tools.
- Clicked on 'Enable Smartflash'.
- Ensured it was on.
- Went to 'install .zip from SD Card'
- Found the Cynagon MOD.
- "Finding update package... Opening update package... Installing update... Install from SD Card complete."
- Rebooted phone.
- A pending update to your boot partition has been detected. Your ROM will reboot once [and then it reboots]. The first time it came up with this though. It said something about how there had been an error.
- Got stuck at the HTC screen again.
I'd just like to reaffirm that before something happened (I believe it was when I tried to flash to stock recovery), my phone was getting to the Beats Audio/Little Blue Man Screen. Now it's getting to the HTC screen.
That donation to the site is still in promise!
Click to expand...
Click to collapse
did you flash gapps and then the CM rom?
if no then:
flash gapps
flash the rom again
(don't forget to enable smartflash again)

rzr86 said:
did you flash gapps and then the CM rom?
if no then:
flash gapps
flash the rom again
(don't forget to enable smartflash again)
Click to expand...
Click to collapse
Sorry to be a pain, but could you run me through a step-by-step on how to do that? *Noob Klaxon*

ElliotHorne32 said:
Sorry to be a pain, but could you run me through a step-by-step on how to do that? *Noob Klaxon*
Click to expand...
Click to collapse
gapps is google apps.is a zip file
if i remember well maybe is in the thread where you downloaded the rom
simply put it in the root of sdcard and flash it from recovery
after that flash the rom(don't forget smartflash)

rzr86 said:
gapps is google apps.is a zip file
if i remember well maybe is in the thread where you downloaded the rom
simply put it in the root of sdcard and flash it from recovery
after that flash the rom(don't forget smartflash)
Click to expand...
Click to collapse
I downloaded it from here [can't post link, but it's the official Cynagon MOD Website] - I then clicked on the 'Stable Mod'.?

If you straight quick responses go on this forum here I have through similar issues before and they so helpful..I'm S-ON
http://forum.xda-developers.com/showthread.php?t=163186
Sent from from my HTC Sensation XE with Beats Audio Z715e using xda app-developers app

Hi there mate!
What I would recommend you to do is running an appropriate RUU for your device, ( i would recommend GB, because then you can S-off very easy), and then re-run the whole process. If you run a GB RUU, you can gain s-off with revolutionary. And the best part, the RUU can be run in bootloader, so it doesn't matter if your ROM does not boot. I can send you a link once my internet gets faster (im using all my bandwidth for source-building lol)
Please keep me posted and feel free to ask any questions
Best of luck !

InfinityFTW said:
Hi there mate!
What I would recommend you to do is running an appropriate RUU for your device, ( i would recommend GB, because then you can S-off very easy), and then re-run the whole process. If you run a GB RUU, you can gain s-off with revolutionary. And the best part, the RUU can be run in bootloader, so it doesn't matter if your ROM does not boot. I can send you a link once my internet gets faster (im using all my bandwidth for source-building lol)
Please keep me posted and feel free to ask any questions
Best of luck !
Click to expand...
Click to collapse
if i remember well he can't downgrade using a GB ruu because he is S-ON
i think he can only upgrade
you have to be already S-OFF in order to downgrade with ruu

InfinityFTW said:
Hi there mate!
What I would recommend you to do is running an appropriate RUU for your device, ( i would recommend GB, because then you can S-off very easy), and then re-run the whole process. If you run a GB RUU, you can gain s-off with revolutionary. And the best part, the RUU can be run in bootloader, so it doesn't matter if your ROM does not boot. I can send you a link once my internet gets faster (im using all my bandwidth for source-building lol)
Please keep me posted and feel free to ask any questions
Best of luck !
Click to expand...
Click to collapse
Thank you for your helpful paragraph If you could send me the link for that RUU, that would be great, but I do have a couple of other questions. What is an RUU? I assume GB is Gingerbread, but is that the OS that I am on? What will the RUU do? I really stepped out of my depth trying this haha!
Elliot,

ElliotHorne32 said:
Thank you for your helpful paragraph If you could send me the link for that RUU, that would be great, but I do have a couple of other questions. What is an RUU? I assume GB is Gingerbread, but is that the OS that I am on? What will the RUU do? I really stepped out of my depth trying this haha!
Elliot,
Click to expand...
Click to collapse
RUU returns your device into completely stock situation as you bought it
now depending your hboot version you are running ics android

ElliotHorne32 said:
Thank you for your helpful paragraph If you could send me the link for that RUU, that would be great, but I do have a couple of other questions. What is an RUU? I assume GB is Gingerbread, but is that the OS that I am on? What will the RUU do? I really stepped out of my depth trying this haha!
Elliot,
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=1074559
RUU stands for Rom Update Utility, and it is an executable (.exe) file wich is ran from a pc with a phone connected in fastboot. The RUU is meant to restore all partitions on your phone
Sent from a muffin inside a muffin using muffintalk.

OK try this.
1. Reboot into 4ext recovery.
2. Wipe everything except sdcard.
3.enable 4ext smart flash
4. Reflash Cyanogenmod.
5. Flash gapps add-on from Cyanogenmod thread.
6. Reboot and wait up to 10 minutes.
If this does not work take your Cyanogenmod rom and on your pc extract the boot.IMG file and move it to your adb folder then repeat but add
8. Fastboot flash boot.IMG using adb while in recovery.
Open your cmd and CD to your ad folder.
Issue the command " fastboot flash boot boot.img " with the phone connected.
9. Reboot and wait up to 10 minutes

Thank you all for your responses, I haven't forgotten about this thread at all haha - I've just been very busy lately but will be doing all of your suggestions over the weekend, so thank you. Will keep you posted. Elliot

ElliotHorne32 said:
Thank you all for your responses, I haven't forgotten about this thread at all haha - I've just been very busy lately but will be doing all of your suggestions over the weekend, so thank you. Will keep you posted. Elliot
Click to expand...
Click to collapse
Btw the only RUU that will work on hboot 1.29.0000 devices is the 3.33.401.153 one IIRC. It's also available to download from my FTP - here
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

Jonny said:
Btw the only RUU that will work on hboot 1.29.0000 devices is the 3.33.401.153 one IIRC. It's also available to download from my FTP - here
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Just when I have everything ready to try this, I am getting '403 Forbidden' on that link you just sent me. What do I do to get that link working?
Also, is it as simple as plugging the phone into Fastboot USB mode and clicking the .exe file?
Elliot,

Any help possible with this one, guys and girls? The last post I made about the 403?
Elliot

stuck in a boot loop after a update from internal storage

Hello my friends!!
I really need you help, I have some kind of soft brick. After I try to update my new htc one xl (asia version), now I'm stuck in a boot loop. Here's my info:
my CID=11111111.
I can get to bootloader & fastboot. My phone is stuck on the htc logo "htc quietly brillant". I think tha I screw up the OS.
Any ideas??
Best regards,

Happened to me, too. What worked for me was getting into fastboot and doing:
Code:
fastboot erase cache
in the windows command prompt. After that get the ROM you most recently installed and extract the "boot.img" and put it in the same directory as fastboot.exe and then flash that boot image with:
Code:
fastboot flash boot boot.img
Once that is done, do this again:
Code:
fastboot erase cache
and it should boot normally.
Let us know if that is not the case.

You should only need to use fastboot erase cache once. Doing it a second time is pointless. Also, your problem is extremely well documented on this site by the hundreds before you who have posted this exact same issue.
Not to mention, if you can't figure this out, you never should have rooted in the first place. This is why I ignored this post.
Search and read and you'll easily fix your phone.
Egoista's solution assumes you have a 1.14 hboot and hadn't flashed the boot.img
Sent from my One X using xda app-developers app

Thanks a lot for both replies!!
Finally I use RUU tool and everything was great. Now I have my phone updated to Jelly Bean
Regards!
exad said:
You should only need to use fastboot erase cache once. Doing it a second time is pointless. Also, your problem is extremely well documented on this site by the hundreds before you who have posted this exact same issue.
Not to mention, if you can't figure this out, you never should have rooted in the first place. This is why I ignored this post.
Search and read and you'll easily fix your phone.
Egoista's solution assumes you have a 1.14 hboot and hadn't flashed the boot.img
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse

Tatirulo said:
I really need you help, I have some kind of soft brick. After I try to update my new htc one xl (asia version), now I'm stuck in a boot loop.
Click to expand...
Click to collapse
The reason for this is quite simple, and should have been obvious. OTA needs stock recovery in order to install. When it can't find stock recovery, the install gets stuck.
RUU worked because RUU also overwrites recovery with the stock one.
In any case, you should never ever install an OTA on a rooted device without first researching what will happen, at a minimum. It usually won't work, and will often bootloop the device.

redpoint73 said:
The reason for this is quite simple, and should have been obvious. OTA needs stock recovery in order to install. When it can't find stock recovery, the install gets stuck.
RUU worked because RUU also overwrites recovery with the stock one.
In any case, you should never ever install an OTA on a rooted device without first researching what will happen, at a minimum. It usually won't work, and will often bootloop the device.
Click to expand...
Click to collapse
I suggest not updating at all without reading. Even custom ROMs.
Sent from my Carbon-ize Evita using xda-developers app

[Q] HTC one S brick

Hello,
I'm new here but today I tried to root my phone and put CM10 on it. Rooting was not that hard but with flashing the rom I had some problems. I used a tutorial from youtube "Htc One s jellybean 4.2.2 Nightly Cm10.1 Rom" and did everything as he said but when I tried to boot CM it came in a boot loop so I restored my backup and everything was back normal again. But I thought i'll give it another try so I did that and it still didn't work so I restored (via recovery) and at the end it said: It appears your phone isn't rooted do you wanna do it now...(or something like that)? I found that a bit strange but I clicked yes but now if I boot up my phone first you just see "HTC - quietly brilliant" and then the red letters come beneath it saying its a developers version. I Couldn't do anything so I jumped into my bootloader and did factory reset but now everything is gone and I still have that booting problem,
I can acces bootloader and recovery mode but that's it
I really need my phone soon and don't have much time to look on the internet for solutions so could you please help me?
Thanks in advance!!
Lennard

Do you have the RUU for your phone? Maybe that would be the quick fix to take it back to stock. You can use an RUU that's equal or newer than what you have currently.
BTW: I went through this as well.

808phone said:
Do you have the RUU for your phone? Maybe that would be the quick fix to take it back to stock. You can use an RUU that's equal or newer than what you have currently.
BTW: I went through this as well.
Click to expand...
Click to collapse
I don't even know what that it >.< (sorry for being noob )

Did you flash boot.img with cm10
Sent from my One S

ka_55 said:
Did you flash boot.img with cm10
Sent from my One S
Click to expand...
Click to collapse
Jep, as instructed in the youtube video

Which hboot version and radio?
Cm10 uses 3.4.x kernel, it won't boot with old firmware
Sent from my One S

ka_55 said:
Which hboot version and radio?
Cm10 uses 3.4.x kernel, it won't boot with old firmware
Sent from my One S
Click to expand...
Click to collapse
Hboot : 2.15.000
Radio : 1.15.50.05.29

Then it can be a bad download. If not I I'm out of ideas
Sent from my One S

Do you remember doing any of the following?
-wipe data/factory reset
-wipe dalvik cache
I think that was my problem that I didn't wipe the cache completely. Possibly a bad download too. Do a search on md5. It's basically a check to see if your download is ok before flashing.
As far the RUU is concerned, it will take you back to stock. You will need the info that appears when you start the phone up by holding down VOL DOWN and POWER. Hold down volume down, then press the power for a second or 2. Then it will boot up into HBOOT.
Write down the info that appears and search for a matching RUU equal or newer.
What is the carrier???

808phone said:
Do you remember doing any of the following?
-wipe data/factory reset
-wipe dalvik cache
I think that was my problem that I didn't wipe the cache completely. Possibly a bad download too. Do a search on md5. It's basically a check to see if your download is ok before flashing.
As far the RUU is concerned, it will take you back to stock. You will need the info that appears when you start the phone up by holding down VOL DOWN and POWER. Hold down volume down, then press the power for a second or 2. Then it will boot up into HBOOT.
Write down the info that appears and search for a matching RUU equal or newer.
What is the carrier???
Click to expand...
Click to collapse
I did the factory reset, dalvik cache and cache wipe. When I tried to install CM it indeed said unable to find md5 or something like that.
I think I have a europe version and looked for fitting RUU but the numbers are completely different maybe you could find a good RUU? (See attachement) Btw I have S4/Ville/Z520e

CID
Could you please read out your CID? Then we can get right RUU.
You can do this by booting your One S into fastboot mode and use the toolkit from the link:
http://forum.xda-developers.com/showthread.php?t=2471151

LS.xD said:
Could you please read out your CID? Then we can get right RUU.
You can do this by booting your One S into fastboot mode and use the toolkit from the link:
http://forum.xda-developers.com/showthread.php?t=2471151
Click to expand...
Click to collapse
I don't know if this is it but it says CID: HTC__E11

Lennardude said:
I don't know if this is it but it says CID: HTC__E11
Click to expand...
Click to collapse
yes thats it
This should be the right RUU http://www.androidruu.com/getdownload.php?file=Ville/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
MAY anyone who reads this confirm it? Just to be safe at all.
btw. "HTC_E11" = unbranded Netherlands
Due to you're S-ON you will have to relock your bootloader to perform a RUU update.
Here you can find a step by step RUU guide by "Flashalot" http://forum.xda-developers.com/showthread.php?p=51016251

LS.xD said:
yes thats it
This should be the right RUU http://www.androidruu.com/getdownload.php?file=Ville/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
MAY anyone who reads this confirm it? Just to be safe at all.
btw. "HTC_E11" = unbranded Netherlands
Due to you're S-ON you will have to relock your bootloader to perform a RUU update.
Here you can find a step by step RUU guide by "Flashalot" http://forum.xda-developers.com/showthread.php?p=51016251
Click to expand...
Click to collapse
Should I first relock my bootloader and follow the tutorial to flash that RUU of vice versa?

Lennardude said:
Should I first relock my bootloader and follow the tutorial to flash that RUU of vice versa?
Click to expand...
Click to collapse
For RUU you need stock recovery and "locked" BL. Please read the guide again and only proceed, if you're sure you got it.
Another question:
You said you got a working recovery? Which version do you use? And have you tried install another custom rom.zip? That would be more easy and safe to you. May be your storage got corrupted and thats why your phone crashed and you can't install the rom.zip stored on the sd-card. You could connect the phone to your pc as mass storage via recovery, format it and put a new customrom.zip on it. By the way, why you installed such an old rom? You can use CM11 for sure

LS.xD said:
For RUU you need stock recovery and "locked" BL. Please read the guide again and only proceed, if you're sure you got it.
Another question:
You said you got a working recovery? Which version do you use? And have you tried install another custom rom.zip? That would be more easy and safe to you.
Click to expand...
Click to collapse
In that guide it doesn't say anything about a relocked bootloader.
I do have a working recovery but how can I get a zip file on it? I can't acces the files of my phone in windows explorer or something like that. Also I don't know if I have a stock recovery but if I don't I have to install that via a zip but how can I get that on my phone...?

Lennardude said:
In that guide it doesn't say anything about a relocked bootloader.
I do have a working recovery but how can I get a zip file on it? I can't acces the files of my phone in windows explorer or something like that. Also I don't know if I have a stock recovery but if I don't I have to install that via a zip but how can I get that on my phone...?
Click to expand...
Click to collapse
PLS boot in recovery mode and tell me what "version" it is You should find it. If you're not sure about it, you can flash a new recovery before installing a rom. Whe you have a working custom recovery you can mount your sd-card to your computer via recovery.
Found the RUU guide i had in mind http://forum.xda-developers.com/showthread.php?t=2501542

LS.xD said:
PLS boot in recovery mode and tell me what "version" it is You should find it.
Click to expand...
Click to collapse
v2.6.0.0

Lennardude said:
v2.6.0.0
Click to expand...
Click to collapse
that is TWRP. My suggestion ist installing the latest Recovery and try install CM11. I just get the links for you.

LS.xD said:
PLS boot in recovery mode and tell me what "version" it is You should find it. If you're not sure about it, you can flash a new recovery before installing a rom. Whe you have a working custom recovery you can mount your sd-card to your computer via recovery.
Found the RUU guide i had in mind http://forum.xda-developers.com/showthread.php?t=2501542
Click to expand...
Click to collapse
The problem is, we're talking about an HTC One S which DOESN"T have a SD Card slot...