After I've been installing ROM's, the boot time on my fascinate has been very slow 1-2 mins just to boot before showing unlock screen. I recently installed adrynalyne's DL30 .8 Froyo which has made my boot even slower. I have tried installing boot animations before with little success. Is there a reason my initial boot is this slow? Is there a way to clean the boot files/settings to make it faster? The current boot animation in DL30 .8 is the galaxy S logo without Verizon and it works every time, just stuck on that screen for 2+ minutes before the unlock screen shows.
Edit:
So I took my SD card out and the phone shut down and booted up really fast. All my apps are stored on my phone haven't moved to SD. My phone also shuts down really slowly when the SD card is inserted. Anyone have reasoning for this?
Most likely a combination of the Media Scanner and the fact that Samsung's RFS file system is SLOW! Once we have Voodoo again things should get way better.
[Also, this belongs in General as it is NOT development]
Martian21
Anytime you flash a new ROM, theme, etc. the next boot up will always take longer
Related
So I was recently experimenting with the I9000xxJP3 and JP2 roms, and things took a turn for the worse. JP3 installed but would only boot into recovery mode and JP2 wouldn't even flash at all. I finally flashed the True 2.1 from the master list and after an hour with titanium it appears I have everything back. My concern is that when I boot up now it shows the GT I9000 then quickly changes to Vibrant as normal. Is this a bad sign? If no, is there a way to remove just that portion as you can remove the boot down sequence?
Sent from my Vibrant
Hi guys
So I installed Nero v3 on my Vibrant, and all is well. I followed the steps on the Nero thread. I like it very much.
Then I decided to flash my gf's phone. It seemed to go well at first, but then some odd stuff started happening. First, I can't open the "Settings" menu - nothing happens. Second, lots of stuff force-closes all the time.
Those two are minor issues, though. Somewhere between 5-15 minutes after flashing, the entire GUI will force close. The phone will vibrate, then the Team Whisky logo will appear again (as if rebooting), and the GUI will appear and begin the regular startup procedure. It will get as far as "Preparing internal SD card" before the GUI will crash again. This cycle continues indefinitely. Once it has begun, not even pulling the battery and rebooting it will solve the problem.
Any advice?
My plan is to find a way to back up the SD card data and format it, since it always crashes on "Preparing internal SD card." However, I doubt this will help, since the other issues (constant force-closes) don't seem to have anything to do with that.
stoanhart said:
Hi guys
So I installed Nero v3 on my Vibrant, and all is well. I followed the steps on the Nero thread. I like it very much.
Then I decided to flash my gf's phone. It seemed to go well at first, but then some odd stuff started happening. First, I can't open the "Settings" menu - nothing happens. Second, lots of stuff force-closes all the time.
Those two are minor issues, though. Somewhere between 5-15 minutes after flashing, the entire GUI will force close. The phone will vibrate, then the Team Whisky logo will appear again (as if rebooting), and the GUI will appear and begin the regular startup procedure. It will get as far as "Preparing internal SD card" before the GUI will crash again. This cycle continues indefinitely. Once it has begun, not even pulling the battery and rebooting it will solve the problem.
Any advice?
My plan is to find a way to back up the SD card data and format it, since it always crashes on "Preparing internal SD card." However, I doubt this will help, since the other issues (constant force-closes) don't seem to have anything to do with that.
Click to expand...
Click to collapse
Was her phone stock before you started tinkering with it?
In any case I'd suggest re-download nerov3 (to avoid corrupted download issue), ODIN back to JFD (remove the ghosts from the past ROM's) and reflash.
Phone was stock aside from rooting for the purpose of TitaniumBackup. It has never had anything installed on it.
I'm currently Odin flashing back to stock, and I'll give it another shot.
stoanhart said:
Phone was stock aside from rooting for the purpose of TitaniumBackup. It has never had anything installed on it.
I'm currently Odin flashing back to stock, and I'll give it another shot.
Click to expand...
Click to collapse
Good luck!
Well, I did the Odin flash to stock, then installed Nero. After first boot, I left it untouched for 20 minutes or so, and then did a clean reboot. Upon starting up, I was once again stuck in the loop.
Boo
stoanhart said:
Well, I did the Odin flash to stock, then installed Nero. After first boot, I left it untouched for 20 minutes or so, and then did a clean reboot. Upon starting up, I was once again stuck in the loop.
Boo
Click to expand...
Click to collapse
Did you re-download nero? It might be a corrupted download, I haven't seen anyone with the same symptoms.
Does it happen if Voodoo is disabled?
EDIT: Saw that you didn't even have a chance to enable it, hmm, try a different ROM? Axura or Eugene's work.
No, I didn't try re-downloading it. Perhaps I'll give that a try, although it is the same file I flashed onto my phone.
After a bit of time playing with Nero, though, I'm considering going back. The parts that work are slick and wonderful, but it very much feels like beta software. In particular, scrolling lists or web pages is choppy. I've heard this criticism of Android before, but I've never experienced it with the original Vibrant software. It was always so smooth. It makes me think that maybe Samsung was using GPU acceleration in some places. Also, I seem to have some problems with the touchscreen becoming unresponsive, especially in the browser if it's blocked waiting for data (another bug...).
Is it possible to run the JL5 modem on the stock image? That would be great.
So I recently purchased my AT&T Galaxy S4 with MDL baseband. I rooted and installed TWRP via motochopper. I then loaded Kangabean 4.2.2 and everything was great. Got notification for OTA update to 4.3 and decided might as well load Kangabean 4.3 as opposed to dealing with the OTA notification. I did so (after formatting internal SD and performing factory reset) and now my phone won't boot beyond the Galaxy S4 splash screen. I restored a nandroid backup of the original software and was able to boot the phone once, but couldn't load the custom rom again, nor can i load into the stock rom anymore either. Does it sound like my phone may have a hardware failure? Would attempting to restore through odin be the next logical step? I'm by no means an expert with these sort of things but my S2 has never given me any sort of grief when flashing various roms in the past. Any advice would be greatly appreciated. Thanks in advance!
Try a different kernel, also, pull the battery for 5 min, it will boot.
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
Yeah I left the phone off with the battery removed all night - didn't want to boot this morning. I'm also noticing an oddity with TWRP - it's for some reason asking for a password on startup even though I've never set one. It also gives an error when attempting to wipe the phone or re-flash
id try odin
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
jd1639 said:
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
Click to expand...
Click to collapse
It will not let you past the password, been there, it will only do simulated flashes.
Odin is his only option.
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Squidbert said:
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Click to expand...
Click to collapse
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
//
Squidbert said:
.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
Click to expand...
Click to collapse
If you're on the stock AT&T rom and you're getting stuck on the AT&T boot logo try the following:
Power off your phone and hold down Volume Up, Center Home, and Power buttons together.
Once you see the Galaxy S4 splash - Keep holding down Volume Up and Center Home buttons but let go of Power button.
Choose the wipe datafactory reset. This will wipe your phone completely but it should boot after.
Hope that helps.
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Squidbert said:
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Click to expand...
Click to collapse
TWRP does not now and has never added LOKI to any ROM or Kernel. Only OUDHS CWM auto-LOKIs. You have to use A pre-LOKIed Kernel or flash the LOKI DokI script to LOKI anything with TWRP. You can do a search to find the LOKI DOKI script and how to use it.
fatah
hi my phone is galaxy s4 at&t i337 rooted but not installed recovery the phone was working good suddenly i deleted at&t software updater after that the phone rebooted it's self and then stuck in at&t boot logo won't bootup please help
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
galaxy s4 i337 stuck on at&t bootAnimation
i tried everything but still same please help my phone is not booting up
fatahmusse said:
i tried everything but still same please help my phone is not booting up
Click to expand...
Click to collapse
Flash the stock firmware.
samsung galaxy s4 i337
thank you i flashed to mf3 everything is ok
fatahmusse said:
thank you i flashed to mf3 everything is ok
Click to expand...
Click to collapse
Glad to hear
Short and sweet. I haven't used SetCPU for awhile and I've been using the ROM in my sig, which isn't entirely stable. Though I went to set the CPU to max 1890Mhz just before I went to use Titanium Backup to do a huge compressed backup. So it makes it a little faster. I accidentally (honest accident) swiped to the end of the list on available CPU frequencies.. I think the highest was like 2334 or something.. well the phone crashed at something like 2035. I rebooted it and it booted up fine, but there had been some noticeable changes. Some apps I had frozen had been unfrozen, some apps had lost their settings etc. I figured this was due to a bad shut down.
Today I was asleep and I left my phone like usual so the alarm would ring. When I woke up I dismissed the alarm and the phone hung for a good 20 seconds. Then 3 apps updated and the phone crashed whilst browsing the play store.
Now when I tried to boot I got that typical vibration that something had got unresponsive in the background and was crashing. (Whilst at boot logo) It was just doing a loop of that. Then I rebooted it myself again and now it does nothing. But it still was stuck at the logo forever.
So I went into PhilZ recovery and wiped everything. Dalvik, Cache and Wipe to Install a New ROM.
Now it won't even GET to the Booting Logo and just stays on the 'Samsung Galaxy S4 Gt-I9505' screen..
So gradually my phone is retreating into an even worse position.
Is there a chance I could have blown my CPU or something with overclocking by accident for a few seconds?
Nope, you shouldn't have blown a cpu, since it was working afterwards. Seems more like hangs due to some bad wipe.
What you can do is try to install any rom and make a full wipe. If that doesn't work apply a new kernel.
If that doesn't work. Try install stock samsung rom (no wipe)
If it's still in boot loop (do full wipe) however if you got any saved data do the last step if you're sure nothing else works.
[I'm helping to tell developers how they can protect their app from being pirated and how they can protect it, in that way you can consider to not worry about your app being patched. too many developers have a bad protection.]
I didn't set it to 'Apply on Boot' because it was only meant to be a temporary overclock.
I just took the MicroSD out now and I am going to put the latest release of the ROM I am using on it, flash it and see if it works and flash the modem too to try and get some more stability out of it. I'll see how that goes, if it doesn't get off the 'Galaxy S 4' screen I am going to have to assume there's a big problem...
Well then there can be something else, if you haven't sent it to apply at boot it can be some kernel issue or something got stuck. It seems like there's something that blocks you from booting the phone up. Interesting,
[I'm helping to tell developers how they can protect their app from being pirated and how they can protect it, in that way you can consider to not worry about your app being patched. too many developers have a bad protection.]
boot into recovery.. wipe /system, /data and /cache then install rom from external sd card
At times the metro boot logo freezes on start up, and also every ten seconds will vibrate five times. Not stuck on the software boot though. restoring to stock firmware does nothing, removed boot animation but still vibrated at black screen. the reason I would want it fixed is I cant install an app that requires reboot every time its stuck. then the only way to repair is to use odin. any help is greatly appreciated.
Capitah Knight said:
At times the metro boot logo freezes on start up, and also every ten seconds will vibrate five times. Not stuck on the software boot though. restoring to stock firmware does nothing, removed boot animation but still vibrated at black screen. the reason I would want it fixed is I cant install an app that requires reboot every time its stuck. then the only way to repair is to use odin. any help is greatly appreciated.
Click to expand...
Click to collapse
You can always try SlimPickins Rom. It's a lighter, faster, version of the stock firmware and, as such, runs smoother.
http://forum.xda-developers.com/showthread.php?p=63868639
If you have tons of apps or if you're using a bunch of Xposed modules on this device though, then it may hang on the boot screen from time to time anyway, causing you to have to pop the battery and try booting again and again until it eventually starts up. Whenever this happens I usually backup all my data in TWRP, then do a standard wipe of the device, reflash SlimPickins clean and then restore my data. If you have a lot of apps though, it may be even better on this device to just back them up in Titanium Backup and restore them one by one as you need them, so as not to bog the device right back down again.
It shouldn't be vibrating on boot though. That usually indicates a deeper problem in the system or with one of the partitions, which is generally fixed by flashing the stock firmware, but I recommend just trying SlimPickins and making sure your apps aren't taking up too much space or using up too much memory. One thing I did was delete the standard Facebook app and went with a 3rd party one called "Swipe", which pretty much looks the same, but is 300mbs less in size and takes up a lot less memory. I also dialed back my Xposed mods to just the essentials and I haven't really had a problem since.