Database Info

[Q] Having trouble flashing roms to my M8

I unlocked the bootloader, did s-off and rooted through weaksauce. However when I try to install a zip file from my SD card in the bootloader, it always ends up aborting the installation, I tried clearing the cache and even wiping all the data but it still doesn't install. I tried two different roms and I get the same problems which makes me think that I am missing something with the phone. Does anyone have any idea what the holdup may be?

Harpuajim said:
I unlocked the bootloader, did s-off and rooted through weaksauce. However when I try to install a zip file from my SD card in the bootloader, it always ends up aborting the installation, I tried clearing the cache and even wiping all the data but it still doesn't install. I tried two different roms and I get the same problems which makes me think that I am missing something with the phone. Does anyone have any idea what the holdup may be?
Click to expand...
Click to collapse
Not sure but your downloads could be having errors, mem card has issues or worse, your recovery is fault!!!

mashk said:
Not sure but your downloads could be having errors, mem card has issues or worse, your recovery is fault!!!
Click to expand...
Click to collapse
I'll try it with the phone storage or a different SD card later tonight. I'll also try a different ROM. When you say my recovery is fault what exactly do you mean? Is this something that can be fixed?

Harpuajim said:
I'll try it with the phone storage or a different SD card later tonight. I'll also try a different ROM. When you say my recovery is fault what exactly do you mean? Is this something that can be fixed?
Click to expand...
Click to collapse
What recovery are you using? I use CWM and works fine for me.

Harpuajim said:
I unlocked the bootloader, did s-off and rooted through weaksauce. However when I try to install a zip file from my SD card in the bootloader, it always ends up aborting the installation, I tried clearing the cache and even wiping all the data but it still doesn't install. I tried two different roms and I get the same problems which makes me think that I am missing something with the phone. Does anyone have any idea what the holdup may be?
Click to expand...
Click to collapse
Take a look in this section at the thread I started. See if you can flash Skyfall or any AOSP ROM I'm able to flash those fine but all of the GPE ROMS and a couple others will not flash for me either. All AOSP and AOKP stuff flashes fine. Skyfall and ViperOne will flash for me. I dont know what the hell is going on.

Did you flash SuperSU zip to get permanent root and get rid of weak sauce after you soffd and flashed your recovery?

silver04v said:
Did you flash SuperSU zip to get permanent root and get rid of weak sauce after you soffd and flashed your recovery?
Click to expand...
Click to collapse
You know what? I'll bet that's whats happening to me. I have a thread in this section with the same deal. Mine has been Rooted and UL/S-Off for a while now but during the rooting, UL/s-off process (Introductions and videos) not once was this ever mentioned. I lost root on an install of Nu Sense today but the entire install was wonky so I just thought it was that. Where can I find this SuperSU zip and how do I get rid of weaksauce? I used Firewater and weaksauce on mine. Or are you saying that once you flash the zip it takes over what weaksauce was doing?
I wonder why so many ROMs flashed properly for months now and it's just recently with these GPE Roms I'm seeing all this trouble.
---------- Post added at 07:14 PM ---------- Previous post was at 06:57 PM ----------
silver04v said:
Did you flash SuperSU zip to get permanent root and get rid of weak sauce after you soffd and flashed your recovery?
Click to expand...
Click to collapse
Well, I found it and flashed it so I guess we'll see if that was the problem. Got it off of Chainfires site.

Duckman_UF said:
You know what? I'll bet that's whats happening to me. I have a thread in this section with the same deal. Mine has been Rooted and UL/S-Off for a while now but during the rooting, UL/s-off process (Introductions and videos) not once was this ever mentioned. I lost root on an install of Nu Sense today but the entire install was wonky so I just thought it was that. Where can I find this SuperSU zip and how do I get rid of weaksauce? I used Firewater and weaksauce on mine. Or are you saying that once you flash the zip it takes over what weaksauce was doing?
I wonder why so many ROMs flashed properly for months now and it's just recently with these GPE Roms I'm seeing all this trouble.
---------- Post added at 07:14 PM ---------- Previous post was at 06:57 PM ----------
Well, I found it and flashed it so I guess we'll see if that was the problem. Got it off of Chainfires site.
Click to expand...
Click to collapse
Yeah, get rid of weak sauce app and flash SuperSU zip. Let me know if that fixes your problem. That would be an easy fix!

silver04v said:
Yeah, get rid of weak sauce app and flash SuperSU zip. Let me know if that fixes your problem. That would be an easy fix!
Click to expand...
Click to collapse
I dont have a weaksauce app???? I used a weaksause zip with ADB when rooting the device??

Duckman_UF said:
I dont have a weaksauce app???? I used a weaksause zip with ADB when rooting the device??
Click to expand...
Click to collapse
Oh, never mind then..I used the app way when I did mine. Let's see if you can flash a rom now! Haha

silver04v said:
Oh, never mind then..I used the app way when I did mine. Let's see if you can flash a rom now! Haha
Click to expand...
Click to collapse
lol....BRB!
---------- Post added at 07:38 PM ---------- Previous post was at 07:30 PM ----------
Duckman_UF said:
lol....BRB!
Click to expand...
Click to collapse
Nope...no such luck. One thing I forgot about is all these ROM's Root the device just before installing the kernal. Mines doung the same thing it always does on this one and Cleanrom....stck on "Trimming File system"....It will fail eventually.

Duckman_UF said:
lol....BRB!
---------- Post added at 07:38 PM ---------- Previous post was at 07:30 PM ----------
Nope...no such luck. One thing I forgot about is all these ROM's Root the device just before installing the kernal. Mines doung the same thing it always does on this one and Cleanrom....stck on "Trimming File system"....It will fail eventually.
Click to expand...
Click to collapse
Hmm.. That's true. So you can't even flash clean rom? Can you get anything flashed? Maybe try and fastboot flash twrp again. Or a different version of twrp than you have now?

silver04v said:
Hmm.. That's true. So you can't even flash clean rom? Can you get anything flashed? Maybe try and fastboot flash twrp again. Or a different version of twrp than you have now?
Click to expand...
Click to collapse
Take a look at my thread in this section and you'll see what ive been through
---------- Post added at 08:07 PM ---------- Previous post was at 08:02 PM ----------
Duckman_UF said:
Take a look at my thread in this section and you'll see what ive been through
Click to expand...
Click to collapse
It's weird. I have Nu Sense up and running but Ive lost Root again just as I did earlier today but everything that doesnt need Root is working. When this happens I never get an "Install complete" it just hangs on Trimming system files then eventually shuts off. I cant seem to get the binaries installed for SuperSU either.

Duckman_UF said:
Take a look at my thread in this section and you'll see what ive been through
---------- Post added at 08:07 PM ---------- Previous post was at 08:02 PM ----------
It's weird. I have Nu Sense up and running but Ive lost Root again just as I did earlier today but everything that doesnt need Root is working. When this happens I never get an "Install complete" it just hangs on Trimming system files then eventually shuts off. I cant seem to get the binaries installed for SuperSU either.
Click to expand...
Click to collapse
Flash the SuperSU.zip via recovery and you'll have root again!
Sent from my HTC One_M8 using XDA Premium 4 mobile app

mashk said:
Flash the SuperSU.zip via recovery and you'll have root again!
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately not, install is corrupt.....You would have to read my entire thread to get an idea of all the BS i have going on lol! I'm sticking with AOSP right now until I figure out what's going on.

Duckman_UF said:
Unfortunately not, install is corrupt.....You would have to read my entire thread to get an idea of all the BS i have going on lol! I'm sticking with AOSP right now until I figure out what's going on.
Click to expand...
Click to collapse
Link?

mashk said:
Link?
Click to expand...
Click to collapse
One post up lol!
http://forum.xda-developers.com/verizon-htc-one-m8/help/flashing-problems-t2834991

Block OTA Updates

I am S-off and rooted on Verizon. What file or files do I have to freeze via TBU to not get the soon to be released update ?
Thanks in advance

jjmstang said:
I am S-off and rooted on Verizon. What file or files do I have to freeze via TBU to not get the soon to be released update ?
Thanks in advance
Click to expand...
Click to collapse
delete or rename from .apk to .bak
system/app
HtcOMADM_SettingsPlugin_VZW.apk
HtcOMADM_VZW.apk

jjmstang said:
I am S-off and rooted on Verizon. What file or files do I have to freeze via TBU to not get the soon to be released update ?
Thanks in advance
Click to expand...
Click to collapse
A custom recovery like CWM or TWRP should also cause the update to fail.

Okay thanks for the quick responses

Figured I'd add on to these answers.
Modifying anything will pretty much mess up the OTA's. As far as I know if everything is not 100% stock (besides S-OFF & bootloader unlock) then the update will fail.
Root your phone = failed update
Custom recovery = failed update
Edit a file in /system (add a line or remove a line or change 0 to 1 in something) = failed update
Etc

Can't you just freeze the Updater 6. whatever with titanium?

Mudvayne622 said:
Can't you just freeze the Updater 6. whatever with titanium?
Click to expand...
Click to collapse
Yes, that will prevent a nag, but it would still allow you to manually update it in settings.
I'd follow what Andy said, then it's for sure unable to update
Sent from my HTC6525LVW using Tapatalk
---------- Post added at 04:13 PM ---------- Previous post was at 04:07 PM ----------
S1L3nTShaDoWz said:
Figured I'd add on to these answers.
Modifying anything will pretty much mess up the OTA's. As far as I know if everything is not 100% stock (besides S-OFF & bootloader unlock) then the update will fail.
Root your phone = failed update
Custom recovery = failed update
Edit a file in /system (add a line or remove a line or change 0 to 1 in something) = failed update
Etc
Click to expand...
Click to collapse
This is mostly true, but sometimes the overall update will fail but bits and pieces of it will actually pass. This is exactly what you don't want.
For example, a new bootloader would pass, but the system and the recovery push would fail. This could potentially lock your bootloader. It's still better to stop the update without giving it a chance to install, despite having root and a custom recovery.
Sent from my HTC6525LVW using Tapatalk

Dougau said:
A custom recovery like CWM or TWRP should also cause the update to fail.
Click to expand...
Click to collapse
It will cause it not to install, but won't stop the nag to install the OTA.

Can't you stop it by going into About/software update and unchecking auto download?

Thanks I wasn't sure. This is my first HTC (former Motorola fan). Even once the developers get ahold of the update and create a flashable zip for us do we still need to put the stock recovery back or flash the update.zip in custom recovery? I'm S-Off, BL unlocked and rooted with TWRP.
---------- Post added at 08:06 PM ---------- Previous post was at 08:01 PM ----------
OdinValknir said:
Can't you stop it by going into About/software update and unchecking auto download?
Click to expand...
Click to collapse
Once I saw this I was curious about that option. But every time I go into About/Software Update, settings crashes. Maybe due to Sense 6 Toolbox in my settings menu?

I'm not 100% sure... I am actually curious about all this too... This phone is the first and only phone I've ever unlocked/rooted/ S-off etc.... I'm currently running Venom Viper ONE ROM on Here and have neglected to flash the most current version bc it's based on 4.3
I'm still waiting to see how it all pans out... And clueless as to how to update kitkat once it does come through... Whether I can do it manually... Or if I have to go back to stock sense 6 so on and so forth... Guess we shall see

OdinValknir said:
I'm not 100% sure... I am actually curious about all this too... This phone is the first and only phone I've ever unlocked/rooted/ S-off etc.... I'm currently running Venom Viper ONE ROM on Here and have neglected to flash the most current version bc it's based on 4.3
I'm still waiting to see how it all pans out... And clueless as to how to update kitkat once it does come through... Whether I can do it manually... Or if I have to go back to stock sense 6 so on and so forth... Guess we shall see
Click to expand...
Click to collapse
You can do it manually through fastboot, all you're going to want to update is the firmware.
Sent from my HTC6525LVW using Tapatalk

BadUsername said:
You can do it manually through fastboot, all you're going to want to update is the firmware.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Through fastboot? I have never seen an option for firmware or update in fastboot... Again.. forgive me I am still relatively new to all this

OdinValknir said:
Through fastboot? I have never seen an option for firmware or update in fastboot... Again.. forgive me I am still relatively new to all this
Click to expand...
Click to collapse
It's not going to update the rom, but it'll update your baseband and other firmware, you can package it in a flashable zip and flash it in a custom recovery or with the fastboot flash command.
Sent from my HTC6525LVW using Tapatalk

andybones said:
delete or rename from .apk to .bak
system/app
HtcOMADM_SettingsPlugin_VZW.apk
HtcOMADM_VZW.apk
Click to expand...
Click to collapse
Will renaming the files with ES File Explorer work instead of TBU. I had to schedule the update for later this evening, hoping that I can rename with ES and be done with it.

GarnerArms said:
Will renaming the files with ES File Explorer work instead of TBU. I had to schedule the update for later this evening, hoping that I can rename with ES and be done with it.
Click to expand...
Click to collapse
Yessir, just rename to .bak rather than .apk

Awesome. Do I need to rename both or just the setting plug-in?
Sent from my HTC6525LVW using XDA Free mobile app

BadUsername said:
Yes, that will prevent a nag, but it would still allow you to manually update it in settings.
I'd follow what Andy said, then it's for sure unable to update
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
FYI: I froze the updater w/ TBU and the nag continued to....nag. I renamed the APK files and so far so good.

andybones said:
Yessir, just rename to .bak rather than .apk
Click to expand...
Click to collapse
Andy, good to see you on here with the M8
I had the G3 for a couple weeks...it was ok I guess, but I already have a tablet. Ha, needed to be able to hold my phone with one hand. G3 is overrated!
I'm about to root and I'll be sure to try out any ROMs you have made for the M8!!

S1L3nTShaDoWz said:
Figured I'd add on to these answers.
Modifying anything will pretty much mess up the OTA's. As far as I know if everything is not 100% stock (besides S-OFF & bootloader unlock) then the update will fail.
Root your phone = failed update
Custom recovery = failed update
Edit a file in /system (add a line or remove a line or change 0 to 1 in something) = failed update
Etc
Click to expand...
Click to collapse
I was rooted with weaksauce and it pestered me with the update relentlessly. Every time I turned on the phone I had to click a bunch of junk to get rid of it. Unfortunately I did not realize this was a full OS update, it just mentioned updating to the fancy charging thing and clicked "yes" to be rid of the annoyance. As soon as I clicked it my phone rebooted and I knew I was in trouble. Lost root and can't get it back without paying for sunshine. I'm poor!

LG G Stylo [H631] Root help

Ive had this phone since January, I had rooted it and flash the Unofficial CM12.1. A couple months ago I reflashed the stock ROM, MM, I didnt realize I lost the root and TWRP, I need help re-rooting because I do not remember hot to

thejegjeg said:
Ive had this phone since January, I had rooted it and flash the Unofficial CM12.1. A couple months ago I reflashed the stock ROM, MM, I didnt realize I lost the root and TWRP, I need help re-rooting because I do not remember hot to
Click to expand...
Click to collapse
Are you still looking for a root method?
Sent from my LG-H631 using XDA-Developers mobile app

CollisionFactor said:
Are you still looking for a root method?
i am! im on the tmobile variant of the h631 on marshmallow. got the boot loader unlocked wont go any further. get this far using adb.... but for some reason i cant reboot into recovery . king root doesnt work... supersu just sits sit there and one touch says maybe at first but does nothing . im usually really good at reading the boards for the info i need but this just isnt working. come in yall H.B.O (Helpa Brotha Out).
Click to expand...
Click to collapse

Dan-T-man10 said:
CollisionFactor said:
Are you still looking for a root method?
i am! im on the tmobile variant of the h631 on marshmallow. got the boot loader unlocked wont go any further. get this far using adb.... but for some reason i cant reboot into recovery . king root doesnt work... supersu just sits sit there and one touch says maybe at first but does nothing . im usually really good at reading the boards for the info i need but this just isnt working. come in yall H.B.O (Helpa Brotha Out).
Click to expand...
Click to collapse
What I was able to do was use an older version of Kingroot, i think it was 4.6.5 or something like that. It took me a few tries with the app until it finally rooted. Then I downloaded flashify from the play store and flashed TWRP. Booted into recovery and installed superSU to replace Kingroot.
If that version doesnt work, keep searching/using different versions to see if any of them work and let me know what worked. I had to kdz back to stock and stupidly took the update to 20c and am now trying to re-root mine.
BTW if your phone isnt rooted you wont be able to boot to recovery until you root and flash TWRP image
Sent from LG H63120c
Click to expand...
Click to collapse

CollisionFactor said:
Dan-T-man10 said:
What I was able to do was use an older version of Kingroot, i think it was 4.6.5 or something like that. It took me a few tries with the app until it finally rooted. Then I downloaded flashify from the play store and flashed TWRP. Booted into recovery and installed superSU to replace Kingroot.
If that version doesnt work, keep searching/using different versions to see if any of them work and let me know what worked. I had to kdz back to stock and stupidly took the update to 20c and am now trying to re-root mine.
BTW if your phone isnt rooted you wont be able to boot to recovery until you root and flash TWRP image
Sent from LG H63120c
Click to expand...
Click to collapse
Ive tried from Kingroot 4.6.5 all the way to 4.5.0 and still no luck with root :/
Click to expand...
Click to collapse

thejegjeg said:
CollisionFactor said:
Ive tried from Kingroot 4.6.5 all the way to 4.5.0 and still no luck with root :/
Click to expand...
Click to collapse
Same here. Am still trying to find a fix. Once I find one I will post it up. Think I am going to look at superSU to find one that will work.
Sent from LG H63120c
---------- Post added at 02:56 AM ---------- Previous post was at 02:31 AM ----------
thejegjeg said:
CollisionFactor said:
Ive tried from Kingroot 4.6.5 all the way to 4.5.0 and still no luck with root :/
Click to expand...
Click to collapse
Ok I was able to re-root. Follow these simple steps below:
Find and download superSU 2.76 zip
Reboot to fastboot via adb
Boot TWRP image via fastboot
Once in recovery, select install
Locate superSU.zip and install
Once completed, reboot system
Verify root via root checker app
So far so good. No force closes or bootloops yet.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Bump

CollisionFactor said:
thejegjeg said:
Same here. Am still trying to find a fix. Once I find one I will post it up. Think I am going to look at superSU to find one that will work.
Sent from LG H63120c
---------- Post added at 02:56 AM ---------- Previous post was at 02:31 AM ----------
thejegjeg said:
Ok I was able to re-root. Follow these simple steps below:
Find and download superSU 2.76 zip
Reboot to fastboot via adb
Boot TWRP image via fastboot
Once in recovery, select install
Locate superSU.zip and install
Once completed, reboot system
Verify root via root checker app
So far so good. No force closes or bootloops yet.
Click to expand...
Click to collapse
My computer, Windows 10, doesn't like ADB and Fastboot for some reason. I will make a VM of Windows 7 to try this method on.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

It keeps saying its offline in the CMD prompt

thejegjeg said:
It keeps saying its offline in the CMD prompt
Click to expand...
Click to collapse
What is offline?
Sent from my LG-H631 using XDA-Developers mobile app

By chance does anyone have a stock recovery.img?
Sent from my LG-H631 using XDA-Developers mobile app

CollisionFactor said:
What is offline?
Sent from my LG-H631 using XDA-Developers mobile app
Click to expand...
Click to collapse
when i type "ADB Devices" it comes up with the serial number of my Stylo and says 'Offline'

What is ur carrier and where did u purchase the phone? I have heard of other having issues like this.

thejegjeg said:
when i type "ADB Devices" it comes up with the serial number of my Stylo and says 'Offline'
Click to expand...
Click to collapse
Is it seeing your Stylo at all?
I had a similar problem and had to change usb cords and then it finally worked.

[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.

[Q] How to back-up stock firmware?

Here's a stupid question(s). How do we backup the stock firmware, and are the fastboot commands for ADB?
---------- Post added at 02:00 PM ---------- Previous post was at 01:41 PM ----------
Is this systemless root?

Darkscan said:
Here's a stupid question(s). How do we backup the stock firmware, and are the fastboot commands for ADB?
---------- Post added at 02:00 PM ---------- Previous post was at 01:41 PM ----------
Is this systemless root?
Click to expand...
Click to collapse
Adb = Android debug bridge and is used when the phone is booted into the OS and connected to a PC
Fastboot = when the phone is booted into the bootloader and is connected to a PC
Yes it is systemless root
You can backup stock firmware with twrp RC1
Sent from my Pixel using Tapatalk

joetheshmo said:
Adb = Android debug bridge and is used when the phone is booted into the OS and connected to a PC
Fastboot = when the phone is booted into the bootloader and is connected to a PC
Yes it is systemless root
You can backup stock firmware with twrp RC1
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Why is the current version for TWRP and the previous not? Is the bootloader download mode?

Darkscan said:
Why is the current version for TWRP and the previous not? Is the bootloader download mode?
Click to expand...
Click to collapse
Current version of root for twrp and the previous not? If that's what you're asking SuperSU was developed before a working twrp was released so we had to use the boot-to-root.img
I guess bootloader mode could be considered download mode but I've never heard it called that.
Sent from my Pixel using Tapatalk

joetheshmo said:
Current version of root for twrp and the previous not? If that's what you're asking SuperSU was developed before a working twrp was released so we had to use the boot-to-root.img
I guess bootloader mode could be considered download mode but I've never heard it called that.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I come from using only Samsung devices, I'm not sure what carries over and what doesn't. The extent of my experience is loading a ROM with download mode and flashing it with recovery. Speaking of which, why does the stock recovery just say no command when I try to launch it from fastboot?

Darkscan said:
I come from using only Samsung devices, I'm not sure what carries over and what doesn't. The extent of my experience is loading a ROM with download mode and flashing it with recovery. Speaking of which, why does the stock recovery just say no command when I try to launch it from fastboot?
Click to expand...
Click to collapse
Because you have to hit power button and volume up at the same time to get the commands to show up now
Sent from my Pixel using Tapatalk

joetheshmo said:
Because you have to hit power button and volume up at the same time to get the commands to show up now
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Well that's silly.

Darkscan said:
Here's a stupid question(s). How do we backup the stock firmware, and are the fastboot commands for ADB?
Click to expand...
Click to collapse
Why would you need to back-up the stock firmware? It is available here: https://developers.google.com/android/images

efrant said:
Why would you need to back-up the stock firmware? It is available here: https://developers.google.com/android/images
Click to expand...
Click to collapse
I suppose "where can we download the stock image" was the real question. Thanks.
Should I flash to stock first? I don't see why it would matter. All I've done is update Android and install a couple apps.

Darkscan said:
I suppose "where can we download the stock image" was the real question. Thanks.
Should I flash to stock first? I don't see why it would matter. All I've done is update Android and install a couple apps.
Click to expand...
Click to collapse
No need.

Would this be an acceptable way for me to downgrade my version? I am currently 100% stock and would like to downgrade so I can root, install TWRP, and start flashing custom ROMs.

This thread is like the twilight zone.

chadhoard said:
Would this be an acceptable way for me to downgrade my version? I am currently 100% stock and would like to downgrade so I can root, install TWRP, and start flashing custom ROMs.
Click to expand...
Click to collapse
Verizon phone? If you are on 7.1.1 you are done.
Google phone? You don't need to downgrade to do any of that.