Quote:
Originally Posted by
sebamerca
Hi.
First thanks for you complete guide.
Now, I did all the steps correctly, but in the final, when I tryed to flash de boot animation logo TWR show me that is all ok, but my phone don't boot... It's stock in the animation all the time. What happend?
What can I do for return at before steps?
The last moment that my phone works, was before to flash the SuperSU. After that, the phone stock it in the big M screen (the white one), then I flash the animation logo zip.
I need my phone D:
EDIT: I add the next --> When I connect my phone to PC, while the first is in the TWRP mode, the windows explorer showme 2 folders: "TWRP" and "0". Is this Correct?
EDIT 2: I flashed the Resurrection Remix ROM (http://forum.xda-developers.com/moto...remix-t3316232) using TWRP and my phone works, but I losed the active display 
Pd: sorry my english, but I larning yet.
From all your edits it seems you actually figured most of it out?

You have now flashed Resurrection Remix Marshmallow ROM. If you did that, then you unlocked your bootloader, installed TWRP, rooted and rebooted successfully!
I'm not sure exactly the steps you did, but for some reason
the TWRP-flashable boot animation and TWRP-flashable boot logos cannot be flashed in the same TWRP session. If you try to flash both in the same TWRP session, one will not flash and you will still have the logo or animation you were trying to replace. I provided two versions of boot logos -- either ADB or TWRP-flashable. You can either flash the boot logo via ADB and then boot animation via TWRP... OR you can flash the TWRP-flashable boot logo via TWRP, reboot to ROM, then go back into TWRP recovery, and then flash the TWRP-flashable boot animation in a separate session.
QUARK AMBIENT DISPLAY SETTINGS
For the active display, in CM-based ROMs it's called
"Ambient Display". Our CM dev @
Skrilax_CZ, put a lot of effort into coding it so it works with the the Quark (Moto Maxx/Moto Turbo/Droid Turbo) IR sensors very much like
Moto Display.
All the other ROMs, like Resurrection Remix, Bliss, etc use the same coding.
It's a
lock-screen notification system. You will not see any notifications if you display is not locked when it is off/dark/sleeping.
In Settings,
- First, you need to turn on Ambient Display.
- Then, you need to configure the actions of Ambient Display. For example, some want to see notifications when they wave their hands over the phone, some do not want that action.
Below are the Ambient Display settings screenshots I took when I was using CM12.1. I am now using Resurrection Remix Marshmallow, like you. The settings are either identical or very, very similar.
____________

_____________
2)
___________
3)
______________

______________
4)
In Lock Screen, you need to have some sort of of screen lock, even if it's just swipe/slide lock. Either swipe, pattern or PIN. You can't choose "none". I choose pattern, but it's up to you.
IF you choose swipe, you may accidentally unlock your phone if you keep it in your pocket. PIN or pattern is better, in my opinion.
In RR, these settings below are under "Security". In CM12.1 it was under "Lockscreen".
Also, helps if you have "Automatically Lock" and "Power Button Instantly Locks" Some people put a delay on those for some reason, and then Ambient Display isn't going to show you notifications on the dark screen because the Display isn't actually locked.
NOTE: After you turn on all the other options, sometimes it's best to then turn off Ambient Display, then turn it back on to make sure it recognizes the other settings you have enabled.