Database Info

htc one s brik problem [SOLVED]

Hi i have a big problem with my new htc one s
i follow all instructions: clear data, factory reset, install rom, then install boot.img
Roms boot until it shows wallpaper and top toolbar with the battery icon and time, then can read preparing phone storage.... and an error appears asking me to wait or close system process
The rom restarts and stucks at this point dont know what else do, i try installing stock recovery and clear data factory reset and try install with 3 versions of recovery whith same result, have tried some different roms and its the same.
Wonder if anyone knows what i have to do solve this..
Thankyou in advance.
--------------------------
solution on post #7

Moved To Q&A​
This is a development section, its not the place for questions.​

Which roms did you try to flash? Did you flash the correct boot.img
Sent from my HTC One S using XDA

thanks for your answer
Yes i flash [ROM][ICS] |June 13th| Energy™ -.¸¸.·´¯ Blue with the boot.img from the downloads
and [ROM] Ir2 1.78.401.2 - HTC One S Stock ROM DUO [Deodexed-Updated-Optimised]
When finish flasing from recovery reboot on fastboot and flash the boot.img and always is the same result.
I've tried to change to stock version of recovery and wipe all, reset to factory default then flash custom recovery and start the process but is the same.
when i whipe from stock or custom version of recovery there isn't any error message.
thankyou very much.

you don't flash the boot.img from recovery--read OP

boot.img
I flash it from fastboot not installing a zip from recovery. I also try installing by script like on [ROM][ICS] |June 14th| Energy™ -.¸¸.·´¯ Blue that there is an script that makes the installation always from fastboot

[solved]
Hi, find a way to make my htc one s woking again
This is the solution:
first i've to change my CID because my phone is from ORANGE spain and cannot flash a official RUU.
for this i follow this tutorial
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
Second flash stock recovery and lock boot
finally i've downloaded the last europe RUU, and execute it.The process works like a charm and in 15 or 20 minutes my one s was working again.
Now i have lock boot, stock recovery and unrooted phone and have one question:
for root my phone again have to unlock and flash a custom recovery, and then.....
should I need to put back again stock recovery and lock boot for working an official RUU?? or can work without problems with unloked boot an custom recovery?
Thanks in advance.

Hey I have the exact same issue but running RUU didnt solve it. I have the US Tmobile Htc one s, S-off, supercid, hboot 1.14. I could load custom roms and mount usb storage only through recovery. my sd card does not show in fastboot. However, my phone never completely boots. It goes all the way to the lockscreen, allows me to pull the ring, then gets stuck on preparing phone storage. Flashing RUU does the same.
can anyone help?

joemanbui said:
Hey I have the exact same issue but running RUU didnt solve it. I have the US Tmobile Htc one s, S-off, supercid, hboot 1.14. I could load custom roms and mount usb storage only through recovery. my sd card does not show in fastboot. However, my phone never completely boots. It goes all the way to the lockscreen, allows me to pull the ring, then gets stuck on preparing phone storage. Flashing RUU does the same.
can anyone help?
Click to expand...
Click to collapse
i too have same prob tried all kinds of ruu's. been trying for 14 hours if you find soething please report how you did it

I have the same problem any ideas?
anyone know of any gurus in the forum knows how to fix
I've been trying for a month
any rom to put loads and after a 10-20sec reset

For you with sd-card problems, have you tried to flash stock recovery and then boot to bootloader and choose clear storage? It worked for me.
If you installed a RUU, ofcourse you already have stock recovery.
Sent from my One S using Tapatalk 4 Beta

I have the same problem, and decided to work on it today... I can say frustratingly i've not had ANY success in getting past the screen that pops up with the lock ring on the bottom...I've tried RUUs , the clear storage ... what is going on... I'm S-off as well so i really don't get why this would happen.

One S (s4)
twrp 2.5
S-on
T-mobile US
CM10.2
kernel 3.4
Hboot 2.15
openDsp v31.1.0.45.0815
current raido :1.11.50.05.28_10.27.50.08L
using the getvar method
i get this
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__203
using fastboot getvar version-main
Version-main : ( BLANK)
Click to expand...
Click to collapse
after following the steps for s-off it worked
the bootloader shows VLE PVT SHIP -S-OFF RL
CID-11111111
right after i followed the last step of the face palm method which was
boot into android and issue the 3 commands
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
Click to expand...
Click to collapse
i went into the bootloader confirmed everything then wen back to CM and it woudnt load
so i wiped everything and flashed a new version and an older 10.1 stable version which didnt work either
it would just freeze at the loading screen and restart
so i tried wiping everything and flash a stock RUU from HTC (t-mobile) 4.1.1
everything went off without a hitch
went to bootloader which showed a new version of the radio
tried to boot it up
and it did boot up but i coudnt go any further it just keeps saying
Preparing phone storage
then restarts
i tried wipe/data factory reset but it says cant mount SDCARD even though TWRP has no problem with wiping it

I have the same problem..
qwerty warrior said:
after following the steps for s-off it worked
the bootloader shows VLE PVT SHIP -S-OFF RL
CID-11111111
right after i followed the last step of the face palm method which was
i went into the bootloader confirmed everything then wen back to CM and it woudnt load
so i wiped everything and flashed a new version and an older 10.1 stable version which didnt work either
it would just freeze at the loading screen and restart
so i tried wiping everything and flash a stock RUU from HTC (t-mobile) 4.1.1
everything went off without a hitch
went to bootloader which showed a new version of the radio
tried to boot it up
and it did boot up but i coudnt go any further it just keeps saying
Preparing phone storage
then restarts
i tried wipe/data factory reset but it says cant mount SDCARD even though TWRP has no problem with wiping it
Click to expand...
Click to collapse
I have the exact same problem did you ever figure out a way of fixing it?

qwerty warrior said:
i went into the bootloader confirmed everything then wen back to CM and it woudnt load
so i wiped everything and flashed a new version and an older 10.1 stable version which didnt work either
it would just freeze at the loading screen and restart
so i tried wiping everything and flash a stock RUU from HTC (t-mobile) 4.1.1
everything went off without a hitch
went to bootloader which showed a new version of the radio
tried to boot it up
and it did boot up but i coudnt go any further it just keeps saying
Preparing phone storage
then restarts
i tried wipe/data factory reset but it says cant mount SDCARD even though TWRP has no problem with wiping it
Click to expand...
Click to collapse
exact same problem except i didnt flash a custom rom. i flashed a radio following this http://forum.xda-developers.com/showthread.php?t=1998270 ( i did everything that I was instructed to do in this page) then my wifi didnt work so i reflash the RUU. now im stuck in preparing storage which then lead to bootloop
found the solution
Originally Posted by muriani View Post
well, as a last resort, i set cid to t-mob010 (stock for my phone), ran the latest ruu for t-mobile, and same result.
I've given it up for lost.
Edit: Holy f*ckballs.
So, i didn't give up after all. Found a couple of other threads, and apparently yes, you have to relock, reset cid, and go s-on (fastboot oem writesecureflag 3) and then run the ruu.
I have a stock fresh tmous 4.1.1 one s now.

xxgummyxx said:
exact same problem except i didnt flash a custom rom. i flashed a radio following this http://forum.xda-developers.com/showthread.php?t=1998270 ( i did everything that I was instructed to do in this page) then my wifi didnt work so i reflash the RUU. now im stuck in preparing storage which then lead to bootloop
found the solution
Originally Posted by muriani View Post
well, as a last resort, i set cid to t-mob010 (stock for my phone), ran the latest ruu for t-mobile, and same result.
I've given it up for lost.
Edit: Holy f*ckballs.
So, i didn't give up after all. Found a couple of other threads, and apparently yes, you have to relock, reset cid, and go s-on (fastboot oem writesecureflag 3) and then run the ruu.
I have a stock fresh tmous 4.1.1 one s now.
Click to expand...
Click to collapse
thank you thanks !!!!!!! two days without finding the solution and in the last paragraph that I will write opened the sky, put it in s-on, Greetings

dosariland said:
thank you thanks !!!!!!! two days without finding the solution and in the last paragraph that I will write opened the sky, put it in s-on, Greetings
Click to expand...
Click to collapse
For about some days, I flash an RUU when I was still s-off and boot-unlocked, then I flash twrp-recovery, make the adb thinks with mmcblk* (dd flash) and flash again a RUU. As you can read here.
But same boot loop problem with "Preparing Phone Storage...".
Because dd flash (the mmcblk* file) under linux and with startet recovery did not solve my bootloop / prepairing sd card problem (I had still access to my sd card with twrp-recovery! All the time!) I really think about to enable s-on
I am only scared when I do:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
How can I re-enable s-off if my os still hangs on "Preparing Phone Storage" after putting s-on and try to flash an ruu to fix my bootloop/Preparing Phone Storage problem?
I did my s-off with rumrunner.
Would be very thankfull about help.
Greetings by I_did_it_just_tmrrow
you have to relock, reset cid, and go s-on (fastboot oem writesecureflag 3) and then run the ruu.
Click to expand...
Click to collapse
THX!!!
I leave superCID and it works! I hope my signal would be fine under stock.
THX a lot!
Greetings by I_did_it_just_tmrrow

[Q] Boot-loop after flashing - Stuck at HTC screen - need help!

Hey guys, before I say something. I have really searched for help on the forum, although I clearly need help.
So I was trying to ROM the new Revelation rom and ended up in a bootloop where phone is restarting at HTC screen. I've flashed ROMs a several times with no problem whatsoever, until now.
I have 4Ext recovery and can access it without problems. Tried installing other ROMs as Cm10 with no luck.
At the time is says in bootloader.
Information about device
**** UNLOCKED ****
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Click to expand...
Click to collapse
ADB-information (when typing "adb getvar all")
version: 0.5
version-bootloader: 1.27.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main: 3.33.401.6
product: pyramid
platform: HBOOT-8260
modelid: PG5813000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4012mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 617f0a98
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
----------------------------------------------.
I've tried installing the RUU 3.33.4, (which I believe is the right firmware for me, still nothing happens really, it loads in bootloader, nothing more).
Thank you very much for any help, I'd really appreciate it.
Links with similar problems
http://forum.xda-developers.com/showthread.php?t=1600324&highlight=bricked+sensation
http://forum.xda-developers.com/showthread.php?t=2271457

Folks, the surgery went well! I fixed it.
Was looking for every possible solution and found a guide! Finally got my lovely sensation back.
1. Put the firmware PG58IMG file in root (3.33.4 - since my fastboot told me so). Let it "flash".
2. Went inside 4Ext and removed the PG58IMG file.
2. Formated and wiped dalvik and cache.
3. With 4Ext smartflash turned on I flashed CM10.1 ROM.
4. Bootet back to bootloader in 4Ext, connected my device to adb and fastboot.
5. Copied the boot.img from the CM10.1 Rom-file and put it in the same folder as adb and fastboot.
6. Typed "fastboot flash boot boot.img", let it flash.
7. Reboot, phone back and feeling good!
Hope this helps for anyone who's stuck at HTC logo screen and has S-ON. Since the S-ON kind of prevented me from changing CID etc. I tried this, which worked successfully!

NickenA said:
Hey guys, before I say something. I have really searched for help on the forum, although I clearly need help.
So I was trying to ROM the new Revelation rom and ended up in a bootloop where phone is restarting at HTC screen. I've flashed ROMs a several times with no problem whatsoever, until now.
I have 4Ext recovery and can access it without problems. Tried installing other ROMs as Cm10 with no luck.
At the time is says in bootloader.
Information about device
ADB-information (when typing "adb getvar all")
----------------------------------------------.
I've tried installing the RUU 3.33.4, (which I believe is the right firmware for me, still nothing happens really, it loads in bootloader, nothing more).
Thank you very much for any help, I'd really appreciate it.
Links with similar problems
http://forum.xda-developers.com/showthread.php?t=1600324&highlight=bricked+sensation
http://forum.xda-developers.com/showthread.php?t=2271457
Click to expand...
Click to collapse
Even I had the same problem today.
http://forum.xda-developers.com/showthread.php?t=2349395
In short..the culprit was the boot.img.
It was not being flashed even after enabling smartflash in 4ext recovery.
So basically what I did was exract boot.img from the AndroidRevolution rom and flashed it via fastboot(fastboot flash boot boot.img).
And it worked!!
Try this and report.

@NickenA
You should probably remove your imei and serial number from OP.
Sent from my Ouya

You can still flash Revelation but since you are S-ON you may need to flash the boot.img separately like you posted in your solution. So, extract the boot.img from the ROM, flash the ROM then push boot.img to your phone afterwards, and before you know it you will be enjoying the smoothest Sensation possible!

I've been having the same problem, once again, after trying to flash Revelation (and yeah, I'm also 1.27 with S-ON) so this looks like it's definitely the common denominator. Even with SmartFlash in 4EXT, the boot.img doesn't seem to flash for any ROM after attempting to flash revelation - I even tried 3 others that I know used to work just fine. I was starting to get afraid that I may have softbricked my phone, but I'll go ahead and try flashing boot.img manually. Thanks
EDIT: Worked like a charm - only needed to do fastboot flash boot boot.img
The other method with the PG58IMG is going a little overboard, IMO

Jus flash the proper boot.img
NickenA said:
Folks, the surgery went well! I fixed it.
Was looking for every possible solution and found a guide! Finally got my lovely sensation back.
1. Put the firmware PG58IMG file in root (3.33.4 - since my fastboot told me so). Let it "flash".
2. Went inside 4Ext and removed the PG58IMG file.
2. Formated and wiped dalvik and cache.
3. With 4Ext smartflash turned on I flashed CM10.1 ROM.
4. Bootet back to bootloader in 4Ext, connected my device to adb and fastboot.
5. Copied the boot.img from the CM10.1 Rom-file and put it in the same folder as adb and fastboot.
6. Typed "fastboot flash boot boot.img", let it flash.
7. Reboot, phone back and feeling good!
Hope this helps for anyone who's stuck at HTC logo screen and has S-ON. Since the S-ON kind of prevented me from changing CID etc. I tried this, which worked successfully!
Click to expand...
Click to collapse
No need to wipe/flash anything.. Most boot-loops with S-ON occur with wrong boot.img. Just use fastboot flash boot boot.img and you should be good to go.

I have the same problem... :/ (Not sure if I have to start a new thread)
I have flashed the Revelation ROM and after rebooting I'm stuck at HTC splash screen. Now after restoring my backup of my previously used CM10.1 ROM I'm stuck on splash screen too. I even tried to flash a clean CM10.1 ROM, but same problem
I'm S-OFF using hboot 1.29 and latest firmware.

BobQuentok said:
I have the same problem... :/ (Not sure if I have to start a new thread)
I have flashed the Revelation ROM and after rebooting I'm stuck at HTC splash screen. Now after restoring my backup of my previously used CM10.1 ROM I'm stuck on splash screen too. I even tried to flash a clean CM10.1 ROM, but same problem
I'm S-OFF using hboot 1.29 and latest firmware.
Click to expand...
Click to collapse
flash the boot.img of the rom manually
from cmd window the command is fastboot flash boot boot.img

rzr86 said:
flash the boot.img of the rom manually
from cmd window use the dommand is fastboot flash boot boot.img
Click to expand...
Click to collapse
I tried that as well (have I to do this even if I am S-OFF?), but still bootloop.

BobQuentok said:
I tried that as well (have I to do this even if I am S-OFF?), but still bootloop.
Click to expand...
Click to collapse
do a full wipe first and then reflash the rom
what recovery are you using?

rzr86 said:
do a full wipe first and then reflash the rom
what recovery are you using?
Click to expand...
Click to collapse
Okay, I'll do full a full wipe, a reflash and then fastboot boot.img (again).
I use 4ext. Thanks for trying to help me

BobQuentok said:
I tried that as well (have I to do this even if I am S-OFF?), but still bootloop.
Click to expand...
Click to collapse
No need for this if you're s off. Do a full wipe except sdcard and reflash.
JAM THAT THANKS BUTTON.
Happy to help.

Far_SighT said:
No need for this if you're s off. Do a full wipe except sdcard and reflash.
JAM THAT THANKS BUTTON.
Happy to help.
Click to expand...
Click to collapse
It's really strange, I have never had that problem. I rewiped (except SD) and reflashed the ROMs many times, but still bootloop.
Even restoring my backup of my CM10.1 doesn't work :/
And fastboot doesn't work, because my bootloader is *** LOCKED ***

BobQuentok said:
It's really strange, I have never had that problem. I rewiped (except SD) and reflashed the ROMs many times, but still bootloop.
Even restoring my backup of my CM10.1 doesn't work :/
And fastboot doesn't work, because my bootloader is *** LOCKED ***
Click to expand...
Click to collapse
Try using a modded hboot. Also, post your bootloader details.
JAM THAT THANKS BUTTON.
Happy to help.

BobQuentok said:
It's really strange, I have never had that problem. I rewiped (except SD) and reflashed the ROMs many times, but still bootloop.
Even restoring my backup of my CM10.1 doesn't work :/
And fastboot doesn't work, because my bootloader is *** LOCKED ***
Click to expand...
Click to collapse
with locked bootloader you are restricted to fastboot commands
what to do is flash 3.33 universal from this thread
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also a patched hboot which is unlocked
follow the instructions carefully
and before flashing check md5 sums(important)
after that try with the command again

Far_SighT said:
Try using a modded hboot. Also, post your bootloader details.
JAM THAT THANKS BUTTON.
Happy to help.
Click to expand...
Click to collapse
Sorry, totally forgot about that
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-V05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012, 18:14:34
Click to expand...
Click to collapse
I'm running latest hboot and FW from that thread: http://forum.xda-developers.com/showthread.php?t=1459767
Thanks for your help

BobQuentok said:
Sorry, totally forgot about that
I'm running latest hboot and FW from that thread: http://forum.xda-developers.com/showthread.php?t=1459767
Thanks for your help
Click to expand...
Click to collapse
are you sure fro that thread?
because you have the official hboot version
also it is locked
the patched hboot will say at the top firmware 3.33

rzr86 said:
are you sure fro that thread?
because you have the official hboot version
also it is locked
the patched hboot will say at the top firmware 3.33
Click to expand...
Click to collapse
Yeah, I'm pretty sure since this is my only source for FW/hboot files.
I'm reflashing 3.33 universal now. Which hboot should I flash? (since the one in the thread is, I guess, only an 1.27 > 1.29 update package)

BobQuentok said:
Yeah, I'm pretty sure since this is my only source for FW/hboot files.
I'm reflashing 3.33 universal now. Which hboot should I flash? (since the one in the thread is, I guess, only an 1.27 > 1.29 update package)
Click to expand...
Click to collapse
3.33 universal will take care too of the patched hboot
probably you will have 1.27.1111

[Q] [Help] [Solved] One X Stuck at Fastboot, Out of Ideas, Failed RUU

Hello, after looking into my problem all night (it is 4 a.m. now) I still cannot get my One X out of its issue.
Background to this story:
Bought this phone from a friend who had TWRP2 as the recovery, unlocked, s-on, supercid. I wanted to upgrade to a newer ROM, specifically Carbon on Jellybean 4.2.2, and I needed to update hboot to accept the newer ROM. Follow the procedures of multiple threads and they all lead me down the same path of re-locking your bootloader and let the install do the rest. However, the installer has failed multiple times (error codes 140 and 158) and I am now stuck and have no idea where to go next.
The current status of the One X is not to great. It now has a relocked bootloader, HBOOT version of 2.14.0000, A broken recovery, what seems to be a mismatched baseband, Stuck at FASTBOOT USB, no ADB, will not boot into a ROM, RUU will not complete its job (fails at sending ROM), and I am all out energy and grammar.
*Trying to re-unlock the bootloader via HTCdev will NOT unlock it.
I am stuck, (yea I am a noob). If you need anymore info, just ask.

I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.

Flashing the stock recovery only really applies when you're trying to take an OTA, it isn't required for an RUU.
Sent from my Evita

whoooops just kidding then. might worth a shot to give it a try though? I was just tossing out ideas.

brotherross said:
I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
I am not exactly sure how to do that.

I honestly don't think that's going to help you anyway.
Sent from my Evita

timmaaa said:
I honestly don't think that's going to help you anyway.
Sent from my Evita
Click to expand...
Click to collapse
Alright, gonna need to fix it later. (Recovery still broken, I assume because of the failed RUU)

Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
brotherross said:
After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).

redpoint73 said:
Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).
Click to expand...
Click to collapse
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Anytype of backup was made on the phone with TWRP, if TWRP still exists on the phone, it should be there.
I have not tried flashing TWRP back. I can try that next, can you point me in the right direction? Which version of TWRP do you recommend? (I am a noob)
"With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot." I am not aware of this, (again, noob) do I just extract the boot.img from the zip and use 'fastboot flash boot boot.img' ?

It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita

timmaaa said:
It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from . Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita
Click to expand...
Click to collapse
I may need to reiterate, that my bootloader is still locked.

MDAWG25 said:
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Click to expand...
Click to collapse
This is why you are getting errors 140 and 158. As timmaaa mentioned, you can't run an older RUU than the hboot that is already on your phone. The RUU you stated is very old, the 1.73 firmware with 1.09 hboot that came out at the phone's release. You are on hboot 2.14, so once the RUU sees that your hboot version is greater than that of the RUU (1.09), it fails.
Thye 3.18 RUU (which comes with hboot 2.14) would be what you want. BUT as already mentioned, you should not run this with S-on and SuperCID, as there is a bug with the Jellybean RUUs where this combo will brick the phone (not fixable without JTAG or new motherboard).
Follow timmaaa's steps in the previous post.
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
You might be in a catch-22 here then. As you know, you can't install custom recovery with a relocked bootloader (and S-on). You can keep trying to unlock it, but I'm not sure if that can be done if the phone can't boot.

MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
Sorry, I missed that. As Redpoint said above, you might be in a catch 22 situation here unfortunately.
Sent from my Evita

Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.

redpoint73 said:
Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.
Click to expand...
Click to collapse
I am currently not home to interface with the device physically (RDP). I should be returning around 4PM EST.
The superCID was written by the previous owner. Writing a generic CID (like HTC_001) is not an option with s-on, is it?
*Are there any RUUs that won't brick when flashing?

<Sorry for the double post but this post is different then my last>
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.

You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
MDAWG25 said:
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.
Click to expand...
Click to collapse
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita

timmaaa said:
You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita
Click to expand...
Click to collapse
Fastboot claims it wrote the recovery image, it just failed the signature check, unless it reverted, should it still be there?
I am not home to try it. I am RDPing to my computer at home, which the phone is connected to. I should be home at 4PM EST (4 hours from now).
Here is a 'getvar all'
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT246*********** (omitted for privacy)
(bootloader) imei: 359****************** (omitted for privacy)
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(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!
See anything out of the usual?
Being able to unlock the bootloader will solve all my issues, I should be able to try again when I get home.

It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita

timmaaa said:
It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
I won't post again until 4pm est, as I do not have full access to the device.
Thank you for your help, I really do appreciate it.

HTC ONE SV Request/Help

Hi,
I have an HTC ONE SV and i tried to flash a stock rom but i haven't any experience with it, and now my device is stucked in boot loading screen.
For what i understand i can install a new stock rom with fastboot because also my recovery mode is corrupted and factory reset as well because when i try to enter it remains in "Loading Recovery Mode boot screen". Could someone help me with a fix and a stock rom for:
K2_UL XC SHIP S-OFF RH
CID - 11111111
HBOOT- 2.19.0000
RADIO - 1.15.49a.00.07
Also i have S-Off as you can see from above and Bootloader Unlocked.
Thanks,
I hope that someone can help me.

What stock Rom did you chose?
Try to flash the RUU
Old.Splatterhand posted the correct link.
Gesendet von meinem HTC One SV mit Tapatalk

Fabian2103 said:
What stock Rom did you chose?
Try to flash the RUU
Click to expand...
Click to collapse
Not so fast, before you tell people to use a RUU, tell them also, how to use. Otherwise people could be lost.
mrrrdude said:
Hi,
I have an HTC ONE SV and i tried to flash a stock rom but i haven't any experience with it, and now my device is stucked in boot loading screen.
For what i understand i can install a new stock rom with fastboot because also my recovery mode is corrupted and factory reset as well because when i try to enter it remains in "Loading Recovery Mode boot screen". Could someone help me with a fix and a stock rom for:
K2_UL XC SHIP S-OFF RH
CID - 11111111
HBOOT- 2.19.0000
RADIO - 1.15.49a.00.07
Also i have S-Off as you can see from above and Bootloader Unlocked.
Thanks,
I hope that someone can help me.
Click to expand...
Click to collapse
I think it could be solved without RUU.
It seems (because of your hboot), you had already the update to Android 4.2.2? Can you tell us which software you were running? Or if you are using an european k2ul? Or any other information could be important.
Please try to use/flash this recovery for flashing a rom:
http://forum.xda-developers.com/showthread.php?p=41456540#post41456540
You have to flash with fastboot. It is made to work also on your hboot.

old.splatterhand said:
Not so fast, before you tell people to use a RUU, tell them also, how to use. Otherwise people could be lost.
I think it could be solved without RUU.
It seems (because of your hboot), you had already the update to Android 4.2.2? Can you tell us which software you were running? Or if you are using an european k2ul? Or any other information could be important.
Please try to use/flash this recovery for flashing a rom:
http://forum.xda-developers.com/showthread.php?p=41456540#post41456540
You have to flash with fastboot. It is made to work also on your hboot.
Click to expand...
Click to collapse
I don't really know if i had the update to Anroid 4.2.2 in Fast Boot Menu it sais OS-3.03.401.1? does that help you? and i think it's an european k2ul. After i flash this recovery image? what do i do next? i mean i want to revert the phone to stock but like i said the Recovery menu dosn't load is there any way to flash the recovery image and then install a stock rom through flasboot commands? i have found this post http://forum.xda-developers.com/showthread.php?t=2277112 and it sais that it's possible but i didn't have the recovery image, now i do but i'm still missing a stock rom that would work with my device.

You had an older recovery, which don't work with your hboot.
Flash the recovery i have linked for you with fastboot, then you should be able to enter recovery.
From recovery you can flash the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip from here. It's a stock rom, with the same software number as you have had.

old.splatterhand said:
You had an older recovery, which don't work with your hboot.
Flash the recovery i have linked for you with fastboot, then you should be able to enter recovery.
From recovery you can flash the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip from here. It's a stock rom, with the same software number as you have had.
Click to expand...
Click to collapse
Thank you, i will try this out and i will let you know if i make any progress

mrrrdude said:
Thank you, i will try this out and i will let you know if i make any progress
Click to expand...
Click to collapse
old.splatterhand said:
You had an older recovery, which don't work with your hboot.
Flash the recovery i have linked for you with fastboot, then you should be able to enter recovery.
From recovery you can flash the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip from here. It's a stock rom, with the same software number as you have had.
Click to expand...
Click to collapse
Hi,
The phone now boots into recovery so i'm on the right track thanks to you, but i don't know how to flash the stock rom? what do i need to do? i put the stock on a sd card and plug it in through an external cable and a card reader but i don't seem to find where is the file? Do i need to flash the boot.img from the zip file too? or rename the zip file somehow in the sd card?

You have to flash it from recovery.
First go (in recovery) to "Wipe"-> "Advanced Wipe" and wipe everything but sd card and internal sd card.
Put the rom on your sd card, choose "Install" and navigate to the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip.
Choose it and confirm with"Swipe to flash".
As you are S-off, you usually don't need to flash boot.img afterwards.
When flashing is done, Reboot.
Wait some minutes, first boot takes some time.

old.splatterhand said:
You have to flash it from recovery.
First go (in recovery) to "Wipe"-> "Advanced Wipe" and wipe everything but sd card and internal sd card.
Put the rom on your sd card, choose "Install" and navigate to the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip.
Choose it and confirm with"Swipe to flash".
As you are S-off, you usually don't need to flash boot.img afterwards.
When flashing is done, Reboot.
Wait some minutes, first boot takes some time.
Click to expand...
Click to collapse
It fails to wipe with this error: E:Unable to mount internal storage. do i need to place the sd card inside the phone?

Hmmm, strange. Yes, put your sd card into your phone. If the rom is there, you can't find it, if its not in the phone.
Go on and try to flash.

old.splatterhand said:
Hmmm, strange. Yes, put your sd card into your phone. If the rom is there, you can't find it, if its not in the phone.
Go on and try to flash.
Click to expand...
Click to collapse
I found my rom on the sd card but after a few seconds the installing fails because of the same error "unable to mount internal storage" is there a way to flash this rom through fastboot?

No.
Seems, something got corrupted on your device.
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)

old.splatterhand said:
No.
Seems, something got corrupted on your device.
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 2.19.0000
version-baseband: 1.15.40a.00.07
version-cpld: None
version-microp: None
version-main:
version-misc: XC SHIP S-OFF
meid:
product: k2_ul
platform: HBOOT-8930
modelid: PL8010000
cidnum: 11111111
battery-status: good
battery-voltage: 3909mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0049fc265e
hbootpreupdate: 11
gencheckpt: 0

Ok, i see what i wanted to see.
Because the rom will not flash, you should really try to flash the RUU.
To do that, you need to downgrade your hboot.
Please read and follow this guide, to downgrade hboot and flash the RUU afterwards.

old.splatterhand said:
Ok, i see what i wanted to see.
Because the rom will not flash, you should really try to flash the RUU.
To do that, you need to downgrade your hboot.
Please read and follow this guide, to downgrade hboot and flash the RUU afterwards.
Click to expand...
Click to collapse
Do i really need to change the supercid to downgrade the hboot as mentioned in the tutorials? because i can't do that because my device is only recognize in fastboot. when i hit the command adb devices my serial number is not shown. but in fastboot device is. or if i use command like su in adb i get an error message like this "error: device not found"

mrrrdude said:
Do i really need to change the supercid to downgrade the hboot as mentioned in the tutorials?
Click to expand...
Click to collapse
Supercid is fine, no need to change it.

old.splatterhand said:
Supercid is fine, no need to change it.
Click to expand...
Click to collapse
It WORKED LIKE A CHARM! THANK YOU! you are a real life saver! I could not have done it without you, thanks allot!

mrrrdude said:
It WORKED LIKE A CHARM! THANK YOU! you are a real life saver! I could not have done it without you, thanks allot!
Click to expand...
Click to collapse
Nice, so have fun with your new born device :laugh:

old.splatterhand said:
Nice, so have fun with your new born device :laugh:
Click to expand...
Click to collapse
Thank you, i will definitly

[Q] Soft bricked HTC One S (S4).. Which RUU to use? Have Fastboot Info

Hi everyone..
I am sitting on a One S which has an unlocked bootloader, is not S-off, Hboot 2.15.
Previously was rooted and had Viper Rom installed 3.1, experienced lot of random reboots, tried to go S-OFF with rumrunner and moonshine, without it working.
Tried to return to a nandroid backup (TrickDroid 9.0) but now system is not responding and results in a reboot after 1-2 minutes after rom is booted.
I would like to return to Stock Rom with a RUU, but I can't seem to find the right one and I really need some help..
Even if I found the right one I don't know how to install it because phone keeps rebooting and fastboot doesn't seem to work on Win 8.
HELP!!

Okay. I got fastboot to work on my girlfriends computer and windows 7..
I got the following from running "fastboot getvar all":
Code:
<bootloader> version: 0.5
<bootloader> version-bootloader: 2.15.0000
<bootloader> version-baseband: 1.15.50.05.29
<bootloader> version-spld: None
<bootloader> version-microp: None
<bootloader> version-main:
<bootloader> version-misc: PVT SHIP S-ON
<bootloader> serialno: H*************
<bootloader> imei: 35***********
<bootloader> product: vle
<bootloader> platform: HBOOT-8960
<bootloader> modelid: PJ4010000
<bootloader> cidnum: T-MOB101
<bootloader> battery-statis: good
<bootloader> battery-voltage: 3867mV
<bootloader> partition-layout: Generic
<bootloader> security: on
<bootloader> buildmode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> cimmitno-bootloader: dirty-64bedd38
<bootloader> hbootpreupdate: 11
<bootloader> gencheckpt: 0
Which RUU should I get my hands on?
And do I need to run any fastboot commands before I try installing the RUU?

same
i've ****d mine to lmao

I tried all the RUU's on the RUU page from one of the sticky posts that had anything to do with T-mobile (since the device came with that as a splash screen) or Europe editions without any positive outcome.
I received Error 130 or 131 at all RUU installation that had either "Europe" or "TMO" in them..
I will keep on trying to find the right RUU, but I would really appreciate if someone had the answer and spoke up..
Thanks!

Hammerbak said:
I tried all the RUU's on the RUU page from one of the sticky posts that had anything to do with T-mobile (since the device came with that as a splash screen) or Europe editions without any positive outcome.
I received Error 130 or 131 at all RUU installation that had either "Europe" or "TMO" in them..
I will keep on trying to find the right RUU, but I would really appreciate if someone had the answer and spoke up..
Thanks!
Click to expand...
Click to collapse
I have not seen a RUU that had a radio version that high. The highest version I have seen is 1.13. I think that's the problem.

Is there no way to downgrade the radio?
I mean I have access to fastboot and TWRP recovery..?
Maybe by using a nand backup or so?
Sent from my C6603 using xda app-developers app

Hammerbak said:
Is there no way to downgrade the radio?
I mean I have access to fastboot and TWRP recovery..?
Maybe by using a nand backup or so?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
---------- Post added at 09:47 AM ---------- Previous post was at 09:38 AM ----------
808phone said:
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
Click to expand...
Click to collapse
Do a search on your radio version: google 1.15.50.05.29
Are you in the US? US T-Mobile??
Anyway, this was the closest info I found:
http://forum.xda-developers.com/showthread.php?t=2520005

808phone said:
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
---------- Post added at 09:47 AM ---------- Previous post was at 09:38 AM ----------
Do a search on your radio version: google 1.15.50.05.29
Are you in the US? US T-Mobile??
Anyway, this was the closest info I found:
http://forum.xda-developers.com/showthread.php?t=2520005
Click to expand...
Click to collapse
Well, no I'm not in the US. I live in Denmark.
The phone however was bought in Germany 2 years ago, and was delivered from T-mobile I think.
I will give this a try.
However the reason I want to get back to STOCK is due to getting S-OFF.
If I can get the phone working as it is now with TrickDroid 9.0 ROM that would also suffice. At least for quite some time.
The problem I have with the ROM is that "system" stops responding on boot.
I am thinking that this problem could be due to kernel incompatibility because the phone had the Viper One ROM before, which I think flashed another kernel together with the ROM.
Could this be the problem and could it be solved with flashing a new kernel?
However is it possible to flash a kernel without the use of the recovery?
I can't mount the internal memory and the phone has no slot for a SD card
Again.. Thanks!

I would post here:
http://forum.xda-developers.com/showthread.php?t=2110195&page=183
This seems to be the place to get help.
Did you do an md5 on the files before flashing? Do you remember flashing boot.img from TrickDroid?

808phone said:
I would post here:
http://forum.xda-developers.com/showthread.php?t=2110195&page=183
This seems to be the place to get help.
Did you do an md5 on the files before flashing? Do you remember flashing boot.img from TrickDroid?
Click to expand...
Click to collapse
Already did post in there, with no responses so far..
Well I had TrickDroid 9.0 running fine before I updated to Viper One ROM, and this was when problems started happening.
Then I went back with a NAND restore from recovery..
I don't remember flashing the boot.img, as I thought that followed along when I flashed the TrickDroid ROM, but since I think that doing a NAND recovery, doesn't bring a long the kernel I guess that if I installed the kernel from TrickDroid I could get the phone working with this.. What do you think?
Which file contains the kernel..? Is that the boot.img?
Once again, thanks for putting an interest in this post and helping me out! You're a lifesaver so far!

If you are not s-off then you need to flash the boot.IMG.
If you didn't do this, then could be the problem. AFAIK the boot.IMG contains the kernel.
http://forum.cyanogenmod.com/topic/79408-fastboot-flash-boot-bootimg/
Here's another link that might help.
http://www.guidingtech.com/12705/solve-boot-loop-htc-one-x-custom-rom/

Latest radio for WWE devices was 1.15 and it's not a problem you have that. For me it proved to be better than 1.20 which is coming from the leaked firmware 2.16 so it's unofficial. You can't flash a different radio unless you're S-Off or have a lower hboot (1.09 or below) which you don't have. Stay with 1.15 it is OK
If you're S-On you MUST flash the ROM kernel EVERY time after you flash a ROM. This is done by extracting the boot.img from the ROM ZIP and flash it via fastboot command (fastboot flash boot boot.img). Also no nandroid restore will flash back the kernel from the backup since it is not possible to write to that partition if you're S-On
Now, what options do you have... First you must decide WHICH ROM do you want on your phone. If it's latest Viper you would like, fine, it's a very good ROM, stable and with lot of customization and support. What you should do is like this:
1. Download the ROM, save it on your pc and check MD5 sum
2. Extract the boot.img from it. This is a little bit tricky since Viper use an Aroma installer and it's made for both 2.15 and 2.16 hboots. So the boot.img is not in the ususal place in the zip file (that is the root of it) and also it is not called plain boot.img. It is located somewhere in the ZIP folders (sorry but I don't use Viper and don't have the zip at hand to tell you exactly where to look) and it should be named something like boot_2.15.img (or something like this). Look into the ZIP and try to locate this file, you should find 2 files named similar one with 2.15 and one with 2.16 in their names. The one you need is the one containing 2.15 in the name. Extract that one on your pc
3. I assume that you have ADB/fastboot working and you can launch the fastboot command from any directory on your pc (it's in the PATH). If not it could be that command will not work. In this case copy the extracted boot_2.15.img in the folder where you have fastboot (usually Android-SDK/platform-tools) and open a command prompt there
4. Restart the phone in recovery and mount the USB storage from it. You should see it after a while on your PC. Don't worry if it doesn't appear instantly, but it shouldn't take more than 1-2 min. Eventually unplug the phone and plug it again into USB. If you cannot mount the USB and have it accessible from PC we have to try the ADB Sideload but first we'll see if you get there and we need this. For now I presume you can mount USB and you can access it from PC. OK, now copy the ROM ZIP on your sdcard in a folder you'll remember
5. Now flash the ROM in recovery as you normal do and wipe cache/dalvik when prompted to
6. Restart your phone in bootloader and plug it in the USB. Go to fastboot and on screen you should see "FASTBOOT USB". Issue on the pc in the opened command prompt the command "fastboot devices". It should return the device id and that's the proof the device is recognised by the fastboot command. If you have returned an blank response or something like an error, check if drivers and everything on your PC is installed properly for fastboot to work
7. If "fastboot devices" returns something (should look like "FA2BGW... fastboot") then you're good to go. Issue from the same command prompt the command "fastboot flash boot boot_2.15.img" (replace boot_2.15.img with the actual name of the file you have extracted from the ROM zip)
8. Restart to system
At this point you should have Viper 3.1.0 flashed and working. Check and setup the ROM then you may want to download the 2 OTA updates and install them to get to the latest 2.1.3
let us know how it went and where are you stuck. Note every error message you might get and better ask first than be sorry later...
Good luck

Rapier said:
Latest radio for WWE devices was 1.15 and it's not a problem you have that. For me it proved to be better than 1.20 which is coming from the leaked firmware 2.16 so it's unofficial. You can't flash a different radio unless you're S-Off or have a lower hboot (1.09 or below) which you don't have. Stay with 1.15 it is OK
Click to expand...
Click to collapse
Could you maybe provide a link to the WWE RUU that has the 1.15 Radio? I have been searching almost everywhere unable to find it and I would really like to go back to stock so that I can use rumrunner or moonshine to get S-off and avoid all the hassle that I have right now.. xD
Rapier said:
If you're S-On you MUST flash the ROM kernel EVERY time after you flash a ROM. This is done by extracting the boot.img from the ROM ZIP and flash it via fastboot command (fastboot flash boot boot.img). Also no nandroid restore will flash back the kernel from the backup since it is not possible to write to that partition if you're S-On
Now, what options do you have... First you must decide WHICH ROM do you want on your phone. If it's latest Viper you would like, fine, it's a very good ROM, stable and with lot of customization and support. What you should do is like this:
1. Download the ROM, save it on your pc and check MD5 sum
2. Extract the boot.img from it. This is a little bit tricky since Viper use an Aroma installer and it's made for both 2.15 and 2.16 hboots. So the boot.img is not in the ususal place in the zip file (that is the root of it) and also it is not called plain boot.img. It is located somewhere in the ZIP folders (sorry but I don't use Viper and don't have the zip at hand to tell you exactly where to look) and it should be named something like boot_2.15.img (or something like this). Look into the ZIP and try to locate this file, you should find 2 files named similar one with 2.15 and one with 2.16 in their names. The one you need is the one containing 2.15 in the name. Extract that one on your pc
3. I assume that you have ADB/fastboot working and you can launch the fastboot command from any directory on your pc (it's in the PATH). If not it could be that command will not work. In this case copy the extracted boot_2.15.img in the folder where you have fastboot (usually Android-SDK/platform-tools) and open a command prompt there
4. Restart the phone in recovery and mount the USB storage from it. You should see it after a while on your PC. Don't worry if it doesn't appear instantly, but it shouldn't take more than 1-2 min. Eventually unplug the phone and plug it again into USB. If you cannot mount the USB and have it accessible from PC we have to try the ADB Sideload but first we'll see if you get there and we need this. For now I presume you can mount USB and you can access it from PC. OK, now copy the ROM ZIP on your sdcard in a folder you'll remember
5. Now flash the ROM in recovery as you normal do and wipe cache/dalvik when prompted to
6. Restart your phone in bootloader and plug it in the USB. Go to fastboot and on screen you should see "FASTBOOT USB". Issue on the pc in the opened command prompt the command "fastboot devices". It should return the device id and that's the proof the device is recognised by the fastboot command. If you have returned an blank response or something like an error, check if drivers and everything on your PC is installed properly for fastboot to work
7. If "fastboot devices" returns something (should look like "FA2BGW... fastboot") then you're good to go. Issue from the same command prompt the command "fastboot flash boot boot_2.15.img" (replace boot_2.15.img with the actual name of the file you have extracted from the ROM zip)
8. Restart to system
At this point you should have Viper 3.1.0 flashed and working. Check and setup the ROM then you may want to download the 2 OTA updates and install them to get to the latest 2.1.3
let us know how it went and where are you stuck. Note every error message you might get and better ask first than be sorry later...
Good luck
Click to expand...
Click to collapse
Thanks.
There's definitively a lot I will have to work with.
As far as I know I can't mount the Internal memory over the USB while in recovery (I have no SD-card slot in my One S), however I will check it out later and get back to you.
I would very much like to get back to TrickDroid first of all, since it's the ROM already installed on the device I think I only have to flash the kernel and then it should be working.
If it is so I can then put Viper One ROM on the phone and flash that using the procedure that you described above.
However I am unable to find the TrickDroid 9.0 ROM since the ROM seems to have gone out of development.. Or at least that is my guess. If I'm lucky I have it somewhere on my old laptop and can get the boot.img from there. And as well I know how fastboot and ADB works, I just need the commands that I will be using.
I will try to find the TrickDroid boot.img and flash that using fastboot and then I will get back to you.
If I don't find it, is it then possible that another kernel might support TrickDroid (like ElementalX or whatever it is called)?

Hammerbak said:
Could you maybe provide a link to the WWE RUU that has the 1.15 Radio? I have been searching almost everywhere unable to find it and I would really like to go back to stock so that I can use rumrunner or moonshine to get S-off and avoid all the hassle that I have right now.. xD...
Click to expand...
Click to collapse
HERE is a list with all RUUs, taken from dev section. Find what you may need
Hammerbak said:
...As far as I know I can't mount the Internal memory over the USB while in recovery (I have no SD-card slot in my One S), however I will check it out later and get back to you...
Click to expand...
Click to collapse
No, you don't have a card slot but you should be able to mount the internal memory as an sdcard
Hammerbak said:
If I don't find it, is it then possible that another kernel might support TrickDroid (like ElementalX or whatever it is called)?
Click to expand...
Click to collapse
Yes, you could flash ElementalX but that was gone further to support the newer ROMs like Viper 3.x. I think it's a better idea to flash Buletproof kernel (also by flar2) that was compatible with older Sense ROMs. It similar with Elemental but more stable and close to stock with some added goodies

Sounds good. I would try and flash that boot.img. I had a similar problem but was able to find an RUU that worked.
Maybe you just missed this part (or not)
Reboot into bootloader
Go into fastboot mode
fastboot flash boot boot.img
fastboot erase cache
Reboot
---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------
I should point out that I did NOT have success with ViperOneS. It looks awesome and did lots of things well except hold onto calls! Every time I would make a call, it would hang up for no reason. This problem apparently doesn't happen to everyone, but it did to me.
BTW: I have CM11 running so smoothly on my HTC One S. Pretty much all of my major issues are fixed. Only the limitations of google remain.

Rapier said:
HERE is a list with all RUUs, taken from dev section. Find what you may need
Click to expand...
Click to collapse
I tried all the "Europe" and "TMO" version already.
Will try the WWE versions in the coming days if I get time. However it doesn't look like there is no 1.15 Radio ones..
Rapier said:
You could flash ElementalX but that was gone further to support the newer ROMs like Viper 3.x. I think it's a better idea to flash Buletproof kernel (also by flar2) that was compatible with older Sense ROMs. It similar with Elemental but more stable and close to stock with some added goodies
Click to expand...
Click to collapse
As far as I could read on the bulletproof kernel page, it requires S-OFF if you're going to use v. 2.x+. I guess I would have to use the version just before 2.0 which is 1.4?
I downloaded the 1.4 version and it contains 4 folders:
boot
kernel
META-INF
system
Is the boot image that is found in the boot folder the only file I will need to flash to install the bulletproof kernel 1.4? Installation on the page said I would need to flash it from recovery, but I am unable to go into recovery. Aka I found a huge problem. Since I tried to install some RUU's I am no longer able to get into recovery because I locked the bootloader..
What do I need to do?
I would suppose that I needed to flash the boot.img from the bulletproof kernel, while being in fastboot, but I don't know how that works with the bootloader being "relocked" so I will stand by for an answer..
Another thing I could do would be to go to the HTCDev page and try to unlock the bootloader again..
Which would you recommend?

Hammerbak said:
I tried all the "Europe" and "TMO" version already.
Will try the WWE versions in the coming days if I get time. However it doesn't look like there is no 1.15 Radio ones..
As far as I could read on the bulletproof kernel page, it requires S-OFF if you're going to use v. 2.x+. I guess I would have to use the version just before 2.0 which is 1.4?
I downloaded the 1.4 version and it contains 4 folders:
boot
kernel
META-INF
system
Is the boot image that is found in the boot folder the only file I will need to flash to install the bulletproof kernel 1.4? Installation on the page said I would need to flash it from recovery, but I am unable to go into recovery. Aka I found a huge problem. Since I tried to install some RUU's I am no longer able to get into recovery because I locked the bootloader..
What do I need to do?
I would suppose that I needed to flash the boot.img from the bulletproof kernel, while being in fastboot, but I don't know how that works with the bootloader being "relocked" so I will stand by for an answer
Click to expand...
Click to collapse
OK, so it's like this. You're right, I forgot that some kernel zips don't contain the boot.img itself, instead they extract the boot.img from your current ROM and repack it, that's why it is required to have S-Off because this operation can be made only in recovery (or by repacking the kernel on your pc but that's more complex and don't want to go through it since it requires Linux and other things). You should find an older kernel ZIP like the 1.4 you mentioned and use the boot.img from it.
Also you should unlock the device again at HTC dev to be able to flash the kernel in fastboot. After unlocking you can re-flash TWRP recovery and If I was you I would rather flash Viper 3.x ROM from recovery then flash the boot.img from it in fastboot, instead of trying to get a boot.img that works with TrickDroid
Now to the radio...latest US radio was 1.11 and latest Europe radio was 1.13. That's why you could not find 1.15 radio in those RUU. Version. 1.15 should be in a WWE RUU but I don't know exactly in which one. Initially I had 1.09es radio and only after changing to another hboot I was able to flash a different one. And I've upgraded my radio via tecardo's zip flashable in recovery since my hboot allows it even if I am not S-Off. There were some older hboots like 1.09 and 1.06 that allows almost everything a S-Off will allow (flashing radios and kernels from recovery that is)
If you're at this point (almost stock) I would try to flash a stock RUU (any stock RUU) and try to get S-Off first. If you previously tried to get S-Off while you were on Viper...that could be the problem. I heard many people having issues or not able to properly S-Off due to the fact they were not on stock ROM. Maybe now it's a good point to start over since you don't have anything to loose anyway. Then the things will be much easier, you could upgrade your radio from the ZIP directly, without the need to flash a RUU for that. If you don't want to try that again, just follow my advice above: unlock the bootloader again on HTC dev site, flash TWRP recovery then flash Viper 3.x and it's kernel in fastboot. You'll end up with an S-On device running on 2.15 firmware and latest Viper. Only downside to this is that you will be stuck with your current radio (the one from the RUU you flashed). You could even flash an AOSP KK ROM if you like, the same way

Rapier said:
OK, so it's like this. You're right, I forgot that some kernel zips don't contain the boot.img itself, instead they extract the boot.img from your current ROM and repack it, that's why it is required to have S-Off because this operation can be made only in recovery (or by repacking the kernel on your pc but that's more complex and don't want to go through it since it requires Linux and other things). You should find an older kernel ZIP like the 1.4 you mentioned and use the boot.img from it.
Also you should unlock the device again at HTC dev to be able to flash the kernel in fastboot. After unlocking you can re-flash TWRP recovery and If I was you I would rather flash Viper 3.x ROM from recovery then flash the boot.img from it in fastboot, instead of trying to get a boot.img that works with TrickDroid
Now to the radio...latest US radio was 1.11 and latest Europe radio was 1.13. That's why you could not find 1.15 radio in those RUU. Version. 1.15 should be in a WWE RUU but I don't know exactly in which one. Initially I had 1.09es radio and only after changing to another hboot I was able to flash a different one. And I've upgraded my radio via tecardo's zip flashable in recovery since my hboot allows it even if I am not S-Off. There were some older hboots like 1.09 and 1.06 that allows almost everything a S-Off will allow (flashing radios and kernels from recovery that is)
If you're at this point (almost stock) I would try to flash a stock RUU (any stock RUU) and try to get S-Off first. If you previously tried to get S-Off while you were on Viper...that could be the problem. I heard many people having issues or not able to properly S-Off due to the fact they were not on stock ROM. Maybe now it's a good point to start over since you don't have anything to loose anyway. Then the things will be much easier, you could upgrade your radio from the ZIP directly, without the need to flash a RUU for that. If you don't want to try that again, just follow my advice above: unlock the bootloader again on HTC dev site, flash TWRP recovery then flash Viper 3.x and it's kernel in fastboot. You'll end up with an S-On device running on 2.15 firmware and latest Viper. Only downside to this is that you will be stuck with your current radio (the one from the RUU you flashed)
Click to expand...
Click to collapse
Okay. Just to put in aspect I have the following choices:
Try to gain S-OFF as phone is now with rumrunner or moonshine
Try to get TrickDroid to work by flashing a kernel that is supported
Try to flash Viper and it's kernel from fastboot
If I try to gain S-OFF using rumrunner, do I still need to unlock the bootloader through HTCDevs?
I will try the first mentioned choice first, since gaining S-OFF would ease stuff up quite a bit.
If I can't gain S-OFF using rumrunner I will try to use moonshine.
If that doesn't work either I will be happy with just getting TrickDroid 9.0 to work as a starter.. Step by step procedure to actually gaining a working device firstly.
Then I can start thinking of how to get Viper One working after that or going back to stock to try the S-OFF methods once again.
My list of intentions is to:
Get S-OFF - whether it works or not
Getting the device to be booted and actually perform phone calls and etc.
Research the method and possibilites of getting back to stock to try S-OFF again.
Plan further upgrades to either new ROMs and/or Kernels

I'm pretty sure rumrunner and moonshine.io are similar. hmmmm after re-reading... you might have to be boot loader unlocked.
"WHAT RUMRUNNER CAN DO FOR YOU:
S-OFF Your HTC device
Unlock your bootloader (devices that are blocked by htcdev only, e.g. Verizon HTC One)"
Hard to tell. I know that someone got their ONE S - S-OFF using moonshine and they did NOT unlock the boot loader.
Good luck.

808phone said:
I'm pretty sure rumrunner and moonshine.io are similar. hmmmm after re-reading... you might have to be boot loader unlocked.
"WHAT RUMRUNNER CAN DO FOR YOU:
S-OFF Your HTC device
Unlock your bootloader (devices that are blocked by htcdev only, e.g. Verizon HTC One)"
Hard to tell. I know that someone got their ONE S - S-OFF using moonshine and they did NOT unlock the boot loader.
Good luck.
Click to expand...
Click to collapse
Okay.
Is was just about to write what you put in your edit. Haha lazy me.. xD
Well I guess as a starter I can go and unlock the bootloader, flash a recovery and try rumrunner.
When I get the recovery working I can start to plan what to do next
EDIT:
Bootloader is unlocked now and for some reason recovery wasn't removed
so I have unlocked bootloader and have a working recovery now.
Will try rumrunner S-OFF now..