why is my epic taking so long to boot? - Epic 4G Q&A, Help & Troubleshooting

Hello,
I was just wondering why my epic was taking so long to boot, A while ago, I could boot in 15 seconds, but now it takes around 2 minutes, I tried syndicate and midnight but they all booted so slow. Anyone else experiencing this?

gokuman56 said:
Hello,
I was just wondering why my epic was taking so long to boot, A while ago, I could boot in 15 seconds, but now it takes around 2 minutes, I tried syndicate and midnight but they all booted so slow. Anyone else experiencing this?
Click to expand...
Click to collapse
I hope your not basing this on the first boot after flashing a new rom, cause its always slow the first time you boot. Both of the roms you mentioned boot for me in around 20~25 seconds.

I know the first time you boot after flashing a rom it can take a few minutes. After that I have never waited longer then 30 seconds.
Sent from my SPH-D700 using XDA App

This regularly happens.
I have already set up the rom and everything. I have been running it for 2 weeks. It still takes forever to start up. Does anyone know why?
thanks

If you're using a no-journaling ROM that could be a factor.

063_XOBX said:
If you're using a no-journaling ROM that could be a factor.
Click to expand...
Click to collapse
I've run all and mainly I run no journaling, except when testing new kernels. All my boot times are pretty much the same. Gokus phone could have something corrupt that's causing the long boots, I know the pre was that way, tho 2 to 3 minutes to boot was fast and 4 to 5 minutes was slow with corruption likely. Something is surely wrong tho, 2 minutes is not normal.

Ok, I will odin back to EC05 and see if that helps. What is the best link for EC05? I want to make it optimal for flashing ROMS, should it be prerooted or something Else?
Thanks

gokuman56 said:
Ok, I will odin back to EC05 and see if that helps. What is the best link for EC05? I want to make it optimal for flashing ROMS, should it be prerooted or something Else?
Thanks
Click to expand...
Click to collapse
Go with prerooted and save some steps. Heard this was a good one for that:
And it is flashable
http://forum.xda-developers.com/showthread.php?t=1027904

Here's an idea that I learned the hard way. Maybe you've got too many programs installed that want to load at boot. Remove one at a time then reboot each time and I bet you'll find the culprit. Another idea is do you have a lot of stuff on your sd card? It's going to want to scan it everytime you boot. The more stuff you have on it the longer it will take the scan to complete. I don't know your setup but I thought I'd mention it anyways.

My stock install takes 30sec
Sent from Snarf phone

Related

Constant Bootloop after flashing ANY kernel

Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
DL the new stock kernel to pc mount card to pc put the new kernel somewhere you'll remember then reinstall sdcard and try flashing the kernel that way if you haven't already
Sent from my ADR6300 using XDA App
Hypcrsy said:
Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
Click to expand...
Click to collapse
You should not be wiping data when flashing a new kernel.
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Hypcrsy said:
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Click to expand...
Click to collapse
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
najaboy said:
You should not be wiping data when flashing a new kernel.
Click to expand...
Click to collapse
Sorry I just saw this post immediately after I replied. I thought wiping data applied for both flashing ROMS and kernels.
najaboy said:
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
Click to expand...
Click to collapse
^This. Only wipe dalvik, not data.
Ok I'll give it a shot while I'm here. I was flashing over to the new edition of Kings and it just became incredibly unstable when interacting with SetCPU, so I was just going to go back to the stock HTC one, that's when I got the first constant bootloop. I'll give it a shot and let you guys know what happens. Thanks for the feedback.
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Hypcrsy said:
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Click to expand...
Click to collapse
thats weird anyone else having that problem? haven't tried 6 yet
Sent from my ADR6300 using XDA App
You only need to wipe dalvik if going to and from one with HAVS, but it doesn't hurt to be safe.
Sent from my ADR6300 using XDA App
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Hypcrsy said:
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Click to expand...
Click to collapse
Not exactly. I was running 5 on SkyRaider 3.3.2 for a while, then all of a sudden I started having horrible lag while unlocking the phone and for about 7-10 seconds afterwards. Is this what you're referencing? When I switched to BFS6, I didn't have the problem. But the problem did kick in a while after install of 5 (few weeks), I didn't have 6 that long. 6 seemed pretty solid. Give 6 a shot, if you don't like it, just flash something else. Nandroid just to be safe, too.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
Yeah I always nandroid just in case when I do any serious modification, but I was experiencing the same issue with 6 as I was with 5. Just checking the different limits with SetCPU, anytime I went over 1.1 for overclocking the phone would stay on for about 15-20 seconds and then reboot, get as far as the red eye and then reboot again. That was as far as I ever got with his kernels which is unfortunate.
When testing SetCPU and overclocking, make sure you don't have set on boot enabled.
Sent from my ADR6300 using XDA App
Thanks I'll give it a shot later on.

all Roms lead to random reboots

recently, my phone has just started a habit of randomly rebooting. i was using myn rls5 with net kernel 4.3.2, but i decided to try something different in an attempt to stop the problem, so i went to mikfroyo with its default kernel. right after i startthe phone and it gets to the homescreen, it starts restarting again. i cleared data and cache between roms, and im using clockworkmod 3.0.0.5
You should always perform a full wipe, to include factory/data, when flashing a new rom.
teh roxxorz said:
You should always perform a full wipe, to include factory/data, when flashing a new rom.
Click to expand...
Click to collapse
i did. every time
ryohei47 said:
i did. every time
Click to expand...
Click to collapse
Also, the dalvik, under advanced? And not flashing a kernel with it?
I found out that Clockwork never cleared Dalvik for me. I changed to AR and after clearing the dalvik I stopped getting reboots or bootloops. Maybe your phone doesn't like the new Clockwork...
Shigster said:
I found out that Clockwork never cleared Dalvik for me. I changed to AR and after clearing the dalvik I stopped getting reboots or bootloops. Maybe your phone doesn't like the new Clockwork...
Click to expand...
Click to collapse
that could be it. everytime i install RA though, it complains and doesnt boot into recovery correctly
oohhh. that sucks. try unrooting or using a stock rom for a while. if it keeps rebooting when you browse the web, play games, anything that works the phone, then there is nothing you can do. the phone is fried. wait until it is bad enough that you can do it whenever you want by firing up a game and playing for a few minutes. then bring to the sprint store and they will replace. hah why do i have to be the person who brings the bad news?
again, try unrooting first. you can even leave s-off to re root easily. if you have no reboots, then the problem can be fixed.
i feel so bad giving this news... hah
My phone recently started doing this. Doesn't matter what ROM I'm on, doesn't matter if I un-root with a factory RUU or re-root, doesn't matter what recovery I use, doesn't matter if I completely format my SD card or boot without one. It got to the point I had to take it to Sprint and have them order me a new one.
It would randomly reboot and then go into a bootloop that not even a factory reset would cure, just decides when to stop bootlooping on its own and occasionally works.
ryohei47 said:
that could be it. everytime i install RA though, it complains and doesnt boot into recovery correctly
Click to expand...
Click to collapse
If you're using ROM Manager, don't! Download the PC36IMG.zip file from amon's thread and place it on the root of your SD card. Shutdown your device. While pressing the down arrow key, press the power button. You will then enter the bootloader screen. After a few seconds, a few lines of text will appear and the bootloader will automatically detect the. PC36IMG.zip file and prompt you to install it. Follow the prompts to install. The installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. The recovery version will be listed at the bottom of the screen. Go to the wipe menu and wipe EVERYTHING except the SD card itself then go to the flash menu and flash whatever rom you wish to flash.
Posting & replying via the XDA Premium app
awesomeindeed said:
My phone recently started doing this. Doesn't matter what ROM I'm on, doesn't matter if I un-root with a factory RUU or re-root, doesn't matter what recovery I use, doesn't matter if I completely format my SD card or boot without one. It got to the point I had to take it to Sprint and have them order me a new one.
It would randomly reboot and then go into a bootloop that not even a factory reset would cure, just decides when to stop bootlooping on its own and occasionally works.
Click to expand...
Click to collapse
Were you one of the unlucky ones who were using CM7 when the bootlooping began?
Posting & replying via the XDA Premium app
dougjamal said:
Were you one of the unlucky ones who were using CM7 when the bootlooping began?
Posting & replying via the XDA Premium app
Click to expand...
Click to collapse
No, I had already moved away from CM7 when it began. It started out of nowhere and just got worse on a daily basis.
I had also never used Unrevoked. I rooted with toast's original root method way back last August or so and was using the .76 ENG bootloader.
I had similar issues, in terms of both posts, and it got to the point that I just got it replaced from Sprint. It just progressively got worse no matter what was done. Has happened to others ... sounds like the phone might just be going.
=(
sent from my
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
awesomeindeed said:
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
Click to expand...
Click to collapse
Damn, that sucks. Is that stock, before u even rooted it? I would just take it right back to Sprint.
Sent from my PC36100 using XDA App
k2buckley said:
Damn, that sucks. Is that stock, before u even rooted it? I would just take it right back to Sprint.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yep, stock. Only apps installed are GoSMS and XDA. I guess I'll give it a factory reset and see if that fixes it, or else it's going back.
awesomeindeed said:
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
Click to expand...
Click to collapse
umm... might have been one of the 2 i got with that problem... srry!
i just hate unrooting, the whole process will end up taking a few hours. im probably gonna unroot, and if the basics work, i'll just stick with some simple z4 root and call it a day. any other options? cause htis is already my second phone, not exactly crazy about getting a third.
ryohei47 said:
i just hate unrooting, the whole process will end up taking a few hours. im probably gonna unroot, and if the basics work, i'll just stick with some simple z4 root and call it a day. any other options? cause htis is already my second phone, not exactly crazy about getting a third.
Click to expand...
Click to collapse
Unrooting take like 5 minutes...flash s-on tool, then the 5 minutes to run the ruu, then another 5 minutes to re-root.
ryohei47 said:
recently, my phone has just started a habit of randomly rebooting. i was using myn rls5 with net kernel 4.3.2, but i decided to try something different in an attempt to stop the problem, so i went to mikfroyo with its default kernel. right after i startthe phone and it gets to the homescreen, it starts restarting again. i cleared data and cache between roms, and im using clockworkmod 3.0.0.5
Click to expand...
Click to collapse
My phone never has random reboots. Never. And I have a list of roms as long as my arm that I have flashed.
HipKat said:
My phone never has random reboots. Never. And I have a list of roms as long as my arm that I have flashed.
Click to expand...
Click to collapse
There are a bunch of bad EVOs floating around. If you have this problem, you're more likely to get one of these as a refurb as they are the ones they get back. They'll replace the display, etc. But its the mobo that is probably the issue, and they don't replace that. They probably just make sure that it boots up and can make a call..
Sent from my PC36100 using Tapatalk

[Q] CyanogenMod 10 Nightlies for Hercules, won't boot.

Ok, so last night I got my phone totally back to stock. So today I decided that stock is boring lets try CM10! I followed all the instructions for my phone a SGH-989D to a tee. The phone boots up and displays the CM Circle logo and just sits there spinning away forever. It's quite pretty really, but the functionality seems to be a little lacking. Any idea how to get past this? I have pulled my battery and factory wipe/ deleted cache / wiped dalvik already. And yes, when I get home I can wipe back to total factory, but I would like to give CM10 a try if possible. Thank you for your time!
My first question would be how long are you waiting? First boot after a clean flash will take a long time. If you've waited more than an hour, then you might have a problem.
What recovery are you using? If cwm, try using darksidecachewipe zip before you reboot to system.
Sent from my cm_tenderloin using xda app-developers app
KaneHusky said:
My first question would be how long are you waiting? First boot after a clean flash will take a long time. If you've waited more than an hour, then you might have a problem.
Click to expand...
Click to collapse
Yeah I waited like 30 min ish, which is way longer than any other ROM i have used. I had all sorts of issues afterwards as well just getting it back to stock. I am now on ICS stock ROM for Telus atm, maybe I'll try the stable CM10 over Christmas break when my phone is not so important. Was annoying being at work all day and having it now work...lol

Undo ICS leaked firmware

Is there a way to undo the leaked ICS firmware I've flashed? I've been hit with the post viper CM10 lag that seems to be going around and I thought I'd try everything to get rid of it.
Have you tried chilly's super wipe? There is a thread for it.
Sent from my Incredible 2 using xda app-developers app
Same here. I super wiped two days ago and formatted my sd card. I thought I had it and my phone ran fine for a day. I charged it over night and when I took it off the charger, it was shot again today. When it actually boots, I can't get past the unlock screen. It holds there for about a minute before going into a boot loop. I didn't even think of the ics firmware. Maybe I'll try going back to stock tomorrow and then reflashing cm10.
Sent from my A500 using xda app-developers app
I don't know if it's the firmware or not, but I thought it was worth a shot. I have used chilly's wipe and I have gotten the huge lag since then. I'm running his PAC rom now and I used his wipe twice before I installed. I've also v6 supercharged so I'm waiting to see if it happens again. Is there a copy of the old firmware that is flashable like the new one?
Baloeb said:
I don't know if it's the firmware or not, but I thought it was worth a shot. I have used chilly's wipe and I have gotten the huge lag since then. I'm running his PAC rom now and I used his wipe twice before I installed. I've also v6 supercharged so I'm waiting to see if it happens again. Is there a copy of the old firmware that is flashable like the new one?
Click to expand...
Click to collapse
There at threads for different ruu's. I'm not sure which one you need. Search through those. Also, when your phone starts lagging try connecting to a computer in adb I think, someone posted that that fixed theirs temporarily. I think they narrowed it down to the SD card being bad and with it connected it dismounts the SD card and doesn't have the problem. That might help.
Sent from my Incredible 2 using xda app-developers app
NeverSeparate said:
There at threads for different ruu's. I'm not sure which one you need. Search through those. Also, when your phone starts lagging try connecting to a computer in adb I think, someone posted that that fixed theirs temporarily. I think they narrowed it down to the SD card being bad and with it connected it dismounts the SD card and doesn't have the problem. That might help.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I'll give that a shot next time. Usually I just pull the battery and install cm7 so I have a working phone.
Okay, 1st you need to return to stock:
http://forum.xda-developers.com/showthread.php?t=1599767
After this process you need to flash cwm and superuser:
I believe this thread http://forum.xda-developers.com/showthread.php?t=1751796 has all the files (including adb) set up in one .zip under "TACOROOT"
Or just download them from here:
https://dl.dropbox.com/u/77740451/recovery-clockwork-5.0.2.0-vivow.img
https://dl.dropbox.com/u/77740451/Superuser-3.0.7-efgh-signed.zip
This is what I did to remove the firmware. I didn't have the lag, but I was hoping to solve camera issues.
SkinnyT said:
Same here. I super wiped two days ago and formatted my sd card. I thought I had it and my phone ran fine for a day. I charged it over night and when I took it off the charger, it was shot again today. When it actually boots, I can't get past the unlock screen. It holds there for about a minute before going into a boot loop. I didn't even think of the ics firmware. Maybe I'll try going back to stock tomorrow and then reflashing cm10.
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
Just a quick note...When I was running CM10 I would get the boot loops at the lock screen, but if I just let it alone, it would loop 2-3 times and then settle in. It took a while, and I avoided rebooting my phone at all costs, but have you just let it sit for about 10 minutes to see if it pulls out of the boot loop? Mine usually came out in less than 5, but you never know. After it booted up it settled down and ran fine. I've never used the Venom rom or super wipe though, so ymmv.
gtdtm said:
Just a quick note...When I was running CM10 I would get the boot loops at the lock screen, but if I just let it alone, it would loop 2-3 times and then settle in. It took a while, and I avoided rebooting my phone at all costs, but have you just let it sit for about 10 minutes to see if it pulls out of the boot loop? Mine usually came out in less than 5, but you never know. After it booted up it settled down and ran fine. I've never used the Venom rom or super wipe though, so ymmv.
Click to expand...
Click to collapse
Mine doesn't boot loop, it runs great for a few days then starts to lag so bad it's unusable.
Baloeb said:
Mine doesn't boot loop, it runs great for a few days then starts to lag so bad it's unusable.
Click to expand...
Click to collapse
Some have reported that it's linked to a usb / sdcard / storage issue. Lag starts after connecting.
Sent from PAC-land

[Q] Help with constant rebooting

Have the ATT version. Over the last 2 weeks no matter what I do my phone will not hold onto a ROM. Have done restores, complete wipes and new
installs yet nothing seems to hold. Will do a complete wipe including internal, data, system, etc.. Have tried all different ROMs. From international, to I317. Have tried TW, AOSP, and MIUI. Sometimes can get through setup, but within 1/2 hour reboot into loop. Thought it might be the battery, not sure though. Any help would be greatly appreciated. Maybe Odin back to stock? Thanks for taking the time to read this.
Update
mdaigt said:
Have the ATT version. Over the last 2 weeks no matter what I do my phone will not hold onto a ROM. Have done restores, complete wipes and new
installs yet nothing seems to hold. Will do a complete wipe including internal, data, system, etc.. Have tried all different ROMs. From international, to I317. Have tried TW, AOSP, and MIUI. Sometimes can get through setup, but within 1/2 hour reboot into loop. Thought it might be the battery, not sure though. Any help would be greatly appreciated. Maybe Odin back to stock? Thanks for taking the time to read this.
Click to expand...
Click to collapse
Update. I tried Odin back to stock. Was able to update to latest firmware in between reboots. Didn't help. Still constantly reboots randomnly.
Again thanks for taking the time to read.
mdaigt said:
Update. I tried Odin back to stock. Was able to update to latest firmware in between reboots. Didn't help. Still constantly reboots randomnly.
Again thanks for taking the time to read.
Click to expand...
Click to collapse
Search this forum [General or Q&A] for "stuck power button". I recall seeing a few threads about a yr ago with constant rebooting issues.... turned out, by cleaning the power contacts it fixed issue for some folks. Good luck.
I agree with the good doctor...
The behavior of the device suggests a forced reboot via the power button...
The other prospect is not quite so simple...and involves hardware damage....but I would certainly pop the case open and clean those contacts first....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Well was lucky to solve my issue. It was the battery being bad. Have had the new battery in for a day now and no
problems what so ever. Thanks for everything. Love reading and learning from XDA:good:

Categories

Resources