Related
Hi guys you know if it's possible to port cm 11.? If yes why nobody port Already?
Sent from my SM-P605 using XDA Free mobile app
It is an easier task for SM-P605 since it uses S800 CPU which has open source-ish drivers which can help devs a lot while compiling a rom from source. Looks like nobody wants to take on this yet since it requires lots of time and knowledge
SM-P600 & P601 & P602 are a bit unlucky since they use Exynos CPU's which we have less source and experience on. Somebody can port from Note 3 with experience in porting (should be easier than building ground-up drivers for now).
Cyanide? Rotfl
On a serious note though...
There have been (successful) bounties for new roms recently and I wonder if we could also get some CM / AOSP love
All we need is a willing CM dev & another bounty, right?
(I'm still on stock, no root, no knox tripping and I don't void my warranty for a touchwiz rom... I would for a CM / aosp rom + kernel though...)
edit: a working CM or AOSP rom + kernel would probably also attract more devs, since most roms are based on either one of them (e.g. slim, paranoid android, etc are all based on AOSP [with their own modifications of course])
I want to port it, but i'm not able to port a fully working ROM, and not have time to fix all.
Sent from my Nexus 5 using XDA Free mobile app
Wasn't clear from your post, did you try to port it but not get things working?
I will probably attempt to port CM11 to the P605. I just got one, and I've worked on OmniROM in the past but this is the first time I have tried to bring up a device from scratch so it will take some time (well, not really from scratch, I'm banking on the fact that the Note 3 and Note 10.1 2014 are quite similar so that that might hopefully save me some time). The other issue for me specifically is that the seal on the box was already broken when I got it so I might want to try to return it, if any issues crop up. So first I need to figure out if I can root it without tripping Knox so that I can do some diagnostic stuff and try and figure out if the device has any problems and/or was a returned device.
But if we're lucky, I think I can port CM, though most likely I won't have a lot of time to do this until mid-June so before then I'll just see what I can do in a short amount of time. Afterwards I'll attempt bringing up Omni as well but I'll attempt CM first since CM actually supports the Note 3 LTE (I tried doing an Omni bringup for Note 3 too, but ran into some issues and haven't had time to debug further).
Just noticed that cyanogenmod is apparently already working on a galaxy note 3 exynos build ( http://www.cyanogenmod.org/blog/this-week-in-cm-apr-26-2014 ) and since note 3 and note 10.1 2014 share the same hardware, i'm sure someone will be able to port it
(Xluco is doing pretty much the same thing with his kernel... porting features over from a note 3 exynos kernel)
I'm quite excited for this, cm will be reason enough for me to finally root my device and like I said a working cm rom + kernel will probably attract more devs (since a lot of roms are based on cm) [emoji106]
Gesendet von meinem SM-P600 mit Tapatalk
lets face it, droid turbo community is dead , nexus 5 with SD 800 have android O !
while our much powerful OG droid stuck on MM or N, and i am not talking about 25$ , it's just xda is the place were you get stuff for free , that's just sad seeing a good device feed away.
droid_ulti said:
lets face it, droid turbo community is dead , nexus 5 with SD 800 have android O !
while our much powerful OG droid stuck on MM or N, and i am not talking about 25$ , it's just xda is the place were you get stuff for free , that's just sad seeing a good device feed away.
Click to expand...
Click to collapse
I'm sorry that you failed to include that in your purchase price . That's your fault.
If Bootloader unlock is that important to you you would've researched and known the cost.
Blame Verizon -- they are the ones that locked down the Bootloader on the droid turbo. The other Quarks have free Bootloader unlock, courtesy of Motorola. Sunshine devs gave Droid Turbo bootloader unlock, so they could join the party. Without them, Droid Turbo would still not have bootloader unlock -- like the Droid Turbo 2.
The XT1250 is identical to the Droid Turbo, with all the Verizon bands, and runs on Verizon just fine. The XT1225 has more LTE and HSPA bands than the Droid Turbo XT1254.
You didn't research before buying.
Quark will also get Oreo, so I don't understand your point there. All LOS-based Quark ROMs are compatible with all Quarks.
Maybe you don't don't about the OTHER Quark forum on XDA? All the dev work is over there. And it's also for the Droid Turbo.
Sent via open market LG US998 V30/V30+
lol man , you missing the point , i don't have issue with paying 25$ in fact my droid is boot-loader unlocked right now using sunshine , the point is community is dead we don't have a variety of roms like the same era phones such as htc m8 and smasung s5 and z2/z3 nexus 5/6 etc , even my 2012 lg l3 have more roms droid turbo, the unlocking boot-loaeder and sunshine was obstacles against all this wonderful hacking and moding things we could do.
droid_ulti said:
lol man , you missing the point , i don't have issue with paying 25$ in fact my droid is boot-loader unlocked right now using sunshine , the point is community is dead we don't have a variety of roms like the same era phones such as htc m8 and smasung s5 and z2/z3 nexus 5/6 etc , even my 2012 lg l3 have more roms droid turbo, the unlocking boot-loaeder and sunshine was obstacles against all this wonderful hacking and moding things we could do.
Click to expand...
Click to collapse
You missed my point. Droid Turbo XT1254 is only one Quark of three, all of which use the exact same LOS-based ROMs.
It would be like LG G3 was divided up into three different model names. The internal name was Quark, but the global consumer name for this device was Moto Maxx -- even for the U.S. model, but Verizon demanded an "exclusive", so theirs was named "Droid Turbo". But the XT1254 exactly the same phone as the XT1250 -- just has a locked down bootloader. It wasn't exclusive in any way. Other carriers in the U.S. sold the Moto Max XT1250, which has the same FCC ID as the the Droid Turbo XT1254.
Then the XT1225 Moto Maxx was renamed Moto Turbo for India, but it's the exact same FCC ID device as the XT1225 Moto Maxx.
Droid Turbo is the only one with locked down bootloader. The others are not. So, nothing is preventing development unless you INSIST on buying the only Quark with locked down bootloader, and didn't research before buying.
That's why all the development for Quarks, including the Droid Turbo is posted in the OTHER QUARK forum. Like TWRP, custom kernels, most of the ROMs.
Your whole premise is flawed. You think people HAVE to buy Droid Turbo or nothing. No, they can buy one of the other Quarks and have free bootloader unlock.
* With XT1225 they can have more LTE and HSPA bands.
* With XT1250 they can have all the Verizon CDMA and Verizon LTE bands.
The Droid Turbo XT1254 is the least desirable of all the Quarks... But if you buy it, be sure to factor in $25 for bootloader unlock. The others have free bootloader unlock.
Sent via open market LG US998 V30/V30+
people buy the Verizon droid turbo over the other Quarks because the price and availability , being said that i think most Quark users are using xt1254 plus it is compatible with CDMA and GSM that's why the user go for xt1254 which is the most desirable,
any the phone is three years old can't people around the globe who are using xt1254 get a free unlock !
droid_ulti said:
people buy the Verizon droid turbo over the other Quarks because the price and availability , being said that i think most Quark users are using xt1254 plus it is compatible with CDMA and GSM that's why the user go for xt1254 which is the most desirable,
any the phone is three years old can't people around the globe who are using xt1254 get a free unlock !
Click to expand...
Click to collapse
Again, you have it wrong.
Why do you think the Droid Turbo is cheaper? Because you have to factor in extra $25 into the purchase price for bootloader unlock. The REAL price is $25 MORE than you paid. People who buy it have to do that -- if bootloader unlocked and root is important to them. Thus, Droid Turbo SEEMS cheaper...
If there was "free bootloader unlock", Droid Turbos would then become more expensive as the price would rise. Just like 2015 Kinzie -- Verizon Droid Turbo 2 are much cheaper because they don't have bootloader unlock, but sibling Moto X Force is more expensive because it's BETTER -- it has free bootloader unlock from Motorola.
Why do you think the other Quarks (XT1250/XT1225) are more expensive? Because they are better. Free bootloader unlock from Motorola.
Outside the U.S. CDMA is mostly useless. Most of the world detests CDMA and doesn't use it. The XT1225 has more LTE and HSPA bands than the XT1254/XT1250 and doesn't have useless CDMA.. It has 64GB storage and FREE bootloader unlock, whereas most XT1254 have 32GB storage (yes, some have 64GB but not many) and you have to pay $25 for bootloader unlock and it's sometimes not easy to do. So XT1225 is worth more money.
____
Sunshine team publicly released the vulnerability they use. Anyone that wants can code free bootloader unlock. Nothing is stopping anyone from coding and releasing it.
But you seem to be blaming the devs who are offering a solution. If there was no Sunshine, you would HAVE to buy XT1250 or XT1225 -- or another phone altogether.
The Verizon Droid Turbo 2 (Kinzie) never got bootloader unlock, so people HAVE to buy the free bootloader unlock Moto X Force (Kinzie) if they want root and custom ROMs. Tons of people would LOVE the opportunity to pay $25 to unlock their Droid Turbo 2!
Sent via open market LG US998 V30/V30+
Here's news about Oreo ROMs for Quark, and the current list of Nougat ROMs. Since you're new, you may have missed this.
https://forum.xda-developers.com/showpost.php?p=75679114&postcount=94
Oreo needs at least Kernel 4.4. To prevent false hopes, it still should be called Resurrection Remix.
It's a bit like installing Vista themes on Windows XP back in the days...
lem22 said:
Oreo needs at least Kernel 4.4. To prevent false hopes, it still should be called Resurrection Remix.
It's a bit like installing Vista themes on Windows XP back in the days...
Click to expand...
Click to collapse
SUMMARY: you're never going to have a kernel for a device which was not first released by the OEM, in this case Motorola.
________
Call the kernel Resurrection Remix? It seems you are confusing kernels with specific ROM names? Maybe you are making a joke, I'm not sure.
Once we have a compatible kernel in the LOS tree to that will run on Oreo, any ROM maintainer can package and release a ROM. @bhb27, our kernel developer also maintains Resurrection Remix ROM. But there's also LOS, crDroid, etc. All the current ROMs will probably follow to Oreo. We may even attract some new ones.
An Oreo compatible kernel is the FOUNDATION for any Oreo ROM. You need that first. But you can't just create a kernel out of thin air. You need to adapt the kernel sources the OEM (in this case Motorola) has released publicly.
_________
Here's the problem with the kernel -- and I'm not an expert on kernels, but I'll explain it the best I can.
When our former official CM dev @Skrilax_CZ started this work back in early 2015, he had to take Motorola KitKat kernel sources and adapt it to work with Lollipop CM 12.0 (March 2015) and then CM12.1 (April 2015). We had Lollipop CM custom ROM BEFORE Motorola gave us Lollipop.
Motorola did release official Lollipop, but didn't release Lollipop kernel sources until like July 2015. At that point our CM dev @Skrilax_CZ then updated the CM kernel to "Lollipop" kernel. Until then for many months, we had Lollipop ROMs running on Kitkat kernel.
WHY? Because you can't just create a kernel that will run on a phone from scratch. You have to adapt the kernel the OEM has made for it.
Then, same thing happened with Marshmallow. For awhile, we had Marshmallow ROMs running on "Lollipop" kernel. Then Motorola released Marshmallow kernel sources and now we have "Marshmallow" kernel. During this time frame (Marshmallow to Nougat) was when @bhb27 took over kernel coding duties.
Well, guess what? Marshmallow was the last firmware Motorola ever released for Quark.
Yet, we have Nougat ROMs -- running on Marshmallow kernel. (Thanks to @bhb27)
If we ever get Oreo -- it will be Oreo running on Marshmallow kernel. (Thanks to @bhb27).
So, no I'd pretty much bet you will never get Linux Kernel 4.4 running on any Quark. If you want that, you would need official OEM kernel coding -- with stock official Oreo ROM -- which is only available with currently supported hardware. XDA devs with skill give life to older devices like these 2014 phones, but there's limits to what they can do.
I have Linux kernel 4.4.63 on my LG V30 US998, but it's a new phone. LG codes that kernel. Three years from now if I still have this phone, any ROMs in running will have to be using kernel sources from LG.
Just like any Quark will need kernel sources from Motorola -- and the last available is Marshmallow kernel, circa 2016.
lem22 said:
Oreo needs at least Kernel 4.4
Click to expand...
Click to collapse
Not true. See link for LOS 15.1 for Nexus 4, Linux kernel 3.4: https://forum.xda-developers.com/nexus-4/development/rom-lineageos-15-1-t3758779
lem22 said:
Oreo needs at least Kernel 4.4.
Click to expand...
Click to collapse
TheSt33v said:
Not true. See link for LOS 15.1 for (2012) Nexus 4, Linux kernel 3.4:
https://forum.xda-developers.com/nexus-4/development/rom-lineageos-15-1-t3758779
Click to expand...
Click to collapse
If he actually meant that, then he's wrong. I pointed out how he was wrong in thinking that older devices running Oreo custom ROMs will ever get Linux kernel 4.4. You need OEM kernel sources for that, and most OEMs aren't going to release Oreo firmware for older phones (like our 2014 Quarks). Because they want you to buy NEW phones. So, devs have to adapt the last kernel sources they have (for Marshmallow, in this case) to work on newer OS. No one except the OEM can make a brand new 4.4.x kernel for an old device.
But I thought he meant "need" as in "want". So, it would run better or something.
Me: We need a new TV.
Wife: No, you want a new TV.
Nexus devices were very open source, so great that a 2012 phone (LG Nexus 4) has Oreo. I skipped that Nexus. I had the gen3 Galaxy Nexus and the gen5 LG Nexus 5 -- as well as the Nexus 9 tablet (which my wife still uses).
lem22 said:
Oreo needs at least Kernel 4.4.
Click to expand...
Click to collapse
For Oreo, the Quark kernel has to be adapted from Motorola Marshmallow kernel to Oreo. @bhb27 did that with Nougat, but Oreo is harder.
A while back, he posted a screenshot of Oreo booted on Quark but still not stable. When he has news he will post about it again. One of the problems is he has one phone, which is his daily phone he has to use to live and work and also doubles as his development phone.
{
"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"
}
TheSt33v said:
Not true. See link for LOS 15.1 for Nexus 4, Linux kernel 3.4: https://forum.xda-developers.com/nexus-4/development/rom-lineageos-15-1-t3758779
Click to expand...
Click to collapse
LOS is LOS and afaik called "15.1" instead of "Oreo" (for good reasons). Google requires kernel 4.4* as the minimum. Therefore, Android™ Oreo® cannot have an older kernel.
I know that for example RR uses "Oreo" in the name too, but I doubt they are allowed to do so since it's a registered trademark.
* or 3.18 for older SoCs resp.
lem22 said:
LOS is LOS and afaik called "15.1" instead of "Oreo" (for good reasons). Google requires kernel 4.4 as the minimum. Therefore, Android™ Oreo® cannot have an older kernel.
Click to expand...
Click to collapse
Oreo is the name given to Android OS version 8.X. Lineage OS 15.1 is a modified fork of the latest Android Open Source Project (Android 8.1). If you install LOS 15.1 on your device and check the Android version, it will tell you 8.1.
Google's kernel requirement is for OEM's manufacturing devices that will launch with Android 8.X and is necessary (or at least preferred) to maintain Project Treble support, which is also a Google requirement for new devices. However, Treble support (and therefore Linux kernel 4.4) is not necessary for Android 8.X to function, as evidenced by all the devices that launched with older versions that were later OTA'd to 8.X and by all the devices currently running LOS 15.1 or any other rom that is a fork of the most recent AOSP.
So yes, LOS 15.1 is different than stock Android Oreo, but only in the same way that Samsung devices running 8.X, for example, are different from Oreo. It is entirely accurate and appropriate to say that all of the cases I've mentioned are running Android Oreo, and it is entirely inaccurate to say that Oreo requires Linux kernel 4.4 to function.
That's what I meant with false hopes because in the end someone might think this phone will really get Oreo.
lem22 said:
That's what I meant with false hopes because in the end someone might think this phone will really get Oreo.
Click to expand...
Click to collapse
Well assuming someone is still working on making the necessary kernel tweaks, it will get Oreo. Once someone does that, everything else is easy. But if work on that has stopped, no Oreo.
lem22 said:
That's what I meant with false hopes because in the end someone might think this phone will really get Oreo.
Click to expand...
Click to collapse
I call Android 8.1 "Oreo". Don't know about you. OREO booted on a Quark.
Did you just ignore that post and screenshot proof? You posted.right below it, so your couldn't miss it.
@bhb27 just has to get it stable.
But there's your Oreo 8.1 on kernel 3.1.
https://forum.xda-developers.com/showthread.php?p=76410082
Sent via open market LG US998 V30/V30+
ChazzMatt said:
I call Android 8.1 "Oreo". Don't know about you.
Click to expand...
Click to collapse
Like I explained, I don't, to avoid confusion. More specifically, I differentiate between Android and RR in this case.
The problem is, usually the preowned used lot of devices shipped to countries other than motorola officially operating-in. In my case, Pakistan. We are mostly unable to buy brand new devices (even if motorola did sell its flagships here) due to hefty prices we have to pay versus the income we have. 25$ might be 2hrs work in US but its almost 3 days of 8hourly shifts on a regular job in Pakistan. Another problem is (I don't know yet) if sunshine supports payments and unlocking outside USA. This caused me to stay away from Motorola as well as HTC devices because the used devices which come to Pakistan are always the verizon ones or the Lenovo's low-end crap. Mind that in Pakistan, currently Turbo 64GB as used device is being sold for 90-110$.
I do understand how OEMs & Carrier-exclusive devices are left in the abyss in terms of software support and speed of security patch arrivals as well as the effort our devs go through to adapt older sources with the newer android builds.
dark_prince said:
The problem is, usually the preowned used lot of devices shipped to countries other than motorola officially operating-in. In my case, Pakistan. We are mostly unable to buy brand new devices (even if motorola did sell its flagships here) due to hefty prices we have to pay versus the income we have. 25$ might be 2hrs work in US but its almost 3 days of 8hourly shifts on a regular job in Pakistan. Another problem is (I don't know yet) if sunshine supports payments and unlocking outside USA. This caused me to stay away from Motorola as well as HTC devices because the used devices which come to Pakistan are always the verizon ones or the Lenovo's low-end crap. Mind that in Pakistan, currently Turbo 64GB as used device is being sold for 90-110$.
I do understand how OEMs & Carrier-exclusive devices are left in the abyss in terms of software support and speed of security patch arrivals as well as the effort our devs go through to adapt older sources with the newer android builds.
Click to expand...
Click to collapse
1) If anyone wants to they can write a free app to do the same thing Sunshine does. The exploit was disclosed publicly. Find someone who knows how to code.
2) Yes Sunshine supports payments and unlocking outside the U.S.. I answered in depth about that just a few weeks ago, that there are alternate ways to pay besides PayPal. It may not be in this thread, but a similar one.
3) There are plenty of Motorola phones that have free bootloader unlock code from Motorola. The reason Pakistan gets the Verizon Motorola phone are probably because they are cheaper -- as they are less useful since have locked down bootloader. So, you have to factor that into the bootloader unlock price (if that option is available) if it's important to you... Some Verizon phones never got dev bootloader unlock.
Whereas the India 64GB Quark Moto Moto Turbo XT1225 (aka Moto Maxx XT1225) -- from the country right next door to you -- probably costs a lot more money than the U.S. Verizon Quark Droid Turbo XT1254. WHY? Not only does it have more LTE and HSPA bands (without the useless CDMA bands), it also has free bootloader unlock code from Motorola. It's the same phone model as the Droid Turbo, they are both Quarks. Just different radio bands. The cost difference is mostly the Verizon locked down bootloader, which makes it a less useful phone.
If you didn't have Sunshine then the 2014 Verizon Droid Turbo (Quark) would have no bootloader unlock, just like the 2015 Verizon Droid Turbo 2 (Kinzie) does not. For Kinzie phones, people have to buy the sibling Moto X Force instead of Droid Turbo 2, to get bootloader unlock and root. Many Droid Turbo 2 owners WISH they could use Sunshine to unlock their bootloaders!
Sent via open market LG US998 V30/V30+
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).
Why still no official status of Lineage OS? Fp issue is solved i guess!
LineageOS community is pretty strict about how they should host a ROM image for any particular phones / tablets on the official website, in fact they have set of rules which you HAVE to abide by, before they would bother to dish up the LineageOS ROMs for, for example, our OnePlus 6T. They do not want half-a**ed builds (that wastes their time).
There are a few bugs still remaining, and we now have to deal with a new problem, hardware mismatch warning (OnePlus have just done something to the recent bootloader in International version of the OxygenOS to discourage the T-Mobile OnePlus 6T users from trying to do conversion from T-Mobile to International, thus the dreaded hardware mismatch warning, however since the Linux kernel just check for two things, bootloader ID and modem status, it can be bypassed) to tackle first before we would see official LineageOS 16 ROM, and it will be distributed via LineageOS page pretty soon.
I had assumed they already done this cuz of all the ROMS we have. Maybe the power and play kernals were used for River too?? I'm hoping this release results in a Magisk w/ twrp ROOTED PHONE!!! Does what I'm thinkin' sound about right?
Motorola releases Android 10 kernel code for the Moto G7
Custom ROM developers, start your engines
www.androidpolice.com
Mk...just read that devs had axx months ago thru treble...which explains all the roms.
If anyone knows of a guide to root the G7 RIVER with magisk...with or without.twrp... PLEASE let it be known!!! I don't NEED twrp...I can make due if need be. I'm soo close to giving up on trying for a magisk root and just doing los,