Database Info

Help Rom Won't Boot

Hi I recently obtained a bunch of free smart phones via my job at t-mobile and people upgrading and just not wanting their old smart phones. One of them was a HTC sensation. I have rooted many phones for years now but this one wants to give me issues. I rooted it, got super user installed and CWM recovery and installed jellybean. When it boots into CM10 it never gets past the boot screen. In HBOOT it says son rl HBOOT 1.27.0000. I cannot for the life of me figure out what is wrong. I did a full wipe and everything. Lucky for me this is a play phone but I still would like to get it up and running. If anyone could please help me figure this out. Thank you

First, please do not post questions in the dev section.
Second, you're s-on so you have to flash your boot.img through fastboot. The boot partition is protected with s-on...

And where do I obtain the boot.img? Sorry for posting here I guess nobody had a problem with it in the DINC forums.
GROGG88 said:
First, please do not post questions in the dev section.
Second, you're s-on so you have to flash your boot.img through fastboot. The boot partition is protected with s-on...
Click to expand...
Click to collapse

wetbo529 said:
And where do I obtain the boot.img? Sorry for posting here I guess nobody had a problem with it in the DINC forums.
Click to expand...
Click to collapse
Extract it from your rom.

Ok I did that and when I go into HBOOT how do I flash it? Sorry again for the noob question and thank you for all your help?
GROGG88 said:
Extract it from your rom.
Click to expand...
Click to collapse

wetbo529 said:
Ok I did that and when I go into HBOOT how do I flash it? Sorry again for the noob question and thank you for all your help?
Click to expand...
Click to collapse
First get familiar with fastboot commands: http://wiki.cyanogenmod.com/wiki/Fastboot
You'll need adb and fastboot setup on your computer and you'll use the following command from terminal or cmd prompt:
Code:
fastboot flash boot /path/to/<boot>.img
Your other option is to flash a rom that uses the stock boot image. There are two TMOUS based roms to choose from: mine, or ARHD.

Have you update to Firmwaer 3.33?
/ Sent from my Sensation XE /

lol

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] Set Telstra HTC One XL to s-off

Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks

jacen72 said:
Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks
Click to expand...
Click to collapse
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita

timmaaa said:
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?

jacen72 said:
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?
Click to expand...
Click to collapse
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita

timmaaa said:
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the info - i know i need to superCID as i checked last night and CID was TELST001 (from memory). Will use 11111111.

No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita

timmaaa said:
No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita
Click to expand...
Click to collapse
I tried so many things last night i couldn't tell you exactly what i did, haha! Will try your way and see what it says.
A quick question - in regard to the facepalm link, it says "Download patcher and unzip it in your working directory" - can this be any folder on my phone (eg: Downloads)? I'm also guessing the other file (OneX.zip) goes in the same directory?

No you place the extracted patcher files and the PJ8312000-OneX.zip into your fastboot folder on your pc.
You need to have adb/fastboot and HTC drivers installed on your pc to do the s-off process.
Sent from my Evita

jacen72 said:
I tried so many things last night i couldn't tell you exactly what i did, haha
Click to expand...
Click to collapse
You should keep better track of things you are doing or you will end like NASA on Apollo 1 and not knowing what went wrong.
To repair something you need to know what you did to break it.

Big thanks timmaaa, have upgraded successfully!
twistedddx, you're not wrong - i should have kept an eye on what i was doing. Luckily for me, all went well!
Thanks again.

Glad to see you got it all sorted mate.
Sent from my Evita

Hi guys, since updating Android, i seem to find my service connection (no service) is being lost fairly easily - is there something i need to do in regard to this, or is it just me?!
Cheers

Which ROM are you on?
Sent from my Evita

timmaaa said:
Which ROM are you on?
Sent from my Evita
Click to expand...
Click to collapse
the one from the following link:
http://forum.xda-developers.com/showthread.php?t=2442946

You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita

timmaaa said:
You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, when you talk about beastmode, is the following link what you are referring to?
http://forum.xda-developers.com/showthread.php?t=1797251
Also, with firmware 2.15 - i would actually like to keep it as stock as possible, so perhaps the firmware upgrade would be the better option? I have found a link that looks like it goes to the correct download:
http://forum.xda-developers.com/showthread.php?p=45646878 - (see last post)
Would i be right in saying the instructions for updating the kernel would be the same as at the following link:
http://forum.xda-developers.com/showthread.php?t=2423735 - (OPTIONAL: Installing the Firmware)
Thanks again for your help.

The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita

timmaaa said:
The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita
Click to expand...
Click to collapse
Thanks - looks easy enough. Can i ask what why i would install Beastmode instead of the firmware upgrade? From what i gather, it is to overclock the CPU?

You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita

timmaaa said:
You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, maybe i will install beastmode instead then if it will help fix my connection issues. Sorry, but would you be able to point in the direction of where it is in the development section, i cannot seem to find it.
I promise if this works you wont have to hear my noob questions anymore!!

[Q]Please help connecting to PC

I hope I'm in the right place. I can't connect at all to the PC since I flashed the AOKP_jb_mr1_build4 ROM. The PC says can't find device driver.
Also, I would love to update to newer builds, requiring a newer hboot version I gather, but not quite sure as to how to go about that, and deal with s-on. I only want to do what has to be done to get the latest AOKP ROM builds. Any advice would be greatly appreciated...
I am using HTC one x, Evita, rooted, (not sure about supercid, I think so), s-on, hboot 1.14, and trwp 2.6+.
Even though I've had my phone a year, I'm still quite the noob when it comes to all this. Heavy forum reading...re-reading. I'm looking for any definitive help on getting me set up on the last steps here.
Sent from my One X using xda app-developers app

Newer builds do require an upgrade but it's not just the hboot that needs upgrading, it's the firmware as a whole which needs upgrading. The firmware does contain the hboot as a component and it is also usually identified by the hboot version number that it contains, I guess that's why there's a common misconception that it's just the hboot you need to upgrade.
Anyway, what you need to do is run the 3.18 RUU which will give you the 2.14 firmware modules. In order to run the RUU you'll first need s-off otherwise you'll end up with a brick. In order to get s-off you need to be sure you have SuperCID, without SuperCID the s-off process won't work. I know this all seems like a lot of work but it's a pretty easy process. Not having s-off at this stage is a stupid hindrance, without it you basically cannot flash any current ROM because they all require some kind of update (which itself requires s-off).
PS. You're not quite in the right place, in future please post questions in the Q&A section. I'll ask for this thread to be moved there.
Sent from my Evita

timmaaa said:
PS. You're not quite in the right place, in future please post questions in the Q&A section. I'll ask for this thread to be moved there.
Sent from my Evita
Click to expand...
Click to collapse
Done and title changed:good:

Thanks. Trying to find noob-proof instructions to accomplish all you mentioned. But I do appreciate being pointed in the right direction. Its good to know definitively what I need to do, now just gotta get down the how lol...
Sent from my One X using xda app-developers app

Ok, I'll make it a bit easier on you. The easiest way for you to get it done will be to follow these steps:
Flash a Sense 4 Android 4.1 ROM with root. It cannot be Sense 5 Android 4.2 though. You'll find plenty in our development section.
Determine whether you have SuperCID or not. Boot into bootloader and connect to your PC then issue this fastboot command:
Code:
fastboot oem readcid
If it shows up as 11111111 or 22222222 you have SuperCID and can continue to the s-off step. If it shows up as anything else you don't have SuperCID, in that case you van use this method to obtain SuperCID:
http://forum.xda-developers.com/showthread.php?t=2212737
Once you have SuperCID you can get s-off by following this guide:
http://forum.xda-developers.com/showthread.php?t=2155071
So now you should have s-off, which means you can run the 3.18 RUU. You'll find it here:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
All you need to do is connect your phone to your PC, run the RUU exe program and follow a few prompts. Make sure no other programs are running and make sure screen saver/hibernation is turned off. Also make sure HTC Sync is uninstalled (leave divers installed) because it gets in the way.
When the RUU is complete you will have a stock ROM and stock recovery on your phone (your bootloader will remain unlocked and you'll still have s-off though) so you'll need to flash TWRP recovery again. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can flash any aosp ROM you want.
Sent from my Evita

Thanks...
Thanks for all the help. I was SuperCID, I achieved S-Off, i think. It says s-off on bootloader, but when I was entering the final 3 commands, the second one said error, I resubmitted it, and it went thru. Now it says S-Off. So is everything cool there?
I am a little concerned as to how terrible sounding running the RUU 3.18 can be. Am I cool to go now with no problems forseen?
Thanks for your responses btw. Very Helpful
Also, do I connect to PC in bootloader, or up and running rom, while running RUU?

If you are s-off running the ruu is entirely safe
Sent from my VENOMized HoxL

Everything went smooth today. I am running s-off, and hboot 2.14. Instructions worked perfectly. Thanks to everyone that helped me.
Sent from my One X using xda app-developers app

:thumbup:
Sent from my Evita

[Q] My HTC One X AT&T has signal issues and random reboots

Hi everybody i flash my htc one x at&t with android 4.2.2 (sense5), i used urdroid version --------->(http://forum.xda-developers.com/showthread.php?t=2331373) and now my phone lost the signal and random reboots, i heard that the problem is the kernel but i don't know what kernel i should install. hope you can help me.
Thanks.
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

Please search properly before posting next time, the answer has been discussed dozens of times in every single Sense 5 ROM thread.
1. Search before posting.
Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news.
Click to expand...
Click to collapse
You can flash the Beastmode kernel to fix the problem but the real solution is to flash the 2.15 firmware package. You'll find it (along with detailed instructions) in Turge's stock Sense 5 ROM thread in our Android Development section.
Sent from my Evita

Thanks for the answer
Could you send me the link please
Sent from my HTC One XL using xda app-developers app

I told you exactly where to find it, I'm not going to go and find it for you, that's something you can do for yourself. In the time it took you to write that post your could have already found it and downloaded it.
Sent from my Evita

Thanks dude, i downloaded the beastmode kernel and flash it but now when my phone is starting stuck on at&t logo and then reboot. Do you know why my phone do that?
I'm not super cid and i'm S-ON
Thanks for your answers.

There are a certain group of phones that have a slow SoC, basically they can't handle the Beastmode kernel. You'll need to get s-off and flash the firmware instead. If you need links just look in the Everything Evita thread in my signature. You should bookmark that thread, it contains links to pretty much everything you'll ever need.
Sent from my Evita

Thanks, i'm thinking return to stock rom. Do i have relock my bootloader right? And then run RUU or what do you recomend me to do?

Whatever you do don't run any RUU yet. If you want to return to stock you need to get s-off first. I know you think you don't have SuperCID but if your phone is an at&t model then there's no way you could have unlocked your bootloader without SuperCID. Basically, s-on + SuperCID + jb RUU = brick. So lets check your CID. I'm assuming you have adb/fastboot installed on your PC? If not you need to do that first. Once you have it installed you can connect your phone in fastboot mode (reboot to bootloader and connect), then you need to open a command prompt from within your fastboot folder on your PC (open folder where fastboot.exe is located, shift + right click, select open command prompt here), then issue this command:
Code:
fastboot oem readcid
Tell me what it says.
Sent from my Evita

I was reading about s-off and super cid but I'm new doing this and sounds a little hard to do so don't you think it's better if I install a stock backup
That will solve my problem?

You were right I'm super-cid my cid is: 11111111

S-off is very easy if you already have SuperCID. The biggest obstacle is installing adb/fastboot, if you haven't already. Otherwise, don't worry about being new. We all were at one time. Just read up and understand the process, and follow the instructions carefully, and you will be fine.
---------- Post added at 12:52 PM ---------- Previous post was at 12:50 PM ----------
arthur2820 said:
don't you think it's better if I install a stock backup
Click to expand...
Click to collapse
I don't see how that is in any way "better". If you s-off, all you then need to do is install the 2.15 firmware package, and the signal drop and random reboot issues will disappear.
If you went through the trouble to be able to flash custom ROMs, let's keep it that way.

arthur2820 said:
I was reading about s-off and super cid but I'm new doing this and sounds a little hard to do so don't you think it's better if I install a stock backup
That will solve my problem?
Click to expand...
Click to collapse
arthur2820 said:
You were right I'm super-cid my cid is: 11111111
Click to expand...
Click to collapse
I thought so. Getting s-off is pretty easy, all you need to do is follow some instructions and enter some fastboot and adb commands. Basically, if you can read and type you can do it. As Redpoint said you do need adb/fastboot installed, if you don't already have those you can Google search 'minimal adb and fastboot' and the first result should be a thread that explains how to install it very easily.
We all started somewhere, it might seem a bit daunting at first but I guarantee you it isn't as hard as it seems. Once you get learning it becomes really easy to understand. If you have any questions and can't find answers after some thorough searching just ask, you've got some good people here to assist you.
Sent from my Evita

Thanks I'll try it, could you send me the link of adb/fastboot installer? I guess that the only thing I have to do to install 2.15 formaware it's get s-off
Sent from my HTC One XL using xda app-developers app

See my post right above yours, I've told you what to search for.
Sent from my Evita

i found this thread http://forum.xda-developers.com/showthread.php?t=2155071 i've downloaded the zips bit in the step number 1 i don't know whats means "working directory" the thread it's the correct to get s-off?
how can i flush the image? (step 5)

That's one of the two s-off methods, yes. Your working directory is the folder on your PC where you have adb.exe and fastboot.exe located. You have those installed now right? In order to open the command prompt from that location just shift + right click anywhere in the folder then select open command prompt here.
Sent from my Evita

yes i've installed minimal adb and fastboot. the other method it's easier?

The method you're already using is fine, I used that method and it took me about ten minutes.
Sent from my Evita

ok. mmm but what means flush image again immediately?
Do i have to put the 2 zips in the working directory?

Did you read the instructions? It details exactly what you need to do, follow those directions to the letter. It tells you which zip needs to stay in zip format and which zip needs to be extracted. It tells you what commands to type when the command prompt returns text.
Sent from my Evita