• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [MetroPCS] Setting up F6 with stable KitKat and SD Card Hack with Working Camera

Alright since the instructions for doing this stuff is all over the place, I want to put it all in one set of directions for new people getting this phone. I have the newest version of the phone so my camera doesn't work with the kitkat roms here. I've been testing tons of different methods with this phone since I got it 4 months ago and this seems to be the best solution for now. Assuming you're starting from stock, unrooted Jellybean on MetroPCS:

Changes were made today, 3/5/15, that added a 3rd file to the sdcard hack part of this guide. It adds a script that starts every time you boot up the phone. This script fixes the permissions issue with apps installed after the sdcardhack. Anything that would require additional downloads and wouldn't work should work with this fix now.

If you have an sd card it's easier to put all the files you're going to download on there, so you can format the internal data when you're ready to flash the new rom.

1. Go in to 'settings -> security' and make sure 'unknown sources' is checked.

2. Go in to developer option and enable 'USB debugging'.

3. Go to https://towelroot.com/ download and put the file on your phone.

4. Go here to download TWRP recovery http://androidforums.com/threads/recovery-twrp-lokied-new-apk-version-08-27-14.861281/ (thanks to hroark13) and put this in your internal or sd card.

5. Download CarbonROM http://androidforums.com/threads/ro...4-4-4-for-lg-optimus-f6-lots-of-fixes.880135/ and put this in your internal or sd card.

6. Download Google Apps here http://www.mediafire.com/download/82b7013dqh8z6g7/7-29_GApps_Standard_4.4.4_signed.zip (thanks to viperkink's link on Angablade's post) and put on your internal or sd card.

7. Download hroark's camfix kernel here GET THE CM11 VERSION NOT THE KK VERSION http://androidforums.com/threads/kernerl-cm11-kk-with-ov5693-camera-support.879804/ and put on your internal or sd card storage.

8. Alright. Now with all these files, you're going to want to start off by going in to file manager and going to either internal storage (sdcard0) or sd card storage (sdcard1)/wherever you put all these files. Find the towelroot.apk and install using 'system installer' not google. Once finished open, and press 'make it ra1n'. It'll say it's successful and you can close out of it.

9. Go back to where all these files are and find 'LG-F6-TWRP-V3'. Install using system installer. Open -> click install recovery, once it pops up and says successful press 'ok' and press 'reboot recovery'. The phone will now turn black, start up with the LG logo, flash a couple times and then you'll see the blue twrp picture.

10. This step is only for those with their install files on the sd card. Before you do anything right now go to the top right where it says 'wipe', select 'wipe data' it'll popup with a keyboard. Type 'yes' and hit enter. This'll wipe all the old crap from the stock rom. If you don't have an sd card you can skip this.

11. Once in TWRP you want to go to where you downloaded the ROM and kernel files along with google apps. If you don't have an sd card you want to go to the top left box that says 'install' and find 'data'. then find 'media' and then press '0'. Your files should be in there. If they're on your sd card (the best method) just go to 'install' and find 'sd card'.

12. DO THESE IN THE CORRECT ORDER: 1) install CarbonROM. 2) install gappskk. 3) install camfix kernel.

13. Go back to the main TWRP menu and go to the top right where it says 'wipe'. Swip the slider and it'll wipe by default the dalvik cache which is what you want.

14. Now go in to the 'reboot' tab on the main TWRP menu and press 'system'. Your phone should start up with the carbon logo.

15. If you for some reason get an infinite boot, use this method to bring your phone fully back to stock unrooted. It's worked for me every time. http://androidforums.com/threads/br...is-might-work-for-you-too.833575/#post6471224

16. Once in Carbon ROM, go to settings -> Carbon Fibers -> interface -> CRT Animation, and select 'none'. Go back to settings, make sure you have performance options. If you don't, go to about phone and tap the 'software version' (one of those, I can't remember) until you get admin rights. Go back to settings -> performance -> turn the 'minimum cpu frequency' up a notch. Set 'apply on boot'.

17. To enable metroPCS data go in to settings -> mobile networks -> access point names -> press the 'MetroPCS LTE' dot.

-------------------------Call Echo Fix----------------------------------

17. If you're getting call echo, which you most likely are, you're going to want to search 'build.prop editor' in play store. Install the first app that shows up, open it, give it SU permissions, and search for 'mic'. Once you find the line 'mic' that says 'digital'. Press on the 'digital' and change it to 'analog'. This will fix your call echo.

-----------------------------------SD CARD HACK--------------------------------

You're going to want a class 10 or higher sd card for this hack, otherwise you will experience lag.

ALSO: The same SD Card Hack files will work with jellybean. Just follow the same directions below.

16. If your phone starts up then congratulations. Set up your phone and your google account and wait a bit for things to settle in. Now we're going to do the sd card hack. Once finished, go here http://androidforums.com/threads/sd-card-hack-to-increase-internal-memory.882907/ to ksjk01414's post and go to the third post down, by 'fbr' with the two files named 'dataonSD-copy' and 'dataonSD-install'. THEN go here to post #505: http://androidforums.com/threads/pr...rnal-sd-storage-solution-on-f6.819792/page-21 and download 'DataonSD-sensorfix' ONLY. Once finished download these 3 files, PUT THEM IN YOUR INTERNAL MEMORY. NOT YOUR SD CARD.

17. Carbon rom has a built in recovery reboot feature. Just hold down the power button, press restart and press 'recovery'. You should boot in to recovery.

18. FIRST. Go to 'settings' -> 'screen' and uncheck 'Enable screen timeout'. If you don't do this, recovery will crash in the process of formatting your sd card.

19. Next, go to 'advanced' -> 'partition SD Card'. FIRST: Press 'EXT4'. You're going to want to set the 'Swap Size' to '128'. Then, depending on the size of your sd card, increase the 'EXT Size' to your desired amount. This will add to your internal memory. Personally I like to add as much as possible to the internal memory as I can. For example: I have a 32 GB sd card. I get a calculator either in hand or in windows and multiply '1024' 32 times. This will be close to the maximum you can allocate to the sd card. The only method in this TWRP is to keep pressing '+' until you reach your desired size in MB. Once you're at the specific size in MB of your sd card, swipe to partition. If it says it's too big of a partition keep pressing subtract on the 'EXT Size' and repeat until you find the maximum size you can set it to.

20. Swipe to partition if you haven't already. This will take a while. It usually takes my phone about 10 minutes to partition the sd card.

21. Once done partitioning, you should be able to go back to 'Mount' in the main menu and check 'SD-Ext'. If you can't, which is common for me, you're going to need to do some additional steps below.

22. After you check 'SD-Ext' go to the main menu -> settings -> check 'Use rm -rf instead of formatting'.

23. Go back to the main menu -> wipe -> advanced wipe -> check 'SD-Ext' and swipe to wipe. This will be pretty fast.

24. Go back to the main menu, go to 'install' and find the 'DataOnSD-copy.zip', 'DataOnSD-install.zip' and 'DataOnSD-sensorfix' you downloaded. Flash 'DataOnSD-copy.zip' first, then 'DataOnSD-Install.zip', then 'DataOnSD-sensorfix'. Once done, you should be set. To double check go back to mount and make sure SD-Ext is checked before you reboot.

25. Reboot system and let in start up to CarbonROM. Give it a minute, then go to settings -> Storage, and you should see your new internal storage size. WOO!!!

----------------------------------SD-EXT WON'T MOUNT AFTER PARTITIONING SD CARD---------------------------

1. Make sure 'Format using rm -rf formatting' is unchecked, Go to 'Wipe' in the main menu of TWRP, then 'Advanced Wipe' and check 'SD-ext', then swipe to wipe. This will take a while. Once done, go back to 'mount' and try to check sd-ext.

2. If the sd-ext still won't check, go back to 'Advanced' partition sd-card. Once finished, you most likely will be able to finally check the 'sd-ext' under 'mount'. If you can't, which happened to me once, usually you just repeat until you can. I've done this 5 times and it never took me more than 3 sd partitions.

-------------------------------SD Card hack disappears (internal memory resets) after kernel crash---------------------

1. Don't panick. Go to the app store and download 'Terminal Emulator'. Open it up, type 'su' (no quotes) hit enter. Once you've given it permissions, type: 'e2fsck -y /dev/block/mmcblk1p2' (no quotes) and hit enter. Restart your phone and you should be good.

2. A couple times I noticed after I turned on my phone from shutting it down overnight, I'd turn it on to find everything is "read only". And things are acting weird. This happens when somehow the "Sd-ext" got unmounted. Just go back in to recovery and mount sd-ext again. Then restart. It should all be good from there.

Fun fact: Cyanogenmod 11 themes work with this rom. I've installed 8 of them and found a great combination. Sometimes the theme chooser will crash, but you can just go back in again.

---------------------------------------Front Camera Blue Fix----------------------------------
To fix the front camera making you look blue, go to the app store and get 'Camera MX'. In the color options select 'Blue' and it'll turn the camera back to normal for your selfies.

-----------------------------Fix Google Camera Crashing when recording video--------------------
The same program used to fix the front camera being blue, CameraMX, also works with taking videos. Google camera seems to be the only things that crashes while taking videos with the camfix kernel.

------------------------------Setting up hardware notification light------------------------
1. Install xposed framework, reboot
2. go to downloads in xposed, search 'gravitybox'. Get the KK version.
3. Go in to settings -> display tweaks -> scroll down to 'button backlight notifications' and enable it. Restart and the home button should light up when you have a notification.
4. Installing gravity box for some reason enabled software navigation buttons for me. Just go in 'navigation bar tweaks' tick the master switch to on, check 'enable navigation bar' scroll down 'dimensions' and slide the first 'navigation bar height' slider all the way to 0%. Restart your phone and there should no longer be software navbuttons.

These are some images of my setup. I have a custom font and boot animation currently installed.
ERmXdss.png
QFDISee.png
JolP7Vr.png
cDZ0zLi.png
SnCWuiW.png
cDyHBPj.png
 
Last edited:
Great post by the way. Very informational and easy to follow along. I have one question though. Do you still experience, with this install method, random reboots when in the google maps application?
 
Great post by the way. Very informational and easy to follow along. I have one question though. Do you still experience, with this install method, random reboots when in the google maps application?
Thank you! And no I don't. Bluetooth, location, and basically everything other than wifi calling and LED work. I've been using Google Maps daily for bus routes without any crashes.
 
Thank you! And no I don't. Bluetooth, location, and basically everything other than wifi calling and LED work. I've been using Google Maps daily for bus routes without any crashes.
Awesome! Looking forward to trying this method out. Will report back with the results :D
 
So far so good, haven't had any crashes yet. However, I have one problem. I previously never had any issues with my camera, so the camera fix kernels and so forth were irrelevant to my phone; but now that I installed this kernel my camera's flash will not work. Also when I'm using the Google camera, it crashes when I try to record a video. Is there a CM kernel without the camfix that still works the way this one does? Or any workaround this?
 
So far so good, haven't had any crashes yet. However, I have one problem. I previously never had any issues with my camera, so the camera fix kernels and so forth were irrelevant to my phone; but now that I installed this kernel my camera's flash will not work. Also when I'm using the Google camera, it crashes when I try to record a video. Is there a CM kernel without the camfix that still works the way this one does? Or any workaround this?
You must have the version of the phone that has the working camera with kitkat roms. Assuming you do, I would skip the install of the camfix kernel. But yes the camfix kernel disables the LED and video recording doesn't work sadly. Sorry I forgot to mention that in the instructions. But it's a compromise for people's cameras that otherwise wouldn't work at all.

For your situation I would replace the step of installing the camfix kernel with Dm47021's updated kernel here: http://www.mediafire.com/download/bu3i9u350fm927i/carbon_kernel.zip
 
You must have the version of the phone that has the working camera with kitkat roms. Assuming you do, I would skip the install of the camfix kernel. But yes the camfix kernel disables the LED and video recording doesn't work sadly. Sorry I forgot to mention that in the instructions. But it's a compromise for people's cameras that otherwise wouldn't work at all.

For your situation I would replace the step of installing the camfix kernel with Dm47021's updated kernel here: http://www.mediafire.com/download/bu3i9u350fm927i/carbon_kernel.zip
Noooo! Lol Well that's the end of the road for me then, because for some reason that kernel doesn't work well on my phone with Google maps. Keep getting kernel crashes in maps constantly, and at really inconvenient times. Haha guess I just have to wait for DM's finished Carbon ROM, worth a try though :P
 
Noooo! Lol Well that's the end of the road for me then, because for some reason that kernel doesn't work well on my phone with Google maps. Keep getting kernel crashes in maps constantly, and at really inconvenient times. Haha guess I just have to wait for DM's finished Carbon ROM, worth a try though :p
Damn :( sorry about that man. You could still compromise for the camfix kernel if you can give up video recording and flash. Your choice though.

Edit: Are you using google camera to take videos? I think I remember being able to record videos using a 3rd party video recording app. That might fix it.
 
Last edited:
I am currently using the Carbon ROM + overclocked but I wouldn't mind doing a clean install using this method.

However, I am using CWM Recovery. In order for the SD hack to work, it appears that I can only use TWRP. Am I correct in assuming this?

If so, is it possible to change from CWM to TWRP?
 
I am currently using the Carbon ROM + overclocked but I wouldn't mind doing a clean install using this method.

However, I am using CWM Recovery. In order for the SD hack to work, it appears that I can only use TWRP. Am I correct in assuming this?

If so, is it possible to change from CWM to TWRP?
I believe you can use an SD card partitioning app off the play store to do what twrp does. But if you want to replace cwm you can just install twrp over it. Back up your stuff and use the restore method in my post in case you get a boot loop. BTW how did you over clock carbon???? I need this
 
Last edited:
My device can run with CWM,but when i install twrp,install recovery,reboot to recovery,my device didnt boot in,it stop at blue screen forever....
Try many times isnt suscessful...
:(
 
My device can run with CWM,but when i install twrp,install recovery,reboot to recovery,my device didnt boot in,it stop at blue screen forever....
Try many times isnt suscessful...
:(
Really? That's weird. Are you sure you have the newest version of the f6? From what I've heard the newer production models are a little different than the first ones. You could either try a full restore using the method I posted with lg support tool and try again, or you can stick with cwm. twrp is just out of convenience, and is mainly good for the sd card hack part of this tutorial. You can get by with cwm!
 
With CWM i can flash any custom rom such as: xperia,cacbon,cm11,kitkat mini,...wipe full,backup too,...
Back to stock i use KDZ flash kdz file 12b,root with towelroot
Every things good
But with Twrp dont like that. Install it ok,kick install recovery ok,it say OK. But then,reboot it stop at blue screen with big TEAMWIN forever
I dont know why
 
With CWM i can flash any custom rom such as: xperia,cacbon,cm11,kitkat mini,...wipe full,backup too,...
Back to stock i use KDZ flash kdz file 12b,root with towelroot
Every things good
But with Twrp dont like that. Install it ok,kick install recovery ok,it say OK. But then,reboot it stop at blue screen with big TEAMWIN forever
I dont know why
Hmm. Well if you're up for it use the lg support tool I linked and report back the results. It completely restores everything back to stock unaltered like it's brand new. But otherwise you're totally fine with cwm, just get an sd partitioning app off the play store.
 
Noooo! Lol Well that's the end of the road for me then, because for some reason that kernel doesn't work well on my phone with Google maps. Keep getting kernel crashes in maps constantly, and at really inconvenient times. Haha guess I just have to wait for DM's finished Carbon ROM, worth a try though :p
Vincible I have confirmed you can take videos with camera mx. The same app also fixes front camera being blue. So the only thing that isn't fixable right now is the LED.
 
Vincible I have confirmed you can take videos with camera mx. The same app also fixes front camera being blue. So the only thing that isn't fixable right now is the LED.
Yeah I forgot to mention that camera MX does record like you said. I think it's worth keeping the ROM though because I don't really take photos that often anyways, it was just that when I actually do it's during priceless moments. I'll sacrifice the LED though for the moment, because Carbon really does enhance the 'phoning' experience :) One thought, I previously used mn1968's snd_soc_msm_Sitar file to increase in call volume, however, with it in use I received complaints about call echo. I noticed though that, it increased the volume to be fairly loud, so I was thinking that maybe the tweaks made were to increased to the point that people could hear them self through the ear speaker piece. So I'd like to ask if you know what is edited in that file to increase/ decrease that volume so I can tweak it to be a little lower?
 
Yeah I forgot to mention that camera MX does record like you said. I think it's worth keeping the ROM though because I don't really take photos that often anyways, it was just that when I actually do it's during priceless moments. I'll sacrifice the LED though for the moment, because Carbon really does enhance the 'phoning' experience :) One thought, I previously used mn1968's snd_soc_msm_Sitar file to increase in call volume, however, with it in use I received complaints about call echo. I noticed though that, it increased the volume to be fairly loud, so I was thinking that maybe the tweaks made were to increased to the point that people could hear them self through the ear speaker piece. So I'd like to ask if you know what is edited in that file to increase/ decrease that volume so I can tweak it to be a little lower?
I'm not sure about the in call volume causing the issue. It's been loud enough for me using this method and without call echo. Have you tried the fix in my guide by editing the build.prop to change the mic to analog coupled with the sitar file you're mentioning? And yeah I tried going back to jellybean but Kitkat with Carbon just feels too fluid. The UI is so easy to navigate, and everything runs so smoothly. If I can just figure out how to overclock the camfix kernel I'll be all set.
 
Last edited:
I'm not sure about the in call volume causing the issue. It's been loud enough for me using this method and without call echo. Have you tried the fix in my guide by editing the build.prop to change the mic to analog coupled with the sitar file you're mentioning? And yeah I tried going back to jellybean but Kitkat with Carbon just feels too fluid. The UI is so easy to navigate, and everything runs so smoothly. If I can just figure out how to overclock the camfix kernel I'll be all set.
Yes I did end up changing the mic in the build.prop to analog and it certainly fixed my in call echo. :D I'll try implementing the sitar file with that change to see if it works without any issues since this kernel has been pretty good so far. I have a question though regarding the camera. I noticed in hroark's camfix thread that he said the kernel was the same as his cm11 kernel, the only difference was added support for the ov5693 camera. With that in mind, I decided to overwrite the camfix files with the cm11 files, and eliminated all the files that had to do with the ov5693 camera. After that I did an overwrite of the boot.lok, update-binary, and updater-script files from the original camfix file to to the one I edited. The question I'm left with is do these three files have to be edited in any way, because there are now missing files from the original camfix kernel? If not would you like to test the kernel and see if the file changing I did worked on fixing the camera?
 

Attachments

idk if im the only one but i have encountered several bugs.. when i call 911 it hangs up right away; and apps that require additional downloads when downloaded. ex. order and chaos. i get an error and im unable to use such apps.
 
Well i can vouch for this, it worked completely as detailed but for some odd reason i'm receiving much lag after i partitioned a 32GB class 10 micro sdcard, supposed you wouldn't have alternate partition configuration that favors performance but still maintains a majority of the storage amount available to install apps using the sdcard?
 
Well i can vouch for this, it worked completely as detailed but for some odd reason i'm receiving much lag after i partitioned a 32GB class 10 micro sdcard, supposed you wouldn't have alternate partition configuration that favors performance but still maintains a majority of the storage amount available to install apps using the sdcard?
hmm.. that's interesting. If it's a class 10 you shouldn't be getting lag. Is it an old sd card? The thing with the sdcardhack is that is basically moves your data to the sdcard. So no matter how small you make the partition, your 'internal memory' with the hack will be as fast as it would be with 32 GB. I'd suggest trying a different sd card and see if the lag persists.
 
idk if im the only one but i have encountered several bugs.. when i call 911 it hangs up right away; and apps that require additional downloads when downloaded. ex. order and chaos. i get an error and im unable to use such apps.
Are you using the sd card hack? So far everything works fine for me. For the 911, did you be sure to set the access point name to metro PCS? Because carbon defaults to t-mobile. It could also be call echo that's causing 911 to hang up on you. When I would call comcast to deal with their petty throttling with this rom, I used to have trouble talking to the computer because the echo wasn't fixed. When I changed the mic to analog in the build.prop, it completely fixed the issue.
 
Last edited:
type: 'e2fsck -y /dev/block/mmcblk1p2' (no quotes) and hit enter.

and apps that require additional downloads when downloaded. ex. order and chaos. i get an error and im unable to use such apps.

but for some odd reason i'm receiving much lag after i partitioned a 32GB class 10 micro sdcard,

http://androidforums.com/threads/proposal-theory-for-external-sd-storage-solution-on-f6.819792/
Check posts
#476,
#505,
#504,
respectively.
 
Back
Top Bottom