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] Rom Installation Problem

Hi,
I tried almost all the roms to see wich one fits me the most and when testing all the roms I came across a problem that I can't manage to solve myself.
Here is the problem:
I downloaded Elegancia rom (ICS) and it worked fine, installed fine, etc. But I saw that they had a rom Elegancia (gingerbread) so I thought what's the diffrence and wanted to put the gingerbread rom on my phone. But here starts my problem. After installing the rom like I always did and starting up my phone, it keeps booting (htc logo, elegancia logo, off, htc logo, elegancia,logo, off,...). So I tried many diffrent roms again to see where the problem lies and it seems that I can only use ICS based roms now. The gingerbread roms (wich I also tried before) doesn't work for me anymore and after installation of a gingerbread based rom it keeps starting up.
Can anyone tell me how to get the gingerbread rom back to work?
Greetings Crasherke

you had to install a other firmware, dont know the number but youll find it in the firmware thread use something under the newest it will help
edit: here it is download and install 1.17 and it will work
http://forum.xda-developers.com/showthread.php?t=1459767
EDIT2: And next time search! here are a lot of threads with the same problem! For example (Want back Gingerbread) it is too much work for you to search first than make a thread?

I found a firmware thread and read it. If I'm right, the I have the 3.24 version and I need the 3.12 version for gingerbread to work. It wasn't smart of me to assume that a higher version of firmware is compatible with all previous roms. Thanks for the quick reply and you point me right back into the right direction.
Greetings Crasherke

[q] bricked? Arhd bootloop

Hey guys, I been away from the sensation for a few months now and I think I bricked it on my first flash back! I was flashing ARHD & I followed the noob guide, I downloaded firmware & updated, deleted the firmware file, performed super wipe, flashed the rom, and I checked my md5 sums. Now I'm bootlooping the white HTC splash screen, and sometimes I see the beats audio symbol but right back to the slash screen! Ahhh.... I use this line for work. I used the 3.30 firmware as it said to & I'm on boot 1.27? I know one of you guys can help, so please ANYONE,I've got a get this fixed tonight.....

well if its booting then fortunately you're not bricked lol
have you tried re flashing the new firmware?

I flashed the 3.30 that the installation guide I was following told me to. I have ext 2.2, so is that an issue or is it the correct recovery.

Anyone who can walk me through this I'd really appreciate it guys. Just like most, I rely on my phone for work. I'm a little worried here, I've flashed quite a few times and I've never had an issue like this that I couldn't restore out of.....

Try this??
what I did was everything you did.. except I used this firmware update...
Firmware from 3.30.401.1 & 3.30.401.101 RUU
--- MD5 checksum: 824295C6ACDC8D55BED9E0B913192DBE *PG58IMG.zip ---
--- Only for 3.30.401.1 & 3.30.401.101 based ROMs
Then I installed the ICS Energy rom, and everything works great.. I've also flashed a few other roms without issues.. I haven't tried the arhd yet.. I'm currently running the virtuous AOSP rom.. and still, everything works great.. I hope this helps
Just a side note.. have you tried formatting the sdcard then trying that setup? I did have issues with my sdcard in the beginning, but after formatting, I've had no issues..Also make sure the ROM you're using is made for the correct firmware, otherwise you'll have bootloops! hope this helped!

That's the same firmware I used, and I've ran the firmware upgrade twice now. Now right after I updated the firmware the first time I did it, I rebooted on accident & it wouldn't boot even before I flashed arhd.... is this normal?

It wouldn't boot into hboot? What I did was put all the needed files on my sdcard, flashed the firmware, removed the sdcard(while the phone is powered on).. booted into the rom, then put the scdard back in and removed the firmware update..then rebooted the phone, then wiped and loaded an ICS rom..that was really about all I did.. and so far all works well.. I'm really at a loss as to what the problem on your end is.. it sounds like you've done everything you're suppose to do..

You could try to run the relevant ruu (assume you have s-off?) and start again?
http://forum.xda-developers.com/showthread.php?t=1074559

Update::II flashed Virtuous and had no issues and everything is running perfect. Looks just like my transformer prime now. I doing know why at this point that my system would not play nice with ARHD, I followed the guide to the letter and I flashed the firmware 3.30 several timed just as directed. None the less, I am satisfied with this from, and my device is much smoother and more productive than the ****ty GS2 by T-Mobile that I had been using the last few months! I just can't retire my Sensation. Thank you to all who chimed in, you're a great community!

Bricked
That happened to me too when I tried to install ICS without updating the firmware
first.
I just re-booted to recovery and did a restore. I'm assuming you backed up your
ROM right?
Then at least your phone will go back to normal and you can start over...and use it for work haha

I'm good now on virtuous, but I just couldn't get ARHD to work for me. Yes I had upgraded to the proper firmware first, and I always compare md5 sums. I'm by no means an expert, but I always research, read and ask all the nessecary questions before I flash anything I'm not familiar with. I think there may just be rare occasions when some of the devices just won't play nice with certain software. Virtuous took on the first flash & I'm actually very pleased with it, so all's well that ends well. ICS is just so much more intuitive & functional for me
.

Help Needed Please with HTC senation root phone after updating to CM9

Hello All,
I have HTC sensation 4g which i rooted the phone back in march by following the steps online after which i never updated it ..Couple of days ago i download cm7 and installed on my phone but forgot to backup ..After installation it started and looks like its a developer edition cm7 i don't see any of my apps and Google play store also .. Then i download cm9 and installed that now my phone restarts every other minute and i don't see any of my apps or Google play store ...Also the touch interface doesn't work ...
Can someone please help me from this situation
Thanks a lot in Advance

CM7 is a GB ROM. CM9 is ICS. You need to update your firmware to run CM9. For your apps and google play store, you have to flash the correct GAPPS after flashing the ROM when using CM.
You won't be able to update your firmware unless you are S-OFF. If you choose not to S-OFF, you need to use GB based ROMs.

Thanks for the response ..
I am okay to S-Off my phone but i am not sure how to do the total process. Right now i am okay to install/unistall/S-off whatever to make my phone restored or make it work like before .. Can you help me by explaining step by step process.

To upgrade your firmware to 3.33 - http://forum.xda-developers.com/showthread.php?t=1459767
Once you upgrade your firmware you can install any ICS ROM you want. Get in the development section and pick a ROM. Just remember to download the correct GAPPS if you decide to use a CM ROM.

there is a way to install fw without S-OFF.see also here
http://forum.xda-developers.com/showthread.php?t=1412618
for ics roms download 3.32 and 3.33 firmwares
only check first your cid and mid(it is necessary)

Thanks to everyone for the help until now ..
I have loaded the below CM ROM but the issue is i am still unable to get the google play and rest of the apps,unable to acess sd card too
cm-10-20120918-NIGHTLY-crespo4g
I know you said i need to install the correct gappss but what should i search for to find the correct one ?
Gapps for CM10 is that what i should be searching for .. Sorry if i have asked something that doesnt make sense...
Thanks in advance
I installed the gapps and looks like i might be able to get the apps will keep you posted ..
You guys rock

[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!