Search results

I removed the files 3 days ago - at this time they have been online for 4 weeks... :rolleyes:

Savoury: I did upload the requested files. Any news on that? Or is the thread really dead?! :eek:

Done. I needed to pack the files because of the size limit. They are from H850 V20a OPEN_COM.

Which KDZ file did you flash? V10c?!

Strange that refurbish option is working for you, as it is not for me and autoprime also wrote here http://forum.xda-developers.com/showpost.php?p=70048689&postcount=5 that "refurbish is not supported" in UPPERCUT. Which software version did you flash? And which was your software version before...

What were your steps before? Flashing KDZ with refurbish option?! Or Wiping + flashing KDZ with upgrade option?! Or something different?!

Will the Themes also work on Nougat (V20a) or will it crash? It seem, that the old method to resize the NavBar via dimens.xml in framework-res.apk seems not be be valid for Android N anymore. How can this be done now? And Savoury: All the links are down! :(

deleted

Only if someone is on the same point: For me, it is only working to flash the COMPLETE ZIP! When I flash bootloader only, LGUP does not detect the model type of my device anymore (detected type is "Unknown"). I have tried it now for 2 times with similar results... BTW: I used this method to get...

"and the error msg should go away on next reboot." I get 3 error messages related to this. Will I get rid of all of them? "old LGUP methods" means tool version 1.11 instead of 1.14? So use version 1.11 for MM and 1.14 for N?! Unfortunately, refurbish does not work even under MM for me regardless...

At first: Big thanks for your quick response!!! to 1.: The reason for 10C instead of 10E is simple: you do not have a KDZ file for 10E on your codefire drive (only a ZIP), but for 10C the KDZ was available. And the links to LG server were not working yesterday for me. I read Uppercut the first...

I had several problems with this procedure (coming from V20a): 1. After flashing 10C BOOTLOADER ZIP via TWRP, LGUP was not able to detect my device type anymore, but this worked with previous bootloader. Why? 2. Flashing the 10C COMPLETE ZIP did result in a loss of TWRP (although recovery.img is...

LG bridge raises an error, that a SW download is not possible. Is the relock required to get LG Bridge to work?

solved

I already asked the same question some posts before (LG G3 D855). But the last 2 pages are full with offtopic stuff. :rolleyes: Short version of answer: We will have to wait for a deodexed version of the Marshmallow ROM!

After the installation of version 3.3.6c it looked good: Checking for Root with success, checking for xposed module running and reparing (activation & reboot). But after the reboot I am now stucking on the next screen: "Checking for root access", altough I can see the toast message, that root...

Done! 01-05 19:29:53.808 I/Amplify: (17960): MaterialSettingsActivity onCreate called 01-05 19:29:53.888 I/Amplify: (17960): MaterialSettingsActivity setting up IAB 01-05 19:29:53.948 I/Amplify: (17960): MaterialSettingsActivity Starting SELinux service 01-05 19:29:54.698 D/Amplify: (17960): IAP...

Yes

Yes!

But the sdk23 version of xposed should be for marshmallow?! :confused: Or do you mean that there is no version working on LG devices? Cause in the xposed download thread, I can only see that it will not work with Samsung devices at the moment...

Permanent root is included in the files of first post. And with modem files of firmware 21c from here http://forum.xda-developers.com/lg-g3/general/radio-modem-lg-g3-t3110376 I do not have issues. But xposed does not work for me and I would be nice if someone else can try it and share the results...

Here the filtered log from the Amplify startup (I cleared the log before I started Amplify): 01-04 20:25:45.570 I/Amplify: (26721): MaterialSettingsActivity onCreate called 01-04 20:25:45.620 I/Amplify: (26721): MaterialSettingsActivity setting up IAB 01-04 20:25:45.630 I/Amplify: (26721)...

Is there anyone who got xposed (v79) to be working with this ROM? I get a bootloop on my D855, when I install it in TWRP 2.8.7.0

I get a bootlop (endless spinning LG logo) with LG G3 (D855) on Android 6 (bumped v30b) when I install xposed (arm v79 sdk23) in TWRP 2.8.7.0 After running the uninstaller within the recovery the device does boot again. Any ideas? Is there anyone out there with G3 and Marshmallow, who tried it...

Done! Should I post the log here or can I send it to you personally?

Yes, doesn't work for me. :( Yes, for me it does move. All that happens in less than 0.5s, so it was hard to do a screenshot, but I got it! :cowboy: My log looks similar as Mickys log: 01-04 11:36:29.971 I/Xposed ( 480): ----------------- 01-04 11:36:29.971 I/Xposed ( 480): Starting...

I tried the current version and some older ones: The same issue on all versions! And it does not matter, if the module is activated in xposed or not. Any ideas?

I don't want full Nfc, but it is the only thing I get to work when I follow the instructions. Can someone where it is only enabled when screen is on please post his modded Nfc.apk?

No, did not work for me! :cyclops: Did it work for you?

As already wrote, this does only work to get the NFC enabled all the time (screen on and screen off). But it does not work for NFC only enabled while the screen is on (lock and unlocked). Do you have a proper solution for that?

I totaly agree with you. I have also given up regarding this issue and I am waiting for someone posting a working file. :good: I tried all version within this thread and also tried to modify 3 or 4 different versions of the nfc.apk myself, but I get only the state of always enabled NFC (also...

This file works for me for Android 5.0.2 on my Xperia Z1c. I can now use NFC while screen is on (both locked and unlocked screen). But NFC is now also active, while the screen is off! Was this your intention? And can you, please, create a version were NFC does only work with active screen...

Doesn't work under Lollipop (Xposed alpha 4) on my Z1c. Other modules work. Any ideas?

CE4 EURO-LTE. Thats nice!:good:

Now that I got the Xposed alpha 4 framework working on my Xperia Z1c with deodexed Lollipop (5.0.2) stock ROM, I'm having trouble with this module! Other Xposed modules are working (e.g. APM+), but the NFC lockscreen enabler doesn't: NFC works normaly with unlocked phone, but no reaction while...

OK. Fine. :good: And do you know which baseband is included? I need a generic DE or at least a CEx (Central Europe) variant.

The CWM from the link is for the A500. It does work, when I flash it into the secboot section, but not flashed on recovery section! I will try the installer app you mentioned, thx... UPDATE: The recoveries inside the installer app are all older than the one I am trying to upgrade. :( Maybe...

for locked bootloader? Silly question: Can I flash this ZIP by TWRP or CWM on a device with locked bootloader? I am currently on a pre-rooted 14.5.A.0.207 odex rom and a locked bootloader.

I just updated the V8 bootloader to V9 (CWM flash). :cowboy: I flashed the TWRP 2.6.3.0 as secondary boot. My "first" recovery is still an old CWM 5.5.x.x, which was supplied by the bootloader V8 update. It didn't work to flash the recovery.img supplied here...

The last time I flashed the A500 was in year 2012! ;) I flashed V8 manually yesterday with nvflash and it works well now with the secondery recovery.

According to this thread http://forum.xda-developers.com/showthread.php?t=1622425 it is only possible for V4 and V5 to flash a cwm package (see first post, second quote). I think the reason is, that a blob is inside the zip, but flashing of blob files was first supported by V4 - but it's only a...

I have a similar issue as mentioned in the second post: writing secboot... FAILED (remote: (00030003)) Unfortunately, I do not see a solution for this. :( Is it maybe a problem with the fastboot of my out-dated bootloader version (Skrilax V3)? And what will happen when I flash the image to...

V3 => V9 I'm currently on BL V3 and flashing the latest CWM recovery image to secboot fails (Error 0x30003). So maybe updating the bootloader to V8 or V9 will help. Is the only way to update by the nvflash tool or is there any easier possibility?

Can I flash the TWRP recovery by the CWM recovery? And will my old backups, which I made with CWM also work with the TWRP? And does the flashing really work with locked bootloader? I wonder because the boot.elf is within the ZIP file.

I have the same problem as ronin. No ideas? :rolleyes: I am using CWM version 6.0.4.7

Okay, I adapted the stock framwork and it works fine now, thanks! Does this mean, in the blackout pack you basicly exchanged the backgrounds of all the other apps in this way to make them black?

Is there any chance, that you can adapt your framework for the swap, please?! :fingers-crossed: I want your black framework!

Shaftenberg, I found 2 problems with your black framework: :( 1.) Entering settings -> Storage leads to FC in "settings" 2.) A second FC occurs on "android.process.media", when connecting the phone to the USB cable It took me some time to find out, that your framework is root-causing this...

After playing around with Omars ROM, I used the pre-rooted "91.2.26001.Retail.en.EU - 4.1.2" from here: http://forum.xda-developers.com/showthread.php?t=1936512 to flash back to Stock-ROM. After that I installed your Files. UPDATE: I found the root cause! I soon as I install the black framework...

Regarding battery life and performance: Your Mod is my daily driver. Good work! Especially the changes on the system UI are really nice! Also battery life is very good. :good: But regarding stability, I have 2 problem: 1.) Entering settings -> Storage leads to FC in settings (not my first...