Hello guys, i've a question, I did a fatory reset on my phone and lost all my data, I did a lot of research and was able to create a img file will all my data using some adb commands, but now I'm stuck because the motox 2014 uses f2fs filesystem and not ext4.
I need to convert a .bin image that is in f2fs to ext4 without loosing it's content, any of you have any idea how to so it?
The forensic tool FTK Imager does not read f2fs filesystem.
Thanks
Related
Hello,
I'm quite new in android development, so sorry for dumb question.
I have new GT-S6102 (because of dualsim setup) and I'd be quite happy with the stock firmware (S6102XXMA2) if it wasn't of the 160M memory. What I'm trying to do is to modify init.rc in bootimage to mount /data on 4G second partition of my SDCard instead of 160M /dev/stl11.
I'm using a Ubuntu 12.04 machine for my experiments.
I've copied /dev/block/bml7 from my phone using ADB, extracted it using abootimg.
First (and I hope that main) trouble is that when I try to update the boot.img (abootimg -u boot.img -r initrd.img), even without modifying the ramdisk, the resulting image has few different bytes near the beginning of the file. Anyway when I flashed it back to phone, it booted normally.
Then I unpacked the ramdisk (using steps from here) and modified init.rc:
Code:
mount ext4 /dev/block/mmcblk0p2 /data nosuid nodev crypt check=no
# mount rfs /dev/stl11 /data nosuid nodev crypt check=no
I have a 32G uSD card with 28G FAT and 4G EXT4 primary partitions.
Then I've repacked it, made new boot.img, flashed with ODIN and it made a nice bootloop with Samsung bootanimation without usual sound.
What am I doing wrong?
Is this modification even possible?
Thanks for advice
P.S.
I've tried to extract the boot.img from S6102XXMA3_S6102DBTMA1_S6102XXMA2_HOME.tar.md5, but 7zip on Windows and TAR on linux complain that it isn't valid archive.
jelinek.01 said:
Hello,
I'm quite new in android development, so sorry for dumb question.
I have new GT-S6102 (because of dualsim setup) and I'd be quite happy with the stock firmware (S6102XXMA2) if it wasn't of the 160M memory. What I'm trying to do is to modify init.rc in bootimage to mount /data on 4G second partition of my SDCard instead of 160M /dev/stl11.
I'm using a Ubuntu 12.04 machine for my experiments.
I've copied /dev/block/bml7 from my phone using ADB, extracted it using abootimg.
First (and I hope that main) trouble is that when I try to update the boot.img (abootimg -u boot.img -r initrd.img), even without modifying the ramdisk, the resulting image has few different bytes near the beginning of the file. Anyway when I flashed it back to phone, it booted normally.
Then I unpacked the ramdisk (using steps from here) and modified init.rc:
Code:
mount ext4 /dev/block/mmcblk0p2 /data nosuid nodev crypt check=no
# mount rfs /dev/stl11 /data nosuid nodev crypt check=no
I have a 32G uSD card with 28G FAT and 4G EXT4 primary partitions.
Then I've repacked it, made new boot.img, flashed with ODIN and it made a nice bootloop with Samsung bootanimation without usual sound.
What am I doing wrong?
Is this modification even possible?
Thanks for advice
P.S.
I've tried to extract the boot.img from S6102XXMA3_S6102DBTMA1_S6102XXMA2_HOME.tar.md5, but 7zip on Windows and TAR on linux complain that it isn't valid archive.
Click to expand...
Click to collapse
OK, so it seems that I´ve managed to work it out at last.
The unpacking and repacking of bootimage was all right, trouble was in updating only the init.rc and probably using ext4. What I have done:
I replaced all mentions of mounting /dev/stl11 on /data by mounting /dev/block/mmcblk0p2 (that was in files fota.rc, init.rc, init.charge.rc, res/recovery.fstab). In res/recovery.fstab I also changed formatting type from rfs16 to rfs32 so it supports my 4.5G partition.
Then I flashed the bootimg in my phone and formatted the data partition in recovery (that was the only way to make it rfs I've found).
Maybe it would all work with changing the format and mount type to ext4, but I hoped for as little modification as possible.
Now it reports 4.25GB free space after all my apps are installed, hurray .
I have just to remember to never boot it up without SDcard inserted. Maybe it would work as a possibility to borrow the phone to somebody with another card.
The boot.img came from S6102XXMA3_S6102DBTMA1_S6102XXMA2_HOME.tar.md5, if someone wants to try it, it is here . It probably wouldn't touch the original /data partition, so it might be possible to try it and undo it by flashing original boot.img. It just requires to have a second primary partition on SDcard and formatting it in recovery before first boot.
i didnt know to do that boot "compiling" like u did, quite good for you, im using cronmod int2ext , i have 850mb internal. i use 'pimp my rom' to get init.d support.
I changed /system partition to f2fs for using temasek. Now I want to change it back to ext4. I converted all the other partitions to ext4 successfully. But when I try to change /system to ext4, it appears to go successfully. However, when I reboot, it still shows f2fs in the TWRP recovery.
I am using latest TWRP recovery (2.8.7.0_7 I believe).
Can anyone help me on this?
if u want to make sure ...just format the sys and if u see the line formatting system ex4_ then it's ext4 and if it's not then flash the latest twrp 2.8.7.0_8 and re-convert sys to ext4
Changed file system to ext4 and then wiped /system partition, now it is successful
Hey there.
In twrp I can't change my system partition file system to F2FS. To do it, I enter twrp and do the "normal" steps (wipe, advanced, change to f2fs).
TWRP says it changed but if I perform the same steps the file system type remains ext4.
Is this supposed to be like this?
You cannot format the system
It's really not practical to change the filesystem of /system since it's distributed as an image and not as files. You theoretically could do it, but it would be a lot of work and you'd have to redo it from scratch every time you updated your ROM. Also, you wouldn't get most of the benefits of f2fs since you'd almost never be writing to it.
Hi, wouldn't it be sufficient to switch to a custom kernel with f2fs driver to be able to run MIUI with a f2fs file system? It is even possible? With LineageOS you still cannot use f2fs on the /system partition (maybe in the initial ramdisk there is no f2fs driver ?) but at least /data and /cache partition, also on MIUI. Is there a way to do that?
I'm trying without success, installed a custom kernel which claims to have f2fs support, formatted the cache partition in f2fs to do some testing, typed the 'df' command in the linux shell but no cache partition is displayed.
Using f2fs on the /system isn't a good idea to begin with, the /system is a read only partition so you wouldn't benefit from anything that f2fs gives.
Hello xda community and OP3(T) users!
In April I created an image of my f2fs /data partition according to this hint:
https://stackoverflow.com/questions/26967862/how-to-make-an-image-of-android-partition-to-your-pc
This was successful and a *.img file sized 53+ GB now resides safely and quietly on an external hard drive.
Now I want to mount as well explore it with my Linux laptop. ))
How do I do this? Which tools and commands are needed?
P.S.: in the past this partition was also encrypted and decrypted via a simple 3x3 pattern by TWRP as well as before a ROM boots....