Database Develop

[Q] Muppet in need of Help

Hi,
I've been a right royal idiot and have spent 2 days trying to get my SGS back into working order.
Flashed Bionix v1.7 Rom (didnt realise it was Vibrant), worked great with the exception that the headset socket logic to be back to front. No audio from external speaker, if you plug in headset you could then external speaker started to work.
I therefore flashed back my origonal ROM with ODIN but on reboot the update failed with can't mount /dev/block/mmcblk0p2 on /data (Invalid argument). After then reading the notes (Yep noob mistake) I realised I should have removed the voodoo lagfix the Bionix ROM had before flashing a new rom.
Having done some investigation it looks like mmcblk0p2 is an j4fs filesystem but nothing I seem to do seems able to change that. Tried to mkfs and ext2 filesystem on it but it seems to be working then aborts saying it wasnt cleanly unmounted and to e2fsck the partition, which I try and it errors with unable to set superblocks on /dev/block/mmcblk0p2.
Any and all help greatly appreciated

Find a full rom that have dbdata.rfs, cache.rfs in it. Flash via Odin with repartition ticked.
Sent from my GT-I9000 using XDA App

JM8 will restore the things your missing

I have tried that, Odin runs through with no issues, but on device reboot it errors with the same. I can boot into clockwork recovery and adb shell. Its really weird, I've done a complete dd dev/zero over that partion. I've mounted it in windows and formatted via that and yet when I reboot and look at the partition via windows, all the data is there. There were a couple of other partions that were j4fs (/datadata) if i wipe that partion using fat.format, when i remount it it mounts as rfs instead of j4fs (great), but when I do the same with /data (mmcblk0p2) it says success on format but when I mount, it still mounts as j4fs...any other ideas?

azzledazzle said:
JM8 will restore the things your missing
Click to expand...
Click to collapse
Will try JM8 and let you know
Tried JM8 Odin complete succesfully, on reboot complains about CSC (multicsc : can not access to /system/csc/KOR/system
copy_common_data E:Can't mount /dev/block/stl11 (invalid argument))
cant do anything with stl11 in adb, complains no such device (although /dev/block/stl11 file exists)

I've managed to recover my SGS with a flash of JPU which is a low level package including repartition with 512.PIT. Here's a download link to JPU if it helps. It's a 3 part flash in Odin: http://www.multiupload.com/L79EDKJIG3
Good luck!

bdl1969 said:
I've managed to recover my SGS with a flash of JPU which is a low level package including repartition with 512.PIT. Here's a download link to JPU if it helps. It's a 3 part flash in Odin:
Good luck!
Click to expand...
Click to collapse
Just tried this and error is back to origonal ie cant mount /dev/block/mmcblk0p2.

You didn't accidentally store those files on your Sim or SD card right?
(I know, beginners question but just to be sure )
So you can't use your phone at all atm? Just stuck at recovery screen?

I had this same problem last night in the end used odin 1.7. With older firmware and pit (512) files doing a full repartition and reflash with csc. And modem files this was a jp4 set i believe.
This would not then upgrade in kies so i flashed a jpy firmware over the top just the firmware file this time. Not sure but i think i could have skipped this stage and restored from the clockmod backup. Can anyone confirm?
Then i rooted the phone again then flashed a kernel with clockwork mod support and was able to go to recovery mode and restore with the back up i made before i started messing about, though i suspect a titanium backup or similar would have worked just as well.
Hope this helps you at one point last night all I had was an icon with the phone and a computer thought I had really bricked it this time but given what I've done over the last couple of weeks i am not sure that's even possible.
Sent from my GT-I9000 using XDA App

curioct said:
I had this same problem last night in the end used odin 1.7. With older firmware and pit (512) files doing a full repartition and reflash with csc. And modem files this was a jp4 set i believe.
This would not then upgrade in kies so i flashed a jpy firmware over the top just the firmware file this time. Not sure but i think i could have skipped this stage and restored from the clockmod backup. Can anyone confirm?
Then i rooted the phone again then flashed a kernel with clockwork mod support and was able to go to recovery mode and restore with the back up i made before i started messing about, though i suspect a titanium backup or similar would have worked just as well.
Hope this helps you at one point last night all I had was an icon with the phone and a computer thought I had really bricked it this time but given what I've done over the last couple of weeks i am not sure that's even possible.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Just tried with Odin 1.7, the JP4 romset still the same error on mmcblk0p2.
Just for avoidance of doubt in case I'm not doing this correctly,
In Odin I have Re-Partition, Auto_reboot, and F.Reset Time checked, Dump, Phone EFS and Phone Bootuploader Update are not checked. I'm using s1_odin_20100512.pit, and have tried Various European Roms including all the ones mentioned so far.
Fundamentally is the problem not that the filesystem type of the internal SD partition is j4fs? It seems the kernels dont know how to mount this type of filesystem, and for some reason I seem unable to change this. I cant even delete/format the data in these partitions.
cronoz, I believe mmcblk0 is the internal SD memory, which has 2 partitions. The first is a 2Gb Fat partition and the second is a 5Gb ext4(j4fs) partition.

Try using hardcore's kernel. In recovery mode try to disable lagfix.
Good luck
Sent from my GT-I9000 using XDA App

lownoise said:
Try using hardcore's kernel. In recovery mode try to disable lagfix.
Good luck
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
thanks, can you point me in the right direction maybe a link just to ensure I download the correct file.

It's in the development section.
Thread hardcore speedmod kernel.
Choose first download speedmod....
500.zip
Unzip and flash with odin.
You do have 3 button combo right!
Sent from my GT-I9000 using XDA App

lownoise said:
It's in the development section.
Thread hardcore speedmod kernel.
Choose first download speedmod....
500.zip
Unzip and flash with odin.
You do have 3 button combo right!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yep, dont have any problem getting into Download mode

nivenj said:
Yep, dont have any problem getting into Download mode
Click to expand...
Click to collapse
then it's save to try

Yes the file system is the issue but repartitioning should reset that at lest it did for me last night. But only once i found a complete set of files. A *512.pit mine came with odin the main firmware in the pda box the modem file in the phone box and the csc file in the csc box once i had that mine refreshed just fine. If you have the right combination of those then I'm not sure what else you can do tbh
Sent from my GT-I9000 using XDA App

lownoise said:
It's in the development section.
Thread hardcore speedmod kernel.
Choose first download speedmod....
500.zip
Unzip and flash with odin.
You do have 3 button combo right!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Well this thas put me a lot further forward thats for sure. So i Flashed speedmod-kernel-k13a-500hz.tar. This now bootsl the SGS. It complains bitterly, force closing just about everything, but it does boot. Just about all apps force close, but I can set debugging mode and get in via adb (although the roms not rooted (JP4) :-S).
I can boot into recovery and choose the speedmod Lagfix option. It correctly identifies that /data is ext4. I disable lagfix and the new config is set to convert data to rfs on next reboot. I reboot and it goes through the conversion, backup of /data /datadb and /cache, it then generates md5 checksum and the aborts saying there is not enough space on internal SD. Not sure how to fix this part. When I enable debug mode I can see 2 partitions in windows a 1.8Gb and 5.3Gb, Both are empty apart from my update.zip in the 5.3Gb partition.
EDIT: Also tried the Yes, with factory reset without backup option, this seems to work but on reboot /data is still ext4 :-S
Any other ideas how to proceed now?
Any Full Roms with the speedmod kernel you could recommend?

nivenj said:
Well this thas put me a lot further forward thats for sure. So i Flashed speedmod-kernel-k13a-500hz.tar. This now bootsl the SGS. It complains bitterly, force closing just about everything, but it does boot. Just about all apps force close, but I can set debugging mode and get in via adb (although the roms not rooted (JP4) :-S).
I can boot into recovery and choose the speedmod Lagfix option. It correctly identifies that /data is ext4. I disable lagfix and the new config is set to convert data to rfs on next reboot. I reboot and it goes through the conversion, backup of /data /datadb and /cache, it then generates md5 checksum and the aborts saying there is not enough space on internal SD. Not sure how to fix this part. When I enable debug mode I can see 2 partitions in windows a 1.8Gb and 5.3Gb, Both are empty apart from my update.zip in the 5.3Gb partition.
EDIT: Also tried the Yes, with factory reset without backup option, this seems to work but on reboot /data is still ext4 :-S
Any other ideas how to proceed now?
Any Full Roms with the speedmod kernel you could recommend?
Click to expand...
Click to collapse
you can try darky's resurrection rom which is a complete rom with pit file 502
http://forum.xda-developers.com/showthread.php?t=940671
If that fails you can also try to flash jpy or js3 with the 802 pitfile
hmm i think the 2 partitions are the main problem....... It's kind off strange that you only can see the update.zip. How did you create the 2 partition???

Ive been trying darkys res rom, the only problem I think though is that it does say that lagfix has to be removed (ie not ext4 partitions) before installing, and that I suppose is the underlying problem of why I cant get it to work.
I just realised it wasnt 2 partitions, its the Internal and external SD cards, the 1.8Gb seemed to be corrupt, I managed to format it via the SGS menu and it shows the correct 8Gb now.s
EDIT: Hmmm just noticed something, its seems that although it appears I can delete and add files to my internal SD card via windows, it doesnt actually do anything on the card. This very strange :-S

How to convert partition to ext4 without lagfix?

Hi all, I just find the mount point /data is in ext4, but /cache and /dbdata both still in rfs. Can I umount /cache and /dbdata manually, then run
mke2fs -t ext4 /dev/XXXX
then change fstab, and reboot the phone?

So, what's the point in avoid using any lagfix? As far as I know lagfix will do exactly what you stated in your post, use mke2fs to convert any partition to ext4.
If /cache and /dbdata were not in ext4 maybe the lagfix you used wasn't supossed to convert those.

I already applied lagfix, and it work good, I don't want to apply another lagfix just to fix those 2 mount point.... as I never smooth to get lagfix working..... doing it step by step myself sound better

carfield said:
I already applied lagfix, and it work good, I don't want to apply another lagfix just to fix those 2 mount point.... as I never smooth to get lagfix working..... doing it step by step myself sound better
Click to expand...
Click to collapse
Emm, have you tried speedmode or SO kernels? Essentially it is what you are asking

OK, so what kernel have you flashed?
First, dbdata contains important system data, mke2fs would clear it,
and you would end up with unusable system. And you have no guarantee
that init script of kernel you are using actually cares what's in fstab. It's
best to do this consistently - I sugest to go back to stock FS (rfs),
and then flash Voodoo Kernel. Except for Voodoo Sound and few tweaks,
it's like stock, without useless bloatware. Seems to be fastest according
to Quadrant, too.

dupel said:
Emm, have you tried speedmode or SO kernels? Essentially it is what you are asking
Click to expand...
Click to collapse
Thanks, would you point me to some links about that? Sorry I haven't done good research before.

carfield said:
Thanks, would you point me to some links about that? Sorry I haven't done good research before.
Click to expand...
Click to collapse
Just do some search, that is another lagfix, can I safely apply multiple lagfix to single device? I will search for the lagfix I used when I at home

HI, the lagfix I applied is ZSJP3 , the kernel is I9000ZSJP3-zImage

To be safe, you should remove all previous lagfix first. Afterwards, flash SpeedMod Kernel via Odin. You can find detailed instructions in the speedmod thread. To put it simply, download the Odin file, get Odin off www.samfirmware.com, put the file you downloaded into "phone". Leave everything else untouched and flash. Afterwards, go into recovery to activate the Lagfix options.

snapper.fishes said:
To be safe, you should remove all previous lagfix first. Afterwards, flash SpeedMod Kernel via Odin. You can find detailed instructions in the speedmod thread. To put it simply, download the Odin file, get Odin off www.samfirmware.com, put the file you downloaded into "phone". Leave everything else untouched and flash. Afterwards, go into recovery to activate the Lagfix options.
Click to expand...
Click to collapse
Thanks, but how to remove previous lagfix?

check if data is ext3 or ext4 ?

I want to check if my data and system partitions are ext3 or ext4. Is there a way to do this ?

Easy, just use a terminal/ADB to run the command 'mount'

cheers for that. it seems that if you run the backtoext3 script and then do a nand restore it converts your data back/system to ext4 .

Correct, it's smart like that.

Thanks, was wondering the same thing. I can see that my data and system are ext4 but cache is ext3. Is that ok, shouldn't they all be the same partition?
Sent from my LG-P990 using XDA App

I think I did it correctly, got a lot of text, like 2 screens there was 4 that found ext3 in, /system, /cache, /data, /lgdrm. So I guess the cm7 rc1 im running is using ext3 then? Why isnt cm7 using ext4?
Sent from my Optimus 2X using XDA Premium App

Because once you go EXT4, the only way back to EXT3 involves your data going bye-bye. I believe it was almost done, but RC changed his mind.

was a way to extract files from a nand back so I could push them to my device

Mount the .img on a Linux machine.

help KK4 Samurai kernel

I flash samurai kk4 kernel v1.4.3 and now phone wont boot past att screen..it will boot to recovery.....but it has all kind of mounting errors...it wont mount any partition..am i screwed and need to odin back to stock?

What kernel where you using before hand? Where you on EXT4 before?

seems like a file system problem, as PR said. going from ext4 back to the samsung proprietary filesystem causes the mounting errors because its not formatted like the kernel expects. im not sure if going from the samsung fs to ext4 causes this (i assume it would without formatting), but i know ext4 to samsung does.

Ext4 conversion

Hi guys! I had converted my phone to ext4 and now i wanted to convert it back to rfs because i wanted to flah a new rom and it gave a sort of a format i mean i see the icons, kinda, of the appa i had but it says that the app isn't installed on my phone and no accounts or anything else... Help?
PS: And in ext4 app i have the the option to convert to ext4 and to rfs... Wtf? and when i want to use it to check the integrity of the system it goes to recovery and reboots
Sent from my GT-I9000 using Tapatalk

did you convert fs in recovery?

Slow down. How did you convert it into ext 4 in the first place? If you converted it in recovery using a custom kernel, you should already know how to convert it back into RFS.

I used the ext4 conversion app from chainfire so yes i went into recovery. To convert to ext4 i pressed convert to ext4 went into recovery and for restore i pressed the efs option went into recovery started converting and when i pixked up the phone i saw CWM recovery so i hit reboot. Now i don't know if my system is efs or ext4 since both options are "active" in chainfire's app and when i hit check integriti it goes to recovery starts something and then reboots...
Damn it's hard to type on your phone... since pc is down so sorry for misspels
Sent from my GT-I9000 using Tapatalk