My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?
Did you have any undervolt settings applied?
The phone is not underclocked, it is not overclocked. It was rooted, I unrooted it. its currently unrooted absolutely factory stock and still doing that. What can I do to fix this?
warranty is over as of 3 months ago
Forgot to mention the most important thing!!!
When I am on the phone with someone, it works perfectly forever, as soon as i hang up, it ends the call. this key thing might help someone find the solution!!
himalaya333 said:
My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?
Click to expand...
Click to collapse
Don't panic just yet... I doubt your phone is dead.
You say you've "wiped data and cache". Are you also making sure to wipe /system and Dalvik Cache?
Try flashing Zeus again.
Boot to CWM, Wipe EVERYTHING (/data, /cache, /system, Dalvik Cache). (Alternatively, get "Clean Wipe" from Qkster's Scripts and flash with CWM to easily wipe everything.)
Flash Zeus and go.
If you're still having problems, perhaps try a different rom?
okay, I read everything you guys wrote.. This is where I am, I am open to suggestions
I am on the stock rom and unrooted. Phone still boot loops. What should I do now? Step by step instructions would be great. Im unrooted, so should i root again? even though im having this problem?
bump! really need help with this guys!
Have you tried going back to stock?
If it keeps looping while on download mode then I would say you are dealing with a hardware issue.
Sent from my sweet & buttery Infuse
It just came to me that it doesn't loop in download mode. It does loop in clockwork, I flashed the stock kernel using ODIN and went completely stock through ODIN.
How do i fix this? i'm pissed that i had it for a year and three months and right after the warranty ended, the phone stopped working! Samsung never again unless this issue is fixed
I'm a newbie to flashing, so take it with a grain of salt. At least two more things seem worth trying to me:
1 - Try factory data reset (assuming you already tried the wipe Davlick and wipe cache). I'm not positive what this does, but I think you may lose some of your data if it's not backed up.
2 - If that doesn't work, try qkster's Heimdall UCLB3 stock (since you can get into download mode...shouldn't be a problem). This is complete back to stock so should be able to clear any software problem I'd think. I know you may think it's redundant since you are already back to stock, but worth trying imo since some things just take more than one try, and you may have had a bad flash the first time around.
Why zeus? try latest ones with jelly bean
Hey,
Try other roms based out of jelly bean. They are pretty stable. CM10 with 09/14 build is the latest
Here are the standard steps if you have CWM enabled.
1. Factory re-set (only when switching between different roms).
2. Cache partition wipe
3. Dalvik Cache wipe
4. Install the zip file
5. Re-start and wait until it re-starts. Initially it will take some time.
I have tried various roms and versions as well. Best would be the CM10 Jelly bean.
Thanks Kran.
Related
(Just wrote a detailed post and when I went to post, it said I wasn't logged in and erased it...will give a quick run down and can supply more detail where needed as I work through fixing my phone)
Stuck on the white htc splash screen is my most recent problem. Sometimes it gets by that but then boots into recovery. I think bananagranola has the solution in their sig to flash a boot.img. and think I'm comfortable with how to do that, just need to find that file (in the ROM zip?)
What led up to this.
Successfully unlocked and flashed to CM7 back in late Jan/early Feb.
Started experiencing random freezing about two weeks ago.
A week later (last weekend) flashed Jellybean (R10). Worked great for a couple hours then started having the same random freezes.
If things froze I'd have to remove the battery and reboot. After a day or two of this though it'd get to the point that even that would leave me on a frozen jellybean boot animation. So I'd go and factory/data reset in CWM Recovery, wipe cache, wipe Dalvik then reflash the ROM. and I'd be good for a little while more.
Tried flashing back to CM7 but Recovery didn't like the file (it has a good MD5 when checked) Had tried my restore point from early Feb before to no avail, so decided this morning to try other restore points from the last few weeks, right before and after switching to JellyBean. They got further, the first step is something with boot then something with system. It failed on the system part. OK...so I wiped and reflashed jellybean again, and now I am to my splash screen freezes.
I should have asked for help much earlier (lesson learned!) but here I am asking now...what's the first step.
Do I test out and see if I hang on the splash screen again. I haven't turned the phone on in about an hour. Worried of screwing it up more.
Thanks all.
TL;DR Believe I'm stuck on splash screen and know solution to that. Have had phone flashed with new ROM with no prob for months, recently freezing, regardless of ROM. Hoping for advice on getting things working again, starting with whether fixing the splash screen thing first is where to start
splash screen issue seems fixed
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
irishpanther said:
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
Click to expand...
Click to collapse
That doesn't sound like an sdcard problem. Are you full wiping?
bananagranola said:
That doesn't sound like an sdcard problem. Are you full wiping?
Click to expand...
Click to collapse
I'm wiping data/factory reset and cache as well as the dalvik cache.
The steps to flashing a ROM by sashank at link mention to format /boot and /system. I didn't specifically do those...but don't see the option for /boot in any menus I've checked.
A week or so ago I was beginning to suspect there was an issue with the memory but I never found the right search terms to find out how to do a memtest if that's what would have found any problems. Yesterday I did come across some discussion of a corrupt partition/bad chips in some HTC devices. I followed the directions there and through adb ran dmesg | grep mmc0 and the output was similar to the 'normal' one given and showed none of the messages they claimed to indicate a bad chip.
I'm not too concerned with any data from the phone...I backed all that up long ago and the rest restores from my google account. So if I getting things running would normally raise concerns of lost data, that's not an issue for me.
Thanks for taking the time to read. I try to be brief...but don't want to leave anything out.
Wanted to update here before trying to start a new thread and clogging up the board. The title of this thread is not up to date though.
I can hboot just fine and boot into recovery just fine. My phone is unlocked and rooted, ENG S-OFF from when I used AAHK quite a while ago.
When trying to navigate from menu to menu in Recovery I will get the following error messages (best I remember from last time I was in there, I've let the phone be for the last 2-3 days now)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
This doesn't show up at first though, only after I do a Wipe Data/Factory Reset. And if I understand correctly, that wipes /cache so maybe that's causing these errors?
Anyway, after wiping the dalvik cache I can flash a ROM, I've been using Jellytime, I haven't been able to rollback to CM7, not sure why not.
Jellytime will run though...at first! the first couple of boots I can get in and get through registering my google account and have it begin restoring apps if i make that selection. The time I have to work on the phone before it freezes gets shorter and shorter though. I have to remove the battery to get it to reboot. Eventually I am left with the phone hung during the boot animation. I've left it for over an hour before...it's definitely hung there.
So my reading leads me to believe corrupt partitions. I'm not finding a lot on what I should do to reformat and maybe repartition or whatever I may need to do to recover a functioning phone. I don't care about any data on the phone. I just want to get things working again. I ended up getting a new SD card during all this that arrived earlier. If I can get my phone working, I'd prefer to use that from here on out too. I can use the adb in recovery mode just fine if that's necessary to rejigger things to work.
Can anyone help reset my partitions, if that's what this issue seems to be? If not...any ideas?
Thanks.
Recovery and version?
bananagranola said:
Recovery and version?
Click to expand...
Click to collapse
ClockworkMod Recovery v5.0.2.0
Full wipe?
bananagranola said:
Full wipe?
Click to expand...
Click to collapse
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
irishpanther said:
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
Click to expand...
Click to collapse
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
OK, I'll give this a try. The issue with the freezing is why I moved from CM7 though (which had been stable for four months) so it's reproduced itself in different ROMS. I'll post back once I give this a try. Thanks.
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
I gave Android Revolution a shot. During the flash it gave a message which might also be why I wasn't able to flash back to CM7. The MD5 did verify.
Code:
assert failed:write_raw_image("/tmp/boot.img","boot")
When I went to reboot, I ended up in Jellytime. Of course I had to sign back in to google apps and those things were reset from the dalvik wipe. Shortly there after the phone froze.
On reboot I tried a logcat. Didn't get it right from the start (you can send the command during the boot animation if I read correctly) but captured the failure of things. It's back around the 09:02 portion of the log. To my eyes it looks similar to others I've collected. Especially the message
Code:
Fatal signal 7 (SIGBUS)
though I haven't been able to figure out much about that, or identify what it is before that that could give another clue as to what is screwy since that's maybe (Probably?) related to the flashing issues.
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.
bweN diorD said:
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.
Click to expand...
Click to collapse
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?
SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
In all likelihood, this is not a LiquidSmooth issue. I would suggest a clean install as the previous posters suggested. The latest stable version of LS is now at v2.10 for Android 4.3
LS 2.10 must be installed as follows, according to the devs:
New Flashing Instructions
wipe data/factory reset
wipe cache partition
wipe dalvik cache
format /system
Install ROM, NOT GAPPS YET!!
Reboot system, first boot may take a few minutes, don't panic ;-D
Setup your phones settings, anything that isn't Google related
or let your phone sit for 5 minutes
reboot back into recovery
wipe cache and dalvik
then flash gapps
reboot and enjoy
Click to expand...
Click to collapse
For the xt926, the download page for LS 2.10 is here: http://d-h.st/users/jsnweitzel/?fld_id=15202#files
gapps 8/13 or newer are supposed to be used with this ROM. dl from here: http://d-h.st/users/jsnweitzel/?fld_id=21058#files
The official ROM page is over at G+ https://plus.google.com/u/0/communities/117452480298315341829, if you have any additional questions.
Give it a whirl, and let us know what happens. Good luck.
SELind01 said:
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?
Click to expand...
Click to collapse
you are wiping very well, i was just confirming you wipe everything possible short of the external sd.
the wipe im talking about in twrp is wiped when you wipe "data", the one where you have to type "yes" before it will wipe. in cwm, in the formatting section (i forget what its called), there is an option that specifically says "data-media /internal sd" or something close to that.
as for the latest recoveries, here is a tool by Tucstwo that i have been updating lately http://www.mediafire.com/download/2o061zcmzlaycb5/Razr_HD_Recovery_Flasher_V8.rar
also, twrp 2.5 doesnt have all the selinux bugs worked out, you need 2.6.3.0, which is in the above utility.
Soooo. The photon i've been using since june lost it's identity (IMEI, ESN, MEID, etc. all GONE and DFS tool kept throwing nasty errors every time it tried to read or write to the phone) so i swapped the board out of my other photon with a broken screen into the pristine chassis of the amnesiac phone.
now the fun starts: i RSD back to stock to activate the phone, all's good while i'm on stock. but if i flash a rom like skrillax's CM 10.2, the phone will boot fine the first time, then upon reboot will hang at the unlocked bootloader warning screen. restoring a backup of stock fixes this issue, but i'd really love to have my CM back
Any ideas?
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
angahith said:
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
Click to expand...
Click to collapse
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
solitarywarrior1 said:
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
Click to expand...
Click to collapse
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
solitarywarrior1 said:
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
Click to expand...
Click to collapse
I just ran into this issue too, after flashing CM10.2.
I can't boot any ROM right now. The phone always shows the unlocked bootloader screen and returns (without button press) to the recovery..
I will try flashing the stock FW with RSD Lite.
I have just been searching for a reason for this issue also.
I was running stock jelly bean, unlocked, twrp. Flashed CM 10.2, and it runs fine right until I reboot the device then it hangs at the red Motorola symbol. I have to hold the power button until it starts vibrating to shut it off. If I boot into recovery and do a factory reset it will then boot again.
I have tried updating to the latest version of TWRP (from 2.5), and tried both Milestone and Nightly versions of CM. I have flashed this phone at least 20 times today. Issue persists with or without Gapps.
I REALLY don't want to go back to stock after all this time I've spent, any ideas on what is causing this?
i had a similar problem monthes ago. i was able to boot but its not a fix more a workaround.
go to bootloader menu (Power+Vol-Up+Vol-Down)
and try the first option it called "normal powerup"
if it not work go again to bootloader menu and try "BP Tool"
same problem here...
after flashing cyanogenmod 10.2 and the first reboot the phone hangs
i restored original moto 4.1.2 from nandroid and now phone runs without problems. is there a problem with cm 10.2 ?
i used last night 20131127 gsm and swapped bootloaderimage.
Know this is an old thread, but after Motorola recently announced that they won't be bringing KitKat to the Photon Q, I finally decided to root and flash mine.
Can't begin to say how disappointed I am at Motorola on this one - the MSM8960 is well supported by KitKat and there are no technical reasons not to... at least Motorola is tactily admitting this is a penny-pinching business decision.
Anyways, I'm stuck at the same hang. Tried flashing known-good Photon Q builds and using the latest TWRP.
It took three flashes just to get the latest stable TWRP for it to take. I suspect the "JBBL" (Motorola Jelly Bean-era Boot Loader) is at fault here. CM just committed some patches to (in the near future) resume issuing builds for JBBL devices, but that won't fix the underlying problems.
And, since Motorola is abandoning the device, it looks like those won't get fixed either.
My next step is to restore via RSDLite, update PRL, Firmware, and Profile in stock ROM, and then start over. Disturbing that's needed, but now Motorola is Lenovo's problem I guess.
How long did you let it boot? Out of five XT897's I've owned, one woul ALWAYS take 15-60 minutes after an initial flash. I guess something was wrong with the memory. After an RSD-return-to-stock and back to CM it would take at least an hour to boot (repair process in the back during bootloader-logo). A wipe (internal too) and CM and it would take 10-15 minutes to get past bootloader logo.
Yesterday I restored a nandroid, wouldn't boot. Installed via zip and 15 minutes later it did boot again.
So just maybe you also have one of those special Photon's . It's worth a try.
I used TWRP 2.7.1.1 and M8 Snapshot in case you were wondering.
Hey! About two weeks ago I rooted my Samsung Galaxy S 4G and installed "Valhalla Final" Gingerbread 2.3.6. Everything has been great until today :crying:... I was talking on the phone and the battery went dead, I got home and charged it then tried to turn it back on. When I did it started to boot up and then got stuck on the "Team Kang" unicorn animation. I'm a noob and not sure what to do? I have tried removing the battery, etc. and still same result. HELP!! What should I do?? Thanks in advance...
Try doing a factory reset in recovery.
To get to recovery:
pull out your phone's battery
put the battery back in
hold BOTH volume keys and do NOT let go of them
Press the power button long enough for the phone to turn on
Once you are in recovery you can let go of the volume keys
What I ended up doing was going to recovery mode, wiping the cache and then flashed the same rom again.. Question is what would have made it do this to begin with? Is there a problem with this rom that im not aware of? After I did the above it now works fine other than having to go through and redo apps, etc..
jevanstintshop said:
What I ended up doing was going to recovery mode, wiping the cache and then flashed the same rom again.. Question is what would have made it do this to begin with? Is there a problem with this rom that im not aware of? After I did the above it now works fine other than having to go through and redo apps, etc..
Click to expand...
Click to collapse
There is no problem with the rom, if you wipe cache before upgrading. I usually wipe dalvik as well. Wipe factory if you are coming from a different rom.
I do the previous three for each rom I use, on any phone I own. I don't always trust that the developer wrote in the updater-script to attempt to wipe cache & dalvik when flashing.
Hi there!
After about a week ago, I’ve turned off my Note 3. Then two days later, when I wanted to use it, I’ve turned it on. After CM logo appears, its says:
“Android is starting
Optimizing x apps of x”
I know this is because of ART, but after it finishes, my phone reboots, and CM logo appears again, and nothing happens. After a while, it starts optimizing apps again. Now I left it for 2 hours, my phone didnt boot up.
What should I do? I didnt flash any new kernel, rom, recovery or anything else. Im on CyanogenMod, with CWM recovery. I dont want to factory reset, because of my photos and videos.
Even I tried to start in safe mode, but I couldnt get to it, and Im not really sure that I tried to enter safe mode properly.
Please help!
Just dirty flash the rom again through cwm.
See if it works
It's high time you flashed TWRP already.
Bence98007 said:
Hi there!
After about a week ago, I’ve turned off my Note 3. Then two days later, when I wanted to use it, I’ve turned it on. After CM logo appears, its says:
“Android is starting
Optimizing x apps of x”
I know this is because of ART, but after it finishes, my phone reboots, and CM logo appears again, and nothing happens. After a while, it starts optimizing apps again. Now I left it for 2 hours, my phone didnt boot up.
What should I do? I didnt flash any new kernel, rom, recovery or anything else. Im on CyanogenMod, with CWM recovery. I dont want to factory reset, because of my photos and videos.
Even I tried to start in safe mode, but I couldnt get to it, and Im not really sure that I tried to enter safe mode properly.
Please help!
Click to expand...
Click to collapse
Ahh I would suggest you to get TWRP, The world has moved on and I think you should too! It's just a little better at things overall. TWRP can be flashed through ODIN. As for the Bootloop, try dirty flashing the ROM. Just wipe the dalvik/ART and cache and leave the rest as it is.
Dinara° said:
Ahh I would suggest you to get TWRP, The world has moved on and I think you should too! It's just a little better at things overall. TWRP can be flashed through ODIN. As for the Bootloop, try dirty flashing the ROM. Just wipe the dalvik/ART and cache and leave the rest as it is.
Click to expand...
Click to collapse
What do you mean on “dirty flashing”? Do I lose my data if I flash my rom again?
Bence98007 said:
What do you mean on “dirty flashing”? Do I lose my data if I flash my rom again?
Click to expand...
Click to collapse
No you don't, dirty flashing = installing the same ROM without wiping or resetting any data sets, just reflashing that zip again, JIC some files got corrupted, if that doesn't help you might have to give it a fresh start.