Downgraded from 5.0.2 to 4.4.4, want 5.0.2 back topic

I had Lollipop and after doing a reset, it was stuck on boot animation. I have successfully downgraded to stock 4.4.4 using fastboot and I didn't flash gpt.bin, motoboot.img and logo.bin while doing so.

Now I want Lollipop again but I don't know what should I do-- whether to simply place the OTA on SD card and get it detected or flashing the TWRP-flashable LP zip? I wonder if following the native OTA method will brick the phone, I'm scared.

Please help :(

[Q] N910C Downgraded from 5.0.1 to 4.4.4 topic

Hi i have downgraded my note 4 N910C from 5.0.1 to 4.4.4 sucessfully but my original CSC is XME malaysia i flashed the official kitkat malaysia ROM but it shows THL thailand version installed help me!!!!kies shows XME but in phone info app shows THL...help

Just downgraded. (Accidentally). Now I have some questions topic

This is NOT a how-to or anything. Don't try to follow in my footsteps of stupidity and brick your phone.

That being said...

XT 1060 (Verizon)

I have been running 4.4.4 for quite a while now. Right after JCase released sunshine for our phones. (I have an unlocked bootloader.)

I had it rooted, and tried out the 5.0 ROMs a while ago. Flashed back to stock to wait for the update when we heard it was coming "very soon". But tonight I got impatient and decided I was going to re-root and switch back to CM12. So, I opened Moto X Toolkit (love that tool) and installed TWRP. When I manually rebooted I forgot to boot into recovery. Don't know if that had anything to do with the ensuing problems or not, but after that, I couldn't get it to boot into recovery.

So, I flashed back to stock 4.4.4 again. Tried rebooting into stock recovery... no joy.
So off I go again... one more attempt to flash stock 4.4.4. This time, when it asked me if I wanted to reboot into bootloader or android, I tried to boot into android. Sadly I missed the "a" and typed "ndroid". The toolkit began doing something... looks like it was running the flash all over again. I let it do its thing, then very carefully typed "android" so I wouldnt screw it up again.

It rebooted perfectly, but once it was up and running, I noticed all of my icons were blue. I quickly jumped into the "about phone section and noticed it said "4.2.2".

This is not supposed to be possible, so at this point I was half panicking and half curious... so I decided to do an even more stupid thing and accept the updates.

I am now updated completely to 4.4.4. Zero issues... recovery works fine, radio is fine, wifi and BT are fine.


This leads me to two questions (Directed to developers)...

1) Is there a possibility this is repeatable?

2) My curiosity is about to get me into trouble... I have two more Moto X's that are 4.4.4. Locked BL. I would like to know what the worst case scenario is. I know there is a possibility of "bricking", but that term has not, for a long time, meant what it originally did. How badly "bricked" might it be? Bootloops? Chance of recovering by flashing stock firmware or RSD? Or truly bricked?