Database Info

Custom Rom nightmare

Hello Everyone, I am hoping someone can tell me what to do to fix this, I have been searchng and reading and trying things I have found online all day, but without luck. I dont think Im savvy enough to know what is actually wrong.
My Phone :
Australian Telstra HTC Sensation running ICS (OTA update)
here is my problem :
Wifi will not turn on, comes up status of error.
I flashed CWM + supersu v0.89 onto my phone to give myself root access so that I can use the gesture control application and also to get access to the \data\data\ folder for the Dead Trigger hack. this worked without issue.
I noticed that I was having major issues with multi-touch after putting ICS on my phone. I read that this is a known issue with ICS on sensations, and that a custom rom would be my best bet to fix.
I had read alot about cyanegen (or however you spell it) mods on androidpolice, so i decided to give that one a go.
Being a noob, I didnt know my sensation cannot be S-off'd (due to Hboot 1.27) and when I flashed the rom onto my phone, it would not boot passed the boot animation. (I followed the instructions on their site and did a backup with CWM as well as wiping the phone).
Looking into the no-booting issue, I found out that my phone is not S-off'd and is the reason the flash did not work, something about not being able to replace the boot.img and custom kernel.
So I found a stock kernel rom (ARHD 6.6.7) and flashed that onto my phone. this one boots, but the wifi will not turn on.
I decided stuff it, and used CWM to restore my backup, now my phone is back to how it was before I started all this flashing, accept that the WIFI will not turn on at all!
please can someone help me? I have no idea how to fix this, I thought using the recover option in CWM would put my phone back to how it was at the beginning, and with the exception of the wifi issue it did. all my apps and customizations came back.
How can fix my WIFI issue?

I have a Telstra Sensation too & i've never had any wifi problems with custom ROMs.
Did you superwipe between flashing ROMs? & Did you flash a different kernel?

Hi, I tried running superwipe which is on the ARHD 6.6.7 thread, however it got a "status 1" error message, so I used the wipe data and cache options available in CWM (which was the steps listed in the cyanagen mod install)
I also tried flashing SebastianFM's custom kernel, but that gave a "status 7" error message. Is this what buggerd my phone?
Thankyou for the fast reply!

the sole reason for everything is recovery
(ARHD says 4EXT custom recovery is mandatory ..yet you are still using CWM)
now first change the recovery to 4EXT
how and all the bleow guide explains (when you are not SOFF ..but SON and have htc-dev unlocked bootloader ..you have to flash roms ..little bit differentely ..traditional way wont work)
FLASHING ROMS WITH SON
FOLLOW the guide to the letter

i got wifi issues when using faux kernel.. no problem with sebastian's

Thankyou so much for that. That solved my issues completely, I was able to flash Cyanogen onto my phone and it boots, wifi works too!
Can you tell me, can I use 4EXT to flash Sebastians custom kernel even though I am S-ON?

templargfx said:
Thankyou so much for that. That solved my issues completely, I was able to flash Cyanogen onto my phone and it boots, wifi works too!
Can you tell me, can I use 4EXT to flash Sebastians custom kernel even though I am S-ON?
Click to expand...
Click to collapse
First do the step 5 in the guide that I've mentioned (permanent enabling of smartflash)
Then forget about smart flash and flash any kernel
Alternatively if you didn't make smart flash permanent yet (which I highly recommend you to do)
You can enable smart flash just before flashing kernel and can flash any kernel
Sent from my pyramid.. Through blazing fast sonic waves

NS 9020t - problem flashing marmite_v4.4 kernel to miui 2.9.7

I'm having a problem flashing marmite 4.4 to the newest miui build (2.9.7).
Basically in cwm recovery and flashed the kernel.
Will say "ununderstandable message 3" and "lid is licked"
Reboot the device and it will get stuck on the miui boot screen.
Tried installing both the "stock OTA" and "All other ROM" version of marmite.
Same message comes up.
Already tried performing a full wipe (actual full restore, format system, format boot), reload the ROM.
Tried wipe cache and dalvic (even though it is not needed)
Just wondering if there is something incompatible or not.
I was able to flash air kernel without issues.
I haven't tried an older version of marmite yet, but will try later.
I'm not blaming marmite, it could be miui as well, or it could be just me.
I'm certain I'm flashing correctly.
I read bedalus' marmite post and saw 2 others with this issue (not same version of kernel or ROM).
The suggestion was that they didn't use the correct kernel for ROM.
I would assume miui would not be categorized as "stock OTA", so I tried "all other ROM" version first"
Am I doing something wrong?

There is a new version 4.5 the message you get I believe is like a joke. It does show however that the installation was successful.
Never experienced boot loops flashing his kernels.
Sent from my Nexus S

Actually, I downloaded that one just now to try and same issue.
It will just stall at the miui (ROM) boot screen.
I am trying some other stuff right now as well.
Really want to use this kernel. :good:
I'll report back later.
Thanks for the help.

Good luck. His kernel offers great speed and stability!
Sent from my Nexus S

For marmite 4.5, did a full wipe again, even formatted the SD partition.
So flashed miui 2.9.7.
Booted to the ROM.
Made sure things seem normal in the ROM.
Restarted just to be sure.
Boot back to recovery.
Flashed marmite 4.5
And it is stuck on the miui loading screen again.
Only thing I haven't tried this time is to fix permissions. (didn't wipe cache or dalvic either)
I'll try it again. :laugh:

Since I formatted the SD partition, it should rule out that it was something on the SD card right?
It's time consuming to copy things back to the NS.
I'll try an older version of marmite afterwards and then an older version of miui.
It should tell me what is causing the lock up by then. I think. :silly:
.... yes I have a lot of time ....

I forgot to mention one thing.
I'm flashing the official Chinese version of miui 2.9.7.
Wonder if that's the cause.
I guess I will download the US or UK version to try as well.

Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S

kwibis said:
Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S
Click to expand...
Click to collapse
Took some time to test, but sort of found my answer.
It's the official Chinese miui that's causing the issue.
Well at least some component in the ROM.
I tested with the MIUI UK (miuiandroid) version 2.9.7 and it installed like a charm.
Before flashing the UK version, I tested with earlier versions of marmite (4.3 and 3.5) on the Chinese 2.9.7.
All failed at the ROM boot screen.
I should check with the miuiandroid team and see what they changed that made it different.
When I was testing I did a full wipe, installed ROM, booted ROM, boot to recovery and flashed the kernel.
I didn't even wipe cache or dalvic (which is not needed anyways).
I had to do a full wipe because the ROM just wouldn't boot back up afterwards.
I'm tempted to test with an earlier version of the official Chinese miui and see if it makes any difference.
... too much time and/or no life ... :laugh:

Lol, well it's good you found your answer So its not a waste lf time as you learn from this
Sent from my Nexus S

If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2

Articudos said:
If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Not sure what the boot.img type is, but I'll look it up. Thanks.
I posted on miuiandroid forums and someone replied saying that the Chinese version is odexed and not busyboxed.
UK and US version is definitely deodexed, I downloaded them and checked. I haven't found out how to check busybox.
I have a few choices.
1. I can use the UK or US version, since I was able to flash marmite on them... easy way out.
2. Find out how to deodex the ROM and, I guess, how to add busybox (?)... I get to learn more stuff.
3. Use a way faster ROM (eg. Paranoid Android - great ROM by the way!) and flash marmite on it as well... but really want to use miui again.
Thanks guys for your help though. Really appreciate the information. :good:

Glad you found a solution

[Q] Phone screen unresponsive after flashing cm10

Hi guys. I have just recently bought this phone. This is my first HTC phone, ive always used samsung phones and wanted to try out the HTC. I managed to unlock the bootloader, root the phone and install twrp. My phone was bone stock so I downloaded the latest nightly for CM10 and gapps. Now for samsungs i didnt have to extract the boot.img and flash that via fastboot. so thinking the flashing process would be the same i flashed cm10, gapps and rebooted. And like clockwork the phone went into a boot loop. I found this little blurb in this thread http://forum.xda-developers.com/showthread.php?t=1957193
"5) Once your phone is in bootloader mode, type the following command fastboot flash boot boot.img ( If command prompt is closed then open command prompt in the folder where boot.img, adb, fastboot are present . For example: C:\android-sdk\platform-tools - Same folder used in step 3)
5) Then run the following command adb reboot recovery
6) Your phone is in TWRP recovery
7) Select mount from recovery ( See mount - image in the attachments for example)
8) Copy the ROM.zip which you downloaded earlier to the SD card ( For example cm-10-20121012-NIGHTLY-evita.zip) ( Not the extracted folder but the actual zip file which you downloaded)
4) Copy the gapps into sd card ( you need to download gapps if you using CM10 or ASOP roms )
5) Unmount, then select Wipe and select Factory reset ( it is recommended to do a factory reset before flashing the new ROM. ) (See wipe, wipe1 images below )
6) Select Install in recovery and flash the ROM.zip
7) You need flash gapps if you flashing CM10 or ASOP ROMS
so i re did the process. flashed boot img through fastboot, rebooted to recovery, flashed the rom that was already on the sd card, flashed the gapps package and rebooted phone. and i did do a factory reset when installing the rom. the phone rebooted, but this is where im stuck. the phone boots to the setup screen where you basically select the language. SCREEN is unresponsive, its not letting me click on start, its not registering my touch anywhere on the screen. I was thinking maybe it was the kernel so i made sure i was using the right kernel. i tried the whole process a few times but it didnt work. same problem. fone boots but doesnt register the touch. i even tried booting with flashing the gapps. so basically im stuck at the first screen. i had done a nandroid back up before and tried flashing that but that doesnt work either i guess because of the same reason.
Any help would be appreciated?
Thank you so much in advance

what hboot version do you have? There is an issue with the 2.14 hboot as HTC modified the firmware so the touchscreen drivers don't work for the older ICS or AOSP roms. If you have the 2.14 hboot, you'll need a JB sense ROM (like jokers or viperXL 3.1, or maybe Newts), check the forums themselves to see if they are compatible with the 2.14 hboot if you have it.\
If you don't have the newest hboot, maybe check the md5sum of the one you downloaded in case it is corrupted? If not try reflashing it, or flashing a different ROM and report back with results.
Good luck.

codeprimate said:
There is an issue with the 2.14 hboot
Click to expand...
Click to collapse
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.

twistedddx said:
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.
Click to expand...
Click to collapse
So in your opinion what is the solution i can try? Im not able to boot my phone so i cant really transfer any ROM zips to my phone. I have to use the bootloader or recovery to somehow get my phone back into workin order and then go from there. Thank you for your response

codeprimate said:
what hboot version do you have? There is an issue with the 2.14 hboot as HTC modified the firmware so the touchscreen drivers don't work for the older ICS or AOSP roms. If you have the 2.14 hboot, you'll need a JB sense ROM (like jokers or viperXL 3.1, or maybe Newts), check the forums themselves to see if they are compatible with the 2.14 hboot if you have it.\
If you don't have the newest hboot, maybe check the md5sum of the one you downloaded in case it is corrupted? If not try reflashing it, or flashing a different ROM and report back with results.
Good luck.
Click to expand...
Click to collapse
So i checked in the bootloader screen and i do have 2.14 hboot. so as the other person said i can downgrade my hboot using JET? and If im not mistaken you said that 2.14 may not be the latest hboot. If not where can i get the latest hboot. The other thing was since im not able to transfer any files to the phone.

Like twisted said you're going to have to flash a sense jb Rom right now go try viper.... Until the others update touch drivers to accommodate you people you have to use jb sense

marijuana king said:
Like twisted said you're going to have to flash a sense jb Rom right now go try viper.... Until the others update touch drivers to accommodate you people you have to use jb sense
Click to expand...
Click to collapse
ok so i downloaded jokers rom, and i was reading this link http://forum.xda-developers.com/showpost.php?p=32794132&postcount=7 to put the rom on my sd card. this link says they are using cwm recovery but i have read in many places that twrp should be used because it is officially supported for our devices. when i boot into recovery and try mount usb storage it doesnt show up on my computer as a flash drive. i have checked the drivers. im going to uninstall them and reinstall them, reboot my lappy and see if it recognizes the device. if you have any suggestions please throw them at me. at this time im looking for any straw that i can get to keep afloat.

anandsamuel said:
ok so i downloaded jokers rom, and i was reading this link http://forum.xda-developers.com/showpost.php?p=32794132&postcount=7 to put the rom on my sd card. this link says they are using cwm recovery but i have read in many places that twrp should be used because it is officially supported for our devices. when i boot into recovery and try mount usb storage it doesnt show up on my computer as a flash drive. i have checked the drivers. im going to uninstall them and reinstall them, reboot my lappy and see if it recognizes the device. if you have any suggestions please throw them at me. at this time im looking for any straw that i can get to keep afloat.
Click to expand...
Click to collapse
you should be able to flash that from TWRP instead of CWM without any dramas. if you can't see the device from your pc while it is booted into TWRP you can use "adb push C:\somepath\somefile /sdcard" to copy it onto your sdcard (you'll need the right version of the drivers and adb in your path). If you can't find the drivers or figure out anything let us know.
twistedddx said:
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.
Click to expand...
Click to collapse
You are right, it isn't the bootloader, it was the firmware upgrade pushed out alongside it, but it is a lot easier to check your hboot version from the bootloader than it is to check what software/firmware version you have, as the OP didn't list his software version, and had since blown it away with a new ROM, it seemed easier to check the firmware compatibility via the hboot version. I know strictly speaking the hboot isn't responsible for the touchscreen drivers, but they got the point quite quickly.

Update: so I was able to get my phone working I had to reinstall drivers on my computer restart the computer and then I was able to actually view my phone on my computer through TWRP and I transferred the ROM on to my phone and rebooted back into the bootloader flashed via boot image then went back to recovery and flash the ROM and everything is good to go now thank you all for your help this is an amazing phone
Sent from my HTC One XL using xda app-developers app

twistedddx said:
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.
Click to expand...
Click to collapse
Because it's the easiest way to identify that they are running the new firmware?

Yes. HTC went off and made some firmware updates to the touchscreen firmware.
We can't do anything about it until kernel source for the jellybean update is released.
Basically, if you took the new hboot EVER(since it updates the touchscreen firmware), that means you cant use AOSP Roms until we get source and can fix it in CM.
Aokp, pa, jellybam, kingkang, etc. All of those Roms use our kernel and device trees as a base. Once we get source and fix, they will update and everyone will be back in business.
The guys at TWRP were able to make recovery work because they just used the prebuilt stock kernel. On AOSP...we need source.
Sorry guys. Pester and scream at HTC to release JB source and that is the only way to help with this. Sorry to all of those that are affected....just know we are waiting impatiently as you are.
Sent from my Nexus 4 using xda app-developers app

h8rift said:
Yes. HTC went off and made some firmware updates to the touchscreen firmware.
We can't do anything about it until kernel source for the jellybean update is released.
Basically, if you took the new hboot EVER(since it updates the touchscreen firmware), that means you cant use AOSP Roms until we get source and can fix it in CM.
Aokp, pa, jellybam, kingkang, etc. All of those Roms use our kernel and device trees as a base. Once we get source and fix, they will update and everyone will be back in business.
The guys at TWRP were able to make recovery work because they just used the prebuilt stock kernel. On AOSP...we need source.
Sorry guys. Pester and scream at HTC to release JB source and that is the only way to help with this. Sorry to all of those that are affected....just know we are waiting impatiently as you are.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
lol, I've tried arguing with HTC's "support" for the source code, they are either extremely thick or deliberately obtuse. They kept telling me how to check if my carrier has released jellybean. I kept telling them that they are required under the GPL to release the source for the kernel along with any binaries.
I think the only way they'll release them in a timely fashion is if we get organised in a class action suit for violation of the GPL. It is for HTC's point blank refusal to meet it's legal requirement in a timely fashion that I refuse to ever buy another HTC device. I'll use this one for the term of my contract and then jump ship to a manufacturer that doesn't treat the open source community with contempt.

I don't mean to hijack this thread, but I'm facing a related issue.
I had rooted and unlocked my bootloader, hadn't yet installed any custom ROM. So today, without thinking, I install the OTA 4.1.1 update. Now of course I lost root, but even worse, when I boot in TWRP, my touchscreen is also unresponsive. I have the hboot 2.14.
I tried flashing TWRP again, but the same deal happens: the touchscreen won't register anything.
When you said that TWRP were able to make the recovery work, was this after the recent firmware update? Do I need a more recent version of TWRP (I'm using 2.3.3.1)?
I asked about this in the TWRP thread, but this seems closely related so I posted again here.
Edit- All is well, goo manager was installing 2.3.3.0 for some reason.

[Q] PAC-man ROM not booting anymore

hi,
so as i can not post in the android development subforum i'll have to try it here..
I have: HOS with TWRP 2.4.4.0 (goo manager) with HBOOT 2.15 (S-ON) running PAC-man ROM 22.1 (the newest update)
also i have bubba v4 installed and everything was working really perfectly. (s2w and some kernel tuner settings)
yesterday i played a bit with UI settings, nothing that i thought would stop my device from booting..
today i woke up, the battery was empty so i plugged in, turned on and left, after a while i came back and it was still at the boot
animation (PAC is loading...).
now i have tried to reflash bubba, PAC (cache+dalvik wipe) and the boot.img via fastboot. still it is stuck on that loading screen.
now i'd really like to use this rom with the bubba kernel.
any clues how i could get it out of this boot cycle?
thanks
-t.

2.4.4.0 is kinda crap in certain things. Flashing roms is one of them. Please use 2.3.3.0 as this will work.

why do you think that twrp version is the problem?
flashing this rom with 2.4.4 has worked well, so flashing over the same ROM with it shouldn't be problem...?
when flashing or wiping everything seems to work normally.
also, i am not sure how to downgrade twrp!?
best,
-t.
edit: okay i found out, fastboot flash recovery .. should work. i'll let you know if it works afterwards *fingers crossed*
edit2: reflashing the ROM it takes much longer (maybe thats good?) i just hope it finishes at some point...
edit3: okay, so re-flashing with twrp 2.3.3.0 did'nt work either, it is still stuck at the "PAC loading..." stage
(yes, i flashed the boot.img too)
any more clues?
finally i had this phone set up just the way i wanted, it was perfect and then this. why couldn't it just keep working
makes me sad, i want to use my phone damnit

okay, so i flashed and wiped and flashed and wiped a few times, system, cache, dalvik whatever, suddenly it started working... i also flashed some different kernels (as i thought some bubba stuff might still be there)
soo IDK what it was but now it works again, thank god..
maybe its worth mentioning that i flashed an older PAC rom (v22.0.1_20130324-230044) though i am not sure if that was the problem...

Sorry, I was off for some time from this forum.
If your bootloader version is > 1.09 you'll have to flash the kernel separately due to some restrictions in the higher bootloader versions.
If e.g. you flashed boot.img only from the 'bubba.zip' you're missing some of the modules needed for working coming with that flashable zip. Just have a look inside the zip file and you'll see some different content besides the boot.img. So you need to flash the complete zip file (to get the modules) and separately again the boot.img (to get the kernel itself).
The point about 2.4.4.0 / 2.5.0.0 is, that some installer scripts for some roms don't work as they should.
:good:

Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Well nevermind I guess I learned something from this little action that cost me most of my precious Saturday...
Also I now tried flashing twisted 3 and bulletproof kernel neither of them worked for pac rom, maybe someone could explain to me which kernel works for which rom? I thought they are completely interchangeable as long as they are compatible to the hardware..
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Well, appreciate the help.
Best,
#t.
Sent from my One S using xda app-developers app harhar

Bulletproof is for sense
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2

Aha okay, I thought sense is like any app running ontop of any kernel...alright.
Sent from my One S using xda app-developers app

tehtomi said:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Click to expand...
Click to collapse
Usually the installer script should set the right permissions already. Nah, modules shouldn't go lost this way ( system/lib/modules/*.ko).
tehtomi said:
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Click to expand...
Click to collapse
In short: boot.img = kernel
It's stored in an own partition (block) on the phone, That's why you have to use 'fastboot flash boot boot.img'. Same for radio: 'fastboot flash radio radio.img' and so on. The bootloader will load them first from this block. But search Google if you'd like to know more. lol
Usually there is a boot.img file in any rom.zip that can be extracted and flashed also it's supposed to be flashed with the rest of rom.zip in one go. Blame htc for their bootloaders which prevent you from this. That's why we talk about htc's half assed bootloader unlock.
To come to an end: There are sense based roms, AOSP and AOKP based roms. Whereas AOSP and AOKP based kernels could be interchangeable, sense based kernels are only compatible to htcs sense UI. That's why you can't mix them up with all the roms out there. Sense is deeply integrated into kernel.

[Q] Custom Roms not working

Hello, long time reader, first time poster. I know about rooting, and installing roms and all that good stuff (had a galaxy s2 but odin bricked it). So I'm new to the sensation, and it's quite different from my previous device. My problem is that when I install a custom rom, the phone will boot and all about after about 30 seconds will freeze and restart.
Okay so these are the steps that I followed:
-Used the KGS Utility and chose "s-off"
-Followed all the prompts everything worked out fine.
-Following that I used it to install a custom recovery.
-Followed the prompts everything worked fine.
-Then I used Revolutionary CWM to flash SuperUser.
-App was there on reboot.
-Then I downloaded the AOKP "Initiate Your Swagger"[4.1.2] Rom
-Put it on my SD card and flashed it (after wiping and backing up)
-When the phone boots the setup wizard starts.
-I follow the prompt and when it gets to "Just a sec" the phone freezes then restarts.
Don't know what the problem is here.
I get the same problem when trying to flash CM10. The phone will boot, but then after 20-30 seconds will reboot.

kojimin said:
Hello, long time reader, first time poster. I know about rooting, and installing roms and all that good stuff (had a galaxy s2 but odin bricked it). So I'm new to the sensation, and it's quite different from my previous device. My problem is that when I install a custom rom, the phone will boot and all about after about 30 seconds will freeze and restart. I also noticed that there is no signal in custom roms either. Don't know what I'm doing wrong here. I used an all in one tool to do s-off, and install a custom recovery. Then I rooted it. Then I started trying to install custom roms but they don't seem to work. What am I doing wrong?
Click to expand...
Click to collapse
Be VERY specific and give a step by step detail of what you are doing to install. Give WAY more detail than you have. And put the detail in a list, not a giant paragraph.
Then we'll look at it and see what's missing.

Skipjacks said:
Be VERY specific and give a step by step detail of what you are doing to install. Give WAY more detail than you have. And put the detail in a list, not a giant paragraph.
Then we'll look at it and see what's missing.
Click to expand...
Click to collapse
Sorry about that. Edited my first post. I hope that is enough.

When you say it boots for 20 seconds, what exaclty for you mean.
Does it just replay the boot animation over and over? Or does it actually bring you to a home screen with the status bar and everything for 20 seconds before the reboot? That's a very important difference in diagnosing this one.
Also try installing 4EXT recovery. CWM has been known to cause weirdness with AOSP roms. Plus you may have an older version of CWM thatcan't properly install the newer roms. If you used a .zip in bootloader to flash CWM yuou probably had an older version. I have a special place in my heart for CWM too, but 4EXT is just so much better for the Sensation. (Different recoveries ar ebetter or worse on different devices.)
If you properly installed superuser on your stock rom that you have a nandroid backup for, installing 4EXT is super easy. Just restore the nandroid, which should boot up without problems, download the 4EXT app from the play store, and use the app to install teh latest version of the recovery. No need for ADB or flashing in bootloader. Then try a full wipe and fresh install of AOKP from 4EXT.

Skipjacks said:
When you say it boots for 20 seconds, what exaclty for you mean.
Does it just replay the boot animation over and over? Or does it actually bring you to a home screen with the status bar and everything for 20 seconds before the reboot? That's a very important difference in diagnosing this one.
Also try installing 4EXT recovery. CWM has been known to cause weirdness with AOSP roms. Plus you may have an older version of CWM thatcan't properly install the newer roms. If you used a .zip in bootloader to flash CWM yuou probably had an older version. I have a special place in my heart for CWM too, but 4EXT is just so much better for the Sensation. (Different recoveries ar ebetter or worse on different devices.)
If you properly installed superuser on your stock rom that you have a nandroid backup for, installing 4EXT is super easy. Just restore the nandroid, which should boot up without problems, download the 4EXT app from the play store, and use the app to install teh latest version of the recovery. No need for ADB or flashing in bootloader. Then try a full wipe and fresh install of AOKP from 4EXT.
Click to expand...
Click to collapse
It boots up to the homescreen (with no signal) then it reboots.
I will try 4EXT and post my results. Thanks for your help thus far!
EDIT: Tryed installing 4EXT now when I try to boot into recovery it shows the HTC spash screen, then it reboots back the homescreen. So I think my recovery is gone.
EDIT 2: So I got the 4EXT recovery installed. But the ROMs are giving me the same issues (no change). I also noticed as before, when the custom roms boot there isn't any cellular signal.

kojimin said:
It boots up to the homescreen (with no signal) then it reboots.
I will try 4EXT and post my results. Thanks for your help thus far!
EDIT: Tryed installing 4EXT now when I try to boot into recovery it shows the HTC spash screen, then it reboots back the homescreen. So I think my recovery is gone.
EDIT 2: So I got the 4EXT recovery installed. But the ROMs are giving me the same issues (no change). I also noticed as before, when the custom roms boot there isn't any cellular signal.
Click to expand...
Click to collapse
Update the firmware.. You are on gingerbread firmware (revolutionary soff worked for you means you are on GB) and it won't work on ics/jb roms
Check the firmware thread by kohr-ah in sensation development section and flash universal 3.33 firmware
It will solve your rom problems
Sent from my HTC Sensation 4G using xda premium

ganeshp said:
Update the firmware.. You are on gingerbread firmware (revolutionary soff worked for you means you are on GB) and it won't work on ics/jb roms
Check the firmware thread by kohr-ah in sensation development section and flash universal 3.33 firmware
It will solve your rom problems
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
it was the firmware! I just updated to 3.33, and 4.1.2 "Initiate your swagger" booted up completely. Thanks for your help :good:

Awesome reply mate :
Sent from my HTC Sensation XE with Beats Audio using xda premium