[Q] Boot very slow - Galaxy S I9000 Q&A, Help & Troubleshooting

Hello, on my Galaxy S I have installed last nightly of CyanogenMod 11.
But from the first time that I have installed the rom (CM 10) the phone take too much time to boot; it's not a big problem, but I don't know if it is normal. It take sometimes 2 minutes, sometimes 1 minute and 40 seconds, other 2 minutes and 30 seconds....
With the original firmware the boot was fast, max 1 minute.

BlackClaudio said:
Hello, on my Galaxy S I have installed last nightly of CyanogenMod 11.
But from the first time that I have installed the rom (CM 10) the phone take too much time to boot; it's not a big problem, but I don't know if it is normal. It take sometimes 2 minutes, sometimes 1 minute and 40 seconds, other 2 minutes and 30 seconds....
With the original firmware the boot was fast, max 1 minute.
Click to expand...
Click to collapse
Hmm... Try clearing cache and/or reflash your rom and see if it helps
Sent from my toaster

But I flash new nightlies often... So the wipe of the cache don't think can help... But I Try the same, thanks

Related

[CM9] Investigation on Bootloops

Hey folks,
being stuck in bootloops is one of the most annoying things for us powerusers.
Therefore I want to investigate a little bit deeper into this topic.
The normal procedure of "solving" the bootloops for me was flashing a base Gingerbread ROM by Ficeto (Mostly JVT) via ODIN, disabling Lagfix, entering CWM & flashing ICS again.
But one time (about 2 weeks ago) I had no time to go through this process, so I took the battery out of the phone (to abord the bootprocess & shut the phone down), placed it in again & putted the phone back in it's pocket.
About one hour later when I looked at it by accident (wanted to check the clock & forgot that it was bootlooping) the phone was fully booted & back to normal.
so the last 4 times my GT-i9000 (running nightlys of CM9) got stuck on the Bootscreen coming again & again, I took the battery out, placed it in again & let it bootloop for a while & after about 20 minutes baaam my SGS was properly booted?!
So my question/request is for you if you are stuck in bootloops:
[highlight]Please try the following:
1. Take the battery out & place it in again
2. Start the phone again
3. wait, wait, wait & be patient
4. Tell me if the problem solved itself or if after more than 2 hours of bootlooping nothing happened [/highlight]
if it didn't please tell me how long you've waited, what caused the looping & which nightly etc you where running!
just for clarification: with bootloops i mean being stuck on the Samsung Galaxy S / Cyanogenmod Screen where it is written in plain text which appears before you can enter recovery or the normal bootanimation appears. When my phone was/is bootlooping I also have no chance to enter Recovery. & I also know that it sounds strange that BL should solve themselves, but please try it!
[edit] I also read some time ago that there where other people with the same experience, this is why I opened a thread & I'm sure this is not a thing related to only my phone
I experienced something similar , also with CM9 . Phone working very hard , so i restarted it , but after the Galaxy S GT i9000 screen , the CM9 blue boot loaded for about 10 minutes and nothing , so I decided to enter in recovery ( I removed the battery , waited a minute , inserted it in the phone , and the recovery didn't work . Waited 10 minutes , and after that the recovery worked , and I reflashed CM9 , because it was the only rom I had in the internal SD card .
About two hours without any improve... CM9 build 12 working every time, build 15 and 16 without chance. Odin is my honey
Thomas. said:
About two hours without any improve... CM9 build 12 working every time, build 15 and 16 without chance. Odin is my honey
Click to expand...
Click to collapse
It would be nice if you could tell exactly what you did, if more people would do that we might be able to figure out why this thing happens to you and why it doesn't happen to me.
when i flash:
*phone not connected to pc or charger
*running stock kernel
*16 gb micro sdcard mounted
*all sorts of battery percentage, from 10 to 100 percent
*reboot recovery by terminal command "reboot recovery"
*format /cache
*flash the build from /mnt/sdcard/download
*flash gapps from same location
*run a script that wipes dalvic, removes several sounds and unwanted apps and fixes permission
*format /cache again
*reboot
I know this is a pretty weird procedure and it's in no way an advice to anyone, it is just an example of giving details that might lead to a common factor for bootloops.
Taptalked u see
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & same thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
BLADESMAN1889 said:
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
Click to expand...
Click to collapse
Thanks for your post!
What caused the bootloops?
fipsib said:
Thanks for your post!
What caused the bootloops?
Click to expand...
Click to collapse
1st time I got bootlooploop was [15/Jan/2012] I was trying to boot into Recovery via power button so I could upgrade from Build 12 to Build 13.
2nd time [2/April/2012]I was on AOKP B28 & I had booted into Recovery to wipe cache & dalvik & after successfully wiping, the bootloop came when I hit the 'Reboot' option to start the phone.
(AGAINST better judgement - since first bll I had avoided wiping cache & dalvik)
jep. I also had bootloop problems by wiping cache and dalvik cache. I was on SlimICS flashed midnight kernel. Everything was working just right but CPU scaling had some bugs for me so i removed init.d scripts went into recovery wiped cache and dalvik cache...and boom....bootloop :/. Now I'm back on CM7 because this is a rather annoying problem....
BLADESMAN1889 said:
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & same thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
Click to expand...
Click to collapse
Can you link me CM7 kernel for Odin? thanks
farid993 said:
Can you link me CM7 kernel for Odin? thanks
Click to expand...
Click to collapse
Yep, here it is,
View attachment 1012442
This worked for me both times
[remember to leave UNCHECKED
Ensure Reboot, Repart, F-Reset]
Then boot into Recovery and restore Nandroid - no need to be flashing gingerbread.
Ever since the first nightly, I have been plagued by bootloops. Usually formatting /system, /data and /cache helped. But not this time. I tried to install the 19/4 nightly, and had gotten into bootloops. Yes, I have used custom kernels before.
However, even clearing init.d, clearing NSTools, flashing from FixRecovery, the cm7 kernel, even flashing with Heimdall (flashing stock kernel and custom kernel) could not get me out of the loop. Note: I tried the method as described in the OP.
What I finally did was format everything, excluding ext-sd. Format internal SD as well, after backing up some files. And BAM! That was it! Something on the SD corrupted the install. No bootloops, can even install custom kernel, no problem.
So, that may be a tip for people not able to get out of the bootloop, or experiencing constant bootloops.
Hey it's under Devs investigation now:
http://forum.xda-developers.com/showthread.php?t=1627689
My galaxy with CM9 started to bootloop yesterday, no way to enter recovery
I'll make you know in a couple of hours if something change leaving it on ..
If nothing change, is there a place where I can find CM9 kernel to flash with odin ?
thanks
Read Bejda's post, one post above yours.
Taptalked u see
wooops didnt see the second page of the thread
anyway leaving it there to bootloop didnt solve the problem
flashing semaphore kernel seems yes

[Help] [CM] My One is rebooting every 5minutes

Hello,
My HTC is rebooting every 5 minutes, somtimes more, somtimes less.
The screen turns black for half a second and after i get the cyanogenmod logo for few second.
I don't have to type my PIN code each time this happens.
My problem started today, I installed CM on saturday.
Sometimes I also can't unlock the phone, the LED is shining but i can't wake it up, i have to hold power + volume - few times to run bootloader and restart the mobile.
This is strange, any ideas what is going on ?
Maybe I am posting in the wrong section and sorry for my english.
Ps : I typed this message 2 times on the HTC but each time it reboot and I have to start again :crying:
Sounds like you need a full wipe
Thank you for your response
I backuped, wiped factory and restore and i didn't help.
So can you tell me what kind of wipe do I have to do ?
I am using TWRP
Do a clean install of the Rom..something you did messed with your stability... Don't restore...
Instructions
Wipe factory and cache
Install Rom freshly

Why does my phone shutdown after 1 minute of use?

I just installed a new rom and every time I turn on my device, it would shut down after 1 minute of use. I try to install different roms, but that doesn't work. Any suggestions?

Long boot issues

When i reboot after installing CM12.1 or RR using TWRP restore, i am jumping between them trying them out, the system takes 5-10-15 minutes and nothing happens and sometimes it boots. i have to force stop, go into recovery and then wipe cache and dalvik cache then restart and it usually boots in < 2 minutes. is this normal? it happens when i do a restore or after i do titanioum backup restore of my apps and data.
From what I've read in the forms those boot times are correct for a new install. There's a lot of things happening when you first install a ROM.
mlk77 said:
From what I've read in the forms those boot times are correct for a new install. There's a lot of things happening when you first install a ROM.
Click to expand...
Click to collapse
Right. First boot takes a long time.
Also helps to stick the phone in the freezer in a zip lock bag as it's doing a lot of work and can get hot. I'm not joking. If your phone goes 20 minutes and turns OFF without finishing boot -- the animation ran and ran and then it just turns off, then it got so hot it shut itself down.
That's why I put mine in the freezer. It also shortens the boot time as the phone is cooler and can run faster. The CPU won't throttle down.
Forcing it to stop and and rebooting is somewhat dangerous as something could get corrupted.
thanks

Xiaomi mi 9 reboot every 15 - 30 minutes

hi i want to ask why my mi 9 is rebooting it self every 15 - 30 minutes. I notice that it even faster reboot if i use the finger print. For the first minute after restart, i can use the fingerprint , but after 5 minutes or so it stuck on the fingerprint animation and then restart again, I try to turn off the finger print and using pattern only, it help but still the problem is not solved, still restarting every 15 - 30 minutes. Oddly it didnt happen if i watch youtube or netflix. After i watch from youtube and start browsing then i can be hang and reboot again. I already try to flash via fastboot the miui 11.0.5 global, the miui 10 , custom rom pixel expereince but the issue is still on. Can i know what's the main problem of this ? many thanks
Go to TEST Mode and check the hardware to get sure about the ruined part! After that you can format the phone in TWRP and clean flash a ROM!

Categories

Resources