So for the last 5 days I had some very weird problems with my phone. About 2 weeks ago I started with my first Cronos Rom and it worked great. I flashed 1.5 and 1.5.1 without problems and I used it without an ext partition all the time. But then the problems started. When I wiped my whole phone and tried to reinstall 1.5.1 JIT, the phone didnt boot anymore (stuck on the "Android" bootscreen). I wiped again and again, tried 1.5.1 without JIT, 1.5 etc, but I couldt get the phone to work. Nothing worked, so I created an ext partition and tried again. It worked. My phone started and I was able to use it for about a day without problems though I didnt want apps2sd. But then some other weird things happened. 3 Days ago I bought a bigger SD Card, partitioned it, wiped the whole phone and flashed 1.5.1 JIT. The phone started, but after I installed a few apps, I got an error message (installing xxx failed). I found out that theres an "repair ext" function, and it worked, but after I installed some more apps, the problem was back. The second problem was, that after rebooting the phone, more and more apps wouldnt start anymore (FC). The last problem that occured was an FC of the market app. After that, I wiped everything again, tried to flash 1.5.1 JIT, but it happened exactly the same like on the first time. Problems installing apps, FCs, stuck on boot etc.
I am totally down at the moment because I killed my whole weekend trying to get my phone working again. Could anyone please help my with this? I just dont understand what I did wrong. Shouldnt a complete wipe fix almost every problem? And I dont understand why I suddenly cant use my phone without an ext partition. Any Cronos version I try freezes on bootscreen without an ext patition. Is there any way to get my hero working again? Please please help me.
(PS: I also posted this on the Cronos Board.)
I would take out the sd card, wipe system and dalvik cache, and install some custom rom.
well, to make sure it is NOT your phone, did you try another ROM? Eliminate possible problems?
At least try something that is known and stable, like a stock rom, the Taiwain-rooted-repacks (not a rom based on it, but just the taiwan rom rooted) or good ol' MoDaCo 3.2 (based on 1.5 stock).
Til now I just tried the last 2 or 3 Cronos Roms, and as I said, they didnt work, but when I get home from work I'll try the Modaco Rom I used before.
I dont understand what this has to do with the Rom I use. I always wiped the whole phone, dalvik, etc. so shouldnt it just work like the first time I flashed it? No matter what Rom I use?
Another weird thing (could have something to do with this): After I wiped everything and flashed Cronos 1.5.1 JIT, the market still knew what apps I had installed last time. It showed my bought apps AND the apps I was able to install before the latest crash. So does this mean the phone wasnt wiped completely?
The market tracks your purchases and (free) downloads through your google account. So that's normal that the download-list is full.
But it might very well be that you didn't wipe correctly, although I'm curious how you manage to accomplish that. What is your current recovery?
The whole point about trying another ROM is elimination. It doesn't need to make sense, but you need to check things of the list.
There is something weird going on, so trying to solve it logically will only get you so far . Keep trying to narrow down the list of causes. Might well be a bug with Cronos 1.5, or the overclock not working these days because your phone is just a bit hotter than before, who knows.. Like I said: eliminate causes!
I'm using the newest AmonRa recovery to wipe the phone.
Theres one thing I forgot: Yesterday I flashed 1.5.1 without JIT, and then 1.5.1 JIT right after it (just rebooted a few times between). The phone worked great until my SD card crashed. In the taskbar it always showed me "checking for errors"(something like that, my phone's in german ), but in my PC and in the recovery the card worked like always, so I had to wipe the card and start again from the beginning.
Try another ROM , and if that doesn't work, try without SD card.
tombond said:
I'm using the newest AmonRa recovery to wipe the phone.
Theres one thing I forgot: Yesterday I flashed 1.5.1 without JIT, and then 1.5.1 JIT right after it (just rebooted a few times between). The phone worked great until my SD card crashed. In the taskbar it always showed me "checking for errors"(something like that, my phone's in german ), but in my PC and in the recovery the card worked like always, so I had to wipe the card and start again from the beginning.
Click to expand...
Click to collapse
Maybe sdcard faulty? What are the logs you get when booting up the phone?
Soooo, I wiped everything again and flashed Modaco 2.8 without an ext partition. It booted correctly, so I wiped the dalvik cache and flashed Cronos 1.5.1 JIT. It also booted (wow, first time it booted without ext since all the problems started to occur) but I instantly got FC's (phone app for example). Now I wiped completely again and flashed 1.5.1 JIT. I hope it boots, as I still dont have an ext partition. As soon as I know something new, I'm gonna tell you.
So now it seems like its working again. I was able to install all the apps I need without a single error and now I'm restoring my settings and contacts. Suddenly it even works without ext again.
I guess there was something very big f*ked up that I couldnt repair by simple wiping the phone. Very weird that just flashing Modaco got it running again. Now I have back my working phone with ultrafast Cronos Rom and without App2SD, perfect. At least till now I hope it keeps working.
Thanks for your help guys, I think I would have smashed the phone to the wall sooner or later. I never thought about flashing Modaco so I'm happy there are people like you.
Thanks again, and thanks to Feeyo for his unbelievable Rom.
PS: Can I uninstall, Facebook and Footprints without destroying everything again?
Yes, just delete both apps using ADB or use a root explorer, search both apps in System/app and delete them.
Or you could use the MoDaCo online kitchen for removing those apps.
I finally decided to attempt to load a custom ROM on my Samsung Fascinate after a couple of months of owning it. Before I started anything, I backed up my current ROM twice using ROM Manager, then used ROM Manager to do the new ROM download and install.
Things didn't go well. At all.
Once the new ROM was installed, my phone restarted, got back to the puzzle screen (thinking I was in business!) and as soon as I unlocked the screen the force closes just kept on coming. One right after another. Pretty much anything and everything force closes, so much so that it is the only thing you can do on the phone now. I have tried force closing things for as much as 5 minutes thinking I might get to the end of it, but no luck.
So now I have 2 backups on my SD card. I went into my Android System Recovery (+, - volume and power button), selected apply sdcard:update.zip which gets me to ClockworkMod Recovery v. 2.5.1.0. From there I go into Backup and Restore, select Restore and then my restore file. After some time the restore process is complete and the phone asks to reboot. I do the reboot and low and behold nothing seems to have changed in the phone. I still have the custom ROM with all of the force closes.
Am I missing something with this CWM restore process? I have read what seems like dozens of forum entries and nobody else seems to have problems with the restoration.It seems like it is pretty straight forward but I am not having any luck with it at all.
Any help is appreciated!
Try This and see if it helps:
http://forum.androidcentral.com/fascinate-roms-hacks/38029-how-escape-force-close-loop-hell.html
Perfect! I am back in business thanks to you. Sure appreciate your help!
Did you wipe first?
I can't begin to describe how frustrated this phone has made me. I am not an Android "n00b" by any stretch. I have had 4 different Android phones, have flashed at LEAST 100 different roms, made complete rom themes, and even glued together one of the first complete Gingerbread roms to flash from recovery for the Motorola Droid (not from source, but first posted rom with working camera, Gapps, and all from standard recovery - not nandroid). With that being said, this phone is next to impossible for me to use. I've lost track of all of the problems I have had with this thing. Everything from CWM not being able to restore any backups, horrible battery life, boot loops galore, the phone freezing anytime it is plugged into the computer or wall (not the car charger, oddly enough), boot loops, tried the Yellow Clockwork (and everything failed that could on that), flashing roms that would work great until you reboot the first time, and so on and so forth. WHEN the phone works, it's great. However, that is starting to become quite rare. Most recently I have been stuck on trying to get either Evil Fascinate to work or MIUIWiz with no luck for either. EF works great...until I restore my apps. Once I reboot, it's all over. EVERYTHING force closes and it becomes completely unusable. Doesn't matter what kernel I use, it always happens. And this is now happening with both 3.5.1 and 3.6.0. Plus I could just watch the battery life plummet as I was using it. I even tried the EC01 radio with it, as it was suggested that might be better. So, I decided to try MIUIWiz. Followed the directions perfectly. Wiped everything, flashed a JT Kernel from 4/15, flashed rom, and...guess what? Boot loops. I am on ClockworkMod 3.0.2.7. I am familiar with how to wipe data/cache/dalvik. There were no voltage settings to wipe. I did check to see if Voodoo was enabled before booting. I just don't know what else to do. This isn't exactly rocket science and I really feel it can't just be user error at this stage with all of the different issues I have ran across. I'm pretty much at the stage that I am gonna return it to stock and sell it, but would really like to enjoy it for a little while longer... Thoughts?
Just for laughs, I downloaded Community Rom 1.3. Was on EF 3.6 (with nothing restored, just signed into Google). Rebooted to Recovery, wiped everything, installed Comm Rom and never got past the Samsung screen. *sigh* Seems odds since they are based on the same base, but yea, that's how it's been going for me.
I think since you are so god awfully experienced that you are looking over something that probably seems useless to you, ive NEVER experienced any of your problems and I can tell you its not the phone.. I would read up about your specific problems or ask a specific question and you might get the help you need.
Edit:Bootloops are user error nearly every time. Unless you have a corrupt download or something.
Sent from my SCH-I500 using XDA App
As much as your sarcasm warrants a rude response, I'll choose not to stoop to that level. The point of the post was that there is not a "specific" problem. Hence the title, "Nothing works as it should..." Not every phone is the same, and just because you have experienced any of these problems does not determine whether my issues are phone related or not. Battery life issues are very common place, which is evident in many threads. The phone lagging when plugged in is most CERTAINLY a phone issue and has nothing to do with rom flashing. It appears this is a firmware issue and is not likely to be fixed at all. Also, I pointed out the steps used to flash the rom, which are posted in the thread, and still have problems with boot loops. So, I guess every rom I download is corrupted? Even though on different networks and computers? That's some luck I have...
Are you referring to "download" mode when you said yellow cwm? If so then maybe reinstall the samsung drivers and give it a clean flash including the pit with voodoo disabled. If you have bad problems like you are having that fixes anything I encounter.
Edit: if you use odin, try heimdall
Sent from my SCH-I500 using XDA App
The newest imnuts kernel installs a yellow CWM, and nothing worked right at all on that. Every verification failed. SO I ODINed back to stock and retried everything anew. Anytime I restore my apps with Titanium, the next reboot fails. I even just went back to stock again, flashed CWM Red 3.0.2.8ti and the stock kernel with recovery fix, restored apps again and rebooted and it did the same thing. I didn't have any issues with Titanium restoring stuff before, having successfully used it on EF 3.5.1 and ComRom 1.3 but not those don't work for me either anymore. I've tried restoring just the apps with no data and that doesn't seem to make a difference either.
EDIT - It must have something to do with Titanium. Gonna try an older version and see if that works. It looks like they updated it recently and maybe it is just not playing nice with anything for my phone.
When you restore try not restoring system data, that is check the box for user applications only. That might be the issue.
yea, I'm going to say Ti backup is the problem because you mention ti every time you have a problem. personally I don't use ti cause its never played nice for me, but did you try manually reinstalling a couple of apps reboot and see if the same problem happened? that would really narrow it down almost completely to ti.
Fascinate 2.2 1.2GHz(uv)
download the imnuts peanut butta jellytime kernel of choice and put it on your sdcard. Odin back to the stock rom of your choice (i recommended eb01 as other odin packages cause bad music quality.), and let the phone boot up.
Next, pull the battery and go back into download mode. Odin one of times_infinity's cwm packages. Then replace the battery and boot straight into CWM. Wipe data, cache, and dalbik and then flash community rom 1.3. IMMEDIATELY AFTER (meaning in the same cwm as when you flashed comm rom 1.3) flash the imnuts kernel that you put on your sdcard. Phone should boot up fine and be fully functional. As mentioned earlier by someone, dont restore system data with titanium backup.
It's not just the system data that is causing issues, as I have tried it both ways, and of course, only restoring system data that is labeled green when attempting to do so. And, it did work previously on EF 3.5.1 but no longer does. I'll give it another shot using thefunkbot's directions. Still confused as to why EF is the only rom that boots normally.
Alright, so that did get Com Rom running. I had actually tried that method before, but it took so long on the Samsung screen that I was sure that it was froze. I just let it go this time, and after about 5 minutes it finally started. None on the other roms I tried took that long, but whatever works...
that's probably due to voodoo, which takes about that time to install/initiate.
Yea, you can hear the creepy robot lady telling you what's going on, but it took a couple of minutes after that even. Also, I skipped Titanium and restored the apps manually. Some were from my SD card and some from the Market, and only about half of them worked after rebooting. Meh
Flash com rom, then flash the otb kernel. Comrom will boot and you will enjoy your phone.
I got Com Rom to boot, but alot of the apps won't reinstall without force closing after rebooting. Not being able to use Titanium is a major PITA to me. But it's not just Com Rom, it's EF, and even the stock rom. Just never had an issue with it before now. But even installing apps through the Market or from the SD card also created issues, so I dunno what is going on.
If you're getting a **** ton of FCs, try fixing permissions via Terminal Emulator. Run 'fxpms' and it *should* solve some FC issues. Also, the phone generally takes much longer than a couple minutes to boot up after doing a full wipe, because the dalvik cache has to be rebuilt. Guarantee that if you had just left the phone alone the first time it was stuck on the Samsung screen, it would've booted just fine.
There are many guides that should help if you run into problems. First odin back to stock update to get new modem (doesn't have to be the newest but might a well), use the pit as well. Second odin cwm. Then flash kern and rom with a voodoo conversion if desired.
At first don't restore any backups. Don't use any themes. Or make any other changes until you see how out runs. Also don't play with the under volting until you've used it a while.
After running it awhile "stock" a it were then start making your changes one by one. This way at least you will know what its causing the trouble.
That happened to me as well when flashed com rom. I took 3 batt pulls before I just let it go to find it was working all along just took its sweet time on first boot. Was not voodoo here. I also agree with your charger problem, but for me its reversed, only happens on the car charger. And I hate to say it but no froyo rom, stock or otherwise, plays nice with my fascinate. I get all kinds of weird bugs. And battery life got worse. Since I have come to the realization that no fascinate aosp or cm rom will ever have bluetooth headset support, I finally threw in the towel and spent an hour on the phone with verizon to get an upgrade. Sad but after all this time it was time to give up.
Sent from my SCH-I500 using XDA App
Wiping Davlik causes unusually long boot times on Froyo ROMs on the Fascinate. If you just wait it out (if it's more than 15 minutes, though, something's wrong) you should be golden. By the way, PBJ 5/23 is literally a non-starter, so I would suggest nemesis2all's OTB kernel until imnuts updates.
Another Fascinating post by my XDA app...
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
es0tericcha0s said:
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
Click to expand...
Click to collapse
Blackhole 4.4? Or an earlier version? I miss SonOfSkywalker's work since he added the Thunderbolt to his arsenal (he also devs for the Vibrant)
Another Fascinating post by my XDA app...
4.4. Haven't had any issues with it so far. Battery life is probably not the best so far it seems, however I don't even care at this stage as long as everything works. I also have not run it down and reset the battery or played with many settings yet so not ready to say it is the rom or anything of the sort. Everyone has their deal breakers with their phone, and not having Titanium work is one of my biggest things. I love that app. I didn't donate for it to not use it, you know? I'm a themer, and I have a lot of themed apps saved with it that makes the Market pretty much useless to reinstall stuff for me. Plus it is an easy way to uninstall system apps without screwing anything else up.
Hey everyone.
I would appreciate some help or suggestions. Maybe someone will know the problem, which I can't seem to figure out. First thing first, I couldn't post in the release thread because I don't have the proper post count.
Anyways, I am not new to installing ROMs on my phone. I can install and run CyanogenMOD easily, and have done so many times. My phone is rooted. So I went from the stock ROM on the MyTouch 4G to CyanogenMOD 7, with no problems. I used it for a while, and then when I saw Virtuous Fusion come out, I wanted that installed. I had tons of trouble getting it to work, even though I was doing everything I was supposed to do. Reset my phone, cleared all caches and data, pretty much cleared everything out. I tried installing from the zip several times in clockwork recovery, and it wouldn't get me past the boot screen. The boot screen would either loop forever, and never get past it, or the boot screen would load up for 3 seconds and then the screen would go completely black (in a state where it looked like the phone turned off).
Eventually, after about the 10th install (which were done all the same exact way), the Fusion ROM decided to work on me and everything went perfectly. This was the first day it was released. I saw the ROM has been through some updates, so I decided to do the recommended clean install of the new version. I am having the same problem as I did before with the boot screen. I temporarily flashed Cyanogenmod so I can have a working phone again, but I would really like to be on Fusion. My favorite ROM out of all the ones I have tried. Does anyone know what could be causing this?
What version of ClockworkMod are you using? Make sure you're on 3.0.2.4 to insure ultimate reliability. Also verify the MD5 hash that eViL provides before flashing. Not doing so means you could have any number of problems caused by a corrupt file download.
Are you rebooting into ROM MANAGER. This ROM is not suppose to be loaded while in the Android OS.