Thanks, impressive ... could you confirm that the DRM fix is working? Because there are some confusing messages.see video proof of working recovery in 1st post
спасибо
Thanks, impressive ... could you confirm that the DRM fix is working? Because there are some confusing messages.see video proof of working recovery in 1st post
Thanks for your reply! I know that, but there's an unsupported lp version of XPrivacy (3.6.7). Ok, I'll try it and report...all modules should be optimised for LP or you'll get bootloop with KK modules
DRM function restore works fineThanks, impressive ... could you confirm that the DRM fix is working? Because there are some confusing messages.
спасибо
TWRP is integrated in kernel. You can install every stockbased custom ROM and TWRP will present in boot partition. For CM and AOSP ROMs use optimised fotakernelWhen i follow this TUT...can i install any custom ROM and keep TWRP??
This is for stock roms with ub!So this is not for stock ROMS? i became bootloops.....
UB = unlocked bootloaderwhat means ub? (are you from german? ICH AUCH)
I think you have "Bootloader unlock allowed: yes"...its not unlocked its LOKEDok...my rom is stock and bl unlocked but it still happens what i said![]()
No it is not, it is possible with a locked bootloaderhmmm i have lollipop with working TWRP and that is only possible with unlocked bootloader......
edit CM flashable zip and add there your device in meta-inf folder where install script. or unpack boot.img from CM zip and flash it via fastbootHi, I've used this kernel to put a recovery on my device, flashed successfully on stock LP5.0.2, then I wanted to flash a stock rom, tried official CM12 and unofficial CM12.1 based, but I couldn't because my device is recognized as Leo and not as D6033, it's the second time I have this problem (with another kernel my device was recognized as D6653 during flash, but in setting was correctly recognized).
I'd like to know why it happens and how to solve this issue.
thx in advance.
Stock flashable kernel 23.1.A.0.690 with integrated TWRP
ONLY FOR UNLOCKED BOOTLOADERS!
Works fine with D6603 and 6653!
Flash via recovery or unpack and flash boot.img via fastboot.
In kernel repacked ramdisk with:
-ric disabled
-adb enabled
-camera api 2
-security 0
-tad off
-init.d enabled
Changelog:
v1 TWRP 2.8.5.0 Download v1
v2 TWRP 2.8.6.0 Download v2
THX my friend from russian comunity for huge help!
For root flash latest SuperSu via recovery.
I have fine working xposed without bootloops (video proof) with this steps:
1. fresh ftf install with full wipes
2. install kernel from this thread
3. install supersu via recovery
4. boot system
5. install titanium backup
6. remove useless system apps
7. clean dalvik via titanium backup
8. reboot system
9. boot recovery and install xposed zip file via recovery
10. boot system and clean dalvik via titanium backup
11. reboot
12. install xposed apk
13. reboot
14. install gravity box module
15. reboot
16. done
With this steps I never have bootloops with xposed.
DRM Restore Function