Database Info

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

[Q] Crash after ROM Flash Help!!!

Hi Guys,
I literally feel sick to my stomach how dumb I've been.
I've basically fallen foul of the temptation to upgrade my HTC Desire S from the standard supplied gingerbread 2.3 to the hydrogen v1.9 saga v3 zip file (2.3.1.).
It’s crashed on me now all I have is the white HTC welcome screen.
I had installed the revolutionary.io s-off tool and rooted it. Everything seemed ok for about 3 weeks then I started to get intermittent phone call cut out and today it’s just frozen at the HTC logo on white background.
Today I have attempted to restore a backup file that I had made, to recovery it through the Revolutionary tool and it installed back to a low tech interface. I then tried to install over the hydrogen ROM again without success. Now it has 5 errors on the Rev tools’ opening page.
A mixture of;
Can’t mount/open recovery log/command/last log.
I don’t know what the hell to do any suggestions from you good altruistic folk?!!
Shall I try a factory reset?
I’d be very thankful of any suggestions. I just wished I’ waited for ICS, curiosity got the better of me

It sounds like an issue with your eMMc. The only way to recover is attempting to flash a stock ruu through hboot. If that doesn't work, it is likely nothing will. Stock RUU's can be found at this link http://forum.xda-developers.com/showthread.php?t=1002506 Good luck.

HI,
I am getting multiple installation errors when trying to clear/wipe/format cache/ system/ data etc.
I have tried installing Cyanogen ROM and installtion was aborted
I'm now trying to install a stock RUU as your suggestion. I don't know which one to choose the orange (I'm on Orange Network but no logo branding on phone) uk one I tried just wouldn't run and aborted and requexted an error mesaage. I'm now trying to install the RUU_Saga_S_HTC_Europe_2.10.401.5, one if thatg doesn't work any ideas which one I should go for?
Cheers

[Q] bootloop after installing ANY custom ROM

Hey there,
I have an interesting problem, and it has completely stumped me for the past couple days. I recently S-Off'd my Sensation, put cwm recovery on it, and set my CID to 11111111.
I haven't had any problems with that (except that I had to change computers to do it, Revolution didn't want to run right on my laptop or set the CID, so I had to use my desktop).
Now the problem comes when I try to flash a custom ROM. The first one I tried flashing was CM7. When it booted, I got a bootloop problem of the CM7 mod logo over and over. I decided maybe it was a problem with CM7 still being in alpha. Then I tried flashing HyperSensation 1.8, and got the same error (bootloop) on the loading screen. After trying various other ROMS, I realized that it was a common problem with all custom ROMS. Luckily I had backed up the stock setup, and was able to get into that. So it's not a problem with the hardware. I have only tried flashing gingerbread ROMS. I know that ICS ROMS need a new firmware, but I dont want to mess with that unless I can actually get a gingerbread ROM working first...
Any ideas? There was a thread or two about this (on other phones) but didn't have any solutions listed..
Thanks for any ideas people can give me!

TheLastGringo said:
Hey there,
I have an interesting problem, and it has completely stumped me for the past couple days. I recently S-Off'd my Sensation, put cwm recovery on it, and set my CID to 11111111.
I haven't had any problems with that (except that I had to change computers to do it, Revolution didn't want to run right on my laptop or set the CID, so I had to use my desktop).
Now the problem comes when I try to flash a custom ROM. The first one I tried flashing was CM7. When it booted, I got a bootloop problem of the CM7 mod logo over and over. I decided maybe it was a problem with CM7 still being in alpha. Then I tried flashing HyperSensation 1.8, and got the same error (bootloop) on the loading screen. After trying various other ROMS, I realized that it was a common problem with all custom ROMS. Luckily I had backed up the stock setup, and was able to get into that. So it's not a problem with the hardware. I have only tried flashing gingerbread ROMS. I know that ICS ROMS need a new firmware, but I dont want to mess with that unless I can actually get a gingerbread ROM working first...
Any ideas? There was a thread or two about this (on other phones) but didn't have any solutions listed..
Thanks for any ideas people can give me!
Click to expand...
Click to collapse
Hi,
Did you root your phone?

Did you flash the superwipe zip first?
Also are you getting full reboots with HTC splash screen then animation or just the animation looping? Sometimes I have to let mine loop for 5 minutes after first boot of new rom before it settles.
Sent from my Sensation XE using XDA App

I guess I hadn't done everything.. I didn't factory reset before flashing the new ROM... As soon as I did that it boot right in. That's a bit odd to me, as I didn't have to do that with my last phone.
Anywho, solved.
Sent from my Sensation using XDA App

Very weird problem with my newly-purchased HTC Sensation 4G

Hello guys, I've been having unusual problems with my recently purchased 2nd HTC Sensation 4g (it was supposedly brand new). I already have one HTC Sensation 4g running on Revolution HD for almost a year and regularly update it. Anyways, onto my issue with my new HTC Sensation...After I attempted to put on a new 3.33 firmware and the RevolutionHD 6.7.2 ROM, I was unable to boot it (stuck at the HTC quietly brilliant screen). I then tried to put on the latest T-Mobile RUU and again, it got stuck at the boot screen. I then superwiped again and repeatedly try out a bunch of the complete big ROMs (OrDroid 9.0, Elegancia Pegasus, etc) without any success. I was about to give up and figured my phone is bricked, but then decided to try out the more simple CM9 ROMs (Extreme Sensation Power-2) and was shocked it was able to boot and fully function! I then tried out similar ROMs and currently running Infinity's TouchCream 2.1.
I would appreciate if anyone have experienced similar issues and could give me some advice on how I could address it. I will have to do more experimenting to find out what's being going on. I have a feeling it could be a much more complicated problem than just simply mismatched/outdated ROM or Firmware. The reason why is because my 1st HTC Sensation (the control) was tested using the exact same configs without one single hiccup.

Reflash the newest firmware and then ARHD

I assume you are s-off with the latest 4EXT. If not, do that first.
I would download the latest 3.33 universal package: http://d-h.st/bCV, along with the latest ARHD 6.7.2: http://goo.gl/QDuTC
Run the firmware update through HBOOT (place PG58IMG.zip on root of the SD card, VOL DOWN + POWER, accept update), and then reboot into recovery.
4EXT should warn you that it is in safe mode due to a change in your HBOOT/partitions (if not, reboot recovery again, and if still not, you were already on 3.33 with revolutionary HBOOT ), so do a format of all partitions except SD card.
From there, reboot recovery again, and do a full wipe again to be safe, and install ARHD. Leave it for 5m to boot, should work.

Thanks for the advices guys. Unfortunately, none of the methods changed any of the results of my 2nd Sensation. It would still not boot the bigger ARHD or Elengancia ROMs (what appears to be Sense ROMs). However, it boots on CM9 ROMs (like TouchCream or Extreme Sensation). I have an identical phone that's a little older, which I've used as the "control" in my experiment. I've been using pretty much the exact same files and steps that you've mentioned, but my 2nd Sensation wouldn't go past the boot screen, even after 30m of waiting (meanwhile, my 1st Sensation has already finished its first boot within 5m). This happens every single time...frustrating! Please note that my 1st Sensation is also going through the exact same steps, just so I can eliminate obvious software or user errors. Anyways, I'm pretty happy at least I'm able to run TouchCream2.1 on this phone and enjoy pretty much all the functions that the HTC Sensation has to offer after I install the suitable apps & widgets. Thanks again!

[Q] Reboots 30 into loading ROM

From the beginning.
Unlocked
EVITA PVT SHIP S-ON RL
HBoot 1.14.002
Radio 0.19as.32.09.11_2
OpenDSP v29.1.0.45.0622
eMMC-boot
June 11 2012, 14:36:28
Click to expand...
Click to collapse
I was running a ViperRom my camera light was staying on, I tried everything to get it to turn off. I decided it been a few month it was time to get a new ROM anyways. I tried installing Gummy Nightly's was having problem with the install read about getting a different version of TWRP so I updated to 2.6.3.0 I believe I had 2.1.0.0. Gummy still won't work, so I changed plans and want for the Viper XL Rom 4.2.0 this led to a bootloop not getting past the Viper splash screen. I thought I might as well just with one of my backup. So, i wiped and loaded a backup. This is the problem, it will load up the ROM for about 30 seconds before the icon all appear it will reboot. I've now been working on this for 2 days. I've went through each post and tried the advice each person was given, I've tried to Flash a different Rom, the Viper Rom I had when I had the Camera Light Issue, each time I get about 30 second into the Rom Load and reboot. (One of the ROMs would let me access the SDCARD0 but found a work around that.) I've let the phone sit charged for 2 hours looping. I've turn it off and let it sit charging. The next thing I'm going to try to to downgrade the TWRP. If anyone can give me some advice, something new and different to try that would be great. Thanks!
Cheers
xDrFirefly

talked to one of my buddy and said the downgrade would be pointless so, i'm trying to flash a stock rom at the moment.

When you changed to TWRP 2.6.3.0 was it the official version or the unofficial modified version?
Sent from my Evita

Recovery: Custom TWRP 2.6.3.0 w/selinux support

And what errors did it give you when trying to install Gummy?
Sent from my Evita

The install failed. I tried it multi times, and even d/l it again to see if that would make a difference. Nope.
Here is what i've done so far. I factory reset everything. Found a stock rom flashed it on. For the two hours I used it seemed to work fine. I then flashed CleanRom everytime I would open Ti Backup the phone would reboot. I flashed another ROM, was getting the signal drop snagged the Beastmode Kernel it keep failing everytime I tried to flash it. Factory Wiped EVERYTHING again. Flashed the Stock, then Flashed ViperXL (then went to bed) in the morning still had signal bars, so far had two reboots, one when I was uninstalling apps using Manage apps feature, and another time when I was in the Venom HUB app. But at the moment the phone seems to be working. The battery life is ****. In the 30 mins I've had the phone unplug i've down to 89% and all I did was delete a few apps, and move some stuff to the home screens. Hopefully it will get better with time.
Side Note: To anyone reading this. I got the AT&T HTC XL preorder. I doubt I will ever do that again. In all the years I've been flashing and messing with phone. ( My first phone I messed with was a Sidekick ) I've never had so much trouble as I had with this phone. ( HTC Tilt, Fuze and Tilt 2 never had this kinda problem ) a friend of mine whom waited a year to get the XL has never had any of the problem I've had. Just my thoughts. Thanks and I hope I won't have to be asking anymore question.
When, I have more time and such I'm going to try to flash Gummy. If I get the same error message for it or anything else I will post it here.
Cheers
-Dr FF

I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita

You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.

jacobas92 said:
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
Click to expand...
Click to collapse
I will try this. Sounds like a very logical plan.

timmaaa said:
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
Click to expand...
Click to collapse
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".

xdrfirefly said:
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
Click to expand...
Click to collapse
Computer always says no for a reason. You need the right recovery installed to flash KitKat ROMs, you also need to check the md5 of every ROM you download before you flash it. What I'm saying is there's no reason Gummy wouldn't install if you have done everything correctly.