Related
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
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?
I think I've made a fairly large mistake going from MIUI to Darkys.
I was on MIUI v3 (based on CM7) for a short while, but wanted to try something else. I chose to try Darky's v10.1.
I opened ODIN, and chose to flash a 512 pit along with Ficeto's JVH rom (in accordance to this guide). After doing this, my phone is stuck in a bootloop of showing Samsung Galaxy S GT-i9000 screen.
I can still access Download Mode, and my Recovery Menu is very limited (restart, wipe/factory reset, wipe cache partition). I've tried all of those but am not sure what to do to get my phone back on its feet again.
Any help is greatly appreciated!
Download any stock firmware or EZBase.
I have a stock Froyo ROM (Full UGJH2 including SBL) that I tried flashing with a 512 pit but it is still stuck in a boot loop. Actually, now it is showing the Galaxy S GT-i9000 white lettering, then turning off completely.
I fear that I have forgotten to disable the lagfix before flashing with ODIN, however, I never applied one...unless it is applied by default, and has to be specifically removed.
After flashing Ficeto's JVH I get this info in Recovery 3E...
Reboot system now
Apple Update from SD card
wipe data/factory reset
wipe cache partition
-- Copying media files...
E:failed to mount /sdcard (file exists)
E:copy_dbdata_media: Can't mount /sdcard
your storage not prepared yet, please use UI menu
for format and reboot actions
--Wiping data...
Formatting /data...
E:format_volume:rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed
Click to expand...
Click to collapse
Your probably best to go to the Ezbase thread(just search it), download the 3 files for either 2.0(Froyo) or 3.0(GB) depending on what you want, the Ezodin and Ezpit, flash using the guide there and start fresh. Let me know if it works!
Thanks for the recommendation! I've made some progress in Flashing EZbase 2.2.
When I try to reboot the phone however, I am still stuck in a boot loop of white Galaxy S GT-i9000 letters.
I now have access to an advanced recover menu ClockworkMod Recovery v2.5.1.0 SOK ULFK. I've checked my lagfix options, all of them say ENABLE LAGFIX: Convert to xxxxxxxxxx. I'm assuming this at least means that none are currently ENABLED, as I don't have the option to disable any of them. I'm looking at an option called CONVERT, where I can choose to convert my filesystem....Should I select one of the following?
Convert to EXT4
Convert to JFS
Convert to EXT2
Convert to RFS
When I try to access Install ZIP from SD Card it tells me E:Can't mount /dev/block/mmcblk0p1 and E:Can't mount /mnt/sdcard . Is this the source of my problems?
Well, I've been flashing various combinations of pits and roms for the past 3 or 4 hours. I'm not exactly sure what did the trick, I was not able to mount or format my internal SD at all. But, after several attempts at the EZBase ROM, followed by trying to flash to 2.1, finally worked. I got into my UI in 2.1, poked around for a second, and then flashed to Ficeto's JVH which worked.
I've now wiped the device and installed Darky's 10.1 JVH successfully. I wish I had a more detailed answer to how I did it exactly, it was quite a crap-shoot
Nice to see you got it going, don't know why EZbase didn't work straight away.
Hey guys here is my story:
I flashed my captivate i896 with cyanogenmod cm7 then tried to flash back to stock with a 2.3.4 rom and checked repartition by mistake...after that the mmcblk partition that recognizes all the media in my cellphone was gone, so it doesn`t reads any sd (internal storage, movinand or external sds), it shows unavailable space with internal 16gb, external sds and 0.0k with internal storage.
I have tried to flash with many roms. The only one that could actually boot the phone was a recovery image of i897 speedmode with CWM, but still can recover the deleted partitions. I went into CWM recovery to try to mount or format them, but it doesn't let me.
In conclusion, I though that maybe flashing movinand and emmc files using heimdall could repair my cellphone, I been looking everywhere for information about flashing this files, but couldn't find the files or usufull information about it. I hope someone here can help me.
link to recovery image:
http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide
All you need to do is flash a stock ROM, from Odin or Heimdall, and a pit file. If you want to use Odin to repartition, it's as easy as loading a pit file in the pit slot, then check repartition. If you want to use Heimdall, you will need to be on Linux instead of windows. If you can use the Odin one click jf6 by designgears(not all phones can use it), it will repartition for you.
I already tried that with no luck, because after flashing back to stock the cellphone can't read the sd so it shows me the following message:
E:Failed to mount...
depending on the build number of your phone, which hopefully its an early build, this should work for you. http://forum.xda-developers.com/showthread.php?t=731989
Did it with no luck.
Hi guys, I keep looking everywhere but haven't g found a way to format the internal storage, no even a low level format
Low level format
michaelsucno said:
Hi guys, I keep looking everywhere but haven't g found a way to format the internal storage, no even a low level format
Click to expand...
Click to collapse
Any resolution to this.. I have the same issue and have tried numerous re-flashes with BL and w/o.. with PIT repartition and several different roms.. all to no avail.
I installed corn kernel and its running fine and I found out that it is lagfix enabled.........just one doubt ....do I need to disable lagfix before flashing any roms? if so how to disable it ....I can see rfs and ext4 in cwm what are these?
which Corn version are you running?
I run 7.0a and by default, it has no lagfix. don't need it afaik.
rfs and ext4 are different types of linux file systems that are used to store data in partitions on your phone. my phone had froyo os with rfs partitions when I bought it new. It still has rfs partitions with Corn 7.0a GB KK4.
If you are messing around with file partitions in cwm recovery, just remember that any change from rfs to ext4 will completely reformat the partition and you will lose any data on it.
If you flash ICS or JB, you are going to an ext4 file system.
goes without saying: backup everything with cwm and a backup app like titanium bu, then copy all of it to an external sd, computer or cloud. if on sd, remove it before flashing, to be safe.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
laughingT said:
which Corn version are you running?
I run 7.0a and by default, it has no lagfix. don't need it afaik.
rfs and ext4 are different types of linux file systems that are used to store data in partitions on your phone. my phone had froyo os with rfs partitions when I bought it new. It still has rfs partitions with Corn 7.0a GB KK4.
If you are messing around with file partitions in cwm recovery, just remember that any change from rfs to ext4 will completely reformat the partition and you will lose any data on it.
If you flash ICS or JB, you are going to an ext4 file system.
goes without saying: backup everything with cwm and a backup app like titanium bu, then copy all of it to an external sd, computer or cloud. if on sd, remove it before flashing, to be safe.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
I'm 7.0 A btw ......thanks for reply it was booting up pretty fastly so I thought it has lagfix enabled .....if it doesn't have lagfix then I can flash ics roms directly without problems rite
The Ext 4 is not enabled by default in the Corn Kernels.
And Yep...flash away.
Sent from my SGH-I897 using xda premium