Hope to see more kernel and ROM options with this release.
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-SU4TL-44
I dont understand. This git says it is for the quark 5.1.1, but the Droid Turbo was the only variant that was brought to 5.1.1. As far as I know, Moto Maxx is stuck on 5.0.2. And if the Droid Turbo does not have an unlockable bootloader, than who is this kernel meant for? Just trying to understand what it means...
IonAphis said:
I dont understand. This git says it is for the quark 5.1.1, but the Droid Turbo was the only variant that was brought to 5.1.1. As far as I know, Moto Maxx is stuck on 5.0.2. And if the Droid Turbo does not have an unlockable bootloader, than who is this kernel meant for? Just trying to understand what it means...
Click to expand...
Click to collapse
1) Droid Turbo XT1254 does NOT have 5.1.1. They only have stock 5.1 from Motorola/Verizon as far as I know. Updated in July. If there was a later OS update, I missed it.
2) It's meant for anyone who has a Quark and can use it -- like the XT1225 and XT1250 (which is identical to the XT1254 -- same FCC ID) which do NOT have locked down bootloaders.
Motorola legally has to release the source code, even though Verizon has them lock down their Quark -- the XT1254. This will help CM and others make better custom ROMs for our Quarks.
We have had 5.1.1 for MONTHS. Not from Motorola, who couldn't care less, but from CM and others who used CM sources. (Thank @Skrilax_CZ, CM team member who bought an XT1225!) We now have FOUR custom 5.1.1 ROMs. However, CM had to use 5.0.2 kernel with 5.1.1. It was Lollipop 5.1.1 with a 5.0.2. Lollipop kernel. Now they can use updated kernel sources! :good:
Skrilax_CZ said:
Meanwhile Motorola released the 5.1 kernel sources at last, so next steps will be to update the proprietaries and rebase the kernel.
Click to expand...
Click to collapse
PwrUsr said:
Hope to see more kernel and ROM options with this release.
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-SU4TL-44
Click to expand...
Click to collapse
" SU4TL-44 "
This is the kernel source for Droid Turbo' s SU4TL-44 firmware, not related to Moto Maxx.
Semseddin said:
" SU4TL-44 "
This is the kernel source for Droid Turbo' s SU4TL-44 firmware, not related to Moto Maxx.
Click to expand...
Click to collapse
It says it's kernel source for Quark.
Quark push for lollipop 5.1.1
Click to expand...
Click to collapse
We have Quarks.
There's also this XDA article, pointing to the exact same link:
Motorola Releases the 5.1.1 Kernel Source Code for the Moto Maxx
http://www.xda-developers.com/xda-e...e-5-1-1-kernel-source-code-for-the-moto-maxx/
Plus I trust this:
@Skrilax_CZ says Motorola has released the 5.1 kernel sources. He was specifically waiting for what Motorola/Verizon gave Droid Turbo users in July. Took Motorola almost 4 months to release it. I'm pretty sure this is what he's talking about.
Skrilax_CZ said:
Meanwhile Motorola released the 5.1 kernel sources at last, so next steps will be to update the proprietaries and rebase the kernel.
Click to expand...
Click to collapse
So, it is related to the Moto Maxx. It's related to all Quarks.
Down in the CM12.1 thread, he and @baybutcher27 have been discussing it in depth. See a couple of posts here:
baybutcher27 said:
@Skrilax_CZ
Have you made wifi working using cm-12.1-5.1.1 kernel tree?
I have not. I try different then you, I merge moto 5.1.1 on the top of 3.10.90, I know that folder have 5.0.2 files and that may creating a bug, but i wanna to try.
I use the existent qcacld-2.0 of CM12.1 and later update from motorola, but wifi doesn't work no matter what qcacld-2.0 I use, I did not make a ROM just a boot and flash those wifi system files that get compile with. Will try to make a ROM to see if the ROM woks but only if you manage to make it work, (make a ROM take too much time)...
The sound files need to be used are those left.tfa9890.*** form su44, I have tested it after flashing it sound is good. Su 44 doesn't have tfa9890.*** it just have left.tfa9890.***.
The wave doesn't work either(The visible red dot sensors on the device lights up but the screen not), after I flash su 44 sensors files, wave doesn't work either and the red dot sensor doesn't light up. But that may be related to the way I merge...
The rest seemed ok.
Click to expand...
Click to collapse
Skrilax_CZ said:
I'm still working on that, have not checked yet if I configured the qcacld-2.0 correctly (different from main now, taken as is from Moto's makefiles). Use the one that you compile with the kernel, but it's stipl WIP. Much of the WIP stuff isn't pushed yet, such as the sound files.
There can be some changes in the devicr tree necessary with respect to the IR sensors.
Click to expand...
Click to collapse
_____________
@baybutcher27 is the person who gave us the official Lollipop compatible TWRP for our Quarks. He also gave us first custom kernel (BHB27-Kernel for Quark, based on CM's sources but with many custom properties) and maintains two different custom 5.1.1 ROMs. And we know the talents of @Skrilax_CZ.
This is an invitation to all developers, compilers and testers of Moto X (2014).
We know that probably our device will not receive officially Nougat update and this is really bad, assuming that our strong Snapdragon 801 can smoothly run without any problems.
My suggestion it's to all developers and compilers from any country work together to sync AOSP from Nougat, adapt device tree and bring up our first AOSP 7.0 rom.
I know that CyanogenMod is working on CM14 for victara... But the idea is bring up pure Android. I never see any pure AOSP rom for our device and would be awesome if we have this now. CM14 maybe will delay a bit and I think that all users here want to feel Nougat experience
Some rumours at internet had saying that Snapdragon 800/801 will not have drivers for Nougat... But I know that this is possible because Nexus 5 had Snap 800 and developers already bring an functional AOSP (link: http://forum.xda-developers.com/google-nexus-5/orig-development/wip-aosp-nougat-nexus-5-t3446875 ). Our developers can check device tree from Nexus 5... See their adaptions in device tree for working Nougat and try to do the same for our Moto X. Maybe disabling Vulkan API for now and we can use same drivers and device tree of Marshmallow!
That's all guys, thanks for reading and we are really expecting an AOSP Nougat for our Moto X before CM14!
The One Plus One (Snapdragon 801) has AOSP Nougat build. Among other devices. The Moto X (2014) is a smaller development community. I was not even expecting CM to build CM14 for this device (see below). It's going to take time
We haven't yet got a Snapshot build (stable release) of Cm13. Small steps.
Visi0nofExcellence2 said:
The One Plus One (Snapdragon 801) has AOSP Nougat build. Among other devices. The Moto X (2014) is a smaller development community. I was not even expecting CM to build CM14 for this device (see below). It's going to take time
We haven't yet got a Snapshot build (stable release) of Cm13. Small steps.
Click to expand...
Click to collapse
I agree, we have small team of developers. And this one more objective of this post: attract more developers.
I think that Moto X doens't have too much developers because we had officially updates since Android 4.4... Numbers of people that goes to custom ROMs is really minimal, because the stock of Motorola doens't give reasons to search custom ROMs (like bloatwares or lags).
But now, we are going to road of needing custom ROMs. Now we have more reasons to search for these ROMs, because we'll probably not receive Nougat. Moto X2 XDA Forum go clog of peoples trying to got Nougat.
I hope for a "pure" aosp too, like the "fake rom" for Nexus 4.
Enviado desde mi XT1095 mediante Tapatalk
cpvm said:
I hope for a "pure" aosp too, like the "fake rom" for Nexus 4.
Enviado desde mi XT1095 mediante Tapatalk
Click to expand...
Click to collapse
Would be awesome
Pls devs we need some nougat !!!
Visi0nofExcellence2 said:
The One Plus One (Snapdragon 801) has AOSP Nougat build. Among other devices. The Moto X (2014) is a smaller development community. I was not even expecting CM to build CM14 for this device (see below). It's going to take time
We haven't yet got a Snapshot build (stable release) of Cm13. Small steps.
Click to expand...
Click to collapse
Dan(Invisiblek) is working on CM14 for Victara. http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_motorola_victara+branch:cm-14.0
and our CM13 Nighly builds is very close to a Snapshot build NO BUGS for me xt1092 very stable as Snapshot build.
Yes it's true . I have been using the nightly builds of CM 13 for Victara and it runs really smoothly. I would encourage developers to work on the Nougat ROM for Victara. We will appreciate it. Thanks
I really hope to see Nougat in this phone, sadly I have no knowledge to help in development, but for sure I will test as it become usable material (its my daily phone, so would be nice that alarm at least works as expected)
We already has an bootable CM14 guys! here's link: http://forum.xda-developers.com/showpost.php?p=68555035&postcount=100
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+