[Q] Problem ext4 to rfs - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi guys!
I used CF-root ext4.apk to pass from ext4 to rfs (SAUROM JW8). Now I want to go back to rfs, but when the phone reboot into CWM recovery nothing happens!!!!
I re-installed the apk, and nothing. I flashed lots of roms on several devices (odin, CWM, etc.) but never had this problem before. Maybe is a problem with the free space in the system? I do not know, I did not find any answer looking in the internet
Any ideas? Thansk!:good:

Related

[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

[Q] MIUI to Darkys problem

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.

[Q] Please Help - lagfix error ext4 > rfs

Hi guys,
My sgs is running stock android 2.3.5 (JVT) and I had rooted it using cf-root and applied lagfix (ext4).
I wanted to apply the ICS custom rom, and that required me to convert back to rfs from ext4 (remove lagfix?)
I also saw that I needed cwm recovery so I downloaded the cwm rom manager shortly before attempting to convert back.
I don't know what has happened - but when it converted back to RFS and my sgs booted up - all my apps are gone except for a handful!! It says that nearly all of them are on the SD (missing icons) - clicking on them says application not found. Even the market and superuser has disappeared but "cmw", "tweaks" and "ext4" are still there!
I think using the ext4 manager - it may have booted into recovery mode using cwm and this has screwed something up.
I've tried unmounting and remounting my external memory card and restarting my phone, but to no avail
I've just rebooted into cwm recovery mode (v3.0.0.5) and it says checking for ext4 partitions........... does this mean that the conversion was not successful!!?
What should I do? I have stuff on my phone I don't want to lose and I want to get my apps back.
Not sure what to do right now... please help! By the way, it's my birthday tomorrow and a solution would be a really nice present
Thanks guys.

[Q] My i9000 "gets stuck" while booting, flashing doesn't help

Dear all, I tried now for two full days to resurrect my i9000, with no success so far. I hope one of you can give me a hint where my problem/error lies.
A bit of background: The phone was bought without a contract (no branding) and with android 2.2 (or 2.1?) installed. Afterwards I upgraded to ginger bread with kies, all worked fine for months.
The day before yesterday (after I installed and updated some apps) the phone was quite slow, so I wanted to reboot it. The booting was looped for a couple of times, and as it made it finally to boot, it was almost not reacting anymore. I uninstalled the apps I recently installed and then the phone froze. Now the phone wasn't able to exit the boot loop anymore. I searched this and other forums and learned about recovery mode, download mode, flashing and bootloaders and all these things. And indeed, in the recovery mode, there was an error:
Code:
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet, please UI menu for format and reboot actions
Media files copy failed.
Finally I convinced myself, that simply - for what ever reason - android needs to be reinstalled. Long story short: I tried different versions (from 2.1 to 2.3.6) with bootloader, with 1 or 3 files, with different versions of Odin3 (1.7, 1.82, 1.85), with or without repartitioning (pit files 214 [EDIT:I meant 512!] and 803, the later succeded as well, but gave me error messages in the recovery mode). All with the same outcome: Now the phone boots up to the blinking S logo ("splash screen"?), and stays there forever (2h+), while the S is not stuck, but blinks and turns b/w in circles. I let it do this over the last night (connected to my laptop, so it would not decharge) and the next morning it was off, so I guess at some point after 2 hrs it gave up. I found a couple of comparable posts, but my situation I found no where... (not really a boot "loop", neither gets it stuck, but can't complete booting plus wiping and/or flashing, no matter which version, seems not to help).
If any one kept on reading until here and knows something that might help (and/or that I have overlooked so far) I would be more than grateful for a hint!
Thanks a lot!
try flashing the 2.3.5 JVT Firmware with 512.pit and repart. I do not know any firmware which uses those strange .pit files you used(except one or two very old Fimrwares which are using the 803.pit file).. If the phone doesn't boot after doing that you can try formatting your SD in recovery. According to that Errormessage you get in Recovery it could be possible that something is wrong with yout internal Memory. Formatting the internal Memory could solve your problem. After doing both your Galaxy might boot again. If not it could be an Hardwareissue too. In this case just flash the latest official Firmware and send it to samsung and let them repair ist Attantion: All Files like pictures, videos or whatever on your Internal-Memory will be deleted if you format your internal memory!(that apps are deleted after flashing schould be known by everyone )
Detailed method given here
Detailed method given here
http://forum.xda-developers.com/showthread.php?t=846913
use the tutorial to boot to stock firmware, this should put your phone back in business....
no success
Thank you two for your fast answer!
Unfortunately it didn't do the trick
As I wrote 214 I meant the "normal" 512 pit file (d'oh!), sorry for that, orangerot.
I noticed something strange: I left the phone turned off for some hours today, and after the reboot there was again the boot loop I had in the very beginning (until the white Logo), and going to recovery mode there was an error:
Code:
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media: Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
I tried a wipe that led me to the following:
Code:
-- Wiping data...
Formatting /data...
E:format_volume rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
asking google for that I found a thread (in german) on handy-faq.de (samsung_i9000_galaxy_s_forum/225311-geraet_gewiped_bootschleife), in which the contributors came to the conclusion the only way would be (and was in the end) the samsung repair service.
Interesting is, that after a reboot I was again at the same position as before (glowing S) and no error message in the recovery mode. From this starting point I tried again to flash (with JVT, 512.pit through Odin3 v1.85, as you suggested), with no visible change of behaviour: still booting only until the glowing S, no error in recovery mode, wiping doesn't help but finishes without error.
If anyone has some additional idea I would appreciate to hear about, otherwise I guess I try to flash an official Android version (any idea how to find out which is the most recent official version updatable from kies?), and bring it to the samsung partner.
Thanks a lot!
I have had athat happen before, try flashing darky's resurrection edition via odin. It worked for me.
Here: http://www.darkyrom.com/community/index.php?threads/odin-darkys-resurrection-edition-10-1-gt-i9000-only-for-now.3237/
still not recovered
Thank you, B1-P,
but unfortunately it didn't work. Odin quitted with green "pass" and "succeed", but after the first reboot afterwards it ended in recovery mode with following errors:
Code:
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
E:format_volume: rfs format failed on /dev/block/stl10
Formatting /cache...
E:format_volume: rfs format failed on /dev/block/stl11
Deleting Meta Data
Data wipe failed.
boronian said:
Thank you, B1-P,
but unfortunately it didn't work. Odin quitted with green "pass" and "succeed", but after the first reboot afterwards it ended in recovery mode with following errors:
Code:
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
E:format_volume: rfs format failed on /dev/block/stl10
Formatting /cache...
E:format_volume: rfs format failed on /dev/block/stl11
Deleting Meta Data
Data wipe failed.
Click to expand...
Click to collapse
Ahh man...
Okay, there are a couple of more things you can do,
1. Try darky resurrection rom V9.2 (I think your issues maybe due to some lagfix problems/mounting filesystem incorrectly etc.) Try the 9.2 in odin, make sure that you have checked the "Repartition" as ON and have a PDA and a PIT file selected.
http://www.darkyrom.com/community/index.php?threads/odin-rom-darkys-resurrection-edition-9-2.895/
2. And if the Darky rom 9.2 does not work, then this thread is your best shot (you will need at least some linux experience for this to be helpful):
http://forum.xda-developers.com/showthread.php?t=845708
If all that doesn't work, then I don't know what will.... I'm sorry.. I don't know what else you could do. Try a repair centre as a last resort I guess.
Did you try to format your internal sd? Wiping and formatting are two diffrent things.. And in your logs I only see that you are wiping your data.. So just try formatting your internal sd. i think you will find it under "mounts and storages" in cwm. I've read before that this may help to solve this problem. if this does not help it could be that your internal sd is broken. In this case you have to send it to the samsung repairservice. but make sure you flash the official JVI firmware to remove the clockworkmod, so they cannot see that you have flashed your mobile cause if the recognize it they may refuse tu repair your mobile
Try darky resurrection rom V9.2
[...]
And if the Darky rom 9.2 does not work, then this thread is your best shot (you will need at least some linux experience for this to be helpful)
Click to expand...
Click to collapse
After I installed Darky's resurrection 10.1 I had troubles to get in recovery mode... and loads of errors the few times I managed... last attempts didn't bring me to the modified but the "original" recovery menu. I think I don't dare to try Darky's ROM 9.2 after this experience. And for messing around with EXT4 and Linux I don't feel ready at all, thanks though for the link! Now I am back on a stock version and again the old picture.
Did you try to format your internal sd?
Click to expand...
Click to collapse
I thought when I use the pit file and check the repartition box it will reformat the internal sd?? If not... this cwm... I didn't quite get what exactly it is. Isn't it an android app? How can I use it, when I am not able to boot?
And then: is JVI and JV1 the same? If not where is the difference?
Thanks again! (And sorry if my questions are silly)
No, repart only reparts the system partition off the phone. the internal and external SD are not going to be formatted while reparting. If it would behave like that all your photos, videos, folders and so one would have been deleted. Apps are deleted because they are saved on the system-partition.
CWM is a recovery which has some more features than the stockrecovery. You get it with flashing a CustomRom(they usually all have CWM) or an CustomKernel(e.g. CF-Root, Semaphore etc.).
You can acces CWM by holding Vol-up+homebutton+powerbutton at boot and release them when the Galaxy GT-I9000 screen appears. Its just like getting into the Downloadmode but instead of pressing vol- you have to press vol+. Once you are in CWM you navigate to mounts and storages(with vol-up/vol-down you can go up/down and with the powerbutton you select an option) and format your internal sd there. After that everything may be fine again If not you have to send it to the samsung-repair-service after flashing the official JVI-firmware to delete CWM and so on. JVI and JV1 are not the same.. JVI ist the last official firmware(2.3.3) while JV1 is a leaked, unoffical firmware. So you have to flash JVI befor sending you phone to samsung while JVI ist the last official firmware.
back to life
Dear orangerot, dear B-1P
thanks for your patience!
Then I knew the cwm, I just didn't know it was called that way.
last attempts didn't bring me to the modified but the "original" recovery menu.
Click to expand...
Click to collapse
So the "modified" recovery menu I talked about was the cwm. In the last attempt with Darky's Rom I couldn't get back to that cwm... maybe I released the 3 buttons at the wrong time? Don't know.
However, in the mean time I gave the phone to a service partner of Samsung, and they sent it to Samsung. Today I got it back and everything works again. Unfortunately they didn't give any details on what they did (except for new installation of the OS, which didn't help for me...).
So for me this problem is solved (for now...)
Cheers!

[Q][SOLVED][HELP] /system, /data not mounting

Hey,
I have an i9000 (Obvious) which, I put in the freezer (please don't ask me why). So, the problem is I had put it at a Live OC of 120% and opened antutu benchmark and put it in the freezer. I know that my phone hangs if I open some heavy apps at 120%. So, that is what happened with the phone while benchmarking. So I had to force shutdown and when I turned it on, it first showed me the error of "Process System is not responding". I clicked on wait. Well, the Status Bar wouldn't turn on and I assumed that the System UI was retarded at the moment. So I factory reset and flashed ROMs multiple times. BUT, I lost access to /data and /system. So I tried restoring, and it did Restore but didn't work, same stuff happened.
So, Ultimately I flashed Stock ROM and tried flashing another ROM again but no. No access to /data or /system. I did this multiple times until I realised I have access to /system and /data and am able to mount them via the CF-ROOT Kernel and that the Stock ROM works fine. Please help!
EDIT: I just forgot to format /system and /data before switching from GB to KK

Categories

Resources