Database Info

CID error after flash generic rom, stuck in boot loader

Right, had desire s from three, alpharevx'd it installed clockwork mod, flashed eng hboot. Tried to flash RUU 1.47 europe on it, and it started to work and go through process, updated radio fine, then came up with CID error. No option to do anything but exit. Now I have a desire s that will boot into Bootloader, which has now s-on'd itself and upgraded to 0.98.0002.
Only method of comms seems to be via fastboot.
Now i cant flash the h3g one cos its too low a bootloader version, and i cant upgrade to a newer version cos one don't exist. Can anyone come up with a solution please??
Cheers.

What does HBOOT screen say (in full)?
Are you still able to get into recovery? If yes, then have you tried loading a custom ROM onto the SD card and simply flashing that using the flash zip from sd card option of CWM (clock work mod)?

Unfortunately I am unable to get into recovery, only bootloader, nothing else works. Hboot is displaying a security error at the top highlighted in pink, followed by the version number as described

You should have stuck with the alpharev hboot, which does not allow itself to be overwritten by RUU installs.
Anyway, you need to:
- install hboot 0.980000 (so you can run alpharevx again and get S-OFF)
- run alpharevx and reinstall CWM at the end
- DO NOT install the eng hboot
- flash whatever rom whichever way you want. Your hboot is safe
Follow the instructions on:
http://forum.xda-developers.com/showthread.php?t=1187231

How can I run alpharevx when I can only boot into bootloader tho?

Try running it while in bootloader. Never tryed it that way, but I'm pretty sure it only needs the USB comms to be up, same as adb. Which they should be anyway in bootloader...

Have you tried to re-setup your phone by executing one of the RUU.exe?

k, as i expected, with no access to adb in bootloader mode, i am unable to do anything. Remember, i only have bootloader to work from. I don't eve3n have a recovery partition installed, it just comes back to bootloader whatever i choose, well, bootloader and fastboot anyway.

yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/

What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...

If all else fails s-off with xtc clip then flash custom rom
Sent from my HTC Desire S using XDA Premium App

Have you tried to use the original RUU for your phone/network? I'm not sure if it would take care of the CID error.
Any of these:
http://forum.xda-developers.com/showthread.php?t=1002506

Clivectmob said:
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
Click to expand...
Click to collapse
I do not expect this to work, but you said you are able to get into recovery, correct?
Well, I would try to enter fastboot mode and try to flash cwm via fastboot -> fastboot flash recovery XXXXXXXX.img
Correct (windows) drivers installed?
Edit:
lowveld said:
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
Click to expand...
Click to collapse
Good suggestion! Try this one first.

The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!

I haven't run a RUU in years, but I think that when you run it on a windows machine, it extracts a bunch of files to a directory. Cancel the process, find the directory, find th PG88... in the directory... You get the drift.

Clivectmob said:
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
Click to expand...
Click to collapse
It is not relevant which network you are using !!! Just try newest RUU to get control over your phone again in the first place!
Even if you don't get any network access after setup newest RUU you will definitely be abte to execute alpharevx again, flash cwm and flash any stuff you want to.

just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)

Clivectmob said:
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Click to expand...
Click to collapse
I guess that means you tried flashing recovery via fastboot?
Then concentrate on our RUU-suggestions.

Yes, as i said, flashed via fastboot, and i already explained that i cant up/down grade via ruu method because of bootloader version. I can't think of a way out of this as it stands. The only thing that may work is doing it via the p88img method with my original 3uk rom, but i cant find it in my temp files, searched everywhere for it. I've seen it's location posted on here before now, and i've searched it to death and can't seem to find it now

I'm going to extract and upload your 3GUK-PG88*.img although I think you'll need an newer one. Just a few minutes of patience.

[Q] stuck on splash-screen

Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow

onemanshow85 said:
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
Click to expand...
Click to collapse
Hi,
2 things you can try.
1.Run a GingerBread RUU.
Look HERE
2.If that works,try s-off.
Look HERE
Then,you could change firmwares and do whatever you like.

Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
edit: I downloaded and executed a RUU that apearantly wasn't compatible with the phone. I'm guessing it removed whatever ROM was installed, but didn't install the ROM from the RUU.
I also followed step 3; RUU to restore stock up to the part of relocking the bootloader. I didn't come any further cause I can't find the right RUU.
the phone now only boots into bootloader with "security warning" displayed below "relocked".
I'm guessing, if I find the correct RUU with gingerbread, things will be okay again.
on a sidenote, does a RUU install also returns the recovery to stock?

onemanshow85 said:
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
Click to expand...
Click to collapse
Hi,
RUU does not matter too much as long as it is Europe and GB.
If you can find a dutch tmo ,then even better.
No harm will come if it is the wrong one.
It will only throw up an error.
This will at least get a ROM on your phone,so that you can s-off .
Revolutionary is the easiest way to s-off.

so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?

onemanshow85 said:
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
Click to expand...
Click to collapse
Hi,
The closer the match,the more chance of success.
But close will do.
Yes,with the same radio.

finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?

onemanshow85 said:
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
Click to expand...
Click to collapse
Hi,
Try the European RUU with the 10.14 radio that matches yours.
Add your CID in the PG58IMG text file.
Make sure you have the phone in fastboot when you attach your USB cable(it should say "fastboot USB"),and start running the RUU from your PC.

http://db.tt/A7lS7PaD
Here is a link to 4ext touch recovery as a IMG. http://db.tt/KFKpcrhB and here is a pg58img.zip. put the zip file onto the sdcard and boot to boot loader. It will hopefully flash the recovery. If not fast boot flash the IMG. Once you have the recovery installed enable smart flash and then flash the roms. Hopefully that will work for you
Sent from my HTC Sensation using xda premium

tnx for the files.
I tried the suggestions you made but flash from sdcard doesn't work; it checks the file once and doesn't do anything after it.
when I try to flash either one of the files through fastboot I get signature verification fail.
my bootloader says RELOCKED, I got that after following step 3.1 in the RUU flash guide to return to stock. I don't know if this is blocking anything from being flashed with the nasty signature notifications?
also, most like because nothing is installed on my device, when I plug in the USB cable when it's turned off, it automatically swithces on displaying SECURITY WARNING below RELOCKED.

Damn, wasn't fast enough. I'm not sure what the best way to approach this is. Either attempt to full s-off the device with revolutionary/ jupuntobear, or re-unlock your boot loader with htcdev, then fastboot flash the recovery. Then install the rom. Then run jupuntobear to full s-off
Sent from my HTC Sensation using xda premium

heavy_metal_man said the right thing. First focus on unlocking it on hTCdev.com and afterwards, flash a 4Ext Recovery to make things easyer. Then put the device in bootmenu (not in the Graphic shell) and attach a USB, start any Official European RUU that is Gingerbread - with 1.50 in the numbers.

an update
I managed to get it unlocked again with htcdev.com. After that I flashed 4EXT recovery, succesfully.
only thing now I need to do is installing a ROM. I tried the following without succes so far:
with RUU
I can't find a dutch RUU for TMO with radio 10.14.9035 anywhere so I tried the closest match possible, a german one. through the .exe method I get incompatibility errors. So I extracted the ROM/.zip, added my CID and tried with SDcard flash and fastboot flash, both unsuccesfull. Hboot checks the file twice and does nothing afterwards, and fasboot prompts the message "FAILED (remote ** unknown fail)"
Universal firmware package to make sure I'm on 3.32, so I can install ARHD 6.7.2 or any other ICS rom
I took one from http://forum.xda-developers.com/showthread.php?p=21711154#post21711154.
I get the same errors as when I was trying to flash the ROM.zip from the RUU, both with sdcard flash and fastboot flash.
a random Gingerbread ROM
I found this GB ROM http://forum.xda-developers.com/showthread.php?t=1226564.
I installed it through EXT4. after a reboot it's stuck in a bootloop. No splash screen is shown however, it get's to the withe-field-green-HTC-screen and reboots after, showing the same.
I don't understand what's wrong. I got a good recovery now and the bootloader is unlocked. For some reason the ROM's I tried are incompatible with the current state of the device and I can't figure out why. are dutch T-mobile branded phones so tough to crack or what?
also, after a certain step wich I can't remember, my bootloader doesn't display a radio anymore.
Current bootloader:
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
EDIT: I would be less restricted in my actions if the damn thing were to be S-OFF. is there any way to get get S-OFF through bootloader/fastboot? All the S-OFF methods and utillities I found so far need the device to have a ROM running.

SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help

onemanshow85 said:
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
Click to expand...
Click to collapse
Glad you got sorted pal and thanks for letting us know

Stuck at boot loop???

Hi, i had a S4 which got a broken screen and costs too much to fix a the moment so i brought a Telstra HTC ONE XL off a friend for $100.
I do like the phone but was over the 4.2.1 software as used to the 4.3 on the S4 which i rooted and put on CM10.
I tried with this phone to put on the nightly cm 10.3 but i hit a problem ,when install the nightlies it boot loops and when i try install the stable 10.1 it fails with an error which i do belive is to do with my V2 hboot.
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial
I have unlocked through htcdev and rooted it ok.
Im stuck now though as i pressed backup current original rom which turns out its not.
The phone details are
CID TELST001
Model: HTC ONE XL TELSTRA
If someone can tell where to either find the newest telstra rru for my phone or how to update my hboot so i can use cm10?
My phone is pretty useless at the moment

stueee said:
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
Click to expand...
Click to collapse
Where are you getting CM from (link it) and what is the file named? CM will typically have the phone's code name (EVITA) in the file name. If the code name ENDEAVORU is in the file name, it is in fact for the wrong device, as the ENDEAVORU is for the quad core Tegra3 (non-LTE) version, which is completely different hardware.
Also, I don't know if 10.3 is even released yet for our device, or for the ENDEAVORU for that matter. I think you might be confused about what you are flashing. So again, link what you are trying to install.

The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have. Getting s-off disables the security check which would let you run any Evita RUU but you need to get a ROM to boot first before you try that. You also need SuperCID.
Your best bet is probably to flash an older Sense ROM (4.0 or 4.1), then you can at least boot, and get SuperCID and s-off so you can run the 3.18 RUU to meet the requirements for the latest cm ROMs.
Sent from my Evita

timmaaa said:
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have.
Click to expand...
Click to collapse
For some reason, I got confused and thought the OP was saying that the ROM install was failing. But it clearly says the RUU (or "rru" anyway) failed.
But yes, you can only run an RUU for your carrier version. So you will need s-off to run the AT&T RUU (the RUU referenced in the OP).
But still confused about the mention of CM10.3. From what I can see, it doesn't exist for either our EVITA, or the ENDEAVORU.

Maybe he meant cm10.2 and it was a typo?
Sent from my Evita

timmaaa said:
Maybe he meant cm10.2 and it was a typo?
Click to expand...
Click to collapse
Could be. Although if so, its a type that appears twice.
It seems fairly common for folks to try to install the wrong CM (wrong device). So I want to make sure the OP isn't doing that.

redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.

stueee said:
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
Click to expand...
Click to collapse
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.

Hi Red,
Sorry i typed out that post at almost 1am after pulling my hair out over a few hours and got a little confused.
My hboot is 2.15 and twrp is 2.6.3.0 which I believe is the latest.
What sense rom would work on mine as i really need this working now as i cant find a rom to suit anywhere with my lesser expertees.
I tried changing the cid using the super cid Telstra bat file but it won't recognize the phone as its not loaded, i tried in off state, bootloader, fastboot and twrp but is just keeps saying cant find phone.
I also tried the hex editor method but it didnt seem to update the CID after i completed it without errors.
thanks for you help.
redpoint73 said:
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Click to expand...
Click to collapse

With 2.15 hboot, you cannot modify the files required for supercid.
You can try the ever so risky jet tool. But this tool deliberately bricks to downgrade your hboot.
Sent from my HTC One XL using xda app-developers app

Any recent Sense ROM will suit your current setup, have a look here and you'll find a whole bunch. Unfortunately for you the 2.15 hboot has write protection enabled so there's no way you can get SuperCID (abd therefore can't get s-off), at least not until an exploit is released.
When you tried to flash CM did you also flash the boot.img via fastboot afterwards? You're s-on so that's necessary to get it to boot. Phones on a higher hboot like yours are unable to flash the boot.img through recovery so it must be done manually.
All you do is retrieve the boot.img from the root of the ROM zip, put it in your fastboot folder on your PC, and after you've flashed the ROM in recovery you reboot to bootloader, connect the phone to the PC, open a command prompt from within your fastboot folder (shift + right click anywhere in the folder then select open command prompt here), then give the following command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the ROM.
Sent from my Evita

stueee said:
My hboot is 2.15
Click to expand...
Click to collapse
That's pretty important. This is the reason why the older CM10.1 failed to install. CM was having issues with older hboots, so a script was added to require hboot 2.14.
Once hboot 2.15 came along, folks found that CM failed to install since the install script explicitly requires 2.14. Later versions include hboot 2.15 in the install script.
As exad and timmaaa mention, SuperCID (and therefore s-off) are not possible on hboot 2.15. So you are stuck with s-on (assuming that is what you are on now). It also means you can't currently run any RUU. Reason being, with s-on you can't run older RUUs, RUUs from another carrier, and there are no RUUs based on hboot 2.15. No "current" RUU exists (for your hboot), you can't run "previous" RUUs with the S-on restriction. So therefore you can't currently run any RUU.
But hboot 2.15 will work with newer versions of CM (and other AOSP ROMs which have been recently updated) as well as any Sense ROMs. But with s-on, you need to extract boot.img and flash manually with fastboot every time you install a ROM (as timmaaa points out). If you did not do this, this is why flashing the recent CM10.2 nightly resulted in a bootloop. Failure to falsh boot.img is the most common reason for bootloop after flashing a ROM.

stuck in bootloop
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..

martin-m7 said:
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
Click to expand...
Click to collapse
You're in the wrong forum, buddy. This is the HTC One XL forum.

[GUIDE][TOOL]FUU/Firmware HTC One XL

General Information
This Has Been Made To Help Those How Have No Clue What There Doing When Upgrading There Firmware Note And Want A One Click That Mimiks HTC RUU
FUU Definition
Firmware Update Utility
There are a few Firmware flashing threads and lots of zips and good and bad instructions. However, i noticed that many users asked about what they get when they flash what they download and also about how to flash it with S-OFF on various threads. This confusion has occasionally lead to people losing their custom kernels and custom recoveries and/or their SDcard partitions being unintentionally wiped.
I am writing this because i believe in "responsible" sharing. Since the full RUU's aren’t shared but only components (modified as well as unmodified) with often insufficient documentation, which in turn leads to a lot of confusion among the lesser informed users, i will try to catch some of that. I believe that sharing full RUU's would be a lot safer, as only those who actually know enough about it can disassemble them. RUU’s do always reassure users that there is a guaranteed and safe way to go back.
Prerequisites:​All you need is a Windows System with current drivers and maybe HTC Sync Manager installed, it is better to have HTC Sync uninstalled and only the drivers left. Just try if the FUU runs without HTC Sync. On my system, i am always greeted with an “Error 170" if i try to run the FUU on a booted Android - it doesn’t recognize the phone with ADB. This is a typical driver and/or ADB error. Solution here: make sure you have the latest driver suite. FailSafe way to get them is to install HTC Sync Manager (remove it if you don’t like it afterwards but leave the drivers in the sytem!).​
FUU How To​
[*]Download the firmware you want
[*]then run the installer
[*]install it to folder you want to any folder will do
[*]then run the tool and upgrade or downgrade your firmware
ZIP Flash HowTo​
Step-By-Step:​1. If device is booted into Android, reboot into bootloader by running:
Code:
adb reboot bootloader
1.a Or else, if your device is in a different state or you just prefer the button method:
Press Power for 15 seconds and hold Vol Down at the same time, when the screen and charging LED go dark immediately release Power but keep holding Vol Down until you see the bootloader screen. Notice: If the device refuses to reboot, you might need to hold it to a bright light with its light sensor. This is a very specific bug in the HTC ONE. The light trick always works.
2. Now place the Firmware_named_something.zip into your adb/fastboot folder
3. Now run:
Code:
fastboot oem rebootRUU
4. Followed by:
Code:
fastboot flash zip Firmware_named_something.zip
(replace "Firmware_named_something.zip" with the name of your zip)
5. Now check the console output. It should approximately look like this:
“flush" certainly means “Flash" so press the arrow up key on your keyboard and enter to run the flash command again without reboot...
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution! The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot! The bar will only fill up to 100% once you type the following command:
6.
Code:
fastboot reboot-bootloader
Error handling strategies:​IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL it could not boot up anymore! It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (dont use hubs! Always straight-to-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot... there are many possible sources for flash fails.
The least dangerous FAILED messages are listed below and are safe to reboot:
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 32 header error (means the zip couldn’t be read and unzipped properly)
- 41 Wrong Model ID (means its not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap cid first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot inbetween).
- 99 UNKOWN (is not yet clear but safe to reboot, might indicate a defunct S-OFF or S-ON)
- 155 you did not lock your bootloader (Needs a relock for S-ON phones that want to update the firmware.)​
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn’t help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
fastboot oem writecid 11111111
You can change back to any desired CID after a successfull firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn’t brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- Tell me if you find out what’s causing an unknown error here!
For “Error 155 relock bootloader" do:
- run the fastboot command “fastboot oem lock" - only applies to S-ON phones that want to update the firmware. There a relocked bootloader is required. This error won’t show on S-OFF phones.
- Error 155 can also mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of wrong region lock.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers or ADB/Fastboot binaries. One way to solve is to run the exe with the phone already in Fastboot mode. Else you will have to dig into your windows driver system and try to fix there. Best option: re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn’t work with ADB and Fastboot.​
I always test all of these zips on my own device. But as always, flash at own risk. You're writing to critical parts of your phone. If anything goes wrong along the way, you might be bricked.​
FUU Downloads (Windows only)​
Update: added Firmware For AT&T HBOOT 2.18 FUU
Download
MD5: 48091aae9ecaf2a9b66449ca3ac1fe93
This FUU is Stock. Contents: Firmware from 24ky And So You should be good to Go. This package does wipes SDcard.​
Update: added Firmware For HBOOT 2.15 FUU
Download
MD5: 3d19ea00d476f88ba3879385eda59ed4
This FUU is Stock. Contents: Firmware from @pandasa123 So You should be good to Go. This package does wipes SDcard.​
Update: added Firmware For HBOOT 2.14 FUU
Download
MD5: 37654a569896117c38e4c76974a31b1d
This FUU is Stock. Contents: Firmware from HTC OTA So You should be good to Go. This package does wipes SDcard.***NOTE*** The Boot Has Been Removed Because It May Cause You Some Problems And Result In Having To Reflash Your Rom​
Fastboot ZIP Downloads​
Update: added Firmware For HBOOT 2.18
Download
MD5: 1d9aa2418726e017f01277958fb60107
This package is stock. Contents: Firmware from 24ky And So You should be good to Go. This package does Not wipe SDcard.
Update: added Firmware For HBOOT 2.15
Download
MD5: 94fc2d03e85259cddb78f256f417f48a
This package is stock. Contents: Firmware from @pandasa123 So You should be good to Go. This package does Not wipe SDcard.
Update: added Firmware For HBOOT 2.14
Download
MD5: d42499f1a27156e56e584f6067160b24
This package is stock. Contents: Firmware from HTC OTA So You should be good to Go. This package does Not wipe SDcard.***NOTE*** The Boot Has Been Removed Because It May Cause You Some Problems And Result In Having To Reflash Your Rom​
Credits​Thank You Sneakyghost For The Tool And The Op
ramjet73 My mentor for HBOOT Modding
pandasa123 For The 2.15 Firmware
24ky For The 2.18 Firmware
Big Thanks To:​ @pandasa123
@Phonefanboys
@Venomtester
Disclaimer​You are aware that writing to the security protected partitions increases your risk to lose the device exponentially. You understand and agree that i cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested on various phones at time of posting, however you are the brains behind the wheel and you are solely responsible for the execution of the process. I will not accept any responsibility. The method itself is developed by Google and HTC, i only provide access and information to it and you execute it.
You understand that you should not do it if you are not willing to accept this risk.​​

For me

Great work! Any plans to include the firmware from the 3.18 update?

timmaaa said:
Great work! Any plans to include the firmware from the 3.18 update?
Click to expand...
Click to collapse
Yup hopefully by the end of today
Sent from my SPH-L710 using Nightmare Rom

Just wanted to say thanks. These tools definitely make the process much easier. .
Also can confirm they both work
Sent from my HTC One XL using Tapatalk

Update for 3.18 (2.14 hboot) Is Now Live Enjoy

a lil lost
Ok so I'm running codefireX, an torched kernel an I'm experiencing very frequent signal drops. Same results without kernel. I was informed to update hboot to 2.18 an radio to 3.18. an that should resolve my issue. I have a couple questions though. First off if I do update using the fuu method will I b able to go back to a non KitKat rom on same radio an hboot? Secondly when I download correct update exactly where do I put it in the internal storage? Thx

chris281987 said:
Ok so I'm running codefireX, an torched kernel an I'm experiencing very frequent signal drops. Same results without kernel. I was informed to update hboot to 2.18 an radio to 3.18. an that should resolve my issue. I have a couple questions though. First off if I do update using the fuu method will I b able to go back to a non KitKat rom on same radio an hboot? Secondly when I download correct update exactly where do I put it in the internal storage? Thx
Click to expand...
Click to collapse
Out of interest, who advised you to update your firmware to 2.18 and your radio to 3.18? That's going to cause a potential mismatch. Update your firmware to 2.18 using this FUU tool and leave the radio as the one that comes with the firmware package (1.35 I believe).
Sent from my Evita

timmaaa said:
Out of interest, who advised you to update your firmware to 2.18 and your radio to 3.18? That's going to cause a potential mismatch. Update your firmware to 2.18 using this FUU tool and leave the radio as the one that comes with the firmware package (1.35 I believe).
Sent from my Evita
Click to expand...
Click to collapse
Someone in the cfx forum. Glad I asked before I did it. So update it to 2.18? Thx for info!

Thanks!

FlubbedJohn said:
Thanks!
Click to expand...
Click to collapse
Next time, just hit the thanks button. It'll say the same thing
Sent from my HTC One XL using Tapatalk

That wouldn't have helped his post count though, would it.
Sent from my Evita

Htc eva_utl
heloo
It is possible to ??????
HTC EVA_UTL
Hboot 2.10
S-off
Unlook

mehdisarvari said:
heloo
It is possible to ??????
HTC EVA_UTL
Hboot 2.10
S-off
Unlook
Click to expand...
Click to collapse
It looks like @timmaaa already told you the same applys here
Sent from my One S using Tapatalk

I have indeed already told him that he can't flash anything from the standard Evita to his variant, apart from ROMs.
Sent from my Evita

Flashalot said:
It looks like @timmaaa already told you the same applys here
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
timmaaa said:
I have indeed already told him that he can't flash anything from the standard Evita to his variant, apart from ROMs.
Sent from my Evita
Click to expand...
Click to collapse
Thanks,
I thought this thread was going to Work
Thanks,

mehdisarvari said:
Thanks,
I thought this thread was going to Work
Thanks,
Click to expand...
Click to collapse
The only things you can flash to your variant of the Evita are ROMs. No firmware, no hboot, no radio, no nothing else is safe for you. Ok, that's three times now, I hope I'm being clear enough, I just don't want to see you brick your phone.
Sent from my Evita

timmaaa said:
The only things you can flash to your variant of the Evita are ROMs. No firmware, no hboot, no radio, no nothing else is safe for you. Ok, that's three times now, I hope I'm being clear enough, I just don't want to see you brick your phone.
Sent from my Evita
Click to expand...
Click to collapse
Thank you.
My goal is Android 4.3.

You're not gonna be able to flash a 4.3 ROM because you're unable to flash the firmware that's required to run them. The closest you're gonna get is a 4.2.2 Sense ROM. We're completely off topic for this thread now though, if you have any further questions you're welcome to ask them in my q&a thread.
Sent from my Evita

tried this as i figured updateing to the newest firmware would be beneficial in some way and after i go to flash the zip again after it tells me to, all it does is hang on sending file for ever? and now im stuck in RUU mode, however when i unplug the phone, the firmware number is now 2.18?? I HAVE NOT rebooted yet though as im scared to please advise!

[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..