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
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.
Hi,
Sorry guys need to ask. I have checked out the forums and i think this hasnt been asked before. Again sincere apologies if it has.
I am using an incredible s, just got it s-off and rooted and was about to flash Android Revolution HD from my sd card.
As part of the process I had to flash 4XT recovery which I have.
I just need to check, whenever I go into recovery is says the following :
"You currently have some EXT3 partitions ->If you wipe/format. I will use EXT3 You can however explicitly wipe EXT4 by visiting the "ext" <-> ext menu
If you are on an EXT4 Rom, you may want to conver the partitions to EXT4. Open the ext3 <-> ext4 menu to do that"
I know I will have to flash a wipe file before flashing the new rom.
Do I need to do anything to address the details above or can I just contiune as normal?
Sorry my first time tinkering with an Android phone.
THanks
You should wipe and convert all partitions to EXT4 before flashing the new ROM.
doctorsax said:
You should wipe and convert all partitions to EXT4 before flashing the new ROM.
Click to expand...
Click to collapse
Thanks, the wipe will be done through flashing the file "Android_Revolution_HD_Super_Wipe" am I corrent?
Also, how do I convert the partitions? I read some threads where people bricked their phones by playing around with the Partitions on the SD card. Not sure if this would mess me up as well
Any insight?
You don't have to wipe or convert! Just flash super_wipe.zip you mentioned, it will do everything for you. It cannot be easier
Thanks, it worked perfectly, running Android Revolution HS with the sense 3.0 all in one patch
Sent from my HTC Incredible S using XDA App
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
Hi, just reporting my findings on F2FS,
To use system partition in F2FS you need to convert rom, adjust scripts, etc.. so i was trying to find if it worth the hassle
Let's take in consideration two things:
1. F2FS have consistently better write speeds than EXT4 , but the same cant be said for read speeds.
2. EXT4 can become laggy when not trimmed, F2FS is always trimmed,
F2FS makes sense for /data and /cache partition but not for /system... /system partition have almost no changes so its 99% trimmed and usually read only
i used this app https://play.google.com/store/apps/details?id=vog.com.aiv to benchmark bootup time in seconds
CM11 2305 nightly, /data and /cache in F2FS , only change is /system partition format (less is better)
ext4
32,06
28,55
28,01
28,13
27,08
27,77
f2fs
27,44
28,65
40,91
36,95
28,29
27,46
28,41
thanks for showing, but i still prefer using f2fs on system because some files in /system get called all time(i.e framework-res.apk),but its not that difference, our nand is already fast.
Even if it is not so good, it is still a step in the right direction.
I will probably try it at some point.
DZeros said:
Even if it is not so good, it is still a step in the right direction.
I will probably try it at some point.
Click to expand...
Click to collapse
F2fs is good, I'm using it, but Just for partitions with lots of writing operations only, simple as that.
And the big plus is that i don't need to worry with compatible roms and updates, just flash any rom updates, without any conversion, and flash kernel after..
Enviado de meu Nexus 4 usando Tapatalk
opssemnik said:
thanks for showing, but i still prefer using f2fs on system because some files in /system get called all time(i.e framework-res.apk),but its not that difference, our nand is already fast.
Click to expand...
Click to collapse
Read times for /system are not faster in f2fs, but it's up to you
Enviado de meu Nexus 4 usando Tapatalk
Thank you for pin pointing this out. A lot of people still believe F2FS will make their phones fly for some reason. I've tested a phone with F2FS next to another running EXT4 and there was no real world performance boost or anything of that sort. F2FS got higher benchmark scores. That's it. Its no a placebo effect but in real world performance it makes no difference.
Sent from my Nexus 4 using XDA Premium 4 mobile app
So, i'm on full F2FS. And i agree with your post. Is there anything i must do to use system as EXT4 or just flash not-f2fs-rom ?
This would explain why there is now a longer than normal delay every single time when I hit the home button that is not noticeable when system is ext4. When on ext4 system this delay was hardly noticeable and with f2fs it seems like there is lag but as soon as it does go home I can then open the app drawer immediately with no lag whatsoever. If it was normally slow or laggy to go home then it took an equal amount of time to open app drawer as the lag existed everywhere, here it is only on the home button.
okanb3 said:
So, i'm on full F2FS. And i agree with your post. Is there anything i must do to use system as EXT4 or just flash not-f2fs-rom ?
Click to expand...
Click to collapse
flash any rom, and then flash one of those jolinard f2fs kernels with filename ending in auto.. they work with any partition layout!
diogo.sena said:
flash any rom, and then flash one of those jolinard f2fs kernels with filename ending in auto.. they work with any partition layout!
Click to expand...
Click to collapse
There must be another way, with this method,the rom doesnt boot.
ashishv said:
There must be another way, with this method,the rom doesnt boot.
Click to expand...
Click to collapse
What rom and what kernel exactly did you use?
diogo.sena said:
What rom and what kernel exactly did you use?
Click to expand...
Click to collapse
I flashed velocity rom, rebooted into recovery again and flashed franko kernel 208 f2fs. The phone didnt get past boot logo.
Then i formatted system, flashed velocity ext4 again, this time without installing kernel. Surprisingly, the rom booted, but the phone was asking password to decrypt storage, ehich left it unusable. So i tried to go back to f2fs rom by formatting system and lashing f2fs velocity, but here again the phone didnt boot past the boot screeen. Finally i had to flash formatpartitions.zip , followed by flashing f2fs velocity, and finally the rom booted. BTW my phone was off for 2 days because of this lol.:laugh:
ashishv said:
I flashed velocity rom, rebooted into recovery again and flashed franko kernel 208 f2fs. The phone didnt get past boot logo.
Then i formatted system, flashed velocity ext4 again, this time without installing kernel. Surprisingly, the rom booted, but the phone was asking password to decrypt storage, ehich left it unusable. So i tried to go back to f2fs rom by formatting system and lashing f2fs velocity, but here again the phone didnt boot past the boot screeen. Finally i had to flash formatpartitions.zip , followed by flashing f2fs velocity, and finally the rom booted. BTW my phone was off for 2 days because of this lol.:laugh:
Click to expand...
Click to collapse
Well, at least you solve it, but next time, try to use twrp from multirom thread instead of flashing fromatpartitions.zip, there's a feature to change back and forth between ext4 and f2fs for any desired partition, and use franco from this link
http://mirror.lnx.im/android/mako/franco/
( i used semaphore auto version, but it should work the same way for franco )
diogo.sena said:
Well, at least you solve it, but next time, try to use twrp from multirom thread instead of flashing fromatpartitions.zip, there's a feature to change back and forth between ext4 and f2fs for any desired partition, and use franco from this link
http://mirror.lnx.im/android/mako/franco/
( i used semaphore auto version, but it should work the same way for franco )
Click to expand...
Click to collapse
Twrp with ext4/f2fs format option for mako
http://d-h.st/g59
Multirom app, which will install the recovery without fastboot.
https://play.google.com/store/apps/details?id=com.tassadar.multirommgr