yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Teura:
shell@i9300:/ $ mount
mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
/dev/block/mmcblk0p9 /system f2fs rw,noatime,nodiratime,background_gc=on,discard
,user_xattr,active_logs=6 0 0
/dev/block/mmcblk0p12 /data f2fs rw,nosuid,nodev,noatime,nodiratime,background_g
c=on,discard,user_xattr,active_logs=6 0 0
/dev/block/mmcblk0p8 /cache f2fs rw,relatime,background_gc=on,user_xattr,active_
logs=6 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barri
er=1,journal_async_commit,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:49 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec
,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp43
7,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0

and

shell@i9300:/ # cat /boot.txt
cat /boot.txt
Mon Feb 3 21:18:26 GMT 2014
generating mount directories...
generating device nodes...
mounting devices...
trying to mount .secondrom as ext4:
mount: mounting /dev/block/mmcblk0p12 on /.secondrom failed: Invalid argument
trying to mount .secondrom as f2fs
mount: mounting /dev/block/mmcblk0p9 on /system failed: Invalid argument
rom does not seem to be based off cm
using omni initramfs
kernelversion: 3.0.101-Devil2-2.4.7
previous version:
updating modules...
unmounting and remounting data
mount: mounting /dev/block/mmcblk0p12 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p8 on /cache failed: Invalid argument
mounting /cache with ext4 failed, trying f2fs...
[Galaxy S III Original Android Development] Ferdimage:
Can anyone confirm if Samsung 4.3 roms are compatible with f2fs file system?
[Galaxy S III Original Android Development] Mostafa Wael:
Sorry for replying too late, but do you mean i should install devil recovery again and format system, data, sdcard, secondrom, cache as ext4 and reflash the ROM?
[Galaxy S III Original Android Development] drgreenth:
Oh it seems that philz or devil (cwm) cant boot without rom. Which is kind of retarted (bootloops on failed auto mounts). So I think you must go on with stock and then flash devil recovery and your rom etc.

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] -MaD-:
Did not had time to test new recovery and kernel yet, but for your work, family and a drink after developing... 6MV51198U0775412L

Do you made this also for SGS1? Did not followed the thread there, but my old phone would like it (and my wife also)!
[Galaxy S III Original Android Development] JustArchi:
Devil, the issue is with f2fs for /data (intsd) at least as primary rom. I reproduced that.
[Galaxy S III Original Android Development] Mostafa Wael:
If i flashed Archidroid 2.3.5 STABLE release with devil2 kernel, can i get the partitions formatted to f2fs out of the box? I mean will formatting to f2fs be done automatically while installing archidroid with your kernel?

Thank you

Btw i had no luck in getting f2fs on my phone... The phone reboots suddenly while formatting the "/data, /sdcard and /.secondrom" and i get error when i try again...

Also i get error can't mount /data

I would like to help, but i had my laptop formatted accidentally and i can not use adb.. :(

So waiting till f2fs is a bit more stable and safe to use,...

I am now on omnirom stock kernel...

Thank you dominik, hope to get it working... :)

Sorry for long text

Entschuldigung
[Galaxy S III Original Android Development] maxq1:
ml2 & ml4 works. haven't tried na2/5 though.

btw, bfq is giving me some lags. switched back to cfq as it gives me a good balance of performance, stability & batt life. any one else getting this?
[Galaxy S III Original Android Development] JustArchi:
Next ArchiDroid version will include "live" repartitioning. Everything works but reformatting /data to f2fs causes bootloop. Devil needs to look at that.
[Galaxy S III Original Android Development] GR0S:
F2FS is a bit pointless just on /system
[Galaxy S III Original Android Development] Moster2:
Then use it on /data and /cache, too
[Galaxy S III Original Android Development] FlemishDroid:
Yesterday I tried the new f2fs thing but I had some problems with the camera on JustArchi so now I'm back on ext4 and everything works again only one problem I can't flash crossbreeder anymore with your recovery and also not with philz cwm and stock cwm recovery it gives permission errors (error 7)...with twrp I can flash the script and it always works in the past so it happens after trying f2fs. Maybe you can take a look when you have some free time? I'm not the only one I have seen. Big thx.

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] Teura:
It seems that every time I try to format /data, /sdcard and secondrom to ext4 when it was f2fs, I will cause recovery bootloop. From ext4 to f2fs, it will just reboot itself once and keep on working, but the other way causes recovery bootloop which is recoverable by flashing TWRP via Odin. So there really seems to be something wrong with formatting /data.

Oh, and Triangleaway support, pretty please? :D

It will say it has done it's job, but flash counter stays on whatever it was.
[Galaxy S III Original Android Development] sirdragon:
Same here, formatting from f2fs to ext4 causes bootloop... Even flashing philz recovery via Odin is useless, to solve the problem I flashed an entire firmware via Odin...

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Original Android Development] DerTeufel1980:
Thanks. There seems to be something wrong with the disabling of selinux. I'll check this, as well as try to build a kernel with selinux set to permissive.

Meanwhile, could you please try from adb

su

restorecon -r /data (same command for system and cache as well)

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
Triangle is working on latest version for me again.

Could you (or someone else) while in my latest recovery, use adb shell, and then

su

cat /proc/version

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] Teura:
shell@i9300:/ $ su
su
shell@i9300:/ # restorecon -r /data
restorecon -r /data
Could not label /data with u:object_r:system_data_file:s0: Operation not supported on transport endpoint
shell@i9300:/ # restorecon -r /cache
restorecon -r /cache
Could not label /cache with u:object_r:cache_file:s0: Operation not supported on transport endpoint
shell@i9300:/ # restorecon -r /system
restorecon -r /system
Could not label /system with u:object_r:system_file:s0: Operation not supported on transport endpoint
shell@i9300:/ #

As for the version info on recovery, I can't get ADB ro recognize the device while on recovery so I'm unable to provide the info.
[Galaxy S III Original Android Development] _Beni_:
you need to install the SAMSUNG Android ADB Interface in the device manager to "GT-i9300"

EDIT and enter adb sideload and Go Back.

worked for me (sometimes).
[Galaxy S III Original Android Development] DerTeufel1980:
Ah, restorecon is the reason boot fails. I could fix this for note2 by taking the cm selinux files (because Samsung and omni were broken as well). Unfortunately the "fix" seems to be inside sepolicy, which is a compiled binary. Hence I don't know what exactly is the fix.

Hasn't there been one with cm11 based rom, and f2fs?

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] Moster2:
I used cm11 with f2fs. It worked totally fine.

Btw, do you have any plans to include the governor pegasusq(plus) that was created by andreilux?
[Galaxy S III Original Android Development] DerTeufel1980:
Maybe I just had forgotten to replace omnirom selinux with cm ones. I try to check it later.

Both kids are ill now, and time is limited...

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] coolhof:
After testing f2fs for a day, on two sammy roms it's very fast.

Booting time is reduced a lot.

(Reboot in 8 sec.)

Thnx.
[Galaxy S III Original Android Development] GR0S:
What about pushing F2FS to omni's upstream?

Edit fstab, modify install script (it should allow fallback), patch kernel.
[Galaxy S III Original Android Development] granets:
I have a problem with the backup process. I click the start custom backup job button, select sdcard1 and then I get nothing. Tried backing to internal card (sdcard) and it worked, but now I can't find the backup's location. Can anyone help me? At least with the location where the backups are stored on the internal SD card?

p.s. I get an "can't mount backup path" error when I try to do a full backup to sdcard1 Any ideas guys?
[Galaxy S III Original Android Development] cba1986:
Nothing to report here. Using Temasek's V42 + devil + f2fs + bfq. Battery and fluidity are awesome. 0% in 6 hours with WIFI on.
[Galaxy S III Original Android Development] _Beni_:
could you run mount and post it here? I tried much (5hours?!) and i never had a success with kitkat :(

f2fs is for Flash, what is when i format my sd card to f2fs. Is it supported?
[Galaxy S III Original Android Development] drgreenth:
Try unmounting and mounting /sdcard1 in recovery.

Location of backups in internal sdcard is /data/media/clockworkmod/backup/ or /data/media/0/clockworkmod/backup/

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] cba1986:
Of course, here you go:
[Galaxy S III Original Android Development] granets:
I did that. It was unmounted, tried mounting it, but I get the error that sdcard/sdcard1 can't be mounted

Anyways, worked around that, got my OTG cable out and did the backup to my USB drive. Let's hope all is well after restore. Guess my SDcard is formated wrong, which is strange as I recently formated it, when I installed CM11 for this exact same reason, and it was working fine till today...

thanks for that. but as I wrote asking about the path I realized it won't do much good, as I can't use my EXTSD card to flash anything from it, when It can't be mounted :)

P.S. I would like to report I have pulled of a backup and restore from external USB Drive. Also I like to live dangerously, so it was done without a MD5 checksum. Runing benchmarks to see if storage is faster.
[Galaxy S III Original Android Development] BrhoomHD:
i tried to format the sd data system...etc but thier is no option to format it ho can i access the submenu in devils recovery ?

i9300 temas v41 & Boeffla
[Galaxy S III Original Android Development] Mostafa Wael:
Flashed TWRP and my phone is back to life. Thanks God!

So now i am on official omnirom nightly with stock omni kernel....

For people who want to know what i did to survive this error, here you go

important Note:

-- You must have an external sdcard with the ROM you want to flash on it, as internal memory is formatted!

Situation

--Devil recovery rebooted when formatting "/data, /sdard and /.secondrom to f2fs"

and gives error when repeating process.

--No bootable ROM

--Stuck at Devil Logo

--Devil Recovery gives error "can't mount partitions or can't mount /data or it fails to install a selected .zip"

Steps i did to survive:

--Format the (/system), (/data, /sdcard, /.secondrom) and (/cache) back to ext4 to revert the whole process...

--since the recovery does not obey orders temporary, it is ODIN time! So i flashed a TWRP-2.6.3.1.tar using ODIN from here http://techerrata.com/browse/twrp2/i9300

--then i selected wipe-->Advanced-->check the system, data, cache, dalvik cache boxes and then slide to wipe

--then install your ROM from the external sdcard normally

--Flash the latest SuperSU

--Flash Devil kernel (optional, but it is highly recommended :p)

--Wipe cache and dalvik cache

--press back and restart system

--Voila!

that is what i did to survive safely if not simply,

thank you [MENTION=5337388]_Beni_[/MENTION] for the link to TWRP (i did not know that there is a .tar file for TWRP :D )

thank you [MENTION=4196889]DerTeufel1980[/MENTION] for bringing us the f2fs filesystem, i really appreciate your hard work and hope you could figure it out soon.

Hope that I helped you

Press the thanks button if i helped you, it only takes little time
[Galaxy S III Original Android Development] GR0S:
Flash TWRP, run make_ext4fs via terminal on /system, /data, /cache partitions and do not mess with devil.
[Galaxy S III Original Android Development] JustArchi:
Exactly.

https://github.com/JustArchi/ArchiD.../google/android/aroma/exec/adreformat.sh#L168

You need mke2fs -t ext4 /dev/block/mmcblk0pX to reformat to ext4, and mkfs.f2fs instead of mke2fs -t ext4 to reformat to f2fs. Don't forget to unmount firstly.
[Galaxy S III Original Android Development] FlemishDroid:
Yesterday I tried the new f2fs thing but I had some problems with the camera on JustArchi so now I'm back on ext4 and everything works again only one problem I can't flash crossbreeder anymore with your recovery and also not with philz cwm and stock cwm recovery it gives permission errors (error 7)...with twrp I can flash the script and it always works in the past so it happens after trying f2fs. Maybe you can take a look when you have some free time? I'm not the only one I have seen. Big thx.

Verstuurd vanaf mijn GT-I9300 met Tapatalk

No one have an idea how to fix this error? Or want to take a look at when having some free time? It occurs after trying f2fs and I formatted everything back to ext4 and flashed cm11 and philz recovery and boeffla kernel then finally everythings works again en then restore my stock 4.3 rom. So the only problem is crossbreeder isn't flashable anymore with cwm based recoverys like Devil recovery, Philz recovery and stock cwm recovery...it's the second thing I always install after installing a custom rom and it always works so I'm 100% sure it's a (devil)recovery/f2fs problem...because with twrp it still works!

Thx for all your hard work and I'm sure I try f2fs another time when it's more stable to install. :thumbup:

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] _Beni_:
Hmm it seems to be true, temasek v42 is working fine with f2fs.
[Galaxy S III Original Android Development] Andro Boy:
I have the same problem here ..

using archidroid 1.7.8 before everything , everything was ok after following the instruction and formatting to f2fs and restored the ROM ,

then after reboot to primary ROM nothing happens just stuck on devil logo -_- , i tried to do a clean install without the backup it flashes ok but also stuck at devil logo .

i will try to use a different ROM and see what happen . tell later .

UPDATE :

now here is what happened :

first when i tried to install another ROM the same problem was existing (i used smart droid and temask + already archidroid v2&1) ,

so i tried to format back to ext4 but there was some problems with the /data mounting after formatting ot to ext4 ,

i went back to philz and formatted everything (despite of some errors) , then did a clean install of archidroid v2.3.5 and back again as it was .

aftermath : back again to ext4 after failing to use f2fs & waiting for any news :) ....

cya :D ...
[Galaxy S III Original Android Development] Mostafa Wael:
Well, do you guys think it is a good idea to try to format to f2fs again? or shall i wait till our great dev figures it out?

Also what will happen if i only formatted the system to f2fs and the /data and /sdcard and /.secondrom are still ext4?

Hope to have it working....
[Galaxy S III Original Android Development] _Beni_:
i only would format cache to f2fs
[Galaxy S III Original Android Development] drgreenth:
This has nothing to do with f2fs. It is because devil and philz recoveries requires new kitkat supported update-binary inside flashable zip file. Just unzip crossbreeder and replace update-binary from like temasek rom zip or something with supported update-binary. You will encounter these issues even with ext4 with these cwm recoveries. Its year 2014 and kitkat is the thing so devs should upgrade those obsolete binary-update binaries.

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] FlemishDroid:
No it works all the time on stock 4.3 and on cm11 and on omnirom also. I flashed it maybe 100 times on those roms with Philz and now after trying f2fs it gives this permissions error. BTW I know what you mean but that was another error in the beginning days of flashing cm11...it was fixed a while ago cause I flash crossbreeder everytime I update cm11 nightly.

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] ariadnejro:
Thank you, I will try your suggestion about CrossBreeder next time I update my Temasek rom. However, I still think that the adblocking features of CrossBreeder don't work with a f2fs formatted /system.
[Galaxy S III Original Android Development] drgreenth:
Ok it was not due to obsolete binary. Just wondering what it might be, because both filesystems ext4 and f2fs follows posix compilance.

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] bj4ever:
Temasek V42 running fine with f2fs, just had a problem formatting /data, /sdcard and /.secondrom...the process stopped after /data so I had to umount /dev/block/mmcblk0p12 and format /sdcard manually with mkfs.f2fs before restoring my backup.
[Galaxy S III Original Android Development] kasperok:
Hi all.. i found a strange behavior of touchwake feature. I think It interfere with dialer proximity sensor..

During a call, I need to touch the screen and turn it on to be able to hung up..

anyone else has the same issue?

tnx
[Galaxy S III Original Android Development] Moster2:
[MENTION=3469974]Der Teufel[/MENTION], what was actually your reason to revert andreilux' changes to the pegasusq governor? I always felt his version was superior to the samsung one.
[Galaxy S III Original Android Development] DerTeufel1980:
I've noticed that as well, but I currently don't know what exactly causes this

I can't remember, to be honest ;)

Maybe I'll just add it back, after other things are finished (memory subsystem is equal to Linux 3.2 now...)

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] wongsyrone:
tested temasek v42 with f2fs and it works well , but /system is ext4 instead of f2fs due to tema's script has format line and the value is ext4 in there.Now I have /data /sdcard and /cache formatted to f2fs.

btw, omni-based rom hasn't tested.
[Galaxy S III Original Android Development] drgreenth:
http://xdaforums.com/showthread.php?p=50004857

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] afineday2die:
noob issue :(

Guys I was in Temasek v42 and devil kernel. I installed f2fs recovery and I used This steps http://xdaforums.com/showpost.php?p=49979584&postcount=1116&nocache=1&z=5207981006242335

I rebooted primary system and temasek boot animation stay attached. System does not open.

what should i do ?
[Galaxy S III Original Android Development] wongsyrone:
noticed that kind of method to keep f2fs on /system.It is similar to the verbose tutorial given by author. Thank you anyway, but I think it will be better if I can find a way to modify the walue in the script and re-sign the zip package or tema can make two different versions for his rom.
[Galaxy S III Original Android Development] coolhof:
Reflash kernel.
[Galaxy S III Original Android Development] kasperok:
Hope this can help.. it seem Temasek find a solution..

http://xdaforums.com/showpost.php?p=42104575&postcount=17993 (input.c: Disable touch2wake if incall)

https://github.com/temasek/android_...mmit/5dd94caccb1990f6b9899a768862a4fa66144e7f (Touchwake v1.1a)

tnx
[Galaxy S III Original Android Development] GR0S:
What branch you used while F2FS porting?
[Galaxy S III Original Android Development] DerTeufel1980:
The dev branch (Linux 3.13/3.14), but I wasn't able to port the last commit yet

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] Ricky Divjakovski:
first time trying this, all i can say is great! would love to look into the source and see if we can find a work around for the long wait while patching the file!
[Galaxy S III Original Android Development] JustArchi:
Looking forward to /data fix :).
[Galaxy S III Original Android Development] DerTeufel1980:
please try if this kernel fixes boot on omnirom with f2fs on /data (and if everything else also works)
[Galaxy S III Original Android Development] JustArchi:
ASAP!! :victory:
[Galaxy S III Original Android Development] -MaD-:
Is there a way to install a second rom without losing f2fs? Or only via nandroid backup and restore?

For me it's probam rom.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] Madness.:
Modify script or ask to dev

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Original Android Development] drgreenth:
Why is second rom image still ext4? Its on top of f2fs tho so probably no need?

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] JustArchi:
I told you guys many times that rom compatibility is also important.

Ask your favourite developer to implement for example mine f2fs-friendly way of flashing, or stick with a rom which has such, for example ArchiDroid.
[Galaxy S III Original Android Development] drgreenth:
Does not boot cm11 temasek rom which is omni based. Cant hand over logcat because im on train..

Lähetetty minun GT-I9300 laitteesta Tapatalkilla

---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------

Oh probably need to create new nandroid with latest recovery and recreate second image. Probably nandroid image contains ext4 partition table?

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] Teura:
Boots up nicely with Omnirom now, /system, /data and /cache as f2fs.
[Galaxy S III Original Android Development] JustArchi:
If you create nandroid in .tar format, then it won't reformat partition. Only .img contains partition table (because it's in fact partition image)
[Galaxy S III Original Android Development] Darkened_Sky:
temasek rom is not based on omnirom but on cm11. it just can handle omnirom kernels. see here
[Galaxy S III Original Android Development] DerTeufel1980:
My recovery does not reformat the partition on nandroid restore, unless you uncheck the option in misc nandroid settings

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
That's why I wrote that it reformats only during restoring from .img file :). And in fact, it's not even reformatting, more like writing raw file (and I'm nearly sure noone has system.img nandroid backup).
[Galaxy S III Original Android Development] drgreenth:
Then its default behavior. I created second image from recovery and restored nandroid tgz image. System is ext4. Bug or works as designed?

Lähetetty minun GT-I9300 laitteesta Tapatalkilla

---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------

So ill try to create nandroid image with that option checked and recreate second system image?

Lähetetty minun GT-I9300 laitteesta Tapatalkilla