Database Users

How many of you did unlock their bootloader?

Hello,
I had the impression of plenty of people unlocking their BL, like far more than 90%.
Now, as I thought about it, it came to my mind that I could be totally wrong about that.
Till now I thought, to unlock BL is like the normal thing to do, and maybe to relock if DRM was needed or DRM hack did not work.
Or, as in case with the latest DRM_Hack from Team HSxEXR, which is really cool! - if you forget to apply it after flashing, you maybe don't want to wipe data/factory reset after you already installed your apps.
So there are some cases where you just want to relock this thing.
But there are maybe some people who never unlocked it and went stock-based all the time? No custom kernels, no multiboot?
Since there is xposed, you can have a lot of things with any rom, if you can root and install a recovery. And there are the fantastic stock based ROMs which I prefered also a lot of the time, because of the better camera.
What is/ was your choice? Feel free to explain I am really eager to know how many of you never unlocked for example! Did you encounter any problems or could you use all the tweaks you wanted to install?

Unlocked 10 minutes after i arrived home with my Z2 XD

I haven't unlocked it and I don't want it because I'm totally satisfied with my stock based rom.
I don't even use xposed.
On previous phones I did both but I haven't crossed anything that would make me want to do it on my Z2

I haven't unlocked my bootloader. I just found the stock experience satisfying and trusted that Sony would still upgrade the software, which they seem to be doing. I use the #nochromo ad-blocking chrome browser and dolphin with an ad-blocker plug-in, so apart from YouTube ads I'm not bothered for root. Emulators run fast, battery life is good, camera is great (if you mess about with manual settings) and benchmarking to 49000 on antutu for what it's worth. Also I have a sony tablet & sony 4k android TV so I've left them all stock so they talk to each other fluidly. MM is only weeks away so I'm not even going to bother flashing the beta rom. And for the record I flashed both my HTC One X and HTC Desire multiple times, to account for the shortcomings in those devices. The shortcomings in the Z2 are so niggly and small that I don't see the point, in fact I have gone sim-only with my provider and refused an S7 Edge upgrade cos I like the Z2 so much!
:silly:

Kept a locked bootloader, only needed to have root.

Well,as for me,im too afraid to unlock the bootloader or even root.First,because im a heavy noob,i dont understand nothing ,even when you explain me,i will be like a girl which says "Ehmm,okay......".
The only thing i did is flashed my phone,thats the simpliest thing ever.My phone is still under warranty so i dont want to mess with stuff like that.

Unlocked it, the first day i got it.
Androplus kernel is must to get the full potential of the snapdragon.

I have LB, but sometimes I unlock for trying ROMs, I have a backup of my TA partition so I don't worry to unlock bootloader every time I want to try something
Enviado desde mi D6503 mediante Tapatalk

I did unlock my bl.
But I couldn't really notice a whole lot of difference, even with a custom kernel, so I relocked it by restoring my ta backup(make sure to take a ta backup no matter what). That was half a year ago though.
I might unlock it now that drm restoration is really easy, but I think that unlocking your bl does wipe your phone, and I am too bored to backup everything.
In all honesty, I don't think you are missing a whole lot by not having a custom kernel or a rom such as cm, as sony's software is already light enough.
However, I am guessing that there should be some gains via installing a custom kernel (overclock, or better battery life) so keep that in mind too.

Unlock and relocked several times already... No problems so far. Total freedom of choice....

Until the Xperia Z3, we still have the choice to keep bootloader locked since root exploit have been found.
But with Z4 then later Xperias you are forced to unlock your bootloader to root.
There won't be anymore root exploit for locked bootloader. We are lucky that Sony is allowing the unlocking of bootloader.
Envoyé de mon D6503 en utilisant Tapatalk

niaboc79 said:
There won't be anymore root exploit for locked bootloader. We are lucky that Sony is allowing the unlocking of bootloader.
Click to expand...
Click to collapse
Could you explain why?
Isn't it possible that new root exploits are developed in the future?

A root exploit is basically an unpatched security issue.
No system will ever be secure, there are possibly even root-exploits out there which are not shared with anybody
(Zero-day-exploit).
Anyways, I like the way Sony is opening their boot loader for public... It's like nexus.

Unlock after back my TA up, for safety

Knutselmaaster said:
Could you explain why?
Isn't it possible that new root exploits are developed in the future?
Click to expand...
Click to collapse
Nobody with requested skills care of Xperia devices anymore.
Envoyé de mon D6503 en utilisant Tapatalk

Unlocked the bootloader was the first thing I did, after testing the Z2 for a few hours only to see that everything works.
I didn't even bother to take a backup of those DRM keys. Never goig to use anything DRM related anyway.
I needed to flash a minimalistic ROM without bloatwares.

I've unlocked it a few times, but the worse photo quality always brought me back to stock. It's a shame we can't have the best of both worlds

Knutselmaaster said:
Could you explain why?
Isn't it possible that new root exploits are developed in the future?
Click to expand...
Click to collapse
XDA did a very nice article about this a while ago:
http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
This line should be easy to understand: "In lieu of an unofficial bootloader unlock (those are fairly rare these days, short of leaked engineering bootloaders for a few Samsung devices), it seems highly unlikely that you’ll be getting root on Android 6.0 without some divine intervention – the combination of dm-verity (to stop your phone from booting with any modifications to the system partition), and the requirement for SELinux changes in the ramdisk (to let root work), look set to make things rather un-fun for root-aspiring users of these locked-down devices."
I'm so glad sony didn't enable dm-verity on the z2 mm beta or else root would be a HUGE problem for users with unlockable bootloader like me (z2 was my first sony device and i stupidly thought i could buy any z2 and request the unlock code from sony's dev site, so i bought it from vodafone at FULL price and got an unlockable bootloader as a bonus :crying: )
Like @niaboc79 said this things are EXTREMELY complex, technical and very hard to get around... and there's no one with the required skills on xperia sections as far as i know. I would gladly pay like 25/30eur to unlock the bootloader of my z2 if a sunshine like hack was available for it.
And to try and keep this still on topic i didn't unlock my bootloader just because i can't xD

I rooted my Z2 within a few days of owning it (coming from a Z1 which was a dud with horrible touch screen issues )
I proceeded to backup the TA partition and unlock the bootloader, and I have never relocked it, and I think it will stay that way for the foreseeable future.
To me, if the bootloader can be unlocked, it shall become unlocked
I'm currently on official CM12.1 with M5 Kernel, and that made me fall in love with the Z2 all over again, and funny enough this isn't the first time using a custom ROM like CM12.1.
I've used many ROMs on the Z2, from stock to custom and from KitKat to Marshmallow, and in the past there was always a catch in some way or another going to something like CM12.1 or anything based on it.
BUT, that isn't the case anymore.
Using official CM12.1 is just pure bliss. Literally everything is working just as well as on stock. It's like owning a Xperia Nexus, if such a thing existed
No random reboots. No lockups. No force closes. No errors. No bugs.
Awesome
So yes. Unlocking the bootloader was so worth it

Yes indeed, I also had a marvelous experience with 12.1 CM.
The only backdraw was that CM feels so "mainstream" and the ****ty "recovery".
This rom definetly ranges in the top 3 for z2 in my opinion.
There is one thing, that I miss on non-Sony ROMs if the camera is ok, and that is the small apps, yt/media-viewer in particular.
I don't like installing xposed if I don't have to, so the small apps are a nice way to listen to yt while screen off or using other apps in the foreground.

LG G4 Bootloader relockable with new Nougat Update!

Today I updated my G4 to Nougat (downloaded via XDA) and discovered that the command "fastboot oem lock" works fine, so guys if you want to relock your device now you've an official option for this
TAKE NOTE: the command wipes the phone so MAKE A BACKUP before doing this!!!

You didn't discover anything; don't claim work you didn't do. You "discovered" it using my thread and/or YouTube video.

Its not a massive discovery and he could very well have found this without seeing your thread/video as could have anyone.
No need to be so hostile!
This is probably due to this release being v29 and not v30.
It is likely that the bootloader distributed with v29 is a test build and that this will not be as easy in the final V30 release.
LG probably overlooked it because they didn't expect it to be available to everyone.
The bootloader has also been relockable for some time through alternative means,
Re-Flashing the MISC partition (Personally tested) from a backup or extracted from a KDZ (Reported by others) will also re-lock your device.

OllieD said:
Its not a massive discovery and he could very well have found this without seeing your thread/video as could have anyone.
No need to be so hostile!
This is probably due to this release being v29 and not v30.
It is likely that the bootloader distributed with v29 is a test build and that this will not be as easy in the final V30 release.
LG probably overlooked it because they didn't expect it to be available to everyone.
The bootloader has also been relockable for some time through alternative means,
Re-Flashing the MISC partition (Personally tested) from a backup or extracted from a KDZ (Reported by others) will also re-lock your device.
Click to expand...
Click to collapse
I know it's not a massive discovery but he did take it from my video at least, before starting this thread he asked for details on YT and now he deleted the comments (need proof? I still have mails of comments). Maybe I should've not been so hostile but this kind of things bother me.

Appears to be a duplicate of [V29a only] I managed to relock the bootloader without any backups.
Better to have all the discussion in one place.
Thread closed.

Can't Install Every Rom for this Phone? (XT1575)

The are only a few roms that actually install but then some roms say they were flashed successfully but when i reboot the system it just bootloops.
I Currently have Slim Rom i'm pretty sure and it's 1 of the only roms that actually booted.
So if anyone can help that would be very helpful.
Baseband Version is M8992_1255331.29.01.88.09R

LGAGaming said:
The are only a few roms that actually install but then some roms say they were flashed successfully but when i reboot the system it just bootloops.
I Currently have Slim Rom i'm pretty sure and it's 1 of the only roms that actually booted.
So if anyone can help that would be very helpful.
Baseband Version is M8992_1255331.29.01.88.09R
Click to expand...
Click to collapse
You are running stock Nougat baseband. Most of the ROMs here were designed to work on the MM baseband so they will not work. Read through the forums here at XDA and you will see which ones you can effectively flash.

aybarrap1 said:
You are running stock Nougat baseband. Most of the ROMs here were designed to work on the MM baseband so they will not work. Read through the forums here at XDA and you will see which ones you can effectively flash.
Click to expand...
Click to collapse
Thanks I thought that it was the marshmallow as I seen a thread that said it was the marshmallow baseband

aybarrap1 said:
You are running stock Nougat baseband. Most of the ROMs here were designed to work on the MM baseband so they will not work. Read through the forums here at XDA and you will see which ones you can effectively flash.
Click to expand...
Click to collapse
Is there a way to get The Marshmallow BaseBand?

LGAGaming said:
Is there a way to get The Marshmallow BaseBand?
Click to expand...
Click to collapse
Not quite sure what's meant by your own meaning of Baseband. Your more than likely going to be answered by people still using the phone in different degrees of knowledge.
The experienced with a real practical application of this XT1575 device mostly have moved on to another device by now - but will any left on it be answering you. I'm glad to see @aybarrap1 has answered.
@stevejohnson42 uses the XT1575 too, and reports here and there of his flasholic tendencies on this device - might be helpful in any Nougat based ROM's to use the search box there and see if he's added anything in it.
Custom ROM Marshmallow development was always greater cause the XT1575 stayed on the Marshmallow OS for so long and because of Motorola not releasing Nougat sooner for it.
There are some Custom ROMS based on Nougat - just read their OP's to understand what's being required to using each one of them...
Nougat ROMs built for a Stock Nougat Kernel and Modem.
To answer your question without you going into a Blackhole in having to know more about your device in getting it back to good ground - I OFFER THIS-
Only way I know is to buy a XT1575 device that's never taken the servers Nougat OTA or has been ADB flashed to Nougat OS...
This as in ADB flashed questioned basically being understood by the device still having the bootloader status to LOCKED - as DEVICE LOCKED, the STATUS will still show 0, and it's software status of OFFICIAL.
Note: The Status Code will always show 2 = (relocked) or 3 = (unlocked), and it can never go back to 0 = (device locked), if it's ever been unlocked by a Motorola token code obtained from their site.
Otherwise you need an image of the Bootloader screen of the device up for sale.
THAT'S THE ONLY WAYS TO KNOW AND A SELLER SHOULD SUPPLY THIS AS A GUARANTEE AND/OR AN IMAGE SHOWING YOU FIRST...
OR YOU BUYING FROM A SITE AND ASKING THESE QUESTION OF THE XT1575 SELLER FIRST BEFORE THE PURCHASE AND THE SITE (LIKE EBAY) HAS A GUARANTEE IN THAT AD - TO FALL BACK ON...
To check this yourself-
1. Using (vol down + power button) put the device in bootloader mode where all of this is visible / should read as follows - see images also.
(A) - totally Stock non-rooted Marshmallow Baseband should read as - M8992_1255331.29.01.88.02R SUPER_NA
as taken from my Marshmallow XT1575 build MPHS24.49-18-16 devices Bootloader.
(B) - Shows the very same thing with device from the ABOUT PHONE in settings.
(C) - Rooted Custom Rom Nougat Baseband M8992_1255331.29.01.88.09R - from the ABOUT PHONE in settings / using the NuclearROM.
(D) - M8992_1255331.29.01.88.09R SUPER_NA - from the Bootloader Mode on same device - using the NuclearROM.
PS: I'm thinking, changing to a different Android build changes the Baseband build as well being applicable to the OS build version.
Warning:::
No don't ever do a complete ADB MM downgrade flash - if wanting to OTA back up to Nougat at some future point after already being on the Nougat OS.
To be clear "It's not recommended to downgrade" and allow a Moto X Pure device in taking the Nougat OTA again.
Once bootloader.img and gpt.bin are updated, there is no reverting back without the serious and the likely risk of a hard-bricked device. Only remedy at this time is a mainboard replacement. Confirmed in this threads post #75 .
A COUPLE POINTS - I'd like to make:
I've always clean flashed my XT1575 in custom roms and to going back in a stock Nougat OS - point being, I have never had any problems thereafter...
Another thing I'm thinking with an LOS based ROM - writes / changes some partitions parts that only with your ADB flashing back to the factory Official Stock Nougat can fix - changing everything back to an original partition structure.
- TWRP only backups a few partitions on the device, so partitions out of it's reach never gets restored back to an original stock environment with a TWRP backup when you do a restore using it/one made thereafter.
OTHER Reading you might want to do:
#30
#61
#73
#147
#179
#184
Baseband
I'm far from being a real practical experienced user in a XT1575 device but, I share in what I've taken a grasp of.
Hope this helps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

LGAGaming said:
Is there a way to get The Marshmallow BaseBand?
Click to expand...
Click to collapse
Sorry I never got around to replying. @ResistanceIsFutile did a pretty good job explaining things as far as I can see. I just flashed stock Nougat within the last month with the intention of staying on stock rooted. I don't know if it is possible to downgrade any parts successfully but from what little I read a month ago on it, I did not remember anything staying how to do so.

LGAGaming said:
The are only a few roms that actually install but then some roms say they were flashed successfully but when i reboot the system it just bootloops.
I Currently have Slim Rom i'm pretty sure and it's 1 of the only roms that actually booted.
So if anyone can help that would be very helpful.
Baseband Version is M8992_1255331.29.01.88.09R
Click to expand...
Click to collapse
As @aybarrap1 has pointed out already, you are running a stock Nougat baseband,
Meaning you've also upgraded fully to the Nougat OS on your device.
Possibly, for someone new to the XT1575 on Nougat OS it's a good place to stay and get acquainted.
There's nothing wrong with Nougat. Root and TWRP are possible, as well advancing us further than what the Marshmallow OS offered.
I can understand Custom Rom wise, your wanting to "Is there a way to get The Marshmallow BaseBand?" but, consider that's just water under the bridge now - never to be the same for you. In anything you'd do to achieve this would just put your device in a Mixed-State, and where an advanced user would be better adapted of dealing with that.
That's why in my 1st. post to you I was trying to encourage you to read more, let it go awhile and sink-in, and read some more getting a mental picture as you understand the depth of everything related.
Or simply sell off your now XT1575 Nougat OS device and what to look for in a stock-locked bootloader of a Marshmallow OS XT1575 device and stay there not taking an OTA of Nougat.
Even in some Custom Rom's built for a Stock Nougat Kernel and Modem there have been changes related to the TWRP version needed to be used of them.
Here gives abit about that information.
I use the NucleaROM on one XT1575 and kind of bias towards it as I've stayed with it in my first flashing of a custom rom when OTAing up to Nougat that is after failing with LOS of the jumbled up thread for clark it uses.
[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Moto X Pure 2015 (clark)
Trying to decipher this LOS thread posts of Official versus Unofficial builds, versus using Modems of MM and Nougat and talking about LOS 14.1 and 15.1 builds along the way and all the different involved posts of each Official - Unofficial unlabeled subjects there of all the posts.
It's no place for an inexperienced user to go and easily understand it.
These are the posts https://forum.xda-developers.com/showpost.php?p=75763876&postcount=1303%22]https://forum.xda-developers.com/showpost.php?p=75763876&postcount=1303 that clearly pointed out the specific information in details that helped me to know of the differences to the posts while I was active in that thread.
I like the NucleaROM because it's being based on LOS, then I can and do - do it without Google for the most part. I've not flashed any g-apps what so ever, play store is not a concern for me to use - there are other less invasive places that don't have the requirements Googles PS imposes. (F-Droid)
Even running a root file explorer I don't see anything Google related - with the way I've installed NR
Besides running an apk through Virus Total gives me peace of mind.
Android is by Google and that's were G stops with me...
NucleaROM - (root - g-apps), all are optional for the two NucleaROM builds out.
Note:It's the wakeblock app or it's folder that is mandatory to do something with in NucleaROM.
In disabling it's app in phone settings (Apps) after 1st. boot, or removing it's folder in NucleaROM's root directory via TWRP before your very 1st boot into OS where you initially setup the OS.
Did any of this help?

aybarrap1 said:
I don't know if it is possible to downgrade any parts successfully but from what little I read a month ago on it, I did not remember anything staying how to do so.
Click to expand...
Click to collapse
Don't take this as Gospel and I don't advise it since we're Post Nougat now.
As it was Pre-Nougat - but, still don't hold me to it...
A stock firmware downgrade (in the terms of) Recovery, Kernel and OS may be performed without any noticeable adverse affects.
This was prior to Nougat, every OS update changes something with a deep impact.
So I'd advise you to check in whatever thread of a Custom Rom using Marshmallow base that your interested in. To finding out any facts before hand. Notably kernel and modem related THERE IN downgrading from Nougat to using it...
As too with what's been said - Once bootloader.img and gpt.bin are updated - there is no reverting them back (DOWNGRADING) without a serious likelihood in risk to having a hard-bricked device. You'd need to skip those parts in the downgrade commands used of your flashing sequence.
I have no real world practical application of experience doing this - just reading about it or book knowledge - that ain't squat to help in a time of trouble if that's what it yields...

ResistanceIsFutile said:
Don't take this as Gospel and I don't advise it since we're Post Nougat now.
As it was Pre-Nougat - but, still don't hold me to it...
A stock firmware downgrade (in the terms of) Recovery, Kernel and OS may be performed without any noticeable adverse affects.
This was prior to Nougat, every OS update changes something with a deep impact.
So I'd advise you to check in whatever thread of a Custom Rom using Marshmallow that your interested in. To finding out any facts before hand. Notably kernel and modem related THERE IN downgrading from Nougat to using it...
As too with what's been said - Once bootloader.img and gpt.bin are updated - there is no reverting them back (DOWNGRADING) without a serious likelihood in risking to having a hard-bricked device. You'd need to skip those parts in the downgrade commands of your flashing sequence.
I have no real world practical application of experience doing this - just reading about it or book knowledge - that ain't squat to help in a time of trouble if that's what it yields...
Click to expand...
Click to collapse
Thanks. As I mentioned earlier, I had planned on potentially using custom ROMs but I have decided to stay stock rooted. I just don't get that much into customization so a custom ROM just doesn't make sense for my purposes.

There's a change in the wind with Oreo...
aybarrap1 said:
Thanks. As I mentioned earlier, I had planned on potentially using custom ROMs but I have decided to stay stock rooted. I just don't get that much into customization so a custom ROM just doesn't make sense for my purposes.
Click to expand...
Click to collapse
Your happy with the stock Nougat - as I've said there's nothing wrong with it.
I get it and respect your decision to do just that in staying with a stock Nougat.
Custom ROMs aren't merely for customization's, back in the day especially with the array of cheaper devices it was the norm though. To make it in ones liking of a polished look or for performance enhancements.
The added themes and applications preinstalled by a manufacturer were reduced to almost nothing. This saved a lot of memory space and increased the device's performance, then with being able address the questionable UI design decisions that a manufacturer had made.
Besides with the XT1575 Moto X Pure, you needn't worry much about Motorola's manufacturers bloat and being skinned to something hideous and repulsive. By that, I mean your not dealing with and like the other manufacturers (tweaking Androids OS) add/remove/change the interface and apps to make it their own highly styled branded system.
Customization's was a way to truly make a phone your own and still is...
After installing a Custom ROM on Android you are the Admin of your Device which means no Objections, no Restrictions, and basically nothing hampering you as your free to do anything with your Android device.
But, customization's is only one facet in the equation to consider with a custom rom.
Taking a view of all devices in the realm of Custom ROM's offered to each (not just an MXP), there's something more also to be gained.
Updates:
One of the most frustrating things about owning an Android device is waiting for your manufacturer to push an update to your phone, so you can get the latest features. The newer versions of Android are not only interesting because they bring new features but, also because they fill security gaps.
Often times manufacturers will even cut support for your device entirely (thinking of Motorola's support for the MXP). This leaves you stuck with a phone on an older version of Android and less secure. The solution is a custom ROM on the newest or a newer Android version for it.
Privacy and Security:
The recent alarming News surrounding data collected by OnePlus devices (along with a second claim that the company has denied), having highlighted the amount of trust we have to place in our phones by the manufacturer itself now.
This doesn't apply more to budget phones in that they may have security problems. And even the world’s second largest smartphone manufacturer, Huawei, has recently found its US ambitions blocked by US security agencies over concerns about it's spying.
And even once you get past this, every Android user is handing over vast amounts of personal data to Google and others (App's) every single day.
[[Like I pointed out in post #7, I like the NucleaROM because it's being based on LOS, then I can and do - do it without Google for the most part. I've not flashed any g-apps what so ever.]]
Lineage OS has numerous privacy controls built in, including a Privacy Guard that restricts how apps can use your data. Plus, you can use it without Google apps if you prefer !
A custom ROM can help address your security and privacy concerns. ROMs are, or should be open source. The code is available for anyone to scrutinize. Even if you don’t have the skills to analyze it yourself, you can be assured someone will flag any privacy concerns to it's custom rom using community.
Other Benefits:
Then one can benefit possibly with Performance, Battery Life. In some cases, you might even be able to unlock new functions or find features from newer flagships ported back to older devices. These are the types of phones that rarely get updated, and are often not as well optimized as their higher end siblings.
Disadvantages:
Sure Custom ROMs have their own, it's not going to be a sunny days walk in the park everyday. Expect some rain too, like in adding an app, tweaking hidden settings of the Android's OS and like-
"many phone cameras have dual lens setups nowadays, fancy HDR effects, and high frame rate 4K video. They all need special tools to drive them, and these are all part of the phone’s manufacturers firmware. There’s no one app that you can simply lift and install on another device. Nor can you replace all of the cameras functionality with a third-party camera app."
Closing thoughts:
One of the biggest draws of custom ROMs used to be that you could install the stock Android experience on any device. You could replace the bloated software from Samsung, Huawei, or HTC and other manufacturers with a ROM based on the open source version of Android. Throw in the suite of Google apps, and you’d have something akin to a pure Android device. This is the principle around which Google’s Nexus phones were built. {In reality, Android is but one of the parts of your phone's software today, not the total sum of those parts as manufacturers hardware needs it's own drivers to function.}
But, that makes the stock Android no longer the best version of Android, even Google admits this. The best parts of the company’s Pixel phones aren’t Android. The camera app, Google Assistant, and the fast streamlined launcher are all proprietary software. They’re developed and owned by Google. In fact, on the product pages for the Pixel phones, Android barely even gets a mention there.
Custom ROMs can be wonderful for older devices but, before you decide to change your device's original manufacturers firmware you should familiarize yourself with the disadvantages of the process.
Custom ROMs are perfect for those who love a good challenge. But if this doesn't sound like you then you won't like custom ROMs. Between the devices need for security updates that custom roms can offer. Comes a need to unlock the bootloader, install a custom recovery, gain system root and dealing with unstable versions being pushed to a device, and having an active ROM maintainer.
Those are some of the things where your patience could reach its limits fast.
Not forgetting, third-party firmware (as in custom roms) comes with very few or no Google apps. The Play Store application has to be installed again if you use that source for you add-on apps.
Then hardware specific software (drivers) to make a devices hardware function properly.
So is it Your device because you've paid for it, or is it a manufacturers device with their own branded apps, style and the flair they choose for you of the price you've paid for it.
It's Your choice and decision to change it or not... :good:
PS: Devices that started to ship with OREO installed will change the custom rom landscape.
There's a change in the wind with Oreo...
Project Treble has some interesting implications for the revival of the custom ROM scene.
XDA community members are excited about the prospect that we may be edging closer to a time where Android software can be easily ported across a range of devices.
Other developers have also already shown off a single system image capable of booting on different devices with different processors.

ResistanceIsFutile said:
Not quite sure what's meant by your own meaning of Baseband. Your more than likely going to be answered by people still using the phone in different degrees of knowledge.
The experienced with a real practical application of this XT1575 device mostly have moved on to another device by now - but will any left on it be answering you. I'm glad to see @aybarrap1 has answered.
@stevejohnson42 uses the XT1575 too, and reports here and there of his flasholic tendencies on this device - might be helpful in any Nougat based ROM's to use the search box there and see if he's added anything in it.
Custom ROM Marshmallow development was always greater cause the XT1575 stayed on the Marshmallow OS for so long and because of Motorola not releasing Nougat sooner for it.
There are some Custom ROMS based on Nougat - just read their OP's to understand what's being required to using each one of them...
Nougat ROMs built for a Stock Nougat Kernel and Modem.
Click to expand...
Click to collapse
Not much to add - I share @ResistanceIsFutile comment - once you have updated - don't try to go back to earlier modem / baseband on this phone
Here is another collection that gives you choices and very clear which version to use for
https://forum.xda-developers.com/moto-x-style/development/collection-random-projects-t3662970
Personally - I flashed the stock ROM that is here ( make sure you have correct variant before doing ) :
https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
to move from Marshmellow modem - as noted above ; much more development on the original modem -- but I had a nagging issue with the Fly Delta app that could be duplicated but not something developers of custom ROMs should have spent time on - going to Nougat stock cleared it - then I went to NucleaROM almost immediately and everything worked fine
I have never tried - but , by searching xda-- you will find many active developers noting it is a good way to brick the phone .. I do not pretend to fully understand -- but have learned long ago to do research , carefully read OPs and safest to follow instructions of those who have much greater knowledge than me .
The phone is still my daily driver - I am currently on rooted stock that was installed by the method noted in the thread above. I have been on NucleaROM as DD and a good ROM ..and have flashed many posted by obsolete1. I have found with many back to back clean flashes - reflashing stock can eliminate issues that you might run into ( don't remember them all - but do recall having an issue wiping phone once )
Also - check carefully what TWRP to use - some of the ones using the Nougat modem require the unofficial TWRP that Hashbang developed for the earliest ROMs that worked on it.
We had a pretty good run on this phone and it appears there still might be a few developers looking at it .. but I understand ; most of them have moved on to other phones or the reality of life has required them to leave development for awhile
Regards

@ResistanceIsFutile
Thanks for the run down and I'm quite aware of many of these things. The MXPE in itself is a great phone with the few added features for Moto being actually somewhat useful.
I am not overly concerned with updates. If I were I would get a pixel or Android one phone.
Prior to the MXPE I had carrier branded phones and found custom ROMs to be quite useful in terms of bloat and better performance.

@aybarrap1
Only meant it peaceably - didn't mean by steps on any toes or persuade - crowd you or anyone at all.
The Moto X style/pure devices age has probably 3rd, 4th even 5th generation owners by now that have no ideal what we're talking about at times.
I then see it as a funneling effect, when I answer one it spreads out to others not knowing, especially in a threads topic as this. If you prefer I'll answer generally and not address anymore to you - I'm easy and would like to make friends on XDA - not loose any prospects.
I like and see your posts as helpful as I hope mine are, and it's encouraged to answer if you can at any experience level on XDA. So please forgive any misunderstanding or intentions on my part.
Thank you.
Everything is beneficial but not useful to all

@ResistanceIsFutile
Thanks. Reading back I see how the "tone" came across. I'm good and only intended to put out my reasons. I do have to say it is good you post this info as it was posts like yours that helped me a lot when I first started looking into rooting and custom ROMs some many years ago (LOL...7 or 8 years only but in terms of phone tech that is a very long time).

Comprehensive step by step guide to flash custom ROM for Moto G5 Plus

Hi all.
I have a Moto G5 Plus(XT1687) that I would like use a custom ROM on. In fact I bought a second one to specifically do this with. I have only done this once with a Samsung Galaxy S5 and the MicroG version of LineageOS 14.1
With the Moto G5 Plus there are some extra steps from what I gather(you have to get permission from Motorola in order to unlock the bootloader is one example). And there are some intimidating things that I am just unsure about - such as to install Arrow you have to have Oreo 8.1 installed - but when you unlock the bootloader it wipes the phone? So how is this possible? Do I have to install the stock Oreo ROM first? Where do I get the stock ROM?
I have done a couple of months of searching for guides but have found different instructions and some with broken links to software on google drives or other sites I am not sure are safe. I asked about on the subreddit for Moto G and they pointed me here(which I have read a lot here over the past several months.).
Here is what I know:
1) I will need to enable developer options and USB debugging on the phone
2) I will have to get a code from the phone through abd and fastboot. In order to unlock the bootloader, I have to contact Motorola. give them a code and they will send me a code in order to do so(correct?)
3) I need to install TWRP in order to flash any ROM and other software, such as Gapps.
What I am asking of the community:
1) Legitimate link to the software needed.
2) Recommendations for ROMs. What do I want? I want to get be able to get out of the clutches of Google as much as possible. I understand that Android is Google, but most of the custom ROMs have removed most of the Google code. There is not a ROM from the MicroG website for Potter, which is what I really wanted(is this just LineageOS with thew micro Gapps?) I also have found replacement apps for almost all of my normal apps in the F-Droid repository. Ones I have studied: LineageOS(no official for Moto G5 Plus), Arrow OS, HavocOS and RessurectionOS. I have heard there are many out there. Important to have the actual phone part working well.
3) What is the differences in the different Gapps packages(Open Gapps, Mind the Gapps)?
4) What is this magisk I keep on reading about? Is that just for root? And don't you need root to install TWRP?
5) A step by step guide to make sure I don't jack this up. Even though this is my 'play' phone, I would like it to become my daily driver and plan on getting a SIM card as soon as I can get a stable OS on it.
6) Any tips or recommendations for someone like me.
I appreciate any input.
Thank you.

OK, I found this, but it is over a year old.
Is the info there still relevant? Is there anything that has changed since it was posted?

one two and three of what you know is ok.
The custom rom must be for the device.
On my motog5 plus I use Crdroid-Rom without Google Gapps.
Magisk is used to get root, that is, make changes and view the root of the device.
The information is valid. Rom-are outdated.

Thank you. Doing more research. Hopefully I will have a functioning device by the end of the weekend.

If you want smoothest experience try citrus-CAF its pure CAF rom its very nice smooth and fast.

Advice on going from Stock 8.1 to ABC ROM.

I recently got a 6P and have learnt a few things that are pushing me towards a custom ROM;
1. No Night Light (blue light filter) on stock.
2. No NFC quick toggle
3. Enforced encryption
4. In the event of the dreaded bootloop, I understand it's only possible to rescue the device if bootloader is unlocked.
I don't particularly want to unlock the bootloader etc as I want to be able to use Google Pay and banking apps freely, however I understand that with the use of Magisk this shouldn't be a problem.
I've rooted etc many devices since Android 2 but I'm aware that each device has its quirks.
Basically (TLDR):
What do I need to know/do to get from Stock to ABC rom with with Google Pay etc working fully?
Thanks for your help!

Just found this thread:
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Is all of that still accurate? Anything else on top of that worth knowing?

tooplanx said:
Just found this thread:
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Is all of that still accurate? Anything else on top of that worth knowing?
Click to expand...
Click to collapse
As far as flashing 8.1 devices? Yeah, based on when this device was made the unlock and flash process was nice and simple.
Don't be surprised if some stuff won't work with an unlocked BL though. Yeah root can hide itself but some safety net checks are better than others and they look at the BL. I don't use banking apps on an unsafe phone, but I still see people every once in a while posting about *whatever* app they use does not work due to safety net.
Do not use above as a reason to lock your BL on a custom rom. NEVER do it.
If you descide at some point to want to move on to 9.0, do some research between FDE encryption, which is what this device has always used. And FBE encryption which some people are building 9.0 ROMs with. This will save you from me yelling at you for not being able to read an OP if you want to go to 9.0

Thanks for your reply.
I apologise for being lazy in my post. I have two small children and know from part experience that one can spend a long time collecting various patchy, out dated pieces of info from disparate, incomplete forum threads! However, it seems that there is pretty good, comprehensive tutorials for the Nexus 6p :victory:
My main questions I guess now are:
1. Do I still need to flash the vendor image if coming from stock 8.1?
2. I've heard ABC has safetynet built in... Does this mean Google Pay etc is more likely to work?
3. I can't find a link to the last ABC rom. That Kajinsk(?) Website doesn't seem to be in use anymore.
4. Is it possible to go back to fully stock with a locked bootloader if I decide to?
Thanks

tooplanx said:
Thanks for your reply.
I apologise for being lazy in my post. I have two small children and know from part experience that one can spend a long time collecting various patchy, out dated pieces of info from disparate, incomplete forum threads! However, it seems that there is pretty good, comprehensive tutorials for the Nexus 6p :victory:
My main questions I guess now are:
1. Do I still need to flash the vendor image if coming from stock 8.1?
2. I've heard ABC has safetynet built in... Does this mean Google Pay etc is more likely to work?
3. I can't find a link to the last ABC rom. That Kajinsk(?) Website doesn't seem to be in use anymore.
4. Is it possible to go back to fully stock with a locked bootloader if I decide to?
Thanks
Click to expand...
Click to collapse
If the vendor image does not match the month of the rooms security patch you get a message that pops up on the device about it, other than that I doesn't hurt anything.
No idea, again, I don't mess with stuff that checks safteynet.
Not sure on the rok quest either, can try in the thread but yeah kantjer nuked his site when he got rid of his 6p.
Yeah, just get the factory image from the Google site and fastboot flash it.

Lawlrus said:
If the vendor image does not match the month of the rooms security patch you get a message that pops up on the device about it, other than that I doesn't hurt anything.
Click to expand...
Click to collapse
Even if vendor image is newer than rom security patch? So I'd probably have to flash an older vendor image than the current OPM7.181205 so that it matches whatever the last ABC rom patch level was?
Knowing that I can go back to stock and locked bootloader makes me happier to see how things go with a custom rom. I know some devices can't be relocked fully.
Think I've found the last ABC rom image:
https://androidfilehost.com/?w=files&flid=288070

tooplanx said:
Even if vendor image is newer than rom security patch? So I'd probably have to flash an older vendor image than the current OPM7.181205 so that it matches whatever the last ABC rom patch level was?
Knowing that I can go back to stock and locked bootloader makes me happier to see how things go with a custom rom. I know some devices can't be relocked fully.
Think I've found the last ABC rom image:
https://androidfilehost.com/?w=files&flid=288070
Click to expand...
Click to collapse
As I said, I have NEVER heard of anyone having issues not being on the right vendor aside from a notification on reboot.

Okay, thanks!