Database Info

[Q] [HELP] Vodafone Branded Desire S - Problems with installing Custom Recovery!

Hi there,
I want to install Miui Rom on my Desire S (vodafone branded). I can achieve root
via SuperOneClick, but i have got Hboot 2.00.002 so i can't S-off my device.
Is there any way to install a custom recovery so i can install Miui or different Roms?
I tried to install CWM Recovery via Rom-Manager, it said "successfully installed" but when i boot into Recovery there is just a Smartphone
with a Red Triangle, so no custom recovery at all, i think it's because i don't have S-Off.
So, i only want to install some Roms, so i need a custom Recovery, how can i install it without s-off?
Here are some information about my phone:
HTC Desire S - Vodafone Germany Branded
Android Version 2.3.5
Sense 3.0
Software Number: 2.10.161.3
Baseband Version: 20.4801.30.0822U_3822.10.08.04_M
Build Number 2.10.161.3 CL156318 release-keys
HBoot 2.00.002
Bootloader is UNLOCKED via HTCDev
I Hope you can help me.

All you are achieving is temp root.
You can either unlock your bootloader with HTCdev, then flash a custom recovery or;
Downgraded to an older ROM and then s-off like normal.
Both are well discussed on forum.
And while you can, make goldcase, just in case you need it later.

Now I'm in the following Situation:
I've got S-On , Hboot 2.00.002, BUT Clockworkmod Recovery installed.
I did a Backup, wiped everything and installed the newest MIUI 2.1.20 i think, worked well in cwm, but when I reboot my phone it just stays at the HTC bootscreen.
My bootloader is unlocked via HTCdev.
So i have an unlocked bootloader, Clockwork Recovery but S-On, but custom Roms don't work... is it because of S-On ?
I tried to Downgrade but none of the tutorials worked for me, the problem was:
I pushed the 2 files misc_version and zergRush to /data/local/tmp and did the other adb commands, got (Temp)Root with zergRush and changed the Version to 1.27.405.6 i think, then I downloaded a HTC RUU (i've tried the vodafone UK but i live in Germany and the HTC Europe RUU) so my phone boots into HTC Bootloader but then the RUU Installer says "cannot install RUU because it's the wrong installer " or something like that...
so i don't know how i can downgrade to get S-Off?

you need to change the cid to install other ruus. or use the ruu matching your cid or
downgrade bootloader to the old one so revolutionary is working and s-off the device with revolutionary

I Just want to flash a custom Rom.
BUT Finally i got it!
http://forum.xda-developers.com/showthread.php?t=1257731
AND
http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37
This is the solution for installing custom roms without downgrading

Yeah you need to flash the boot/kernel afterward when on the 2.00.0002 hboot.

[Q] please help my sdcard show just 48mb.

Hi I have big problem with my HTC one s I decided to install maximus hd but I need super cid and s-off facepalm metod everything I do original cid cange to 1111111... Get s-off acses and and install Rom then firmware and when Rom but Rom loads very slowly and sometimes
Black screen and not won't load Rom. And I decided to back s-on and back to original CID HTC_111 and install tricdroid beta 10.0 and then my sdcard 48mb. I try everything flash stock recovery delete all data and wipe but still 48mb try changing a few recovery cmrecovery all types and Twrp recovery but work one prefect Twrp 2.6.1.0 this recovery show me 12gb but I installed Rom on pc 48 I try again flash firmware from maximus hd but failed bicose I change my cid and back to s-on then. I try to go to s-off and change my cid to 11111111.
Noting happen my cid still htc_111 I can't do s-off my hboot is 2.16.0000 I read this forums I find many solutions but no-one don't help my. Try install three roms trickdroid magiobeta and source v14 still 48 I just want get my sd card please somebody. I try many thing relock boot loader try with ruu but still 48. Sorry for my language mistakes I am from Lithuania. Thanks:crying:

Your stuck like me...you cant do nothing for now. Wait for s-off hboot 2.16.

Aca902 said:
Your stuck like me...you cant do nothing for now. Wait for s-off hboot 2.16.
Click to expand...
Click to collapse
when it is released for hboo 2.16
Maybe impossible downgrade hboot to 2.15?

Maybe never, maybe today. No, you cant... because everything is write protected, you cant even brick your phone.

Look at the second post in this thread it might help you mount the sdcard correctly forum.xda-developers.com/showthread.php?t=2448950 also check out the unbridled project I'm pretty sire they can get you back to an older hboot if you send your phone to them...

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.

ONE S [S4] problem

hello guys,
I have a problem with htc one s (version S4).
I tried to unlock the bootloader and have root permissions by installing the recovery t.
I then tried to install the maximusHd without myself realized that he had S-OFF (installed through a full wipe).
Currently I find myself with the hboot version updated to 2.15, I tried to change the supercid (successfully) and get the s-off (but are not successful, even though I tried several times gives me errors sh)
I am now S-ON hboot with 2:15 ... I would use my phone, trying to return or stock, or have prefixed S-off for maxiumsHD ... can anyone help me?
I tried to do everything, but the RUU gives me (or signature error with the latest version, or error dell'hboot, too updated with earlier versions), while S-OFF with facepalm, or even having the moleshine Supercid do not work.
I'm really felling: (

antomc said:
hello guys,
I have a problem with htc one s (version S4).
I tried to unlock the bootloader and have root permissions by installing the recovery t.
I then tried to install the maximusHd without myself realized that he had S-OFF (installed through a full wipe).
Currently I find myself with the hboot version updated to 2.15, I tried to change the supercid (successfully) and get the s-off (but are not successful, even though I tried several times gives me errors sh)
I am now S-ON hboot with 2:15 ... I would use my phone, trying to return or stock, or have prefixed S-off for maxiumsHD ... can anyone help me?
I tried to do everything, but the RUU gives me (or signature error with the latest version, or error dell'hboot, too updated with earlier versions), while S-OFF with facepalm, or even having the moleshine Supercid do not work.
I'm really felling: (
Click to expand...
Click to collapse
Well its seems like your in a soft-brick
so download a ROM not for hboot 2.16 like sourcE or vipers then if you still want to run maximusHD then after running a hboot 2.15 ROM like I stated above then download moonshine or rumrunner then get s-off and after that you could download my tool kit for one click upgrade to hboot 2.16 or download the firmware from the thread in maximusHD
Sent from my Nexus 7 using Xparent Red Tapatalk 2

[HELP] cant go after boot screen

hi,
i undergrade 2.15 from 2.16 but i had mount sd card error so i upgrade it again to 2.16 but now when ever i flash any rom i stuck on boot screen or in cynogenmod rom it is restarting in boot animation ... please help me ... i am very tense ... i have s-off , unlocked , radio 1.20 cid 111111

I had the same problem, it was a directory rights problem (/mnt/sdcard if I remember correctly). The best thing to do once you downgrade your HBOOT is to use a RUU to go back to a known working base and then install the ROM you want.

kdd998 said:
I had the same problem, it was a directory rights problem (/mnt/sdcard if I remember correctly). The best thing to do once you downgrade your HBOOT is to use a RUU to go back to a known working base and then install the ROM you want.
Click to expand...
Click to collapse
not working for me ... i upgrade again to hboot 2.16 via fastboot then install maximus but having problem of bootloop... and same in cynogenmod roms .... i install ruu YOUN but same problem ... any help???