Develop Bugs

[INFO] Recoveries for the Samsung Galaxy Ace II X

Work in Progress
List of Custom Recoveries for the Samsung Galaxy Ace II X
For all things rooting and installing, a custom recovery is often needed. New things are being developed day and night. Thus, I find it necessary for there to be a list of all the recoveries that are compatible with the Samsung Galaxy Ace II X. Some are better than others, though it is a matter of preference. Anyways, commencing the list...
1. ClockworkMod 5.5.0.4 - not my work
ClockworkMod recovery, usually abbreviated as CWM or CWMR, is a custom recovery based off of AOSP source, created by Koushik Dutta (known by the nickname "Koush").
Bugs - Mount USB doesn't work.
Download
2. ClockworkMod 6 - not my work
Bugs - Mount USB doesn't work, "dancing screen," SOME USERS REPORT THAT INSTALLING CWM6 CAUSES THE DEVICE TO BOOT INTO RECOVERY INSTEAD OF THE ROM
Download
3. TeamWin Recovery Project 2.6.3.0 - my work
TeamWin Recovery Project, often abbreviated as TWRP, is a custom recovery that has a fully touch-driven interface. Aside from the uniquity of being 100% touch controlled, it also contains an ubiquity of features. It has a built-in file manager, support for sideloading via ADB, support for backups and restoring backups, a completely theme-able interface, and more sorts of customization.
Bugs - Mount USB doesn't work.
Download
Changelog:
Release 2 - backported some features from TWRP 2.7, fixed color tint issue, implemented internal storage
Release 1 - initial release
4. TeamWin Recovery Project 2.7.1.0 - my work
Download
Bugs - None reported.
{
"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"
}
Changelog:
Release 4 - Upgraded to 2.7.1.0 (customized to build on a JB-based tree: removed mouse support via USB OTG, removed text wrap for now), fixed internal storage
Release 3 - Fixed color tint issue
Release 2 - Fixed USB Mass Storage
Release 1 - Initial release *TWRP 2.7.1.0 has some mount issues. Don't use it.
5. TeamWin Recovery Project 2.8.1.1 - by @draekko
Check his post here for details and download links.
This list will be updated regularly as recoveries are updated, new recoveries are built, or for miscellaneous reasons. If there are any bugs I haven't mentioned for any of the recoveries, let me know and I'll add it to the OP.

Nice thread.
keep up the good work.

Any more recoveries and kernels for ace2x 7560m
Sent from my GT-S7560M using XDA Premium 4 mobile app

CodeName, you resolve the bug for TWRP 2.6 can you try for CWMR 6 ? :angel:
It's just a question :good:

Woops, wasn't seeing any notifications because I forgot to suscribe. Anyways...
AndroidAssassin said:
Any more recoveries and kernels for ace2x 7560m
Sent from my GT-S7560M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What do you mean? I can tell you that I am not done with custom recoveries or custom kernels. CM10.2 is just my focus at the moment. Also, this thread is under construction. I don't have time to work on it for awhile.
Seb269 said:
CodeName, you resolve the bug for TWRP 2.6 can you try for CWMR 6 ? :angel:
It's just a question :good:
Click to expand...
Click to collapse
I've already tried, but I either got build errors or a black screen when I booted into CWM6. I'll try again sometime another day, because I would love to get a nonbuggy CWM6 working. Just a question - is CWM6 different from Philz Touch or are the two a single custom recovery?

Codename13 said:
Woops, wasn't seeing any notifications because I forgot to suscribe. Anyways...
What do you mean? I can tell you that I am not done with custom recoveries or custom kernels. CM10.2 is just my focus at the moment. Also, this thread is under construction. I don't have time to work on it for awhile.
I've already tried, but I either got build errors or a black screen when I booted into CWM6. I'll try again sometime another day, because I would love to get a nonbuggy CWM6 working. Just a question - is CWM6 different from Philz Touch or are the two a single custom recovery?
Click to expand...
Click to collapse
They are the same.

Bug report (TWRP 2.7.0.0)
I have bug report (TWRP 2.7.0.0) - settings are not saving, every time I enter recovery, I have to set everything again. Console says that it can't find something to store the settings if I remember correctly.

gregory678 said:
I have bug report (TWRP 2.7.0.0) - settings are not saving, every time I enter recovery, I have to set everything again. Console says that it can't find something to store the settings if I remember correctly.
Click to expand...
Click to collapse
The latest release? I have no such problem. TWRP is configured so that the settings are stored on the external sdcard. So if you don't have one, your settings won't be saved. I considered setting the cache partition as the TWRP settings storage, but cache is often wiped when installing ROMs and packages. The same with system, data, et cetera. I've considered setting the recovery partition as a settings storage partition; however, whenever a new build of TWRP is installed, the recovery partition will be overwritten. I could try splitting the cache partition up so there is the cache partition and a new 12mb partition, but then there would either be errors when installing firmwares via Odin, or the new settings storage partition would be wiped. Unless you have any better ideas than the sdcard being the settings storage, don't complain. I'm not sure what's causing your issue - perhaps it's because you only insert your sdcard when you boot into TWRP? Enlighten me, and tell me a bit about your device setup (ROM, kernel, size of sdcard, etc).

OMG, I'm such dumb, I just noticed that settings file is hidden. I was wondering why it's always left empty folder after rebooting from recovery mode, now I discovered a hidden settings file in it, I'm Scherlock of the year . Sorry for bothering you, can someone delete these ashaming posts?

Hi Everyone, so I have tried installing a few of these recoveries with Odin. Every time it runs through fine, no errors, but when I restart the device in recovery mode I just get the default stock recovery screen. Has anyone encountered this?

I'm going to stop working on TWRP 2.7.x because it is designed to be built in KitKat-based ROMs' source trees since I don't work on KitKat. I had several issues trying to restore a backup of stock ROM, because it does not have SELinux support at all. There's a reason why TWRP dropped support for older versions of Android - SELinux. It causes the restore to fail for some reason. Anyways, I'll message one of our device's KitKat-based ROM devs, and I'll find someone who can continue work on TWRP 2.7 for us. I was also having issues compiling it after some major commits that were committed to it, so I really am unable to compile it properly unless I migrate to KitKat, which I won't be doing for awhile. Good news though, I've managed to get internal storage working on TWRP 2.6.3.0!
Jeremicus said:
Hi Everyone, so I have tried installing a few of these recoveries with Odin. Every time it runs through fine, no errors, but when I restart the device in recovery mode I just get the default stock recovery screen. Has anyone encountered this?
Click to expand...
Click to collapse
Delete /system/etc/install-recovery.sh then try installing a recovery again and booting into it.

Can someone make a .zip file that has the recoveries .img to be flashed in recovery instead of .tar which needs odin for the ace2x preferably one of TWRP RECOVERIES PLEASE
Sent from my GT-S7560M using Tapatalk

I was thinking about the advantages of TWRP 2.7 over 2.6. I knew that if I looked in the commit history for 2.7 on Github, I would be bound to find the commits that brought in some of my favorite features of TWRP 2.7.0.0. That, along with I having just discovered that Github commits can be download as patches, will bring the best version of TWRP for us yet. So far, I've successfully backported haptic feedback (along with the settings for it) and a bit more. I've also fixed internal storage in TWRP. I plan to backport the smoother scrolling, USB Mass Storage (it only works in 2.7 at the moment because 2.7 added in a different way to handle and mount UMS. I'll backport the different way of handling and mounting UMS), and add in some other bits of fun. It's going to be really cool, and it really isn't time consuming, so I should be able to bring it to you all very soon.
AndroidAssassin said:
Can someone make a .zip file that has the recoveries .img to be flashed in recovery instead of .tar which needs odin for the ace2x preferably one of TWRP RECOVERIES PLEASE
Sent from my GT-S7560M using Tapatalk
Click to expand...
Click to collapse
Just download Recovery Tools from the Play Store.

It dont have nething for ace2x
Sent from my GT-S7560M using XDA Premium 4 mobile app

Codename13 said:
I'm going to stop working on TWRP 2.7.x because it is designed to be built in KitKat-based ROMs' source trees since I don't work on KitKat. I had several issues trying to restore a backup of stock ROM, because it does not have SELinux support at all. There's a reason why TWRP dropped support for older versions of Android - SELinux. It causes the restore to fail for some reason. Anyways, I'll message one of our device's KitKat-based ROM devs, and I'll find someone who can continue work on TWRP 2.7 for us. I was also having issues compiling it after some major commits that were committed to it, so I really am unable to compile it properly unless I migrate to KitKat, which I won't be doing for awhile. Good news though, I've managed to get internal storage working on TWRP 2.6.3.0!
Click to expand...
Click to collapse
So you suggest 2.6.3.0 instead 2.7.0.0 for stock rom users. Regarding restore issues?
______________________________________________
Thank you for great work.
So far so good. The only Bug-free recovery! :victory:

husokal said:
So you suggest 2.6.3.0 instead 2.7.0.0 for stock rom users. Regarding restore issues?
______________________________________________
Thank you for great work.
So far so good. The only Bug-free recovery! :victory:
Click to expand...
Click to collapse
Yes, I say to use 2.6.3.0 as a universal recovery for our device. TWRP 2.6.3.0 works for both stock and custom ROMs, it doesn't enforce SELinux, so I say to use it. Plus, I've back ported some little changes from 2.7 to make it even better. Thank you for the praise, but it actually does have some bugs (mount USB storage) which I'll probs try to fix after the summer.

Codename13 said:
Yes, I say to use 2.6.3.0 as a universal recovery for our device. TWRP 2.6.3.0 works for both stock and custom ROMs, it doesn't enforce SELinux, so I say to use it. Plus, I've back ported some little changes from 2.7 to make it even better. Thank you for the praise, but it actually does have some bugs (mount USB storage) which I'll probs try to fix after the summer.
Click to expand...
Click to collapse
Im sorry i dont know much things about SELinux
As i see 2.7.0.0 Forces SELinux which i dont know what can be problem about it.
and 2.6.3.0 Mount Storage not working.
So im using 2.7.0.0 for my stock. Cause i need this function sometimes.
Sorry for noob question but what can be problem about Enforcing SELinux for 4.0.4
Edit:
Got it! : http://forum.xda-developers.com/showpost.php?p=52013947&postcount=5392

There's another bug with cwm 6. It shows a warning called warning:no file_contexts, as well as bootlooping into cwm again. This happens when you flash any rom, or restore to a nandroid backup. Please add this bug for future reference, as this can cause low experienced users to brick their devices.

s7560m said:
There's another bug with cwm 6. It shows a warning called warning:no file_contexts, as well as bootlooping into cwm again. This happens when you flash any rom, or restore to a nandroid backup. Please add this bug for future reference, as this can cause low experienced users to brick their devices.
Click to expand...
Click to collapse
So is it pretty much unusable? I never actually tested it and I didn't even create it, but a user had told me that it worked fine. I'll post a little warning for CWM6. Anyways, I think that TWRP 2.6.3.0 is the best custom recovery ATM. Of course, there are only 4 custom recoveries that have been built. I actually was going to return to porting some other custom recoveries to our device the other day. I want to port CWM6, Philz Touch, try out a few little hacks, and I want to implement internal storage into TWRP 2.7 just as it is in TWRP 2.6. Also, I think I'm going to try fixing the USB Mounting issue in TWRP 2.6. I know that 2.7 introduced a new, more universal way of handling UMS, so I'm going to see if I can backport it.
EDIT - It seems that there's also a new version of TWRP out. It seems to be quite minor, but I'll see if I can port it. It's been bumped up to version 2.7.1.0 now.

Codename13 said:
So is it pretty much unusable? I never actually tested it and I didn't even create it, but a user had told me that it worked fine. I'll post a little warning for CWM6. Anyways, I think that TWRP 2.6.3.0 is the best custom recovery ATM. Of course, there are only 4 custom recoveries that have been built. I actually was going to return to porting some other custom recoveries to our device the other day. I want to port CWM6, Philz Touch, try out a few little hacks, and I want to implement internal storage into TWRP 2.7 just as it is in TWRP 2.6. Also, I think I'm going to try fixing the USB Mounting issue in TWRP 2.6. I know that 2.7 introduced a new, more universal way of handling UMS, so I'm going to see if I can backport it.
Click to expand...
Click to collapse
Definitely twrp is the best! Never had any issues with it whatsoever, and has a great ui. If you could though, it would be awesome to try and port philz touch and cwm touch as well, just in case those who like cwm want that touch feature, or like the theme and features of philz touch . And I really hope the usb mounting issue can be fixed, as it can save so much time, rather than downloading to my computer, transferring to phone external storage, and then booting into recovery. Those who are lazy don't want to do all of that lol. Anyways, keep up all of the good work, and hopefully these bug fixes and new recoveries are implemented in future notice!

[Q] F2FS in Note2 Support is needed

Hello All,
I'm not expert in android platform. I found that there are many articles that are talking about F2FS performance in compare to EXT4.
Is there any tool to convert my device t889 to F2FS keeping the same experience? i.e. android 4.3, current ROM DN3 V3.2 LTE, and Kernel AGNI V3.9.4-OC-LTE
Regards

Guys ... Your reply please ... I think this may have significant performance change if it is doable ... Also if there is a way to override all system call to fsync() by fdatasysnc(), it will produce a massive performance change in the whole device

K3A said:
Guys ... Your reply please ... I think this may have significant performance change if it is doable ... Also if there is a way to override all system call to fsync() by fdatasysnc(), it will produce a massive performance change in the whole device
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2631278 try this rom

mattlowry said:
http://forum.xda-developers.com/showthread.php?t=2631278 try this rom
Click to expand...
Click to collapse
I just did the f2fs and had ROM running OK, did not see any improvement so I flashed CWM recovery and tried to restore a nandroid and it failed on data then phone would boot but gave me an error about having to reset phone. So i'm odining+root66ing my Note2 to get back to stock. I assume Im not f2fs any more.
Question? Once you switch to f2fs, do you have to use devil recovery from that point on to flash new roms?
Can some one explain the options to flashing a new roms once on f2fs, ex: what recovery can be used?
Converting to f2fs was not difficult and will do once again when I understand more.
Cheers, they really need a beer mug icon, but jolly face will do.

pvaldeben said:
I just did the f2fs and had ROM running OK, did not see any improvement so I flashed CWM recovery and tried to restore a nandroid and it failed on data then phone would boot but gave me an error about having to reset phone. So i'm odining+root66ing my Note2 to get back to stock. I assume Im not f2fs any more.
Question? Once you switch to f2fs, do you have to use devil recovery from that point on to flash new roms?
Can some one explain the options to flashing a new roms once on f2fs, ex: what recovery can be used?
Converting to f2fs was not difficult and will do once again when I understand more.
Cheers, they really need a beer mug icon, but jolly face will do.
Click to expand...
Click to collapse
Odin will format as ext4. You will need to keep devil recovery in order to keep f2fs as no other recovery can write to f2fs partitions. Ive found though that some zips dont like to install using devil recovery. Once partitions are f2fs, before you can do anything else with another recovery, you need to reformat the partitions back to ext4 ( or go through odin and start all over again lol ).
You will need to use devil and reformat the partitions back as ext4. Then flash cwm / phils touch recovery. Once thats done you can flash a new rom zip. To revert the new rom back to f2fs, Install a compatible kernel (agni and devil so far ), then flash devil f2fs recovery. Reboot to make sure things are working properly. Then reboot into devil recovery to do a nandroid, format f2fs, and restore the new nandroid.
Hope this helps! I just did a write up in the Jedi X2 thread with links.
Dont forget the thaks button
Sent from my SGH-T889 using xda app-developers app

pyraxiate said:
Odin will format as ext4. You will need to keep devil recovery in order to keep f2fs as no other recovery can write to f2fs partitions. Ive found though that some zips dont like to install using devil recovery. Once partitions are f2fs, before you can do anything else with another recovery, you need to reformat the partitions back to ext4 ( or go through odin and start all over again lol ).
You will need to use devil and reformat the partitions back as ext4. Then flash cwm / phils touch recovery. Once thats done you can flash a new rom zip. To revert the new rom back to f2fs, Install a compatible kernel (agni and devil so far ), then flash devil f2fs recovery. Reboot to make sure things are working properly. Then reboot into devil recovery to do a nandroid, format f2fs, and restore the new nandroid.
Hope this helps! I just did a write up in the Jedi X2 thread with links.
Dont forget the thaks button
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Yes Saw your post on JediX2 and used you link to get the devil recovery. really not difficult as you explained it. But just posted my question here as f2fs was deviating from rom thread. Thanks again. Cheers.

Read directions in op from thread provided by matt. Performance gains require a little more than converting file system. Added effort is well worth it.

Bruce lee roy said:
Read directions in op from thread provided by matt. Performance gains require a little more than converting file system. Added effort is well worth it.
Click to expand...
Click to collapse
Shore enough.
I readit and I'm going to try again.
Shore enough.

[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.

[Q&A] [ROM][V500][5.0.x][CM12] Official CyanogenMod 12

Q&A for [ROM][V500][5.0.x][CM12] Official CyanogenMod 12
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][V500][5.0.x][CM12] Official CyanogenMod 12. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

is there any way of getting MULTICAST enabled in the CM12 stock kernel?

axelander1 said:
is there any way of getting MULTICAST enabled in the CM12 stock kernel?
Click to expand...
Click to collapse
Yes, the first step is to submit a patch to gerrit. Is there a patch available?

Deltadroid said:
Yes, the first step is to submit a patch to gerrit. Is there a patch available?
Click to expand...
Click to collapse
I could probably create one.
Do you know which kernel config is used? is it one in https://github.com/CyanogenMod/android_kernel_lge_v500/tree/cm-12.0/arch/arm/configs ?
Is this even the kernel repo which is used for the cm12 nightlies?

axelander1 said:
I could probably create one.
Do you know which kernel config is used? is it one in https://github.com/CyanogenMod/android_kernel_lge_v500/tree/cm-12.0/arch/arm/configs ?
Is this even the kernel repo which is used for the cm12 nightlies?
Click to expand...
Click to collapse
This is the script that generates the config and moves it to arch/arm/configs/
https://github.com/CyanogenMod/android_kernel_lge_v500/blob/cm-12.0/make_defconfig.sh

Deltadroid said:
This is the script that generates the config and moves it to arch/arm/configs/
https://github.com/CyanogenMod/android_kernel_lge_v500/blob/cm-12.0/make_defconfig.sh
Click to expand...
Click to collapse
this file takes a parameter, I suppose awifi070u-perf_defconfig is used (see the other make script make_awifi070u_defconfig.sh).
However this has CONFIG_IP_MULTICAST=y.
I somehow doubt that this is the config which is actually used for the official builds. If I understand http://wiki.cyanogenmod.org/w/Build_for_v500 correctly, the command "breakfast v500" would pull the kernel repo and triggers make for the kernel's .config file?

Yes. You can also create a local manifest to pull a specific repo without having to pull everything.
Example:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="cmhub" fetch="git://github.com/CyanogenMod/" review="review.cyanogenmod.com" />
<project path="device/lge/v500" name="android_device_lge_v500" remote="cmhub" />
</manifest>
Example Procedure:
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
repo sync device/lge/v500
repo start my_fixed_branch device/lge/v500
cd device/lge/v500
<edit files>
git commit -a
repo upload device/lge/v500
---------- Post added at 12:23 AM ---------- Previous post was at 12:11 AM ----------
Just substitute "device" for "kernel" in the project path and name.

How do I know if I'm using hardware or software decoding for Netflix? No idea if I need your patch.
Also, I installed cm-12-20150226-NIGHTLY-v500.zip yesterday. Updated to cm-12-20150227-NIGHTLY-v500.zip with CyanDelta today, works like a charm. Thank you!

If you make a backup of /system/etc/media_codecs_google_video.xml then you can revert the patch. It only removes one line in that xml file so that adaptive playback is not an option for h264 decoding. The only difference is that hardware decoding should save on the battery. This patch was taken from slimRom and I need it for other devices, so I thought it would be worth testing for this device also.

Hi everyone, I am on 28\02 nightly and Google Now doesn t work, showing "Network error. Check your network connections".
Does anyone knows how to solve it?

It's working here. Either the Google services is temporarily down in your area or you need to install the correct version of gapps. The "Delta" gapps that I have posted in the development section are up to date and working.

cm12 crashes after flashing
Everytime I flash cm12 it fails. I get into the setup process, login to wifi' cyanogenmod, and google. I never get passed this. During setup I get messages that say "unfortunately there is a problem with music", then the same for camera. Then the screen stars flashing and eventually goes dark. The back key shows at the bottom, but the other two do not show. The back key is nonresponsive. I have to power down and get back to recovery and restore my cm11 backup.
When I got the gpad, it came with 20D, andI had to use the lgflashtool to get back to 4.2.2. (20A0. Then I rooted with stump and installed twrp using flashify. Then I was able to flash cm11 (m10, 11 and 12). Cm11 ran like a champ.
A couple of weeks ago I decided to flash a cm12 nightly and had the problem described above.
I have tried multiple combinations of steps to solve this problem: going back to 4.2.2, rooting and flashing cm12 from 4.2.2, I have tried 4.4.2. I have tried multiple versions of twrp and philz. I have wiped with and without wiping system. I have tried different versions of gapps-lp. I have tried different versions of the nightlies.
Every time I get the same result (which I think is the definition of insanity).
What is most frustrating is that I have another gpad that went from cm11 to cm12 with no problems. Worked the first time using the 0217 nightly,
So what am I doing wrong? Why am I having problems with cm12 after I flash it?
Thanks in advance. Xda has been a life saver since I got my first tablet, a viewsonic, a few years ago.
John

It sounds like you know the procedure of installing CM because one of your devices works fine. There seems to be a difference between your two devices. Have you looked at the thread for "back cam fix" in the development section to find out how to check which camera module your device has? Maybe one of your devices has a different camera module than the other (which requires other camera drivers). Although, the device should still function with cm12 even if your camera module is unsupported.
Also, make sure you format the cache, Dalvik cache, and system partitions in addition to a factory reset before flashing from your internal sdcard.

Still can't set up CM12
Deltadroid said:
It sounds like you know the procedure of installing CM because one of your devices works fine. There seems to be a difference between your two devices. Have you looked at the thread for "back cam fix" in the development section to find out how to check which camera module your device has? Maybe one of your devices has a different camera module than the other (which requires other camera drivers). Although, the device should still function with cm12 even if your camera module is unsupported.
Also, make sure you format the cache, Dalvik cache, and system partitions in addition to a factory reset before flashing from your internal sdcard.
Click to expand...
Click to collapse
Thanks for the suggestions. I first checked the camera.
While in CM11 I turned on the camera and took a picture. I also opened a terminal window and grepped both the OV and the S5K cameras. Nothing came back for OV. I did get stuff from S5k. So I assume the camera is the right one.
Then I did went into recovery, carefully wiped and formatted, and flashed CM12 and Gapps.
I am still getting the camera and music errors. Then the screen flashes to black and the it locks.
The bad news is that I cannot get back to recovery. It looks like I'm back to the lgflashtool.
I will try again from stock. But right now I think it is miller time.

Yeah, if it was working on cm11 then your camera is supported.
Maybe going back to latest stock Rom with lg tool would help fix any unknowns. Instead of flashing the 10a firmware, stay on 20d stock and just replace aboot so you can install a custom recovery. Next, install cm12 with red kernel or mani kernel to support your stock 20d 4.4.2 firmware.

Are you sure you did wipe SYSTEM before flashing?

Still can't set up CM12
Deltadroid said:
Yeah, if it was working on cm11 then your camera is supported.
Maybe going back to latest stock Rom with lg tool would help fix any unknowns. Instead of flashing the 10a firmware, stay on 20d stock and just replace aboot so you can install a custom recovery. Next, install cm12 with red kernel or mani kernel to support your stock 20d 4.4.2 firmware.
Click to expand...
Click to collapse
No cigars yet! Same error with camera and music then screen locking.
I found an XDA tool called Original LG Firmware.exe. It allowed me to download V50020d_00.kdz.
I used LGFlashTool2014 to install.
I used Stump to get Root.
I downloaded SuperSU and Flashify to set up recovery.
Recovery failed. It didn't think I was rooted.
I used another tool, LGGPabRecoveryTWRP 2.8(BypassBootloader).apk to resolve this problem
I installed CM11-M12.
Then I went to recovery to install CM12, gapps, and red kernal.
The first attempt used the 0305 nightly. It hung on the flash.
I forced a power down and manual reboot into recovery.
Did all the wiping and tried the 0217 nightly. The flash was successful but as it initialized, CM12 crashed and burned again.
I'm beginning to believe I have a poltergeist in this gpad.

johnseidel said:
No cigars yet! Same error with camera and music then screen locking.
I found an XDA tool called Original LG Firmware.exe. It allowed me to download V50020d_00.kdz.
I used LGFlashTool2014 to install.
I used Stump to get Root.
I downloaded SuperSU and Flashify to set up recovery.
Recovery failed. It didn't think I was rooted.
I used another tool, LGGPabRecoveryTWRP 2.8(BypassBootloader).apk to resolve this problem
I installed CM11-M12.
Then I went to recovery to install CM12, gapps, and red kernal.
The first attempt used the 0305 nightly. It hung on the flash.
I forced a power down and manual reboot into recovery.
Did all the wiping and tried the 0217 nightly. The flash was successful but as it initialized, CM12 crashed and burned again.
I'm beginning to believe I have a poltergeist in this gpad.
Click to expand...
Click to collapse
The reason your recovery failed is because your 20D firmware has an aboot.img that is not loki exploitable. After rooting, you will need to replace your aboot.img with the aboot.img from 10A firmware. This means you are keeping the 20D bootloader but only downgrading the 10A aboot.img so that you can use the loki tool to install a custom recovery. Flashify also needs a loki exploitable aboot.img (10A) to be installed before it can work and install a lokified recovery. The trick is to keep your new bootloader from 20D but only downgrade the aboot.img. There is a batch file in the development section that does this with a script using the dd command.

Okay.
20D is flashed and rooted.
V50020_aboot_twrp_v2 has been executed.
Flashify flashed TWRP 8.0.0.0 and rebooted.
I am assuming the next step is to flash CM12, but wanted to make sure. I've shot myself in the foot so many times I'm running out of toes.

Next, factory reset, and format /system. You could also format your internal sdcard, but it's not often necessary.
Finally, install latest nightly build of cm12. You can install gapps later.
---------- Post added at 02:45 AM ---------- Previous post was at 02:36 AM ----------
Note, make sure you copy the files to your sdcard first if you plan on formatting the internal sdcard.

[POLL] TWRP for stock ROMs

Hey, I've got some ideas how to fix TWRP for stock. Does anyone need it?
The first and main problem is the screen split bug, which probably can be fixed by commiting this in kernels. The second problem is absence of extract_elf_ramdisk utility, but as stock is not updated anymore we can just use boot repacking script instead. Or I can try packing stock kernel with EER support. But I don't have much time now and will try it all only if enough people wants it.
Also I don't mind if some of devs or other users will try doing this using info given by me. I will provide needed help if anyone is interested and skilled enough. If someone succeeds, the credit will be given in official thread.
So do you REALLY need it in stock?

Yah I need this recovery, twrp is more better than Cwm, now am in4.3 stock,tell me how to install this recovery into stock,

Yes.
Definitely i needed TWARP for stock rom...
Will waiting for your update.
Good initiative..
Best of luck...

Please, create recovery for XMDual JB 4.3, thank you.

I'll have a time to work on this maybe in January. And I'll try to do this only if there will be enough votes. BTW, if you think that TWRP is needed for stock too, write why is it so important and what doesn't satisfy you in CWM/PhilZ.

i hopes this will happen on the future, need this

Hi, I have Philz Touch 6.50.6 but this is probably (I don't know) unusable if I want to try [ROM][MOB31K][6.0.1][NIGHTLY][FINAL] Official CyanogenMod 13.0 (https://forum.xda-developers.com/xperia-m/orig-development/rom-unofficial-cyanogenmod-13-0-t3245573) on my dual sim phone, where I must use yours TWRP to aply DUAL-SIM-PATCH (https://forum.xda-developers.com/showpost.php?p=65104843&postcount=49).
Now I have stock rom 15.5.A.1.5 and I don't know how to change my Philz recovery to TWRP without losing data/phone config. I have Philz nandroid backups via recovery and have TWRP nan. backups via Online Nandroid Backup (https://forum.xda-developers.com/showthread.php?t=1620255) - if is it usable backup - I don't know and don't want to risk. My phone is working well with stock but I want to try to use CM on it with dual sim working.
Sorry for my bad english.
EDIT:
Got the solution myself (https://forum.xda-developers.com/xperia-m/orig-development/recovery-twrp-xperia-m-t3147051/page45) even though I changed the kernel to SXDNickiDS.