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.
Here is the story. I've got my Vibrant as a replacement for my older one two weeks ago. The old one had a problem with Home button responsiveness and at the end I decided to go with replacement. After some testing with identical firmware (freshly flashed) on both phones I found that the the new one boots much faster - around 12 sec difference (the time my audio widget is fully loaded) and overall I was very happy, until today when my phone screen turn of during some work on the browser. The buttons light was on and the screen became black.
1. I did battery pool. First boot was very slow. Force close for some koush process ( probably clockworkmod) came out .
2. I did 'wipe cache' - multiple force close after that
3. Factory reset - it was somewhat booting very slow and I decided to go with Odin.
I was able to put the phone in downloading mode and flash JFD with repartitioning. Everything looked ok during the process, but after reboot it plays Tmobile animation, startup sound, shows the letter S and stucks there.
I am able to get in stock 2e recovery. If I choose reinstall packages it goes to clockworkmod recovery (I thought clockworkrecovery should disappear after flashing with odin, but it is there) I tried flashing different usb ports - no difference.
The phone was with stock JI6 firmware, rooted with OCLF, ROM Manager with clockworkmod installed. Was working fine till today. I didn't experience any lag issues and neither of the lag fixes were installed or tested.
I played with clockworkmod recovery options format: system, data, sdcard.
I was not able to format boot - some error.
I am not a very good writer... sorry if somebody gets upset.
I will appreciate any help or idea.
Thanks
Fix for your problem
Sounds like some of the rom is either corrupted or the factory reset did not have J i-6 in it.......not enough info. Personal message me and i ll help you fix this problem.
Has anyone else had any problems with ROM Manager? I can't create a backup from ROM Manager. It boots from the M to a triangle, then reboots the current ROM. If I use Bootstrap to boot into Clockwork Recovery, I can create a nandroid backup. I've tried uninstalling/reinstalling, reflashing the ROM(formated system, wiped data & cache) and reinstalled Busybox. Any suggestions??
continue using bootstrap, there are many people with this problem
I was able to use Rom Manager just as you would on any non locked bootloader phone on my original droid X. Now on my replacement one I'm unable to load roms or make backups directly from rom manager, I have to use bootstrap and do it manually. Not a huge deal but it's kind of annoying. I also had problems with other roms though like Rubix focused (the newest) the dialer app would just dissapear and I couldn't connect to a cell tower... really weird. With ApeX I would get random reboots every couple minutes. With FlyX I would get the syncing icon come up and just stay permanently. These were all installed after completely wiping several times and doing fresh installs. Finally ended up trying Tranquility 2.5 I think? Anyway that one worked. I figured my phone was just messed up in some way and that's why I couldn't do things directly from Rom Manager. This phone also occasionally boots up all the way but the display never makes it past the M logo. I can unlock and power off the phone just off memory of where the stuff is at but the screen never initializes. Other than that, runs great! lol
Same problem here. I have to do it manually with bootstrap...pretty annoying.
I used odin, then CWM 3, then flashed to Syndicate Frozen. It seemed to work fine...except that the phone seems sluggish and none of the soft keys or hardware keys work. When I press one, the phone vibrates a few times, then shows this android logo put on by syndicate, and seems to reset the OS. The touchscreen seems to work fine.
I don't know if this is an issue with the rom, cwm, or something I did wrong. Can anyone advice?
Bad flash. Wipe data and flash again, and if you continue to have problems, use Odin to go back to EB13. Still having problems? Format your SD card, redownload the ROM, and flash.
EDIT: HEYO! 1,000th post.
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.