yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] mrjoy:
Who I am, what do u mean? I'm also xda member same as others. & he wrote in OP which u r telling me that for sure he didn't say. Check this link & read properly http://xdaforums.com/showpost.php?p=49979584&postcount=1116
[Galaxy S III Original Android Development] bajica:
Read the changelog for latest test version, he added cache to f2fs
[Galaxy S III Original Android Development] mrjoy:
Anyway he added cache to f2fs but i'm unable to change kernel to agni kernel which is also f2fs file system supported, any help?
[Galaxy S III Original Android Development] Moster2:
You said in your post "you told that cache cant be .....". So I asked who you mean with "you", because formating cache to f2fs was working from the beginning.
[Galaxy S III Original Android Development] mrjoy:
Now i'm critical condition. I'm unable to goto to any other rom from since i flashed devil kernel with formatted all partitions as f2fs. Now what i should to do. I am flashing pac-man rom & before flashing i formatted again all partitions as f2fs format but rom stucked on boot, now i want my all partitions as it was before by default, i formatted all partitions as ext4 but all in vain. Plz help
[Galaxy S III Original Android Development] cyrusavirus:
Follow following steps:

1. Flash philz

2. Reboot to recovery.

2. Format everything except modem partition and external sdcard. (Optional internal card as well.... i would strongly recommend to format though)

3. Flash the rom you want to flash...

If this fails....Download archidroid's any rom... (version 1x or 2x). Use the aroma to flash Ad.. choose the format as ext4.. and flash the rom...

If that fails as well....i am afraid the option left would be to odin flash the stock and start all over again...
[Galaxy S III Original Android Development] Erahgon:
After flashing the ROM, reflash the devil kernel.
[Galaxy S III Original Android Development] drgreenth:
Did u flash devils kernel after rom flash? Kernel _needs_ to support f2fs not ROM.
[Galaxy S III Original Android Development] mrjoy:
Thanx for guide me but that's will surely make my all partitions same as by Samsung's defaults? I will give a try & tell u later

---------- Post added at 01:01 AM ---------- Previous post was at 12:54 AM ----------

I know mate after flashing ROM I hv to flash devil kernel again. But the point is why I install devil kernel again if I want to test others.....but i'm unable to flash any other kernels which are not supported by f2fs. But now I formatted all partitions as f2fs & don't knw wat happed with the partitios that only f2fs kernel working not other. That's the problem. I don't want f2fs on my device. So please help me to remove this f2fs from my device so that my device's partitions can become as before & can flash normal kernel too without f2fs.
[Galaxy S III Original Android Development] tetakpatak:
Can you not use devil recovery to format again all the partitions back to ext4?
[Galaxy S III Original Android Development] Andr3y29:
Here's how I see it and how for me it worked. Download Odin and latest TWRP in .tar format and flash it. First, format data. Then select Advanced Wipe and check everything. It will automatically format ext4 because it does not know other format. Then flash latest philz touch 6.19.3.zip, because if the data won't be formatted correctly, philz will just reboot. Then, select wipe, and clean up to install a new rom. His, flash whatever you want :D you may format data, but I usually get reboots of recovery and have to do the process again.
[Galaxy S III Original Android Development] DualJoe:
This would be a good time to update the kernel indeed. Those with f2fs slowly getting into trouble since latest CM11 nightlies depend on new kernel changes (dual sim).
[Galaxy S III Original Android Development] Moster2:
Nah, latest kernel works fine. Im using it on the snapshot m4 which also includes those changes. They fixed the compatibility
[Galaxy S III Original Android Development] cyrusavirus:
3rd method is failsafe method which would definitely make it atock... but firat two methods would keep the root and they would definitely not make.it all stock... in normal scenerio first method qould.work and u should be back on track... it would only fail.in case u have done sone other changes to partition table.
[Galaxy S III Original Android Development] DualJoe:
Anyone know why fstrim doesn't work? There are some positive reports on Google that i9300 should work.

When i start 'fstrim -v /data' i just get an error 'not a typewriter'.
[Galaxy S III Original Android Development] mrjoy:
i did that. I formatted all partitions as ext4 format again but later it doesn't mount data partition while flashing rom or anything else. Thats why i'm saying i'm in critical satiation.
[Galaxy S III Original Android Development] JustArchi:
Well, some time ago I said that if we're talking about /cache /system or /preload then we're fine because these partition are easily restorable via Odin and Sammy's ROM (it contains blocks in .img file, so filesystem as well).

But this is not the case with /data.

Boot into recovery, connect through ADB, execute:

umount /dev/block/mmcblk0p12 (if it prints error about nothing to unmount, that's fine)

mke2fs -t ext4 /dev/block/mmcblk0p12

mount -t ext4 /dev/block/mmcblk0p12 /data

And pray that it'll work because if not then you're screwed, literally.
[Galaxy S III Original Android Development] mrjoy:
I'm trying with TWRP but it unable to format anything except cache partition. It says unable to mount system partition...
[Galaxy S III Original Android Development] Andr3y29:
Try latest TWRP 2.7.0 . It was launched in the morning. For me it always always worked. Try an aroma installer rom that lets you format partitions. You can also try another f2fs kernel. Like agni or xpure. Do you still have a rom installed ?
[Galaxy S III Original Android Development] mrjoy:
I tried this trick too, but this trick also failed. Philz recovery unable to mount data & system partition but its formatted only system partition but not data.

---------- Post added at 01:38 PM ---------- Previous post was at 01:27 PM ----------

Bro i have no problem to flashing any rom, bcoz i know i can install any rom with f2fs kernel. Now the satiation is that i can flashed rom if i have f2fs kernel. Now the problem is not related to rom or kernel, it is related to partitions that is already formatted as f2fs & not allowing to mount data & system partition to flash other rom. I tried archi's aroma rom but same issue, the rom starts but says data memory is corrupted.

---------- Post added at 02:13 PM ---------- Previous post was at 01:38 PM ----------

even how would i flash the sammy stock rom, bcoz it needs download mode & i'm unable to go to download mode. It stucks on download mode.
[Galaxy S III Original Android Development] cyrusavirus:
Do the following:-

1. Odin flash philz 4.9x. Please ensure u flash that version only.

2. Format ur partitions.

3. Reboot recovery.

4. Try ur rom.

Regarding download mode... do not use reboot to download mode. Rather use key combination... it would work.
[Galaxy S III Original Android Development] mrjoy:
ohh ****... due to burden on mind i flashed wrong twrp recovery & device won't boot up. Plz help help help
[Galaxy S III Original Android Development] Andr3y29:
I can't understand... What's the problem with your download mode ? Can't you reboot into download by holding down the power button, home and volume down ?
[Galaxy S III Original Android Development] mrjoy:
Ohh thanx, with the help of your advice to goto download mode which i was wrongly trying with reboot button. i flashed correct recovery again. thank god. Now i have to follow yout 1st step downlaod philz 4.3 recovery & tell u later. Thnx

---------- Post added at 02:49 PM ---------- Previous post was at 02:44 PM ----------

It solved now thanks mate. But the again problem starts to find out the solution to format partition on correct state to remove f2fs restrictions..

---------- Post added at 02:50 PM ---------- Previous post was at 02:49 PM ----------

Sir I'm unable to find Philz 4.9

version. I think its too old & there not available. I found only from 5.03 version.
[Galaxy S III Original Android Development] Andr3y29:
If you still have TWRP 2.7 boot into recovery, select Wipe, and then "format data", not "Advanced Wipe". It will ask you to type "yes". Type it and press "Enter". That's how I ussualy get back to ext4 from f2fs when I am in trouble. And I think from now on noone should try F2fs, unless they have lot of free time to spend and they re relly calm. I got tons of errors with f2fs. Also, had to install Windows again on my PC, so almost 1 full day my phone just sat on the table...
[Galaxy S III Original Android Development] mrjoy:
I was trying with this guide but adb gives error

adb pull error: more than one device and emulator

Even i'm using adb 1st time

---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------

i did same but its says unable to mount data partition
[Galaxy S III Original Android Development] cyrusavirus:
http://xdaforums.com/showthread.php?t=2002953

In 2nd post, you would find older versions.... download for i9300....
[Galaxy S III Original Android Development] mrjoy:
Just quick question. Thanx to all. I have successfully flashed stock rom & hopefully the f2fs filesytem removed now from my device's partitions. But now to flash my choice rom it needs to root 1st, but odin does not detect my device... I'm trying from much time. How i can root without going to download mode, even the stock recovery is too old & not flashing superSu root zip file....
[Galaxy S III Original Android Development] cyrusavirus:
Hmmmm.... are u using odin3 v1.85?... if ur computer is able to detect ur phone in normal mode... it would detect it in download mode as well... just ensure u have downloaded and installed samsung drivers.... and let the computer install drivers in download mode as well.....

Follow chainfire's method
[Galaxy S III Original Android Development] mrjoy:
yes my pc detects my device so that i was able to flashed stock rom, even right now my pc detecting my device in normal mode but after goes to download mode nothing happens, even not showing any popup message on pc.
[Galaxy S III Original Android Development] cyrusavirus:
Change the usb port.... if fails then try restarting your pc.....if you have another usb cable or pc... try that as well....
[Galaxy S III Original Android Development] mrjoy:
i already tired to another usb port even did restart pc. Sir i want tell you that i bring my friend's galaxy s3 mobile & checked this, it worked & detects in download mode. Then what could be the problem. I'm confused. I wonder if downloaded wrong firmware from site. Bcoz didn't download from sammobile........

---------- Post added at 09:01 PM ---------- Previous post was at 08:51 PM ----------

sir i checked. The firmware is well downloaded. Bcoz for experiment i flashed same stock firmware to my frnd's device but this i didn't use odin for pc, I flashed this in device with mobile odin pro & this apps flashed with re-root & detects in download mode tooo. But devices gets flasjed by odin for pc & this didn't root the mobile & not detecting the device in download mode. So overall the problem might be with root. So i have to root. But how?
[Galaxy S III Original Android Development] Andr3y29:
If I were you, I would download the latest recovery I want ( recommending latest Philz 16.9.3 I think it is) from my phone because I guess you can connect it to WiFi, and then flash it using your current recovery. Then I would reboot recovery and BOOM. I have a new recovery able to flash SuperSu. You can also try to download latest SuperSU.zip and flash it with your actual recovery. As I said, I reinstalled Windows yesterday, and all my drivers were gone, like my phone thanks to f2fs :| I downloaded latest Google drivers with the latest Android SDK. Still my phone could not be recognized in the download mode by Odin. I let it connected to PC while I downloaded latest Kies (the simple one, not Kies 3, as SGS3 is launched before Note 3. While Kies it was installing, Windows started installing drivers and it was finally recognized by Odin. Try this to use Odin later.
[Galaxy S III Original Android Development] mrjoy:
i didn't understand properly. Mean how i can download recovery from device? from play store? what you say that you can connect to wifi? Yes i connected to wifi then what should i do to download recovery?
[Galaxy S III Original Android Development] Andr3y29:
Download this: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300/philz_touch_6.19.3-i9300.zip and then flash it via your recovery that is already installed on your device.

L.E. Look what I've found while I was searching for somethingt to help you: http://xdaforums.com/galaxy-s3/orig-development/samsung-galaxy-s3-unified-toolkit-v7-0-t1703488 I don't know how it works. Never used it.
[Galaxy S III Original Android Development] mrjoy:
But this rom is not rooted & the stock recovery is too old & how it flash the philz recovery. Ok will give try
[Galaxy S III Original Android Development] mrjoy:
i tries philz recovery to flash with current recovery but didn't flash. I'm sending you snapshot of current recovery so that you can know what recovery i have.
[Galaxy S III Original Android Development] Andr3y29:
​

Ah.. I forgot that when you flash a stock ROM it automatically flashes the stock recovery. I thought you still have the recovery you used to get back to ext4 from f2fs. I tried you to say in the other post that my phone also didn't get recognized by PC. I installed Kies: http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP#none . Kies, not Kies 3, solved my problem.

This it will install the drivers and your phone will be recognized in the download mode by Odin.
[Galaxy S III Original Android Development] mrjoy:
Thanx all. Finally all problem solved. I changed the cable & pc detects my device in download mode & i rooted with new recovery & my device now out of danger from f2fs :) heheheheheheh

---------- Post added at 10:54 PM ---------- Previous post was at 10:50 PM ----------

Special thnx to Andr3y29 & cyrusavirus which helps me most & great. Thank U very much. Even i pressed thanks button too u. ;)
[Galaxy S III Original Android Development] spoonymoon:
This thread is history....

No more support because most in here couldent spare a couple $
[Galaxy S III Original Android Development] BradleyR2010:
where is the link to the post where he said this?

Please stop posting crap like this, unless there is an official statement from Dertufel which i havent read anywhere in xda.
[Galaxy S III Original Android Development] spoonymoon:
there´s no thread..thats excatly the problem, der Teufel is well we know that, he´s posting in other forums, so he´s ok!

you that´s slightly closer too him, should at least have gotten a pm from him about this..but you obvious haven´t...

open your eyes mate ;)
[Galaxy S III Original Android Development] Mostafa Wael:
spoonymoon, can you please tell me when was the latest derteufel's post in the

"other forums"?

i do not see him posting even in the Note II forum, where else would he post? :confused:

Sorry my bad english might sound a bit harsh, but all what i want from you is to verify what you said...

i am pretty sure Dominik has his own life problems and he will be back in a couple of days, if he is not already back to improving f2fs....

---------- Post added at 10:44 AM ---------- Previous post was at 10:34 AM ----------

i am now between two fires

Should i change back to ext4? or keep on f2fs?

F2FS: gives me a buttery smooth experience on almost every ROM so it rocks!!!! but the problem is that Derteufel is not posting any updates or details or anything so there is a problem with compatibility with newer ROM nightlies!!! "like CM11 recent initramfs changes" so you will be limited to a certain nightly and can not update.. :( Also it is in alpha stage so expect any problems at any time "i think we are already dealing with this for a long time.... :D"

EXT4: normal filesystem that will not get your mobile enjoyable as f2fs, But you will have the freedom to change kernels, update ROM nightlies to the latest and if the kernel hasn't been updated, you can always remain on stock kernel until the kernel dev back you up with the latest changes.....

that is my own overview about both filesystem...

which choice do you think is the better? EXT4 or F2FS

i think a poll will be quite helping..
[Galaxy S III Original Android Development] zeljkobo12:
I have same doubt, and will wait for some more time, but eventually we will have to change kernel.

Sadly, because it is really great experience with Devil kernel and recovery.
[Galaxy S III Original Android Development] Andr3y29:
You can also try Agni
[Galaxy S III Original Android Development] lmulli:
+1

A very active Kernel dev who updates on a regular basis. Comes with F2FS support built in and works a treat. A very underrated kernel imo.
[Galaxy S III Original Android Development] zeljkobo12:
Yes, but if I understand correctly Devil kernel is the only option when it comes to Dual Boot :(
[Galaxy S III Original Android Development] Moster2:
I have to revise my last statement that the latest nightlies fixed the issue with custom kernels. I compiled a version that supports the latest versions of cm and other aosp roms that implemented the multisim support.

I tested it and it seems to work. Maybe someone else can confirm that.

Google Docs Download
[Galaxy S III Original Android Development] francescozanghetta:
[MENTION=4196889]DerTeufel1980[/MENTION]

A small reward for your great work! I hope you will carry on ;)

8C256505726119518
[Galaxy S III Original Android Development] xeizo:
Great initiative, I will test but not until tomorrow :)
[Galaxy S III Original Android Development] Mostafa Wael:
Thanks Moster2 will try this kernel with latest CM11 soon!!!
[Galaxy S III Original Android Development] FadeFx:
Good initative indeed, but please nake your own thread and dont pollute [MENTION=4196889]DerTeufel1980[/MENTION]'s thread with stuff he didnt build.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] Moster2:
Im not going to make a new thread. Its his kernel, same toolchain, same code, just with a small fix regarding latest changes in cm.
[Galaxy S III Original Android Development] DaReDeViL:
But you'll have to answer questions about your selfmade build in derteufel's thread. So please consider creating a seperate thread mentioning that it's a continuation of derteufel's great work.

Of course I congratulate you for the initiative and wish you good luck ;)

Envoyé de mon GT-I9300 en utilisant Tapatalk
[Galaxy S III Original Android Development] Moster2:
Yes, but I really didnt do anything special. Its not worth to open a thread for that. The patch for that was even in the hellybean kernel sources. So everyone could have done that. Im just providing it for the people here.
[Galaxy S III Original Android Development] DaReDeViL:
As you like ;)

Envoyé de mon GT-I9300 en utilisant Tapatalk
[Galaxy S III Original Android Development] Andr3y29:
Have you thought about continuing this project ? Like Devil was the continuation of the Perseus kernel, you can start a new one. I even saw here few people that are willing to donate for Devil to continue ;)
[Galaxy S III Original Android Development] Moster2:
It is interesting of course, but I lack the knowledge of kernel development so far. I would need to learn a lot :D

Im also sure that DerTeufel is only busy with some other stuff and will return soon.
[Galaxy S III Original Android Development] DerTeufel1980:
new try for omni. i am optimistic :)
[Galaxy S III Original Android Development] serkaon:
No. Boot loop. I'm using cwm 6.0.4.4 and is this a problem for devilkernel??

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Original Android Development] DerTeufel1980:
No, the recovery does not matter.

Can you try to get a logcat?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] serkaon:
How can i do this??

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Original Android Development] DerTeufel1980:
By using adb

More important would even be this:

adb shell

cat boot.txt

For logcat

adb shell

logcat > sdcard/logcat.txt

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
anyway...new omni test. this one most probably does not work for cm11...

http://www.mediafire.com/download/4pa54g5usgj0gra/Devil2-1.5.3-i9300-DUAL-20131125.zip

upload didnt work here
[Galaxy S III Original Android Development] Zocker Tko:
thx 1.5.3 is booting on omni:D
[Galaxy S III Original Android Development] temasek:
I've to admit your passion and determination are beyond words.

An asset to i9300 community.

Kudos
[Galaxy S III Original Android Development] serkaon:
Thank you so much. İt runs very well.

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Original Android Development] DerTeufel1980:
Thanks. I just don’t like things not working.

Would you mind trying it on your rom

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Zocker Tko:
will try temasek v9 (downloading now) as first rom and omni as second rom with 1.5.3 kernel, but when it not work maybe is it possible to switch your kernels (1.5.0 and 1.5.3) via recovery to boot in each rom?

sry for bad english
[Galaxy S III Original Android Development] DerTeufel1980:
This would be possible as a work around

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Zocker Tko:
wowwwwwwwwwwwwwwww

it works with .1.5.3

first rom temasek v9

second rom omni

both are booting and running fine

big thanks
[Galaxy S III Original Android Development] temasek:
But I wonder why u want 2 aosp roms in a single device? :D
[Galaxy S III Original Android Development] Zocker Tko:
hehe i cant me decide;)
[Galaxy S III Original Android Development] temasek:
Omni is better.
[Galaxy S III Original Android Development] Zocker Tko:
No, both are wonderful roms, maybe the most wanted and now with the super working kernel i have both:D
[Galaxy S III Original Android Development] DerTeufel1980:
Thank you for testing. :)

That's interesting, this means cm works with initramfs of omni, but omni does not work with cm initramfs. Anyway, great that both are working now.

Anyone tried slimkat on 1.5.3?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] habylab:
Why are there two threads for this kernel? I'm away at the moment so can't tell the difference!
[Galaxy S III Original Android Development] DerTeufel1980:
The other kernel is pre update12 and is not going to be updated again

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DaReDeViL:
Just go ahead, we'll support you as long as you wish ... ;)

Envoyé de mon GT-I9300 en utilisant Tapatalk
[Galaxy S III Original Android Development] PedroJuuu:
Why with 3.4 kernel camera and videos stop working after few minutes/hours? I need to reboot to make it work. Thanks in advance

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] Moster2:
Are you on cm? The camera is pretty unstable in general there, so its not necessarily related to the kernel.
[Galaxy S III Original Android Development] PedroJuuu:
Yes, I'm on CM11 but with stock CM kernel and others this bug does not appear
[Galaxy S III Original Android Development] Moster2:
Ok, I can try and take a look, but as mentioned earlier in this thread Im still pretty new to kernel stuff. So dont expect too much.
[Galaxy S III Original Android Development] PedroJuuu:
Ok, really thank you so much, If you need mi help you can count with it :)
[Galaxy S III Original Android Development] S1ay3r666:
I got a similiar bug.

Playing videos on Youtube,Facebooh,Galerie just work for 2 Times then you can not watch any Video.

After a restart you can watch 2 videos and then the same problem!