I just followed the instructions from this thread. The phone is currently on the honeycomb like boot screen. I know it is supposed to take a while for it to install, but I usually see 10-15 minutes. It is going on well over 20 this time. Is this normal? At what point should I start over?
Edit: It went to 30-40 minutes so I decided to start over. To my surprise it booted up after removing and replacing the battery. I cleared cache and data a few times and reinstalled the rom from CW. This is what I am used to doing on my N1 and it seems to have worked fine on the Fascinate.
Is there anything I might have missed by doing this?
I've had this happen about about every third or fourth time I would wipe cache and dalvik before installing something. I usually wait five minutes and if it was still stuck I would pull the battery. It would be nice though to figure out what was causing it.
Sent from my Fascinate
Superclean 2.9.1
EC10 voodoo kernel
EA28 radio
A couple problems with a few roms dissappear after rebooting or by resetting after removing battery.
Related
Hi,
I was trying to flash a Ultimate Honeycomb v3.1.1 theme on my VZN Fascinate using CWM, but after flashing and rebooting, it just sits there on the booting screen (flashing honeycomb) while the phone vibrates occasionally. Can someone tell me how to fix this or why it's happening? I didn't have problem flashing gingerbread theme by nitsuj17.
I have SC2.9.2 voodoo/EB01
many thanks,
kim2rock said:
Hi,
I was trying to flash a Ultimate Honeycomb v3.1.1 theme on my VZN Fascinate using CWM, but after flashing and rebooting, it just sits there on the booting screen (flashing honeycomb) while the phone vibrates occasionally. Can someone tell me how to fix this or why it's happening? I didn't have problem flashing gingerbread theme by nitsuj17.
I have SC2.9.2 voodoo/EB01
many thanks,
Click to expand...
Click to collapse
Download might have been corrupted or you flashed SC and then flashed the theme without rebooting in between.
Thanks jonesya13!
I'm pretty sure I rebooted in between, but I will try to re-download the file and then flash the theme again as you suggested.
This happened to me on both the 3.1 & 3.1.2 with superclean 2.9.2. I booted fully into superclean as well before flashing the theme after a cache/dalvik wipe. Battery pull worked both times. Rebooted normally after that.
Thanks garywojdan81!
I tried to flash with a newer ultimate honeycomb (3.1.2), it flashed without a hitch but I found out that menu & home button didn't work. So I went back to SC2.9.2... I will try battery pull & wiping cache/dalvik then reflash the 3.1.2 theme.
kim2rock said:
Thanks garywojdan81!
I tried to flash with a newer ultimate honeycomb (3.1.2), it flashed without a hitch but I found out that menu & home button didn't work. So I went back to SC2.9.2... I will try battery pull & wiping cache/dalvik then reflash the 3.1.2 theme.
Click to expand...
Click to collapse
I had the menu and home button problem as well, ended up flashing, I think the EC10 kernal, and it fixed that problem for me.
Thanks jonesya13 and garywojdan81!
I tried reflashing the theme after wiping cache/dalvik - that did the trick!
I have not tried the EC10 kernel yet. So far, I'm satisfied with EB01, so I'll try sticking with it until it causes problems.
kim2rock said:
Thanks jonesya13 and garywojdan81!
I tried reflashing the theme after wiping cache/dalvik - that did the trick!
I have not tried the EC10 kernel yet. So far, I'm satisfied with EB01, so I'll try sticking with it until it causes problems.
Click to expand...
Click to collapse
You might as well as update to jt's ec10. BLN + Sound + Color.. Epiiiic
Just wipe cache/dalvik
Rocking Frankenclean 2.9.2 Voodoo/EC10+Sound+BLN+Color/Nitro Ultra Honeycomb v3.1/XDA Premium
xHoLyx,
What might be some advantages of jt's EC10 over regular EB01, in your opinion? I'm not too familiar with kernel replacement, so reading relevant posts might take some time. thx!
I tried 2.2 out a few weeks ago and decided I couldn't live without Voodoo Sound and BLN so I decided to wait it out. Obviously we have these enhancements available for Froyo now, so I made the jump to JT's initial EC10 release.
Everything worked fine, I just didn't feel that "snappiness" I had before. I thought maybe it had something to do with being undervolted (even though only slightly.) I saw that there were some problems with imnuts initial kernals he posted and waited to flash the updated (fixed) link for 0328_imnuts_sv_voodoo.zip. I flashed last night, booted up, and played around for a little bit and everything was working great. I had it plugged in to charge overnight. That brings me to my issue...
I woke up this morning, reached over to turn my phone on and I got NOTHING. No boot, samsung, lights, nada...I thought "****, I really bricked my phone now." I tried booting into recovery using the 3-button combo, plugging it in my computer to try download mode, plugging my charger in different outlets,etc...The phone seemed like there was no sign of life. I was ready to head to Verizon before work then decided to plug in my car charger for ****s and giggles and sure enough...IT WORKED! It started charging and I turned the phone on. Now I am at work and the phone seems to be working just fine...I even have the usb plugged in my computer and it is charging now (The same one that didn't work this morning.) This has never happened to me before and it was pretty scary. I have had to ODIN before, but I was worried that wasn't even an option. Thanks god everything SEEMS to be working fine right now, though that made me a little concerned.
Do anyone have ANY idea what might have happened!? Thanks in advance.
EDIT: After a couple hours, I saw my battery start to wig out. It went from being at like 34% to flashing the "low battery" warning. It then turned off and did the exact same thing. I had to go out to use my car charger to get into recovery. I wiped cache/dalvik cach, and re-installed SC. Not sure if it's kernal/ROM/Theme with 3rd party battery supprt...
Voodoo'd Samsung Fascinate
Kernal: 0328_imnuts_sv_voodoo
ROM: Superclean 2.9.2
Theme: Nitro's Ultimate Honeycomb v3.1.2
on ed04 w/ newest MIUIwiz
pick up phone and its rebooting over and over...for no reason. Pull battery, it reboots to "safe" mode? Now it boots fully and its force close city, gapps force closes, launcher force closes, everything force closes then the phone reboots. Is there an obvious fix or reason for this? Reflashed rom and kernel, wiped caches and reinstalled, and its the same thing, force close city. Any reason why this would randomly happen out of the blue? All was well before.
mikey6p said:
on ed04 w/ newest MIUIwiz
pick up phone and its rebooting over and over...for no reason. Pull battery, it reboots to "safe" mode? Now it boots fully and its force close city, gapps force closes, launcher force closes, everything force closes then the phone reboots. Is there an obvious fix or reason for this? Reflashed rom and kernel, wiped caches and reinstalled, and its the same thing, force close city. Any reason why this would randomly happen out of the blue? All was well before.
Click to expand...
Click to collapse
Did you wipe data/factory reset? If so, and you still have problems, you could try fixing permissions in CWM (advanced menu). If that still doesn't work, I recommend flashing imnuts' Odin ED01 stock package here: http://www.multiupload.com/6ET46L1ATD (it should not replace your ED04 modem) and then downloading the MIUIWiz ROM again (in case the first download was corrupted).
Another Fascinating post by my XDA app...
i could tell u this much my wife phone is fully stock from day one (she would never let me flash anything to her phone but always liked my phone)and her phone was doing the same thing. so i dont think its just the rom.she called vz they told her to do a factory reset,and she did.2 days know and she ok. this happen a after updating to ed04.
If you've reflashed the ROM, then you've essentially wiped /system and started new there. Sounds like something in /data is corrupt. Wipe data (yeah, not having a recent backup will suck, but you'll get by) and everything should be fine.
I odin'd back, wiped data blah blah blah and fixed it all back up, but I am curious what happened in the first place.
Phone was working flawlessly for weeks, I go to take it out of my pocket and its on the boot animation, boots to something saying safe mode with force closes galore. Pull battery and reboot, and its the same thing, force close city, and backups through recovery do not work. I am curous why that happened
mikey6p said:
on ed04 w/ newest MIUIwiz
pick up phone and its rebooting over and over...for no reason. Pull battery, it reboots to "safe" mode? Now it boots fully and its force close city, gapps force closes, launcher force closes, everything force closes then the phone reboots. Is there an obvious fix or reason for this? Reflashed rom and kernel, wiped caches and reinstalled, and its the same thing, force close city. Any reason why this would randomly happen out of the blue? All was well before.
Click to expand...
Click to collapse
Personally, every so often, I'd recommend doing this http://forum.xda-developers.com/showthread.php?t=1090127&highlight=ext4+formatter. It wipes EVERYTHING.
Same thing happened to me for the second time last night. On com rom 2.1/otb kernel. Phone froze up randomly, held up and power to reboot. When it came back it was.force close city. Subsequent reboots would freeze on the lock screen or reboot right as the lock screen loaded.
Recovering a backup didn't work. Wiped data and reinstalled com rom and phone is fine again.
Is my phone possessed????
Sent from my SCH-I500 using XDA App
Hey guys,
little frustrated here as i am having some issues. I have the ERIS running Gin tazz CM7, and when the phone is on, it runs flawlessly, but as soon as i reboot or turn the phone off, and turn it back on, i get a force close error message stating "com.android.phone" has stopped working, and pretty much makes the phone useless. I then have to wipe and re-flash the ROM and everything is fine again, until I reboot/turn phone off and boot back up.
I experimented a little last night, and put the phone in airplane mode and shut the phone off, rebooted, and turned it off of airplane mode when it was done booting, and i did not get that message. I thought i had found the cure. Rebooted again and got the same error message! I'm pulling my hair out, not sure what else to do. Has anyone heard of this issue, and if so is there a quick fix? FYI i used another ROM and it did the same thing, so i do not think it is the software. It is almost as if on the reboot it can't load the necessary "codes" to get the radios up and running again. Any feedback appreciated!
p.s i attached a screenshot to let you guys see what the error message looked like!
do you do full wipes of data and dalvik for every flash? The same issue hit me one time when I had not done wipes of both. I went back and wiped both, dalvik I just went ahead and wiped three times. Idk that three times matters but I wanted to make sure I was good to go and I know I had seen workshed post before about 3x wipe of dalvik. When I went back and wiped everything like that and re-flashed everything went back to normal for me.
The wipe of Data & Dalvik is a critical step. Like the poster above me, I've heard the "3 times" suggestion and I'm not sure why 1 versus 3 would make a difference. However, just to be safe, I have started wiping Data & Dalvik 5x each, each time I flash. It's most likely just overkill & paranoia, but hey, I've had no issues.
Some roms, depending on what are are upgrading from, may also require you to delete a folder from your sd card. For example, as Workshed states in his GSB v3.7 thread,
"If you're coming from a cm6 or 2.1 ROM, make sure you delete .android_secure folder on your sdcard before flashing."
http://forum.xda-developers.com/showpost.php?p=11178912&postcount=1
Hope this helps!
Having similar problems. Only wiped once, I'll try it a few times and see how that goes.
I was running Eternity version 116 for a long time, and decided i should upgrade to a more recent rev. I tried flashing v236 (and 238 and various versions in between) and all appears to go well, I get a message for successfully installing, but on first reboot, I get stuck on the splash screen. While I haven't tried many ROMs, I always wipe first. I am currently running Bamf Forever. But for whatever reason, I just can't get Eternity to load. Any suggestions? Thanks!
If you wiped data first and didn't get a bad download (if you've tried multiple versions, that would be very unlikely) then there really wouldn't be a logical reason for it not to work. All I can tell you is that it takes a long time (5 minutes maybe) to boot up the first time you flash a new ROM, I think it's because it zipaligns your apps. Hope you figure it out, if you find out what the problem was, let me know.
I've let it boot up for hours, but it never gets past the splash screen.
are you wiping data/cache/dalvik
Bigandrewgold said:
are you wiping data/cache/dalvik
Click to expand...
Click to collapse
Yes, wiping everything. I don't seem to have a problem installing other ROMs, just Eternity.
disregard. i got 216 to work. i don't know wtf was going on. but i'm happy now.
Glad you got it working. There have been some significant changes since 216 that makes it worth your time to upgrade to R238.
I figured out what the problem was. turns out all i needed to do was update CWM. now all versions flash fine. I was using a 3.0 version of CWM.
Hey, so about a month or so back, my Vibrant has started to restart seemingly randomly. I do nothing to trigger it, I will just have it sitting on my desk and then I see the boot animation. This has happened on various ROMs as I have tried fixing it by flashing different ones. Fishmanmod v4, Slim ICS, CM9 nightlies, all the same issues. Different kernels, same problem as well.
I have ODIN'd back to stock multiple times and reflashed all different ROMs to no avail. I always wipe cache, dalvik, format system, factory reset... all that stuff when I flash a new ROM. I have left things stock, not installing any apps, same issue.
So, does anyone know what could be the issue, how I can fix this? Any information anyone needs for me to post? I am not sure what to do, and it is a rather annoying problem.
Me and my sister have the same phone (Vibrant) and she had the same issue. Not exactly sure what caused it, but switching out the battery seemed to help. (It was probably something else, but it seemed to be working after we switched batteries. Worth a shot!)