It says this and gets stuck there after its done optimizing. Any ideas? If I reboot it just goes into a bootloop. If I clear the cache, it starts the whole upgrading process over again.
What version did you flash? Did you try a full wipe? Are you flashing a kernel with it?
Sometimes it takes a while before it starts up like a few minutes. How long have you tried waiting?
Sent from my Nexus 7 using XDA Premium HD app
Try clearing cashes (davlik included) from recovery.
Edit: I didn't read the full OP before responding. My bad. Did you try to do a full reflash? Preferably a clean one?
Sent from my Droid DNA running Rootbox
Try to back to stock ROM and then try to flash another ROM and see if this thing will happen again or not.
Yes. It said it was compatible with CRPALMER but thats what my issue was. Used boot.img provided with .zip. Worked fine. Other than that, this rom seems really sluggish.
rickylm said:
Yes. It said it was compatible with CRPALMER but thats what my issue was. Used boot.img provided with .zip. Worked fine. Other than that, this rom seems really sluggish.
Click to expand...
Click to collapse
give it some time to settle in, I have no lag/stutters after it set in (after all apps/data were installed/restored)
.torrented said:
give it some time to settle in, I have no lag/stutters after it set in (after all apps/data were installed/restored)
Click to expand...
Click to collapse
Full wipe, still nothing.
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
edit: See my post here for details on what I've found so far, I may have fixed the problem but needs more testing http://forum.xda-developers.com/showthread.php?t=2397438&page=2
TWRP!!!!
SellswordShev said:
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
Click to expand...
Click to collapse
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
thepianoman77 said:
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
Click to expand...
Click to collapse
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
SellswordShev said:
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
Click to expand...
Click to collapse
oh dude.... I was on v2.6... I think we have an issue.
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
i had a very bad experience with CWM... never using it again man.... no way.
thepianoman77 said:
i had a very bad experience with CWM... never using it again man.... no way.
Click to expand...
Click to collapse
Lol ok :thumbup:
Sent from my SCH-I545 using Tapatalk 2
I've been using TWRP too. I panicked last night when I couldn't boot at all. I couldn't even get to recovery. I then tried the no wipe odin without luck. I finally got the stock odin image to work but I've been having serious issues with booting on this phone since I got it this weekend and it could be TWRP I suppose. I was using it on my note 2 with no issues. Very strange. I'm back to stock and running fine now.
Sent from my SCH-I545 using xda premium
Still having odd issues with TWRP after updating to 2.6, getting stuck on boot as before, and sometimes flashing a ROM will just fail and the data partition becomes read only, and I can't push anything to it till I reformat /data.
Going to try CWM today, really hope this is just a recovery issue. Are there any tests to check the health of on board memory? I am really hoping I don't have bad hardware here.
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
ruffneckZeVo said:
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Root / recovery methods will be the same for everyone, regardless of what guide / thread you followed, in the end you will have a loki-patched recovery and kernel, as thats the only way to run unsigned images on these phones. Whats relevant here is which recovery and kernel you are using, as these are the only 2 things that could effect errors in the boot logo state (aka freezes before the ROM boot animations kick in). Ive been looking through various ROM threads of people reporting this issue and its pretty widespread, and usually is linked to recoveries rather than ROMs. If you can post your recovery + ROM here that would be helpful. Here is what I've done so far:
I was initially on TWRP 2.5.0.2, which had possible bugs that could corrupt /data, leading to failed flashes, and being unable to read/write from /data entirely (including /sdcard). After switching to 2.6.0.0 I was still getting stuck on the boot animation. (All of this running the CM10.2 ROM with the stock kernel here http://forum.xda-developers.com/showthread.php?t=2384470). Note I did not do a full wipe after switching to 2.6.0.0, so that recovery MAY still be ok if someone wants to test it out.
I am now running CWM (official installed off ROM Manager). After flashing this I did a full re-format (/system, /data (including /data/media), etc.). And so far I haven't had any problems, going to do some more fiddling / flashing tonight to try and see if its really fixed, but I know for sure that atleast the reboot bug is gone.
So my advice is to flash the official CWM recovery, do a full re-format using that recovery, and then re-install your ROM.
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Monkz said:
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Click to expand...
Click to collapse
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
SellswordShev said:
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
Click to expand...
Click to collapse
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Monkz said:
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Click to expand...
Click to collapse
is PhilZ a recovery?
thepianoman77 said:
is PhilZ a recovery?
Click to expand...
Click to collapse
Yes its a custom build of CWM maintained by an xda dev here http://forum.xda-developers.com/showthread.php?t=2322675
Im still having the issue with philz. Everything was fine for the first 4-5 weeks. Now about every 3rd reboot or if battery dies I have to wipe data and nandroid. Im running stock with several tweaks. Going to try and odin restore to stock re root snd install cwm tonight and see if that helps will report back
Sent from my SCH-I545 using xda premium
Alright, I'm almost 99% sure this problem is gone after I switched to the official CWM. I've tried everything from restoring nandroids to flashing TWiz / AOSP 4.2 and 4.3 ROMs, everything boots and reboots and /data is no longer getting corrupt. I also loki patched the official CWM touch recovery (the one on their site is not patched), and flashed + used it successfully. Its pretty simple to do this, just follow the guide here: https://github.com/djrbliss/loki and use this recovery: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.2-jfltevzw.img
The only issue I've been having is that when I reboot to recovery, it sometimes gets stuck and I have to do a battery pull and go back into recovery.
Sent from my SCH-I545 using Tapatalk 4
I'm having the same issue on TWRP 2.6. Tried with multiple ROMs. Everytime I reboot I have to format /Data. So frustrating. I will try CWM now.
So the problem started when I flashed a 4.3 rom last friday. I formatted my internal memory in recovery mode because for some reason I only had 4 gigs of space and had moved everything over to the sd card. Once that was done phone said like 8 gigs available and thought everything was fixed. Well now if I turn off my phone it gets stuck in some kind of bootloop but it's not looping. It's just sits at the Samsung unlock symbol and custom screen. Doesn't loop just sits there. So one day I decided to format the internal memory again and the phone boots up like normal, but I can't power off the phone without going into recovery and formatting the internal memory every time. Any ideas on what is causing it or how I can make the Samsung custom boot stock instead so I can send it out.
I also have tried flashing another 4.3 rom and it doesn't seem to go away either.
I'm not an expert on how they have to make this stuff work with the mdk bootloader but I'm sure it's not hardware related. Have you tried flashing back to a 4.2 rom?
Sent from my SCH-I545 using Tapatalk 2
Downloading one now hopefully it will fix it.
Which recovery are you using? Make sure to wipe data, cache, and dalvik 3x each, then flash your rom
Sent from my SCH-I545 using Tapatalk 2
TWRP and I flashed hyperdrive still no luck still freezing in the same spot and have to actually format to get past it.
Anyone else have any idea on what else I can try?
BlackDynomitr said:
Anyone else have any idea on what else I can try?
Click to expand...
Click to collapse
What version of TWRP are you using?
Sent from my SCH-I545 using Tapatalk
I believe 2.5 I'm guessing only way to check is to go into recovery again.
BlackDynomitr said:
I believe 2.5 I'm guessing only way to check is to go into recovery again.
Click to expand...
Click to collapse
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
heath2805 said:
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
BlackDynomitr said:
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
Click to expand...
Click to collapse
Well if it doesn't turn on after flashing stock firmware via Odin, you'll know its a hardware issue with it and your warranty should cover a new replacement.
Sent from my SCH-I545 using Tapatalk
I had this issue when I first got my phone. I bought it off Swappa, it was already running TWRP 2.5.0.2, giving me nothing but problems. I switch to Philz Touch and no longer have the issue.
I am wondering if anyone can help. I installed a new rom and the data partition is showing 9.31GB /9.59GB used. I haven't loaded any additional apps since I started with this rom though, so I don't know what is using the data. Because of this, I can't install new apps.
When I loaded the rom, it shows 9GB free, but then after restarting for the first time, it uses up all 9GB. I've tried wiping and formatting the data in twrp, but it still has the issue.
I'm currently using PAC rom but I also had the same issue with Omni, Slimkat, and liquid smooth.
Any ideas?!!
You really don't need to start a second thread...
sent by baja kitkat S4
decaturbob said:
You really don't need to start a second thread...
sent by baja kitkat S4
Click to expand...
Click to collapse
Thanks for your help
Fitz1883 said:
I am wondering if anyone can help. I installed a new rom and the data partition is showing 9.31GB /9.59GB used. I haven't loaded any additional apps since I started with this rom though, so I don't know what is using the data. Because of this, I can't install new apps.
When I loaded the rom, it shows 9GB free, but then after restarting for the first time, it uses up all 9GB. I've tried wiping and formatting the data in twrp, but it still has the issue.
I'm currently using PAC rom but I also had the same issue with Omni, Slimkat, and liquid smooth.
Any ideas?!!
Click to expand...
Click to collapse
I'd say it's time to just wipe the phone using Odin and start over since you've had that issue across a few ROMs
Sent from my SCH-I545 using Tapatalk
And no matter how many times I do a system or full wipe when my phone finally boots it goes into the android is upgrading screen. It hasn't done this before and It just started doing this about a week ago and I can't make it stop. Anyone have any idea what may be going on?
Sent from my LG-VS985 using XDA Free mobile app
syde1020 said:
And no matter how many times I do a system or full wipe when my phone finally boots it goes into the android is upgrading screen. It hasn't done this before and It just started doing this about a week ago and I can't make it stop. Anyone have any idea what may be going on?
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
It does this at every reboot even after the first boot? How many apps optimize? It eventually does boot, correct? If it eventually boots, take a logcat right after bootup and post.
hawkswind1 said:
It does this at every reboot even after the first boot? How many apps optimize? It eventually does boot, correct? If it eventually boots, take a logcat right after bootup and post.
Click to expand...
Click to collapse
It only does it after I install a new ROM. Just the first boot. I'm doing a full wipe several times and then installing the ROM and gapps and as soon as the ROM boots it shows the android is upgrading, counts up the number of apps then goes into the setup wizard. All previous apps and data are gone but I can't figure or went it's showing me the upgrading message after every new ROM install.
Sent from my LG-VS985 using XDA Free mobile app
syde1020 said:
It only does it after I install a new ROM. Just the first boot. I'm doing a full wipe several times and then installing the ROM and gapps and as soon as the ROM boots it shows the android is upgrading, counts up the number of apps then goes into the setup wizard. All previous apps and data are gone but I can't figure or went it's showing me the upgrading message after every new ROM install.
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
This is normal whenever you install a new ROM. You're doing a full wipe. This is nothing new or strange. Basically, you've wiped the phone and it has to recompile all the apps (whether it's Dalvik or ART). It only occurs on the initial boot after flashing to a new ROM when you do a full wipe.