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.
Related
Has anyone else had a boot loop problem with the new V of TWRP?? I'm running SOAv3 ROM and had ZERO problems, upgraded my twrp and had about a dozen restarts and freezes and then when I tried to boot into recovery, it boot looped. Fixed it with ODIN, then tried installing it fresh, and got the same thing. Went back to my older version and things are fine once again just wondered if this is isolated or just a known bug??
Yes its a know issue right now go back to the previous working version of twrp and wait for it to get fixed.Also be sure to check big Biff's twrp page before trying to update again to make sure everything is good.
Sent from my SGH-I717 using xda premium
Just update from Padawan V8 to SOA build 3. Was skeptical for a day or so but finally did it last night. Was just about to update to the New TWRP, thank fully I read through all those pages before I did, I usually don't. Saved me a head ache except I forgot to wipe cache's before installing the GAPPS, going to have to re-do that I believe to get the new camera functions from what I've read.
Demmonnixx said:
Just update from Padawan V8 to SOA build 3. Was skeptical for a day or so but finally did it last night. Was just about to update to the New TWRP, thank fully I read through all those pages before I did, I usually don't. Saved me a head ache except I forgot to wipe cache's before installing the GAPPS, going to have to re-do that I believe to get the new camera functions from what I've read.
Click to expand...
Click to collapse
you are correct Sir.....wipe caches and re-flash gapps.....g
psycoartwork said:
Has anyone else had a boot loop problem with the new V of TWRP?? I'm running SOAv3 ROM and had ZERO problems, upgraded my twrp and had about a dozen restarts and freezes and then when I tried to boot into recovery, it boot looped. Fixed it with ODIN, then tried installing it fresh, and got the same thing. Went back to my older version and things are fine once again just wondered if this is isolated or just a known bug??
Click to expand...
Click to collapse
How did you fix with odin? I can't get mine into the download mode to connect to odin. it just keeps boot looping?
whitebrw said:
How did you fix with odin? I can't get mine into the download mode to connect to odin. it just keeps boot looping?
Click to expand...
Click to collapse
Hold volume down and power ...it will go into download mode
Sent from my SGH-I717 using xda app-developers app
thanks but no thanks, when i do that it does the same thing as any other way of starting, just loops.
check out my post if you want.
http://forum.xda-developers.com/showthread.php?t=2202663
And the all have the same green leaf for a home screen, so are my ROMS not being written to the right place or what. this is getting confusing. the ROM form about shows the different versions but all are skipping the setup and I have no 3G/LTE connection, only wifi.
Whatever I am doing I seem to be consistent about it
Did you flash gapps?
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
Did you flash gapps?
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
the AOPK had gapps folded in. what is odd is I have now tried AOPK and a CM10 and CM10.1 and they all seem to have the same start screen, come up after the boot like it is already installed, missing any 3G/4G connection. Now I have flashed back to EG01 and run up though iCS several times and it isn't taking the CWM now, says it installs ok but boots into stock recovery. Now I using the older CWM 5504 for the i-905 and it writes somewhere, but apparently not where it should be. I was going to try TWRP but that doens't appear to run on HC/ICS - is it JB only? I have shied away from the newer CWM for a long time because for a while they just seemed to boot-loop the tablet.
Any one have a suggested working version of CWM? This starting from scratch and rolling in all the updates is getting old - which is why I was wondering if there is a way to build my own ODIN set to just flash back to this point without having to go though reroot and install of the recovery (which apparently now I am not able to do - wts! )
Thanks!
Rob (lost) in Katy.
Twrp is compatible with ICS too, if im not mistaken. Go to www.droidbasement.com and download pershoots's version of cwm recovery. That should work just fine. BTW, you did make a full wipe (system, data, cache, dalvik) right? And what's EG01?
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
Twrp is compatible with ICS too, if im not mistaken. Go to www.droidbasement.com and download pershoots's version of cwm recovery. That should work just fine. BTW, you did make a full wipe (system, data, cache, dalvik) right? And what's EG01?
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
I am now one cycle 15 and doing the last update to 4.04. every stinking rom I load goes back to the factory or the ROM starts off and ignores the setup. The really annoying thing is I have had all this setup and working before. Ahhhhhh!
rgranger said:
I am now one cycle 15 and doing the last update to 4.04. every stinking rom I load goes back to the factory or the ROM starts off and ignores the setup. The really annoying thing is I have had all this setup and working before. Ahhhhhh!
Click to expand...
Click to collapse
Ok, i found another recovery laying around that seems to be working. I also found that the bug where you need to delete the script that deletes the new recovery. Once I got that far things started making sense. I guess whatever mod I was on before didn't need it. The next trick will be trynig to decifer how to do an odin backup so that I don't haver to roll though 4/5 upgrades to get here. I know someone is doing it. thanks for the help and a place to bounce ideas. will update if i come up with anything.
Rob
The other day, for reasons I'm not entirely clear on, after trying to reboot my phone, I found it unable to boot (just stuck at the last boot animation). I went ahead and decided to wipe and tried to flash a custom ROM (started with Beans, also tried Hyperdrive), but for both ROMs, I wind up in a bootloop after installation. Generally it will get to the very first screen, language selection, then simply reboot after a few seconds. This just happens continually. Only got things working again by using Odin to get back to the stock MDK release.
Trying to flash coming from build number JDQ39.1545VRUAMDK. Appreciate any suggestions. Thanks
Tried again with flashing a factory stock, rooted rom from recovery after full wipe/reset. It wouldn't boot. When I recover a backup I've previously made, it will boot up once just fine, then when I reboot, it just sits at the "Samsung" "Custom" screen with a lock on it.
Would really appreciate some help. Thanks
Same here, I tried to flash Illusion, and now my phone is stuck at the Samsung Custom lock screen...
make sure you are wiping everything (i do dalvik, data, system, cache, and factory reset) 3x for a complete clean install, then flash.
a.demarco said:
make sure you are wiping everything (i do dalvik, data, system, cache, and factory reset) 3x for a complete clean install, then flash.
Click to expand...
Click to collapse
thanks for the reply. I've definitely been trying that, but to no avail.
Are you using cwm or twrp?
SCH-I545 using Tapatalk 2
hexitnow said:
Are you using cwm or twrp?
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Twrp 2.6
You might want to try cwm there has been a few posts with people and a similar situation. Twrp wipes differently then cwm and thats what causes it.
SCH-I545 using Tapatalk 2
hexitnow said:
You might want to try cwm there has been a few posts with people and a similar situation. Twrp wipes differently then cwm and thats what causes it.
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
THanks for the advice. Hopefully will have time today to give this a try. If not, this weekend. Will post back with results. Thanks again.
TWRP 2.5 works perfectly for me...
Solved! Went through another reinstall of hyperdrive, this time I only checked one or two options. Now I'm running smoothly with no issues.
Every time my phone dies, or I turn it off or I reboot, no matter what 4.3 rom I'm using, it stays on the boot animation until I either pull battery or hold power to turn off. I've flashed, reflashed, dirty flashed clean flashed (I format the system as well) I've tried CM10.2, PacMan, and Beanstalk and all three have this issue. I haven't read anywhere that someone else is having problems like this. Please advise!:fingers-crossed:
Aiekazie said:
Every time my phone dies, or I turn it off or I reboot, no matter what 4.3 rom I'm using, it stays on the boot animation until I either pull battery or hold power to turn off. I've flashed, reflashed, dirty flashed clean flashed (I format the system as well) I've tried CM10.2, PacMan, and Beanstalk and all three have this issue. I haven't read anywhere that someone else is having problems like this. Please advise!:fingers-crossed:
Click to expand...
Click to collapse
I have the same problem. Can't seem to figure it out either. The only way to fix it is to reflash. At first I thought it was an app or setting but after a clean install and boot I reboot without going through the setup but it still would not reboot.
Same
I'm having the exact same issue and as you have, I've tried everything I can think of.
Ive tried flashing CM 10.2 + GAPPS, just CM10.2, 3 different types of Google Edition Roms and in every case the initial boot is fine... It boots and works perfectly, however on first reboot, it wont boot back up.
It just sits on the SGS4 logo, have left it for 25 minutes.
I would really love to know how to fix this. The only way to get it working after it has been restarted once is to delete cache, dalvik AND data...
Cache and Dalvik don't fix it.
figured a little bit...
Well now that I've flashed it using TWRP instead if CWM touch, it does reboot back up. However with TWRP flashing I'm getting reboots while typing.
Aiekazie said:
Well now that I've flashed it using TWRP instead if CWM touch, it does reboot back up. However with TWRP flashing I'm getting reboots while typing.
Click to expand...
Click to collapse
I used Goo manager to install TWRP. Then used that to install the latest nightlies and latest gapps - 0813. So far so good!!
anandlal said:
I used Goo manager to install TWRP. Then used that to install the latest nightlies and latest gapps - 0813. So far so good!!
Click to expand...
Click to collapse
Gonna give this a try I'll post back.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Aiekazie said:
Gonna give this a try I'll post back.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Click to expand...
Click to collapse
If this works can you post a quick overview of what you did...
Because I've tried reinstalling TWRP and it didnt seem to help, but happy to try again if it works for you!
All is good!
Been running it since I installed using the method i mentioned above.
The ROM is running smoothly with no issues or reboots. I did reboot it a couple times to verify that it is booting properly.
Alright...I installed TWRP through Goomanager, when I did this I selected the manual option and booted into CWM and performed a BACK UP first...flashed the TWRP.zip file that goo downloaded for me. Version 2.6.0.1 I think it was? I rebooted into recovery and found it successfully flashed TWRP, I went into the wipe options and chose data cache system and dalvik, backed out and chose install and reinstalled Cm10.2 and GApps. I'm able to reboot and all but I'm still finding reboots here and there....I was able to go 18hrs on battery (awesome for stock settings!) And without a single reboot.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Yup that's the same for me. Random reboots here and there but overall very solid with great battery life.
Can't wait for more nightlies.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Ya know. Now that I've let 8.14.2013 nightly settle in I havent had a reboot in quite some time. I might stick here til some major change logs come..
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Try This Rom
[Rom][JellyBean][4.3][BeanStalk Build 4.3.05][updated 8.19]
I have Flashed it with no issues :fingers-crossed:
hope this will help you
Yeah, I posted in the dev thread, that particular one gives me reboots while typing if the vibrate on key press is on. Other than that it was working fine. I'm still digging the cm 14th nightly.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Aiekazie said:
Yeah, I posted in the dev thread, that particular one gives me reboots while typing if the vibrate on key press is on. Other than that it was working fine. I'm still digging the cm 14th nightly.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Click to expand...
Click to collapse
Yup same with me. Kinda surprised that there have been no more Nightlies for this though, The Note II has one updated to 18th.
I'm sticking with this.
I was on TWRP 2.6.3.0 and just flashed CWM 6.0.3.6. I was having random FCs on TACHYON and wanted to see if CWM might help. Do I need to wipe anything after flashing a new recovery? Thanks.
geronimo48 said:
I was on TWRP 2.6.3.0 and just flashed CWM 6.0.3.6. I was having random FCs on TACHYON and wanted to see if CWM might help. Do I need to wipe anything after flashing a new recovery? Thanks.
Click to expand...
Click to collapse
No you don't need to wipe anything after flashing a new recovery. What force closes were you getting?
Sent from my ADR6425LVW using Tapatalk
XAlexander_AlexanderX said:
No you don't need to wipe anything after flashing a new recovery. What force closes were you getting?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Phone randomly shuts down. I get a black screen and can't reboot unless I pull the battery. It usually won't fully boot unless it is plugged into a charger or PC. I had a problem with battery drain and overheating. I did S-Off and went through all of R3v3nt3ch's procedures to return to stock and reload all signed RUUs and OTAs. Then flashed TACHYON. The battery drain/overheating problem seems much better. There were no FCs at first, but they are getting more frequent. Just had one and my battery is at 80%.
geronimo48 said:
I was on TWRP 2.6.3.0 and just flashed CWM 6.0.3.6. I was having random FCs on TACHYON and wanted to see if CWM might help. Do I need to wipe anything after flashing a new recovery? Thanks.
Click to expand...
Click to collapse
If your recovery is the "cause" of your force closes, then after you install the new recovery, you need to do a complete wipe and reinstall the ROM and setup manually... If recovery is the "cause" of your issues, it is in the flashing of the ROM that is problem, not the actual recovery itself, that is the issue.
To be honest, those issues sound more like you need to S-OFF and clean flash everything from first RUU forward... it is not the most logical approach, but it seems to work for people having "weird" issues that don't seem to have a real cause.
I just did all of that.
Thanks
Sent from my Rezound on Tachyon using xda app-developers app
Your recovery isn't in use when you're booted into a rom, that's not what is causing your FC's unless as noted the ROM didn't install correctly.
mjones73 said:
Your recovery isn't in use when you're booted into a rom, that's not what is causing your FC's unless as noted the ROM didn't install correctly.
Click to expand...
Click to collapse
correct me if im wrong but couldnt an all in one kit if he flashed a recovery that way possibly cause issues...ive seen prior posts of people having similar issues with flashing that method
REV3NT3CH said:
correct me if im wrong but couldnt an all in one kit if he flashed a recovery that way possibly cause issues...ive seen prior posts of people having similar issues with flashing that method
Click to expand...
Click to collapse
As far as a I know those all in one kits still run the same fastboot flash command under the covers so I don't know how that could cause an issue. It's basically a GUI that runs the commands for you, not a big fan of them because you never learn the actual commands.