Hi, I have been experiencing substantially longer boot time on my Desire S after having updated to FW 2.10.401.8, using RUU method.
Fast boot is obviously enabled, i am 100% stock, S-On, Unrooted. I also tried a factory reset last night but it didn't change anything.
The RUU flash completed flawlessly and did not get any error during the update process.
Has anybody else noticed something similar?
I always suggest that you Disable fast boot, it saves seconds but brings no real benefit while being dangerous
How often do you restart your device and why?
What does seconds on restart boot matter?
I Suggest dropping into custom recovery and perform a full format on all partitions, then install custom ROM and report back
Edit
Just re read you say stock soff and UN rooted, this doesn't add up
Swyped from my Desire S using XDA Premium
Ben, I made a mistake while writing the post, I am S-On. I know a few seconds doesn't make a big difference but I would like to understand if the update introduced longer boot times for everybody or if anything in particular is causing this on my phone.
I do not want to root yet as I am still under warranty.
Ok, it seems now the boot time is short again. I think that the only change I made has been removing and updating some apps...
Related
I tried the different ROMs after Full Wipe each time but same problem happens.
i did FIX PERMISSIONs and Wiped Dalvik cahe and battery stats ..
I also did use Set_to_default_1.2GHz_Sensation.zip and it also didnt work
so please if anyone have any solution ..inform me asap
AND I WANT TO KNOW WHAT IS CAUSED THIS PROBLEM
This happened to me. I didn't follow every step to getting permanent root in the correct order. Luckily, I did the nandroid back-up, and restored the back up, then went back to s-on and started over.
Everything I read says if you have s-off, it is an installation of the rom issue, like installing an incremental update instead of a full rom.
Hope that helps.
When I had this problem, it turned out to be caused by my trying to use Titanium Backup to restore backups of Sense-related apps.
boot loop
It isn't as bad as you think I had a boot loop and its a easy fix step one boot into recovery and don't back up anything do a wipe and clear out your cache and battery stats and flash the rom oh by the way don't flash any kernel's yet use the one that is included in the ROM that should get you going and the reason your haveing this problem is because you didnt follow directions and you should flash the rom as it is intended because most roms are optimized to operate with certain kernels and stop taking short cuts or you will end up with a paper wait good luck and follow the step-by-step instructions and you will have a very nice sensation 4g souped that is
how can I turn it back to S-On ?
Hi,
Sometimes my Sensation just reboots itself. My first thought was because of the beta version of the ICS, so I decided to go back to the Ginger. But im still having the same problem.
Does someone has the problem and what did you do, to let it disappear
Thanks
reeboots
hi,
first you should download the latest firmware package from mike1986 and upgrade.
put it on your sd and go into bootloader and let it detect it (that the one you need "Firmware from 3.12.401.2/102 RUU")
after that put your wanted rom and do full wipe ext4 and than flash your wanted rom.
remember don't use any ad dons that are not supported it will cause you those reboot problems, also when restoring from backup restore only data like sms and ppl. apps data may be not supported and could cause problems.
good luck...
Ok, i'll try it again.
I've already did that so.. we shall see..
Thanks ;-)
The random reboots seem to be a quite common problem. I'm also having this issue. But setting the phone to either GSM only or WCDMA only seems to keep it alive (if the cause for reboot is the same as mine of course..). I installed the new firmware hoping it would help but I still get reboots. It's actually not a reboot as the phone just turns off and I have to manually turn it on again.
Yes its the same as me, but sometimes my phone 'reboots' more than once in 5 minutes..
Also my battery change from 5% to 30% to 7% to 41%...
Sent from my HTC Sensation using XDA Premium App
guys I have a serious problem..!!
I was in 5.1.8 everything was fine non a problem and when 5.5 came out I installed it, super wipe script, and install the Rom; I was getting a lot of boot loops. Reinstall the ROM again full wiping, ans still the same. I came back to 5.1.8 and I'm still having boot loops but not that often like it was in 5.5, now I have boot loops when turn on the data or when I try to make a call... I really don't know what could be the problem because I have installed hundreds of roms with the same steps and everything was fine,.I don't know what could be the problem...
I hope someone could help me thanks a lot
from my HTC Sensation XE with Beats Audio using xda premium
renehd2 said:
guys I have a serious problem..!!
I was in 5.1.8 everything was fine non a problem and when 5.5 came out I installed it, super wipe script, and install the Rom; I was getting a lot of boot loops. Reinstall the ROM again full wiping, ans still the same. I came back to 5.1.8 and I'm still having boot loops but not that often like it was in 5.5, now I have boot loops when turn on the data or when I try to make a call... I really don't know what could be the problem because I have installed hundreds of roms with the same steps and everything was fine,.I don't know what could be the problem...
I hope someone could help me thanks a lot
from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Hi... I once had a similar problem late last year. My phone kept rebooting randomly, sometimes as soon I switch the phone on, or data like yourself. What I did was.... Installed the official RUU that came on my phone (O2) and the rebooting stopped. But I felt the need to send it back anyway, so I did and just as well, because HTC replaced the mainboard and a few other things. I hadn't overclocked or anything either so it was a strange one.
This way worked for me, so give it a go.
I rooted my phone, then unrooted without ever installing a custom rom. I have gotten boot loops ever since and seemingly random shut downs that require me to take out the battery and put it back in before the phone will boot up again. Happens every day, several times a day.
MANTI5 said:
I rooted my phone, then unrooted without ever installing a custom rom. I have gotten boot loops ever since and seemingly random shut downs that require me to take out the battery and put it back in before the phone will boot up again. Happens every day, several times a day.
Click to expand...
Click to collapse
When you say rooted and unrooted what exactly did you do?? Meaning did you HTC unlock or use revolutionary to s-off? And what recovery did you use? Because in actuality all root is, is the su binaries and the su app, not the process of gaining the access. There are inherent problems with the htcdev unlock and using cwm as your recovery. Even if you delete su the remnants of either process could possibly cause problems. Did you return to s-on again?? Because that will cause serious issues if you don't have the correct ruu. Did you flash any newer firmwares??? The few before .32 did cause loops without the correct rom.
Also in your case it sounds like a rogue app causing loops because it boots up after a battery pull. Have you tried to factory reset and wipe your data to see if that helps??
Sent from my Sensation using xda premium
renehd2 said:
guys I have a serious problem..!!
I was in 5.1.8 everything was fine non a problem and when 5.5 came out I installed it, super wipe script, and install the Rom; I was getting a lot of boot loops. Reinstall the ROM again full wiping, ans still the same. I came back to 5.1.8 and I'm still having boot loops but not that often like it was in 5.5, now I have boot loops when turn on the data or when I try to make a call... I really don't know what could be the problem because I have installed hundreds of roms with the same steps and everything was fine,.I don't know what could be the problem...
I hope someone could help me thanks a lot
from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
it's maybe hardware failure in first place but after doing battery thing it was fine
go here and try battery fix thread plzzz post back and vote in first thread
MANTI5 said:
I rooted my phone, then unrooted without ever installing a custom rom. I have gotten boot loops ever since and seemingly random shut downs that require me to take out the battery and put it back in before the phone will boot up again. Happens every day, several times a day.
Click to expand...
Click to collapse
it's a battery thing go here and try battery fix thread plzzz post back and vote in first thread
Used Revolutionary, not sure what I used to put it back as it's been a while but I followed a guide from here. I'm trying the card piece trick so we'll see if it does anything.
Pm me if your soff I can help easy
Sent from my Sensation using xda premium
Thanks but not s-off anymore and just got another reboot so I doubt it's the battery. I guess I'll try to deal with it until ICS and see if that fixes anything. If not then I guess I'll try something more drastic.
Well get soff you can't fix with out it
Sent from my Sensation using xda premium
Ok, got s-off again.
It seems to have something to do with going in and out of service or switching between wifi and cell service. But that could just be a coincidence.
Anyone have ideas on how to fix this? I got the OTA ICS and I'm still getting reboots.
MANTI5 said:
Anyone have ideas on how to fix this? I got the OTA ICS and I'm still getting reboots.
Click to expand...
Click to collapse
it's a battery thing go here and try battery fix thread plzzz post back and vote in first thread
it won't hurt ur phone u must stick a tape to close the gap between batt pins and connectors do it and see it easy but worth allot
Tried that earlier in this thread and it didn't help.
Anyone else?
Well guys after reading I fixed my problem cleaning the little panels in the battery, and also installing another rom, seems like the htc sense roms have some problems with that because since I install a senseless rom (not aosp) the problem is gone
Sent from my HTC Sensation using xda premium
I think you did not unroot properly. Can you please describe the process you used for unrooting?
Don't remember what guide I used to unroot as it was a while back. It definitely seems to have something to do with the signal. It will lose signal, reboot, get pretty warm and repeat while sometimes just shutting off and needing the battery pulled and put back before it will turn back on. My wife will have a signal just fine in the same areas mine loses them.
Very frustrating because I'm missing a lot of calls and txts because it'll just shut down.
MANTI5 said:
Don't remember what guide I used to unroot as it was a while back. It definitely seems to have something to do with the signal. It will lose signal, reboot, get pretty warm and repeat while sometimes just shutting off and needing the battery pulled and put back before it will turn back on. My wife will have a signal just fine in the same areas mine loses them.
Very frustrating because I'm missing a lot of calls and txts because it'll just shut down.
Click to expand...
Click to collapse
First make a NANDROID backup now. Then try rooting again to see if that fixes the issue.
If not, try to flash a different Radio. I would in your case also suggest wiping all partitions except SD card and re-installing the ROM, after flashing the radio.
Had just flashed the latest CM9 nightly (clean install, fresh wipe) yesterday and everything was running fine.
This morning, woke up, my phone was turned off. When powering it on it hung on the google screen. Fastboot still working, booted into recovery only to find that I would get error messages when trying to load my backs "E:unable to mount /sdcard". Apparently it also couldn't mount /data. So I was unable to flash any images or restore or boot up.
Seeing that fastboot was still working I assume I'm not bricked yet. I tried flashing a new boot and cwm recovery via fastboot - no dice. Same errors.
I don't have a recent backup of anything in sdcard, but at this point I'm willing to sacrifice it.
Found this thread http://forum.xda-developers.com/showthread.php?t=1078213
and I'm trying to follow the steps to flash back to stock GB. using the GRJ22 images
It flashed the boot and recovery without issue but seems to hang while flashing the system.img. I know it's a big file, but it was up to ~2hrs with it still transferring. I pulled the plug on it and tried again, lost patience after an hour.
Now I had the idea of maybe locking and unlocking the boot loader would help things.....not sure why I thought this. Anyway, now it seems to hang on the unlock bootloader screen.
So my question now - am I screwed?
- anything else to try?
- is it really "hanging" or do I need to give it more time?
- have I screwed myself even more by now locking my bootloader and flashing the stock recovery?
Any help would be very much appreciated....
Some new additions and new insights from the reddit android community:
- this probably has nothing to do with CM9. My phone has been wonky for about two weeks - random reboots, sometimes rebooting into recovery. That's why I thought I'd throw on the latest nightly and do a fresh wipe yesterday.
- There's definitely something up with /data. Anytime I tried wiping all/factory reset in cwm recovery I got errors about not being able to mount /data or being able to find files in /data
- basically anything I do involving /data partition causes the phone to lock-up -- flashing the boot.img and recovery img worked, but not system. Also, I think the reason I can't re-unlock the bootloader is because during the unlock process it tries to do a factory reset/data wipe
Basically I think there are two things I need to know if I can do - 1) unlock the bootloader again, via some way that won't try to reset the /data partition and thus won't freeze the phone. 2) try repartitioning /data
I really hope I didn't screw myself by locking the bootloader. I'd actually feel a lot better if it was something in my phone that just failed hardware-wise rather than something I could've fixed if I wasn't too quick to try poorly thought out ideas.....
Any help at all would be appreciated!
Possibly (and likely) a corrupted nand flash. Fairly common problem sadly. I'd say it's a good thing your bootloaders locked, no dramas sending it back to samsung. It might've been possible to reset the partitions and flash fastboot images but i don't think i've seen anyone who has done this to sort any similar problem. Hopefully your phones still under warranty
Well thank God that it turns out that I'm still on warranty.....sending the phone back to Samsung tomorrow.
Like you said, it's actually a good thing the bootloader is now locked and the stock boot img and recovery img are now back on! Hopefully this makes it more likely that they weren't turn away my phone.
I've yet to hear someone not getting work done under warranty because of an unlocked boot loader but it's always good to have it as stock as can be. Hope they don't take too long with your phone.
Harbb said:
I've yet to hear someone not getting work done under warranty because of an unlocked boot loader but it's always good to have it as stock as can be. Hope they don't take too long with your phone.
Click to expand...
Click to collapse
I bricked my nexus s 4 days before Christmas last year... and i was using a custom rom obviously with an unlocked bootloader and custom recovery image, and i handed it to vodafone, and guess what? they repaired without asking any questions, and the day before Christmas! sooo happy maybe because i was thirteen then, they didn't suspect a thing
I have had nothing but issues with this phone upgrading. Every time it bricks, the first time I got it working by reformatting DATA partition. The other times basically gave up and 2-3 days later I come back and it magically starts working again. The day that 5.0.1 came out I downloaded the FUU, well everything looked good the it gets stuck at the Android is upgrading starting apps. Since then I have redownloaded all 5.0.1 files I could find on XDA, and the same results. I tried different roms, using TWRP to wipe and rewipe and format and do it again and again. I have tried to downgrade to 4.4.2 and 4.4.4 but i get the process system isn't responding when it boots up. I am unsure what to do now, anything will help.
You flashed this RUU???
http://forum.xda-developers.com/showthread.php?t=3047103
After flashing that do a factory reset from hboot. That should get you back to a healthy stock system
berndblb said:
You flashed this RUU???
http://forum.xda-developers.com/showthread.php?t=3047103
After flashing that do a factory reset from hboot. That should get you back to a healthy stock system
Click to expand...
Click to collapse
Yes, that was the first thing I tried, but I just downloaded it again twice and did factory reset both times and I still get stuck on the "Android is upgrading... Starting apps."
dab1414 said:
Yes, that was the first thing I tried, but I just downloaded it again twice and did factory reset both times and I still get stuck on the "Android is upgrading... Starting apps."
Click to expand...
Click to collapse
So after it upgrades all apps its just sits on starting apps?
Can't hurt to run RUU again. Perhaps even4.4.4 then take the OTA for 5.0.1
andybones said:
So after it upgrades all apps its just sits on starting apps?
Can't hurt to run RUU again. Perhaps even4.4.4 then take the OTA for 5.0.1
Click to expand...
Click to collapse
Yes It gets stuck there everytime. Seems like no matter what I do for 5.0.1. When I tried to downgrade ( I did both 4.4.2 and 4.4.4) it gets the process system isn't responding error.
dab1414 said:
Yes It gets stuck there everytime. Seems like no matter what I do for 5.0.1. When I tried to downgrade ( I did both 4.4.2 and 4.4.4) it gets the process system isn't responding error.
Click to expand...
Click to collapse
that's very strange. What method are you going about with the RUU?
using adb?
perhaps maybe try going through hboot with the sdcard?
not sure it will make any difference what-so-ever, just brainstorming.
andybones said:
that's very strange. What method are you going about with the RUU?
using adb?
perhaps maybe try going through hboot with the sdcard?
not sure it will make any difference what-so-ever, just brainstorming.
Click to expand...
Click to collapse
Yes, it is very strange. OK so I have done nothing with adb for the upgrade. I have tried the FUU.exe, and the RUU through fastboot, fastboot flash all files separately, and put on an external drive that is fat32 to use HBOOT method. and I just downloaded the firmware and did the HBOOT again twice, doing a factory reset after each one. But in bootloader screen all firmware numbers match up and I never get any errors, just gets stuck on starting apps.
dab1414 said:
Yes, it is very strange. OK so I have done nothing with adb for the upgrade. I have tried the FUU.exe, and the RUU through fastboot, fastboot flash all files separately, and put on an external drive that is fat32 to use HBOOT method. and I just downloaded the firmware and did the HBOOT again twice, doing a factory reset after each one. But in bootloader screen all firmware numbers match up and I never get any errors, just gets stuck on starting apps.
Click to expand...
Click to collapse
Are you S-OFF?
If so are you wanting to run a ROM or just be on stock + rooted?
andybones said:
Are you S-OFF?
If so are you wanting to run a ROM or just be on stock + rooted?
Click to expand...
Click to collapse
Yes I am S-OFF since the day I got the phone. And I have been using RKND roms, but I downloaded and tried all the 5.0.1 roms to see if anything would help. At this point I just want my phone working again, but preferably with the ability to change roms when i want to which is about once a month or two.
So I had tried everything I knew how to do again with no luck. Then I just let my phone sit for the last week. Then I decided to turn it on last night and it works fine. Is there any reason why I had to let the phone stay powered down for days for it to start working? This is the second time I had to do that when upgrading the firmware.
Thanks for bringing this up and I'm glad to hear it worked out for you even tho it took some time. My bro just ran the vzw update while on viper 4.1.0 and now he says his screen is unresponsive. He said it ran through all the normal start up procedures but the welcome screen is shaded (like it's in the background) and he says it won't respond to any touches whatsoever. I won't get a chance to see it until I return to work on Wednesday but if it does the same as yours maybe it'll fix itself by then. :fingers-crossed:
Edit: I just realized that you ran the FUU. He went and said yes to the stupid OTA! Hopefully I'll be able to do something with it when I get back but I'm thinking that running the OTA while rooted and S-Off'd might've screwed it up.
Update: I'm a moron! :silly: It didn't do anything to his phone. I just had to reinstall the recovery and viper 4.3.0 and it's working fine again. I think actually it might've been a good thing he did cause now the phone had the right firmware on it for LP so it all worked out. Sorry for cluttering up your thread.