Recent content by lion567

It seems that correct way is fastboot format cache fastboot format userdata Your way leaves userdata and cache unformated - this can be bootloop reason. You can boot into TWRP fastboot boot twrp-3.1.1-0-lenok.img and format userdata and cache from within TWRP.

Does "ntfs-3g /dev/block/mmcblk1p1 /sdcard/test" works? It seems that ntfs-3g doesn't see device file. Is it realy /dev/block/vold/public:179,129 in MM? I'm still on LP and device file is /dev/block/vold/179:129.

Tzul, do you have any ideas what is /sig/recovery.sig for in A10-70L_S000214_170606_ROW_WCFEE7F639.zip ? I don't find recovery.img in OTA archive and recovery.sig doesn't mentioned in updater script ... :confused: Does TWRP survives after flashing OTA?

Surely it shoudn't. Only exact (and rather old) GFE version 2.7.1.390 works with this module. Newer GFE versions detects Xposed by itself and prohibits to start. Very likely that Good Work behavior would be the same.

I don't know, I don't test that one ever, I've managed to compile TWRP 2.8.7.0 for P6000 Pro in Dec 2015 and use TWRP on my phone since that. Currently I'm using TWRP 3.0. For unknown (for me) reason Deepflex strongly promotes his build of PhilZ recovery as the only one suitable for flashing CM...

Not sure what enhancements you are talking about :confused: Which one - LG logo or bootanimaion. In case of bootloop on bootanimation - your choices are wipe Dalvik/ART cache or factory reset via recovery. Also you can revert to previous version (MEC23G) by flashing full ROM via fastboot...

Don't waste your time - life is short :D Don't wait - try it by yourself and you'll be surprised. I've also use DCU for several months, then switched to CM12.1 in March and install latest CM 12.1 version (2016.06.10) a week ago and quite happy with it. Security updates 01.05.2016 - Stagefright...

therock11, only boot partition hashsum is checked in AW 1.5 (MWD48B) OTA update apply_patch_check("EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:15124480:1aed84fff4ee49b1304b57d62249e3a419331dd5:15126528:be9b0260b6d91f620fa27963cc87762fb8de99f2") ||...

AFAIK Xposed couldn't allow voice calls, it's blocked at lower lower in modem and NVRAM settings. As for cm-su - it's integrated in CM code and much more secure intelligent, than external root tools for stock, thus introduced less security risks.

Xposed won't patch stock ROM with newest Google security updates. Stock ROM still has vulnarable Stagefright Multimedia Framework. And Xposed won't allow neither USSD requests nor voice calls on this tab. Many security enhanced apps, such as mobile internet banking, or corporate remote access...

Not sure, something wrong with TWRP 3.0.0-0? I've looked through commits in GitHub TWRP repo form 3.0.0-0 to 3.0.2-0 and don't find any significant changes. Most commits are about some language translation improvement.

If you use root embedded in CM 13 (cm-su) you could try to temporary disable root access in settings - for developers before starting GFE.

AFAIK there is configurable setting on GFE server that prohibit attachments opening via regular Android apps. It seems that ddimple4 is lucky and this security setting does not enforced on GFE server he is working with. Attachments viewer (a part of SmartOffice code) is embedded in GFE apk, so...

What GFE version non-rooted users use to see the attachment? I guess 3.x? It seems to be a kind of drawback of this hack. Current GFE (3.2.2.442) included special restricted version of SmartOffice 2.5 for attachments viewing without dropping file on device outside GFE. Several versions before it...

*.apk coudn't be a "true" virus (like stealth viruses for Windows) because every apk required java runtime (dalvik or ART) which is separated from apk. Thus every apk is running within its own virtual environment (sandbox). And powerfull antivirus software mostly detect suspicious code inside...