Database Info

[Q] Help: ROM installation problem

Hello,
I have obtained S-OFF and root for my sensation. My first attempt at installing a new rom was successful, and I used Android Revolution 3.6.1. Success, and I was happy. Now I decided to change to 4.1.2 and it hangs on the boot screen after installing the rom.
Can someone please tell me why 3.6.1 works, and 4.1.2 doesn't? The procedure should be the same, correct?
Thanks in advance!

Did you use the Super Wipe zip?
Sent from my HTC Sensation 4G using XDA App

Yes, I used super wipe before installing each rom.

it might be your radio if you haven't updated it yet. thats the only other thing that could be missing. many people including myself have had successful flashes with 4.1.2 so thats not the problem. try updating your radio and super wipeing again.

Thanks for the suggestion. I updated my radio, but 4.1.2 still hangs on startup.

Did you forget something? Check Mike's tips and follow it. I flashed 4.1.2 four times today, it's ok.
Try another ClockworkMod Recovery. 4.0.1.4 from AlphaRev or 5.0.1.0 from ROM Manager is recommand in Mike's post. Mine is 5.0.2.0, just ok.

I followed the same procedure to flash 3.6.1 and when I flashed 4.1.2. For some reason, I can get only the first one to work, and not the other. I am certain both roms are working properly, but I was hoping to get some help as to why the one won't work on my phone.

Fixed: Let that be a lesson to you, remember to check your md5 checksum! Rom is now working perfectly.

I had faith in you the whole time been thinking about the possibilities all day

Thanks! Its all part of the learning experience I suppose.

Issues with kernel on 4.1.2, it has been superceded by 4.1.3, which is working fine and available now.
You did nothing wrong.
P.

having problem flashing deamonspeed
after i have succesfully flashed deamonspeed, my sensation bootloops at the htc screen..im using the cyanogenmod7 rom....could that be why its not working?

[Q] Phone shuts down.

My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody

What kernels have been used with the roms?
Sent from my HTC Sensation Z710e using XDA App

The used kernels were default kernels of the roms I used. Problem started wen using CM7 alpha. and now using Android Revolution with Faux123

Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Same for me, but ONLY with Revo HD ROM...

SadMac said:
Same for me, but ONLY with Revo HD ROM...
Click to expand...
Click to collapse
You don't have it in any other ROM?

I had the same problem before, I changed my kernel to bricked 0.91 and the problems are gone now.

I'm downloading Insertcoin rom now. I'll report back if the problem still occurs.

Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Change kernels. Go from 1.5ghz to 1.2 via daemon controller or another CPU adjuster.
The bricked 0.91 also fixes most issues too as stated above
Sent from my HTC Sensation in UR-Quan subspace.

Before you suspect Hardware.. Check first your software.. I'f i were you, i'll back up all my roms.. full / super wipe, then check it on by one.. lets say IC for first 2 days then ARHD on the 3nd-4th day.. If it does not shut down, it only means one thing, its not HARDWARE, it can be software.. Check also your chosen Kernel on your flashed ROM.. there might be an incompatibility running multiple different roms and kernels..
hope i'd help.. click thanks if i enlighten you so far..

Okay, I'm back from a weekend away.
What I did before I went away (Friday afternoon) is:
- Reboot to Recovery
- Wipe cache, wipe dalvik, wipe data
- install zip: Super-wipe (just to be sure)
- Install zip: InsertCoin 3.3.0
- install zip: InsertCoin 3.3.1
It all went well until Saturday evening. It was off when I got it out of my pocket. i tried to turn it on and it booted up. If it is on there is no problem at all. It stays on all the time...... Until I unlock my sim with my personal code. 2 seconds atfter that the phone turns off...
Since the problem reoccurred I tried the following things:
- Wipe cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, Super-Wipe, re-install rom, reboot (problem still exists)
Is there a way to test the hardware to rule it out? The problem occurred in three different roms and got worse. I really can't see how this could be a software problem.
I'm now going to download the latest stock rom and see what happens...

I had the same problem I'm on tmobile sensation 4g in the us and I think all us sensations have the problem... When I was using any rom that was based on the experimental sense 3.5 base my phone would turn off/crash I tried all different Roms but the problem still occured, I though about it and installed revolution hd with sense 3.0 and still on the old base and the problem is gone. I'm waiting for the official release of the new sense 3.5. Hope it helps

I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?

Frazzy said:
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Click to expand...
Click to collapse
I am having the same problems. I tried all of the same roms you have tried and as of last week I have decided to unroot my phone and return it to stock rom and recovery. after a week I am still getting the same random reboots. the only non stock part of my phone is that it is still S-Off, but I think im going to have to learn how to put stock S-On and go yell at the T-mobile guys to see if I can get a new phone.
If you can come up with anything better I would be willing to try it. the reboots are killing me.

This issue sucks. I'm glad I'm not the only one that has it though lol. I've also gone back to stock rom, no root/S-ON etc. Just to rule out the possibility that it's something funky going on with custom roms, kernels etc. So far I do still have random shutdowns, possibly a little less than I did before, but still there nonetheless. To get S-ON again, flash the RUU appropriate for your phone, then get into fastboot and type
fastboot oem writesecureflag 3
and then
fastboot reboot-bootloader
More on all this is here: http://forum.xda-developers.com/showthread.php?t=1201773
As far as logs to track down what is going on, I think it might be in lastkmsg. Unfortunately I don't know exactly where to find that or what to look for exactly.

And as stated twice before me, the problem still exists. I'm going to undo all changes to the Sensation and see what happens. If the problem is still there the phone will go back for warranty.
And again my old trustworthy HD2 saves the day as a backup...

I've never experience having a reboot with a super wipe then flashing a custom rom.. i do it almost everyday.. maybe its already a hardware since software installation (roms, and kernels) are clean when you do the flashing.. Has your phone experience some accidents? like fell on the ground?

Not that I know of.
I'm not new to flashing and I'm a real flashoholic. Nothing ever went wrong with flashing. Where other people would have problems with a certain ROM I could always enjoy the Rom without trouble.
I installed the eu version of the shipped roms. the problem seems to be different again. Nof it shuts down far less then before but I have to pull the battery to get it to boot up again.
I hope I have enough time today to S-on the phone. Does anybody know if the box states which version number it was shiped with? I know it's EU but there are different version numbers. (or is that not impotant)
Thanks for your help everybody.

I think the problem is the battery. I bought a new battery, the evo3d batery and so far I have not had this issue again.

Problem is solved. I got a free board swap and now everything is working again. So it was a hardware defect.
Thanks for the help all.

Revolution HD flash on two phones. Both phones are now slooooowwww...

A while back I rooted and flashed Revolution HD 3.6.4 on my Sensation without any issues; noticed immediate improvements, and was really pleased with the performance and battery life. Only issue was the occasional boot loop which I remedied by flashing a Bricked kernel.
Fast forward to two nights ago…
My parents also have Sensations and were not very happy with them so I convinced them let me root them which I did.
I did to their phones exactly what I did to mine, including; s-off, perma root, CWM, nandroid backup, flash ARHD 3.6.4 w/ bricked kernel.
The weird part is both of them are now having identical issues with their phones; really slow, 4hr battery life and laggy.
However…
I was sure to wipe the battery stats by draining the battery to complete shutoff, recharging to 100% (basically overnight 8hr+ charge) and erase battery stats from within CWM
I did not do a Titanium backup because a)they really didn’t have much installed, app-wise and b)I thought a fresh install would be cleaner without trying to recover any settings
I made sure to run the Revolution HD Super wipe before flashing the Rom
Installed the HTC Bricked kernel
The only thing different about their phones than my phone is they never applied the official HTC OTA major update. I went into this thinking it would not matter since we’re installing a new rom anyway but perhaps I’m wrong???
Why would two freshly-rooted phones exhibit the same issues?
I’m planning on re-flashing their phones later this week with the newer ARHD 3.6.5 rom (which I just did to mine ) hoping this will clear up any issues they’re having but want to make sure I’m not doing something wrong first…

Let me ask a more direct question.
Can I flash the new Revolution HD 3.6.5 (including the bundled faux kernel) to a phone that has not had the HTC Sense OTA update? Or will issues arise?

I think the problem is radio wise. Install the recommended radio and see if it solve the problem

OKors said:
Let me ask a more direct question.
Can I flash the new Revolution HD 3.6.5 (including the bundled faux kernel) to a phone that has not had the HTC Sense OTA update? Or will issues arise?
Click to expand...
Click to collapse
Hi,
The issue is most probably the kernel.
Try installing the latest.
You have two choices.
1.faux.(in my sig)
2.bricked.(HERE)
Seeing as you have two phones to play with,why not try one on each.

malybru said:
Hi,
The issue is most probably the kernel.
Try installing the latest.
You have two choices.
1.faux.(in my sig)
2.bricked.(HERE)
Seeing as you have two phones to play with,why not try one on each.
Click to expand...
Click to collapse
I flashed both their phones with the bricked kernel when I installed the rom originally.
If the problem isn't due to the older Sense version being installed what I plan on doing is flash both phones with ARHD 3.6.5 and leave the bundled kernel installed (have the 3.6.5 with new faux on my phone and so far so good).
I can try the radio flash also but I never had to flash the radio on my phone and all three phones are identical (bought them at the exact same time; family plan-thing).

OKors said:
I flashed both their phones with the bricked kernel when I installed the rom originally.
If the problem isn't due to the older Sense version being installed what I plan on doing is flash both phones with ARHD 3.6.5 and leave the bundled kernel installed (have the 3.6.5 with new faux on my phone and so far so good).
I can try the radio flash also but I never had to flash the radio on my phone and all three phones are identical (bought them at the exact same time; family plan-thing).
Click to expand...
Click to collapse
Hi,
I have never updated via OTA,and I never will.(Do not trust what it will do to my phone)
There are known issues with the bundled kernels.
Both of the latest kernels have had good reviews.
Just saying.

The OTA could've updated your radio.
Sent from my Sensation using XDA Premium App

Check if you have recommended radio or not. If not, flash recommended radio. Then,
Try to download ARHD 3.6.5 (check MD5), download latest kenels of your choice.
- Super wipe
- Flash Room, and reboot (just set up phone, dont set google account and facebook yet).
- If you want do flash roomcleaner: reboot into recovery and flash roomcleaner.
- If not, just reboot in recovery, wipe cache and wipe davik cache, then flash kenel of your choice.
- Reboot, set up your google account, facebook account, email account, etc...
- If phone experiences a bit lag during turning page to page in homescreen. Just reboot again. After that you can do all battery calibration, flashing mods or themes.
It may be too careful but that just to make sure I dont mess up everything with flashing.
Hope this help!

stevendph said:
Check if you have recommended radio or not. If not, flash recommended radio. Then,
Try to download ARHD 3.6.5 (check MD5), download latest kenels of your choice.
- Super wipe
- Flash Room, and reboot (just set up phone, dont set google account and facebook yet).
- If you want do flash roomcleaner: reboot into recovery and flash roomcleaner.
- If not, just reboot in recovery, wipe cache and wipe davik cache, then flash kenel of your choice.
- Reboot, set up your google account, facebook account, email account, etc...
- If phone experiences a bit lag during turning page to page in homescreen. Just reboot again. After that you can do all battery calibration, flashing mods or themes.
It may be too careful but that just to make sure I dont mess up everything with flashing.
Hope this help!
Click to expand...
Click to collapse
Hi,
ROM cleaner is flashed immediately after flashing the ROM, without any reboot.

Thanks for all the advice. I just got a call from my mom today saying her phone dies real fast and every time she takes a photo the screen goes black resulting in a battery-pull.
I gotta fix their ****z pronto.
I hyped the whole rooting thing up pretty good after flashing my phone, so far their experiences are pretty bad.
@ stevendph, I'll do exactly as you outlined. Thanks for the step by step.
fwiw the radio is whatever was on the phone from the time of purchase. Ill flash it as well with the 'recommend' radio.
So the consensus is to go back to the Bricked kernel and overwrite the new "updated" Faux kernel bundled in the ROM???

malybru said:
Hi,
ROM cleaner is flashed immediately after flashing the ROM, without any reboot.
Click to expand...
Click to collapse
Yep, it's can be flashed immediately or after 1st reboot, the result will be the same as roomcleaner's function is to delete system apps, files, skin and wallpaper (which are useless or you dont use). Those also can do it manually but yes painfull .
As i stated before, it's just i am doing carefully to watch if is there anything wrong with room flashing, then continue flash other things. What i did was flash, check, flash, check... until having what neccessary -->nandroid backup, flash, check, etc . Just me to be careful
@Okors: related to kenels, just make sure you notice this.
- Faux latest kenels 0.24r1 is really good and stable (if you have 0.24 beta 7, you dont need to update, as they are same).
- Bricked kenels: v1.5 final has the problem with camera, playback video (sometimes for some devices) as blackscreen, freezing. Version 1.4r1 is really good and stable (without Zram enable). Version 1.5 beta #490 with zram, working great for me anytime including camera, playback, etc... but there are reports from someone that they have lags (i dont)...
That's all what i know when testing and reading reports about these kenels, you have the right to choose what is suite for you.

I would just flash Pyramid 3D and 0.91 Bricked, check if GPS and camera work, then call it a day. If GPS doesn't work you could always try my fix or crypted's, boh are flashable.
Pyramid 3D has been the most stable and the fastest out of all the ROMs that I've tried without having to extensively customize for myself. Honestly though, I would just flash your parents stock again. Doesn't sound like they are power users.
Sent from my HTC Sensation

nrvnqsrxk said:
...Honestly though, I would just flash your parents stock again. Doesn't sound like they are power users.
Sent from my HTC Sensation
Click to expand...
Click to collapse
To be honest, I'm mostly after the improved battery life for them. You're right, they're not power users; in fact the phones are way to "smart" for them. Their biggest complaint is battery life (as was mine before I rooted).
At this point I just want to get their phones back to a stable state. It's frustrating because I NEVER had any of these issues when I flashed my phone.
Even the kernels, radios, etc didn't make 'much' of a difference. I was blessed with a really, really stable flash right out of the gate
I even updated to the latest ARHD and bundled faux kernel and my phone is rock solid.
Both of my parents are coming over tonight for dinner. I'm planning on reflashing them to ARHD 3.6.5. using the steps outlined earlier. Hopefully all goes well or it's restore-to-stock time.

OKors said:
To be honest, I'm mostly after the improved battery life for them. You're right, they're not power users; in fact the phones are way to "smart" for them. Their biggest complaint is battery life (as was mine before I rooted).
At this point I just want to get their phones back to a stable state. It's frustrating because I NEVER had any of these issues when I flashed my phone.
Even the kernels, radios, etc didn't make 'much' of a difference. I was blessed with a really, really stable flash right out of the gate
I even updated to the latest ARHD and bundled faux kernel and my phone is rock solid.
Both of my parents are coming over tonight for dinner. I'm planning on reflashing them to ARHD 3.6.5. using the steps outlined earlier. Hopefully all goes well or it's restore-to-stock time.
Click to expand...
Click to collapse
Hi,
May I suggest using the 3.6.x series with the 0.9.1 bricked kernel,found HERE
I put it on my son's Sensation,and he loves the stability and battery life.
He's not a power user.
He just wants a smartphone that works.
Just a thought.

You could also try the stock rom xe by eddyos. Everything works fine and battery last for 14 to 24 hrs in medium to light usage.
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App

Constant Random Reboots

Hello!
So there is this annoying thing that's been going on since I firstly rooted my phone and started flashing ROM's, radios etc.
I've been using only ARHD ROM's since they have a great reputation, haven't tried others.
So, I started with ARHD 3.6.x ROM's and now I'm on the latest 6.2.1. XE ( No OC ).
So the problem for me all through my experience with my phone, is getting random reboots at mostly no specific times.
The most common is in this situation:
The phone is just sitting nicely in my pocket, I feel that somebody is calling me. I take the phone out of the pocket, want to answer by unlcoking the phone and ding! it just crashes.
When I turn it on, the random reboots just won't stop until I give the phone a rest and don't use it for a while. Because after a random reboot the reboots just keep on coming, if I use the phone.
This also happens when I just take the phone out of my picket and try to unlock it.
So, mostly it reboots when I try to unlock it.
This just makes the phone unreliable and many times people can't call me because I have no idea that it has crashed in my pocket.
I've been hoping that it would stop with the next version of ARHD but it didn't. The problem keeps comming back.
So I wanted to know: Is there any way to see, what is the soul purpose of those crashes? Is there anyway it's curable? Because I don't know if it's the HW or the SW. When I had stock everything and no root, these problems were not present.
My setup:
* Super CID
* Firmware from 3.24.401.1 & 3.25.401.101 RUU
* Android Revolution HD 6.2.1 XE
* Radio: 11.68.3504.00U_11.21.3504.13_2
* Kernel ( from about info ): 3.0.16-g5e58c5e [email protected] #1
* Any other info you need to help me fully?

the kernel could be the problem...try not to use it and see if it happens again..however i suggest to you to flash the insertcoin rom cause it is the best ics rom out there...trust me try it and you will not be disappointed

I have the same problem with all ROMs, including stock, except for the Virtuous Quattro alphas which I was able to run 20 days straight without a crash (impossible with other ROMs). Also the battery readings after a crash is weird, dropping from eg. 60% before the crash, down to 5% when booting after a crash. I contacted HTC about this and they told me it's probably a faulty mainboard. So I'm planning on sending it back in a few months.

I have the same problem with all sense roms GB and ICS its really frustrating I've had it for some time already
Sent from my HTC Sensation XE with Beats Audio using xda premium

Today I will try virtuous_quattro_alpha3_pyramid. If it's too buggy, will try the Inqusition. And if I still have any problem, give the InsertCoin a try. Will post my findigs as I get them.
Any idea what kernel to use? Which is the most stable?

not sure but crashes may have something to do with your applications being in sdcard. i have moved all my applications to phone memory (though i don't have many) and i have not had a forced reboot after that. also super-smooth/ultra-smooth rosie helped, with this tweak my phone is really fast now.
using leedroid rom.

If the phone didn't reboot on stock then it's a firmware/software issue - go back to fully stock and see if the problem still occurs.
If not then start from scratch and make sure the checksums match the downloaded file before you install then, especially the firmware and radio file.
From my hd2 days you might first try setting your network manually, as I did hear that even native Android phones can reset during auto network selection.

So now I am on Virtuos Inqusition and the reboots still occur. It's frustrating.
And ONLY when I take my phone out of my pocket to see what time is it.
So I met a guy who is on all stock, without root etc. and he's getting the same issues.
Anyone else having this problem?
Could it really be the HW fault?
Or still could just be because an official ICS ROM for the Sensation hasn't come out yet?

Full wiped?
Did you full wiped it before you upgraded to the latest verison? In many cases reason for reboots are kernel and/or cache related. So maybe something which is still in your cache could bring that output. Another possibility is when you restore apps and settings from System Tuner or Titanium backup. As you are using stock kernel I don't think it should be the problem generator.
1. Do a nandroid backup
2. Full wipe with Mike's script
3. Fresh install ICS rom you like (I'm using Insertcoin 4.5.4 + Ultrasmooth Rosie)
4. Check MD5
5. install custom ROM
6. Don't restore settings/apps from Google.
7. Don't restore apps/settings from Titanium etc...
Just try to use your phone without all your apps installed for a short time.
Good Luck, hope it helps...

Yes, I always Super-Wipe before a fresh install.
But I will re do everything, installing only the timetable for buses - addicted to that app.
Can I restore contacts from google or should that wait for a while?

Update
So, it's been a while that I've been using Virtous Inqusition with Google sync and nothing else. The original problem still exists, Could this be a HW issue?
I don't really want to go all stock to loose SuperCID and everything else.
So, I guess I have to stick with this problem and leave my Sensation unreliable.

Tomekks said:
So, it's been a while that I've been using Virtous Inqusition with Google sync and nothing else. The original problem still exists, Could this be a HW issue?
I don't really want to go all stock to loose SuperCID and everything else.
So, I guess I have to stick with this problem and leave my Sensation unreliable.
Click to expand...
Click to collapse
Do a full wipe and reflash the ROM also wipe the battery stats and perhaps try a different kernel maybe one closer to stock frequency
Sent from my HTC sensation 4g using Tapatalk

[Q] Digitizer not working when installing ViperS rom

Hi guys,
First of all my apologies for posting this here, and not in the ViperS development topic. I have been reading a lot on the forums for over a year now, but only registered today, and therefore I am not able to post in that thread (10 post minimum rule). I have tried searching the topic and similar topics, but I have not found anything.
The issue is the following: when flashing the newest version (1.5.2) of ViperS, my digitizer does not work anymore. The LCD itself and hardware buttons work fine.
Some additional info:
* Device info:
- HTC Sensation XE
- coming from ViperS 1.3.5
- XxXPachaXxX 3.0.16 kernel (currently know as the PYD kernel)
- S-OFF
- HBOOT 1.27.1100
- 4ext v1.0.0.5 RC8
* what i've tried already:
- Flashing again, both with and without wiping dalvik/cache/factory reset
- Flashing another sense ROM, works fine
- 4ext touch recovery works fine
- MD5 check, correct every time
* I do get "Status 0/Installation aborted" errors every time I install a ROM (actually when aroma wants to reboot). This does not have an effect on the other ROMs i've flashed.
* It's worth noting that the digitizer has been replaced 2 weeks ago, but works perfectly on any other rom.
Thanks in advance guys!

Did you try 'factory reset' prior to the flash?
Edit: also recheck MD5 checksum of the downloaded rom.. weird sh*t happens when the download is corrupted.
Sent from my HTC Sensation Z710e using xda premium

Carrein said:
Hi guys,
First of all my apologies for posting this here, and not in the ViperS development topic. I have been reading a lot on the forums for over a year now, but only registered today, and therefore I am not able to post in that thread (10 post minimum rule). I have tried searching the topic and similar topics, but I have not found anything.
The issue is the following: when flashing the newest version (1.5.2) of ViperS, my digitizer does not work anymore. The LCD itself and hardware buttons work fine.
Click to expand...
Click to collapse
So Viper 1.3 works but 1.5 doesn't?
That is weird.
Try to download a fresh copy of the Viper ROM and start over. Even if you have matching MD5 sums on the copy you have, just delete it and start over. A fresh download can be a miricle cure sometimes.
Also, instead of flashing over your existing 1.3 version, try a full wipe and fresh install. See if that makes a difference.
If that doesn't work maybe it's some kind of strange kernel compatibility issue with the new digitizer. Maybe something from the kernel you are installing with Viper 1.5 isn't up to date for the latest replacement digitizer parts? (I'm admittedly reaching on this one...) I don't know if you are using the stock kernel that comes with Viper or immediately flashing a new kernel prior to boot.
Just as an experiment, try flashing another kernel that's compatible with Viper and see if it fixes your problem. If you're flashing a customer kernel right after installing the ROM, skip that part next time. If you're using the stock kernel, try a different one. Any different one.
If that doesn't help, post back here and at least we'll have ruled one thing out. And since that's easy enough to try it should be simple to test.

@Raven2k: my initial posts states that I have already tried both your suggestions, so no luck on that. Thanks for helping though.
Skipjacks said:
So Viper 1.3 works but 1.5 doesn't?
That is weird.
Try to download a fresh copy of the Viper ROM and start over. Even if you have matching MD5 sums on the copy you have, just delete it and start over. A fresh download can be a miricle cure sometimes.
Also, instead of flashing over your existing 1.3 version, try a full wipe and fresh install. See if that makes a difference.
Just as an experiment, try flashing another kernel that's compatible with Viper and see if it fixes your problem. If you're flashing a customer kernel right after installing the ROM, skip that part next time. If you're using the stock kernel, try a different one. Any different one.
If that doesn't help, post back here and at least we'll have ruled one thing out. And since that's easy enough to try it should be simple to test.
Click to expand...
Click to collapse
I have downloaded the ROM three times now, always with a correct MD5 sum (checked with 4ext). Also, my steps when flashing a new ROM are always the same:
1. backup
2. full wipe + wipe dalvik/cache (unless upgrading is specifically mentioned as an option).
3. install with full wipe (unless upgrading is specifically mentioned as an option)
Trying a different kernel is indeed a good idea, I'll try that tomorrow (it's 1:30am here). As far as I know, ViperS uses the bricked kernel, and the ROM i tried (elegancia) uses the stock one. I'll try several tomorrow, and give you an update .

I meant redownload and check MD5 again, sorry. Md5 errors are not probable, but they still do occur. Also, I would suggest reflashing 4ext recovery. It seems very weird to have errors for every rom being flashed.
Also, one more thing you can do is try booting vipers without your sdcard. The one thing not being formatted and cleared is the sdcard content which contains some app data etc.
Sent from my HTC Sensation Z710e using xda premium

My wife had viperS 1.4.1 on her sensation XE and a several days ago her screen stopped responding.
It was fine in recovery but when the ROM was booted up it just didn't work, so it was stuck at the lockscreen. I fully wiped everything and flashed the latest version of viperS and it still remained the same. Tried booting with the SIM card and SD card removed - still the same.
I fully wiped again and flashed a different ROM (Elegancia 3.7.0 - which I have had on my XE since it was released and I know to work well) and the screen worked fine, but she did have a few random reboots.
I then fully formatted her SD card using Gparted 2 days ago and (fingers crossed) it has been fine ever since.
I have no idea what the problem was, but I feel it was caused by the viperS ROM and that it affected the SD card too.
I'm not criticizing ViperS as I've used it before and know it's a great ROM, but I cannot be 100% sure that using it does not carry the risk of problems such as this.

Ok guys, sorry for my late reply. Due to the holidays and a trip to germany last week i did not have much time to do the flashing. Flashing an new kernel helped, I am now on ViperS 1.6 (which did not work out of the box, but after installing the bricked kernel it works .
Thanks to all for the help!