Last Updated: Oct 06,2014
Well if someone manages to give me a kdz, i'm fine to test it.
sorry for the dupe
Do you see any chance to get a good working remote for F6 in the future with which we could also control other devices, like a set top box?
Currently we have the IR blaster there with extremely limited capabilities.
Many thanks for any advice on that!
I can't say 100% for sure but it's v20b on the following page
Lg Optimus F6 Firmware List
Ok, downloaded, if all goes well... Am i gonna end up with a language i cant read, will i lose my phone sevice?
Downloaded the one circled in the attatchment
I honestly don't know. I'd assume English is an option on pretty much any phone around the world.
Actually a lot.
G2/G3 remote is fully functional remote with many devices and features.
With F6 remote I cannot even change the input on my TV.
Don't really know much about IR blasters whether or not if there are different ones and allows more features, or maybe you guys have the same one you can find in the g2/3 and lg just disabled them. Have you guys scattered the web to find custom apps app IR blasters?
LG locks IR blaster access, so no third-party app will work with it.
I've tried many times to install LG IR apps on my F6 w/o any success.
I do believe the blasters are the same. For some unknown reason LG provides different QRemote features, depending on the provider, another words QRemote for T-Mo F6 is different from QRemote for MetroPCS F6.
Ok then yeah its definitely disabled by LG, have you guys tried switching out the Qremote apks from the T-Mo F6 to the metro F6 or vice versa? to see if the differences were made or not?
So i tried flashing that kdz, did not pass the 100, just stayed there for a long time
So its a fail? Figured .... Gonna have to wait IF we get it
I hope LG corrects the storage issue in JB...
Its not an issue, they give us 2GB of shared system and user storage, as they intended to.
I'm talking about how our SD Card is mounted and how the system registers the partition, so data from apps and such are stored on that 1GB of user storage instead of my 64GB SDcard.
I don't think they will help us with the link2sd, they might put an option to move apps to SD but there are some apps that are not intended to be in the SD card, our best shot is to port a hack to invert the storages. Make the external internal and vise versa like the hack from the photon 4G. No other way, the hacks might work but they will cause problems and let's face there is no way to fix it and lg probably won't help us either because they want to sell their flaships instead of the budget phones
first of all sorry for my English, it is not my mother tongue.
I am from Spain and I have a LG Optimus F6 D505 which I updated to Kit Kat on 17th of July.
Mi opinion about the new firmware it is not positive due to the following reasons:
1.- It is not as fluid with kitkat as before.
2.- There is a common issue related to led and notifications of third party applications as, for example, whatsapp. Not everybody has this problem but almost. There are several solutions which do not work, therefore, they are useless for many people.
3.- As many of you surely know, there is a restriction in KitKat on the external storage management. This problem can be solved using an application or midifiying a file in /system/etc
4.- In my honest opinion, besides what I mentioned before, it was more beautiful the general look and feel with JB. However, besides the fact that it is not so important, it can be easily changed.
5.- Now, there is no way to keep root working indefinitely. Root is possible but every time the phone is rebooted root disappears.
6.- ARJ, the new virtual machine, does not work for everybody, indeed, not in my case.
For all these reasons I am absolutelly disappointed with KitKat, so I am considering to turn it back to Jelly Beam. With JB, Xposed Framework, etc., it is possible to have more features than with KitKat, and what it is more important, a perfect performance.
For those who are interested in the update, even though all these problem, I will comment some tricks.
A) Root (not persistent)
It is necessary to use towelroot v3 and Superuser Elite by ChainSDD -Play Store-, instead SuperSu by chainfare
B) To fix the storage restriction (root neccessary):
- Easy: Install https://play.google.com/store/apps/d...=nextapp.sdfix
<group gid ="sdcard_r" />
<group gid ="sdcard_rw" />
<group gid ="media_rw" />
I haven't tried switching apks, but just by changing the device name in the build.prop one would get different versions of the QRemote.
If you modify the build.prob it will break the IR, tried it when I change my build.prob for milk music to work
The reason we want KitKat is to make custom Roms lol I don't think I'm staying in stock and having the KitKat libs will make it. Easier to port Roms. I suppose, in any case I only use root for adblock haha
How did you root? Lol if it keeps disappearing then either you're not doing something right or there's a init script that unroot each time u boot. Probably the first option lol
Why so many lol?
I did root as I said before.
1.- Installing Towelroot
2.- Installing Superuser
3.- "Make it ra1n" from Towelroot
There is no complex things where I could make a mistake. Is it there?
(Unfortunately root is lost when you switch yout device off).
You are wong, it is not the first option, but the second one. It is exactly because the init scripts have changed. In fact linux boot systems (GNU and not GNU) are constantly changing for several reasons. One of them is related to security issues.
As exploits are found, apps like towelroot appear, then as theese apps appear manufarers patch the firmwares. (As usual). (*)
This patches can be applied either to the kernel or to other parts. This case occurs to other LG recent Kit Kat roms indeed, i.e., LG L9 II.
Root Permanente LG Optimus F6 con Kit Kat -sin confirmar- - HTCMania (In Spanish) It can be observed that, in recent LG's kitkat, towelroot failure is caused by a change in boot scripts ( /system/etc/init.engdo.post_boot.sh , /system/etc/install-revovery.sh and /system/etc/install-recovery.sh
If you dare, you can try applying this method of 'presistent root to your F6 when you, and LG, want to update it to Kitkat.
(*) You can see here: https://lists.debian.org/debian-security-announce/2014/msg00130.html the vulnerability (CVE-2014-3153) in which George Hotz (aka geohot, popular for jailbreaking iOS and PS3 as well) based its last version of towelroot. As you can see this vulnerability was made public in June, and Kit Kat for LG F6 D505 is available from 17th of June.
If you read it probably you will think that LG F6 firmware with Kit Kat has been patched. Now, if so, probably you are right.
PS: Perhaps my 'English' is worst than I thought. I can imagine there are people interested in new stockroms for modding and hacking (I did not say the opposite, did not I?) but most users just want updates in order to improve overall features and performance. What is more, I think manufacturers aim these updates precisely to do that, not for hacking nor modding. What I tried to comment is that, in my opinion, this new firmware not only does not improve the user experience but the contrary (apart from whether is good to have more roms or not). (In English it is not easy for me).
How am i wrong? Didn't you just say it was because of init scripts? lol all you have to do is delete em. If the Kernel was built after june 2nd? i think thats geohot said??? then the exploit was probably patched. The install-revovery.sh script is nothing new, i've seen that around since gingerbread days, just delete and it should be good. Im pretty sure thats how towelroot roots your phone though? i could be wrong but im sure that towelroot placed that file there and not LG lol. Haven't seen LG used that script in a while and i don't see why they would now its kinda useless.
Chevanlol, you are "wrong" because of your own comment:
HLHLGD505 went over the steps he performed for root and they seem sound. So you were "wrong" because you originally implied that he it was likely his or her fault. Given that HLHLGD505 is a new member, that English is not his or her first language, and that he or she is providing helpful information, I think you could have phrased your comments in a way which was more respectful (you could start by dropping the lolz).
To HLHLGD505: Your English is absolutely fine. Please don't let the fact that it's not your native language discourage you from contributing further here. Your comments make me think I don't need to be in such a rush to get KitKat once it becomes available for my device.
Ok first of all, its not impossible to be incorrect when you're rooting. When I read peoples comments I don't check to see whether they are a new user or not or treat them differently than I would treat another person even if I personally knew they had experience with things like these before. I listed 2 options. 1. Either you did something wrong "once again not impossible cause we're not immune to mistakes" or LG is screwing with you with a init.d script. There could have also been a third option such as maybe LG block it in KK update but I highly doubt that because the user said root is not persistent meaning the device was actually had rooted at some point. In a other post about you said something about the update being released on a certain date and that LG might have killed the exploit within the kernel. That's not impossible but somewhat unlikely since LG build date for the kernel could be since way back before June. The release date and the actual ROM/build date is entirely different. If I had my hands on the KK ROM for the 505 I could tell you right now whether the towelroot exploit was killed or not.
I'm not wrong. I wasn't implying that he/she was stupid or something and I absolutely was implying that it was the first option I listed as to why the root wasn't working correctly because in his second post he/she said
"You are wong, it is not the first option, but the second one"
Is everyone forgetting I listed a second one? Which is why I replied to how am I wrong if the second option I listed was correct?
Separate names with a comma.