yashsingh1/xdaforums huggingface dataset:
[Xperia Z4/Z3+ General] [NUT]:
The more I think about it and read up on the different security systems, I might be coming to the conclusion the RIC kernel integration actually IS Sony's implementation of the dm-verity module...

I'm not sure though, I still need that ivy kernel to check it all.
[Xperia Z4/Z3+ General] zxz0O0:
Actually while reading about dm-verity, it came to my mind that newer system.sin files always have some additional data at the end. I've never bothered to check it and just cut it off in PRFCreator. Now I checked it and it is indeed the verity metadata and the hashtree.

This may make things even more compilacted.
[Xperia Z4/Z3+ General] Sacktreter:
hi, back from work, sorry for to be late. So many posts meanwhile...

1. When i flashed rooted phone back to stock kernel only start screen came, no green light and no vibes. Loop was before.

2. - I flashed system.sin, kernel.sin and boot.img --> flashtool_2015-09-07_04-53-17.log

- replaced wp_mod.ko in /byeselinux and /easyroottool, then run install.bat option 1 --> install.txt

- restart --> 4 XZDualrecovery-files as log

- Searching for wp_mod.ko in phone --> only 1x in /data/local/tmp/

All works fine.

3. How can i log when init stage is running?

more logs are coming up (dmesg etc)...
[Xperia Z4/Z3+ General] zxz0O0:
/dev/block/bootdevice/by-name/system /system ext4 rw,seclabel,relatime,discard,data=ordered 0 0

Why is system mounted as rw?

byeselinux should work fine. At first I thought it might fail due to 32bit code (similiar like wp_mod) but it's not even needed since the necessary symbols are in kallsyms again (in some firmwares like Z3 they removed it so I had to use a less portable method). :)
[Xperia Z4/Z3+ General] Sacktreter:
following I put in installrecovery.sh at line 19 and ca. 126

18
19 WATCHING="/${DRPATH}/message2.log"
....
126 ${BUSYBOX} dmesg >> ${WATCHING}

Here is the log.
[Xperia Z4/Z3+ General] zxz0O0:
Was wp_mod loaded? There is nothing logged about it.

byeselinux though is not correctly working.
[Xperia Z4/Z3+ General] McBane87:
For me it looks like the byeselinux module isn't working completely. First part is OK but second looks strange:

[ 7.079296] byeselinux: module loaded
[ 7.082090] byeselinux: old selinux_enabled 1
[ 7.100687] byeselinux: current selinux_enabled 0
[ 7.119969][COLOR="Red"][B] byeselinux: old selinux_enforcing: 13645482734322188288[/B][/COLOR]
[ 7.119973] byeselinux: current selinux_enforcing: 0
[Xperia Z4/Z3+ General] zxz0O0:
Yes indeed. According to the source code selinux_enforcing shouldn't be in kallsyms anyway. Not sure what kernel he uses though.
[Xperia Z4/Z3+ General] McBane87:
Should be the Stock-Kernel from 28.0.A.7.24
[Xperia Z4/Z3+ General] DHGE:
kernel options for SELinux do not work

I tried to disable SELinux when rooting 28.0.A.7.24 via the options I found researching it - to no avail.

I ended up patching the SONY provided (and modified!) source to make SELinux and RIC believe they are active but let every call return with "permitted".

Speculation by me is that any options are overridden by init or SONY modifications in the source though i did not find obvious hints for the latter.

thread: http://xdaforums.com/z4-tablet/help/enybody-root-t3154926
[Xperia Z4/Z3+ General] zxz0O0:
byeselinux patches the kernel to disable SELinux. [MENTION=4712883]McBane87[/MENTION] can you provide a new compiled binary? I've made some changes to the source.

First priority is to get byeselinux and wp_mod to work. wp_mod still remains untested (though I'm very sure it won't work).
[Xperia Z4/Z3+ General] dl12345:
I have a functional version of TWRP built. Everything seems to be working with a only one or two oddities that I can see (the Data partition is listed twice in the advanced wipe screen and it offers to let you back up the android secure partition at 0 bytes in length). I'll get around to uploading my config later today, but here's a link to the recovery image if you want to play with it. Be warned, this is not properly tested so use at your own risk.

To use

adb reboot bootloader
fastboot boot recovery.img
[Xperia Z4/Z3+ General] DHGE:
not on SGP712 :(

[MENTION=5971873]dl12345[/MENTION]

fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
[COLOR="Red"]FAILED (remote: dtb not found)[/COLOR]
finished. total time: 0.906s

28.0.A.7.24 on my Tablet

... as to be expected
[Xperia Z4/Z3+ General] [NUT]:
I doubt the dtb will be valid for the tablet...

---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------

That is very, very bad news for LB root/recovery ... that means the check takes place during kernel init or is done by the bootloader... :rolleyes:
[Xperia Z4/Z3+ General] McBane87:
Unfortunately I'm not able to reach my build-system at the moment. Will do that this evening. ...
[Xperia Z4/Z3+ General] McBane87:
See in Attachment newest byeselinux Module

[MENTION=3975929]zxz0O0[/MENTION]
[MENTION=6902252]Sacktreter[/MENTION]
[Xperia Z4/Z3+ General] dl12345:
Yeah it is a bit of a hassle to disable. You need to set the kernel parameter for runtime disable of SELinux and compile a new kernel. Just attempting to define a service in init.rc won't switch it off because of the SELinux policy. The solution is to use SuperSU's ability to execute scripts in /su.d and put in a /system/bin/setenforce 0.

This relies on SuperSu being properly installed of course. It worked fine for me and my ROM switches into permissive mode at boot time.
[Xperia Z4/Z3+ General] venkat kamesh:
Try this kernel included recovery

hello testers and [MENTION=6902252]Sacktreter[/MENTION]

this kernel included recovery

let's give a try ( dont worry it boots )

flash it by flashtool (fastboot mode )

please report back

waiting for your report ;)

( any volume key trig will get you twrp :p )
[Xperia Z4/Z3+ General] Sacktreter:
tested new byeselinux.ko, looks good.
[Xperia Z4/Z3+ General] dl12345:
It happens during kernel init. If the system partition is altered the checks fail.

I agree it's a bad thing. I think locked bootloader recovery is impossible. Frankly, I think that this is exactly why Sony implemented DM_VERITY, to make locked bootloader recovery and exploits much much harder.
[Xperia Z4/Z3+ General] McBane87:
Still looks not good:

[ 8.474296] byeselinux: module loaded
[ 8.477055] byeselinux: old selinux_enabled 1
[ 8.498657] byeselinux: current selinux_enabled 0
[COLOR="Red"][B][ 8.517459] byeselinux: old selinux_enforcing: 0[/B][/COLOR]
[ 8.517464] byeselinux: current selinux_enforcing: 0

Unless selinux_enforcing is already disabled at this stage ( I doubt that), I would expect this:

[ 8.474296] byeselinux: module loaded
[ 8.477055] byeselinux: old selinux_enabled 1
[ 8.498657] byeselinux: current selinux_enabled 0
[COLOR="Green"][B][ 8.517459] byeselinux: old selinux_enforcing: 1[/B][/COLOR]
[ 8.517464] byeselinux: current selinux_enforcing: 0
[Xperia Z4/Z3+ General] zxz0O0:
Code must be correct. What I can think of is, they don't use selinux_enforcing variable (thus it's still uninitialized) anymore, they just assume it's always set to enforcing (permissive does not exist anymore). This would resemble the official kernel source from Sony. Still does not explain why selinux_enforcing is in kallsyms though.

It would be extremly helpful if we could load the kernel into IDA but I'm unable to extract the zImage. DooMLoRD's script seems to fail.
[Xperia Z4/Z3+ General] McBane87:
I could give you the compiled Kernel from source. But I'm afraid you need the original from Sony, don't you?
[Xperia Z4/Z3+ General] Sacktreter:
after a complete flash with autoroot and first install recovery this log came out.

Maybe some is interrested at dmesg message2.log
[Xperia Z4/Z3+ General] DHGE:
@zz0O0

The latest Flashtool works with the 64bit kernels.

More interesting might be init in IDA.
[Xperia Z4/Z3+ General] zxz0O0:
Extracting the data from the sin was never a problem, the problem was loading it in IDA. In older kernels the zImage was lzop compressed but now it's not compressed anymore. Anyway I've figured out how to load the 64bit kernel into IDA. :)

It looks like byeselinux is doing its job.

[ 7.125644] type=1400 audit(1664326.889:3): avc: denied { write } for pid=414 comm="busybox" name=".XZDualRecovery" dev="mmcblk0p43" ino=301329 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=dir permissive=1 ppid=380 pcomm="chargemon" pgid=380 pgcomm="chargemon"

Also note the permissive=1 here which means it's not blocked, just logged.

[MENTION=6902252]Sacktreter[/MENTION] that custom kernel you're using, does it have Sony RIC disabled?
[Xperia Z4/Z3+ General] [NUT]:
Was chatting with [MENTION=3975929]zxz0O0[/MENTION] earlier, ranting on how unhappy I was because I decided to skip the Z3+/Z4 series as well and suddenly it hit me...

As a new phone with my contract renewal, I got a Xperia M4 Aqua... it's been waiting for XZDR 2.9 and root ever since I got it... but it also has a 64bit cpu AND it uses a 64bit kernel :victory:

I have something to test with which is actually comparable to the Z3+ :cool:
[Xperia Z4/Z3+ General] Sacktreter:
This kernel i use: A Z3+ E6553/Dual E6533 Auto Root Kernel.

first time RIC was shown in log by Flashtool (0.9.19.1).

After flash boot.img in flashtool fastboot mode i pressed "Reboot device into system". I din't unplug USB.

flashtool made this:

[COLOR="SeaGreen"]# start to flash boot.img[/COLOR]
08/027/2015 03:27:44 - INFO - Flashing selected kernel
08/027/2015 03:27:47 - INFO - sending 'boot' (41308 KB)...
08/027/2015 03:27:47 - INFO - OKAY [ 1.499s]
08/027/2015 03:27:47 - INFO - writing 'boot'...
08/027/2015 03:27:47 - INFO - OKAY [ 0.371s]
08/027/2015 03:27:47 - INFO - finished. total time: 1.870s
08/027/2015 03:27:47 - INFO - FASTBOOT Output:
sending 'boot' (41308 KB)...
OKAY [ 1.499s]
writing 'boot'...
OKAY [ 0.371s]
finished. total time: 1.870s

08/027/2015 03:27:47 - INFO - Please check the log before rebooting into system
08/028/2015 03:28:08 - INFO - Now plug your device in Fastboot Mode
[COLOR="SeaGreen"]# here i pressed "Reboot device into system"[/COLOR]
08/028/2015 03:28:09 - INFO - Device will now exit fastboot mode and start booting into system
08/029/2015 03:29:00 - INFO - Device connected with USB debugging on
08/029/2015 03:29:00 - INFO - Connected device : Sony Xperia Z3+
08/029/2015 03:29:00 - INFO - Installed version of busybox : BusyBox v1.23.2-Stericson (2015-04-10 10:51:32 CDT) multi-call binary.
08/029/2015 03:29:00 - INFO - Android version : 5.0.2 / kernel version : 3.10.49-ImageBreaker-Alpha / Build number : 28.0.A.7.24
08/029/2015 03:29:00 - INFO - Checking root access
[COLOR="SeaGreen"]# I allow smartphone to accept USB connection[/COLOR]
08/029/2015 03:29:39 - INFO - Root Access Allowed
[COLOR="Blue"]08/029/2015 03:29:39 - INFO - Stopping ric service
08/029/2015 03:29:39 - INFO - ric service stopped successfully[/COLOR]
08/029/2015 03:29:39 - INFO - Installing toolbox to device...
08/029/2015 03:29:39 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
08/029/2015 03:29:40 - INFO - Running installftkit as root thru sysrun
[Xperia Z4/Z3+ General] DHGE:
here could be Devries sources

[MENTION=6902252]Sacktreter[/MENTION] [MENTION=3975929]zxz0O0[/MENTION] [MENTION=4533099]Devries[/MENTION] [MENTION=5971873]dl12345[/MENTION]

Devries put his source on Github:

https://github.com/DevriesL/E6553_ImageBreaker

Reading his comments here in thread A Z3+ E6553/Dual E6533 Auto Root Kernel I got a sense that his binaries are not necessarily compiled from the source on GitHub.

Lots of gotos at places where I just changed (with comment) the return code - last time I looked.

With the code posted it is impossible to activate SELinux.

see also: http://xdaforums.com/showpost.php?p=62728445&postcount=48
[Xperia Z4/Z3+ General] Devries:
the boot.img I uploaded only with commit "disable RIC and SELinux" , and by this method , selinux always set to permissive.
[Xperia Z4/Z3+ General] zxz0O0:
Due to dm-verity feature, perm root / recovery on locked bootloader will highly likely not be possible for this and upcoming devices.
[Xperia Z4/Z3+ General] shoey63:
Yep. Same as the "concept rom " for Z3. If system is modified in any way, you don't get past the kernel splash screen on stock kernel. If you want root, you MUST unlock the bootloader, say goodbye to DRM keys and be on a custom kernel.
[Xperia Z4/Z3+ General] Kelvin0007:
Wasn't there a way to keep drm after UB in a previous xz release?
[Xperia Z4/Z3+ General] [NUMINIT]:
It's been possible to restore some functionality that gets lost with the keys, but the keys themselves are gone forever.
[Xperia Z4/Z3+ General] shoey63:
Correct. This is the thread for it

http://xdaforums.com/showthread.php?p=56541777

But it involves rolling back to kitkat, which Z3+/z4/z5 etc. have never had, and will not ever have:(

From Z3+ onwards, the only way to root the device will be be to unlock bootloader, lose DRM keys and flash a custom kernel.
[Xperia Z4/Z3+ General] [NUT]:
No, actually, they updated to include LP (I'm using it as we speak on my Z2).
[Xperia Z4/Z3+ General] [NUMINIT]:
But will it restore stuff that's been added with the XZ3+/4?
[Xperia Z4/Z3+ General] AndroPlus:
DRM restore patch won't work (at least for now)

http://xdaforums.com/showpost.php?p=62753170&postcount=1152
[Xperia Z4/Z3+ General] [NUMINIT]:
Damnit, I almost got excited there.
[Xperia Z4/Z3+ General] Groggas:
Hey man! But what if someone manage to port one of this kitkat versions.

http://www.christianpost.com/news/android-4-4-kitkat-update-to-support-64-bit-smartphones-104848/

Could this patch work then?

Skickat från min E6553 via Tapatalk
[Xperia Z4/Z3+ General] DHGE:
Sure - if you sign the resulting FTF with SONY's private keys to flash it past the BL.
[Xperia Z4/Z3+ General] AMoosa:
Are the keys still private? Following the Sony hack? Lol.

Sent from my Xperia Z3+
[Xperia Z4/Z3+ General] ROHIT GOUD:
hyy iam unable to root my mobile sony xperia z3+ can u plz findout hoe to do it even i tried a lot but unable to do it i urgently needd to root my mobile plz send me link or process or steps hoe to do it
[Xperia Z4/Z3+ General] addicted1900:
No words for this. Try to search properly and you will find...
[Xperia Z4/Z3+ General] Kelvin0007:
There's no root unless you unlock the bootloader and flash kernel exploit, so its sad for ppl with lb as me..
[Galaxy Note5 Q&A, Help & Troubleshooting] vaeevictiss:
so im up to my renewal, and ive been looking at the note 5 and the LG g4. I really like the note, however the lack of SD card bugs me, and the fact that the Verizon version apparently bricks when you root it is making me lean towards the g4.

That being said, I can get the note 5 for free right now. IF i did go with the note 5, knowing there is no root, am i **** out of luck getting all my apps + their data from my titanium backups to the Note 5? I have a ton of backup up app data and if i would have to redo all of it im def going with the G4.
[Galaxy Note5 Q&A, Help & Troubleshooting] jthrasher47:
No.. Just copy the whole titanium backup folder to the note 5.. Simple as that
[Galaxy Note5 Q&A, Help & Troubleshooting] quangtran1:
I'm curious how you can get TB to run without root.
[Galaxy Note5 Q&A, Help & Troubleshooting] sml2004:
. But with data restore your hit until root
[Galaxy Note5 Q&A, Help & Troubleshooting] jthrasher47:
It will not be long until this thing gets rooted
[G3 Q&A, Help & Troubleshooting] Gamer4Life:
Hello, i have xperia z1

i like it's 6H+ screen on time

i like it's snappy lag free performance

i am happy with it's camera , but i don't like it's low light performance

What should i expect from LG G3 ?

How is screen on time ?

how is camera?

how is performance ?( i used LG G3 once for one day but i returned it, and it's ui didn't feel as smooth as z1, it feelt more like touchwiz with little stutter here and there)

how much free ram is available on the 2gb/3gb versions on average?

do 1080p/720p videos look blurry on the 1440p screen ? (720p don't look good on my z1)

and is it a good deal to get LG G3 2gb version for MY Z1+50euros
[G3 Q&A, Help & Troubleshooting] serqeftin:
my opinion, don't change your phone, Z1 is better than G3, G3 ROM and kernel is customised, like Samsung, HTC, everytime use pure android device, like Nexus, Sony. (sorry for my english)
[G3 Q&A, Help & Troubleshooting] GuestK00280:
1) 6H and 5% more . That's if you keep brightness below 50%...

2) Camera is good, but nothing spectacular. Low light is.. normal, at best.

3) Laggy. Lags are EVERYWHERE: from last "Initial setup" page and smart notice widget to messaging app... It's as bad as I9300 on latest firmware...

4) 700m on 3g model.

5) no, they look sharp enough.

My advice? Stay on Z1.
[Ascend Mate 7 Q&A, Help & Troubleshooting] blackinfinity:
Lets face it, the M7 camera ap is not much to put in the christmas tree.

Hopefully you will also be able to get better photo result with a 3rd party app ?

Which maybe have better auto settings etc, better auto exposure ?

I have tried the google camera app a little... it is a lot faster then the m7 app faster interface.. but I see no direct

improvment/difference in photo quality. But the Google camera app is good enough to replace the mediocre M7 Camera app, but I am sure there is even better ?
[Ascend Mate 7 Q&A, Help & Troubleshooting] muzammil84:
a better camera. Don't know if the photos are better but more options/tweaks.
[Ascend Mate 7 Q&A, Help & Troubleshooting] Kalemucu:
Hi

I dont understand why people are complaining about mate 7's camera so much. It is much better than my old LG G2's camera.

I am using stock camera with no tweak. Really happy with its performance. I am on holiday with my friends and as you guess i took tons of photos and selfies, all my friend praised my phone's camera as having a very good performance.
[Ascend Mate 7 Q&A, Help & Troubleshooting] blackinfinity:
I have tried an app called perfectly clear it brings superior quality to the m7 camera in hdr realistic mode.. A must have now... Must good hdr apps cost money...

Down side with the app is that you must hold the of steady since the app takes two pics and merge them so it takes a few seconds longer to take the shot but it's worth it.
[Xposed Framework Modules] robertogl:
Hi! Another little module...

This module allows the LED to stay on while the screen is on. So if you receive a message while the screen is on, the led will turn on.

For my decision, the led will stay on also if you unlock the phone with the led on, or if you turn off the screen with the led on. You can turn off the led only pulling down the notification bar (you don't have to read the notification). Of course, if there are no bugs: i've seen that this is working with the 'charging led', or the sms, or some Tasker tasks, for example. With WhatsApp it doesn't seem to work, but this could be a WhatsApp problem. Or my problem. Of course if you have the screen on and you receive a WhatsApp message, the led will turn on.

I've already implemented a way to change that, as you can see on GitHub: using the code i've write, you can for exampe turn off the led when the screen turns on. Or something else... But this is not implemented in the apk, so...

This works only from Lollipop

. For Android 4.x, there is the beautiful XLED.

Download: http://repo.xposed.info/module/com.robertogl.ledonscreeoff

Source: https://github.com/robertoglxda/LED-On

Changelog:

22/08/2015

V1.0

- Initial release

Big thanks to @C3C076 for GravityBox: i've worked on this using his code, basically.

Thanks also to cinhoo, author of XLED. His module give me this idea. Well, because XLED doesn't do that on Lollipop, and i was sad...
[Xposed Framework Modules] Macusercom:
I'm using Lightflow and it doesn't work. Nexus 6 running latest CM12.1 and latest Xposed version by romracer.

Gesendet von meinem Nexus 6 mit Tapatalk
[Xposed Framework Modules] robertogl:
How that led works? I remember that on nexus 6 there were some problems, if I'm correct to use that you have to use root. Look at xposed log, there are errors?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] robertogl:
Have you enable the module using Xposed Installer? The module isn't loaded, for some reason.
[Xposed Framework Modules] Macusercom:
Well, it turns out that Xposed Installer 3.0 Alpha 2 is now incompatible with the latest Xposed. After upgrading to Alpha 4 it works :o

Gesendet von meinem Nexus 6 mit Tapatalk
[Xposed Framework Modules] robertogl:
Well, happy that it works ;)
[Xposed Framework Modules] dallas220:
hmm, I can't seem to get it to work..

Using the latest Alpha 4 running 5.1.1 , Nexus 5. Is there something I am missing?
[Xposed Framework Modules] robertogl:
Can you post the Xposed log?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] dallas220:
Yes, of course

Hopefully I did this right.
[Xposed Framework Modules] robertogl:
Like @Macusercom, the module isn't loaded. Check if it is selected on Xposed Installer.
[Xposed Framework Modules] dallas220:
Hey, thanks brother for the replies, appears its working now!! Thank you :)

oh, will this have any noticeable impact on battery levels , just curious

5 star module :)
[Xposed Framework Modules] robertogl:
Nope, you not even notice it ;)

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] vagenrider:
very good module..will be great if you add option for blink the led on internal storage activity..
[Xposed Framework Modules] robertogl:
For this you have to ask to the developers of app like Light Manager ( [MENTION=4047489]mckoo[/MENTION] has a thread on xda).

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] Kenzo9x7:
Hey I like your module <3 :)

No problem on my s6 (g920f)

Thanks ;)
[Xposed Framework Modules] sherri:
So wait..... I have been begging for this for 4 or 5 years.... Since Gingerbread removed this native option from Froyo.... I had to root and use a custom ROM. CM had it up to ICS. AOKP and ROMs based on it had it. AOKP stopped development for my phone, Motorola Razr Maxx. The only ROM that enabled it in Kitkat was [MENTION=5709478]tonyt.[/MENTION] version of AOKP. Used that forever. Finally, CM enabled it in their Lollipop version, and it works beautifully with Light Flow.

Now, if this module works on Lollipop, I can try any ROM for my phone? REALLY? Haven't played with CM long enough yet, so giving it a try for a few days. Then I will try LS with this module. If it works, I will be a very happy woman! I will even donate!
[Xposed Framework Modules] sherri:
Place to donate?
[Xposed Framework Modules] robertogl:
My signature [emoji14]

So, it is working?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] sherri:
Sorry... I view this on Tapatalk, so there are no signatures. I will check when I get to a pc. And yes, it works perfectly! Currently using a Liquid Smooth LP ROM. Your module and Light Flow are great! Thank you!
[Xposed Framework Modules] robertogl:
Good ;)

You can donate from here https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=QK5CWVFKU9UXE

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] Swizzle82:
Sadly not working on stock G4.
[Xposed Framework Modules] robertogl:
Log?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] Swizzle82:
Trying to pull one but can't get anything to show up.
[Xposed Framework Modules] yurividal:
Can you PLEASE add an option to disable the lights completely when Priority or None mode is enabled?? Android 5.1 allows led on priority mode (5.0 did not).

This is terrible for use it at night, beside bed.

Can you???
[Xposed Framework Modules] :
Hi dev....it don't work for me.....I have Galaxy Alpha (G850F) whit rom 5.0.1 ....Plase fix it thank you
[Xposed Framework Modules] TheFerhatKing:
[MENTION=613602]robertogl[/MENTION] I thank you very much, I used XLED on KitKat too and I noticed too that it doesn't work anymore, I thought the problem is the Sony Lollipop not the the generall Android Lollipop.

Sony Xperia Z2
[Xposed Framework Modules] robertogl:
Sorry for the delay. Have you the Xposed log?

You can use other apps for that.

Xposed log?

Inviato dal mio GT-I9505 utilizzando Tapatalk