Database Develop

Observation On Infinix Hot 2 [X510-D5110-Androidone-20151208] on Root

So today I embarked on what seemed to be a fruitless journey as I tried to root the Infinix Hot 2 on the latest build (December Security Patch of course) and I observed the following:
1. Flashing TWRP Recovery that was previously made for this device doesn't Flash. SP/Infinix Flash Tool flashes the recovery quite alright but booting to recovery with ADB afterwards gives a "No command" screen.
2. Kingroot (PC & Mobile) can't root this device as of yet :'(
3. I think the bootloader can be unlocked using the Android One Toolkit that was created for 1st Gen Android One devices. Reason being the fact it booted to fastboot and prompted me with the option to accept bootloader unlock or not.
Should you come come successful with flashing recovery or rooting this latest build, please comment your method. Thank you...

Link to Android One Toolkit:
http://forum.xda-developers.com/crossdevice-dev/android-one-general/toolbox-android-one-toolkit-one-click-t3030165

recovery partition is protected, it will get back to stock recovery if you boot the system. so you really need to boot recovery as the first thing you do after flashing.
which because of the similar bug we can't unlock our bootloader, is impossible to do with default setting. flash your lk partition with this:
http://www80.zippyshare.com/v/X4etwppD/file.html
taken from: http://forum.xda-developers.com/hot-2/development/android-one-rom-recovery-twrp-root-sp-t3227682

sabcpj said:
recovery partition is protected, it will get back to stock recovery if you boot the system. so you really need to boot recovery as the first thing you do after flashing.
which because of the similar bug we can't unlock our bootloader, is impossible to do with default setting. flash your lk partition with this:
http://www80.zippyshare.com/v/X4etwppD/file.html
taken from: http://forum.xda-developers.com/hot-2/development/android-one-rom-recovery-twrp-root-sp-t3227682
Click to expand...
Click to collapse
Thanks I will try this in the morning...
One more question... Does this mean after flashing recovery I can boot directly into TWRP using key combo?

iAmWiz said:
Thanks I will try this in the morning...
One more question... Does this mean after flashing recovery I can boot directly into TWRP using key combo?
Click to expand...
Click to collapse
yes, you should be. and you need to

Alright then

sabcpj said:
yes, you should be. and you need to
Click to expand...
Click to collapse
there is no scatter file for the lk-recovery.. I do not think I can flash it directly with Flash Tool without the scatter file

iAmWiz said:
there is no scatter file for the lk-recovery.. I do not think I can flash it directly with Flash Tool without the scatter file
Click to expand...
Click to collapse
why do you think you need another scatter file. you already tried flashing twrp right? use that one. then change the location of partition named "lk" to point this file. that's all.

sabcpj said:
why do you think you need another scatter file. you already tried flashing twrp right? use that one. then change the location of partition named "lk" to point this file. that's all.
Click to expand...
Click to collapse
Alright. If I cannot get a workaround on this, I'll just Flash Infinix 5.1 ROM and wait till M

Try using towel root
https://towelroot.com/

Mysteryagr said:
Try using towel root
https://towelroot.com/
Click to expand...
Click to collapse
Thanks but towelroot didn't work out.

Root achieved... More at
http://forum.xda-developers.com/hot-2/development/root-recovery-xposed-successfully-t3276420

please can you help me sp flashtool stuck at 0 and nothing happens

TWRP 3.2.3-1 for Pixel Devices

TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set

How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.

Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this

Wow and so it begins, great work thanks!

Thanks
Sent from my Pixel using XDA-Developers mobile app

has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well

Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:

Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.

GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...

zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.

Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.

Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.

zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.

rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....

Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?

ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk

Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.

fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off

ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????

BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root

Root without twrp

Is there any way to root without TWRP? I'll be doing this for a family member, and want to keep it as stock as possible. I just want root to remove some stock apps they don't need, then probably unroot. Is there any way to do so? Otherwise I was thinking of flashing TWRP, rooting, then flashing back the stock recovery.

Purplezigar said:
Is there any way to root without TWRP? I'll be doing this for a family member, and want to keep it as stock as possible. I just want root to remove some stock apps they don't need, then probably unroot. Is there any way to do so? Otherwise I was thinking of flashing TWRP, rooting, then flashing back the stock recovery.
Click to expand...
Click to collapse
You can boot into twrp.
Use "fastboot boot twrp-recovery-file location"
Then you can just use the root shell from twrp to make changes, no need to flash SuperSU if you want the ROM unrooted.

mrmazak said:
You can boot into twrp.
Use "fastboot boot twrp-recovery-file location"
Then you can just use the root shell from twrp to make changes, no need to flash SuperSU if you want the ROM unrooted.
Click to expand...
Click to collapse
I'm not quite sure what you're saying, but it sounds like you're saying that I can boot into the TWRP image while I'm connected with fastboot, without actually installing TWRP?

Purplezigar said:
I'm not quite sure what you're saying, but it sounds like you're saying that I can boot into the TWRP image while I'm connected with fastboot, without actually installing TWRP?
Click to expand...
Click to collapse
That's right. You can just boot twrp instead of flashing it.
And when twrp is booted you can connect to phone with adb, you will have a shell with root privileges.

mrmazak said:
That's right. You can just boot twrp instead of flashing it.
And when twrp is booted you can connect to phone with adb, you will have a shell with root privileges.
Click to expand...
Click to collapse
Cool! So then I can just remove system installed apps that I don't want (e.g. Google Play Movies and Books)?

Purplezigar said:
Cool! So then I can just remove system installed apps that I don't want (e.g. Google Play Movies and Books)?
Click to expand...
Click to collapse
You could also read this thread as see if the twrp packages there are what you want to do.
They can all be run from the booted twrp.
https://forum.xda-developers.com/r1-hd/how-to/guide-ad-removal-debloat-block-ota-easy-t3429555

mrmazak said:
You could also read this thread as see if the twrp packages there are what you want to do.
They can all be run from the booted twrp.
https://forum.xda-developers.com/r1-hd/how-to/guide-ad-removal-debloat-block-ota-easy-t3429555
Click to expand...
Click to collapse
Awesome, thanks!

Magisk 14 News

Wow no need for custom recovery...
http://www.androidpolice.com/2017/0...hout-root-installing-without-custom-recovery/

@ultramag69 Maybe he doesn't follow Magisk closely? I know I don't. Magisk is only on used my stepmom's OP3T H2OS (which I update but don't look at the change log since it's only there in case I need it in the future), the other 2 phones I support don't use Magisk they use LOS su add-on. Not everyone who uses root cares about all the bloated/"nifty" features that come out, some just want plain old root.

I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.

I'm letting people know that with 14 they can keep stock recovery and take OTAs

ultramag69 said:
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
Click to expand...
Click to collapse
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS

lollyjay said:
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
Click to expand...
Click to collapse
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.

ultramag69 said:
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
Click to expand...
Click to collapse
No need to do that now

Honestly, who roots a phone without flashing a custom recovery the very second after? Unless they are forced to use Flashfire without BL unlock, I guess.

lollyjay said:
No need to do that now
Click to expand...
Click to collapse
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...

ultramag69 said:
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
Click to expand...
Click to collapse
No problems at all with my OP5

Magisk 14.0 breaks XPosed so had to go back to Magisk 13.3

Now where can we obtain a copy of the stock boot.img?

almostthere said:
Now where can we obtain a copy of the stock boot.img?
Click to expand...
Click to collapse
What you're supposed to do is make a backup of your boot partition any time you update your rom. So if you didn't do that then you can dirty flash your current Rom and that would give you the stock boot.img and again, go into recovery and make a backup of your boot partition. then if you want to flash a custom kernel you can.

Help the noobs
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.

s_ofer said:
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
Click to expand...
Click to collapse
I have the stock 4.5.10 boot.img for download here:
https://drive.google.com/file/d/0B3gcDbDvV4Mkbm5EMEZ4dnpSbk0/view?usp=drivesdk
Sent from my OnePlus5 using XDA Labs

Thanks.
Do any of you think it is possible to FLASH anything without unlocking the bootloader?
There is a thread somewhere for OP3T that shows somehow that is possible to load TWRP on the phone without unlocking the bootloader or wiping data.

I only use for root too but every so often I open magisk manager as it updates also both the manager app and magisk itself. But using magisk to root my Axon 7 with unlocked bootloader.

Stock Owens XT1775, just got notice update is ready to install - root first or after?

Sorry if this seems like a dumb question - I'm a little green on the phone modding (last phone was a S3, rooted with oneclickroot I think) I have a bootloader unlockable XT1775 owens (bought from retail, no carrier lock) that I have been planning to bootloader unlock and root with TWRP & Magisk. I just got a notification that update "NPR26-58-45" is available. I downloaded it, but haven't installed yet - for fear that it might affect what I want to do for root.
What should I do? ie: - install it, and go forward with the root process? Root first, and then install?

jdsmn21 said:
Sorry if this seems like a dumb question - I'm a little green on the phone modding (last phone was a S3, rooted with oneclickroot I think) I have a bootloader unlockable XT1775 owens (bought from retail, no carrier lock) that I have been planning to bootloader unlock and root with TWRP & Magisk. I just got a notification that update "NPR26-58-45" is available. I downloaded it, but haven't installed yet - for fear that it might affect what I want to do for root.
What should I do? ie: - install it, and go forward with the root process? Root first, and then install?
Click to expand...
Click to collapse
Do NOT root first!
Edit: do me a favor and upload a system backup after you update, root and install twrp (if you do anyway), so I can make a twrp flashable ROM.
Edit-2: actually, if you could backup system before rooting or anything, that would be better.

You do not want to root first. Update then root as doing an ota while rooted may loose your root status or worse!

Goose03 said:
Do NOT root first!
Edit: do me a favor and upload a system backup after you update, root and install twrp (if you do anyway), so I can make a twrp flashable ROM.
Edit-2: actually, if you could backup system before rooting or anything, that would be better.
Click to expand...
Click to collapse
Thanks Goose. I will gladly upload that, but I will have to get back to you after the weekend - I apologize, heading out of town after work.
To clarify on the process, I would go through the step to unlock the bootloader (using the code I will get from Moto website and "fastboot oem unlock CODE"). After that is the TWRP step, right? If so, which command do I use: "fastboot boot recovery.img" or "fastboot flash recovery recovery.img" ??

jdsmn21 said:
Thanks Goose. I will gladly upload that, but I will have to get back to you after the weekend - I apologize, heading out of town after work.
To clarify on the process, I would go through the step to unlock the bootloader (using the code I will get from Moto website and "fastboot oem unlock CODE"). After that is the TWRP step, right? If so, which command do I use: "fastboot boot recovery.img" or "fastboot flash recovery recovery.img" ??
Click to expand...
Click to collapse
Np. Take your time. Thanks. Yes, that is what you do to unlock. Then for flashing twrp it's like you have but make sure to match the last part "recovery.img" to whatever the recovery is named. If your recovery is named twrp.img the command is:
fastboot flash recovery twrp.img

If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334

koop1955 said:
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
Click to expand...
Click to collapse
That's the one I had been following! I found that very helpful - that would make a good sticky post for guys like myself.
Since I have your attention too, I'd like to ask - is dmnoverity and phh's SU not needed at all? The only three files copied to the SD card (and then installed) are TWRP, Magisk zip, and Magiskmanager APK?

jdsmn21 said:
That's the one I had been following! I found that very helpful - that would make a good sticky post for guys like myself.
Since I have your attention too, I'd like to ask - is dmnoverity and phh's SU not needed at all? The only three files copied to the SD card (and then installed) are TWRP, Magisk zip, and Magiskmanager APK?
Click to expand...
Click to collapse
Phh SU is not needed since Magisk gives you all the necessary root and features. dmnoverity is not needed. I recommend you allow twrp system write access.

koop1955 said:
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
Click to expand...
Click to collapse
Well, I followed your instructions....with a minor tweak - and I'm having problems.
I unlocked the bootloader a couple days ago, but couldn't download the TWRP.bin file, so I used my phone through today. Formatted a 64gb card and loaded the magisk zip and apk on it. Flashed the TWRP on the phone, and used the wipe function to wipe data, cache, and dalvik, and then made a backup to my sd card. Flashed the magisk.zip, and then hit reboot "system". Now it just reboots to TWRP. I can reboot to bootloader, but hitting "start" goes to TWRP again.
What do I do? Where did I go wrong?

jdsmn21 said:
Well, I followed your instructions....with a minor tweak - and I'm having problems.
I unlocked the bootloader a couple days ago, but couldn't download the TWRP.bin file, so I used my phone through today. Formatted a 64gb card and loaded the magisk zip and apk on it. Flashed the TWRP on the phone, and used the wipe function to wipe data, cache, and dalvik, and then made a backup to my sd card. Flashed the magisk.zip, and then hit reboot "system". Now it just reboots to TWRP. I can reboot to bootloader, but hitting "start" goes to TWRP again.
What do I do? Where did I go wrong?
Click to expand...
Click to collapse
Try fastboot oem fb_mode_clear
Sent from my Moto E (4) Plus using XDA Labs

Goose03 said:
Try fastboot oem fb_mode_clear
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Thank you. I tried the command, and it said OK, but it still boots to TWRP; i then reboot to bootloader, and select Start and it goes into the normal system. Is that how it is supposed to work?
Last night I was stuck in a TWRP loop, but i got it to go with formatting data and factory reset wipe in TWRP. After finally getting the system to boot, I installed the Magisk Manager and then Adaway. Now today I was playing with the Chase Pay app, which won't let me sign in due to being rooted. I then reverted my hosts file and uninstalled Adaway, and played with all the hide options in Magisk., to no avail. Root Checker app says that Safetynet is tripped.
Does Magisk effectively work for apps that look at Safetynet on this phone - apps like Chase Pay?

jdsmn21 said:
Thank you. I tried the command, and it said OK, but it still boots to TWRP; i then reboot to bootloader, and select Start and it goes into the normal system. Is that how it is supposed to work?
Last night I was stuck in a TWRP loop, but i got it to go with formatting data and factory reset wipe in TWRP. After finally getting the system to boot, I installed the Magisk Manager and then Adaway. Now today I was playing with the Chase Pay app, which won't let me sign in due to being rooted. I then reverted my hosts file and uninstalled Adaway, and played with all the hide options in Magisk., to no avail. Root Checker app says that Safetynet is tripped.
Does Magisk effectively work for apps that look at Safetynet on this phone - apps like Chase Pay?
Click to expand...
Click to collapse
It is not normal to have it boot straight to twrp or the bootloader rather than the rom unless you do so manually.
Have you triedbplaying with the settings in Magisk Manager? There is an option to hide Magisk from your choice of apps. There is also a couple other options in the settings to hide things as much as possible. If you have Xposed installed it won't pass a safteynet check.
Sent from my Moto E (4) Plus using XDA Labs

XT1775 rom's is possible install on XT1776 ?

almao11 said:
XT1775 rom's is possible install on XT1776 ?
Click to expand...
Click to collapse
You could. I've flashed xt1775 firmware to my xt1776 to get a backup of the system to make a twrp flashable from. I don't recommend it, but if you only flash the system and not the modem and oem it should provision data services. Why do you ask exactly?
Sent from my Moto E (4) Plus using XDA Labs