Related
So I've been researching the great scales of the Internet for anything that would allow us to have ANY form of AOSP on this carrier locked POS. Not just a themed version of TW but legit. I've seen on the S4 that there were safestrap compatible versions. I was wondering what had happened to the S5 that this wasn't possible anymore?
No going happen with locked bootloader. Best u can get well be Xtreme Dynamic Kat rom. @talkingmonkey had done good job taking over dynamic kat.
I agree. I've been running TM's version for the past few days and it's fantastic. I was just curious as to why a safestrap compatible version of AOSP was available on bl locked phones in the past, but not on our S5?
Twiisted said:
I agree. I've been running TM's version for the past few days and it's fantastic. I was just curious as to why a safestrap compatible version of AOSP was available on bl locked phones in the past, but not on our S5?
Click to expand...
Click to collapse
The exploit that allowed the S4 to flash custom kernels and AOSP Roms was patched in subsequent updates from AT&T. The S5 has for lack of a better explanation kind of a sidestep recovery that uses the stock kernel only hence the ability to flash other T/W Roms, mods and themes.
As far as a Safestrap compatible version of AOSP on a locked bootloader I'm not sure if it was AOSP or just themed to look that way.
I'm afraid the bootloader will stay locked tight as a drum.
If any of you have a cricket phone and assumed it was locked down since cricket is at&t, it is not locked and you can flash anything you want... Just fyi
sent from my lollipop'd S5
Am I completely missing something? Last I knew 5.1 was the latest OTA on XT1096, not 5.1.1.
5.1.1 would be a custom rom. 5.1 is the latest official.
Sent from my XT1095 using Tapatalk
AGISCI said:
5.1.1 would be a custom rom. 5.1 is the latest official.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Exactly, but when the word "stock" is stuck in front of "5.1.1" I'm left like
As far as I know, the fixes from android 5.1.1 were included in the 5.1 update moto provided..
So in a matter of speaking, the moto 5.1 ís android 5.1.1
N01tra said:
As far as I know, the fixes from android 5.1.1 were included in the 5.1 update moto provided..
So in a matter of speaking, the moto 5.1 ís android 5.1.1
Click to expand...
Click to collapse
And you think that because?
It seems to me that if that were the case they wouldn't have called it 5.1.
I think I read it in a thread here, or at another forum.. Don't recall.
I concur, it isn't logical to name it 5.1 instead of 5.1.1... But then again, the combo "Moto" and "making good decisions" isn't really happening at the moment
Remember when we had to wait 9 months for Lollipop? Here's to hoping that those of us with Bootloader unlock won't have to wait that long! I wonder how much faster anyone but Motorola can dish out good workable updates for Motorola phones.
cyrushehe said:
Remember when we had to wait 9 months for Lollipop? Here's to hoping that those of us with Bootloader unlock won't have to wait that long! I wonder how much faster anyone but Motorola can dish out good workable updates for Motorola phones.
Click to expand...
Click to collapse
No, I remember getting Lollipop before Motorola gave us Lollipop. Back when all the Quarks were in one forum, we XT1225 owners had CM 12.0 (Lollipop 5.0.2) in March 2015 before Motorola gave any of the Quarks 5.0.2. (April 2015 for the Moto Turbo XT1225).
Then CM12.1 (Lollipop 5.1.1 was released in mid-April 2015 for Quark.
I do remember the XT1254 didn't get Lollipop until July 2015... But the rest of us had 5.1.1 since mid-April. The difference was the XT1254 didn't have an unlocked bootloader, thanks to Verizon.
The forums were finally split in September 2015.
It's entirely possible history will repeat itself. The CM dev bought a 2nd Quark and is using it just for CM13 (Marshmallow) testing. It's possible we may get a custom Marshmallow ROM before Motorola releases stock Marshmallow ROM. And now the XT1254 bootloader is unlocked -- so everyone will get it.
I do remember being stuck on an outdated OS for 9 months. It was very frustrating. I also remember being extremely jealous of all the other Quark models in our forum with unlockable bootloaders. I watched them get root and custom roms as I sat by locked down on 4.4 thanks to Verizon. Then mofo came along and gave us a glimpse of freedom. And now sunshine unlock has fully given us our devices back! I'm excited to rejoin the other Quarks in development and see what the future holds for custom roms. I'm loving computerfreek's builds because I like having stock moto apps, but I might try out CM13 when it's ready. That's the beauty of nandroid backups.
Sent from my K00C using Tapatalk
Two bits of news, now in the 2nd week of February 2016...
I wouldn't be surprised if we got Marshmallow on all the Quarks by end of February.
_________________________
1) Moto Maxx: Android 6.0 tests are finally starting in Brazil
http://arena4g.com/2016/02/soak-test-moto-maxx.html
E-mail invitation to update the Moto Maxx | Source: Anonymous User:
{
"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"
}
Marshmallow soak tests are going on in Brazil for the "international" Quark, Moto X1225. What does this mean for Droid Turbo users?
The only difference in all the Quarks ("international" Moto Maxx XT1225, Moto Turbo XT1225, U.S. Moto Maxx XT1250, Droid Turbo XT1254) are the radios. (In fact the U.S. Moto Maxx XT1250 and Droid Turbo XT1254 are identical in every way, including the radios! Even the same FCC ID.)
Everything else is identical, which is why all the Quark ROMs work on all the Quarks -- including the Droid Turbo XT1254 (with unlocked bootloader):
CM12.1 ( @Skrilax_CZ dev)
Resurrection Remix ( @baybutcher27 dev)
Mokee (AOSP ROM, @baybutcher27 dev)
Nexus Experience (AOSP ROM),(EDIT: Nexus Experience has not been updated recently and does not work with Droid Turbo radio.)
Xperia Z5G
as well as custom kernel BHB27 ( @baybutcher27 dev).
Droid Turbo owners are using all of these above.
These Motorola soak tests usually last a week or two, then the official OTA is pushed out.
Point is, as soon as the soak test is over and the OTA officially hits the XT1225, the devs will update all the custom ROMs to Marshmallow and the Droid Turbo owners can install them. The custom ROMs all auto-detect the appropriate radios for each model. No need to wait for Verizon.
________________________________________________
2) Our Quark CM dev @Skrilax_CZ is already making Marshmallow kernel updates.
@baybutcher27 has also contributed. Here's the thread. One of them is titled "FIX:quark: Update filesystem config for 6.0"
baybutcher27 said:
@Skrilax_CZ
Nice work on the fix of the kernel. I try had no luck.
Are those the final changes before released the first test build?
As you just released those, I had not the time to test yet...
Check this before you release one... very minor fix...
https://github.com/bhb27/android_de...mmit/60f2c0f697bf2a97354d5d32d370859c9a76e6d2
https://github.com/bhb27/android_de...mmit/07bebb5d30cc58e27b2268779143677188e7df4a
config_screenBrightnessSettingMinimum in the 1° config_screenBrightnessDim as it is duplicated.
the last one is present on cm12 too.
:good:
Click to expand...
Click to collapse
Skrilax_CZ said:
Yes, there was a major patch to fix display HAL in the kernel. Thx for the rest, reviewed, pushed.
Click to expand...
Click to collapse
baybutcher27 said:
@Skrilax_CZ
I know you may have not finished...
But check...
this on the kernel
https://github.com/bhb27/android_ke...mmit/ea3c27bee339852dfb42cfac42b67e4192a57607
need this
https://github.com/bhb27/android_ke...mmit/7c1352298e00059769724b806b3a3c0fc47d4b9a
........
this I add in the pass on L...
https://github.com/bhb27/android_de...mmit/52b11efc1eeca7ea2f3a63912638d21f1dae95f6
and this M only
https://github.com/bhb27/android_ke...mmit/bed942732b86b5d46be8d0d679f3677c839e1bb4
https://github.com/bhb27/android_de...mmit/ba797f67f306bfbbf3b09c7cc4960b8ddabf6624
this may need blobs have not tested this yet... is easy to test with the ROM on the device, I test when have the ROM and the time...
https://github.com/CyanogenMod/andr...mmit/a39a9b51c93af54b3f0a46ae424631fa442daf7f
:good:
PS...
I find this minor thing...
https://github.com/bhb27/android_ke...mmit/eef0532fa70ae727ff5cdab262fed31d89edbcb5
Click to expand...
Click to collapse
Skrilax_CZ said:
Will review.
Click to expand...
Click to collapse
This has to mean CM13 (Marshmallow) is very close -- even without Motorola's Marshmallow OTA update! And Resurrection Remix is based on CM.
Either way, I wouldn't be surprised if we got Marshmallow on all the Quarks by end of February.
ChazzMatt said:
Either way, I wouldn't be surprised if we got Marshmallow on all the Quarks by end of February.
Click to expand...
Click to collapse
So how will that effect those of us who have unlocked our bootloaders and rooted?
And how can we block the OTA until there is a clear upgrade path?
nlinecomputers said:
So how will that effect those of us who have unlocked our bootloaders and rooted?
And how can we block the OTA until there is a clear upgrade path?
Click to expand...
Click to collapse
1)With root and unlocked bootloader and TWRP recovery, you can install the custom Marshmallow ROM of your choice.
2) as far as blocking OTA, do you have custom recovery (TWRP) installed? Things like that will block OTA from installing (because you have changed system files). You still might get nagged, but it won't actually install. IF you want to stop the nagging, there's some sort of update file to re-name or delete.
I pretty happy with stock. Just want minor modifications hence going to root. ROMS just never seem to be as stable as stock. Even upgrades by the carriers don't seem often as stable as the shipped stock.
CM 12 is beyond smooth (& stable) on my quark. Can't wait for CM13 !!!!!
Hey @ChazzMatt roughly how difficult will this be to port to Verizon? I'm assuming CF could implement his tweaks fairly easy while only losing Verizon only features like Advanced Calling, right?
Looking forward to the official ROM more so than CM13 if CF can help out.
pjd2011 said:
Hey @ChazzMatt roughly how difficult will this be to port to Verizon? I'm assuming CF could implement his tweaks fairly easy while only losing Verizon only features like Advanced Calling, right?
Looking forward to the official ROM more so than CM13 if CF can help out.
Click to expand...
Click to collapse
Not sure I understand the question. CM12.1 already works with Verizon Droid Turbo, as does Mokee, Resurrection Remix and Xperia. Quarks are Quarks. Ever since the Droid Turbo bootloader got unlocked in November 2015, all the Quark ROMs (except one) have been updated to also with the the laggard Droid Turbo.
So, CM13 Preview already works with Verizon. Go over to the thread, you'll see Droid Turbo users reporting feedback.
[Moto MAXX XT1225 / Droid Turbo XT1254][PREVIEW] CyanogenMod 13.0
http://forum.xda-developers.com/mot.../moto-maxx-xt1225-droid-turbo-xt1254-t3315912
Here's a re-post from another thread, explaining the situation...
_________
You just aren't looking in the right place. All the Quarks have the same hardware, and except for the Droid Turbo they all had unlock-able bootloaders from the very beginning via Motorola websitie. So, there's tons of development.
For almost a year the Quarks were all in this forum. But because the Droid Turbo was locked down (per orders from Verizon), the Droid Turbo people got mad because they saw all this neat dev stuff they couldn't get. So, they petitioned XDA mods to split the forum into the "dead" Droid Turbo dev forum and the active rest-of-the-Quarks forum.
The forum split happened in September 2015...
Then, guess what? About two months later, exploit was found to unlock the Droid Turbo bootloaders! So, now all the Droid Turbo users who want custom ROMs, custom kernels, etc, have to trek over to the rest-of-the-Quarks forum -- aka Moto Maxx forum, but it's also the Moto Turbo forum. Yeah, there's TWO Quarks called Turbo.
After the Droid Turbo bootloader unlock, the CM dev started a CM thread over here --but it's the SAME ROM as in the Moto Maxx forum, and most people (even Droid Turbo users) just post over there.
_______
The only difference in all the Quarks ("international" Moto Maxx XT1225, Moto Turbo XT1225, U.S. Moto Maxx XT1250, Droid Turbo XT1254) are the radios. (In fact the U.S. Moto Maxx XT1250 and Droid Turbo XT1254 are identical in every way, including the radios! Even the same FCC ID.)
The DEVICE called the Droid Turbo was NEVER exclusive to Verizon. The exact same phone is/was sold by U.S regional CDMA/LTE carriers as the U.S . Moto Maxx. Motorola even used the "Turbo" name again for another Quark. Only the "Droid" name was exclusive, because Verizon licenses that name from LucasArts. So, yeah you can only buy a "Droid Turbo" from Verizon, but you can buy the EXACT SAME PHONE (with the same bands) from another carrier in the U.S. Put a Verizon SIM card into a U.S. Moto Maxx and it runs on Verizon just like a non-Verizon Nexus 6...
It would be like Samsung calling their Galaxy S6 the "S6", everywhere but Verizon. For Verizon, it would be called the "Yabba Dabba Do" phone. And Verizon puts out press releases: The "Yabba Dabba Do" phone is EXCLUSIVE TO VERIZON! It's still just a Galaxy S6! Oh, but the Verizon version would have a locked-down bootloader...
____________
Only the Quark radios are different. Everything else is identical, which is why all these Quark ROMs below work on all the Quarks -- including the Droid Turbo XT1254 (with unlocked bootloader):
CM12.1 ( @Skrilax_CZ dev)
Resurrection Remix ( @baybutcher27 dev)
Mokee (AOSP ROM, @baybutcher27 dev)
Xperia Z5G
as well as custom kernel BHB27 ( @baybutcher27 dev).
Droid Turbo owners are using all of these above. But except for the CM dev, the devs aren't posting duplicate threads over here in the Droid Turbo forum. You have to go over to the Moto Maxx forum to participate.
ChazzMatt said:
Not sure I understand the question. CM12.1 already works with Verizon Droid Turbo, as does Mokee, Resurrection Remix and Xperia. Quarks are Quarks. Ever since the Droid Turbo bootloader got unlocked in November 2015, all the Quark ROMs (except one) have been updated to also with the the laggard Droid Turbo.
So, CM13 Preview already works with Verizon. Go over to the thread, you'll see Droid Turbo users reporting feedback.
[/SIZE]
Click to expand...
Click to collapse
Sorry - Already know all of that. I'm more concerned with Motorola actually pushing the MM update. My question is how easily would that be able to be ported over to the Turbo? Could we bake in the Verizon specific features?
A @computerfreek274 image based on the official Motorola Maxx release would be my DD over CM13 (as much as I love CM).
pjd2011 said:
Sorry - Already know all of that. I'm more concerned with Motorola actually pushing the MM update. My question is how easily would that be able to be ported over to the Turbo? Could we bake in the Verizon specific features?
A @computerfreek274 image based on the official Motorola Maxx release would be my DD over CM13 (as much as I love CM).
Click to expand...
Click to collapse
Sorry for misunderstanding you. It seemed you were asking if CM13 would work on the Droid Turbo.
You are asking if all the features Verizon's eventual official stock Marshmallow image can be ported over to some other ROM.
The problem with that is some are Motorola features, which would work on all Quarks, and some are possibly Verizon only features (like Verizon voice mail) which non Verizon customers don't care about.
@baybutcher27 with his Resurrection Remix ROM (based on CM) has tried to get both Motorola features working as well as Verizon features which can be installed as add on items. For instance, Verizon voicemail works on his ROM, If you follow the instructions.
But other features are substitutes... Ambient Display= Moto Display. OK Google=Moto Voice.
The trade off is custom ROMs like CM or RR have other features not found on stock ROM. For instance, the ability to use your phone like a flash drive. I was surprised Verizon ROM, even Computerfreek274's Verizon-based ROM doesn't have that feature... I can plug in my phone and pull off TWRP backups in normal GUI mode.
Only Computerfreek274 makes tweaked Verizon stock ROMs with all features included, plus some extras.
So, his eventual Marshmallow ROM, based on Verizon's update is probably what you want.
Correct me if I am wrong, but with out unlocked bootloader, a dev could make a sense rom if there was enough kind requests?
While the unlocked bootloader makes it possible, that doesn't mean it will happen. Most developers don't make ROMs because its requested, but because they enjoy doing so and giving to the community. We could all band together and request a billion dollars from the bank but that's not gonna make them give it to us.
Unfortunately, those of us with a quark phone with a passion for modding and flashing is small. That's why we don't ha e a community with tons of ROMs like Nexus and other flagship devices.
But what we do have is a top of the line phone with some DEV love that is truely appreciated by those of us that use it and take pride in having a special unique phone.
However. There is an Xposed add-on that will allow you to flash sense apps, and with some theming and tweaks you can make CM almost look and function exactly like sense
What he said. Due to Verizon locking down the bootloader, which took about a year to overcome, the Droid Turbo XT1254 got ignored by a lot of devs.
However, dev work was done on the sibling Quarks (Moto Maxx/Moto Turbo XT1225)-- which luckily also works on the Droid Turbo (now that that bootloader is unlocked). Only problem is Motorola did not sell the other Quarks in places like Europe, Canada nor Asia (except for India) and even in the U.S. the unlockable bootloader Quark (the U.S. Moto Maxx, with same FCC ID as the Droid Turbo) was only sold via regional CDMA/LTE carriers and hard to get. The "international" Moto Maxx XT1225 was sold in Latin American countries and the Moto Turbo XT1225 was sold in India. This should have been a WORLD WIDE phone, sold EVERYWHERE -- like a Samsung or LG flagship phone, but was not for some reason. Very strange!
However, there's 3 or 4 custom 5.1.1 ROMs over in the Quark/Moto Maxx section which will work with the XT1254:
* [ROM][5.1.1][OFFICIAL][QUARK] MoKee OpenSource Project
MoKee OpenSource is based on the Google AOSP. @baybutcher27 is the dev.
http://forum.xda-developers.com/moto-maxx/development/rom-mokee-opensource-project-t3188936
* [ROM][All Quark][5.1.1]Resurrection Remix 5.5.9 [Optimized / O3 / GRAPHITE / KRAIT]
Resurrection Remix has tons of options. @BayButcher is the also the dev for this ROM, which is very popular.
http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-5-5-5-t3197643
* [Moto MAXX XT1225 / Droid Turbo XT1254][OFFICIAL] CyanogenMod 12.1
CM12.1 was our first custom ROM and without it there would be no others, because all the Quark (Droid Turbo/Moto Maxx/Moto Turbo) custom ROMs use @Skrilax_CZ CM kernel in their ROMs. Even @baybutcher27 kernel uses @Skrilax_CZ CM kernel as a base.
http://forum.xda-developers.com/mot.../moto-maxx-xt1225-cm12-0-pre-release-t3060089
Also, a custom kernel:
* [Kernel][All Quark]BHB27-Kernel[5.1.1][CM base ROM's][V-1.2.3]
Custom kernel for our Quarks, using CM kernel as base but with lots more options. @baybutcher27 is the dev.
http://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526
I don't see any Sense ROM for any non HTC device.
Are you guys thinks that is really possible to make one for quark? I'm not shore if a regular dev can do, a very experience dev with Knowledge of CM quark and or Sense porting may, but I don't see one available to do that, I know I can't today and even if I do only that I may never be able some things are really hard to port.
Make a CM base ROM is easy any one can do if follow CM default recipe there is no mystery, may take a while to learn a few thing but is generally easy, the most hard thing is to setup the machine but for that google has a good tutorial and all the ROM manifest on git have they on too like RR for exemplo, if the particularly source need special config it will be on they manifest on git, if it is not there, is a easy find by just searching on other Moto device for that source.
Google tutorial
RR tutorial
So if you guys really wanna a ROM make your hands dirty and try to make one start by the easiest one that are CM base, the only thing that is need is a PC/Notebook with internet access average CPU about 100 to 150gb of free space, I'm build for months on my notebook and is a really simple one...
For a fact I know MM will bring new ROM different from the one we have today, I see some other dev with they MM source ready to make a ROM for quark the only problem is that today custom ROM are not working on MM but they will soon and then more ROM will be available.
If any one need help in build a ROM fell free to open a thread and quote me to help I will but don't expect step by step tutorial that already exist on google and XDA, I help in some things that are not much common and or related to quark only.
Fell free too to quot this post to any one that wanna this or that ROM, this way we may have more ROM in the future.
:good:
baybutcher27 said:
I don't see any Sense ROM for any non HTC device.
Are you guys thinks that is really possible to make one for quark? I'm not shore if a regular dev can do, a very experience dev with Knowledge of CM quark and or Sense porting may, but I don't see one available to do that, I know I can't today and even if I do only that I may never be able some things are really hard to port.
Make a CM base ROM is easy any one can do if follow CM default recipe there is no mystery, may take a while to learn a few thing but is generally easy, the most hard thing is to setup the machine but for that google has a good tutorial and all the ROM manifest on git have they on too like RR for exemplo, if the particularly source need special config it will be on they manifest on git, if it is not there, is a easy find by just searching on other Moto device for that source.
Google tutorial
RR tutorial
So if you guys really wanna a ROM make your hands dirty and try to make one start by the easiest one that are CM base, the only thing that is need is a PC/Notebook with internet access average CPU about 100 to 150gb of free space, I'm build for months on my notebook and is a really simple one...
For a fact I know MM will bring new ROM different from the one we have today, I see some other dev with they MM source ready to make a ROM for quark the only problem is that today custom ROM are not working on MM but they will soon and then more ROM will be available.
If any one need help in build a ROM fell free to open a thread and quote me to help I will but don't expect step by step tutorial that already exist on google and XDA, I help in some things that are not much common and or related to quark only.
Fell free too to quot this post to any one that wanna this or that ROM, this way we may have more ROM in the future.
:good:
Click to expand...
Click to collapse
Wow thanks alot, mabye ill have to give it a shot
Title says it all. I am thinking about getting a droid turbo, and im just wondering If I can flash moto maxx custom ROMs onto the turbo without it bricking. Can anyone say if this works or not?
Yes, of course. If it says Quark, it's Quark.
Quark =
XT1254 Droid Turbo,
XT1250 U.S. Moto Maxx,
XT1225 "international" Moto Maxx,
XT1225 Moto Turbo
They are ALL the same phone, like an LG G3 is an LG G3 -- whether sold in Britain or sold in U.S. or sold in Australia. In fact, the XT1254 is EXACTLY the same device as the XT1250 U.S. Moto Maxx -- same radio bands, same FCC ID. Verizon just re-named it the "Droid Turbo" -- so they could claim to have an "exclusive" phone. The only thing "exclusive" about the Droid Turbo is the Verizon-mandated locked down bootloader. (The other Quarks can be unlocked via free code from Motorola on request.)
Here's the list of ROMs you can flash on your Droid Turbo XT1254 AS LONG AS YOU UNLOCK YOUR BOOTLOADER with Sunshine:
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=70473048&postcount=58
However, if your Droid Turbo is already on stock 6.0.1 with locked bootloader you are out of luck. Sunshine ($25) only works on Verizon Lollipop firmware. See that post for specific options on how to avoid getting a 6.0.1 Droid Turbo with bootloader which cannot be unlocked.
Here in this Droid Turbo forum you have AOKP on Nougat, over in the other Quark forum you have Resurrection Remix Nougat, crDroid Nougat, unofficial CM14 Nougat -- plus various Marshmallow and Lollipop ROMs scattered throughout.
We used to be ONE forum, but it was split in September 2015 -- ironically about two months before Sunshine team cracked the Droid Turbo bootloader (November 2015). Now we just all go back and forth, since the Droid Turbo joined the custom ROM party. Go up to that link and look at that ROM list.
That's why the EXACT same CM12.1 and CM13 are listed in both forums. After Droid Turbo bootloader was unlocked, the Quark official CM dev @Skrilax_CZ was nice enough to come back and re-list the ROMs here, even after he was booted out when the forums were split. (The Droid Turbo owners were tired of seeing all the dev work they couldn't have. They demanded the forums be split. Then two months later when Sunshine unlocked the bootloader, suddenly they wanted it all. ) He was nice enough to re-code his Quark CM kernel to also allow the Droid Turbo to use his work, when he didn't have to. Because of him, that allowed ALL the Quark custom ROMs to also run on Droid Turbo XT1254. All the custom ROMs (except for computerfreek274's Verizon stock-based Marshmallow ROM) run on CM-based kernel code -- which was pioneered by @Skrilax_CZ. Others like @bhb27 got us official Quark TWRP, more ROMs, several Quark specific apps, @bhb27 custom kernel, etc. All that work led to even more ROMs, now in both forums.
Most ROMs are listed over there, but some are listed in this forum. Go up that list and see them.
Thank you
ChazzMatt said:
Yes, of course. If it says Quark, it's Quark.
Quark =
XT1254 Droid Turbo,
XT1250 U.S. Moto Maxx,
XT1225 "international" Moto Maxx,
XT1225 Moto Turbo
They are ALL the same phone, like an LG G3 is an LG G3 -- whether sold in Britain or sold in U.S. or sold in Australia. In fact, the XT1254 is EXACTLY the same device as the XT1250 U.S. Moto Maxx -- same radio bands, same FCC ID. Verizon just re-named it the "Droid Turbo" -- so they could claim to have an "exclusive" phone. The only thing "exclusive" about the Droid Turbo is the Verizon-mandated locked down bootloader. (The other Quarks can be unlocked via free code from Motorola on request.)
Here's the list of ROMs you can flash on your Droid Turbo XT1254 AS LONG AS YOU UNLOCK YOUR BOOTLOADER with Sunshine:
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=70473048&postcount=58
However, if your Droid Turbo is already on stock 6.0.1 with locked bootloader you are out of luck. Sunshine ($25) only works on Verizon Lollipop firmware. See that post for specific options on how to avoid getting a 6.0.1 Droid Turbo with bootloader which cannot be unlocked.
Here in this Droid Turbo forum you have AOKP on Nougat, over in the other Quark forum you have Resurrection Remix Nougat, crDroid Nougat, unofficial CM14 Nougat -- plus various Marshmallow and Lollipop ROMs scattered throughout.
We used to be ONE forum, but it was split in September 2015 -- ironically about two months before Sunshine team cracked the Droid Turbo bootloader (November 2015). Now we just all go back and forth, since the Droid Turbo joined the custom ROM party. Go up to that link and look at that ROM list.
That's why the EXACT same CM12.1 and CM13 are listed in both forums. After Droid Turbo bootloader was unlocked, the Quark official CM dev @Skrilax_CZ was nice enough to come back and re-list the ROMs here, even after he was booted out when the forums were split. (The Droid Turbo owners were tired of seeing all the dev work they couldn't have. They demanded the forums be split. Then two months later when Sunshine unlocked the bootloader, suddenly they wanted it all. ) He was nice enough to re-code his Quark CM kernel to also allow the Droid Turbo to use his work, when he didn't have to. Because of him, that allowed ALL the Quark custom ROMs to also run on Droid Turbo XT1254. All the custom ROMs (except for computerfreek274's Verizon stock-based Marshmallow ROM) run on CM-based kernel code -- which was pioneered by @Skrilax_CZ. Others like @bhb27 got us official Quark TWRP, more ROMs, several Quark specific apps, @bhb27 custom kernel, etc. All that work led to even more ROMs, now in both forums.
Most ROMs are listed over there, but some are listed in this forum. Go up that list and see them.
Click to expand...
Click to collapse
Holy information Batman! These forums rock been unlocked running customs Roms by these guys for a few months now.
Thank you to all!
Running Computer Freaks MM 1.05 with bhb27 kernal now trying to figure out theme ready Gapps now....Such a pain lol back to reading I go.
Ultross said:
Holy information Batman! These forums rock been unlocked running customs Roms by these guys for a few months now.
Thank you to all!
Running Computer Freaks MM 1.05 with bhb27 kernal now trying to figure out theme ready Gapps now....Such a pain lol back to reading I go.
Click to expand...
Click to collapse
CF's ROM doesn't need GAPPS, as it's stock-based firmware. It already has Google apps. Any others you need, you have to download manually.
Here's from the dev himself:
computerfreek274 said:
This is a stock based rom do not use gapps.
Click to expand...
Click to collapse
computerfreek274 said:
Because people get confused I am trying to keep it simple for others. Never run gapps on stock based roms it makes it unstable and some Google stuff not work correctly.
Click to expand...
Click to collapse
ChazzMatt said:
CF's ROM doesn't need GAPPS, as it's stock-based firmware. It already has Google apps. Any others you need, you have to download manually.
Here's from the dev himself:
Click to expand...
Click to collapse
Thanks!
Ultross said:
Running Computer Freaks MM 1.05 with bhb27 kernal now trying to figure out theme ready Gapps now....Such a pain lol back to reading I go.
Click to expand...
Click to collapse
ChazzMatt said:
CF's ROM doesn't need GAPPS, as it's stock-based firmware. It already has Google apps. Any others you need, you have to download manually.
Click to expand...
Click to collapse
He's actually looking for the "Theme-ready Gapps" package, which includes replacement Google apps that are modified by 3rd-parties to remove hard-coded colors and fonts. This is beneficial if you're using a dark or bold-colored theme, and are tired of some apps forcing a white "material design" background, or seeing dark text on a dark background.
Unfortunately, installation and maintenance of those modified apps is rather time intensive, as you're always delayed in getting new versions, you have to remove the official versions and disable updates, you have to manually check for updates, and each time an update is released you have to flash it through TWRP (frequently, as this is Google and it includes several apps).
I looked into it, but decided not to bother. I like my phone to be working for me, instead of me continually working on my phone.