Database Info

[Bootloader] JZO54K Bootloader

Here is the bootloader in a zip that can be flashed over anything.
I recommend flashing this because it fixes the issue where you couldn't boot into recovery from the bootloader.
Download (Mediafire)
Download (Goo.im)
MD5: a8715642fcb0400579dde21b5e4cc673

yeah,finally!!!!
it's my fisrt need in absolute in all my device the fix of the reboot-to-recovery from bootloader's bug...many times away from pc i bootlooped the n7 by my tests,and i had to wait hours to came back home to connect to pc...very good by google!:laugh:
On another side,i think is abolsutely right flash this BL and continue using a 4.1.1 rom instead of new base...right?
EDIT Wow,is very light a bootloader for nexus 7...compared tol for example a gnex one..

Odd...doesn't fix the boot into recovery bug for me. At least with TWRP.

In the german android-hilfe forum someone soft bricked his N7 by flashing this (He got a bootloop and cannot Boot into the CWM anymore).
Can someone confirm that the zips are functional or not?

I downloaded from the meadifure link in his forum on rw, installed it through clockworkmod touch and haven't had any problems. Booting to recovery from the bootloader works fine for me.
Sent from my Nexus 7 using xda premium

Thanks for this, for some reason when I updated to 4.1.2 OTA using CWM everything went fine no errors but it didn't actually update my bootloader which is odd. So I was able to update it using the CWM zip provided. Thanks!

Thanks for this! Flashed without issues.
Skickat från min Nexus 7 via Tapatalk 2

How would this affect my ability to hide breaching my warranty? Would replacing the bootloader that was shipped with the device give me away, or does an OTA update flash the new one anyway?

z1gackly said:
How would this affect my ability to hide breaching my warranty? Would replacing the bootloader that was shipped with the device give me away, or does an OTA update flash the new one anyway?
Click to expand...
Click to collapse
Update is supposed to flash new one anyway
---------- Post added at 11:13 PM ---------- Previous post was at 11:00 PM ----------
Worked fine here, thanks a lot
TWRP and PA 2.1799

how do we flash this? i have cm10 running. Thanks in advance

this,in recovery cwm...or via fastboot if you found the .img,but this case is from cwm

sert00 said:
in recovery cwm of course.(or twrp)
Click to expand...
Click to collapse
Thanks i tried that and i ended up with boot loops. I managedto flash the grouper bootloader and booted up. What am i missing or doing wrong?

Worked great for me, thanks OP.

Thanks, worked for me on JRO03S ROM.
Sent from my Nexus 7

Thanks OP worked like a charm!!!
Sent from my Nexus 7 using XDA Premium HD app

Crazy4G1 said:
Thanks i tried that and i ended up with boot loops. I managedto flash the grouper bootloader and booted up. What am i missing or doing wrong?
Click to expand...
Click to collapse
Did you double-check the MD5 hash of the download to ensure it wasn't corrupted in the downloading process?

Ahh dang i got a bootloop, I can get into fastboot mode but recovery is a no go, any suggestions?

Same im stuck at google logo, cant get into recovery. Any ideas?

Pithism said:
Same im stuck at google logo, cant get into recovery. Any ideas?
Click to expand...
Click to collapse
I'm bout to factory reset with the nexus 7 toolkit, just for reference which link did you download from?
---------- Post added at 02:18 AM ---------- Previous post was at 01:51 AM ----------
Okay i was able to factory reset and got out of the bootloop. But I lost all my data(which is my fault for not making a backup to my pc). OP should really post the md5 so we can check it.

Dl'd via goo link, but used browser to access. Flashed via teamwin, wiped, profit. PA 2.14
sent secretly from my paranoid 7

[Q] ota sideloading aborted

Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance

drunken monkey said:
Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance
Click to expand...
Click to collapse
Are you rooted or having custom kernel?

kaushikd said:
Are you rooted or having custom kernel?
Click to expand...
Click to collapse
I'm currently running stock recovery, stock os rooted and unlocked bootloader

I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.

drunken monkey said:
I'm currently running stock recovery, stock os rooted and unlocked bootloader
Click to expand...
Click to collapse
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.

I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img

So while sideloading it should I unroot as well?

jsgraphicart said:
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.
Click to expand...
Click to collapse
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?

drunken monkey said:
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?
Click to expand...
Click to collapse
That correct
Sent from my Nexus 5 using XDA Free mobile app

pauleyc said:
I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img
Click to expand...
Click to collapse
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.

jrronimo said:
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.
Click to expand...
Click to collapse
It won't cause any data loss. It's about the only way to get the ota to work. But in your case, since you have twrp you should also flash the stock recovery.img
Sent from my Nexus 5 using XDA Free mobile app

No data loss (well, apart from root) if you flash just the radio, system and boot images. Worked great for me.

Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?

jrronimo said:
Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?
Click to expand...
Click to collapse
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Good thing I didn't get past this step -- I had downloaded the wrong factory image. D: That'll explain things a bit...
---------- Post added at 02:13 PM ---------- Previous post was at 01:54 PM ----------
Alrighty! New problem: After the phone boots, I get the battery and signal icons in the top right, but a black screen otherwise. If I hit the power button to put it in sleep mode and then hit the power button again, I get a quick flash of the "Welcome to Android, select your language" screen. Any pro-tips?
If I have to set up from scratch, it's no big deal. Most of the important stuff should be backed up; it'd just be annoying. All that Desert Golfing progress!!!
Finally managed to get around it. Ended up updating TWRP and re-flashing most of the .imgs a bunch, then using TWRP to first let me back up data to my computer and then wipe partitions. I'm on 5.0.1 again.
Welp, that was painful, haha. I'm sure I did something wrong leading into this, but I'm not sure what that was...

If i just flash the whole Firmware that i downloaded from Google, will i be able to flash it and loose root?
I am OK with loosing root and beeing back to stock.
At this moment i have Lolipop 5.0 that is rooted with Chainfire.

I was running rooted stock 5.0 with TWRP and had already flashed the 5.0.1 radio, so I just fastboot flashed the 5.0.1 system.img and rerooted. All is well so far.

jd1639 said:
That correct
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So if I unroot and then sideload it will I loose all my data ?
P.s I'll be rooting it back immediately after I get 5.1
So is there any way which can avoid a data loss?

I still have a doubt, I saw rootjunky's video in which he sideload 5.1 to his nexus 7 using nrt..
Even I followed the same method but it didn't succeed for me

pauleyc said:
I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.
Click to expand...
Click to collapse
So after flashing your stock kernal and stock recovery did the sideload work.. I mean that it didn't get stuck at the 61% mark?

[Q] clockworkmod recovery

I have a verizon galaxy S3 sch-i535 that I successfully rooted & unlocked to T-mobile have been using it for a while
with no issues until yesterday when I had to install a new T-Mobile sim card. I got the dreaded " The process com. android. phone has stopped" I cleared all the phone cache as was recommended. But when I boot into recovery mode it comes up with android recovery instead of clockwork mod recovery. which is what I have. I wanted to
clear the cache in that as well which was recommended. I can receive calls and text and can send text but I can't
make a phone call. Can someone help me please! Thanks

H779 said:
I have a verizon galaxy S3 sch-i535 that I successfully rooted & unlocked to T-mobile have been using it for a while
with no issues until yesterday when I had to install a new T-Mobile sim card. I got the dreaded " The process com. android. phone has stopped" I cleared all the phone cache as was recommended. But when I boot into recovery mode it comes up with android recovery instead of clockwork mod recovery. which is what I have. I wanted to
clear the cache in that as well which was recommended. I can receive calls and text and can send text but I can't
make a phone call. Can someone help me please! Thanks
Click to expand...
Click to collapse
You can re-flash your phone with the firmware of sammobile
You will lose root.

H779 said:
I have a verizon galaxy S3 sch-i535 that I successfully rooted & unlocked to T-mobile have been using it for a while
with no issues until yesterday when I had to install a new T-Mobile sim card. I got the dreaded " The process com. android. phone has stopped" I cleared all the phone cache as was recommended. But when I boot into recovery mode it comes up with android recovery instead of clockwork mod recovery. which is what I have. I wanted to
clear the cache in that as well which was recommended. I can receive calls and text and can send text but I can't
make a phone call. Can someone help me please! Thanks
Click to expand...
Click to collapse
Sounds like you may be on one of the locked bootloaders which is why a custom recovery won't work
Sent from my Nexus 5

ShapesBlue said:
Sounds like you may be on one of the locked bootloaders which is why a custom recovery won't work
Sent from my Nexus 5
Click to expand...
Click to collapse
Sorry I didn't get back sooner. working crazy hours. So is there and option here. I got this bootloader from this site. I think from chainfire.

H779 said:
I have a verizon galaxy S3 sch-i535 that I successfully rooted & unlocked to T-mobile have been using it for a while
with no issues until yesterday when I had to install a new T-Mobile sim card. I got the dreaded " The process com. android. phone has stopped" I cleared all the phone cache as was recommended. But when I boot into recovery mode it comes up with android recovery instead of clockwork mod recovery. which is what I have. I wanted to
clear the cache in that as well which was recommended. I can receive calls and text and can send text but I can't
make a phone call. Can someone help me please! Thanks
Click to expand...
Click to collapse
How to install a working custom recovery again:
Flash TWRP as "AP" using ODIN while phone is connected in "DOWNLOAD" mode.
I really appreciate your iron will to use a CDMA S3 with GSM service

LS.xD said:
How to install a working custom recovery again:
Flash TWRP as "AP" using ODIN while phone is connected in "DOWNLOAD" mode.
I really appreciate your iron will to use a CDMA S3 with GSM service
Click to expand...
Click to collapse
If he is on the locked bootloader flashing a custom recovery will brick his device. I understand your intentions are good but by doing so this will not help
Sent from my Nexus 5
---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------
H779 said:
Sorry I didn't get back sooner. working crazy hours. So is there and option here. I got this bootloader from this site. I think from chainfire.
Click to expand...
Click to collapse
Post a screen shot of your about phone screen, if its on the 4.3 ML1 or 4.4.2 NE1 bootloader you do not have the option of flashing a custom recovery other than safestrap
Sent from my Nexus 5

ShapesBlue said:
If he is on the locked bootloader flashing a custom recovery will brick his device. I understand your intentions are good but by doing so this will not help
Sent from my Nexus 5
---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------
Post a screen shot of your about phone screen, if its on the 4.3 ML1 or 4.4.2 NE1 bootloader you do not have the option of flashing a custom recovery other than safestrap
Sent from my Nexus 5
Click to expand...
Click to collapse
My bad. If you're still on Android 4.1.1 or Android 4.1.2 you can permanently unlock your bootloader. Which firmware is actually installed?

Thanks I don't know why this occurred just because I changed sims . I'm not that savey just persistent Btw your message only says flash TWRP usind AP in odin. the link is missing when I log in to XDA on my PC the link shows up only on my Gmail.

H779 said:
Thanks I don't know why this occurred just because I changed sims . I'm not that savey just persistent Btw your message only says flash TWRP usind AP in odin. the link is missing when I log in to XDA on my PC the link shows up only on my Gmail.
Click to expand...
Click to collapse
As posted previously:
Post a screen shot of your about phone screen, if its on the 4.3 ML1 or 4.4.2 NE1 bootloader you do not have the option of flashing a custom recovery other than safestrap
Sent from my Nexus 5

version 4.0.4, baseband I535VRLHE, build number IMM76DI535VRALHE

H779 said:
version 4.0.4, baseband I535VRLHE, build number IMM76DI535VRALHE
Click to expand...
Click to collapse
Wow, still on ICS. Might be because your on such an old bootloader
Sent from my Nexus 5

I guess I'm confused, When I originally Unlocked this verizon phone to use a T-Mobile sim I flashed a new bootloader about a week ago Does the original bootloader still exist and is flashed over? hope this isn't a stupid question.

H779 said:
version 4.0.4, baseband I535VRLHE, build number IMM76DI535VRALHE
Click to expand...
Click to collapse
Pretty good You can use EZ unlock 1.2 to unlock your bootloader and then install the TWRP I mentioned earlier
---------- Post added at 05:08 PM ---------- Previous post was at 05:01 PM ----------
H779 said:
I guess I'm confused, When I originally Unlocked this verizon phone to use a T-Mobile sim I flashed a new bootloader about a week ago Does the original bootloader still exist and is flashed over? hope this isn't a stupid question.
Click to expand...
Click to collapse
May you post a link to the "bootloader" you think you flashed earlier?

I deleteted it because I didn't think I needed any longer. I remember it being something like : vrzbootchain.tar thats all I remember

Lubeck can you please send me the TWRP link. All that came through was " Flash TWRP using AP in Odin Thanks

LS.xD said:
How to install a working custom recovery again:
Flash TWRP as "AP" using ODIN while phone is connected in "DOWNLOAD" mode.
I really appreciate your iron will to use a CDMA S3 with GSM service
Click to expand...
Click to collapse
Why? Link is working...
BUT I don't know what exactly you did with your bootloader, so I can't guarantee its compatible.

[OTA] Official Marshmallow build MCG24.251-5

WARNING: THIS HAS BRICKED PHONES! It is suspected that having an encrypted phone causes these bricks, but that has not been confirmed. If your data partition is encrypted, it is extra important that you perform a factory reset before taking this OTA. Doing this will remove the encryption.
WARNING: INSTALLING THIS ON A LOCKED BOOTLOADER WILL ELIMINATE ALL CHANCE OF YOU EVER UNLOCKING YOUR BOOTLOADER.
If your bootloader is unlocked, it will not be re-locked after this update.
Do NOT flash this using TWRP. If you want to do that, use this version: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
So if you're a bad enough dude to flash this anyway, follow these instructions:
1. Backup all data on your phone. It will be lost.
2. If your bootloader is locked, make sure you are on SU4TL-49. If you aren't, take all available OTAs until you are.
3. If your bootloader is unlocked and you have TWRP installed, flash SU4TL-49 using this package: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
4. If you have TWRP installed on your phone, download the stock SU4TL-49 recovery here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8 and install it using the install image option in the install menu in TWRP. Reboot to recovery.
3. Perform a factory reset using the stock recovery menu. This will wipe all data and ensure that everything is formatted exactly as it should be.
4. Boot the phone normally and place the marshmallow update on the root of the directory that pops up when you plug in your phone.
5. Boot to recovery and at the stock recovery menu, select "apply update from sdcard."
6. Select the update and cross your fingers.
Get the update here: https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8

TheSt33v said:
WARNING: THIS HAS BRICKED PHONES! Do not use this unless you know what you're doing.
I will do my best to provide more detailed instructions later today. Good luck.
https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
Click to expand...
Click to collapse
Are you sure that that file is the right one? It has the same version number as su4tl-49.

zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
I'm positive. I seem to remember they did the same thing with SU4TL-49. The OTA was named after SU4TL-44 for some reason.

This is the stock recovery version, correct?

koftheworld said:
This is the stock recovery version, correct?
Click to expand...
Click to collapse
Correct. You install this using the sideload option in the stock recovery.

TheSt33v said:
Correct. You install this using the sideload option in the stock recovery.
Click to expand...
Click to collapse
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.

Thank you, now we can see what can be done with the new modem, kernel, etc...
Looking forward to a plethora of improvements to our phones

koftheworld said:
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Click to expand...
Click to collapse
I'm testing the TWRP version now. It should be up shortly.
EDIT: I flashed it and it seems to work fine. Uploading now. Should be up in a few hours. I'll check on it after I go run some errands real quick.

Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.

Sweet. I am going to wait till it is more stable. I do have a bad esn Turbo but I will need to unlock to bootloader to test.

Mirror for people having "quota exceeded" error at Mega
https://yadi.sk/d/AhmhE-yX32E84p
Rename to Blur_Version.24.81.5.quark_verizon.verizon.en.US.zip before use, throw in internal storage, and check for updates.
PS: I have 64Gb Employee Edition, and still had not receive update by air. What a shame, VZ! )

kitcostantino said:
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Click to expand...
Click to collapse
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.

TheSt33v said:
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
Click to expand...
Click to collapse
Negative. Stock recovery on a system that reports "Official". I'm at a loss.

kitcostantino said:
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
Click to expand...
Click to collapse
Strange. Try reflashing SU4TL-49. If my TWRP package doesn't do it for you, use the full firmware package and do it manually with fastboot.

Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"

s5610 said:
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
Click to expand...
Click to collapse
lol. lawd, No. Ive been rocking status 3 for over a year.
As a tip, if anyone else with an unlocked bootloader runs into this,
what i had to do was restore my su-44 unmodified backup, OTA to SU-49, and then, after confirming my
q/e status was 0/1 i was able to update via the file in my Mega download folder. all is well now. they even added the newer version of command center. sweet. thank you all!!

It works in LOCKED BOOTLOADER??? .-.

square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Um, I couldn't tell you.i be been unlocked since the day Sunshine could unlocked our bootloader's. What I can tell you is you should absolutely unlock that via Sunshine before you even dream of applying this update. There will never be another opportunity.
Just my
.02. This is likely the last update for this phone, and your only chance of seeing N is via custom Roms.

TWRP version up now: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949

square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Yes it should. See instructions in OP.

[ROM] MCG24.251-5 100% Stock

Flash using TWRP. This will flash all files in the MCG24.251-5 update except for recovery.
New features in this update that I've noticed:
-Marshmallow, aged to perfection in Verizon's own servers. Only one major release version obsolete, and with outdated security patches!
-WiFi calling (woooooo! Those custom roms just got another carrier-specific, unportable feature to compete with)
-The command center widget has been replaced with the Droid Turbo 2 version
Get it here: https://mega.nz/#!G1xg1aYa!fm2hUL7hDDVaxTAj_iPbtY61P-8VrQEvoOJiVsDtdho
Here's the stock recovery image if you want it: https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
Flashing this rom updates the bootloader to a version that can communicate with the kernel to tell SafetyNet that it is unlocked, causing it to fail. Fret not, however, as there are two options to fix this:
OPTION 1: Flash the SU4TL-49 bootloader using the following TWRP package: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ
OPTION 2: Flash this patch made by @bhb27: https://www.androidfilehost.com/?fid=745425885120696423
Wipe cache and dalvik/art cache after either of these options.
NOTE that these options only fix failures due to SafetyNet checking the bootloader status. It will still fail due to root, xposed and the like. There are no known consequences or side effects to either of these options, so just pick whichever one you feel like.
If you notice weird things after you flash this rom (long boots other than the first one which is supposed to be long, random reboots, etc.) try flashing the stock recovery image and factory resetting.
If you want root, flash this version of SuperSU first, then flash whatever newer version you want: https://download.chainfire.eu/751/SuperSU/
If you have trouble flashing this, try TWRP Mod 3 instead of Mod 4.

Ouch, you have almost full flash inside archive, with bootloader too... Who is the most brave, introduce yourself ))
+ mirror

I can confirm that it works on old bootloader.
I had SULT-49 5.1 installed before and I just flashed this via TWRP. I haven't taken the OTA. It works perfectly. Thank you.
PS: My bootloader now is moto-apq8084-70.95 (2016-06-29). Do you have same version after taking OTA?

Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk

Thanks OP

rickyblaze13 said:
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
When in doubt, always wipe.

Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.

rickyblaze13 said:
have to wipe the system, data and cache first
Click to expand...
Click to collapse
It works w/o, but, IMO, better wipe, than not. You don't need extra bugs, right )

It's completing setup now, I did a wipe after I backed up my phone. It's unlocked and rooted before I flashed the zip
Sent from my QMV7A using Tapatalk

Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...

Crowick said:
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
Click to expand...
Click to collapse
My google drive is full and I don't have Dropbox. But if you wanted to mirror it, I will gladly add the link to the OP.

Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg

Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
thanks for gdrive mirror

Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
I don't. I don't know how I would get it since I need root access to get it, and I can't get root access without TWRP, and I have to overwrite the stock recovery to get TWRP.

TheSt33v said:
I have to overwrite the stock recovery to get TWRP.
Click to expand...
Click to collapse
fastboot boot TWRP.img

s5610 said:
fastboot boot TWRP.img
Click to expand...
Click to collapse
Nice! Good call.
https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8

Is anyone else having exceptionally long reboot/start times for their phone after flashing this rom?

Just the first boot after flashing
Sent from my XT1254 using Tapatalk

Thanks for that! Did anybody try to install it right over SU4TL-44? Just in case, I'm rooted, using xposed and twrp.

TheSt33v said:
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
Click to expand...
Click to collapse
Perhaps this:
https://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
I just tried using AP a few hours ago and it failed with the screen in the article. OTA with unlocked bootloader.