Related
I've been trying to load a new rom onto my fascinate sch-i500v for a few hours now. I previously had a 4.1 build (milestone I think) and cwm 4.0.1.0 installed. I've tried every rom from cw10 to hellybean to avatar and they all do the same thing. I wipe the cache, factory reset. Then installed from the zip file. At this point, the install starts to initiate, but the phone suddenly reboots and after a few seconds tries to load up the old rom (unsuccesfully, hence why I said I'm seeing the "initiating swagger" load screen forever)
Yesterday, I did this exact upgrade successfully to my other fascinate sch-500 (no v on the end for that one, not sure if that makes any difference).
That one rebooted suddenly as well, but it went back into the clockwork recovery and completed the install without a hitch.
Anybody have any suggestions? I'm sort of a noob, but I have flashed over ten phones...
Go back to stock and start over
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Go back to stock and start over
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Thank you. i fugured that was what I needed to do, but I was afraid of how complicated it would be. LMFAO, it was pretty simple!
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?.
So i was going to flash a rom I made a back up, I hit fixed permissions. and now all I have is Samsung Galaxy S4 logo and is just stuck there. I can get into twrp and have tried wiping and starting from a clean slate and restoring the back up but still get the galaxy logo? any suggestions ?
**have just tried to use odin and fails also*** How do I get back to stock please? Anyone please help
bump
Imprezive13 said:
bump
Click to expand...
Click to collapse
Have you tried flashing a stock ROM from TWRP?
-------edit----------
I just remembered. This used to happen on the Note 2 at times. If you're booting and get the Samsung splash screen, try going to TWRP and doing a Factory Reset a couple times. No idea if it will work, but with the Note that would usually clear whatever block existed and allow the ROM to boot past the splash screen. Good luck.
eakeller said:
Have you tried flashing a stock ROM from TWRP?
Click to expand...
Click to collapse
what do you mean ? first time ever having a problem with this. are you talking about the SCH-I545_MDK_562219_Stock_Restore.tar file ?
Imprezive13 said:
what do you mean ? first time ever having a problem with this. are you talking about the SCH-I545_MDK_562219_Stock_Restore.tar file ?
Click to expand...
Click to collapse
If it exists, it would basically be that ROM stuck into a .zip file which could be flashed from TWRP. I'm not sure it exists, was just browsing the Dev thread for you to see if anyone posted it. There is a version here http://forum.xda-developers.com/showthread.php?t=2292707 , but I'm not familiar with Loki enough to say whether or not you have it.
eakeller said:
If it exists, it would basically be that ROM stuck into a .zip file which could be flashed from TWRP. I'm not sure it exists, was just browsing the Dev thread for you to see if anyone posted it. There is a version here http://forum.xda-developers.com/showthread.php?t=2292707 , but I'm not familiar with Loki enough to say whether or not you have it.
Click to expand...
Click to collapse
Well for right now im trying to just get the phone back to its working condition. trying to using odin, but fails every time. and not sure what i should do.
Imprezive13 said:
Well for right now im trying to just get the phone back to its working condition. trying to using odin, but fails every time. and not sure what i should do.
Click to expand...
Click to collapse
If Odin isn't working for you, a solution might be had via TWRP since you can still get into the recovery. If you flash your ROM or try your backup, does the install complete or does it crash? Have you wiped cache, dalvik, system, and data before the flash?
-edit-
Sorry, just saw your OP where you said you wiped and tried. If I were you my next step would be trying a different ROM just to see if you can get something booting.
eakeller said:
If Odin isn't working for you, a solution might be had via TWRP since you can still get into the recovery. If you flash your ROM or try your backup, does the install complete or does it crash? Have you wiped cache, dalvik, system, and data before the flash?
Click to expand...
Click to collapse
Trying again. First wiping wiped cache, dalvik, system, and data , then restoring back up. I've tried this multiple times before hopefully it works this time. But generally when i hit reboot system afterward it just hangs at the Samsung Galaxy IV boot screen and does nothing.
Imprezive13 said:
Trying again. First wiping wiped cache, dalvik, system, and data , then restoring back up. I've tried this multiple times before hopefully it works this time. But generally when i hit reboot system afterward it just hangs at the Samsung Galaxy IV boot screen and does nothing.
Click to expand...
Click to collapse
After your backup restores, try using TWRP to do a Factory Reset a couple times before rebooting. Also wipe cache/dalvik again before the boot.
Failed again stuck at Samsung Galaxy S4 boot screen
eakeller said:
After your backup restores, try using TWRP to do a Factory Reset a couple times before rebooting. Also wipe cache/dalvik again before the boot.
Click to expand...
Click to collapse
Stuck again
Imprezive13 said:
Stuck again
Click to expand...
Click to collapse
Sorry to hear that, man. I'm out of ideas and hopefully someone with more know-how can give the solution.
Sent from my SCH-I545 using Tapatalk 2
I would try downloading a ROM to your computer then copying it to a microsd, put the card in your phone and then try to flash the fresh ROM from TWRP. (After wiping everything again.)
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
I would try downloading a ROM to your computer then copying it to a microsd, put the card in your phone and then try to flash the fresh ROM from TWRP. (After wiping everything again.)
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Ive been looking for the stock rom files no luck at the moment.
Maybe this one?
http://forum.xda-developers.com/showthread.php?t=2292707
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
Maybe this one?
http://forum.xda-developers.com/showthread.php?t=2292707
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
downloading now wish me luck
Good luck to you.
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
Good luck to you.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
got it working. on a deoxed rom. but is there a way to go completely back to stock using odin ?
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Well went to restart the phone and now its stuck on a Samsung logo with a unlocked icon thats says custom underneath it and just sits there.
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.
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.