Database Info

[Q] Is my device bricked or what?

I know there are probably other threads that can help me but I'm really desperate here. I just got my Sensation 4G (T-Mobile) a few days ago and decided to root it and install a custom ROM. This is my first Android device so I followed a newb guide specifically for the Sensation 4G. However, I think I accidentally missed the step describing how to S-Off and I ended up trying to install Cyanogen Mod 9. It installed ok but I got stuck at the boot screen. From there, I tried restoring to a backup I made before installing Cyanogen but it didn't work. Now I'm stuck at the HTC logo. Can anyone help me out? Here are some more details about my device:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012, 17:33:34
I think my firmware is 3.32 and the Android version was 4.0.3 although I guess there's nothing on it now.
EDIT: The latest guide I followed shows how to install/flash the stock ICS firmware but I couldn't update the firmware. It says "Parsing .zip" but doesn't go further than that.

Enable smartflash in 4ext recovery, then flash Rom again
Enviado desde mi HTC Sensation 4G

serio22 said:
Enable smartflash in 4ext recovery, then flash Rom again
Enviado desde mi HTC Sensation 4G
Click to expand...
Click to collapse
I don't have 4ext recovery installed, only CWM. Is there a way to install it even though I can't boot into the phone?

Yeah, just have to flash another recovery (4ext) through fastboot.
If you look around the development section, you'd probably find a guide how to do it, if not PM me, and I'll give you the steps.

Have a look in this thread: http://forum.xda-developers.com/showthread.php?t=1631861 Asskicker's guide, how to flash roms with S-ON. If you don't want to flash the 4ext recovery (I highly recommend to install it!) then you can do Step "EXTRA 1" from that guide and install "boot.img" from the downloaded rom. You find it in the zip file, in the kernel folder. But read the guide, there are plenty of very useful info in it! And to answer your question, No! Your phone is not bricked!

matekaneve said:
Have a look in this thread: http://forum.xda-developers.com/showthread.php?t=1631861 Asskicker's guide, how to flash roms with S-ON. If you don't want to flash the 4ext recovery (I highly recommend to install it!) then you can do Step "EXTRA 1" from that guide and install "boot.img" from the downloaded rom. You find it in the zip file, in the kernel folder. But read the guide, there are plenty of very useful info in it! And to answer your question, No! Your phone is not bricked!
Click to expand...
Click to collapse
I have a bunch of ROMS that I've tried and they're all on my desktop. Only two of them have a kernels folder, so I guess the other two are using a stock kernel and I can't use them, right? I'll try following that thread you linked me to, hopefully it'll work this time.
EDIT: It worked! Thank you so much! Now if I wanted to install Cyanogen Mod 9 for example, which doesn't have that kernels folder, I would need to S-OFF first right?

If you want to install ROM's without being S-OFF I'm pretty sure you need 4EXT.
And for future reference to all who may find this thread down the road, if you can get into your Recovery (any recovery) your phone is almost certainly not bricked. You may have a lot of fixing to do, but it's almost certainly fixable.
When the splash screen doesn't even come up after hitting the power button or the charing light doesn't come on when plugged in...that's when it's time to worry. (And even then you may have options)

Skipjacks said:
If you want to install ROM's without being S-OFF I'm pretty sure you need 4EXT.
And for future reference to all who may find this thread down the road, if you can get into your Recovery (any recovery) your phone is almost certainly not bricked. You may have a lot of fixing to do, but it's almost certainly fixable.
When the splash screen doesn't even come up after hitting the power button or the charing light doesn't come on when plugged in...that's when it's time to worry. (And even then you may have options)
Click to expand...
Click to collapse
I did the wire-trick to S-OFF my device. WHen I first did that, my only option in the bootloader was RUU and I was about to ask you about that but took my battery out first. Now it's back to normal and it shows S-OFF. However, my microSD card is now completely wiped. I have a backup on my computer, so should I just copy the files back on there and try another ROM so that my WiFi will work?

Ir0nMa1deN said:
I did the wire-trick to S-OFF my device. WHen I first did that, my only option in the bootloader was RUU and I was about to ask you about that but took my battery out first. Now it's back to normal and it shows S-OFF. However, my microSD card is now completely wiped. I have a backup on my computer, so should I just copy the files back on there and try another ROM so that my WiFi will work?
Click to expand...
Click to collapse
copy your files into sdcard then reboot your device
about wifi you can flash the boot.img manually(maybe you do not need that because you are S-OFF now)
otherwise flash your rom again
up the irons:good:

Ir0nMa1deN said:
I did the wire-trick to S-OFF my device. WHen I first did that, my only option in the bootloader was RUU and I was about to ask you about that but took my battery out first. Now it's back to normal and it shows S-OFF. However, my microSD card is now completely wiped. I have a backup on my computer, so should I just copy the files back on there and try another ROM so that my WiFi will work?
Click to expand...
Click to collapse
Yes. Just copy everything back. Everything will be where its supposed to be.
Sent from my HTC Sensation using xda app-developers app

rzr86 said:
copy your files into sdcard then reboot your device
about wifi you can flash the boot.img manually(maybe you do not need that because you are S-OFF now)
otherwise flash your rom again
up the irons:good:
Click to expand...
Click to collapse
Haha I was waiting for that "Up the Irons." My username is pretty much the same on every site I register on so I always get that. Anyway, I'm not sure what's going on with the WiFi but I'm going to try a different ROM and hope WiFi works there.
:highfive:

[Q] CWM Recovery H Boot 1.27 Android 4.03

Hi
I have tried looking around this forum for a way to install CWM recovery on a HTC Sensation unlocked S on I am getting more confused and have quite a pile of zip files been trying this for 2 days now
Clockwork rom manager throws a message saying must root phone superuser not found at "/system/bin su or xbin/su I have super user installed
I have tried fastboot flash recovery recovery.img cant find the file or no such file (i pointed to the correct folder) Using Android SDK (not sure if it is installed correctly but had the required files in the folder with the unlock. bin
Tried HTC One X All-In-One Toolkit it said done but S is still on
Any Help very much appreciated and sorry if I have not done the obvious
Thanks
Smokes

Smokes68 said:
Hi
I have tried looking around this forum for a way to install CWM recovery on a HTC Sensation unlocked S on I am getting more confused and have quite a pile of zip files been trying this for 2 days now
Clockwork rom manager throws a message saying must root phone superuser not found at "/system/bin su or xbin/su I have super user installed
I have tried fastboot flash recovery recovery.img cant find the file or no such file (i pointed to the correct folder) Using Android SDK (not sure if it is installed correctly but had the required files in the folder with the unlock. bin
Tried HTC One X All-In-One Toolkit it said done but S is still on
Any Help very much appreciated and sorry if I have not done the obvious
Thanks
Smokes
Click to expand...
Click to collapse
with all in one tool kit you won't bring S-OFF
from this thread try to flash this recovery.it is better than cwm
http://forum.xda-developers.com/showthread.php?t=1631861 (only step 2)

I used HTC One X toolkit, but it wouldn't S-Off as I had hboot 1.29.0000, therefore couldn't use revolutionary method. In this instance you can s-off using a paperclip, some insulating tape, and running the ControlBear software. To find out how to do this, type the following into YouTube:
JuopunutBear S-Off HTC Sensation.
... That will show you how to achieve S-Off which will unprotected the nand storage to write enabled so you can flash a new ROM.
See JuopunutBear website for instructions. You can find it by typing:
unlimited.io
... Into google.

or you can use the guide from our forum in dev section
http://forum.xda-developers.com/showthread.php?t=1661631

Thanks
rzr86 said:
with all in one tool kit you won't bring S-OFF
from this thread try to flash this recovery.it is better than cwm
http://forum.xda-developers.com/showthread.php?t=1631861 (only step 2)
Click to expand...
Click to collapse
Thanks for the replys and help, thought it was working hope I can get out of this problem I installed OrDroid_V9.0.0 everything seemed to go ok until it came to boot screen its stuck there. Might be easier, if I have not caused any real damage to take it to a shop I dont know what I am doing with this
Thanks
Smokes

Smokes68 said:
Thanks for the replys and help, thought it was working hope I can get out of this problem I installed OrDroid_V9.0.0 everything seemed to go ok until it came to boot screen its stuck there. Might be easier, if I have not caused any real damage to take it to a shop I dont know what I am doing with this
Thanks
Smokes
Click to expand...
Click to collapse
because you are S-ON when flashing a rom it doesn't write the boot partition by itself
the only thing you have to do is enable smartflash from 4ext recovery and after flash the rom
or
you can follow extra 1 step in the link i provided you in my first post

Stuck
rzr86 said:
because you are S-ON when flashing a rom it doesn't write the boot partition by itself
the only thing you have to do is enable smartflash from 4ext recovery and after flash the rom
or
you can follow extra 1 step in the link i provided you in my first post
Click to expand...
Click to collapse
Done the wire trick, got it after a few attempts recovery screen now says
revolutionary
Pyramid pvt ship s off RL
Hboot 1.27.1100
Radio 11 24a 3504 31 H
now asking for update I ok that phone eventually boots up then says unexpected UI error and screen goes blank. I cant get anything transferred to the phone as the pc isnt seeing it
Is there anyway to get a recovery on the phone so I can load a rom.
Juopunutbear backed up my images but have no idea how to get them back. Before the wire clip trick the phone had Super-Threading-Rom-v1.2.1 4ext recovery it seemed better than my old clockwork recovery
If this isnt bricked what rom would you suggest and how do i flash it
Thanks
Smokes

Smokes68 said:
Done the wire trick, got it after a few attempts recovery screen now says
revolutionary
Pyramid pvt ship s off RL
Hboot 1.27.1100
Radio 11 24a 3504 31 H
now asking for update I ok that phone eventually boots up then says unexpected UI error and screen goes blank. I cant get anything transferred to the phone as the pc isnt seeing it
Is there anyway to get a recovery on the phone so I can load a rom.
Juopunutbear backed up my images but have no idea how to get them back. Before the wire clip trick the phone had Super-Threading-Rom-v1.2.1 4ext recovery it seemed better than my old clockwork recovery
If this isnt bricked what rom would you suggest and how do i flash it
Thanks
Smokes
Click to expand...
Click to collapse
how did you get S-OFF with juopunutbear method when it was already be done with revolutionary?
nevermind
did you install 4ext recovery?
if yes put the rom in the root of the sdcard
go to bootoader
navigate to recovery
flash the rom

rzr86 said:
how did you get S-OFF with juopunutbear method when it was already be done with revolutionary?
nevermind
did you install 4ext recovery?
if yes put the rom in the root of the sdcard
go to bootoader
navigate to recovery
flash the rom
Click to expand...
Click to collapse
Before using bear it said UNLOCKED S on with 4ext recovery found out what caused the issue you replied to i removed temp root with controlbear fone is Soff and boots without problems I ran su-2.3.6.3-efgh-signed do I need to do anything else?
Thanks

If you have installed recovery and installed successfully the rom
then there is nothing else to do
Sent from my HTC Sensation Z710e using xda premium

THANKS
rzr86 said:
If you have installed recovery and installed successfully the rom
then there is nothing else to do
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Thanks for the help, very good forum & very helpful people, our phones would be nowhere near as good without this knowledge Ive added :good: to the replys
Thanks

Just tried connecting to wifi in settings on wifi there is an error I am using Super-Threading-Rom-v1.2.1 not sure how to go about updating any radio (if this might be causing the problem)
Could someone please point me in the right direction, if poss
Thanks

Smokes68 said:
Just tried connecting to wifi in settings on wifi there is an error I am using Super-Threading-Rom-v1.2.1 not sure how to go about updating any radio (if this might be causing the problem)
Could someone please point me in the right direction, if poss
Thanks
Click to expand...
Click to collapse
from recovery format all partitions except sdcard and then flash the rom again
if that doesn't work from this guide do only extra 1
http://forum.xda-developers.com/showthread.php?t=1631861

Thanks, its working fine now :good:

[Q] How to root Desire S, S-OFF, hboot 2.00.0002, android 4.0.4

Hello people. Just one question. I searched on google and here on xda how to do it but still Im not sure how to do it. I have HTC Desire S, S-OFF with 2.00.002 hboot version and 4.0.4. android version. How do I permanetly root? The official 4.0.4 is kinda laggy, at least for me. I tried few methods but still nothing.. And, I found few methods like for 0.98 hboot or 2.3.5. android but my phone isnt that so Im not sure will it work. Thanks im advance

chorba69 said:
Hello people. Just one question. I searched on google and here on xda how to do it but still Im not sure how to do it. I have HTC Desire S, S-OFF with 2.00.002 hboot version and 4.0.4. android version. How do I permanetly root? The official 4.0.4 is kinda laggy, at least for me. I tried few methods but still nothing.. And, I found few methods like for 0.98 hboot or 2.3.5. android but my phone isnt that so Im not sure will it work. Thanks im advance
Click to expand...
Click to collapse
Is your bootloader unlocked? If so then flash a custom recovery and flash a custom ROM, they all tend to be pre-rooted.
Sent from my Desire S using xda app-developers app

You're already S-OFF so you don't need to worry about most steps in guides.
I assume you have a custom recovery? You can just flash one of the superuser/superSU zip packages. (Desire S uses ARM).
You may also need to flash busybox.

My good gentlemen,
he says the phone is s off already

If you want to ROOT your phone (my case: Desire S , Mfc date: 2011-July ). This is the procedures i learned from China Android forums, at least it works on Me.!!
Make Sure your Hboot is 2.00.0002
Prepare 2 files first: Superuser-3.0.7-efghi-signed.zip and su-bin-3.0.3.2-efghi-signed.zip
(you should find those on the internet)
First:
Recovery --> install Superuser-3.0.7-efghi-signed.zip from SDcard, and Reboot;
Second:
Recovery --> Install su-bin-3.0.3.2-efghi-signed.zip from SDcard Again and Reboot.
Usually, your phone should be Rooted.!!
Have Fun

Thanks for answers Well, the only thing I wanna do is flash a custom rom, and I dont know do I need rooted device for that? If I dont, what do I need? And, how can I check is my bootloader unlocked? And, where can I find a custom recovery? Can anyone link me please? Thanks ^^
I learned few things on my old Desire but this seems little complicated If isnt a probem, can anyone give me a step by step guide what I have to do to start flashing custom roms or something? I'd appreciate it. Thanks in advance

chorba69 said:
Thanks for answers Well, the only thing I wanna do is flash a custom rom, and I dont know do I need rooted device for that? If I dont, what do I need? And, how can I check is my bootloader unlocked? And, where can I find a custom recovery? Can anyone link me please? Thanks ^^
I learned few things on my old Desire but this seems little complicated If isnt a probem, can anyone give me a step by step guide what I have to do to start flashing custom roms or something? I'd appreciate it. Thanks in advance
Click to expand...
Click to collapse
Reboot to bootloader and check the first and second lines of text there...
first states < unlocked > if it was unlocked
second at the end: s-off.... or s- on
If your device realy was: s- off,
then your bootloader does not perform check of a signature,
so, in human language means: you may flash anything you want
custom recovery: clockworkmod or 4ext,
you may find in index thread for desire s...
here is the link
http://forum.xda-developers.com/showthread.php?t=1146601
there you can find tutorials about flashing, rooting etc, etc...all you`ll need
here is another link to the help thread, where you may ask questions if you
stumbled somewhere, along the way
http://forum.xda-developers.com/showthread.php?t=2143855
one more thing: when choosing roms, you should only flash roms for your device
htc desire s ( that`ll save you headaches )

Erm.. Just checked and it says bootloader is locked :/ It is S-OFF but locked. How can I unlock it? On HTCdev or? Thanks

chorba69 said:
Erm.. Just checked and it says bootloader is locked :/ It is S-OFF but locked. How can I unlock it? On HTCdev or? Thanks
Click to expand...
Click to collapse
I`ve never had stock s-off device ( always had to do it myself )
but if you phone was never rooted before and its security flag is set to s- off,
then i think its bootloader will never check manufacturer`s signature
Try this:
download from the market or from 4ext thread (index thread )
< 4ext recovery updater > and from within that application,
try to install recovery ( you`ll need it anyway )
if that`ll turn out to be succesful, then your phone is ready for the ride...
Go to the thread from the second link ( help thread )
and ask there whether device that is s- off, needs its bootloader to be unlocked
in order to be ready to flash custom roms...
To unlock bootloader you may try comand ( not sure if that would work for you )
fastboot oem unlock
issued to you phone through comand prompt ...
Prior to this action you should set up ADB on your pc,
and of course install the drivers for your device...

Says this what I attached. What now?

chorba69 said:
Says this what I attached. What now?
Click to expand...
Click to collapse
Ok then...
you have to flash recovery via fastboot
1. download and set up adb and drivers for you phone ( and install them )
2. download recovery ( clockworkmod or 4ext )
3.extract < recovery_xxxyyy.img > from the zip file- if you downloaded it zipped...
4.rename file to < recovery.img > and place it in the folder
where you`ve placed ADB
5.open command prompt and issue command:
cd c:\name of the folder with ADB [ enter ]
6. reboot your phone to bootloader and wire it to you pc
7. issue command:
fastboot devices
if your device has been recognised( list of devices attached xxxyyy05321...)
you`ll see your phone`s ID
8. issue command:
fastboot flash recovery recovery.img
9. reboot bootloader, and from its option choose recovery
10. from recovery you may flash < superuser.zip >
if you just want your current rom rooted
or via recovery you may flash custom rom...

Alright mate thanks a lot. Im gonna try that as soon as I come home. Just one thing more, any chance of bricking my device? While doing that.

chorba69 said:
Alright mate thanks a lot. Im gonna try that as soon as I come home. Just one thing more, any chance of bricking my device? While doing that.
Click to expand...
Click to collapse
To be honest, when fiddling with phone`s system, bootloader etc..
however small- there is always a chance that you may manage to brick it,
but i`ve been followiing the above mentioned procedures- and many others before me,
many times, and it was always working without a problem,
it was tested and shared, first by the great ones among us,
so one may call them safe to perform,
but you should always remember to be careful,
and better read or ask twice, before doing something you do not fully understand

Ok just to make sure Im doing everything alright.
First, nothing to do with bootloader? Unlock or something?
Next, I create new folder on my pc on C partiton (because of cmd prompt you've said?), download adb and phone drivers and place them in the folder. Then install the drivers. Afterwards, download recovery and place it in the folder with adb and phone drivers and rename to recovery.img. Next, I reboot phone in bootloader and flash recovery. Then I have to reboot in bootloader again, how to? Phone will turn off so I can reboot in bootloader or what? Then I go in recovery, flash superuser.zip for rooted phone and afterwards flash custom rom. Thats it?

chorba69 said:
Ok just to make sure Im doing everything alright.
First, nothing to do with bootloader? Unlock or something?
Next, I create new folder on my pc on C partiton (because of cmd prompt you've said?), download adb and phone drivers and place them in the folder. Then install the drivers. Afterwards, download recovery and place it in the folder with adb and phone drivers and rename to recovery.img. Next, I reboot phone in bootloader and flash recovery. Then I have to reboot in bootloader again, how to? Phone will turn off so I can reboot in bootloader or what? Then I go in recovery, flash superuser.zip for rooted phone and afterwards flash custom rom. Thats it?
Click to expand...
Click to collapse
In bootloader, there is an option to reboot it,
While in fastboot usb mode, bootloader is the first option,
go into it (power button )....
There you can also find < recovery > option....

@chorba69
Go here and find the zip download link (here), extract to same folder as fastboot/adb (and optionally md5 check).
Reboot your phone into Fastboot (reboot to bootloader and if there is an option "fastboot", choose it, else you're already there)
Connect by USB (see the "+files" in my signature if you need windows drivers so your computer understands it's an android phone)
Open a command prompt window (hold shift, right click in the folder, open command prompt..)
Code:
fastboot flash recovery recovery.img
Wait for flash, if you see a message like "waiting for device", your phone isn't connected, you're on the wrong screen on your phone or your computer doesn't have the drivers installed.
Reboot back into bootloader
vol up/down, power button to choose Recovery
You now have a custom recovery (and you're viewing it), now you just have to select your zip from sdcard to flash it (this time the zip is the superuser/whatever).
Backups save phone's lives!
I'm curious about the first line of your hboot (after locked/unlocked/relocked)? e.g. mine is "SAGA PVT ENG S-OFF", if yours says "SAGA PVT SHIP S-OFF" then you're "radio s-off" and can do things like change your phones CID (let it use any network). If it's ENG S-OFF and not pre owned, then you're very lucky indeed (and some people might want more info about/a copy of your hboot)!

Paulie, I attached the image as you can see. Says it's PVT SHIP S-OFF. Do I need to do something before flashing recovery and superuser/rom etc? Or it's not important? Whats the difference anyways between PVT and ENG? And thanks ^^

Mhm. Just tried to flash recovery but recieved this message (attached). Im on FASTBOOT USB screen on phone and in the right directory on pc. Do I need to set up adb or something? Or what do I have to do now?

PVT is expected there, SHIP seems to mean "this version is for general release" whereas "ENG" signifies that it is an ENGineering version.
chorba69 said:
Mhm. Just tried to flash recovery but recieved this message (attached). Im on FASTBOOT USB screen on phone and in the right directory on pc. Do I need to set up adb or something? Or what do I have to do now?
Click to expand...
Click to collapse
I'm surprised you got this error. S-OFF should've meant you had no problem. Instead, you can try using the PG88IMG.zip method. Place the file in the root directory of your phone's SD card, reboot to bootloader and it should detect it and ask you if you want to apply the update.
Remember to delete/rename/move this zip file after it's done, as you'll not be able to use your bootloader normally whilst it is detected.
If you still get another error message, let us know!
Please be careful with the file below.
P88IMG.zip MD5: 729f7b435eadf6321ffc36d1da6a0f83
recovery.img MD5: b81b154d1381c9a7f23be39b645be38b

paulie-uk said:
PVT is expected there, SHIP seems to mean "this version is for general release" whereas "ENG" signifies that it is an ENGineering version.
I'm surprised you got this error. S-OFF should've meant you had no problem. Instead, you can try using the PG88IMG.zip method. Place the file in the root directory of your phone's SD card, reboot to bootloader and it should detect it and ask you if you want to apply the update.
Remember to delete/rename/move this zip file after it's done, as you'll not be able to use your bootloader normally whilst it is detected.
If you still get another error message, let us know!
Please be careful with the file below.
P88IMG.zip MD5: 729f7b435eadf6321ffc36d1da6a0f83
recovery.img MD5: b81b154d1381c9a7f23be39b645be38b
Click to expand...
Click to collapse
Hmm. So after I put that file on SD card, I have to flash it or flash the recovery.img? Or just when I put it and enter bootloader it will automatically start flashing the recovery?

[Q] Sensation alive....sort of

Hello to all you phone guru's,
I am pretty much a noob, so go easy on me please.
Back story...I have been interested in electronic for years and though I am ok on the hardware side of things, the software and programming I struggle with, I am trying to learn but like any beginner there are hurdles at which I stumble and have to ask for help, hence my typing the post.
My trade is mechanics so if you would like any car advice and I can help my door is always open.
Anyway, I bought the sensation I have as a little project, so I could start learning while hopefully getting a nice operating phone out of it as well, it is operating as far as I can get it into hboot etc and it has Tea Win recovery which I can access but that's about it, it appears to have no OS on it, no image....nothing.
I have tried to follow several guides on this site concerning RUU's and images but have failed to have any success, I have ADB downloaded and drivers....the details I have been able to get off phone are as follows:
hboot-1.27.0000
radio-11.23.3504.07_M2
open adsp-v02.6.0.2226.00.0131
eMMC-boot
jan 13th 2012.
unlocked s-on
---------------------------
C:\Program Files\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH16GV810960 recovery
C:\Program Files\Android\android-sdk\platform-tools>
cid: H3G__001 =
H3G-UK
-------------------------------
So now I have shared my problem, please bring forth the solutions, to which I really hope there are some.
Is the phone dead never to be revived?
Thank you for taking the time to read this and any help is appreciated.

since you can boot to the bootloader your device is not dead
the only thing it needs is to flash a custom rom from recovery
i suggest to use 4ext recovery because you are on S-ON
follow only step 2 from here(flashing a recovery)
http://forum.xda-developers.com/showthread.php?t=1631861
then download your desired rom and put it in your sdcard
boot to the recovery
enable smartflash from 4ext
flash the rom
done

rzr86 said:
since you can boot to the bootloader your device is not dead
the only thing it needs is to flash a custom rom from recovery
i suggest to use 4ext recovery because you are on S-ON
follow only step 2 from here(flashing a recovery)
http://forum.xda-developers.com/showthread.php?t=1631861
then download your desired rom and put it in your sdcard
boot to the recovery
enable smartflash from 4ext
flash the rom
done
Click to expand...
Click to collapse
Brilliant, thank you.
I will give it a go and post back if that ok?
One question, Will any uk RUU be ok, perhaps the latest ICS?

TommyTits said:
Brilliant, thank you.
I will give it a go and post back if that ok?
One question, Will any uk RUU be ok, perhaps the latest ICS?
Click to expand...
Click to collapse
since you are on S-ON you can use only the one which corresponds to your region(same firmware or higher) and cid

Neeeeed more help please...
Unfortunately the already suggested ideas have not worked.
So here I am pleading for help again.
I have tried flashing a few roms, 2 of which have installed but not solved the problem and the rom apparently for my phone cid and mid didn't want to installed at all, I have tried flashing PG58.img but again it simply doesn't want to know, I can't s-off for the fact that when it comes to reboot it reboots into the problem which is getting stuck on htc screen then nothing, I've relocked and unlocked via dev, I've also tried editing cid in PG58 img then flashing...still no joy.
I am stuck completely, my eyes are boggling from the amount of threads and posts I've trawled through and im a gnats **** away from taking a hammer to the phone
Anyone out there that can help?

Solved....
Please close thread.

TommyTits said:
Please close thread.
Click to expand...
Click to collapse
at least can you share us the solution so anyone else will benefit from it if it comes in a similar situation?

Absolutely...
rzr86 said:
at least can you share us the solution so anyone else will benefit from it if it comes in a similar situation?
Click to expand...
Click to collapse
Of course you are correct sir, my apologies.
Tbh I thought that nobody would look at my post as im a noob...
Turned out to be that there was a rom (the stock one installed fresh) but no boot
So accessed the rom file copied boot.img and pasted into sdk platform-tools, which I am sure
y'all know is adb, so in fastboot usb....flashed boot boot.img a voila a phone that does not get
stuck on htc screen.
Have a wifi issue now though, which I think may be a rom thing....yet more investigation under way.
Thanks to rzr86 for the help and communications.

TommyTits said:
Of course you are correct sir, my apologies.
Tbh I thought that nobody would look at my post as im a noob...
Turned out to be that there was a rom (the stock one installed fresh) but no boot
So accessed the rom file copied boot.img and pasted into sdk platform-tools, which I am sure
y'all know is adb, so in fastboot usb....flashed boot boot.img a voila a phone that does not get
stuck on htc screen.
Have a wifi issue now though, which I think may be a rom thing....yet more investigation under way.
Thanks to rzr86 for the help and communications.
Click to expand...
Click to collapse
that's why i told you to enable smartflash from 4ext in my 2nd post
smartflash is doing exactly what you did manually(with boot.img)
in S-ON devices boot partition is still protected so recovery can't flash the boot.img while installation except if you have enabled smartflash previously
that's why for S-ON users 4ext is more preferable

rzr86 said:
that's why i told you to enable smartflash from 4ext in my 2nd post
smartflash is doing exactly what you did manually(with boot.img)
in S-ON devices boot partition is still protected so recovery can't flash the boot.img while installation except if you have enabled smartflash previously
that's why for S-ON users 4ext is more preferable
Click to expand...
Click to collapse
Trust me my mate i tried what you said several times with 4ext and smartflash enabled only for it to start then abort install.
Hence my confusion and being stuck, i have no idea why it wouldn't install, i checked and double check that it was the right
boot img for rom but as i say it just refused to install boot img.

TommyTits said:
Trust me my mate i tried what you said several times with 4ext and smartflash enabled only for it to start then abort install.
Hence my confusion and being stuck, i have no idea why it wouldn't install, i checked and double check that it was the right
boot img for rom but as i say it just refused to install boot img.
Click to expand...
Click to collapse
maybe you were enabling smartflash in the wrong time
you just enable it exactly before flashing a rom

[Q] ROM question about installing

I want to install "[ROM][AROMA] KickDroidXL v5.2.0" but my htc one x (at&t) is completely stock.
So: step 1: unlocked with htcdev.com
step 2: Custom recovery
step 3: Firmware
Based on the "you need" info
Step 4: flash rom.
(I think i will s-off as well my mobile)
My questions are:
1) Is there any problem if i keep stock recovery?
2) On firmware instructions that is given here: "http://forum.xda-developers.com/showthread.php?t=2485865" 4th post
how should i do this throught commands (i use windows) or through my phone's screen when it is powered up by volume down and power buttons??
thanks a lot!

ps.christos said:
I want to install "[ROM][AROMA] KickDroidXL v5.2.0" but my htc one x (at&t) is completely stock.
So: step 1: unlocked with htcdev.com
step 2: Custom recovery
step 3: Firmware
Based on the "you need" info
Step 4: flash rom.
(I think i will s-off as well my mobile)
My questions are:
1) Is there any problem if i keep stock recovery?
2) On firmware instructions that is given here: "http://forum.xda-developers.com/showthread.php?t=2485865" 4th post
how should i do this throught commands (i use windows) or through my phone's screen when it is powered up by volume down and power buttons??
thanks a lot!
Click to expand...
Click to collapse
Here are your steps:
Before I can give any advice on the steps you need to take I need to see your bootloader details, the first five lines will do. I can answer your questions though.
1. You can't keep the stock recovery, a custom recovery is required on a modified phone.
2. The commands are issued through a command prompt on a Windows PC (you need to have adb/fastboot installed on the PC).
Sent from my Evita

timmaaa said:
Here are your steps:
Before I can give any advice on the steps you need to take I need to see your bootloader details, the first five lines will do. I can answer your questions though.
1. You can't keep the stock recovery, a custom recovery is required on a modified phone.
2. The commands are issued through a command prompt on a Windows PC (you need to have adb/fastboot installed on the PC).
Sent from my Evita
Click to expand...
Click to collapse
There are some changes of the planes and because of lack "playing" with my mobile i haven't reply you. So i desided to go for CyanogenMod 11.0 so instractions are:
" 1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU or later.
3.Flash a custom recovery (TWRP/CWM with SELinux capabilities).
4.Download latest nightly from http://download.cyanogenmod.org/?device=evita.
5.Locate 4.4 Gapps via a quick Google search.
6.Wipe factory/data reset in recovery before installing CM11.0 (unless you are already on a CM11.0 build).
7.Reboot into recovery and install nightly and gapps."
Before the instraction i think i should root and unlock the bootloader, so i used "[TOOL] HTC One X (Evita) All-In-One Toolkit V3.0.1 [7-7-2013] [PERM ROOT][Noob-Proof]" to unlock bootloader and root the phone. I have done this. I will (haven't do it yet) s-off and then flash custom recovery. Then it is the easy part i thing, (same as in every device, i have done it to htc desire).
So my question is am i rooted? Some apps like titanium backup and adfree gives me error, that is why i am thinging or i am not rooted or i have to "gain" su access through terminal. For flashing custome recovery i will use "[TOOL] HTC One X (Evita) All-In-One Toolkit V3.0.1 [7-7-2013] [PERM ROOT][Noob-Proof]" and for s-off i will try to use this guide "[S-Off] Facepalm S-Off for HTC One XL" any easier suggestions about s-off??
So to make our life easier here is what i get form power button + volume down:
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot

Forget about using the toolkit, all it does is act as a crutch and it clearly hasn't succeeded in rooting your device. Plus, it removes some vital learning experience which you definitely need.
You don't need root yet if you're going to flash a custom ROM. All that's required to install a custom recovery is an unlocked bootloader which you already have. The custom ROMs you want to install are pre-rooted.
To install a recovery is very simple, all it takes is a few fastboot commands. Download the modified version of TWRP 2.6.3.0 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
Once you've done this all you need to do is find a ROM and gapps and install them. Take a look at the Evita FAQ thread and the How-To Guide For Beginners thread in my signature, they contain some very valuable information that you'll need.
Sent from my Evita

timmaaa said:
Forget about using the toolkit, all it does is act as a crutch and it clearly hasn't succeeded in rooting your device. Plus, it removes some vital learning experience which you definitely need.
You don't need root yet if you're going to flash a custom ROM. All that's required to install a custom recovery is an unlocked bootloader which you already have. The custom ROMs you want to install are pre-rooted.
To install a recovery is very simple, all it takes is a few fastboot commands. Download the modified version of TWRP 2.6.3.0 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
Once you've done this all you need to do is find a ROM and gapps and install them. Take a look at the Evita FAQ thread and the How-To Guide For Beginners thread in my signature, they contain some very valuable information that you'll need.
Sent from my Evita
Click to expand...
Click to collapse
I found what i did wrong so now i have root my mobile! The guide that you posted is very helpfull, thanks for that! One last question though (hopefully last) i still have to go s-off for flashing CyanogenMod 11.0 since it is in the installation procedure right?? Thanks again.

You do need s-off, because you need to run the 3.18 RUU in order to flash any current aosp ROM. You must have s-off before you run the RUU or you'll brick.
Sent from my Evita

timmaaa said:
You do need s-off, because you need to run the 3.18 RUU in order to flash any current aosp ROM. You must have s-off before you run the RUU or you'll brick.
Sent from my Evita
Click to expand...
Click to collapse
I have done everything exept s-off. So now what i get in the "info" screen is what i had before, but at the begging it says *** TAMPERED *** , root works as well. The thing is i tried s-off using this method "http://forum.xda-developers.com/showthread.php?t=2155071" and i had exactly what it says i mean both in screens and the 92 error, but i always was s-on when system boot to bootloader at the end. I tried more times and after a point i tried the toolkit, from that point error 92 turned to error 99 (unkown error). Now this holds for both ways that i try. Any ideas what i do wrong? By the way i made a backup before starting the whole procedure. Thanks again and sorry for asking, but everything else was solven by reading and i can not reach as many info about s-off as it was for root.

The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app

timmaaa said:
The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just show the so wanted s-off. I read somewhere that error 99 will turn to "normal error 92" after rebooting. So yesterday i did 3 reboots and felt to sleep and today i tried the same procedure and now i am s-off! Sorry for the nagging!!

timmaaa said:
The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok i need your help again, if it is possible. I try to flash cm11 rom and i got the:
"E:error executing updater binary in zip ..........
E: error installing the zip file ......."
So i did my research and i thing the problem is due to recovery, right??
In this threat "[Q&A][CM 10.1][4.2.2] CyanogenMod 10.1 Questions and Help thread"
you have said: " Originally Posted by timmaaa View Post
No you can't use TWRP 2.6, you need to use the unofficial modified version of TWRP 2.6.3.0 from our Original Android Development section."
The thing is i am using TWRP 2.6.3.0 downloaded from here: "http://forum.xda-developers.com/showthread.php?t=1677447" should i go for "http://forum.xda-developers.com/showthread.php?t=2558503"??????
some more details (bootloader details):
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
e-MMC-boot
Thank you very much.

Well, only one of those links contains the unofficial modified TWRP 2.6.3.0 which is 4.4 compatible, so the answer should be simple.
Sent from my Evita

timmaaa said:
Well, only one of those links contains the unofficial modified TWRP 2.6.3.0 which is 4.4 compatible, so the answer should be simple.
Sent from my Evita
Click to expand...
Click to collapse
Do you know if there might be a problem with compatibility?? I mean if i try to restore back up made with TWRP 2.5 when i have the unofficial modified TWRP 2.6.3.0??i bet there is a backwords compatibility, right?
thanks again!

From all reports I've seen, they're not compatible. But even if you didn't want to flash KitKat ROMs you should never use TWRP 2.5 because it's super buggy and will cause issues. I'd say just flash the unofficial TWRP 2.6.3.0 and install the KitKat ROM of your choice. If you need to go back to stock there are other ways apart from a backup you can do it.
Sent from my Evita