Develop Bugs

CM 11 4.4 kitkat issue

I'm using cm9 that has the team win recovery. When I try to flash the cm 11 kitkat rom it says fail. Do i need to use a cwm recovery or is the download link bad ?

mr. ya-di-da said:
I'm using cm9 that has the team win recovery. When I try to flash the cm 11 kitkat rom it says fail. Do i need to use a cwm recovery or is the download link bad ?
Click to expand...
Click to collapse
Flash it from cwm... but after the flash completes, reboot recovery and do you're wipes ( again ) and flash kitkat from it's recovery. Then reboot.
Let it chill for a few minutes, then boot back to recovery and flash you're 4.4 gapps.
This process always worked for me on 4.3 and I'm assuming it will work on 4.4. But I've not flashed 4.4 yet. So proceed with caution.
Good luck...

I will try it when I get home from work so I can use Odin to flash a cwm recovery. Everytime I use mobile Odin to flash a recovery it bricks my phone ....why does that happen ?

mr. ya-di-da said:
I will try it when I get home from work so I can use Odin to flash a cwm recovery. Everytime I use mobile Odin to flash a recovery it bricks my phone ....why does that happen ?
Click to expand...
Click to collapse
I'm not sure about the mobile Odin issue... are you making sure the tar file for the kernel is a good download and that it is compatible with the Android version and rom you're trying to run...?
Try downloading the Directboot EL29 kernel from rwilco12's repo.. ( make sure you get the Directboot EL29 kernel and not the stock el29 kernel )
After you have it and the rom you want on you're sdcard... use mobile Odin to flash the el29 db kernel.. it should boot to recovery on it's own..
Push volume up, volume down, volume up... this enables the power button as the select button...
Do you're wipes... and flash 4.4...reboot recovery... do wipes.. ( data, cache, dalvik, and format system )...flash 4.4 again.. reboot.. settle in for a few minutes and then boot recovery and flash gapps 4.4...reboot.
Let me know how it goes... I'll stick around tonight until we get ya up and running...

It failed.. (status 7)

mr. ya-di-da said:
It failed.. (status 7)
Click to expand...
Click to collapse
Ok... I'll try to get to it tomorrow... but Thursday at the latest.

OK thx. I saw that other people where getting the same fail (status 7) let me know what u find.

Status 7 is a syntax error in the updater script... Probably missing a semicolon or something silly like that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Not related to this issue, unsure if it would be better etiquette to make my own thread for this, but an issue I'm having with dastins CM11 ROM (12-04-13 version) is that I have two "Internal Storages" instead of one (I do not own/use a SD card)
On CM10/10.1/10.2 I had one internal storage, but on CM11 I have a 2GB internal storage and then a second internal storage (that things seem to not be installed to at all) with the remainder of my devices space.
One of the applications I used a lot on stock TouchWiz and earlier versions of CM is larger than two gigs, so on CM11 I can't even install it because it says I have insufficient storage. Is there a way I can combine the two internal storages into one, so it functions like it did on CM10.2 so I can use all of my devices space instead of only 2GB?
---------
Another question, and this one I'm probably just being blind and not seeing it, or maybe this setting is in a different location in KitKat, is my phone is set to USB mass storage instead of MTP. Normally I head over to Settings > Storage > hit the menu key and change USB connection type to MTP, but the menu key doesn't seem to do anything anymore on the Storage page. Where would I change to MTP instead of Mass Storage, or how can I just disable Mass Storage, I honestly don't care about being able to get any files on/off the device, but 90% of the time I'm charging on USB and I just don't want a full screen prompt showing up every time I touch my phone saying "Hey! It's Plugged In! Do you want to turn USB Storage on?"

You need to flash cm11 with the newest cwm... The old regular way of the"safe" recovery doesnt work... The easy way Is to download the blasphemy kernel and install it then boot back into recovery... It will be cwm 6.0.4.5... Flash the rom with this and no status 7...
Hope this helps...
Sent from my SPH-D710 using Tapatalk 2

I have an EL29 direct boot zip file that works with agats and even the newer cwms to flash back to.
I've tested it on the following recoveries and not had an issue at all:
agats (both 1.3 and 1.4), stock twiz, and the latest CWM they are useing.
I have gone to el29 direct boot with all of the above and had no issues, it goes into el29 recovery just fine.
DO keep in mind though I made this zip mainly for flashing into roms, not as a stand alone kernel, so you may have issues wif you use this as your standard go to kernel with the rom. Mst roms already have thier own kernel anyways, so that's normally not an issue, jsut so you are aware this is basically used for flashing roms not as the normal kernel.
I can host it on dev-host if anyone is interested, otherwise I won't bother.....and I ask because sometimes people just don't wanna be bothered, so I always ask......anyways let me know I will host it.
Just as a side note the steps I have done are as follows:
-reboot to recovery
-flash el29 zip file within said recovery (as I said I've tested this on all the above and it works fine)
-reboot recovery (it will be el29 now)
It should be back to the el29 recovery and you can flash from there.
Done this on hood pope (4.3), Viluminati (4.4 and 4.4.1 KitKat), cm10.1 (4.2.2) and stock Twiz rooted (not stock Twiz recovery) but agats recovery 1.3 and 1.4.
Those that don't know how to activate the power button to select what you do is toggle up > down >up > down until it says something about it being activated, you can then just use power to select your option.

kitkat 4.4.1
I rooted my device using rwilcos fl24 method although I was on a fd24 model. After root I flashed a custom recovery using Odin I believe it was agats...I then proceeded to flash a ROM cm10.1 then upgraded to cm 10.2. Now running KitKat 4.4.1 12/7 edition I believe and works like a charm...thought I had a battery problem because it wouldn't charge right it would take forever. I didn't I jus had to stop oc/uv ...BTW using the kernel that came with the rom flashed using cwm recovery from cm10 which was on jb not ICS and works fine little bugs here and there such as attempting to open incognito window fc browser the battery read when phone was off was inconsistent versus when the device is off but other then that KitKat is great if I can help anyone I'll be more then glad to I don't mind helping people that don't know I don't give attitude and noon user friendly,after all I was there once....besides all the guys who really know what thier doing are busy creating Roma and tweakimg programs to keep us happy let's make it a little easier on them like I said I don't know everything but I have some knowledge and if I'm able to point you in the right direction without wasting your time I will

easyrider77 said:
I have an EL29 direct boot zip file that works with agats and even the newer cwms to flash back to.
I've tested it on the following recoveries and not had an issue at all:
agats (both 1.3 and 1.4), stock twiz, and the latest CWM they are useing.
I have gone to el29 direct boot with all of the above and had no issues, it goes into el29 recovery just fine.
DO keep in mind though I made this zip mainly for flashing into roms, not as a stand alone kernel, so you may have issues wif you use this as your standard go to kernel with the rom. Mst roms already have thier own kernel anyways, so that's normally not an issue, jsut so you are aware this is basically used for flashing roms not as the normal kernel.
I can host it on dev-host if anyone is interested, otherwise I won't bother.....and I ask because sometimes people just don't wanna be bothered, so I always ask......anyways let me know I will host it.
Just as a side note the steps I have done are as follows:
-reboot to recovery
-flash el29 zip file within said recovery (as I said I've tested this on all the above and it works fine)
-reboot recovery (it will be el29 now)
It should be back to the el29 recovery and you can flash from there.
Done this on hood pope (4.3), Viluminati (4.4 and 4.4.1 KitKat), cm10.1 (4.2.2) and stock Twiz rooted (not stock Twiz recovery) but agats recovery 1.3 and 1.4.
Those that don't know how to activate the power button to select what you do is toggle up > down >up > down until it says something about it being activated, you can then just use power to select your option.
Click to expand...
Click to collapse
There's a tread that might use your assistance
Sent from my d710 using XDA Premium 4 mobile app

CM 4.4.1 build 2013-12-07
Hey guys...Been rocking this build for a month now with no real problems. Only a couple of things i have noticed and thought I would drop in and mention since I haven't heard about it talked about in the main thread or here yet.
1. Every once in a while I will be showing full 3g bars and wont connect to the internet (says "no connection") I have fixed this with just toggling off and then back on the Sprint Radio Toggle in the drop down window. The phone will then immediately connect after.
2. During the first 2 weeks the camcorder was working...now its just borked. Every time i try to use it, it will just freeze up (the camcorder) and then force close. Then the camera is also unresponsive after trying to use the camcorder. I have tried to clear catch and force stop but the only way to fix this is with a reboot.
SPH-D710 EL26.....flashed to Boost Mobile with working Hangouts MMS and SMS from day one (no fix)
Build; 4.4.1 2013/12/07
Everything else is just ROCK SOLID, and love this ROM.

adjday said:
2. During the first 2 weeks the camcorder was working...now its just borked. Every time i try to use it, it will just freeze up (the camcorder) and then force close. Then the camera is also unresponsive after trying to use the camcorder. I have tried to clear catch and force stop but the only way to fix this is with a reboot.
Click to expand...
Click to collapse
This Camera Fix worked to get my camcorder working perfectly. Have you tried it? http://forum.xda-developers.com/showthread.php?p=48620791&highlight=3a04f599232ee62c6b63a6e4f1d3f7d3#post48620791

You can uninstall the gallery app (using titanium backup)
Then download and install a different Kit Kat gallery app...(just search google, it's everywhere Lol)

[RECOVERY][Unofficial][Epic4GTouch] TWRP 2.6.3.0 touch recovery [2014-02-11]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
Latest Builds Here
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.[/QUOTE]

Links are up enjoy the light show
Twrp now has haptic feedback.

Wow...first post. I thought this would explode...Lol.
Great job dev.

Like the haptic... Thanx!
Sent from my SPH-D710

Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.

EVObastard said:
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
Click to expand...
Click to collapse
This recovery is pretty useless if you're not going to flash a Kit Kat ROM.

HighxVoltage said:
This recovery is pretty useless if you're not going to flash a Kit Kat ROM.
Click to expand...
Click to collapse
It works to flash jb+ I first built twrp when I was on stock then I flashed jb and went to 4.4
Sent from my SPH-D710 using Tapatalk

This is a repost of the twrp from a while back right?
sent from tumblr
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
EVObastard said:
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
Click to expand...
Click to collapse
I've used an older version of twrp. I install it through Odin then upgrade to this one.
sent from tumblr

@Linux guy this is a new build hint why it has haptic feedback.
Sent from my SPH-D710 using Tapatalk

Working great on my E4GT. Thanks
☞"And on the eight day the Lord made a backup"☜

Any chance for v2.7.0.0 in the near future?

CrimsonKnight13 said:
Any chance for v2.7.0.0 in the near future?
Click to expand...
Click to collapse
This is 2.7 basically I wait for major changes but probably in a week

Unjustified Dev said:
This is 2.7 basically I wait for major changes but probably in a week
Click to expand...
Click to collapse
Thanks! I look forward to your next release.

Any updates regarding 2.7 being compiled & released?

How does one flash this?
I downloaded the file, but don't see any instructions on how to flash this on the phone. I installed Goo Manager. From the menu, when I select "Install OpenRecoveryScript", I get the toast "No recoveries were found for your device"

os2baba said:
I downloaded the file, but don't see any instructions on how to flash this on the phone. I installed Goo Manager. From the menu, when I select "Install OpenRecoveryScript", I get the toast "No recoveries were found for your device"
Click to expand...
Click to collapse
Can't use goo for this phone... Simply install it from the current recovery you have now...
Sent from my SPH-D710 using Tapatalk

dirtyhewr said:
Can't use goo for this phone... Simply install it from the current recovery you have now...
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I don't have the phone with me. But it looks like I have the stock recovery. At least it doesn't look like either CWM or TWRP. I downloaded it as a zip file (Twrp_6.3_Unofficial_20140211_d710.zip) from http://www.androidfilehost.com/?w=files&flid=12045. Should I just rename it as update.zip and install it from the stock recovery?

os2baba said:
I don't have the phone with me. But it looks like I have the stock recovery. At least it doesn't look like either CWM or TWRP. I downloaded it as a zip file (Twrp_6.3_Unofficial_20140211_d710.zip) from http://www.androidfilehost.com/?w=files&flid=12045. Should I just rename it as update.zip and install it from the stock recovery?
Click to expand...
Click to collapse
This is not for stock ROMs. You should probably read up some more in this device
Trolling from my SPH-D710 using Tapatalk

Surj138 said:
This is not for stock ROMs. You should probably read up some more in this device
Trolling from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Okay. Thanks. I'm a long time Android user (from G1 days). New to the S2 though. I have to use the S2 for a couple of months. I thought of installing Cyanogenmod KitKat. But lack of 4G is a deal killer. So I'm probably going to stick with the stock ROM. I just wanted to use TWRP so I can do system backups. From what you are saying, that doesn't seem to be an option. Strange. I have never had this issue on any other phone. I have changed the recovery on G1, HTC G2, Vibrant, Galaxy S3, LG G2, HTC One, Nexus 4, 4, 7, 10. I'll have to read up to see why I can't do that on the Galaxy S2.

os2baba said:
Okay. Thanks. I'm a long time Android user (from G1 days). New to the S2 though. I have to use the S2 for a couple of months. I thought of installing Cyanogenmod KitKat. But lack of 4G is a deal killer. So I'm probably going to stick with the stock ROM. I just wanted to use TWRP so I can do system backups. From what you are saying, that doesn't seem to be an option. Strange. I have never had this issue on any other phone. I have changed the recovery on G1, HTC G2, Vibrant, Galaxy S3, LG G2, HTC One, Nexus 4, 4, 7, 10. I'll have to read up to see why I can't do that on the Galaxy S2.
Click to expand...
Click to collapse
This device is different because the recovery comes bundled with the kernel. This particular recovery is only for kk aosp ROMs... It overwrites the recovery those ROMs come with (CWM).
There are custom kernels for stock ROMs that come with a custom recovery. If you're on stock JB I recommend Agats 1.3
Trolling from my SPH-D710 using Tapatalk

[recovery]TWRP 2.8.0.0 v2 for e98x[TEMP CLOSED]

Temporarily forget it. Link removed.
TWRP 2.8 v2 for e980.
Fixed auto-loki support.(But there will be a weird floating loki option, i will fix the position of it when i have time)
Should be no longer have secure boot issue after flashing kernel.
Reboot-into-recovery-loop bug still presents, always prepare madmack's twrp for e986 hack, in case boot-loop happens!
When recovery-loop happens, please flash madmack's hacked TWRP 2.6 for e986(please see post #23), then reboot into madmack recovery(you can install back my recovery in this step), reboot system, the recovery-loop will stop.
I am not able to solve this bug, as with Philz touch also has this bug and never solved.
**This recovery will only cause recovery-loop. All other bootloop will not be cause by this recovery!**
**I held no responsibility for any damage due to the use of this recovery.**
Features:
1)Full nandroid backup is much faster on TWRP than on CWM / PHILIPS TOUCH.
2)Ability to format any partition into F2FS/EXFAT/FAT/EXT2/EXT3/EXT4, and read/write all these format partitions.(don't use F2FS format until a compatible kernel and rom come out.)(I am using stock at this moment, still love stock, but failed to make stock rom fully compatible with F2FS, what a pity!)
Download it from attachment.
Backup anythings important.
Flash through recovery.
Enjoy!
Wing
P.S. I am **not** a developer, so I **may not be able to** fix any bugs if you encounter!
P.S. Again, i am using phone network at home, which have data usage limit, so the source will be uploaded when i can use wifi.
P.S.I am not programmer, I used very long time to understand what is what, if you think this recovery is useful, consider make a donation!

Wow, thanks! Working great!

Wow .thank you so much .already flashed waiting for new build to test .will report back .thanks again
---------- Post added at 03:01 AM ---------- Previous post was at 03:00 AM ----------
Keep this thread alive

Actually, the thing i actually want/try to do is to add F2FS support to CM kernel and whole CM rom.
Since i am not a developer, i use a lot of time try to figure out what need to patch and failed.
I used too much time and can't understand what make the compile fail and give up.
Then I do the next thing I want to do: compile a fully working twrp to replace the easily boot-loop PhilZ Touch recovery.
This TWRP is actually a side product of my failure attempt.
(ha, i still don't have right to post external links, so i will put the TWRP e980 compile method and source up later)
Wing

Great job man .thanks

mukwing said:
Actually, the thing i actually want/try to do is to add F2FS support to CM kernel and whole CM rom.
Since i am not a developer, i use a lot of time try to figure out what need to patch and failed.
I used too much time and can't understand what make the compile fail and give up.
Then I do the next thing I want to do: compile a fully working twrp to replace the easily boot-loop PhilZ Touch recovery.
This TWRP is actually a side product of my failure attempt.
(ha, i still don't have right to post external links, so i will put the TWRP e980 compile method and source up later)
Wing
Click to expand...
Click to collapse
how did u build i could help i have linux on virtual mmachine on windows 8.1

bountyman334 said:
how did u build i could help i have linux on virtual mmachine on windows 8.1
Click to expand...
Click to collapse
Attached is the patch file for cm kernel to make it support F2FS.(I forget where to get)
Not all codes can be patched sucessfully, some I need to modify the kernel sources by hand.
It seems some codes will lead to compile error, but i am not programmer, I don't know how to adjust.
I am using up-to-date CM sources, without modification, i can compile unofficial cm build successfully for my own test.
Wing

Forget this patch. I think this patch might be outdated.
I am trying to investigate the commits about F2FS in Nexus 5 CM F2FS kernel sources.
Will try to merge these commits to see if it can compile.
If I sucessfully getting a F2FS supported CM kernel, will try to make a F2FS supported TWRP.
Making CM rom to support F2FS seems to be easy, there exists some tools ready to do it.
Wing

Thank you so much for you hard work

I finally learned how to correctly patch kernel commits!
Good news. A F2FS suppported kernel has been successfully compiled!
(need testing, but need to compile F2FS suppported TWRP and ROM before i can test.)
Next step, F2FS suppported TWRP.
Wing

I can't find resources of how to modify TWRP 2.8.0.0 to support F2FS for our device.
But the modified KT-TWRP from the following
http://forum.xda-developers.com/showthread.php?t=2778248
I can compile it successfully against e980 CM sources.
So, I get F2FS supported TW-TWRP working on my phone.
I still haven't try format partition to F2FS.
Will report if it works later.
I don't want to be another failure, used me sooooo much time to research.
Wing

version?
It says in the flash screen that it is madmack's 2.6.1.0 only.
I am confused..
Edit - but the recovery header says it is 2.8.0.0
XD
Edit 2 - It has messed up with the phone. Not able to get into the ROM. only boots into the recovery. Tried philz recovery and then tried to boot again but it isn't working anymore.

mukuluppal said:
It says in the flash screen that it is madmack's 2.6.1.0 only.
I am confused..
Edit - but the recovery header says it is 2.8.0.0
XD
Edit 2 - It has messed up with the phone. Not able to get into the ROM. only boots into the recovery. Tried philz recovery and then tried to boot again but it isn't working anymore.
Click to expand...
Click to collapse
It say madmack's 2.6.1.0 because i use madmack's old zip and replaced the recovery.
If in the boot-into-recovery loop, install philz recovery, then install TWRP again should fix it?
BTW, is it caused by wiping of /data?
Again, i am not programmer. I will try to find out reason to see if i can fix it.
Wing

mukwing said:
It say madmack's 2.6.1.0 because i use madmack's old zip and replaced the recovery.
If in the boot-into-recovery loop, install philz recovery, then install TWRP again should fix it?
BTW, is it caused by wiping of /data?
Wing
Click to expand...
Click to collapse
Yeah i tried that and it didn't work.
So i tried a bunch of my old recoveries and the twrp e986 hacked one worked.
Now i can see ext card too in twrp. But that's not your recovery. It's old one.
No it didn't happen coz of wipe data.. After flashing it,the recovery boot started.

Failed to find out why has this bug on this recovery. Sorry.
Btw, testing of F2FS gave me soft brick of my phone. When I returned to stock, I surely love the smoothness of original stock lg 4.1.2. So I may stay with stock for a while.
When I feel too boring with stock again, I will return to cm and try compiling something to have fun again.

recovery updated.
please test!
Wing

If anyone tests this out let me know if the Loki works because last time I tried it it made my phone soft brick. It was an easy fix to unbrick it but I'm hoping it doesn't do that anymore.

mukwing said:
recovery updated.
please test!
Wing
Click to expand...
Click to collapse
So..
If you go to install,there is a "Loki support" floating checkbox that won't go away...
If you try to Enable MTP and actually try to copy something to internal SD card, recovery reboots and copy fails (I noticed that you can still delete stuff).
It also got me a bootloop when flashing a rom, I had to recover through download mode and a KDZ...
Bunch of issues that are pretty noticeable, OP,are you even testing this on your phone before sending it out risking other phones?

The floating Loki doesn't affect the usage much.
And the boot loop have been mentioned using madmack 2.6 e986 to solved.
Sorry, will never share anything again.

Jeez....
2SHAYNEZ

[DEV][KERNEL][13 NOV] Convert EXT4 to F2FS [BETA]

I thank @frantisek.nesveda for his Agnostic-kernel - partition independent kernel flasher on which I base this. I also thank everyone he thanks. Additionally, I thank anyone who posted about F2FS and formatting partitions. I read a lot of threads and I’m sure I gleaned something from everything I read.
For now this has to be done after flashing your preferred firmware (ROM). I recommend you make all your desired changes especially changing kernels.
Copy the files to your sdcard where you typically put flash files. I recommend an external card, because this is the only way I do it and I have not tested the other way. If you put it on your internal card it needs to be outside the /system and /data partitions because you'll lose them during formatting.
Also, I have only tested this on PhilZ Touch 6.58.9 recovery. I would appreciate anyone testing on other recoveries if you find one that supports f2fs.
If you are not on PhilZ 6.58.9, flash the zip and reboot to recovery.
Make a full back up of your ROM.
I also recommend you have an Odin based recovery plan. During my trials I ended up with a blank screen and used Odin to get back. This may not be the case with this latest PhilZ.
Format the partitions to f2fs.
It is in "Wipe and Format Options", then "Custom Format Options" then "Toggle f2fs <-> ext4 migration"
Remember, to format data you pick /sdcard. Also, this will remove everything on your internal card.
See warnings in post #2
I include a testF2FS zip to confirm the formatting.
Then use custom restore to get the data and/or the system from the backup. You can skip cache since it gets rebuilt.
Then flash GS3-F2FS-kernel-fstab-Fixer to adjust the kernel boot image to support the new formats.
This only fixes the fstab and if the kernel does not have f2fs support it will not work.
As always, no one is responsible for what happens to your phone. Everyone does this on their own and at their own risk.
Please do NOT mirror these files.
It appears to only work with the PhilZ recovery I built. If someone finds another please let us know.
Also, it does not work on TouchWiz ROMs. If someone finds one that it does work on please let us know.
Do not use the phone setting Factory Data Reset
XDA:DevDB Information
F2FS, Tool/Utility for the AT&T Samsung Galaxy S III
Contributors
RoryB
Version Information
Status: Beta
Beta Release Date: 2014-11-13
Created 2014-10-21
Last Updated 2014-12-06

Reserved
Latest files on Android File Host
Remember, to format data you pick /sdcard. Also, this will remove everything on your internal card.
Do not factory reset through the phone settings. This appears to format as ext4 and does not keep your formatting.
If you do you would need to try the f2fs fixer before rebooting. I have not so let us know how it goes if you try.

[OLD WAY]
For now this has to be done after flashing your preferred firmware (ROM).
Copy the files to your sdcard where you typically put flash files. I recommend an external card, because this is the only way I do it and I have not tested the other way. Also, I have only tested this on PhilZ Touch 6.48.4 recovery. I would appreciate anyone testing on other recoveries.
Make a full back up of your ROM.
It seems it is best to get everything the way you want before the back up, including any kernel changes.
I also recommend you have an Odin based recovery plan. During my trials I ended up with a blank screen and used Odin to get back.
Flash the zip file for what format you want to change. I include a testF2FS zip to confirm the formatting. For some reason it sometimes takes more than one try to format the partitions. Sometimes rebooting recovery helps before trying to confirm the formatting.
NOTE: Sometimes the phone reboots on its own while formatting. Be prepared to press the home and volume up buttons for two vibrations to get back to recovery. The first is the final power down and the second is the powering up. Remember to wait for the blue text in the upper left corner.
Then I use custom restore to get the data and/or the system from my backup. You can skip cache.
Then I flash GS3-F2FS-kernel-Fixer to adjust the boot image to support the new formats.
This only fixes the fstab and if the kernel does not have f2fs support it will not work. If they are getting upstream changes they should have it.
As always, no one is responsible for what happens to your phone. Everyone does this on their own and at their own risk.
Please do NOT mirror these files.

yahoo!!!! thank you for what had to have been alot of research , testing , and i cant imagine what-nots.:victory:
will try out tonite and report back
err on the side of kindness

Saving my response until after class... Thus is awesome
Sent from my HTC One_M8 using XDA Free mobile app

Look forward to testing tonight! Will post with results when I have them
Sent from my CARBON-SGH-I747

TheSchatz said:
Look forward to testing tonight! Will post with results when I have them
Sent from my CARBON-SGH-I747
Click to expand...
Click to collapse
Two different phone both liquid ROM. F2fs all versus f2fs none

Thanks again Rory!!

Didn't work for me in TWRP, with latest Carbon Nightly. Just finished in about two seconds, and the test zip failed, indicating nothing changed.
Next step is a CWM I guess!
Sent from my CARBON-SGH-I747

TheSchatz said:
Didn't work for me in TWRP, with latest Carbon Nightly. Just finished in about two seconds, and the test zip failed, indicating nothing changed.
Next step is a CWM I guess!
Sent from my CARBON-SGH-I747
Click to expand...
Click to collapse
I tried some stuff before with formatting partitions in twrp and it always failed. Even the newest 8.whatever just freaks out with unrecognized file system. I've not been a fan of philz ever before, but since that's what is working I Will adapt

aircooledbusses said:
I tried some stuff before with formatting partitions in twrp and it always failed. Even the newest 8.whatever just freaks out with unrecognized file system. I've not been a fan of philz ever before, but since that's what is working I Will adapt
Click to expand...
Click to collapse
I guess Philz it is, as latest CWM failed in the same fashion.

Yeah, same here with CWM.
Running vanilla CM11. Took a full nandroid, formatted system, cache, and data with Philz. Restored nandroid, installed latest Quantum kernel and flashed the kernel fix.
Everything is up & running, but performance has downgraded. AnTuTu score down by about 20%. I have seen other f2fs discussions that said it needs time to settle in, so I'll let the phone on all night and check it in the morning.

Just some more scores I am not too sure what to make of. But obviously f2fs has the edge.
Html5 test seems a bit fictitious but again shows f2fs showing some advantage....... If more birds is a good thing that is.

one more to confirm: failed with twrp 2.6.3.1 . tried multiple times. running Q v3.66 with appropriately dated kernels = QK / dkp / BMS .
ohh philzzz , where are you ? time to come and play.!
err on the side of kindness

mrrocketdog said:
one more to confirm: failed with twrp 2.6.3.1 . tried multiple times. running Q v3.66 with appropriately dated kernels = QK / dkp / BMS .
ohh philzzz , where are you ? time to come and play.!
err on the side of kindness
Click to expand...
Click to collapse
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/
I used one for d2lte. Please ignore the update to latest binary message

TheSchatz said:
Didn't work for me in TWRP, with latest Carbon Nightly. Just finished in about two seconds, and the test zip failed, indicating nothing changed.
Next step is a CWM I guess!
Sent from my CARBON-SGH-I747
Click to expand...
Click to collapse
Remember, sometimes it takes a few times. I've been trying things like adding sleeps to "rest" between each format command. It did not help. I sometimes had to format, reboot to recovery, format again and then maybe it showed up as changed.
I think I got things mixed up. I have to set up boot image to support the new format and then flash quantumkernel. I"ll update the first post.
Yup, I use this one https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.zip

RoryB said:
Remember, sometimes it takes a few times. I've been trying things like adding sleeps to "rest" between each format command. It did not help. I sometimes had to format, reboot to recovery, format again and then maybe it showed up as changed.
I think I got things mixed up. I have to set up boot image to support the new format and then flask quantumkernel. I"ll update the first post.
Yup, I use this one https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.zip
Click to expand...
Click to collapse
Well, now I can't get past the kernel splash. Philz finally sees everything as f2fs, but I can't mount data at all... I've managed to royally screw up everything, lol. Off to Odin, I'll try again sometime but it's a no go for now.
Thanks for the files though, I'm really excited for the opportunity!

TheSchatz said:
Well, now I can't get past the kernel splash. Philz finally sees everything as f2fs, but I can't mount data at all... I've managed to royally screw up everything, lol. Off to Odin, I'll try again sometime but it's a no go for now.
Thanks for the files though, I'm really excited for the opportunity!
Click to expand...
Click to collapse
Yes, formatting is a bit wonky but the test zip file is very helpful. After formatting I'd run the test zip till desired partitions showed f2fs and not unknown. I also rebooted recovery before restoring. That custom restore really messed me up and I had to have only one back up to keep stuff straight. Then the fix file and a reboot. I only flashed qk 10.11 after it was all running.
Don't know if This will help anyone but it worked for me.

aircooledbusses said:
Yes, formatting is a bit wonky but the test zip file is very helpful. After formatting I'd run the test zip till desired partitions showed f2fs and not unknown. I also rebooted recovery before restoring. That custom restore really messed me up and I had to have only one back up to keep stuff straight. Then the fix file and a reboot. I only flashed qk 10.11 after it was all running.
Don't know if This will help anyone but it worked for me.
Click to expand...
Click to collapse
Eventually everything read f2fs, but I wasn't doing any data restoration. I was just going to start with a fresh rom install, but that's when I was stuck on the kernel splash with no adb. I'll probably try again tonight after work, maybe I'll have better luck!
Sent from my CARBON-SGH-I747

Many ROMs have format built into their updater script and that would undo your format to f2fs unless the ROM is written to support it.

[MOD][12 GEN 2015] [D851] Multirom

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Lg G3. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-d851.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_d851_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
Check on my github...
Credits: @tassadar for the awesome work; @invisiblek and @savoca @patrik.KT for them help
@Tectas cause i used his ( awesome) source code for building the kernel
And sure... tnx to @arifqur and @SonjaMichelle for testing this
...and all the people that now i forget

PLEASE READ THE MULTIROM WIKI TO UNDERSTAND BETTER WHAT YOU ARE DOING
IMPORTANT: Need to be with a Kitkat stock Rom ( if you use my kernel ) or with a rom that have a kernel with the kexec hardboot patch.
HOW TO INSTALL:
1- reboot in recovery and flash the new TWRP with Multirom support; --> HERE
2- reboot the recovery;
3- flash the kernel with the kexec hardboot patch HERE
4- flash the multirom zip; ---> HERE
5- install every Rom you want ( advanced--> multirom --> add rom )
6- reboot and choose the rom you want to boot.
You can also use a Cyanogenmod or similar with the wonderful Rin Kernel by @Tectas --> DOWNLOAD FOLDER
If you want show me your love for this you can consider a small DONATION
Issues:
1- On boot the touch need some seconds to work in multirom menu, you can use the volume keys to move and the power button to select.

another one

Was the first one to get it working on my D851,
Thanks to the OP.
Man you are definitely a very gifted developer as you did not even have the device and got everything to work on the first try.
Brilliant stuff my man.
You deserve the best.

I was the second one to test and run MultiROM this morning. skin1980 does excellent work! I could barely keep up. :good:
So far I've installed the stock factory ROM, SkyDragon 1.1.0 and Fusion5.0 (1/11/15). I have been able to swap the primary ROM with the secondary ROM and back again, install from backup and install from zip. Installing PA-gapps was a cinch when installing Fusion.
So far so good.

First and foremost, THANK YOU @Skin1980!!!!!!!!!!!!!!
Two quick questions though after reading Multiroms wiki page and the information provided in the OP.
1. Do you have the compatible uninstaller zip file compiled for the d851? (On the wiki it states that in order to fully remove multirom you have to flash an uninstaller) - Not that I plan on removing multirom, TRULY AWESOME & THANK YOU!!!, but better safe than sorry....should something go wrong... (yes, I am currently backing up my phone & will be placing it on my computer prior to diving into this fun)
2. After reading Multirom's WIKI, I know it states you can load ANY rom once you have everything setup, but does that include having both 4.4.x & 5.0 roms at the same time -- stated more plainly, Can I flip between Kitkat and Lolli with this??? (I was always taught, "If something seems too good to be true......")
But if it is true, aww man, you just answered my prayers!!! (Stock based KK @ home for wifi-calling (TMO has no signal @ my house) and L @ work cause I'm impatient and can't wait for TMO any longer to rollout 5.0)
I know it's been my burden to bear, but flashing twice a day just to enjoy L for part of my day has become tiresome....lol
Sorry about the long post, but thanks again for porting this over to d851 for us!!!!

mjfrank said:
First and foremost, THANK YOU @Skin1980!!!!!!!!!!!!!!
Two quick questions though after reading Multiroms wiki page and the information provided in the OP.
1. Do you have the compatible uninstaller zip file compiled for the d851? (On the wiki it states that in order to fully remove multirom you have to flash an uninstaller) - Not that I plan on removing multirom, TRULY AWESOME & THANK YOU!!!, but better safe than sorry....should something go wrong... (yes, I am currently backing up my phone & will be placing it on my computer prior to diving into this fun)
2. After reading Multirom's WIKI, I know it states you can load ANY rom once you have everything setup, but does that include having both 4.4.x & 5.0 roms at the same time -- stated more plainly, Can I flip between Kitkat and Lolli with this??? (I was always taught, "If something seems too good to be true......")
But if it is true, aww man, you just answered my prayers!!! (Stock based KK @ home for wifi-calling (TMO has no signal @ my house) and L @ work cause I'm impatient and can't wait for TMO any longer to rollout 5.0)
I know it's been my burden to bear, but flashing twice a day just to enjoy L for part of my day has become tiresome....lol
Sorry about the long post, but thanks again for porting this over to d851 for us!!!!
Click to expand...
Click to collapse
1- will compile but to remove completely just reflash the kernel and delete the multirom folder in sdcard
2- yes... you can have kk and LL togheter without issue... in my D855 i have 5 rom installed right now

Very nice.
Only one question if it's okay. Where it says one needs to be with a KK stock ROM does it have to be factory stock or will stock-based do (such as SkyDragon, et al)?
Thanks.
Sent from my LG-D851 using Tapatalk

marcdw said:
Very nice.
Only one question if it's okay. Where it says one needs to be with a KK stock ROM does it have to be factory stock or will stock-based do (such as SkyDragon, et al)?
Thanks.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
I'm running the SkyDragon ROM with skin1980's kernel. This was NOT by design. I did this by accident when I was flashing in TWRP. FOLLOW AT YOUR OWN RISK!
Here is what I did from memory as best as I can recall.
Boot into Recovery
Made a Nandroid Backup
Wiped System/Data/Cache/Dalvik
Restored my Factory Stock Backup that I made when I first rooted my phone.
Installed skin1980's Recovery
Installed skin1980's Kernel
Installed skin1980's MultiROM Zip
Installed a Second ROM
Rebooted Made sure Everything Worked.
Back into Recovery
Restored my Nandroid Backup
Installed skin1980's Kernel
Installed skin1980's MultiROM Zip
Reboot.
SkyDragon 1.1.0 is running with skin1980's kernel. Like I said, this was all by accident. FOLLOW AT YOUR OWN RISK!

marcdw said:
Very nice.
Only one question if it's okay. Where it says one needs to be with a KK stock ROM does it have to be factory stock or will stock-based do (such as SkyDragon, et al)?
Thanks.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Stock based is OK too
Sent from my SM-N910F using XDA Free mobile app

Thank you so much been waiting 7 months for this.
Sent from my LG-D851 using XDA Free mobile app

Screen Brightness
Any way to adjust the screen brightness on boot? Its really dull and hard to read when it comes to the option screen. Thanks!

Erock2k4 said:
Any way to adjust the screen brightness on boot? Its really dull and hard to read when it comes to the option screen. Thanks!
Click to expand...
Click to collapse
TWRP advanced multirom settings... choose your brightness level
Sent from my SM-N910F using XDA Free mobile app

Two things that I would love to have adjusted:
1) Vibrator intensity in the Modified TWRP recovery is very very low.
2) Screen size in Multirom Menu
Any ways this is just nit picking basically we are very lucky to have this in the first place.
Great job man.

Are you gonna be able to make this compatable with the multirom manager app from the play store? It says currently device is unsupported when app is opened.
Sent from my LG-D851 using XDA Free mobile app

anoymonos said:
Are you gonna be able to make this compatable with the multirom manager app from the play store? It says currently device is unsupported when app is opened.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
I would assume that's only for officially supported phones....as ours is not.....

Im definitely sticking away from this one! I like my phone not being bricked!!! Haha
Thanks for brining it to XDA though

yanowman said:
Im definitely sticking away from this one! I like my phone not being bricked!!! Haha
Thanks for brining it to XDA though
Click to expand...
Click to collapse
You should give it a try... By definition, a brick is a device that is 100% useless. Bricking devices is almost completely extinct. The worst that could possibly happen is you end up having to restore bone stock and start all over. The last device that I actually "bricked" and rendered useless was my HTC G1...The first Android device...
@OP, thanks so much for this I will definitely be doing some flashing when I get home.
Quick question tho... Which Kernel was used as a base for the kexec hardboot patch? I assume it was just stock/patched. Is this correct? (I only ask, because I like to know what I will actually be changing when I flash things.)

I did something wrong. My phone goes into fastboot mode instead of recovery now

YES!
I have seriously missed the days of Boot Manager on my HTC Rezound. This is a GODSEND! I can have my stock rom at home and use the wifi calling in my low signal environment AND play with the 5.0 roms at work! WOOT! I did manage to install Multirom and throw a 5.0 rom on my internal storage. I made sure I could boot into my stock rom first and now I am setting up the 5.0 rom. This rocks!
Now which one shall I pair with my 360?