Related
I think this is some good news at some point. http://motorola-blog.blogspot.com/2013/11/you-asked-we-listened-announcing.html?m=1
For customers who have previously purchased a 2012 or 2013 Developer Edition device directly from Motorola and who have requested a bootloader unlock code, we will reinstate the warranty effective from the date of original purchase.
i like this line..
meaning if you had one of these phones and it had some issues, you still cant send it in cause it will be out of warranty.
they should start the warranty from now. so you would at least have a chance to send it in.
Well that's very, very good news. Means we can buy a Moto G, unlock the bootloader, flash roms, and participate in rom development -- all without fear of being out of warranty. That right there is my incentive to upgrade -- just having my phone under warranty would be a nice feeling...Officially, my AHD warranty goes up in 4 months, so the ability to get an unlocked Moto with warranty coverage in 2 months is awesome (or and X Dev now...but I can't afford that).
Also means they'll be releasing the Atrix HD Developer Edition fastboot
I wonder which OS it will have.....assuming ICS, but KK or JB would be pretty cool too.
I'm going to get flamed for this but I'm getting irritated with Verizon or Motorola on how long this is taking. The 4.4 update took 4 weeks max and was a big update and this "minor" update has taken 2 months.....I don't understand what the hold up is. I bought this phone off contract because I wanted a phone that would receive updates relatively quickly and based my decision on the fast update to KitKat. I know there are a few Moto people here.....any insight on the delay? I do understand this is minor....just like being up to date. Okay...everyone yell at me for asking about this .
I'm used to updates taking 6-12 months, so I'm not complaining. It hasn't been that long since the last update.
sent from LenoMoto X
Ryno77 said:
I'm going to get flamed for this but I'm getting irritated with Verizon or Motorola on how long this is taking. The 4.4 update took 4 weeks max and was a big update and this "minor" update has taken 2 months.....I don't understand what the hold up is. I bought this phone off contract because I wanted a phone that would receive updates relatively quickly and based my decision on the fast update to KitKat. I know there are a few Moto people here.....any insight on the delay? I do understand this is minor....just like being up to date. Okay...everyone yell at me for asking about this .
Click to expand...
Click to collapse
Reason why because people are going to hard brick the frigging devices, all unlockable boot loader firmware will be sent out first to see how things go, at that point moto will send out Verizon and at&t firmware and watch all the hard bricks that happen, hope I'm wrong .
Sent on my Lenoto A2109 tablet
How come with have a 4.4.2 deodexed verison for Verizon? Isnt that the release?
flashallthetime said:
Reason why because people are going to hard brick the frigging devices, all unlockable boot loader firmware will be sent out first to see how things go, at that point moto will send out Verizon and at&t firmware and watch all the hard bricks that happen, hope I'm wrong .
Sent on my Lenoto A2109 tablet
Click to expand...
Click to collapse
Well, that's a reasonable explanation . Why are they messing with the bootloader with every update? I think it was you that posted in another thread about PM'ing this info rather than posting it on an open thread? If you don't mind I'd appreciate your explanation on this..If it's not a hassle PM'ing me with the info you have would be very much appreciated. Thanks.
The first update was a special occasion. Verizon never pushes crap out that fast. Money changed hands to get the first X and G updates through carriers ASAP is my guess. The carriers also got burned by the 4.4 exchange bugs which have probably been causing thousands of customer service calls and returns.
We're on a more normal schedule now, although still faster than Samsung or HTC as there is little to modify. Expect Verizon to be last with a 3-6 month delay for updates. Sunday will be 2 months since 4.4.2 pushed to the nexus 5. I would still be (pleasantly) surprised if we saw it before March or even April.
If you bought this phone thinking every update would be within weeks I'll remind you than a single data point does not make a trend.
Sent from my XT1060 using Tapatalk
Ryno77 said:
Well, that's a reasonable explanation . Why are they messing with the bootloader with every update? I think it was you that posted in another thread about PM'ing this info rather than posting it on an open thread? If you don't mind I'd appreciate your explanation on this..If it's not a hassle PM'ing me with the info you have would be very much appreciated. Thanks.
Click to expand...
Click to collapse
Verizon and at&t have locked boot loader on their consumer version, we all know about slapmymoto and all the root hacks, so does moto. The reason why the eliminated boot loader downgrade is due to slapmymoto, no other reason to do it. Just my thoughts . Moto left the vulnerability in the 4.4 upgrade , well its gone now so it should decrease hard bricks in theory but there's always someone who wants to stick a square peg in a round hole
Sent on my Lenoto A2109 tablet
I'm pretty sure downgrading the bootloader hasn't been possible on many recent moto phones. I agree that it's likely to prevent exploits, but it's not something new or unique to the X
Having just received my Verizon Dev Ed only a week or so ago, it updated to 4.4 almost immediately. What's better about 4.4.2?
We should also stress that some people have the update. Motorola is known for doing "Soak Tests" which, is a good idea. For production devices even if you HAVE all the specs on the device and drivers and such with the source code for them so as a developer you can go and in really look at everything... Takes time to not only make sure it works with the device on a basic level (compiles, boots, phone calls, etc..) there is the fact that bugs crop up and I have read a lot of things about it being pulled because of devices being locked - that of course has to be solved and since each device comes with a bootloader for the carrier it is on (unless I'm wrong in that since Sprint uses the 1060 as well and has the update) I would imagine Verizon is being cautious and giving it extra time. Perhaps Verizon noticed some bugs and the other carriers said to release and work on a fix later and Verizon said - no, fix it first.
I know it is hard to think of Verizon as a 'good guy' like that but it is possible, last thing they need is another phone update the kills devices - they've played that game before.
Anyway, just my two cents worth. I think it is being tested and tweaked before release.
Comparing this to the fact that my Galaxy Note 8.0 (which has no carrier cruft) still is on v4.2.2 and has been since October, so... I'm pretty happy with waiting a few months knowing that they'll get it out to me for the Moto X.
Roland Stone said:
What's better about 4.4.2?
Click to expand...
Click to collapse
My question exactly. I bet most people who harp about updates don't even know what the changes are. I have 4.4.2 on my N7 and I can't tell a difference in performance compared to 4.4. Most of the changes are camera related for the N5 and N7 which doesn't affect the Moto x's camera since it's updates come from the play store.
flashallthetime said:
Reason why because people are going to hard brick the frigging devices, all unlockable boot loader firmware will be sent out first to see how things go, at that point moto will send out Verizon and at&t firmware and watch all the hard bricks that happen, hope I'm wrong .
Sent on my Lenoto A2109 tablet
Click to expand...
Click to collapse
You're not wrong. LOL. Unfortunately.
Sent from my Moto X cellular telephone...
Verizon customer complaining about slow updates? Surprise surprise. Dude there are phones on Verizon right now that are still on 4.1-4.3 I'd relax and thank my lucky stars Motorola is only taking months instead of years.
If fast updates were so important you should have gotten a developer edition. I've had 4.4.2 for at least a week now and I had most of the 4.4 bugs fixed months ago
MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
SymbioticGenius said:
Verizon customer complaining about slow updates? Surprise surprise. Dude there are phones on Verizon right now that are still on 4.1-4.3 I'd relax and thank my lucky stars Motorola is only taking months instead of years.
If fast updates were so important you should have gotten a developer edition. I've had 4.4.2 for at least a week now and I had most of the 4.4 bugs fixed months ago
MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
Click to expand...
Click to collapse
Developer Editions don't get updates any faster than non-DE versions. The carriers still have to release the updates. I have a VZW DE, and I do not have 4.4.2 yet.
You do realize that you can install it yourself right? There are images all over the place now.
MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
SymbioticGenius said:
You do realize that you can install it yourself right? There are images all over the place now.
MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
Click to expand...
Click to collapse
I don't think there are Verizon/xt1060 4.4.2 images available yet. There are 4.4 images readily available though,
SymbioticGenius said:
You do realize that you can install it yourself right? There are images all over the place now.
MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
Click to expand...
Click to collapse
I understand I can flash the system image from another service provider. Everything I've come across is a sbf file....I can't flash just system from that can I? My last two phones have been from Samsung so I'm not too familiar with this stuff yet.
Ryno77 said:
I understand I can flash the system image from another service provider. Everything I've come across is a sbf file....I can't flash just system from that can I? My last two phones have been from Samsung so I'm not too familiar with this stuff yet.
Click to expand...
Click to collapse
I highly discourage you from doing this. There have been several people bricking by flashing the wrong thing. I almost bricked mine, but was able to save it. Then I had to spend 2 hours on the phone with Verizon because something I flashed made my phone show up as a non-Verizon device and temporarily blacklisted it. It now registers as a test device in Verizon's system, and I don't know what the implications of that is if I try to sell it later to someone else.
It was absolutely not worth it and I should have waited for my carrier to officially release an upgrade. I'm sure some here will disagree with me, but I'm telling you from personal experience.
Mr. Orange 645 said:
I highly discourage you from doing this. There have been several people bricking by flashing the wrong thing. I almost bricked mine, but was able to save it. Then I had to spend 2 hours on the phone with Verizon because something I flashed made my phone show up as a non-Verizon device and temporarily blacklisted it. It now registers as a test device in Verizon's system, and I don't know what the implications of that is if I try to sell it later to someone else.
It was absolutely not worth it and I should have waited for my carrier to officially release an upgrade. I'm sure some here will disagree with me, but I'm telling you from personal experience.
Click to expand...
Click to collapse
Yes..this. be patient. 4.4.2 won't change your life or anything.
Sent from my Moto X cellular telephone...
I to agree with the previous poster, as you said you came from a Sammy product, forget and throw all the past experience with Sammy out the window. Moto is a totally different beast. Wait till your sbf firmware is available and flash that. I have seen to many know it alls royally screw their brand new moto's up. Patience soon all will be for told , I can see in the not so distance future the 4.4.2 update
Sent on my Gummy running Lenoto X
i hope the devs support the droid turbo.
verizon locks down the droid tight.
With the nexus 6 also coming out it'll be a coin toss. Motorola has been cool about it since Google had it but now Lenovo takes over...
i think Sunshine V3.0 will work.. fingers crossed.
its so similar in hardware to nexus 6, time will tell.
Jaocagomez said:
its so similar in hardware to nexus 6, time will tell.
Click to expand...
Click to collapse
I think the comparison would be to a moto X 2nd Gen. It's got more similar firmware.
Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
Jaocagomez said:
its so similar in hardware to nexus 6, time will tell.
Click to expand...
Click to collapse
It literally takes ONE TINY THING which has nothing to do with advertised specs to make the phone bullet proof, or at least impermeable by usual means.
http://forum.xda-developers.com/showpost.php?p=56172538&postcount=20
jmonroe0914 said:
If you're going to comment on a dev forum, at least understand the terminology before you use it... otherwise it makes you seem ignorant. "UNLOCKED" and "UNLOCKING THE BOOTLOADER" are two very different things that have ZERO to do with one another.
All LTE CDMA phones for the past 2 years that use a SIM are "unlocked", as this refers to the carrier lock that is placed on the device when it is sold in bulk to network providers (which is why you have three network settings in your phones setting menu - LTE, GSM, and Global). Don't use terminology you don't understand, as you're adding to the ignorance too many seem to have about what unlocking is and what unlocking a bootloader is. It makes it only that much harder for other individuals to get the correct information, and is the reason why a VZW rep tried to tell me I don't need a developer edition to unlock my phone, because all LTE devices are unlocked when I tried to explain I was looking for a developer edition so I could unlock the bootloader.
Very few Verizon phones have the capability to unlock the phone's bootloader, which allows for rooting without an exploit and the ability to flash custom ROMs (firmware), such as Cyanagenmod. Those of you believing root will appear on any new Motorola phones are not well versed in Motorola phones sold by Verizon. Dan Rosenberg, who is the person anyone with a Motorola device on Verizon has to to thank for the last half decade of being able to root your Motorola VZW phones, has repeatedly posted on numerous threads for over a year to not expect for your Motorola devices to be rooted and if you want root, either buy a Nexus or buy a Developer Edition (if VZW is going to release any more editions after the S5 is not known and information about Developer Editions for the Note 4 Droid Turbo have been repeatedly ignored by VZW's Public Affairs office). This is due to the fact VZW has wizened up and made finding an exploit on anything past 4.4.4 nigh impossible. Exploits that allow root access are not easy to find (taking several months for most VZW Moto root exploits) and as soon as one is found, within a matter of weeks, if not days, VZW will push an automatic update, forcing your phone to update to patch the exploit. This is why when you root your phone you're told to disable OTA updates at the apk level by freezing the update apk or removing it all together after making a backup of it.
Many Motorola users got a surprise in late Spring when a Moto employee "accidentally" included the exploited code that allowed you to blow the fuse and unlock the bootloader of devices running 4.4.2. That was a once in a billion opportunity that will probably never happen again. Every time an exploit has been found that allowed root access or the ability to unlock the bootloader (which was only recently cracked in the past year, possibly two... to put that in perspective, it took over half a decade for Dan Rosenberg to find the exploit that allowed the internal fuse to be blown, unlocking the bootloader). Exploits are not easy things to find, especially in Motorola devices running on VZW's network.
To all of those that like to post root bounties... BUY A DEVELOPER EDITION. You'll pay $300 for a device and then offer $300+ for a root bounty... which is the cost of developer edition device... considering VZW offers Edge, you no longer have to pay full retail in one go for a DE. From this point forward, VZW customers need to comprehend the fact that rooting will continue to be increasingly difficult to perform, most especially on Moto phones running on VZW's network. If you want root access, buy the S5 developer edition or wait until the first week of december to see if a developer edition for the Note 4 will be released (if a Note 4 DE is going to be released, it will occur within the 4 - 6 weeks following it's RTM on 10/23 [Thursday]).
Click to expand...
Click to collapse
The answer is no, you will probably never see a root exploit for the Droid Turbo. The person above linked to one of my prior posts on a different thread, and it comes down to two fundamental facts... there is probably not going to be a DE of the Turbo because of the Nexus 6, and rooting a non-bootloader unlocked device once it's running Android 5.0 [Lollipop] and beyond is damn near impossible. The latter has to do withe SELinux and how Google locked down the partitions and permissions. ChainFire wrote two posts on Google+ that explain in great detail why those without unlocked bootloader can kiss rooting goodbye. It's not impossible, however it is highly improbable a root exploit will be found, in the same way it's possible the Earth could be hit today by a 5 mile wide asteroid, but it's highly improbable.
The new security features Google built into Android 5.0 is a double edged sword... on one hand they've finally addressed issues that, as of today, make Android the least secure OS on the market; however, the security that all of us most definitely want makes it highly unlikely a root exploit could be run on a non-bootloader unlocked device. The only reason it would work on an unlocked bootloader device is because a previous kernel could be flashed that would allow the exploit to run at bootup (flashing kernels is prevented by locked bootloaders).
Sent from my SM-N910V using Tapatalk
I hope so
So, I just got this Moto X not an hour ago that's a "replacement exchange" for the Atrix HD that bricked with Motorola's last update from 2014. Took 2+ months of online chats, phone calls, etc to get them to at least do something to alleviate the situation caused by their own update. But enough of that...
What they sent me is an apparently brand new never ever used (not even refurbished) white Moto X with a label on the box dated Sept 25 2013 (verified the bar codes upon booting it the first time). It's running Android 4.2.2 and it appears to have a bootloader of 30.70 (yes, thirty dot seventy) so, obviously I grabbed Sunshine to see if it would work and it passed all the tests with flying colors as expected but I'm not sure I want to go that far.
The issue for me is that it's one of those dreaded scumbucket Moto X models that has the IMEI number starting with 35321 which means it can't or won't be carrier/SIM unlockable by anyone, not AT&T and certainly not Motorola.
Since that would mean it's locked down with AT&T and I won't use AT&T - diehard fan of T-Mobile for years now with that still awesome $30/month 5GB plan - I'm wondering what I should do with this thing.
I wouldn't suspect that having the full capabilities of accessing this device will matter with respect to it remaining carrier locked, i.e. even with a properly unlocked bootloader and s/off if I were to muck around with the CID/MID stuff that still wouldn't help me like if I converted it to the "Developer Edition" or even the XT1053, the T-Mobile variant, it'll still be carrier locked to AT&T forever.
If I'm wrong there I'm hoping that someone reading this will chime in about it but, for the moment it seems I've got a brand new Moto X that I can't even use, sadly. Thinking about putting it on craigslist for $125 and just moving on, I'm kinda sick of Motorola's crap over the years. Was an Atrix 4G owner and waited on ICS which they promised but never delivered, owned a Photon and they promised ICS and never delivered, and so on.
I think I'm going to start saving up for the LG G4 which appears - at least from the currently available info - to be the wicked evil cool smartphone I've been waiting on for years now...
I'm wondering, if any of you were in the same situation, what would you do with this somewhat rarity in the Moto X world nowadays, a pristine untouched 4.2.2 device with an original bootloader just waiting for possibilities?
Keep it, sell it... I wonder.
Auction it on eBay and post the link here
Not a big fan of auctions, and since I don't do them with any regularity if I did that even if I made some money from it PayPal would make me wait a month to claim the funds, unfortunately.
It's listed on craigslist for $125 and will more than likely disappear in the next few hours, who knows.
Hello, i have a Motorola Droid turbo stock, with ultimate release android 5.1.. I noto can unlock bootloader whit sunshine apk.. I try can forum officiale Motorola whit code bootloader and not found compatibility.. Please help me to unlock bootloader, i can flash cm13
SylarScareCrow said:
Hello, i have a Motorola Droid turbo stock, with ultimate release android 5.1.. I
noto can unlock bootloader whit sunshine apk..
I try can forum officiale Motorola whit code bootloader and not found compatibility..
Please help me to unlock bootloader, i can flash cm13
Click to expand...
Click to collapse
What is "ultimate release 5.1"?
Which factory image version? If you took the 5.1-SU4TL-49 update you are out of luck.
Read this:
http://forum.xda-developers.com/showthread.php?p=66869729
jcase said:
Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader.
If you are already unlocked, you are fine (dont relock it!).
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
Click to expand...
Click to collapse
People stop taking the OTA update! It's only to prevent you from unlocking your bootloader! Verizon is evil, don't you understand?
Of all the Quarks, only the Verizon one (Droid Turbo XT1254) cannot be unlocked from the Motorola website. Because Verizon demands Motorola keep the bootloader locked down.
All the other Quarks (U.S. Moto Maxx XT1250, International Moto Turbo/Moto Maxx XT1225) can easily be unlocked with a code from Motorola.
So, when an exploit is found (Sunshine) to forcibly unlock the bootloader, of course any Verizon update AFTER that will be to prevent that exploit from working. Duh. Because Verizon is evil.
Yes have a su4tl-49 ((
ChazzMatt said:
What is "ultimate release 5.1"?
Which factory image version? If you took the 5.1-SU4TL-49 update you are out of luck.
Read this:
http://forum.xda-developers.com/showthread.php?p=66869729
People stop taking the OTA update! It's only to prevent you from unlocking your bootloader! Verizon is evil, don't you understand?
Click to expand...
Click to collapse
SylarScareCrow said:
Yes have a su4tl-49 ((
Click to expand...
Click to collapse
Very sorry. Nothing you can do. Thank Verizon.
Is impossibile a sunshine.apk update for this problemi in future?
ChazzMatt said:
Very sorry. Nothing you can do. Thank Verizon.
Click to expand...
Click to collapse
SylarScareCrow said:
Is impossibile a sunshine.apk update for this problemi in future?
Click to expand...
Click to collapse
@jcase, whom I quoted above is the Sunshine guru. He says no. (Edit: See below. He says maybe. But the last one took a year to find.)
The Sunshine exploit worked on SU4TL-44 Stock. If you go past that, you are out of luck. The recent OTA update closes that loophole and you cannot revert firmware.
It took a year to even find the first exploit and it was unique to Snapdragon 805. The Verizon Droid Turbo is a late 2014 phone. Even if there was another exploit, it takes time and money to find them, bricking phones in the process. This is why the first exploit was packaged into $25 fee, to compensate the devs and fund their research.
This phone isn't even being made anymore, so investing any more time and money to find another exploit for people who take OTA updates without investigating is probably not going to happen, for a phone that will soon be 2 years old. There are many other newer phones that can get the attention.
People on Verizon who REALLY want a "Droid Turbo" with a bootloader that can easily be unlocked will buy the U.S. Moto Maxx XT1250. Same device as the Droid Turbo, same bands, same hardware, same FCC ID. And bootloader can be unlocked via Motorola website.
IF you don't have Verizon and don't need CDMA bands (or LTE band 13), then the XT1225 is even better. More HSPA bands, more LTE bands. LTE bands 2, 3, 4, 5, 7, 17. And bootloader can be unlocked via Motorola website.
They are all Quarks with the same hardware. The XT1254/XT1250 even share the same radio bands, same FCC ID. The XT1225 has different radio bands.
SylarScareCrow said:
Is impossibile a sunshine.apk update for this problemi in future?
Click to expand...
Click to collapse
Answer is maybe. We wont be investing in another round of research for the Droid Turbo itself, if we have some research on another device that crosses over with the Turbo then maybe. A small maybe.
You're all just front runners of a arrogant and pointless waste of time... Let's investigate this and fund this for $25 so the dev can get rich on something he stole from someone else and takes the money and credit. But he'll yea, let's keep cheating people out of money and point the finger at noobs and other individuals that don't spend pointless and limitless time on browsing lines of code, just to say I know how to flash this and exploit that. Listen,......who gives a **** buddy. Another thing, don't belittle someone that doesn't have the same knowledge and asks the "annoying" questions..... We people of the society have other things we are doing, besides having a phone in one ear and a keyboard typing in commands in abd fastboot crammed up our ass.... Thanks..."Fin"
Causticcatalyst said:
You're all just front runners of a arrogant and pointless waste of time... Let's investigate this and fund this for $25 so the dev can get rich on something he stole from someone else and takes the money and credit. But he'll yea, let's keep cheating people out of money and point the finger at noobs and other individuals that don't spend pointless and limitless time on browsing lines of code, just to say I know how to flash this and exploit that. Listen,......who gives a **** buddy. Another thing, don't belittle someone that doesn't have the same knowledge and asks the "annoying" questions..... We people of the society have other things we are doing, besides having a phone in one ear and a keyboard typing in commands in abd fastboot crammed up our ass.... Thanks..."Fin"
Click to expand...
Click to collapse
Actually the blame all rests on Verizon for demanding Motorola lock the bootloader. Other Quarks -- even one IDENTICAL to the Droid Turbo sold under another model name -- are not locked down. Verizon is the villain.
Credit goes to any devs who create a workaround. But it's not always possible. The exploit found took a year of research, bricked phones, etc to find. Nobody "stole" anything. The exploit was published publicly. You can write an installer yourself if you have the skill, and give it away for FREE. The fact that no one else has done so means there must not be that much demand.
But if you took the recent Verizon SU4TL-49 OTA update, you are out of luck. Simple as that. Verizon is to blame -- but so are the users who blindly take an update from an evil carrier who locks down bootloaders. The dev even created an XDA thread specifically warning people NOT to take the update! Don't know what else could be done except for owners to take some responsibility and exercise common sense?
If you are on a carrier locked down bootloader phone, and you are wanting to escape from that prison, you should know not to take any carrier OTA updates until you investigate WHY the update was published -- in this case to specifically shut down that exploit.
Of course anyone who buys this phone KNOWS it's locked down and shouldn't expect a bootloader unlock in the first place. Anyone who buys it, KNOWS it's crippled. They need to buy another Quark, like the XT1250 U.S. Moto Maxx -- which is the exact same device as the Droid Turbo XT1254 with Verizon bands and everything. Droid Turbo owners were just very lucky a dev created an exploit that could unlock the bootloader for one version of firmware.
Wonder why you created this new user name to post this one response? Already an XDA member and don't want to burn your regular user name? Or just a lurker who took the OTA update, huh? Blame Verizon and yourself, not the messengers. You bought the phone, knowing it was locked down. It's Verizon. That's what they do.
So, there was a brief window of escape, starting last November on firmware SU4TL-44 . The Sunshine devs gave you that window of freedom and somehow you are mad at them?
The locked down Droid Turbo anyone bought is STILL the locked down Droid Turbo they bought. It still functions just like it was bought. No one has harmed their phone. The only difference is if you take the SU4TL-49 OTA update it will remain locked down -- whereas before that OTA thanks to Sunshine you could unlock it, install custom recovery, root, custom ROMs. If that's important to you, then yeah, you do some research first here on XDA or even just using Google. (I never buy a phone I can't unlock the bootloader and root.)
But if you don't do research first, then obviously unlocking the bootloader is not that important to you? And the phone functions just like when you bought it.
Well folks I hate to say it but all I did was call Motorola, told them I have a droid turbo and in the developer settings there is a key to unlock OEM bootloader but does nothing. They asked for my email and sent me the complete link as to unlock the bootloader. BAM! I'M UNLOCKED!!!
butler911 said:
Well folks I hate to say it but all I did was call Motorola, told them I have a droid turbo and in the developer settings there is a key to unlock OEM bootloader but does nothing. They asked for my email and sent me the complete link as to unlock the bootloader. BAM! I'M UNLOCKED!!!
Click to expand...
Click to collapse
Wait , what? Can you share little more info on this?? Which phone exactly you have?
EDIT: Tried this right away, of course it didn't work . They told me that it's not part of unlockable bootloader program, but to check often because they very often add new phones to the program.
Also , on the link they gave me, I don't see Moto Maxx either https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215
butler911 said:
Well folks I hate to say it but all I did was call Motorola, told them I have a droid turbo and in the developer settings there is a key to unlock OEM bootloader but does nothing. They asked for my email and sent me the complete link as to unlock the bootloader. BAM! I'M UNLOCKED!!!
Click to expand...
Click to collapse
how to set phone in developer setting? maybe not all the phone can get the unlock code.
EjđiSixo said:
Also , on the link they gave me, I don't see Moto Maxx either https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215
Click to expand...
Click to collapse
Doesn't show up for Moto Maxx, but it works anyway. It did show up in previous version of website. And owners recently are still getting their XT1225/XT1250 unlocked, as evidenced by questions in my Moto Maxx/Moto Turbo guide in the other forum. So, it still works for those phones.
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
butler911 said:
Well folks I hate to say it but all I did was call Motorola, told them I have a droid turbo and in the developer settings there is a key to unlock OEM bootloader but does nothing. They asked for my email and sent me the complete link as to unlock the bootloader. BAM! I'M UNLOCKED!!!
Click to expand...
Click to collapse
Pictures or it didn't happen.
Show us bootloader status picture.
That will prove everything you just said, that you actually have a Droid Turbo and the bootloader is indeed unlocked. Extra credit if you post the communication from Motorola.
ChazzMatt said:
Doesn't show up for Moto Maxx, but it works anyway. It did show up in previous version of website. And owners recently are still getting their XT1225/XT1250 unlocked, as evidenced by questions in my guide in the other forum. So, it still works for those phones.
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
Pictures or it didn't happen.
Show us bootloader status picture.
That will prove everything you just said, that you actually have a Droid Turbo and the bootloader is indeed unlocked. Extra credit if you post the communication.
Click to expand...
Click to collapse
Probably had moto maxx or noob assistent gave code without knowing they can although I don't think they can do that, system would probably block it.
butler911 said:
Well folks I hate to say it but all I did was call Motorola, told them I have a droid turbo and in the developer settings there is a key to unlock OEM bootloader but does nothing. They asked for my email and sent me the complete link as to unlock the bootloader. BAM! I'M UNLOCKED!!!
Click to expand...
Click to collapse
EjđiSixo said:
Probably had moto maxx or noob assistent gave code without knowing they can although I don't think they can do that, system would probably block it.
Click to expand...
Click to collapse
I'm very skeptical of someone with just two posts. Trolls do abound, you know. I prefer more proof than someone just typing a few taunting words into a forum. I would be curious if he was already on Marshmallow when this alleged bootloader unlock code was given.
About a year ago, someone posted how he had "flashed a Nexus 6 ROM" over his Droid Turbo and it "worked perfectly" and encouraged everyone else to do the same. 2014 Shamu and Quark were both released by Motorola at the same time, share a lot of the same specs -- and well known Motorola had a 5.2" Shamu variant in testing as late as mid-August 2014. But Google chose the 6" WHALE to be the only gen6 Nexus phone. Quark in many ways is the sibling to Shamu (perhaps the 5.2" was even re-purposed for Quark?), very similar to how the 2013 LG Nexus 5 and LG G2 were developed at the same time on parallel path by LG. BUT, you can't flash Nexus 6 (Shamu) ROMs over Quark, so matter how much you might envy Nexus development.
The only way you can do that is to disable some safety measures, and yes if you are silly enough you can brick your phone. Basically he had bricked his phone and was mad -- and misery loves company. The thread was quickly locked and everyone was told NOT to even try it.
My point is you can't believe everything someone types unless they offer some kind of proof.
ChazzMatt said:
I'm very skeptical of someone with just two posts. Trolls do abound, you know. I prefer more proof than someone just typing a few taunting words into a forum. I would be curious if he was already on Marshmallow when this alleged bootloader unlock code was given.
About a year ago, someone posted how he had "flashed a Nexus 6 ROM" over his Droid Turbo and it "worked perfectly" and encouraged everyone else to do the same. 2014 Shamu and Quark were both released by Motorola at the same time, share a lot of the same specs -- and well known Motorola had a 5.2" Shamu variant in testing as late as mid-August 2014. But Google chose the 6" WHALE to be the only gen6 Nexus phone. Quark in many ways is the sibling to Shamu (perhaps the 5.2" was even re-purposed for Quark?), very similar to how the 2013 LG Nexus 5 and LG G2 were developed at the same time on parallel path by LG. BUT, you can't flash Nexus 6 (Shamu) ROMs over Quark, so matter how much you might envy Nexus development.
The only way you can do that is to disable some safety measures, and yes if you are silly enough you can brick your phone. Basically he had bricked his phone and was mad -- and misery loves company. The thread was quickly locked and everyone was told NOT to even try it.
My point is you can't believe everything someone types unless they offer some kind of proof.
Click to expand...
Click to collapse
Your very correct and I do want to say that this is an excellent site with very true and capable designers! Trust me I'm absolutely no troll, I hate them, I was just simply putting my experience out there for others to try. I meant no disrespect or meant to step on anyone's toes. My apologies
butler911 said:
Your very correct and I do want to say that this is an excellent site with very true and capable designers! Trust me I'm absolutely no troll, I hate them, I was just simply putting my experience out there for others to try. I meant no disrespect or meant to step on anyone's toes. My apologies
Click to expand...
Click to collapse
You're not stepping on anyone's toes. If true, then somehow you gamed the system in a way no one has been able to do. Congratulations on your good fortune!
Just asking for a couple of screenshots for proof, maybe the Motorola communication? Maybe someone else can do the same?
Were you on stock Lollipop or Marshmallow?