Database Info

[Q] PLEASE HELP! random rebooting about every 5 min

random rebooting after flashing CM9 nightly roms. seems to be some kind of bug every time i start an application or turn on mobile data it cuases a reboot. i have flashed all of the following roms in an attempt to fix the problem:
PkMn ROM 4.1 Charmander
OrDroid V6.0.0
and the latest official cyanogenmod nightly
i did a restore to an ics lee droid rom i previously backed up before
and it seemed to run without a problem but after that i re flashed PkMn ROM for the sensation and now it performs a hot reboot instead. if anyone could help it would be greatly apprieciated as the problem seems to worsen after every reboot.
some times it would just go into a bootloop.

bryancruzdr said:
random rebooting after flashing CM9 nightly roms. seems to be some kind of bug every time i start an application or turn on mobile data it cuases a reboot. i have flashed all of the following roms in an attempt to fix the problem:
PkMn ROM 4.1 Charmander
OrDroid V6.0.0
and the latest official cyanogenmod nightly
i did a restore to an ics lee droid rom i previously backed up before
and it seemed to run without a problem but after that i re flashed PkMn ROM for the sensation and now it performs a hot reboot instead. if anyone could help it would be greatly apprieciated as the problem seems to worsen after every reboot.
some times it would just go into a bootloop.
Click to expand...
Click to collapse
I think some partition is still corrupted.. I recommend you to do a wipe from recovery rather than scripts (if using 4ext then wipe/format ->>format all partitions except sdcard) and then flash another rom Again
If that didn't solved the issue RUU is the next thing.. If you are soff and supercid then get any ics RUU and run it.. It completely formats through phone and takes everything to stock.. But still retains soff.. So you revert back to normal once you do a ruu run(remember ruu run should be done with device in fastboot)
Sent from my pyramid.. Through blazing fast sonic waves

Thank You so much!
i will try this, but which RUU do you recommend i run?

bryancruzdr said:
Thank You so much!
i will try this, but which RUU do you recommend i run?
Click to expand...
Click to collapse
RUU is just to clean the partitions.. So just get any.. If you want one get the Europe umbranded one(latest)
Check in pyramid shipped rom collections thread in sensation Android Development section
Sent from my pyramid.. Through blazing fast sonic waves

Before you look into a partition problem, which is a pain to fix, check to make sure the battery is securely seated in the phone.
The batteries can become loose over time. Not very loose, but just enough to break electrical contact. And if the electrical contact is broken and restored quickly, a reboot is likely.
Open the phone and see if the battery wiggled. See if you can create the reboot problem by jiggling the battery. If you can, there are a few things to try to make the battery tighter.

Skipjacks said:
Before you look into a partition problem, which is a pain to fix, check to make sure the battery is securely seated in the phone.
The batteries can become loose over time. Not very loose, but just enough to break electrical contact. And if the electrical contact is broken and restored quickly, a reboot is likely.
Open the phone and see if the battery wiggled. See if you can create the reboot problem by jiggling the battery. If you can, there are a few things to try to make the battery tighter.
Click to expand...
Click to collapse
Thanks for your suggestion. i saw a post on this yesturday, and this doesnt seem to be my issue, althought i tried the trick that is mentioned on the post, about putting a business card to make it tighter, and it deffinitely made it very tight, but the issue remained. thanks for your help though
such a friendly and helpful community

bryancruzdr said:
random rebooting after flashing CM9 nightly roms. seems to be some kind of bug every time i start an application or turn on mobile data it cuases a reboot. i have flashed all of the following roms in an attempt to fix the problem:
PkMn ROM 4.1 Charmander
OrDroid V6.0.0
and the latest official cyanogenmod nightly
i did a restore to an ics lee droid rom i previously backed up before
and it seemed to run without a problem but after that i re flashed PkMn ROM for the sensation and now it performs a hot reboot instead. if anyone could help it would be greatly apprieciated as the problem seems to worsen after every reboot.
some times it would just go into a bootloop.
Click to expand...
Click to collapse
I always use super wipe when flashing new roms
Sent from my HTC Sensation using xda premium

OreoBoyVa said:
I always use super wipe when flashing new roms
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Formatting all partitions is better than SuperWipe. It will ensure everything is completely cleaned out.

ganeshp said:
RUU is just to clean the partitions.. So just get any.. If you want one get the Europe umbranded one(latest)
Check in pyramid shipped rom collections thread in sensation Android Development section
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
While Running RUU i get "Error [156] Image Error" ive downloaded atleast 4 different ics ruu's and get the same error. perhaps this is the initial problem?

bryancruzdr said:
While Running RUU i get "Error [156] Image Error" ive downloaded atleast 4 different ics ruu's and get the same error. perhaps this is the initial problem?
Click to expand...
Click to collapse
no no are you SOFF ?
if you are not SOFF but has unlocked bootloader..then relock it before running RUU
(fastboot oem lock)
then run the RUU..with phone connected in bootloader

i am s-off
if it helps heres what it says on the bootloader:
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
i put it on fastboot and connect it to my computer when running RUU. am i missing anything?

bryancruzdr said:
i am s-off
if it helps heres what it says on the bootloader:
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
i put it on fastboot and connect it to my computer when running RUU. am i missing anything?
Click to expand...
Click to collapse
ok we do it different way then
first extract the rom.zip from any ICS RUU (choose one )
here is the guide to extract the rom.zip
http://www.htcsensationforum.com/htc-sensation-rooting/how-to-extract-rom-zip-from-ruu/
then keep the rom.zip in adb folder
keep the phone in fastboot
and connect it to pc (mobile reads "fastboot usb")
now type these commands one by one
1.fastboot erase cache
2.fastboot oem rebootRUU
3.fastboot flash zip rom.zip
4.fastboot reboot
if worked fine otherwise
im particularly interested in the complete output of the third command
so use PASTEBIN to paste the output and then repost the url with the pasted output

ganeshp said:
no no are you SOFF ?
if you are not SOFF but has unlocked bootloader..then relock it before running RUU
(fastboot oem lock)
then run the RUU..with phone connected in bootloader
Click to expand...
Click to collapse
Check point 4 of my RUU guide. You can link all such questions there. Detailed explanation & methods.
I'm just suggesting because you gave him a very short explanation.
EDIT: Sorry, I probably didn't see that this is solved.
ganeshp said:
keep the phone in fastboot
and connect it to pc (mobile reads "fastboot usb")
now type these commands one by one
1.fastboot erase cache
2.fastboot oem rebootRUU
3.fastboot flash zip rom.zip
4.fastboot reboot
Click to expand...
Click to collapse
Some questions. The method from above is the same one used for flashing engineering bootloader after JB S Off
So, what exactly is this RUU mode? And does it bypass CID and fw version checks?
Also, what are the requirements for this mode to work (i.e. S-Off, unlocked bootloader)?
What are the benefits of using this over renaming rom.zip to PG58IMG.zip and flashing?
Thanks a lot for this. It will surely come in handy sometime & will definitely go into my guide.

kgs1992 said:
Some questions. The method from above is the same one used for flashing engineering bootloader after JB S Off
So, what exactly is this RUU mode? And does it bypass CID and fw version checks?
Also, what are the requirements for this mode to work (i.e. S-Off, unlocked bootloader)?
What are the benefits of using this over renaming rom.zip to PG58IMG.zip and flashing?
Thanks a lot for this. It will surely come in handy sometime & will definitely go into my guide.
Click to expand...
Click to collapse
its the same way as flashing via PG58IMG way
to bluntly say the PG58IMG flashing ..internally does the flashing the same way I've put it
RUU mode is the lowest level(visible) mode where flashing of bootloader,firmware,radio and even ROM is possible but the file format should be of PG58IMG zip
so simply put any PG58IMG.zip file which is not being parsed by bootloader properly can be manually flashed the above way
the same requirements that apply for PG58IMG.zip file applies over here too
i.e SOFF (irrespective of type of bootloader)
or unlocked bootloader with SON ...(remember in this case as only recovery,boot,data,system partitions are opened only those partitions can be flashed )

ganeshp said:
its the same way as flashing via PG58IMG way
to bluntly say the PG58IMG flashing ..internally does the flashing the same way I've put it
RUU mode is the lowest level(visible) mode where flashing of bootloader,firmware,radio and even ROM is possible but the file format should be of PG58IMG zip
so simply put any PG58IMG.zip file which is not being parsed by bootloader properly can be manually flashed the above way
the same requirements that apply for PG58IMG.zip file applies over here too
i.e SOFF (irrespective of type of bootloader)
or unlocked bootloader with SON ...(remember in this case as only recovery,boot,data,system partitions are opened only those partitions can be flashed )
Click to expand...
Click to collapse
Thanks a lot Ganesh! Very useful info. So you mean that in this mode CID check is bypassed. That's nice.

kgs1992 said:
Thanks a lot Ganesh! Very useful info. So you mean that in this mode CID check is bypassed. That's nice.
Click to expand...
Click to collapse
no please don't get me wrong
at the end the zip we are flashing requires android-info.txt too (PG58IMG.zip has it too) which has cid and mid to it
the cid check is bypassed only when you are SOFF or has unlocked bootloader (for unlocked bootloader ..we still require cid signed radio,hboot (firmware) to update them via this method ..this is required as they are still secured [SON])
the above way of flashing gives you much more detail of whats happening when on command prompt..where we can identify the problem ..when flashing RUU..precisely

ganeshp said:
no please don't get me wrong
at the end the zip we are flashing requires android-info.txt too (PG58IMG.zip has it too) which has cid and mid to it
the cid check is bypassed only when you are SOFF or has unlocked bootloader (for unlocked bootloader ..we still require cid signed radio,hboot (firmware) to update them via this method ..this is required as they are still secured [SON])
the above way of flashing gives you much more detail of whats happening when on command prompt..where we can identify the problem ..when flashing RUU..precisely
Click to expand...
Click to collapse
Thanks for the clarifications. I will add it to the guide because this is really a nice method.

[Q] Steps to install CleanROM 6.5?

I have recently restored my phone back to stock rom due to a soft-brick.
I need a step by step approach to help me install CleanROM 6.5 into my HTC One X (AT&T).
The CleanROM 6.5 thread is here: http://forum.xda-developers.com/showthread.php?t=1655011
The steps in the thread are too vague and general for me.
This is my phone's software information:
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.85.502.3 710RD
HTC SDK API level: 4.11
HTC Extension version: HTC Extension_403_1_GA_4
More: Baseband, Kernel version, etc.
-I have CleanROM 6.5.zip downloaded
-I have my phone rooted using the approach from here: http://forum.xda-developers.com/showthread.php?t=1709424
-I have tried following the steps from threads in the Development section and I'm not entirely sure whether what to do next in my case
What are my next steps to installing CleanROM 6.5? Please provide step-by-step instructions as I don't want to mess up. Thanks!

synconclick said:
I have recently restored my phone back to stock rom due to a soft-brick.
I need a step by step approach to help me install CleanROM 6.5 into my HTC One X (AT&T).
The CleanROM 6.5 thread is here: http://forum.xda-developers.com/showthread.php?t=1655011
This is my phone's software information:
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.85.502.3 710RD
HTC SDK API level: 4.11
HTC Extension version: HTC Extension_403_1_GA_4
More: Baseband, Kernel version, etc.
-I have CleanROM 6.5.zip downloaded
-I have my phone rooted using the approach from here: http://forum.xda-developers.com/showthread.php?t=1709424
-I have tried following the steps from threads in the Development section and I'm not entirely sure whether what to do next in my case
What are my next steps to installing CleanROM 6.5? Please provide step-by-step instructions as I don't want to mess up. Thanks!
Click to expand...
Click to collapse
Troll?

exad said:
Troll?
Click to expand...
Click to collapse
I'm not trolling. I seriously need help. Tell me what I'm doing inappropriate and I will fix it.

synconclick said:
I'm not trolling. I seriously need help. Tell me what I'm doing inappropriate and I will fix it.
Click to expand...
Click to collapse
Is your bootloader locked or unlocked?
S-ON or S-OFF?
Before we continue, I will advise you that the fact you need me to make out a step by step guide for you means you should remain stock. Please do not take this advice lightly. I am very serious and I am not trying to insult you or make myself seem superior to you or keep the XDA community exclusive (all of which I've been accused of when offering this advice). You should really read and understand before you do something like this because when something goes wrong, and something WILL go wrong, there's no guaranty anyone will be around to help you.
If you want to continue, just answer those two questions above. I'll help you but just remember, I warned you

exad said:
Is your bootloader locked or unlocked?
S-ON or S-OFF?
Before we continue, I will advise you that the fact you need me to make out a step by step guide for you means you should remain stock. Please do not take this advice lightly. I am very serious and I am not trying to insult you or make myself seem superior to you or keep the XDA community exclusive (all of which I've been accused of when offering this advice). You should really read and understand before you do something like this because when something goes wrong, and something WILL go wrong, there's no guaranty anyone will be around to help you.
If you want to continue, just answer those two questions above. I'll help you but just remember, I warned you
Click to expand...
Click to collapse
bootloader is relocked
as for S-ON or S-OFF, I don't understand. How do I check?
I've been trying to read and understand all this, but I have a feeling I've been reading wrong threads. If there's any links for a complete understanding of all this, that'd be nice.

synconclick said:
bootloader is relocked
as for S-ON or S-OFF, I don't understand. How do I check?
I've been trying to read and understand all this, but I have a feeling I've been reading wrong threads. If there's any links for a complete understanding of all this, that'd be nice.
Click to expand...
Click to collapse
S-On or S-oFF will be in your bootloader screen.
SInce you're relocked you'll have to unlock the bootloader again first. the unlock_code.bin should work again if you still have the one you got when you first unlocked the bootloader. Do you still have the unlock_code.bin?

exad said:
S-On or S-oFF will be in your bootloader screen.
SInce you're relocked you'll have to unlock the bootloader again first. the unlock_code.bin should work again if you still have the one you got when you first unlocked the bootloader. Do you still have the unlock_code.bin?
Click to expand...
Click to collapse
It says EVITA PVT SHIP S-ON RL.
No, I do not have the unlock_code.bin

synconclick said:
It says EVITA PVT SHIP S-ON RL.
No, I do not have the unlock_code.bin
Click to expand...
Click to collapse
Ok.. is your CID still 11111111
if you don't know boot to bootloader/fastboot and do:
fastboot oem readcid
Or
fastboot getvar cid

exad said:
Ok.. is your CID still 11111111
if you don't know boot to bootloader/fastboot and do:
fastboot oem readcid
Or
fastboot getvar cid
Click to expand...
Click to collapse
Yes

So the first step is to go to htcdev.com and get a new unlock_code.bin so you can unlock the bootloader.
Htcdev.com has all the instructions to get the unlock_code.bin
Once you receive it you'll want to put the unlock_code.bin in your fastboot folder, boot your phone to bootloader/fastboot and do:
fastboot flash unlocktoken Unlock_code.bin
Then select unlock bootloader in your phones screen.
Then verify that it worked in bootloader. If it didn't (sometimes it doesn't work right away) press and hold power to simulate a battery pull, when the screen goes black after capacitive buttons blink a bunch of times, let go of power, press and hold volume down until the bootloader comes up and the try again. It should work that time.
Once the bootloader is unlocked post here and I'll guide you through the rest.
Sent from my HTC One X using xda app-developers app

exad said:
So the first step is to go to htcdev.com and get a new unlock_code.bin so you can unlock the bootloader.
Htcdev.com has all the instructions to get the unlock_code.bin
Once you receive it you'll want to put the unlock_code.bin in your fastboot folder, boot your phone to bootloader/fastboot and do:
fastboot flash unlocktoken Unlock_code.bin
Then select unlock bootloader in your phones screen.
Then verify that it worked in bootloader. If it didn't (sometimes it doesn't work right away) press and hold power to simulate a battery pull, when the screen goes black after capacitive buttons blink a bunch of times, let go of power, press and hold volume down until the bootloader comes up and the try again. It should work that time.
Once the bootloader is unlocked post here and I'll guide you through the rest.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Do I select All Other Supported Models on this page? http://www.htcdev.com/bootloader/

Yes
Sent from my HTC One X using xda app-developers app

Got it. Successfully unlocked

Good. Next you'll want to download twrp 2.3.3.1 from goo.Im
Then check md5 to make sure the download is not corrupt. Google md5 checker if you need one.
Then put it in your fastboot folder. Boot to bootloader/fastboot
Fastboot flash recovery twrp2.3.3.1filename.img
Fastboot erase cache
Fastboot reboot bootloader
Select recovery from bootloader screen on your phone.
Mount usb storage in twrp with your phone connected to the pc.
Copy your Rom to your phone
Unmount your phone usb storage
Select wipe in twrp
Wipe cache, dalvik, system, factory reset
Go to install in twrp
Select your Rom.
Follow procedure on phone screen
Reboot phone when flash successful.
Because your hboot is under 1.14 that is all. If it was 1.14 or higher you would have to extract the boot.img from the Rom and fastboot flash boot boot.img
Also with s-on never ruu or ota to 3.18 or you will brick. Installing roms based on 3.18 is fine though.
Sent from my HTC One X using xda app-developers app

exad said:
Good. Next you'll want to download twrp 2.3.3.1 from goo.Im
Then check md5 to make sure the download is not corrupt. Google md5 checker if you need one.
Then put it in your fastboot folder. Boot to bootloader/fastboot
Fastboot flash recovery twrp2.3.3.1filename.img
Fastboot erase cache
Fastboot reboot bootloader
Select recovery from bootloader screen on your phone.
Mount usb storage in twrp with your phone connected to the pc.
Copy your Rom to your phone
Unmount your phone usb storage
Select wipe in twrp
Wipe cache, dalvik, system, factory reset
Go to install in twrp
Select your Rom.
Follow procedure on phone screen
Reboot phone when flash successful.
Because your hboot is under 1.14 that is all. If it was 1.14 or higher you would have to extract the boot.img from the Rom and fastboot flash boot boot.img
Also with s-on never ruu or ota to 3.18 or you will brick. Installing roms based on 3.18 is fine though.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I'm not sure which TWRP is correct to download. I searched up twrp 2.3.3.1 from goo.lm and got a list of options

synconclick said:
I'm not sure which TWRP is correct to download. I searched up twrp 2.3.3.1 from goo.lm and got a list of options
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img

mebyUni can
ronnie498 said:
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Click to expand...
Click to collapse
I tried verifying with MD5 Check and it says the codes do not match.
Also, when I tried downloading from the link, I get
"We are currently experiencing difficulties with one or more of our distribution servers. Please hang tight for this to get resolved"

synconclick said:
I tried verifying with MD5 Check and it says the codes do not match.
Also, when I tried downloading from the link, I get
"We are currently experiencing difficulties with one or more of our distribution servers. Please hang tight for this to get resolved"
Click to expand...
Click to collapse
You have a message

Goo.Im link seems to be up right now
Sent from my HTC One X using xda app-developers app

ronnie498 said:
You have a message
Click to expand...
Click to collapse
Thank you! I downloaded the file now. But what about the problem from MD5 Check?

Firmware Update Q&A [extra noob friendly]

WARNING*WARNING*WARNING
do this at your own risk! This is for s4 only!!
It has been brought to my attention that there might be a mid (model id) conflict
With flashing this and me along with others are trying to narrow down the issue. Thanks to @real187 for bring this to my attention.
I'm
S-off
Cid 11111111
MID PJ4011000
And had no problems flashing this firmware but others with same setup have reported soft brick.
OK I think @mkinney88 may have pin pointed where the soft brick may be coming from. If you s-off using facepalm, flash the firmware.zip and get soft bricked try this.
1. Get back to s-on (warning read directions several times before doing you CAN hard brick your phone) ~ http://forum.xda-developers.com/showthread.php?p=38267667
2. Get s-off with moonshine ~ http://forum.xda-developers.com/showthread.php?p=42613403
First off this is mostly ment for the T-Mobile branded phones but ill try and help all please let me know when asking questions if you have a T-Mobile or HTC branded phone (it has it right on the front of phone ).
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111 (I had no problem flashing firmware with s-off and Cid 11111111 but others have reported problems so if you don't want to chance it write your Cid to T-MOB010)
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin

Downloads
FIRMWARE ZIP DOWNLOAD
https://drive.google.com/folderview?id=0B-BYnLh2sosKamRwaUJJS05oU3M&usp=sharing or http://db.tt/Wua8mDS2
Credit go's to mkinney88 for the firmware

Bricks
First off if you can get into bootloader then you don't have a hard brick.
If your phone is in the black screen of death there may be hope but we're still trying to figure that one out.
If your phone doesn't respond to any input from you (power, power+volume down) then congratulations you have a hard brick but don't through it in the junk drawer just yet, you can have it jtag repaired (they open phone plug into main board and flash everything)
Here's the link (you do have to pay for this)
http://forum.xda-developers.com/showthread.php?p=37136553

One more just in case

rc420head said:
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin
Click to expand...
Click to collapse
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though

vatsaman said:
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though
Click to expand...
Click to collapse
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!

I put a note of this in op just now, thanks for the warning, I'm trying to figure out why some can do this Cid 11111111 and some can't.
-----------------------------------------
Friends don't let friends post without searching first!

rc420head said:
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!
Click to expand...
Click to collapse
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.

vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
Something else is going on. I used facepalm, and Cid 11111111 to flash firmware twice now with no issues and started same as you hboot 1.14
-----------------------------------------
Friends don't let friends post without searching first!

thank you!

I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?

khan.orak said:
I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?
Click to expand...
Click to collapse
I'm not sure if I understand your question. So let me ask a few questions.
What hboot are you on?
What carrier are you using?
Are you wanting to try cm 10.1 and afraid for losing stock?
What is stock just HTC sense 4+ or is there carrier added stuff?

rc420head said:
I'm not sure if I understand your question. So let me ask a few questions.
Click to expand...
Click to collapse
ok I'll try to make it clearer.
What hboot are you on?
Click to expand...
Click to collapse
I'm on hboot 2.15.0000
What carrier are you using?
Click to expand...
Click to collapse
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Are you wanting to try cm 10.1 and afraid for losing stock?
Click to expand...
Click to collapse
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
What is stock just HTC sense 4+ or is there carrier added stuff?
Click to expand...
Click to collapse
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.

khan.orak said:
ok I'll try to make it clearer.
I'm on hboot 2.15.0000
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.
Click to expand...
Click to collapse
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)

rc420head said:
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)
Click to expand...
Click to collapse
Thanks for the reply, really much appreciated.
I already have rooted the device and custom recovery TWRP 2.5. Though I am considering to downgrade it to 2.3.30. Now I made a backup of stock ROM. (System + Boot Partition)
So is this the only way I can get to stock?
I read somewhere that the following method could be used too(?)
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?

khan.orak said:
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?
Click to expand...
Click to collapse
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app

ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Big thanks! :good:

vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app

ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Yes this will also work (I was under the impression no ruu's were available)
khan.orak said:
Big thanks! :good:
Click to expand...
Click to collapse

forgiven90 said:
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah disabling the fast dormancy solved all my problems. :good:

[Q] S-OFF F/W 3.14.531.17 (T-MOB) possible?

I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?

Bump
Sent from my One S using XDA Premium 4 mobile app

My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.

tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?

bump

Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.

evrycard said:
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
Click to expand...
Click to collapse
He probably cannot downgrade from *.17 to *.11.
I don't know what parts of the firmware moonshine needs. But you could try downgrade using a OTA or Nandroid.

Same here
I'm pretty much stuck with a One-S Bootloader unlocked with S-on.
I can't find a way to get S-Off. Just googling and throwing prayers in the sky someone develops a way.

pyrocide said:
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
Click to expand...
Click to collapse
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app

havikx said:
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It took me 5 hours total to begin finding all req's and trying the above method, finding it not to work, redoing the RUU *.17 and getting BACK on CM10.2 and having a phone to make calls with. The method above took maybe 20-30 minutes of double checking and making sure i didn't miss something.

Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.

tivofool said:
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
Click to expand...
Click to collapse
PM'd him for more info. Thanks!

So I was having problems getting s-off as well, eventually I got it done, but it was definitely a big trial and error process.
What I ended up doing was:
1) Get the 3.14.531.11 RUU from http://www.androidruu.com/index.php?developer=Ville (make sure you get the TMOUS one) This link is also provided in the first post in the Android development section
2) I ended up using Moonshine S-Off (http://forum.xda-developers.com/showthread.php?t=2325590) but I needed to use it in conjunction with running it on Ubuntu. Luckily I had a spare hard drive lying around. If you don't, I believe you can run it through the CD as well as long your burn the Ubuntu.iso on a disc. Plug in your phone to the computer and let it do its magic
3) From there, if you wanted to, you can change to SuperCID. Since you have s-off by then, you can change it from the fastboot usb in the bootloader with the line fastboot oem writecid 11111111 (double check, i'm just writing off the top of my head)
4) Then install roms and etc through the usual custom recovery
Note. I tried the Maximus HD, yes it was nice, but it didn't allow me to utilize my phone as a hotspot, so I ended up using the Dark Jelly rom instead. So far it's been very nice. The hotspot works, but the tethering portion is still unavailable. Just my two cents.

I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise

tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
i can say that this worked for me as well. i didn't relock bootloader before installing the 3.14.531.11 ruu though. still worked for me. also installed moonshine on windows. ( guess i'm lucky )

bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
You saved me so much time. Thanks!

bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
I do not understand meet all the requirement and I run it step by step and still gets stuck in step 3 moonshine I need urgent help, thanks

pyrocide said:
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Click to expand...
Click to collapse
Test... click here
http://forum.xda-developers.com/showthread.php?t=2569755

[Q]Hboot/Firmware update 2.15 to 2.16 et al.
Sorry wrong thread.

[Q] Stuck on Hboot/fastboot with full stock phone

Hi guys,
My sister sent me her HTC One SV aka K2-UL i offered her from expansys on june, it is stuck on Hboot
*** LOCKED***
K2_UL XA SHIP S-ON RL
HBOOT-2.00.0000
eMMC Boot
...
I can go to Fastboot USB ( or AC )
She 's worst than a noob so phone is stock, up to date but non-root non-unlock, still S-ON and so on.
just once phone reboot and stay stuck...
From here i can navigate but after reboot i'm still here.
I tried :
factory reset and recovery (with rom renamed PL80DIAG but would be too easy...)
RUU but RUU asked for bootloader so stuck on "waiting for bootloader"
go to htc dev to unlock bootloader but after flash unlock token ( unlock token check successfully) but : Nothing happens and still writtten ***Locked*** then if I "fastboot oem unlock" it says failed :<remote : loading custom splash failed>
fastboot flash boot.img but nothing works since still S-on and locked bootloader (superCID is out too)
flash custom recovey or even fresh stock recovery but nothing worked for the same reasons...
Do you guys have any idea of something i could do?
Thanks for your answer and forgive my English I'm French

As long as you are ***LOCKED*** you can quiet do nothing.
To use our available RUU you must also be unlocked & S-Off.

Somewhat the same situation
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
I can get into Fastboot as well as bootloader, I CANNOT GET INTO RECOVERY. I have tried to restore with the respective RUU files from the All things HTC ONE SV forum. I have also tried to flash the recovery boot and radio img files through fastboot usb. NONE of this has worked for me. I really enjoyed this phone before I went and made it all FUBR. If there is anyway to get it to boot to any recovery or rom, i will much appreciate it. Thanks for all your help from previous posts as well as any future help I get from information posted here.

Related to your hboot, you should be able to flash any recoveries, but i usually recommend this one.
What command do you use to flash recovery and do you get an output from "fastboot devices"?

Thedc24 said:
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
Click to expand...
Click to collapse
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.

eduardog131 said:
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.
Click to expand...
Click to collapse
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk

Modding.MyMind said:
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Well then I was right then I was wrong. Sorry. HBOOT versions for the Sensation are stuck in my mind.
Sent from my HTC Sensation

Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.

Thedc24 said:
Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.
Click to expand...
Click to collapse
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation

He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.

old.splatterhand said:
He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.
Click to expand...
Click to collapse
Wow! Awsome! This bad boy booted. I was able to flash the rom through recovery. This is much further than I expected to get with this device. Now when I try to go S-Off with either moonshine or rumrunner I get an error saying not able to make adb connection. When I use fastboot devices my device will show up...if i do adb devices nothing...Would love to have S-Off and SU installed. But like I said this is much further than I expected to get so anything further is icing on the cake. Thanks in Advance.

Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?

old.splatterhand said:
Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?
Click to expand...
Click to collapse
He can just use the Naked Driver for the adb driver. http://forum.xda-developers.com/showthread.php?t=2263822

Ok I DID have USB debugging enabled. After messing with the drivers and my Windows 8 computer, I have came to the conclusion that it is something with the drivers and their compatibility with Windows 8. Either way moonshine or rumnunner never worked for me in a windows 8 environment. I dual boot ubuntu 12.04 anyway, it saw my device just fine adb and fastboot. I ran moonshine and it went through all the testing stages, but was never able to completely run...so I still have no S-Off. Do I need to update Hboot or anything? Also am I able to load a custom rom on this device with S-ON? I have been looking but I do not see many out for this device at all, which is a shame because I feel as though it is very comparable to my GS3. It would be nice to see a nice AOSP ROM on this device. But all take any updates I can for the device, hopefully it will help with the issue I have will cell reception dropping all the time. Thanks

To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!

old.splatterhand said:
To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!
Click to expand...
Click to collapse
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
eduardog131 said:
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation
Click to expand...
Click to collapse
Yea that would be cool. I am assuming I would just flash it through recovery?

Thedc24 said:
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
Yea that would be cool. I am assuming I would just flash it through recovery?
Click to expand...
Click to collapse
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk

eduardog131 said:
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?

Thedc24 said:
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?
Click to expand...
Click to collapse
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)

eduardog131 said:
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)
Click to expand...
Click to collapse
Downloading now. I will let you know how it goes...thanks a million.
This is what I got when I tried to flash the rom:
sending 'zip' (691470 KB)...
OKAY [ 37.267s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 37.301s
I dont understand if I am S-Off and super CID.