yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] FadeFx:
Sure, recovery is a complete os finally. Also it is not a real problem, as we still can use current version of your recovery, id just ask permission to either upload it to googy thread with credits to you, or to leave current version available here as well.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] Jejebond:
My actual ROM BAM V2 RC2 (4.4.2) use framework2.jar and not framework-2.jar. Do i need to change the name before flashing this kernel ?
[Galaxy S III Original Android Development] DerTeufel1980:
You/googy can upload it to his thread. That's fine for me

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] rascal0pl:
thanks, it is working now with
[Galaxy S III Original Android Development] DualJoe:
I've linked both obb folders since one is only visible inside vm mountspace and the other can be used from outside (ssh, adb..). But the latter one is not important if you don't use it.

/.secondrom/media/obb

/.secondrom/media/0/Android/obb
[Galaxy S III Original Android Development] jimhaddon:
Whenever I install a rom to secondrom

Using your recovery, it overwrites first rom. Why does it so this?
[Galaxy S III Original Android Development] Darkened_Sky:
have you followed the dualboot FAQ in the OP?

probably you choosed "install zip to secondary FS", but you have to choose "install rom to secondary FS". only that way the zip gets modificated.

it also depends on the rom you try to install. for example I experienced that some aroma based roms cannot be directly flashed as second rom. so you have to install them in form of a nandroid backup (btw. that is also mentionned in the dualboot FAQ ;) )
[Galaxy S III Original Android Development] jimhaddon:
I have read the FAQ. I used install rom, not zip. I've tried aroma and non aroma roms. All install over primary rom.
[Galaxy S III Original Android Development] Darkened_Sky:
do you have in data/media/ a .secondrom folder which is ~1.5gb big?

are you able to restore a nandroid backup as second rom?
[Galaxy S III Original Android Development] KKTHX:
Same here.

+1

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Original Android Development] soronk:
Just wanted to say a big THANK YOU for your hard work!

Then I donated to the wrong thread ;) your old kernel is also good, but this recovery/kernel combo wins everything!
[Galaxy S III Original Android Development] DerTeufel1980:
Thank you very much for your generous donation. It is Highly appreciated and also helping me much :)

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] drgreenth:
Whats the status of new implements? Dont take this as pushing just being curious.

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] BradleyR2010:
Quick Question

Is anyone getting into reboots after android starts using fiops as Scheduler? my phone does this but I wanna make sure its not my app that is causing it :S

edit: well is not my app guess my phone doesnt like fiops cause deviltools also caused the reboots
[Galaxy S III Original Android Development] DaReDeViL:
To make things clear. The statement "devil recovery is not as good as your old" is fully wrong because of 2 things:

1) the "old" recovery isn't even mine, it's gokhanmoral's wonderful work

2) your recovery is way better. People complaining about it simply mistakenly use it.

Comparisons must be done to same categories. You can't compare apples to bananas (but we can't deny they are both beneficial and tasteful ;) )

Please don't get offfended by such things and keep in mind that it won't stop even if you drop support for googymax :p (even if I get into the f2fs train) :D

Anyway, I am here to testify you do a great great job and I keep on learning from you as much as I can.

So let's keep the spirit of it that way while ignoring what can be said behind ....

"A bon entendeur, salut!"

Envoyé de mon GT-I9300 en utilisant Tapatalk
[Galaxy S III Original Android Development] xeizo:
I have pretty much settled for row as the most stable and smooth scheduler with this kernel. It just works :)
[Galaxy S III Original Android Development] cba1986:
[MENTION=4196889]DerTeufel1980[/MENTION] There was any progress on the project? My finger is getting very itchy. hehehehe
[Galaxy S III Original Android Development] DerTeufel1980:
Recovery already built. I just need to update the kernel initramfs to support f2fs as well.

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] cba1986:
Excellent!!!!

i am exciding mysef too much asking for an ETA? :D
[Galaxy S III Original Android Development] xeizo:
Yes! :D Give him some time to play around with his stuff to make sure it works as great as his previous work :good:

Good thing is, if this hadn't taken some time I might never have been bored enough to start compiling stuff myself :eek:
[Galaxy S III Original Android Development] cba1986:
I was joking people... :angel:
[Galaxy S III Original Android Development] cKenny:
today i installed devil's recovery (it's awesome!) + kernel, and intend to setup dual boot.

after flashed jelly bean 4.3 as primary rom + devil kernel, i nandroid backup it and restore as 2nd rom,

wip data, clear calvik, install cm11, gapps to it, then flash devil kernel to it too.

then when i boot into 2nd rom to see the result, i found that 1st rom and 2nd rom has been swapped, and the system are unstable and laggy.

did i do anything wrong? anybody can help to advise? thanks in advance. :)
[Galaxy S III Original Android Development] xeizo:
Yes, the recovery has sometimes behaved funny for me as well, but it is a very advanced piece of software so I'm mostly amazed that it works at all :eek:

Anyway, to avoid the situation described I always do like this when i flash second rom:

If second filesystem have been wiped:

1. Install rom to second filesystem, a message should appear that the rom is being prepared, if not something is wrong!

2. Install Gapps as zip to second

3. Install kernel as zip to second

4, Install kernel again, but as kernel(in the menu)

5. Install supersu as zip to second

6. reboot second filesystem!

If dirtyflashing second filesystem:

1. Install rom to second filesystem, a message should appear that the rom is being prepared, if not something is wrong!

2. Install Gapps as zip to second

3. Install kernel as zip to second

4. Install supersu as zip to second

5. reboot second filesystem!

(as you see if dirtyflashing you can skip to install kernel as "kernel")

This procedure has worked stable for me, on some occations in certain scenarios when dirtyflashing I have used Yanks kernel cleaner before flashing the kernel to survive wihout a wipe :silly:
[Galaxy S III Original Android Development] Svartsyn333:
Sadly the recovery freaked me out totally as I recovered a backup of Sammy Stock 4.3 ML2 to 2nd rom. Didn't boot, just black screen. Then I deleted 2nd rom, still the same. At last I tried to flash Philz recovery again but it just stayed that way. Could only restore backup to 1st rom.

Sent from my ? using my ?.
[Galaxy S III Original Android Development] spoonymoon:
Sounds like you guy's made some mistakes while installing.. Never had a single issue with this genial pice off code :)

Few rules:

Make sure atleast 3gb free space on internal sd

Use wipe in recovery and select "clean install a new rom" first

Don't restore nandroid before both roms are booting ok

Then always select install rom, not install zip when it comes to rom itself

And always after rom flash remember to flash dual boot kernel once again

Then there's only left flashing gapps/asop calendar sync/super su 1.91 zip's

Reboot desired rom

Never failed here :)
[Galaxy S III Original Android Development] Svartsyn333:
Maybe it works that way, but I didn't install a new rom to 2nd rom, I restored a backup. That's pretty much something totally different...

Sent from my ? using my ?.
[Galaxy S III Original Android Development] DerTeufel1980:
This should be fixed in the next recovery version

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
please try and report back, if this kernel is booting/working well on cm, omni and sammy

details later ;)
[Galaxy S III Original Android Development] coolhof:
Working good on two sammy roms.

Both are booting fine.
[Galaxy S III Original Android Development] shaarky:
Temasek v41 - boot OK on latest Devil version

Is it placebo that it feels snappier?
[Galaxy S III Original Android Development] DerTeufel1980:
What's your selinux state? Is it enforcing or permissive?

Anyone tried on omnirom or slimkat?

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] shaarky:
For me SeLinux is enforcing
[Galaxy S III Original Android Development] vegaman:
I'm running it on omnirom now. So far no problems.
[Galaxy S III Original Android Development] DerTeufel1980:
here is the new recovery now. with this, and the 2.4.7 kernel from previous page, you are able to format and use f2fs instead of ext4. below a guide by a user in my note2 thread:

here some additional info about the changes to kernel and recovery:

what's new:

kernel:

added new f2fs filesystem support (supposed to be up to 2 times faster than ext4), backported from linux 3.13

introduce the BFQ-v6r2 I/O sched for 3.3

block, bfq: add Early Queue Merge (EQM) to BFQ-v6r2 for 3.3.0

enable CGROUP_BFQIO by default

backport SLUB (memory allocator, very important) from Linux 3.8

Big thanks to arter97 at this point. He sent me the initial f2fs patches, fixed building of bfq io scheduler, as well as had ported slub to 3.3 already.

updated block subsystem (io schedulers) to Linux 3.4

afsync: replace fput() with fput_light() accordingly

cfg80211: Fix memory leak

mm: implement WasActive page flag (for improving cleancache)

fix triangle away

usb: fix 'adb root'

recovery:

complete rework of recovery ui (primary and secondary rom need to be selected once in dualboot menu)

if you can't access dualboot menu, please boot primary or secondary rom with the new kernel once

resized secondary system image to 1.9 gb

possibility to flash roms to secondary without modifying the zip (you HAVE TO CHOOSE ROM). if this fails, select use workaround (this is the old method) next time

added support to format and mount f2fs formated partitions (/system, /data and /cache)

if you format data to f2fs (this gives the maximum prformance, you have to select primary rom in dualboot menu, then the option will be in mounts and storage: format /data, /data/media and secondary (please backup before, this wipes your internal sdcard as well))

I'll update the op, once i get confirmed f2fs is working well for you

This has been the work of almost one month every evening.

Please consider a small donation to show me your appreciation (and i can show my family that i am not just wasting my time :p).

latest kernel can be found here:

http://xdaforums.com/showpost.php?p=51148539&postcount=1804
[Galaxy S III Original Android Development] coolhof:
Going to test it after work.

Thnx.
[Galaxy S III Original Android Development] spoonymoon:
You rock Devil and has done for a very long time on all of my s? Phones I owe you soo much in return…

Her's a start : transaction id 8J252644RP841602T

Cheers :P

Thankyou very much

:)

--- come on guy"s spit in, don't be cheap, if any deserves this it's the Devil---
[Galaxy S III Original Android Development] cba1986:
Awesome, i am already restoring the data. Only one question. How do you check that all partitions are formatted in f2fs?
[Galaxy S III Original Android Development] Moster2:
One way is to open the app terminal emulator and type in "mount". /system/, /data/ and /cache/ should show f2fs

Btw, I donated, too. Its definitely worth it :) Currently trying and it feels smooth.
[Galaxy S III Original Android Development] coolhof:
Oke done...

I think al is fine.

I have 2 booting sammy roms and I think it's f2fs system. (See screen shot)
[Galaxy S III Original Android Development] dyval:
recovery is compatible with any roms/kernel?thanks :)
[Galaxy S III Original Android Development] JustArchi:
[MENTION=4196889]DerTeufel1980[/MENTION]

Could you write all required commands for reformatting and mounting through terminal?

Thanks in advance.
[Galaxy S III Original Android Development] Moster2:
The rom shouldnt matter as long as the kernel supports it. I dont think that any other kernel currently supports it though, but correct me if Im wrong
[Galaxy S III Original Android Development] dyval:
you mean the f2fs implementation? I think you're right.:angel:
[Galaxy S III Original Android Development] Moster2:
Yes, Im talking about the f2fs implementation. We need to ask the other devs to support it :)
[Galaxy S III Original Android Development] JustArchi:
Most of the roms have format /system command, which will reformat /system to ext4, unless Devil took care of that.

That's why I made ArchiDroid f2fs-compatible some time ago.
[Galaxy S III Original Android Development] soronk:
Seems like wlan isn't working with slimrom 4.4.2
[Galaxy S III Original Android Development] xeizo:
Everything installed, now I just have to do nandroids of the two OSs because it was a couple of days since, after that f2fs here I come! :D
[Galaxy S III Original Android Development] francescozanghetta:
Many Thanks for your great work!!!

Everything seems fine Imperium 24.0 + last devil kernel! To check your filesystem you can use partition table from google store.

I had just on error during the f2fs migration regarging data formating.

I format system and cache from submenu straight to f2fs. If I want to format data to f2fs I need to use "format / data. /sdcard and second rom" instead of "format data", is it right? When I use "format / data. /sdcard and second rom" it gives me and errore related to the cache and second rom. Also when I use "format / data. /sdcard and second rom", at the end of the process the recovery reboot automatically. This happens only the first time when I migrate from ext4 to f2fs. Is this behaviour normal?

Thanks in advance
[Galaxy S III Original Android Development] nagi_007pk:
Stock Samsung Rom

I have been facing the same error as well. My system restore didn't go as expected... It failed once and again says failed to restore system. I had a stock Samsung rom with cm11 dualbooting.

My recovery also restarted for some odd reason and I can't seem to restore my system files as the system folder is less than 1328 megabytes can you give me a hint as to what is the issue?
[Galaxy S III Original Android Development] francescozanghetta:
I can restore the rom without problem. Evrything seems faster.

Still checking recovery errors

format system to f2fs goes ok

format cache to f2fs goes ok

format /data. /sdcard and second rom --> recovery reboot the first time I try to migrate to f2sf. When recovery restart it says data bloked.I try again format /data. /sdcard and second rom this is what has been shown:

E: copy: source file not found (/.secondrom/media/.devil_recoverysetting/devil_6.ini)

Formatting /data to f2fs.....

Done.

E: copy: source file not found (/cache/settingfile_backup.ini).

After this I can restore the rom without problem and all three partitions are f2fs. The other thing which I notice is that the system partition is almost full after restore.
[Galaxy S III Original Android Development] Mostafa Wael:
Hey dominik

i am not using dualboot, i am on official omnirom nightlies and use TWRP so i can use OpenDelta, so will i have the capability to update using opendelta with TWRP after changing the filesystem to f2fs?

i am really thankful for your work....

a BIG BIG BIG Thanks for your job!

:good: :good: :good: :good:

:D :D :) :) :victory:
[Galaxy S III Original Android Development] Moster2:
You need derteufels recovery and kernel, so no updates with opendelta.
[Galaxy S III Original Android Development] Mostafa Wael:
No No No i mean after changing the filesystem using devil's recovery of course... :D

i mean after restoring the ROM after the whole process, can i change to TWRP again and continue to update ROM using OpenDelta?

i think there is a little misunderstanding.. :)
[Galaxy S III Original Android Development] Moster2:
I understood you in first place, but Im not 100% sure this will work. Go ahead and try it.
[Galaxy S III Original Android Development] rascal0pl:
Is stock rom working as 2nd rom already?

Edit: Nevermind, it is working, but still I can't write on my ExFat formatted SD :(
[Galaxy S III Original Android Development] FlemishDroid:
When you flash a stock 4.3 rom and immediately flash a custom kernel the camera gives an error. So I always flash a custom 4.3 rom with stock kernel and reboot then open the camera and reboot back to recovery and flash a custom kernel and then camera works fine but now when you want to use the new f2fs you have to use your kernel immediately so the camera gives an error. Maybe you can take a look why the camera gives an error when you flash a stock 4.3 rom + a custom kernel? I think it's a problem with the flash light because the app flash notification also doesn't works and 3th party camera apps also doesn't works. So if you boot with stock kernel and open camera and then flash a custom kernel then it works...

Big thanks for all your hard work.

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] shaarky:
Trim is not supported or not needed in F2fs?
[Galaxy S III Original Android Development] Mostafa Wael:
I confirm this issue of sudden recovery reboot, i am restoring the backup now!!!

---------- Post added at 12:50 AM ---------- Previous post was at 12:44 AM ----------

i am having a bootloop here what should i do? :confused::confused::confused:
[Galaxy S III Original Android Development] rascal0pl:
format again and restore after success format (without reboot)
[Galaxy S III Original Android Development] Mostafa Wael:
oh man, i can not even make anything, "can't mount partitions!" on everything HELP ME PEOPLE
[Galaxy S III Original Android Development] francescozanghetta:
those errors don't prevent you to install the rom with f2fs file system. Just format again ;)

DOes anyone have full system partition after restore?
[Galaxy S III Original Android Development] drgreenth:
Everything is working with primary rom flawlessly. System is exact same size than it was with ext4. Only issue is that I cannot create second rom image (only for devil kernel) after formatting /data ..

Any ideas? Reflash kernel?

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] JustArchi:
[MENTION=4196889]DerTeufel1980[/MENTION]

+ Source code

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

Now I'm ready to build interactive f2fs reformatting in ArchiDroid :D.

Please correct me if I used wrong method for something (especially $TOOL $EXTRA), this is important for me. Thanks.
[Galaxy S III Original Android Development] Darkened_Sky:
for me a complete boot of primary rom and then restart into recovery solved the problem (as it was mentioned in the description)
[Galaxy S III Original Android Development] DerTeufel1980:
The check isn't perfect yet. Please boot up once, then reboot recovery

Seems to be good :) if it even boots up, you did it properly :D

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] drgreenth:
Got it working. Now EVERYTHING is perfect! Thanks a million!

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] DerTeufel1980:
Thank you both for your donations :) I am really in the need for some money at the moment, and you even donated before you tried f2fs. Thank you to confide in me.

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] drgreenth:
What if I upgrade my tema rom with just dirty flashing a new zip, does it format my system as ext4?

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] drgreenth:
Doh. Well probably it cannot be done performing a nandroid and formatting system as f2fs and then restoring system?

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] Undermyoath:
Was going to ask the same thing :o but damn, I love this kernel.
[Galaxy S III Original Android Development] JustArchi:
Try with ArchiDroid, I implemented f2fs support already 2 or 3 versions before. Now I'm implementing interactive reformatting to selected filesystem :p.

F2FS support itself is very easy, but rom developer must implement it in order to keep /system formatted in f2fs:

a) We can't mount /system as ext4, if we need to remount /system then it must be done through automatic filesystem, in ArchiDroid I'm using mount -t auto /system

b) We can't reformat /system to ext4, instead we should make sure it's mounted (look above) and then execute delete_recursive("/system") or similar.
[Galaxy S III Original Android Development] Gold_Diesel:
After using f2fs for a few hours, the whole system seems a lot smoother. Thanks for all the hard work.

I have a quick question about swappiness. Does swappiness work in the traditional way of swap space in the fs? And if yes, where exactly is it held?

Cheers
[Galaxy S III Original Android Development] maxq1:
mighty awesome work as always, DerTeufel1980! f2fs, recovery & kernel works as advertised. gonna try dual boot when i have time. btw, is multi boot still in your pipeline?

7XC12018TP319912S...cheers, man!
[Galaxy S III Original Android Development] JustArchi:
Devil...

:D
[Galaxy S III Original Android Development] maxq1:
^ looks awesome as well, man! thank god for xda & devs!
[Galaxy S III Original Android Development] JustArchi:
No, this looks awesome:

Yep, it works :D.
[Galaxy S III Original Android Development] vegaman:
Been trying all day to get f2fs working on my phone but had no luck. Not sure if its my phone or omnirom. Out of time for now though.

Edit: to clarify I've followed the instructions and always end up with a bootloop. I got it to 'boot' but it wasn't really working (no lockscreen or launcher or anything) when I reformatted /data to ext4 and left /system as f2fs. I think the issue might be with the recovery though because I ended up using philz to get my phone back to a working state.

It seemed to be quite common that the devil recovery couldn't mount the /data partition as well, sometimes because it rebooted when I tried to format, sometimes it would do it even when it looked like it formatted properly.
[Galaxy S III Original Android Development] slg1119:
Where is Credit?

F2FS isn't YOUR WORK

I think arter97 too
[Galaxy S III Original Android Development] vegaman:
No he didn't write f2fs (the credit for that is in the kernel source like everyone else's), but he's spent a lot of time getting it working (well for some of you at least, hope I can get mine working soon) on our phones.
[Galaxy S III Original Android Development] KMino:
He did.. See the commits :rolleyes:
[Galaxy S III Original Android Development] cnn888:
archi, just wondering if you can share the app?

will it work on sammy rom 4.3? just seem easy to check if i got f2fs or still on ext4.

thanks.
[Galaxy S III Original Android Development] maxq1:
^ you could use diskinfo from the playstore if you just want to check file system types on your partitions. issuing "mount" on terminal also works. if you see "f2fs" after /system, /cache, etc, you're good
[Galaxy S III Original Android Development] cnn888:
with all the fuzz about f2fs, is it really that much better than ext4?
[Galaxy S III Original Android Development] BrhoomHD:
how can i access the sub menu ??

i9300 temas v41 & Boeffla