[Q] Desire S taking ages to boot - HTC Desire S

After upgrading to 2.3.5 + Sense 3.0, my phone takes about 2 minutes to boot up (as opposed to about 40s before the update) The majority of the boot procedure shows the Vodafone logo.
Does anyone else with a Vodafone-branded Desire S with the latest update experience this? Is there a way to reduce the time?
PS, the quick boot has always been disabled, so it isn't that.
Thanks in advance.

Mine too. It is ok

I had the same issue with my unbranded Desire S. I already had a post on this. It went back to fast boot times without me doing anything after a couple of days. The only think I may have done was uninstalling some unneeded applications and updates other ones.

I have this same issue. I have stock ROM with no changes. After upgrading to version 2.3.5 is boot time about 3 minutes long.. I cleaned applications, updated them, but with no effect.

Related

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

Phone keeps rebooting

Just installed new rom on phone.
Keeps rebooting every couple of minutes. Now I am not sure if it happened before I installed rom or not as I just went straight ahead and installed it as I have just received a replacement handset from a broken screen.
Any help?
Sense rom? Aosp rom? Rom name? Root? No root? More info man...
*Swaypovano sa Desire S BRE*
Saga3D v3.0 (Desire S official Sense 3.0) - [2.3.5] OTA 2.10.401.5
That rom. Installed the new hboot and orig stock kernal
Assume you have rebooted into recovery and wiped data, cache and dalvik cache, then tried to reboot?
Yes, I have done that a couple of times. I left it on connected with cable overnight and it doesnt seem to have rebooted. Seems to point to a battery problem??
It does boot properly. But after a minute it just restarts.
Edit. A bit more testing and it doesnt reboot when using a game or app. As soon as it closes to main screen it seems to just reboot as the screen goes into standby.
Edit 2. I have changed setting to stop screen turning off and its not done a reboot for the whole 10 minutes.
Does anyone think its a warranty claim? Or any more things to try?
Warranty claim seems a bit drastic, I'd try installing the rom again, or try a different rom, Endymion is sense 3.5 and stable... I was toying with it today, or pre rooted stock or even cm7 which at least you know is also rock solid
Sent from my HTC Desire S using xda premium
Just tried cm7 and it does the exact same.
Edit.... tried 4 different roms now. Going to go to stock with s-on and test. Then back to the shop again
Edit 2. Just use RUU on it and it is the same. Looks like I need to return it yet again.
Any more tips before I take it back in?
I had the same problem after 2.3.5 update. Went back to old version and it's fine now.
Assuming that you are not OC or UV then continue, else adjust to stock settings and re-try.
I recall a couple of others having a similar problem that was caused by either
a) loose battery connection, resolved by placing a piece of folded paper on top of battery to ensure it sat solidly in the slot.
b) dodgy battery, suggest that you contact HTC support, explain that phone keeps rebooting you suspect battery and request that they post you a new battery - don't post old battery back until you are sure its the battery at fault.

[Q] Strange bootloop behaviour on sense 3.5 roms

Hello people.
Since I got my sensation I have been trying a bunch of 3.5 roms, mostly Virtuous 3.0.0 beta and ARHD 4.1.5.
It seems that somehow, after I install all of my apps (~250) I start to get bootloops. Phone boots normally, loads sense, but after a minute or two it just reboots. Sometimes it even shows a "process system is not responding error" but tapping on "wait" does nothing. This happens even if I underclock to 1.18GHz and in ARHD has also happened with just 30 apps installed, just after I set up a bunch of HTC widgets on my homescreens!
I know most of the times bootloops have to do with kernel. In ARHD I tried both the stock kernel, the latest faux beta and the bricked kernel. With no luck.
Now, to make sure that the bootloop wasn't caused by one of my apps, I did the following: I split my apps onto three "sets". a) bought from market (around 70), b) free from market (around 120) and c) saved .apk's (around 50). Yesterday after flashing Virtuous, I spend around 6 hours installing them in random order (a/b/c, c/a/b etc) and rebooting multiple times between them, as to eliminate any potential apps. While at first it seemed ok, after having all of them installed I started having bootloops again.
Weird thing is, the first two or three reboots went on normally before I started getting loops again.
I'm using Radio 10.58.9035.00U_10.15.9035.02_2 with corresponding RIL.
Battery does not get hot, around 31-32c on boot and gradually becomes cooler.
Any ideas on what else to try and troubleshoot next? Radio possibly?
I highly doubt it has to do with the number of apps I have installed... could it be that my phone can't handle sense 3.5 roms for some reason? :/
ps: I'm NOT dissing those roms! I'm just reporting weird behavior on my handset
edit: I just flashed stock 2.3.5 kernel on Virtuous and tried again, seems to be fine for now. I'm gonna try a couple of more manual reboots, even try InsertCoin for the last time if it fails and then go for a 2.3.4 Sense 3.0 Rom :/
edit2: still no luck, bootloop after a couple successful reboots :/
akpidis said:
Hello people.
Since I got my sensation I have been trying a bunch of 3.5 roms, mostly Virtuous 3.0.0 beta and ARHD 4.1.5.
It seems that somehow, after I install all of my apps (~250) I start to get bootloops. Phone boots normally, loads sense, but after a minute or two it just reboots. Sometimes it even shows a "process system is not responding error" but tapping on "wait" does nothing. This happens even if I underclock to 1.18GHz and in ARHD has also happened with just 30 apps installed, just after I set up a bunch of HTC widgets on my homescreens!
I know most of the times bootloops have to do with kernel. In ARHD I tried both the stock kernel, the latest faux beta and the bricked kernel. With no luck.
Now, to make sure that the bootloop wasn't caused by one of my apps, I did the following: I split my apps onto three "sets". a) bought from market (around 70), b) free from market (around 120) and c) saved .apk's (around 50). Yesterday after flashing Virtuous, I spend around 6 hours installing them in random order (a/b/c, c/a/b etc) and rebooting multiple times between them, as to eliminate any potential apps. While at first it seemed ok, after having all of them installed I started having bootloops again.
Weird thing is, the first two or three reboots went on normally before I started getting loops again.
I'm using Radio 10.58.9035.00U_10.15.9035.02_2 with corresponding RIL.
Battery does not get hot, around 31-32c on boot and gradually becomes cooler.
Any ideas on what else to try and troubleshoot next? Radio possibly?
I highly doubt it has to do with the number of apps I have installed... could it be that my phone can't handle sense 3.5 roms for some reason? :/
ps: I'm NOT dissing those roms! I'm just reporting weird behavior on my handset
edit: I just flashed stock 2.3.5 kernel on Virtuous and tried again, seems to be fine for now. I'm gonna try a couple of more manual reboots, even try InsertCoin for the last time if it fails and then go for a 2.3.4 Sense 3.0 Rom :/
Click to expand...
Click to collapse
Hi,
How are you installing all of your apps?
Are you ,by any chance ,using Titanium Backup to restore the data?
And if so ,are you restoring any system apps or data?
Restoring system data from an old ROM to a new ROM has been shown to cause problems.
Nope, thought that would be the case at first and tried downloading them from market/installing them through ES, same result :/
Edit: what bothers me is that even tough the first couple of reboots are stable, usually the third or fourth result in a bootloop and or a "process system is not responding" error. Like something is being written or I don't know what at those first boots which causes the erros and bootloops afterwards.
Could this be attributed to my phone not being able to "handle" the leaked 2.3.5 rom?
I had the same issues on my Desire HD with some 2.3.5/Sense 3.5 roms, however once I flashed a 2.3.4/Sense 3.0 one bootloops stopped.

[Q] Infinite Boot Looping

-sigh- Alright, so I'm thoroughly confused. My Sensation has been constantly showing the boot screen, and then promptly shutting itself down and restarting the process. I can access recovery, but not sure what to do there. Here's some background info:
So, I've been using Virtuous Inquisition since version 1.0, including the original firmware, and I haven't updated the firmware since. I recently decided it was too buggy and decided to switch back to MIUI (the latest build), which is naturally Gingerbread, and not ICS. Everything force closed and the phone constantly shut itself down, so I assumed it was the admittedly very test/alpha-y ICS firmware that was the problem, so I updated to 3.24 (not Revolutionary), which people said should be compatible. At this point, I couldn't even boot up properly anymore. I removed the SD card to delete the firmware update, and now I can access recovery.
The weird thing is, I've tried many things, and all to no avail. Using recovery, I attempted to restore my stock Sensation, and so then I could see the "Quietly Brilliant" screen before rebooting, as well. Why didn't this work? I then removed the battery for ten minutes or so, Super Wiped (a la ARHD), and reflashed MIUI. Still nothing.
Is my phone hopelessly lost? ;_; Is the firmware still the issue? What on Earth can I do to save my irreplacable phone? Thanks in advance; I will be forever grateful if it can be salvaged.
invalid473d said:
-sigh- Alright, so I'm thoroughly confused. My Sensation has been constantly showing the boot screen, and then promptly shutting itself down and restarting the process. I can access recovery, but not sure what to do there. Here's some background info:
So, I've been using Virtuous Inquisition since version 1.0, including the original firmware, and I haven't updated the firmware since. I recently decided it was too buggy and decided to switch back to MIUI (the latest build), which is naturally Gingerbread, and not ICS. Everything force closed and the phone constantly shut itself down, so I assumed it was the admittedly very test/alpha-y ICS firmware that was the problem, so I updated to 3.24 (not Revolutionary), which people said should be compatible. At this point, I couldn't even boot up properly anymore. I removed the SD card to delete the firmware update, and now I can access recovery.
The weird thing is, I've tried many things, and all to no avail. Using recovery, I attempted to restore my stock Sensation, and so then I could see the "Quietly Brilliant" screen before rebooting, as well. Why didn't this work? I then removed the battery for ten minutes or so, Super Wiped (a la ARHD), and reflashed MIUI. Still nothing.
Is my phone hopelessly lost? ;_; Is the firmware still the issue? What on Earth can I do to save my irreplacable phone? Thanks in advance; I will be forever grateful if it can be salvaged.
Click to expand...
Click to collapse
You have to downgrade your firmware to 3.17 or lower in order to re-flash any gingerbread rom like MIUI. The 3.24 is NOT compatible with GB and will bootloop, in which you are experiencing.
Take the sd card out, delete the 3.24 img file and replace it with the 3.17. Boot into hboot and flash the downgraded firmware. Then go reboot. If you can get up and running go and delete the img file immediately. IF not, remove the card again and delete it with a card reader.
If you are already on a GB rom, the downgraded firmware should have booted up.

[Q] Phone boots very slow! Huge problem!

My problem is when I turn on the phone, the Google logo stays stuck and after unknown minutes boots in with the software animation, but very slow! First a little history of my upgrades with this phone.
My friend bought me Nexus S T-mobile version for US 6 mounts ago, and the phone was with Gingerbread 2.3.4. After reading many post from here, I decided to upgrade because I can't upgraded 2.3.6 OTA. After many hours I finally upgraded it to 2.3.6.
Then ICS came out, and again, I upgraded to 4.0.3. Then, a few weeks ago, I got the 4.0.4 OTA notification. Happily I taped yes. And then before two days ago, my phone just died. I don't know how.
I have 115 installed application, no music inside, no ROOT - just pure stock. I was in my college room and I left my phone on the desk right in front of me and after few minutes when I looked at the phone, the Google logo was there. I didn't give the phone to anyone to picks or anything. When I get home, I turn the phone on and still the Google logo just was there doing nothing and like I said before, after unknown minutes the phone boots in with very slow animation of the ICS software. I decided to install Clockwork Mod recovery 5.0.2.0 and root the phone. After reading many tutorials I installed CWM recovery successfully. Then I tried to downgrade to 2.3.4 and successfully I did that to.
Now after doing all this things to this phone, after so many hours in pain, the phone is nothing like one week ago. The booting is very slow, the animation is veryyy slow, and I don't know what to do anymore... I think this is hardware problem.
Please help me solving this problem, I really expect someone here to know what is the problem and will help me in anyway. I'm desperate, and I don't know what to write here to tell you how desperate and sad I am...
Thank you in advance.
p.s. sorry for any grammar mistakes.
http://forum.xda-developers.com/showthread.php?t=1572307&highlight=factory+images
yeah, definitely flash the factory images, you'll have to reflash cwm after though
Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!
muldy said:
Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!
Click to expand...
Click to collapse
not if youre a crackflasher(flash stuff often). i see my boot animation 5+ times daily, if not much more
Yeah.. I forgot that...
When I had the Htc Magic, I used to flash it a LOT
I like Stock, the auto-updates...
dewaffelhaus8 said:
yeah, definitely flash the factory images, you'll have to reflash cwm after though
Click to expand...
Click to collapse
I flash with the official images from here and I reflashed cwm.
muldy said:
Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!
Click to expand...
Click to collapse
I don't reboot that often, my phone itself reboots... I need to fix that problem, the slow booting, restarting, slow software... I need to know is it a hardware problem or software, because I did everything related to software problems...

Categories

Resources