Format EFS to ext4 - Galaxy S II Q&A, Help & Troubleshooting

I have a galaxy s2 gt-i9100. My original efs partition was ext4 filesystem, but due to corruption, I reformatted it using SII_Repair. Unfortunately, the tool formatted it to ext2 instead of the original ext4. I have tried to use parted to reformat it, but it only support up to ext2. Are there other ways? How does clockworkmod reformat the other partition to ext4? what is the name of the tool? I can use terminal to reformat efs if only I know the utility name that clockworkmod uses to reformat other system partitions.

Try to flash older 3/4 file firmware with proper PIT file. It will fix partitions and wipe phone. After that format your internal memory card, otherwise it could be still broken

mar10o said:
Try to flash older 3/4 file firmware with proper PIT file. It will fix partitions and wipe phone. After that format your internal memory card, otherwise it could be still broken
Click to expand...
Click to collapse
I have tried flashing PIT which usually reformat everything, but it didn't work for efs partition for some reasons. However, I got it reformatted to ext4 by flashing an efs.img I got from somewhere.

Related

[Q] Clockworkmod and sd-ext

Just installed link2sd earlier (formatted partition as ext3). Wanted to flash a different rom. Trying to backup my phone, and clockworkmod tells me it can't mount sd-ext. Anyone know a reason and/or work around?
I think CWM works only with ext4 partition AFAIK. So, you can re-partition your sd card to a ext4 partition using CWM, or you can format the ext partition only to ext4 using a computer.
YouArePoop said:
Just installed link2sd earlier (formatted partition as ext3). Wanted to flash a different rom. Trying to backup my phone, and clockworkmod tells me it can't mount sd-ext. Anyone know a reason and/or work around?
Click to expand...
Click to collapse
which version of CWM have you got?
3.0.2.4, which I've used for a while now, always tries to back up my 6GB ext2 debian partition unless I remember to change cards first. no way I leave room in the vfat partition to back up that much data.
I'll put it up on 4shared if you want it.
mihir287 said:
I think CWM works only with ext4 partition AFAIK. So, you can re-partition your sd card to a ext4 partition using CWM, or you can format the ext partition only to ext4 using a computer.
Click to expand...
Click to collapse
Guess when I get home I'll copy the contents to computer, reformat, and copy back. Hopefully link2sd will notice the formatting has changed and reset itself
Sent from my LG-VM670 using XDA App
Doesn't work with extra either. Version 3.2.0.1 I believe it was.
Guess it doesn't really matter, can just use titanium since its all app stuff on there anyways...
Sent from my LG-VM670 using XDA App
i use CWM to back up my 512MB ext2 partition for my data2ext all the time (with the rest of the backup) and it seems to have no problem, and just to check i just mounted the partition in mounts and storage and it mounts fine. I know some recoveries ive used in the past on other phones would have problems with partitions that were not in 64-128-256-512-1024 MB, etc. format because of block size issue errors that i would get (when mounting or trying to set block size to 4096). I also found that when partitoning/formatting to ext2/3/4 some programs do not properly write the drive formatting and certain systems/recoveries/apps could not properly read them on the android. the best most consistent (android friendly) formats that i have gotten to date were in ubuntu (or any other) linux using "gparted". It seemed to always be the best and usually better than the format done by the phone recovery. Hope this helps. Sorry to drone on and on.
Partitioned originally with gparted. Have since resized to be 2048, and set its label to 'sd-ext'. Now instead of getting an error saying sd-ext might not be supported on my device, it just gives me a generic 'error mounting sd-ext'
I've had ext partition mounting problems before, I'm not sure if the cause is something to do with vold or what, but
after unmounting a sd card to exchange it with another one, it changes the device partitions in /dev/block like
/dev/block/mmcblk1p2
for the sd-ext partition instead of the normal
/dev/block/mmcblk0p2
you can see if this has happened by
Code:
ls /dev/block
in adb shell.
to mount it manually, if the numbering is off,
Code:
mount /dev/block/mmcblk1p2 /sd-ext
I've only had this happen with android running, but it might work in recovery too
Switched over to using data2ext. Mounts the 2nd partition as the /data partition instead of /sd-ext. Can manually mount 2nd as /sd-ext from within rom, but it doesn't carry over to recovery.
A possible solution... Create a symbolic link pointing /sd-ext to the 2nd partition? But then again, since /data now points to 2nd partition, is recovery picking up on that unknowingly and backing up the 2nd's contents when it thinks its backing up the normal /data?
I suppose I should investigate.
Edit: Yep it does backup the 2nd partition, thankfully. Just tried to install a theme made in UOT Kitchen, it borked some stuff, and the restore worked.

[Q] SD card change+Rom change from xpart to a2sd+ and taking over ext4?

Hey guys.
I've read some threads about moving ext4 from one SD to another, but this isn't exactly what I need.
I am currently on MIUI XJ 1.8.12 XPart rom and I want to change to 1.8.12 A2SD+ and a bigger SD card.
Changing the rom isn't the problem, but backing up my ext4 partition from the old SD is!
I used the newest ubuntu live CD(11.04 I believe) to partition the new SD card to FAT32/ext4. Everything is fine.
The SD gets recognized as it should. FAT32 and EXT4 partition mount and I can access them.
But with my old SD it doesn't work.
If I plug it in, FAT32 and EXT4 partition get recognized. FAT32 partition is named "195" and EXT4 is "userdata".
When I try to click the EXT4 it just dissappears. In the media tab it is listed, but I can't access it because I am not the owner of it/I am missing permissions/rights to access it.
I partitioned it with CWM recovery, but meanwhile I changed my recovery to RMD 1.03 (I don't think that this matters though...).
Now my questions:
1. How can I access my EXT4 partition to backup its content?
2. If I can't access it because I can't change permissions... do I really need to copy it or will it be enough to restore my apps that I backed up under xpart with MIUI Backup?
3. Is it a problem to restore a app backup done under xpart-script with a a2sd+ rom?
Thank you for reading!
you can backup your ext partition in recovery. i think you can also just open a file explorer and copy the folder /sd-ext (i havent tried this, so im not sure if this will work)
Ok, I haven't tried to backup it with recovery.
Will it then be possible to flash a new rom (a2sd+ instead of xpart) and restore only the ext partition?
I want a clean install with a2sd+ but I don't want to loose settings and savegames.
Just a small "up" for my thread.
I backed up my sd-ext partition and I could wipe right now.
Will there be any problems with restoring the ext partition on a new rom?
What will happen if I just wipe sd-ext and restore MIUI Backup?
Will sd-ext will just be "rebuilded" from the MIUI Backup?
Bananebieger said:
Will there be any problems with restoring the ext partition on a new rom?
Click to expand...
Click to collapse
there will only be problems if your rom does not support either your a2sd or your current ext filesystem (which is to say, does it support ext4 or does it only support ext2 or ext3?)
Bananebieger said:
What will happen if I just wipe sd-ext and restore MIUI Backup?
Will sd-ext will just be "rebuilded" from the MIUI Backup?
Click to expand...
Click to collapse
i believe so (please dont take my word for it as i have not done this before. however, im pretty sure it will be "rebuilt" as you have it included in your backup)
Thank you again.
Its the MIUI rom from XJ for Desire Classic with XPART script. Your ext Partition gets converted to ext4 if you install this rom.
Will there be problems with using sd-ext content from XPART after update to A2SD+?
Maybe I'll bother the dev from this rom

[Q] CWM3/5 corrupting sd-ext partitions

Hi,
I've read that CWM3/5 can corrupt sd-ext partitions, and the recommendation is to revert back to the latest CWM2 version. Does this only apply only if I have an sd-ext partition? My Desire Z's sdcard is pure FAT32, I'm assuming CWM5 would be fine?
Also, does it matter if CWM wasn't used to create the sd-ext partition? On my wife's Desire, I used gparted to create the sd-ext4 partition. Is there a possibility CWM3/5 will corrupt it in this case? If so, when? During bootup to recovery? Or day to day use?
Thanks.
My sd ext got corrupted during a nandroid restore. I have since move to Amon Ra and it's been solid for me on my N1

[Q] Format UMS partition back to FAT32

I started playing with my Galaxy S2 I9100 recently after upgrading to a Galaxy S4 I9505 and trying custom ROMs. As the system partition wasn't big enough to install a ROM and a full Gapps package, I thought I'd try to change the partition table and increase the size of the FACTORYFS and DATAFS partitions at the same time reducing the size of the UMS partition.
My first attempt was to use parted through an ADB bridge with the phone in CWM recovery and doing so managed to get the phone working with the exception of the camera which immediately threw up the error 'Unfortunately camera has stopped working.' The Gallery app also doesn't work saying there is no storage present. When using the print function of parted, there was a msftres flag indicated for the FAT32 formatted UMS partition.
I have since used PITmagic to set FACTORYFS to 1GB and DATAFS to 4GB but interestingly when using the print function in parted, DATAFS and UMS had nothing listed under filesystem. I was able to get the DATAFS partition to ext4 using the wipe data function in CWM recovery but am unable to get the UMS partition formatted to FAT32. I have tried flashing busybox to use the mkdosfs or mkfs.vfat commands but these are unable to format a partition of the size that my UMS currently is set at.
Does anyone know of a way to reformat the internal UMS partition back to FAT32?
I eventually got this sorted but it seemed like a fairly complicated process. Firstly I used PITmagic to prepare a PIT file which I flashed using Odin. All the necessary files and instructions por PIT Magic can be found in the links below:
http://forum.xda-developers.com/gal...es/mod-partition-internal-memory-app-t2538947
http://forum.xda-developers.com/showthread.php?t=1916936
By booting into recovery (either CWM or TWRP will work for this) I was able to format some of the partitions but not all. I then used parted which is included in both CWM or TWRP to print out the partition table. Where a partition was not what it should be I removed it then recreated it using the guide I found for a kindle fire in the link below:
http://forum.xda-developers.com/showthread.php?t=1388996
Note that ext4 partitions cant be created in parted so I created them as ext2 partitions and upgraded them as in the guide. The big problem with the FAT32 partition for UMS is that it gets the msftres flag set owing to a bug in parted. However by flashing the same PIT file as before through odin this can be removed.
Now my camera works as the UMS partition mounts properly.

[Q] PIT Flash(repartition) failed,but its working!

Hey guys,
Today I did a repartition of my phone with the 1GB system 3 GB appstorage pit file.
I also used a PDA file with a apolo 4.x kernel(for neatrom 4.1)
Well... the flash failed...
I however could start the phone. I booted up and presente me with: type in password to access encrypted storage.
I then booted into the recovery and tried to flash a new ROM.
but emmc / the internal SD card could not be mounted.
I then formated the internal SD in windows and was able to access the card again.
But I still could not install a rom because /data could not be mounted. I formated the /data partition after "repair" under TWRP for the data partition didnt work.
I now could access all partitions and install th ROM.
I now have 1009 MB space in /system and 3GB in /data and I can also use the ROM
but why did I get an Error MSG in odin? Is everything OK with my mobile phone or should I try to repartition it again until I get a "sucessfull" MSG?
Thanks

Categories

Resources