Database Info

Need help loading rom eclair?

hello, I'm Spanish so excuse my bad English.
I'm trying to load some rom eclair and no I finished the installation,
error busybox sys,
and all abortions.
I checked the integrity of the downloaded rom.
I have recovery: 1.6.2g. that screenshot is old
here a screenshot of the error:

The following observations were made by me :
1: Wrong Forum
2: Minimal information provided by Original Poster
To assist you i need more information such as your radio/spl and what rom it is you are trying to flash.
Since english isnt your native language, guys dont flame the guy plz.

apology for the location on forum
spl: original htc g1
rom: SuperEclair v8.2 (htcmania) and SuperEclair v3.0 (xda-developers)

Ok i would re-download the rom just to be sure no corruption has occured.
Then i would do a phone wipe.
Then i would backup my information on my sdcard and create an ext partition
Then i would flash this rom.

Daneshm90 said:
Ok i would re-download the rom just to be sure no corruption has occured.
Then i would do a phone wipe.
Then i would backup my information on my sdcard and create an ext partition
Then i would flash this rom.
Click to expand...
Click to collapse
room tested with sha1, correct code, downloaded two times
wipe: all, the five wipe.
sd: partitioned into ext3, swap, fat32 (without deleting content for:fat32 loading rom)

I found this on their thread. Try it
+ boot into recovery
+ Wipe everything (data, dalvik, ext, batt stats, rotation)
+ partition sd (96/128 swap, 512/1024/whatever you want, rest fat)
+ repair ext
+ ext2 to ext 3
+ ext 3 to ext4
+ Put rom sd (toggle MS)
+ wipe data and dalvik again
+ flash zip from sd
+ reboot system
Click to expand...
Click to collapse

Daneshm90 said:
Ok i would re-download the rom just to be sure no corruption has occured.
Then i would do a phone wipe.
Then i would backup my information on my sdcard and create an ext partition
Then i would flash this rom.
Click to expand...
Click to collapse
Daneshm90 said:
I found this on their thread. Try it
Click to expand...
Click to collapse
now I do.
question:
repairing ext. that achievement? returns since ext3 to ext2?

ext repairing fixes any file access issues u get from switching roms. Just do as it says.

Daneshm90 said:
ext repairing fixes any file access issues u get from switching roms. Just do as it says.
Click to expand...
Click to collapse
Indeed the steps!.
error screenshot:

K that error i remember seeing when i had the wrong spl. So it seems as though you need danger spl for his rom or you could use firerat's patches to make it work on stock spl

Daneshm90 said:
K that error i remember seeing when i had the wrong spl. So it seems as though you need danger spl for his rom or you could use firerat's patches to make it work on stock spl
Click to expand...
Click to collapse
I would like to retain the original spl. by the break.

Ok try this.
Flash the rom, when u get the error flash again. Dont reboot or do anything just flash again.

I just flashed on my phone with stock spl and it worked.
So its something wrong with urs.

Daneshm90 said:
Ok try this.
Flash the rom, when u get the error flash again. Dont reboot or do anything just flash again.
Click to expand...
Click to collapse
hise what I intended.
update the rom, error.
new charge, without rebooting. and error. :S

elfasito said:
hise what I intended.
update the rom, error.
new charge, without rebooting. and error. :S
Click to expand...
Click to collapse
Are you sure you are downloading it without any corruptions because it sounds like you are downloading bad files left and right??? I just re downloaded and flashed and worked fine...
You need EXT 4 for some reason but that isn't the problem when your flashing your missing files try re downloading in a new browser like Firefox or Opera

Somthing like this happened to me one time after flasing an eclair rom. I couldn't restore nandroid ("error: try running nandroid from adb" blah blah), and if i wiped and flashed it wouldn't get past splash screen. I finally flashed super d OVER an eclair rom, booted up, did sign it, went back to recovery, wiped and reflashed super d, and viola. I think my errors were like his, too.
Edit: HOWEVER! I could reflash the eclair rom and it boot up perfectly. I didn't try a different ROM. So I can't really say if another eclair would have done the same thing.
One more edit: This actually happens to me everytime i flash an eclair rom then try and go back to a donut. that's why i just stay away from them. really like them, just scared one day it wont be fixable.

XxKOLOHExX said:
Are you sure you are downloading it without any corruptions because it sounds like you are downloading bad files left and right??? I just re downloaded and flashed and worked fine...
You need EXT 4 for some reason but that isn't the problem when your flashing your missing files try re downloading in a new browser like Firefox or Opera
Click to expand...
Click to collapse
I assure you that is not corrupt.
and I tried to load 2 different rom.
and also have tested the code with sha1.
if you have time, adjuntame the rom that was downloaded.
use firefox

r3s-rt said:
Somthing like this happened to me one time after flasing an eclair rom. I couldn't restore nandroid ("error: try running nandroid from adb" blah blah), and if i wiped and flashed it wouldn't get past splash screen. I finally flashed super d OVER an eclair rom, booted up, did sign it, went back to recovery, wiped and reflashed super d, and viola. I think my errors were like his, too.
Edit: HOWEVER! I could reflash the eclair rom and it boot up perfectly. I didn't try a different ROM. So I can't really say if another eclair would have done the same thing.
One more edit: This actually happens to me everytime i flash an eclair rom then try and go back to a donut. that's why i just stay away from them. really like them, just scared one day it wont be fixable.
Click to expand...
Click to collapse
I do not understand much, (English)
you could spend the steps or explain a little better?, I would appreciate
edit:I never flash an eclair.
single donut

without error flash this rom: http://forum.xda-developers.com/showthread.php?t=633957
the others give error

help with C7 RC1 installtion

So i have tried for the past few days to get RC1 working on my phone, i cannot get it to work for the life of me, im currently running build 78 on my phone, anytime i flash the new rom, it wont go past the android guy riding the skateboard, and will get stuck at bootloop on the animation, i have tried doing a fresh install, any suggestions?

Build 78? I need 10char

mmmk it says the mod version is "CYANOGENMOD-7-01162011-NIGHTLY-LIBERTY"

Build 78 doesn't even exist, lol.
You've Nandroid-ed your previous install right? Just in case.
Maybe you should try build 43, as if you use RC1, you will have the lockscreen dialer issue.
Try re-downloading the ROM's zip file. You may have got a bad one. (I realize there are MD5 tools out there, but I could never get one to work right.)
Are you are booting into clockworkmod recovery by holding down the down volume button when turning on the phone and selecting recovery? And not when you have the USB plugged in? The usb way does not work right.
Make sure you have factory wiped, wiped cache, and wiped dalvik before installing the zip. (You can use the trackball to navigate recovery fyi)
Don't use a old google apps zip either.
Sent from my Aria - CM7 Build 43

have you tried formatting system seperately after wiping data? as it instructs from the first release of the nightlies? (if i remember right, hah) wipe data/factory reset, wipe cache , then partitions>format system, then flash the zip ?

That hasn't been required for awhile, I believe.
joachim123 said:
have you tried formatting system seperately after wiping data? as it instructs from the first release of the nightlies? (if i remember right, hah) wipe data/factory reset, wipe cache , then partitions>format system, then flash the zip ?
Click to expand...
Click to collapse
Sent from my Aria - CM7 Build 43

Yes, i have nanaroid's backed up, as well downloaded new zip files of everything, at first i assumed it was due to wireless MAYBE that packet was dropped, downloaded it on hard wire just to be safe, fresh zip files, for everything same thing, and i dont boot while plugged into USB

Yes i have tried formatting the system.

Can you flash and boot other roms successfully? CM6 or FR008?
Sent from my Aria - CM7 Build 43

have you ever used Android Commander? i use it for DDMS to try to figure out whats going on sometimes with my phone if its acting weird. im sure itll show up with the error before it loops.

yes, i can flash to any of those w/out any issues, even up to Nightly. of CM7.

While this doesn't fix your issue, could you try a night-
*checks teamdouche*
Never mind. They're gone.
secrethojo said:
yes, i can flash to any of those w/out any issues, even up to Nightly. of CM7.
Click to expand...
Click to collapse
Sent from my Aria - CM7 Build 43

Do you have your phone plugged into the outlet/PC while running Clockwork? Because if you do, well, unplug it and reflash.

OT: MD5 Tool
L551 said:
... (I realize there are MD5 tools out there, but I could never get one to work right.) ...
Click to expand...
Click to collapse
HashTab makes life a bit simpler.
http://implbits.com/Products/HashTab.aspx

[Q] Clockworkmod can't mount /system, error making nandroid

Last night, I decided to try out the Trinity kernel. I downloaded and flashed, and everything went without error. After that, I pushed a custom boot animation over ADB. The first one didn't work, and after the splash screen disappeared it was simply a black screen, but then I pushed one I downloaded from XDA and it was fine.
Now, though, I want to make a nandroid, but CWM is running into some issues. I started the ROM manager app, entered a name for the nandroid as usual, and hit OK, but when it rebooted into nandroid, it gave me an error saying "Error mounting /system" and rebooted back into CM7. That's odd, I thought, I never had any problems like that before. So I rebooted into CWM myself by holding down power+vol down and tried making a nandroid there. No luck. Then I went to mounts and storage and tried to manually mount /system. CWM gave me the error again.
I'm not really sure what's causing this. I thought it might be because now I'm using an ext4 filesystem because of Trinity (right? haha I'm new to kernels and such) and CWM might not support reading it, but if that's the case, I think I would not be the first to have this issue. Yet I searched, on that thread, on Google, on XDA general search, and didn't see anything. I also doubt it's the boot animation.
My last nandroid was yesterday. The only changes to the system I remember right now is that I flashed CM7 nightly 101, then flashed Trinity, rebooted, and flashed the boot animation mentioned. I installed apps since then but none of them had root so I doubt that's it. I would reflash CM7 to overwrite Trinity, but I read on the Trinity thread that if I did that without restoring an old CM7 kernel nandroid first, I'd be stuck in a bootloop because of ext4...?
So, what should I do? I don't want to make anything worse than it already is by tinkering with this myself, I no longer have a current nandroid, that's why I'm asking XDA. Does anyone have an idea why this might be happening? I'm sorry if a thread like this already exists or if this is in the wrong forum (if so mods please move it), this is my first time posting and my search skills could suck (although I looked in all the places I could think of)
Thanks for your help! My G2x is running CM7 nightly 101. Both the nvflashed CWM in recovery and the CWM started by the rom manager app are version 3.0.2.7.

I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App

ritthyhang said:
I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Good, so I'm not the only one! I thought that was too odd to be true.
Here's what I've done. I reflashed cm7 nightly 101 to get my CM kernel back and rebooted. Sure enough, bootloop. Or it never got past the splash screen to the CM7 android skateboard boot animation. I went back in recovery, though, and was able to mount /system. Odd. So I flashed trinity again and tried mounting /system again and no go. So this definitely has something to do with Trinity... I restored my nandroid, reflashed 101,and that's where I am now. Tomorrow, I will make an up-to-date nandroid and do some tinkering to try to figure out what's going on. Maybe it has something to do with the boot animation, maybe not, exactly what's going on is what I am going to try to figure out if no dev shows up here.
Could you give me a few details about your case? Were you coming from cm7 too? Did you do any boot animation tinkering like me?
Sent from my LG-P999 using XDA App

Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App

ritthyhang said:
Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Hmm. So to clarify: You were running MIUI, then you flashed eb followed by trinity. Then, eb 1.7 was released and you went to nandroid, but you couldn't mount /system, so you took the risk and upgraded anyways. The new be came with a new version of superuser, and you were able to make nandroids once again. Is this correct?
One very important question if it is. Did you flash trinity again after flashing the eb 1.7 update?
Also, could I ask what version of superuser came in this update? I am using version 2.3.6.3, which is the latest according to Superuser check for updates, but ROM Manager lists a 3.0 beta version and I'm wondering if you're using that. To check, open Superuser, go to the settings tab, and scroll all the way down. It's the second to last option for me. It's unlikely that superuser is making the difference, since it works as a part of Android and our problem is in recovery, before Android loads, but I can see how it might be possible. If you're using the 3.0 beta, I will flash to that and see if it fixes.
I will look into this some more tomorrow, specifically right now I want to know what filesystem eb's kernel recommends.
Sent from my LG-P999 using XDA App

G2X here same problem.
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?

lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
Update cwm to latest recovery 5.0.2.0 i believe.

fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium

lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
I just stopped using Trinity and went back to the stock CM kernel. I don't think it's just miui, I never used that. But...
fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
squish099 said:
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
YESS! Looks good. I did hear about that. Looks like it's time to give Trinity another try

Error mount/system!
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??

asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
Update your recovery, both, fake and nvflash.

i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.

jblah said:
i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.
Click to expand...
Click to collapse
Where do I find the latest clockwork mod and how do I install it? I currently have a soft bricked phone, and I can't seem to get it unbricked. I tried using the pit files with the stock rom, the dbdata stuff and everything else. What happened was the the system was in ICS, but something happened and I couldn't load into CWM 4 and the system wouldn't boot. So to fix, I used odin to install the stock rom (v2.3.3), but the stock rom came with CWM 3.0, so now I'm at 3.0 and can't mount the file system and it's not booting. I'm assuming that if I upgraded the CWM back to a newer version, I'll be able to restore the system and gain access to the file system again.

reboot problem
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help

Abizer98 said:
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help
Click to expand...
Click to collapse
I'd ask in the samung galaxy forums bud.
"my mind draws lots of blanks actually"

Solution
asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
actually yes. the /system folder is corrupt and it need to be formatted. so all you need to do is format / system then it will work as it should
hope that helps

[Q] phone will not boot after installing any kernel

about a week ago i updated to the newest cm10.1 nightly with gapps 4.2. after flashing those i tried to flash leankernel. my battery was low and the phone turned off when rebooting after the leankernel flash. since then i cannot flash any kernel. i have to do a battery pull to get back into cwm recovery. once in recovery i can wipe data and reinstall cm 10.1 with the standard kernel. i have tried just about every combo of wiping cache, davlik, fix permissions. still not able to flash any kernel. could it have something to do with gapps 4.2 or the phone shutting off mid flash? if so does anyone know how to repair? i already flashed back to stock and rerooted re-unlocked, etc. thanks

and to clarify , it was gapps 4.2.2

Ive found that 3.4 based kernels work with some roms and not with others.
try an older build date its likely not 3.4 based.
or, if your trying a non 3.4 kernel and it wont boot, try a 3.4 kernel.

If you're trying to flash LeanKernel, what's the zip file you're attempting to flash? Also, what are you wiping prior to flashing the kernel?
Sent from my SCH-I535 using xda app-developers app

i tried the mastamoon 3.4 kernel with no luck . the rom i amrunning is the cm-10 nightly 2013-03-24. the leankernel version i am running is lk_s3vzw_aosp_jb42-v2.9. i wipe cache then wipe davlik then flash, it always worked with that procedure before, but since the problem i have tried wiping both after along with fixing permissions. before this issue it was simple as pi, wipe cache, davlik, flash, reboot .

You could always try twrp. Ha. It would make no sense why you couldn't install a kernel.
I would assume since you went back to Odin stock. It would flash factory kernel and give you a clean slate.
So unless cwm is outdated.... ?
Sounds very weird.

actually that is another variable that i didnt think of. cwm updated from 6.0.1 to 6.0.3 or something like that. but then again the original recovery i used after the clean slate was the ez recovery which used 6.0.1 stupid question, but how does twrp work? i always used cwm. i tried flashing twrp but cwm came up when i went to recovery when i tried using twrp?! that was before i did a stock recovery so it couldnt be possible that i am running both? should i delete cwm before i use twrp? if so how? if you dont feel like going into that much detail, i can search it.

i figured out twrp. never gave it achance. ill see if that does the trick

tried twrp. still the same thing going on. gonna go to bed now. ill check back tomorrow after work to see if there are any more ideas. thanks

Problem solved. I went into my internal SD via astro and deleted all old traces of cwm as well as ez unlock and ez recovery. I was getting a generic (showed setting icon instead of regular su icon)super user screen come up prior to that, after deleting those files the regular super user came back. Rebooted into recovery via twrp , cleared cache, Davlik, flashed lean kernel and it worked. What do you think the issue was? Lingering files from ez recovery? That weird su thing?

[Q] No ROMS are working

I have CWM 5.0.2.7. I want to upgrade from 2.3.6 Gingerbread to Android 4(PACMAN ROM preferred). I tried at least 50 - 75 times flashing >5 different ROMS, almost once bricked my phone... I found stable Gingerbread 2.3.6 and I am using it right now. I really want to upgrade to version 4, because I develop apps in Buzztouch and they will now support Android devices with Honeycomb or later. My question now is: how can I really upgrade to Android 4, because every ROM I flash is stuck at the first boot. Any help?

There is absolutely zero possibility of bricking your phone in flashing custom ROMs unless you do it in a wrong way (flashing other phone's ROM ). Same thing goes for bootloop. Wipe data,cache, dalvik cache and even format /system before flashing and also do wipes after flash. This way u can view a new dimension to the android world

swat4samp said:
There is absolutely zero possibility of bricking your phone in flashing custom ROMs unless you do it in a wrong way (flashing other phone's ROM ). Same thing goes for bootloop. Wipe data,cache, dalvik cache and even format /system before flashing and also do wipes after flash. This way u can view a new dimension to the android world
Click to expand...
Click to collapse
I already knew everything you said, even more, but thanks for idea of formatting /system. Maybe that is the main problem. Thank you so much!

UPDATE! Nothing is working. I think I will give up on ROMing.

Lol which baseband are u on? Try to flash latest stock rom ie DXKT7 and then flash a custom rom.

swat4samp said:
Lol which baseband are u on? Try to flash latest stock rom ie DXKT7 and then flash a custom rom.
Click to expand...
Click to collapse
I cannot find any with DXKT7 baseband. I am on XWKTI.

I got the same problem. Flashing from stock 2.3.6 XWKTI to any other cm 10.1 rom is not working. Clearing caches etc. does not help.
Any solution to this?
The latest rom I tried is cm-10.1-20130907-NIGHTLY-beni.zip. No luck so far.
What is wrong here?

Solved. I used the wrong CWM. beni_cwm-5_ext4_v2.tar does the trick.

Junnix said:
Solved. I used the wrong CWM. beni_cwm-5_ext4_v2.tar does the trick.
Click to expand...
Click to collapse
How did you solve the problem?

AleksaSavic said:
How did you solve the problem?
Click to expand...
Click to collapse
Did u ever successfully used ny custom rom b4.. or is this ur 1st chance...??

AleksaSavic said:
How did you solve the problem?
Click to expand...
Click to collapse
The CWM you use might be a one which is not working. At least I used a CWM 5.0.2.7. But it was rfs which is not compatible with the S5670.
So install CWM beni_cwm-5_ext4_v2.tar and you will be able to install any custom rom without problem.

Junnix said:
The CWM you use might be a one which is not working. At least I used a CWM 5.0.2.7. But it was rfs which is not compatible with the S5670.
So install CWM beni_cwm-5_ext4_v2.tar and you will be able to install any custom rom without problem.
Click to expand...
Click to collapse
It is this:
http://forum.xda-developers.com/showthread.php?t=1339640

BRO F U WANT TO UPDATE TO 4.+ THEN FOLLOW THESE STEPS
BOOT TO RECOVERY
WIPE DATA
WIPE CACHE
ADVANCE>>WIPE DALVIK CACHE
MOUNTS AND STORAGE>>FORMAT SYSTEM
INSTALL THE ROM U WANT
WIPE DATA
WIPE CACHE
REBOOT
WAIT FOR 5-10 MINS AS IT TAKS TIME FOR FIRST BOOT
STILL NOT HAPPENING
THEN UR DOWNLOADED FILE MUST BE CORRUPTED SO DOWNLOAD THE FILE AGAIN

Galaxy_Rohit said:
Did u ever successfully used ny custom rom b4.. or is this ur 1st chance...??
Click to expand...
Click to collapse
Flashed custom ROMs at least 75 times. I am not a newbie.

Junnix said:
The CWM you use might be a one which is not working. At least I used a CWM 5.0.2.7. But it was rfs which is not compatible with the S5670.
So install CWM beni_cwm-5_ext4_v2.tar and you will be able to install any custom rom without problem.
Click to expand...
Click to collapse
I already have CWM 5.0.2.7. Can I install it again via Odin or not?

ZmisiS said:
It is this:
http://forum.xda-developers.com/showthread.php?t=1339640
Click to expand...
Click to collapse
I flashed that already(I think).

vinayaksuresh said:
BRO F U WANT TO UPDATE TO 4.+ THEN FOLLOW THESE STEPS
BOOT TO RECOVERY
WIPE DATA
WIPE CACHE
ADVANCE>>WIPE DALVIK CACHE
MOUNTS AND STORAGE>>FORMAT SYSTEM
INSTALL THE ROM U WANT
WIPE DATA
WIPE CACHE
REBOOT
WAIT FOR 5-10 MINS AS IT TAKS TIME FOR FIRST BOOT
STILL NOT HAPPENING
THEN UR DOWNLOADED FILE MUST BE CORRUPTED SO DOWNLOAD THE FILE AGAIN
Click to expand...
Click to collapse
/system - ext4
/data - rfs
/cache - rfs
/db-data - unknown
I am using this apk:
CF-Root-ext4-v1.3-Addon.apk from Chainfire, but it is not made for my phone.
It has options for converting ext4 to rfs and rfs to ext4, but I am scared to do that. How can I manually convert from rfs to ext4? And, will my system even boot after doing that?

Possible solution...
Hi,
I have successfully flashed cm-10.1-20130914-NIGHTLY-beni.zip using ClockWorkMod 6.0.2.7. I initially had problems getting cm 10.1 to boot, it would just stop at the cyanogenmod logo. I got this ROM to work by first flashing ╰☆╮ [ROM][CM7.2] JellyBread v5.0 | SURPRISE! UPLOAD COMPLETE! ╰☆╮. then flashing the nightly.
Good luck:fingers-crossed:.
Regards,
jemail

I wouldn't recommend installing ICS on a Galaxy Fit. The phone doesn't really stand that much of the ROM itself.. I use a rom that'll look exactly alike it, that's basically it. But I tried Lenio vQuattro. it seemed pretty nice If you really need to then try this rom. And it wouldn't be such a bad idea tp update CWM, or try another Recovery.

AleksaSavic said:
/system - ext4
/data - rfs
/cache - rfs
/db-data - unknown
I am using this apk:
CF-Root-ext4-v1.3-Addon.apk from Chainfire, but it is not made for my phone.
It has options for converting ext4 to rfs and rfs to ext4, but I am scared to do that. How can I manually convert from rfs to ext4? And, will my system even boot after doing that?
Click to expand...
Click to collapse
Good question.
I really got no answere to that question. But as far as I know there are CMW for rfs and for ext4/ext3 filesystems.
If you use the wrong CMW than the phone will hang in a boot loop after flashing. That's what I had.
So I suggest you should try different CMW. For rfs and ext4. Better to flash them with Odin. I used Odin_Multi_Downloader_v4.42.exe.
As CWM try: http://forum.xda-developers.com/showpost.php?p=24719114&postcount=1387 or this CWM http://androidlegend.com/dl/beni_cwm-5_ext4_v2.tar
One of these should work for you.