yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Android Development] Coronado is dead:
Just checking before I flash: will the unlocked warning remover set it back to the same M logo it was before, or is this a different boot logo?

Thanks!
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
Same logo, just no unlocked warning.
[Verizon Motorola Droid Turbo Android Development] activeservo:
Came from Mofo 5.1 to Sunshine and running ComputerFreak's Unlocked 1.2 rom. Updated Booloader/baseband and removed bootloader warning files both flashed in TWRP with no problems. Thank you!
[Verizon Motorola Droid Turbo Android Development] PILLMUZIK3600:
Any bugs with the twrp flashable bootloader unlock warning zip file?
[Verizon Motorola Droid Turbo Android Development] mrkhigh:
It worked fine.
[Verizon Motorola Droid Turbo Android Development] frpst9:
After flashing these (via TWRP zip), my device now reports that it is missing a SIM card (I'm using the Verizon Droid Turbo on T-Mobile, fyi). I had no issues prior to updating. Any ideas?
[Verizon Motorola Droid Turbo Android Development] mikelikesbikes:
I was on mofo'd 4.4.4 and didnt read the op closely enough and flashed the bootloader and radio. Now I sit with only access to bootloader mode and recovery and no OS. Been trying everything for a couple days, still no dice. Any advice? Recovery gets me nowhere. I am still able to fastboot. Tried using fastboot to flash some stock firmware I have found but I get bootloader signed fail or validation fail, something similar. Same message when flashing "sparsechunks". All other commands go through no problem.
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
Are you running stock firmware or a custom ROM?

Try flashing a factory image, here's the latest. Edit the first line of the .bat file to point to your fastboot.exe (or copy fastboot.exe into that directory), and remove the "erase userdata" line if you'd like to keep data. Your only option for flashing custom firmware now is to use KingRoot then unlock using SunShine.
[Verizon Motorola Droid Turbo Android Development] frpst9:
Thanks for the response.

I was running a custom ROM (NX from the moto maxx section). I'm back in business now (I had to fastboot flash all of the stock firmware). Prior to that I tried wiping everything and flashing a new ROM (no luck), I tried a new Sim card (no luck), I tried flashing the 39 radio only (no luck). I had to do the whole stock firmware package/bat file (minus userdata and recovery) to get back in operation. Once I did, I was able to restore a backup of NX, and data was back. So now I'm back to 39 firmware on a 5.1.1 custom ROM and all is working. Not sure how to proceed at this point. I guess if it ain't broke, don't fix it....
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
It's possible the Nexus Experience ROM doesn't properly support the newest DT radio. Changes had to be made to the CM-based ROMs after the DT got unlocked, and it looks like NX was last updated in September.

Though I'm not completely ruling out the possibility that it's an error on my part. If anyone else has had issues with the TWRP zip, please let me know.
[Verizon Motorola Droid Turbo Android Development] frpst9:
I was thinking the same thing, so I wiped everything and tried installing CM (as well as another variant), had the same results. Again, I'm using T-Mobile on the Droid Turbo, so maybe it's just my goofy scenario that's caused this condition. Someday when I have some free time, I'll give it another go and see if I can identify specifically which firmware is the cause (and which of the stock restoration steps actually did the trick). Thanks for responding though, and thanks for your work!
[Verizon Motorola Droid Turbo Android Development] Shtiff1:
No issues here. Perfect!
[Verizon Motorola Droid Turbo Android Development] meskes:
I'm not trying to downplay your contribution, but is TWRP and the CM stock recovery the only two actively recoveries for this device? I'm personally a fan of Philz Touch, however, from what I can remember, he stopped development of said recovery. Are there any other recoveries laid out like Philz?
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
Not that I know of. I've said TWRP rather than just "recovery" because it's the most popular one, as well as the one I use. Though it's technically misleading because it'll work on any recovery.
[Verizon Motorola Droid Turbo Android Development] meskes:
Right. Completely understand.
[Verizon Motorola Droid Turbo Android Development] meskes:
At this point, I've pretty much just themed TWRP, so I didn't have to deal with the stock UX. That was more or less my issue with TWRP. I personally feel that it's got a rather lacking UX.
[Verizon Motorola Droid Turbo Android Development] MARKREIF:
Do I have the latest?

Please let me know if I have the latest package installed - thanks
[Verizon Motorola Droid Turbo Android Development] meskes:
Yes

Sent from my DROID Turbo with Tapatalk. Now with that CyanogenMod goodness.
[Verizon Motorola Droid Turbo Android Development] MARKREIF:
Ty
[Verizon Motorola Droid Turbo Android Development] kingersj1:
Every time I try to download the flas file for Bootloader warning removal I get brought to the play store to install an app. Is there a better link?
[Verizon Motorola Droid Turbo Android Development] jlang11:
Try here: http://xdaforums.com/droid-turbo/development/unlocked-warning-fix-version-1-t3258443
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
That's irritating... I've updated the links in OP to a new file host (AndroidFileHost) and kept the MEGA links as mirrors.
[Verizon Motorola Droid Turbo Android Development] corona63976:
Will it come back if you go back to stock or FDR
[Verizon Motorola Droid Turbo Android Development] MazinDLX:
Sorry I dont understand the question? maybe reword it?
[Verizon Motorola Droid Turbo Android Development] corona63976:
OK if I flash it then do a factory data reset will the warning return or is it permanent?
[Verizon Motorola Droid Turbo Android Development] MazinDLX:
if you flash the remover zip it will be gone
[Verizon Motorola Droid Turbo Android Development] veloct:
If I'm on RR 6.0.1, can I still use the unlocked flashable package to remove the message at boot up?
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
Permanent until you flash a factory image.

Yes.
[Verizon Motorola Droid Turbo Android Development] hotrodwinston:
Just to be sure - I'm unlocked for the first time using sunshine - never used mofo - was on the latest ota - is there any advantage to flashing the bootloader/radio zip? Is it needed for the warning removal zip to work?
[Verizon Motorola Droid Turbo Android Development] Grynch13:
You should be fine to just flash the removal zip the bootloader radio zip is only needed if your phone was rooted before lollipop since you used sunshine all should be good without that.
[Verizon Motorola Droid Turbo Android Development] Huntereb:
Thanks for this! Fixed the issues I was having in CM with Location and GPS... It just refused to find my location. With this, it now finds it immidiately. Cheers!
[Verizon Motorola Droid Turbo Android Development] Bloodgod:
Thanks for this I was annoyed with that unlock warning. :beer:
[Verizon Motorola Droid Turbo Android Development] y8s:
Well that was easy. Thanks for the boot logo fix!
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
No and no.
[Verizon Motorola Droid Turbo Android Development] blacksn:
Please upload 4.4.4 Radio
[Verizon Motorola Droid Turbo Android Development] shehroz222:
Hello,

My Droid Turbo is cureently on 5.1 su4tl-44, and i have unlocked it's bootloader using sunshine. Now I want to remove unlock bootlader warning, so kindly guide me that it supports my phone or not?

Thanks.
[Verizon Motorola Droid Turbo Android Development] veloct:
Instructions are given in the initial post.
[Verizon Motorola Droid Turbo Android Development] Grynch13:
Your good to go it will work on all the quark phones just use the fastboot method or if u dig there is a twrp file u can flash instead if u don't want to use your computer just dig through this thread a bit its hear sonewhere
[Verizon Motorola Droid Turbo Android Development] rascal9:
What about XT1254 Running CM13 MM 6.0.1 Still work to get rid of yucky pop up?
[Verizon Motorola Droid Turbo Android Development] veloct:
Yes it will, the unlocked bootloader removal works on it.
[Verizon Motorola Droid Turbo Android Development] GeoFX:
Is the SU4TL-49 fastboot image available somewhere? Already have the upgraded radios and CF ROM installed but would like to go to a bone stock image. Thanks!
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
I plan to make stock images for SU4TL-49, including a bootloader/radio package. I haven't gotten around to it yet as I've been very busy (currently at Google I/O, as a matter of fact), but I'll try to get to it soon.
[Verizon Motorola Droid Turbo Android Development] Astrobrewer:
Please do make the bootloader/radio package for SU4TL-49! I took the OTA and upgraded to SU4TL-49, flashed the unofficial CM13 and found that I GPS was broken. Searching for a quick fix I found a link for for fixing GPS problems that pointed to this thread, and I flashed a radio and bootloader thinking it would be a quick fix. I realized only after flashing that I had flashed the SU4TL-44 bootloader and radio. Everything seemed to be working including GPS so I thought it was ok. But ever since then TWRP 3.0.2 won't decrypt my data partion anymore and I think it's related. I have a working phone so I'm not in a big hurry, but I have no way to use TWRP anymore so I'm a little stuck and can't flash zips. I'm hoping not to have to wipe my phone again, so I'd really like to try flashing a SU4TL-49 bootloader/radio to see if that fixes TWRP.

Thanks in advance!
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
I can't imagine the radio/bootloader affects TWRP. Have you tried reflashing TWRP? Or tried BHB27's TWRP mod?

As far as an update, I've gotten most of the work done but I'm struggling with Moto's sparse image format. Quark bootloader doesn't like my custom radio image.

At this point a factory image of SU4TL-49 might come out soon, which would make it all much easier. But I'm still working on it when I can. Using my Turbo as my daily driver makes it hard to find the time to hack on it.
[Verizon Motorola Droid Turbo Android Development] realbbb:
Sent you a PM with a link to download the SU4TL-49 FXZ.

System Version: 23.21.49.quark_verizon.verizon.en.US

Model number: DROID TURBO

Android Version: 5.1

Baseband Version: MDM9625_104651.11.05.16.03R

Build Number: SU4TL-49

Build Date: Thu May 5 09:15:28 CDT 2016

edit - Trying another host for those that cannot wait. Click Here to Download

BBB

Wanting Two and Not One
[Verizon Motorola Droid Turbo Android Development] Astrobrewer:
I did reflash the same version of TWRP and that didn't have any effect. I was thinking of reflashing a different version to see if that would make a difference. I'll give BHB27's a shot.

Thanks for the help!

---------- Post added at 09:41 AM ---------- Previous post was at 08:53 AM ----------

When I flashed TWRP before I just used the official one because it seemed like the thing to do. But I see now from the change log that the Mod 2 version fixes decryption of custom ROMs. I still can't explain how it seemed to be working fine initially, but I spent hours messing with my phone that day and didn't keep a log of all my steps. But it looks like Mod 2 is the answer.

Thanks [MENTION=2730403]firstEncounter[/MENTION]! That totally worked! Now TWRP prompts me for my password and successfully decrypts /data just like it's supposed to do! I am very happy about this. :D
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
Hi all,

I've added SU4TL-49 radio/bootloader packages to the original post.

They will not overwrite the unlocked warning removal, and the unlocked warning removal package will still work on SU4TL-49, as always.

Let me know if any issues arise.
[Verizon Motorola Droid Turbo Android Development] Astrobrewer:
Thanks so much! This is exactly what I needed! TWRP Mod 2 fixed decryption and this restored my radio and bootloader back to where they were before I got a little too flash-happy and ended up reverting them back to SU4TL-44. I love it when a plan comes together!!! :laugh:
[Verizon Motorola Droid Turbo Android Development] RL_Wells:
I really appreciate you putting these packages together; I was having numerous GPS issues (waze and gmaps not locating) and my wifi at my house would not connect. I recently broke my XT1254 and replaced it with an XT1250 I purchased on jet.com. I am running the latest RR 6.0 rom after trying stock 4.4.4 and CM 12.1; once I flashed this radio package, the problems I mentioned above kept occurring - until today. Thanks again.
[Verizon Motorola Droid Turbo Android Development] schwinn8:
Just to be clear, I'm on stock-rooted-unlocked. Can I simply apply this radio/BL package to get me up-to-date with the radio?

For that matter, is there a reason to update the BL at all? I believe I'll remain unlocked and rooted, but would it make sense to just do the radio alone?
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
Yes, the package will make sure your radio is up to date.

There's no reason not to update the bootloader if you're already unlocked. Using an older, buggy bootloader provides no benefit. Keeping it up to date with the radio likely will avoid weird problems in the future.
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
"dev" version of Droid Turbo XT1254

Kudos to you, sir -- for being smart enough to buy the "dev" version of the Droid Turbo XT1254 to replace your broken XT1254 to run on Verizon. ;)

The dev version being the one without the locked-down bootloader, the XT1250. Bootloader easily unlockable from Motorola, for free.

I know I've tried to spread the word, and I know many people have bought the XT1250 to run on Verizon with a Verizon SIM card -- but you are the first instance of replacing your XT1254 with an XT1250 that I've read here on XDA. There may be others, your story caught my eye.

Also, I didn't know jet.com (a wholesale site, much like Costco, Sam's Club) had new ones for sale. Until now people were either buying 2nd hand on eBay or Amazon. For "new", they were having to go through the regional CDMA/LTE carriers who were selling them -- sometimes at outrageous prices.

Here's the jet.com listing for the new XT1250:

Motorola MOTO Maxx XT1250 32GB Unlocked GSM 4G LTE 21MP Camera Cell Phone

by Motorola

FREE Shipping

$259.94

https://jet.com/product/Motorola-MO...a-Cell-Phone/381c3dd786d9400d9fb435a77af9cec9
[Verizon Motorola Droid Turbo Android Development] schwinn8:
Cool, thank you. Update applied without issue. "Build number" in the phone still says -44, as expected (since this is a radio-only update)... baseband changed to:

"MDM9625_104651.11.05.16.03R QUARK CUST" - I assume that means I'm all set now. Thanks!
[Verizon Motorola Droid Turbo Android Development] Pukhton:
Downgrade!

can we downgrade from this version to SU4TL-44? thanx!
[Verizon Motorola Droid Turbo Android Development] realbbb:
No
[Verizon Motorola Droid Turbo Android Development] Pukhton:
Confused!

:crying:

i want to know--! Why?
[Verizon Motorola Droid Turbo Android Development] realbbb:
Motorola security measures.
[Verizon Motorola Droid Turbo Android Development] Pukhton:
No way-!

So my Droid turbo bacome just a Crap!! with FRP Lock... There is No way to Downgrade It!
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
Because SU4TL-49 (May 2016) was a trojan horse update to close the Sunshine bootloader exploit (November 2015). If you did not unlock your bootloader sometime in the last six months, you waited too late.
[Verizon Motorola Droid Turbo Android Development] Pukhton:
Thanx!

Great! Now there is no way to unlock my accidentally reset! FRP enabled! phone!:crying:
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
You can always sell it on Swappa and then buy another that has SU4TL-44 or lower.

Just make sure the previous owner didn't re-lock the bootloader before selling. Ask to see a picture of the bootloader status. Some people have found some good ones on eBay that didn't have the new update.
[Verizon Motorola Droid Turbo Android Development] Marky__Mark:
What about downgrading from with just the radios only? I only did the 49 radio and ran into issues. Lost 4G a couple days later which is weird.

---------- Post added at 07:19 PM ---------- Previous post was at 06:38 PM ----------

So I just saved my phone after flashing the 49 radio by itself and wanted to share my experience. I'm back on 44. I flashed 49 and it worked fine for a few days. Then I couldn't make any calls. Messed with it and eventually all service was dead, which was out of the blue. I reflashed 44 and it didn't work. The only thing that worked was 1. restoring my backup (gave me 3g only and service). 2. flashing the clean modem zip and 44 zip. And now all is well. So yes, do not flash the 49 radio by itself if you're not ready to add that bootloader Trojan with it. The radio isn't noticeably better anyway.
[Verizon Motorola Droid Turbo Android Development] RLShiftyDoggit:
So just to make sure what one do I flash just to update the radio (I can't remember) and can I update them I'm running RR 6.0.1 with BHB-27 kernel
[Verizon Motorola Droid Turbo Android Development] tylertitus14:
I flashed the SU4TL-49 from the OP in TWRP successfully but when I navigate to "about phone" it still lists SU4TL-44... So was flashing SU4TL-49 actually unsuccessful in reality or is this just a "glitch" and the SU4TL-49 actually flashed succesfully but is incorrectly being identified as "SU4TL-44" in the about phone settings? FYI baseband was/ still is 11.05.16.02R

I'm not going to push my luck and try to reflash it or push it via adb... Moving on to flashing computerfreeks rom now. It doesn't sound like having the latest bootloader/ radio really matters anyhow. I don't think this was a necessary step considering I was already on baseband 11.05.16.02R to begin with but figured I might as well flash the SU4TL-49 to start out with the latest stuff before flashing the ROM.

Forgive me I am a good researcher/ instruction follower, without good guidance I would be lost on this stuff. I just wanted to point out the 49/44 discrepancy in the about phone section to either report a "bug" or have someone tell me it must not have flashed correctly lol.
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
You did NOT flash SUTL-49 firmware from the OP because SUTL-49 firmware is not listed in the OP. ;) What is listed in the OP is the bootloader and radio from SUTL-49, not the complete firmware itself. Therefore, the only thing that would be updated would be those elements. Look at your BASEBAND. Or boot into the bootloader mode and look at your bootloader version. HINT: Neither one is going to say "SUTL-49". it will be the versions associated with SUTL-49.

SUTL-49 is a complete firmware image. You can get it here:

[ROM] SU4TL-49 100% Stock

http://xdaforums.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041

If you ever flash the complete firmware, THEN the firmware in your "about phone" should list SUTL-49, instead of SUTL-44.

But you will not find it in the op of this Bootloader and Radio Packages thread.

_______

The SUTL-49 baseband is this:

Does the baseband in "About Phone" and the baseband in bootloader mode show the same version? Does it show the SUTL-49 baseband in bootloader mode?

In the past when I've flashed baseband occasionally the baseband in "About Phone" does not match the baseband listed in the bootloader mode. One time for months there was no baseband listed in bootloader mode, but obviously I still had baseband. ;)
[Verizon Motorola Droid Turbo Android Development] tylertitus14:
OK, I didn't catch on to the fact it was just the bootloader and radio package and not the whole firmware package.

I just checked my baseband and now it is showing .03 not .02 I could have sworn it was still showing .02 after flashing the -49 stuff but I don't have a screen shot to support my memory. I'd say I'm bout 90% sure (and I'm only ever 95% sure of anything :p) it stayed .02 last night after I flashed the -49 stuff. I have done quite a few reboots since then so I suppose it could have "caught up". I will check the bootloader mode for its version and report back (I'm on the device typing this now).

May I ask a dumb question? Why go thru the trouble of separation the newer bootloader and radio package from the -49 firmware? Is there a problem with just flashing the complete -49 firmware after you've unlocked your bootloader? Forgive me if this is a dumb question lol
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
Because unless you are on stock ROM (and most people on XDA run custom ROMs, custom kernels), all you need from "stock" is the newest radio.

Everything else is supplied by the XDA devs, even my custom boot logo. ;)

http://xdaforums.com/moto-maxx/themes-apps/moto-maxx-black-motorola-logo-boot-t3065141

There's a great demand for just various radio packages.

For instance there's a stock Marshmallow ROM originally intended for Brazil QUARK, and [MENTION=7109882]iiWoodstocK[/MENTION] adapted it to work for all Quarks. But it uses the radio you have installed. So, XT1254 Droid Turbo owners can grab just the radio from here. Even though it is still Lollipop radio, it will work fine.

_________

[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]

http://xdaforums.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234

If you flash it you have to be rooted and have TWRP installed. Verizon's VoLTE will not work on the Droid Turbo, but everything else does. It's pure factory Marshmallow for ANY Quark -- XT1254, XT1250, XT1225. It will use whatever radio you already have installed.

______

And sometimes the "newest" turns out to not be the "best". Sometimes an older radio might actually work better. Thus SUTL-44 radios are also listed.

When i had the Galaxy Nexus, it seemed like the radio for another continent worked better for me here in Atlanta than the "North America" radio. Same model number, same bands. They both had the same bands, but obviously there had to be some difference or Google would have just one radio package for that model number.
[Verizon Motorola Droid Turbo Android Development] tylertitus14:
All makes sense, thanks for the reply.

I came from a Galaxy Nexus to the turbo when it came out. Reception was always pretty awful on the gnex for me. Two different g nexes, stock, rooted, different radios, etc it always performed worse than another vzw phone beside it. Still loved the phone tho.
[Verizon Motorola Droid Turbo Android Development] Claps1775:
Downloading our .49 twrp package and also ComputerFreaks 1.3.7 rom. Lets see how this goes. Even though some say they do not see much difference in the .44 to .49 radios. Why not have the newest radios? No need to worry about unlocking the Bootloader again since this will not lock it. Thank you for your work [MENTION=2730403]firstEncounter[/MENTION].
[Verizon Motorola Droid Turbo Android Development] mubaidr:
Bootlaoder and modems from 3.01 update available?
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
Be more specific. What is 3.01? Is that a date? Some version number? What is it?
[Verizon Motorola Droid Turbo Android Development] mubaidr:
Oops. Sorry, i meant to write 6.01. :/