Related
Folks,
This is something we should keep an eye on:
FXP article: "Finally! Boot to recovery enabled in special bootloaders from Sony"
=> http://fxpblog.co/2015/05/01/finally-boot-to-recovery-enabled-in-special-bootloaders-from-sony.html
Let's hope there will be a Z3c open bootloader in the works.
arturiu said:
Folks,
This is something we should keep an eye on:
FXP article: "Finally! Boot to recovery enabled in special bootloaders from Sony"
=> http://fxpblog.co/2015/05/01/finally-boot-to-recovery-enabled-in-special-bootloaders-from-sony.html
Let's hope there will be a Z3c open bootloader in the works.
Click to expand...
Click to collapse
While coming from an Nexus 4 and waiting for my Z3C delivery to arrive.
I just read that bootloader news, too. Would it be useful to wait some time, if Sony releases some updated bootloader?
Or perhaps better to say, are there any huge problems / differences with the current procedure of unlocking the Z3C?
I already noticed the list for unlocking and rooting is very long with respect to N4 ....
damaddy said:
While coming from an Nexus 4 and waiting for my Z3C delivery to arrive.
I just read that bootloader news, too. Would it be useful to wait some time, if Sony releases some updated bootloader?
Or perhaps better to say, are there any huge problems / differences with the current procedure of unlocking the Z3C?
I already noticed the list for unlocking and rooting is very long with respect to N4 ....
Click to expand...
Click to collapse
The "unofficial" method of installing a bootloader is currently stable, thanks to many xda contributors (check this same forum for it).
But it's not officially supported by Sony and it involves a step that invalidates the device DRM keys.
You can (and should) perform a backup of the TA partition in order to restore those keys if you want to revert to an official firmware.
What is announced there may take some time for the Z3c, and it's not guaranteed to happen. But it would certainly make things easier...
So if you want to test a different rom, you should go with the current process.
(important: do some research on this same forum, follow the instructions, and start by backing up)
As to the device itself, you won't find a gadget out there comparable in specs and size.
IMHO, it's a default choice for a compact high-end device.
are there any news about the bootloaders?
MOD EDIT by @gregbradley. I did not see the need for the expletive in the title, so i took it out for you.
So here's a little rant.
Read it if you'd like to, don't read if you don't like to.
Let's start with a little introduction. I've bought my Z3 about a year ago. I wanted to go with the z3+, but the Snapdragon 810 seemed to cause some issues. I still wanted the Sony batterylife after coming from a Galaxy S4 (which doesn't have the best battery life). I found online that Sony shares AOSP source code, so building a custom rom shouldn't be too hard.
Recently I have thought about unlocking my bootloader, but reading further into it, I found there to be NO upsides to unlocking your bootloader.
- There's a possibility of losing your DRM Keys when unlocking bootloader.
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Maybe I'm just nitpicking, but this seems very hypocritical from Sony..
C'mon Sony, your mobile department isn't doing too well, and this sure as hell doesn't make it better.
Now I know there are maybe only several thousand people actually wanting to run AOSP on their Sony, but I sure as hell am not buying another Sony phone until this policy changes.
Thanks.
Joost
Im still trying to figure out which part you unhappy about lol ?????
I have the Z3 rooted with Android 6.0.1 Slim1.6 Rom LB
And its the best ever with longest battery life ive experienced no issues fast and smooth
I dont want any other phone right now what more could you want?
MasterCMTS said:
Im still trying to figure out which part you unhappy about lol ?????
I have the Z3 rooted with Android 6.0.1 Slim1.6 Rom LB
And its the best ever with longest battery life ive experienced no issues fast and smooth
I dont want any other phone right now what more could you want?
Click to expand...
Click to collapse
My issue?
On one hand Sony releases AOSP code, while on the other hand they make it a real damn pain in the ass to even run an AOSP rom. There have been several developers out there to try and build an AOSP rom. None of them managed to make a fully working one, because Sony made it so damn hard. I find this hypocritical and unjust.
What I want is for Sony to make it actually possible to run an AOSP rom, and stop pretenting like it's possible.
Me Gusta said:
So here's a little rant.
Read it if you'd like to, don't read if you don't like to.
Let's start with a little introduction. I've bought my Z3 about a year ago. I wanted to go with the z3+, but the Snapdragon 810 seemed to cause some issues. I still wanted the Sony batterylife after coming from a Galaxy S4 (which doesn't have the best battery life). I found online that Sony shares AOSP source code, so building a custom rom shouldn't be too hard.
Recently I have thought about unlocking my bootloader, but reading further into it, I found there to be NO upsides to unlocking your bootloader.
- There's a possibility of losing your DRM Keys when unlocking bootloader.
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Maybe I'm just nitpicking, but this seems very hypocritical from Sony..
C'mon Sony, your mobile department isn't doing too well, and this sure as hell doesn't make it better.
Now I know there are maybe only several thousand people actually wanting to run AOSP on their Sony, but I sure as hell am not buying another Sony phone until this policy changes.
Thanks.
Joost
Click to expand...
Click to collapse
You can use TA Backup to restore your DRM keys as long as you back them up before unlocking the bootloader ('m just about to do it)
You can install a custom recovery via fastboot (I used TWRP to replace cyanogen recovery).
Not really sure your points to be honest.
savo83 said:
You can use TA Backup to restore your DRM keys as long as you back them up before unlocking the bootloader ('m just about to do it)
You can install a custom recovery via fastboot (I used TWRP to replace cyanogen recovery).
Not really sure your points to be honest.
Click to expand...
Click to collapse
Sure, you can restore DRM.. but is it really convenient? My point is that Sony basically promotes AOSP roms by releasing source code, but on the other hand they make it impossible to enjoy a fully working AOSP rom because of DRM, camera's never working, etc..
Oh, and if you could explain to me how you flashed TWRP, and which file exactly, that'd be great . I've literally already spent 6 hours today trying to figure **** out after unlocking my bootloader..
Thanks in advance!
I totally agree with you. Building an AOSP ROM for Z3 seems to be difficult (Tried cm too but extracting proprietary blobs did not work). The way how recovery works here is pretty stupid, seeing that we dont have a recovery on N for example, so I need to be on it without root (i dont blame developers here, but again, Sony's implementation). Also I haven't been able to work around the radio or camera thing in AOSP, even though I have only been able to build the ROM like once some weeks ago
---------- Post added at 06:00 AM ---------- Previous post was at 05:55 AM ----------
Me Gusta said:
Sure, you can restore DRM.. but is it really convenient? My point is that Sony basically promotes AOSP roms by releasing source code, but on the other hand they make it impossible to enjoy a fully working AOSP rom because of DRM, camera's never working, etc..
Oh, and if you could explain to me how you flashed TWRP, and which file exactly, that'd be great . I've literally already spent 6 hours today trying to figure **** out after unlocking my bootloader..
Thanks in advance!
Click to expand...
Click to collapse
Also the recovery thing. Just download the .img from Nailyk's thread and put it in ADB folder. Then go to fastboot and type fastboot flash FOTAKernel . Then boot to recovery by pressing power and volume down button, releasing power when phone vibrates and volume when sony logo appears.
Me Gusta said:
- There's a possibility of losing your DRM Keys when unlocking bootloader.
Click to expand...
Click to collapse
That is true and disappointing. However, there is a way to backup the keys and restore whenever the need arises.
Me Gusta said:
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
Click to expand...
Click to collapse
fastboot oem lock or restoring the DRM keys should relock the bootloader.
Me Gusta said:
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
Click to expand...
Click to collapse
Sure it works, you just need to run 23.4.A.1.264 firmware or newer. I use fastboot flash recovery something.img all the time.
Me Gusta said:
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Click to expand...
Click to collapse
I think the Concept software is for those who don't need Sony enhancements (X-Reality, ClearAudio+, etc.) and want something that is close to stock.
So:
-You can backup and restore DRM functions even with an unlocked BL.
-You can relock BL again (haven't tried it myself but I think it's possible, if you check out DRM restoration guides I think they also show how to relock the BL)
-The new Sony BL allows fastbooting recoveries, the older ones support FOTA recoveries (I've used both with no problems)
-The MM concept project is still live, you can install it and continue using it, it gets updated regularly and is very close to AOSP.
-True Sony is kind of shady with their sources but you can build AOSP, there are AOSP builds for the Z3 here: http://fxpblog.co/ they get released whenever Sony releases new sources but you can also make builds yourself. The only true issue with sources comes out on certain AOSP functions and that we don't have (yet) fully working CM13 builds. As for the concept firmware it's exactly what you said, Sony is giving it out to people who are interested in having a close AOSP experience with support from the vendor while giving feedback to further improve it. Sony is making moves and is becoming more developer friendly by the month, other than new and constantly updated sources, proof of this is the Xperia Z3 is the only non-Nexus device that gets to run the Android N preview officially given from the vendor.
The Z3 is a great device, I personally haven't regreted the purchase, the only thing that bugs me is that neither I nor anyone else has managed to build a fully functional CM13 build (kudos to infected btw).
---------- Post added at 09:02 AM ---------- Previous post was at 08:58 AM ----------
Evokkimus said:
I totally agree with you. Building an AOSP ROM for Z3 seems to be difficult (Tried cm too but extracting proprietary blobs did not work). The way how recovery works here is pretty stupid, seeing that we dont have a recovery on N for example, so I need to be on it without root (i dont blame developers here, but again, Sony's implementation). Also I haven't been able to work around the radio or camera thing in AOSP, even though I have only been able to build the ROM like once some weeks ago
---------- Post added at 06:00 AM ---------- Previous post was at 05:55 AM ----------
Also the recovery thing. Just download the .img from Nailyk's thread and put it in ADB folder. Then go to fastboot and type fastboot flash FOTAKernel . Then boot to recovery by pressing power and volume down button, releasing power when phone vibrates and volume when sony logo appears.
Click to expand...
Click to collapse
As I said fxp has some builds, I haven't tested them but I think they work (http://fxpblog.co/)
I was eager to try out FXP's aosp ROM, due to 3.10 kernel and such, but I got an error about updater-script in META-INF, didn't read further. I have my suspicions that it was a bad download, but their current site is so slow to download from (about 2 hours to download, and only a +20kb/s faster if you register), and i'm not going to pay for that site. If it helps any, i just wiped data, system and caches and tried flashing the ROM.
---------- Post added at 12:14 PM ---------- Previous post was at 11:56 AM ----------
CedArctic said:
So:
-You can backup and restore DRM functions even with an unlocked BL.
-You can relock BL again (haven't tried it myself but I think it's possible, if you check out DRM restoration guides I think they also show how to relock the BL)
-The new Sony BL allows fastbooting recoveries, the older ones support FOTA recoveries (I've used both with no problems)
-The MM concept project is still live, you can install it and continue using it, it gets updated regularly and is very close to AOSP.
-True Sony is kind of shady with their sources but you can build AOSP, there are AOSP builds for the Z3 here: http://fxpblog.co/ they get released whenever Sony releases new sources but you can also make builds yourself. The only true issue with sources comes out on certain AOSP functions and that we don't have (yet) fully working CM13 builds. As for the concept firmware it's exactly what you said, Sony is giving it out to people who are interested in having a close AOSP experience with support from the vendor while giving feedback to further improve it. Sony is making moves and is becoming more developer friendly by the month, other than new and constantly updated sources, proof of this is the Xperia Z3 is the only non-Nexus device that gets to run the Android N preview officially given from the vendor.
The Z3 is a great device, I personally haven't regreted the purchase, the only thing that bugs me is that neither I nor anyone else has managed to build a fully functional CM13 build (kudos to infected btw).
---------- Post added at 09:02 AM ---------- Previous post was at 08:58 AM ----------
As I said fxp has some builds, I haven't tested them but I think they work (http://fxpblog.co/)
Click to expand...
Click to collapse
I also tried building CM but stuck on proprietary blobs part. Couldn't pull them from the device for some reason, even though i was on CM rom at the time. (I did it because breakfast ended up in some vendor errors and Z3 didnt show up on the list either)
Evokkimus said:
I also tried building CM but stuck on proprietary blobs part. Couldn't pull them from the device for some reason, even though i was on CM rom at the time. (I did it because breakfast ended up in some vendor errors and Z3 didnt show up on the list either)
Click to expand...
Click to collapse
Weird, I build CM12.1/CM13.0/twrp 3 with theMuppet repo without a glitch. Can you paste your compilation error in a pastebin or something like this? Maybe I can help you a little (I'm a compilation newbie)
nailyk said:
Weird, I build CM12.1/CM13.0/twrp 3 with theMuppet repo without a glitch. Can you paste your compilation error in a pastebin or something like this? Maybe I can help you a little (I'm a compilation newbie)
Click to expand...
Click to collapse
Basically the error I get is with extract-files.sh. When I run "./extract-files.sh" while phone is plugged in, I get permission denied. The other option for me is to run it with sudo, but then I get "line XX adb: command not found" (many lines of this error). Someone suggested chmod or opening a terminal window inside the folder where extract-files.sh is located. There shouldn't be any errors with my AndroidSDK path, even though some suggest the error is with this.
Also the reason I'm trying to pull these blobs, is because the CM tutorial told me so
{
"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"
}
https://wiki.cyanogenmod.org/w/Build_for_z3
------------------------------------------------------------
Also the reason I'm building CM is because I still don't know how to get radio working, even though a person has told how to get it working, I don't know how to exactly do it. But firstly I would like this CM thing to work. Thanks for your help.
Evokkimus said:
Also the reason I'm building CM is because I still don't know how to get radio working, even though a person has told how to get it working, I don't know how to exactly do it. But firstly I would like this CM thing to work. Thanks for your help.
Click to expand...
Click to collapse
No worries.
So it may be a little more complicated.... If you just need a functional self build CM, try to include themuppet repo. If your device variant is not currently officially supported it can be more complicated.
I suggest you to open (or find) a dedicated thread and quote me, or join #[email protected]
Otherwise I'm following this thread because I found some point really interesting. I'm currently in trouble with Sony, that's why I subscribe.
Sorry for off-topic answers.
sorry did not see the date
arminbih said:
sorry did not see the date
Click to expand...
Click to collapse
Customer service troubles. They didn't respect law about unlocked bootloader into my country and refused to fix my device.
I know this thread is basically dead but I figured I'd poke it with a stick a few times and give my two cents.
First of all, the reason I chose Sony. I peviously owned Galaxy S4 and at some point (Android 4.2.2?) they implemented a security software called KNOX. It lets you create encrypted partitions for business stuff. Soon after, users started reporting that any unofficial changes result in a "0x01" flag showing in the download mode. Turns out, the device has a physical e-fuse which is burned and can not be reverted (except with a motherboard change). It was mainly for the customer services to be able to tell if the phone had been tampered with. But here's the catch - it was also triggered when installing official Samsung firmware using ODIN (basically FlashTool or Emma for Samsung). And downgrading firmware to pre-KNOX resulted in a special lock - the inability to upgrade again.
XDA members, such as Chainfire and others, have not managed to crack the software after several years, despite the bounty of thousands of dollars. I didn't think much of it, and rooted. Months after that my phone stopped recognizing the SIM card. And since I had "0x01" I had no warranty. So it went to customer service many times, I paid for the SIM reader change, and still nothing. Even custom ROMs didn't help.
So, I had a phone with no SIM support, and no faith in Samsung. I found out that Sony "encourages Android development" - bootloader unlocking and so on. Soon after I bought a Z3, and being a power user, I wanted to root. And then I found out about the DRM. The more I researched, the more livid I got. Finally I managed to dig up a method of rooting without bootloader unlock. After every small update Sony issued, I had to go through hours of researching and developing a new cusom update for my device. After some time I just decided to go with a (back then unreliable) DRM function restoring flashable zip.When I heard there will be no Nougat for Z3, I was quite mad. I looked into some AOSP's. NONE of them were working correctly. So I settled with a Z3 on unlocked BL with some DRMs working. The device has hiccups but is usable. I am disappointed in Sony and I am disappointed in Samsung. Never buying their phones again.
But now that @nailyk is developing LineageOS for Shinano devices, we have new hope! :victory:
The Android Robot said:
I know this thread is basically dead but I figured I'd poke it with a stick a few times and give my two cents.
First of all, the reason I chose Sony. I peviously owned Galaxy S4 and at some point (Android 4.2.2?) they implemented a security software called KNOX. It lets you create encrypted partitions for business stuff. Soon after, users started reporting that any unofficial changes result in a "0x01" flag showing in the download mode. Turns out, the device has a physical e-fuse which is burned and can not be reverted (except with a motherboard change). It was mainly for the customer services to be able to tell if the phone had been tampered with. But here's the catch - it was also triggered when installing official Samsung firmware using ODIN (basically FlashTool or Emma for Samsung). And downgrading firmware to pre-KNOX resulted in a special lock - the inability to upgrade again.
XDA members, such as Chainfire and others, have not managed to crack the software after several years, despite the bounty of thousands of dollars. I didn't think much of it, and rooted. Months after that my phone stopped recognizing the SIM card. And since I had "0x01" I had no warranty. So it went to customer service many times, I paid for the SIM reader change, and still nothing. Even custom ROMs didn't help.
So, I had a phone with no SIM support, and no faith in Samsung. I found out that Sony "encourages Android development" - bootloader unlocking and so on. Soon after I bought a Z3, and being a power user, I wanted to root. And then I found out about the DRM. The more I researched, the more livid I got. Finally I managed to dig up a method of rooting without bootloader unlock. After every small update Sony issued, I had to go through hours of researching and developing a new cusom update for my device. After some time I just decided to go with a (back then unreliable) DRM function restoring flashable zip.When I heard there will be no Nougat for Z3, I was quite mad. I looked into some AOSP's. NONE of them were working correctly. So I settled with a Z3 on unlocked BL with some DRMs working. The device has hiccups but is usable. I am disappointed in Sony and I am disappointed in Samsung. Never buying their phones again.
But now that @nailyk is developing LineageOS for Shinano devices, we have new hope! :victory:
Click to expand...
Click to collapse
Lots of OEM are doing this stuffs to protect their intellectuals rights with DRMs. AFAIK oneplus allow bootloaders unlock.
Just for fun, the TA partition of sony contain so much things... It is crazy! BTW I think we have fuse too
idk where you live but in Europe there is a law which basically said: hardware and software are separated and OEM need to fix hardware, except if they can prove this is user fault.
1999/44/CE in date of 1999-05-31.
Many devices tend to loose picture quality when unlocked, it never happened to me with my previous devices but I need to ask to users here if it will happen with the g4 plus,
I am talking about the picture quality in stock ROM here, will an unlocked bootloader affect the picture quality of stock ROM?
Sent from my Moto G (4) using Tapatalk
Unlocking the bootloader does nothing (zero changes) to the actual system files. It won't affect the "quality" of pictures.
The only time when, after unlocking, picture quality decrease is when using a ROM/firmware that doesn't integrate the correct blobs for camera or the native app - this is the case with some (most) CM/Lineage ROMs.
Unlocking the bootloader will not affect the picture quality. Changing ROMs can affect picture quality though , depending on the libraries and the camera app. I faced the same issue initially, but eventually it got better.
Thanks for your answers ?
Couple of questions
1. Is the 22/5 build of LOS stable, means is everything working?
2. Can I relock bootloader and reclaim warranty?
Sent from my Moto G (4) using Tapatalk
Haven't tried LOS but as far as the second question is concerned, it's better you keep your bootloader unlocked since problems may arise with locked bootloader and custom ROM, and AFAIK you cannot flash any custom file with a locked bootloader. Plus you won't gain much by locking your bootloader...(correct me if I have stated anything wrong)
pooniaprashant said:
Thanks for your answers
Couple of questions
1. Is the 22/5 build of LOS stable, means is everything working?
2. Can I relock bootloader and reclaim warranty?
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
In addition to what nlp931 has mentioned, re-locking your bootloader will not recover your warranty. Motorola has a record of the unlocking and thus voiding of the warranty - there are reports of some users re-locking their devices and being able to claim warranty repairs. How much of that was up to the discretion of the service centre, the repair performed or simply looking at the receipts (rather than checking the IMEI), I don't know. Also, relocking (and unlocking again) may wipe your device.
I concur though that re-locking a bootloader is only advisable with stock firmware - given the verification checks performed at boot, having anything custom (be it recovery, system or kernel) may trip those checks and render your device unable to boot!
Having a quick look through the posts around the 22/05 LineageOS release, looks like there's not much in the way of bugs (call recording isn't working still, it seems) and Moto camera won't work without deleting of .jar files (or you could flash the patched camera app https://forum.xda-developers.com/moto-g4-plus/themes/stock-motorola-camera-t3596659). Additionally, as mentioned above in the thread, the camera quality may be subjectively different to stock. If you're looking to theme LineageOS, there's the OMS version too with Substratum support: https://forum.xda-developers.com/moto-g4-plus/development/unofficial-lineageoms-14-1-athene-t3598237 I don't think the OMS and official builds are compatible with each other though (on a side note, the OMS build is newer than the official build at the moment )
Oh, as with any custom ROM, if you've got a G4 Plus, ensure you've updated to Nougat before flashing the custom ROM, else you're likely to run into fingerprint enrolment issues....
1. When you unlock the bootloader, you provide the serial to Lenovo in exchange for the unlock code. And you will click on a agreement that says that you will loose the warranty. They keep that record on their servers, re-locking will not erase that.
2. With any LOS firmware you will have issues with camera, the drivers for that are proprietary, you are stuck using generic drivers.
So, from searching this forum it seems like people think the V20 doesn't support Treble. I've seen articles that state with Oreo it will. I am running the unofficial Los 15.1 build and downloaded the app that checks for Treble compatibility and it states my phone is treble ready though I don't have the A/B setup. Now looking at treble project builds there are many that state they are a only as well as a/b.
So, is the rooted v20 treble ready with Oreo firmware?
Also, when I do this cmd in terminal - getprop ro.treble.enabled, it returns true.
Is it possible, yes, will they do it, probably not.
You can set the boot LUN now, without Oreo, and force the phone to boot from the *bak partitions (xblbax, abootbak, lafbak, recoverybak, etc)
Notice there is one important partition missing .. bootbak. We don't have it. That would require the phone to be repartitioned, and I just don't see LG risking that.
It is hard enough to repartition a UFS NAND via a firehose, it would be insane to try it via an OTA update.
-- Brian
Thanks Brian. Guessing these treble check apps should have a big warning plastered on them for the less savvy in the android intricacies such as myself. Glad I posted before going ham on trying to install Treble roms
Actually we have xbl2 and xbl2bak that could be repurposed. They aren't actually used as part of the boot process (they are identical copies of xbl and xblbak).
However, that still leaves system. In order to have a systembak, they would have to shrink userdata which is currently 52.2G, so plenty of room, but that is VERY risky.
Again, though, this is very doable. Heck, even if they don't do it, the AOSP builds for the V20 could support it with the tweaks stated above.
-- Brian
runningnak3d said:
Actually we have xbl2 and xbl2bak that could be repurposed. They aren't actually used as part of the boot process (they are identical copies of xbl and xblbak).
However, that still leaves system. In order to have a systembak, they would have to shrink userdata which is currently 52.2G, so plenty of room, but that is VERY risky.
Again, though, this is very doable. Heck, even if they don't do it, the AOSP builds for the V20 could support it with the tweaks stated above.
-- Brian
Click to expand...
Click to collapse
So, does the V30 have all these partitions set up? It's my understanding that the V30 is definitely going to be treble supported so I'm curious if it already has these partitions in place or needs modifying (in which case I imagine some crafty bastard will be able to replicate the process).
Or along those lines, several of the supported current phones I don't believe shipped with Oreo so they had to undergo the reformatting process, I wonder if there's anything to glean from them. I'll have to see if I can wrap my head around this whole deal.
Also, is this what we are lacking? https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
Wow, I should really drink at least 3 cups of coffee before posting.
What I was referring to was A/B system updates which I swore had a code name, but damn if I can find it now.
Anyway, yes, even Project Treble will still require repartitioning since we don't have a vendor partition (vendor is on system). Much easier to implement than A/B system updates, but I still don't think LG will do it.
We will just have to wait and see...
EDIT: good read on A/B system updates: https://source.android.com/devices/tech/ota/ab/ab_implement
-- Brian
LG may not add /vendor partition, but if you put the pieces together from some of the posts around the dev section theres work being done to add one in Lineage, though it hasnt been done yet.
runningnak3d said:
Anyway, yes, even Project Treble will still require repartitioning since we don't have a vendor partition (vendor is on system).
Click to expand...
Click to collapse
Just FWIW, Treble doesn't necessarily require repartitioning.
PhantomGamers said:
Just FWIW, Treble doesn't necessarily require repartitioning.
Click to expand...
Click to collapse
i've been following project treble for sometimes and there are lot of misunderstanding
1. having custom oreo roms doesnt mean you had treble support. it is true most treble phone coming with oreo by default
2. even if your phone has official oreo rom doesnt mean it support treble project ( like samsung S8 or note 8)
3. there are some devices with unnoficial treble support like oneplus devices but it still in development and as brian said we need repartition and needs lot of work. and your link above still on experiment.
i didnt say its impossible, but its far away for our devices not to mention we still need to dealing with ARB and lafs. just hope more devs joining on LG development and not rush them ( i saw lot of people doing that on brian's thread) . remember they did it for free while risking their devices on the process.
Loopback mounting is by far the safest method. You mess that up, and you phone just doesn't load the OS. You try and shrink a partition, and you mess up, and you could be toast. It isn't just shrinking, you also have to add a new entry to the GPT .. that is dangerous.
Also, if you do succeed, you will never be able to flash a stock ROM unless you put things back. For one thing stock system would no longer fit
-- Brian
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
walidham said:
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
Click to expand...
Click to collapse
Has someone tried this? Sorta feels like he just took that article and just keeps adding phone models to it without trying it.
walidham said:
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
Click to expand...
Click to collapse
I saw that article -- and had also come across phhusson treble_experimentations on github -- and am also wondering if anyone has tried it for the LG V20, in particular the H918. LG V20 is not listed in the vendor-HAL directory of the github repo. I'd love to hear from anyone who has tried this with the H918.
stcr1 said:
I saw that article -- and had also come across phhusson treble_experimentations on github -- and am also wondering if anyone has tried it for the LG V20, in particular the H918. LG V20 is not listed in the vendor-HAL directory of the github repo. I'd love to hear from anyone who has tried this with the H918.
Click to expand...
Click to collapse
you can't just grab random drivers (that's what these HALs are) and hope they fit your device. x86cpu got close to a working treble implementation, but LG's camera drivers wern't compatible and has since put off that project and is working more on lineage 16 (pie). IF LG ever does release a stock version of pie, perhaps a newer version of the camera driver might be compatible, but perhaps not.
Phoenix591 said:
you can't just grab random drivers (that's what these HALs are) and hope they fit your device. x86cpu got close to a working treble implementation, but LG's camera drivers wern't compatible and has since put off that project and is working more on lineage 16 (pie). IF LG ever does release a stock version of pie, perhaps a newer version of the camera driver might be compatible, but perhaps not.
Click to expand...
Click to collapse
OK. Got it. So it seems that LG is going to give the V20 a Pie update. There are announcements to that affect. Assuming LG follows through, the Pie update may or may not be Treble compatible. With Oreo, device OEMs were required (??) to be Treble compatible on new Oreo devices, but could provide non-Treble Oreo updates to existing devices. That's what I gathered. So with Pie, what you are saying is that it will be the same: OEMs are not necessarily going to package Treble support in Pie updates to existing devices. But if LG does provide a Pie update, AND if the update is Treble compatible, then things will be easy-peasy for ROM developers to port their wares to it because drivers -- like the troublesome camera driver -- will be abstracted and basically have the same abstraction across all Android devices. Is that right?
stcr1 said:
OK. Got it. So it seems that LG is going to give the V20 a Pie update. There are announcements to that affect. Assuming LG follows through, the Pie update may or may not be Treble compatible. With Oreo, device OEMs were required (??) to be Treble compatible on new Oreo devices, but could provide non-Treble Oreo updates to existing devices. That's what I gathered. So with Pie, what you are saying is that it will be the same: OEMs are not necessarily going to package Treble support in Pie updates to existing devices. But if LG does provide a Pie update, AND if the update is Treble compatible, then things will be easy-peasy for ROM developers to port their wares to it because drivers -- like the troublesome camera driver -- will be abstracted and basically have the same abstraction across all Android devices. Is that right?
Click to expand...
Click to collapse
LG released oreo without treble support, LG releasing a pie update for the V20 is doubtful at best and if they do it more than likely it won't have treble support either
Sent from my LG-H910 using XDA Labs
walidham said:
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
Click to expand...
Click to collapse
warwagon19792 said:
Has someone tried this? Sorta feels like he just took that article and just keeps adding phone models to it without trying it.
Click to expand...
Click to collapse
stcr1 said:
I saw that article -- and had also come across phhusson treble_experimentations on github -- and am also wondering if anyone has tried it for the LG V20, in particular the H918. LG V20 is not listed in the vendor-HAL directory of the github repo. I'd love to hear from anyone who has tried this with the H918.
Click to expand...
Click to collapse
I did know of someone who tried this. And it seemed to work but it never passed from the booting animation screen. He tried to go back and the phone was rendered useless. (and he was a developer). SOOOOO no.... I don't recommend attempting this.
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).