Database Users

TWRP prevents Marshmallow?

I may be doing something stupid, but I've tried various options...
I had an original 5.1.1 build that I let OTA to 6.0. Everything was working fine. I wanted to root, so I installed TWRP... and then the machine wouldn't reboot; it stuck at the "powered by Android" screen and never went into the standard animation screens. I could reboot into TWRP recovery easily enough and using that I could see the filesystem data, but the OS wouldn't boot.
So I reflashed back to 5.1.1 (using http://www.andromods.com/download-files/xt1575-stock-firmware-moto-x-2015-pure-edition.html ), let that OTA to 6.0, installed TWRP... same result.
Third attempt; started at 5.1.1 then installed TWRP (which worked) and then did OTA to 6.0... but this went into a reboot loop.
(Of course during all this I've lost my configs, but I can rebuild that)
Has anyone been able to install TWRP onto an X-Pure 2015 that's running 6.0 ?

What TWRP version are you installing? Make sure it's 2.8.7.1 https://dl.twrp.me/clark/
Sent from my XT1575 using Tapatalk

Sorry, yes, I should have mentioned that; twrp-2.8.7.1-clark.img

Did you install TWRP as read only? I did this and now system recovery is overwriting TWRP and I have no idea how to get out of it.

I had the same problem a couple days ago and posted about it in the 'Android 6.0 Update rolling out! Pure Edition' thread:
"I keep running into a problem after doing the MM update when I flash TWRP (either 2.8.7.0 or 2.8.7.1) where it won't boot into system, just sits there where the animation part should start. Booted/rebooted fine a few times after finishing the MM update, even after flashing the unlocked bootloader logo fix, but as soon as I flash recovery it won't boot system. "
Tried it several times with both TWRP 2.8.7.0 and 2.8.7.1 with no success. Also tried sideloading the OTA per the manual steps in this thread but still couldn't boot to system. Only by already having TWRP installed on 5.1.1 am I able to flash a custom 6.0 ROM successfully. Haven't seen a really clear statement yet that someone has flashed TWRP on fully stock MM with no problem..

EVR_PR said:
Did you install TWRP as read only? I did this and now system recovery is overwriting TWRP and I have no idea how to get out of it.
Click to expand...
Click to collapse
First time I let /system be read-write and second time I let /system be RO. However this likely isn't related to recovery overwriting TWRP; it's documented that on first boot the OS may rewrite the recovery data meaning you'd need to install TWRP again.

Dahenjo said:
I had the same problem a couple days ago and posted about it in the 'Android 6.0 Update rolling out! Pure Edition' thread
...
Haven't seen a really clear statement yet that someone has flashed TWRP on fully stock MM with no problem..
Click to expand...
Click to collapse
Thanks; at least I know it's not me being stupid then (or if I am, then I'm not alone ).

sweh said:
First time I let /system be read-write and second time I let /system be RO. However this likely isn't related to recovery overwriting TWRP; it's documented that on first boot the OS may rewrite the recovery data meaning you'd need to install TWRP again.
Click to expand...
Click to collapse
I have flashed TWRP twice and even rebooted to recovery from recovery and system recovery still overwrites TWRP after booting to system.
Only way I can access TWRP is either flashing it or booting into from the fastboot folder using the fastboot boot command.
Doesn't matter what I do, the option for changing TWRP from read-write to read only doesn't show up anymore.

sweh said:
Thanks; at least I know it's not me being stupid then (or if I am, then I'm not alone ).
Click to expand...
Click to collapse
Well, at age 65 I do put my socks on backwards sometimes..... :silly:

Read on a fairly-detailed post that using adb to flash recovery and rebooting into it should actually work fine!
Could anyone confirm? Is it even possible?
P.S. I'm on XT1572 Indian stock 6.0, and very eager for twrp

I had the exact same problem. I used adb. Stuck on loading screen and then suddenly black. Not able to boot the phone. I'd like to make a nandroid and after that I'd like to use systemless root. If I'm correct, I'll still receive ota's while using systemless root.

Same for me. Returned to stock EU 5.1.1, got update, installed it. Later unlocked bootloader and installed latest TWRP. And now I am stuck on booting up image.
So stock Marshmallow cant be used with TWRP?

BooBzi said:
Same for me. Returned to stock EU 5.1.1, got update, installed it. Later unlocked bootloader and installed latest TWRP. And now I am stuck on booting up image.
So stock Marshmallow cant be used with TWRP?
Click to expand...
Click to collapse
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.

Dahenjo said:
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Click to expand...
Click to collapse
Thanks for reply, I did listen to you and post on TWRP thread.

Dahenjo said:
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Click to expand...
Click to collapse
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.

ccic2491 said:
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
Click to expand...
Click to collapse
Hello, is it possible to get step by step tutorial?
Later will try on Style with stock MM.
Thanks!

ccic2491 said:
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
Click to expand...
Click to collapse
Did you not use the Fastboot Install Method on the TWRP site? We are unable to reboot back into system after using this on stock MM, which always worked fine on stock LP. If you used a different method that worked could you please share what that was?

I am using twrp 2.8.7.1 on my Moto X Style XT1572 Asia retail without any trouble for past two weeks.
I normally flashed it using the fastboot and never ran into trouble.

gulshanstrider said:
I am using twrp 2.8.7.1 on my Moto X Style XT1572 Asia retail without any trouble for past two weeks.
I normally flashed it using the fastboot and never ran into trouble.
Click to expand...
Click to collapse
Just to confirm - when you flashed TWRP you were completely stock after installing the 6.0 OTA (not still on 5.1.1 before taking the OTA), correct?

Dahenjo said:
Just to confirm - when you flashed TWRP you were completely stock after installing the 6.0 OTA (not still on 5.1.1 before taking the OTA), correct?
Click to expand...
Click to collapse
Here is what I did:-
1) I was in Stock 5.1.1 (had unlocked bootloader)
2) I took the OTA.
3) Flashed the twrp 2.8.7.1 using fastboot
So yes I was completely stock 6.0 when I flashed the TWRP for MM

New July images posted

Two again - MMB30K & MOB30O. I have no idea what the difference is, but I've used MOB30O successfully.
Link to the Nexus 6 OTA page with instructions for sideloading (no data loss, need to reinstall TWRP & reroot):
https://developers.google.com/android/nexus/ota
For those people who prefer to install separate components:
MMB30K
MOB30O

dahawthorne said:
Two again - MMB30K & MOB30O.
Click to expand...
Click to collapse
Did anyone ever figure out what the difference was? Google did this last time, and the result seemed the same between the two.

I went with MOB30M last time and it worked fine, so I'm going with MOB30O.

@dahawthorne added the links on the first post for you..

Thanks. I should have included the links, but I reckoned that anyone who's interested knows where to find them, and anyone who doesn't know probably shouldn't be tinkering...
But yes, the pointer is appreciated.
Edit: I used the OTA at this link - simpler, and doesn't lose your data:
https://developers.google.com/android/nexus/ota#shamu
Instructions are on the page. A simple sideload, flash recovery, install SuperSU.

Sir , is there any difference between MMB30K and MOB30O versions?

marcus droid said:
Sir , is there any difference between MMB30K and MOB30O versions?
Click to expand...
Click to collapse
we have to wait for the AOSP change logs on that

Encrytable boot/kernel IMGs:
MOB30O:
https://www.androidfilehost.com/?fid=24572369242688110
MMB30K:
https://www.androidfilehost.com/?fid=24572369242688111

What was the difference between the last 2 images? That was released without explanation as well!

I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.

Strange. I sideloaded the MOB30O OTA, flashed TWRP (twice - it didn't stick first time) then installed SuperSU 2.76 from TWRP. No problems at all so far.

ayang02 said:
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Click to expand...
Click to collapse
I flashed SuperSU 2.76 just fine after flashing the MOB30O image. Also, I've never had stock recovery get replaced on my Nexus 6 ever. That's really strange.

The difference between these two images has been posted many times - not sure why people are confused about it!
MOB is the version you want.
MMB is the version for the Carriers who haven't approved the newer radio in MOB.
MOB also includes some kernel enhancements to increase performance. These changes related to the Kernel "Tick Rate". I think the changes have improved performance a little, but you're not going to think you've purchased a new phone or anything.
Summary:
MOB: Newer kernel with performance improvements, updated Radio image.
MMB: Older kernel sans performance improvements, old radio.
Summary: MOB is the train you want to be on.

ayang02 said:
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Click to expand...
Click to collapse
I dl'd the O image, extracted and flashed the system image only through twrp while at work. Rooted using a PC when I got home and I have no issues so fah. I use chainfires method and his method requires running his image with fast boot. Fastboot boot cf... What ever you have the file named. It'll do it's thing on the phone then reboot 1-3x before it boots up fully. This root it rebooted once. On previous updates, up to 3 times before it finally finished.

Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.

dahawthorne said:
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
Click to expand...
Click to collapse
For me it's because I've lost my data a couple of times in the past doing an OTA update. I guess old habits die hard and I like the control I have flashing each image file manually. At least that way I can be reasonably sure that my data isn't messed with by not flashing the userdata image, plus, I can skip flashing recovery so I don't have to reinstall that. It only took me 9 minutes to complete the process tonight, including re-rooting, doing it the "old" way.

dahawthorne said:
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
Click to expand...
Click to collapse
Two very simple reasons. 1) if you are rooted. 2) if you are unencrypted.
FWIW: it takes about 60 seconds to extract the images from the .zip file. And about 3 minutes to flash the boot and system image files in fastboot.

before i download the entire package can anyone tell me if there is a new modem in july update?

H4X0R46 said:
I flashed SuperSU 2.76 just fine after flashing the MOB30O image. Also, I've never had stock recovery get replaced on my Nexus 6 ever. That's really strange.
Click to expand...
Click to collapse
Then that means you were able to get root successfully. My TWRP recovery got overwritten because I didn't get root. Anyways, I am gonna try flashing stuff from scratch in a few days. I've also never had issues flashing monthly updates and SuperSU until now.
Sent from my Nexus 6 using XDA Free mobile app

adm1jtg said:
before i download the entire package can anyone tell me if there is a new modem in july update?
Click to expand...
Click to collapse
There is no new modem, nor bootloader. Just security updates to boot and system images.

[ROOT] SM-G532F/G532G/G532M - Galaxy J2 GRAND PRIME PLUS (2016)

Below you will find my procedure to root the SM-G532F/G532G/SM-G532M Galaxy J2 GRAND PRIME PLUS/ Mediatek MT6737T.
This will root your device with SR3-SuperSU-v2.79-SR3-20170114223742
This procedure may work for previous and future firmware releases or it may not, however it is intended for the firmware versions as posted below. If you encounter issues simply flash the stock boot image included with the download.
If an updated firmware becomes available my advice is to update with FLASHFIRE to maintain root.
STATUS: Tested working
DISCLAIMER: YOU FLASH THESE AT YOUR OWN RISK. THE KNOX COUNTER WILL BE TRIPPED AND WILL POTENTIALLY VOID YOUR WARANTY. HAVING THE STOCK FIRMWARE TO HAND IS ALSO ADVISED
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Instructions:
◘ 1. Download the respective files below:
For SM-G532F based on AQD1 firmware- root_and_boot_sm-g532f
For SM-G532G based on AQC4 firmware - root_and_boot_sm-g532g
For SM-G532M based on AQD2 firmware - SuperSU-v2.79-SR3_rooted_boot_sm-g532m_AQD2_31517
ODIN 3.12
SAMSUNG_USB_Driver_for_Mobile_Phones
◘ 2. Install the USB driver and ODIN to Windows.
◘ 3. Boot your device to DOWNLOAD mode then connect your USB cable.
◘ 4. Run ODIN and place either SuperSU-v2.79-SR3_rooted_boot_sm-g532f_AQD1.tar or SuperSU-v2.79-SR3_rooted_boot_sm-g532g_AQC4.tar or SuperSU-v2.79-SR3_rooted_boot_sm-g532m_AQD2_3151 as is in the AP slot. Don't change any options and hit START.
◘ 5. Wait for the device to flash and reboot.
◘ 6. Install the SuperSU apk from Play store and you should be rooted.
◘ 7. Have fun!
Credits: ME, @Chainfire and my tester @ShaDisNX255
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
IF YOU APPRECIATE WHAT I DO AND WISH TO DONATE ME A COFFEE/BEER THEN CLICK HERE OR HIT THE THANKS BUTTON IF I HELPED YOU

I wish I could try this out
I've got the M variant, but it's good to know a recognized contributor is somewhat interested in this device.
Keep up the good work!

ShaDisNX255 said:
I wish I could try this out
I've got the M variant, but it's good to know a recognized contributor is somewhat interested in this device.
Keep up the good work!
Click to expand...
Click to collapse
There isn't actually any difference between models except region, so it's likely any one of these boot images may work.
However I will look at the M variant also.

ashyx said:
There isn't actually any difference between models except region, so it's likely any one of these boot images may work.
However I will look at the M variant also.
Click to expand...
Click to collapse
I'd totally test it out if you include a file for the M variant.
I would flash newest firmware first, flash the file that you would upload and see if it works.
I am currently rooted on "G532MUMU1APIG" firmware.
I think the newest available firmware for me is "G532MUBU1AQA3"

ShaDisNX255 said:
I'd totally test it out if you include a file for the M variant.
I would flash newest firmware first, flash the file that you would upload and see if it works.
I am currently rooted on "G532MUMU1APIG" firmware.
I think the newest available firmware for me is "G532MUBU1AQA3"
Click to expand...
Click to collapse
AQD2 is the latest.
Leave it with me.

ashyx said:
AQD2 is the latest.
Leave it with me.
Click to expand...
Click to collapse
Aaaah yes, that is correct.
Sorry, I was looking at my carrier's specific firmware update (TCE G532MUBU1AQC1 is the last update they have sent out)
Count me in for testing

ShaDisNX255 said:
Aaaah yes, that is correct.
Sorry, I was looking at my carrier's specific firmware update (TCE G532MUBU1AQC1 is the last update they have sent out)
Count me in for testing
Click to expand...
Click to collapse
Follow the procedure above: https://www.androidfilehost.com/?fid=745425885120735954
NOTE: Not always required, but if your device is using encryption it may be be necessary to format the /data partiton AFTER flashing the boot image for the device to boot.
.

ashyx said:
Follow the procedure above: https://www.androidfilehost.com/?fid=745425885120735954
NOTE: Not always required, but if your device is using encryption it may be be necessary to format the /data partiton AFTER flashing the boot image for the device to boot.
.
Click to expand...
Click to collapse
I'm fully backing up and will proceed to test this root method.
I will be back in a few minutes
---------- Post added at 06:22 PM ---------- Previous post was at 05:37 PM ----------
After installing SuperSU apk from the play store, I open it up (expecting to get something regarding updating binary) but instead I get a message: SuperSU Binary occupied
I'm guessing this means I am not rooted?

ShaDisNX255 said:
I'm fully backing up and will proceed to test this root method.
I will be back in a few minutes
---------- Post added at 06:22 PM ---------- Previous post was at 05:37 PM ----------
After installing SuperSU apk from the play store, I open it up (expecting to get something regarding updating binary) but instead I get a message: SuperSU Binary occupied
I'm guessing this means I am not rooted?
Click to expand...
Click to collapse
Are you using magisk or some other root application?
I also suggest to install V2.79 apk as the latest Supersu updates are having issues.
http://www.apkmirror.com/apk/coding...79-release/supersu-2-79-android-apk-download/

ashyx said:
Are you using magisk or some other root application?
I also suggest to install V2.79 apk as the latest Supersu updates are having issues.
http://www.apkmirror.com/apk/coding...79-release/supersu-2-79-android-apk-download/
Click to expand...
Click to collapse
Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.
---------- Post added at 02:48 AM ---------- Previous post was at 02:19 AM ----------
ShaDisNX255 said:
Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.
Click to expand...
Click to collapse
Also, this seems to have broken my IMEI. I got IMEI unknown

ShaDisNX255 said:
Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.
---------- Post added at 02:48 AM ---------- Previous post was at 02:19 AM ----------
Also, this seems to have broken my IMEI. I got IMEI unknown
Click to expand...
Click to collapse
The problem is once the bad version has been installed it doesn't automatically get removed by rolling back and the binary won't update, but you should still have root.
All this has been documented in the supersu beta thread.
https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
To start afresh delete su.img from /data then just reboot or wipe the /data partition in recovery.
Regarding the IMEI issue. This is related to a kernel/firmware mismatch.
You should be running the AQD2 firmware.
Which firmware are you currently running?

Not work for my phone
Everybody help me please

AlexEvans6 said:
Not work for my phone
Everybody help me please
Click to expand...
Click to collapse
What does that actually mean?

ashyx said:
The problem is once the bad version has been installed it doesn't automatically get removed by rolling back and the binary won't update, but you should still have root.
All this has been documented in the supersu beta thread.
https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
To start afresh delete su.img from /data then just reboot or wipe the /data partition in recovery.
Regarding the IMEI issue. This is related to a kernel/firmware mismatch.
You should be running the AQD2 firmware.
Which firmware are you currently running?
Click to expand...
Click to collapse
I am running (or was) AQA3 since that is the firmware I have downloaded to my computer at the moment. I am trying to download the firmware from samsung-firmware (AQD2) but it seems my download keeps getting cancelled and sammobile doesn't have AQD2 yet.
Went ahead and took it a step forward and re-flashed stock AQA3 via Odin, set it up again and flashed your file and same thing happened. It asked me to update binary, tried updating binary and states that it fails, not before, once again, requesting me to remove Knox.
I will once again try to download AQD2 firmware but I don't think it would make much a difference (or it could, you never know)
Tried it also with the APIG firmware I have that I originally rooted with and asked me for a password after booting your file even with OEM unlocking turned on.

ShaDisNX255 said:
I am running (or was) AQA3 since that is the firmware I have downloaded to my computer at the moment. I am trying to download the firmware from samsung-firmware (AQD2) but it seems my download keeps getting cancelled and sammobile doesn't have AQD2 yet.
Went ahead and took it a step forward and re-flashed stock AQA3 via Odin, set it up again and flashed your file and same thing happened. It asked me to update binary, tried updating binary and states that it fails, not before, once again, requesting me to remove Knox.
I will once again try to download AQD2 firmware but I don't think it would make much a difference (or it could, you never know)
Tried it also with the APIG firmware I have that I originally rooted with and asked me for a password after booting your file even with OEM unlocking turned on.
Click to expand...
Click to collapse
Is your data partition using encryption?
Im also a little confused regarding the binary update. It doesn't usually ask to disable Knox unless you have root.
Do you have root irrespective of updating the binary or not?

ashyx said:
Is your data partition using encryption?
Im also a little confused regarding the binary update. It doesn't usually ask to disable Knox unless you have root.
Do you have root irrespective of updating the binary or not?
Click to expand...
Click to collapse
I am not sure about how to answer both questions as I'm not sure how to check if the data partition is using encryption or I do not know what exactly do you mean if I have root irrespective?

ShaDisNX255 said:
I am not sure about how to answer both questions as I'm not sure how to check if the data partition is using encryption or I do not know what exactly do you mean if I have root irrespective?
Click to expand...
Click to collapse
OK what I mean is, regardless of whether the binary updates or not do you have root?
Do any root checkers or apps gain root privileges?
Unless you've disabled it then it is highly likely your device is encrypted. Encryption causes all sorts of issues with root.
It can be removed by wiping data in recovery but this will wipe everything on internal storage.

ashyx said:
OK what I mean is, regardless of whether the binary updates or not do you have root?
Do any root checkers or apps gain root privileges?
Unless you've disabled it then it is highly likely your device is encrypted. Encryption causes all sorts of issues with root.
It can be removed by wiping data in recovery but this will wipe everything on internal storage.
Click to expand...
Click to collapse
By wiping everything on the internal storage, you mean everything including media and such, correct?
I always thought that wiping the /data partition only meant everything related to the operating system, not the actual "internal" sd card, though in this phone's case I think they're one in the same.
This phone doesn't have a custom recovery and flashing the firmware I have (AQA3) for some reason has no recovery at all!
Anyway, yeah I tried a root checking app and it didn't detect root.
I will try once again with a root checker app and flashfire to see if either detects root with SuperSU 2.79 and without updating binaries and then try them again after I've tried to update binaries and failing.
My AQD2 download keeps getting interrupted again and again, do you know any other reliable source to download it beside samsung-firmware?
Let me give it a try and I'll give you a heads up.
BTW, how can I disable encryption?

ShaDisNX255 said:
By wiping everything on the internal storage, you mean everything including media and such, correct?
I always thought that wiping the /data partition only meant everything related to the operating system, not the actual "internal" sd card, though in this phone's case I think they're one in the same.
This phone doesn't have a custom recovery and flashing the firmware I have (AQA3) for some reason has no recovery at all!
Anyway, yeah I tried a root checking app and it didn't detect root.
I will try once again with a root checker app and flashfire to see if either detects root with SuperSU 2.79 and without updating binaries and then try them again after I've tried to update binaries and failing.
My AQD2 download keeps getting interrupted again and again, do you know any other reliable source to download it beside samsung-firmware?
Let me give it a try and I'll give you a heads up.
BTW, how can I disable encryption?
Click to expand...
Click to collapse
Data is the internal storage. It's separate from the system partition where the OS resides. Wiping data basically makes your device factory fresh as it wipes all user apps, settings and media.
In stock recovery it's labelled factory reset.
Every firmware has a recovery even the one you mentioned or your device just wouldn't boot.
If root apps are reporting not rooted then there is an issue somewhere. Quite likely it's encryption on the data partition that's causing the issue.
To remove encryption it is required to wipe data in recovery after flashing the boot image.
If it still doesn't work without encryption then I'm a little unsure of what the issue is as this procedure works just fine on Snapdragon and Exynos devices. It may be some kind of mediatek weirdness.
In any case I have an alternative method which should work, but involves an extra step.
At some point I will be looking at compiling twrp for this device, but I'd like to work out this root issue first.
For fast downloads go to updato.com

ashyx said:
What does that actually mean?
Click to expand...
Click to collapse
Idk help me please

Help with soft brick

Hi guys,
I got the ASUS Zenfone 3 Zoom and started playing with it. Unfortunately I managed to soft brick it and somehow I can't go back to stock. Here are all the things I did. I would be happy to get any ideas what to try next:
1. unlocked the bootloader - using asus's official unlock tool
2. flashed twrp recovery - twrp-3.2.1-0-Z01H-20180304.img, using:
adb reboot bootloader
fastboot flash recovery twrp.img
3. updated asus's firmware to the latest official one:
copying UL-Z01H-WW-71.60.139.30.zip onto internal memory
android detects the update and applying it using android
4. Enabling lock pattern at boot (from android settings). Correct pattern required even when booting into recovery
5. Installing supersu via twrp:
adb reboot recovery
installing supersu
wiping caches (the cache partition cannot be wiped)
6. SuperSu working (tested via android)
7. Reading about Magisk. Trying to install magisk via twrp. Magisk's installer complained that the system is not vanilla (due to SuperSu modifications). Have to uninstall SuperSu to return to previous state.
8. Tried uninstalling SuperSu from the program itself (in android). The uninstaller got stuck. The phone become unresponsive and had to reboot.
9. Found a script packaged as an executable zip (to be installed via twrp) that will uninstall SuperSu and return system to pristine state (SuperSu makes a backup of the files it changes before installation) - UPDATE-unSU-signed.zip. Uninstallation worked.
10. Magisk installation still complained about the bootloader. Then things started to go wrong. I unpacked the latest firware UL-Z01H-WW-71.60.139.30.zip, took out boot.img and tried to flash just the bootloader
fastboot flash boot boot.img
11. Upon reboot the phone got stuck at the ASUS logo. Reboot into recovery and into fastboot still works (soft brick). Still shows unlock pattern at boot.
12. I tried flashing the original firmware using TWRP (install a zip). However the installation threw some errors. Unsuccessful.
13. I've tried flashing the system.img from the original firware using fastboot but still it's stuck at the ASUS logo at boot.
fastboot flash system system.img
Here I am stuck. I've read that TWRP cannot install properly the ASUS official firmware but if you flash the original recovery, it can probably flash it properly. Another thing that I think might explain why I cannot get out of the soft brick is that I've enabled the lock pattern at boot, which effectively encrypted some parts of the phone and I have a strong feeling this interferes with the boot process. I will look for a script/installable zip (via twrp) that can remove the lock.
I really need ideas/suggestions before I make something that will turn my phone into a hard brick. Thanks.

What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you

Thanks
+)KEV1N(+ said:
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Click to expand...
Click to collapse
Thanks,
I tried to find a stock recovery images but unsuccessful. Can you tell me where to get it from?

Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck

+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
-- [link] removed due to XDA regulations
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).

mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.

mollonado said:
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
Click to expand...
Click to collapse
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
It came preloaded with Nougat? Interesting.

+)KEV1N(+ said:
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
It came preloaded with Nougat? Interesting.
Click to expand...
Click to collapse
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?

mollonado said:
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
Click to expand...
Click to collapse
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.

+)KEV1N(+ said:
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
Click to expand...
Click to collapse
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.

mollonado said:
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
Click to expand...
Click to collapse
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?

mollonado said:
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
Click to expand...
Click to collapse
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.

+)KEV1N(+ said:
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
Click to expand...
Click to collapse
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,

mollonado said:
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
Click to expand...
Click to collapse
First off, my apologies for this late reply (Been superbusy with school and internship assignments)
Secondly, and that is why I only use magisk. Because once you mess with the host file, depending on what module you install, it can range from tripping safetynet to bootlooping.
So quick question, is it still in this state right now since 9 days ago?
Greetings,
Kevin

+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
I made a mistake and could not install recovery stock, I followed what you wrote in the beginning install MM recovery and so I did a hard reset and I was able to install the most current recovery stock and installed ROM Oreo, Thanks. Sorry, I'm on google translator.

Welp, I searched, didn't find a relevant answer. XT1625 help wanted.

Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.

Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)

Wolamute said:
Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.

What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
fastboot flashing unlock
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
So I went through and fastboot flashed all those files from your link to Motorola support.
It wouldn't let me relock the bootloader with fastboot oem lock
it did lock with fastboot flashing lock
I was able to reboot, now of course with a verification error boot msg
Connected to wifi and it auto-prompted the Nougat ota update.
Just completed the Nougat install currently on build NPJ25.93-14
Maybe you just need to reflash those files from the Motorola site, and connect to wifi for the 700+MB download?
there's another security update to NPJ25.93-14-4 available after you get back to nougat. Good luck

superceege said:
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Click to expand...
Click to collapse
My xt1625 was boot-unlocked, and I was try the same twrp version you mentioned. I continued researching, and found that, despite the error msg, twrp was flashed correctly. I just needed to go to recovery directly from the bootloader screen. Thanks for your help.

superceege said:
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)
Click to expand...
Click to collapse
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.

Wolamute said:
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.
Click to expand...
Click to collapse
Hmm, what 6.0.1. build do you have (if you scroll down to the bottom of Settings>About Phone, there should be an entry for Build Number)? I recall that for US devices you need to be on MPJ24.139-48/49 or MPJ24.139-64 to be eligible for the OTA update to Nougat. Any other different firmware build may not give you an update as the build's not recognised by the update server for your region/software channel.
However, as you flashed the MM firmware onto your device when you previously had Nougat, I would advise against taking the OTA update route. Depending on what version of Nougat you had before you tried to root, you may hard brick your device if you try to flash the OTA, since flashing MM firmware may not downgrade your bootloader, as such you'd be flashing an old OTA onto a newer Nougat bootloader, which is a really bad idea. If you can remember what stock firmware you had (or at least what security patch it was), we can try to locate the correct firmware for you to flash and safely get you back onto the update path.
As for the recovery, that sounds like the stock recovery you have on your device, which if you re-flashed the stock ROM, will replace TWRP. You may have to re-flash TWRP.
On a related note, on Marshmallow, you do not need to flash a custom kernel - you could flash TWRP and your choice of root manager. On stock Nougat (on the G4/Plus devices), you must flash a custom kernel, else you will likely bootloop as you experienced. Here's a rooting guide for G4/Plus Nougat devices: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
---------- Post added at 04:28 AM ---------- Previous post was at 04:23 AM ----------
Baboon_Red said:
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
That error is normal, as far as I know - the TWRP image is not cryptographically signed by Motorola, so that message seems to be mainly informational and alerting you that you are flashing unsigned images in fastboot (which you are), since fastboot is mainly used to flash signed images. Once you've flashed TWRP, reboot straight to recovery to ensure the TWRP is not overwritten by the stock recovery. Afterwards, you can boot as normal.
Be careful to flash the TWRP version/architecture for what you want to do - e.g. if you wish to flash 64 bit custom ROMs, you must use a 64 bit TWRP version. Attempting to flash 64 bit custom ROMs via 32 bit TWRP may give you an error 255 otherwise.