Related
Lately I've been having a problem with my Evo. After flashing the latest stable roms 6.1 and 6.1.1, I found my phone freezes, force closes, and reboots, then wont get past the white evo screen. Ive wiped everything using amon ra and clockwork but i keep coming back to the same issues. I even try not using Setcpu on a clean install and still have issues. I also noticed that everytime I wipe then flash, the google apps show up after my first boot, even though i never flashed the google zip file. Is my phone wiping correctly? What could be the problem?
aheavyguy said:
Lately I've been having a problem with my Evo. After flashing the latest stable roms 6.1 and 6.1.1, I found my phone freezes, force closes, and reboots, then wont get past the white evo screen. Ive wiped everything using amon ra and clockwork but i keep coming back to the same issues. I even try not using Setcpu on a clean install and still have issues. I also noticed that everytime I wipe then flash, the google apps show up after my first boot, even though i never flashed the google zip file. Is my phone wiping correctly? What could be the problem?
Click to expand...
Click to collapse
If this ONLY happens to you when using cyanogenmod roms, then you are not alone. The exact same issue happens to me also ONLY when using CM 6.1 and CM 6.1.1. I have never had this issue with any other rom, both aosp or sense-based, except with CM 6.x roms.
Sent from my HTC EVO running Myn's Warm TwoPointTwo RLS 4 loaded with all the goodies
Yea for some reason these last 2 releases just wont work right on my phone. Which def sucks because I love Cyanogenmod roms. Anyone have any suggestions as to why this might be happening?
Try the following:
Wipe data+cache twice
Flash sense ROM
boot
wipe data+cache twice
verify MD5's
flash CM
flash gapps
U recommend clockwork or ra
What? This title for a thread and no poop jokes? The Internet makes me sad.
Seriously, though...
I'm partial to Clockwork now because I use ROM Manager Pro. AmonRa was the one I always used on my Hero. Both are good. It's yet another "personal preference" thing.
CM6 Issues
I too have had trouble with CM 6.0 and 6.1. I flashed CM6.0 Stable, and could not get apps to install or uninstall after flashing. I tried restoring an earlier Nandroid backup of my previously working HTC Sense ROM, and still could not install/uninstall any apps. I tried clearing Market cache, fixing permissions, wiping cache, Dalvik cache, numerous reboots, and flashing earlier ND backups with no luck. I finally bit the bullet, flashed Stock RUU, and had to reroot to get phone working properly again.
Think I would have learned from above, but being flashaholic that I am, I flashed CM 6.1 when it came out. Exact same probs, and again had to reflash stock RUU and reroot.
No more Cyanogen mod for me. Nothing against CM, and it may work great on some people's EVOs, but its only caused me headaches.
Good news is I'm getting pretty damn proficient rooting phone using old-school manual adb shell/rageagainstthecage/chmod exploit method, having done it three times now (although I hope I don't find myself in this situation again).
YMMV
Me too. Tried with both clockwork and ra...no dice. Problem is, when I went back to warm, it left pieces and now even warm doesn't run correct. I tried wiping twice and clearing the dalvik too. I know it wasn't erasing everything because there would be apps that were already installed. Like it was installing to a partition, though I have never set that up.
...
Hello all
I just updated to 3.0.0.5 and now when I reboot into revocery via Rom Manager I get to the HBOOT screen with the only options for:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I don't get the usual black background with green letters? From what I've read it should go to the black background but now with Orange letters?
Please advise at what I'm doing wrong. Which option should I use to get to clockworkmod 3.0.0.5
Thanks in advance
-g
A lot of the current ROMS are not compatible with the new CWM and many people experienced the same as you. In RM, scroll all the way down and go back to the previous version.
patsfan1130 said:
A lot of the current ROMS are not compatible with the new CWM and many people experienced the same as you. In RM, scroll all the way down and go back to the previous version.
Click to expand...
Click to collapse
The oldest version available is the current one I am on 3.0.0.5. There are newer version .6 .7 and .8? Do you know if those versions will produce the same issue?
After much reading this cwm3 is causing lots of problems. I've searched the forums for a write up on how to flash back to 2x but haven't found one. Does anyone have a quick write up to get this done either through fastboot or adb?
Thanks
-g
I have a thread in the dev forum updated today that explains exactly what you want.
I had issues when I previously upgraded from 2.5.1.2 to 3.0.0.5 when I tried to restore a backup made with 2.5.1.2. It restored and got to the point of loading the kernel where the boot animation was animating. It just sat there for about 20 minutes so I pulled the battery and went back to 2.5.1.2 and restored the same backup and it worked. I wanted to see if 3.0.0.8 had fixed restores and I found it hasn't in my case although I do see how others don't have this problem. Just some info before I do a restore I always do a full wipe including boot and system. Oh and I flashed 3.0.0.8 in Rom Manager and the text in recovery is orange. Does anyone know why I can't restore a backup made from 2.x with 3.x recovery loaded?
tdiman said:
I have a thread in the dev forum updated today that explains exactly what you want.
Click to expand...
Click to collapse
Awesome tdiman! Thanks for the write up, it worked. I just needed to enable wipe!
sitrucz said:
I had issues when I previously upgraded from 2.5.1.2 to 3.0.0.5 when I tried to restore a backup made with 2.5.1.2. It restored and got to the point of loading the kernel where the boot animation was animating. It just sat there for about 20 minutes so I pulled the battery and went back to 2.5.1.2 and restored the same backup and it worked. I wanted to see if 3.0.0.8 had fixed restores and I found it hasn't in my case although I do see how others don't have this problem. Just some info before I do a restore I always do a full wipe including boot and system. Oh and I flashed 3.0.0.8 in Rom Manager and the text in recovery is orange. Does anyone know why I can't restore a backup made from 2.x with 3.x recovery loaded?
Click to expand...
Click to collapse
The only thing I've heard is that it works. When I've had a boot animation that loops like that, the following things have worked for me:
boot back into recovery, wipe the cache, then go to advanced and wipe the dalvik cache. Reboot. Give the boot animation a good 5 minutes before giving up. This is especially needed when going between different ROM versions (e.g. skyraider to CM7, non-sense to sense, etc.) .
Also, did you try booting it up twice after the boot animation loops before reflashing CWM? Sometimes all it takes is a battery pull and reboot. It does happen randomly.
I'm not convinced its related to the CWM version directly because I see that happen all the time randomly. Of course, I'm not convinced its not related either
tdiman said:
The only thing I've heard is that it works. When I've had a boot animation that loops like that, the following things have worked for me:
boot back into recovery, wipe the cache, then go to advanced and wipe the dalvik cache. Reboot. Give the boot animation a good 5 minutes before giving up. This is especially needed when going between different ROM versions (e.g. skyraider to CM7, non-sense to sense, etc.) .
Also, did you try booting it up twice after the boot animation loops before reflashing CWM? Sometimes all it takes is a battery pull and reboot. It does happen randomly.
I'm not convinced its related to the CWM version directly because I see that happen all the time randomly. Of course, I'm not convinced its not related either
Click to expand...
Click to collapse
First, thank you for your response. I'm not going to spend too much time on this since 3.x is the new standard. I use Cyanogenmod 7 dailys as my daily driver and rEVOlution 2.2 as my sense rom backup. So, if after a restore and rebooting and then wiping cache and davlik and possibly reflashing a froyo kernel, incredikernel 12/20, doesn't solve it I'll just restore from 2.x recovery, upgrade recovery, and then get a new backup. I'll do the same for Cyanogen and call it a day and start using cwm 3.x.
After testing I was unable to restore my rEVOlution rom using 3.0.0.8 from 2.5.1.2. I wiped cache and davlik and flashed a froyo kernel and still no dice. It was strange even though I could only see the boot logo the rom was fully booted as I had voicemails and I heard the voicemail notifications but the home screen never came up. I rebooted and still the same thing. So I reflashed 2.5.1.2 restored rEVOlution upgraded recovery then got a backup. I did the same for my Cyanogen nightly and I'm on 3.0.0.8 now for good. I wanted to pass this on to others. If I want to restore an older backup I'll just restore recovery to 2.5.1.2 and do a restore.
Tried Bonsai and Syndicate first, neither flashed properly first time, seemed to work on the second flash, but eventually they would start freezing occasionaly when the screen was off, had to pull out battery to reboot. Tried flashing to stock di18 then flashing to Midnight, it seemed to work for a day or so, and now its freezing a few times a day when the screen turns off. I read somewhere that in odin you only need the victory8g.pit (not sure the exact file name) if you are flashing a custom rom, and I'm only ever flashing a stock rom, then rooting and flashing from the sd card. I've always used the .pit file im odin, and I've eventualy had problems with all custom roms.
Any ideas?
Skimp Killah said:
Tried Bonsai and Syndicate first, neither flashed properly first time, seemed to work on the second flash, but eventually they would start freezing occasionaly when the screen was off, had to pull out battery to reboot. Tried flashing to stock di18 then flashing to Midnight, it seemed to work for a day or so, and now its freezing a few times a day when the screen turns off. I read somewhere that in odin you only need the victory8g.pit (not sure the exact file name) if you are flashing a custom rom, and I'm only ever flashing a stock rom, then rooting and flashing from the sd card. I've always used the .pit file im odin, and I've eventualy had problems with all custom roms.
Any ideas?
Click to expand...
Click to collapse
What version of the ROMs are you trying to use?
If you start with di18 and tried to use a dk28 ROM you would have to odin the new modem.
If you're trying the EB13 ROMs, then you want to odin the EB13 tar that is stock + recovery + ext4; then flash an EB13 ROM of your choosing.
Also, you have to be sure to wipe 3x (factory reset, cache partition and davlik cache)
Be sure to follow each and every step on the first few pages of the ROM thread your going to flash, also read some into the thread too. that will give you a heads up as to what others have experienced and what might be a problem and its fix.
Good luck!!
With syndicate and bonsai I flashed the stock eb13 first, then cwm, then flashed the rom in recovery mode, midnight I flashed from stock di18, followed all instructions. Just tried midnight again, except I didnt used the victory8g.pit file or whatever, just the di18 tar, then cwm then flashed the rom.
I think me using the pit file may be what the problem was, unless you are supposed to use the pit file even when flashing a stock rom, in odin.
Are you using setcpu? Do you have a screen off profile? Are you running your phone at 1.2ghz?
Sent from my SPH-D700 using Tapatalk
Are you using setcpu? Do you have a screen off profile? Are you running your phone at 1.2ghz?
I'm not sure the answer to any of those questions, so I'm assuming no. I think the MidnightROM can run the cpu faster, but you have to download some app to turn that function on or off. I'm pretty much running MidnightRom with the regular **** on it right now. I'm thinking my problem may have been using the victory8g.pit file in odin every time I flashed to a stock rom before running clock work and flashing to a custom rom. I'm running the latest midnight off a clean flash of di18 without the victory8g.pit file, so far that seem to be the only thing I can find that would cause all the custom roms to eventualy crash...
Im going on a few hours with out a crash, but the first time it took a day or so, then started doing it more often.
Skimp Killah said:
Are you using setcpu? Do you have a screen off profile? Are you running your phone at 1.2ghz?
I'm not sure the answer to any of those questions, so I'm assuming no. I think the MidnightROM can run the cpu faster, but you have to download some app to turn that function on or off. I'm pretty much running MidnightRom with the regular **** on it right now. I'm thinking my problem may have been using the victory8g.pit file in odin every time I flashed to a stock rom before running clock work and flashing to a custom rom. I'm running the latest midnight off a clean flash of di18 without the victory8g.pit file, so far that seem to be the only thing I can find that would cause all the custom roms to eventualy crash...
Im going on a few hours with out a crash, but the first time it took a day or so, then started doing it more often.
Click to expand...
Click to collapse
What kernel is midnight using? The reason I ask the questions I'm asking is cause not every phone can be over clocked and it causes data locks. That's what it sounds like that's happening to you. there is nothing to the pit. All the pit is mapping information nothing actually gets flashed from the pit. The full tar as that information in it so its not making any changes.
Another question I have is since you keep coming from stock are you flashing the rom twice? On the first flash wipe data, cache, dalvik and on the second flash only wipe cache, and dalvik.
Sent from my SPH-D700 using Tapatalk
I'm pretty sure Midnightnight uses the Bonsai Kernel. On the about phone section it say 2.6.32.9 for kernel version. When I did bonsai and syndicate I usually data reset 3 times and cache and dalvik or whatever, once, each time I flashed it, which was usually twice.
okay, in the phone it says Bonsai/Kernal-v3.0.0
Obviously I'm on an epic 4g. When it freezes its always when the screen is off, never during actual use. I'm not sure if that helps narrow it down. And I had an epic with a cracked screen, same freezing problems, now on a new epic, still same thing, but I assumed it was the custom roms doing it because the problem only started after that.
MidnightROM and bonsai didn't require a wipe, when I tried syndicate i wiped as per the instructions, except I did the factory reset 3 times on the second flash as well.
Skimp Killah said:
I'm pretty sure Midnightnight uses the Bonsai Kernel. On the about phone section it say 2.6.32.9 for kernel version. When I did bonsai and syndicate I usually data reset 3 times and cache and dalvik or whatever, once, each time I flashed it, which was usually twice.
Click to expand...
Click to collapse
Is the bonsia kernel oced to 1.2 ghz out the box?
Try this when you get a chance.
1) odin eb13 full tar
2) run the cwm3.0.0.6 one click
3) reboot into recovery and let the auto conversion do its thing.
4) flash your rom of choose (after wiping data, cache, dalvik 3 times)
5) let the phone boot all the way up.
6) reboot into recovery again
7) flash the rom again (after wiping cache, dalvik 3 times)
8) let the phone boot
9) install setcpu and see where your clocked at
Sent from my SPH-D700 using Tapatalk
Skimp Killah said:
okay, in the phone it says Bonsai/Kernal-v3.0.0
Obviously I'm on an epic 4g. When it freezes its always when the screen is off, never during actual use. I'm not sure if that helps narrow it down. And I had an epic with a cracked screen, same freezing problems, now on a new epic, still same thing, but I assumed it was the custom roms doing it because the problem only started after that.
MidnightROM and bonsai didn't require a wipe, when I tried syndicate i wiped as per the instructions, except I did the factory reset 3 times on the second flash as well.
Click to expand...
Click to collapse
Theres gonna be problems coming from stock cause of there back up there script performs. Follow the instructions I just posted and lets go from there
Sent from my SPH-D700 using Tapatalk
Flashed to EB13
Ran oneclick CWM 3.0.0.6
Converted.
wiped data, cache and dalvik, 3 times each
Flashed MidnightROM
it did the whole random vibrations flashing two screens thing.
removed battery and booted into recovery
wiped cache and dalvik 3 times each
flashed MidnightROM again
After the second flash it went to the intial start up screen welcoming me to the phone, that was odd, never had it do that before.
Booted to recovery again and installed market and other standard apps.
Downloaded cpu master cause im cheap,
phone is clocked at 1000
I'll let you know if i have any more problems, the whole welcoming me to the phone thing was new, ive never had it bring that screen up any of the other times i flashed a custom rom, hopefully this is a sign of good things
Skimp Killah said:
Flashed to EB13
Ran oneclick CWM 3.0.0.6
Converted.
wiped data, cache and dalvik, 3 times each
Flashed MidnightROM
it did the whole random vibrations flashing two screens thing.
removed battery and booted into recovery
wiped cache and dalvik 3 times each
flashed MidnightROM again
After the second flash it went to the intial start up screen welcoming me to the phone, that was odd, never had it do that before.
Booted to recovery again and installed market and other standard apps.
Downloaded cpu master cause im cheap,
phone is clocked at 1000
I'll let you know if i have any more problems, the whole welcoming me to the phone thing was new, ive never had it bring that screen up any of the other times i flashed a custom rom, hopefully this is a sign of good things
Click to expand...
Click to collapse
Some rom devs have that enabled while others don't. If your flashing the same rom you have been and haven't seen that before I bet your good
Fyi: setcpu is free to xda users you just need to find it as I can't post links from my phone
Sent from my SPH-D700 using Tapatalk
from midnight i flashed to cm7, then wiped installed google apps and re-booted, so far so good
gingerbread
I've tried to install midNIGHT rom 6 times now with the same result. I cannot install any apps from the market, titanium backup, or from sdcard. It will vibrate once at the beginning of install than again 2 or 3 times. My phone will then show the bootup animation and return to the homescreen. Ive odined back to stock and rerooted 4 times and wiped everything 3x each time. Each time I get the same result. Ive also tried reformatting my sd card and starting with a fresh download. Other roms work, just not this one. I dont have enough posts to reply to the midnight thread, so what should I try next to make it work?
acburnett said:
I've tried to install midNIGHT rom 6 times now with the same result. I cannot install any apps from the market, titanium backup, or from sdcard. It will vibrate once at the beginning of install than again 2 or 3 times. My phone will then show the bootup animation and return to the homescreen. Ive odined back to stock and rerooted 4 times and wiped everything 3x each time. Each time I get the same result. Ive also tried reformatting my sd card and starting with a fresh download. Other roms work, just not this one. I dont have enough posts to reply to the midnight thread, so what should I try next to make it work?
Click to expand...
Click to collapse
what rom did u have before that workd ??
i had acs with ext then flashed to rooted ec05 with rfs. had several eclair roms installed.
acburnett said:
i had acs with ext then flashed to rooted ec05 with rfs. had several eclair roms installed.
Click to expand...
Click to collapse
MAYBE YOUR flashing the wrong rom to update from the midnight ex: if you use dk28 ... i dnt think thats gets the proper update ec05
so lets see if you flash a dI18 or better get eb13 stick rom ... now u can either flash the ec05 modem or as my phone did when i used the stock eb13 it sent me the update for ec05 then i rooted w 3.0.6 clockworkmod then i went to BONSAI .. i left BONSAi to midnight ... i wiped factory data 3x - cache petition 3x and davlik cache 3x ... then i installed the zip MIDNIGHT V5.2 JOURNALING ON .... THEN AFTER IT BOOTED .... i went back into RECOVERY and flash the ZIP EXTRAS .. bang it was magic ... lol'
but basically im tryn to give you steps that maybe something might help u or give u and idea ..... IT WORKED FOR ME .....
DISCLAIMER : im not a professional if something major goes wrong i dnt not claim responsibility ...
I have the same problem. Worked the first time I installed it but I restored back to stock. Now when I install I can't install from market. Tried odin back to stock but It still doesn't work. Haven't seen a solution in the midnight thread besides going to EXT.
I am having issues as well and cannot post a reply. I have wiped and re installed 3x but my phone will randomly turn off and I have to pull the battery to reset device. If the device stays plugged in I do not have this issue. Any ideas or suggestions would be greatly appreciated!!
You note that this version is the one with journaling enabled... have you tried the version without journaling? You can manually re-enable it by making a CWM Nandroid backup and then restoring that backup immediately after.
acburnett said:
i had acs with ext then flashed to rooted ec05 with rfs. had several eclair roms installed.
Click to expand...
Click to collapse
On the instructions for midNIGHT 5.2 with Journaling On it says not to start with a pre-rooted EC05. Start with stock EC05 and then root with CWM 2.5.5 for RFS or 3.0.0.6 if you are wanting to use the EXT4 one. There is a link for a stock EC05 on the instructions in the thread for the ROM
And how to check if the journaling is actually on or off.
dito33 said:
And how to check if the journaling is actually on or off.
Click to expand...
Click to collapse
I'm not sure if there's a quick and easy way to detect this through the Terminal Emulator. I tried a line of code that I believed would tell me but I didn't get the answer I was looking for. Someone else may have the answer.
The quick and dirty way, however, is to make a Nandroid backup through Clockworkmod, as you should generally just have one at all times anyway. Now turn your phone on, and pull the battery out. If when you turn your phone back on you don't encounter any FC's, then your journaling is on and your data is protected. If not, then restore your Nandroid backup you just made and that will enable journaling.
If you installed a no-journaling rom, rest assured, journaling is off if you haven't restored. Either way you should have a Nandroid backup just in case.
Note: This process has been documented and posted many many many times across XDA at this point.
I was also having this issue so I installed the EXT4 Journal On version and problem solved. No one knows why LOL.
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919
aLdaRiS said:
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919
Click to expand...
Click to collapse
Interesting.
I was about to try odin'ing back to stock and reflashing twrp.
The only thing I wonder if may be related is when you restore a backup with TWRP it gives options of all sorts of partitions besides system/data/cache etc... preload etc. It's possible it doesn't like mucking with those.
Interesting to note: If I install a CM nightly, it will allow me to reboot. Wickedv2 or my backup of wickedv2 no go.
Testing further.
Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.
saldebot said:
Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.
Click to expand...
Click to collapse
Righto. Sounds like a valid idea.
Unfortunately, the download links in konane's thread are timing out for me mid download. Tragic.
Managed to snag it from another location. Flashed back to stock firmware/recovery via odin.
Letting it boot to see what it does.
EDIT:
That did it.
Restored my backup and most everything is working correctly (restoring my titanium backup of all apps now.)
Few things were messed up (swiftkey was missing a language pack etc?)
But looks like AOSP/AOKP roms do something to the partition table as you said that requires flashing back the original.
Good to know and thanks for the help!
Don't wipe system in twrp.
makomek said:
Don't wipe system in twrp.
Click to expand...
Click to collapse
Does this cause issues? Didn't know.
I found that only CM nightlies would reboot fine. restoring via odin stock official then going back and putting on wicked again seemed to work to fix it and I can now reboot in a touchwhiz based rom.
re: stuck
bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
If you want a 95% sure way of fixing it so it boots completly,
then try this, it usually always works.
Get the phone into recovery mode twrp/cwm does not matter.
Then simply do a "factory reset" and I am fairly certain that it
will boot completly, I have seen this issue so many times
already not just here in the S4 thread but also in the S3.
The factory reset will not delete any of your music, videos and pictures.
Good luck!