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
Related
Hi all
I'm not new to flashing but I'm new to flashing cm7.
I odin back to stock jfd eclair. Root and Install CWM 2.xxx. I downloaded the stable cm7 and I started flashing. (after I wipe data/cache of course)
IN recovery, it said finding package, opening package, then my phone processed a series of lines and reboot automatically. On the startup, it says VIBRANT SAMSUNG, then GALAXY S CYANOGEN(mod) then the same recovery screen with many lines. It moved too fast into another reboot I couldn't read what was on the screen. And it kept doing this for quite 10 mins now.
Is it normal? if not, what did I do wrong? I can get into download mode and odin back to stock but I did it last night and I couldn't think what i did wrong.
Please help!
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
stumpyz9 said:
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
wavestar92 said:
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
Click to expand...
Click to collapse
Try reflashing cwm when your rooted, may have not flashed right
Sent from my Gewgle Phone via XDA App
This happened to me also, I went directly back to recovery, 3 button, and reflashed. Worked the second flash for some reason.
Thanks. I turn it off, get into recovery again, and re flash it successfully
Same exact thing happened. I have no idea how many time I odened back to stock trying to figure it out.
I did as you guys said, as soon as that loop began, pulled the battery and got back into recovery. flashed again and worked just fine!
same thing happened to me...i got back into recovery...i noticed cwm updated to 5.0.2.8 then i reflashed and all good...when i tried to flash at first. cwm was 2.5 ..maybe thats the issued it wont flash on that...has to be cwm 5.0
anyway getting ready enjoy some cm7 on my vibrant...
Fixed but I have no idea how or why. If any can explain I would appreciate it.
I was on TWRP and flashed Hyperdrive which caused me to Boot loop at the Samsung screen. I then tried to restore my backup which failed. I then went through and wiped all the data and tried a different rom (Clean rom) this caused boot issues too.
I ODIN using factory image which still boot looped. I then went into recovery ( i lost TWRP when I odin'd) and wiped everything and still boot looped. I wiped everything again 3 times and this time I was able to get into my stock rom.
I am confused with is happening inside the phone that caused the boot loop and why I still had boot loops even after a ODIN restore.
SuperKerp said:
Fixed but I have no idea how or why. If any can explain I would appreciate it.
I was on TWRP and flashed Hyperdrive which caused me to Boot loop at the Samsung screen. I then tried to restore my backup which failed. I then went through and wiped all the data and tried a different rom (Clean rom) this caused boot issues too.
I ODIN using factory image which still boot looped. I then went into recovery ( i lost TWRP when I odin'd) and wiped everything and still boot looped. I wiped everything again 3 times and this time I was able to get into my stock rom.
I am confused with is happening inside the phone that caused the boot loop and why I still had boot loops even after a ODIN restore.
Click to expand...
Click to collapse
sometimes it just takes a little while. was it actually looping or just stuck there? Ive had to wait 10 minutes before it actually got passed that screen.
Yeah, you probably just didn't wait long enough...
Sent from my SCH-I545 using xda premium
theidoctor said:
sometimes it just takes a little while. was it actually looping or just stuck there? Ive had to wait 10 minutes before it actually got passed that screen.
Click to expand...
Click to collapse
nfederic said:
Yeah, you probably just didn't wait long enough...
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Wow, 10 minutes? Yeah ok, I definitely didn't wait that long before. I started to freak out a bit when it started resetting continuously. I thought the waiting would be just sitting at the boot screen and then when my restore failed the worst things were going through my head.
I am having the same issue after I reinstalled hyperdrive v6 where do I wait 10mins at?
My bootlooping starts at the language selection screen do I wait 10mins at the installation page?
Fixed it.... it was the Walkman player.
i have the answer!!
dont install any of the audio hacks and also dont install the walkman musci player just use the samung one ... peace!!!!!
was installing the hyperdrive Rom using clockwork recovery mod, it says it installed sucessfully but when i go to reboot the device it just going into reboot loop, i can get back into recovery mod but when i try to factory reset and try it again it just does the same thing again, tried installing a different rom and still same thing, what am i doing wrong?
im having the same problem. i cant boot into recovery. is there anything i can do. i was on cm10.1 before this and it worked fine. i flashed hyperdrive using OUDHS and it installed and everything. i let it sit for 10 minutes like it said to then i continued to reboot... and now its stuck on the custom padlock screen and im cant boot into recovery for some reason...
OMsupp said:
im having the same problem. i cant boot into recovery. is there anything i can do. i was on cm10.1 before this and it worked fine. i flashed hyperdrive using OUDHS and it installed and everything. i let it sit for 10 minutes like it said to then i continued to reboot... and now its stuck on the custom padlock screen and im cant boot into recovery for some reason...
Click to expand...
Click to collapse
Try to get in to Odin mode. If you can flash the Stock Image and go from there.
RLS7 Verizon S4 continuous reboot loop
galaxyfans said:
was installing the hyperdrive Rom using clockwork recovery mod, it says it installed sucessfully but when i go to reboot the device it just going into reboot loop, i can get back into recovery mod but when i try to factory reset and try it again it just does the same thing again, tried installing a different rom and still same thing, what am i doing wrong?
Click to expand...
Click to collapse
Hi I have the exact same pb, I flashed several times my S4 (I was on RLS4 before) following the instructions, no way to get out from the endless reboot loop.
There is a suggestion using ODIN, I am not very familiar on how to do that, any help?
Thanks
abalgir66 said:
Hi I have the exact same pb, I flashed several times my S4 (I was on RLS4 before) following the instructions, no way to get out from the endless reboot loop.
There is a suggestion using ODIN, I am not very familiar on how to do that, any help?
Thanks
Click to expand...
Click to collapse
dont install any audio mod and also dont install any of the music players just the samsung one !
before you go through all the trouble of ODIN, which seems to be everyones answer now a days, it is a kernel issue, flash a verizon loki kernel. It should boot.
abalgir66 said:
Hi I have the exact same pb, I flashed several times my S4 (I was on RLS4 before) following the instructions, no way to get out from the endless reboot loop.
There is a suggestion using ODIN, I am not very familiar on how to do that, any help?
Thanks
Click to expand...
Click to collapse
First, if you have a back up, restore just the system partition (this will also format your current /system) Then do a factory reset and reboot. Now I if that doesn't work, Odin is your best bet.
Sent from my SCH-I545 using xda app-developers app
FOR anyone installing Hyperdrive, the most probable cause of boot loop in the Walkman Music App. Don't choose it in Aroma!!!
If you already have, the only way to fix the boot loop is to ODIN back to stock, as Dark Menace suggested.
He can PM you the stock image, which you will have to flash in ODIN to successfully boot up again.
hey I do plenty of flashing, and from time to time get into trouble... But ODIN is not the first choice to fix... Please read the forums:cyclops:
Sent a few PM's to see if that helps. You can try the kernels first then go from there.
Sent from my SCH-I545 using xda premium
fix
I had the same problem had to go back in odin mode and reflash a old stock. If that does not work reset data and cache and install a new rom. Worked for me
DarkMenace said:
Sent a few PM's to see if that helps. You can try the kernels first then go from there.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
I will try again without selecting the music app. I was always selecting the Sony one. I will try this afternoon and keep you informed.
Thanks
abalgir66 said:
I will try again without selecting the music app. I was always selecting the Sony one. I will try this afternoon and keep you informed.
Thanks
Click to expand...
Click to collapse
It worked perfectly if we do not select any music app. Thanks
Device gets stuck at S4 logo with blue font RECOVERY BOOTING, even after Odin, any ideas??
I'm so stuck!
TheAxman said:
before you go through all the trouble of ODIN, which seems to be everyones answer now a days, it is a kernel issue, flash a verizon loki kernel. It should boot.
Click to expand...
Click to collapse
I can't get my phone to see the the SD card in recovery. My Verizon Galaxy S4 is stuck in a boot loop thanks to Hyperdrive RLS12 and Odin fails every time I try it. Any help would be greatly appreciated!!
Surge1223 said:
First, if you have a back up, restore just the system partition (this will also format your current /system) Then do a factory reset and reboot. Now I if that doesn't work, Odin is your best bet.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I am trying hyperdrive on Baseband I545VRUEMJ7 and build JSS15J.I545VRUEMJ7 (4.3). I am able to root and install safestrap. Even hyperdrive/dirty unicorns (i tired both) installs fine, but ends up in reboot loop. am i missing anything here?.
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.
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.